Accessing the conversion utility
On the Automation Menu, enter C (CSM Conversion) on the OPTION line.
BMC Software ---------------- AUTOMATION MENU -------------------- BMC AMI OpsA
OPTION ===> DATE -- 2007/10/02
TIME -- 16:05:50
Basic Automation:
1 Event Activity Statistics
2 Display/Modify Rules and Rule Sets
3 Continuous State Manager - Global Overview
4 Object Management
Advanced Automation:
6 Shared Object Facility
7 Display/Modify EXEC Status
8 Time-Initiated EXEC Requests
9 Open Systems Procedural Interface (OSPI)
Utilities:
C CSM ConversionThe CSM Conversion confirmation panel is displayed.
BMC Software ---------------- AUTOMATION MENU -------------------- BMC AMI OpsA
OPTION ===> DATE -- 08/01/14
TIME -- 15:17
1. Convert CSM to TOMOn the CSM Conversion confirmation panel, enter 1 on the OPTION line.The CSM to TOM Conversion confirmation panel is displayed.
CSM to TOM Conversion - Input
Command ===>
Enter YES to convert the data set. Enter TEST to generate a test report only.
Convert Data Set?: TEST ( YES or TEST )
Specify the name of CSM v6 or higher repository data set containing the
CSM objects to be converted into TOM format.
CSM Repository: 'BBTEST.TEST.BBIREPS'
Specify if short name should be automatically generated:
Suppress short name auto generation: N ( Y or N )
Specify the TOMPLEX where the CSM objects will be converted.
TOMPLEX: BMCTOMNS Use ? to select from active TOM Plexes
Specify the name of the data set where the Conversion Log will be written.
If the data set does not already exist, it will be allocated dynamically.
Log Data Set: 'BBTEST.LOG'
Disposition : SHR ( SHR or MOD )
Press ENTER to continue or CANCEL to exit- In the Convert Data Set? field, enter TEST.
The conversion attempt does not actually produce any TOM objects from the CSM object repository. Test mode shows how many CSM objects can be converted to TOM objects. You can review the Conversion Log to see which CSM objects might require manual conversion. - In the CSM Repository field, enter the name of the CSM repository.
- In the Suppress short name auto generation field, specify N if short names should be auto generated for all objects.
- In the Log Data Set field, enter the name of the data set to which you want the conversion utility to write the log.
- In the Disposition field, enter SHR to overwrite a preexisting Conversion Log data set or enter MOD to append the log information to an existing log data set.
Press Enter to continue.A panel is displayed in the following image, explaining that, for each CSM group that you want to convert, you must define
- The name of a valid system on which the objects will run
- The name of a TOM Definition Base to use to store the newly converted objects
- The initial control setting for each object (ACTIVE or SUSPEND)
CSM to TOM Conversion
Command ===>
Please review the following information before proceeding:
The next panel will display the CSM Groups in the requested repository. For
each Group that you wish to convert, specify a Valid System, Definition Base
and Control setting.
Valid System: The MVS sysname where the CSM Group will be enabled.
Definition Base: The name of the Object Base where the objects from the CSM
group are to be stored. Since only one TOM Plex can be active at a time,
use the same Definition Base for all CSM Groups which will be managed by
the same TOM Plex. Specify a unique Definition Base for any CSM Group
which is to be used an Alternative Definition Base.
Control: Specify whether the objects in the Group should be activated by TOM
as soon as the Definition Base becomes active. If you wish to activate the
objects in the Group immediately after the conversion, set Control active
for the currently active Definition Base.
Press ENTER to continue or CANCEL to exitReview the instructions and press Enter to continue.The conversion utility displays a panel that lists all CSM groups found in the specified CSM repository data set.
CSM to TOM Conversion - Groups
Command ===>
TOMPLEX: BMCTOMNS
Enter a Valid System, Definition Base and Control for the CSM Groups
that you wish to convert.
Valid Control
Group System Definition Base Active/Suspend
TEST SYS1____ Test Definition Base S______
TESTX SYS2____ Prod Definition Base S______
NS64 ________ ________________________ _______
NS64X ________ ________________________ _______
NS6N ________ ________________________ _______
NS65 ________ ________________________ _______
NS7B ________ ________________________ _______
________ ________ ________________________ _______
________ ________ ________________________ _______
________ ________ ________________________ _______
Press ENTER to continue or CANCEL to exitIf there are more than ten (10) CSM Groups, press Enter to display the next set of Groups, otherwise fill in the valid system name, Definition Base name, and initial control setting and press Enter.Another conversion panel is displayed.
CSM to TOM Conversion
Command ===>
TOM stores objects by default using the pattern: object name and system
name separated by a period e.g. TSO.SYS1
For CSM moveable objects, the default naming pattern is object name and
sysplex name separated by a period e.g. TSO.PLEX1. This is because a
moveable object can be moved between systems within a sysplex.
If you wish TOM to use a different pattern (such as object.sysname.sysplex)
enter it below. To accept the default pattern, leave the field blank and
press ENTER to continue.
The pattern can contain the following nodes: SYSPLEX, SYSNAME and OBJECT.
Object name pattern: OBJECT.SYSNAME.SYSPLEX
Press ENTER to continue or CANCEL to exitIn the Object name pattern field, enter the pattern that the new TOM objects will have and press Enter.For information about entering a name pattern for newly converted TOM objects, see Preparing-to-convert.
During the conversion, a dialog shows how many groups are being converted. When the conversion is complete, the TOM Conversion Log is displayed.
The TOM Conversion Log provides valuable information about the newly converted TOM object names and descriptions of the CSM object attributes in relation to TOM objects.
The following image shows an example of the TOM Conversion Log.
********************************* Top of Data **********************************
BMC Software TOM Conversion Log
Input CSM repository data set: 'BBTEST.TEST.BBIREPS'
Converted by ................. TESTER1 at 12:43 on 01/15/2008
TOMPLEX....................... TOMN1
Conversion status............. Test Mode!!! CSM Objects not converted.
Group: TEST Valid System: SYSB Definition Base: Test Definition Base
==============================================================================
General Group exceptions:
- Enable Plex not converted. TOM to TOM communication can be enabled by
specifying the same TOMPLEX in BBPARM member MAMPLXxx.
- Alert Queues not converted.
TOM issues exception messages to the Logger.
These messages can be captured with JRNL Rule(s) and converted to Alerts.
- Startup and Shutdown validation Rules in TOM are not being generated with
a Type. Therefore the Rules will match whether the specified message is
issued from a JOB, STC, or TSO.
Objects: Exception Notes:
-------- ----------------
*BBISS - Object renamed to BBISS.SYS1.TOMPLEX01
*BBISS - Start and Stop events converted to Startup and Shutdown validation
*BBISS Rules.
--------
*APPC - Object renamed to APPC.SYS1.TOMPLEX01
*APPC - Start and Stop events converted to Startup and Shutdown validation
*APPC Rules.
--------
Summary for group TEST: 2 objects converted and defined as SUSPEND.
To view objects, switch to Definition base: Test Definition Base.Not every object definition from CSM is converted automatically by the utility; however, the utility does provide messages that explain why a conversion did not take place. See Conversion-exception-messages for all possible messages that are returned from the conversion process and a brief description of what the messages mean.