IBM Support

PH60089: CMAS ISOLATION POSSIBLE AFTER APPLYING FIX FOR PH48455. EYUCP0205S AND EYUCP0011E REPORT REPOSITORY SYNC FAILED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are restarting many of your CMASs simultaneously after
    running the EYU9XDUT utility against their EYUDREP data sets.
    You receive messages indicating the repository resync process
    has failed, and that one or more of your CMASs are being
    isolated. Some of the messages in the CMAS job output related to
    this event may include the following (not all messages in each
    CMAS)
    
    EYUCP0033I cmasname Disconnect requested for CMAS cmasname2.
              Reason: CMAS isolated.
    EYUCP0207E CICSplex plexname on CMAS cmasname cannot be
              redefined as MASes are active on CMAS cmasname
    EYUCP0205S plexname Repository Synchronization with CMAS
              cmasname failed.
    EYUCP0011E cmasname Repository synchronization failed for one or
              more CICSplexes. This CMAS is being isolated at the
              request of CMAS (cmasname).
    

Local fix

  • Simply restarting the isolated CMAS may bring it back into the
    CICSplex network
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM users                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When multiple CMASs connect to the MP   *
    *                      at the same time, e.g. when restarting  *
    *                      the MP CMAS, and one CMAS has had its   *
    *                      EYUDREP upgraded by EYU9XDUT, other     *
    *                      CMAS(es) can be isolated.               *
    *                                                              *
    *                      Messages in the MP CMAS -               *
    *                      +EYUCP0207E xxxxxxxx CICSplex yyyyyyyy  *
    *                      on CMAS zzzzzzzz cannot be redefined    *
    *                      as MASes are active on CMAS zzzzzzzz    *
    *                      +EYUCP0010E xxxxxxxx Synchronization    *
    *                      for CICSplex yyyyyyyy on CMAS zzzzzzzz  *
    *                      failed. That CMAS is being isolated     *
    *                                                              *
    *                      Messages in CMAS zzzzzzzz -             *
    *                      +EYUCP0033I zzzzzzzz Disconnect         *
    *                      requested for CMAS xxxxxxxx. Reason:    *
    *                      CMAS isolated.                          *
    *                      +EYUCP0011E zzzzzzzz Repository         *
    *                      synchronization failed for one or more  *
    *                      CICSplexes. This CMAS is being isolated *
    *                      at the request of CMAS (xxxxxxxx).      *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF to all CMASs. These can be     *
    *                 done in any order.                           *
    ****************************************************************
    When multiple CMASs connect to the Maintenance Point (MP) CMAS
    at the same time, and one of its CMASs has had its EYUDREP
    upgraded using the EYU9XDUT utility, then it is possible for
    other CMASs, that have MASs active, to be isolated.
    This problem is due to timing between the multiple CMASs
    connecting, including one where the data repository has been
    updated in the described manner. It could also occur if
    no definitional updates have been made to the CICSPlex SM
    data repository for at least two week prior to the
    CMAS restart.
    
    Method CPLT (EYU0CPLT) reread the CICSplex level,
    CPLXCMAS_SYNCDATA, just before it was used so it knew about the
    latest changes. However it didn't know about MPSYNCCR record
    additions in some cases, leading to delete/define of the remote
    CICSplex definition and possible CMAS isolations as the new data
    was propagated.
    

Problem conclusion

  • This APAR rereads the MPSYNCCR records available info,
    CPLXCMAS_FSYNC, just before it uses it so it knows if it can
    do an incremental upgrade of the CICSplex rather than a
    delete/define, which can be more disruptive.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH60089

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    30M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-02-28

  • Closed date

    2024-03-19

  • Last modified date

    2024-04-01

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

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

    PH60167 UI96131 UI96132

Modules/Macros

  • EYU0CPLT
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R20M PSY UI96132

       UP24/03/23 P F403

  • R30M PSY UI96131

       UP24/03/23 P F403

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":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.6","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
03 April 2024