PH57291: DYNAMIC PROGRAM EXECUTED ON LOCAL MAS (TOR) RATHER THAN ON REMOTE AOR.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Dynamic Program installed on local MAS (TOR) rather than on
  remote AOR.
                                                                 .
  To set the scene:
  On local TOR (MAS)
  Program defined with Dynamic Status as 'DPL Permitted', no
  Remote Sysid and Remote transid XXXX.
                                                                 .
  The DTRPGM exit is configured as EYU9XLOP so CPSM will act as
  the routing exit.
  As no Remote Sysid is defined, CICS assumes the default choice
  is the Local region.
  This input is passed from CICS to CPSM.
  CPSM examines the WLMSPEC and relevant WLMDEFs to decide where
  the request is to be routed to.
  The tranid XXXX is used to drill down from a specific Workload
  to Transaction Group and from there to locate the particular
  target regions AOR1 and AOR2 connected to CMASnnnn.
                                                                 .
  Amongst the factors to decide on the best choice between these
  regions is WLMHEALTH.
  CPSM found that WLMHEALTH for AOR1 was 0.
  Therefore if AOR2 was temporarily unavailable, eg restarting,
  there would be no viable target region for the routing request,
  and the program would be loaded/installed on the local TOR
  region.
                                                                 .
  It looked like there was a timing issue between WLMHEALTH value
  changes and delays in different CMASs processing the MAS
  topology join.
  The initial connect and join events contain a WLMHEALTH value
  from when the MAS starts its initial CONNECT. This is usually
  zero.
  In this timing issue, some messages were processed out of order
  and the WLMHEALTH=0 was unfortunately written over the newer
  WLMHEALTH=100 for target MAS region AOR1.
  Then in the problem scenario, CPSM found that AOR1 had
  WLMHEALTH=0, and AOR2 unavailable (restarting), so the Program
  was loaded in the local TOR region.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM Users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: CMAS regions processing a topology      *
  *                      JOIN for a remote MAS region, may       *
  *                      incorrectly report the WLMHEALTH        *
  *                      value of the MAS region. This may       *
  *                      result in workloads not correctly       *
  *                      routing work to this MAS region, though *
  *                      the MAS region has a higher or 100%     *
  *                      WLM health.                             *
  ****************************************************************
  * RECOMMENDATION: Apply PTF fixing this APAR to all CMAS       *
  *                 regions and restart. Regions may be          *
  *                 restarted in any order.                      *
  ****************************************************************
  When a MAS region connects to a CMAS, the CMAS exports the MAS
  region information to other CMASes. These process a topology
  join. However if the communication long running task (CPLT) is
  busy at this time, the MASDIR import may get delayed. During
  this time, the MAS regions WLMHEALTH value changes. This results
  in an EWEALTH event being produced, containing the updated
  WLMHEALTH value. This is processed by the CMAS processing the
  import and stored locally in a CSDB. When CPLT completes the
  import processing an EENDJOIN event is produced, containing
  the WLMHEALTH value at the time of the MAS starting. When
  this event is then processed, this value is then stored in the
  CSDB for the MAS, replacing this previously stored value.
  
  This results in the CMAS reporting the wrong WLMHEALTH value
  for the MAS region, until a EWEALTH is later produced. As such
  CPSM workloads will factor the incorrect WLMHEALTH value,
  resulting the the MAS region being incorrectly ranked and
  work not being routed to this region.
  

Problem conclusion

• CMAS processing of WLMHEALTH has been updated to ensure the
  value is only updated by EENDJOIN, when the MAS start time and
  therefore the events contained WLMHEALTH value is later than
  the value stored in the CSDB for that region.
  

Temporary fix

Comments

• ×**** PE25/05/08 FIX IN ERROR. SEE APAR PH66461  FOR DESCRIPTION
  

APAR Information

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

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

  UI94157

Modules/Macros

• EYU0TIST
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R40M PSY UI94157

     UP23/10/27 P F310

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.