Joel C. Ewing wrote: >VSAM KSDS data sets are always variable length by definition. Setting >"average record length" = "maximum record length" indicates an intent to write >same length records and that information is used for space calculations, but >each record still has its own length value, is structurally variable length, >and records of any length up to the maximum record length are allowed by VSAM. > So if you just re-defined the file with higher maximum and average record >length and copied the old records to a new file using something like REPRO, or >some other utility with no explicit record size redefinition, the old records >would be exactly preserved including the original record length of 200, just >like you were using the utility to copy from one RECFM=VB file to another VB >file defined with a larger record size. There are utilities that will expand >and pad the records on copy, but you have to use appropriate control cards to >explicitly request that be done.
Thanks for this refreshing overview, much appreciated. Mind you, it was some time ago (I was force-feeded that work when I was a junior!) I wrote programs handling those VSAM KSDS datasets. So my memory is indeed hazy about that. What would you suggest to the OP what should he/she do with the excess 50 characters? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
