Professional Documents
Culture Documents
Migration Guide
Supporting
Version 6.4.01 of CONTROL-M/Server for UNIX® and
Microsoft Windows
September 2008
www.bmc.com
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC Telephone 713 918 8800 or Fax 713 918 8000
2101 CITYWEST BLVD 800 841 2031
HOUSTON TX 77042-2827
USA
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000
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
3
4 CONTROL-M/Server Migration Guide
Contents
Chapter 1 Migration overview 7
The Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Migrating data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Index 29
Contents 5
6 CONTROL-M/Server Migration Guide
Chapter
1
1 Migration overview
This guide explains how to migrate CONTROL-M/Server data from earlier versions
to version 6.4.01. Versions that can be migrated are:
■ CONTROL-M/Server 6.1.03 UNIX and Windows all releases from the major one,
including all fix packs
■ CONTROL-M/Server 6.2.01 UNIX and Windows, all releases from the major one,
including all fix packs
■ CONTROL-M/Server 6.3.01 UNIX and Windows, all releases from the major one,
including all fix packs
The term earlier_version used in this guide refers to any of the above products.
■ UNIX to UNIX
■ Windows to Windows
■ UNIX to Windows
■ Windows to UNIX
■ from one UNIX platform to another (for example, from Solaris to HP-UX-11)
NOTE
The removal of the earlier_version CONTROL-M/Server software and the installation of the
new software is handled separately and is not within the scope of this book. For information
on installing and uninstalling the CONTROL-M/Server software, see the CONTROL-M
Installation Guide.
You should be aware that configuration settings are not always transferred to the new
installation along with the data. For precise information, see Table 1 on page 9.
If you have installed the full CONTROL-M solution, migration must be performed in
the following order:
1. CONTROL-M/EM
2. CONTROL-M/Server
3. CONTROL-M/Agents
BMC Software recommends planning for the new version well in advance.
Installation of the new CONTROL-M software and setting up the environment can be
accomplished in a relatively short time frame (from several hours to several days
depending on the complexity of your system). However, preparing the earlier_version
data for migration can take several weeks.
The best method of ensuring a smooth transition from the earlier_version to the new
version is to use the parallel installation method. For more information, see “Parallel
and non-parallel installations” on page 14.
NOTE
CONTROL-M/Agents should not be installed or upgraded until the new version of
CONTROL-M/Server is installed and the earlier_version data migrated.
There may be some data that cannot be adjusted while you are still using the current
version. This is usually due to new features implemented for the new version you are
about to install, which are not recognized by the current version. These occurrences
are listed in the individual messages of the Readiness report (see Appendix A,
“Readiness report messages” on page 23).
After you are satisfied that the current version data is fully ready for the new version,
you can transfer all the converted data to the new version environment and resume
production in a minimum amount of time.
Migrating data
The types of CONTROL-M/Server data that can and cannot be migrated are shown
in Table 1 and Table 2.
WARNING
After migration, some configuration parameters such as
WD_ERROR_HANDLER_SCRIPT_FILE, WD_USEREXIT_# _SCRIPT_FILE may need to be
adjusted to the new environment values.
2
2 Migrating from previous versions
This chapter guides you through the process of migrating CONTROL-M/Server data
from an earlier_version.
The migration procedure is performed using the sequential steps presented in the
following table:
Pre-migration considerations
Before beginning the migration procedure consider the following:
■ 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.
■ If your environment uses a database server that is not case-sensitive, see the
appendix called “Working with Databases that are not Case-Sensitive” in the
CONTROL-M Installation Guide.
If you 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:
2 Export the validated data to a location where it will be available for import to the
new version.
The parallel installation method uses the same set of instruction except for step 3.
With this method, the earlier_version can be uninstalled after the full migration
procedure is completed.
2 Download the install_migration script for the UNIX Migration Toolkit to the
home directory. The migration toolkit is available on the BMC Software Customer
Support Web site (http://www.bmc.com/support_home) in solution
SLN000015061431.
4 To check if the installation was successful, open the following installation log file:
${HOME}/log/cts_migration_install_log.txt
If you are working with a non-English version of Windows, before installing the
Windows Migration Toolkit, set the system locale and language settings to English as
follows:
1 Select Western Europe and United States in Control Panel => Regional and
Language Options for the system to receive all messages in English.
2 Select English (US) in Control Panel => Regional and Language Options => to set
the locale to English.
After installation you can reconfigure your computer to operate in a language other
than English. For more information, see the CONTROL-M Language Customization
Guide.
4 To check if the installation was successful, review the installation log file:
%TEMP%\ctms_migration_install_log.txt
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.
When a problem with the data is detected, a message is written to the Readiness
report as described below in step 2.
To check validity and to ensure that your earlier_version definitions will function
correctly in the new release, perform the following data validation procedure.
NOTE
If you are working with a non-English version of Windows, before activating the Migration
Toolkit and running any command, set the system locale and language settings to English as
described in “Installing the Migration Toolkit on Windows” on page 16
1 Ensure that one of the following is your working directory and then run the
migration command to activate the Migration Toolkit.
2 Choose the Validation option in the Migration menu. This step generates the
Readiness report.
TIP
It is recommended that you stop running CONTROL-M/Server, in order to assure that you
are generating the most recent report.
3 Analyze the results and correct all errors. Data that generated informational
messages and warnings will be automatically adjusted when imported to the new
version as specified in the Readiness report.
You can view the Readiness report online by selecting View Readiness Report from
the Migration menu. For a printed copy of the report, print the ValidityReport.out
file from the migrate_ctm directory. Alternatively, you can use a text editor to view
the report.
All errors must be corrected before importing the data. Due to new features
implemented for the version you are about to install, some errors can be corrected
only when the current version is about to be shut down for the final time.
Information on these and other errors is listed in the Readiness report. Just before
shutdown, these errors must be corrected and a final version of the data exported
using the Migration Toolkit. For information about analyzing the Readiness report,
see “Messages” on page 24.
Repeat the data validity check until no error messages are generated (except for
errors that need to be corrected after the new version is running). When there are no
error messages, the data is ready to be exported (see “Exporting the earlier_version
data”).
Iterations of the report are stored in the same directory. A sequence number is
appended to the report name so that you can compare the reports. Readiness report
message types are described in Appendix A.
NOTE
If you are working with a non-English version of Windows, before activating the Migration
Toolkit and running any command, set the system locale and language settings to English as
described in “Installing the Migration Toolkit on Windows” on page 16
1 Ensure that one of the following is your working directory and then run the
migration command to activate the Migration Toolkit.
The Export step also generates another copy of the Readiness report,
ValidityReport.out, in the migrate_ctm directory.
3 Copy the exported files to a location that can be accessed by the new release
environment. Do not change the exported file names as the import process requires
the files to have the same names given to them by the export process.
■ Windows to UNIX:
WARNING
If the exported files are copied using FTP, they must be transferred in binary mode.
At this point, the entire earlier_version environment can be backed up and removed.
For details on how to uninstall the earlier_version, see the CONTROL-M Installation
Guide.
ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Server_for_UNIX_a
nd_Microsoft_Windows
To install CONTROL-M/Server and the latest Fix Packs, see the CONTROL-M
Installation Guide.
NOTE
You do not have to install the Migration Toolkit, because it is integrated in to the
CONTROL-M/Server 6.4.01 installation.
If you plan to uninstall the earlier_version of CONTROL-M/Server, you must save the
exported files to a location outside the account as it will be erased when the earlier_version is
uninstalled.
NOTE
If you are working with a non-English version of Windows, before activating the Migration
Toolkit and running any command, set the system locale and language settings to English as
described in “Installing the Migration Toolkit on Windows” on page 16
NOTE
You can view the status of the CONTROL-M/Server, CONTROL-M/Server Configuration
Agent, and database server by running ctm_menu => CONTROL-M Manager => Check All
in the command line window.
1 Ensure that the exported earlier_version files are accessible to the new
CONTROL-M/Server version and import the export data as follows:
The import process converts the data and imports it into the new environment.
Data for which informational messages and warnings were generated are
automatically adjusted to comply with the new version format.
B If you have jobs for which no node group is defined (these jobs ran on a local
agent in an earlier_version CONTROL-M/Server), and your
CONTROL-M/Server 6.4.01 installation is located on a different computer from
the Agent, you will need to either point these jobs to the agent on the
earlier_version computer, or configure the local agent on the
CONTROL-M/Server 6.4.01 computer.
NOTE
If you migrated CONTROL-M/Server to a different computer, reconfigure the host
name and port system parameters in the CONTROL-M/EM database. For more
information, see the CONTROL-M Administrator Guide.
5 If you are migrating from CONTROL-M/Server version 6.1.03, you will need to
configure the CTM_ADJUST_COND_SCOPE parameter manually in the
config.dat file as follows:
A If you want this parameter to relate to jobs at the group level, set the value of
CTM_ADJUST_COND_SCOPE to GROUP.
B If you want this parameter to relate to jobs at the at the active jobs file level, set
the value of CTM_ADJUST_COND_SCOPE to AJF.
NOTE
For more information about specific parameters that are migrated, see “Migrating
data” on page 9.
NOTE
On Unix, the ctmldnrs.dat is deleted from the default location
(<ctmHomeDir>/ctm_server/tmp) when CONTROL-M/Server is started.
7 BMC Software recommends that immediately after you have completed data
import and migration of CONTROL-M/Server definitions, you synchronize your
data by downloading it to CONTROL-M/EM.
9 Manually remove the directories of the Migration ToolKit from the earlier_version
environment.
10 You can now uninstall the earlier_version (if you have not already done so).
A
A Readiness report messages
Messages are prefixed according to message type. Each message type has a unique
prefix describing the nature of the message as explained in the following table.
Prefix Description
ERR Error
Error messages indicate that job processing definitions contain values that are
inconsistent with new version formats. These values might affect job
scheduling.
You must manually correct the errors identified in job processing definitions
before continuing the migration.
Errors in a job in the Active Jobs file must be corrected, or the job must
removed from the file. If you can, manually correct the errors. If not, the job
can be removed by the New Day procedure at the beginning of the next day.
Otherwise, you can manually request the job to be deleted during the next
daily maintenance.).
INFO Information
These messages indicate that the data contains values that are no longer
relevant or supported in the new version.The data will automatically be
corrected during the “import” process. No manual changes are required or
accepted. The automatic changes will not affect your new version scheduling
environment.
WRN Warning
These messages indicate that job processing definitions in your current
environment contain statements that have no production meaning. For
example, an ON statement with no DO action, or a SHOUT statement with no
destination.
You can correct these warning situations (for example, you can add a DO
action to an ON statement, or a destination to a SHOUT statement). However,
if you choose not to correct these warnings, the problematic statements will be
removed during the “import” process to the new version. These changes will
not affect your scheduling environment.
msg_code message_text
___________________________________________________
Error Code: entity_name [entity_name] [entity_name]
xxxnn aaaaaaaaa
xxxnn bbbbbbbbb etc.
xxxnn ccccccccc
Example
This example displays a problem with the quantitative resource name in a job
processing definition:
Messages
ERR01 Periodic calendar has “Y” or “N” values
User Response: Verify that the calendar is a periodic calendar and delete all Y and N
values. If you determine that the calendar is a regular calendar, ensure that the
calendar has only N and Y values. You can use CONTROL-M/EM Desktop or
CONTROL-M/EM utilities to define the calendars correctly.
ERR02 Condition in the Conditions file contains an invalid date: **** or $$$$
Explanation: **** and $$$$ cannot be specified as the date for a condition in the
Conditions file.
System Action: The export procedure cannot process the data. The system may issue
other error messages to this report that indicate which job processing definitions
create or use these improperly named conditions.
User Response: Delete the condition from the Conditions file, and reenter the
condition with a valid date. (You can use the Conditions window to delete and add
the condition.) Also, correct the source of the condition (for example, an OUT
statement or a script that invokes a CONTROL-M utility).
ERR03 Condition name in the Conditions file contains one or more of the following
invalid characters: “(“, “)”, “|” and/or an embedded space
Explanation: Condition names cannot contain the “(“, “)”, or “|” characters or
embedded spaces.
System Action: The export procedure cannot process the data. The system might issue
other error messages to this report that indicate which job processing definitions
create or use these improperly named conditions.
User Response: Use the Conditions window to delete the condition from the
Conditions file, and reenter the condition with a valid name. Also, correct the source
of the condition (for example, an OUT statement or a utility) and any jobs that use the
condition as an IN condition.
ERR101 Quantitative resource name in the Active Jobs file cannot be set to a blank
value
User Response: In the Active Jobs file, manually specify a valid value for the resource
name, or delete the resource from the job.
ERR93 More than one IN condition of the job has a row order of 1
Explanation: The IN conditions of a job in the Active Jobs file are not ordered, since
more than one IN condition has a row order of 1.
System Action: CONTROL-M/Server cannot automatically decide the correct order of
the IN conditions, and therefore the export procedure cannot process the data.
User Response: You can do one of the following:
■ Redefine the conditions of the job using Zoom & Save in CONTROL-M/Enterprise
Manager.
■ Remove the job. Either remove it manually, or wait until the New Day procedure
removes it automatically.
If you are migrating from version 6.1.03, install the latest fix pack in order to prevent
newly created jobs from having this problem.
ERR94 More than one OUT condition of the job has a row order of 1
Explanation: The OUT conditions of a job in the Active Jobs file are not ordered, since
more than one OUT condition has a row order of 1.
System Action: CONTROL-M/Server cannot automatically decide the correct order of
the OUT conditions, and therefore the export procedure cannot process the data.
If you are migrating from version 6.1.03, install the latest fix pack in order to prevent
newly created jobs from having this problem.
Index
Symbols
.tar file, saving 20 I
importing
B exported data 19
install_migration script 15
BMC Software, contacting 2 install_migration.exe file 16
invalid characters
error message 25
C invalid date
error message 25
configuration parameters 21
CONTROL-M/Agent 22
reconfiguration 21
customer support 3
L
language settings
Windows 16
D locale settings 16
data
synchronization 22
M
messages
E analyzing 24
prefixes for 23
embedded space Readiness report 24
error message 25 migrating
error messages 23 overview 7
executable files. See files
exporting
considerations 14
saving .tar file before uninstalling 20
N
non-English versions of Windows 16
F
files
P
install_migration script 15 periodic calendar
install_migration.exe 16 error message 24
ValidityReport.out 17 port 21
prefixes, message 23
product support 3
H
host name 21
Q
quantity zero
Index 29
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
error message 26
R
Readiness report 23
reconfiguring
CONTROL-M/Agents 21
host name and port 21
regional settings 16
S
support, customer 3
synchronizing data 22
T
tar file. See files 20
technical support 3
V
validating earlier_version data 16
ValidityReport.out file 17