A fix is available
APAR status
Closed as program error.
Error description
In a multiple LPAR environment you have CMAS's that are connected directly and indirectly to each other. You are in a HUB and WHEEL configurations and you IPL the HUB CMAS. When this occurred, one of the "satellite" CMAS's was isolated by the HUB after the HUB had restarted. The ASYNC element being processed when the ISOLATION occurred indicated that XDGR received a XDGR_KERNERROR. This isn't a communication error, this just says that we were waiting for the repository sync response to be returned from the "satellite" CMAS, and a kernel error occurred. We (the HUB CMAS) have an indirect connection to the "satellite" through a 3rd CMAS per the CMASDIR DLIST. When we check the CMASDIR DLIST for the "satellite" CMAS, it thinks that it has a DIRECT link to the HUB CMAS. So it tries to respond directly to the HUB, but no connection exists. When the direct connection between the HUB and the SATELLITE originally failed, the receive task on the SATELLITE side did not call EYU0CPRL to remove the direct link. ADDITIONAL KEYWORDS: LNCI LNMI LNCS LNMS CLCU CLMU CPRL CLCS CLMS EYU0XDGR
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex/SM V3R1M0 Users * **************************************************************** * PROBLEM DESCRIPTION: If a CMAS to CMAS direct connection * * terminates while in the process of * * initializing, subsequent attempts to * * retry the connection may fail with * * abnormal termination error messages * * (EYUCL0113E) until one or both of the * * CMASes is restarted. * * * * This can lead to other communications * * failures, including but not limited to: * * * * - message EYUCS0105E indicating an * * inability to assign a link set for * * a connection. * * * * - message EYUCP0205S indicating * * repository synchronization errors. * * * * - messages EYUCP0023E and EYUCP0024E * * indicating that a repository * * synchronization error has resulted * * in a CMAS being isolated from the * * CMAS network. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes must be restarted. Note * * that the restarts do not need to occur at * * the same time. * **************************************************************** When a CMAS to CMAS connection is initialized in a CMAS, method EYU0CLCU (CLCU - LU62 receive) or EYU0CLMU (CLMU - MRO receive) turns on a flag in the Link Set Descriptor (EYURCLSD) control block for the connection indicating that cleanup must be performed for the connection when it terminates. If an error occurs during the initialization process that results in the link being terminated, it is possible that CLCU/CLMU may not be called. This will result in cleanup not being performed, which will cause failures when the connection is re-tried, until the CMAS where cleanup was not performed is started.
Problem conclusion
While it is possible that CLCU/CLMU may not be called during a CMAS to CMAS connection attempt, it is required that either or both EYU0CLCT (CLCT - LU62 initial contact) and EYU0CLCS (CLCS - LU62 send) or EYU0CLMT (CLMT - MRO initial contact) and EYU0CLMS (CLMS - MRO send) will be called. As a result, the setting of the cleanup required flag has been moved from CLCU/CLMU to CLCT/CLMT and CLCS/CLMS.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK16892
Reported component name
CPSM CICS 3.1
Reported component ID
5655M1501
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-12-19
Closed date
2006-02-17
Last modified date
2006-03-02
APAR is sysrouted FROM one or more of the following:
PK16943
APAR is sysrouted TO one or more of the following:
UK11826
Modules/Macros
EYU0CLCS EYU0CLCT EYU0CLCU EYU0CLMS EYU0CLMT EYU0CLMU
Fix information
Fixed component name
CPSM CICS 3.1
Fixed component ID
5655M1501
Applicable component levels
R100 PSY UK11826
UP06/02/18 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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
22 February 2023