Migrating the CSM repository to TOM (recommended method)

(BMC.AMIOPS.SPE2110)

This section includes the following topics:

The CSM Migration Utility enables you to easily define TOM managed objects or layer objects from a CSM input repository data set. BMC AMI Ops Automation provides a REXX EXEC and MAMMGCSM in BBSAMP that helps you define TOM managed objects or layer objects from CSM objects. For more information about defining TOM layer objects, see Defining TOM layer objects.

After you modify the parameters in the MAMMGCSM EXEC, execute the EXEC to create an import EXEC from the input CSM repository data set. You can review the created import EXEC before you execute it. The import EXEC then defines a new definition base with TOM managed objects, layer objects, and sets that any TOMPLEX can use.

Prerequisites

MAMMGCSM EXEC does not require TOM or CSM (BMC AMI OpsA) to be active during the migration process.

Defining TOM layer objects

Specify LAYER(Y) in MAMMGCSM to define the following TOM items:

Layer objects
Layer sets
System layers
Layer sysplex (Sysplex matrix)
Sysplex layer
System pool

Using parameters in MAMMGCSM

The CSMGRP(*ALL*|<groupName>) parameter controls the scope of input objects for migration. When you specify CSMGRP(*ALL*), EXEC scans all CSM groups in the input repository. Unique objects, such as objects that are members in only one CSM group and are not moveable, are added to a system layer named sl.<systemName>. Non-unique objects, such as those that are members in more than one CSM group or are moveable, are added to a system layer named sl.BASE.

When you specify CSMGRP(<groupName>), only the objects in this group are used to create layer objects and these objects are added to a system layer named sl.BASE. If you specify LAYER(N), the CSMGRP(*ALL*) specification is enforced.

You can schedule the MAMMGCSM EXEC from BMC AMI Ops Automation or execute it from TSO.

TIP

The MAMMGCSM supports a demo-mode option which you can use to define demonstration objects that run the AATWAIT program. Using AATWAIT can be a useful tool you can use to train your operators about using TOM.

Specify a catalogued procedure name (for example, TOMCSMOB) with the DEMOPROC parameter to define demonstration objects that run the AATWAIT program which BMC AMI OpsA distributes. For more information about the AATWAIT program, review BBSAMP member TOMCSMOB.

MAMMGCSM includes the optional parameter SCAN that you can use to create a report of all the occurrences of CSM variables and the usage of CSMACT in UBBPARM rules and UBBPROC EXECs. When you specify SCAN(Y), you must also specify the UBBPARM and UBBPROC data set names for the scan to produce the report. A list of all occurrences of CSM variables (prefixed by &CSM) and CSMACT are written to the migration log. Specify the migration log data set with the LOG(dataSetName) parameter.

To use the CSM Migration Utility

Copy MAMMGCSM from the BBSAMP data set to your UBBPROC data set.
Edit basic and advanced user-modifiable sections of the MAMMGCSM EXEC to meet the needs of your conversion.
You can also specify the parameters when MAMMGCSM is executed as a part of the command.
For example, %MAMMGCSM LAYER(Y) CSMGRP(*ALL*) SCAN(Y) DEMOPROC(TOMCSMOB) INDSN(MY.CSM.REPOSITORY) DSN(MYLIB.EXEC) MBR(TOIMPORT) REUSE(Y)
Schedule MAMMGCSM EXEC from the BMC AMI OpsA Journal by issuing %MAMMGCSM.
Review the issued messages to make sure that the migration process was completed successfully.
You can also execute the MAMMGCSM EXEC from TSO or in TSO batch. If you have executed the MAMMGCSM EXEC from TSO or TSO batch, check the TSO session or the SYSTSPRT output to ensure that the migration process successfully completed.
Important
When you execute from TSO or TSO batch, the UBBLINK parameter must specify the data set name of the BMC AMI OpsA load modules.
Review the import EXEC created by the utility and make modifications, if necessary.

Be cautious when you are modifying the EXEC. If there are dependencies among objects, sets, or calendars; modifying or deleting objects might affect other objects and definitions.
Execute the import EXEC from the BMC AMI OpsA Journal to import the definitions to a TOM definition base.
BMC AMI OpsA and TOM must be active to perform this step.

MAMMGCSM parameters

You can specify the parameters when MAMMGCSM is executed as part of the command. You can also edit and modify the parameters in MAMMGCSM EXEC after you copy it to your UBBPROC library.

The user-modifiable section of MAMMGCSM contains two segments: basic and advanced. The following table describes the parameters for the basic segment:

