70705

8/7/2019 70705

1/32

www.bmc.com

CONTROL-M/ServerMigration Guide

Supporting

Version 6.4.01 of CONTROL-M/Server for UNIX and

Microsoft Windows

September 2008

8/7/2019 70705

2/32

Contacting BMC Software

You can access the BMC Software w ebsite at http:/ / www.bmc.com. From this website, you can obtain informationabout 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 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

Copyright 2008 BMC Softwar e, Inc.

BMC, BMC Softwar e, and the BMC Softwar e logo are the exclusive pro perties of BMC Software, Inc., are registered with the U.S. Patent

and Trademar k Office, and may be registered or pend ing registration in oth er countries. All other BMC trad emarks, service marks, and

logos may be registered or pend ing registration in the U.S. or in other coun tries. All other tradema rks or registered trad emarks are theproperty of their respective owners.

CONTROL-M/Server Migration GuideAll IBM trademarks that are referred to or displaye d in the document are trademarks or

registered trad emarks of International Business Machines Corpor ation in the Un ited States, other count ries, or both.

ITIL is a registered trad emark, and a registered comm un ity tradem ark of the Office of Governm ent Comm erce, and is registered in the

U.S. Patent and Trademar k Office, and is used here by BMC Software, Inc., und er license from and with the p ermission of OGC.

Linux is the registered trad emark of Linu s Torvalds.

Oracle is a registered trad emark of Oracle Corporation.

UNIX is the registered tradem ark of The Open Grou p in the US and other coun tries.

BMC Softwar e considers information included in this docum entation to be p roprietary an d confidential. Your u se of this information is

subject to the terms and cond itions of the app licable End U ser License Agreement for the prod uct and t he prop rietary and r estricted

rights notices included in this documentation.

Restricted rights legend

U.S. Gover nm ent Restricted Rights to Com pu ter Softwar e. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COP YRIGHT LAWS OF

THE UNITED STATES. Use, du plication, or disclosure of any data and compu ter software by the U.S. Governmen t 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 am end ed from time t o tim e. Cont ractor/ Manufactu rer is BMC SOFTWARE INC , 2101 CITYWEST BLVD,

HOUSTON TX 77042-2827, USA. Any contract notices shou ld b e sent to this add ress.
http://www.bmc.com/http://www.bmc.com/http://www.bmc.com/

8/7/2019 70705

3/32

3

Customer support

You can obtain technical support by using the BMC Software Customer Support website or by contacting CustomerSupp ort by teleph one or e-mail. To exped ite your inqu iry, see Before contacting BMC.

Support website

You can obta in technical sup port from BMC 24 hours a d ay, 7 days a week at http:/ / ww w.bmc.com/ supp ort_home.

From this website, you can

read overviews abou t sup port services and programs that BMC offers

find the most current information about BMC p rodu cts

search a database for issues similar to yours and possible solutions

order or d ownload p roduct documentation

download p roducts and m aintenance

report an issue or ask a question

subscribe to receive proa ctive e-ma il alerts when new produ ct notices are released find worldw ide BMC supp ort center locations and contact information, includ ing e-mail addresses, fax nu mbers, and

telephone numbers

Support by telephone or e-mail

In the United States and Can ada, if you n eed techn ical sup port and do n ot have access to the w eb, call 800 537 1813 or

send an e-mail message to custom er_sup [email protected]. (In th e su bject line, enter SupID :,

such as Sup ID:12345). Outside th e United States and Canada , contact you r local sup por t center for assistance.

Before contacting BMC

Have th e following information available so that Cu stomer Supp ort can begin working on you r issue immed iately:

prod uct 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 hardw are configuration

serial num bers

related software (database, application, and commun ication) including typ e, version, and service pack or

maintenance level

sequence of events leading to the issue

command s and options that you used

messages received (and the time and d ate that you received them )

product error messages

messages from the operating system, such as f i l e s y s t e m f u l l

messages from related software
http://www.bmc.com/support_homehttp://www.bmc.com/support_homemailto:[email protected]:[email protected]:[email protected]://www.bmc.com/support_home

8/7/2019 70705

4/32

4 CONTROL-M/Server Migration Guide

8/7/2019 70705

5/32

Contents 5

Contents

Chapter 1 Migration overview 7

The Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Migrating d ata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Migrating from previous versions 13

Pre-migration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Parallel an d non-parallel insta llation s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing the Migr ation Toolkit on UN IX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing th e Migration Toolkit on Wind ow s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Ensu ring d ata correctness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Exporting the earlier_versiondata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Imp orting the expor ted data to the new version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Appendix A Readiness report messages 23

