Migrating Your CONTROL-M

Environment to the Latest

Version

Scott Fluegge
& Richard Sherman
Infospectrum Consulting
What is Migration?

›Upgrade!

Old New
Types of Migration

› In Place Vs. Parallel

In Place Migration

› Advantages
– Less Space Required
– Fewer System Resources Required
– No Port Conflicts

› Disadvantages
– No Burnin
– No Testing
– No Backout
– Higher Scheduling Impact (Down Time - Cutover)
Parallel Migration

› Advantages
– Testing
– Buy In
– Burn In
– Limited Down Time (Cutover)
– Simple Backout

› Disadvantages
– Possible Port Conflicts
– Greater Disk Space
– More System Resources
EM Migration Steps– In Place

› Validate EM Data
› BRING PROD EM DOWN
› Export EM Data
› Un-Install existing EM
› Install NEW EM
› Install New Clients (First uninstall where necessary)
› Configure New EM
› Import old EM Data
› Test new environment
› BRING PROD EM UP
› Migration Complete
EM Backout - In Place Migration

› BRING PROD EM DOWN

› Un-Install new EM
› Re-Install old EM (And all associated Fix Packs)
› Un-Install new clients
› Re-Install old clients where necessary (And all associated Fix Packs)
› Configure newly installed EM
› Import Data
› BRING PROD EM UP
› Backout Complete
EM Migration Steps– Parallel

› Install new EM
› Install new EM Clients
› Configure new EM
› Test new environment
› Validate old EM Data
› BRING PROD EM DOWN
› Export EM Data
› Import old EM Data
› BRING PROD EM UP
› Migration Complete
› Cleanup old install
EM – Parallel Migration Backout

› BRING NEW PROD EM DOWN

› START OLD PROD EM
› Backout Complete
Questions on EM Migration?
CONTROL-M Server Migration

› In Place Vs. Parallel

AND

› Migrate Vs. Upload

CTM Migrate Vs. Upload

› Migrate
– Advantages
• Migrates AJF
• Migrates Security
• Migrates Q Resources
• Migrates Shout Destinations
• Migrates Stats
• Migrates Node Groups
– Disadvantages
• May take longer
• Longer Down Time
CTM Migrate Vs. Upload

› Upload
– Advantages
• Fast
• Can be pre-staged to minimize down time
– Disadvantages
• Does not migrate AJF
• Does not migrate Security
• Does not migrate Q Resource Definitions
• Does not migrate Shout Destinations
• Does not migrate Stats
• Does not migrate Node Groups
CTM Migrate Vs. Upload

› How do you choose?

CONTROL-M - In Place - Comparison
CTM Migration Steps – In Place - Migrate CTM Migration Steps – In Place - Upload

Validate SERVER Data BRING PROD SERVER DOWN

BRING PROD SERVER DOWN Create Reports (Waiting Jobs, Q Res, Security, Shouts, Node Groups)

Export SERVER Data Un-Install existing SERVER

Un-Install existing SERVER Install NEW SERVER

Install NEW SERVER Configure New SERVER

Configure New SERVER Manually Create Q Res, Security, Shouts and Node Groups

Import old SERVER Data Migrate_dc (moves EM Defs to new release)

BRING PROD SERVER UP Upload Tables and Cals from EM

Migrate_dc (moves EM Defs to new release) BRING PROD SERVER UP

Monitor New Day Monitor New Day

Migration Complete Manually order jobs from previous day still waiting

Migration Complete
CONTROL-M - Parallel - Comparison
CTM Migration Steps – Parallel - Migrate CTM Migration Steps – Parallel - Upload

Install NEW SERVER (Use new ports) Install NEW SERVER

Configure New SERVER Configure New SERVER

Validate SERVER Data Create Reports (Waiting Jobs, Q Res, Security, Shouts, Node Groups)

BRING PROD SERVER DOWN Manually Create Q Res, Security, Shouts and Node Groups

Export SERVER Data Migrate_dc (moves EM Defs to new release)

Import old SERVER Data Upload Tables and Cals from EM

Change Ports to old values BRING PROD SERVER DOWN

BRING PROD SERVER UP BRING NEW PROD SERVER UP

Migrate_dc (moves EM Defs to new release) Monitor New Day

Monitor New Day Manually order jobs from previous day still waiting

Migration Complete Migration Complete

Questions on CTM Server Migration Steps?
Migration Tools

› Supplied by BMC
› Free and Downloadable
› Product Specific
› For 6.2.01:
– http://www.bmc.com/support/techdocs/LPH3S.6.2.01.html
› Check all pertinent values based on release
› Validation portion runs while products are up
› Export is database un-aware
The Migration Process

› Install New Release (Parallel Install)

› Download Tools
› Install (in both releases) Migration Toolset
› Run Validation
› Fix Reported Errors
› Export Data from Old Install
› Import into New Install
› Migrate Datacenter
Migration steps - Install

› Step 1
– Install New Release of CONTROL-M/EM
• Install the database & server components on a new environment (an alternative
Unix account for example)
• Install the client components on selective desktops. Note that the basic client
components (CONTROL-M/Desktop and CONTROL-M/EM GUI) can co-exist
with CONTROL-M/EM 6.1.03
• Get familiar with the new release
Migration steps – Download/Install

› Step 2 & 3 - http://www.bmc.com/support/techdocs/LPH3S.6.2.01.html

– Download, Install & execute the migration tool-kit on the base release
• Run the “install_migration” executable
• The CONTROL-M/EM 6.2.0x provides an interactive utility to be executed on all
supported base releases accessible through the “migration” utility located in the
“migration_export” directory
• Installation will determine whether the Export (prior version) or Import (6.2.01) utilities and
menu items are installed.
 Migration steps - Validation

› Step 4 – Execute the Validation

Report
– Executing it will verify the
correctness of the current data
with respect to the new release
• The report itself is kept in
“migration_export” directory
within a file named
“ValidityReport.out”
Migration steps - Resolve Errors

› Step 5 – Scrub Data

– The validation step can be executed over and over again – while the
production is up and running – with no direct effect on it.
– The validation step might generate 3 various levels of messages:
• ERROR – Indicates that job processing definitions contain values that are
inconsistent with 6.2.01 formats, and that these problematic values might affect
job scheduling.
• WARNING– Indicates that job processing definitions contain statements that
have no production meaning:
– an ON statement with no accompanying DO action
– a SHOUT statement with no destination
• INFORMATION– indicates that the data contains values that are no longer
relevant or supported in the new version. The data will automatically be corrected
during the “import” process; no manual changes are required or accepted
Migration steps - Export

› Step 6 - Export
– Run the “export” option at the migration menu
• Assure all components besides the database are shut down prior to actual export
to verify data consistency
• Export results are kept in:
– Unix – migration_export/ECSExportForMigration.tar
– Windows – migration_export/data/*
 Migration steps - Export

› Step 6 (cont)
– Migrated and non-migrated information

CONTROL-M/EM 5.0.09
Migrated Data Non-Migrated Data
■ Job processing definitions ■ Active jobs, conditions, and resources.
■ Calendar definitions These will be updated after a connection to CONTROL-M/Server is
■ Global conditions information (such established.
as prefixes) ■ Alerts
■ CONTROL-M definitions ■ Old nets information
■ System parameters ■ User authorizations (report can be generated to manually enter
■ Users list authorizations)

EM 6.0.05, 6.1.02, and 6.1.03

Migrated Data Non-Migrated Data
■ Job processing definitions ■ Active jobs, conditions, and resources.
■Calendar definitions These will be updated after a connection to CONTROL-M/Server is
■ Global conditions information (such as prefixes) established.
■ CONTROL-M definitions ■ Old nets information
■ System parameters
■ User authorizations and ViewPoint definitions
■ Alerts
Migration steps - Export
› Step 6 (cont)
– Control-M/Server Migrated and non-migrated information
CONTROL-M/Server
Migrated Data
■ Database data:
— Job processing definitions
— Calendar definitions
— Active environment
— Security definitions
— Configuration parameters
■ CONTROL-M/Server configuration
files:
— Configuration parameters
■ CONTROL-M/Agent parameters
■ System parameters
Non-Migrated Data
■ Configuration parameters:
— CTM_RT_PORT_NUMBER
— CONTROLM_DATABASE
— OS_PRM_SOCKET_PORT_NUM
— OS_PRM_LOCK_DIR (Unix only)
— OS_PRM_HOSTNAME (Unix only)
— CTMS_HOSTNAME
— CTMS_PORT_NUM
— TMP_PATH
■ CONTROL-M/Server configuration files:
— Process parameters
— Comments
■ Communication parameters:
— ECS port
— Minimum server processes (CS)
— Maximum server processes (CS)
■ Computer/account specific parameters:
For example, proclib: Executables path
Migration steps - Export Notes

› Security issues when migrating from ENTERPRISE/CS 5.0.09

– The 6.0.0x release introduces a different secured approach for account management
– making automatic migration of users impossible
– CONTROL-M/EM 6.2.0x offers a new tool that reports all existing security definitions
to a text file so it is easier to re-define them
5.0.09 Security Report

› Syntax:
$HOME/migrate_ecs/save_authorizations <user> <password>
– A report called save_authorizations.txt is created in the
$HOME/migrate_ecs/data directory
– This report is used after the migration process as a basis for the
authorizations that will need to be manually defined in the 6.2.01
environment
Migration steps - Import

› Step 7 - Import
– Import the data into the new environment and activate it
• Copy the output of the “export” step to the new environment
• If using ftp – assure binary transfer mode is used
• Assure all components but the database are shut down
• Activate the “migration” utility (can be found at the “migration_import”
directory) and select the “import” option
• Initiate the environment and start using the new CONTROL-M/EM

– The import step performs data adjustments that deals with database
schema changes and with all warning and information messages that were
left after the validation step
Migration steps – Migrate Datacenter

Old EM EM New EM Migrate New EM

Migration
Datacenter
Old CTM Old CTM New CTM

Gateway Gateway Gateway

CTM
Old CTM New CTM
Migration
Migration steps – Migrate Datacenter

› “migrate_dc” command line

Ex
tr a 1
cti EM Database
n gd
ata
Data Center C Data Center D
2 Migrate_dc
Migrating
data d ata t Data Center A Data Center B
t he r m a
o r ing w fo
St e ne
th
in General definitions
3
Migration steps – Migrate Datacenter

– With Migrate_DC, it is possible to separate applications that were scheduled

on the same server so they are
• Migrated to the new release in stages
• Physically separated to different CONTROL-M/Servers
– The command line flags supporting these functionality (all optional) are:
• Old_dc <name> - specify the source CONTROL-M/Server
• New_dc <name> - specify the target CONTROL-M/Server that should be defined in
the system prior the execution of the utility
• Table <name> - specify the name of the scheduling table to be migrated both from
one release to another and between CONTROL-M/Server

Note:This functionality is supported only when the CONTROL-

M/Servers involved are on the same platform (Unix, MVS etc.)
and the lower version involved is of 6.1.0x
Migration steps – Migrate Datacenter

› The migrate_dc utility converts CONTROL-M/Server job processing

definitions within the CONTROL-M/EM database.
› Compatible with versions:
– CONTROL-M/Server for Unix or Microsoft Windows version 2.24.0x
– CONTROL-M/Server for Unix version 6.x.xx
– CONTROL-M for OS/390 (any version)

– NOTE: There is no rollback procedure from changes made by the

migrate_dc utility. Before using the migrate_dc utility, backup all your data.
Migration steps – Migrate Datacenter

› What is performed:
› from 2.24.0x
– Updates the data center version
– Rearranges condition order to comply with the AND/OR logic of version
6.0.xx.
– Converts the INTERVAL value.
– Initializes the INTERVAL_FROM field.
– Generates errors when illegal characters), (, |, and blank are found in IN, OUT,
and DO CONDITION names.
– Updates job processing definitions to support the modified WEEKSCAL
parameter.

› CONTROL-M/Server for Unix version 6.1.0x or CONTROL-M for OS/390

– only the values of the INTERVAL parameter are converted
Migration steps – Migrate Datacenter

› Log on to a Windows computer where the CONTROL-M/EM server

components or the Administration facility is installed.
› migrate_dc -u <DBO name> -p <DBO password> -dc <data center>
› [-hostname <datacenter_hostname> ] [-port <datacenter_portnumber>]
› [-interval_from {S|E}] [-version {610|613|620}]

› Where:

– hostname is the data center host name (maximum length: 255

characters)
– port is the data center port number (range: 1024 – 65533)
– interval_from is either S or E.
Migration Complete!!

Old CONTROL
New CONTROL--M
M
Q&A