DBUTLTY BACKWARD RECOVERY DB13004W DB13001E 13 (62) ICE025A

Document ID : KB000098408
Last Modified Date : 31/05/2018
Show Technical Document Details
Issue:

DBUTLTY RECOVERY OPTION=BACKWARD with MISMATCH=FAIL getting errors:

 DB13004W - NO RECORD FOUND AT REQUIRED LOCATION                           DUMP---------1                 
 DB13001E - UNEXPECTED RETURN CODE 13 (62) SORT IN LOAD/RETIX HAD AN ERROR 
 DB10045E - ABNORMAL TERMINATION DUE TO ERROR(S) 

Error message in SORT: 

ICE025A 0 RECORD COUNT OFF 

Cause:

All the problems are caused by the first error: 

DB13004W - NO RECORD FOUND AT REQUIRED LOCATION 

The DB13004W error indicates that backward recovery was not able to find the record subject to an ADDIT or UPDAT command. This is because it was subsequently deleted by another transaction. 
When the RECOVERY specifies MISMATCH=FAIL, this will cause the recovery to stop at this point.
This in turn causes the SORT to end prematurely and it returns error ICE025A 0 RECORD COUNT OFF and return code 13 (62). 

In the RECOVERY output it shows you the record causing the problem: 

 JOB NAME R-UNIT   DATE       TIME   REQUEST  BASE  BLOCK      URI  AREA RM START OF RECORD       ERROR MESSAGES                                                             
 CICSS    63,725  4/29/2018 10.30.34 UPDATF04   33  00002007 00005F11 A01    198EHDH45HWHFH33HER0  

There is also a dump of the log record in the output. 

Resolution:

Use the information from the RECOVERY output to run a DBUTLTY RXX report to confirm when the record was deleted. Use the DBID and URI:

REPORT AREA=RXX,LOGPRINT=DETAIL,TSNPRINT=DETAIL,DBID=33,URINUM=00005F11 

Rerun the RECOVERY with MISMATCH=IGNORE to skip the records causing the problem and continue recovering the rest of the TSN.
Additional Information:
See DocOps sections RECOVERY Command (RECOVERY) and  Recovery File (RXX) Report
For other reasons that can cause the return code 13 (62)  see KB000047598