Well, the obvious suggestion is that DSN's can contain IBM's "national characters": @, #, and $ z/VM defaults don't care about the $-sign, but older VM systems and apps may care about the @ (character delete) and # (linend) characters.
If the DSN with those special characters was rear from a file and passed directly to the TSO stage, it would keep the Pipe from attempting to process them (perhaps even as your own STAGESEP or other characters), right? Does the comment " /* avoid RXG abend */" help so shed any light on your mystery? What's an RXG ABEND? Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Glenn Knickerbocker" <[email protected]> Sent by: "CMSTSO Pipelines Discussion List" <[email protected]> 04/16/2010 02:31 PM Please respond to "CMSTSO Pipelines Discussion List" <[email protected]> To [email protected] cc Subject TSO stage abends? I went to share a TSO pipeline with someone and found that I had written myself a TSOEACH REXX stage last year to issue each TSO command in a separate pipeline, with only the cryptic comment: /* avoid RXG abend */ 'addpipe *: | specs "callpipe tso " 1 1-* n "||*:" n | pipcmd | *:' More mysteriously, I apparently already tried rewriting the stage earlier this year to have each TSO stage read a command from the input file instead, to avoid collisions with pipeline characters--and then went back to the original version! Unfortunately, I didn't keep notes of exactly what was abending, and now I can't come up with a case that works one way but not the others. Obviously it wasn't invalid commands--PIPCMD stops on a negative return code just like TSO (and SUBCOM, CMS, COMMAND, CP). All three ways seem to continue fine after a command with invalid parameters. It doesn't seem to matter whether PIPE was called from the command line or a REXX exec, or whether SYSTSPRT is allocated or not. Where I used it was in issuing LISTDS (dsn) MEMBERS commands. Anybody have an idea what problem I might have run into that would actually have been solved by putting the command in the argument to the TSO stage? ¬R The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
