CRU204I   SMF DELETE 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 DELETE CAUSES THE RECORD
TO BE OMITTED FROM THE NEW
EXPORT

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 a DELETE resulting from an smftype (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.
  • The time of the SMF record precedes the time of the EXPORT.
  • 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. Determine whether the date and time of the SMF record is within plus or minus the specified clock-difference value of the specified start date and time. If it is, assume that this SMF record duplicates activity already reflected in the EXPORT copy and disregard this message.
  4. 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.
  5. 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 available, proceed as follows:
    1. The entry will not appear in the IDCAMS LISTCAT output. Use the volume information from the dumped record. Look for recognizable volume serials information in the interpreted portion of the dump.
    2. For nonVSAM entries, check the VTOC for disk data sets. For VSAM data sets, IDCAMS DIAGNOSE VVDS will do this. 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 for all data set types using PRINT INFILE(ddname) COUNT(1) to DD DUMMY with a DD statement for the volumes in question 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.
    3. If the data set or a component of a VSAM sphere is not subsequently found on any volume, then we are finished.
    4. If the data set or any component is present on the volumes, then SMF data has been lost and this entry (for delete) cannot be the most current one. A correct catalog entry for this data set or VSAM sphere must be built.
    5. Using the volume serials and device types on which the components or data sets were found above, redefine (DEFINE NONVSAM or DEFINE CLUSTER RECATALOG) the entry.
Parent topic: CRU messages