APAR status
Closed as program error.
Error description
The PowerHA cluster manager is supposed to reject changes to the application monitor function unless the cluster state is ST_STABLE. However, if the cluster is in a state such as ST_RP_FAILED and an attempt is made to suspend application monitoring, the application state will be changed to "ONLINE MONITOR SUSPENDED", but the application monitor(s) will not be suspended. This application state prevents either suspend or resume of application monitoring, even after the cluster state has been returned to ST_STABLE.
Local fix
Check to make sure that the cluster manager is in state ST_STABLE on all nodes before attempting to suspend or resume application monitoring. However, once the mismatched state has occurred, this can be corrected only by stopping and restarting PowerHA cluster services on that node.
Problem summary
If user trying to suspend or resume the application when the cluster is not ST_STABLE state below message is seen in the clstrmgr.debug file even though suspend is failed Resource::setState: Resource APP_CON is already 6, return
Problem conclusion
Using the clmgr manage suspend/resume application command from the smit to prevent application suspend or resume if cluster is not in ST_STABLE state.
Temporary fix
Comments
APAR Information
APAR number
IJ45671
Reported component name
POWERHA SYSMIR
Reported component ID
5765H3900
Reported release
727
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-03-02
Closed date
2023-03-02
Last modified date
2023-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
POWERHA SYSMIR
Fixed component ID
5765H3900
Applicable component levels
[{"Business Unit":{"code":"BU008","label":"Security"},"Product":{"code":"SGL4G4","label":"PowerHA"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"727"}]
Document Information
Modified date:
02 March 2023