Yes.
Many years ago when it we called what we do DP, I was in a DP
shop, where we effectively created batch pipes and passed
buffers. The only I/O that was done was for open and read by the
initial program, the rest read the output buffer of the "stage"
ahead of it and wrote what ever report it was to do, unless the
output was to be a buffer passed to another program. And then we
had a program that was the termination but I can no longer
remember the names of these special programs we had written for
doing all of this.
We basically had a S/370-158 glowing red because of keeping stuff
in memory within a JOB step. Note, that 90-ish percent of our
programs were ALC and we had a very large macro library built for
doing things like this.
When they got talked into going to an AS400... 4 AS400's later,
they were still trying to get migrated (read that converted).
--
Regards,
Steve Thompson
MAGA: Make Assembly language Great Again
On 9/7/2025 4:58 PM, Paul Gilmartin wrote:
On Sun, 7 Sep 2025 13:36:25 -0500, Jon Perryman wrote:
Pipes 101: The most rudimentary z/OS PIPE is batch (step 1 feeds step2 that
feeds ... that feeds step #).
Can batch do this without using a temporary data set?
can a downstream step take timely action on output
from an upstream step? This is routine design in
CMS Pipelines.
Multi-tasking 102: TSO and ISPF do not multi-task because people do not
understand multi-tasking and would abuse it. TSO PIPEs are not acceptable
because it encourages mult-tasking.
I hear the arrogance alarm. Don't thus demean your colleagues.
CMS pipes 101: CMS PIPE's power is in the CMS pipe subcommands built
specifically for PIPE because CMS has very few commands and they were not
designed with PIPEs in mind.
Agreed. CMS facilities are meager. I/O abstraction is sorely lacking.
Pipelines fills the gap.
But Pipelines can not run two CMS stages concurrently. MVS ATTACH does
that well, with some restrictions due to the kludge of the alternate DDNAME
list. It should have been possible to make DDNAMEs have task scope
optionally, instead of job scope.
TSO pipes 101: Those CMS PIPE subcommands could be implemented as TSO commands.
They could even be implemented as programs called using ADDRESS LINK. If you
can't easily solve the same problems as CMS, then you're asking the wrong
person for help.
ADDRESS ATTCHMVS for compatibility. But, ironically, that
does not support multitasking, at which some people, contrary
to your prejudice, are competent.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
