IBM Support

PI98974: CPSM CMAS IS ISOLATED AFTER BEING RECYCLED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You run CPSM and recycle a non-MP CMAS. When the CMAS is
    started again, it gets removed from the CICSplex and becomes
    isolated.
    .
    This is indicated by following message:
    .
    +EYUCP0023E A communications failure has occurred while
                performing Repository Synchronization with CMAS.
                That CMAS is being isolated.
    .
    This problem is caused by a timing issue. As part of the
    automatic DREP synchronization process between the MP CMAS xxxx
    and non-MP CMAS yyyy, the non-MP CMAS needed to be deleted and
    re-added to the CICSplex by the MP CMAS.
    .
    It was found that during this automatic delete-and-re-add
    process, MASes joined the non-MP CMAS which prevented the
    CICSplex from  being re-added. This meant that the CMAS had
    been deleted from the CICSplex and resulted in its isolation.
    

Local fix

  • not available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of CPSM V5.2, V5.3 and V5.4.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a CMAS is going through automatic    *
    *                      plex delete/re-add processing as        *
    *                      part of DREP synchronization, it may    *
    *                      become isolated and message             *
    *                      EYUCP0033I issued: Disconnect           *
    *                      requested for CMAS xxxxxxxx.            *
    *                      Reason: CMAS isolated.                  *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, restart all CMASes in the CICSplex.    *
    *                 Note that the CMAS restarts do not have to   *
    *                 occur at the same time.                      *
    ****************************************************************
    During DREP synchronisation, a CMAS may need to be removed
    from the plex and re-added if it is not possible to update its
    copy of the DREP due to it being too out-of-date from the MP
    CMAS.  This plex delete/re-add processing is automatically
    initiated by the MP CMAS.
    There is a timing hole during this processing in which MASes
    may connect to the CMAS in the middle of the CMAS's plex
    deletion process but before the deletion process completes and
    the re-add process begins.  If this occurs, then the CMAS
    cannot be re-added to the plex because MASes are active.
    When diagnosing this problem, it was found that an abend could
    occur in module EYU0CWTU when COMS level 26 tracing was
    active.
    
    KEYWORDS:
    EYU0CWTU ABEND/S0C4 CWTU 0C4 OFFSET 19C
    

Problem conclusion

  • CPSM has been modified to remove a CMAS during its deletion
    process from the ESSS sooner so that MASes are not able to
    join to it during the automatic delete/re-add process which
    may take place as part of DREP synchronization.
    When a CMAS reads its DREP, it checks to make sure that it is
    not currently being deleted from the plex and takes the
    appropriate error logic if it is.
    Module EYU0CWTU has also been modified to stop the
    aforementioned abend from occurring when COMS level 26 trace
    is active.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI98974

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-08

  • Closed date

    2018-07-24

  • Last modified date

    2018-08-02

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

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

    UI57424 UI57445 UI57446

Modules/Macros

  • EYU0CCPD EYU0CWTU EYU0XDGR
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R00M PSY UI57445

       UP18/07/26 P F807

  • R10M PSY UI57446

       UP18/07/26 P F807

  • R90M PSY UI57424

       UP18/07/27 P F807

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:
02 August 2018