Clist has been subject to the same restrictions since long before Rexx came to TSO/E. It's not up to Rexx to fix the problem.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, November 02, 2016 7:33 PM To: [email protected] Subject: (External):Re: TSO Command to issue message to Outtrap On 2016-11-02 13:51, Nims,Alva John (Al) wrote: > From: "z/OS TSO/E REXX Reference" > > OUTTRAP function does not trap command output that is sent to the terminal by: > * TPUT > * WTO macro > And that's the source of recurrent misery reported on these lists. Rexx really ought to fix that or arrange that it be fixed so OUTTRAP captures all (or at least linemode) terminal output. Possibly selected by a keyword option. > * messages issued by TSO/E REXX (that is, messages beginning with IRX) > * messages issued by TRACE outputex > There's a reason that UNIX has separate streams for messages and main output. But those can be merged by redirection. Wjs once reported that he petitioned the powers that be that Rexx messages and TRACE output issued under OMVS go to stderr rather than stdout. The request was denied. > However, OUTTRAP does trap output from the PUTLINE macro with DATA or INFOR > keywords. > I guess that's better than if it trapped nothing at all. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
