A fix is available
APAR status
Closed as program error.
Error description
You upgrade your non-MP (non-Maintenance Point) CMAS. On first startup, the non-MP CMAS communicates with the MP CMAS for the CICSPlex(s) to which it is assigned to manage. The EYULOG shows it imports the CICSPlex(s). However, subsequent CONNECT or JOIN (or other RTA related events) fail, issuing messages similar to: . EYUPS0106W <cmasname> RTASAM event EMASJOIN processing failed. or EYUPS0106W <cmasname> RTASAM event EMASSTRT processing failed. . The problem that causes these failures is the RTA Plex Descriptor token has not been stored. To verify that this is the case, do the following: . - Logon directly to the CMAS - Enter transaction COD0 - Enter START TSXR You'll receive a warning. Press Enter to continue. - Fill in the following input parms: . EYUQTSXR IN *FUN FUNCTION( RETCPDT ) *CHR DEBUG( TESTTEST ) *CHR CONTEXT( xxxxxxxx ) <<<<<<<< replace with *CMP SUBCOMP_ID( RTA ) your plex name OUT *RSP RESPONSE( * ) *REA REASON( * ) *EPT SUBCOMP_DATA_TOKEN( A= * O= ) STA STATUS( ) . - Press Enter, then PF3 to return. The status will first show as: . S Type Meth Task# Debug Status START TSXR TESTTEST Waiting on subtask/method start. . - Press enter to see the status change to: . S Type Meth Task# Debug Status START TSXR 12345 TESTTEST Completed, RESPONSE:OK . - Put a 'V' next to the START command to View the results and press Enter. If you are encountering this error, you will see zeros for the SUBCOMP_DATA_TOKEN value: . *EPT SUBCOMP_DATA_TOKEN( A= 00000000 O= 00000000 ) . - To exit the COD0 transaction, type EXIT on the command line. . Additional Symptom(s) Search Keyword(s): KIXREVSVR . Customers putting on the fix for this APAR should also apply the following fix, which deals with similar timing issue during first startup of a CMAS after an upgrade: . PI32997 UI26183
Local fix
Recycle the CMAS. This occurs due to a timing issue during first startup after an upgrade. A recycle of the CMAS should correct the situation if you do not already have the PTF for this issue applied.
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: When a CICSplex is added, removed, or * * removed and re-added to a CMAS's data * * repository during CMAS intialization, * * various errors may occur. The action * * can be by design, for example, because * * an ASSIGN (add) or UNASSIGN (remove) * * was issued for the CMAS to a CICSplex, * * or it can be the result of the * * maintenance point (MP) CMAS determining * * that the CMAS's representation of the * * CICSplex is invalid and must be * * refreshed (remove and re-add). One * * condition that will cause the latter * * will be when a non-MP CMAS is upgraded * * to CPSM V5R2M0 and connects to the MP * * CMAS for the first time after upgrade. * * * * The errors seen include, but are not * * limited to, the following: * * * * - The CMAS may issue one or more * * EYUPS0106W warning message. The * * text of the message will be similar * * to the following: * * * * EYUPS0106W RTASAM event <eventnm> * * processing failed. * * * * - The CMAS may not issue EYULOG * * message EYUCW0107I for the CICSplex. * * The text of the message will be * * similar to the following: * * * * EYUCW0107I Plex end-of-interval is * * set to occur once every <nnnn> * * minutes for context (<plexname>). * * * * - If the action is a remove and add, * * MASes that were connected to the * * CMAS when it was last up and were in * * restart mode, may fail to Topology * * Connect to the CMAS. * * * * - If the action results in the add of * * a CICsplex, the CMAS may not * * Topology Join MASes that are * * actively connected to other CMASes * * in the network for the CICSplex at * * the time the add occurs. * * * * - If the action results in the remove * * of a CICsplex, abend ASRA/S0C1 may * * occur in method EYU0WMAD (WMAD) in * * the CMAS. The offset for the abend * * will be indicated as ???????? in the * * EYUXL0905E message issued by the * * CMAS to document the abend, and the * * PSW and R14 at time of abend will * * point to low core. * * * * - Method EYU0XDRS may fail with a * * response of EXCEPTION and a reason * * of METHOD FAILED if called to * * process a CICSplex update request * * while a CICSplex add or remove is in * * progress. * * * * A recycle of the CMAS may resolve the * * errors. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes must be * * restarted. Note that the restarts do not * * need to occur at the same time. * **************************************************************** When a CICSplex is added to a non-maintenance point (MP) CMAS, before the CICSplex records are imported into the CMAS's data repository (EYUDREP) by method EYU0XDIP (XDIP), methods EYU0CCPD (CCPD) and EYU0XDDP (XDDP) may be called to perform cleanup processing to ensure that no residual records for the CICSplex reside in the CMAS's EYUDREP. As part of this cleanup, CCPD and/or XDDP may cause a CICSplex remove event to be broadcast to other processing within the CMAS. If this occurs during CMAS initialization, some CPSM components may remove their association with the CICSplex, causing errors to occur when future processing for the CICSplex is required. For example, if the RTA component removes it association with a CICSplex, its system availability monitoring (SAM) subcomponent will fail with message EYUPS0106W when processing an event associated with the CICSplex. Additionally, as part of the CICSplex import process, XDIP will issue a CICSplex add event that the Topology component service method EYU0TIST (TIST) listens for under the TIST long running task. When received, TIST calls method EYU0TSPA (TSPA) to initialize the CICSplex for Topology. After performing this initialization, TSPA will broadcast a CICSplex add event to the other CPSM components in the CMAS, and then calls method EYU0CPEJ (CPEJ), which will perform processing to ensure that MASes that are actively connected to other CMASes in the network for the CICSplex at the time of the import are Topology Joined by the CMAS. Before performing its processing, TSPA will verify if the CICSplex has already been initialized by Topology. If that is the case, it will not broadcast the CICSplex add event and will not call CPEJ. If a CICSplex is added to a CMAS after the Communications component has completed initialization, and before the Topology component has initialized, then all components besides Communications will have initialized the CICSplex. Since Topology initialized the CICSplex during CMAS initialization, when TSPA is called from TIST it will not broadcast the CICSplex add event and will not call CPEJ. As a result, the Communications component will not be informed of the CICSplex add, so if will not issue the EYUCW0107I message for the CICSplex, and MASes that are active at the time of the CICSplex import will not be Topology Joined by the CMAS.
Problem conclusion
Methods CCPD and XDDP have been updated to not issue a CICSplex remove event if the CICSplex did not exist in the CMAS data repository at the time either runs. Method XDIP has been updated to check if CMAS external component initialization has completed when it is called to process a CICSplex add request. If not, then XDIP will wait for that to complete before processing. Methods XDIP (CICSplex add), XDDP (CICSplex remove) and XDRS (CICSplex update) have been updated to serialize processing by acquiring a common enqueue upon entry, and releasing the enqueue upon exit. Method EYU0XDIN (XDIN - data repository component initialization) has been updated to build the enqueue name and store it in the data repository major object environment block (MOEB) so that it is accessible to XDIP, XDDP and XDRS. Method EYU0XLBI (XLBI) has been updated such that after it completes component initialization, it will check to see if XDIP is waiting to process a CICSplex add request. If so, XLBI will POST the waiting XDIP so that it can start processing. Method EYU0XLBV (XLBV) has been updated such that when it is running in a MAS that is in RESTART mode, if the CMAS that it was previously connected to becomes active but does not manage the CICSplex to which the MAS was connected, the MAS will continue to wait for the CMAS to become a manager for the CICSplex. Method WMAD has been updated to correct abend ASRA/S0C1 that can occur when a CICSplex is removed from a CMAS during initializtion.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI42334
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
90M
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2015-06-03
Closed date
2015-09-08
Last modified date
2015-10-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI30942
Modules/Macros
EYU0CCPD EYU0WMAD EYU0XDDP EYU0XDIN EYU0XDIP EYU0XDRS EYU0XLBI EYU0XLBV
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R90M PSY UI30942
UP15/09/10 P F509 ½
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":"5.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":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 October 2015