IBM Support

PH00907: CICS MAS REGION FAILS TO CONNECT TO CMAS. EYUNL0906E IN MAS JOB LOG DURING STARTUP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Your CICS region starts and begins to connect to the CPSM CMAS.
    The messages seem to indicate that things are going well, but
    you quickly see a message similar to the following:
    .
    EYUNL0906E masname The CMAS has initiated a shutdown
               of the MAS agent. See the CMAS job log for
               additional information.
    .
    Over in the EYULOG for the CMAS that this MAS was trying to
    connect to, you see a sequence of messages similar to the
    following:
    .
    EYUXL0006I masname  BAS initialization has started.
    EYUTS0001I cmasname Topology Connect for masname Initiated -
                        APPLID(masname) CICSplex(plexname).
    EYUXD0002I cmasname Delete CONTEXT(plexname)
                        MAJOR_ID(resourceid)
                        MAJOR_NAME(resourcename) MAJOR_VER(1)
                        MINOR_ID(NONE) MINOR_NAME(NONE)
                        MINOR_VER(NONE) By User(username) On
                        System(cmasjobname) Date(date) Time(time).
    EYUTS0002E cmasname Topology Connect for masname Failed -
                        APPLID(masname) CICSplex(plexname).
    .
    An SVC dump is not produced, however an exception trace is
    written in the CMAS. Looking at the trace, you will see the
    problem during Topology CONNECT reflected in the following:
    .
    Task  Mtd  Prev Tran Obj Level Pt-ID  Debug   UOW
    12345 BMES TSCI TSSC BAS Excp      3 BMESXDGR CPSM
    12345 TSCI TSSC TSSC TOP Excp      2 TSCIXQDQ CPSM
    12345 TSSC XLOP TSSC TOP Excp      4 TSSCTSCI CPSM
    .
    The first failure, with Debug Text of BMESXDGR, is a call from
    method BMES to XDGR to read a record from the EYUDREP
    repository. This is to build the Install Queue during the
    CONNECT process for the MAS. In the trace you can see that
    method BMES gets RESP=2, RSN=3. This is Exception Point #3,
    corresponding to BMPI_XDGR_NRF, for "Repository Get no record
    found".
    .
    There is a small timing window that exists where an
    administrator may be deleting a resource from CPSM BAS at the
    same time that a MAS is CONNECTing to the CMAS. During that
    window of time, the in-storage list of resources to be
    installed by BAS into the MAS may contain a resource that has
    already been deleted from the CMAS EYUDREP.
    .
    .
    Additional Symptom(s) Search Keyword(s): KIXREVSVR
    

Local fix

  • Restart the MAS or try using COLM transaction in the MAS to
    restart the MAS agent.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of CPSM V5R2M0, V5R3M0 and V5R4M0. *
    ****************************************************************
    * PROBLEM DESCRIPTION: When BAS resource management is used,   *
    *                      MAS regions will install CICS resources *
    *                      during startup initialization. If a     *
    *                      CICS resource definition is deleted in  *
    *                      the data repository during the MAS      *
    *                      installation, the MAS may fail to       *
    *                      initialize, causing the MAS agent to    *
    *                      shut down.                              *
    *                      Similar information may appear in the   *
    *                      logs of CMAS and MAS:                   *
    *                      EYUNL0906E masname The CMAS has         *
    *                                 initiated a shutdown of the  *
    *                                 MAS agent. See the CMAS job  *
    *                                 log for additional           *
    *                                 information.                 *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be recycled to pick up *
    *                 the new code.  Note that the restarts do not *
    *                 need to occur at the same time.              *
    ****************************************************************
    During CMAS initialization, a CMAS generates a list of resources
    that will be installed during the initialization of each MAS. If
    a resource is deleted from the data repository, the resource
    list is updated accordingly.
    
    During MAS initialization, the CMAS reads the resource list from
    the data space to obtain a list of resources to be installed. It
    then reads the detailed resource definition from the data
    repository, and sends it to the MAS for resource installation.
    
    In the reported problem, a resource was deleted from the data
    repository, but a MAS initialized before the resource list (held
    in the BAS data space) could be updated. The CMAS was unable to
    obtain the complete resource definition from the data
    repository, which caused MAS initialization to fail, and the MAS
    agent to automatically shut down.
    

Problem conclusion

  • CICSPlex SM has been updated so that MAS initialization will
    continue. Other resources will be installed; the MAS agent will
    not be shut down.
    
    A new message, EYUBM0349W, will be written to the CMAS EYULOG to
    aid debugging. The message indicates which resource could not be
    read from the data repository.
    
    The CICSPlex SM Knowledge Center will be updated with new
    message:
    
    EYUBM0349W The deftype (defname) record for CICSplex(plexname)
               cannot be found in Data Repository.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH00907

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    90M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-25

  • Closed date

    2018-10-19

  • 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:

    UI59246 UI59247 UI59248

Modules/Macros

  • EYU0BMES EYUMCBMC EYUMCBME EYUMCBMK
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R00M PSY UI59247

       UP18/10/20 P F810

  • R10M PSY UI59248

       UP18/10/20 P F810

  • R90M PSY UI59246

       UP18/10/23 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.2","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.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 November 2018