CONTROL-M/Server

Migration Guide

Supporting
Version 6.4.01 of CONTROL-M/Server for UNIX® and
Microsoft Windows

September 2008

www.bmc.com
 Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC Telephone 713 918 8800 or Fax 713 918 8000
2101 CITYWEST BLVD 800 841 2031
HOUSTON TX 77042-2827
USA
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000

© Copyright 2008 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent
and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and
logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
CONTROL-M/Server Migration GuideAll IBM trademarks that are referred to or displayed in the document are trademarks or
registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
ITIL® is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the
U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC.
Linux is the registered trademark of Linus Torvalds.
Oracle is a registered trademark of Oracle Corporation.
UNIX is the registered trademark of The Open Group in the US and other countries.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is
subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted
rights notices included in this documentation.

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF
THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to
restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and
DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD,
HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
 Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer
Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”

Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home.
From this website, you can
■ read overviews about support services and programs that BMC offers
■ find the most current information about BMC products
■ search a database for issues similar to yours and possible solutions
■ order or download product documentation
■ download products and maintenance
■ report an issue or ask a question
■ subscribe to receive proactive e-mail alerts when new product notices are released
■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and
telephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or
send an e-mail message to customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>,
such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:
■ product information
— product name
— product version (release number)
— license number and password (trial or permanent)
■ operating system and environment information
— machine type
— operating system type, version, and service pack or other maintenance level such as PUT or PTF
— system hardware configuration
— serial numbers
— related software (database, application, and communication) including type, version, and service pack or
maintenance level
■ sequence of events leading to the issue
■ commands and options that you used
■ messages received (and the time and date that you received them)
— product error messages
— messages from the operating system, such as file system full
— messages from related software

3
4 CONTROL-M/Server Migration Guide
Contents
Chapter 1 Migration overview 7
The Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Migrating data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Migrating from previous versions 13

Pre-migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Parallel and non-parallel installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installing the Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing the Migration Toolkit on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing the Migration Toolkit on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Ensuring data correctness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Exporting the earlier_version data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Importing the exported data to the new version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Appendix A Readiness report messages 23

Readiness report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Analyzing report messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Index 29

Contents 5
6 CONTROL-M/Server Migration Guide
 Chapter

1
1 Migration overview
This guide explains how to migrate CONTROL-M/Server data from earlier versions
to version 6.4.01. Versions that can be migrated are:

■ CONTROL-M/Server 6.1.03 UNIX and Windows all releases from the major one,
including all fix packs
■ CONTROL-M/Server 6.2.01 UNIX and Windows, all releases from the major one,
including all fix packs
■ CONTROL-M/Server 6.3.01 UNIX and Windows, all releases from the major one,
including all fix packs

The term earlier_version used in this guide refers to any of the above products.

CONTROL-M/Server data can be migrated

■ across platforms such as:

■ UNIX to UNIX
■ Windows to Windows
■ UNIX to Windows
■ Windows to UNIX

■ from one UNIX platform to another (for example, from Solaris to HP-UX-11)

■ between different database types. For example, from MSSQL/Oracle/Sybase to

MSSQL/Oracle/Sybase/ PostgresSQL.

NOTE
The removal of the earlier_version CONTROL-M/Server software and the installation of the
new software is handled separately and is not within the scope of this book. For information
on installing and uninstalling the CONTROL-M/Server software, see the CONTROL-M
Installation Guide.

You should be aware that configuration settings are not always transferred to the new
installation along with the data. For precise information, see Table 1 on page 9.

Chapter 1 Migration overview 7

The Migration Toolkit

If you have installed the full CONTROL-M solution, migration must be performed in
the following order:

1. CONTROL-M/EM

2. CONTROL-M/Server

3. CONTROL-M/Agents

This sequence is important as a new version of CONTROL-M/EM can work with an

earlier version of CONTROL-M/Server, but the opposite is not true.

BMC Software recommends planning for the new version well in advance.
Installation of the new CONTROL-M software and setting up the environment can be
accomplished in a relatively short time frame (from several hours to several days
depending on the complexity of your system). However, preparing the earlier_version
data for migration can take several weeks.

