PI35429: PROBLEMS WITH SDEP INDOUBTS AND /ERE. 1) LOOP DBFDLSR0 2) INDOUBT NOT RESOLVED CORRECTLY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Problems with SDEP InDoubt processing:
  1) Loop in DBFDLSR0.
  Sequence of log records for UR is 5950,5950 (SDEP ) 5611.
  The 5950 records are first use of a new CI RBA.
  Restart builds LSRTs from 5950s but will only move the data
  from LSRT to buffer at commit ( 5937 ). There is no 5937 before
  IMS abend, so records are not moved.
  The 5611 causes a RIS to be built, in this case by FDBR.
  FDBR produces a 5613 log record for the RIS.
  IMS is then /ERE'd and the 5613 processed. At 5613, DBFDLSR0
  is called to rebuild RIS. DBFDLSR0 loops through LSRTs to
  determine if the RBA is in current DMACXNYW set for DMAC
  ( Area ). Since there was no 5937 log record in the stream,
  and the CI had never been used before, there is no DMHR for
  this RBA on the DMACXNYW chain. A logic error here causes a
  loop because the LSRT chain pointer is loaded to point at next
  LSRT when the RBA is not found on the DMACXNYW chain.
  2) Because the new CI RBA is never 'used' by restart, it is
  never closed out by restart. The new segments in the LSRTs
  for the InDoubt were never moved to a buffer and thus the
  CI RBA contains old data. If a utility happened to run, it
  might be in NOT-FULL status and contain a dummy aborted segment.
  The problem here is that once the RIS structure is built, and
  Resolve InDoubt done - with commit - IMS will read this CI and
  turn off the Indoubt flags in segment prefix, but the CI will
  not have these segments in it at all. Resync Commit does not
  copy the segments from LSRT to CI buffer again, only turn off
  InDoubt flag on assumption segments are already there.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMSFP V13 DEDB SDEP users.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: PROBLEM WITH SDEP INDOUBTS AND /ERE.    *
  *                      LOOP IN DBFDLSR0.                       *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  During /ERE, looping in DBFDLSR0 occurred during SDEP indoubt
  processing under the scenario:
  Sequence of log records for UR is 5950,5950 (SDEP ) 5611.
  The 5950 records are first use of a new CI RBA.
  Restart builds LSRTs from 5950s but will only move the data
  from LSRT to buffer at commit ( 5937 ). There is no 5937 before
  IMS abend, so records are not moved.
  The 5611 causes a RIS to be built, in this case by FDBR.
  FDBR produces a 5613 log record for the RIS.
  IMS is then /ERE'd and the 5613 processed. At 5613, DBFDLSR0
  is called to rebuild RIS. DBFDLSR0 loops through LSRTs to
  determine if the RBA is in current DMACXNYW set for DMAC
  ( Area ). Since there was no 5937 log record in the stream,
  and the CI had never been used before, there is no DMHR for
  this RBA on the DMACXNYW chain. A logic error here causes a
  loop because the LSRT chain pointer is not loaded to point
  at next LSRT when the RBA is not found on the DMACXNYW chain.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  The following change has been made to correct the reported
  problem:
  
  DBFDLSR0:  Correct code to obtain the next LSRT on chain.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  PI41155 UI27698

Modules/Macros

• DBFDLSR0
  

Fix information

• Fixed component name

  IMS V13

• Fixed component ID

  5635A0400

Applicable component levels

• R300 PSY UI27698

     UP15/05/20 P F505 Ž

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.