Control M em Migration

CONTROL-M/Enterprise Manager
Migration Guide
Supporting
Version 6.4.01 of CONTROL-M/Enterprise Manager
August 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

2101 CITYWEST BLVD
HOUSTON TX 77042-2827
USA
Telephone
713 918 8800 or

800 841 2031
Fax
(01) 713 918 8000
Fax
713 918 8000
Outside United States and Canada

Telephone
(01) 713 918 8800
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.
z/OS is a trademark or registered trademark 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
CONTROL-M/EM Migration Guide
Contents
Chapter 1
Migration overview
The Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Migrated data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2
Migrating information from previous versions
13
Pre-migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing to migrate a non-English locale on UNIX . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ensuring data correctness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting the earlier_version data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing the exported data to the new version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
15
15
16
18
20
22
Appendix A
23
CONTROL-M/EM optional migration procedures
Synchronizing CONTROL-M/Server job processing definitions. . . . . . . . . . . . . . . . . 23

Migrating SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Migrating asc_ebc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix B
Whats different
27
Appendix C
Readiness report messages
55
Readiness report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Analyzing report messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Appendix D
BMC Batch Impact Manager and CONTROL-M/Forecast migration

procedures
Migrating Remedy system parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Migrating CONTROL-M/Server New Day Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting New Day Time migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating BMC Batch Impact Manager exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting BMC Batch Impact Manager exceptions . . . . . . . . . . . . . . . . . . .
Migrating CONTROL-M/Forecast exception conditions . . . . . . . . . . . . . . . . . . . . . . .
Migrating CONTROL-M/Forecast Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating BMC Batch Impact Manager Web Application settings from an
earlier_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
63
64
64
64
66
66
68
69
69
5
Re-activating CONTROL-M/Forecast and BMC Batch Impact Manager . . . . . . . 69

Appendix E
CONTROL-M/EM Migration Toolkit debugging mechanism
71
Tables
Migrated and non-migrated information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration from version 6.1.03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Usability changes from version 6.2.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Usability changes from version 6.3.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables
11
13
27
38
45
48
53
Chapter
Migration overview
This guide explains how to migrate CONTROL-M/EM data from earlier versions to
the version described in this guide.
All references in this chapter to CONTROL-M/Server also include CONTROLM/Server for z/OS and CONTROL-M/Server for Distributed Systems
NOTE
Special migration considerations for CONTROL-M/EM:
Review the changes that have been made for this version, especially the sizing guidelines
for migrating from CONTROL-M/EM earlier versions to the current version. For
information on sizing guidelines and other changes, see Appendix B, Whats different
on page 27.
Database data from earlier versions of CONTROL-M/EM cannot be accessed by the new
version until the data is restructured to the new version format using the procedures
described in this guide.
Migration is the process of moving the database data from an earlier version of
CONTROL-M/EM to a new version.
Note that the removal of the earlier_version CONTROL-M/EM 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/EM
software, see the CONTROL-M/Enterprise Manager Installation Guide.
Migration of data can be performed across accounts (UNIX), computers, and
platforms. You should be aware that configuration settings are not always transferred
to the new installation along with the data.
A first time installation of CONTROL-M/EM is the only circumstance for which
migration is not performed as there is no previous data to carry over to the new
version.
Earlier versions that can be migrated to the current version are listed in Table 1.
Chapter 1 Migration overview
The Migration Toolkit
If you have installed the full CONTROL-M solution, migration must be performed in
the order listed below. This sequence is important as a new version of CONTROLM/EM can work with an earlier version of CONTROL-M/Server, but the opposite is
not true.
1. CONTROL-M/EM
2. CONTROL-M/Server
3. CONTROL-M/Agents
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. This involves installing the new
version on a separate computer (on UNIX the new software can be installed in a
separate account on the same computer) and leaving the earlier_version in place. Using
this method, the new version can be set up, tested, and fine-tuned without disturbing
production.
The Migration Toolkit

The Migration Toolkit is used to test the earlier_version CONTROL-M/EM 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 C,
Readiness report messages on page 55).
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.
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:
10
Migrated data
1 Validate the existing data.

2 Export the validated data to a location where it will be available for import to the
new version.
Migrated data
The CONTROL-M/EM migration procedure migrates all permanent scheduling
definitions data.
Active data containing status information within the current production environment
is not migrated by the migration procedure. However, this data is refreshed from the
production CONTROL-M/Server(s) once new connections between the new version
of CONTROL-M/EM and the CONTROL-M/Server(s) are re-established. The data
migrated by the CONTROL-M/EM migration procedure is listed in Table 1.
The CONTROL-M/EM application data that can be migrated is independent of the
installed database software (for example, Sybase, Oracle, MSSQL).
Table 1
Migrated and non-migrated information
Migrated Data
Non-Migrated Data
CONTROL-M/EM versions 6.1.03, 6.2.01, and 6.3.01
Job processing definitions

Calendar definitions
Global conditions information (such
as prefixes)
CONTROL-M definitions
System parameters
User authorizations, ViewPoint
definitions, and audit activities
Alerts
BMC Batch Impact Manager
exceptions
CONTROL-M/Forecast historical
data from versions 6.2.01 or 6.3.01
(optional)
CONTROL-M/Forecast manual
conditions from versions 6.2.01 or
6.3.01
CONTROL-M/Forecast and BMC
Batch Impact Manager rules 6.4.01
Active jobs, conditions, and resources.

These will be updated after a connection
to CONTROL-M/Server is established.
Old nets information
Chapter 1
Migration overview
11
Migrated data
12
Chapter
Migrating information from previous

versions
2
This chapter guides you through the process of migrating CONTROL-M/EM data
from an earlier_version of CONTROL-M/EM. You can migrate CONTROL-M/EM
data across UNIX and Windows platforms.
NOTE
If BMC Batch Impact Manager was installed in the earlier_version environment, follow the
migration instructions in Appendix D, BMC Batch Impact Manager and
CONTROL-M/Forecast migration procedures on page 63.
The migration procedure is performed using the sequential steps presented in the
following table:
Table 2
Migration Steps
Step
Explanation
1. Installing the Migration Toolkit
The Migration Toolkit must be installed in

the earlier_version (for data validation and
export) and the new version (for importing
the validated data).
2. Ensuring data correctness
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.
3. Exporting the earlier_version data
Use the Migration Toolkit to export the

error-free data to a location available to the
new version.
4. Importing the exported data to the new

version
Import the error-free data to the new version
Chapter 2
13
Pre-migration considerations
Pre-migration considerations
Backup the current environment.
Uninstall all old Migration Toolkit software.
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.
If you are migrating both CONTROL-M/EM and CONTROL-M/Server, 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 or CONTROL-M/Server. This operation could generate
invalid data in the new CONTROL-M/EM or CONTROL-M/Server environment.
If you want to migrate your CONTROL-M/EM database configuration

parameters, you must do so before installing the new release. The new release
installation will automatically look for the database configuration file exported
from the earlier_version. For more information, see Appendix A,
CONTROL-M/EM optional migration procedures on page 23.
If you are running CONTROL-M/Server for UNIX or Windows previous to

version 6.1.03, you must first upgrade to a higher version before migrating the
data.
If you are running CONTROL-M/Server for z/OS or OS/390 previous to version

6.1.0x, you must first upgrade to a higher version before migrating the data.
If you are running a non-English locale on UNIX, see Preparing to migrate a

non-English locale on UNIX on page 15.
NOTE
If BMC Batch Impact Manager or CONTROL-M/Forecast is installed on the earlier_version,
and on the new version, refer to Appendix D, BMC Batch Impact Manager and
CONTROL-M/Forecast migration procedures on page 63 for information on migrating the
data from these components.
14
Preparing to migrate a non-English locale on UNIX
Preparing to migrate a non-English locale on UNIX

If you are using a non-English locale on an UNIX operating system, perform the steps
that follow before installing the Migration Toolkit.
1 Note the current value of the environment variable LC_ALL.

2 Set the value of the environment variable LC_ALL as follows:
For csh/tcsh users:

setenv LC_ALL C
For sh/ksh users:

LC_ALL=C
export LC_ALL
3 After the Migration Toolkit has been installed, set the environment variable
LC_ALL back to the original value noted.
Installing the Migration Toolkit