Read iness report form at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Analyzing rep ort messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Index 29

8/7/2019 70705

6/32


8/7/2019 70705

7/32


C h a p t e r 11Migration overview

This guide explains how to migrate CON TROL-M/ Server data from earlier versions

to version 6.4.01. Versions th at can be m igrated are:

CON TROL-M/ Server 6.1.03 UNIX and Wind ows all releases from the m ajor on e,

includ ing all fix packs

CON TROL-M/ Server 6.2.01 UNIX and Wind ows, all releases from th e major on e,


CON TROL-M/ Server 6.3.01 UNIX and Wind ows, all releases from th e major on e,


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

CON TROL-M/ Server data can be migrated

across platform s such as:

UNIX to UN IX

Window s to Window s

UNIX to Window s

Window s to UNIX

from on e UN IX platform to another (for example, from Solaris to H P-UX-11)

between d ifferent database typ es. For example, from MSSQL/ Oracle/ Sybase toMSSQL/ Oracle/ Sybase/ PostgresSQL.

NOTEThe removal of the earlier_version CONTROL-M/ Server software and the installation of the

new software is han dled separately and is not within the scope of this book. For information

on installing an d un installing th e CONTROL-M/ Server software, see the CONTROL-M

Installation Guide.

You sh ould be aw are that configuration settings are not alway s transferred to the new

installation along with the d ata. For p recise information, see Table 1 on p age 9.
http://-/?-http://-/?-

8/7/2019 70705

8/32

The Migration Toolkit


If you have installed the full CONTROL-M solution, migration m ust be p erformed in

the following order:

1. CONTROL-M/ EM

2. CONTROL-M/ Server

3. CONTROL-M/ Agents

This sequen ce is imp ortant as a new version of CON TROL-M/ EM can work w ith an

earlier version of CONTROL-M/ Server, but the opp osite is not tru e.

BMC Software recomm end s plann ing for the new version well in adva nce.

Installation of the new CON TROL-M software and setting up th e environm ent can be

accomp lished in a relatively short time fram e (from several hou rs to several days

dep ending on the complexity of your system). H owever, preparing the earlier_version

data for migration can take several weeks.

The best m ethod of ensuring a smooth transition from th e earlier_version to the new

version is to use the parallel installation meth od . For more information, see Parallel

and non-parallel installations on p age 14.

The Migration Toolkit

The Migration Toolkit is used to test the earlier_version CONTROL-M/ Server

database d ata (the data belonging to th e version you are current u sing) and adjust it

as necessary to meet the requ irements of the new version. It can be accomp lished

directly in you r current p rodu ction environment w ithout first having to install the

new version software.

There may be some d ata that cannot be ad justed wh ile you are still using the current

version. This is usually du e to new features implemented for the n ew version you are

abou t to install, which are not recognized by the current version. These occurren ces

are listed in th e individu al messages of the Read iness report (see Appendix A,

Readiness report m essages on page 23).

After you are satisfied that the cur rent version d ata is fully ready for the new version,

you can transfer all the converted d ata to the new version environm ent and resume

prod uction in a minimu m am ount of time.

NOTECONTROL-M/ Agents shou ld not be installed or u pgrad ed u ntil the new version ofCON TROL-M/ Server is installed and the earlier_version data migrated.

8/7/2019 70705

9/32

Migrating data


Migrating data

The types of CONTROL-M/ Server d ata that can an d cannot be migrated are show n

in Table 1 an d Table 2.

Table 1 Migrating data

Migrating Data Comments

Database data Types of database data:

Job processing definitions

Calendar definitions

Active environm ent

Security d efinitions

Configuration parameters

CON TROL-M/ Server configura tion

files (config.dat, TimeZone.dat):

Not all configuration p arameters ar e migrated. See

Table 2.

CONTROL-M/ Agent statuses

(AGSTAT d irectory)

The disabled agents m aintain their status when

migrated from th e export env ironment . statuses of the

non-disabled remote hosts and / or non-disabled

regular agents are changed to d iscovery status.

CONTROL-M/ Agent param eters

(AGPRM directory)

This directory contains pre-defined agent specific

param eter files.

Manu al conditions file ctmldnrs.dat

(created by th e ctmld nrs u tility)

This file will be migrated only if it exists in the d efault

/tmp directory.

System parameters N/ A

SSL certifications

The SSL kdb files on the import

environment are und er

/ctm_server/data/

SSL/cert directory.

SSL migration is not available when migrating from

