A fix is available
APAR status
Closed as program error.
Error description
You may get a series of messages similar to the following: . hh:mm:ss EYUTS0001I cmasname Topology Disconnect for masname Initiated - APPLID(masname) CICSplex(plexname). hh:mm:ss EYUTS0003I cmasname Topology Disconnect for masname Complete - APPLID(masname) CICSplex(plexname). - - - - hh:mm:ss EYUTS0001I cmasname Topology Join for masname Initiated - APPLID(masname) CICSplex(plexname). hh:mm:ss EYUTS0002E cmasname Topology Join for masname Failed - APPLID(masname) CICSplex(plexname). . DISCONNECT processing occurs under an existing task, TIST, while CONNECT and JOIN processing occur under new tasks (TISC and TISJ respectively.) If a CONNECT or JOIN is received by a CMAS, and the new TISC or TISJ tasks get delayed for some reason (MXT, SOS, or the CMAS is too busy to handle them for another reason) there is an opportunity for a DISCONNECT request to come in and get handled immediately by the already-running TIST task. In that case, you could see a DISCONNECT happen successfully, the MAS completes its shutdown, then CONNECT or JOIN messages for the MAS which at that time may very well not be running. . This APAR is being opened to clarify the messages that are produced in such circumstances. . Additional Symptom(s) Search Keyword(s): KIXREVEPH
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R1M0 and V5R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: When a MAS is terminated shortly after * * it is started or is terminated while a * * CMAS is in the process of starting, it * * is possible for a CMAS to process the * * Topology disconnect for the MAS * * termination before processing the * * Topology connect or join for the MAS * * start. When this occurs, the * * EYUTS0001I/EYUTS0003I Topology * * disconnect initiated and complete * * messages may precede the EYUTS0001I * * Topology connect or join initiated * * message, and the EYUTS0002E error * * message will be issued for the connect * * or join. * * * * For example, if this occurs in the * * joining CMAS, the message display will * * likely be similar to the following: * * * * EYUTS0001I Topology Disconnect for * * <masname> Initiated - * * APPLID(<applid>) * * CICSplex(<plexname>). * * * * EYUTS0003I Topology Disconnect for * * <masname> Complete - * * APPLID(<applid>) * * CICSplex(<plexname>). * * * * EYUTS0001I Topology Join for * * <masname> Initiated - * * APPLID(<applid>) * * CICSplex(<plexname>). * * * * EYUTS0002E Topology Join for * * <masname> Failed - * * APPLID(<applid>) * * CICSplex(<plexname>). * **************************************************************** * 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 learns of a MAS start or termination, an event is sent to the processing queue for method EYU0TIST (TIST), which runs under the long running task TIST. When TIST receives a connect or join event, it requests that a TSSC (connect) or TSSJ (join) task be started to handle the request. If TIST receives a disconnect request, it calls method EYU0TSST directly to handle the request. If the disconnect request is received before the TSSC or TSSJ task has started, it is possible that TSST will run first. When this occurs, the connect or join will be properly terminated, but with an error message instead of a more appropriate message.
Problem conclusion
Copybook EYURTISD, which maps the main Topology component control block for a MAS, the CICS system descriptor block (CSDB), has been updated to include two new time stamps, one indicating when TIST processed a connect or join event for a MAS, and one indicating when TIST processed a disconnect event for a MAS. Changes have been made to TIST to set these time stamps, and to TSST, EYU0TSSC (TSSC) and EYU0TSSJ (TSSJ) to examine the time stamps. Based upon the examination, if TSST processes a disconnect before TSSC or TSSJ have been able to process the connect or join, then: - TSST will suppress issuing the EYUTS0001I/EYUTS003I Topology disconnect initiated and complete messages. - TSSC or TSSJ will issue the EYUTS0001I Topology connect or join initiated message, but instead of issuing the EYUTS0002E error message, they will issue the EYUTS0025I informational message. This message will be similar to either of the following: EYUTS0025I Topology Connect for <masname> terminated due to Disconnect request - APPLID(<applid>) CICSplex(<plexname>). EYUTS0025I Topology Join for <masname> terminated due to Disconnect request - APPLID(<applid>) CICSplex(<plexname>).
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI24066
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
80M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-08-18
Closed date
2014-11-18
Last modified date
2015-03-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI23166 UI23167
Modules/Macros
EYU0TIST EYU0TSSA EYU0TSSC EYU0TSSJ EYU0TSST
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
01 May 2020