Tried this: 'pipe listpds test.pdse | substr 1:8 | members test.pdse | count lines | cons'
And got this: BPW00027E Entry point SUBSTR not found BPW00003I ... Issued from stage 2 of pipeline 1 BPW00001I ... Running "substr 1:8" Probably an anomaly in z/OS not found in CMS. So tried this: 'pipe listpds test.pdse | chop 8 | members test.pdse | count lines | cons' And it worked - Thank You Lionel B. Dyck <sdg>< Website: https://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -----Original Message----- From: CMSTSO Pipelines Discussion List <[email protected]> On Behalf Of Rob van der Heij Sent: Wednesday, September 9, 2020 3:27 AM To: [email protected] Subject: Re: [CMS-PIPELINES] PIPE MEMBERS Anomaly ??? On Wed, 9 Sep 2020 at 10:08, Lionel Dyck <[email protected]> wrote: > Is there a way with PIPE MEMBERS to have it process all members? > Sure, you're right about the LISTPDS (or LISTISPF) to produce the member names like that. You need to specify the dataset again with the MEMBERS stage (the MEMBERS stage has no idea that you got that list from the LISTPDS). Like this: listpds fplom maclib s | substr 1.8 | members fplom maclib s | count lines | cons But normally you want to do something to identify the member that produced the content, something like this maybe: PIPE (END \) listpds fplom maclib s | substr 1.8 | o: fanout | pad 9 | j: juxtapose | cons \ o: | members fplom maclib s | locate ,ISPF, | j: This selects the records that contain the specified string, and JUXTAPOSE prefixes them with the name of the member that contains the data. There's no fancy wildcard selection in MEMBERS. If you'd want to select a subset of the members, that's something you do with separate stages on the output of LISTPDS before you feed the records to MEMBERS. On z/OS you could even use the extra information that ISPF keeps in the PDS directory. Sir Rob the Plumber