The Migration Toolkit is used to export CONTROL-M/EM information from an
earlier version as well as to import it into the new version. The latest version of the
Migration Toolkit must be installed in both environments. 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/EM
environment.
Up-to-date, essential installation and service installation is available on the BMC
Software Customer Support Web site ( http://www.bmc.com/support_home) in
solution SLN000015053002.
To install the Migration Toolkit on UNIX

1 Log on to the CONTROL-M/EM account and navigate to the home directory.
2 Download and run the CONTROL-M/EM Migration Toolkit installation program.
The latest version the Migration Toolkit as well as the latest version of this guide,
can be downloaded from BMC Software Customer Support Web site
(http://www.bmc.com/support_home) solution SLN000015056372.
Chapter 2
15
Ensuring data correctness
3 To check if the installation was successful, open the installation log file:
${HOME}/log/ctmem_migration_install_log.txt
To install the Migration Toolkit on Windows

1 Log on to the CONTROL-M/EM account and navigate to the CONTROL-M/EM
software folder.
2 Download and run the CONTROL-M/EM Migration Toolkit installation program.

The latest version the Migration Toolkit as well as the latest version of this guide,
can be downloaded from BMC Software Customer Support Web site
(http://www.bmc.com/support_home) solution SLN000015056372.
3 To check if the installation was successful, open the installation log file:
%TEMP%\ctmem_migration_install_log.txt
NOTE
If BMC Batch Impact Manager exists in the earlier_version CONTROL-M/EM environment,
the Migration Toolkit must be installed on the same machine or account where BMC Batch
Impact Manager is installed.

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.
When a problem with the data is detected, a message is written to the Readiness
report as described below in step 2.
16
To check validity and to ensure that your earlier_version definitions will function
correctly in the new release, perform the following data validation procedure.
To check CONTROL-M/EM data validity

1 Make migration_export your working directory and then run the migration
command to activate the Migration Toolkit. Specify the full path if you are not in
the migration_export directory. For example:
$HOME/migration_export/migration for UNIX

<em_home>\migration_export\migration.bat for Windows
2 Choose the Validation option in the Migration menu. This step generates the
Readiness report.
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.
When running the Validation option, the CONTROL-M/EM system can be up and
running
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 migration_export 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 new 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.
EXAMPLE
In CONTROL-M/EM, special characters, " "and " ", are used to filter the display of user
authorization definitions. However, the migration export procedure uses these same
characters to perform special actions. If these characters are encountered in the export data
stream, for example when the CONTROL-M/EM filter list is exported, an error will occur. To
avoid this error, the " " and " " characters need to be prefixed with the backslash "escape
character". However, this can only be done after the old version has been shut down for the
final time. Otherwise, the CONTROL-M/EM filter will not work with backslashes present.
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 58.
Chapter 2
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 on page 18).
Iterations of the report are stored in the same directory. A sequence number is
appended to the report name so that different reports can be compared. Readiness
report message types are described in Appendix C, Readiness report messages on
page 55.

When all the data is ready, you can migrate it to the new version. This involves
exporting the earlier_version data to a temporary location and then importing it to the
new version.
Once you start the export process, the earlier_version CONTROL-M/EM should be
permanently shut down so that no new data can be generated and no definitions can
be updated or changed.
Further processing should be performed only with the new version of
CONTROL-M/EM after all the migrated data has been imported into the new version
database.
To export the CONTROL-M/EM earlier version data

1 You will need to shut down the following earlier_version components (do not shut
down the database server) before exporting the data:
18
All EM server components

GUI Server
Global Alerts Server
Global Conditions Server
Gateways
BMC Batch Impact Manager Server (if installed)
CONTROL-M/Forecast Server (if installed)
Central Management Server (CMS) for 6.3.01
Administration Agent (6.2.01 or 6.1.03) or Configuration Agent (6.3.01)
Administration Facility (6.2.01 or 6.1.03) or CONTROL-M Configuration
Manager (6.3.01)
All open connections to the CONTROL-M/EM database that use database tools
such as isql, osql, or sqlplus.
The export process will not run if any of the above components are not shut down.
The active components, along with their process IDs and the names of the
machines they are running on, are displayed on the screen before the export
process terminates.
Migration is not finished until the exported data is imported into the new
database.
2 Make migration_export your working directory and then run the migration
command to activate the Migration Toolkit. Specify the full path if you are not in
the migration_export directory. For example:
$HOME/migration_export/migration for UNIX

<em_home>\migration_export\migration.bat for Windows
3 Run Export from the menu. If CONTROL-M/Forecast is installed, you will be

prompted to export the CONTROL-M/Forecast historical data.
NOTE
Migrating the CONTROL-M/Forecast data could require a significant amount of time.
Running CONTROL-M/Forecast in the new environment without this data will still
accurately generate the required information.
If you choose to migrate the CONTROL-M/Forecast data, and the migration of
CONTROL-M/Forecast fails, it will have no impact on the rest of the CONTROL-M/EM
migration.
The output files are saved in the following location:
$HOME/migration_export/ECSExportForMigration.tar on UNIX.
<em_home>\migration_export\data\* on Windows.
The Export step also generates another copy of the Readiness report,
ValidityReport.out, in the migration_export directory.
4 Copy the exported files to a location that can be accessed by the new release
environment.
WARNING
If the exported files are copied using FTP, they must be transmitted 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/Enterprise
Manager Installation Guide.
Chapter 2
19
Importing the exported data to the new version
Importing the exported data to the new

version
If you have not yet installed the new version of CONTROL-M/EM and the Migration
Toolkit, you should do so now (see Installing the Migration Toolkit on page 15). To
install CONTROL-M/EM see the CONTROL-M/EM Installation Guide.
NOTE
If you plan to uninstall the earlier_version of CONTROL-M/EM and CONTROL-M/Server,
you must save the exported .tar file to a location outside the account as it will be erased when
the earlier_version is uninstalled.
If an older version of the Toolkit is detected during installation, it is backed up to the

migration_import.PREVIOUS directory in the new version CONTROL-M/EM
environment.
To import the CONTROL-M/EM data

1 You will need to shut down the following components (do not shut down the
database) before importing the data:
All CONTROL-M/EM server components

GUI Server
Central Management Server (CMS)
Gateways
BMC Batch Impact Manager Server (if installed)
CONTROL-M/Forecast Server (if installed)
All CONTROL-M/EM Configuration Agents
CONTROL-M Configuration Manager and the Reporting Facility
All open connections to the CONTROL-M/EM database that use database tools
such as isql, osql, or sqlplus.
The import process will not run if any of the above components are not shut down.
The active components, along with their process IDs and the names of the
machines they are running on, are displayed on the screen before the import
process terminates.
20
Importing the exported data to the new version
2 Ensure that the exported earlier_version export files are accessible to the new
CONTROL-M/EM version.
For UNIX
If export was preformed on UNIX, the recommended location for the
exported file, ECSExportForMigration.tar is: <em_home>/migration_import.
If export was performed on Windows, copy
<em_home>\migration_export\data from the source installation to
<em_home>\migration_import\data.
For Windows
Copy <em_home>\migration_export\data from the source installation to
<em_home>\migration_import\data.
3 Import the copied export data into the new version database by making
migration_import your working directory and then running the migration
command to activate the Migration Toolkit.
The import process converts the data and imports it into the new version database.
Data for which informational messages and warnings were generated are
automatically adjusted to comply with the new version format. If you chose to
migrate the CONTROL-M/Forecast historical data from the earlier_version, it is
now imported to the new version. This process may require a significant amount
of time.
NOTE
New user and group authorizations defined in the new version before migration of
earlier_version data will keep their definitions after migration. In the case of a conflict (that
is, new groups or users having the same names in both environments), authorizations,
including passwords will be overwritten by the migrated data. Specifically, groups and
users that were defined in both environments will have the attributes of the earlier_version
environment only. This also applies to new users defined in the new environment that
belong to a group that existed in the earlier_version. For more information and examples,
refer to Appendix B, Whats different on page 27.
4 After completing the import process, BMC Software recommends synchronizing

the system by uploading the imported CONTROL-M/EM data to all
CONTROL-M/Servers.
This process also synchronizes all jobs in the system by overwriting the job
definitions in CONTROL-M/Server with the information from CONTROL-M/EM.
5 Manually remove the directories of the ToolKit from the old and new
environments.
Chapter 2
21
Completing the Migration
Completing the Migration

After completing the import process, BMC Software recommends synchronizing the
system by uploading the imported CONTROL-M/EM data to all
CONTROL-M/Servers.
This process also synchronizes all jobs in the system by overwriting the job
definitions in CONTROL-M/Server with the information from CONTROL-M/EM.
If you also installed a new version of CONTROL-M/Server and migrated the data,
you need to migrate its definitions in the CONTROL-M/EM database from
earlier_version format to the format of the new version. This is done by downloading
definitions from the CONTROL-M server machine using CONTROL-M/EM Desktop
or the migrate_dc utility. For more information see Synchronizing
CONTROL-M/Server job processing definitions on page 23.
22
Appendix
CONTROL-M/EM optional migration

procedures
A
This chapter discusses the following additional migration options:
Synchronizing CONTROL-M/Server job processing definitions
Migrating SSL
Migrating asc_ebc file
Synchronizing CONTROL-M/Server job

processing definitions
The migrate_dc is part of the CONTROL-M migration process. The migrate_dc utility
converts CONTROL-M/Server job processing definitions within the
CONTROL-M/EM database. The CONTROL-M/Server job processing definitions
are converted from the earlier_version CONTROL-M/Server data formats to the new
CONTROL-M/Server data format.
NOTE
Do not use this utility if you have not yet installed and migrated to a new version of
CONTROL-M/Server. This procedure should be executed only after CONTROL-M/Server
migration as a means to synchronize the CONTROL-M/EM and the CONTROL-M/Server
database job processing definitions to the new CONTROL-M/Server version.
Note the following:
The utility logs its operation for each data center that is migrated in:
$HOME/log/migrate_<dataCenter>.log for UNIX.

Appendix A
23
Synchronizing CONTROL-M/Server job processing definitions
<drive:>\<emHome>\log\migrate_<dataCenter>.log for Windows.
To use the migrate_dc utility:

NOTE
There is no rollback procedure from changes made by the migrate_dc utility. Before
using the migrate_dc utility, backup all your data.
1 Log on to a computer where the current (newest) version CONTROL-M/EM or the

CONTROL-M Configuration Manager is installed.
2 If the data center's host and port have changed during the CONTROL-M/Server
migration and the correct host and port are not specified in the -hostname and -port
options of migrate_dc, select the relevant CONTROL-M/Server in the
CONTROL-M Configuration Manager GUI and update the host and port
definitions.
3 Verify that the data center being migrated is disconnected from

CONTROL-M/EM and that the corresponding gateway is down.
4 In the CONTROL-M Configuration Manager, if data center version 6.3.01 or higher

(CONTROL-M/Server on UNIX or Windows) or version 62A or higher
(CONTROL-M for OS/390) are in Managed mode, change the status to
Unmanaged.
5 Open a Command Prompt window on Windows or log in to the account where

CONTROL-M/EM is installed on UNIX.
6 Migrate the data for data_center using the following command:

migrate_dc -u <dboName> -p <dboPassword> -dc <dataCenter>
[-hostname <dataCenterHostName>]
[-port <dataCenterPortNumber>]
[-version {620|62A|630|640}]
hostname is the data center host name (maximum length: 255 characters)
port is the data center port number (range: 1024 65533)
version is the newly migrated CONTROL-M/Server version number. This

makes CONTROL-M/EM aware of migration done at the CONTROL-M/Server
level and accordingly adjusts it to the new CONTROL-M/Server version.
By default, all job definitions are converted to a format that is consistent with
the standards for the current version.
24
Migrating SSL
If you migrated or upgraded CONTROL-M/Server on UNIX or on Microsoft

Windows to a version higher than 6.1.03, or if you migrated or upgraded
CONTROL-M for OS/390 to a version higher than 6.1.0x, and then want to run
the migrate_dc utility in CONTROL-M/EM for the migrated CONTROL-M
definitions, you must specify -version {620|62A|630|640} in the migrate_dc
command line to prevent the current version format from being applied to the
jobs for this CONTROL-M.
NOTE
As of this printing, CONTROL-M/Server version 6.4.01 has not yet been released.
Migrating SSL
For more information on SSL migration, refer to SSL for the CONTROL-M
Administration Guide.

When migrating the asc_ebc file from the source version it is copied and saved under
the new name asc_ebc.source as opposed to being overwritten. If you want to
replace the default factory setting file with a customized file from the source version,
contact BMC Software Customer Support for assistance.
NOTE
This step is relevant only if you have customized the asc_ebc file on your source environment.
Appendix A
25
26
Appendix
Whats different
This appendix lists the differences that you need to know about in order to facilitate a
smooth migration from earlier versions to the current version of CONTROL-M/EM
(version 6.4.01).
Differences relevant to migration from version 6.1.03 are in Table 3 on page 27.
Usability changes from version 6.2.01 are in Table 6 on page 48.
Usability changes from version 6.3.01 are in Table 7 on page 53.
NOTE
For detailed information about the features of CONTROL-M versions 6.1.03, 6.2.01, 6.3.01, and
6.4.01 see the CONTROL-M/Enterprise Manager User Guide and CONTROL-M/Enterprise
Manager Administrator Guide for the appropriate version.
Table 3
Migration from version 6.1.03 (Part 1 of 12)
Component
or feature
Version 6.1.03
Version 6.4.01
Supported platforms
For full information on supported

platforms and operating systems, see
the CONTROL-M version 6.1.03 Release
Notes.
For full information about supported

platforms and operating systems, see the
CONTROL-M Release Notes for the current
version.
Microsoft Windows
Gateway and GCS log files are under

the <emHome>\
Gtwgcs\ECS_HOME_NAME\Log
folder on Microsoft Windows.
Gateway and GCS log files are under

the<emHome>\Log directory.
Appendix B
Whats different
27
Table 3
Component
or feature
Side by side
installation
Version 6.1.03
Version 6.4.01
Only clients from different versions

can be installed on Microsoft
Windows platforms
It is now possible to install multiple client

component instances of the same version on
Microsoft Windows platforms. The instances
are installed in separate folders showing the
instance name. Server components can only
have one instance.
For more information see the CONTROL-M
Installation Guide.
N/A
Due to multi instance functionality in

CONTROL-M/EM version 6.4.01, the path to
the CONTROL-M/EM client libraries is not
updated in the system environment variable,
PATH. The user must specify the full path
from the command prompt to activate xml
utilities or update the PATH variable
manually.

and GUI Server
Multiple servers are not supported on Multiple servers with unique logical names
the same computer.
are supported on the same computer. If a
logical name is not specified, the host name
is used and the system works as it did for
version 6.1.03.
BMC Batch Impact

Manager memory
consumption
N/A
28
The Batch Impact Manager algorithm has

been improved so that it consumes 50% less
CPU and memory than in previous versions.
Table 3
Component
or feature
Administration of
server components
Version 6.1.03
Administration of server
components was done by the
Administration Facility
application.
Configuration of parameters were
performed via the Tools->Options
menu which contained the
following parameters:
Database Polling Interval
Delete Log Entries Older Than
Component Restart Interval
Only the DBO user had access to
the Administration Facility
Version 6.4.01
Administrating CONTROL-M/EM
server components and
CONTROL-M/Servers are performed
via the CONTROL-M Configuration
Manager application. For more
information, see CONTROL-M/EM
Administrative tasks in the
CONTROL-M Administrator Guide.
Parameter Database Polling Interval is
replace by Requests polling interval in
the Tools->Options menu
Delete Log Entries Older Than is now
configured in the Tools->System
Parameters menu of the system
parameters window. It is represented by
the LogHistoryDays parameter.
Component Restart Interval is now
the ComponentRestartInterval
parameter.
Users and groups from earlier versions
that had full permissions to perform
authorization actions such as defining
other users or granting permissions to
others, now have permissions to log into
the CONTROL-M Configuration
Manager and perform any operation.
The former Administration Agent is now
called the CONTROL-M/EM
Configuration Agent.
Appendix B
Whats different
29
Table 3
Component
or feature
CORBA
Version 6.1.03
Version 6.4.01
Implemented with Orbix.

Configuration domain:
$IT_CONFIG_DOMAINS_DIR
$IT_CONFIG_DOMAIN_NAME
Configuration file format text file
Administration utilities:
itconfigure
itdeployer
itadmin
iordump
CORBA services:
Locator
Node daemon
Naming service
Implemented with TAO.

Configuration domain:
$ECS_HOME/etc/domains
$EM_DOMAIN_NAME
Configuration file format xml file
Administration utilities:
orbconfigure
orbadmin
nslist
NamingViewer
catior
ior-parser
CORBA services:
Naming service
For more information, see CORBA
Configuration in the CONTROL-M
Administrator Guide.
SSL
Available between the gateway and

CONTROL-M/Server.
Available between Gateway and

CONTROL-M/Server
Available between the following server
components:
CORBA Naming Service
CONTROL-M/EM GUI Server
BMC Batch Impact Manager server
and between the following client
components:
CONTROL-M/EM GUI client

cli utility and XML utilities
CONTROL-M/Desktop
CONTROL-M/Forecast Server
CONTROL-M/EM APIs
BMC Batch Impact Manager Web
Interface
Available between CONTROL-M
Administration Agent and CMS Gate.
For more information, see Security in the

30
Table 3
Component
or feature
GCS and Gateway
Version 6.1.03
N/A
The following Defaults.rsc file

parameters have been converted
into system parameters in version
6.4.01:
limit_gcs_distrib_activate
limit_gcs_distrib_max_days
limit_gcs_distrib_disable_dates
max_ws_queue_size
max_mf_queue_size
srvrs_poll_int
gc_retry_int
gc_max_retry
gc_unsent_wait
upd_comm_int
clean_old_int
gc_done_wait
set_gc_multiple_handling
gc_handle_multiple
comm_userid
bulk_send_int
bulk_send_max
db_diag
comm_diag
Version 6.4.01
GCS starts without command line

parameters. Parameters -U, -P, -D, and
-S are not supported for the gateway.
User name and password are obtained
from an external file.
The following new system parameters
that reside on the database have been
converted from Default.rsc file
parameters:
LimitGCDistribActivate
LimitGCDistribMaxDays
LimitGCDistrubExcludeDates
CommEMBufferSize
CommCtmBufferSize
SrvrsPollIntSecs
GcRetryIntSecs
GcMaxRetries
GcUnsentWaitSecs
UpdCommIntSecs
CleanOldIntSecs
GcDoneWaitSecs
SetGcMultipleHandling
GcHandleMultiple
GCSCommUserId
BulkSendIntSecs
BulkSendMax
DbLogLvl
CondLogLvl
Appendix B
Whats different
31
Table 3
Component
or feature
Version 6.1.03
Sending SNMP traps
N/A
Version 6.4.01
New fields were added to the ALARM

table. This means that there is an
additional parameter in the SNMP trap
data. It relates the Send SNM and Send
Alarm to Script features. The fields are:
TYPE
CLOSED_FROM_EM
TICKET_NUMBER
RUN_COUNTER
SNMP now supports the use of the MIB

file named CONTROLMEM-MIB.txt
located under <emHome>\Data.
The SNMP format has been changed in

comparison to previous versions (refer to
the MIB file).
The SnmpHost system parameter now

supports multiple destination values in
the form of a list with each item
separated by a semi-colon. It is also
possible to set a customized port for each
destination host. For more information,
see the CONTROL-M Administrator
Guide.
For more information, see the CONTROL-M

EM API package
The API mechanism uses .dtd

files.
The function encodePassword is
supported and can be used to
encrypt the user password.
CONTROL-M/Enterp (Unix only) The component binaries

rise Manager Server
are 32 bit.
32
The API mechanism uses XML schema.

The encodePassword function is not
supported. All calls to encodePassword
must be replaced by the
BuildPasswordString.
The EM API XML message structure is
different than in previous versions. For
more information, see the CONTROL-M
API Guide.
(Unix only) The component binaries are 64

bit.
Table 3
Component
or feature
Version 6.1.03
Version 6.4.01
Utility Scripts
Contains utility scripts that are no

longer available in version 6.4.01.
The following utility scripts have been

removed:
install_defs
DBASQL_ecs
sp_configure
masterdbuse
more_func
netlist
test_sql
make_db_oracle
export_defcal
copy_defcal
import_def_table
import_cal
export_def_table
GTWCtl
check_gtw
show_env
copy_def_table
addto_interfaces_file
DBASQL
db_create
erase_alerts
Increased usage of
resources due to
archived Viewpoints
and playback
N/A
Use of the archived ViewPoints and

playback facility causes the GUI Server to
consume additional CPU resources.
In addition, each archive Viewpoint loads its
own private copy of the jobs it contains into
the GUI Server's memory. The copies are
kept there until that Viewpoint is closed.
A single job takes 25 kilobytes of the GUI
Server's memory. One can estimate the
expected memory increase according to the
total number of archive jobs that would be
loaded.
The maximum number of archive jobs
residing in the GUI server's memory can be
controlled using the
LimitArchiveJobsInMem system parameter.
Appendix B
Whats different
33
Table 3
Component
or feature
Version 6.1.03
Version 6.4.01
Reporting
The Reporting facility produces

reports using Actuate.
The Reporting facility includes:

new types of reports
enhancements to existing reports
dynamic report generation
enhanced wizard to create reports
ability to export reports using file
formats not previously supported
ability to run reports using a command
line utility
Reports are produced with Crystal Reports
components.
Auditing
Only log in and log out activities are

audited. Audit records are saved in
the log file in the $HOME/log
directory.
To continue auditing log in and log out

activities, set the UserAuditContext system
parameter to a string that contains AUTH.
Audit records are stored in the
AUDIT_ACTIVITIES table in the
CONTROL-M/EM database. For
information on auditing other activities, see
the CONTROL-M Administrator Guide
34
Table 3
Component
or feature
Defining
Authorizations
Version 6.1.03
Values in authorization fields are

prefixes. If CONTROL-M is set to
A*, all CONTROL-Ms that start
with an A are included.
Scheduling table authorizations
must contain values for three
fields: Scheduling Table, Library,
and CONTROL-M name. If any of
these fields are not specified,
authorization is not granted.
For example:
If CONTROL-M is empty, the user
or group is not authorized for any
CONTROL-M function at that
level (Browse/Update/Full).
For Scheduling Tables, Control
Resources, Quantitative
Resources, Global Conditions,
Prerequisite Conditions and
calendars:
Authorizations granted to
individual users at a group level
can be further refined at the user
level.
For example:
User X belongs to group A.
Group A has Full authority (*)
for all global conditions
prefixes.
User X has Browse authority
for test1* global condition
prefixes.
User X can only view global
conditions which begins with
test1 prefix, but can create,
update and delete other global
conditions.
Note: Definitions which reduce

authorizations on the user level
should be re-defined to conform to the
current version behavior.
Version 6.4.01
Values in authorization fields are regular

expressions (not prefixes). CONTROL-M
A* specifies all CONTROL-Ms that start
with A. CONTROL-M A[123] specifies
CONTROL-Ms A1, A2, and A3.
Authorizations must contain a value for
at least one field. If other fields are blank,
they do not limit the authorization in any
way.
Resources, Quantitative Resources,
Global Conditions, Prerequisite
Conditions, and Calendars:
The relationship between values on a
line is AND.
The relationship between multiple
lines is OR.
Resource authorization rules can use
more than one field. Example: Calendar
name like cal[E1-8]* and CONTROL-M
Name like B*.
Complex boolean relations can be used
between terms; for example:
authorization for CONTROL-M
installation X and prerequisite
conditions (beginning with) Y*,
or for CONTROL-M Z and prerequisite
conditions M[123]*.
Resources, Quantitative Resources,
Global Conditions, Prerequisite
Conditions and calendars:
Authorizations that are specifically
defined for a user only extend and do not
reduce the authorizations specified for
that user on a group level.
For example:
User X belongs to group A. Group A
has Full authority (*) for all global
conditions prefixes.
User X has Browse authority for
test1* global condition prefixes.
User X can create, update and delete
any global conditions.
Appendix B
Whats different
35
Table 3
Component
or feature
Version 6.1.03
Version 6.4.01
GCS
Default: the GCS log is empty.
Default: The GCS log has messages

generated by the default diagnostic level
for global conditions traffic.
The log is managed cyclically to support
permanent logging.
The Log file format allows better tracing
and facilitates automated searches for
keywords in the GCS log.
Diagnostic context C (Condition handled
by GCS) is enhanced for communication
activities about global conditions. New
diagnostic contexts for I (Internal GCS
activities) and M (Messages
communicated with GCS) are introduced for
the log file. For more information, see See
Diagnostics and troubleshooting in the
CONTROL-M Administrator Guide for
information about auditing other activities.
Modes for loading

Scheduling Tables
from CONTROL-M/
Enterprise Manager
database
Local mode is the only available

mode. It provides exclusive access to
jobs and scheduling tables by
automatically locking the tables.
Changes do not take effect until the
user performs a write to the
CONTROL-M/EM database.
Both local mode and online mode are

available.
CONTROL-M/EM
scripts used to control
the Administration
Agent in UNIX
environments
User group filtering
Names changed to:

Script used to start the
Administration Agent was named
start_admin_agent
start_config_agent
Script used to stop the
stop_config_agent
Administration Agent was named check_config_agent
stop_admin_agent
Script used to check the status of
the Administration Agent was
named check_admin_agent
N/A
It is now possible to filter jobs by group level

as well as by user level.
36
Table 3
Component
or feature
root_menu script
Version 6.1.03
CONTROL-M/Server
New Day Time used
by BMC Batch Impact
Manager and Forecast
Root_menu could be accessed by

CONTROL-M/EM users other
than the CONTROL-M/EM
database owner.
The following capabilities are now
deprecated:
Erasing old alerts (DB
Maintenance menu)
Enabling Gateway diagnostics
(Troubleshooting menu)
Setting GCS configuration
Check database available space
The root_menu can be accessed only by

the CONTROL-M/EM database owner.
This change is due to new security
standards where only the
CONTROL-M/EM database owner is
allowed to perform most of the
root_menu functions. For more
administration menu (root menu) on
UNIX in the CONTROL-M
The former capabilities are now available
by using the CCM GUI and/or CCMCLI.
CTM/Server New Day Time

definition used by BMC Batch
Impact Manager was recorded in
file: bim_ctm.ini.
CONTROL-M/Forecast used the
definition from the database.
Both BMC Batch Impact Manager and

CONTROL-M/Forecast now use the value
defined in the database. Migration from file
to database is performed by the Migration
tool-kit. In the case of a conflict between the
value in BMC Batch Impact Manager
(defined in the file) and the value in
CONTROL-M/Forecast, the
CONTROL-M/Forecast value in the
database is used.
BMC Batch Impact Manager Exceptions now
reside in the database. Migration from the
xml file to the database is now performed by
the Migration tool-kit. Defining exceptions is
now performed in the CONTROL-M/EM
GUI.
BMC Batch Impact

Manager statistical
exceptions

statistical exceptions resided in
XML file: bim_statistics.xml.
Exceptions were defined via the
user interface.
Database connections
System parameter
NumberOfCTMDBConnections
determined the maximum
number of concurrent connections
between the GUI Server and the
database server.
Gateway consumes up to 2
database connections.
Version 6.4.01
General CPU and

N/A
memory consumption
increase
The former system parameter

NumberOfCTMDBConnections is now
obsolete. If you changed the default
value in version 6.1.03, you should
contact BMC Software.
Gateway consumes up to 5 database

connections.
Benchmark tests have indicated an increase

of up to 60% in memory and no substantial
increase in CPU consumption (this does not
apply to Windows with MSSQL). Refer to
the following sections for exceptions.
Appendix B
Whats different
37
Table 3
Component
or feature
Increased gateway
CPU consumption
Version 6.1.03
Version 6.4.01
N/A
Gateways use 5080% more CPU resources

than they did in previous versions.
A single gateway does not consume many
CPU resources. However, customers with
installations containing a large number of
gateways (5 or more), connected to large
CONTROL-M/Servers (more than 3000 jobs
per day) should pay close attention to the
application's CPU consumption for several
days, mainly during peak time.
Increased gateway
N/A
memory consumption
Gateways consume 150% more memory in

Oracle and Sybase and 200% in MSSQL.
Customers containing a large number of
gateways (5 or more) should check the
current memory consumption of the
gateways for version 6.1.03 and verify
whether their computers need additional
memory for version 6.4.01.
N/A
The BMC Batch Impact Manager algorithm

has been improved to consume 50% less
CPU and memory than it used in earlier
versions.
BIM memory
consumption
Table 4
Component
or feature
Supported Platforms
38
Version 6.2.01
Version 6.4.01

platforms and operating systems, see
the CONTROL-M Release Notes for
version 6.2.01 version.

platforms and operating systems, see the
CONTROL-M Release Notes for this version.
Table 4
Component
or feature
Side by side
installation
Version 6.2.01
Version 6.4.01
Only clients from different versions

can be installed on Microsoft
Windows platforms
It is now possible to install multiple client

component instances of the same version on
Microsoft Windows platforms. The instances
are installed in separate folders showing the
instance name. Server components can only
have one instance.
For more information see the CONTROL-M
Installation Guide.
N/A
Database connections
BMC Batch Impact

Manager memory
consumption
System parameter
NumberOfCTMDBConnections
determined the maximum
number of concurrent connections
between the GUI Server and the
database server.
Gateway consumes up to 2
database connections.
N/A
Due to multi instance functionality in

CONTROL-M/EM version 6.4.01, the path to
the CONTROL-M/EM client libraries is not
updated in the system environment variable,
PATH. The user must specify the full path
from the command prompt to activate xml
utilities or update the PATH variable
manually.
The former system parameter

NumberOfCTMDBConnections is now
obsolete. If you changed the default
value in version 6.1.03, you should
contact BMC Software.

connections.
The Batch Impact Manager algorithm has

been improved so that it consumes 50% less
CPU and memory than in previous versions.
Appendix B
Whats different
39
Table 4
Component
or feature
Administration of
server components
Version 6.2.01
Administration of server
components was done by the
Administration Facility
application.
Configuration of parameters were
performed via the Tools->Options
menu which contained the
following parameters:
Database Polling Interval
Delete Log Entries Older Than
Component Restart Interval
Only the DBO user had access to
the Administration Facility
Version 6.4.01
root_menu script
40

database owner.
The following capabilities are
now deprecated:
Maintenance menu)
Check database available space
Administrating CONTROL-M/EM
server components and
CONTROL-M/Servers are performed
via the CONTROL-M Configuration
Manager application. For more
Administrative tasks in the
Parameter Database Polling Interval is
replace by Requests polling interval in
the Tools->Options menu
Delete Log Entries Older Than is now
the LogHistoryDays parameter.
Component Restart Interval is now
the ComponentRestartInterval
parameter.
Users and groups from earlier versions
that had full permissions to perform
authorization actions such as defining
other users or granting permissions to
others, now have permissions to log into
the CONTROL-M Configuration
Manager and perform any operation.
The former Administration Agent is now
called the CONTROL-M/EM
Configuration Agent.
The root_menu can be accessed only by
the CONTROL-M/EM database owner.
This change is due to new security
standards where only the
CONTROL-M/EM database owner is
allowed to perform most of the
root_menu functions. For more
administration menu (root menu) on
UNIX in the CONTROL-M Administrator
Guide.
The former capabilities are now available
by using the CCM GUI and/or CCMCLI.
Table 4
Component
or feature
Version 6.2.01
Sending SNMP traps
N/A
Version 6.4.01
New fields were added to the ALARM

table. This means that there is an
additional parameter in the SNMP trap
data. It relates to the Send SNMP and
Send Alarm to Script features. The fields
are:
TYPE
CLOSED_FROM_EM
TICKET_NUMBER
RUN_COUNTER
SNMP now supports the use of the MIB
file named CONTROLMEM-MIB.txt
located under <emHome>\Data.
The SNMP format has been changed in
comparison to previous versions (refer to
the MIB file).
The SnmpHost system parameter now
supports multiple destination values in
the form of a list with each item
separated by a semi-colon. It is also
possible to set a customized port for each
destination host. For more information,
see the CONTROL-M Administrator
Guide.

EM API package
User group filtering
The API mechanism uses .dtd

files.
Both the encodePassword and
BuildPasswordString functions
are supported and can be used to
encrypt a user password.
N/A
The API mechanism uses XML schema

supported. All calls to the
encodePassword function must be
replaced by the BuildPasswordString.
The EM API XML message structure is
different than previous versions. For
more information, see the CONTROL-M
API Guide.
It is now possible to filter jobs by group level

as well as by user level.
Appendix B
Whats different
41
Table 4
Component
or feature
CONTROL-M/Server
New Day Time used
by BMC Batch Impact
Manager and Forecast
Version 6.2.01
Version 6.4.01
CTM/Server New Day Time

definition used by BMC Batch
Impact Manager was recorded in
file: bim_ctm.ini.
CONTROL-M/Forecast used the
definition from the database.
Both BMC Batch Impact Manager and

CONTROL-M/Forecast now use the value
defined in the database. Migration from file
to database is performed by the Migration
tool-kit. In the case of a conflict between the
value in BMC Batch Impact Manager
(defined in the file) and the value in
CONTROL-M/Forecast, the
CONTROL-M/Forecast value in the
database is used.
BMC Batch Impact Manager Exceptions now
reside in the database. Migration from the
xml file to the database is now performed by
the Migration tool-kit. Defining exceptions is
now performed in the CONTROL-M/EM
GUI.
BMC Batch Impact

Manager statistical
exceptions

statistical exceptions resided in
XML file: bim_statistics.xml.
Exceptions were defined via the
user interface.
CONTROL-M/EM
scripts used to control
the Administration
Agent in UNIX
environments
Names changed to:

Script used to start the
Administration Agent was named start_config_agent
start_admin_agent
stop_config_agent
Script used to stop the
check_config_agent
Administration Agent was named
stop_admin_agent
Script used to check the status of
the Administration Agent was
named check_admin_agent
CONTROL-M/EM
Server
42
(Unix only) The component binaries

are 32 bit.
(Unix only) The component binaries are 64

bit.
Table 4
Component
or feature
Utility Scripts
Version 6.2.01
Version 6.4.01

The following utility scripts have been

removed:
install_defs
DBASQL_ecs
sp_configure
masterdbuse
more_func
netlist
PURGE_RUNINFO_ORA.sql
PURGE_RUNINFO.sql
test_sql
make_db_oracle
export_defcal
copy_defcal
import_def_table
import_cal
export_def_table
GTWCtl
check_gtw
show_env
copy_def_table
DBASQL
db_create
erase_alerts
Appendix B
Whats different
43
Table 4
Component
or feature
GCS and Gateway
Version 6.2.01
N/A
The following Default.rsc file
to system parameters in version
6.4.01:
max_ws_queue_size
max_mf_queue_size
srvrs_poll_int
gc_retry_int
gc_max_retry
gc_unsent_wait
upd_comm_int
clean_old_int
gc_done_wait
gc_handle_multiple
comm_userid
bulk_send_int
bulk_send_max
db_diag
cond_diag
int_diag
msg_diag
gcs_log_size
max_gcs_logs
General CPU and

N/A
memory consumption
increase
Version 6.4.01

parameters. Parameters -U, -P, -D, and -S
are not supported for the gateway. User
name and password are obtained from
an external file.
The following new system parameters
that reside on the database have been
converted from Default.rsc file
parameters:
CommEMBufferSize
CommCtmBufferSize
SrvrsPollIntSecs
GcRetryIntSecs
GcMaxRetries
GcUnsentWaitSecs
UpdCommIntSecs
CleanOldIntSecs
GcDoneWaitSecs
GcHandleMultiple
GCSCommUserId
BulkSendIntSecs
BulkSendMax
DbLogLvl
CondLogLvl
IntLogLvl
MsgLogLvl
LogSize
MaxLogs
Benchmark test have indicated an increase of

up to 60% in memory (this does not apply to
Windows with MSSQL) and up to 10% in
CPU.
Database Disk Space
N/A
Database storage space has increased up to

150% in Oracle and MSSQL and 500% in
Sybase.
BIM memory
consumption
N/A
The BMC Batch Impact Manager algorithm

has been improved to consume 50% less CPU
and memory than it used in earlier versions.
44
Table 5
Component of
feature
Version 6.3.01
CONTROL-M/EM (Unix only) The component binaries

Servers
are 32 bit.
System Parameters
MaxUpdatedJobstoAudit - An
available system parameter.
PasswordEncode - The default
value is 1.
Version 6.4.01
(Unix only) The component binaries are now 64
bit.
MaxTableJobsTo Audit - This system

parameter replaces and is equivalent to the
former, which is now obsolete.
PasswordEncode - The default value is 2 for
stronger password protection.
BIM Exception
Manager
EM API package

The following utility scripts have been removed:

install_defs
DBASQL_ecs
sp_configure
masterdbuse
more_func
netlist
PURGE_RUNINFO_ORA.sql
PURGE_RUNINFO.sql
test_sql
make_db_oracle
export_defcal
copy_defcal
import_def_table
import_cal
export_def_table
GTWCtl
check_gtw
show_env
copy_def_table
DBASQL
db_create
erase_alerts
Appears as exceptions and

periods.
Utility Scripts
The BMC Batch Impact Manager

exceptions period uses regular
calendar rules.
Note: Exception periods are not migrated.

Appears as Job Run Time in the
BIM/Forecast configuration window.
The BMC Batch Impact Manager exceptions
period uses periodic calendars.
A new periodic statistics mechanism
reduces the number of runtime rules
needed.
Both the encodePassword and

BuildPasswordString functions
are supported and can be used to
encrypt a user password.

supported. All calls to encodePassword
must be replaced by the
BuildPasswordString. For more
information, see the CONTROL-M API
Developers Guide.
Appendix B
Whats different
45
Table 5
Component of
feature
Version 6.3.01
root_menu script
N/A
GCS and Gateway
The following Default.rsc file

to system parameters in version
6.4.01:
max_ws_queue_size
max_mf_queue_size
srvrs_poll_int
gc_retry_int
gc_max_retry
gc_unsent_wait
upd_comm_int
clean_old_int
gc_done_wait
gc_handle_multiple
comm_userid
bulk_send_int
bulk_send_max
db_diag
cond_diag
int_diag
msg_diag
gcs_log_size
max_gcs_logs
Database
connections
46

database owner.
The following capabilities are
now deprecated:
Maintenance menu)
Check database available
space (Troubleshooting menu)

