Topic moved from assembler to IBM-MAIN

> CMS Pipelines is immensely powerful.  Unix cannot compare. 
> TSO Pipelines was almost infinitely better than not having Pipelines at all 
> on MVS!
> and you can read records efficiently by record number,

Netview is the last user of PIPEs in z/OS. Ask yourself why. Even Netview's 
competition (automation) refuses to implement pipes despite it being simple to 
implement!

Our competitive analysis conclusion: "Are they FREAKIN CRAZY!". PIPEs serve no 
useful purpose in z/OS (except z/OS UNIX). Everything is achievable using 
standard z/OS features.

Pipes 101: The most rudimentary z/OS PIPE is batch (step 1 feeds step2 that 
feeds ... that feeds step #). 

Multi-tasking 101: People are clueless. A performance sysprog will tell you 
that decreasing wall clock time is not a sign of efficiency and they should be 
consulted if that's needed.

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.

Performance 101: CICS and IMS are the bread and butter of z/OS by efficiently 
supporting thousands of users. Running z/OS at 100% capacity is not a problem 
when planned correctly. Ask your performance sysprog if it's acceptable for 30 
TSO users to impact CICS and IMS to reduce their wall clock time?  

Efficient record processing 101: If z/OS can achieve 100,000 transactions per 
second, clearly efficient record processing is built into z/OS. It's time to 
replace the z/OS dasd sysprog if he/she can't help in doing efficient I/O.

Unix pipes 101: The gold standard for PIPEs where every program is compatible 
with PIPEs without thinking. The simple fact is they chose STDIN, STDOUT and 
args which makes PIPEs a no brainer.

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. 

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.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to