A common approach, which I frequently use.... /* */ Parse source . . . . . . env . ... If env='?' then Parse value 'CallPipe *:' with pcmd pout Else Parse value 'PIPE Cons' with pcmd pout ... pcmd <pipeline spec> '|'pout
[email protected] z/VM systems support for Kyndryl WWVM support [email protected] (925) 672-4403 (o) (925) 672-3922 (h) (925) 323-2070 (m) <R=V/I> ​Vacation Alert: One sorely needed ________________________________ From: CMSTSO Pipelines Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Wednesday, August 10, 2022 15:30 To: [email protected] <[email protected]> Subject: [EXTERNAL] Re: Fwd: CALLPIPE ends (-3) On 8/10/22 15:45:44, Steve Thompson wrote: > > Driver EXEC (REXX) invokes, via a CALL, MISSLFS passing a variable to it > which SAY in MISSLFS shows it got. > > MISSLFS EXEC *was* copied from MISSLFS REXX so I can experiment with it > (yes, in the environment it normally runs in it is a STAGE). > Eek! > CALLPIPE in MISSLFS EXEC terminates with (-3). > > I can't seem to figure out why this is. > > Doesn't -3 mean a problem with the environment? > CALLPIPE is a PIPE command, not a CMS command. > Any suggestions for this? > I once converted a medium-sized Rexx EXEC (I wasn't the author) to a Pipelines stage by renaming it and invoking it wth a PIPE REXX command. At the top I added: STAGE = ADDRESS() /* People have told me this doesn't work. */ ADDRESS CMS All the original author's CMS commands worked as before, but I could then do such as: ADDRESS VALUE STAGE CALLPIPE ... while I progressively converted the script to be more Pipe-like. -- gil