UNIX to Window s or from Wind ows to UN IX.

SSL migration is available only when migrating from

UNIX to UNIX and from Window s to Window s. The

Secur e Sockets Layer pa rameter m ust be set to

ENABLED.

This param eter can be viewed by ru nning th e

following command:

ctm_menu=> Parameter Customization => System

Parameters and Shout D estination Tables => System

Parameters => Next Page =>Secure Sockets Layer.Lists of utilities permitted to be

activated by CONTROL-M/ Agen ts.

Located in the

/data/AGDEFS/AGUTILS_PERMIT file and the content of the AGPERMIT_UTILS

directory.

Remote agent maps The /data/AGSTAT_RJX

directory is migrated.

Remedy parameters A ll Remedy configurat ion parameters located in the

exported ctmHomeDir\ data\ config .dat file are

migrated to the new RemedyConf.xml file located in

ctm\ \ data\ remedy directory.
http://-/?-http://-/?-

8/7/2019 70705

10/32

Migrating data


Table 2 Non-migrating data

Non--migrating data Comments

Configuration parameters CTM_RT_PORT_NUMBER

CONTROLM_DATABASE

OS_PRM_SOCKET_PORT_NUM OS_PRM_LOCK_DIR

OS_PRM_HOSTNAME

CTMS_HOSTNAME

CTMS_PORT_NUM

TMP_PATH

MAIL_HANDLER

CD_IPC_IN

CD_IPC_OUT

CTM_SEM_KEY_ID

CTM_SEM_TIMEOUT

MAX_GET_HOST_RETRIES

Remedy related parametersConfiguration files Process param eters

Comments

Commu nication parameters CONTROL-M/ EM port

Minimum server processes (CS)

Maximum server pr ocesses (CS)

Comp uter/ accoun t specific

parameters

For examp le, pr oclib: Executable path

CONTROL-M/ Server SMTP

configuration settings

N/ A

User Exit scripts N/ A

Diagnostic messages recorded from

stored p rocedures (SPs) in th e

CONTROL-M/ Server database

wh ich w ere set byctmspdiag utility

N/ A

Parameters for Commu nicating w ith

the Agent Platform (including new

values).

These new valu es are assigned du ring migration and

overwrite any existing param eter values.

Comm un ication Protocol Version: 07

Unavailability Shout Urgency: R

Persistent Connection: N

Maximum Concurrent Sessions: 256

Allow Agent Disconnection: Y Session Id le Time-ou t: 900 Maximum Disconnect Time: 300

Database configuration parameters N/ A

8/7/2019 70705

11/32

8/7/2019 70705

12/32

Migrating data


8/7/2019 70705

13/32


C h a p t e r 22Migrating from previous versions

This chapter gu ides you th rough the p rocess of migrating CON TROL-M/ Server data

from an earlier_version.

The migration p rocedu re is performed using the sequen tial steps presented in th e

following table:

Table 3 Migration Steps

Step Explanation

1. Installing the Migration Toolkitt The Migration Toolkit must be installed in

th e earlier_version for data validation an d

export.

2. Ensuring d ata correctness Use the Migration Toolkit to examine th e

earlier_version data for comp atibility with the

new version format. This p rocess w ill

norm ally need to be run m ultiple times.

After each ru n, you mu st correct all errors

and re-run un til no more errors are detected.

3. Exporting the earlier_version d ata Use the Migration Toolkit to export the

error-free data to a location available to the

new version.

4. Importing the exported d ata to the new

version

Import the error-free data to the n ew version

8/7/2019 70705

14/32

Pre-migration considerations


Pre-migration considerations

Before beginning the m igration procedu re consider the following:

Back up the current environmen t.

If you have installed n ew versions of both CON TROL-M/ EM and

CONTROL-M/ Server, you mu st migrate CONTROL-M/ EM first before migrating

CONTROL-M/ Server.

If you a lready comp leted the process of ensu ring data correctness or have alread y

exported the data with an older version of the Migration Toolkit, you m ust

perform the p rocedu re again u sing the n ew Migration Toolkit.

Acquire the necessary database password or adm inistrator passwords.

Until CONTROL-M/ Server m igration is comp leted, do n ot perform a definition

down load from the earlier_version CON TROL-M/ Server to th e new

CONTROL-M/ EM. This operation cou ld genera te invalid da ta in the new

CONTROL-M/ Server environm ent.

If your environmen t uses a d atabase server that is not case-sensitive, see the

app end ix called Working w ith Databases that are not Case-Sensitive in the

CONTROL-M Installation Guide.

