IBM Support

PH50247: EYUXU0218I CMASXXXX BATCH CREATE REQUEST COMPLETE - STATUS(INCONSISTENT_SET) - ASSOCIATED FIELDS RESDESC .

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CPSM Maintenance Point upgraded from CICS TS 5.4 to 6.1.
    The same batchrep process fails with the following message:
    EYUXU0218I CMASxxxx Batch CREATE request complete -
               Status(INCONSISTENT_SET) - Associated fields RESDESC
                                                                   .
    There appeared to be inconsistencies in some DB2EDEF resources.
    There were 2 separate versions of the resources being built,
    with different plan names, targeting different regions/groups,
    so this shouldn't have been flagged as an error. However this
    was seen as an error by the code and the message was issued.
    

Local fix

  • The BAS definitions were manually rearranged in a different
    order and this then worked successfully.
    .
    Additional Symptoms:
    .
    This can manifest itself as an AICA in transaction XDNR, with a
    dump title looking similar to this:
    .
    EYU9XLRV Dump,cmasname,applid,sysid,CMAS,XDNR,0012345,
             AICA,EYU0XCLR,mm/dd/yyyy,hh:mm:ss
    .
    And a method stack list in the job output reported in EYUXL0905E
    messages that looks like this:
    .
    +EYUXL0905E Methods=XCLR,BMZ6,BMZ3,BMXR,BACR,XLSD,XLSI,MOMS,
    +EYUXL0905E Methods=XDH6,XDNR,XLOP
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM Users                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR addresses several problems    *
    *                      discovered in the CICSPlex SM BAS       *
    *                      component. These issues relate          *
    *                      to the management of resources through  *
    *                      RESINDSC, or RASINDSC relationships:    *
    *                                                              *
    *                      - Installing a single resource into     *
    *                      different (non-conflicting) target      *
    *                      scopes, using two separate resource     *
    *                      assignments specifying different        *
    *                      override strings (ORSTRING), may        *
    *                      produce INCONSISTENT_SET.               *
    *                      This occurs at CPSM V6.1.               *
    *                                                              *
    *                      - You attempt to add a Resource Group   *
    *                      to a Resource Description (RESINDSC).   *
    *                      The resource group contains one or      *
    *                      more CONNDEF or SESSDEF resources.      *
    *                      Alternatively you add a CONNDEF or      *
    *                      SESSDEF to a resource group which is    *
    *                      installed by a Resource Description     *
    *                      (RESINDSC).                             *
    *                      The API returns INCONSISTENT_SET at     *
    *                      V6.1, or at earlier releases may fail   *
    *                      with Response (EXCEPTION)               *
    *                      Reason (METHOD_FAILED).                 *
    *                      This may cause a dump in the CMAS,      *
    *                      either when the request fails or when   *
    *                      the CMAS is subsequently restarted.     *
    *                                                              *
    *                      - You remove the association between a  *
    *                      Resource Group and a Resource           *
    *                      Description (RESINDESC). The group      *
    *                      contains one or more SESSDEF resources. *
    *                      The effect is that all connection       *
    *                      resources are removed from the BAS      *
    *                      install list, not just those CONNDEFs   *
    *                      which where matched by the SESSDEF(s)   *
    *                      being removed.                          *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF which resolves        *
    *                 this APAR, all CMAS regions should be        *
    *                 restarted. The restarts may occur at any     *
    *                 time and in any order.                       *
    ****************************************************************
      The CICSPlex SM BAS component maintains an in-memory list
    detailing all resources which should be installed by CPSM as
    a result of an association to a Resource Description.
    This is the BAS Install List. Each list element in this list
    is known as a BRSE. When a resource is added to the BAS Install
    List, for example through the creation of a new RESINDSC
    relationship, this list is used to perform inconsistency
    checking.
    
    Several problems with this processing have been identified,
    and fixes will be provided at the following supported releases
    of CICSPlex SM:
      APAR PH50247: V5.4, V5.5, V5.6
      APAR PH48865: V6.1
    
    
    
    - Installing a single resource into different (non-conflicting)
    target scopes, using two separate resource assignments
    specifying different override strings (ORSTRING), may
    produce INCONSISTENT_SET.
    This occurs at CPSM V6.1 as a result of increased inconsistency
    checking. The configuration is incorrectly detected as being
    inconsistent.
    
    
    - You attempt to add a Resource Group to a Resource Description
    (RESINDSC). The resource group contains one or more CONNDEF or
    SESSDEF resources.
    Alternatively you add a CONNDEF or SESSDEF to a resource group
    which is already installed by a Resource Description (RESINDSC).
    The API returns INCONSISTENT_SET at V6.1, or at earlier releases
    may fail with Response (EXCEPTION) Reason (METHOD_FAILED).
    
    This may cause a dump in the CMAS, either when the request
    fails or when the CMAS is subsequently restarted.
    @EYUXZ0910I applid EYU0XZPT Dump,jobname,cpsmname,system,CMAS,
                XDBM,tasknum,TRAC,EYU0BMRA,date,time.
    
    
    In the case where this occurs during CMAS initialisation,
    the BAS component will fail to initialise.
    @EYUXZ0910I applid EYU0XZPT Dump,jobname,cpsmname,system,CMAS,
                XLEV,tasknum,TRAC,EYU0BMRA,date,time.
    +EYUBI0102E applid BAS initialization for CICSplex p has failed.
    
    This occurs when the definitions being added would create a
    logical inconsistency, as one of more of the CONNDEF/SESSDEF
    resource being added to the BAS Install List would be in
    conflict with other elements in the list, but that
    inconsistency cannot be detected as inconsistency checking
    can be applied only to CICS systems, and not system groups.
    
    The dump is the result of key collisions occurring within the
    BAS install list, and will occur only when the CICS system group
    (CSYSGRP) used as a target scope for the BAS Resource
    Description does not contain any CICS system.
    If CICS systems are present in the group then INCONSISTENT_SET
    is returned as expected.
    
    
    - You remove the association between a Resource Group and a
    Resource Description (RESINDESC). The group contains one or
    more SESSDEF resources.
    The effect is that all connection resources are removed from
    the BAS install list, not just those CONNDEFs which where
    matched by the SESSDEF(s) being removed.
    
    Only the in-memory BAS Install List is damaged by this process;
    the data repository is modified correctly.
    The list is rebuilt from the data repository when the CMAS
    next restarts.
    