The best method of ensuring a smooth transition from the earlier_version to the new
version is to use the parallel installation method. For more information, see “Parallel
and non-parallel installations” on page 14.

NOTE
CONTROL-M/Agents should not be installed or upgraded until the new version of
CONTROL-M/Server is installed and the earlier_version data migrated.

The Migration Toolkit

The Migration Toolkit is used to test the earlier_version CONTROL-M/Server
database data (the data belonging to the version you are current using) and adjust it
as necessary to meet the requirements of the new version. It can be accomplished
directly in your current production environment without first having to install the
new version software.

There may be some data that cannot be adjusted while you are still using the current
version. This is usually due to new features implemented for the new version you are
about to install, which are not recognized by the current version. These occurrences
are listed in the individual messages of the Readiness report (see Appendix A,
“Readiness report messages” on page 23).

After you are satisfied that the current version data is fully ready for the new version,
you can transfer all the converted data to the new version environment and resume
production in a minimum amount of time.

8 CONTROL-M/Server Migration Guide

 Migrating data

Migrating data
The types of CONTROL-M/Server data that can and cannot be migrated are shown
in Table 1 and Table 2.

Table 1 Migrating data

Migrating Data Comments
Database data Types of database data:
■ Job processing definitions
■ Calendar definitions
■ Active environment
■ Security definitions
■ Configuration parameters

CONTROL-M/Server configuration Not all configuration parameters are migrated. See

files (config.dat, TimeZone.dat): Table 2.
CONTROL-M/Agent statuses The disabled agents maintain their status when
(AGSTAT directory) migrated from the export environment. statuses of the
non-disabled remote hosts and/or non-disabled
regular agents are changed to discovery status.
CONTROL-M/Agent parameters This directory contains pre-defined agent specific
(AGPRM directory) parameter files.
Manual conditions file ctmldnrs.dat This file will be migrated only if it exists in the default
(created by the ctmldnrs utility) <ctmHomeDir>/tmp directory.
System parameters N/A
SSL certifications SSL migration is not available when migrating from
UNIX to Windows or from Windows to UNIX.
The SSL kdb files on the import
environment are under SSL migration is available only when migrating from
<ctmServerHome>/ctm_server/data/ UNIX to UNIX and from Windows to Windows. The
SSL/cert directory. Secure Sockets Layer parameter must be set to
ENABLED.

This parameter can be viewed by running the

following command:

ctm_menu=> Parameter Customization => System

Parameters and Shout Destination Tables => System
Parameters => Next Page =>Secure Sockets Layer.
Lists of utilities permitted to be Located in the
activated by CONTROL-M/Agents. <ctmserverHomeDir>/data/AGDEFS/AGUTILS_PER
MIT file and the content of the AGPERMIT_UTILS
directory.
Remote agent maps The <ctmserverHomeDir>/data/AGSTAT_RJX
directory is migrated.
Remedy parameters All Remedy configuration parameters located in the
exported ctmHomeDir\data\config.dat file are
migrated to the new RemedyConf.xml file located in
ctm\<serverHomeDir>\data\remedy directory.

Chapter 1 Migration overview 9

Migrating data
Table 2 Non-migrating data
Non--migrating data
Configuration parameters
Configuration files
Communication parameters
Computer/account specific
parameters
CONTROL-M/Server SMTP
configuration settings
User Exit scripts
Diagnostic messages recorded from
stored procedures (SPs) in the
CONTROL-M/Server database
which were set by ctmspdiag utility
Parameters for Communicating with These new values are assigned during migration and
the Agent Platform (including new overwrite any existing parameter values.
values).
Database configuration parameters
10 CONTROL-M/Server Migration Guide
Comments
■ CTM_RT_PORT_NUMBER
■ CONTROLM_DATABASE
■ OS_PRM_SOCKET_PORT_NUM
■ OS_PRM_LOCK_DIR
■ OS_PRM_HOSTNAME
■ CTMS_HOSTNAME
■ CTMS_PORT_NUM
■ TMP_PATH
■ MAIL_HANDLER
■ CD_IPC_IN
■ CD_IPC_OUT
■ CTM_SEM_KEY_ID
■ CTM_SEM_TIMEOUT
■ MAX_GET_HOST_RETRIES
■ Remedy related parameters
■ Process parameters
■ Comments
■ CONTROL-M/EM port
■ Minimum server processes (CS)
■ Maximum server processes (CS)
For example, proclib: Executable path
N/A
N/A
N/A
■ Communication Protocol Version: 07
■ Unavailability Shout Urgency: R
■ Persistent Connection: N
■ Maximum Concurrent Sessions: 256
■ Allow Agent Disconnection: Y
■ Session Idle Time-out: 900
■ Maximum Disconnect Time: 300
N/A
 Migrating data

