A fix is available
APAR status
Closed as program error.
Error description
During shutdown of the System Automation Netview customer trapped an abend0C4 in IEAVEPST via SLIP during POST processing. Dump analysis has shown that there is a timing problem within CICSPlex SM termination processing within System Automation. This timing problem has led to an abend0C4 during XM-POST processing. POST was issued at EYUTXEPC+62C at level UI12192. ECB was freed via Storage Release between POST and XM-POST-SRB- scheduling by EYU0ABN4+14D8.
Local fix
*
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V4R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: During termination of a long-running * * system automation tool which drives the * * CPSM API, you notice an abend S0C4 in * * module IEAVEPST. Examination of system * * trace data for the time when the abend * * occurred shows that a cross-memory POST * * was issued at or near offset +2D32 in * * module EYUTXEPC. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, insure that module EYU9A420 in the * * linklist concatenation is replaced by the * * updated version from SEYULINK. Refresh LLA * * to insure that the updated module will be * * ATTACHed during initialization of API pro- * * grams not running as CICS tasks. * * * * After applying the PTF that resolves this * * APAR, the CPSM Environment Services System * * Services (ESSS) Address Space (EYUX420) must * * be terminated on any MVS image on which a * * CMAS has executed, since the last IPL. This * * can be accomplished in either of two ways: * * * * 1 - Insure that module EYU9X420 in the link- * * list concatenation is replaced by the * * updated version from SEYULINK. * * - IPL the MVS Image. * * * * Or, if an IPL is not possible: * * * * 2 - Stop all CMASes and MASes on the MVS * * image. * * - Use EYU9XENF to check that no Address * * Spaces are connected to the ESSS. * * - Use the EYU9XEUT TERMINATE function to * * stop the ESSS service address space. * * - Insure that module EYU9X420 in the link- * * list concatenation is replaced by the * * updated version from SEYULINK. * * - Refresh LLA to ensure the updated * * version of EYU9X420 is picked up. * * * * Restart all CMASes and MASes, insuring * * that the updated libraries are being picked * * up. * * * * For details on EYU9XENF and the EYU9XEUT * * TERMINATE function refer to the manual "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. * **************************************************************** When a CPSM API program ends without going through normal API termination, actions are triggered in the API Control subtask to release resources allocated on behalf of the API program. These actions are triggered by the CPSM termination PC routine running in the EYUX420 address space, by formatting a signal block and adding it to a FIFO chain anchored in the Connected Address Space Table Element (CASTE) associated with the address space in which the API program executed. A cross-memory POST is then executed to POST an ECB waited on by the API Control subtask. When the ECB is POSTed, the API subtask retrieves the first signal block on the chain and performs the requested action. For efficiency, once POSTed, the API Control subtask retrieves and processes all signal blocks on the request chain before it reenters its WAIT. A signal block is queued for each API thread which was open when the API program ended to allow it to be terminated. When no threads remain, an API_TERM signal is added to the chain to cause the Control subtask to shut down. If the API_TERM signal is processed before the Control subtask has reentered its WAIT after processing one or more thread termination signal events, it is possible that the subtask could end, freeing the storage in which the signal ECB was defined, before an SRB is dispatched to perform the cross-memory POST. If this happens, the POST might receive an S0C4 abend in module IEAVEPST or if the storage has been reacquired by another task, a word of storage at the address of the ECB could be overwritten.
Problem conclusion
A new ECB was registered during API subtask initialization, to be POSTed by the termination PC routine instead of chaining a signal block and POSTing the signal ECB. The API Control subtask will not shut down until this new ECB is POSTed, so the storage in which the ECB is defined cannot be released until after the ECB has been POSTed.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI15524
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
2014-04-09
Closed date
2014-04-28
Last modified date
2014-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI15590 UI17480
Modules/Macros
EYUTXEPC EYU0ABO0 EYU9X420
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
R70M PSY UI17480
UP14/04/30 P F404 ½
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 May 2014