IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Error when compiling a REXX exec with "OUTTRAP"


IBM Mainframe Forums -> CLIST & REXX
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Ricardo Viegas

New User


Joined: 18 Oct 2012
Posts: 39
Location: Brasil

PostPosted: Tue Dec 18, 2018 5:44 am
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 Moderator


Joined: 14 Mar 2007
Posts: 10730
Location: italy

PostPosted: Tue Dec 18, 2018 12:36 pm
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: 39
Location: Brasil

PostPosted: Wed Dec 19, 2018 4:07 am
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 View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CLIST & REXX

 


Similar Topics
Topic Forum Replies
No new posts How to replace a string dynamically i... CLIST & REXX 16
No new posts Determine Library REXX exec was execu... CLIST & REXX 7
No new posts Secondary index error while loading d... IMS DB/DC 2
No new posts Error 0C1 Reason Code 1 with branch i... PL/I & Assembler 3
No new posts Any examples of calling FTP from REXX? CLIST & REXX 1
Search our Forums:

Back to Top