WARNING
After migration, some configuration parameters such as
WD_ERROR_HANDLER_SCRIPT_FILE, WD_USEREXIT_# _SCRIPT_FILE may need to be
adjusted to the new environment values.

Chapter 1 Migration overview 11

Migrating data

12 CONTROL-M/Server Migration Guide

 Chapter

2
2 Migrating from previous versions
This chapter guides you through the process of migrating CONTROL-M/Server data
from an earlier_version.

The migration procedure is performed using the sequential steps presented in the
following table:

Table 3 Migration Steps

Step
1. Installing the Migration Toolkitt
2. Ensuring data correctness
3. Exporting the earlier_version data
4. Importing the exported data to the new
version
Explanation
The Migration Toolkit must be installed in
the earlier_version for data validation and
export.
Use the Migration Toolkit to examine the
earlier_version data for compatibility with the
new version format. This process will
normally need to be run multiple times.
After each run, you must correct all errors
and re-run until no more errors are detected.
Use the Migration Toolkit to export the
error-free data to a location available to the
new version.
Import the error-free data to the new version

Chapter 2 Migrating from previous versions 13

Pre-migration considerations

Pre-migration considerations
Before beginning the migration procedure consider the following:

■ Back up the current environment.

■ If you have installed new versions of both CONTROL-M/EM and

CONTROL-M/Server, you must migrate CONTROL-M/EM first before migrating
CONTROL-M/Server.

■ If you already completed the process of ensuring data correctness or have already
exported the data with an older version of the Migration Toolkit, you must
perform the procedure again using the new Migration Toolkit.

■ Acquire the necessary database password or administrator passwords.

■ Until CONTROL-M/Server migration is completed, do not perform a definition

download from the earlier_version CONTROL-M/Server to the new
CONTROL-M/EM. This operation could generate invalid data in the new
CONTROL-M/Server environment.

■ If your environment uses a database server that is not case-sensitive, see the
appendix called “Working with Databases that are not Case-Sensitive” in the
CONTROL-M Installation Guide.

■ If you are running a CONTROL-M/Server for UNIX or Windows version earlier

than version 6.1.03, you must first upgrade and migrate your current version to
6.1.03 or 6.2.01 before installing and migrating to the 6.4.01 version.

■ Migration from CONTROL-M/Server version 6.3.01 to 6.4.01 requires more disk

space for the entire installation. The required disk space has increased by:
— 50% for Oracle
— 70% for Sybase
— 20% for MSSQL

Parallel and non-parallel installations

The parallel installation method is consider the best method as the earlier_version can
remain in use until the new version is in place and has been tested. Using this
method, the new version can be set up, tested, and fine-tuned without uninstalling
the earlier_version and disturbing production.

If you do not have the resources to set up a new version environment in parallel to
the current environment, before uninstalling the earlier_version software you need to:

14 CONTROL-M/Server Migration Guide

 Installing the Migration Toolkit

1 Validate the existing data before uninstalling the earlier_version.

2 Export the validated data to a location where it will be available for import to the
new version.

3 Uninstall the earlier_version.

4 Install the new version of CONTROL-M/Server.

5 Import the earlier_version data into the new version.

The parallel installation method uses the same set of instruction except for step 3.
With this method, the earlier_version can be uninstalled after the full migration
procedure is completed.

