IBM MAINFRAME HELP & SUPPORT FORUMS
Technical Forums for IBM Mainframe Applications like COBOL, JCL, CICS, DB2, FileAid, DFSORT, Endevor, Xpediter, CoolGen, CA-7&11, AbendAid, IMS, IDMS, PL/I, MqSeries, SyncSort, Assembler, ChangeMan, Easytrieve, InterTest, REXX, CLIST etc...
 

Trapping WTO messages

THIS IS AN ARCHIVE FORUM: CLICK HERE TO GO TO THE ORIGINAL TOPIC

 
       IBMMAINFRAMES.com - IBM Mainframe Support Forums Index -> CLIST & REXX
View previous topic :: View next topic  
Author Message
spanda



Joined: 31 Aug 2005
Posts: 49
Location: U.K.

Posted: Thu Dec 08, 2005 10:39 pm    Post subject: Trapping WTO messages  

Hi all,

I have a piece of rexx code that calls an assembler program to do someting. The assembler program validates the inputs and issues WTO (Write To Operator) messages for invalid input or in case of errors.

Is there any way to trap these WTO messages? If I could trap these messages, then I could handle the conditions better. Has anybody ever tried this?

Any help will be appreciated.

Thanks,
Panda.
Back to top  
ofer71



Joined: 27 Dec 2005
Posts: 1959
Location: Israel

Posted: Tue Dec 27, 2005 12:56 pm    Post subject:  

Hi -

Unfortunately, there is no way to trap TPUT and WTO messages in pure REXX (see the OUTTRAP documentation).

However, you can try and read the SDSF LOG and parse the message associated with the JOBID - using batch SDSF command.

Let me know if you need an example of how to read SDSF dataset in batch (you can do that in foreground, too), or just read the fine section in the SDSF book.

O.
Back to top  
 
       IBMMAINFRAMES.com - IBM Mainframe Support Forums Index -> CLIST & REXX
Page 1 of 1
THIS IS AN ARCIVE FORUM IN READ ONLY MODE. IF YOU WANT TO ASK YOUR DOUBTS USE THE ACTUAL FORUM