Poked around my own code and found one subcommand example, which works. SPACE
is a TSO command that allows a number of subcommands. SPACE stays in control
until END. One subcommand is Vxxxxxx, which display info for all volumes
beginning with xxxxxx. This Rexx captures all output and displays at the end.
Notice that subcommands must be QUEUEd in advance of the SPACE command itself.
x = OUTTRAP("cmdl.")
PROFILE PROMPT
QUEUE "?" /* help */
QUEUE "vSYSX"
QUEUE "END"
"SPACE"
DO i = 1 TO cmdl.0
SAY cmdl.i
END
Output:
Enter Command (? for help)
All List data on all online disks
Devices List data on all devices
End End program
Fxxxxxx List data on device with volser 'XXXXXX'
Gname List data on generic unit 'name'
TEDSKIP generic unit 'name' is SYSDX
List List the generic unit names
Offline List data on both online and offline disks
Uxxx List data on device with unit ADDR 'xxx'
Uxxx,nn List nn devices starting from ADDR 'xxx'
Uxxx-yyy List devices from ADDR 'xxx' to 'yyy'
S OFF/ON Print sum of free cylinders and tracks
$ Toggle LSPACE option on or off
? Print this list
Help Show the meaning of the fields
Enter Command (? for help)
----Cylinders----- ---Tracks---
Addr Volume Device Atr Mnt Total Free Contig Free Contig Ext. Usect Vtoc
6500 SYSXL1 3390-3 SHR PVT 03338 02359 02147 00018 00000 00004 0007 IX
6508 SYSXL2 3390-3 SHR PVT 03338 02441 02218 00000 00000 00002 0001 IX
6700 SYSXL3 3390-3 SHR PVT 03338 01001 01001 00000 00000 00001 0001 IX
6708 SYSXL4 3390-3 SHR PVT 03338 02216 02204 00000 00000 00002 0002 IX
7309 SYSX04 3390-3 SHR PVT 03338 00199 00135 00029 00000 00010 0217 IX
7801 SYSX01 3390-3 SHR PVT 03338 00385 00041 00443 00000 00095 0103 IX
7A0A SYSX06 3390-3 SHR PVT 03338 02999 02999 00005 00000 00002 0006 IX
7B02 SYSX02 3390-3 SHR PVT 03338 00006 00003 00054 00000 00010 0005 IX
7C12 SYSX03 3390-3 SHR PVT 03338 00026 00002 00464 00013 00099 0260 IX
7E02 SYSX05 3390-3 SHR PVT 03338 01149 00176 00276 00000 00076 0015 IX
Enter Command (? for help)
.
.
.
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 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
I have tried to capture test subcommand output I.E list under clist with no
success Dont know about Rexx I am now thinking the AT subcommsnd in TEST
leaves you the ability to to exec a CLIST as part of the parameters maybe I'll
try the SYSOUTTRAP/SYSOUTLINE in that instance
> On Jul 3, 2016, at 1:51 PM, Jesse 1 Robinson <jesse1.robin...@sce.com> wrote:
>
> I was sloppy. AFAIK the functions are equivalent. In Rexx, you use this
> syntax:
>
> x = OUTTRAP("cmdl.")
> "LISTALC STATUS"
> line_count = cmdl.0
> dsn = cmdl.i
> ...
>
> Output goes into the named array. Lines are identified by the value of i.
>
> Equivalent in Clist:
>
> SET SYSOUTTRAP = 600
> LISTALC STATUS
> SET SYSOUTTRAP = 0
> SET &LINE_COUNT = &SYSOUTLINE
> SET DSN = &STR(&&SYSOUTLINE&I)
> ...
>
> Output always goes into complex variable &SYSOUTLINE. Lines are identified by
> the value of &I.
>
> The real difference for OP is the scope of output capture in Rexx vs. Clist.
> When Rexx switches into subcommand mode, I don't think output is captured
> from the original OUTTRAP.
>
> .
> .
> .
> 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:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TSO TEST and SYSOUTTRAP/SYSOUTLINE
>
> 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
