PI17157: WORKLOAD TO BE DISTRIBUTED FROM AOR TO ALL AVAILABLE TARGETS IN AORSCOPE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have set up CICSPlex WLM from a TOR to a set of AORs.  When
  transaction ABCD is started in the TOR, it is to be routed to
  any one of the AORs in the AORSCOPE.  If the AOR is a routing
  region, when transaction ABCD is started in the AOR, it is also
  to be routed to any one of the AORs in the AORSCOPE, including
  the local AOR.
  .
  Due to performance issues it is required that a transaction is
  started more evenly across the AORs.  Currently it is executing
  in one AOR (the local AOR) at a time.
  .
  Additional Symptom(s) Search Keyword(s): KIXREVGJT
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V4R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the LNQUEUE or LNGOAL algorithm is *
  *                      used for the workload routing, CPSM     *
  *                      currently doesn't consider the type of  *
  *                      connection between routing region and   *
  *                      target region. However, CPSM will favor *
  *                      running the workload locally if the     *
  *                      routing region is a member of the       *
  *                      target regions (AORSCOPE).              *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all MASes must be recycled to pick up  *
  *                 the new code. Note that regions do not need  *
  *                 to be brought down and restarted at the same *
  *                 time.                                        *
  ****************************************************************
  Method EYU0WNAL (WNAL) is called to calculate the weight for
  each target region, based on the current algorithm, and to
  store the weight in the region's scope vector element.
  
  If QUEUE or GOAL algorithm is used, WNAL currently calculates
  the link weight based on:
  
      - The type of connection between the routing region and
        the target region.
  
      - The current link status, such as: Active, Down etc.
  
  If LNQUEUE or LNGOAL algorithm is used, WNAL won't consider
  the connection type between the routing region and the target
  region, and the calculation is based on:
  
      - The current link status
  
  The link weight for the target regions are the same if their
  current link status have no difference. However, if the routing
  region is also a member of target regions (AORSCOPE), the weight
  for the region is less than other target regions. As a result,
  CPSM choose to run the workload locally.
  

Problem conclusion

• Method WNAL has been updated to set the same link weight for
  all the target regions in the AORSCOPE, when algorithm LNQUEUE
  or LNGOAL is being used.
  

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:

  PI20302 UI19562

Modules/Macros

• CJA0WNAL CJB0WNAL CJC0WNAL EYU0WNAL
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R70M PSY UI19562

     UP14/07/22 P F407

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.