connections (per gateway).
Version 6.4.01

parameters. Parameters -U, -P, -D, and -S
are not supported for the gateway. User
name and password are obtained from an
external file.
The following are new system parameters
that reside on the database and were
converted from Default.rsc file parameters:
CommEMBufferSize
CommCtmBufferSize
SrvrsPollIntSecs
GcRetryIntSecs
GcMaxRetries
GcUnsentWaitSecs
UpdCommIntSecs
CleanOldIntSecs
GcDoneWaitSecs
GcHandleMultiple
GCSCommUserId
BulkSendIntSecs
BulkSendMax
DbLogLvl
CondLogLvl
IntLogLvl
MsgLogLvl
LogSize
MaxLogs
The root_menu can be accessed only by the
CONTROL-M/EM database owner. This
change is due to new security standards
where only the CONTROL-M/EM database
owner is allowed to perform most of the
root_menu functions. For more information,
see CONTROL-M/EM administration
menu (root menu) on UNIX in the
The former capabilities are now available by
using the CCM GUI and/or CCMCLI.

connections (per gateway).
Table 5
Component of
feature
Version 6.3.01
Version 6.4.01
General CPU and

memory
consumption
increase
N/A
Benchmark test have indicated an increase of up

to 60% in memory (this does not apply to
Windows with MSSQL) and up to 10% in CPU.
Database Disk
Space
N/A
Database storage space has increased up to