If you are ru nn ing a CON TROL-M/ Server for UNIX or Wind ows version earlier

than version 6.1.03, you m ust first upgrade and m igrate your curren t version to6.1.03 or 6.2.01 before insta lling and migrating to the 6.4.01 version.

Migration from CON TROL-M/ Server vers ion 6.3.01 to 6.4.01 requ ires more d isk

space for the entire installation. The requ ired d isk space has increased by:

50% for Oracle

70% for Sybase

20% for MSSQL

Parallel and non-parallel installations

The parallel installation meth od is consider the best method as the earlier_version can

remain in u se until the new version is in place and h as been tested. Using this

method , the new version can be set up, tested, and fine-tun ed w ithout un installing

th e earlier_version and disturbing production.

If you d o not have th e resources to set up a new version environment in parallel to

the current environment, before uninstalling the earlier_version software you n eed to:

8/7/2019 70705

15/32

Installing the Migration Toolkit


1 Validate the existing data before uninstalling the earlier_version.

2 Expor t the validated da ta to a location w here it will be available for imp ort to the

new version.

3 Uninstall the earlier_version.

4 Install the new version of CON TROL-M/ Server.

5 Import the earlier_version data into the new version.

The parallel installation method uses th e same set of instruction except for step 3.

With this method, the earlier_version can be un installed a fter the fu ll migration

procedure is comp leted.

Installing the Migration Toolkit

The Migration Toolkit is used to export CON TROL-M/ Server information from an

earlier version. The latest version of the Migration Toolkit mu st be installed in th e

earlier_version environmen t. If an older version of the Toolkit is detected d ur ing

installation, it is backed u p to the migration-export.PREVIOUS directory in theearlier_version CON TROL-M/ Server environment.

Installing the Migration Toolkit on UNIX

To install the Migration Toolkit on UNIX

1 Log on to CONTROL-M/ Server accoun t and nav igate to the home d irectory.

2 Download the install_migration script for the UN IX Migration Toolkit to thehom e d irectory. The migration toolkit is available on the BMC Software Cu stomer

Sup por t Web site (http:/ / ww w.bmc.com/ sup port_home) in solu tion

SLN000015061431.

3 Run the install_migration command.

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

${HOME}/log/cts_migration_install_log.txt
http://www.bmc.com/support_homehttp://www.bmc.com/support_home

8/7/2019 70705

16/32

Installing the Migration Toolkit on Windows


Installing the Migration Toolkit on Windows

Before you begin

If you a re work ing with a non -English version of Wind ows, before installing theWind ows Migration Toolkit, set the system locale and langu age settings to English as

follows:

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

2 Select Engli sh (US) in Control Panel => Regional and Language Options => to setthe locale to English.

After installation you can reconfigure you r compu ter to opera te in a language other

than English. For more information, see the CONTROL-M Language CustomizationGuide.

To install the Migration Toolkit on Windows

1 Log on to CON TROL-M/ Server user and navigate to th e CON TROL-M/ Server

folder.

2 Download the install_migration.exe self-extracting Zip file containing theWindow s Migration Toolkit to the %TEMP% directory. The migration toolkit is

available on the BMC Software Cu stomer Sup por t Web site(http:/ / ww w.bmc.com/ sup port_home) in solu tion SLN 000015061431.

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

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

%TEMP%\ ctms_migration_install_log .txt

Ensuring data correctnessAs a result of enhancements to the CON TROL-M solution in the p ast several

versions, some of the curren t sched uling d efinitions might function d ifferently when

migrated to th e new release.

When th e Migration Toolkit validation and expor t processes are performed, the

earlier_version da ta is checked to ensu re that it conforms to the new version rules.

All job p rocessing definitions are checked at the time of valida tion.
http://www.bmc.com/support_homehttp://www.bmc.com/support_home

8/7/2019 70705

17/32

Ensuring data correctness


When a problem w ith the d ata is detected, a m essage is w ritten to the Readiness

repor t as described below in step 2.

To check validity and to ensure th at your earlier_version definitions will function

correctly in the new release, perform the following d ata validation p rocedu re.

To check CONTROL-M/Server data validity

1 Ensure that one of the following is your w orking d irectory and then ru n the

migration command to activate the Migration Toolkit.

$HOME/migrate_ctm for Unix

\ migrate_ctm for Window s

2 Choose the Validation option in the Migration m enu. This step generates theReadiness report.

3 Analyze the resu lts and correct all errors. Data that gen erated inform ational

messages and w arnings will be autom atically adjusted w hen imp orted to the new

