CRU203I   SMF UPDATE IS MOST CURRENT BUT NO PRIOR RECORD EXISTS FOR ( t )  catalog entryname /nn NEWER: smftype FROM SYS sysid AT
hh:mm:ss.hh ON mm/dd/yy (yy.ddd)OLDER: NONESMF UPDATE RECORD IS WRITTEN
TO THE NEW EXPORT DATA SET

Explanation

The record is for an entry of type t named catalog entryname, extension number nn. For t, A=nonVSAM, B=GDG, C=cluster, E=VSAM extension, G=AIX, J=GDG extension, R=path, T=truename, U=catalog connector, X=alias. nn=00, except for types E and J.

The only record for this catalog entry is an UPDATE resulting from an smftype (DEFINE, DELETE or ALTER) by the system with identifier sysid at the time and on the date indicated on the NEWER message line.

Another record for this entry should have appeared either in the EXPORTed copy or as an older SMF insert record. However, none was found for one of the following reasons:
  • The EXPORT copy used as input is not the correct one.
  • The EXPORT copy used as input is in error.
  • Some necessary SMF data was not included in the input.
  • Some necessary SMF data was lost.

System action

After taking the action indicated in the last message line, the condition code is set to 8 (if not already higher) and processing continues.

Operator response

Take the following actions:

  1. If the correct EXPORT data set was not supplied as input, correct the data set name on the EXPIN DD statement and rerun the job.
  2. If the EXPORT data set was found to have errors detected by message CRU302I or CRU303I, respond as indicated for that message.
  3. Review the reports and messages from CRURRSV, Record Selection and Validation, for lost or omitted SMF data. If SMF data was omitted, supply the missing data and re-execute this recovery.
  4. If none of the above apply, assume that SMF data has been lost. Further assume that one of the missing records is for this catalog entry and save this log for use with the diagnostic information to be gathered after the output data set is imported. When the output of IDCAMS LISTCAT and IDCAMS DIAGNOSE is later available, proceed as follows:
    1. If the entry appears in the IDCAMS LISTCAT and if IDCAMS DIAGNOSE does not find it to be in error, confirm that the data set or each component of a VSAM sphere is actually on the volumes indicated by LISTCAT. The IDCAMS DIAGNOSE with the COMPARE option will accomplish this for VSAM entries. For nonVSAM entries, check the VTOC for disk data sets. For data sets on tape, check the tape data set inventory, if a tape management system is in use, or actually check the tape volume. You could also run IDCAMS PRINT IDS(entry.name) COUNT(1) to DD DUMMY for all data set types, if you use standard-label tapes and if you don't have so many tape data sets as to make the number of mounts intolerable.
    2. If the data set and each component is present on the volumes, then assume that this entry is the most current one and no further action is required.
    3. If the entry does not diagnose correctly, or if it mismatches the data volumes, then SMF data has been lost and this entry is not the most current one for one of the following reasons:
      • The data set, sphere or component no longer exists and the catalog entry should be deleted.
      • The data set, sphere or component now exists on different volumes and a correct catalog entry for this data set or VSAM sphere must be built.
    4. Make a note of the volumes on which the data set was last known to reside and then delete the existing catalog entry specifying NOSCRATCH.
    5. If the component is not subsequently found on any volume, then we are finished.
    6. If the data set name tells you that this was a data set that can be easily recreated or is otherwise not essential, allow volume cleanup processing to scratch the data set when it is encountered.
    7. If is necessary to locate a disk data set, examine the VTOCs of all volumes that might contain the data set. For VSAM data sets, IDCAMS DIAGNOSE VVDS will do this. For nonVSAM data sets, use IEHLIST LISTVTOC ...,DSNAME=.... You could also use DFSMSdss with the NORUN option to DUMP ...BY(CATLG,EQ,NO)....
    8. If is necessary to locate a tape data set, look for it in the tape management inventory.
    9. When the data set is found, redefine (DEFINE NONVSAM or DEFINE CLUSTER RECATALOG) the entry.
Parent topic: CRU messages