Documente Academic
Documente Profesional
Documente Cultură
Migration Guide
Supporting
Version 6.4.01 of CONTROL-M/Enterprise Manager
August 2008
www.bmc.com
Telephone
Fax
Fax
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.
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
product information
product name
product version (release number)
license number and password (trial or permanent)
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
messages received (and the time and date that you received them)
Contents
Chapter 1
Migration overview
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
Whats different
27
Appendix C
55
63
64
64
64
66
66
68
69
69
5
71
Tables
Migrated and non-migrated information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration from version 6.1.03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration from version 6.2.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration from version 6.3.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
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.
10
Migrated data
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 Data
Non-Migrated Data
Chapter 1
Migration overview
11
Migrated data
12
Chapter
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
Chapter 2
13
Pre-migration considerations
Pre-migration considerations
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.
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
3 After the Migration Toolkit has been installed, set the environment variable
LC_ALL back to the original value noted.
Chapter 2
15
3 To check if the installation was successful, open the installation log file:
${HOME}/log/ctmem_migration_install_log.txt
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.
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.
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
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.
18
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:
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.
$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
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.
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
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.
5 Manually remove the directories of the ToolKit from the old and new
environments.
Chapter 2
21
22
Appendix
Migrating SSL
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.
The utility logs its operation for each data center that is migrated in:
23
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.
hostname is the data center host name (maximum length: 255 characters)
24
Migrating SSL
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.
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.
Differences relevant to migration from version 6.2.01 are in Table 4 on page 38.
Differences relevant to migration from version 6.3.01 are in Table 5 on page 45.
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
Component
or feature
Version 6.1.03
Version 6.4.01
Supported platforms
Microsoft Windows
Appendix B
Whats different
27
Table 3
Component
or feature
Side by side
installation
Version 6.1.03
Version 6.4.01
N/A
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.
N/A
28
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
configured in the Tools->System
Parameters menu of the system
parameters window. It is represented by
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
SSL
30
Table 3
Component
or feature
GCS and Gateway
Version 6.1.03
N/A
Version 6.4.01
Appendix B
Whats different
31
Table 3
Component
or feature
Version 6.1.03
N/A
Version 6.4.01
32
Table 3
Component
or feature
Version 6.1.03
Version 6.4.01
Utility Scripts
Increased usage of
resources due to
archived Viewpoints
and playback
N/A
Appendix B
Whats different
33
Table 3
Component
or feature
Version 6.1.03
Version 6.4.01
Reporting
Auditing
34
Table 3
Component
or feature
Defining
Authorizations
Version 6.1.03
Version 6.4.01
Appendix B
Whats different
35
Table 3
Component
or feature
Version 6.1.03
Version 6.4.01
GCS
CONTROL-M/EM
scripts used to control
the Administration
Agent in UNIX
environments
N/A
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
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
Appendix B
Whats different
37
Table 3
Component
or feature
Increased gateway
CPU consumption
Version 6.1.03
Version 6.4.01
N/A
Increased gateway
N/A
memory consumption
N/A
BIM memory
consumption
Table 4
Component
or feature
Supported Platforms
38
Version 6.2.01
Version 6.4.01
Table 4
Component
or feature
Side by side
installation
Version 6.2.01
Version 6.4.01
N/A
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.
N/A
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
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
configured in the Tools->System
Parameters menu of the system
parameters window. It is represented by
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
information, see CONTROL-M/EM
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
N/A
Version 6.4.01
N/A
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
CONTROL-M/EM
scripts used to control
the Administration
Agent in UNIX
environments
CONTROL-M/EM
Server
42
Table 4
Component
or feature
Utility Scripts
Version 6.2.01
Version 6.4.01
Appendix B
Whats different
43
Table 4
Component
or feature
GCS and Gateway
Version 6.2.01
N/A
The following Default.rsc file
parameters have been converted
to 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
cond_diag
int_diag
msg_diag
gcs_log_size
max_gcs_logs
Version 6.4.01
N/A
BIM memory
consumption
N/A
44
Table 5
Component of
feature
Version 6.3.01
MaxUpdatedJobstoAudit - An
available system parameter.
PasswordEncode - The default
value is 1.
Version 6.4.01
(Unix only) The component binaries are now 64
bit.
BIM Exception
Manager
EM API package
Utility Scripts
Appendix B
Whats different
45
Table 5
Component of
feature
Version 6.3.01
root_menu script
N/A
Database
connections
46
Version 6.4.01
Table 5
Component of
feature
Version 6.3.01
Version 6.4.01
N/A
Database Disk
Space
N/A
BIM memory
consumption
N/A
Appendix B
Whats different
47
Table 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.
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
condition inheritance
48
Table 6
Category of changes
Description
Change
6.2.01
6.4.01
Templates replace
skeletons 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
Workspaces replace
modes in
CONTROL-M/Desktop
Work is performed in
CONTROL-M/Desktop in online
or local mode.
Order/Force in
CONTROL-M/EM
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.
Table 6
Category of changes
Description
Change
6.2.01
6.4.01
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
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.
Order/Force
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
Communication menu
options (menu no longer
exists)
52
6.2.01
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
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
JEF
Drafts
Appendix B
Whats different
53
Table 7
Category of changes
Description
Change
6.3.01
6.4.01
CONTROL-M
Configuration Manager
Agent window
Agent System
Agent system parameters are
parameters configuration configured in the agent
installation.
Reporting facility
command line utility
Forecast Gantt
Calendar definition
Authorization
There is only a BMC Batch Impact There is a new BMC Batch Impact
Manager authorization.
Manager and Forecast authorization.
Job definition
comparison
Auditing
Application fields
Job templates
Find
54
Appendix
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
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.
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
ERR messages
WRN messages
INF messages
None.
Messages
ERR30001
ERR30002
ERR30003
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: ,^
System Action: The export procedure cannot process the data.
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.
ERR30005
ERR30006
ERR30007
Appendix C
59
Messages
ERR40001
ERR40002
ERR40003
INF30001
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
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
WRN40001
WRN50001
Appendix C
61
Messages
62
Appendix
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.
Appendix D
63
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.
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:
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_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_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
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.
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.
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:
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:
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:
-bimsrv -bim_StatExPeriod_to_Scenario=
<emHome>\migration_import\data\bim_statistics.xml for Windows.
Appendix D
67
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.
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.
Solution: After migration, execute the following command from the command line:
68
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.
Solution: After migration, execute the following command from the command line:
70
Appendix
The Migration Toolkit can generate high-level debugging information for analysis by
BMC Software customer support. The debugging mechanism can be used as follows:
Appendix E
71
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_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
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
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
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*