Ed, Johnathan; You guys are *so *lucky.
A few quick notes to get you started: - Unlike Unix piping, terminal output from the last stage is not implied. (You'll find this makes sense later.) pipe < some.dsn | count words lines | term - The <, >, and >> are filters on their own, also unlike Unix. (You'll see this makes sense later.) - Pipes I/O is better than execio. You can read and write both datasets and DD names: "pipe < ddname=sysut1 | translate lower | > lower.case" - Pipes is integrated with REXX. You can use variables and stems: "pipe var fred | split | stem fredwords." - - Stay with single stream piping for now. You can do a lot with single streams before you need to go to the next level. - Stages can be aware of their position in the stream. Some stages behave differently depending where they appear, especially in first position. (You'll also see that this makes sense later.) - *pipe help count* and/or *pipe ahelp translate* is a full-screen resource. *pipe help* for a menu. Take a look at the marist.edu pipeline site, especially Melinda Varian's introduction to pipes. Be prepared to blow the minds of your coworkers and your management I'll be happy to help in any way I can. When I first tried Pipes, not giving a pipe specification just gave an obscure syntax error. Good luck. OREXXMan Would you rather pass data in move mode (*nix piping) or locate mode (Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands with more than a dozen filters, while Pipelines specifications are commonly over 100s of stages, and 1000s of stages are not uncommon. REXX is the new C. On Thu, Oct 21, 2021 at 10:59 AM Ed Jaffe <[email protected]> wrote: > On 10/21/2021 8:18 AM, Nash, Jonathan S. wrote: > > ... I just tried TSO PIPE and it worked > > READY > pipe > BPW00256I Enter a pipeline specification > READY > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > -------------------------------------------------------------------------------- > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
