A fix is available
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 V12 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 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.
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** The following change has been made to correct the reported problem: DBFMIOS0: Add code to use the request RBA DMHRSRBA for validity checking.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI38775
Reported component name
IMS V12
Reported component ID
5635A0300
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-09
Closed date
2016-02-25
Last modified date
2016-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DBFMIOS0
Fix information
Fixed component name
IMS V12
Fixed component ID
5635A0300
Applicable component levels
R200 PSY UI35674
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020