A fix is available
APAR status
Closed as program error.
Error description
You have a CICS region (Managed Address Space, MAS) that is connected to CPSM. Your MAS experiences MVS related storage issues such as S878 or S80A. The region either terminates on its own or you cancel the region through the console. At this point the region terminates, and you may see an S922 return code. . Because CPSM has told MVS that they are to be notified when an address space goes away, the CPSM EOT (End Of Task) and EOM (End Of Memory) routines are invoked by MVS RTM. These EOT and EOM routines are supposed to clean up the CPSM environment when a MAS region ends. However, due to the storage shortage, the exit routines may not be able to perform their function. This may leave the CPSM environment in a state where it believes the MAS region is still running, even after it has terminated. On the subsequent restarts of the MAS, CICS will initialize but the CPSM MAS agent will not connect to the CMAS. You will see the following messages in your MAS . EYUCL0112E <masappl> Protocol Services initialization unable to perform ICT Attach. EYUCL0124E <masappl> A failure occurred while attempting to connect to CMAS <cmasname>. EYUCL0101E <masappl> Protocol Services initialization failed. EYUCI0101E <masappl> Communications initialization failed. EYUXM0004I <masappl> Message Services termination complete EYUXL0023I <masappl> Trace Services termination requested EYUXZ0001I <masappl> Trace Services termination complete EYUXL0012I <masappl> ESSS disconnect complete EYUXL0112E <masappl> LMAS initialization failed . . While in the EYULOG for the CMAS that it's trying to connect to you will see the following: . Shortly after the previous run of the MAS terminated: EYUCS0207W <cmasappl> Connected MAS <masname> is not responding - APPLID(<masname>) CICSplex(plexname). . . and then upon restart attempts for this same MAS, you see: EYUCL0008I <cmasappl> ESSS ICT entered for Attach to <masname>. EYUCL0107E <cmasappl> ESSS ICT attach to <masname> failed, MAS already exists. EYUCL0009I <cmasappl> ESSS ICT entered for Detach from <masname>. . Additional Symptom(s) Search Keyword(s): KIXREVSCB
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: You have a CPSM Managed Address * * Space (MAS) which is connected to a * * CMAS. Your MAS experiences MVS re- * * lated storage issues such as abend * * S878 or abend S80A. Either the region * * terminated on its own or you cancelled * * the region through the system console. * * The region terminated and you might * * have seen an S922 abend. * * * * On the subsequent restarts of the * * MAS, CICS will initialize but the CPSM * * MAS agent will not connect to the CMAS. * * You will see the following messages in * * your MAS joblog: * * . * * EYUCL0112E Protocol Services * * initialization unable to * * perform ICT Attach. * * EYUCL0124E A failure occurred * * while attempting to connect * * to CMAS <cmasname>. * * EYUCL0101E Protocol Services * * initialization failed. * * . * * and finally: * * . * * EYUXL0012I ESSS disconnect * * complete * * EYUXL0112E LMAS initialization * * failed * * . * * In the EYULOG for the CMAS to which * * the MAS attempted to connect you will * * see the following messages. * * . * * Shortly after the MAS terminated: * * . * * EYUCS0207W Connected MAS <mas> * * is not responding - * * APPLID(<masappl>) * * CICSplex(<plexname>). * * . * * Then during restart attempts for this * * same MAS, you see: * * . * * EYUCL0008I ESSS ICT entered for * * Attach to <mas>. * * EYUCL0107E ESSS ICT attach to * * <mas> failed, MAS already * * exists. * * EYUCL0009I ESSS ICT entered for * * Detach from <mas>. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, the CPSM Environment Service System * * Services (ESSS) subsystem address space * * (EYUXvrm where vrm is 410 for CPSM V4R1M0 * * and 420 for CPSM V4R2M0) must be terminated * * and the EYUX subsystem End of Task (EOT) * * exit (EYU9XEET) must be reloaded on every * * MVS image where a CMAS has been executed * * without the updated code, since the last * * IPL. * * * * This can be accomplished in either of two * * ways: * * * * 1 - IPL the MVS Image. * * * * Or: * * * * 2 - Stop all CMASes, MASes, and batch * * API programs executing on an MVS * * image. * * * * - Use EYU9XENF to check that no address * * spaces are connected to the ESSS * * subsystem. * * * * - Use the EYU9XEUT TERMINATE function to * * stop the ESSS. * * * * - Use the EYU9XEUT RELOAD function with * * the EOT option to reload EYU9XEET, * * ensuring that UTILLIB specifies the * * SEYUAUTH library updated by the PTF. * * * * - Refresh LLA to ensure the updated * * version of EYU9Xvrm is picked up. * * * * - Restart any CMASes and MASes which * * execute on the MVS image, insuring * * that updated libraries are being * * picked up. When the first CMAS is * * started the EYUXvrm address space will * * be started automatically. * * * * For details on EYU9XENF and the EYU9XEUT * * TERMINATE function refer to "CICS Trans- * * action Server for z/OS CICSPlex SM Problem * * Determination Version 4 Release 1" * * (GC34-7037-xx) or "CICS Transaction Server * * for z/OS CICSPlex SM Problem Determination * * Version 4 Release 2" (GC34-7203-xx). * * * * Note that each MVS image can be updated * * separately, and systems on an MVS image that * * are using the new code can communicate with * * systems on other MVS images that are not yet * * using the new code. * **************************************************************** Because CPSM has installed subsystem End of Task and End of Memory exits, when an address space terminates modules EYU9XEET (XEET - CPSM End Of Task Exit) and EYU9XEEM (XEEM - CMSP End of Memory Exit) are invoked by MVS RTM. These EOT and EOM modules are supposed to clean up the CPSM environment when a MAS region ends. However, because of the storage shortage, the exits may be unable to perform their function. This could leave the CPSM environment in a state where the CMAS believes that the MAS is still connected, even after the region has terminated.
Problem conclusion
The CPSM CONNECT PC routine was modified to store a pointer to the work area acquired when it is entered in the region's Subsystem Connection Block (XECB). If the TERMINATE PC routine finds a valid XECB containing a saved work area pointer, it will use the pre-allocated block rather that acquiring its own work area. On completion, the TERMINATE routine will free the work area storage. When called for end of memory, a valid XECB will not exist, but the EOM exit executes in the Scheduler address space, which will not be storage constrained. Because the MVS Address Space Control Block (ASCB) may no longer be valid when subsystem EOM exits are called, validation of the ASCB whose address was stored in the Connected Address Space Table Element (CASTE) will be bypassed if the TERMINATE PC routine is called by the EOM exit.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM92599
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
70M
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-09
Closed date
2013-11-05
Last modified date
2013-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI12191 UI12192
Modules/Macros
EYUTXEPC EYU9XECS EYU9XEET EYU9X410 EYU9X420
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"4.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 December 2013