A fix is available
APAR status
Closed as program error.
Error description
During Group restart, all member were coming up and some of them started Retained lock.New member was joying the group which was trigger of Max Connection rebuild. DXRRL770 incorrectly issued IXLLOCK request even if we already found we have an invalid RLE id.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All HIR2220 (irlm220) and HIR2230(irlm230) * * users datasharing SYSPLEXDS. * **************************************************************** * PROBLEM DESCRIPTION: Abendu2025 from DXRRL770 during a group * * restart. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** During a group restart phase DB2 was issuing RETLOCK requests to IRLM to create retained locks. IRLM in turn will send request to all members in the group to create local retained locks for the same resource. A lock structure rebuild happening before the global retain lock is processed, could create a new RLE in the CF. This would result in failure and abendu2025 when the DB2 member which was restarting and had initiated the rebuild to increase the max users to the lock structure, processes the pending retain lock requests received before the rebuild and reacquires the retained lock during startup.
Problem conclusion
GEN: KEYWORDS: SYSPLEXDS *** END IMS KEYWORDS *** This APAR provides a change in IRLM lock structure rebuild logic for increasing the number of connections dynamically. IRLM will not initiate a max user rebuild when the 7th or 23rd member joins the group. This used to be done earlier to accommodate additional members to join the group. With this APAR, IRLM will initiate a max user rebuild only when it is needed, ie. when the 8th or 24th member attempts to join the group and there are no more connections available at that time. This will avoid unnecessary rebuild of the lock structure which could affect CF storage for the lock structure. Rebuilding the lock structure only when it is needed will reduce a timing window where IRLM waits until the rebuild is done. Requests received during this wait may have locking information that may have been altered by the rebuild. This fix will avoid abendu2025 in DXRRL770 on IXLLOCK failure on the member that started the max user rebuild. The IRLM member is not going to an active connector and will not receive any global requests until the rebuild is over.
Temporary fix
Comments
APAR Information
APAR number
PM15077
Reported component name
IRLM V2
Reported component ID
569516401
Reported release
220
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-05-23
Closed date
2011-03-29
Last modified date
2011-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK66258 UK66260
Modules/Macros
DXRRC710 DXRRC732 DXRRC752 DXRRLMCB DXRRL710 DXRRL732 DXRRL752 DXRRS710 DXRRS732 DXRRS752
Fix information
Fixed component name
IRLM V2
Fixed component ID
569516401
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":"BU048","label":"IBM Software"},"Product":{"code":"SSEPHL","label":"IRLM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 May 2011