That's what I thought. Thanks.
It's to bad there's no way to re-use a label on different filter stages which only have one input stream, list multiple label references at the start of a pipe, or designate which input/output streams a label connects to. Any of them would get rid of the "pipe clamps". Brian Nielen On Thu, 13 Jul 2006 12:09:39 -0400, Marty Zimelis <[EMAIL PROTECTED]> wrote: >Brian, > To the best of my knowledge, you're "stuck" with the structure you >described in your note. The syntax of label definitions and references >requires it. If you're concerned about the number of lines added to you r >pipeline with each selection stage, note that since the pipeline description >is nothing more than a string in Rexx, the last three lines could easily be >written as > > '? p: | f:', > > Marty > >-----Original Message----- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Brian Nielsen >Sent: Thursday, July 13, 2006 10:57 AM >To: IBMVM@LISTSERV.UARK.EDU >Subject: A PIPE structure question > >Is there a more elegant way to do the following PIPE structure: > >'PIPE (ENDCHAR ?)', > > ... /* some stream of records */ > > '| p: PICK ... > '| t: TAKE ... > > ... /* only the records that pass all the filters come here */ > > '?', > 't:', > '| f: FANINANY', > > ... /* all the records that were filtered out come here */ > > '?', > 'p:', > '| f:' > > >What irks me is needing the last 3 lines. As more filters get added mor e= > >of these trivial connections are required. > >I'd really like to be able to connect the secondary output streams from = > >multiple stages in the same pipe (in this case PICK and TAKE) directly t o= > >the pipe that collects the rejected records (in this case the pipe with = > >FANINANY). If I read the PIPE syntax correctly there's no alternative, = > >but I'm hoping I've overlooked some technique. > >Brian Nielsen >======================== ========================= ========================
