I owe the List an update. Based on earlier advice, I added a PROFILE command to
a skeleton REXX. When testing, to my astonishment, I could not reproduce my
earlier problem. I tested with both PROMPT and NOPROMPT. No difference. Example
below. I would not have waded into the CLIST manual if I had not (seemed to)
hit a wall. I cannot explain it.
BTW What advantage would PUSH have over QUEUE? I thought the only difference
was LIFO vs. FIFO. QUEUE is easier to write and comprehend. This REXX gives the
right result. ? is the help 'command'. vSYSX displays info for all SYSX*
volumes.
/* REXX */
x = OUTTRAP("cmdl.")
PROFILE PROMPT
QUEUE "?"
QUEUE "vSYSX"
QUEUE "END"
SPACE /* TSO SPACE command runs in subcommand mode */
DO i = 1 TO cmdl.0
SAY cmdl.i
END
.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Shmuel Metz (Seymour J.)
Sent: Monday, May 11, 2015 3:15 PM
To: [email protected]
Subject: Re: Did I really need a CLIST???
In
<sn1pr0101mb15201b846e38f6ce22e7b39cce...@sn1pr0101mb1520.prod.exchangelabs.com>,
on 05/06/2015
at 04:48 PM, J O Skip Robinson <[email protected]> said:
>Question: did I really need to do that?
In your particular case, you could have just pushed the required lines onto the
stack, assuming that SPACE is housebroken. If you need to generat subcommands
based on the results of previous subcommands, then there is no way to do it in
REXX.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
