Why is the journal dataset empty after a DB2 lockout?

Document ID : KB000046295
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

The batch job received a user abend U0066, which was the result of calling the ABEND routine with a SQL-ERROR-CODE of 66. 

The run was successful, though, but they saw:

FILE-ERRB68 ESTAE HAS DETECTED AN ABEND 
FILE-MSG031B SUCCESSFULLY WROTE THE LAST JOURNAL BLOCK- OK TO PERFORM BACKOUT

But they were not sure how it is saying “ESTATE has detected an abend” even for successful run.  They were seeing these messages for all executions where the journal file was populated with the data.

Why would you get 'ESTAE has detected an abend" even on a successful run?

 

Answer:

This is a known problem:

*** DISPLAY PROBLEM ***

Product: FILESA PROBLEM ACTIVITY - PR05

Problem #: 297

Title: BATCH JOURNAL MISSING RECORDS FILE-ERRB68 AND FILE-MSG031

PROBLEM DESCRIPTION:

CA Filesave batch journal is missing records after ESTAE is executed.  This happens when an application recovers after abend and continues processing.

SYMPTOMS:

Batch job continues processing after FILE-ERRB68 and FILE-MSG031 messages are issued.  This problem can easily go undetected.

The batch journal may be missing records, but users will not be aware of that unless they balance the journal contents against their batch processing. A secondary symptom is if they use the journal in a recovery, and the recovery fails.

IMPACT:

Journal will be missing records. If used in a recovery, not all records will be recovered.

CIRCUMVENTION:

None.

<END>