PI39386: SPURIOUS DFS2605I AREA=XXXXXXXX DD=XXXXXXXX,ERROR IN RBA OF CI READ DURING MADS CREATE. PM95607 BROKE PQ06447.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer is doing MADS CREATE on Area recently restored from
  an older IC. The Area has data in REORG UOW, which has not
  been used for many releases. IMS validity checks RBA in CI
  suffix vs RBA of read request, and if mismatch DFS2605I will
  be issued and read handled as error:
  DFS2605I AREA=aaaaaaaa,DD=dddddddd,ERROR IN RBA OF CI READ
  This is the same issue as PQ06447 - the REORG UOW may contain
  CIs from other RAA UOWs and hence RBA in CI read won't match
  CI actual RBA. Only MADS CREATE is exposed to this since only
  MADS CREATE would ever read the REORG UOW ( it is no longer
  used for anything ). PQ06447 corrected this to bypass validity
  check for the REORG UOW. However, it seems PM95607 broke this
  check by reversing the comparison - instead of requested RBA
  ( DMHRSRBA ) being checked, the RBA in CI suffix or *read* CI
  is checked, which of course is NOT in the REORG UOW so the
  error occurs.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMSFP V13 DEDB MADS users.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: SPURIOUS DFS2605I AREA=XXXXXXXX         *
  *                      DD=XXXXXXXX,ERROR IN RBA OF CI READ     *
  *                      DURING MADS CREATE.                     *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  Customer is doing MADS CREATE on Area recently restored from
  an older IC. The Area has data in REORG UOW, which has not
  been used for many releases. IMS validity checks RBA in CI
  suffix vs RBA of read request, and if mismatch DFS2605I will
  be issued and read handled as error:
  DFS2605I AREA=aaaaaaaa,DD=dddddddd,ERROR IN RBA OF CI READ
  This is the same issue as PQ06447 - the REORG UOW may contain
  CIs from other RAA UOWs and hence RBA in CI read won't match
  CI actual RBA. Only MADS CREATE is exposed to this since only
  MADS CREATE would ever read the REORG UOW ( it is no longer
  used for anything ). PQ06447 corrected this to bypass validity
  check for the REORG UOW. However, it seems PM92552 broke this
  check by reversing the comparison - instead of requested RBA
  ( DMHRSRBA ) being checked, the RBA in CI suffix or *read* CI
  is checked, which of course is NOT in the REORG UOW so the
  error occurs.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  The following change has been made to correct the reported
  problem:
  
  DBFMIOS0:  Add code to use the requested RBA DMHRSRBA for
             validity checking.
  

Temporary fix

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

Comments

APAR Information

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

  PI38775

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

  UI35675

Modules/Macros

• DBFMIOS0
  

Fix information

• Fixed component name

  IMS V13

• Fixed component ID

  5635A0400

Applicable component levels

• R300 PSY UI35675

     UP16/02/27 P F602 Ž

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.