A fix is available
APAR status
Closed as program error.
Error description
Customer having run a DUMP, and a subsequent restore of KSDS dataset, with REPLACE option. The creation date for the restored dataset, which should show the original create date of the dataset is corrupted, and shows in LISTCAT and IEHLIST a date such as 1901.921, or some similarly invalid date. This apar ONLY affects releases 1.8 and 1.9. Release 1.10 is not affected by the symptoms described in this apar. ADDITIONAL SYMPTOM: A HSM HRECOVER OR HRECALL will also cause the corruption of the creation date. VSAM datasets that have been recovered, restored, or migrated and recalled can expire and be deleted based on the incorrect creation date. This can occur during HSM PSM and SSM auto-processing FIXCAT: ZOS0204C/K
Local fix
If you have been exposed to this problem, there are several steps that must be taken to determine the extent of the problem, to repair records that contain corrupted CREATE DATEs, and to recover datasets that have been prematurely expired/deleted. 1) Maximize your ability to recover data if needed - Do not run HSM RECYCLE or EXPIREBV until all recovery actions are complete. 2) Prevent further premature dataset deletions - Do not run PSM or SSM autofunctions until the CREATION DATE has been corrected in all MCDS records and all affected datsets on primary volumes have been fixed. Alternatively, you can adjust the SMS expiration attributes in all management classes to prevent datasets from expiring by setting the "DELETE BY DATE/DAYS" to NOLIMIT. NOTE: Customers who specify DELETE BY DATE/DAYS NOLIMIT are not affected by this problem. 3) Repair MCDS records of all datasets that are currently migrated with corrupted CREATION DATEs. First, run the following job. This will produce a dataset containing commands that will repair the affected MCD records. //SMCDS JOB ,CLASS=A,USER=&userid,PASSWORD=&pword, // MSGCLASS=H,MSGLEVEL=(1,1) //STEP1 EXEC PGM=ICEMAN //SYSOUT DD SYSOUT=* //SORTIN DD DSN=&mcds.dataset.name,DISP=SHR //FIXCMD DD DSN=&userid.FIXCDS.DATA, // DISP=(NEW,CATLG),UNIT=SYSDA, // DCB=(RECFM=FB,DSORG=PS), // SPACE=(TRK,(5,1),RLSE) //SYSIN DD * OPTION VLSHRT SORT FIELDS=COPY RECORD TYPE=V OUTFIL FNAMES=FIXCMD, INCLUDE=((51,1,BI,EQ,X'00'),AND, (81,4,BI,LT,X'0050001F'),AND, (110,1,BI,EQ,B'....1...')), CONVERT,OUTREC=(C' HSEND FI D ',5,44, C' P(12 X''0109180F'')') /* Next, run the following job to execute the HSM FIXCDS commands generated by the previous job. //FIXMCDS JOB ,CLASS=A,USER=&userid,PASSWORD=&pword, // MSGCLASS=A,MSGLEVEL=(1,1) //STEP001 EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=A //SYSTSIN DD DSN=&userid.FIXCDS.DATA,DISP=SHR /* Completing this step will prevent HSM from prematurely expiring VSAM datasets that are migrated with corrupt CREATE DATEs. 4) Recover datasets that were prematurely deleted. To determine if any VSAM datasets were deleted, first determine the window that VSAM datasets were susceptible to the problem. Determine the time frame between when PTFs UA46732/UA47067 R180 or UA46733/UA47068 R190 were applied and when the fixing ++APAR or PTF was applied. For this time frame, collect all SMF records type 60 to 65 and HSM FSR records (SMF 241 if using the default value for SETSYS SMF(type)+1). The SMF data along with the date of when the ptfs were applied will be needed by IBM support to determine what datasets may have been prematurely deleted. Contact IBM support once you have the all of the above information. * * * Do not run HSM RECYCLE or EXPIREBV until all recovery actions are complete. * * *
Problem summary
**************************************************************** * USERS AFFECTED: All HDZ1180 and HDZ1190 DFSMSdss RESTORE * * users including HSM RECALL and RECOVER * * Processing for a VSAM * * data set. * **************************************************************** * PROBLEM DESCRIPTION: During a RESTORE of a KSDS, * * with the REPLACE keyword specified, * * the creation date is corrupted. * * The LISTCAT shows an invalid creation * * date of 1901.921. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
DFSMSdss has been modified to correct the problem. KEYWORDS: R11COEXS/K ZOS0201C/K ZOS0202C/K ZOS0203C/K
Temporary fix
Comments
APAR Information
APAR number
OA29102
Reported component name
DFSMSDSS, ISMF
Reported component ID
5695DF175
Reported release
190
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-05-19
Closed date
2009-06-22
Last modified date
2019-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA48232 UA48233
Modules/Macros
ADRCATLG
Fix information
Fixed component name
DFSMSDSS, ISMF
Fixed component ID
5695DF175
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"190","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 April 2019