Problem conclusion

  • The issues described have been corrected through updates to
    the following CICSPlex SM modules:
    
    - EYU0BMRA (BMRA) has been corrected at V6.1 such that
    inconsistency checking will be performed only on BRSE entries
    representing CICS systems, and not the internal BRSE entries
    representing CICS system groups. At V5.4, V5.5, and V5.6,
    BMRA is updated to correct a logic error when searching the
    BAS resource install list.
    
    - EYU0BMCP (BMCP) has been updated to correct a logic error
    which led to inconsistent cache list keys for BRSE elements
    representing CONNDEF and SESSDEF elements.
    
    - EYU0BMZ3 (BMZ3) has been updated in the same way as BMCP.
    
    - EYU0BMZ6 (BMZ6) has been updated to correct a logic error
    in building the generic key used to remove elements from the
    BAS resource install cache list. This ensures that only the
    intended elements are removed from the in-memory list.
    
    - EYU0DVBF (DVBF) has been updated with improvements to the
    VERBX EYU9Dnnn 'BAS' IPCS dump formatting routine.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH50247

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    10M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-10-18

  • Closed date

    2022-11-16

  • Last modified date

    2023-11-10

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

    PH48865

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

    UI83302 UI83303 UI83304

Modules/Macros

  • EYU0BMCP EYU0BMRA EYU0BMZ3 EYU0BMZ6 EYU0DVBF
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R10M PSY UI83304

       UP22/11/22 P F211

  • R20M PSY UI83303

       UP22/11/18 P F211

  • R30M PSY UI83302

       UP22/11/18 P F211

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

Document Information

Modified date:
10 November 2023