PI90286: CPSM FROZEN WORKLOAD - ADDITIONAL DIAGNOSTICS NEEDED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a CMAS managing a CPSM Workload ( WLMSPEC ) loses
  connectivity with another CMAS that also manages that same
  workload (and which has active MASes in the workload) then the
  workload is put into a FROZEN state. When connectivity is
  restored, the workload is 'thawed' or 'unfrozen'. This may
  happen regularly, and under normal circumstances, poses no
  problems.
  .
  There may be times however where something goes awry in the
  process and a workload remains in a FROZEN state. This may not
  get noticed until much later (days, weeks, months) when a
  customer needs to install updates to the active workload. If
  the workload is in a frozen state, CPSM will prevent any
  changes from taking place. Having a history of when the
  workload gets frozen and thawed would greatly help diagnosing
  the situation.
  .
  .
  Additional Symptom(s) Search Keyword(s): KIXREVGJT
  EYUVC1231E
  EYUVC1272I Action INSTALL failed 23
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V5R2M0, V5R3M0               *
  *                 and V5R4M0 Users.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: A CMAS reports a Workload status of     *
  *                      "Frozen", even though all CMAS and MAS  *
  *                      elements of the workload are active.    *
  *                      In addition, cache lists relating to    *
  *                      the unit-of-work relationships of a     *
  *                      restarted TOR are becoming orphaned.    *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes must be recycled to pick    *
  *                 up the new code. The restarts need not be    *
  *                 performed at the same time.                  *
  ****************************************************************
  For a Workload to be in an active state, all CMASes and MASes
  that are participant in the workload must be active and
  contactable.  If a MAS should drop out of CPSM control in an
  unplanned manner, then it would be deemed to be in a
  "Lost contact" condition, and the active workload would move
  into a "Frozen" state.  Whilst in this state new MASes may
  join the workload, but there cannot be any changes to any
  affinities that were active at the time the Frozen condition
  arose.  Normally, the most likely way for a Frozen workload to
  occur is for a CMAS (that is managing a MAS in the workload) to
  go out of contact with its connected CMAS partners.
  
  In a multiple CMAS workload situation, a timing hole has been
  found whereby a CMAS and TOR restarting at the same time can
  cause the workload defrost to fail on the restarting CMAS.
  All other CMASes managing the workload will report it as active,
  but the restarted CMAS will continue to show the workload as
  frozen. This will leave the workload in an unstable state,
  preventing new TORs from joining the workload, and preventing
  workload affinity management from processing properly.
  

Problem conclusion

• The CMAS workload import method EYU0WMQU has been updated to
  fix a logic error when comparing the name of a joining TOR's
  owning CMAS with that of the local CMAS name, which was
  causing the suppression of a defrost notification for the
  joining TOR.
  
  The CMAS TOR Join method EYU0WMTJ has been updated to add
  processing to ensure that if an old unit-of-work affinity
  list is still anchored in the TOR descriptor control
  block (WTOR), then it is removed prior to allocating and
  chaining a new UOW affinity list into the WTOR.
  

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:

  UI56301 UI56302 UI56303

Modules/Macros

• EYU0WMQU EYU0WMTJ
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R00M PSY UI56302

     UP18/06/08 P F806

• R10M PSY UI56303

     UP18/06/08 P F806

• R90M PSY UI56301

     UP18/06/14 P F806

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.