IBM Support

PK85169: MESSAGE EYUXU0239E ISSUED USING BATCHREP TO CREATE CSYSDEF / CSYSGRP AND ADDING CICSSYS TO THE GROUP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using BATCHREP to create a a CSYSDEF and then a CSGLCGCS,
    it fails with message:
    .
      EYUXU0293E applid Batch CREATE request fialed - Response
         (EXCEPTION) - Reason (METHOD_FAILED)
    .
    In the trace we see the following exceptions:
      BMWU TAAC XDBM BAS EXCP.      4 BMWUBMSA
      TAAC XLSD XDBM TOP EXCP.     11 TAACBMWU
      MOFB MOMS XDBM DAT EXCP.      2 MAL_FAIL
      MOMS XDBM XDBM DAT EXCP.      8 FEEDBACK
      XDBR XDBM XDBM DAT EXCP.     14 MALERROR
    .
    TAAC is called to add the CSGLCGCS.  It calls BMWU to verify the
    request will not create any inconsistensies.  BMWU calls BMSA
    and BMSA calls TSVS to see if the CICSNAME exists.  Trace point
    id 4 is BMPI_BMSAF_POINT_ID  (CICS system add fail).  The
    BMSA_STATUS is x'03' indicating BMSA_CSYSNAME_NOT_FOUND upon
    return from the TSVS method call.
    
    Additional Keywords:
    KIXREVBDB
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:    When adding a newly created CICS     *
    *                      system (CSYSDEF) to a CSYSGRP using     *
    *                      BATCHREP or the API (CREATE CSGLCGCS),  *
    *                      the CREATE might fail.  API users will  *
    *                      receive:                                *
    *                      .                                       *
    *                           RESPONSE=FAILED,REASON=EXCEPTION   *
    *                      .                                       *
    *                      from the CREATE verb.  BATCHREP streams *
    *                      will return message:                    *
    *                      .                                       *
    *                           EYUXU0219E  Batch CREATE request   *
    *                              failed - Response (EXCEPTION) - *
    *                              Reason (METHOD_FAILED)          *
    ****************************************************************
    * 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 be done at the same time.     *
    ****************************************************************
       CREATE CSYSDEF is a two step process.  First the definition
    is added to the Data Repository.  Then a CPSM Event is generated
    to notify interested components of the new definition.  Not
    until this event is processed by Topology will the structures
    describing the CICS System be defined.  When EYU0TAAC (TAAC -
    Add System Group Link) is invoked, it calls EYU0BMWU (BMWU -
    BAS Update CICS System Group) to confirm that the new definition
    will not result in BAS Inconsistent Set or Inconsistent Scope
    errors.  If Topology has not processed the CREATE event for the
    CSYSDEF yet, this call will return a response and reason of
    EXCEPTION, METHOD_FAILED.  TAAC will propagate this exception to
    the API / BATCHREP caller.
    

Problem conclusion

  •    EYU0BMWU was modified to return STATUS=CSYSNAME_NOT_FOUND
    instead of a response and reason of EXCEPTION, METHOD_FAILED
    if the CICS system for which it was called is not found.
    EYU0TAAC was modified to retry the call to BMWU up to five
    times with a one second delay between tries, if a status of
    CSYSNAME_NOT_FOUND is returned by BMWU, to allow time for
    the preceding CREATE event to be processed by Topology.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK85169

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-22

  • Closed date

    2009-05-04

  • Last modified date

    2009-06-01

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

    PK85144

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

    UK46208

Modules/Macros

  •    EYU0BMWU EYU0TAAC
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK46208

       UP09/05/07 P F905

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

Document Information

Modified date:
01 June 2009