CRU111I   SMF DELETE WAS SUPERSEDED BUT WAS PRECEDED BY AN SMF DELETE FOR ( t )  catalog entryname /nn NEWER: smftype FROM SYS sysid AT
hh:mm:ss.hh ON mm/dd/yy (yy.ddd)OLDER: smftype FROM SYS sysid AT
hh:mm:ss.hh ON mm/dd/yy (yy.ddd)TIMES DIFFER BY hh:mm:ss [AND
dddd DAYS][NO] SYNCHRONIZATION CHECK
{BASED ON INTERVAL OF ssss
SECONDS}{SINCE ONLY ONE SYSTEM IS
INVOLVED}{SINCE CLOCK DIFFERENCE =
'spec'}RECORD 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.

The SMF record with the NEWER, higher (but not most current) date/time stamp 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.

The SMF record with the OLDER, next-lower date/time stamp 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 OLDER message line.

The TIMES between these two SMF records DIFFER BY hh hours mm minutes and ss seconds (AND dddd DAYS). Synchronization checking for multiple systems is based on the (nonzero) difference in seconds, ssss, supplied by the user. A SYNCHRONIZATION CHECK occurs when the time difference between the two SMF records is less than ssss. NO SYNCHRONIZATION CHECK means the SMF time difference is larger than ssss, or that synchronization checking was bypassed because ONLY ONE SYSTEM IS INVOLVED or because the CLOCK DIFFERENCE was defaulted, spec = NONE, or was specified as spec = 0000.

A record for an insert of this entry should have appeared between these two records, but none was found for one of the following reasons:
  • Some necessary SMF data was lost.
  • Some necessary SMF data was not included in the input.
  • In a multi-system environment, the clocks were not synchronized more closely than the interval between changes to the catalog, resulting in incorrect ordering of an intervening insert from a different system. (The clock on the system performing the insert was behind the clock of the OLDER sysid by more than the interval between the insert and the OLDER delete or ahead of the clock of the NEWER sysid by more than the interval between the insert and the NEWER delete.)

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 that 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 not 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.
  5. If the component is present on the volumes, then the entry cannot be the most current one.
  6. Redefine (DEFINE NONVSAM or DEFINE CLUSTER RECATALOG) this entry.
Parent topic: CRU messages