It's between steps in different jobs. A pipeline in the context of CMS Pipelines consistent of stages that use built-in programs or user-written programs that fit in and typically transfer data through the pipeline. Stages that are less well-behaved (like both writing to the same file) would get in trouble.
Rob Op za 6 sep 2025, 22:17 schreef Paul Gilmartin < [email protected]>: > On 9/6/25 12:07, Rob van der Heij wrote: > > Yes, better than nothing. But by little. > > I don't know whether John distributed the TSO Pipelines on 2010 level. I > do > > know IBM Denmark did it as PO until John retired. It contained several > > things not in the batchpipes edition (which landed at IBM again later) > > I think the concept with pipes between job steps was pretty cool, > > ... > Between job steps? Or between jobs? > o Has the Initiator the ability to run multiple steps concurrently? > o Or is this a *major* Type 1 enhancement added by Pipes? > o Or must the concurrent steps be in separate jobs? > > What would the (pointless) illustration look like? > IEBGENER | IEBGENER > > How are DDNAME conflicts handled? (two SYSUT1 and two SYSUT2?) > Possibly alternate DDNAME lists? > > > especially with CMS Pipelines in between. Those involved didn't > understand > > the potential of the solution. > > Regular expressions? > > -- > gil >
