CRU201I SMF RECORD GAP LIMIT EXCEEDED (FORWARD) FOR SYSID sysid yy.ddd hh:mm:ss PRECEDING
RECORDyy.ddd hh:mm:ss RECORD
BEING
PROCESSED - DUMP
FOLLOWS
Explanation
The time difference between contiguous SMF record from the same system, sysid, exceeds the specified gap interval. The date and time, yy.ddd hh:mm:ss, of the previous record from this system is earlier than the date and time, yy.ddd hh:mm:ss, of the record now being processed.
System action
The current record is dumped, the condition code is set to 8 (if not already higher) and and processing continues.
Operator response
Examine the indicated gap to see if there is, or may be, lost SMF data. You should first determine whether all SMF data from this system has been supplied as input. Review the JCL and the allocation messages. If the data sets are out of sequence, message CRU200I should also be produced (given a correct gap specification). Use the date/time stamps of these records, to attempt to establish continuity of the SMF data from this system.
If the gap is not accounted for by the omission of SMF data sets or by the sequence in which they were read, look for an IPL record (message CRU021I) or a lost-data record (message CRU202I). If the IPL record is not preceded by a HALT EOD record, examine the system log and your problem management records to determine if there was a system interruption which accounts for the gap.
The gap may correspond to a period of scheduled or normal inactivity for this system. Examine the dates and times to see if this is the case.