IBM Support

PH48803: CPSM CMAS REPOSITORY SYNCHRONIZATION FAILURE. CMAS ISOLATION OCCURS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CMAS MPSYNC process may not send records to all CMASes. This is
    due to a timing issue. If the CMASes then are left running 2
    weeks or more, upon next recycle and repository synchronization,
    the MP CMAS may direct the non-MP to delete and reimport the
    CICSPlex. This would not be possible if the non-MP already has
    MASes connected. The following messages may occur in that case
    
    EYUCP0207E applid CICSplex plexname on CMAS cmasname
              cannot be redefined as MASes are active on
    
              CMAS cmasname.
    
    
    EYUCP0033I applid Disconnect requested for CMAS cmasname.
              Reason: CMAS isolated.
    
    
    The send and receive links between the CMASes will also be
    terminated as shown by EYUCL0016I messages.
    

Local fix

  • Shut down all MASes that were connected to the isolated CMAS,
    then recycle the CMAS and allow it to connect to and perform
    repository synchronization with the MP CMAS. Once that has been
    completed and the CICSPlex has been removed and reimported, the
    MASes may be restarted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CPSM users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: During MP-CMAS restart if one of the    *
    *                      attached CMASes requires a data         *
    *                      repository delete/define of a CICSplex  *
    *                      definition it is possible that other    *
    *                      CMASes connecting at the same time are  *
    *                      not informed of this change.            *
    *                                                              *
    *                      A later CMAS restart can lead to a CMAS *
    *                      being forced to isolate.                *
    *                                                              *
    *                      MP-CMAS                                 *
    *                      +EYUCP0207E xxxxxxxx CICSplex xxxxxxxx  *
    *                      on CMAS xxxxxxxx cannot be redefined    *
    *                      as MASes are active on CMAS xxxxxxxx.   *
    *                                                              *
    *                      non-MP-CMAS                             *
    *                      EYUCP0033I xxxxxxxx Disconnect          *
    *                      requested for CMAS xxxxxxxx.            *
    *                      Reason: CMAS isolated.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF and recycle the CMASes. This   *
    *                 can be done in any order.                    *
    ****************************************************************
    The process of CICSPlex SM data repository synchronisation
    occurs when a CMAS which is a Maintenance Point for a CICSplex
    connects to another CMAS which manages that CICSplex. If the
    non-MP CMAS does not have an up to date copy of all CICSplex
    records in the MPs data repository, the MP will attempt to send
    over the MPSYNCCR records describing the required updates.
    If those records are not available, for example because they
    have been aged out of the repository, then the MP CMAS will
    remove the other CMAS from the CICSplex, and add it back.
    This causes a full copy of the CICSplex to be sent.
    
    If multiple CMASes connect to the MP CMAS at the same time, e.g.
    during MP-CMAS restart when the MP-CMAS is the first speaker
    then code in EYU0CPLT processes all the incoming repository
    synchronisation requests at the same time and switches between
    them when a remote response is requested from the non-MP CMAS.
    CPLT reads its own MPSYNCCR level for the CICSplex at the start
    of each process.
    If one of the connecting CMASes requires a Delete/Define of its
    CICSplex definition this adds two new MPSYNCCR records. This
    information would be transmitted to all the other CMASes in the
    CICSplex but some CMASes, currently undergoing synchronisation,
    may not receive this update.
    
    Normally this discrepancy would be resolved by a restart of
    either CMAS. However if the next restart is much later then the
    MPSYNCCR records may have been removed and a delete/define of
    a CICSplex definition is required. If MASes are attached to
    the non-MP CMAS then the CICSplex cannot be deleted and so the
    CMAS is isolated until it can be recycled.
    

Problem conclusion

  • EYU0CPLT has been updated to re-read its own MPSYNCCR level for
    the CICSplex just before it needs to decide on what updates, if
    any, are required.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH48803

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    40M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-08-19

  • Closed date

    2022-08-26

  • Last modified date

    2022-09-01

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

    PH48455

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

    UI82125

Modules/Macros

  • EYU0CPLT
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R40M PSY UI82125

       UP22/08/31 P F208

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"}],"Version":"6.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 September 2022