PH44819: RTA Event is removed as MQ and CMAS is shutdown but on restart CMAS WLM is not notified, thus affecting workload routing tothis

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In this issue a TOR stopped routing work to its local target
  AORs unexpectedly.  In this scenario an RTA VHS event occurred
  in each of the regions that caused them to have the higher
  routing weight and therefore not be selected for routing of the
  workload.  The VHS event was that the MQCONN was shutdown for
  upgrade.  This created an outstanding RTA "EYUPN0007W Notify
  created" event for each of the local AORs.  While MQ was down,
  the connected CMAS was also brought down for upgrade.  This
  resulted in the "EYUPN0013W Notify removed" for each of the
  outstanding events.  The MQCONN was restarted  and eventually
  the CMAS was restarted.  After that point, although the event
  was removed, from a WLM perspective for each of the target AORs
  the VHS event was never cleared thus affecting the routing.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM Users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Workload weightings from outstanding    *
  *                      RTA events incorrectly persist across   *
  *                      CMAS warm start.                        *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF for this APAR to all CMASes.   *
  *                 This can be done in any order.               *
  ****************************************************************
  During normal CMAS termination, outstanding RTA events are
  removed, as shown by message EYUPN0013W showing REMOVED for the
  definitions. However, after CMAS warm start, these previous
  outstanding RTA events are still factored in algorithmic weights
  for the workloads to which the RTA definition is applied.
  
  This is due to the workload management component data spaces
  persisting over CMAS warm starts. The WLM cache list
  containing the RTA event information for workloads, is not
  cleared over CMAS warm starts, and as such the weightings
  incorrectly represent RTA events which have been previously
  removed or resolved.
  
  Note, when the CMAS starts, if no data spaces that the CMAS
  used the last time it was active still exist, the start is a
  CMAS cold start; if such data spaces exist, the start is a
  CMAS warm start.
  Refer to 'Managing CMAS restarts' in IBM Documentation.
  

Problem conclusion

• WLM warm start has been updated to clear the WLM event cache
  list of the previously outstanding RTA events from the previous
  instance of the CMAS. This removes the previously calculated
  algorithmic weightings from the workloads which were outstanding
  at the point the CMAS was terminated. Currently outstanding RTA
  event criteria met by locally connected active MAS regions are
  not represented in the workload weightings after restart until
  the next RTA evaluation interval, when they are shown as
  outstanding RTA events in the CMAS.
  

Temporary fix

Comments

APAR Information

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

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

  UI80258

Modules/Macros

• EYU0WMEA EYU0WMWS EYU9WMP3 EYU9WMP4 EYU9WMPU EYU9WMR3 EYU9WMR4
  EYU9WMRU
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R30M PSY UI80258

     UP22/04/26 P F204

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.