PM68907: DUE TO IMS CHANGE LOG RECORD PRECEDE THE DATABASE UPDATE BEGIN RECORD. CUSTOMER GET DFS896A WHEN RUNNING BBO.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer get DFS896A UNEXPECTED RECORD ENCOUNTERED- SEQUENCE
  ERROR 03 ON DDNAME IMSLOGR when running BBO job.
  And this error message is due to IMS change log record precede
  the database update begin record.
  The problem is occurred by following steps.
  Delete a record which has only root in a PHIDAM. That would
  causes the 50 LOG of the index change precede 5701 LOG of the
  database update begin.
  So if using that log for Batch Backout that would cause error
  message DFS896A.
  

Local fix

• N/A.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V11 HALDB PHIDAM users.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message DFS896A RC03 (unexpected record *
  *                      encountered) was received during Batch  *
  *                      Backout ( BBO ) execution.  The message *
  *                      is issued because the IMS log records   *
  *                      used as input to BBO contained a type50 *
  *                      record ( DB 50 update record ) for a    *
  *                      delete of a PHIDAM root prior to the    *
  *                      type5701 ( DB begin update record ).    *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  During Batch Backout execution for a HALDB PHIDAM database,
  MSGDFS896A RC03 is issued because the first record in the UOW
  was for the delete of a primary index.   When the delete call
  was issued for the PHIDAM root segment, DFSRDBL0 logged the
  delete record ( 50 record ) for the delete of the primary
  index before the begin update record ( type5701 alloc record ).
  Code in DFSRDBL0 skipped the required DBRC alloc call if the
  first call in the UOW was a delete of a PHIDAM primary index.
  This caused the type50 record to be logged before the type5701
  record, creating an out-of-sequence condition for BBO.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  The following module has been modified to correct the reported
  problem:
  
  ************
  * DFSRDBL0 *
  ************
  Code has been modified to test and set the correct bitmask in
  DDIRFUCS / DDIRHFUI so that routine ALLOCALL is called when
  required in order that the DBRC alloc call is made to log the
  type5701 begin update record prior to any type50 database update
  records.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM25262

• APAR is sysrouted TO one or more of the following:

  PM69374 UK83618

Modules/Macros

•    DFSRDBL0
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK83618

     UP12/12/02 P F211

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.