A fix is available
APAR status
Closed as program error.
Error description
MSGDSNJ700I DSNJ700I -R6D1 DSNJPB01 ERROR ATTEMPTING TO ACCESS BSDS FOR PEER MEMBER ID= 5, MEMBER NAME= , followed by: Dump Title: R6D1,ABND=04E-00D10309,U=SYSOPR ,M=N ,C=111.RLMC-DSNJOLGR,M=DSNJRE01,LOC=DSNJL002.DSNJR001+0E06 ------------------------------------------------------------- The abend occurs on restart of a cloned DB2 subsystem trying to clear GRECP. Peer member 5 does not exist, as both the source and target cloned DB2 systems only have 2 members.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Db2 for z/OS V11 and V12 data sharing users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00D10309 in DSNJR001 during * * GRECP recovery. * **************************************************************** * RECOMMENDATION: * **************************************************************** The abend happens when trying to access the logs for an invalid data sharing group member when performing GRECP recovery, which is due to the presence of a log range for the invalid member in the GRECP DBET entry. The bad log range may be there due to the problem fixed by PI49850, where the GCPR contains invalid log ranges due to treating the member restart LRSN list as if it contained 6-byte LRSNs when in fact it had been converted to 10-byte LRSNs. Even after applying PI49850, the bad ranges for members which don't exist can persist until a new instance of the GBP is allocated, which may not occur until a group-wide shutdown has taken place.
Problem conclusion
The GBP damage assessment logic has been modified to only use the GCPR entries for members which actually exist, when marking objects GRECP. These entries are regularly maintained by the GBP structure castout engine, unlike the ones for non-existent members which are only set on a connect to a new GBP instance (and which are meaningless in any case).
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PH07324
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-01-15
Closed date
2019-02-06
Last modified date
2019-03-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI61177 UI61181
Modules/Macros
DSNB1DA1 DSNB1DA2
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 March 2019