A fix is available
APAR status
Closed as program error.
Error description
ERROR DESCRIPTION:Ø Running CPSM, a target region was quiesced from an active workload and remained in a QUIESCING state indefinitely. The following message was issued to indicate the quiesce request was issued: . EYUWM0441I date time applid A quiesce has been issued for target region (sysname) for context (plexname). . But the subsequent message was never issued to indicate the region had been quiesced from the workload: . EYUWM0423I date time applid Target region (sysname) has been quiesced for context (plexname). . This problem can occur when a MAS was a target region known to a CMAS that manages the workload in the network. For example: . - If the MAS was in the AORSCOPE for a workload that the CMAS manages, but was removed from the AORSCOPE. . - If the MAS was not in an AORSCOPE for a workload that the CMAS manages, but connected to the CMAS and its CSYSDEF indicated that it run optimized, and then subsequently terminated and connected to another CMAS. . . . Additional Symptom(s) Search Keyword(s): KIXREVGJT
Local fix
While the target region is in a QUIESCING state, issue the ACTIVATE action against the target region, and then re-issue the QUIESCE action.
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R2M0, V5R3M0 and V5R4M0 * * Users. * **************************************************************** * PROBLEM DESCRIPTION: When a QUIESCE action is issued against * * the WLMAWAOR resource record of a CPSM * * WLM target region, the region may enter * * and stay in QUIESCING state but never * * transition to QUIESCED state, even * * though no active affinities exist for * * the region. * * * * Message EYUWM0441I will be issued by * * CMAS(es) indicating the switch to * * QUIESCING state, but message EYUWM0423I * * indicating the switch to QUIESCED state * * will not be issued. * * * * This is more likely to occur if: * * * * - the region was in the AORSCOPE for a * * workload that a CMAS manages, but * * was removed from the AORSCOPE and is * * not in the AORSCOPE for any other * * workload managed by that CMAS. * * * * - the region was not in an AORSCOPE * * for any workload managed by a CMAS, * * but Topology connected to the CMAS * * and its CSYSDEF indicated that it * * was enabled for WLM optimization, * * and then subsequently terminated and * * connected to another CMAS. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes must be recycled to pick up * * the new code. Note that the restarts do not * * need to occur at the same time. * **************************************************************** When a QUIESCE action is issued for a CPSM WLM target region, method EYU0WAUO (WAUO) runs in all CMASes in the network that manage the CICSplex the region is associated with. When WAUO runs in a CMAS, if the CMAS has an EYURWAOR control block (WAOR) for the region, and the WAOR indicates that the region is ACTIVE, it will mark the region's WAOR as QUIESCING and issue message EYUWM0441I. Regardless of whether it has a WAOR for the region or not, each CMAS then has the responsibility to notify each other CMAS that it has no active affinities for the region, and that the region can be marked QUIESCED. Once all CMASes have been notified as such, every CMAS that issued message EYUWM0441I will mark the WAOR as QUIESCED and issue message EYUWM0423I. If a CMAS has a WAOR for a region that indicates that the region is DOWN, then it will not process the region, and will not notify the other CMASes that they can mark the region as QUIESCED. While this is valid if the region is not active, there are some situations where a WAOR can be marked as DOWN while the region is active. When this occurs, the other CMASes in the network will never be notified that they can mark the region as QUIESCED.
Problem conclusion
WAUO has been updated such that if the WAOR indicates that a region is DOWN, it will verify whether the region is active or not. If the region is not active, it will properly ignore the request. If the region is active, it will process the request.
Temporary fix
Comments
APAR Information
APAR number
PI94221
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
90M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-23
Closed date
2018-03-06
Last modified date
2018-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI54286 UI54287 UI54288
Modules/Macros
EYU0WAUO
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R00M PSY UI54288
UP18/03/07 P F803
R10M PSY UI54287
UP18/03/08 P F803
R90M PSY UI54286
UP18/03/08 P F803
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 April 2018