On 2020-04-23, at 06:22:52, Jonathan Scott wrote: > >> Can CMS/TSO Pipelines be run under z/OS batch, such as IRXJCL, or is >> it inextricably bound to TSO? > > I've been using the IBM internal version of TSO Pipelines in > Ah! Akin to PL/X it's Internal Use Only. A pity; I've heard no reports of a customer's success in ordering it.
> z/OS batch for many years. Here's a typical trivial use in one > of my batch jobs: > > //* > //* Store the listing. > //* > //LISTING EXEC PGM=PIPE,PARM='< dd=pipe|strip|join *|runpipe|cons' > //CPPLIST DD DSN=&&CPPLIST,DISP=(OLD,PASS) > //LISTING DD DSN=&RELHLQ..&LEVEL..&OLIST,DISP=SHR > //PIPE DD * > < dd=CPPLIST > |strip trailing > |pad 2 > |> dd=LISTING(&OREF) ispfstat > /* > > The PARM field in this case is used to run a general pipe supplied > in the PIPE DD statement. For a simple case, you can just specify > everything in the PARM field: > > //WAIT1MIN EXEC PGM=PIPE,PARM='literal +1:00|delay' > Recently, PIPE DD is superfluous. The same could be achieved with PARMDD SYMBOLS=JCLONLY. Either allows portrat representation of the Pipeline. Or with Rexx ADDRESS LINKMVS 'PIPE PARM', where PARM can be up to 32767 characters. Thanks, gil
