Wow. Thanks again. I was obviously doing something wrong earlier, because it (the SELECT to BLSGSCMD) is working now when I pass the LIST command as a parm.
I did a little experimenting, and it seems the "Address IPCS" in front the "ISPEXEC SELECT PGM(..." is apparently redundant, as it seems to work the same and just as well as: Address ISPEXEC "SELECT PGM(BLSGSCMD) PARM(LIST" modaddr". LENGTH(256))..." So, what BLSGSCMD is doing for me is capturing the END when the user presses PF3 when viewing the output of LIST. When issuing LIST without the SELECT to BLSGSCMD, the user entering END on the LIST output report causes my REXX exec to terminate. With BLSGSCMD, control is returned to the instruction following the SELECT PGM... Thanks Bob. Todd > > > I don't see your rationale for getting a data set into the picture. > Instead of passing a LIST subcommand to IPCS, you should be able to pass > an ISPEXEC request as though it were the original subcommand that you > had in mind. Skipping the quotation marks and substitution concerns: > > Address IPCS ispexec PGM(BLSGSCMD) PARM(list modaddr length(256)) > PASSLIB > > BLSGSCMD takes care of breaking out the subcommand/command-procedure > invocation using what TSO I/O service routines call an instorage list. > IPCS/TSO code lets your pass command names and operands in mixed case, > folding those operands that need it to upper case during parsing. I'd > have to double-check whether the text interpreted by ISPEXEC needs to be > in upper case as I've shown. > > -- > Bob Wright No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.6.7/1628 - Release Date: 8/22/2008 6:32 PM ---------------------------------------------------------------------- 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
