Record Analysis and Processing produces a summary report of all anomalies encountered that result in a condition code of 0 or 4.

0 ANOMALIES(CONDITION CODES 4 AND 0)

The Record Analysis and Processing program recognizes as anomalies, synchronization checks not accompanied by a sequence error and sequence errors that do not involve the most current record for a catalog entry.

0 SYNCHRONIZATION CHECKS INVOLVING THE MOST CURRENT RECORD
                  BUT WITH NO EVENT SEQUENCE ERROR (CRU113I)

   0 SMF UPDATE PRECEDED BY AN SMF INSERT     (CRU003I)
   0 SMF DELETE PRECEDED BY AN SMF INSERT     (CRU004I)
   0 SMF UPDATE PRECEDED BY AN SMF UPDATE     (CRU005I)
   0 SMF DELETE PRECEDED BY AN SMF UPDATE     (CRU006I)
   0 SMF INSERT PRECEDED BY AN SMF DELETE     (CRU007I)

A "synchronization check" is the condition which exists when there are SMF records for the same catalog entry from different systems within the interval you specified as the multi-system clock difference.

The "most current record" for a catalog entry is either its SMF record with the highest date/time stamp or, if there is no SMF record, its record from the EXPORT input data set.

The main purpose of performing synchronization checking is to help resolve sequence errors. However, even if no sequence errors are noted, a large number of synchronization checks may indicate that the specification for the clock difference was too large.

ERRORS IN EVENT SEQUENCE INVOLVING SUPERSEDED RECORDS

Certain sequences of SMF and EXPORT records These are referred to as "errors in event sequence" or simply as "sequence errors" because there must be a missing record or a record that is actually newer bears an earlier date/time stamp.

A "superseded record" for a catalog entry is either an SMF record that bears a lower date/time stamp than at least one other SMF record for that data set (and so is not processed in favor of the newer record), or it can be a record from the EXPORT input data set of a catalog entry that is also represented by an SMF record. The SMF record is presumed to be the more current representation of the catalog entry.

0 SEQUENCE ERRORS, BUT NO SYNCHRONIZATION CHECK
   0 SMF UPDATE FOR A NON-EXISTENT RECORD     (CRU106I)
   0 SMF DELETE FOR A NON-EXISTENT RECORD     (CRU107I)
   0 SMF INSERT PRECEDED BY AN SMF INSERT     (CRU108I)
   0 SMF INSERT PRECEDED BY AN SMF UPDATE     (CRU109I)
   0 SMF UPDATE PRECEDED BY AN SMF DELETE     (CRU110I)
   0 SMF DELETE PRECEDED BY AN SMF DELETE     (CRU111I)
   0 SMF INSERT PRECEDED BY EXPORT RECORD     (CRU112I)

"Sequence errors" and "synchronization checks" are explained above.

These errors should be investigated carefully because they may indicate an otherwise undetected lost SMF data condition.

Review the log message for each error, noting the date and time. The most common explanation will be that there were SMF records within the interval between the effective start time (specified start time minus the clock difference) and the specified recovery start time,that is, the time the backup copy of the catalog was made.

If the records are not within this "start-up interval", note the date and time of the records in the companion message and investigate the system log and other sources for possible indications of lost data.

0 SEQUENCE ERRORS, WITH A SYNCHRONIZATION CHECK
   0 SMF INSERT PRECEDED BY AN SMF INSERT     (CRU108I)
   0 SMF INSERT PRECEDED BY AN SMF UPDATE     (CRU109I)
   0 SMF UPDATE PRECEDED BY AN SMF DELETE     (CRU110I)
   0 SMF DELETE PRECEDED BY AN SMF DELETE     (CRU111I)

"Sequence errors" and "synchronization checks" are explained above.

Errors in this category are most frequently explained by a difference in the clocks in a multi-systems environment, so that the SMF date/time stamps do not reflect the true order of the catalog updates. If reversing the order of updates makes the sequence a logical one, this is most likely the situation. Otherwise, proceed as for errors in the preceding category.

0 SYNCHRONIZATION CHECKS INVOLVING SUPERSEDED RECORDS
                  BUT WITH NO EVENT SEQUENCE ERRORS (CRU020I)

   0 SMF UPDATE PRECEDED BY AN SMF INSERT     (CRU013I)
   0 SMF DELETE PRECEDED BY AN SMF INSERT     (CRU014I)
   0 SMF UPDATE PRECEDED BY AN SMF UPDATE     (CRU015I)
   0 SMF DELETE PRECEDED BY AN SMF UPDATE     (CRU016I)
   0 SMF INSERT PRECEDED BY AN SMF DELETE     (CRU017I)

"Sequence errors", "synchronization checks" and "superseded records" are explained above. Since no errors are involved in this situation, the most likely explanation is that the clock difference specification is too large (or that the clocks are not synchronized closely enough).