CRU208I   SMF DELETE IS MOST CURRENT BUT IS 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'}SMF 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 most current SMF record with the NEWER, highest 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 not included in the input.
  • In a multi-system environment, the clocks were not synchronized more closely than the interval between these 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.)
  • 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. 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.
  2. If all SMF data is accounted for, 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:
  3. Review the chain of messages for this entry, looking for the missing INSERT. If an INSERT appears near the top of the chain, probably with a synchronization check or another error message, then the NEWER DELETE may be assumed to be the most current record. Confirm that the data set or a component of the VSAM sphere is not actually on the volumes indicated in the dumped DELETE record. 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. If you are uncertain that this is the case, continue with the next step.
  4. If neither of the above apply, assume that SMF data has been lost. Further assume that one of the missing records is for this catalog entry.
    1. The entry will not appear in the IDCAMS LISTCAT output. Use the volume information from the dumped records. 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