You use SYSOUTTRAP in Rexx thought it's a clist command unless you are calling clist from Rexx
> On Jul 3, 2016, at 12:48 PM, Jesse 1 Robinson <jesse1.robin...@sce.com> wrote: > > I use SYSOUTTRAP in Rexx all the time for ordinary commands. There is indeed > a huge difference between Rexx and Clist vis a vis 'subcommand mode'. An > example of subcommand mode is the SEND command under OPER. Another is LIST > under ACCOUNT. TEST runs in practice almost entirely in subcommand mode. > > In a Clist, the exec retains control when running in subcommand mode. In > Rexx, the exec loses control in subcommand mode, so successive commands must > be 'stacked' ahead of time via QUEUE. Trouble is that in TEST, subsequent > command operands usually depend on the result of previous commands, which > makes QUEUEing commands ahead of time nearly impossible. > > I don't recall ever trying SYSOUTTRAP in TEST. > > . > . > . > 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 > robin...@sce.com > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joseph Reichman > Sent: Sunday, July 03, 2016 9:18 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE > > I don't think the clist SYSOUTTRAP/SYSOUTTRAP Work to trap TEST output maybe > Rexx OUTTRAP does didn't try that > > > >> On Jul 3, 2016, at 9:16 AM, Rupert Reynolds <rreyno...@cix.co.uk> wrote: >> >> TEST behaves differently (or did, when I used it in the 90s) in CLIST. >> As I remember it, the CLIST that starts TEST keeps running for the >> TEST session, so the next line of a CLIST after the TEST command >> itself can be subcommands such as AT and GO. >> >> As I remember it, there were important differences in SYSOUTTRAP as >> well. I had a small collection of REXX and CLIST that could be run in >> TEST to do things such as single step and redisplay registers, >> storage, code, PSW and so on, almost half way to a full screen debugger. >> >> I found the differences meant I had to mix REXX and CLIST to get the >> job done. >> >> Roops >>> On 3 Jul 2016 12:53, "Joseph Reichman" <reichman...@gmail.com> wrote: >>> >>> Thanks so much 🤗 >>> >>> Joe Reichman >>> 8045 Newell St Apt 403 >>> Silver Spring MD 20910 >>> Home (240) 863-3965 >>> Cell (917) 748 -9693 >>> >>>>> On Jul 3, 2016, at 7:38 AM, Mike Shorkend <mike.shork...@gmail.com> >>>> wrote: >>>> >>>> I am not sure about CLIST but for REXX, the following will place >>>> each output line into a the stem variable 'test'. >>>> >>>> /* REXX */ >>>> x=outtrap('test.') >>>> push "end" >>>> PUSH "go" >>>> PUSH "at +0" >>>> "test 'sys1.linklib(iefbr14)'" >>>> say "number of trapped lines is" test.0 do i = 1 to test.0 say >>>> test.i end >>>> >>>> HTH >>>> >>>> Mike >>>> >>>> >>>>> On 29 June 2016 at 15:21, Joseph Reichman <reichman...@gmail.com> >>> wrote: >>>>> >>>>> Hi >>>>> >>>>> Does any one know if capturing TEST output Into CLIST variables is >>>>> possible >>>>> >>>>> >>>>> Thanks > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