version as specified in the Readiness rep ort.

You can view th e Readiness report online by selecting View Readiness Report fromthe Migration m enu. For a printed copy of the report, print th e ValidityReport.outfile from the migrate_ctm directory. Alternatively, you can use a text editor to viewthe report.

All errors mu st be corrected before imp orting the d ata. Due to new featur es

implemented for the version you are about to install, some error s can be corrected

only when the current version is about to be shut d own for the final time.

Information on th ese and other error s is listed in the Readiness report. Just before

shutd own , these errors mu st be corrected an d a final version of the d ata exported

using th e Migration Toolkit. For information abou t analyzing the Readiness report,

see Messages on page 24.

NOTEIf you are w orking w ith a n on-English version of Window s, before activating the Migration

Toolkit and run ning any comman d, set the system locale and langu age settings to English as

described in Installing the Migration Toolkit on Wind ows on page 16

TIPIt is recomm end ed that you stop ru nning CON TROL-M/ Server, in ord er to assure that you

are generating the most recent report.

8/7/2019 70705

18/32

Exporting the earlier_version data


Repeat the d ata validity check until no error messages are generated (except for

errors that need to be corrected after the n ew version is runn ing). When there are n o

error messages, the data is ready to be exported (see Expor ting th e earlier_version

data).

Iterations of the report are stored in the same directory. A sequence num ber isapp ended to the report name so that you can compare the rep orts. Readiness report

message typ es are described in Append ix A.

Exporting the earlier_version data

Before beginn ing to expor t the earlier_version data perform the following:

Shut d own the earlier_version of CONTROL-M/ Server and CONTROL-M/ ServerConfiguration Agent (starting from version 6.3.01)

Make sure the d atabase server is up

To export the CONTROL-M/Server earlier version data

1 Ensure th at one of the following is your w orking d irectory and then ru n the

migration comma nd to activate the Migration Toolkit.

$HOME/migrate_ctm for Unix

\ migrate_ctm for Window s

2 Run Export from the menu .

The exported files are saved in the follow ing location:

$HOME/ExportForMig.tar for Unix.

\ migrate_ctm\ backup_ctm directory for Window s.

The Export step a lso generates another copy of the Readiness rep ort,

ValidityReport.out, in th e migrate_ctm directory.

3 Copy the exported files to a location tha t can be accessed by th e new release

environment. Do not change th e exported file names as the import p rocess requires

the files to have the same nam es given to them by the export p rocess.

NOTEIf you are work ing w ith a n on-English version of Window s, before activating the Migration

Toolkit and run ning any comman d, set the system locale and langu age settings to English as


8/7/2019 70705

19/32

Importing the exported data to the new version


4 When migration from:

Windows to UNIX:

A. Backup the content of the \ migrate_ctm\ backup_ctm

directory of the exported Window s environment.

B. Copy th e content of\ migrate_ctm\ backup_ctm directory of

the exported Wind ows environment to $HOME/migrate_ctm/backup_ctm

directory in the UN IX accoun t.

UNIX to Windows : Copy th e content of$HOME/migrate_ctm/backup_ctmdirectory from the exported UNIX accoun t to the

\ migrate_ctm\ backup_ctm directory in the Windows

environment.

At this point, the entire earlier_version environment can be backed up and rem oved.

For d etails on how to un install the earlier_version, see the CONTROL-M Installation

Guide.

Importing the exported data to the newversion

If you have not yet installed th e new version of CON TROL-M/ Server 6.4.01, you

shou ld do so now. You should also check for and install the latest

CON TROL-M/ Server 6.4.01 fix pa cks. You can access th e latest Fix Packs at th e

following site:

ftp:/ / ftp.bm c.com/ pu b/ control-m/ opensystem/ CONTROL-M_Server_for_UNIX_and_Microsoft_Windows

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

Installation Guide.

WARNING

If the exported files are copied using FTP, they mu st be transferred in binary mod e.

NOTEYou do not h ave to install the Migration Toolkit, because it is integrated in to the

CONTROL-M/ Server 6.4.01 installation.
ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Server_for_UNIX_and_Microsoft_Windowsftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Server_for_UNIX_and_Microsoft_Windowsftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Server_for_UNIX_and_Microsoft_Windows

8/7/2019 70705

20/32



If you p lan to un install the earlier_version of CONTROL-M/ Server, you mu st save the

exported files to a location ou tside the accoun t as it will be erased w hen th e earlier_version is

uninstalled.

Before you begin

Before beginning to import th e earlier_version data perform the following:

Shut d own the earlier_version of CONTROL-M/ Server and CONTROL-M/ Server

