Lizette's point that IBM can change the information in a PDS directory without notice is of course generically correct
That conceded, such changes have been infrequent for many years; and the functional stabilization of PDS support that came about with the introduction of PDSEs makes further such changes unlikely. Brutally put, PDSEs are changing, PDSs are not. Have you succeeded in opening your PDS as a sequential file? --jg On 9/6/12, Lizette Koehler <stars...@mindspring.com> wrote: > Charles, > > If I recall when writing an Assembler Program for a STOW macro there were > some pointers on how to dump a PDS Directory. And I think there may be > information in the ISPF Manuals as well. > > Though I think you are better served by doing this with an assembler > program. Also, remember IBM can change the info in the directory without > explanation. > > Lizette > > >> >> I want to make a PS (flat file) copy of the series of 256-byte blocks of >> a > PDS >> directory. (I want to copy the data to another platform so I can test >> some > code with it >> more readily.) >> >> I tried >> >> //GENER EXEC PGM=IEBGENER >> //SYSUT1 DD DSN=MY.PDS,DISP=SHR,RECFM=F,DSORG=PS >> //SYSUT2 DD DSN=THE.SAMPLE.PDSDIR,DISP=(NEW,CATLG), >> // SPACE=(TRK,(1,1)) >> >> but IEBGENER is too smart for that: >> >> IEB311I CONFLICTING DCB PARAMETERS >> IEB311I CONFLICTING DCB PARAMETERS >> >> (and copied nothing). >> >> Anyone know how to accomplish this, short of writing an assembler program > to >> do it? >> >> Charles >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
