Control-M/EM migration considerations

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.00.

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.00 and Control-M for z/OS version 8.0.00

After upgrading to 9.0.00, 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