150% in Oracle and MSSQL and 500% in Sybase.
BIM memory
consumption
N/A
BMC Batch Impact Manager consumes 50% less

CPU and memory than it used before 6.3.01 fix
pack 5 (in 6.3.01 fix pack 5, the BMC Batch
Impact Manager algorithm was improved).
BMC Batch Impact Manager consumes an
additional 50% CPU and an additional 20% of
memory in comparison to 6.3.01 fix pack 5.
Appendix B
Whats different
47
Table 6
Usability changes from version 6.2.01 (Part 1 of 6)
Category of changes
Description
Change
6.2.01
6.4.01
Note: This table identifies usability changes from 6.2.01. It is not a summary of Whats New items in the
release, and many new items in the release may not be listed in the table.
General usability changes
New GUI replaces the
Administration facility
and adds new
functionality
The CONTROL-M/EM
Administration facility requires a
database owner, and there was no
security for operations, nor
auditing, nor a full picture of the
entire product.
Defining CONTROL-Ms CONTROL-Ms had to be defined

in both CONTROL-M/Desktop
and CONTROL-M/EM.
Flow diagram panes can

be moved
A new GUI, called the

CONTROL-M/EM Configuration
Manager, replaces the
CONTROL-M/EM Administration
facility. It does not require a database
installation. It provides security, so that
not only administrators but users as
well can use it. It provides auditing
capabilities. And it can manager not just
CONTROL-M/Servers, but also
CONTROL-M/Agents, Control
Modules, and CONTROL-M for z/OS.
You define CONTROL-Ms only using
the CONTROL-M/EM Configuration
Manager. CONTROL-M/Desktop and
CONTROL-M/EM take (discover) the
definitions from the CONTROL-M
Configuration Manager.
Panes in the flow diagram can be CONTROL-M/EM and

