I think Ed might be right here on the SYSGEN option history, however TSO EDIT doesn't seem to support it fully these days. I have access to 5 very different systems each with different heritage. Two of them are >30 years old and will date back to the SYSGEN days, one of them I'm not sure of it's age, but the other two are much younger. All of them use an FB 80 SYSPROC concatenation except for one of the older systems which uses a VB 255 SYSPROC concatenation. TSO EDIT creates a VB,255,3120 data set for type CLIST on all the systems except for the older FB 80 system, which creates a corrupt FB,80,3120 data set. I'm guessing that the original SYSGEN option of FB was copied across for this system, but it doesn't look like TSO EDIT fully supports it as it's obviously still using variable length edit buffers, but writing full FB 80 byte records to the new PDS with the line numbers at the beginning of the record rather than in columns 72-80. Here is a transcript of a TSO session on the older FB system to demonstrate this:
READY listds temp.clist IKJ58503I DATA SET xxxxxx.TEMP.CLIST NOT IN CATALOG READY e temp(hello) cl IKJ52320I DATA SET OR MEMBER NOT FOUND, ASSUMED TO BE NEW INPUT 00010 proc 0 00020 write hello mick 00030 end 00040 E l 00010 PROC 0 00020 WRITE HELLO MICK 00030 END IKJ52500I END OF DATA end save READY listds temp.clist xxxxxx.TEMP.CLIST --RECFM-LRECL-BLKSIZE-DSORG FB 80 3120 PO --VOLUMES-- vvvvvv READY print inda(temp.clist(hello)) char RECORD SEQUENCE NUMBER - 1 00000010PROC 05...........IBMOSVS2 ..............&....&......QS............ . RECORD SEQUENCE NUMBER - 2 00000020WRITE HELLO MICK..IBMOSVS2 ..............&....&......QS............ . RECORD SEQUENCE NUMBER - 3 00000030ENDTE HELLO MICK..IBMOSVS2 ..............&....&......QS............ . IDC0005I NUMBER OF RECORDS PROCESSED WAS 3 READY exec temp.clist(hello) 00000010PROC 05 -È- - IBMOSVS2 ØØ -- ° - & Ø& - -QS - IKJ56545I THIS STATEMENT HAS AN INVALID SYMBOLIC VARIABLE READY Same member shown in ISPF/PDF browse: 00000010PROC 05..È. ......IBMOSVS2 ...ØØ....°....&...Ø&......QS............. 00000020WRITE HELLO MICK..IBMOSVS2 ...ØØ....°....&...Ø&......QS............. 00000030ENDTE HELLO MICK..IBMOSVS2 ...ØØ....°....&...Ø&......QS............. As you would expect, editing a new member in an existing FB 80 CLIST data set works fine and puts the line numbers in the right place. Interesting stuff! Cheers, Mick. On 16 November 2016 at 04:38, Edward Gould <edgould1...@comcast.net> wrote: > > On Nov 15, 2016, at 1:16 PM, Dyck, Lionel B. (TRA) <lionel.d...@va.gov> > wrote: > > > > I'm in the 255 camp and just tried a simple experiment. > > > > From TSO issue the Edit command: E T(ABC) CL > > > > This opens the old editor on dataset t.clist member abc and after adding > a few records and saving I checked the dcb which was VB,255,3120 > > > > Not the ideal blksize but the lrecl is what I expected. > > > > hth > > > > Lionel: > > At least in mvs 3.8 there was a sysgen macro you could specify FB VB and > lrecl blksize etc. > Since system dissapeared I am not sure what the defaults are now days. > > Ed > > ---------------------------------------------------------------------- > 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