Configuration Agent (starting from version 6.3.01)

Make sure the d atabase server is up

To import the CONTROL-M/Server data

1 Ensure that the exported earlier_version files are accessible to the new

CONTROL-M/ Server version an d imp ort the export d ata as follows:

A Make \ migrate_ctm your w orking directory.

B Run the migration comma nd to activate the Migration Toolkit.

C Activate the imp ort process from th e Migration Toolkit men u.

The imp ort process converts the d ata and imports it into the new environment.

Data for w hich informational messages and w arnings were generated are

automa tically ad justed to comply w ith the new version format.

NOTE

If you are work ing w ith a n on-English version of Window s, before activating the MigrationToolkit and run ning any comman d, set the system locale and langu age settings to English as


NOTEYou can v iew the status of the CON TROL-M/ Server, CON TROL-M/ Server Con figurat ion

Agent, and database server by ru nning ctm_menu => CON TROL-M Manager => Check All

in the command line window .

8/7/2019 70705

21/32



2 To continue w orking w ith earlier_versionCON TROL-M/ Agen ts, proceed asfollows:

A If CON TROL-M/ Server h ad no specific CONTROL-M/ Agen t comm unicationparameters defined, configure CON TROL-M/ Server w ith the commu nication

protocol that m atches the curren t CON TROL-M/ Agen t version (this step isnecessary because the default comm un ication p rotocol version for

CON TROL-M/ Agent in CON TROL-M/ Server 6.4.01 is 08). For details, see the

Maintenance chap ter in the CONTROL-M Administrator Guide.

B If you h ave jobs for which no node group is defined (these jobs ran on a localagent in an earlier_versionCON TROL-M/ Server), and your

CON TROL-M/ Server 6.4.01 insta llation is located on a d ifferent comp uter from

the Agent, you w ill need to either point these jobs to the agent on the

earlier_version computer , or configure the local agent on the

CONTROL-M/ Server 6.4.01 computer.

C If you installed CO NTROL-M/ Server on an other m achine, reconfigure you rCONTROL-M/ Agents so that they p oint to the new h ost name an d port. For

details, see the CONTROL-M Administrator Guide.

3 Migrate CON TROL-M/ Server d efinitions in the CON TROL-M/ EM database from

th e earlier_version to version 6.4.01 by ru nning the migrate_dc utility in theCON TROL-M/ EM environm ent. For more information on the migrate_dc utility,see the CONTROL-M /Enterprise Manager Migration Guide.

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

configuration p aram eters that ar e compu ter or accoun t specific. This information is

not migrated from the earlier_version in a parallel installation. Con figu ration

param eters that refer to specific path nam es may also need to be ad justed.

5 If you are m igrating from CONTROL-M/ Server version 6.1.03, you w ill need to

configure the CTM_ADJUST_CON D_SCOPE parameter man ua lly in th econfig.dat file as follows:

A If you w ant th is param eter to relate to jobs at the grou p level, set the value ofCTM_ADJUST_COND_SCOPE to GROUP.

B If you want this param eter to relate to jobs at the at th e active jobs file level, setthe valu e of CTM_ADJUST_COND_SCOPE to AJF.

NOTEIf you m igrated CONTROL-M/ Server to a d ifferent compu ter, reconfigure the h ost

nam e and port system p arameters in the CON TROL-M/ EM d atabase. For m ore

information, see the CONTROL-M Administrator Guide.

8/7/2019 70705

22/32



For more information on th e CTM_ADJUST_COND_SCOPE parameter, see the

CONTROL-M Administrator Guide.

6 If the ctmldnrs.dat file is migrated , it is placed in the CONTROL-M/ Server h omedirectory (). From there you can copy th e file to the default location

(/ctm_server/tmp) or anoth er location as required .

7 BMC Software recomm ends that imm ediately after you have comp leted dataimport and migration of CONTROL-M/ Server d efinitions, you synchron ize your

da ta by dow nload ing it to CONTROL-M/ EM.

Download ing the da ta pop ulates CON TROL-M/ EM version 6.4.01 with the

corrections that you p erformed m anu ally in CONTROL-M/ Server as outlined in

the Readiness r eport. It will also enable you to control jobs in the

CONTROL-M/ EM Active Jobs file (for example, a request for job order or rerun).

How ever, if the sched uling tables in CON TROL-M/ Server are not fu lly

synchron ized w ith those in CON TROL-M/ EM (that is, there are jobs that r eside

only on one side, or correspon ding jobs on both sides that are not identical), the

