Current state set to DOWN while the task was still active during shutdown
Article ID: 111828
OPS/MVS Event Management & Automation
During shutdown OPS/MVS issued set to SSMTABLE for a resource of CURRENT_STATE=DOWN. Since (current_state and desired_state) are both set to DOWN. SSM Action table wasn't driven to bring down the resource. The STOPJES2 routine issued an cancel this task later. From OPSLOG: OPS7914T SSMv2 AUDIT: STCTBL.taskname UPDATED by OPSOSF SSMSHUT CURRENT_STATE=DOWN
Release: Component: OPSMVS
From this message: "OPS7914T SSMv2 AUDIT: STCTBL.taskname UPDATED by OPSOSF SSMSHUT CURRENT_STATE=DOWN" we can see it was the SSMSHUT REXX program that set the CURRENT_STATE of this resource to DOWN. SSMSHUT takes this action when the resource mode is PASSIVE or INACTIVE. From SSMSHUT comments: "For any PASSIVE or INACTIVE resource force the current state to it's DOWN state (even though the resource isn't actually DOWN). "