Steve Comstock wrote on 10/27/2005 08:55:31 AM: > > Read up on the EXEC subcommand of EDIT. > > OK, done. Interesting, but less than enlightening. It > looks like when I am in TSO EDIT I can issue the > EXEC subcommand and invoke a CLIST or a REXX exec. > > But, the doc goes on to say: > > "Specify only REXX instructions in the REXX exec. > Specify only EDIT subcommands and CLIST statements > in the CLIST." [interesting restrictions; not > useful for my needs; also interesting that this > is one of those areas where a CLIST can be more > powerful than a REXX exec] > > But, the short write up ends with this mysterious > assertion: > > "You cannot specify TSO/E commands in the CLIST or > REXX exec until you specify END to terminate EDIT." > > I consider it mysterious because it seems to imply > you can be in TSO EDIT, invoke a CLIST or exec which > can terminate TSO EDIT and then continue to run, > issuing TSO commands. This seems really unlikely. > > Anyway, thanks for pointing this feature out to me.
CLISTs do have the property that you doubt - as long as the commands of interest use the TSO I/O service routines to get line mode input. You can use a CLIST to start EDIT, change whatever you want, exit from EDIT, .... Unfortunately, EDIT was designed before the CLIST facility was added to TSO, so subcommands don't supply return codes to do things like let your CLIST know whether FIND found the thing of interest, but it is quite useful for a class of editng tasks where you have a well-defined group of things to alter before saving or submitting the data. Bob Wright ---------------------------------------------------------------------- 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
