Restoring VSAM data sets with expiration dates beyond 2000 (OW00780)

Prior to the fix of APAR OW00780, DFSMSdss sometimes mishandled VSAM expiration dates during logical data set DUMP and RESTORE operations. Data sets that had expiration dates in the year 2000 or beyond were dumped and restored as though they had expired in the 1900s.

The byte of offset X'1C' of module ADRPATCH has been defined to allow special processing for VSAM data sets with expiration dates in the year 2000 or beyond that were dumped without the fix of OW00780. The possible settings for the flag byte are listed below:

X'00': Any VSAM data sets that expired in the years 20nn or 21nn and that were dumped without the fix for OW00780 are restored with an expiration date of 19nn.
X'FF': Any VSAM data set that was dumped with an expiration date less than 1980 will have 100 years added to the expiration date. This includes not only data sets that were dumped without the fix for OW00780 that had expiration dates for 2000 to 2080 or from 2100 to 2180, but also any VSAM data set that actually had an expiration date less than 1980.

Note: This patch does not yield the correct expiration dates for data sets that expire beyond the year 2100. However, it at least causes the data sets to be restored with an expiration date that has not already passed. Users then have several years to correct the date.

To set the flag to on dynamically, use the SET PATCH command. To set the flag to on permanently, modify the sample JCL (see Sample JCL) as follows:

//SYSIN DD *
   NAME ADRDSSU ADRPATCH
   VER   1C        00
   REP   1C        FF