The System State Manager (SSM) facility automates and controls the management of system resources, such as started tasks, subsystems, JES initiators, and VTAM nodes. SSM supervises system resources, such as running tasks and peripheral devices. The goal of the SSM engine involves always keeping a resource in its desired state. When the current state differs from the desired state, SSM dispatches an action (as specified in the action text) to restore the resource to its proper state.
The states of started tasks, subsystems, and other resources change frequently. These states start, stop, and recycle continually. Often, resources have dependencies between them, and you cannot start or stop a resource until some other resource initializes or stops. For example, TSO cannot start until VTAM initializes, and VTAM cannot stop while TSO remains active. Sometimes, a system ABEND or other system problem causes a started task or subsystem to terminate abnormally, which requires the operator to recover or restart it.
The current SSM (Version 2) provides a framework for cross-system resource management. This framework lets you extend your SSM applications in environments where there are resources with cross-system prerequisite relationships and resources that can run on alternative backup systems to the primary system. Specifically, SSM Version 2 includes enhancements for naming cross-system prerequisites and handling cross-system events. These enhancements allow for gathering, communicating, and maintaining information on cross-system resource relationships, and initiating actions based on this information.
SSM also provides more robust prerequisite capabilities in single system and sysplex environments, exploitation of a new SQL capability to support variable length character data, and global variable syntax that simplifies defining automation actions across both sysplex and non-sysplex systems. SSM also provides an audit trail for SSM table updates.
Note: The SSMVERSION parameter controls which version of SSM starts. In CA OPS/MVS Release 11.6, the SSMVERSION parameter defaults to a value of 2, and cannot be set to any other value. If you are migrating to Release 11.6 from a prior release of CA OPS/MVS that was running with parameter SSMVERSION set (or defaulting) to a value of 1, you must run the OPS/REXX program OPSSM2CV to convert your SSM resource and action tables for use by SSM Version 2.
|
Copyright © 2014 CA.
All rights reserved.
|
|