IBM Support

PM71302: EYUXU0219E IN CPSM BATCHREP. CREATE OF CGSLCGCS FOR NEW CSYSDEF FAILS, BUT IS SUCCESSFUL ON SUBSEQUENT ATTEMPT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You run a BATCHREP request with many CPSM CREATE commands. You
    create a Group-in-Group definition, then create CSYSDEF,
    followed by a request to add the CSYSDEF to the new group (a
    CGSLCGCS definition.) The request to create the CGSLCGCS
    definition fails with
    .
    EYUXU0219E Batch CREATE request failed - Response (EXCEPTION) -
               Reason (METHOD_FAILED).
    EYUXU0226E A previous error has caused incomplete processing
               to occur.
    .
    If you resubmit the BATCHREP request, starting with the failed
    CREATE command and not making any other changes, the request
    will process successfully. AUX trace from the connecting CMAS
    will show trace entries similar to
    .
    TASK  MTD  PREV TRAN OBJ LEVL  PT-ID   DEBUG
    12345 XSLA XSRA XDBM SRV EXCP       3 RESIHELD
    12345 XSRA XDGT XDBM SRV EXCP       6 XSLAFAIL
    12345 XSLA XSRA XDBM SRV EXCP       3 RESIHELD
    12345 XSRA XDGT XDBM SRV EXCP       6 XSLAFAIL
    12345 TAAC XLSD XDBM TOP EXCP      12 MOS TAAC
    12345 MOFB MOMS XDBM DAT EXCP       2 MAL_FAIL
    12345 MOMS XDBM XDBM DAT EXCP       8 FEEDBACK
    12345 XDBR XDBM XDBM DAT EXCP      14 MALERROR
    .
    The RESIHELD and XSLAFAIL trace entries are expected in certain
    instances, and are not relevant to this issue.
    .
    .
    Another problem can occur if your BATCHREP commands include the
    following sequence of commands:
    .
    CREATE CPLEXDEF CICSPLEX(mynewplex) ... ;
    CONTEXT mynewplex;
    CREATE xxxxxxxx  ..... ;
    .
    If a new CICSPlex is created, then the context set to that new
    CICSPlex, followed by a CREATE command for a new resource, the
    CREATE of the new resource may fail with the following:
    .
    EYUXU0219E Batch CREATE request failed - Response (INVALID) -
               Reason (INVALID_CONTEXT).
    .
    AUX trace from the connecting CMAS will show trace entries
    similar to:
    .
    TASK  MTD  PREV TRAN OBJ LEVL  PT-ID   DEBUG
    12345 TSFD CPAI XDBM TOP EXCP       2 PLEXUNKN
    12345 XSLA XSRA XDBM SRV EXCP       3 RESIHELD
    12345 XSRA XDGT XDBM SRV EXCP       6 XSLAFAIL
    12345 BACS XLSD XDBM BAS EXCP       0
    12345 XDBR XDBM XDBM DAT EXCP      14 MALERROR
    .
    Additional Symptoms/Keywords:
    KIXREVxxx
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users      *
    ****************************************************************
    * PROBLEM DESCRIPTION:    You execute a stream of BATCHREP     *
    *                      commands to create a new CICSplex and   *
    *                      define related resources.  The BATCHREP *
    *                      stream begins with the following com-   *
    *                      mands:                                  *
    *                                                              *
    *                         CONTEXT mycmas ;                     *
    *                         CREATE CPLEXDEF CICSPLEX(newplex) ;  *
    *                         CONTEXT newplex ;                    *
    *                         CREATE xxxxxxxx(newrsrc) ..... ;     *
    *                                                              *
    *                      The CREATE of the new resource fails    *
    *                      with the following messages:            *
    *                                                              *
    *                           EYUXU0219E Batch CREATE request    *
    *                              failed - Response (INVALID) -   *
    *                              Reason (INVALID_CONTEXT).       *
    *                           EYUXU0226E A previous error has    *
    *                              caused incomplete processing    *
    *                              to occur.                       *
    *                                                              *
    *                         You create two new CSYSGRP defini-   *
    *                      tions and a Group-in-Group (CGSLCGCG)   *
    *                      link definition, then create a new      *
    *                      CSYSDEF, and attempt to create a new    *
    *                      System-in-Group (CGSLCGCS) definition   *
    *                      adding the CSYSDEF to the inner group.  *
    *                      The CREATE command for the CGSLCGCS     *
    *                      definition fails with the following     *
    *                      messages:                               *
    *                                                              *
    *                           EYUXU0219E Batch CREATE request    *
    *                              failed - Response (EXCEPTION) - *
    *                              Reason (METHOD_FAILED).         *
    *                           EYUXU0226E A previous error has    *
    *                              caused incomplete processing    *
    *                              to occur.                       *
    *                                                              *
    *                         If you resubmit the BATCHREP stream  *
    *                      starting with the failed CREATE command *
    *                      and not making any other changes, the   *
    *                      failing request completes successfully. *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be recycled to pick    *
    *                 up the code changes.  Note that CMASes do    *
    *                 not need to be brought down and restarted    *
    *                 at the same time.                            *
    ****************************************************************
       When a new CICSplex or a Topology resource like a CYCSDEF or
    CSYSGRP is created, the definition is added to the CMAS's Data
    repository.  A notification is then sent to all CPSM components
    to allow necessary updates to be made to reflect the new defini-
    tion.  When a batched update utility like BATCHREP or EYU9XDBT
    creates new definitions, asynchronous processing triggered by a
    creation of a new definition may not be completed before the
    next command is processed.  This can result in failures because
    the creation or update of internal data structures to reflect
    the previous change may not be complete.
       If a new CPLEXDEF is created via BATCHREP and the CONTEXT is
    set to the new CICSplex, asynchronous updates to Topology data
    structures may not be complete when the next CREATE command is
    executed.  Module EYU0XDBM (XDBM - BATCHREP Command Processor)
    calls methods to confirm that the new context has been defined
    to the Communications component (COM), but does not validate the
    target CICSplex with Topology (TOP).  This problem may also be
    observed in batch API programs in which a CPLEXDEF resource is
    created, followed immediately by a CONNECT or QUALIFY command
    setting the thread context to the new CICSplex.
       If a new topology resource (CSYSDEF or CSYSGRP) is created,
    then a CREATE of a CSGLCGCS or CSGLCGCG is attempted, to add
    it to an existing CICS system group, module EYU0TAAC (TAAC -
    Create System Group Link Definition) might call EYU0BMWU (BMWU -
    BAS Management Update CICS Group) to perform BAS inconsistency
    checking. TAAC already contains code to repeat the call to BMWU
    after a one second delay if it is called from a batch process
    (that is, BATCHREP or a batch API program) and BMWU returned a
    status indicating that the CICS system being added was not
    found.  However TAAC may call itself recursively when a CICS
    system or group is being added to a member of a nested Group-
    in-Group. The flag identifying the current execution as having
    been called for a batch process is not propagated to the recur-
    sive execution, so the call to BMWU is not repeated if BMWU's
    returned status indicates that the target CICS system was not
    found.
    

