A fix is available
APAR status
Closed as program error.
Error description
In a CPU constraint environment, a CMAS may fail to response to the other CMAS, which leads to the termination of the CMAS-CMAS connection. Later, the CMAS with lower SYSID, also known as the first speaker, will initiate a new connection request to the other CMAS (the quiet side). However, due to CPU starvation, the previous connection has not yet been able to terminate. The CMAS couldn't handle the new request, and CLMT goes into an error path. Code added in V5.5 then attempts to reference a CLCB control block using a pointer which has not been instantiated, which leads to the ATCV abend eventually.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R5M0 and V5R6M0 users. * **************************************************************** * PROBLEM DESCRIPTION: Module EYU0CLMT or EYU0CLCT reports an * * S0C4 abend while attempting to * * establish a new CMAS to CMAS * * connection. * **************************************************************** * RECOMMENDATION: After applying the PTF which resolves * * APAR PH31408 all CMAS regions must be * * restarted. The restarts do not need to * * occur at the same time and can occur in * * any order. * **************************************************************** CMAS to CMAS links require a pair of tasks (a send task and a receive task) to execute in each region. When two CMAS regions establish a new connection, the initial contact transient (ICT) module runs to establish a receive task. If the link cannot be established (for example a prior link between this pair of regions has not yet completely terminated) then the ICT attempts to reply to the partner CMAS with an error code. While handling this error an attempt is made to access the link control block (CLCB) but one was never allocated. The attempt to access storage linked from the CLCB results in an 0C4 abend. The ICT executes module EYU0CLMT under transaction LNMI for connections using the MRO protocol, or EYU0CLCT under transaction LNCI for LU62 connections. Additional Keywords: abend0C4 abendS0C4 abendATCV ConExist
Problem conclusion
EYU0CLMT and EYU0CLCT have been updated to ensure that a CLCB is only referenced in the case where one has been acquired.
Temporary fix
Comments
APAR Information
APAR number
PH31408
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
20M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-11-09
Closed date
2021-04-15
Last modified date
2021-05-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI74944 UI74945
Modules/Macros
EYU0CLCS EYU0CLCT EYU0CLCU EYU0CLMS EYU0CLMT EYU0CLMU EYU0CPAC
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
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.
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5"}]
Document Information
Modified date:
04 May 2021