dow nload op eration will overwrite the definitions in CON TROL-M/ EM with

those from CONTROL-M/ Server.

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

up graded to 6.4.01 from th is point onward . Although not required, this upgrad e

will allow u tilization of the newest Agent fun ctionality.

9 Manu ally remove the d irectories of the Migration ToolKit from the earlier_version

environment.

10 You can n ow un install the earlier_version (if you h ave not alread y don e so).

NOTEFor more information abou t specific param eters that are migrated , see Migrating

data on page 9.

NOTEOn Un ix, the ctmldnrs.dat is deleted from the d efault location

(/ctm_server/tmp ) when CONTROL-M/ Server is started .

8/7/2019 70705

23/32


A p p e n d i x AAReadiness report messages

Messages are prefixed according to message type. Each message typ e has a un ique

prefix describing the natu re of the message as explained in the following table.

Prefix Description

ERR Error

Error messages ind icate that job processing definitions contain values th at are

inconsistent with new version formats. These values might affect job

scheduling.

You mu st man ually correct the error s identified in job processing d efinitions

before continuing the m igration.

Errors in a job in the Active Jobs file must be corrected, or the job mu st

removed from th e file. If you can, man ually correct the error s. If not, the jobcan be removed by the New Day p rocedure at the beginning of the next day.

Otherw ise, you can m anu ally request the job to be deleted d uring th e next

daily maintenan ce.).

INFO Information

These messages ind icate that the d ata contains values that are n o longer

relevant or supp orted in the new version.The data will automatically be

corrected du ring the import p rocess. No m anu al changes are required or

accepted. The au tomatic changes will not affect you r n ew v ersion scheduling

environment.

WRN Warning

These messages indicate that job p rocessing definitions in your current

environm ent contain statements that have no p rod uction meaning. For

example, an ON statement w ith no DO action, or a SHOUT statement w ith no

destination.

You can correct these w arning situations (for examp le, you can add a DO

action to an ON statem ent, or a destination to a SHOUT statement). How ever,

if you choose not to correct these warning s, the problematic statements will be

removed du ring the imp ort process to the new version. These chan ges will

not affect your schedu ling env ironment.

8/7/2019 70705

24/32

Readiness report format


Readiness report format

Each p roblem in the Readiness report is presented in a format similar to the

following:

Example

This examp le displays a problem w ith the quantitative resource nam e in a job

processing d efinition:

Analyzing report messages

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

following table.

MessagesERR01 Periodic calendar has Y or N values

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

(non-periodic) calend ars can have Y and / or N values.

System A ction: The export p rocedu re cannot process the data.

ms g _ c o d e me s s a g e _ t e x t_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Er r o r Co d e : e n t i t y _ n a me [ e n t i t y _ n a me] [ e n t i t y _ n a me]x x x n n a a a a a a a a ax x x n n b b b b b b b b b e t c .x x x n n c c c c c c c c c

E r r o r ER R1 0 0 : Qu a n t i t a t i v e r e s o u r c e n a me c a n n o t b e s e t t o a b l a n k v a l u e_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Co d e Sc h e d u l i n g T a b l e Na me J o b NO J o b Na me Me m Na me- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -E RR 1 0 0 t 4 4 3 1 4

If the report contains: Appropriate user action

ERR messages Correction of errors is mand atory.

WRN messages Correction of the m essages is op tional.

INF messages None.

8/7/2019 70705

25/32

Messages


User Response: Verify that the calendar is a periodic calendar and d elete all Y and N

values. If you d etermine that the calendar is a regular calendar, ensu re that th e

calend ar has only N an d Y values. You can u se CONTROL-M/ EM Desktop or

CON TROL-M/ EM utilities to define the calendars correctly.

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

Explanation: **** an d $$$$ cannot be specified as the d ate for a cond ition in theCond itions file.

System A ction: The export p rocedu re cannot process the data. The system m ay issue

other error m essages to this report that ind icate wh ich job p rocessing d efinitions

create or u se these imp roperly named conditions.

User Response: Delete the cond ition from th e Cond itions file, and r eenter the

cond ition with a valid d ate. (You can u se the Conditions w indow to delete and ad d

the cond ition.) Also, correct the sou rce of the cond ition (for example, an OUT

statemen t or a script that invokes a CONTROL-M u tility).

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

Explanation: Cond ition names cannot contain the (, ), or | characters or

embedded spaces.

System A ction: The export p rocedu re cannot pr ocess the data. The system might issue

other error m essages to this report that ind icate wh ich job p rocessing d efinitions

