IBM Support

PK90603: EYUWM0401E WORKLOAD SPECIFICATION FAILED TO INSTALL FOR TOR JOINXCLA_DUPLICATE_KEY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You recycle your regions, bringing the MP CMAS down last, but
    the TOR fails to join the workload.  You receive the following
    message in your CMAS:
    
      EYUWM0401E Workload type (name) failed to install for context
      (plexname) - direction initiated by join of TOR
    
    The workload build files when XCLA returns XCLA_STATUS = 02
    (XCLA_DUPLICATE_KEY) to WMTJ.  The trace shows the following
    entries:
    
         task# WMTJ WMWC WMWC WLM EXCP.      8 WMTJXCLA
         task# WMWC XLOP WMWC WLM EXCP.     17 WMWCWMTJ
    
    where
       WMWC exception 17 means 'WLM TOR Join failed'
       WMTJ exception 8  means 'Add entry to cache list error'
    
    The workload build is failing because CPSM thinks that the TOR
    which we are building the workload has two IP connections with
    the same name.
    
    
    Additional Symptom(s) and Keyword(s)
    KIXREVRBD
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: If an IP connection with a name that    *
    *                      has a length greater than four          *
    *                      characters is installed into a CPSM     *
    *                      routing region, various errors may      *
    *                      occur:                                  *
    *                                                              *
    *                      -  if the connection is installed       *
    *                         before the routing region connects   *
    *                         to its CMAS, then the TOR join       *
    *                         processing may fail.                 *
    *                                                              *
    *                         If this failure occurs and the       *
    *                         routing region in question is the    *
    *                         first started under that CMAS for    *
    *                         the specific workload, then the      *
    *                         workload build process will also     *
    *                         fail, and the following message will *
    *                         be issued:                           *
    *                                                              *
    *                           EYUWM0401E Workload Specification  *
    *                           (<wlmspec>) failed to install for  *
    *                           context(<plexname>) - initiated by *
    *                           join of router (<torname>).        *
    *                                                              *
    *                      -  if the connection is installed after *
    *                         the routing region connects to its   *
    *                         CMAS, and the first four characters  *
    *                         of the IP connection match the first *
    *                         four characters of an existing       *
    *                         connection, then the existing        *
    *                         connection element may be modified   *
    *                         invalidly.  This can result in       *
    *                         invalid routing.                     *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be restarted.  Note    *
    *                 that the restarts do not need to occur at    *
    *                 the same time.                               *
    ****************************************************************
    When a TOR join occurs for a CPSM routing region, method
    EYU0WMTJ (WMTJ) builds a list that contains an element for each
    connection installed in the routing region.  If after the TOR
    join completes, a connection is installed, method EYU0WMEV
    (WMEV) is notified of the install, and calls method EYU0WMTU
    (WMTU) to update the list for the routing region.
    
    Since CPSM WLM is only concerned with links between the routing
    region and other CICS regions, the list only allows for a four
    character connection name.  If the connection name is greater
    than four characters, for example, if it is an IP connection to
    a CTG region, then WMTJ and WMEV will truncate the name to the
    first four characters.  If this truncated name clashes with an
    existing element in the list, the errors described above may
    occur.
    

Problem conclusion

  • Since all connections between CICS systems, regardless of
    whether they are MRO, LU62 or IP, cannot have a name greater
    than four characters, WMTJ and WMEV have been updated to ignore
    any connection that has a name greater than four characters when
    building (WMTJ) or updating (WMEV) the connection list for a
    CPSM routing region.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK90603

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    60M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-06

  • Closed date

    2009-07-14

  • Last modified date

    2009-08-03

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

    PK90227

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

    UK48357

Modules/Macros

  • EYU0WMEV EYU0WMTJ
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UK48357

       UP09/07/17 P F907

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

Document Information

Modified date:
03 August 2009