Important
We recommend that you to use the advanced CSM Migration Utility MAMMGCSM instead of the one described in these topics. For more information, see Migrating the CSM repository to TOM (recommended method).
Some of the enhanced features of MAMMGCSM are:
- Create TOM Layer Objects from CSM objects
- Create an import EXEC instead of a Definition Base
- Create a TOM set from a CSM grouping object
- Execute the utility standalone (without BMC AMI OpsAor TOM active)
- Demo-mode to create simulated objects that represent actual objects
- SCAN feature to create a report of all uses of CSM variables and CSMACT EXEC in UBBPARM rules and UBBPROC EXECs
The legacy conversion information in this section only supports converting CSM objects into TOM managed objects but does not support defining TOM layering objects. Layering objects are very useful and allow you to quickly define and manage many similar objects that are running on multiple LPARs or sysplexes. Layering creates objects and sets that you can deploy to other sysplexes. This process minimizes the number of times that you have to define or update objects and sets (and their associated definitions). For more information, see Managing-objects-across-sysplexes-with-layering.
This conversion utility works only with BMC AMI OpsA CSM. It allows you to use a single CSM as a template for multiple conversions by using different pattern names while preventing the accidental destruction or corruption of current objects.
The CSM conversion utility can only be run after TOM version 2.1 (or later) is installed and active, and requires that you use an authorized terminal session. If an authorized terminal session is not used or the version of code in STEPLIB or LINKLST does not match the TOM version code, CSM conversion will fail with appropriate messages.
This section contains the following topics: