Control-M/EM migration considerations

During the migration of Control-M/EM data, the following data files are migrated:

DirectoryServiceType.cfg (see DirectoryServiceType.cfg parameters)
em.plc
emkey.kdb
tree.bin
RemedyConf.xml
remedy.pwd

In addition, the Defaults.rsc files in the <EM_HOME>/etc/resource and <EM_HOME>/etc/site/resource directories of the old and new environments are merged, to preserve the customized values in both environments.

NOTE: If you want to migrate data from version 9.0.00 to version 9.0.19 or higher, the recommended migration process depends on your plans for Compatibility Mode:

If you want Compatibility Mode turned on, install the base version 9.0.00 and then install fix pack 9.0.00.100 or higher on the new host, migrate your data, and then upgrade it to version 9.0.19 or higher. This sets Control-M/EM server with Compatibility Mode on, which enables Control-M clients with version 9.0.00 to connect to Control-M/EM 9.0.19 or higher.
If you are not interested in turning on Compatibility Mode, migrate data from version 9.0.00 directly to version 9.0.19 or higher.

The following table describes the Control-M/EM migration considerations before you migrate Control-M/EM.

Item	Description	Action
LDAP user definitions in Control-M	Consider the following cases: LDAP authentication is configured in Control-M/EM version 7.0.00 (or 8.0.00 fix pack 2 or earlier) and Control-M for z/OS is connected to Control-M/EM. Control-M for z/OS users are managed in RACF. LDAP authentication is configured in Control-M/EM version 7.0.00 and the cross-platform Control-M CTMSEC utility is used. Job actions might not pass Control-M security for these users after migration to 9.0.19.	Do the relevant action: In the Control-M for z/OS RACF interface, cancel the User exit used to map user short names to long names. In the cross-platform Control-M CTMSEC utility, update the user name definitions from long format (user@domain) to short format (user) that is entered during login.
Enabling SYNC mode between Control-M/EM version 9.0.19 and Control-M for z/OS version 8.0.00	After upgrading to 9.0.19, a special user must be defined in Control-M for z/OS to enable automatic synch with Control-M/EM.	Define a Control-M/EM CTMSYNC user in Control-M for z/OS.

Item

Description

Action

LDAP user definitions in Control-M

Consider the following cases:

LDAP authentication is configured in Control-M/EM version 7.0.00 (or 8.0.00 fix pack 2 or earlier) and Control-M for z/OS is connected to Control-M/EM. Control-M for z/OS users are managed in RACF.
LDAP authentication is configured in Control-M/EM version 7.0.00 and the cross-platform Control-M CTMSEC utility is used.

Job actions might not pass Control-M security for these users after migration to 9.0.19.

Do the relevant action:

In the Control-M for z/OS RACF interface, cancel the User exit used to map user short names to long names.
In the cross-platform Control-M CTMSEC utility, update the user name definitions from long format (user@domain) to short format (user) that is entered during login.

Enabling SYNC mode between Control-M/EM version 9.0.19 and Control-M for z/OS version 8.0.00

After upgrading to 9.0.19, a special user must be defined in Control-M for z/OS to enable automatic synch with Control-M/EM.

Define a Control-M/EM CTMSYNC user in Control-M for z/OS.

Parent Topic

Migration planning process