I'm not sure why you'd think it may have problems punching/printing PDS members that happen to contain JCL which happens to contain IEBPTPCH commands. It's all just data to IEBPTPCH.
One of the examples in the documentation is to "copy a card deck". Yes, there are limitations. 80 bytes of data for punching (what is wanted here), and 96 bytes for printing, apparently. Strong implication at least that it is fixed-length only for input. It is documented, you could consider giving it a whirl with something else and lettings us know. I did assume since the question was about looking through programs that it would be fixed-length 80-byte records, which I know for sure works. On Tuesday, 14 June 2016 23:55:15 UTC+2, Paul Gilmartin wrote: > On Tue, 14 Jun 2016 12:47:24 -0500, Bill Woodger wrote: > > >IEBPTPCH. Flattens a PDS to a sequential dataset and handily indicates where > >members start/end with name. Can even update/create new output and get it > >back into a PDS. > > > Does it deal nicely with a PDS that may contain members which > are themselves IEBPTPCH JCL with instream data by somehow > protecting images of IEBPTPCH comands? > > Has it any restrictions on RECFM/LRECL? > > -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