resized, but remained anchored in CONTROL-M/Desktop both allow you
place.
to move the flow diagram panes to any
location in your screen (dockable and
floatable panes).
Multiple opened job The opening of multiple job editing forms in CONTROL-M/Desktop and
editing forms
CONTROL-M/EM is fully supported without limitations (Mode-less operation).
This allows you to compare jobs and copy/paste information between them.
CONTROL-M/Desktop
login
You can log into

You logged into
CONTROL-M/Desktop only after CONTROL-M/Desktop as you are
opening it (though this is not required).
the application was opened, the
first time login was required by an
operation.
condition inheritance
If you delete a job that is a

successor to one job and a
predecessor to another job, the
flow between the non-deleted jobs
is broken.
Filtering in the Calendar You cannot filter the Calendar

Manager
Manager display.
48
If customization options are

appropriately set, the conditions of the
deleted job are appropriately
propagated in the non-deleted jobs so
that the job flow is not broken.
The Calendar Manager now lets you
filter the display.
Table 6
Category of changes
Description
Change
6.2.01
6.4.01
Templates replace
skeletons in
CONTROL-M/Desktop
You could use skeletons to

create or update large
numbers of jobs.
Templates replace skeletons for

Mass job create and update.
One type of skeleton was used

for both jobs and for
scheduling groups. Edited in
the skeleton editor, this
skeleton lacked fields unique
to scheduling groups, such as
scheduling tags. Furthermore,
since scheduling groups
require at least one scheduling
tag, you could not use a
skeleton to create a fully valid
scheduling group.
Two basic types of templates are

available one for jobs and the
other for scheduling groups. Job
templates are almost identical to job
processing definitions and group
templates are almost identical to
scheduling group definitions. You
define templates in the template
editing form which resembles the
job (or group) editing form.
Templates are platform-specific
platform-specific changes in the job
editing form or group editing form
appear in the template.
Not all fields of job processing

definitions can be defined in
skeletons (for example, you
cannot define On statements).
There are no limits on the fields you

can define in templates.
All skeletons were save in one

file.
Templates are saved in separate files

that can be shared (by a copy) with
other client installations
The Condition format is part

of the skeleton.
The Condition format is part of Tool

=> Options => Links.
CONTROL-M/Desktop comes with

pre-defined templates. You can
define your own templates, and
save job processing definitions as
templates.
You can automatically insert

functions into most template fields.
Dialog boxes simplify insertion.
You can automatically populate any

job processing definition with
template values.
You manage templates in the

Template Manager (in
CONTROL-M/Desktop)
Appendix B
Whats different
49
Table 6
Category of changes
Description
Change
6.2.01
6.4.01
Automatic condition
deletion in
CONTROL-M/Desktop
When you use the click and drag

method to automatically create job
dependencies, you cannot
automatically generate Out
conditions that will delete the
condition after the dependent job
has executed.
If the customization options are

