IBM Support

PH42413: MAS FAILS TO CONNECT TO CMAS WITH TOPOLOGY CONNECT MESSAGE DURING START UP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When starting up the MAS the following messages occur as it
    tries to connect to the local CMAS:
     +EYUTS0001I applid Topology Connect for MYMAS1 Initiated -
    APPLID(MYMAS1) CICSplex(MYPLEX).
    
     +EYUTS0002E applid Topology Connect for MYMAS1 Failed -
    APPLID(MYMAS1) CICSplex(MYPLEX).
    
    
    This results in a dump titled:
    EYU0XZPT Dump,cmasname,cmasname,lpar,CMAS,TSSC,0000123,TRAC,EYU
    0TSSC,date,time     .
    
    
    The dump was taken due to a topology connect failure. During
    the topology connect process, we attempted to acquire a lock on
    the CLCB for the MAS, but failed with the INVALID_RESOURCE_PTR
    error because the lock is not available.  Right before this in
    the trace we see the LEEI task running method CLET to process
    the initial connection request from the MAS. This shows the XSRS
    call attempting to create that lock, and that method call
    failed. This is why the lock is not available to be acquired
    later during top connect.  The reason code from the XSRS
    exception shows RESOURCE_ALREADY_REGISTD.
    
    During the CMAS restart, the communications component has
    acquired a new block of storage in the MAS data space to contain
    the CLSD and CLCBs for CMAS-MAS communication. The address of
    the new CLCB for the MAS is 00012345, which would place the lock
    for that MAS CLCB at 00089395. Unfortunately that area is
    already registered as a lock block! This suggests that an
    earlier run of the CMAS was not able to release that storage
    area correctly, and left the lock registered.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM Users.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Topology connect may fail on a CMAS     *
    *                      region with message EYUTS0002E, due to  *
    *                      bad CLCB reuse. This can occur          *
    *                      following a CMAS warm start, after the  *
    *                      CMAS region has previously terminated   *
    *                      ungracefully or cancelled.              *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF which resolves        *
    *                 APAR PH42413, all CMAS regions should        *
    *                 be restarted to activate the fix.            *
    *                 The restarts do not need to occur at the     *
    *                 same time.                                   *
    ****************************************************************
    If a CMAS abnormally terminates while the CPSM Communications
    component is processing the ICT attach to initialise the
    connection to a MAS, then the CLCB representing the link to that
    MAS can be left in an invalid state.
    During a subsequent CPSM CMAS WARM restart, when
    the CPSM communication component is initialised, previous state
    should be clean up and control blocks freed from the shared
    data spaces. However, if the CLCB state was left in the invalid
    state, due to the abnormal termination during its initialisation
    then it cannot be correctly freed.
    
    After this occurs, if the CPSM communication component
    attempts to allocate another CLCB control block, in the same
    area of the shared data space, the initialisation of this block
    will fail. This will then result in ESSS believing a lock is
    allocated for this control block, when it was for the previous
    block.
    
    When this CLCB is later used, calls to register this control
    block will fail with RESOURCE_ALREADY_REGISTD. This can
    result in topology connect failing, when it attempts to
    establish the connection for remote MAS regions. In this case
    topology connect fails with message :
      EYUTS0002E Topology event for sysname Failed - APPLID (applid)
      CICSplex (plexname)
    This is also accompanied by abend ASRA from EYU0CLET.
    

Problem conclusion

  • Method EYU0CLET (CLET) which contains initialisation code
    to be run during CMAS warm restart, as well as serving as
    the initial contact module for new MAS connections,
    has been changed.
    - Additional logic is provided to correctly free a CLCB which
      was part way through initiation (ICT ATTACH) or release (ICT
      DETACH) when the previous instance of the CMAS was cancelled.
    - Improved error handing is provided in the case where a new
      CLCB retrieved from the free CLCB chain cannot be initialised.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH42413

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-29

  • Closed date

    2022-02-09

  • Last modified date

    2022-03-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI79230

Modules/Macros

  • EYU0CLET
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R30M PSY UI79230

       UP22/02/11 P F202

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.6"}]

Document Information

Modified date:
02 March 2022