Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Error when compiling a REXX exec with "OUTTRAP"

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CLIST & REXX
View previous topic :: :: View next topic  
Author Message
Ricardo Viegas

New User


Joined: 18 Oct 2012
Posts: 38
Location: Brasil

PostPosted: Tue Dec 18, 2018 5:44 am    Post subject: Error when compiling a REXX exec with "OUTTRAP"
Reply with quote

Following code:

Code:
X = OutTrap('line_trap.', 2, , 7)


is inside a REXX program.
When program is run interpreted, it runs perfectly normal.

Following error is show when trying to compile it:

Code:
      194      X = OutTrap('line_trap.', 2, , 7)
               |                                     
+++FANGAO0774I Number of arguments in standard function not valid


The format is correct, accordingly to the REXX manual.
At the Compiler Guide manual there is no reference to any special action needed related to the OUTTRAP function.

Does anybody faced same problem, and was able to find a solution to it?
Thanks!
Back to top
View user's profile Send private message

enrico-sorichetti

Senior Member


Joined: 14 Mar 2007
Posts: 10632
Location: italy

PostPosted: Tue Dec 18, 2018 12:36 pm    Post subject: Reply to: Error when compiling a REXX exec with "OUTTRAP"
Reply with quote

add the unspecified argument CONCAT/NOCONCAT and see what happens
Back to top
View user's profile Send private message
Ricardo Viegas

New User


Joined: 18 Oct 2012
Posts: 38
Location: Brasil

PostPosted: Wed Dec 19, 2018 4:07 am    Post subject:
Reply with quote

I created a REXX exec with 3 lines only, just to test your recommendation, it worked OK, with or without the "NOCONCAT" parameter.
The message appears in any situation, but it is only an informational message (it ends with "I"), and the member with the compiled REXX is created.

The original program used the initialization format of OUTTRAP in four different places, and when it was compiled the compiler generated the 4 informational msgs plus a severe one related to another error, and ended with RC=12.

I tried many options to solve the OUTTRAP msg (including the use of NOCONCAT), and always received the RC=12, because of the other error, and never realized that!
So I decided to execute the interpreted version, and the reason it finished successfully was that the piece of code containing the severe error was never executed.

Sorry for not realizing this from the start, but anyway, thanks for the suggestion - with it I was able to find that there was no problem at all with the compilation of the OUTTRAP function.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CLIST & REXX All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts DB2 Block insert (-803 Error Handling) NJDevils28 COBOL Programming 5 Mon Nov 11, 2019 7:54 pm
No new posts Can you manually set an EOF marker in... Don Allard CLIST & REXX 5 Sat Nov 02, 2019 12:30 am
No new posts Running a REXX exec program using ZOSMF Sakthi344 CLIST & REXX 2 Tue Oct 15, 2019 3:13 pm
No new posts REXX VSAM Harold Barnes CLIST & REXX 3 Sat Oct 05, 2019 2:38 pm
No new posts REXX for Reading SMF type 70-1 AdrielGB Testing & Performance analysis 6 Sat Oct 05, 2019 3:03 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us