I think that BatchPipeWorks was similar to the IBM internal TSO Pipelines, but I don't know whether it was higher, lower or parallel. I think that one of the reasons IBM didn't want to release TSO Pipelines is that it had sold the rights to the vendor as part of BatchPipes.
BatchPipes itself is a separate function from BatchPipeWorks and involves the use of subsystem sequential file DDnames to allow data to flow in and out of jobs. I don't know the details, but I just looked up the books: >pubslist batchpipes os/390 https://publibfp.dhe.ibm.com/epubs/book/asf1a110.boo GA22-7459-00 BatchPipes OS/390 V2R1 Introduction https://publibfp.dhe.ibm.com/epubs/bkshelf/asf1bs11.bks GA22-7473-01 BatchPipes OS/390 V2R1 Bookshelf https://publibfp.dhe.ibm.com/epubs/book/asf1bs11.bki GA22-7474-01 BatchPipes OS/390 V2R1 Bookindex https://publibfp.dhe.ibm.com/epubs/pdf/i1006610.pdf GI10-0661-00 BatchPipes OS/390 V2R1 Program Directorya https://publibfp.dhe.ibm.com/epubs/book/asf1a411.boo SA22-7456-01 BatchPipes OS/390 V2R1 BatchPipeWorks Reference https://publibfp.dhe.ibm.com/epubs/book/asf1a310.boo SA22-7457-00 BatchPipes OS/390 V2R1 BatchPipeWorks User Guide https://publibfp.dhe.ibm.com/epubs/book/asf1a210.boo SA22-7458-00 BatchPipes OS/390 V2R1 Users Guide and Reference You'll need to download the IBM Softcopy Reader to be able to read those books, and probably download each one using "Save As" after the browser shows the book as rubbish text. (If I still had access to my old tools I could have converted those books to HTML). Jonathan Scott -----Original Message----- From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf Of Paul Gilmartin Sent: 06 September 2025 18:27 To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: TSO Pipelines (was: HLASM and VM ...) On 9/5/25 03:54, Jonathan Scott wrote: > ... > CMS Pipelines is immensely powerful. Unix cannot compare. You can write a > basic Pipelines HTTPS web server in about 30 lines. I helped to develop the > VM Charlotte web browser, for which I rewrote the HTML formatting in systems > programming C, which all runs as a CMS Pipeline. Within IBM, we also had TSO > Pipelines, based on an earlier internal level of the same code, and I made > heavy use of it in our MVS jobs, as it greatly simplified many tasks. IBM > included a variant of that as BatchPipeWorks in BatchPipes but then sold that > off to a vendor. If z/OS had TSO Pipelines at the same level as current CMS > Pipelines, it would be a far more programmer-friendly environment. > ... Is (current?) TSO Pipelines included as a component of BatchPipes? If so, I can understand IBM's reluctance to compete against an ISV/partner by making TSO Pipelines a base component of z/OS. A question I have asked before, but never been able to phrase clearly: is it possible for a pipeline to connect to the "other side" of a ddname? Not a driver which can read from or write to a ddname allocated otherwise, such as by BPXWDYN, but so that a Classic utility, such as ISPF SRCHFOR or IEBGENER might read/write a pipeline? BatchPipes must have this. What is the syntax? Example? -- gil
