DFR3130E error_type ERROR IN xxxx DDNAME=ddname BLK=blk_num nnnnnnnn TO nnnnnnnn

Explanation

An error was found in the indicated log data set. The error type is indicated by error_type as follows:
Type
Meaning
READ
Read error.
BLEN
Log block length is less than 3 bytes.
RLEN
Log record length is less than 3 bytes.
BSEQ
The log block sequence number of a log block in OLDS is not one greater than that of the preceding block.
LSEQ
The log record sequence number of a log record in OLDS is not one greater than that of the preceding record.
TSEQ
The time stamps in the suffixes of OLDS blocks are not in ascending sequence.
WRITE
A write error has occurred when attempting to write (1) a log block that remained in WADS, (2) a sync point log record (X'38' or X'5938') that is used to invalidate the transaction that did not reach a sync point, or (3) a log record (X'06' or X'48') for closing OLDS.

blk_num indicates the block number within the log data set. nnnnnnnn TO nnnnnnnn is displayed for BSEQ, LSEQ, and TSEQ, indicating the sequence error detail.

If the log mode is dual, this message is not displayed and processing continues if the corresponding log record of the other log data set is not in error (except for WRITE).

System action

If any of the above errors except WRITE was found for OLDS when IMS failed, IMS DEDB Fast Recovery assumes that the block immediately preceding the error block is the last-written block, and closes the OLDS after writing log blocks that remain in WADS. Otherwise, the job ends with an abend code of U3130.

The WRITE error occurs only for the OLDS that was in use when IMS failed. For dual log data sets, the job ends with an abend code of U3130 if errors were found in both data sets.

User response

No action is needed if the job ended normally and the error was not a WRITE error.

For a WRITE error, recover the OLDS in error from a correct OLDS or register the OLDS error condition to the DBRC RECON data set by using the DBRC CHANGE.PRILOG or CHANGE.SECLOG command.

If DBRC=N was specified in the EXEC statement and the job ended abnormally with a sequence error (BSEQ, LSEQ, TSEQ), check if a correct ddname was specified for message DFR3110A. If not, rerun the job and specify the correct ddname. In any other case, use the Log Recovery utility to recover the error block and rerun the job.