PM69436: CPSM WORKLOAD INCORRECTLY ROUTING AS IF LINK-NEUTRAL ALGORITHMS SELECTED IN MIXED CPSM RELEASE ENVIRONMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have a CPSM Workload in a mixed-release environment (4.2
  CMASes and pre-4.2 CMASes.) The WLMSPEC definition indicates
  that the routing algorithm should be QUEUE or GOAL. You also
  have Transaction Groups (TRANGRP) defined as part of this
  workload.
  .
  Your 4.2 CMAS initializes and imports an existing workload from
  a pre-4.2 CMAS. You notice that routing regions connected to the
  4.2 CMAS are routing as if the algorithm was one of the
  Link-Neutral algorithms, LNQUEUE or LNGOAL.
  .
  On the Active Workload Transaction Groups view in the WUI
  (EYUSTARTWLMATGRP.TABULAR) you notice the 'Algorithm type' field
  (ALGTYPE) is set to 'N_a'.
  .
  The 4.2 CMAS has imported the active workload definition from a
  CMAS that is at a level that does not know about the TRANGRP
  algorithm field.
  .
  Additional Symptoms/Keywords
  KIXREVEPH
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V4R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:    You have a CPSM Workload in a mixed  *
  *                      release environment (V4.2 CMASes and    *
  *                      pre-V4.2 CMASes.) The WLMSPEC specifies *
  *                      that the routing algorithm should be    *
  *                      QUEUE or GOAL.  You also have several   *
  *                      Transaction Groups (TRANGRP) defined    *
  *                      as part of this workload.               *
  *                         Your V4.2 CMAS initializes and when  *
  *                      the first TOR connects, it imports an   *
  *                      existing workload from a pre-V4.2 CMAS. *
  *                      You notice that routing regions which   *
  *                      connect to the V4.2 CMAS are routing as *
  *                      if the algorithm was one of the Link-   *
  *                      Neutral algorithms, LNQUEUE or LNGOAL.  *
  *                         In the "Active Workload Transaction" *
  *                      Groups view in the WUI:                 *
  *                           (EYUSTARTWLMATGRP.TABULAR)         *
  *                      you notice the 'Algorithm type' field   *
  *                      (ALGTYPE) is set to 'N_a'.              *
  *                      .                                       *
  *                         In the "Active target regions"       *
  *                           (EYUSTARTWLMATARG.TABULAR)         *
  *                      and "Active workload target distri-     *
  *                      bution factors"                         *
  *                           (EYUSTARTWLMAWAOR.TABULAR2)        *
  *                      views in the WUI, you notice that the   *
  *                      field 'WLM routing weight for region'   *
  *                      (ROUTEWGHT) displays "1" for all        *
  *                      healthy AORs, making it impossible to   *
  *                      see the effect of transaction load on   *
  *                      workload routing.                       *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes executing V4.2 of CPSM      *
  *                 must be recycled to pick up the new code.    *
  *                 Note that regions do not need to be shut     *
  *                 down and restarted at the same time.         *
  ****************************************************************
     The ability to specify a routing algorithm for each TRANGRP
  was introduced in V4.2 of CPSM.  Prior to this release, the
  algorithm type was not stored in the active TRANGRP descriptor
  (WTGD).  When a CMAS executing V4.2 of CPSM imports an active
  workload from a CMAS that is at a level in which the algorithm
  cannot be specified in the TRANGRP, the algorithm type in the
  WTGD will be null, and will be displayed as "N_a" in views in
  the EYUSTARTWLMATGRP viewset.  This might result in undesired
  routing behavior.
     Modules EYU0WABA (WABA - Browse WLMAWAOR Resources) and
  EYU0WABB (WABB - Browse WLMATARG Resources) calculate a weight
  for each target region as a floating point value which is con-
  verted to an integer for display by truncating.  The weight for
  most healthy regions is between 1.000 and 1.999 with the exact
  value depending on the ratio of actual load to MAXTASK limit.
  When truncated these values all display as "1", making it im-
  possible to see the effect of transaction load on routing weight
  in the WUI views.
  

Problem conclusion

•    Module EYU0WMQU (WMQU - Updated Queried Workload) was
  updated to test the incoming values for initial and actual
  routing algorithm, and if null, to set the values in the new
  TRANGRP Descriptor to INHERIT.
     Modules EYU0WABA and EYU0WABB were modified to scale the
  calculated weight values by 1000 before truncating for display.
  Since the weight values are significant only as they can be
  compared to the weights for other regions, this allows the
  effect of transaction load to routing weight to be seen.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  UK80815

Modules/Macros

•    EYU0WABA EYU0WABB EYU0WMQU
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R70M PSY UK80815

     UP12/08/04 P F208

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.