Implementing Continuous State Manager

This section provides information to help you implement Continuous State Manager (CSM).

Important

Before implementing CSM, note that the Total Object Manager (TOM) application is a newer and more functionally-rich object manager. TOM is more flexible and supports more object management options, such as managing USS processes and Workload Manager Resources as objects. For more information, see Using-Total-Object-Manager.

For existing CSM users, the CSM to TOM conversion utility automates and simplifies the conversion process for moving your object management automation from CSM to TOM. For more information, see Converting-the-Continuous-State-Manager-repository. 

Running CSM with Rules Management

In version 8.3, BMC AMI Ops Automation allows you to migrate your CSM Rule Sets to run in the Rules Management application.

For more information about Rules Management, see Implementing-Rules-Management.

For more information about migrating your CSM Rule Sets to the Rules Management application, see Migrating-Continuous-State-Manager-Rules-CSM-to-the-Rules-Management-application.

Related topic

Customizing-BMC-AMI-Ops-Automation-after-installation

Performance considerations

For the best performance results, add both CSM EXEC libraries, prefix. BBPROC and prefix. BBCLIB, to the Virtual Lookaside Facility (VLF). See the IBM documentation TSO Customization Guide for more information about VLF.

Review BBPARM member AAOEXP00 and ensure the CSM EXECs are defined as HIGH priority EXECs. See Continuous-operation-with-dynamic-parameter-management, for more information about AAOEXP00 and high-priority EXECs.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*