A fix is available
APAR status
Closed as program error.
Error description
max member id in groupbufferpool could not be set correctly and result in long grecp recovery(look for old logs.)
Local fix
n/a Another symptom: DSNJ113E or DSNI005I with 00D1032A can show up during grecp recovery because older grecp recovery timestamp (lrsn) is used and log data set having the lrsn cannot be located. DSNJ113E -???? DSNJR003 LRSN 'CA3D3583BFBB' NOT IN ANY ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=????, CORRELATION-ID=014.AUTOGREC, MEMBER-ID=? DSNI005I -???? DSNICLST LPL OR GRECP RECOVERY CANNOT BE DONE FOR START DATABASE COMMAND-ID = 91 OBJECT TYPE 00000200 OBJECT NAME dbname.tsname REASON 00D1032A TYPE 00000200 NAME dbname.tsname
Problem summary
**************************************************************** * USERS AFFECTED: DB2 data sharing users * **************************************************************** * PROBLEM DESCRIPTION: Long GRECP recovery time or ABEND0C4 * * in DSNB1CNE after UK77778, UK77779, * * or UK77780 was applied * **************************************************************** * RECOMMENDATION: * **************************************************************** After ptfs UK77778, UK77779, or UK77780 are applied, a buffer pool level variable, used to remember the members connecting to a group buffer pool (GBP), may remain unchanged when a new member is added into a data sharing group, or remain zero when a new GBP is used or a new data sharing group is built. This can lead to an older GBP recovery timestamp which either does not cover the activities of the newly added member or does not advance with GBP checkpoints. This also causes an incorrectly allocated notify message to be sent by GBP checkpoints. The notify exit logic gets an ABEND0C4.
Problem conclusion
DB2 code has been modified to update the buffer pool level variable correctly to reflect the DB2 members connecting to a GBP.
Temporary fix
Comments
APAR Information
APAR number
PM77211
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-15
Closed date
2013-01-14
Last modified date
2013-03-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK90931 UK90932 UK90933
Modules/Macros
DSNB1GC1
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK90931
UP13/01/31 P F301
R810 PSY UK90932
UP13/01/31 P F301
R910 PSY UK90933
UP13/01/31 P F301
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":"9.1","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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 March 2013