appropriately set, when you use the
click and drag method to automatically
create job dependencies, Out conditions
that delete the condition after the
dependent job has executed are also
automatically generated.
Workspaces replace
modes in
CONTROL-M/Desktop
Work is performed in
CONTROL-M/Desktop in online
or local mode.
Modes have been replaced by

workspaces. CONTROL-M/Desktop
allows you to work in the following
workspaces:
Local workspaceyou work locally

by loading jobs from the
CONTROL-M/EM database. You
are granted exclusive access over
the jobs, and you can save the
definitions in a draft file, which you
can later reopen.
Online workspaceyou can work

directly on the CONTROL-M/EM
database. You are granted access
over relevant jobs, and save your
work directly in the database. You
can create new jobs directly in
online mode.
List view display in

CONTROL-M/EM
You can only view jobs in a flow

diagram
You can toggle between display jobs in a

flow diagram or in a list (List view).
Order/Force in
CONTROL-M/EM
You can only select one or all jobs

in the Order/Force dialog box in
CONTROL-M/EM.
You can select any number of jobs in the

Order/Force dialog box in
CONTROL-M/EM.
Changes to the job editing form in CONTROL-M/Desktop

CONTROL-M and Job
Type fields
Node ID/Group field
50
CONTROL-M and Form fields are CONTROL-M and Job Type fields
located in specific tabs of the job
appear above the job editing form tabs,
unconnected to a specific tab. (The Job
editing form.
Type field is new. It generally indicates
the type of external application,
represents a combination of the
Application Node Group, Application
Type, Application Version, CM Version,
and Form Name parameters.
For applications, the Node
ID/Group field in the Execution
tab is read only.
The Node ID/Group field is now

updatable for applications.
Table 6
Category of changes
Description
Change
6.2.01
6.4.01
selection lists for fields
To enter values for fields, you

must type them in, for many fields
such as Table, Application, Group,
Calendar, condition relationships,
scheduling rules.
You can select values from selection lists

(combo boxes), rules dialog boxes,
condition relationship selection lists,
and so on.
advanced scheduling
rules in the Scheduling
tab
To define scheduling rules in the Each scheduling rule now has its own
Scheduling tab, you had to know separate, clearly explained, entry field.
rule formats and correctly type the
entries into a single field.
mandatory fields
Mandatory fields are indicated by red

The job editing form does not
asterisks.
indicate mandatory fields. You
discover mandatory fields when
you try to save or use a job
processing definition that lacks a
mandatory value.
buttons
The Save button is at the bottom of Buttons have been moved to a tool bar
the job editing form.
at the top of the job editing forms. You
can now perform Save, Save and close,
Save As, Save as a Template, and
one-click upload.
prompt to save changes
There is no confirmation prompt

to save changes
You are prompted to whether to save

changes.
Order/Force
You cannot order or force a job

from the job editing form in
CONTROL-M/Desktop.
You can perform an Order/Force action

from the job editing form in
CONTROL-M/Desktop, and this action
lets you to perform a write to the
CONTROL-M/EM database and an
upload to the CONTROL-M database in
the same step.
Look and feel changes

New icons and colors The icons and colors in version the GUIs, especially the CONTROL-M/Desktop
in GUIs
and CONTROL-M/EM windows, have been changed in 6.3.01 to make them
clearer and more appealing. Menus and their options have also changed
(discussed below, individually). Note: Status colors did not change.
Calendar Manager and
Scheduling Table
Manager
Options (in the form of

rectangular blocks) appear on the
side of the window.
Options, in the form of icons, appear on

the top of the window.
Appendix B
Whats different
51
Table 6
Category of changes
Description
Change
CONTROL-M/Desktop
menu options version
6.2.01 replaced by
version 6.3.01
Edit => CONTROL-M

Definition no longer exists
You define CONTROL-Ms using the

CONTROL-M/EM Configuration
Manager
Edit => Job
separate Edit options
Edit => Scheduling Group

menu no longer exists
Edit => New Scheduling Group

option is new. To perform tasks that
used to be in the menu, use the
Scheduling Table Manager.
Edit => Scheduling Tables =>

Scheduling Table Manager
Tools => Scheduling Table

Manager
Edit => Scheduling Tables =>

Write to CONTROL-M/EM
File => Write to CONTROL-M/EM
Edit => Calendars Manager
Tools => Calendar Manager
Tools => Mass Update
Edit => Find and Update
Tools => Skeleton
Tools => => Template Manager
Tools => Collections
Edit => Filter
Tools => Neighborhood
Views => Neighborhood
Communication menu
options (menu no longer
exists)
Options from the Communication

menu moved to the Tools menu
52
6.2.01
The Help => Wizard option

no longer exists.
Tools menu now has options for:

Global conditions and
CONTROL-M Forecast.
6.4.01
Table 6
Category of changes
Description
Change
6.2.01
CONTROL-M/EM menu
options version 6.2.01
replaced by version
6.3.01
File => Close ViewPoint no

longer exists.
Edit => ViewPoint Manager
Tools => ViewPoint Manager
The following options in the

Actions menu have been
moved: Status Summary,
Sysout, Statistics,
Documentation, Log, Why,
Enhanced Why, Critical Path
The options now appear in the

Analysis menu.
Actions => Activate

Applications
Tools => Activate Applications
View => Messages
View => Output Windows =>

Messages
Resources menu no longer

exists.
Its options now appear in the Tools

menu.
Tools => Alerts
View => Alerts
Table 7
6.4.01
Category of changes
Change
Description
6.3.01
6.4.01
Note: This table identifies usability changes from 6.3.01. It is not a summary of Whats New items in the
release, and many new items in the release may not be listed in the table.
General usability changes
Find and update
Enables you to find all related jobs.
Enables you to find the next and all

related jobs.
Allows you to update all job
attributes including the
applications job fields.
JEF
DO Mail includes enhancements to the

The enhancements made to DO
MAIL that are available in version window that can now be used to
display all necessary information.
6.4.01 are not available in this
version but might be available in a
future fix packs.
Drafts
Drafts can only be saved from the

Desktop in .drf format.
Drafts can be saved from the Desktop in

.drf and xml formats.
Appendix B
Whats different
53
Table 7
Category of changes
Description
Change
6.3.01
6.4.01
CONTROL-M
Configuration Manager
Agent window
Testing users and passwords

before saving their properties and
recycling an agent must be
performed manually.
The testing of users and passwords

before saving their properties and
recycling an agent can be performed
using the CONTROL-M Configuration
Manager.
Agent System
Agent system parameters are
parameters configuration configured in the agent
installation.
There is a new option in the

CONTROL-M Configuration Manager
to configure the Agent System
parameters.
Reporting facility
command line utility
The input parameters for batch

reports are received from a xml
file.
Additional usage flags have been added

to the command line utility of the
reporting facility to allow for easy
execution of batch reports without
having to create a xml file.
Forecast Gantt
Displays one day of scheduled

jobs.
Displays two days of scheduled jobs.
Node group management Node group management is

conducted in the CONTROL-M
Server command utility.
Node group management can be

conducted through the CONTROL-M
Configuration Manager.
Calendar definition
Calendar definitions from year to

year must be entered manually.
An entire year of jobs can be copied to

the following year.
Authorization
There is only a BMC Batch Impact There is a new BMC Batch Impact
Manager authorization.
Manager and Forecast authorization.
Job definition
comparison
The user interface does not

facilitate comparing two jobs
simultaneously on the desktop.
There is a new user interface that can be

used to compare two job
simultaneously on the desktop.
Auditing
The details provided in the audit

report are less detailed in
comparison to version 6.4.01.
The audit report contains a greater

amount of details.
Application fields
The dynamic find, find and

update, and view points cannot
search for applications and their
fields.
The dynamic find, find and update, and

view points can search for applications
and their fields.
Job templates
Job templates are available.
The job templates available have been

changed.
Alert and Resources

window
The search results are always

filtered before displayed in the
Resources window.
The filter can be selected after all the

jobs are displayed. Additionally, the
look of the Alert and Resources
windows differ than in previous
versions and contain several
functionality changes, such as filtering
the grid view.
Find
The Find feature is available.
The Find feature in the desktop is more

intuitive and user friendly.
Look and Feel changes
54
Appendix

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.
Appendix C
55
Readiness report format
Prefix
Description
PLN
PLN Warning
These messages warn that job processing definitions in your current
environment contain an improper combination of basic scheduling parameters
that affect the jobs scheduling plan in the new version.
PLN messages are always accompanied by an ERR99 message, which is a
general error message indicating that job scheduling plan differences in the
new version.
The data cannot be migrated until the scheduling plan differences are
resolved. The migration utility cannot determine what corrections to make.
You must perform the required changes manually.
Note: If ERR99 is issued without any PLN warnings, notify BMC Software
Customer Support.
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.

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
56
Example
This example displays a problem with a date value in an OUT statement in a job
processing definition:
Error ERR04:OUT condition is being added with an invalid date: **** or $$$$
__________________________________________________________________________________________
Code Scheduling Table Name Job NO
Job Name
Mem Name
CONDNAME
----- --------------------- -------- ---------- --------------------------- -----------------ERR04 migr
1833
dt_dollars test_mem
date_dollars_out
Appendix C
57
Analyzing report messages
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.
ERR99 with PLN messages
Correction of PLN problems is mandatory.
ERR99 without PLN messages
Contact BMC Software support.
WRN messages
Correction of the messages is optional.
INF messages
None.
Messages
ERR30001
Fields contain illegal TAB sign

Explanation: The specified field cannot contain a TAB sign.
System Action: The export procedure cannot process the data.
User Response: Delete the illegal TAB signs.
ERR30002
Special characters are used in the ViewPoint Collection definitions: !,()[]{}.+^$|

Explanation: Special characters are used in the ViewPoint Collection definitions. The
6.2.01 environment treats the following special characters as regular expressions:
!,()[]{}.+^$|
User Response: Escape the special characters by adding a backslash character "\"
before each special character if the "\" is not present. To avoid a change of behavior in
the earlier_version environment, make this correction when the system is down and
ready to export the data.
ERR30003
Special characters are used in the ViewPoint filter definitions: ,^

Explanation: Special characters are used in the ViewPoint Filter definitions. The 6.2.01
environment treats the following special characters as regular expressions: ,^
58
Messages
ERR30004
Special characters are used in the Displayed Jobs Filter of user authorization
definitions: ,^
Explanation: Special characters are used in the Displayed Jobs Filter for user
authorization definitions. The 6.2.01 environment treats the following special
characters as regular expressions: ,^
ERR30005
Special characters are used in the Resource Authorizations of user

authorization definitions: !,()[]{}.+^$|*?
Explanation: Special characters are used in the Resource authorization definitions.
The 6.2.01 environment treats the following special characters as regular expressions:
!,()[]{}.+^$|*?
ERR30006
Encountered a data center not supported by CONTROL-M/EM version 6.3.0x.

Explanation: CONTROL-M/Enterprise Manager version 6.3.0x supports data centers
for the following products only:
AS/400 version 2.2.5
CONTROL-M/Server for Distributed Systems versions 6.1.03 and 6.2.0x
CONTROL-M for OS/390 and CONTROL-M for z/OS versions 6.1.0x and 6.2.0x
Data centers for versions earlier than those listed above must be upgraded.
User Response: Upgrade data center to a version which is supported by CONTROLM/Enterprise Manager 6.3.0x.
ERR30007
Fields contain illegal new line character

Explanation: The specified field cannot contain a new line character. The new line
character is represented in the Readiness report with the string <NL>
User Response: Delete the illegal new line character.
Appendix C
59
Messages
ERR40001
Fields contain illegal TAB sign

Explanation: The specified field cannot contain a TAB sign.
User Response: Delete the illegal TAB signs.
ERR40002
Encountered a data center not supported by CONTROL-M/EM version 6.3.0x.

Explanation: CONTROL-M/Enterprise Manager version 6.3.0x supports data centers
for the following products only:
AS/400 version 2.2.5
CONTROL-M/Server for Distributed Systems versions 6.1.03 and 6.2.0x
CONTROL-M for OS/390 and CONTROL-M for z/OS versions 6.1.0x and 6.2.0x
Data centers for versions earlier than those listed above must be upgraded.
User Response: Upgrade data center to a version which is supported by CONTROLM/Enterprise Manager 6.3.0x.
ERR40003
Fields contain illegal new line character

Explanation: The specified field cannot contain a new line character. The new line
character is represented in the Readiness report with the string <NL>
User Response: Delete the illegal new line character.
INF30001
Special characters - |(){}$! - are used in the ViewPoint Filter definitions.

Explanation: The special characters |(){}$! are used in the ViewPoint Filter definitions.
In the 6.2.01 environment the specified characters have different meanings.
System Action: To avoid a change behavior after migrating to the 6.2.01 environment,
the system will add a \ before each special character if the backslash is not present,
but will remove it if it is present.
INF30002
Special characters - |(){}$! - are used in the Displayed Jobs Filter of user
authorization definitions.
Explanation: The special characters |(){}$! are used in the Displayed Job Filter for user
authorization definitions. In the 6.2.01 environment the specified characters have
different meanings.
System Action: To avoid a change behavior after migrating to the 6.2.01 environment,
the system will add a \ before each special character if the backslash is not present,
but will remove it if it is present.
60
Messages
WRN30001
Wildcard characters * and ? are used for Viewpoint collection definitions

Explanation: Wildcard characters * and ? when used in Viewpoint collection
definitions in combination with operators =, <, >, !=, yield incorrect results.
For example
FieldName Operator FieldValue
Group
=
*group*
If production groups *group* and %group% both exist, the Viewpoint collection will
display jobs with %group% only.
System Action: All wildcard characters * and ? when used in Viewpoint collection
definitions in combination with operators =, <, >, != will be replaced by % and _
respectively.
WRN30004
Default.rsc parameters different from factory settings

Explanation: The CONTROL-M/EM configuration parameters in the Default.rsc files
differ from the default factory settings values.
User Response: Contact BMC Software Customer Support in order to determine the
value that should be set for the target version.
WRN40001

WRN50001

Appendix C
61
Messages
62
Appendix
BMC Batch Impact Manager and

CONTROL-M/Forecast migration
procedures
D
NOTE
BIM and Forecast migration procedures are automatically handled by the Migration toolkit.
The manual procedures that follow can be used to handle situations in which the automatic
process fails.
This appendix explains:
Migrating Remedy system parameters

Migrating CONTROL-M/Server New Day Time
Troubleshooting New Day Time migration
Migrating BMC Batch Impact Manager exceptions
Troubleshooting BMC Batch Impact Manager exceptions
Migrating CONTROL-M/Forecast exception conditions
Re-activating CONTROL-M/Forecast and BMC Batch Impact Manager
Migrating CONTROL-M/Forecast Historical Data
Migrating BMC Batch Impact Manager Web Application settings from an
earlier_version
Appendix D
BMC Batch Impact Manager and CONTROL-M/Forecast migration procedures
63

When migrating from 630 GA-FP4 while DO Remedy is in use, the user is required to
run the remedy configure utility and reenter the Remedy password. For more
information, see the CONTROL-M Business Service Management Solutions User
Guide.
Migrating CONTROL-M/Server New Day Time

New Day Time is one of the parameters that BMC Batch Impact Manager and
CONTROL-M/Forecast relate to during standard operations. On earlier versions of
BMC Batch Impact Manager, CONTROL-M/Server New Day Time definitions were
defined in the bim_ctm.ini file of each data center. On CONTROL-M/Forecast, New
Day Time was defined as a data center definition residing on the CONTROL-M/EM
database.
Starting from version 6.3.01, New Day Time for both BMC Batch Impact Manager and
CONTROL-M/Forecast is defined only in the database. The bim_ctm.ini file is now
obsolete. The Migration Toolkit migrates New Day Time from the earlier_version
bim_ctm.ini file directly to the new version database.
NOTE
Specific data center definitions must exist in both the earlier_version bim_ctm.ini file as well
as in the new version database. Otherwise the data is not migrated.
If the bim_ctm.ini file did not exist at its designated location in the earlier_version, the import
procedure will skip this step.
In the case of parameter conflict between its value in the earlier_version bim_ctm.ini
file and its value in the new version database, the information from the bim_ctm.ini
file will overwrite the data in the database.
If any step fails during the New Day Time import procedure, for example, the New
Day Time information is not found because the import process did not locate the
earlier_version bim_ctm.ini file, New Day Time must be updated manually. For more
information see Troubleshooting New Day Time migration.

If the migration of New Day Time fails, one of the following messages is written to
the screen and to the Migration Toolkit log file.
64
BMC Batch Impact Manager CTM New Day Time file cannot be found. Refer to the
CONTROL-M/Enterprise Manager Migration Guide to perform this process manually.
BMC Batch Impact Manager related New Day Time configurations defined on the
source environment will not take effect until this process is completed.
Solution: After migration, check if the bim_ctm.ini file is present in the following
location of the new version:
<emHome>/migration_import/data for UNIX.
<emHome>\migration_import\data for Windows.
If the file is not present, manually copy it from the earlier_version to the above location
(for UNIX or Windows) and execute the following command:
ecs-no_wrap bimsrv - NewDayTime_migrate=

<emHome>/migration_import/data/bim_ctm.ini for UNIX.
ecs_bim.exe -NewDayTime_migrate=
<emHome>\migration_import\data\bim_ctm.ini for Windows.
Failed to execute the BMC Batch Impact Manager CTM New Day Time import
command. Refer to the CONTROL-M/Enterprise Manager Migration Guide to perform
this process manually. BMC Batch Impact Manager related New Day Time
configurations defined on the source environment will not take effect until this process
is completed.
Solution: After migration, execute the following command from the command line:
ecs-no_wrap bimsrv - NewDayTime_migrate=

<emHome>/migration_import/data/bim_ctm.ini for UNIX.
ecs_bim.exe -NewDayTime_migrate=
<emHome>\migration_import\data\bim_ctm.ini for Windows.
Failed to import BMC Batch Impact Manager CTM New Day Time file. Check the
following log file: <EM_HOME>/migration_import/logs/bim_ctm_import.log. For
additional information, refer to the CONTROL-M/Enterprise Manager Migration Guide
to perform this process manually. BMC Batch Impact Manager related New Day Time
configurations defined on the source environment will not take effect until this process
is completed.
Solution: Read the bim_ctm_import.log file for full information on the success or
failure of the import process in the following location of the new version
Appendix D
65
Migrating BMC Batch Impact Manager exceptions
<emHome>/migration_import/logs for UNIX.

<emHome>/migration_import/logs for Windows.
If the process failed, you should manually update the New Day Time value using the
CONTROL-M Configuration Manager GUI. For further information about
CONTROL-M Configuration Manager, refer to the CONTROL-M/Enterprise Manager
Administration Guide.
NOTE
BMC Batch Impact Manager New Day Time definitions that were set in the earlier_version will
not take effect in the new version until this process is completed successfully.
Migrating BMC Batch Impact Manager

exceptions
On the earlier versions of BMC Batch Impact Manager, statistical exceptions were
defined using the BMC Batch Impact Manager Web application and stored in the
bim_statistics.xml file. Starting from version 6.3.01, exceptions are defined using the
CONTROL-M/EM GUI and stored in the database. The bim_statistics.xml file is now
obsolete. The Migration Toolkit migrates BMC Batch Impact Manager exceptions
from the earlier_version bim_statistics.xml file directly to the new version database.
If any step fails during the BMC Batch Impact Manager exceptions import procedure,
for example, BMC Batch Impact Manager exceptions information is not found
because the import process did not locate the earlier_version bim_statistics.xml file,
BMC Batch Impact Manager exceptions must be updated manually. For more
information see Troubleshooting BMC Batch Impact Manager exceptions.
NOTE
If the bim_statistics.xml file did not exist at its designated location in the earlier_version, the
import procedure will skip this step.

If the migration of BMC Batch Impact Manager exception definitions does not
complete successfully, one of the messages below are written to the screen and to
Migration Toolkit log file. The procedure must then be executed manually.
66
Failed to import BMC Batch Impact Manager statistics exceptions file. Refer to the
CONTROL-M/Enterprise Manager Migration Guide to perform this process manually.
BMC Batch Impact Manager related statistical exceptions that were defined on the
previous version will not take effect until this process is completed.
Failed to execute the BMC Batch Impact Manager statistics exceptions import command.
Refer to the CONTROL-M/Enterprise Manager Migration Guide to perform this process
manually. BMC Batch Impact Manager related statistical exceptions that were defined
on the previous version will not take effect until this process is completed.
Solution: After migration, check if the bim_statistics.xml file is present in the
following location of the new version:
<emHome>/migration_import/data for UNIX.
<emHome>\migration_import\data for Windows.
If the file is not present, manually copy it from the earlier_version to the above location
(for UNIX or Windows).
If the source version is 6.1.03 or 6.2.01, execute the following command from the
command line:
esc -no_wrap bimsrv -bim_Xml_to_Scenario=

<emHome>/migration_import/data/bim_statistics.xml for UNIX.
ecs_bim.exe -bim_Xml_to_Scenario=
<emHome>\migration_import\data\bim_statistics.xml for Windows.
If the source version is 6.3.01, after migration, execute the following command from
the command line:
ecs -no_wrap bimsrv -bim_StatExPeriod_to_Scenario=

<emHome>/migration_import/data/bim_statistics.xml for UNIX.
-bimsrv -bim_StatExPeriod_to_Scenario=
<emHome>\migration_import\data\bim_statistics.xml for Windows.
Check for success or failure in the bim_exeptions_import.log file in the following

location of the new version
<emHome>/migration_import/logs for UNIX.
<emHome>/migration_import/logs for Windows.
Appendix D
67
Migrating CONTROL-M/Forecast exception conditions
If the process failed, you must now manually define the statistical exceptions using
the CONTROL-M/EM GUI. For more information see the CONTROL-M/Enterprise
Manager Administration Guide.
NOTE
BMC Batch Impact Manager statistics exceptions that were set in the earlier_version will not
comply with the new version until this process is completed successfully.
Failure to migrate BMC Batch Impact Manager statistics exceptions may influence BMC Batch
Impact Manager estimations reliability.
Migrating CONTROL-M/Forecast exception

conditions
In source versions lower than 6.3.01 Fix Pack3, if the migration of CONTROLM/Forecast exception conditions do not complete successfully the migration
procedure must be executed manually. One of the following error messages are
issued:
Failed to import Forecast rules. For information on how to migrate the CONTROLM/Forecast exception conditions manually, see the CONTROL-M/Enterprise Manager
Migration Guide.
Failed to execute Forecast rules. For information on how to migrate the CONTROLM/Forecast exception conditions manually, see the CONTROL-M/Enterprise Manager
Migration Guide.
68
ecs -no_wrap forecastserver -fc_SimExCond_to_Scenario for UNIX.

emforecastserver -fc_SimExCond_to_Scenario for Windows.
Migrating CONTROL-M/Forecast Historical Data
Migrating CONTROL-M/Forecast Historical

Data
CONTROL-M/Forecast reports are based on CONTROL-M/Forecast Historical data
that resides in the database. This data can be migrated from an earlier_version to the
new version using the Migration Toolkit.
When the Migration Toolkit identifies CONTROL-M/Forecast historical data in the
earlier_version environment, you are prompted to include this data in the CONTROLM/EM migration. No is the suggested default, as migrating the data could require a
significant amount of time, CONTROL-M/Forecast will still accurately generate
information without this data. If you choose to migrate the CONTROL-M/Forecast
data, and the migration of CONTROL-M/Forecast fails, it will have no impact on the
rest of the CONTROL-M/EM migration.
Migrating BMC Batch Impact Manager Web

Application settings from an earlier_version
To preserve the filters setting on the Services List display, you must copy the
earlier_version bim_filters.xml file to the BMC Batch Impact Manager server home
directory of the new version.
<emHome>/appl/bim/etc/bim_filters.xml for UNIX.
<emHome>\bim\etc\bim_filters.xml for Windows.
Re-activating CONTROL-M/Forecast and BMC Batch Impact

Manager
The CONTROL-M/Forecast or BMC Batch Impact Manager when installed on the
destination version but not on the source version reactivates automatically by the
migration toolkit.
If a problem occurs both or one of the following error messages are issued:
Failed to reactivate Forecast. For instruction on how to perform the reactivation process
manually, see the CONTROL-M/Enterprise Manager Migration Guide.
Appendix D
69
Failed to reactivate BMC Batch Impact Manager. For instruction on how to perform the
reactivation process manually, see the CONTROL-M/Enterprise Manager Migration
Guide.
70
For Forecast on UNIX: ecs -no_wrap forecastserver -install

For Forecast on Windows: emforecastserver -install
For BMC Batch Impact Manager on UNIX: ecs -no_wrap bimsrv -install
For BMC Batch Impact Manager on Windows: ecs_bim -install
Appendix
CONTROL-M/EM Migration Toolkit

debugging mechanism
E
The Migration Toolkit can generate high-level debugging information for analysis by
BMC Software customer support. The debugging mechanism can be used as follows:
If a problem occurs during the export stage:

On UNIX systems, run the following command from the
<emHome>>/migration_export directory:
export -debug
On Microsoft Windows systems, run the following command from the
<emHome>>\migration_export directory:
export.bat -debug
The export debugging information is saved in the ecs_migration.txt Migration
Toolkit log file, which is located at:
For UNIX: <emHome>>/migration_export/logs
For Windows: <emHome>>\migration_export\logs
If a problem occurs during the import stage:

On UNIX systems, run the following command from the
<emHome>/migration_import directory:
import -debug
On Microsoft Windows systems, run the following command from the
<emHome>\migration_import directory:
import.bat -debug
Appendix E
CONTROL-M/EM Migration Toolkit debugging mechanism
71
The import debugging information is saved in the ecs_migration.txt Migration

Toolkit log file, which is located at:
For UNIX: <emHome>>/migration_import/logs
For Windows: <emHome>>\migration_import\logs (Windows)
Additional debugging information is saved in the util.log and util_auth.log files,
which are located at:
Export debugging information

For UNIX: <emHome>>/migration_export/logs
For Windows: <emHome>>\migration_export\logs
Import debugging information

For UNIX: <emHome>>/migration_import/logs
For Windows: <emHome>>\migration_import\logs
If a problems occurs during the execution stage of the "util" as part of the migration
tool-kit operation, use the flag "-debug_util" as opposed to "-debug".
72
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
A
Audit facility 34
authorizations
conflicting 21
defining 35
exporting
considerations 14
earlier_version data 18
migration_export directory 17
saving .tar file before uninstalling 20
F
files
BIM migration procedures 63

bim_ctm.ini file 64
bim_ctm_import.log file 65
bim_exeptions_import.log file 67
bim_statistics.xml file 66
BMC Software, contacting 2
BMI exceptions, migrating 66
bim_ctm.ini 64
bim_ctm_import.log 65
bim_exeptions_import.log 67
bim_statistics.xml 66
ECSExportForMigration.tar 19
migrate_.log 23
migrate_dc utility 23
root_menu script 37, 40, 46
ValidityReport.out 17
Forecast historical data, migrating 69
CONTROL-M/EM database, loading modes 36

CORBA 30
customer support 3
Gateway log file location 27

GCS. See Global Conditions Server
Global Alerts Server, multiple 28
diagnostics 36
log file location 27
GUI server, multiple 28
D
data center host name and port 24
database, loading modes for CONTROL-M/EM 36
defining authorizations 35
diagnostics
See also messages
Global Conditions Server (GCS) 36
differences between 6.1.03 and 6.2.01 27, 38, 48
Displayed Jobs filter with special characters 59
H
historical data, migrating Forecast 69
host name of
data center 24
server components 28
ECSExportForMigration.tar file 19
error messages 55
exceptions, BMI 66
illegal TAB sign 58

importing
exported data 20
Index
73
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
Forecast historical data 21
initialization file (.ini). See files
prefixes, message 55
product support 3
job processing definitions, synchronizing 23
Readiness report 55
Reporting facility 34
Resource Authorizations with special characters 59
root_menu script 37, 40, 46
L
loading modes for CONTROL-M/EM database 36
log files
bim_ctm_import.log 65
bim_exeptions_import.log 67
for migrate_dc utility 23
location of Gateway and GCS 27
logical name of server components 28
M
messages
analyzing 58
prefixes for 55
Readiness report 56
migrate_.log files 23
migrate_dc utility
how to use 24
job processing definitions 23
log files 23
migrating
BIM exceptions 66
CONTROL-M/Server definitions 22
Forecast historical data 69
from version 6.1.03 27, 38, 48
New Day Time parameter 64
overview 9
multiple servers on one computer 28
N
New Day Time parameter, migrating 64
O
operating systems, supported 27, 38
Orbix 30
P
parameters
New Day Time 64
platforms, supported 27, 38
port for data center 24
74
S
servers, multiple on one computer 28
special characters
error message 58
in Displayed Job filter 59
in Resource Authorization 59
SSL 30
support, customer 3
supported platforms 27, 38
synchronizing job processing definitions 23
T
TAB sign, illegal 58, 60
TAO 30
tar file. See files
technical support 3
V
validating earlier_version data 16
ValidityReport.out file 17
version 6.1.03, migration to 6.2.01 27, 38, 48
Notes
*70704*
*40707*
*40707*
*40707*
*40707*

Control M em Migration

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Control M em Migration

Transféré par

Droits d'auteur :

Formats disponibles

CONTROL-M/Enterprise Manager

Contacting BMC Software

United States and Canada

BMC SOFTWARE INC

713 918 8800 or

(01) 713 918 8000

713 918 8000

Outside United States and Canada

(01) 713 918 8800

Copyright 2008 BMC Software, Inc.

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

operating system and environment information

sequence of events leading to the issue

commands and options that you used

product error messages

CONTROL-M/EM Migration Guide

The Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Migrating information from previous versions

CONTROL-M/EM optional migration procedures

Synchronizing CONTROL-M/Server job processing definitions. . . . . . . . . . . . . . . . . 23

Readiness report messages

Readiness report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

BMC Batch Impact Manager and CONTROL-M/Forecast migration

Migrating Remedy system parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Re-activating CONTROL-M/Forecast and BMC Batch Impact Manager . . . . . . . 69

CONTROL-M/EM Migration Toolkit debugging mechanism

CONTROL-M/EM Migration Guide

CONTROL-M/EM Migration Guide

Chapter 1 Migration overview

The Migration Toolkit

The Migration Toolkit

CONTROL-M/EM Migration Guide

1 Validate the existing data.

Migrated and non-migrated information

CONTROL-M/EM versions 6.1.03, 6.2.01, and 6.3.01

Job processing definitions

Active jobs, conditions, and resources.

CONTROL-M/EM Migration Guide

Migrating information from previous

1. Installing the Migration Toolkit

The Migration Toolkit must be installed in

2. Ensuring data correctness

Use the Migration Toolkit to examine the

3. Exporting the earlier_version data

Use the Migration Toolkit to export the

4. Importing the exported data to the new

Import the error-free data to the new version

Migrating information from previous versions

Backup the current environment.

Uninstall all old Migration Toolkit software.

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

Acquire the necessary database password or administrator passwords.

If you are migrating both CONTROL-M/EM and CONTROL-M/Server, until

If you want to migrate your CONTROL-M/EM database configuration

If you are running CONTROL-M/Server for UNIX or Windows previous to

If you are running CONTROL-M/Server for z/OS or OS/390 previous to version

If you are running a non-English locale on UNIX, see Preparing to migrate a

CONTROL-M/EM Migration Guide

Preparing to migrate a non-English locale on UNIX

Preparing to migrate a non-English locale on UNIX

1 Note the current value of the environment variable LC_ALL.