CRU106I   SMF UPDATE WAS SUPERSEDED BUT NO PRIOR RECORD EXISTED FOR ( t )  catalog entryname /nn NEWER: smftype FROM SYS sysid AT
hh:mm:ss.hh ON mm/dd/yy (yy.ddd)OLDER: NONE
RECORD IS
BYPASSED, ACTION WAS TAKEN
FOR A MORE CURRENT RECORDRECORD IS BYPASSED, ACTION
WAS TAKEN FOR A MORE
CURRENT RECORD

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.

This SMF record (not the most current one) 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 in error.
  • The EXPORT copy used as input is not the correct one.
  • Some necessary SMF data was lost.
  • Some necessary SMF data was not included in the input.
  • In a multi-system environment, the clock on this system, sysid, was behind the clock on the system actually inserting the entry by more than the interval between the insert and this update.

System action

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

Operator response

The content of the new, output EXPORT data set is not affected by this entry and no action is normally required.

If message CRU113I, CRU205I, CRU206I, CRU207I or CRU208I for this catalog entry has appeared previously, respond to that message using this additional information.

If there was no previous error message for this entry but your setting of the clock-difference value might have precluded effective multi-system synchronization checking, it is possible that this entry should be the most current one. If you suspect that this might be your situation, save this log data set and do the following analysis after the catalog is recovered:

  1. Check that this entry appears in the listing of the recovered catalog.
  2. If it does appear, then check that the entry is correct and current; that is, IDCAMS DIAGNOSE does not find it in error and the data set is actually on the volumes indicated. If the entry is current and correct, disregard this error message.
  3. If this entry does not appear in the recovered catalog, or if its entry is not correct and current, then check for the presence of this component on the volumes found in the record dump following this message. (Look at the interpreted section of the dump for recognizable volume serials.)
  4. If the component is present on the volumes, then assume that this entry is the most current one. Delete the existing catalog entry (if one is present), specifying NOSCRATCH, then redefine (DEFINE NONVSAM or DEFINE CLUSTER RECATALOG) this entry.
  5. If the component is not present on the volumes, then the entry cannot be the most current one.
  6. Delete the existing catalog entry (if one is present), specifying NOSCRATCH.
Parent topic: CRU messages