CA OPS/MVS release 12.3 SSM V3 transient resource states (starting/stopping) support and the possible effect on pre-existing SSM configurations ? Best Practice
search cancel

CA OPS/MVS release 12.3 SSM V3 transient resource states (starting/stopping) support and the possible effect on pre-existing SSM configurations ? Best Practice

book

Article ID: 43599

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

Introduction:

Upon installation of CA OPS/MVS release 12.3 PTF APAR RO86755 and the setting of parameter SSMVERSION to 3, the current state will be updated automatically to starting or stopping when actions are taken for the up_down and down_up state mismatches to simplify state management and eliminate PREREQ errors.  Transient states will be set automatically to indicate a down_up or up_down action has been initiated. The SSM engine will set the current state immediately before the up_down or down_up action is taken.                                                              

Instructions:

Once SSM V3 is fully deployed consider running extensive testing to assure transient states are handled properly by any pre-existing automation code that you decide to keep in use. As a best practice we are recommending the use of the new SSM V3 policy management code. We also recommend that Shutdown and IPL procedures are tested over sandbox systems to simulate these type of scenarios. This should be done before the product is promoted over production systems. In case automation related problems are detected while handling transient states we encourage you to contact CA Technologies Customer Support. A new ticket should be open so your situation can be diagnosed and a formal recommendation can be provided.

Additional Information:

You can find additional information at our website: CA Technologies Documentation

Environment

Release: PVLA2.00200-12.3-OPS/MVS-Event Management & Automation-for JES2
Component: