We had OPSMAIN emergency shutdown and restarted however one of the started task was turned down.
search cancel

We had OPSMAIN emergency shutdown and restarted however one of the started task was turned down.

book

Article ID: 225443

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

We had OPSMAIN emergency shutdown and restarted however one of the started task SYSVUSER was down and no notifications received.

 

Environment

Release : 14.0

Component : OPS/MVS

Cause

Incorrect option was replied to the SSMBEGIN WTOR. 

Resolution

When OPS is restarted during normal operations the response to the SSMBEGIN WTOR must be 4A.
The WTOR is:

xxx SSMBEGIN Enter desired Stateman startup option (1-5) and/or mode (A/P/I).

The most common responses are:

3A - Used for an IPL. The resource table (usually STCTBL) column IPL_STATE is copied over the column DESIRED_STATE

4A - Used for OPSMAIN restarts during normal operations. The column CHECKPOINT_STATE is copied over the column DESIRED_STATE. The CHECKPOINT_STATE contains the latest value of the DESIRED_STATE column before OPS was shutdown.

Additional Information

https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/using/using-ca-ops-mvs/using-system-state-manager/methods-for-setting-the-desired-state.html#concept.dita_40bd14385a1d9e33ff9abc65494f096cf935a569_SetDesiredStatesThroughSSMBEGIN