I can report that even with WTPMSG in effect (it is standard here) OUTTRAP 
cannot trap WTO messages.

We don't use TSO Sess Man here so I can't answer that one.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Lennie Dymoke-Bradshaw
Sent: Wednesday, May 10, 2023 12:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

I think a WTO that is issued and then written to the TSO screen (as a result of 
PROFILE WTPMSG) must ultimately use a TPUT.
(It may even use PUTLINE, which itself then uses a TPUT.) Can these messages be 
captured by TSO Sess Man or by OUTTRAP?

Lennie

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Seymour J Metz
Sent: 10 May 2023 13:01
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

OUTTRAP is for messages written by PUTLINE and PUTGET; the TSO Session Manager 
can capture TPUT but there is no way to capture WTO directly. 

However, if you have the proper authorization (OP does not) then you can 
examine console messages with the CONSOLE facility.

________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Farley, Peter [0000031df298a9da-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, May 9, 2023 1:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Can REXX OUTTRAP trap WTO's?

Cross-posted to IBM-MAIN and TSO-REXX lists.

Is there any way for  Rexx script to capture WTO output?  This is a simple 
case, a one-line WTO, no multiline possible.

I only recently found a need to do this, and my tests so far say "no it can't".

/* Rexx */
/* Capture WTO from BATCHPGM */
xtrp = outtrap("zdsp.")
address attchmvs "BATCHPGM"
xtrp = outtrap("OFF")
say "ZDSP.1="zdsp.1

Execution result online in TSO:

*** WTO OUTPUT FROM BATCHPGM ***
ZDSP.1=ZDSP.1

Peter
--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to