Installing the Migration Toolkit

The Migration Toolkit is used to export CONTROL-M/Server information from an
earlier version. The latest version of the Migration Toolkit must be installed in the
earlier_version environment. If an older version of the Toolkit is detected during
installation, it is backed up to the migration-export.PREVIOUS directory in the
earlier_version CONTROL-M/Server environment.

Installing the Migration Toolkit on UNIX

To install the Migration Toolkit on UNIX

1 Log on to CONTROL-M/Server account and navigate to the home directory.

2 Download the install_migration script for the UNIX Migration Toolkit to the
home directory. The migration toolkit is available on the BMC Software Customer
Support Web site (http://www.bmc.com/support_home) in solution
SLN000015061431.

3 Run the install_migration command.

4 To check if the installation was successful, open the following installation log file:

${HOME}/log/cts_migration_install_log.txt

Chapter 2 Migrating from previous versions 15

Installing the Migration Toolkit on Windows

Installing the Migration Toolkit on Windows

Before you begin

If you are working with a non-English version of Windows, before installing the
Windows Migration Toolkit, set the system locale and language settings to English as
follows:

1 Select Western Europe and United States in Control Panel => Regional and
Language Options for the system to receive all messages in English.

2 Select English (US) in Control Panel => Regional and Language Options => to set
the locale to English.

After installation you can reconfigure your computer to operate in a language other
than English. For more information, see the CONTROL-M Language Customization
Guide.

To install the Migration Toolkit on Windows

1 Log on to CONTROL-M/Server user and navigate to the CONTROL-M/Server

folder.

2 Download the install_migration.exe self-extracting Zip file containing the

Windows Migration Toolkit to the %TEMP% directory. The migration toolkit is
available on the BMC Software Customer Support Web site
(http://www.bmc.com/support_home) in solution SLN000015061431.

3 Run install_migration.exe to extract the Migration Toolkit files.

4 To check if the installation was successful, review the installation log file:

%TEMP%\ctms_migration_install_log.txt

Ensuring data correctness

As a result of enhancements to the CONTROL-M solution in the past several
versions, some of the current scheduling definitions might function differently when
migrated to the new release.

When the Migration Toolkit validation and export processes are performed, the
earlier_version data is checked to ensure that it conforms to the new version rules.

All job processing definitions are checked at the time of validation.

16 CONTROL-M/Server Migration Guide

 Ensuring data correctness

When a problem with the data is detected, a message is written to the Readiness
report as described below in step 2.

To check validity and to ensure that your earlier_version definitions will function
correctly in the new release, perform the following data validation procedure.

NOTE
If you are working with a non-English version of Windows, before activating the Migration
Toolkit and running any command, set the system locale and language settings to English as
described in “Installing the Migration Toolkit on Windows” on page 16

To check CONTROL-M/Server data validity

1 Ensure that one of the following is your working directory and then run the
migration command to activate the Migration Toolkit.

■ $HOME/migrate_ctm for Unix

■ <ctmserverHome>\migrate_ctm for Windows

2 Choose the Validation option in the Migration menu. This step generates the
Readiness report.

TIP
It is recommended that you stop running CONTROL-M/Server, in order to assure that you
are generating the most recent report.

3 Analyze the results and correct all errors. Data that generated informational
messages and warnings will be automatically adjusted when imported to the new
version as specified in the Readiness report.

You can view the Readiness report online by selecting View Readiness Report from
the Migration menu. For a printed copy of the report, print the ValidityReport.out
file from the migrate_ctm directory. Alternatively, you can use a text editor to view
the report.

All errors must be corrected before importing the data. Due to new features
implemented for the version you are about to install, some errors can be corrected
only when the current version is about to be shut down for the final time.

Information on these and other errors is listed in the Readiness report. Just before
shutdown, these errors must be corrected and a final version of the data exported
using the Migration Toolkit. For information about analyzing the Readiness report,
see “Messages” on page 24.

Chapter 2 Migrating from previous versions 17

Exporting the earlier_version data

Repeat the data validity check until no error messages are generated (except for
errors that need to be corrected after the new version is running). When there are no
error messages, the data is ready to be exported (see “Exporting the earlier_version
data”).

Iterations of the report are stored in the same directory. A sequence number is
appended to the report name so that you can compare the reports. Readiness report
message types are described in Appendix A.

Exporting the earlier_version data

Before beginning to export the earlier_version data perform the following:

■ Shut down the earlier_version of CONTROL-M/Server and CONTROL-M/Server

Configuration Agent (starting from version 6.3.01)
■ Make sure the database server is up

NOTE
If you are working with a non-English version of Windows, before activating the Migration
Toolkit and running any command, set the system locale and language settings to English as
described in “Installing the Migration Toolkit on Windows” on page 16

To export the CONTROL-M/Server earlier version data

1 Ensure that one of the following is your working directory and then run the
migration command to activate the Migration Toolkit.

■ $HOME/migrate_ctm for Unix

■ <ctmserverHome>\migrate_ctm for Windows

2 Run Export from the menu.

The exported files are saved in the following location:

■ $HOME/ExportForMig.tar for Unix.

■ <ctmserverHome>\migrate_ctm\backup_ctm directory for Windows.

The Export step also generates another copy of the Readiness report,
ValidityReport.out, in the migrate_ctm directory.

3 Copy the exported files to a location that can be accessed by the new release
environment. Do not change the exported file names as the import process requires
the files to have the same names given to them by the export process.

18 CONTROL-M/Server Migration Guide

 Importing the exported data to the new version

4 When migration from:

■ Windows to UNIX:

A. Backup the content of the <ctmserverHome>\migrate_ctm\backup_ctm

directory of the exported Windows environment.

B. Copy the content of <ctmserverHome>\migrate_ctm\backup_ctm directory of

the exported Windows environment to $HOME/migrate_ctm/backup_ctm
directory in the UNIX account.

■ UNIX to Windows: Copy the content of $HOME/migrate_ctm/backup_ctm

directory from the exported UNIX account to the
<ctmserverHome>\migrate_ctm\backup_ctm directory in the Windows
environment.

WARNING
If the exported files are copied using FTP, they must be transferred in binary mode.

At this point, the entire earlier_version environment can be backed up and removed.
For details on how to uninstall the earlier_version, see the CONTROL-M Installation
Guide.

Importing the exported data to the new

version
If you have not yet installed the new version of CONTROL-M/Server 6.4.01, you
should do so now. You should also check for and install the latest
CONTROL-M/Server 6.4.01 fix packs. You can access the latest Fix Packs at the
following site:

ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Server_for_UNIX_a
nd_Microsoft_Windows

To install CONTROL-M/Server and the latest Fix Packs, see the CONTROL-M
Installation Guide.

NOTE
You do not have to install the Migration Toolkit, because it is integrated in to the
CONTROL-M/Server 6.4.01 installation.

Chapter 2 Migrating from previous versions 19

Importing the exported data to the new version

If you plan to uninstall the earlier_version of CONTROL-M/Server, you must save the
exported files to a location outside the account as it will be erased when the earlier_version is
uninstalled.

NOTE
If you are working with a non-English version of Windows, before activating the Migration
Toolkit and running any command, set the system locale and language settings to English as
described in “Installing the Migration Toolkit on Windows” on page 16

Before you begin

Before beginning to import the earlier_version data perform the following:

■ Shut down the earlier_version of CONTROL-M/Server and CONTROL-M/Server

Configuration Agent (starting from version 6.3.01)
■ Make sure the database server is up

NOTE
You can view the status of the CONTROL-M/Server, CONTROL-M/Server Configuration
Agent, and database server by running ctm_menu => CONTROL-M Manager => Check All
in the command line window.

To import the CONTROL-M/Server data

1 Ensure that the exported earlier_version files are accessible to the new
CONTROL-M/Server version and import the export data as follows:

A Make <CONTROL-M_home>\migrate_ctm your working directory.

B Run the migration command to activate the Migration Toolkit.

C Activate the import process from the Migration Toolkit menu.

The import process converts the data and imports it into the new environment.
Data for which informational messages and warnings were generated are
automatically adjusted to comply with the new version format.

20 CONTROL-M/Server Migration Guide

 Importing the exported data to the new version

2 To continue working with earlier_version CONTROL-M/Agents, proceed as

follows:

A If CONTROL-M/Server had no specific CONTROL-M/Agent communication

parameters defined, configure CONTROL-M/Server with the communication
protocol that matches the current CONTROL-M/Agent version (this step is
necessary because the default communication protocol version for
CONTROL-M/Agent in CONTROL-M/Server 6.4.01 is 08). For details, see the
Maintenance chapter in the CONTROL-M Administrator Guide.

B If you have jobs for which no node group is defined (these jobs ran on a local
agent in an earlier_version CONTROL-M/Server), and your
CONTROL-M/Server 6.4.01 installation is located on a different computer from
the Agent, you will need to either point these jobs to the agent on the
earlier_version computer, or configure the local agent on the
CONTROL-M/Server 6.4.01 computer.

C If you installed CONTROL-M/Server on another machine, reconfigure your

CONTROL-M/Agents so that they point to the new host name and port. For
details, see the CONTROL-M Administrator Guide.

3 Migrate CONTROL-M/Server definitions in the CONTROL-M/EM database from

the earlier_version to version 6.4.01 by running the migrate_dc utility in the
CONTROL-M/EM environment. For more information on the migrate_dc utility,
see the CONTROL-M /Enterprise Manager Migration Guide.

NOTE
If you migrated CONTROL-M/Server to a different computer, reconfigure the host
name and port system parameters in the CONTROL-M/EM database. For more
information, see the CONTROL-M Administrator Guide.

4 If you installed CONTROL-M/Server in parallel, you may need to customize

configuration parameters that are computer or account specific. This information is
not migrated from the earlier_version in a parallel installation. Configuration
parameters that refer to specific path names may also need to be adjusted.

5 If you are migrating from CONTROL-M/Server version 6.1.03, you will need to
configure the CTM_ADJUST_COND_SCOPE parameter manually in the
config.dat file as follows:

A If you want this parameter to relate to jobs at the group level, set the value of
CTM_ADJUST_COND_SCOPE to GROUP.

B If you want this parameter to relate to jobs at the at the active jobs file level, set
the value of CTM_ADJUST_COND_SCOPE to AJF.

Chapter 2 Migrating from previous versions 21

Importing the exported data to the new version

For more information on the CTM_ADJUST_COND_SCOPE parameter, see the

CONTROL-M Administrator Guide.

NOTE
For more information about specific parameters that are migrated, see “Migrating
data” on page 9.

6 If the ctmldnrs.dat file is migrated, it is placed in the CONTROL-M/Server home

directory (<ctmHomeDir>). From there you can copy the file to the default location
(<ctmHomeDir>/ctm_server/tmp) or another location as required.

NOTE
On Unix, the ctmldnrs.dat is deleted from the default location
(<ctmHomeDir>/ctm_server/tmp) when CONTROL-M/Server is started.

7 BMC Software recommends that immediately after you have completed data
import and migration of CONTROL-M/Server definitions, you synchronize your
data by downloading it to CONTROL-M/EM.

Downloading the data populates CONTROL-M/EM version 6.4.01 with the

corrections that you performed manually in CONTROL-M/Server as outlined in
the Readiness report. It will also enable you to control jobs in the
CONTROL-M/EM Active Jobs file (for example, a request for job order or rerun).

However, if the scheduling tables in CONTROL-M/Server are not fully

synchronized with those in CONTROL-M/EM (that is, there are jobs that reside
only on one side, or corresponding jobs on both sides that are not identical), the
download operation will overwrite the definitions in CONTROL-M/EM with
those from CONTROL-M/Server.

8 CONTROL-M/Agents connected to the migrated CONTROL-M/Server can be

upgraded to 6.4.01 from this point onward. Although not required, this upgrade
will allow utilization of the newest Agent functionality.

9 Manually remove the directories of the Migration ToolKit from the earlier_version
environment.

10 You can now uninstall the earlier_version (if you have not already done so).

22 CONTROL-M/Server Migration Guide

 Appendix

A
A Readiness report messages
Messages are prefixed according to message type. Each message type has a unique
prefix describing the nature of the message as explained in the following table.

Prefix Description
ERR Error
Error messages indicate that job processing definitions contain values that are
inconsistent with new version formats. These values might affect job
scheduling.

You must manually correct the errors identified in job processing definitions
before continuing the migration.

Errors in a job in the Active Jobs file must be corrected, or the job must
removed from the file. If you can, manually correct the errors. If not, the job
can be removed by the New Day procedure at the beginning of the next day.
Otherwise, you can manually request the job to be deleted during the next
daily maintenance.).
INFO Information
These messages indicate 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. The automatic changes will not affect your new version scheduling
environment.
WRN Warning
These messages indicate that job processing definitions in your current
environment contain statements that have no production meaning. For
example, an ON statement with no DO action, or a SHOUT statement with no
destination.

You can correct these warning situations (for example, you can add a DO
action to an ON statement, or a destination to a SHOUT statement). However,
if you choose not to correct these warnings, the problematic statements will be
removed during the “import” process to the new version. These changes will
not affect your scheduling environment.

Appendix A Readiness report messages 23

Readiness report format

Readiness report format

Each problem in the Readiness report is presented in a format similar to the
following:

msg_code message_text
___________________________________________________
Error Code: entity_name [entity_name] [entity_name]
xxxnn aaaaaaaaa
xxxnn bbbbbbbbb etc.
xxxnn ccccccccc

Example

This example displays a problem with the quantitative resource name in a job
processing definition:

Error ERR100:Quantitative resource name cannot be set to a blank value

____________________________________________________________________________________
Code Scheduling Table Name Job NO Job Name Mem Name
----- --------------------- -------- ---------- -------------------------------
ERR100 t 44314

Analyzing report messages

Actions that need to be taken are based on the message type as explained in the
following table.

If the report contains: Appropriate user action

ERR messages Correction of errors is mandatory.
WRN messages Correction of the messages is optional.
INF messages None.

Messages
ERR01 Periodic calendar has “Y” or “N” values

Explanation: The periodic calendar contains invalid Y or N values. Only regular

(non-periodic) calendars can have Y and/or N values.
System Action: The export procedure cannot process the data.

24 CONTROL-M/Server Migration Guide

 Messages

User Response: Verify that the calendar is a periodic calendar and delete all Y and N
values. If you determine that the calendar is a regular calendar, ensure that the
calendar has only N and Y values. You can use CONTROL-M/EM Desktop or
CONTROL-M/EM utilities to define the calendars correctly.

ERR02 Condition in the Conditions file contains an invalid date: **** or $$$$

Explanation: **** and $$$$ cannot be specified as the date for a condition in the
Conditions file.
System Action: The export procedure cannot process the data. The system may issue
other error messages to this report that indicate which job processing definitions
create or use these improperly named conditions.
User Response: Delete the condition from the Conditions file, and reenter the
condition with a valid date. (You can use the Conditions window to delete and add
the condition.) Also, correct the source of the condition (for example, an OUT
statement or a script that invokes a CONTROL-M utility).

ERR03 Condition name in the Conditions file contains one or more of the following
invalid characters: “(“, “)”, “|” and/or an embedded space

Explanation: Condition names cannot contain the “(“, “)”, or “|” characters or
embedded spaces.
System Action: The export procedure cannot process the data. The system might issue
other error messages to this report that indicate which job processing definitions
create or use these improperly named conditions.
User Response: Use the Conditions window to delete the condition from the
Conditions file, and reenter the condition with a valid name. Also, correct the source
of the condition (for example, an OUT statement or a utility) and any jobs that use the
condition as an IN condition.

ERR100 Quantitative resource name cannot be set to a blank value

Explanation: .Quantitative resource names cannot have a blank value. The

problematic quantitative resource name appears in the indicated job processing
definition.
System Action: The export procedure cannot process the data.
User Response: Specify a valid value for the resource name, or delete the resource
from the job processing definition.

ERR101 Quantitative resource name in the Active Jobs file cannot be set to a blank
value

Explanation: .Quantitative resource names cannot have a blank value. The

problematic quantitative resource name appears in the indicated job processing
definition in the Active Jobs file.
System Action: The export procedure cannot process the data.

Appendix A Readiness report messages 25

Messages

User Response: In the Active Jobs file, manually specify a valid value for the resource
name, or delete the resource from the job.

ERR16 Quantitative resource has a quantity value of zero

Explanation: Zero is an invalid quantity for a Quantitative resource. The minimum

quantity is 1. The problematic resource quantity appears in the indicated job
processing definition.
System Action: The export procedure cannot process the data.
User Response: Specify a quantity of 1 or more for the resource, or delete the resource
from the job processing definition.

ERR17 Quantitative resource in the AJF has a quantity value of zero

Explanation: Zero is an invalid quantity for a Quantitative resource. The minimum

quantity is 1. The problematic resource quantity appears in the indicated job in the
Active Jobs file.
System Action: The export procedure cannot process the data.
User Response: In the Active Jobs file, manually specify a quantity of 1 or more for the
resource, or delete the resource or the job.

ERR93 More than one IN condition of the job has a row order of 1

Explanation: The IN conditions of a job in the Active Jobs file are not ordered, since
more than one IN condition has a row order of 1.
System Action: CONTROL-M/Server cannot automatically decide the correct order of
the IN conditions, and therefore the export procedure cannot process the data.
User Response: You can do one of the following:
■ Redefine the conditions of the job using Zoom & Save in CONTROL-M/Enterprise
Manager.
■ Remove the job. Either remove it manually, or wait until the New Day procedure
removes it automatically.

If you are migrating from version 6.1.03, install the latest fix pack in order to prevent
newly created jobs from having this problem.

ERR94 More than one OUT condition of the job has a row order of 1

Explanation: The OUT conditions of a job in the Active Jobs file are not ordered, since
more than one OUT condition has a row order of 1.
System Action: CONTROL-M/Server cannot automatically decide the correct order of
the OUT conditions, and therefore the export procedure cannot process the data.

26 CONTROL-M/Server Migration Guide

 Messages

User Response: You can do one of the following:

■ Redefine the conditions of the job using Zoom & Save in CONTROL-M/Enterprise
Manager.
■ Remove the job. Either remove it manually, or wait until the New Day procedure
removes it automatically.

If you are migrating from version 6.1.03, install the latest fix pack in order to prevent
newly created jobs from having this problem.

Appendix A Readiness report messages 27

Messages

28 CONTROL-M/Server Migration Guide

 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index
Symbols
.tar file, saving 20 I
importing
B exported data 19
install_migration script 15
BMC Software, contacting 2 install_migration.exe file 16
invalid characters
error message 25
C invalid date
error message 25
configuration parameters 21
CONTROL-M/Agent 22
reconfiguration 21
customer support 3
L
language settings
Windows 16
D locale settings 16

data
synchronization 22
M
messages
E analyzing 24
prefixes for 23
embedded space Readiness report 24
error message 25 migrating
error messages 23 overview 7
executable files. See files
exporting
considerations 14
saving .tar file before uninstalling 20
N
non-English versions of Windows 16

F
files
P
install_migration script 15 periodic calendar
install_migration.exe 16 error message 24
ValidityReport.out 17 port 21
prefixes, message 23
product support 3
H
host name 21
Q
quantity zero

Index 29
 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

error message 26

R
Readiness report 23
reconfiguring
CONTROL-M/Agents 21
host name and port 21
regional settings 16

S
support, customer 3
synchronizing data 22

T
tar file. See files 20
technical support 3

V
validating earlier_version data 16
ValidityReport.out file 17

30 CONTROL-M/Server Migration Guide

Notes
*70705*
*70705*
*70705*
*70705*
*70705*