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
