On 1/11/2019 12:35 PM, David Spiegel wrote:
R'Shmuel, Can you please explain what you mean by "... TSO stack mechanism ..." and where the documentation is? (I've never encountered a TSO stack (outside of Rexx) in my 43 years of using TSO.)
I suspect this is a reference to REXX's total lack of interactive command processor support like you get with CLIST.
A CLIST can invoke a command processor, issue a subcommand to it, and -- based on the results of that subcommand or others that follow -- issue additional subcommands. The entire command processor session is programmatically controlled by the CLIST.
In REXX, you must place all subcommands ahead of time on the stack and then invoke the command processor. You cannot interrogate intermediate results and modify/change the remaining subcommands as might be needed. Your REXX does not get control back until the stack is exhausted and the command processor ends.
If you have 43 years of experience, I'm sure you know exactly what I'm trying to describe here...
-- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ -------------------------------------------------------------------------------- This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
