IBM Support

PH04179: EYUCP0022E EYUXD0031E AND EYUXD0031E IN CMAS AFTER PTF UI57267 APPLIED. SMP HOLD ACTION DATA MISSING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CPSM PTF UI57267 updated the RULES base table. When a base
    table is updated, CMASes that are a Maintenance Point CMAS must
    be updated first. Failure to do so will result in EYUCP0022E
    and EYUXD0031E error messages. There will also be EYUXD0031E
    messages stating that the RULE table has a mismatch between the
    local CMAS and the REMOTE CMAS that it was trying to sync with.
    The CMAS will be isolated.
    .
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

  • Ensure that any CMAS that acts as a Maintenance Point CMAS gets
    the PTF first
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V5R4M0 Users                 *
    *                 with UI57267 applied.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: MASes may fail to connect to CMASes     *
    *                      and CMASes may fail to connect to       *
    *                      other CMASes after applying             *
    *                      the following PTF :                     *
    *                        V5R4M0 - UI57267                      *
    *                                                              *
    *                                                              *
    *                      The MAS-CMAS connection problems may    *
    *                      be accompanied by the following         *
    *                      message IDs:                            *
    *                                                              *
    *                       - in the CMAS joblog:                  *
    *                      EYUXD0031E, EYUCL0130E, EYUCL0131E,     *
    *                      EYUCL0107E                              *
    *                                                              *
    *                       - in the MAS joblog:                   *
    *                      EYUCL0112E, EYUCL0124E, EYUCL0101E      *
    *                                                              *
    *                                                              *
    *                      The CMAS-CMAS connection problems only  *
    *                      occur when one CMAS is a maintenance    *
    *                      point (MP) CMAS, and may be             *
    *                      accompanied by the following message    *
    *                      IDs:                                    *
    *                                                              *
    *                       - in the MP CMAS joblog:               *
    *                      EYUXD0031E, EYUCP0022E                  *
    *                                                              *
    *                       - in the non-MP CMAS joblog:           *
    *                      EYUCP0022E, EYUXZ0910I, EYUCP0033I,     *
    *                      EYUCP0011E, EYUCP0205S                  *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes and MASes, including MASes  *
    *                 running as WUI servers, must be recycled to  *
    *                 pick up the new code.                        *
    *                                                              *
    *                 The restarts need not be performed at the    *
    *                 same time, however if systems are not        *
    *                 restarted at the same time, the following    *
    *                 rules apply:                                 *
    *                                                              *
    *                 - Maintenance Point (MP) CMASes must be      *
    *                   restarted with the updated code before     *
    *                   non-MP CMASes.                             *
    *                                                              *
    *                 - If you have more than one MP CMAS and any  *
    *                   of those MP CMASes are connected directly  *
    *                   or indirectly, then those MP CMASes must   *
    *                   be restarted with the updated code at the  *
    *                   same time.                                 *
    *                                                              *
    *                 - Before a MAS, regardless of whether it is  *
    *                   running as a WUI server, is restarted with *
    *                   the updated code, the CMAS to which the    *
    *                   MAS connects must be running with the      *
    *                   updated code.                              *
    *                                                              *
    *                 Additionally, all API programs that access   *
    *                 the RULE resource table should be            *
    *                 reassembled or recompiled pointing to the    *
    *                 libraries updated by the PTF that resolves   *
    *                 this APAR.                                   *
    ****************************************************************
    The PTF mentioned in the problem description above, made a
    change to the RULE resource table.  The change requires that
    CMASes and MASes, including MASes running as WUI servers, be
    restarted with the updated code in a specific order, but the
    APAR Recommendations did not document this, and ACT HOLD data
    was not included in the PTF to indicate this.
    
    As a result of the above, errors can occur when connection
    attempts are made between CMASes and MASes (including MASes
    running as WUI servers) or between different CMASes.
    
    
    In the MAS-CMAS case, you may see the following messages:
    
     - in the CMAS joblog:
    
     EYUXD0031E Capability mismatch (HIGH) for table 215/RULE
                (Service=<svclvl>) Local=<val>: Remote=<val>.
    
     EYUCL0130E Capability of MAS <masnm> is not lower or equal.
    
     EYUCL0131E Resource type mismatch 1 with MAS <masnm> is RULE.
    
     EYUCL0107E ESSS ICT attach to <masnm> failed, check capability
                failed.
    
     - in the MAS joblog:
    
     EYUCL0112E Protocol Services initialization unable to
                perform ICT Attach.
    
     EYUCL0124E A failure occurred while attempting to connect
                to CMAS <cmasnm>.
    
     EYUCL0101E Protocol Services initialization failed.
    
    
    
    In the CMAS-CMAS case, the problem occurs when the two CMASs
    are at CPSM V5R4M0, and if one CMAS is a maintenance
    point (MP) CMAS for a CICSplex, and the partner CMAS is a
    non-MP CMAS for the same CICSplex.  The connection problems
    may be accompanied by the following messages:
    
     - in the MP CMAS joblog:
    
     EYUXD0031E Capability mismatch (HIGH) for table 215/RULE
                (Service=<svclvl>) Local=<val> : Remote=<val>.
    
     EYUCP0022E Maintenance Point for CICSplex <plxnm> on CMAS
                <mpcmas> has a lower capability than CMAS
                <nonmpcmas>. CMAS <nonmpcmas> will be
                isolated from the CICSplex.
    
     - in the non-MP CMAS joblog:
    
     EYUCP0022E Maintenance Point for CICSplex <plxnm> on CMAS
                <mpcmas> has a lower capability than CMAS
                <nonmpcmas>.  CMAS <nonmpcmas> will be
                isolated from the CICSplex.
    
     EYUXZ0910I EYU0XZSD Dump,<jobname>,<cmasname>,<lparid>,CMAS,
                XLST,<tasknum>,TRAC,EYU0CPRL,<date>,<time>
    
     EYUCP0033I Disconnect requested for CMAS <mpcmas>.  Reason:
                CMAS isolated.
    
     EYUCP0011E Repository synchronization failed for one or more
                CICSplexes. This CMAS is being isolated at the
                request of CMAS (<mpcmas>).
    
     EYUCP0205S Repository Synchronization with CMAS <mpcmas>
                failed.
    

Problem conclusion

  • To correct the possible connection problems:
    
    -  An APAR Recommendation and ACT HOLD data have been added to
       this APAR, to document the correct method of restarting
       regions after applying the PTFs that resolve this APAR.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH04179

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    10M

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-17

  • Closed date

    2018-10-26

  • Last modified date

    2018-11-01

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

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

    UI59350

Modules/Macros

  • EYUA0215 EYUC0215 EYUL0215 EYUP0215 EYUT0215 EYUY0215
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R10M PSY UI59350

       UP18/10/27 P F810 {

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.4","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.4","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 November 2018