IBM Support

PI24737: EYUCP0016I MESSAGES MAY BE INCORRECTLY ISSUED FOR CMASES THAT ARE NOT CURRENTLY ACTIVE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Implementing the fix for APAR PI17724 in a CPSM 4.2 CMAS that
    connects to a CPSM 5.1 CMAS, requires that the CPSM 5.1 CMAS
    have the fix for APAR PI17725 implemented first, otherwise
    mismatches messages will result for CRESPRGM and CRESLIBR
    resources when CPSM compatibility testing goes on.
    However this testing should only be going on for active CMASes
    in the network. It should not be occurring for CMASes that are
    not currently active (in the network.)
    .
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Invalid error and informational         *
    *                      messages may be issued for a terminated *
    *                      CMAS when other CMASes in a CMAS        *
    *                      network start or terminate.             *
    *                                                              *
    *                      Messages seen include, but are not      *
    *                      limited to:                             *
    *                                                              *
    *                        EYUCP0016I This CMAS converts to the  *
    *                                   lower capability of CMAS   *
    *                                   <cmasname>.                *
    *                                                              *
    *                        EYUCP0017E Capability of CMAS         *
    *                                   <cmasname> is not valid    *
    *                                   for this CMAS to connect.  *
    *                                                              *
    *                        EYUCP0018E Resource type mismatch 1   *
    *                                   with CMAS <cmasname> is    *
    *                                   <resname>.                 *
    *                                                              *
    *                      Note that these messages can occur      *
    *                      validly.  However, if the CMAS          *
    *                      identified as <cmasname> is not active  *
    *                      in the CMAS network, then the messages  *
    *                      were issued invalidly.                  *
    ****************************************************************
    * 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 two CMASes connect directly or indirectly, each CMAS passes
    to the other CMAS a list of all CPSM resource tables it manages,
    along with the version of the table that it supports.  The
    partner CMAS then uses that information to create a resource
    table capability matrix for the partner.  This table is anchored
    in the CMAS directory element (CMASDIR) for the partner CMAS,
    and is used to manage resource table conversion between the two
    CMASes.  As other CMASes enter the network, the tables are
    passed to them as part of the network topology (NETTOP) exchange
    that CMASes perform when a CMAS enters the network.
    
    When a CMAS receives this information, either directly from the
    partner CMAS, or from another CMAS as part of NETTOP exchange,
    it performs validation of the compatibility of its matrix with
    the other CMAS.  Compatibility requires that both CMASes be at
    the same version for each table, or that one CMAS can have
    higher or lower versions, but not both higher and lower
    versions.  If the local CMAS has higher versions, then it will
    issue message EYUCP0016I.  If the local CMAS has higher and
    lower versions, then it will issue messages EYUCP0017E and
    EYUCP0018E, and will terminate its connections to the other
    CMASes in the network.
    
    Because all CMASes build the matrix for all other CMASes in the
    network, and pass the information around during NETTOP exchange,
    it is possible that if a CMAS leaves the network, for example to
    apply maintenance that may affect its matrix, other CMASes that
    have been restarted with updated matrix information may have
    conflicts with the old data for the terminated CMAS.  While a
    conflict that causes the CMAS to issue message EYUCP0016I will
    not result in a problem, a conflict that causes messages
    EYUCP0017E and EYUCP0018E will result in the issuing CMAS being
    terminated from the network.  Restarting that CMAS will result
    in the same errors, until the terminated CMAS is restarted and
    its matrix updated by all other CMASes in the network.
    

Problem conclusion

  • The resource table capability matrix is only required while two
    CMASes are connected.  If the matrix of a terminated CMAS is
    passed to other CMASes during NETTOP exchange, it serves no
    purpose other than to possibly cause invalid problems.  So to
    avoid invalid problems, updates have been made to methods
    EYU0CPAG (CPAG) and EYU0CPUC (CPUC), to call method EYU0MOCS
    (MOCS) to delete the local copy of a matrix for a CMAS that has
    left the network.  When the CMAS returns, it will broadcast its
    matrix.  This will ensure that other CMASes in the network will
    only perform validation against a current matrix.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI24737

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    70M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-27

  • Closed date

    2015-01-05

  • Last modified date

    2015-05-20

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

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

    PI29221 UI24208 PI40709 PI40710 PI40711

Modules/Macros

  • EYU0CPAG EYU0CPRI EYU0CPUC
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R70M PSY UI24208

       UP15/01/07 P F501

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:
30 April 2020