create or u se these imp roperly named conditions.

User Response: Use the Cond itions w indow to delete the cond ition from theCond itions file, and r eenter the cond ition w ith a valid nam e. Also, correct the source

of the cond ition (for examp le, an OUT statement or a u tility) and any jobs that use the

cond ition as an IN cond ition.

ERR100 Quantitative resource name cannot be set to a blank value

Explanation: .Quan titative resource nam es cann ot have a blank value. The

problematic quantitative resource name ap pear s in the ind icated job processing

definition.


User Response: Specify a valid v alue for the resou rce name, or d elete the resource

from the job p rocessing d efinition.

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

Explanation: .Quan titative resource nam es cann ot have a blank value. The

problematic quantitative resource name ap pear s in the ind icated job processing

definition in the Active Jobs file.


8/7/2019 70705

26/32

Messages


User Response: In the Active Jobs file, manu ally specify a valid value for the r esource

nam e, or delete the resource from the job.

ERR16 Quantitative resource has a quantity value of zero

Explanation: Zero is an invalid qu antity for a Quan titative resource. The minimu mquantity is 1. The p roblematic resource quan tity app ears in the ind icated job

processing d efinition.


User Response: Specify a qu antity of 1 or more for the resource, or d elete the resou rce

from the job p rocessing d efinition.

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

Explanation: Zero is an invalid qu antity for a Quan titative resource. The minimu m

quantity is 1. The problematic resource quan tity app ears in the indicated job in theActive Jobs file.


User Response: In the Active Jobs file, manu ally specify a quantity of 1 or m ore for the

resource, or d elete the resource or the job.

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

Explanation: The IN cond itions of a job in the Active Jobs file are not ordered, since

more than one IN condition h as a row order of 1.

System A ction: CON TROL-M/ Server cannot au tomatically d ecide the correct ord er ofthe IN conditions, and therefore the export procedure cannot p rocess the data.

User Response: You can do one of the following:

Redefine the conditions of the job using Zoom & Save in CON TROL-M/ Enterprise

Manager.

Remove the job. Either remove it manu ally, or wait u ntil the New Day p rocedu re

removes it au tomatically.

If you are m igrating from v ersion 6.1.03, install the latest fix pack in or der to p revent

new ly created jobs from hav ing this problem.

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

Explanation: The OUT cond itions of a job in the Active Jobs file are n ot ord ered, since

more than one OUT cond ition has a row order of 1.

System A ction: CON TROL-M/ Server cannot au tomatically d ecide the correct ord er of

the OUT conditions, and therefore the export p rocedu re cannot p rocess the d ata.

8/7/2019 70705

27/32

Messages


User Response: You can do one of the following:

Redefine the conditions of the job using Zoom & Save in CONTROL-M/ Enterp rise

Manager.

Remove the job. Either remove it manu ally, or wait u ntil the N ew Day procedure

removes it au toma tically.

If you are m igrating from v ersion 6.1.03, install the latest fix pack in order to p revent

new ly created jobs from hav ing this problem.

8/7/2019 70705

28/32

Messages


8/7/2019 70705

29/32

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

Index

Symbols.tar file, saving 20

BBMC Software, contacting 2

Cconfiguration p arameters 21

CON TROL-M/ Agent 22

reconfiguration 21

customer support 3

Ddata

synchronization 22

Eembedded space

error message 25

error messages 23

executable files. See files

exporting

considerations 14

saving .tar file before un installing 20

Ffiles

install_migration script 15

install_migration.exe 16

ValidityReport.out 17

Hhost name 21

Iimporting

exported data 19

install_migration script 15

install_migration.exe file 16

invalid characterserror message 25

invalid d ate

error message 25

Llanguage settings

Windows 16

locale settings 16

Mmessagesanalyzing 24

prefixes for 23

Readiness report 24

migrating

overview 7

Nnon-English versions of Windows 16

Pperiodic calenda r

error message 24

port 21

prefixes, message 23

product support 3

Qquan tity zero

8/7/2019 70705

30/32


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

RReadiness report 23reconfiguring

CON TROL-M/ Agents 21

host name and port 21

regional settings 16

Ssup port, customer 3

synchronizing d ata 22

Ttar file. See files 20

technical supp ort 3

Vvalidating earlier_version data 16

Valid ityRepor t.out file 17

8/7/2019 70705

31/32

Notes

8/7/2019 70705

32/32

* 7 0 7 0 5 *

* 7 0 7 0 5 *

* 7 0 7 0 5 *

* 7 0 7 0 5 *

*70705*

70705

Documents