Problem conclusion

  •    Module EYU0XDBM was modified to call EYU0TSFD (TSFD - Return
    Topology Descriptor) to retrieve the CICSplex Descriptor (CPDB)
    for the target CICSplex.  If TSFD returns STATUS=UNKNOWN_CONTEXT
    the call to TSFD will be repeated up to five times after a one
    second delay, to allow asynchronous processing to complete.
       Module EYU0XDF1 (XDF1 - API Connect Processor) already calls
    modules EYU0TSCV (TSCV - Topology Validate Context) and EYU0TSVS
    (TSVS - Topology Validate Scope), to check the passed CONTEXT
    and SCOPE, but was modified to retry up to five times after a
    one second delay, if the request was initiated by a batch API
    program, and the context or scope was not found.
       Module EYU0XDQ1 (XDQ1 - API Qualify Processor) already calls
    modules EYU0TSCV (TSCV - Topology Validate Context) and EYU0TSVS
    (TSVS - Topology Validate Scope), to check the passed CONTEXT
    and SCOPE.  XDQ1 was modified to call modules EYU0CPLP (CPLP -
    Connection Services Locate CICSplex) and EYU0CPLC (CPLC - Con-
    nection Services Locate CMAS) to insure that the passed CONTEXT
    is defined, and retry calls to TSCV or TSVS up to five times
    after a one second delay, if the request was initiated by a
    batch API program, and the context or scope was not found.
       Module EYU0TAAC was updated to propagate the flag identifying
    a batch process on recursive calls.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • ž**** PE12/11/15 FIX IN ERROR. SEE APAR PM77168  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PM71302

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    70M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-21

  • Closed date

    2012-10-25

  • Last modified date

    2012-11-16

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

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

    UK82956 UK82957

Modules/Macros

  •    EYU0TAAC EYU0XDBM EYU0XDF1 EYU0XDQ1
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UK82956

       UP12/10/26 P F210

  • R70M PSY UK82957

       UP12/10/26 P F210

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

Document Information

Modified date:
16 November 2012