SSMSTOP not intercepting P command.

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

A REXX program is being triggered from a TOD rule to cycle our TPX session manager once a week.  This week it failed on shutdown.  CASTATE is used for Activation Complete Event.  EOM is used for Inactivation Complete Event. The shutdown ended with a RC=0.  However, the current state was set to failed.  The desired state was UP.  It appears that the P TPX command bypassed the SSMSTOP CMD rule as there is no indication in the log of the desired state being changed.

 

 

 

 

Environment

Release : 14.0

Cause

The SSMSTOP rule has code to let STOP commands issued by OPS itself execute normally without setting the desired state of the task to DOWN.

This includes OPSMAIN and OPSOSF servers.

Resolution

Instead of issuing the STOP command from a REXX using the ADDRESS OPER statement, use ADDRESS SQL to set the desired state of the resource to DOWN:

Address SQL                                
"Update STCTBL set DESIRED_STATE = 'DOWN'",
  "Where JOBNAME = 'resource' "