Migrating from CSM to TOM

When you are defining objects for Total Object Manager (TOM) to manage by using the local system, you can migrate existing definitions from an existing availability manager into a format that TOM can use to create object definition bases.

TOM provides migration utilities for Continuous State Manager (CSM), IBM System Automation for z/OS, IBM Tivoli AF/Operator, and CA OPS/MVS Event Management Automation. The TOM migration utilities require input from the availability manager to produce a REXX EXEC. TOM uses the produced REXX EXEC to create a definition base containing object definitions from the existing object definitions in the availability manager from which you are migrating.

CSM provides a REXX EXEC named CSMACT that allows custom automation to send request to CSM to start and stop an object, and perform other functions.

Important

If you are currently using custom automation, you must change your automation to call TOMACT instead of CSMACT.

Related topics

Migrating-the-CSM-repository-to-TOM-recommended-method

Converting-the-Continuous-State-Manager-repository

Converting-the-CSM-repository

Because TOM provides automation variables for the objects that it manages, you must locate references to the variable data, and change the automation to reference TOM's automation variables. 

This section contains the following topics:

 

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