Steve Comstock wrote on 10/18/2005 02:10:12 PM: > In our TSO CLIST course, we include a brief discussion > of the [rather arcane] TSO EDIT command; it is clear > I can include an edit command followed by various > edit subcommands in a CLIST. > > But I have trouble accomplishing the same work in > a REXX exec. I've tried emulating the CLIST approach > (edit command followed by lines with edit subcommands) > and PUSHing the edit subcommands on the stack before > issuing the edit command. To no avail. > > Looks like I'll have to call a CLIST to get that > work done. Anyone able to shed any light on this one?
EDIT is an example of what the original TSO design called a modal command, one that chats with you repeatedly until you say END. (IPCS is another.) CLIST caters to such commands by yielding control each time that a GETLINE, PUTLINE, PUTGET, or STACK operation completes, allowing the TMP to pass control to a program and the program, in turn, to solicit input from the same CLIST. REXX assumes a different control flow model. It sets up shop and passes what are generally-expected to be requests for complete transactions to commands. REXX can pass control to a modal command, but it just waits for the command to complete before progressing past invoking the modal command. Bob Wright - z/OS MVS Service Aids ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