Parameter	Description
LAYER(Y\|N)	Optional Y specifies whether the layer objects and associated layer items should be defined. N specifies that normal managed objects should be defined. The default value is Y.
CSMGRP(ALL\|<groupName>)	Required only when you specify LAYER(Y) Specify either ALL or a CSM group name. The following events occur when you specify ALL and all CSM groups are scanned: Layer objects found in more than one CSM group have their names added to a system layer called sl.BASE. Layer objects found in a single CSM group have their names added to a system layer called *sl.<system name>. If you specify a single CSM group name, only the objects in this group are used to define layer objects and their names will be added to system layer sl.BASE. If you specify LAYER(N), the CSMGRP(ALL*) specification is enforced.
SYSPLEX(<plexname>)	Required Specifies the sysplex name to be used for the layer sysplex and sysplex matrix definitions, and (possibly) layer-generated object names. The sysplex name can also be used in object name or pattern.
UBBLINK(‘<dataSetname>’)	Required only when MAMMGCSM is not executed from BMC AMI OpsA Specifies the fully qualified data set name where BMC AMI OpsA load modules are found.
INDSN(‘<repository dataSetName>’)	Required Specifies the fully qualified name of the CSM repository VSAM data set.
DSN(‘<dataSetname>’)	Required Specifies the default fully qualified name of the pre-allocated output partitioned data set (PDS or PDS/E) where the import EXEC will be written.
MBR(<memberName>)	Required Specifies the member name to be given to the import EXEC created by MAMMGCSM. If you specify REUSE(Y) and the member name already exists in the PDS, the member is overwritten; else processing terminates and a warning message is issued.
LOG(‘<dataSetname>’)	Required Specifies the fully qualified name of the migration log data set. In case a data set of that name does not exist, it is either created or the pre-allocated data set is used.
REUSE(N \| Y)	Optional Specifying REUSE(Y) allows the specified PDS member (MBR parameter value) to be overwritten if it already exists in the PDS. Specifying any other value causes the process to terminate if the specified member already exists in the PDS. The default value is N.
VERBOSE(N \| Y)	Optional Specifying VERBOSE(Y) writes more information about processed items to the log. The default value is N.

The following table describes the parameters for the advanced segment:

Parameter	Description
DEMOPROC(<procName>)	Optional Specifies the name of the cataloged procedure to use on the start command for all migrated STM objects. The PROC uses the AATWAIT program which is distributed with BMC AMI Ops Automation. All started task names will be MAMGnnnn /lo.MAMGnnnn (LAYER=Y), where nnnn is a number between 0001 and 9999. Demo mode is activated when you specify this parameter. BBSAMP member TOMCSMOB is also distributed with BMC AMI Ops Automation. To use this option, copy TOMCSMOB to your procedure library, modify it as needed, and specify DEMOPROC(TOMCSMOB) or create your own procedure and specify its name.
SCAN(N \| Y)	Optional Specifying SCAN(Y) creates a report of all uses of CSM variables and CSMACT EXEC in UBBPARM Rule Sets and UBBPROC EXECs. You must also specify all data set names used by the PAS for the corresponding concatenations for the UBBPARM and UBBPROC parameters. The default value is N.
UBBPARM(’<dsn1,dsn2,…dsnN>’)	Required when SCAN(Y) is specified Specifies all data sets used by the BMC AMI OpsA PAS for the UBBPARM concatenation.
UBBPROC(’<dsn1,dsn2,…dsnN>’)	Required when SCAN(Y) is specified Specifies all data sets used by the BMC AMI OpsA PAS for the UBBPROC concatenation.
OBJNAM(<nameConvention>)	Optional Specifies the naming convention for a non-moveable object. The following lists the valid options: object_name object_name.system object_name.sysplex sysplex.object_name sysplex.system.object_name system.sysplex.object_name object_name.sysplex.system object_name.system.sysplex system.object_name (default)
MVOBJNAM(<nameConvention>)	Optional Specifies the naming convention for a moveable object. The following lists the valid options: object_name object_name.system object_name.sysplex system.object_name sysplex.system.object_name system.sysplex.object_name object_name.sysplex.system object_name.system.sysplex sysplex.object_name (default) We do not recommend using a system name for a moveable object.
PTRN(<patternConvention>)	Optional Specifies the pattern attribute for non-moveable layer objects. The following lists the valid options: object_name &SYSPLEX.&SYSNAME.object_name &SYSNAME.&SYSPLEX.object_name &SYSPLEX.object_name object_name.&SYSPLEX.&SYSNAME object_name.&SYSNAME.&SYSPLEX object_name.&SYSPLEX object_name.&SYSNAME &SYSPLEX.&SYSCLONE.object_name &SYSCLONE.object_name object_name.&SYSPLEX.&SYSCLONE object_name.&SYSCLONE.&SYSPLEX object_name.&SYSCLONE &SYSNAME.object_name (default/recommended) The layer object will be named lo.<object_name>.
MVPTRN(<patternConvention>)	Optional Specifies the pattern attribute for moveable Layer Objects. The followings lists the valid options: object_name &SYSPLEX.&SYSNAME.object_name &SYSNAME.&SYSPLEX.object_name &SYSNAME.object_name object_name.&SYSPLEX.&SYSNAME object_name.&SYSNAME.&SYSPLEX object_name.&SYSPLEX object_name.&SYSNAME &SYSPLEX.&SYSCLONE.object_name &SYSCLONE.object_name object_name.&SYSPLEX.&SYSCLONE object_name.&SYSCLONE.&SYSPLEX object_name.&SYSCLONE &SYSPLEX.object_name (default/recommended) The layer object is named lo.<object_name>. We do not recommend using &SYSNAME in a pattern for moveable layer objects.
SHORTNM(N \| Y)	Optional SHORTNM(Y) will automatically populate Short Name with CSM object name for all objects in the selected group. The default value is N.
CTRL(SUSPEND \| ACTIVE)	Optional Sets the initial control mode of the newly generated objects. If you want the objects to be active immediately after running the import EXEC, set CTRL(ACTIVE). The default value is SUSPEND.