Control-M Installation Guide 6.1.03 PDF

CONTROL-M
Installation Guide
Version 6.1.03
March 31, 2004
Copyright 2003 BMC Software, Inc., as an unpublished work. All rights reserved.
BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered
trademarks or trademarks of BMC Software, Inc. Oracle is a registered trademark, and the Oracle product names
are registered trademarks or trademarks of Oracle Corp. All other registered trademarks or trademarks belong to
their respective companies.
THE USE AND CONTENTS OF THIS DOCUMENTATION ARE GOVERNED BY THE SOFTWARE
LICENSE AGREEMENT ENCLOSED AT THE BACK OF THIS DOCUMENTATION.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER
THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer
software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14,
DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended
from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX
77042-2827, USA. Any contract notices should be sent to this address.
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain
information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Outside United States and Canada
Address
Telephone
(01) 713 918 8800
Fax
(01) 713 918 8000
BMC Software, Inc.

2101 CityWest Blvd.
Houston TX 77042-2827
Telephone
713 918 8800 or

800 841 2031
Fax
713 918 8000
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or by contacting
Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC
Software.
Support Web Site

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

In the United States and Canada, if you need technical support and do not have access to the Web, call
800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To
find telephone and e-mail contact information for the BMC Software support center that services your location,
refer to the Contact Customer Support section of the Support page on the BMC Software Web site at
www.bmc.com/support.html.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin
working on your problem immediately:
product information
product name
product version (release number)
license number and password (trial or permanent)
operating system and environment information
machine type
operating system type, version, and service pack or other maintenance level such as PUT or PTF
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, and service pack or
maintenance level
BMC Software, Inc., Confidential and Proprietary Information
iii
sequence of events leading to the problem
commands and options that you used
messages received (and the time and date that you received them)
product error messages

messages from the operating system, such as file system full
messages from related software
iv
CONTROL-M Installation Guide
Contents
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Chapter 1
Getting Started
Choose Which CONTROL-M Products to Install . . . . . . . . . . . . . . . 1-2

Choose a Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Identify and Arrange for Installation Resources . . . . . . . . . . . . . . . . 1-7
Map your CONTROL-M solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Choosing the Installation CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Set up and Install CONTROL-M Components . . . . . . . . . . . . . . . . . 1-10
Chapter 2
Pre-Installation Steps for Unix with a Sybase Database
Prepare for Database Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Choose a Sybase Database Configuration . . . . . . . . . . . . . . . . . 2-2
Prepare to Install with an Existing Sybase Database Server . . . . 2-4
Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Check Locale Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Check Operating System Levels and Patches . . . . . . . . . . . . . . . 2-6
Check Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Check and Modify System Parameters . . . . . . . . . . . . . . . . . . . . . . . 2-12
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Compaq Tru64 (OSF1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Create Database Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Create the CONTROL-M/EM Administrator Account . . . . . . . . . . . 2-22
Create the CONTROL-M/Server Administrator Account . . . . . . . . . 2-24
Review Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Contents
Chapter 3
Pre-Installation Steps for Unix with an Oracle Database
Choose a Files or Raw Partitions for the Oracle Database . . . . . . . .3-2

Prepare to Install with an Existing Oracle Database Server . . . .3-3
Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Check Locale Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Check Operating System Levels and Patches . . . . . . . . . . . . . . .3-5
Check Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Check and Modify System Parameters . . . . . . . . . . . . . . . . . . . . . . .3-11
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14
Compaq Tru64 (OSF1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
Create the CONTROL-M/EM Administrator Account . . . . . . . . . . .3-17
Create the CONTROL-M/Server Administrator Account . . . . . . . . .3-19
Review Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
Chapter 4
Pre-Installation Steps on Microsoft Windows
Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6
Verify Installation Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
Review Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
Where to go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8
Chapter 5
Installing an Oracle Database on Unix
Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

Prepare Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
Run the Oracle Pre-Installation Script . . . . . . . . . . . . . . . . . . . . .5-5
Run the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
Run the Oracle Post-Installation Script . . . . . . . . . . . . . . . . . . . .5-10
Chapter 6
Installing an Oracle Database on Microsoft Windows
Oracle Database Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

Chapter 7
Installing CONTROL-M/EM on Unix
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

Mount the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3
Run the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5
Chapter 8
Installing CONTROL-M/EM for Microsoft Windows
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

Installing CONTROL-M/EM Components . . . . . . . . . . . . . . . . .8-4
vi
Silent Installation of a CONTROL-M/EM Basic Client . . . . . . . 8-10

Chapter 9
Installing CONTROL-M/Server for Unix
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Upload the Installation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Installing CONTROL-M/Server on Unix . . . . . . . . . . . . . . . . . . 9-8
Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Record Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Modify the Automatic Startup Procedure . . . . . . . . . . . . . . . . . . 9-12
Chapter 10
Installing CONTROL-M/Server for Microsoft Windows
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Installing CONTROL-M/Server on Microsoft Windows . . . . . 10-3
Chapter 11
Silent Installation of CONTROL-M/Server for Microsoft Windows

11-2
Chapter 12
Installing or Upgrading CONTROL-M/Agent for Unix
Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Configure NIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Upgrade with CONTROL-M Option for Oracle Applications
Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Upgrade with CONTROL-M Option for PeopleSoft Installed . 12-7
Mount the CD-ROM Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Installing or Upgrading CONTROL-M/Agent on Unix . . . . . . 12-11
Set the Protocol Version for the Upgraded CONTROL-M/Agent
12-13
Installing or Upgrading CONTROL-M/Agent for Unix in Silent
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Changes to System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Chapter 13
Installing or Upgrading CONTROL-M/Agent for Microsoft Windows
Installing CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Importing WIN Panel Functionality . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
13-10
Contents
vii
Chapter 14
Silent Installation of CONTROL-M/Agent for Microsoft Windows

14-2
Set the Protocol Version for the Upgraded CONTROL-M/Agent 14-5
Chapter 15
Post-Installation Configuration
On Unix Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-2

Check the Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-2
Start CONTROL-M/EM Components . . . . . . . . . . . . . . . . . . . .15-2
Starting CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . .15-3
Check the CONTROL-M/EM to CONTROL-M Port Number .15-4
On Microsoft Windows Computers . . . . . . . . . . . . . . . . . . . . . . . .15-6
Register CONTROL-M/EM Server Components . . . . . . . . . . .15-6
Create CONTROL-M Definitions in CONTROL-M/EM . . . . .15-8
Register Gateways for Communication With CONTROL-M/Server
15-10
Create CONTROL-M Definitions in CONTROL-M/Desktop .15-11
Show Extra Keyboard Help in Programs . . . . . . . . . . . . . . . . . .15-13
Check Communication with CONTROL-M/Agent . . . . . . . . . . . . .15-13
Chapter 16
Troubleshooting
CONTROL-M/EM Installation on Unix . . . . . . . . . . . . . . . . . . . . .16-2

CONTROL-M/EM Installation on Microsoft Windows . . . . . . . . .16-6
Check Startup Options for CONTROL-M/EM Services . . . . . .16-10
CONTROL-M/Server for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-12
Oracle Database Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-15
Sybase Database Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-15
Chapter 17
Uninstalling CONTROL-M Components
Uninstalling CONTROL-M/EM On Unix Computers . . . . . . .17-2

Uninstalling CONTROL-M/EM On Microsoft Windows . . . . .17-6
Uninstalling CONTROL-M/Server on Unix Computers . . . . . .17-11
Cleanup for Sybase Database Servers . . . . . . . . . . . . . . . . . . . .17-12
Uninstalling CONTROL-M/Server on Microsoft Windows . . .17-13
Uninstalling CONTROL-M/Agent for Unix . . . . . . . . . . . . . . .17-14
Uninstalling CONTROL-M/Agent for Microsoft Windows . . .17-17
Appendix A
Mounting CDs on Unix Computers
Mounting Installation CDs on an AIX Computer . . . . . . . . . . . . . . A-2

Mounting Installation CDs on an HP-UX Computer . . . . . . . . . . . . A-3
Mounting Installation CDs on a Solaris Computer . . . . . . . . . . . . . A-6
viii
Mounting Installation CDs on a COMPAQ Tru64 Computer . . . . . A-6

Mounting Installation CDs on a Linux Computer . . . . . . . . . . . . . . A-8
Appendix B
CONTROL-M/EM Components
Appendix C
Unix Operating System Requirements
Appendix D
CONTROL-M/EM Database Size
Appendix E
CONTROL-M/Server Database Size
Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Calculating the Size of the Active Jobs File . . . . . . . . . . . . . . . . . . . E-3
Database Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . E-8
Appendix F
New Database Schema on an Existing Oracle (Unix)
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2

Run the Oracle Pre-Installation Script . . . . . . . . . . . . . . . . . . . . F-3
Installing the Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . F-6
Build the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10
Run the Oracle Post-Installation Script . . . . . . . . . . . . . . . . . . . . . . . F-11
Appendix G
New Database Schema on an Existing Oracle (Microsoft Windows)
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2

Appendix H
Tuning Steps for Oracle on AIX
Appendix I
Working with CONTROL-M Databases that are not Case-Sensitive
CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-2
Implications of Changing from Case-Sensitive to Non-Case-Sensitive
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-2
Implications of Changing from Non-Case-Sensitive to Case-Sensitive
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-3
Appendix J
Language Configuration
Japanese . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Procedure Task Flow . . . . . . . . . . . . . . . . . . . . . .
Configuration Tasks for Japanese Support on Unix . . . . . . . . . .
Western European Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-2
J-2
J-3
J-6
J-6
Contents
ix
Compatibility with Prior Versions . . . . . . . . . . . . . . . . . . . . . . . . J-7

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-7
Upgrade and Migration Considerations . . . . . . . . . . . . . . . . . . . . J-8
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-9
Configuration Procedure Task Flow . . . . . . . . . . . . . . . . . . . . . . J-9
Additional Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-10
General Configuration on Microsoft Windows . . . . . . . . . . . . . . J-12
Setting the Default Microsoft Windows Command Prompt Code
Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-16
General Configuration on Unix . . . . . . . . . . . . . . . . . . . . . . . . . . J-18
Additional CONTROL-M/EM Configuration . . . . . . . . . . . . . . . J-22
Additional CONTROL-M/Agent Configuration on Unix . . . . . . J-25
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-26
Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-27
Sybase Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-31
MSSQL Configuration for the CONTROL-M/EM Database . . . J-36
MSSQL Configuration for the CONTROL-M/Server Database . J-39
MSSQL Configuration for Clients . . . . . . . . . . . . . . . . . . . . . . . J-42
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-44
Parameters that Support Western European Language Special
Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-47
Index
Figures
Figures
Figure 1-1
Figure 16-1
CONTROL-M Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

SQL Query Analyzer Window. . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Figures
xi
xii
Tables
Tables
Table 1-1
Table 1-2
Table 1-3
Table 1-4
Table 1-5
Table 1-6
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 2-9
Table 2-10
Table 2-11
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 3-7
Table 3-8
Table 3-9
Table 4-1
Table 5-1
Parts of the CONTROL-M Installation Guide . . . . . . . . . . . . . .

CONTROL-M Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Server Configurations CONTROL-M . . . . . . . . . . .
Installation Resource Requirements . . . . . . . . . . . . . . . . . . . . .
Installation CDs by Computer Type. . . . . . . . . . . . . . . . . . . . . .
Major Steps for CONTROL-M Installation. . . . . . . . . . . . . . . .
Minimum Partition Sizes for a Sybase Installation . . . . . . . . . .
Sybase Database Server Parameters Minimum Values . . . . . . .
Unix Computer Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Check Available Memory . . . . . . . . . . . . . . . . . . . . . . .
Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Kernel Parameters HP-UX with Oracle . . . . . . . . . . . . . . . . .
Kernel Parameters Solaris with Sybase . . . . . . . . . . . . . . . . .
Kernel Parameters Compaq Tru64 with Sybase . . . . . . . . . . .
Limits for the CONTROL-M/EM User Account. . . . . . . . . . . .
Unix Computer Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to for Check Available Memory . . . . . . . . . . . . . . . . . . . .
Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Kernel Parameters HP-UX with Oracle . . . . . . . . . . . . . . . . .
Kernel Parameters Solaris with Oracle . . . . . . . . . . . . . . . . . .
Kernel Parameters Compaq Tru64 with Oracle . . . . . . . . . . .
Limits for the CONTROL-M/EM User Account. . . . . . . . . . . .
System Requirements for CONTROL-M Products . . . . . . . . . .
Oracle Database Installation Types. . . . . . . . . . . . . . . . . . . . .
1-1
1-3
1-5
1-7
1-9
1-10
2-3
2-5
2-9
2-9
2-10
2-10
2-11
2-13
2-17
2-18
2-23
3-8
3-9
3-9
3-10
3-10
3-12
3-15
3-16
3-18
4-2
5-1
Tables
xiii
Table 5-2
Table 6-1
Table 6-2
Table 7-1
Table 8-1
Table 8-2
Table 9-1
Table 9-2
Table 10-1
Table 11-1
Table 11-2
Table 12-1
Table 12-2
Table 12-3
Table 12-4
Table 12-5
Table 13-1
Table 14-1
Table 15-1
Table 16-1
Table 16-2
Table 16-3
Table 17-1
Table B-1
Table B-2
Table B-3
Table B-4
Table C-1
Table D-1
Table E-1
Table 5-2
Table E-3
Table F-1
Table G-1
Table J-1
Table J-2
Table J-3
Table J-4
Oracle Database Unix Installation Parameters . . . . . . . . . . . 5-11

Oracle Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Oracle Database Microsoft Windows Installation Parameters 6-5
CONTROL-M/EM Unix Installation Parameters . . . . . . . . . 7-8
CONTROL-M/EM Parameters Microsoft Windows . . . . . . . 8-5
Installation Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
CD_INST Messages for Upgrade. . . . . . . . . . . . . . . . . . . . . . . . 9-6
CONTROL-M/Server Unix Installation Parameters . . . . . . . 9-14
CONTROL-M/Server Parameters Microsoft Windows . . . . 10-5
Silent Installation Batch File Default Parameters . . . . . . . . . 11-4
Silent Installation Batch File Cluster Parameters . . . . . . . . . 11-7
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
CONTROL-M/Agent for Unix Silent Installation Parameters . .
12-16
Configuration CONTROL-M/Agent for Unix. . . . . . . . . . . . 12-17
Service Definition CONTROL-M/Agent for Unix . . . . . . . . 12-18
Installation Parameters - CONTROL-M/Agent on Unix . . . . . 12-19
CONTROL-M/Agent Installation Parameters . . . . . . . . . . . 13-5
Silent Installation Batch File Default Parameters . . . . . . . . . 14-6
Fields in the CONTROL-M Dialog Box . . . . . . . . . . . . . . . . . 15-12
CONTROL-M/EM Installation Error Message Handling . . . 16-2
CONTROL-M/EM Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
CONTROL-M/Server for Unix Troubleshooting . . . . . . . . . . . 16-12
Uninstallation Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Client Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Administrator Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Third Party Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Unix Operating System Requirements for CONTROL-M. . . . . C-2
Job Definition Elements and Disk Space Requirements . . . . . . D-3
Job items and Disk Space Requirements . . . . . . . . . . . . . . . . . . E-2
Job Definition Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Active Jobs File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-6
Oracle Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9
Default Tablespace Size Settings . . . . . . . . . . . . . . . . . . . . . . . . G-8
Configuration Tasks for Japanese Language Support . . . . . . . . J-2
ISO English Character Set Locale Settings for Unix (for Use with
Japanese Operating Systems) . . . . . . . . . . . . . . . . . . . . . . . . . J-4
Unix Environment Variables for Japanese in the .cshrc File . . . J-5
Configuration Tasks for Western European Language Support . J-10
xiv
Table J-5
Table J-6
Table J-7
Table J-8
Table J-9
ISO Latin-1 Character Set Locale Settings for Unix . . . . . . . . . . J-19

Unix Environment Variables for Western European Languages in the
.cshrc File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-20
Setting System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-23
Possible Character Sets Outputs and Corresponding Actions for
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-27
Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-47
Tables
xv
xvi
About . . .
About This Book

This book describe how to install CONTROL-M/Enterprise Manager
(CONTROL-M/EM), CONTROL-M/Server and CONTROL-M/Agent
version 6.1.03.
If you are upgrading from an earlier version of one of these products, see
the CONTROL-M Upgrade Guide before performing any procedures in
this book.
If you wish to perform a default installation for a small data center or for
a test environment, see one of the CONTROL-M Quick Installation
Guides.
Note
CONTROL-M products may be installed in any order. However, it is

important that each installation procedure be performed completely
before you install another CONTROL-M product on the same computer.
About This Book
xvii
How This Book Is Organized

This book is organized as follows.
Chapter
Description
Chapter 1
Getting Started
Describes how to choose the CONTROL-M products and
configuration that is appropriate for your site.
Chapter 2

Describes prerequisites and preinstallation steps for
CONTROL-M/Products to be installed on Unix computers
with a Sybase database.
Chapter 3
Pre-Installation Steps for Unix with an Oracle

Database
CONTROL-M/Products to be installed on Unix computers
with an Oracle database.
Chapter 4

CONTROL-M/Products to be installed on Microsoft
Windows.
Chapter 5

Describes how to install an Oracle Database server on a
Unix computer, for use with CONTROL-M/Server or with
CONTROL-M/EM.
Chapter 6

Describes how to install an Oracle Database server on a
Microsoft Windows computer, for use with
CONTROL-M/EM.
Chapter 7

Describes how to install CONTROL-M/EM on Unix
computers.
Chapter 8

Describes how to install CONTROL-M/EM on computers
running Microsoft Windows.
Chapter 9

Describes how to install CONTROL-M/Server for Unix.
Chapter 10

Describes how to install CONTROL-M/Server for Microsoft
Windows.
xviii
Chapter
Description
Chapter 11
Silent Installation of CONTROL-M/Server for Microsoft

Windows
Describes how to install CONTROL-M/Server for Microsoft
Windows with minimal user intervention.
Chapter 12

Describes how to install CONTROL-M/Agent for Unix.
Chapter 13
Installing or Upgrading CONTROL-M/Agent for

Microsoft Windows
Describes how to install CONTROL-M/Agent for Microsoft
Windows.
Chapter 14
Silent Installation of CONTROL-M/Agent for Microsoft

Windows
Describes how to install CONTROL-M/Agent for Microsoft
Windows with minimal user intervention.
Chapter 15
Describes the how to perform configuration tasks after all
necessary CONTROLM products have been installed.
Chapter 16
Troubleshooting
Describes how to recover from and avoid problems that
may occur during installation of CONTROL-M products.
Chapter 17

Describes how to remove various CONTROL-M products
from your computer.
Appendix A

Describes how to mount the various installation CDs on
the various Unix computer types.
Appendix B
Describes each CONTROL-M/EM component in detail,
and includes installation notes for each component.
Appendix C

Provides details about supported Operating system levels
and required patches.
Appendix D

Provides information for calculating the database data file
size and the memory requirements of the
CONTROL-M/EM database.
About This Book
xix
Chapter
Description
Appendix E

Provides information for calculating the database data file
size and the memory requirements of the CONTROL-M
database that is used by CONTROL-M/Server.
Appendix F

Describes installation of an Oracle Database schema for
CONTROL-M on an existing Oracle Server version 9.2.0
with an existing Oracle Client.
Appendix G
New Database Schema on an Existing Oracle

(Microsoft Windows)
Describes installation of an Oracle Database schema for
CONTROL-M on an existing Oracle Server version 9.2.0
with an existing Oracle Client.
Appendix H

Describes recommended modifications for sites that are
using on Oracle database server on a computer running
AIX.
Appendix I
Working with CONTROL-M Databases that are not

Case-Sensitive
Describes special considerations for CONTROL-M/EM or
CONTROL-M/Server when working with a Sybase or
MSSQL database that is not case sensitive.
Appendix J
Describes special considerations for how to configure a
CONTROL-M environment for a language other than
English.
Index
Related Documentation
The following BMC publications are relevant to CONTROL-M version
6.1.03.
CONTROL-M Upgrade Guide describes how to upgrade from an

earlier version of CONTROL-M/EM, CONTROL-M/Server or
CONTROL-M/Agent.
xx
CONTROL-M Quick Installation Guides each describe a default

installation of the CONTROL-M Scheduling solution. Each of these
guides is intended for trial and proof-of-concept implementations on
a specific default configuration (for example a Unix-based
installation).
CONTROL-M/Enterprise Manager User Guide describes

CONTROL-M/EM concepts, features, facilities, and operating
instructions.
CONTROL-M Job Parameter and Variable Reference Guide

describes syntax and usage for all parameters and variable that are
included in CONTROL-M job processing definitions.
CONTROL-M Utility Guide describes command-line utilities that

can be used to perform various CONTROL-M tasks in batch.
CONTROL-M/Desktop User Guide describes how to define and

manage CONTROL-M job processing definitions, Scheduling tables,
and Calendars.
CONTROL-M/Enterprise Manager Administrator Guide

describes the tasks that the CONTROL-M/EM administrator must
perform to define and to monitor and maintain the
CONTROL-M/EM environment.
CONTROL-M/Server Administrator Guides describe setup,

maintenance, and security, for CONTROL-M/Server on Unix or
Microsoft Windows.
CONTROL-M/Agent Administrator Guides describe setup,

maintenance, and security, for CONTROL-M/Agent on various types
of computers (for example, Unix or Microsoft Windows).
CONTROL-M User Manual (for OS/390) is a complete guide to

the CONTROL-M Production Control System in a mainframe
environment.
About This Book
xxi
Online and Printed Books

The books that accompany BMC Software products are available in
online format and printed format. You can view online books with
Acrobat Reader from Adobe Systems. The reader is provided at no cost,
as explained in To Access Online Books. You can also obtain
additional printed books from BMC Software, as explained in To
Request Additional Printed Books.
To Access Online Books
Online books are provided as Portable Document Format (PDF) files.

You can view them, print them, or copy them to your computer by using
Acrobat Reader 3.0 or later. You can access online books from the
documentation compact disc (CD) that accompanies your product or
from the World Wide Web.
In some cases, installation of Acrobat Reader and downloading the
online books is an optional part of the product-installation process. For
information about downloading the free reader from the Web, go to the
Adobe Systems site at http://www.adobe.com.
To view any online book that BMC Software offers, visit the support
page of the BMC Software Web site at http://www.bmc.com/support.html.
Log on and select a product to access the related documentation. (To log
on, first-time users can request a user name and password by registering
at the support page or by contacting a BMC Software sales
representative.)
To Request Additional Printed Books
BMC Software provides a core set of printed books with your product
order. To request additional books, go to
http://www.bmc.com/support.html.
xxii
Online Help
You can access Help for a product through the products Help menu. The
online Help provides information about the products graphical user
interface (GUI) and provides instructions for completing tasks.
Release Notes
Printed release notes accompany each BMC Software product. Release
notes provide up-to-date information such as
updates to the installation instructions

last-minute product information
The latest versions of the release notes are also available on the Web at
http://www.bmc.com/support.
Conventions
The following abbreviations are used in this guide:
Abbreviation
Description
CONTROL-M/EM
CONTROL-M/Enterprise Manager
The following conventions are used in this guide:
About This Book
xxiii
<key>
When describing keystrokes, angle brackets are

used to enclose the name of a key (for
example, <F1>). When two keys are joined with +
as in <Shift>+<F1>, hold down <Shift> while
pressing <F1>.
Menu => Option
This represents an option selection sequence. For

example,
Users and Groups => Groups => Add
means that you first select Users and Groups from
the menu bar. Select the Groups option from the
submenu. Finally, select the Add option from the
Groups submenu.
{Option A|Option B}
The vertical bar is used to separate choices. For

example:
{AND|OR}
means that you specify either AND or OR.
[Option]
Square brackets are used to enclose parameters

that are optional.
Code Samples
Format syntax, operating system terms,

examples, and JCL scripts are
presented in this typeface.
Option Symbol
A vertical bar ( | ) separating items indicates that

you must choose one item. In the following
example, you would choose a, b, or c:
a|b|c
xxiv
Getting Started
This book guides you through the CONTROL-M installation process.

Table 1-1 describes the chapters that make up the CONTROL-M
Installation Guide.
Note
If you are upgrading to version 6.1.03 from an earlier version of

CONTROL-M, you can perform an abbreviated planning phase. Review
this chapter quickly to confirm that you have the necessary prerequisites,
and then continue with the instructions in the CONTROL-M Upgrade
Guide.
Table 1-1
Parts of the CONTROL-M Installation Guide
Chapters
Description
1 through 4
Planning and Preparation

Describe how to determine which CONTROL-M products you
need and how to prepare for installation of these products.
5 through
14
Installation Procedures
Each of these chapters describes the installation procedure
for a specific CONTROL-M product on a specific type of
computer.
Instructions for how to install an Oracle Database using the
supplied CDs is also included in these chapters.
15 through
17
Configuration
Describe various post-installation steps that are used to
ensure communication between CONTROL-M products.
These chapters also include uninstallation procedures and
troubleshooting information for failed installations.
Getting Started
1-1
The remainder of this chapter describes how to determine which

CONTROL-M products and configurations are appropriate for your site.
Step 1 Choose Which CONTROL-M Products

to Install
Identify your scheduling needs, and then consult with your BMC
Software representative to determine how CONTROL-M should be set
up to respond to these needs. Your BMC representative may also suggest
additional functions of CONTROL-M that can enhance business process
automation at your site. Possible issues are:
Coordination between different applications

Coordination between sites with different types of computers in
different locations.
Incorporation of information arriving from outside sources (for
example, the internet).
Figure 1-1 illustrates the relationships between the various products in

the CONTROL-M scheduling solution. These products are further
described in Table 1-2.
1-2
Figure 1-1
CONTROL-M Products
Table 1-2
CONTROL-M Products
Product
Description
CONTROL-M/Enterprise
Manager
(CONTROL-M/EM)
The central GUI-based control center from which you can manage all
scheduling and workflow activities.
CONTROL-M/EM is composed of a number of different components.
These components can be installed together on a single computer, or
they can be distributed across a number of different computers.
For more information about CONTROL-M/EM components, see
Appendix B, CONTROL-M/EM Components.
CONTROL-M/Server
The engine (on a Unix or Microsoft Windows computer) used to drive

scheduling in a data center. Each CONTROL-M/Server can manage
multiple CONTROL-M/Agents on various platforms.
CONTROL-M/Agent
The software responsible for job submission and execution. An Agent

must exist on each computer that is used to execute CONTROL-M jobs.
CONTROL-M/eTrigger
A web-based product that enables you to use input from a web page to
create and run jobs under CONTROL-M.
CONTROL-M/Control
Module
(CONTROL-M/CM)
CONTROL-M Control Modules enable CONTROL-M/Agents to interface

with other applications (for example SAP, Oracle Applications, and FTP).
Getting Started
1-3
Step 2 Choose a Database Configuration

CONTROL-M/EM and CONTROL-M/Server each maintain a database
using an Oracle Server, a Sybase Adaptive Server, or an MSSQL Server.
These databases can be implemented in the following ways:
Dedicated installation: Installs a new database server, and creates a

CONTROL-M database on this database server.
Dedicated installation of the CONTROL-M database is not supported
for CONTROL-M/Server on Windows.
Existing installation: Uses a database server that is already installed.

Creates a new database on that database server, and installs a
database client on the local computer.
You can also use an existing Oracle Client and Database (Database
Connection Only described above). This type of installation is
described in Appendix G, New Database Schema on an Existing
Oracle (Microsoft Windows), and Appendix F, New Database
Schema on an Existing Oracle (Unix).
Client installation: Installs database client software and configures

the computer for connection to a CONTROL-M database on a
different computer.
Not every database server is supported on every platform or in every

installation format. Supported formats are listed in Table 1-3.
1-4
Table 1-3
Database
Type
Oracle
Database Server Configurations CONTROL-M
Description
An Oracle database server must be installed before CONTROL-M/EM and
CONTROL-M/Server are installed.
For Unix: Supported by CONTROL-M/EM and CONTROL-M/Server. Installation
CDs are provided for Oracle 9.2.0.4.
For Microsoft Windows: Supported by CONTROL-M/EM only. Installation CDs
are provided for Oracle 9.2.0.1.
Notes:
If you already have Oracle Server 8.1.7, it is supported as an existing installation
only. In this case, it is recommended that you install a version 9.2 client in the
CONTROL-M/Server or CONTROL-M/EM account (using the provided installation
CD).
Existing Oracle database servers with a full Enterprise edition installed can be
used for CONTROL-M databases. Oracle Standard edition servers cannot be used.
For more information about installation of an Oracle Database, see Chapter 5,
Installing an Oracle Database on Unix and Chapter 6, Installing an Oracle
Database on Microsoft Windows.
Getting Started
1-5
Table 1-3
Database
Type
Database Server Configurations CONTROL-M
Description
Sybase
For Unix: Supported by CONTROL-M/EM and CONTROL-M/Server.

An existing Database server can be used, or the Sybase Database server can be
installed during installation of CONTROL-M/EM or CONTROL-M/Server using a
separate installation CD.
For Microsoft Windows: Supported by CONTROL-M/EM only. A Sybase client is
installed with CONTROL-M/EM. For this configuration, the Sybase Database server
must be installed by the user on a different computer before CONTROL-M/EM.
MSSQL
An MSSQL Database Server must be installed before CONTROL-M/EM and

CONTROL-M/Server are installed.
For Unix: Not Supported.
For Microsoft Windows: Supported by CONTROL-M/EM and
CONTROL-M/Server.
Notes:
In addition to the database server, MSSQL clients must be installed on each
machine that will host CONTROL-M/Server or any component of CONTROL-M/EM
(aside from Orbix E2A, the CONTROL-M/EM GUI, CONTROL-M/Desktop, and the
Command Line interface).
For compatibility reasons, the MSSQL database must be configured as
"case-sensitive". If you install your CONTROL-M/EM database on an MSSQL
Database server that is not case-sensitive, the new database is nevertheless
configured as case-sensitive.
The MSSQL Client is not installed as part of the CONTROL-M product installation,
and must be installed before CONTROL-M product installation.
If you install CONTROL-M/Server or CONTROL-M/EM on the same computer as
an existing MSSQL server, there is no need to install the MSSQL Client.
Calculating Database Size
The size of your CONTROL-M databases will depend on the number and
type of processes that will be managed by CONTROL-M.
To ensure that you have enough space for your databases, you can
calculate their approximate size before installation of CONTROL-M
products.
For CONTROL-M/EM databases, see Appendix D,

CONTROL-M/EM Database Size.
For CONTROL-M/Server databases, see Appendix E,

CONTROL-M/Server Database Size.
1-6
Step 3 Identify and Arrange for Installation

Resources
Ensure that the following resources will be available to you when you
install CONTROL-M at your site (in addition to the hardware and
software requirements described in the next phase of the installation).
Table 1-4
Installation Resource Requirements
Resource
Requirements
Database
Administrator
Needed for:
Administrator Passwords for Existing Database servers
Information regarding location of SQL servers and data
files.
System
Administrator
Needed for:
Mounting the CD-ROM drive (for most Unix computers)
Definition of User Accounts
Modification of System (Kernel) parameters (for Unix)
Granting Authorization to necessary directories.
Step 4 Map your CONTROL-M solution

Before installing anything you should determine where you are going to
install the major components of the CONTROL-M solution. A typical
solution includes:
CONTROL-M/EM Server components on one computer (Unix or

Microsoft Windows)
CONTROL-M/EM Basic Client components on a number of
computers (Microsoft Windows only)
A small number of CONTROL-M/Server installations (Unix or
Microsoft Windows)
CONTROL-M/Agents on every computer that will be used to run
CONTROL-M jobs.
Getting Started
1-7
A database server (Oracle, Sybase, or MSSQL).

Note
A database will need to be installed for CONTROL-M/EM and for each

CONTROL-M/Server. These databases may all use the same database
server, or each may be totally independent - depending on the size of
your environment and your various requirements.
Tip
You may also choose to install various CONTROL-M/Control Modules

to enable management of jobs produced by other applications (for
example SAP).
If you are planning on integration of Web-based information, you may
also want to install CONTROL-M/eTrigger.
When your map is complete, you should have a list of every computer
that will be part of the CONTROL-M environment, and that list should
indicate which components will be installed on each of those computers.
Step 5 Choosing the Installation CDs

After you have determined your installation type, you will need to choose
the installation CDs from the packages that were provided with
CONTROL-M/EM and CONTROL-M.
Table 1-5 lists the major installation types, and the correct CDs for each
type.
1-8
Table 1-5
Installation CDs by Computer Type
Platform
Required CDs
Microsoft
Windows
FD5305
FD5448
For installation of the CONTROL-M/Server and Agent for Microsoft

Windows.
Note: These two FDs are provided together on a single CD.
FD5143
CONTROL-M Documentation
FD5310
For installation of all CONTROL-M/EM components.
Database
Oracle Server
version 9.2.0.1
FD5381 for the Oracle Database Server

FD5382 for the Oracle Database Client
Sybase or MSSQL
Must be installed using the procedures provided

with these products.
Unix
FD5306
FD5449
For installation of the CONTROL-M/Server and Agent for Unix

Note: These two FDs are provided together on a single CD.
FD5143
CONTROL-M Documentation
FD5307
FD5308
FD5309
For installation of CONTROL-M/EM server components.

AIX FD5307
HP-UX FD5308
Solaris FD5309
Compaq Tru64 not supported
FD5310
For installation of CONTROL-M/EM client components on a Microsoft

Windows computer.
Database
Choose one of the following databases:

Sybase Adaptive
Server version 12
FD5316 for AIX

FD5317 for HP-UX, Solaris, or Compaq Tru64
Oracle Server
version 9.2.0.4
FD5380 CONTROL-M Oracle Installation

Package for Unix and one of the following:
FD5459: for HP-UX (64-bit only) - 5 CDs
FD5458: for AIX version 5.L (64-bit only) - 5
CDs
FD5461 for Solaris 32-bit systems (4 CDs)
FD5462 for Solaris 64-bit systems (4 CDs)
For Solaris 2.8, or 2.9 use the following
command to determine if your system is 32-bit
or 64-bit: isainfo -b
FD5460 for Compaq Tru64 (5 CDs)
Getting Started
1-9
Step 6 Set up and Install CONTROL-M

Components
Use the following table to determine the major steps that you will need to
follow to complete your installation on each computer in your
CONTROL-M solution.
Table 1-6
Major Steps for CONTROL-M Installation
Component
Path
CONTROL-M/EM
Server components
on Unix with Oracle
1. Prepare for installation (see Chapter 3).
CONTROL-M/EM
Server components
on Unix with Sybase
CONTROL-M/EM on
Microsoft Windows
with MSSQL
1. Install or verify the existence of an MSSQL database server version 2000

or later.
2. Install Oracle (see Chapter 5)

3. Install CONTROL-M/EM Server components (see Chapter 7)
2. Install CONTROL-M/EM Server components (see Chapter 7)

3. Install CONTROL-M/EM (see Chapter 8)
4. After all other CONTROL-M components have been installed on other
computers, perform the post-installation configuration tasks (see Chapter
15)
CONTROL-M/EM on
Microsoft Windows
with Oracle

After all other CONTROL-M components have been installed on other
computers, perform the post-installation configuration tasks (see Chapter 15)
CONTROL-M/EM on
Microsoft Windows
with Sybase
1. Install or verify the existence of a Sybase database server version

12.0.0.7 or later.
4. After all other CONTROL-M components have been installed on other
computers, perform the post-installation configuration tasks (see Chapter
15)
1-10
Table 1-6
Major Steps for CONTROL-M Installation
Component
Path
CONTROL-M/Server
on Unix with Sybase

2. Install CONTROL-M/Server (see Chapter 9)
3. Perform the relevant post-installation configuration tasks (see Chapter
15)
CONTROL-M/Server
on Unix with Oracle

15)
CONTROL-M/Server
on Microsoft Windows
1. Install or verify the existence of an MSSQL database server version 2000

or later.
or use the silent installation procedure described in Chapter 11.
15)
Getting Started
1-11
1-12
Pre-Installation Steps for Unix with a

Sybase Database
2
This chapter describes the steps that must be performed before
installation of CONTROL-M products on a Unix computer to be used
with a Sybase database.
Before you proceed with the steps described below, verify that you have
reviewed Chapter 1, Getting Started. You should now have a plan
indicating which CONTROL-M products will be installed, and which
computers they will be installed on.
Note
If you are upgrading from a previous release of CONTROL-M, many of

the steps in this chapter will not require any action. However, it is highly
recommended that you review these steps to verify that you have all the
necessary information ready before you proceed to the upgrade
procedure.
During upgrade from a previous version of CONTROL-M/Server or
CONTROL-M/EM, you can choose to switch databases, database sizes
and many other parameters.
2-1
Step 1 Prepare for Database Installation

Step 1.1 Choose a Sybase Database Configuration
1.1.1
Existing or Dedicated?
CONTROL-M products can either be installed with a new database
(dedicated), or they can use a database server that has already been
installed (existing).
1.1.2
If you are planning to install a dedicated Sybase database server,

continue with Step 1.1.2 below
If you are planning to use an existing Sybase database server,

continue with Step 1.2 on page 2-4.
Decide if the Sybase database should be installed on raw partitions

During CONTROL-M/Server or CONTROL-M/EM installation, you can
choose either a regular file system or raw partitions for the database.
1.1.3
If you intend to use raw partitions, continue with Step 1.1.3 below.
If you intend to use a regular file system, skip to Step 2 on page 2-6.
Set Up Raw Partitions for the CONTROL-M/Server or

CONTROL-M/EM database
You must prepare the required partitions before starting CONTROL-M
product installation. The number and size of partitions that you can use
depends on the type of installation.
For a Compact installation of CONTROL-M/Server, or

CONTROL-M/EM Default installation, you cannot use raw
partitions. All elements of the database must use regular files. For
this type of installation, continue with Step 2 on page 2-6.
2-2
For a Typical installation (CONTROL-M/Server only), you can set

aside two partitions, (one each for data and log), with a total of at
least 50 MB. (The size of the log partition should be 33% of the size
of the data partition.) The other three elements of the database use
regular files.
For a Custom installation of CONTROL-M/Server or

CONTROL-M/EM, you can prepare between two and five partitions.
data and log must each have their own partition. In addition,
tempdb, systemprocs, and masterdb can each be assigned a
partition.
Note
Each partition can be used for only one element of the database.
It is not recommended to use a raw partition for tempdb.
Elements of the database that do not use raw partitions use regular files.
The minimum sizes of the partitions are described in Table 2-1.
Table 2-1
Minimum Partition Sizes for a Sybase Installation
Partition
Size
data
50 MB for CONTROL-M/Server
80 MB for CONTROL-M/EM
log
tempdb
systemprocs
80 MB
master
30 MB
Ask the system administrator for more information about raw partitions.
1.1.4
If you are installing a Sybase database on raw partitions, ensure the

Asynchronous IO is turned on:
For HP-UX, consult your system administrator for how to do this.
2-3
For AIX, this will be described in a later phase of the preparation

steps (in Step 3.2 on page 2-14).
For Compaq Tru64 and Solaris, asynchronous IO is on by default.
Step 1.2 Prepare to Install with an Existing Sybase

Database Server
1.2.1
Obtain the SA (System Administrator) password. This will be necessary

in order to continue building the database.
1.2.2
Use the following command on the computer where the Sybase Database
server is installed, to verify that it is running:
isql -U <DBA_usr> -P <DBA_pwd> -S <server_name>
Where:
<DBA_usr> is the name of the DBA account (Sybase default: sa)
<DBA_pwd> is the DBA account password (Sybase default: password)
<server_name> is the name of the target Sybase database server
Note
The existing Sybase database server must be running during installation

and whenever CONTROL-M/EM or CONTROL-M/Server is operating.
1.2.3
Verify that the Sybase device names and the device file name paths are
unique and valid names. The device file names reside on the local file
system on which the Sybase Database Server is installed.
1.2.4
Use the following command to ensure that parameters in Table 2-2

contain appropriate values:
sp_configure <parameter_name>, <desired_value>
2-4
Table 2-2
Sybase Database Server Parameters Minimum Values
Item
Small
< 80 MB
Medium
80-200 MB
Large
> 200 MB
number of locks
30,000
30,000
40,000
number of user connections

Note: The number of user
connections is the total number
of connections to the Sybase
Database Server required for all
applications accessing the
Sybase Database Server,
including all CONTROL-M/EM
and CONTROL-M/Server
installations.
60
100
200
total memory (in Sybase blocks)
32, 768
40,000
100,000
If you change any of these parameters, the change will not be

implemented until you shut down and restart the Sybase Database Server.
1.2.5
Obtain a database name and a database owner name (DBO) to be

specified for the CONTROL-M/Server database and the
CONTROL-M/EM database.
Use the sp_helpdb command to verify that the database name and
database owner name are unique for the Sybase Database Server. Note
that the database name and the database owner name can be identical to
each other.
Note
When creating more than one CONTROL-M installation using the same
Sybase Database Server, the database name and database owner name
must be unique for each installation.
2-5
Step 2 Check System Requirements

Verify that your computer meets the minimum requirements for
installation of CONTROL-M products.
Note
The requirements listed for all platforms are minimum requirements. You
may need to add additional memory, increase disk space, and so on to
ensure optimum system performance.
For the most current compatibility information, see
http://www.bmc.com/supportu/PAC_utility/index.cfm.
Step 2.1 Check Locale Settings

Ensure that locale parameters, in the CONTROL-M account, are set to an
English variant locale (for example C, english, us_english).
Step 2.2 Check Operating System Levels and Patches

In this step, you will run the check_req.sh script. This script checks the
operating system version, maintenance level (patches), and Unix kernel
parameters. The output of this utility indicates if the computer is
compatible with the requirements of CONTROL-M/EM and
CONTROL-M/Server.
2-6
2.2.1
Download the pre_req.tar.Z file from the following location:
ftp://ftp.bmc.com/pub/control-m/opensystem/FD4928/
Note
The check_req.sh file is located in the pre_req directory on the

CONTROL-M/Server and CONTROL-M/EM installation CDs. However,
due to constant changes applied to various operating systems, this file
may not check for a patch that supersedes one of the originally required
patches.
It is recommended that you download the latest version of this script
from the above-mentioned location.
2.2.2
If you downloaded the pre_req.tar.Z file from the internet, follow the
instructions in the readme file that is provided as part of this file and then
If you are using the check_req script that is provided on the
CONTROL-M installation CDs, continue with Step 2.2.3.
2.2.3
Log in as a root user.
2.2.4
Mount a CONTROL-M installation CD. For details of mount procedures

for your Unix platform, see Appendix A, Mounting CDs on Unix
Computers.
2.2.5
Use the following command to start this script from the

CONTROL-M/Server or CONTROL-M/EM installation CD:
<CD_path>/pre_req/check_req.sh
2.2.6
In the prompts that follow, specify the product(s) that you intend to
install, their versions, and the database types.
2.2.7
If the operating system and patches meet CONTROL-M requirements,

messages similar to the following are displayed:
2-7
Operating System patches check completed successfully

You can now install CONTROL-M/EM on this <OStype> <OSver> <OSbits> bit
computer
Where:
<OStype> is the type of Unix (AIX, HP-UX, Solaris, or COMPAQ

Tru64)
<OSver> is the version of the operating system
<OSbits> is either 32 or 64.
If the operating system version or patches do not match expected

requirements, messages similar to the following are displayed indicating
the required patches and versions.
The following $os_type patches or packages are missing. Please ask your
system administrator to either verify that a superceding patch has been
installed for each missing patch, or to install them and then restart
check_req.sh
If necessary, consult your system administrator to verify that either the

required patches or patches that supersede them have been installed on
your computer.
Note
For more specific information about required operating systems levels

and patches, see Appendix C, Unix Operating System Requirements.
Step 2.3 Check Hardware Requirements

Note
All commands that are used to check the requirements described below
should be performed from a root user account.
Verify that your computers have the minimum necessary hardware:
2-8
2.3.1
Verify that your computer meets the hardware requirements in the

following table:
Table 2-3
2.3.2
Vendor
Minimum Requirement
AIX
IBM RISC System/6000
HP-UX
HP 9000/700 or HP 9000/800.
Solaris
Sun SPARCstation
Compaq Tru64
Digital Unix Alpha System (for CONTROL-M/Server only)
Verify that each computer also has the following hardware:

Table 2-4
2.3.3
Unix Computer Types
Unix Hardware Requirements
Item
Description
Media Drive
CD-ROM drive.
Communication
Adapter
Any TCP/IP adapter is acceptable.
Verify that your computers have the necessary memory requirements for
CONTROL-M components.
Table 2-5 lists the memory requirements for each CONTROL-M

product.
Table 2-6 describes how to check available memory on Unix
computers.
Note
For information about calculating database memory requirements, see

Appendix D, CONTROL-M/EM Database Size, and Appendix E,
2-9
Table 2-5
Unix Memory Requirements
CONTROL-M
Product
CONTROL-M/EM
with Sybase
128 MB RAM for running the operating system, the

RDBMS, X-Windows, communication, and so on.
-plus 10 MB RAM for each concurrent CONTROL-M/EM user.
18 MB RAM for the Sybase Adaptive Server (on AIX or
HP-UX).
24 MB RAM for the Sybase Adaptive Server (on
Solaris).
64 MB RAM for CONTROL-M/EM database files.
CONTROL-M/
Server with
Sybase
Memory required for a database of size x MB:

30 MB < x < 50 MB requires 64 MB RAM.
50 MB < x < 250 MB requires 80 MB RAM.
x > 250 MB requires 200 MB RAM.
Table 2-6
How to Check Available Memory
Vendor
How to check available RAM
AIX
Use the following command to determine the amount of

available memory in Kilobytes:
lsattr -El sys0 -a realmem
Divide the result of the command by 1024 to get the
number of MB.
HP-UX
Log in as the root user and use the following command to

check how much RAM is supplied with your computer:
/usr/sbin/dmesg
Solaris
prtconf -v |grep Memory
Compaq Tru64
Enter the following command as a superuser:

vmstat -P | more
2-10
RAM Requirements
2.3.4
Verify that your computers have the necessary disk space requirements
for CONTROL-M components. Table 2-7 on page 2-11 lists disk space
requirements for each CONTROL-M product.
Tip
Use the following command to check how much disk space (in kilobytes)
is available on your partition:
df -k .
Table 2-7
Disk Space Requirements
CONTROL-M
Product
CONTROL-M/EM
files on AIX
Program Files
New CONTROL-M/EM 6.1.03 installation: 522 MB free
disk space for the programs.
It is recommended that an area three times the amount
of RAM in the system be reserved for swap space.
Sybase Adaptive Server and Database Files
323 MB for Sybase Adaptive Server files.
The default size of the CONTROL-M/EM database is
220 MB.
Note: The amount of free space in the file system in which
the Sybase database server is installed cannot exceed
4 GB.
CONTROL-M/EM
files HP-UX
Program Files
220 MB.
2-11
Table 2-7
CONTROL-M
Product
CONTROL-M/EM
files on Solaris
Program Files
220 MB.
Note: The amount of free space in the file system in which
the Sybase database server is installed cannot exceed
4 GB.
CONTROL-M/
Server files
(all platforms)
200 MB. An additional 100 MB disk space may be

required if you are planning to run CONTROL-M in Debug
mode.
CONTROL-M/
Server Database
using Sybase
(all platforms)
Dedicated Sybase server installation: 570 MB

When x is the size of the database in MB.
Disk space required is: (x + 570 + x * 0.6) MB
CONTROL-M/Server database using an existing
Sybase Database Server: 210 MB
Note:
For AIX and Solaris: The amount of free space in the file
system in which the Sybase database server is installed
cannot exceed 4 GB.
Step 3 Check and Modify System Parameters

Preparation for installing CONTROL-M varies by platform.
For CONTROL-M/EM on HP-UX, see Step 3.1 on page 2-13.

For CONTROL-M/Server on HP-UX, skip to Create the
CONTROL-M/Server Administrator Account on page 2-24
For AIX, see Step 3.2 on page 2-14.
For Solaris, see page 2-16.
For Compaq Tru64, see page 2-18
2-12
Step 3.1 HP-UX

We recommend that you ask your system administrator to modify the
necessary system (kernel) parameters. If you must make these changes
yourself, follow the instructions below very carefully.
Note
If changes are made to kernel parameters, the Unix computer will have to
be rebooted at the end of this procedure.
3.1.1
Log on as user root.
3.1.2
Type sam and press <Enter>.
3.1.3
Use the down arrow to select Kernel Configuration and press <Enter>.
3.1.4
Use the down arrow to select Configurable Parameters and press

<Enter> a list of parameters is displayed.
Table 2-8 lists the values that are recommended for installing with an
Oracle database server.
Table 2-8
3.1.5
Kernel Parameters HP-UX with Oracle
Parameter
Value
max_thread_proc
512. This value is appropriate for a

CONTROL-M/EM installation with up to 50
CONTROL-M definitions, 80 ViewPoints and 30
concurrent users.
Note: If your datacenter is larger than this
configuration, contact BMC Technical Support for
the value for this parameter. For more information
about CONTROL-M definitions, and ViewPoints,
see the CONTROL-M/Enterprise Manager User
Guide.
To change the value of a kernel parameter:
2-13
A:
Use the down arrow to move the cursor to the parameter.
B:
Press the spacebar to select the parameter.
C:
Press <Tab> to activate the menu bar.
D:
Press the right arrow until the Actions menu is selected.
E:
Use the down arrow to select the Modify Configurable Parameters

option, and press <Enter>
F:
Use the <Tab> key to go to the Formula/Value field and enter the
desired value. (If the default value is more than needed, do not
change it.)
G:
Use the <Tab> key to go to the [OK] button and press <Enter>
3.1.6
When you have finished modifying all relevant parameters, use the
<Tab> key to activate the menu bar.
3.1.7
Use the down arrow to select the Choose Process New Kernel option
using down arrow and press <Enter>. (This action will reboot the Unix
computer. It may take a few minutes.)
3.1.8
Continue your installation preparation with Step 5 on page 2-22.
Step 3.2 AIX

Use the following steps to activate the RS/6000 Asynchronous I/O
option:
3.2.1
3.2.2
Enter the following command to ensure that you are using an appropriate
display setting:
setenv DISPLAY <hostname>:0.0
3.2.3
Enter the following command:
2-14
smit aio
3.2.4
Select the Change/Show Characteristics of Asychronous I/O option.

Enter the following values for the displayed parameters:
Parameter
Value
Minimum number of servers
Maximum number of servers
10
Maximum number of requests I/O
4096
Server priority
39
ASYNC I/O State to be configured at system start
Available
State of fast path
Enabled
Note
If your system uses more than seven hard disks for Asynchronous I/O,
the Maximum number of servers setting must be increased by one for
every active device after the seventh.
3.2.5
Click OK and wait for the operation to complete.
3.2.6
Click Done. Control returns to the main Asynchronous I/O menu.
3.2.7
Select the Configure Defined Asynchronous I/O option.
3.2.8
Press <F12> to exit from smit.
3.2.9
Log out.
3.2.10
Exit the shell prompt.

Note
If State to be configured at system start is not

Available (for example, defined), the computer must be rebooted at
the end of the procedure.
2-15
3.2.11
Continue installation preparation:
If you are installing CONTROL-M/EM using an existing Sybase

Database server, continue your installation preparation with Step 4
on page 2-19.
For installation of CONTROL-M/EM with a new (dedicated) Sybase

database server, continue with Step 5 on page 2-22.
For installation of CONTROL-M/Server with a new (dedicated)

Sybase database server, continue with Step 6 on page 2-24.
Step 3.3 Solaris

It is recommended that you ask your system administrator to modify the
yourself, follow the instructions provided below very carefully.
Note
If changes are made to kernel parameters, the Unix machine will have to
3.3.1
3.3.2
Open the operating system configuration file /etc/system

Each line in the /etc/system file has the following format:
set shmsys:shminfo_<param_name>=<value>
For example, to set the shmmin parameter to 1:
set shmsys:shminfo_shmmin=1
3.3.3
If necessary, add/modify the parameters (as listed in Table 2-9).
2-16
Table 2-9
Kernel Parameters Solaris with Sybase
Parameter
Minimum Value
shmmax
Same as the amount of RAM (in bytes) on this computer. For

information about how to determine the amount of RAM on
your computer, see the table on page 2-10.
shmseg
36
semvmx
32767
3.3.4
If you modified any of the system (kernel) parameters, reboot the

computer.
3.3.5
In the console window, run the xhost + command. This command will
ensure that your computer can be accessed using a Unix emulation for
CONTROL-M installation.
3.3.6
Continue installation preparation:
If you are installing CONTROL-M/EM using an existing Sybase

Database server, continue your installation preparation with Step 4
on page 2-19.


2-17
Step 3.4 Compaq Tru64 (OSF1)

3.4.1
Verify that system (kernel) parameters match the requirements listed in

Table 2-10. It is recommended that you ask your system administrator to
modify the necessary system (kernel) parameters.
Note
Kernel configurations should be performed under the root user. If any of

the parameters are changed, the system must be rebooted for changes to
take effect.
If changes are made to kernel parameters, the Unix machine will be have
to be rebooted at the end of this procedure.
Table 2-10
3.4.2
Kernel Parameters Compaq Tru64 with Sybase
Parameter
Minimum Value
shmmax
About one-half the amount of RAM (in bytes) on

this computer. To determine the amount of RAM on
your computer, see Table 2-5, Unix Memory
Requirements, on page 2-10.
ssm-threshold
Continue installation preparation with Step 6 on page 2-24.
2-18
Step 4 Create Database Devices

This step is relevant only if you are installing CONTROL-M/EM using
an existing Sybase Database server.
Note
If you are upgrading from an earlier version of CONTROL-M/Server or

CONTROL-M/EM, consult Chapter 1 of the CONTROL-M Upgrade
Guide in order to determine how to proceed.


In this step you will use the disk init command to allocate data and log
devices.
Note
Only a superuser can execute the disk init command on the Sybase
Adaptive Server host computer.
4.0.1
Use the following command to log on as the Sybase Adaptive Server

superuser on the computer on which the Sybase database server is
installed:
isql -U sa -P <DBA_Password> -S <Sybase_host>
where <Sybase_host> is the hostname that is specified in the Sybase

interfaces file on the computer where Sybase is installed.
4.0.2
Determine if there are free device numbers that are available. Any free
device numbers can be used in the disk init command in Step 4.0.4
(below). Use the following command to display a list of occupied device
numbers:
2-19
select distinct convert(int,(low/power(2,24))) & 255

from sysdevices order by 1
go
If no free devices are available, ask your database administrator to

increase the value of the Sybase number_of_devices parameter.
4.0.3
Enter the following command to display the number of existing devices

already assigned to the Sybase database server.
sp_configure "number of devices"
go
4.0.4
Enter the following disk init command twice, once for the data device
and once for the log device. For disk init examples, see page 2-21.
disk init
name = "<logical_device_name>",
physname = "<physical_pathname>",
vdevno = <virtual_device_number>,
size = <number_of_pages>
go
Note that:
A:
The value for <number_of_pages> is given by the formula

(database size in MB) * 512
For example, for a 1200 MB database:
<number_of_pages> = 1200 * 512 = 614400.
B:
For <virtual_device_number>, do not use any occupied device

number that was listed in Step 4.0.2 or Step 4.0.3.
C:
Record the values you give to each device in the parameter line
name= <logical_device_name>
You will need these names during the installation process.
2-20
disk init Examples

disk init
name = "em610_dat",
physname = "/home/ecs/sybase/em610.dat",
vdevno = 9,
size = 40960
go
disk init
name = "em610_log",
physname = "/home/ecs/sybase/em610.log",
vdevno = 10,
size = 10240
go
4.0.5
Continue installation preparation with Step 5 on page 2-22.

2-21
Step 5 Create the CONTROL-M/EM

Administrator Account
In this step, you will create the user account for the CONTROL-M/EM
administrator. If you are not familiar with how to do this, consult your
system administrator.
Notes
The CONTROL-M/EM administrators account must include a home

directory with sufficient diskspace for installation of
CONTROL-M/EM components (described in Table 2-7 on page
2-11).
Any valid group name is acceptable.
The initial program for the CONTROL-M/EM administrators user

account must be specified as /bin/csh, or /bin/ksh.
Perl is installed during CONTROL-M/EM installation. The location

of the Perl files is recorded in the .cshrc or .profile files.
For Solaris computers the Perl shared library path is recorded
using the using the LD_LIBRARY_PATH parameter.
For HP-UX computers the Perl shared library path is recorded
using the using the SHLIB_PATH parameter.
For AIX computers the Perl shared library path is recorded using
the using the LIBPATH parameter.
If you have another copy of Perl installed on your computer, you will
need to use the full path to access that copy.
2-22
Setting Limits for the CONTROL-M/EM User Account
Unix computers have predefined limits which ostensibly avoid excessive

use of resources by a process. When the process rises past the limit
specified, the Operating System may kill the process in a way that allows
for no clean up or diagnostics generation.
Unix default limits are also very small, and unexplained outages may
occur when the Operating System terminates a naturally growing
process. We recommend setting limits to higher values to avoid these
unexpected outages, which may be mistaken for an actual product failure.
The current limits in your machine can be checked by issuing the limit
command. (The limit command may be reserved for the Super User on
some Operating Systems installations.)
The limits that are affect CONTROL-M/EM processes are described in
Table 2-11, Limits for the CONTROL-M/EM User Account, on page
2-23.
Table 2-11
Limits for the CONTROL-M/EM User Account
Parameter
Description
datasize
The maximum size of the "data" segment of a process.

Maximum applicable values are
Solaris: 2GB
HP-UX: 4GB (using third and fourth quarter enabled)
AIX: 2GB
stacksize
The maximum size of the stack segment of a process. We

recommend 400 MB for all Unix types.
coredumpsize
The maximum size that a core dump can reach. We

recommend that this be set to be the same as the datasize,
so that a complete core dump can be generated if a failure
occurs. There must also be enough disk space available for
the complete core dump to be generated.
descriptors
The maximum number of descriptors in use by a single

process. Recommended value: 2000
Note: This parameter should not be set to unlimited.
memoryuse
The maximum amount of memory to be used by a single

process. We recommend that this be set to unlimited.
2-23
Step 6 Create the CONTROL-M/Server

In this step, you will create the user account for the
CONTROL-M/Server administrator. If you are not familiar with how to
do this, consult your system administrator.
Verify that:
The home directory of the CONTROL-M/Server administrators

account has sufficient diskspace to install CONTROL-M/Server
components (as described in Step 2.3 on page 2-8).
The administrators group name is controlm. If necessary, create a

new group.
The HOME directory parameter for the CONTROL-M/Server

administrators account must contain the full path name of the
directory to be created for the CONTROL-M/Server administrator.
The specified HOME directory must be on a local disk. NFS and
other mount disk systems (for example, clusters) are not supported.
The initial program for the CONTROL-M/Server administrators

user account must be specified as /bin/csh, or /bin/tcsh.
2-24
Step 7 Review Installation Parameters

Each installation procedure that is described in this book is followed by a
table that describes the parameters and prompts for that procedure. If this
is the first time that you are installing CONTROL-M, it is recommended
that you review the tables in the appropriate installation chapters. This
will help you gather whatever information is necessary before you run
the actual installation.
Step 8 Where to go from here

This completes the Preparation phase of CONTROL-M installation on a
Unix computer.
To install CONTROL-M/Server on Unix with a Sybase database,

continue with Chapter 9, Installing CONTROL-M/Server for Unix.
To install CONTROL-M/EM Server components on Unix with a

Sybase database, continue with Chapter 7, Installing
CONTROL-M/EM on Unix.
Note

2-25
2-26
Pre-Installation Steps for Unix with an

Oracle Database
3
This chapter describes the steps that must be performed before
installation of CONTROL-M products on a Unix computer to be used
with an Oracle Database.
Note
Before you proceed with the steps described below, verify that you have
planned your CONTROL-M configuration as described in Chapter 1,
Getting Started.
3-1
Before you Begin
Make sure that you have reviewed Chapter 1 and now have a plan
indicating which CONTROL-M products will be installed, and which
computers they will be installed on.
Note
If you are upgrading from a previous release of CONTROL-M, many of

the steps in this chapter will not require any action. However, it is highly
recommended that you review these steps to verify that you have all the
necessary information ready before you proceed to the upgrade
procedure.
During upgrade from a previous version of CONTROL-M/Server or
CONTROL-M/EM, you can choose to switch databases, database sizes
and many other parameters.
Step 1 Choose a Files or Raw Partitions for

the Oracle Database
During CONTROL-M/Server or CONTROL-M/EM installation, you can
choose either a regular file system or raw partitions for the database.
1.0.1
If you wish to use raw partitions for the CONTROL-M/EM or

CONTROL-M/Server database, prepare them before installation of the
Oracle Database server.
The size of each raw partition must be equal to the size of the tablespace
plus 4 MB.
Note
Oracle Database log files must not be placed on a raw partition.

Ask the system administrator for more information about raw partitions.
3-2
1.0.2
If you will be installing only one new (dedicated) database using a new
Oracle Database server, continue with Step 2 on page 3-5.
If you will be using an existing Oracle database server, continue with
Step 1.1 on page 3-3.
Note
If you will be installing databases for CONTROL-M/EM and

CONTROL-M/Server together on one dedicated server, the first database
installation will create the dedicated server, and the second database
installation will treat this newly installed instance as an existing server.
Review Step 1.1 on page 3-3 to prepare for the second database
installation.
Step 1.1 Prepare to Install with an Existing Oracle Database

Server
Existing Oracle database servers must have a full Enterprise edition
installed, including support for the partitioning option. Oracle Standard
edition servers cannot be used for CONTROL-M databases.
Note
If you are going to be using a dedicated Oracle Database server, skip this
step and continue with Step 2 on page 3-5.
1.1.1
Using the operating system account that installed the Oracle server, log
in to the computer where the Oracle database server is installed.
Note
The existing Oracle database instance must be running during installation

and whenever CONTROL-M/EM or CONTROL-M/Server is operating.
3-3
1.1.2
Use the following command to verify that Oracle Database server is

running:
sqlplus <DBA_usr>/<DBA_pwd>
where:
<DBA_usr> is the name of the DBA account (Oracle default: system)
<DBA_pwd> is the DBA account password (Oracle default: manager)
1.1.3
Verify that this database is served by an Oracle listener running on the

same computer on which the database is installed.
1.1.4
A tablespace name and a tablespace owner name (DBO) must be

specified for each CONTROL-M database.
The tablespace name and tablespace owner name must be unique for
each Oracle Database server.
To display a list of existing tablespace names:
1. Login as the database administrator.

2. Type the following SQL instruction:
SQL> select tablespace_name from dba_tablespaces;
To display a list of existing usernames:
1. Login as the database administrator.

2. Type the following SQL instruction:
SQL> select username from all_users;
Note
When creating more than one CONTROL-M installation using the same
Oracle Database server, be sure to specify a unique tablespace name and
tablespace owner name for each installation.
3-4

Verify that your computer meets the minimum requirements for
installation of CONTROL-M products.
Note
The requirements listed for all platforms are minimum requirements. You
may need to add additional memory, increase disk space, and so on to
ensure optimum system performance.
Step 2.1 Check Locale Settings

Ensure that locale parameters, in the CONTROL-M account, are set to an
English variant locale (for example C, english, us_english).
Step 2.2 Check Operating System Levels and Patches

In this step, you will run the check_req.sh script. This script checks the
operating system version, maintenance level (patches), and Unix kernel
parameters. The output of this utility indicates if the computer is
compatible with the requirements of CONTROL-M/EM and
CONTROL-M/Server.
3-5
2.2.1
Download the pre_req.tar.Z file from the following location:
ftp://ftp.bmc.com/pub/control-m/opensystem/FD4928/
Note
The check_req.sh file is located in the pre_req directory on the

CONTROL-M/Server and CONTROL-M/EM installation CDs. However,
due to constant changes applied to various operating systems, this file
may not check for a patch that supersedes one of the originally required
patches.
It is recommended that you download the latest version of this script
from the above-mentioned location.
2.2.2
If you downloaded the pre_req.tar.Z file from the internet, follow the
instructions in the readme file that is provided as part of this file and then
If you are using the check_req script that is provided on the
CONTROL-M installation CDs, continue with Step 2.2.3.
2.2.3
2.2.4
Mount a CONTROL-M installation CD. For details of mount procedures

for your Unix platform, see Appendix A, Mounting CDs on Unix
Computers.
2.2.5
Use the following command to start this script from the

CONTROL-M/Server or CONTROL-M/EM installation CD:
<CD_path>/pre_req/check_req.sh
2.2.6
In the prompts that follow, specify the product(s) that you intend to
install, their versions, and the database types.
2.2.7
If the operating system and patches meet CONTROL-M requirements,

messages similar to the following are displayed:
3-6
Operating System patches check completed successfuly

You can now install CONTROL-M/EM on this <OStype> <OSver> <OSbits> bit
computer
Where:
<OStype> is the type of Unix (AIX, HP-UX, Solaris, or COMPAQ

Tru64)
<OSver> is the version of the operating system
<OSbits> is either 32 or 64.
If the operating system version or patches do not match expected

requirements, messages similar to the following are displayed indicating
the required patches and versions.
The following $os_type patches or packages are missing. Please ask your
system administrator to either verify that a superceding patch has been
installed for each missing patch, or to install them and then restart
check_req.sh
If necessary, consult your system administrator to verify that either the

required patches or patches that supersede them have been installed on
your computer.
Note
For more specific information about required operating systems levels

and patches, see Appendix C, Unix Operating System Requirements.
Step 2.3 Check Hardware Requirements

Note
All commands that are used to check the requirements described below
should be performed from a root user account.
Verify that your computers have the minimum necessary hardware:
3-7
2.3.1
Verify that your computer meets the hardware requirements in the

following table:
Table 3-1
Unix Computer Types
Vendor
Minimum Requirement
AIX
IBM RISC System/6000

For Oracle installation, hardware must be 64-bit.
HP-UX
HP 9000/700 or HP 9000/800.
For Oracle installation, hardware must be 64-bit.
Solaris
Sun SPARCstation
Compaq Tru64
Digital Unix Alpha System (for CONTROL-M/Server only)
3-8
2.3.2
Verify that each computer also has the following hardware:

Table 3-2
2.3.3
Unix Hardware Requirements
Item
Description
Media Drive
CD-ROM drive.
Communication
Adapter
Any TCP/IP adapter is acceptable.
Verify that your computers have the necessary memory requirements for
CONTROL-M components.
Table 3-3 lists the memory requirements for each CONTROL-M

product.
Table 3-4 describes how to check available memory on Unix
computers.
Note
For information about calculating database memory requirements, see

Appendix D, CONTROL-M/EM Database Size, and Appendix E,
Table 3-3
Unix Memory Requirements
CONTROL-M
Product
RAM Requirements
CONTROL-M/EM
with Oracle
512 MB RAM available.
CONTROL-M/
Server with
Oracle
512 MB RAM available.
3-9
Table 3-4
2.3.4
How to for Check Available Memory
Vendor
How to check available RAM
AIX
Use the following command to determine the amount of

available memory in Kilobytes:
lsattr -El sys0 -a realmem
Divide the result of the command by 1024 to get the
number of MB.
HP-UX
Log in as the root user and use the following command to

check how much RAM is supplied with your computer:
/usr/sbin/dmesg
Solaris
prtconf -v |grep Memory
Compaq Tru64
Enter the following command as a superuser:

vmstat -P | more
Verify that your computers have the necessary disk space requirements
for CONTROL-M components. Table 3-5 on page 3-10 lists disk space
requirements for each CONTROL-M product.
Tip
Use the following command to check how much disk space (in kilobytes)
is available on your partition:
df -k .
Table 3-5
CONTROL-M
Product
CONTROL-M/EM
files on AIX
For a new installation, 522 MB free disk space for the

programs.
CONTROL-M/EM
files HP-UX

programs.
CONTROL-M/EM
files on Solaris

programs.
3-10
Table 3-5
CONTROL-M
Product
CONTROL-M/Server
files (all platforms)
200 MB. An additional 100 MB disk space may be

required if you are planning to run CONTROL-M in
Debug mode.
CONTROL-M/EM
Database
-orCONTROL-M/Server
Database
4 GB of space for the Oracle Server, and 400 MB in

the /tmp directory.
Space for the CONTROL-M/EM database,
depending on the size of database chosen:
Small: 650 MB
Medium: 1.1 GB
Large: 1.9 GB
(all platforms)
Step 3 Check and Modify System Parameters

Preparation for installing CONTROL-M varies by platform.
For CONTROL-M/EM on AIX, skip to Step 4 on page 3-17.

For CONTROL-M/Server on AIX, skip to Step 5 on page 3-19.
For HP-UX, see page 3-11.
For Solaris, see page 3-14.
For Compaq Tru64, see page 3-16
Step 3.1 HP-UX

We recommend that you ask your system administrator to modify the
yourself, follow the instructions below very carefully.
Note
If changes are made to kernel parameters, the Unix computer will have to
3-11
3.1.1
3.1.2
Type sam and press <Enter>.
3.1.3
Use the down arrow to select Kernel Configuration and press <Enter>.
3.1.4
Use the down arrow to select Configurable Parameters and press

<Enter> a list of parameters is displayed.
Table 3-6 lists the values that are recommended for installing with an
Oracle database server.
Table 3-6
Kernel Parameters HP-UX with Oracle (Part 1 of 2)
Parameter
Value
ksi_alloc_max
(NPROC*8)
Eight times the value specified for the NPROC
parameter.
maxdsiz
1073741824
maxdsiz_64bit
2147483648
maxssiz
134217728 bytes
maxssiz_64bit
1073741824
maxswapchunks
16384
max_thread_proc
512. This value is appropriate for a

CONTROL-M/EM installation with up to 50
CONTROL-M definitions, 80 ViewPoints and 30
concurrent users.
Note: If your datacenter is larger than this
configuration, contact BMC Technical Support for
the value for this parameter. For more information
about CONTROL-M definitions, and ViewPoints,
see the CONTROL-M/Enterprise Manager User
Guide.
maxuprc
((NPROC*9)/10)
msgmap
(MSGTQL+2)
msgmni
NPROC
msgseg
32767
msgtql
NPROC
3-12
Table 3-6
3.1.5
Kernel Parameters HP-UX with Oracle (Part 2 of 2)
Parameter
Value
ncallout
(NKTHREAD+16)
ncsize
((8*NPROC+2048)+VX_NCSIZE)
nfile
(15*NPROC+2048)
nflocks
4096
ninode
(8*NPROC+2048)
nkthread
(((NPROC*7)/4)+16)
nproc
4096
semmap
(SEMMNI+2)
semmni
4096
semmns
(SEMMNI*2)
semmnu
(NPROC - 4)
semvmx
32768
shmmax
Half the amount of RAM (in bytes) on this

computer. For information about determining the
amount of RAM on your computer, see Table 3-4 on
page 3-10.
shmmin
shmmni
512
shmseg
32
vps_ceiling
64
To change the value of a kernel parameter:

A:
Use the down arrow to move the cursor to the parameter.
B:
Press the spacebar to select the parameter.
C:
Press <Tab> to activate the menu bar.
D:
Press the right arrow until the Actions menu is selected.
E:
Use the down arrow to select the Modify Configurable Parameters

option, and press <Enter>
3-13
F:
Use the <Tab> key to go to the Formula/Value field and enter the
desired value. (If the default value is more than needed, do not
change it.)
G:
Use the <Tab> key to go to the [OK] button and press <Enter>
3.1.6
When you have finished modifying all relevant parameters, use the
<Tab> key to activate the menu bar.
3.1.7
Use the down arrow to select the Choose Process New Kernel option
using down arrow and press <Enter>. (This action will reboot the Unix
computer. It may take a few minutes.)
3.1.8
Define the Unix user account:
For CONTROL-M/EM, continue your installation preparation with

Step 4 on page 3-17.
For CONTROL-M/Server, continue your installation preparation

with Step 5 on page 3-19.
Step 3.2 Solaris

It is recommended that you ask your system administrator to modify the
yourself, follow the instructions provided below very carefully.
Note
3.2.1
3.2.2
Open the operating system configuration file /etc/system

Each line in the /etc/system file has the following format:
set shmsys:shminfo_<param_name>=<value>
3-14
For example, to set the shmmin parameter to 1:

set shmsys:shminfo_shmmin=1
3.2.3
If necessary, add/modify the parameters (as listed in Table 3-7).

Table 3-7
Kernel Parameters Solaris with Oracle
Parameter
Minimum Value
shmmax
4294967295
shmmin
shmmni
100
shmseg
10
semmns
Twice the total number of Oracle processes (minimum 1024).
semmni
100
semmsl
260
semopm
100
semvmx
32767
3.2.4
If you modified any of the system (kernel) parameters, reboot the

computer.
3.2.5
In the console window, run the xhost + command.
3.2.6
Define the Unix user account:
For CONTROL-M/EM, continue your installation preparation with

For CONTROL-M/Server, continue your installation preparation

with Step 5 on page 3-19.
3-15
Step 3.3 Compaq Tru64 (OSF1)

3.3.1
Verify that system (kernel) parameters match the requirements listed in

Table 3-8. It is recommended that you ask your system administrator to
modify the necessary system (kernel) parameters.
Note
Kernel configurations should be performed under the root user. If any of

the parameters are changed, the system must be rebooted for changes to
take effect.
Table 3-8
3.3.2
Kernel Parameters Compaq Tru64 with Oracle
Parameter
Recommended Value
FIFO_DO_ADAPTIVE
MAX_PER_PROC_STACK_SIZE
33554432
NEW_WIRE_METHOD
PER_PROC_STACK_SIZE
33554432
PER_PROC_DATA_SIZE
201326592
SHM_MAX
4278190080 (4 GB less 16MB)
SHM_MIN
1024
SHM_MNI
256
SHM_SEG
128
Continue your installation preparation with Step 5 on page 3-19.
3-16
Step 4 Create the CONTROL-M/EM

In this step, you will create the user account for the CONTROL-M/EM
administrator. If you are not familiar with how to do this, consult your
system administrator.
Notes:
The CONTROL-M/EM administrators account must include a home

directory with sufficient diskspace for installation of
CONTROL-M/EM components (described in Table 3-5 on page
3-10).
When installing CONTROL-M/EM on Unix with Oracle Server, the

administrators group name must be dba.
The initial program for the CONTROL-M/EM administrators user

account must be specified as /bin/csh, or /bin/ksh.
Perl is installed during CONTROL-M/EM installation. The location

of the Perl files is recorded in the .cshrc or .profile files.
For Solaris computers the Perl shared library path is recorded
using the using the LD_LIBRARY_PATH parameter.
For HP-UX computers the Perl shared library path is recorded
using the using the SHLIB_PATH parameter.
For AIX computers the Perl shared library path is recorded using
the using the LIBPATH parameter.
If you have another copy of Perl installed on your computer, you will
need to use the full path to access that copy.
3-17
Setting Limits for the CONTROL-M/EM User Account
Unix computers have predefined limits which ostensibly avoid excessive

use of resources by a process. When the process rises past the limit
specified, the Operating System may kill the process in a way that allows
for no clean up or diagnostics generation.
Unix default limits are also very small, and unexplained outages may
occur when the Operating System terminates a naturally growing
process. We recommend setting limits to higher values to avoid these
unexpected outages, which may be mistaken for an actual product failure.
The current limits in your machine can be checked by issuing the limit
command. (The limit command may be reserved for the Super User on
some Operating Systems installations.)
The limits that are affect CONTROL-M/EM processes are described in
Table 3-9, Limits for the CONTROL-M/EM User Account, on page
3-18.
Table 3-9
Limits for the CONTROL-M/EM User Account
Parameter
Description
datasize
The maximum size of the "data" segment of a process.

Maximum applicable values are
Solaris: 2GB
HP-UX: 4GB (using third and fourth quarter enabled)
AIX: 2GB
stacksize
The maximum size of the stack segment of a process. We

recommend 400 MB for all Unix types.
coredumpsize
The maximum size that a core dump can reach. We

recommend that this be set to be the same as the datasize,
so that a complete core dump can be generated if a failure
occurs. There must also be enough disk space available for
the complete core dump to be generated.
descriptors
The maximum number of descriptors in use by a single

process. Recommended value: 2000
Note: This parameter should not be set to unlimited.
memoryuse
The maximum amount of memory to be used by a single

process. We recommend that this be set to unlimited.
3-18
Step 5 Create the CONTROL-M/Server

In this step, you will create the user account for the
CONTROL-M/Server administrator. If you are not familiar with how to
do this, consult your system administrator.
Verify that:
The home directory of the CONTROL-M/Server administrators

account has sufficient diskspace to install CONTROL-M/Server
components (as described in Step 2.3 on page 3-7).
The administrators group name is controlm. If necessary, create a

new group.
If you are installing a dedicated Oracle Database server on the same
account, make sure that either the primary or secondary group for
this user is the dba group.
The HOME directory parameter for the CONTROL-M/Server

administrators account must contain the full path name of the
directory to be created for the CONTROL-M/Server administrator.
The specified HOME directory must be on a local disk. NFS and
other mount disk systems (for example, clusters) are not supported.
The initial program for the CONTROL-M/Server administrators

user account must be specified as /bin/csh, or /bin/tcsh.
3-19

Each installation procedure that is described in this book is followed by a
table that describes the parameters and prompts for that procedure. If this
is the first time that you are installing CONTROL-M, it is recommended
that you review the tables in the appropriate installation chapters. This
will help you gather whatever information is necessary before you run
the actual installation.
Step 7 Where to go from here

This completes the Preparation phase of CONTROL-M installation on a
Unix computer.
Before installing CONTROL-M components on a Microsoft

Windows computer, continue with Chapter 4, Pre-Installation Steps
on Microsoft Windows.
If you have completed all necessary preparation, continue with

Chapter 5, Installing an Oracle Database on Unix or Chapter 6,
Installing an Oracle Database on Microsoft Windows.
Note

3-20
Pre-Installation Steps on Microsoft

Windows
4
This chapter describes how to prepare for installation of CONTROL-M
components on Microsoft Windows computers.
Most scheduling environments combine CONTROL-M components on
Microsoft Windows and on Unix. Preparation procedures for Unix-based
components are provided in Chapter 2 and 3.
Note
If you are upgrading from a previous version of CONTROL-M, much of

this chapter will not require action. However, it is highly recommended
that you review it, before upgrading.
During upgrade, you can switch to a different database, modify database
sizes and many other parameters. For more information, see the
CONTROL-M Upgrade Guide.
Before you begin:
Review Chapter 1, Getting Started., and use that chapter to acquire the
following information:
A list of databases and CONTROL-M applications or components to

be installed on Microsoft Windows computers.
The appropriate installation CDs.
4-1

In this step you will verify that your computers meet the system
requirements for the CONTROL-M components you plan to install on
Microsoft Windows. Table 4-1 describes general system requirements for
CONTROL-M/Server and for CONTROL-M/EM components.
Table 4-1
Hardware
System Requirements for CONTROL-M Products (Part 1 of 4)

For CONTROL-M/EM Client:
Computer: Pentium IV 1 GHz or higher
Display: 16-bit (65536) colors or higher
RAM:
256 MB (minimum)
512 MB (recommended for up to 40,000 jobs)
1 GB (recommended for more than 40,000 jobs)
For CONTROL-M/EM Server Components or CONTROL-M/Server:
Computer: Pentium IV 1 GHz or higher
RAM: 512MB of real memory.
For CONTROL-M/Agent:
Computer: Pentium III 500 MHz or higher
RAM: 256 RAM
4-2
Table 4-1
Operating System
Software
How do I check
it?
Run the winver
command from the
Start=>Run dialog
box
For CONTROL-M/Agent:
Microsoft Windows 2000 Professional SP3 or SP4
Microsoft Windows XP Professional with no SP
Microsoft Windows XP Professional with SP1
Microsoft Windows 2000 Server with SP3 or SP4
Microsoft Windows 2000 Advanced Server SP3 or SP4
Microsoft Windows 2000 Datacenter SP3 or SP4
Microsoft Windows 2003 Standard
Microsoft Windows 2003 Enterprise
For CONTROL-M/Server
Microsoft Windows 2000 Advanced Server with SP3 or SP4
Microsoft Windows 2000 Datacenter with SP3 or SP4
Microsoft Windows 2003 Standard
Microsoft Windows 2003 Enterprise
Microsoft Windows 2003 Data Center
For CONTROL-M/EM Server Components:
For CONTROL-M/EM Client Components:
Microsoft Windows 2000 Professional with SP3 or SP4
Microsoft Windows XP Professional with SP1
Notes:
The above versions of Microsoft Windows also supported when enabled for
Japanese. However, Japanese characters are not supported in CONTROL-M
product windows.
Cluster machines are supported by CONTROL-M/Server and Agent when
they are installed on Microsoft Windows 2000 Advanced Server or Data
Center.
For CONTROL-M/Agent, Java Runtime Environment (JRE) version 1.3 or 1.4
should be installed. If Java is not installed, the GUI-based configuration utility
for CONTROL-M/Agent will not work. (However, the text-based version of this
utility will work even without Java).
4-3
Table 4-1
Software
For CONTROL-M/EM:
Internet Explorer version 5.5 or later
Open Database Connectivity (ODBC) version 3.52 or later.
How do I check my ODBC version?

Choose Start => Settings => Control Panel. Double-click the Administrative
Tools icon to display the Administrative Tools window. Double-click the Data
Sources (ODBC) icon to display the ODBC window. Click the About tab. The
ODBC version is displayed in the Version column.
Note: For cluster environments, during the CONTROL-M/Server installation,

the primary node is checked for the presence of the msvcp60.dll and
msvcrt.dll files. If these files do not exist (or the existing version is older), these
files are placed (or replaced) in the WinNT\System32 directory on the primary
node.
After the installation, you will need to copy these two files to other relevant
nodes in the cluster that do not have (or have an older version of) these files.
Memory
How do I check
It?
CONTROL-M/Server
128 MB
CONTROL-M/Agent
128 MB
CONTROL-M/EM Client installation
256 MB (minimum)
512 MB (recommended for up
to 40,000 jobs)
1 GB (recommended for more
than 40,000 jobs)
Open the
performance tab of
the windows task
manager to
determine available
physical and virtual
RAM.
4-4
Table 4-1
Diskspace
Disk space for

database
components is
described in Step
1.1 on page 4-6.
Environment
Variables
CONTROL-M/Server
20 MB
CONTROL-M/Agent
100 MB
CONTROL-M/EM Gateway
200 MB
CONTROL-M/EM GUI Server
100 MB
Global Conditions Server
200 MB
Global Alerts Server
50 MB
CONTROL-M/EM GU
50 MB
CONTROL-M/Desktop
50 MB
Administration Facility
50 MB
Reporting Facility
50 MB
Command Line Interface
50 MB
Orbix E2A
140 MB
A reference to the WINNT\System32 folder must be in the PATH environment

variable.
The TEMP environment variable must indicate a path that exists on your
computer.
How do I check It?

Choose Start => Settings => Control Panel => System, and click
Environment Variables in the Advanced tab.
Media Drive
CD-ROM drive
Communication
Adapter
Network connection for TCP/IP
Language
Settings
When working with non-English versions of Microsoft Windows, set the system
locale and language settings to English before installing CONTROL-M/EM:
1. Select "Western Europe and United States" in Control Panel => Regional
Options => Language settings for the system to receive all messages in
English.
2. Select English(US) in Control Panel => Regional Options => Your locale
(location) to set the locale to english.
After installation you can reconfigure your computer for work with a non-English
language. For more information, see Appendix J, Language Configuration.
4-5
Step 1.1 Database Requirements

A database must be installed as part of each CONTROL-M/Server and
CONTROL-M/EM installation.
The following table lists the disk space required for dedicated installation
of supported database servers, and for the new database.
Database Server
Server Disk Space
Database Disk
Space
Oracle Server
Enterprise Edition
Version 9.2.0.1
Note: Oracle Server
Standard Edition cannot
be used.
2.7 GB, on NTFS disk

(Oracle not supported
for CONTROL-M/Server
on Windows)
for CONTROL-M/EM:
Small: 520MB
Medium: 1.1 GB
Large: 1.9 GB
The following table lists the disk space required for the new database or
schema on the existing database server, and for the database client on the
local computer.
Database/Schema
Disk Space
Database Client
Disk Space
Sybase Adaptive Server

Version 12.0.0.7
Client Version 12.0.0.0
for CONTROL-M/EM:
120 MB
(Sybase not supported
for CONTROL-M/Server
on Windows)
200 MB
MSSQL Server 2000 with

SP3 or SP3a
MSDE 2000 with SP3 or
SP3a
for CONTROL-M:
Default: 100 MB
for CONTROL-M/EM:
Default: 100 MB
25 MB
Oracle Server
Enterprise Edition
Version 8.1.7, 9.0.1, or
9.2.0
Note: Oracle Server
Workgroup Edition
cannot be used.
for CONTROL-M/EM:
Small: 70 MB
Medium: 350 MB
Large: 700 MB
(Oracle not supported for
CONTROL-M/Server on
Windows)
630 MB
Database Server
4-6
Step 2 Verify Installation Privileges

The user installing CONTROL-M components on a specific computer
running Microsoft Windows must have Administrator privileges for that
computer.
If you are installing CONTROL-M components from a CD-ROM drive
that is located on a remote computer, ensure that you have the necessary
privileges to access the media on the remote computer.

The parameters for each installation procedure are described in a table at
the end of the chapter that describes that procedure. If this is the first
time that you are installing CONTROL-M, it is recommended that you
review the relevant tables. This will help you gather whatever
information is necessary before you run the actual installation.
4-7
Step 4 Where to go From Here

This completes the preparation phase for CONTROL-M/EM or
CONTROL-M/Server installation on a Microsoft Windows computer.
For a new 6.1.03 installation with Oracle, continue with Chapter 5,

Installing an Oracle Database on Unix., or Chapter 6, Installing an
Oracle Database on Microsoft Windows..
For installation of CONTROL-M/EM on Microsoft Windows using

MSSQL or Sybase, continue with Chapter 8, Installing
CONTROL-M/EM for Microsoft Windows.
For installation of CONTROL-M/Server on Microsoft Windows,

continue with Chapter 10, Installing CONTROL-M/Server for
Microsoft Windows, or Chapter 11, Silent Installation of
CONTROL-M/Server for Microsoft Windows.
If your scheduling environment will contain Unix-based

CONTROL-M components, continue with Chapter 2 or 3 (depending
on your database type).
If you are upgrading from an earlier version of CONTROL-M/EM or

CONTROL-M/Server, continue with the appropriate chapters in the
If you have completed all pre-installation steps, continue with the

relevant CONTROL-M installation procedures later in this book.
4-8
Installing an Oracle Database on Unix5

This chapter describes how to install an Oracle database on Unix for use
with CONTROL-M/Server or with CONTROL-M/EM. Table 5-1
describes the various ways to install CONTROL-M with an Oracle
Database server.
Table 5-1
Oracle Database Installation Types
Installation Type
Description
Dedicated
Installs full Oracle Server software, initiates an

instance, and then places the CONTROL-M
database schema in it.
A dedicated Oracle database can be installed using
either of the following installation options:
Default Uses default values for all database
parameters.
Custom Allows customization of database
parameters during installation.
For more information about these parameters and
their default values, see Table 5-2 on page 5-11.
(Default or
Custom)
Existing
Installs only the Oracle client software, connects to

an existing Oracle database instance, and places
the CONTROL-M database schema in it.
Client Only
Installs only the Oracle client software.

This installation type can be performed only after
the schema for the CONTROL-M/EM database has
been defined in the Oracle Database server.
5-1
Before you Begin

Summary:
Ensure that all necessary pre-installation procedures have been

performed. For more information, see Chapter 2 or 3 (depending on your
database type).
If you will be installing Oracle Client software that will place a
CONTROL-M database schema in an existing Oracle instance, verify
that you have the correct host, port, path name, and password information
for the existing Oracle instance. The administrator of the existing Oracle
instance must have Read/Write access to the target directory for the
CONTROL-M database schema.
Note
To implement a CONTROL-M/Server database on existing Oracle

database instance, the target computer for CONTROL-M/Server
installation and the host computer of the Oracle Database server must
have the same date setting.
5-2
Prepare Installation Files

Summary:
Use the method described below to copy the Oracle CDs to a location
that is accessible to the CONTROL-M/EM or CONTROL-M/Server
account.
(For COMPAQ Tru64 version 5.1b, the Oracle CDs must be copied to a
location on the same computer as where the Oracle software will be
installed.)
Note
In addition to the space that is required for Oracle installation (as

described in Chapter 3, Pre-Installation Steps for Unix with an Oracle
Database):
* For Solaris computers, the destination file system must have 2.8 GB of
available disk space.
* For all other platforms, the destination file system must have 3.5 GB of
Step 1
Select the Oracle CDs for 32-bit or 64-bit systems, as appropriate.
For Solaris, there are 4 CDs.

For HP-UX, AIX, or COMPAQ Tru64, there are 5 CDs.
Step 2
Insert the first Oracle CD in the CD-ROM drive.
Step 3
Mount the CD-ROM drive. For details about the mount procedure for
your Unix platform, see Appendix A, Mounting CDs on Unix
Computers.
Note
The CD mount procedure is handled automatically by the Solaris

operating system.
5-3
Step 4
Use the following command to create a temporary directory:

Note
The CONTROL-M user must have read access to this directory.
mkdir <ora_inst_dir>
For all subsequent steps, <ora_inst_dir> refers to this directory you have
created.
Step 5
Use the following command to copy the contents of each Oracle CD to

the temporary directory:
cp -R <CD_path>/* <ora_inst_dir>
Where <CD_path> is the directory on which you mounted the

installation CD.
Step 6
Unmount the last Oracle CD and insert the CONTROL-M Oracle

installation Package (FD5380) in the CD-ROM drive. Mount the
CD-ROM drive.
Where to go from here
Continue with Run the Oracle Pre-Installation Script on page 5-5.
5-4
Run the Oracle Pre-Installation Script

Summary:
In this task, you will run the Oracle pre-installation script. This script
check prerequisites for Oracle installation and determines certain system
settings and defaults for the database to be installed.
Step 1
Ensure that you are still logged in as the root user.
Step 2
Navigate to the CONTROL-M/EM or CONTROL-M/Server user home

directory.
Step 3
Specify the <CD_path>/orapreinst.sh command:

Where <CD_path> is the directory on which you mounted the
installation CD.
Note
The orapreinst.sh script is located on the CONTROL-M Oracle

Installation Package for Unix CD (FD5380), not in the files copied from
the Oracle CDs.
Step 4
Select the CONTROL-M product for which you are creating a database.
This is the product you selected in Step 2. This selection determines the
default settings that will be used to create the database.
Step 5
A message similar to the following is displayed:

Enter the Oracle configuration file path and name
(default: /<CD_path>/<config_path>):
Where <config_path> is:
ora_defs_controlm for a CONTROL-M/Server database

ora_defs_ctmem for a CONTROL-M/EM database.
Press <Enter> to accept the default file path and name.

Step 6
The following messages are displayed:

Saving current Oracle products configuration.
5-5
Enter the oracle installation directory (default:

/<install_dir>) :
Where <install_dir> is the user directory you created on the local
computer for CONTROL-M/Server or CONTROL-M/EM installation.
Press <Enter> to install Oracle in the default directory, or enter a
different directory path.
Step 7
Indicate if you are installing a database client (C) or server (S).
Step 8

Done.
Creating Oracle Inventory pointer file
(/var/opt/oracle/oraInst.loc)
orapreinst.sh execution ended successfully.
On AIX systems, the path shown is /etc/oraInst.loc.
Step 9
Log out.
Where to go From Here
Continue with the next task Run the Installation Script on page 5-7.
5-6
Run the Installation Script

Step 1
Log in to the CONTROL-M product user account created during

pre-installation preparations (see Chapter 3, Pre-Installation Steps for
Unix with an Oracle Database).
Step 2
Use the following command to set the display environment to display

graphics:
where <hostname> is the name (or the IP address) of the computer from
which the installation is being performed.
It is recommended to run a small application (such as xclock) at this time
to ensure that the specified display settings are working.
Step 3
Navigate to the directory on which the CD-ROM drive is mounted.
Step 4
Use the following command to run the installation script from the Oracle
installation package CD:
inst_oracle
Step 5
Follow the prompts to complete the installation.

The parameters and fields for this installation are described in Table 5-2
(on page 5-11).
Note
Even if you do not modify any other parameters, you must enter the
directory path to the Oracle installation files.
Step 6
When you are satisfied with the values of the database parameters,
specify option b (from any page in the parameters menu) to build the
oracle database.
5-7
If you are installing a new, dedicated Oracle database server, messages

similar to the following are displayed:
############################################
############################################
INSTALLING <product> DATABASE SERVER
############################################
############################################
Starting Oracle Server software installation. This may take a while ...
Oracle Server Software installation in progress. 99 percent already completed
################################################
Installation of Oracle SERVER Ended successfully
################################################
On some systems, these messages are followed by LISTENER

configuration messages.
Step 7
The following messages are displayed during database creation:

############################################
############################################
INSTALLING <product> DATABASE
############################################
############################################
Starting Database creation. This may take a while ...
Oracle Database Creation in progress. 99 percent already completed
################################################
Installation of Oracle Database Ended successfully
################################################
5-8
Step 8
The following messages are displayed during installation of the 9.2.0.4

patch for the Oracle Database server:
Database objects creation ended.
Starting to apply Oracle patch 9.2.0.4
The installation of Oracle Universal Installer was successful.
Starting Oracle 9.2.0.4 software installation. This may take a while ...
Oracle 9.2.0.4 Software installation in progress. 90 percent already
completed .
The installation of Oracle9iR2 Server PatchSet was successful.
Starting Database migration. This may take a while ...
Oracle database migration in progress. 99 percent already completed ...
############################################
Installation of Oracle 9.2.0.4 patch Ended successfully
############################################
Note
The messages shown above, are displayed for a custom or default

installation. Different messages may be displayed for Existing and Client
installations.
Where to go From Here
Continue with the next task Run the Oracle Post-Installation Script on
page 5-10.
5-9
Run the Oracle Post-Installation Script

Summary:
The following procedure removes the temporary directories and files

created by Oracle database server setup.
Step 1
Log on as the root user.
Step 2
Navigate to the home directory of the CONTROL-M product user

account.
Note
The orapostinst script is located on the CONTROL-M Oracle

Installation Package CD, not in the files copied from the Oracle CDs.
Step 3
Enter the following command.

<CD_path>/orapostinst.sh
Where <CD_path> is the mounted location of the CONTROL-M Oracle
Installation Package.
Step 4
If necessary, confirm the removal of files.
Step 5
Log off.
Where to Go From Here
If you require additional Oracle databases on Unix for other

CONTROL-M products, return to the beginning of this chapter, and
repeat the installation procedure for your other databases.
If you have completed installation of all databases for CONTROL-M

products, continue the installation process with the appropriate
chapters later in this book.
If you are performing an upgrade of CONTROL-M/Server for Unix,

continue with Chapter 9, Installing CONTROL-M/Server for Unix.
5-10
Table 5-2
Oracle Database Unix Installation Parameters (Part 1 of 6)
Parameter or
Prompt
Description
Installation Type
Indicates which software installed with which configuration.

For more information, see Table 5-1 on page 5-1.
Oracle temporary
components were detected.
In order to continue with
installation, they should be
deleted.
Do you wish to delete these
components? [y/n]
The orapreinst.sh script finds and removes any temporary files

from earlier Oracle installations, and creates a tmp directory for the
current Oracle installation.
This message is issued if temporary Oracle files were found:
Enter the Oracle for

<unix_type> Installation files
path:
<unix_type> is the operating system of the computer.
Database Size (menu)
You must enter y to continue the installation.
Specify the full path name you used to copy the first Oracle CD to
the local drive: <ora_inst_dir>/Disk1
Enter the size (S, M, or L) for the database and press <Enter>.
Note: During upgrade installations, an additional item appears on
this menu, select the upgrade option, and the Oracle installation
procedure will detect the existing databases configuration file, and
use this file to configure the new database.
More information about these database sizes is provided below:
Database Element
Small
(Minimum)
Medium
Large
System Tablespace
200
250
300
RBS Tablespace
100
200
300
Temporary Tablespace
50
100
200
Data Tablespace
150
250
500
Index Tablespace
50
100
200
Redo Log Files (2)
50 (x2)
100 (x2)
200 (x2)
Total Database Size

(in MB)
650
1100
1900
5-11
Table 5-2
Parameter or
Prompt
Description
Database instance name
Instance name of the database.

CONTROL-M/EM default: em613
CONTROL-M/Server default: controlm
Notes:
The database instance name should not exceed 8 characters.
The database instance name cannot begin with a numeral.
For installation using an existing Oracle Database server, this
parameter indicates the instance name of the existing database.
Get this value from the DBA.
For "Client Only" installations, this parameter must indicate the
name of the existing database instance.
Oracle Server host name
For installations that use an existing Oracle Database server,

Name or IP address of the computer on which the existing Oracle
instance is located.
Database user
Name of the database user to be created. This is the user used to

log on to the CONTROL-M product.
CONTROL-M/EM default: emuser.
Notes:
The CONTROL-M/EM database user name should not exceed 8
characters.
For "Client Only" installations, this parameter indicates the name
of the existing database user (that is used to log on to the
CONTROL-M product).
User password
Password for the database user (6 to 30 characters, alphanumeric).

The characters are not displayed for security reasons.
CONTROL-M/EM default: empass.
CONTROL-M/Server default: password
Note: This password can be changed at a later time. For more
information, see, Maintaining CONTROL-M/EM, in the
CONTROL-M/Enterprise Manager Administrator Guide.
ORACLE home directory
Directory in which the Oracle Server files are installed.

Default: $HOME/oracle
5-12
Table 5-2
Parameter or
Prompt
Data tablespace name
Description
Name of the data tablespace that will be created on the existing
Oracle database instance. This tablespace will contain the database
data.
CONTROL-M/Server default: ctrlm
Note: This parameter is displayed only for installations that use an
existing Oracle Database server.
Data tablespace size
The default size of the data tablespace depends on the size of the
database chosen.
See Database Size (earlier in this table).
Data tablespace file name
The default path to the data tablespace file is based on the

database instance name.
CONTROL-M/EM default:
$HOME/oracle/oradata/em613/em613data01.dbf
CONTROL-M/Server default:
$HOME/oracle/oradata/ctrlm/ctrlmdata01.dbf
For installation using a existing Oracle Database server:
This parameter indicates the full path and filename for the Data file
of the database.
The specified path must be an existing path for which the
administrator of the existing Oracle instance has READ and
WRITE permission.
The filename must not be the name of an existing file. This file will
be created during installation of the database.
index tablespace size
The default size of the index tablespace depends on the size of the
database chosen.
See Database Size (earlier in this table).
5-13
Table 5-2
Parameter or
Prompt
index tablespace file name
Description
The default path for the file is based on the database instance
name. For example:
When the instance name is em613, the default path is:
$HOME/oracle/oradata/em613/em613indx01.dbf
When the instance name is ctrlm, the default path is:
$HOME/oracle/oradata/ctrlm/ctrlmindx01.dbf
For installation using a existing Oracle Database server:
This parameter indicates the full path and filename for the Index file
of the database.
The specified path must be an existing path for which the
administrator of the existing Oracle instance has READ and
WRITE permission.
The filename must not be the name of an existing file. This file will
be created during installation of the database.
Examples for Unix:
<ctmem_home>/oracle/oradata/em_inx.dbf
<database_server_home>/oracle/oradata/em_inx.dbf
Note: The path to the database files may differ at your site,
depending on where your Oracle database server is installed.
Database redo log file size (2

files)
Each Oracle database has two redo log files. These files are used
to record all committed changes that are applied to the database, so
that this information is available in case of a media failure.
The default log file size depends on the size of the database
chosen. See Database Size (earlier in this table).
Database redo log01 file

name (full path)
The default path to the first database redo log file is based on the
database instance name. For example:
$HOME/oracle/oradata/em613/log01.dbf
$HOME/oracle/oradata/ctrlm/log01.dbf
Database redo log02 file

name (full path)
The default path to the second database redo log file is based on
the database instance name. For example:
$HOME/oracle/oradata/em613/log02.dbf
$HOME/oracle/oradata/ctrlm/log02.dbf
5-14
Table 5-2
Parameter or
Prompt
Description
Oracle SYSTEM password
Password for the Oracle SYSTEM account.

Length: Between 6 and 30 characters.
Default: manager.
Note: For installation using an existing Oracle Database server, this
parameter indicates the Password for the Oracle superuser that
manages the existing Oracle instance.
Database system tablespace

size
The default size of the system tablespace depends on the size of

the database chosen. See Database Size (earlier in this table).

file name
The default path to the system tablespace file is based on the

$HOME/oracle/oradata/em613/system01.dbf
$HOME/oracle/oradata/ctrlm/system01.dbf
Database rollback segments

tablespace size
The default size of the RBS tablespace depends on the size of the
database chosen. See Database Size (earlier in this table).
Database rollback segments

tablespace file name (full
path)
The default path to the rollback segments tablespace file is based

on the database instance name. For example:
$HOME/oracle/oradata/em613/rbs01.dbf
$HOME/oracle/oradata/ctrlm/rbs01.dbf
Database temporary
tablespace file size
The default size of the temporary tablespace depends on the size of

the database chosen. See Database Size (earlier in this table).
5-15
Table 5-2
Parameter or
Prompt
Description
Database temporary
tablespace file name (full
path)
The default path to the temporary tablespace file is based on the

$HOME/oracle/oradata/em613/temp01.dbf
$HOME/oracle/oradata/ctrlm/temp01.dbf
Oracle LISTENER port

number
Communications port used by the Oracle Database server to

communicate with Oracle Database.
Default: 1521.
How do I find an available port?
If TCP/IP protocol is installed, the following command checks if a
specific port is available:
netstat -na | grep .<portnumber>
where <portnumber> is the number of the desired port. If this
command returns no result, the port is available.
Note: If your installation is using an existing Oracle database, get
the appropriate port number from your database administrator
(DBA).
5-16
Installing an Oracle Database on

Microsoft Windows
This chapter describes how to install an Oracle database on Microsoft

Windows for use with CONTROL-M/EM. Table 6-1 describes the
different ways that CONTROL-M/EM can be installed with an Oracle
Database.
Table 6-1
Oracle Installation Types
Dedicated Server
Installs full Oracle Server software and initiates an

instance, then places the CONTROL-M database
schema in it.
This procedure is described in this chapter.
Two types of dedicated installation are available:
Without customization Uses default values
for all Oracle Database parameters.
With customization Select this installation
type if you want to be able to modify Oracle
Database parameters.
6-1
Table 6-1
Oracle Installation Types
Installation on
Existing Server
Installs only the Oracle client software and places

the CONTROL-M database schema in an existing
Oracle database instance in your environment.
This procedure is described in this chapter.
Note: To use an existing database server, verify
that the existing Oracle server has the full
Enterprise Edition software installed, including
support for the partition option. Oracle Standard
Edition servers cannot be used for CONTROL-M
databases.
Oracle Client
6-2

This installation type can be performed only after
the schema for the CONTROL-M/EM database has
been defined in the Oracle Database server.
Oracle Database Installation

Summary:
Use the following steps to install an Oracle Database server or client for
use with CONTROL-M/EM.
Before you Begin
Ensure that all pre-installation procedures have been performed. These

procedures are described in Chapter 4, Pre-Installation Steps on
Microsoft Windows.
If you will be installing a new Oracle database on an existing database
server, verify that you have the correct host, port, path name, and
password information for the existing database server.
Copy the Oracle Installation Files
Installation files for Oracle on Microsoft Windows are provided on three

CDs (FD5463). Before installing the Oracle Database server, you will
need to copy the contents of these CDs to a location that can be accessed
by your computer.
Note
For installation of a only an Oracle client, or using an existing Database

Server, use the FD5382 CD for a quicker installation process (on a single
CD.
Step 1
Create a temporary directory.
Step 2
Copy the three FD5463 CDs to separate directories called Disk1, Disk2,
and Disk3 under the temporary directory that was created in Step 1.
(You must use these specific names in order for the installation to work
correctly.)
6-3
Running the Installation Script

Step 1
Stop all applications on the current computer. This will free resources for
the Oracle installation procedure.
Step 2
Insert the CONTROL-M Oracle Installation Package for Microsoft

Windows (FD5381 or FD5382) in the CD-ROM drive.
Step 3
If Autorun is enabled on your computer, the installation procedure

runs automatically after you insert the CD.
If Autorun is not enabled, browse to the

OracleInstallationFiles\executables\OracleInstallationDriver
directory on the CD and run the Setup.exe file.

(on page 6-5).
Note
Two items are added to the Start => Programs menu:

* Oracle-<Oracle_Home>, which references the database schema
installed at <Oracle_Home>.
* Oracle Installation Products, a set of Oracle utilities. This is added
only if it did not exist on the computer.
If your installation plan includes CONTROL-M components on

Unix, perform the relevant preparation steps in Chapter 3,
Pre-Installation Steps for Unix with an Oracle Database..
If this was the first installation of an Oracle database, and you will
need other Oracle databases for other CONTROL-M products, return
to the beginning of this chapter, and repeat the installation procedure
for your other databases.
6-4
Table 6-2
If you have completed installation of all the necessary Oracle

databases for CONTROL-M products, continue the installation
process with the appropriate chapters later in this book.
Oracle Database Microsoft Windows Installation Parameters (Part 1 of 4)
Parameter
Description
Upgrade
Parameter Path
If the OracleUpgradeParams.txt file is on the target drive, an upgrade installation

is assumed and the path to this file is displayed. This file contains parameter
settings that will be carried over to the new database during upgrade.
It is recommended not to change the path displayed in this window.
Destination
Directory in which the Oracle components will be installed.

Default: <OS_install_drive>:\Oracle
Note: The specified directory name must not include blanks.
Oracle
installation
Type
Dedicated server
(without
customization)
Uses default values for all Oracle Database parameters.
Dedicated server
(with
customization)
Select this installation type if you want to be able to modify

Oracle Database parameters.
Installation on
Existing Server
Installs a new tablespace for CONTROL-M/Server or

CONTROL-M/EM using an existing (already installed) Oracle
Database server.
Oracle Client

This installation type can be performed only after the schema
for the CONTROL-M/EM database has been defined in the
Oracle Database server.
Instance Name
Name of the database instance for the CONTROL-M/EM Database. The length of
this name cannot exceed eight characters. Default: EM613.
How do I find this value?
1. Search for the listener.ora file in the following locations:
<home_dir>\Oracle\Ora920\network\ADMIN\ (on Windows)
<home_dir>/oracle/product/9.2.0/network/admin/ (on Unix)
where home_dir is the directory in which the Oracle server is installed.
2. In this file, the value of the SID_NAME parameter, is the instance name.
If the SID_NAME parameter appears more than once in the listener.ora file,
consult your Oracle database administrator to determine which name you
should use.
Notes
Use only 8 alpha-numeric characters
The first character must be a letter, not a number
6-5
Table 6-2
Parameter
Description
Database
Server Host
Name
Host name of the computer on which the Oracle Database server is installed.
This parameter is required only when installing a new database using an already
installed (existing) Oracle Database server.
Note: The value for this parameter is in the HOST parameter in the listener.ora
file on the server computer. If you cannot find the listener.ora file, or if a
parameter appears more than once in the file, consult your Oracle database
administrator to determine which value you should use.
For more information about how to locate the listener.ora file, see the Instance
Name parameter (above).
Oracle Server
TCP/IP Port
Number
Port number Default: 1521. Contact your System Administrator to verify the correct
value.
Note: The value for this parameter is in the PORT parameter in the listener.ora
file on the server computer. If you cannot find the listener.ora file, or if a
parameter appears more than once in the file, consult your Oracle database
administrator to determine which value you should use.
For more information about how to locate the listener.ora file, see the Instance
Name parameter (above).
Tablespace
Size
The size specification for the CONTROL-M/EM database. Choose small,

medium, or large.
Database User
Properties
Username
Name of the CONTROL-M/EM Database User. Normally, this

is also the name of the CONTROL-M/EM Administrator. The
Administrator is the default user when logging on to
CONTROL-M/EM GUI for the first time. Enter the name of the
database user that was defined when the CONTROL-M/EM
Oracle tablespace was created.
Default: emuser.
Maximum length is 8 alphanumeric characters.
The value must begin with a letter (not a number).
No spaces or special characters are allowed.
Note: When installing a new tablespace using an existing
Oracle Database server, the database user name specified in
this window must be unique (not the same as any existing
user name for the Oracle database server).
Password
Password for the CONTROL-M/EM Database Owner.

Enter the password of the CONTROL-M/EM Database owner
that was defined when the CONTROL-M/EM Oracle
tablespace was created.
Minimum length is 6 alphanumeric characters, maximum
30 characters.
The value must begin with a letter (not a number).
Default: empass
6-6
Table 6-2
Parameter
Description
Database
Server
Properties
Username
Default value SYSTEM is displayed. This value cannot be

modified for installation of a dedicated database server.
Password
Password of the Oracle Server Administrator.

Default: MANAGER
Data File
Component
Name
Data Files Component Tablespace Name.

Default: <instance_name>_EM_USERS
Note: For installation using an existing Oracle Database
server, the tablespace name must be new and unique for the
current database installation.
Location
Path for the Data Files component.

Default: D:\Oracle\oradata\<instance_name>\data01.dbf
server, the tablespace location must be new and unique for
the current database installation, and the path must exist on
the computer where the database server is installed.
Size
Size for the Data Files component.

Defaults: 50, 250, or 500 depending on the selected
database size.
Name
Index Files Component Tablespace Name.

Default: <instance_name>_EM_INDEX
server, the tablespace name must be new and unique for the
current database installation.
Location
Path for the Index Files component.

Default: D:\Oracle\oradata\<instance_name>\index01.dbf
server, the tablespace location must be new and unique for
the current database installation, and the path must exist.
Size
The size for the Index Files component

Default: 20, 100, or 200 depending on the selected
database size.
Location
System (Component) Tablespace Location

(Default: D:\Oracle\oradata\<instance_name>\system.dbf).
Size
System (Component) Tablespace Size.

database size.
Index
Component
System
Component
6-7
Table 6-2
Parameter
Description
Redo Log Files
#1 Location
Path for the first redo log file

Default: D:\Oracle\oradata\<instance_name>\redo01.dbf
#2 Location
Path for the second redo log file

Default: D:\Oracle\oradata\<instance_name>\redo02.dbf
Size
The size for each redo log file.

Defaults: 50, 100, or 200 depending on the selected
database size
Location
Path for the Rollback Tablespace.

Default: D:\Oracle\oradata\<instance_name>\rbs01.dbf
Size
Size for the for the Rollback Tablespace.

database size.
Location
Path for the Temporary Tablespace

Default:
D:\Ecsnt\Oracle\oradata\<instance_name>\temp01.dbf
Size
Size for the for the Temporary Tablespace.

database size
Rollback
Component
Temporary
Component
6-8
Installing CONTROL-M/EM on Unix 7

This chapter describes installation of CONTROL-M/EM on a Unix
computer.
CONTROL-M/EM consists of:
Basic client components are usually installed on all Microsoft

Windows computers in the environment.
Databases and other server components are only installed on a few

computers in the environment.
Use the procedures described in this chapter to install the

CONTROL-M/EM server components on Unix. For how to install the
client components, see Chapter 8, Installing CONTROL-M/EM for
Microsoft Windows.
Note
The procedure in this chapter can also be used to Add or Remove

CONTROL-M/EM components on the local computer. (This procedure
cannot be used to Add or Remove components on a remote computer.)
For more information about specific CONTROL-M/EM components, see
Appendix B, CONTROL-M/EM Components.
7-1
Preparing for Installation

Summary:
Use the following steps to ensure that you are ready for installation of
CONTROL-M/EM on Unix.
Step 1
Ensure that all pre-installation procedures have been performed. (See

Chapter 2 or 3 depending on your database type.)
Step 2
You can install a Sybase database server as part of this installation, or use
an existing Sybase database server.
If you wish to use an Oracle database server for the CONTROL-M/EM
database, you must first install the database as described in Chapter 4 or
5.
Note
If you are upgrading from an earlier version of CONTROL-M/EM, see

the CONTROL-M upgrade guide for instructions on how to do this.
Continue with the next task: Mount the Installation Media on page 7-3.
7-2
Mount the Installation Media

Summary:
For details of the CD mount procedure on your Unix platform, see

Appendix A, Mounting CDs on Unix Computers.
Step 1
Step 2
Mount the CONTROL-M/EM installation CD for your Unix system into

the CD-ROM drive.
Step 3
If you are installing CONTROL-M/EM using an Oracle database, or

an existing Sybase database, continue with Run the Installation
Script on page 7-5.
If you are installing CONTROL-M/EM with a new Sybase database

on a computer with a single CD-ROM drive, continue with Step 3.
If you are installing CONTROL-M/EM with a new Sybase database

on a computer with two CD-ROM drives, mount the Sybase CD for
your platform in the second CD-ROM drive, and then continue with
the next task: Run the Installation Script on page 7-5.
To install CONTROL-M/EM with a Sybase database on a computer with

a single CD-ROM drive:
3.A
Log out of the root user account.
3.B
Log in as any other user (not the root user).
3.C
Use the following command to create a temporary directory that

is not under the CONTROL-M/EM user home directory:
mkdir <install_dir>
While it is important that this temporary directory be created in
a location that is not under the CONTROL-M/EM user home
directory, the CONTROL-M/EM user must have read access to
this directory.
7-3
Grant Read and Execute authorizations to the directory you

created. This is a sample command:
3.D
chmod 655 <install_dir>

For all subsequent steps, <install_dir> refers to this directory.
The destination file system must have at least 650 MB of
Use the following command to copy the contents of the
CONTROL-M/EM installation CD to the temporary directory:
3.E
<CD_path>/copy_from_cd <CD_path> <install_dir>

3.F
Unmount the CONTROL-M/EM Installation CD.
3.G
Remove the CONTROL-M/EM CD and insert the Sybase CD for

your Unix platform in the CD-ROM drive.
For more information about the Sybase CDs for various
configurations, see Choosing the Installation CDs on page
1-8.
3.H
Mount the Sybase CD.
3.I
Log out.
3.J
Log in to the CONTROL-M/EM user account.
Continue with the next task: Run the Installation Script on page 7-5.
7-4
Run the Installation Script

Summary:
Use the following steps to install CONTROL-M/EM Server Components.
Step 1
If you are installing with an Oracle database, use the following command
on the computer hosting the database server to verify that the Oracle
Server is running:
ps -ef | grep ora_ | grep <oracle_user_account>
If the Oracle server is running, a list of Oracle processes is displayed.

If you are installing using an existing Sybase database server, use the
following command on the computer hosting the database server to
verify that the database server is running:
ps -ef | grep syb | grep <sybase_user_account> | grep
-v "grep"
Step 2
Log on to the CONTROL-M/EM user account.
Step 3
Use the following command to run the installation script:

<install_dir>/INSTALL/LOAD
When installing with Sybase using only one CD-ROM drive,

<install_dir> is the directory to which you copied the installation
CD.
When installing with Oracle, or with Sybase using two CD-ROM

drives, <install_dir> is the directory on which the installation CD is
mounted.
7-5
Note
If there is a problem configuring the Orbix Server, a message is displayed

informing you of the problem. When the installation is complete, you
must configure Orbix Server by running the configure script. For more
information, see Configure the Orbix Server on page 16-3. (Run the
configure script only if the installation notifies you of a problem.)
Step 4

(on page 7-8).
Step 5
One of the following messages is displayed after installation is complete:

For csh Users
*********ATTENTION*********************************
To start working with the CONTROL-M/EM immediately,
you must execute:
source <em_home_dir>/.cshrc
*********************************************
For sh Users
*********ATTENTION*********************************
To start working with the CONTROL-M/EM immediately,
you must execute:
<em_home_dir>/.profile
*********************************************
If you want to use CONTROL-M/EM immediately, run the script

specified in this message, where <em_home_dir> is the home directory
of the CONTROL-M/EM user account.
If you log out of the CONTROL-M/EM user account and then log back
into this account, this script will not be necessary.
7-6
A list of parameters (called Installation_Parameters.txt) is created by

the installation procedure in the $HOME/site/ directory of the
CONTROL-M/EM user. This file should be printed and used to ensure
compatible specifications during CONTROL-M/EM client components
installation, or during installation of other CONTROL-M/EM server
components.
Note
The CONTROL-M/EM database password is not included in this log file.

If you do not know the database password, get it from your Database
administrator.
Step 6
Unmount the CONTROL-M/EM CD and remove it from the CD-ROM

drive.
If you have not yet installed CONTROL-M/EM client components,

do so using the procedure described in Chapter 8, Installing
CONTROL-M/EM for Microsoft Windows.
If you plan to install other CONTROL-M products in your

scheduling solution, continue with the installation procedure in the
appropriate chapter of this book.
If you have now completed installation of all CONTROL-M products

in your solution, proceed to the configuration chapter in Chapter 15,
Post-Installation Configuration.
7-7
Table 7-1
CONTROL-M/EM Unix Installation Parameters (Part 1 of 5)
Parameter or
Prompt
Description
Please enter the

Oracle
CONTROL-M/EM
user password
Enter the password you specified for the CONTROL-M/EM database during
Oracle installation.
Do you want an
automatic full
default
installation? (y/n)
Enter n to begin any of the custom installation procedures.

Enter y to perform a non-interactive installation procedure that installs
CONTROL-M/EM locally with default settings.
Did you perform

smitty aio? (y/n):
This message is displayed if you are installing CONTROL-M/EM using a

Sybase database server on an AIX computer.
Note: This refers to activation of the RS/6000 Asynchronous I/O option
(performed as part of the pre-installation steps). Verify that you have
performed this step, and then type y and press <Enter> to continue the
installation.
Do you want to
install the Orbix
Server on this
machine?
(y/n):(default y)
The Orbix Server is a set of processes that handle communication between

CONTROL-M/EM components.
If you answer y (yes), you are prompted for the Orbix Locator port number,
and the and Orbix node daemon port.
The default port for the locator is 3075.
The default port for the node daemon is 3079.
If you answer n (no), an Orbix client is installed and you are prompted for
the hostname and Orbix port number of the Orbix Server host computer.
Do you want to
install the GUI
Server and the
GAS on this
machine?
(y/n):(default y)
Type y and press <Enter> to install the CONTROL-M/EM GUI Server and the
Global Alert Server (GAS) on the current computer.
Do you want to
install the Gateway
on this computer?
(y/n):(default y)
Type y and press <Enter> to install the CONTROL-M/EM Gateway on the

current computer.
Note: The GUI Server handles information that must be passed to each online
user of CONTROL-M/EM. This is not the same as the CONTROL-M/EM GUI
component, which can be installed only on a computer running Microsoft
Windows.
Note: The CONTROL-M/EM Gateway is the component that handles

communication between the CONTROL-M/EM database, and one or more
CONTROL-M/Server databases.
7-8
Table 7-1
Parameter or
Prompt
Description
Do you want to
install the Global
Condition Server
on this computer?
(y/n):(default y)
Type y and press <Enter> to install the Global Conditions Server on the
current computer.
Do you want to
work with a
dedicated
Database Server?
(y/n):(default y)
To install a new database on a new (dedicated) Sybase database server,

enter y.
To install using an existing database server, specify n.
Do you want to
create a new
CONTROL/EM
database on the
existing Sybase
server?
(y/n):(default y)
This message is displayed if you have indicated that you want to use an
existing Sybase Database server.
Enter y to install a new CONTROL-M/EM database on the existing Sybase
Server.
Enter n to connect to an existing CONTROL-M/EM database on the existing
Sybase Server.
Configuration files
of a previous
Sybase installation
were found in
<em_home_dir>/in
stall
This message is displayed if you are migrating an existing ENTERPRISE/CS

database to CONTROL-M/EM version 6.1.03.
Do you want to use

them for new
Sybase
installation?(y/n)
<em_home_dir> is the CONTROL-M/EM user directory you created as part

of pre-installation.
Type y and press <Enter> to configure the new database using parameters
exported from the old database.
7-9
Table 7-1
Parameter or
Prompt
Sybase Database
Parameters
Description
CONTROL-M/EM
Database Owner
(DBO)
The administrator of the CONTROL-M/EM database. By

default, the DBO name is the user name of the account
being used to install CONTROL-M/EM.
For an existing database server: If CONTROL-M
databases have already been installed on this server, you
must change this name from the default to a completely
new DBO name.
Note: The CONTROL-M/EM Database Administrator
name should not exceed 8 characters.
Default: emuser.
Sybase Database
Parameters
(continued)
DBO Default
Password
The DBO password must be 6 or more characters. The

password is case-sensitive.
Default: empass.
For information about changing the password, see
"Maintaining CONTROL-M/EM" in the CONTROL-M/EM
Administrator Guide.
Database
Administrators
Password
Password for the DBA (the superuser who administrates

all databases on the Sybase Server).
The DBA password must be 6 or more characters. The
password is case-sensitive.
Default: password.
Database (Data
Portion) Size
Size of the CONTROL-M/EM database. In addition to the

database portion, a log portion is created. The log size is
about 30% of the data portion.
Default: 80 MB.
Query Socket
Port Number
Port used to communicate with database clients.

Default: 8760.
Backup Socket
Port Number
Number of the backup port used to communicate with

database clients.
Default: 8761.
7-10
Table 7-1
Parameter or
Prompt
Description
Sybase Database
Device Parameters
Data Device
Type
Data Physical
Device/Path
Name
FILE or RAW. Default: FILE.

If you want to use RAW, the raw device must be defined
prior to CONTROL-M/EM installation.
Location of the data device. Default:
<em_home_dir>/database/em610.dat
For existing database servers, this parameter indicates
the name of the device where the CONTROL-M/EM
database data is stored, as specified in the disk init
procedure that was run during pre-installation.
Log Device Type

Log Physical
Device/Path
Name
The location of the log device. Default:
<em_home_dir>/database/em610.log
For existing database servers, this parameter indicates
the name of the device where the log file of the
CONTROL-M/EM database is stored, as specified in the
disk init procedure that was run during pre-installation.
Master Device
Type
Sybase Database
Device Parameters
(continued)
Master Physical
Device/Path
Name
The master device holds server-level data for the entire

database server in a master database.
The location of the master physical device. Default:
<em_home_dir>/database/master.dat
SYBSYSTEMPR
OCS Device
Type
SYBSYSTEMPROCS is the database where all the

system procedures are stored for managing the Sybase
Server.
SYBSYSTEMPR
OCS Physical
Device/Path
Name
The location of the SYBSYSTEMPROCS device. Default:
<em_home_dir>/database/system.dat
7-11
Table 7-1
Parameter or
Prompt
Sybase Database
Parameter
(Installation with an
Existing Database
Server)
Sybase Database
Parameter
(Installation with an
Existing Database
Server)
Continued
Description
CONTROL-M/EM
Database Name
Name of the CONTROL-M/EM database.

Note: If you are installing CONTROL-M/EM using an
existing Sybase Database server, you must specify a new
name for the CONTROL-M/EM database to be created by
the installation procedure.
Sybase Server
Name
Name of the existing Sybase database server.
Sybase Server
Host Name
Host name of the computer on which the Sybase

database server is installed.
Query Socket
Number
Number of the port (on the computer that is hosting the

Sybase database server) that is used to communicate
with the database client.
Backup Socket
Number
Number of the backup port (on the computer that is

hosting the Sybase database server) used to
communicate with the database client.
Sybase Interface
Directory
Location where the Sybase Interface file will be created.

Before changing this value from the default, consult your
Sybase system administrator.
Default:
/home/<DBOname>/sybase/<Unix_type>
Sybase Server
Name
Name of the Sybase Adaptive Server.

Note: This value is automatically copied from the
previous menu (Interface File Parameter menu). There is
no need to modify this parameter in this menu.
CONTROL-M/EM
Database Name

Note: This value is automatically copied from the
previous menu (Interface File Parameter menu). There is
no need to modify this parameter in this menu.
7-12
Installing CONTROL-M/EM for

Microsoft Windows
This chapter describes how to install CONTROL-M/EM components on

Microsoft Windows.
CONTROL-M/EM consists of several components, which are used to
configure CONTROL-M/EM Clients and CONTROL-M/EM Servers.
Basic clients are usually installed on all computers.
Clients with administrator components are installed on a limited

number of computers for the use of CONTROL-M/EM
administrators.
Databases and other server components are only installed on a few

computers in the environment.
Tip
For installation of a Basic CONTROL-M/EM client, you can use a

special silent (non-interactive) procedure to speed up installation. For
more information, see Silent Installation of a CONTROL-M/EM Basic
Client on page 8-10.
Note
If you are upgrading from an earlier version of CONTROL-M/EM, see

the CONTROL-M upgrade guide for instructions on how to do this.
8-1

Summary:
Use the following steps to ensure that you are ready to install
CONTROL-M/EM on Microsoft Windows.
Step 1
Ensure that all pre-installation procedures have been performed. (see

Chapter 4, Pre-Installation Steps on Microsoft Windows.)
Step 2
Ensure that you already have a database server installed.

If you will be working with an existing Oracle database server, ensure
that you have installed the CONTROL-M/EM tablespace (as described in
Chapter 5 or 6).
Step 3
For installations that will use a Oracle or MSSQL database, ensure that
you have installed a database client on the current computer if any of the
following components will be installed on this computer:

CONTROL-M/EM Gateway
Global Alert Server
Reporting Facility
For more information about how to install an Oracle Client on Microsoft

Windows, see Chapter 6, Installing an Oracle Database on Microsoft
Windows.
Note
CONTROL-M/EM cannot be installed on the same computer as Sybase

Adaptive server. If a Sybase client is already installed on the computer, a
message is issued, offering the option of either:
- disabling the Client and replacing it with a new one
or
- exiting the installation.
8-2
Step 4
Check Parameters for Client Components

CONTROL-M/EM server components (using either the Full installation,
or Server components setup type) should be installed before
CONTROL-M/EM clients are installed on other computers.
Tip
For more information about setup types, see Setup Type on page 8-5.
Installation of the server components generates a list of parameters
(called Installation_Parameters.txt) that should be printed and used to
ensure compatible specifications during CONTROL-M/EM client
components installation.
On Microsoft Windows, the Installation_Parameters.txt file is in

the CONTROL-M/EM home directory (Default: D:\Program
Files\BMC Software\Control-M/EM).
On Unix, the Installation_Parameters.txt file, is in the

$HOME/site/ directory of the CONTROL-M/EM user.
Note
The CONTROL-M/EM database password is not included in this log file.

If you do not know the database password, get it from your Database
administrator.
Continue with the next task: Installing CONTROL-M/EM Components

on page 8-4.
8-3
Installing CONTROL-M/EM Components

Step 1
Log on as a user with Administrator privileges.
Step 2
Exit all Microsoft Windows applications before running the

CONTROL-M/EM installation procedure.
Step 3
Put the CONTROL-M/EM installation CD (FD5310) in the CD-ROM

drive.
Step 4
If Autorun functionality has not been disabled, a startup window is

displayed. Click on Install to continue.
If Autorun is disabled on your computer, or you exited this menu

previously, use Windows Explorer to select the drive containing the
installation media and double-click setup.exe.

(on page 8-5).
Note
After installation, certain services are set so that they will automatically
start when the computer is booted. If, after installation, you are having
trouble starting CONTROL-M/EM, you may need to verify that these
services have been set correctly. For more information, see Check
Startup Options for CONTROL-M/EM Services on page 16-10.


in your solution, proceed to Chapter 15, Post-Installation
Configuration.
8-4
Table 8-1
CONTROL-M/EM Parameters Microsoft Windows (Part 1 of 5)
Parameter
Description
Destination
Directory
The directory you specify in this window becomes the root directory for
CONTROL-M/EM. All selected components are installed in sub-directories under
this root directory.
Default: D:\Program Files\BMC Software\Control-M/EM
Note: You cannot specify the root drive of your hard disk as the destination
directory.
Program
Folder
Indicates the program folder to which CONTROL-M/EM program icons should be

added.
Default: CONTROL-M/Enterprise Manager 6.1.03
You can specify a new folder name in the Program Folders field, or select an
existing folder from the list.
Setup Type
Indicates the CONTROL-M/EM components that should be installed on the current

computer.
The various setup types are described below. For more information about specific
components, see Appendix B, CONTROL-M/EM Components.
Note: The Administration facility must be installed on at least one Microsoft
Windows computer.
Basic Client
Components
Installs the basic set of client components that are required on

every CONTROL-M/Enterprise Manager Windows user
workstation:
CONTROL-M/Enterprise Manager GUI
CONTROL-M/Desktop
Command Line interface
This installation type is appropriate for workstations that will be
used primarily to monitor and create job processing definitions.
Client and
Administrator
Components
Installs the Basic Client Components, plus the following

additional components:
Reporting Facility
Custom
Installation
Enables you to select specific components to be installed.
Full
Installation
Installs all CONTROL-M/EM server and client components.
8-5
Table 8-1
Parameter
Description
Setup Type
(continued)
Server
Components
Select
Components
Window
If you choose a custom installation setup type, this window is used to choose the
components to install.
Installs all the CONTROL-M/EM server components:

GUI Server
Gateway
Each of these components must be installed on at least one
computer in the scheduling environment, on computers running
Unix or Microsoft Windows. To distribute the server components
across several computers, use the Custom Installation option to
install individual CONTROL-M/EM components on each
computer.
Note: Before installing these components you must have already
installed the CONTROL-M/EM database and the Orbix E2A
server, on either this computer or a remote computer that
communicates with this computer.
Notes:
If CONTROL-M/Enterprise Manager Database or Global Conditions Server is
selected, Gateway is automatically selected.
If Global Alerts Server is selected, GUI Server is automatically selected.
If certain CONTROL-M/EM components were already installed on this computer,
they are displayed as selected in this window.
Certain prerequisite components are selected when other components are
selected. These prerequisite components are dimmed (grayed out).
For more information about specific CONTROL-M/EM components, see Appendix
B, CONTROL-M/EM Components..
Database
Server Type
Indicates the database type that will be used by CONTROL-M/EM.

Note: The database server must be installed or upgraded to the supported version
before installing CONTROL-M/EM. For more information, see Choose a Database
Configuration on page 1-4.
Configuration for Sybase or MSSQL

Database
Server Name
Name of the Database Server. Consult your database administrator for this name.
For MSSQL, this must be the name of the existing server.
To view this name, on the computer where MSSQL server is installed, choose
Start=>Programs=>Microsoft SQL Server <version>=>Service Manager
Sybase, specify a new (unique) name for the Sybase Database server. This
name will be added to the Sybase sql.ini file together with the host and port for
the database (specified later).
8-6
Table 8-1
Parameter
Description
Database
Server
Administrator
Password
Password of the database administrator account. Obtain this value from the
database administrator (sa).
Database
Files
Location
Full path name of the directory where the CONTROL-M/EM database files will be
created. This path must exist on the database server platform before
CONTROL-M/EM installation. Obtain the path name from the database
administrator.
Default values are:
For MSSQL 2000:
<drive_ID>:\Program Files\Microsoft SQL Server
\MSSQL\Data
where <drive_ID> is the local drive on which the server is installed.
For Sybase on Windows: <drive_ID>:\Sybase\data
For Sybase on Unix: /home/<ControlM_EM_account>/database
CONTROL-M/
Enterprise
Manager
Database
Name

Maximum length:
123 characters for MSSQL
30 characters for Sybase
The name must begin with a letter (not a number).
From the second character through the end:
Any letter or number is allowed.
Special characters; $, _, @, # are allowed.
No other special characters or spaces are allowed.
Default: em610
If you are installing a new CONTROL-M/EM database, specify a new unique
name for this database (not an existing name in the database server).
If you are using an existing (already installed) CONTROL-M/EM database,
specify the name of the existing database.
CONTROL-M/
Enterprise
Manager
Database
Size
Specify the Database Size (Default: 70) and database Log Size (Default: 30) in
Megabytes (MB).
Note: It is recommended that your log size be approximately 40% the size of the
database.
8-7
Table 8-1
Parameter
Description
CONTROL-M/
EM Database
Administrator
Name
Name of the CONTROL-M/EM Database Owner (DBO). Normally, this is also the
user account of the CONTROL-M/EM Administrator. The Administrator is the default
user when logging on to the CONTROL-M/EM GUI for the first time.
Maximum length up to 8 alphanumeric characters.
Default: emuser.
If you are using an existing CONTROL-M/EM database, enter the name of the
CONTROL-M/EM administrator for that database.
If you are creating a new database, specify a new (unique) name for the database
administrator.
CONTROL-M/
EM Database
Administrator
Password
Password for the CONTROL-M/EM Database Owner (DBO).

Minimum length 6 characters, Maximum 30 characters.
Database
Server
Properties
For Sybase only:

1. Specify the IP address or host name for the database server.
2. Specify the port number for communications with the database server.
Defaults:
Sybase Server on Windows: 5000
Sybase Server on Unix: 8760
Note: The port number specified in this window must match the port number that is
used by the database server. To determine the correct number, see the sql.ini
configuration file in your Sybase server installation.
Orbix Server Parameters

The Orbix Server need to be installed on only one computer in your CONTROL-M/EM environment.
Locator
Set the port number to be used by the Orbix Locator Service for communication
with Orbix clients.
Default: 3075
Note: The number specified for this parameter will be needed for all installations of
Orbix clients in your CONTROL-M/EM environment.
Node
Set the port number to be used by the Orbix Node-daemon service.

Default: 3079
8-8
Table 8-1
Parameter
Description
Orbix Client Parameters

The Orbix client is automatically installed when you choose to install any of the following
CONTROL-M/EM components:
Global Alert Server
GUI Server
CONTROL-M/EM GUI
CONTROL-M/Desktop
Host
Host name of the computer where the Orbix E2A Server is installed.
Port
Specify the Port number of the Orbix Locator Service (Default: 3075).
8-9
Silent Installation of a CONTROL-M/EM Basic Client

Summary:
Use the procedure described below to install a Basic CONTROL-M/EM

client. This client consists of the following components:
CONTROL-M/EM GUI
CONTROL-M/Desktop
Command-Line Interface
Note
For new installations (not upgrades), no CONTROL-M/EM components

can be installed on the computer prior to running this procedure.
Obtain Installation Information
The client components that you are installing must communicate with an
CONTROL-M/EM version 6.1.03 installation that is already installed on
your network.
Obtain the following information from your system administrator before
performing the steps described in Run the Installation Procedure on
page 8-10:
Host name of the computer on which the Orbix E2A Server was
installed
Port number of the Orbix Server Locator service
Run the Installation Procedure
Perform the following procedure on every computer where you are

installing the CONTROL-M/EM basic client components:
Step 1
Log on as an administrator.
Step 2
Insert the installation CD in the CD-ROM drive.
8-10
Step 3
Copy the appropriate setup file for your Microsoft Windows version from
the installation CD to the hard disk. This file has read only permission.
The following table lists the available setup files for each silent
installation/upgrade type:
Filename
Description
<CD>:\setup.iss
Installation of a CONTROL-M/EM Basic

Client on Microsoft Windows 2000.
<CD>:\setup_XP.iss
Installation of a CONTROL-M/EM Basic

Client on Microsoft Windows XP.
<CD>:\setup_desktop.iss
Installation of only the CONTROL-M/Desktop

component on Microsoft Windows 2000.
<CD>:\setup_desktop_XP.iss
Installation of only the CONTROL-M/Desktop

component on Microsoft Windows XP.
<CD>:\upgrade\setup.iss
Upgrade of an existing CONTROL-M/EM

Basic client (not an administrator client) from
an earlier version.
Note: This same procedure can be used for
upgrade of either a basic client, or just the
desktop component.
It also will work on either Microsoft Windows
2000 or XP.
Step 4
Change the permissions for the setup file on the hard disk to write.
Step 5
Open the setup file using a text editor.
Step 6
Search for the parameters described in the table below. Modify these
values as directed.
Note
Do not make any additional modifications to the setup file.
8-11
Parameter
Description
szDir
Indicates the directory where the CONTROL-M/EM

client components will be installed (for example,
D:\Program Files\BMC Software\Control-M/EM).
Note: This parameter is not relevant for upgrade
procedures.
HostOrbix
Indicates the host name of the Orbix Server Locator

service.
PortOrbixLocator
Port of the Locator service on which the local Orbix

E2A Server was installed.
Default: 3075
Step 7
Save and close the file.
Step 8
Open a command prompt window.
Step 9
Navigate to the CD drive.
Step 10
Enter the following command to start the installation procedure:

setup.exe -s -f1<setup_file_path> -f2<log_file_path>
Note
For new installations, run the setup.exe file from the root directory of the
installation CD.
For upgrade installations, run the setup.exe file from the <cd>\upgrade\
directory.
Do not put a space after the -f1 or the -f2 in the command.
-s indicates that the installation should run silently.
-f1<setup_file_path> indicates the full path to the location of the

setup file.
-f2<log_file_path> indicates the full path to the installation log file.

The installation must have full (write) permission to this
directory/file. Default: setup.log. Optional.
8-12
Step 11
Use the following methods to track installation progress:
Check if the installation is running, by looking for the IKernel.exe

process in the Task Manager window. If this process is listed, the
installation is still active.
Look in the output file (specified in the -f2 parameter in Step 10).
If the ResultCode is 0 it doesn't mean the installation ended, but it
does indicate that the silent procedure did not fail. (Other ResultCode
values are described in Table 8-2 below.)
Example of a successful silent log:
[InstallShield Silent]
Version=v6.00.000
File=Log File
[ResponseResult]
ResultCode=0
Find the log file of the installation procedure in the

Program Files\BMC Software\BMC Logs\ctmem folder.
The message: END OF INSTALLATION at the end of this file
means that it ended successfully.
(If the last line of this log file contains an error or warning message,
and it remains this way for a long time, try to find the reason.)
The installation adds an CONTROL-M Enterprise Manager 6.1.03

entry to the Start => Programs menu and desktop shortcuts to the
CONTROL-M/EM GUI and CONTROL-M/Desktop.
ResultCode Values
Table 8-2 lists possible return codes for the silent installation procedure.
Table 8-2
Installation Return Codes
Code
Description
Installation was successful.
-1
General error.
8-13
Table 8-2
Installation Return Codes
Code
Description
-2
Invalid mode.
-3
Required data not found in the Setup.iss file.
-4
Not enough memory available.
-5
File does not exist.
-6
Cannot write to the response file.
-7
Unable to write to the log file.
-8
Invalid path to the InstallShield Silent response file.
-9
Not a valid list type (string or number).
-10
Data type is invalid.
-11
Unknown error during setup.
-12
Dialogs are out of order.
-51
Cannot create the specified folder.
-52
Cannot access the specified folder.
-53
Invalid option selected.
8-14
Installing CONTROL-M/Server for

Unix
This chapter describes how to install CONTROL-M/Server for Unix.

Note
If you are upgrading from an earlier version of CONTROL-M/Server for

Unix, ensure that you have performed the initial steps that are described
in the CONTROL-M Upgrade Guide and also the preparation steps that
are described in Chapter 2 (for Sybase) or 3 (for Oracle) of this book.
Procedure
Description
Actions to be performed before installing

CONTROL-M/Server.
Upload the Installation files
How to upload installation file before running the

installation procedure.
Installing CONTROL-M/Server on Unix
How to run the installation procedure.
Record Port Usage
How to maintain the /etc/services file to help prevent

conflicting usage of ports by various applications.
Modify the Automatic Startup

Procedure
How to ensure that the Database Server and

CONTROL-M/Server are started at system startup time.
Note
In addition to these procedures, a table of all parameters and prompts for

CONTROL-M/Server installation is provided on page 9-14.
9-1

Summary:
Step 1
CONTROL-M/Server on Unix.
procedures are described in Chapter 2, Pre-Installation Steps for Unix
with a Sybase Database, or Chapter 3, Pre-Installation Steps for Unix
with an Oracle Database.
Note
The CONTROL-M/Server that you are about to install is compatible with

CONTROL-M/EM version 6.1.03 or later.
It is recommended that you verify that you have installed or upgraded to
CONTROL-M/EM version 6.1.03 before installing this version of
CONTROL-M/Server.
Step 2
If you want to use an Oracle database server for the

CONTROL-M/Server database, ensure that you first install the database
as described in Chapter 5 of this book.
Note
You can install a Sybase database server as part of this installation, or use
an existing Sybase database server.
Step 3
Mount the CONTROL-M/Server Installation CD (FD5306). This

procedure is slightly different for each Unix type. For information about
mounting CDs on supported Unix systems, see Appendix A, Mounting
CDs on Unix Computers.
9-2
Step 4
Check database processes
If you will be using CONTROL-M/Server with an Existing Sybase

Adaptive server, ask your DBA to verify that the Sybase Adaptive
server is active.
If you will be using CONTROL-M/Server with an Oracle database

server, ask your DBA to verify that the Oracle database server is
active.
The target computer for CONTROL-M/Server installation and the
host computer of the Oracle database server must have the same date
setting.
Step 5
Log in to the <controlm_user> account.
Continue with the next task: Upload the Installation files on page 9-4.
Tip
If you are replacing an old CONTROL-M/Server installation with a new

one from the same version (e.g., moving to a new computer), it is
recommended that you copy the existing installation to the new location
instead of installing a new CONTROL-M/Server. For more information
about how to do this, see Create a Staging Environment in the
CONTROL-M/Server for Unix chapter in the CONTROL-M Upgrade
Guide.
9-3
Upload the Installation files

Summary:
Use the following steps to copy the installation files to a working

directory in your Unix environment.
This procedure assumes that the CONTROL-M/Server installation CD is
still in the drive you configured in Step 3 on page 9-2.
Step 1
Use the following command to ensure that you are in the home directory
of the CONTROL-M user account:
cd <ctm_home_dir>
Step 2
Specify the following command to begin the installation procedure:

/<CD_path>/CD_INST
Where <CD_path> is the path of the mounted CD.

Note
The CD_INST command must be run from the installation CD. Do not
copy the CD contents to a temporary directory before running this
command.
A screen similar to the following is displayed:
+----------------------------------+
| Products Available on this Media |
+----------------------------------+
1) FD5306 CONTROL-M/Server Version 6.1.03 Release for Solaris, Compaq Tru64,
HP-UX, AIX
2) FD5449 CONTROL-M/Agent Version 6.1.03 Release for Solaris, Compaq Tru64,
HP-UX, AIX, NCR, SGI IRIX, Linux, DGUX
q) Quit
Select the product to install:
Step 3
Specify 1 to install CONTROL-M/Server.

A series of messages are displayed indicating the username and
destination directory for upload of the CONTROL-M/Server files.
9-4
Step 4
The following message is displayed:

Note:
CONTROL-M/Server.
Do you wish to continue with the current installation [y/n]?
Enter y to continue.
Step 5
The following options are displayed:

+----------------------------------+
|
CONTROL-M Installation
|
+----------------------------------+
N - New installation of CONTROL-M/Server
U - Upgrade from a previous version of CONTROL-M/Server
Q - Quit
Select the required option.
For a new installation, specify N, and then press <Enter>.

For an upgrade installation, specify U, and then press <Enter>. (This
option is displayed only if a supported previous version of
CONTROL-M/Server is detected.)
Note
When U (upgrade) is chosen, the CD_INST procedure performs certain

cleanup and backup functions for the old database. The messages that are
produced during this phase, are described in Table 9-1, CD_INST
Messages for Upgrade, on page 9-6.
CONTROL-M/Server files are extracted from the CD. This process
requires several minutes. After all CONTROL-M/Server files have been
loaded, the following messages are displayed.
Load completed successfully.
CD_INST was completed successfully.
9-5
For new installations or upgrade installations using a Sybase

database, continue with the next task: Installing CONTROLM/Server on Unix on page 9-8.
For upgrade installations using an Oracle database, upgrade the

database first (as described in Chapter 5, Installing an Oracle
Database on Unix) and then continue with Installing CONTROLM/Server on Unix on page 9-8.
Messages for Database Backup and Cleanup for Upgrade Installation
One or more of the following messages are displayed during the run of
the CD_INST program if you are upgrading from an earlier version of
CONTROL-M/Server:
Table 9-1
CD_INST Messages for Upgrade
Message
Description
Checking existing Database. Please wait.

The upgrade procedure needs at least <nn> MB free
space for backing up the database.
Please check if there is enough space on the disk.
Do you wish to continue? [y/n]:
The CD_INST procedure

automatically backs up your old
database files.
If you already confirmed that there
is enough space for the database
backup, type y and press <Enter>.
If you are not sure, check for the
specified amount of space, and
then type y and press <Enter>.
If you enter n the CD_INST
procedure will terminate.
9-6
Table 9-1
CD_INST Messages for Upgrade
Message
Description
For Sybase:
The CD_INST procedure

disassociates the files or devices for
the old database from the SQL
server.
CONTROL-M/Server database files:"

<list of database files>
WARNING ! These files or raw partitions are on
remote SQL Server computer.
Attention:
In order to release resources of Sybase SQL Server,
please restart it and delete the above files (not
including raw partitions).
However, it does not remove them

physically. This message reminds you
of this, and recommends that you
remove them manually after the
CD_INST procedure is finished.
For Oracle:
CONTROL-M/Server database datafile: <filename>
WARNING ! This file or raw partition are on remote
SQL Server computer.
CONTROL-M/Server database indexfile: <filename>
WARNING ! This file or raw partition are on remote
SQL Server computer.
Old CONTROL-M/Server database was successfully
dropped.
Ensure that a supported database version has been
installed before continuing.
For list of supported database versions, refer to chapter
1 of the installation guide.
This message is displayed if your

existing Sybase database server is
not supported with
CONTROL-M/Server version 6.1.03
(only versions 12.0.07 or 12.5 are
supported).
To upgrade CONTROL-M/Server using Oracle to 6.1.03

with Oracle, <user_home>/oracle directory should be
removed. proceed (Y/N)? :
This message reminds you that you

have to remove the old user directory
of the Oracle database.
If you specify Y for this message,
the CD_INST procedure removes
this directory.
If you specify N for this message,
the following message indicates
that you will have to rename it or
delete it before installing the new
Oracle database.
Before installing Oracle,
<user_home>/oracle directory
should be removed or renamed.
9-7
Installing CONTROL-M/Server on Unix

Summary:
Step 1
Use the following steps to install CONTROL-M/Server.

Mount the Sybase Installation CD (optional)
If you are going to be installing a Sybase database server together with
CONTROL-M/Server, use the following steps to mount the Sybase CD
before starting CONTROL-M/Server installation:
1.A
Use the following command to unmount the

CONTROL-M/Server installation CD:
umount <CD_path>
For Solaris computers, use the eject command.
Step 2
1.B
Remove the CONTROL-M/Server CD (FD5306) and insert the

Sybase installation CD (FD5316 or FD5317) in the CD-ROM
drive.
1.C
Mount the Sybase CD. For information about mounting CDs on

supported Unix systems, see Appendix A, Mounting CDs on
Unix Computers.
Use the following command to run the installation procedure:

install/custom
Step 3

The parameters and prompts for this installation are described in Table 92 (on page 9-14). For detailed information about these parameters, see
the CONTROL-M/Server for Unix Administrator Guide.
Step 4
The following message is displayed when installation is complete:

Before starting CONTROL-M/Server please source
the .cshrc file with the command: source ~/.cshrc
9-8
If you want to use CONTROL-M/Server immediately, run the source

<ctm_home_dir>/.cshrc command (where <ctm_home_dir> is the
home directory of the CONTROL-M/Server administrator account).
If you close the current unix session and then open a new one, this
command is not necessary.
Continue with the next task: Post-Installation Tasks on page 9-10.
9-9
Post-Installation Tasks
Some of these procedures must be performed immediately after the
installation or upgrade. Other procedures can be performed any time after
the CONTROL-M/Server installation or upgrade.
The following procedures are described:
Record Port Usage
Describes how to maintain the /etc/services file to

help prevent conflicting usage of ports by various
applications.
Modify the Automatic

Startup Procedure
Describes how to ensure that the Database Server

and CONTROL-M/Server are started at system
startup time.
After performing the post-installation tasks:


Configuration.
Note
It is strongly recommended that you install CONTROL-M/Agent on the

same computer on which you installed CONTROL-M/Server.
9-10
Record Port Usage

Summary:
Step 1
The /etc/services file contains a description of the usage of each port on

the CONTROL-M/Server platform. Proper maintenance of this file helps
prevent conflicting usage of ports by various applications.
To save all operations and communications parameters in the file
etc/services, run the following command under a root user:
install/ctm_etcservices
The following prompt is displayed:

It is recommended that you record the port numbers
used by CONTROL-M in /etc/services file on your
machine.
Do you wish these port numbers to be recorded in the
/etc/services file now (y/n) [y]:
Step 2
Type y and press <Enter> to update the /etc/services file.
9-11
Modify the Automatic Startup Procedure

Summary:
The Database Server and CONTROL-M/Server should be running at all

times on the primary server platform. It is recommended that they be
started at system startup time.
Modify the startup procedure according to the instructions for your Unix
type (below).
Note
Do not perform this procedure when installing CONTROL-M/Server on

a mirror (backup) environment.
For AIX, specify the following command:

cp <ctm_home_dir>/install/rc.<controlm_user> /etc/
Open the /etc/inittab file in an editor, and append the following line at
the end of the file.
<controlm_user>:2:respawn:/etc/rc.<controlm_user>
Example
For a user called controlm, specify the following command:

cp /home/controlm/install/rc.ctm610 /etc
and in file /etc/inittab add:

controlm:2:respawn:/etc/rc.ctm610
This copies a file containing the proper command to your system startup
directory.
9-12
For HP-UX, specify the following command:

cp <ctm_home_dir>/install/rc.<controlm_user> /sbin/init.d/<controlm_user>
ln -s /sbin/init.d/<controlm_user> /sbin/rc2.d/S98<controlm_user>
Example
cp /home/controlm/install/rc.ctm610 /sbin/init.d/ctm610
ln -s /sbin/init.d/ctm610 /sbin/rc2.d/S98ctm610
directory.
For Solaris, specify the following command:
cp <ctm_home_dir>/install/rc.<controlm_user> /etc/rc2.d/S98<controlm_user>
Example
cp /home/controlm/install/rc.ctm610 /etc/rc2.d/S98ctm610
directory.
Type exit to log out; then, log in as the CONTROL-M/Server user
(usually controlm).
For COMPAQ Tru64(Digital Unix), specify the following command:
cp <ctm_home_dir>/install/rc.<controlm_user> /sbin/init.d/<controlm_user>
ln -s /sbin/init.d/<controlm_user> /sbin/rc2.d/S98<controlm_user>
Example
cp /home/controlm/install/rc.ctm610 /sbin/init.d/ctm610
ln -s /sbin/init.d/ctm610 /sbin/rc2.d/S98ctm610
directory.
9-13
Table 9-2
CONTROL-M/Server Unix Installation Parameters (Part 1 of 9)
Parameter
Description
CONTROL-M/Server
will be installed with
the <DB_type>
database.
Do you wish to
continue with the
current installation
[y/n]?
Indicates which type of database will be installed for CONTROL-M/Server
CONTROL-M/
Server Installation
Type
Indicates the size of the installation.

Note: This selection of installation types is offered only if you are installing
with a Sybase database. For installations using an Oracle database, only a
custom installation is available. In this case, database size is determined
during installation of the Oracle database (described in Chapter 5,
Installing an Oracle Database on Unix.)
Note: If no Oracle database was installed on the computer, the system

assumes a Sybase installation must be performed as part of the
CONTROL-M/Server installation.
Compact
Compact installation is for small tests and demos. It is

not recommended for normal production.It has the
following restrictions:
You can use only one disk for database files.
CONTROL-M/Server is configured to use the new
dedicated database server supplied on the Sybase
installation CD.
Default values are used for all installation
parameters.
You cannot use raw partitions.
If you choose this installation type, the remainder of the
installation will be performed automatically, and a series
of status messages will be displayed.
Typical
A Typical installation is used for a small to medium size

database. It allows you to:
Use two disks for database files.
It is recommended that you use one disk for data and
the other disk for the transaction log.
Choose between using a dedicated database server
and an existing database server. You can modify
database parameters as required.
Change default values for all installation parameters.
Custom
A Custom installation is the same as a Typical

installation, but you can use up to five disks for
database files (to increase throughput).
Note: You can increase database performance by
using a different controller for each disk.
9-14
Table 9-2
Parameter
Description
Agent
Communication
Parameters
Use these parameters to control communication between

CONTROL-M/Server and all Agent platforms. Parameter values for
individual Agent platforms can be modified later from the CONTROL-M
Maintenance menu.
Polling Interval
Interval (in seconds) between requests from

CONTROL-M/Server for status updates from Agent
platforms that are executing jobs. Default: 900.
Communication
Timeout
Maximum time (in seconds) that CONTROL-M/Server

should spend attempting to communicate with an Agent
platform before assigning it Unavailable status.
Default: 120.
During this time, CONTROL-M/Server attempts to
communicate with the Agent platform x times, where x
is the value specified by parameter Maximum Retries.
Maximum
Retries
Number of communication retries attempted in the time

period specified in the Communication Timeout
parameter, before assigning Unavailable status to an
Agent platform. Default: 12.
Retry Interval
(Unavailable)
Time (in seconds) between attempts to communicate

with an Agent platform whose status is Unavailable.
Default: 90.
Server-to-Agent
Port Number
Listening port in the Agent computer through which

data is received from CONTROL-M/Server. The value
assigned to this parameter must correspond to the
value assigned to the Server-to-Agent Port Number
parameter in the Configuration file on the
corresponding Agent platform. Default: 7006.
Communication
Protocol
Version
Version of CONTROL-M/Agent.
Valid values:
01 version 2.2.4
02 version 2.2.5
03 version 6.0.0x
(Unix, or Microsoft Windows using short path
names)
05 version 6.0.0x
(Microsoft Windows using long path names)
06 version 6.1.0x (Default)
Check Interval
(Available)
Interval (in seconds) between status checks for each

CONTROL-M/Agent that communicates with
CONTROL-M/Server. Default: 7200 (2 hours).
9-15
Table 9-2
Parameter
Description
Server
Communication
Parameters
Note: If you perform a failover installation on the mirror environment,

ensure that Agent-to-Server Port Number and Server-to-Agent Port
Number parameters are the same for the CONTROL-M/Server platforms in
the mirror environment and the primary environment. You should also
ensure that both machines use the same date.
Local IP Host
Interface Name
Host interface name of the TCP/IP network interface

card on the Server platform to use for communication
with CONTROL-M/EM. This is typically the host name
of the Server computer. The default value for this
parameter is the default host interface name defined in
the Server computer operating environment. This
parameter can also be specified by its IP address (for
example, 192.123.186.20). This parameter should be
modified only if the Server platform contains more than
one network interface card (for example, Ethernet and
Token-Ring).
Note: CONTROL-M does not support dual IP
addresses for one machine in the DNS (Domain
Naming System). If your operating system supports
dual IP addresses, run the nslookup utility and verify
that the domain name resolves to one IP address.
(Dual IP addresses are often specified for load
balancing purposes).
Agent-toServer Port
Number
CONTROL-M/Server communicates with

CONTROL-M/Agent via two TCP/IP ports.
This parameter specifies the port used in the Server
platform for receiving data from the Agent platform. The
second port is specified using Server-to-Agent Port
Number parameter. The value for this parameter on the
CONTROL-M/Server must match its value on the Agent
platform.
Verify that the port number specified for this parameter
is not used for any other purpose in the Server
platform. The value for this parameter in the range
1024 through 65533. Default: 7005.
Communication
Protocol
Protocol used to communicate with the Agent

platforms. Note: This parameter cannot be modified.
The only valid value is TCP.
9-16
Table 9-2
Parameter
Description
Operational
Parameters
Inter Process
Communication
Port Number
Port number used for communication between

CONTROL-M processes. This parameter replaces the
Input Mailbox Key and Output Mailbox Key
parameters in earlier versions of CONTROL-M/Server.
Default: 6005
Maximum Job
State Changes
Number of job state changes CONTROL-M/Server

retains if communication with CONTROL-M/EM is
interrupted.
If the number of job state changes that occur exceeds
this value, CONTROL-M/Server initiates a download
when communication with CONTROL-M/EM is
resumed. Default: 1000.
CONTROLM/EM TCP/IP
Port Number
CONTROL-M communicates with CONTROL-M/EM

using a pair of consecutive TCP/IP ports (for example,
2370 and 2371). The lower port passes data from
CONTROL-M to CONTROL-M/EM. The higher port
passes data in the reverse direction.
This parameter is specifies the lower of the two port
numbers and must correspond to the value for TCP/IP
Port Number in the CONTROL-M definition in the
CONTROL-M/EM Data Centers window. Verify that the
two port numbers are not used for any other purpose
on the Server platform. The value for this parameter
must be a number from 1024 through 65533.
Default: 2370.
Statistics Mode
Mode used by the ctmjsa utility to collect summary

statistics.
JOBNAME compiles statistics for each CONTROL-M
Job Name and Node ID where the job was
submitted.
MEMNAME compiles them for each CONTROL-M
Mem Name/Mem Lib and Node ID.
Default: MEMNAME.
9-17
Table 9-2
Parameter
Description
Sybase Configuration
CONTROL-M/
Server
Database
Owner
Sybase user name for the CONTROL-M database

owner. The installation procedure creates this user in
the database. This name is used by CONTROL-M
when accessing its database. Default: ctrlm
Note: For installation with an existing Sybase Database
server, the value for this parameter must be unique
within the database server. (Do not specify the same
value as was used for the CONTROL-M/EM database).
DBO Password
Sybase password for the CONTROL-M database owner

(6 to 30 characters, alphanumeric). This password is
used by CONTROL-M processes and utilities to access
the CONTROL-M database. Default: password
Database
Administrators
Password
Password (6 to 30 characters, alphanumeric) for the

Sybase database administrator (user sa). This
password is used by CONTROL-M utilities to access
restricted sections of the CONTROL-M database.
Default: password
CONTROL-M/
Server
Database (Data
Portion) Size
Amount of space (in MB) to allocate for the data portion

of the CONTROL-M database. Default: 50.
If the database will be located in a file system (not a
raw partition), the installation procedure allocates the
amount of space you specify plus an additional 33% to
accommodate the Sybase transaction log.
For example, if you specify 60 MB, the amount of space
allocated is 80 MB.
Tempdb
Database (Data
Portion) Size
The amount of space occupied by temporary database

files. This value should be 33% of the total database
size (database size + log size). Default: 22
For example, if 60 MB is specified for the CONTROL-M
Server Database Size, an additional 20 MB is added for
the Sybase transaction log, and 26 MB (approximately)
should be specified for Tempdb Database size.
Note: This parameter is displayed only during custom
installation.
Log Database
(Data Portion)
Size
The amount of space occupied by Sybase transaction

log files. This value should be 33% of the database
size. Default: 17
installation.
9-18
Table 9-2
Parameter
Description
(continued)
Query Socket
Port Number
-andBackup Socket
Port Number
Sybase utilizes these two TCP/IP ports for

communication between CONTROL-M and Sybase
database server. The port numbers must be different
from each other. If these port numbers are already
used by an existing application, choose other values
from 1024 through 65534.
The Query Socket and Backup Socket each comprise 2
ports. Therefore, each value entered should be the
lower port of a pair of available ports. For example, if
the Query Port Socket is 7102, then port 7103 will also
be used for Query Port communications. Default: 7102
and 7104
Data Device
Type
Type of disk storage (raw partition or file system) used

for the CONTROL-M/Server database.
Valid values:
FILE (Default)
RAW
Data Physical
Device/Path
Name
For Data Device Type FILE: Full path name where

the CONTROL-M/Server database will be located.
Default:
/<ctm_home_dir>/sybase/data/ctrlm_data.dat
For Data Device Type RAW: Physical device name of
the raw partition in which the CONTROL-M/Server
database will be located.
server, ensure that the database server has permission
to access files at the specified path.
Log Device
Type

for the CONTROL-M database log.
Valid values:
FILE (Default)
RAW
Log Physical
Device/Path
Name
For Log Device Type FILE: Full path name where the
CONTROL-M database log will be located. Default:
/<ctm_home_dir>/sybase/data/ctrlm_log.dat
For Log Device Type RAW: Physical device name of
the raw partition in which the CONTROL-M/Server
database log will be located.
server, ensure that the database server has permission
to access files at the specified path.
9-19
Table 9-2
Parameter
Description
(continued)
Master Device
Type

for the master Sybase database. (A raw partition
installation offers enhanced database integrity.)
Valid values:
FILE (Default)
RAW
If you want Sybase to use a raw partition, type y in
response to the prompt. An additional prompt will be
displayed requesting the physical device name
(described below).
installation.
Master Physical
Device/Path
Name
For Master Device Type FILE: Full path name where

the master Sybase database will be located. Default:
<ctm_home_dir>/sybase/data/master.dat
For Master Device Type RAW: Physical device name
of the raw partition on which the Sybase database
will be located.
installation.
Tempdb Device
Type

for the Sybase temporary database. (A raw partition
installation offers enhanced database integrity.)
Valid values:
FILE (Default)
RAW
(described below).
installation.
Tempdb
Physical
Device/Path
Name
For Temporary Database Device Type FILE: Full path

name where the Sybase temporary database will be
located. Default:
<ctm_home_dir>/sybase/data/ctrlm_temp.dat
For Temporary Database Device Type RAW: Physical
device name of the raw partition on which the
Sybase temporary database will be located.
installation.
9-20
Table 9-2
Parameter
Description
(continued)
Sybsystemprocs
Device Type

for the Sybase System Processes database. (A raw
partition installation offers enhanced database
integrity.) Default: FILE.
(described below).
installation.
Sybsystemprocs
Physical
Device/Path
Name
For Sybase System Processes Database Device

Type FILE: Full path name where the Sybase system
processes database will be located. Default:
<ctm_home_dir>/sybase/data/ctrlm_sybsystemprocs.dat
For Sybase System Processes Database Device
Type RAW: Physical device name of the raw partition
on which the Sybase system processes database will
be located.
installation.
Remote Sybase
Host Name
For installation using an existing Sybase Database

Server:
Name of the host for the existing Sybase Database
server installation. This value must be a name, not an
IP address.
CONTROL-M/
Server
Database
Name

Server:
Name for the CONTROL-M/Server database. This
name must be unique. Default: ctrlm
Note: The value for this parameter must be unique
9-21
Table 9-2
Parameter
Description
(continued)
CONTROL-M/
Server
Database Data
Device Name

Server:
Sybase device on which the CONTROL-M/Server
database will be created. (See the disk init command
in the Sybase Commands Reference Manual for
information about creating a Sybase device.)
Default: ctrlm_data
CONTROL-M/
Server
Database Log
Device Name

Server:
Sybase device on which the CONTROL-M/Server
database log will be created. (See the disk init
command in the Sybase Commands Reference Manual
for information about creating a Sybase device.)
Default: ctrlm_log
9-22
10
Installing CONTROL-M/Server for

Microsoft Windows
10
This chapter describes how to install CONTROL-M/Server for Microsoft

Windows.
Note
CONTROL-M/Server for Microsoft Windows is supported only with an

MSSQL database (Sybase and Oracle are not supported). Ensure that the
database server and, if necessary, client software are installed before you
install CONTROL-M/Server. For more information, see Table 1-3,
Database Server Configurations CONTROL-M, on page 1-5.
Instead of the procedure described in this chapter, a silent installation
procedure can be used to install CONTROL-M/Server and its database
without interactive prompts. This is useful for batch installation of
CONTROL-M/Server on several computers in your environment. See
Chapter 11, Silent Installation of CONTROL-M/Server for Microsoft
Windows, for details of the silent installation procedure.
10-1

Summary:
Step 1
CONTROL-M/Server on Microsoft Windows.
procedures are described in Chapter 4, Pre-Installation Steps on
Microsoft Windows.
Note

CONTROL-M/Server.
Step 2
If you will be associating the CONTROL-M/Server Windows service

with a specific user, define the user before installation. Refer to your
system administrator for the permissions this user must have.
Continue with the next task: Installing CONTROL-M/Server on

Microsoft Windows on page 10-3.
10-2
Installing CONTROL-M/Server on Microsoft Windows

Summary:
Step 1
Use the following steps to install CONTROL-M/Server.

Log in as a user that has Administrator privileges on the current
computer. This user must have the following privileges:
Step 2
act as part of operating system

logon as batch job
increase quotas
replace a process level token
logon as a service
Insert the installation CD in the CD-ROM drive.
If Autorun is enabled on your computer, the installation procedure

runs automatically after you insert the CD.
If Autorun is not enabled, browse to the FD5305 directory on the
CD and run the Setup.exe file.
Click CONTROL-M/Server to continue.

Step 3

(on page 10-5).
Note
If you do not already have MDAC (Microsoft Data Access Components)

version 2.7 with SP1, it will be installed with CONTROL-M/Server and
you will be asked to reboot at the end of the installation.
10-3
After Installation...
Step 4
For Cluster Environments Only:

4.A
Update the system path of all other relevant nodes with the
CONTROL-M/Server path that is specified in the system path of
the primary node.
4.B
Use the following steps to set the environment path for

CONTROL-M/Server:
Choose Start => Settings => Control Panel => System

Click Environment Variables in the Advanced tab.
Click OK.

It is strongly recommended that you install CONTROL-M/Agent on
the same computer on which you installed CONTROL-M/Server.

Configuration.
10-4
Table 10-1
CONTROL-M/Server Parameters Microsoft Windows (Part 1 of 6)
Parameter
Description
Cluster
Configuration
Parameters
The following fields are displayed if your computer supports a cluster environment.
(Clustering supports several processors with a virtual addressing scheme.)
Cluster
Configuration
Parameters
(continued)
Destination
Folder
Virtual Server
Name
The virtual name assigned to the CONTROL-M/Server

application in the cluster environment.
Virtual IP
Address
The virtual IP address assigned to the CONTROL-M/Server

application in the cluster. The virtual address you assign will be
used to access the CONTROL-M/Server application as it passes
between nodes in the clustered environment.
Network to
Use
Choose the IP network path that is used to access the

CONTROL-M/Server application. You must select a mixed or
public network (not a private network).
To check if a network name is public/mixed or private, run the
following command:
Cluster.exe network <network_name> /prop:role
Where <network_name> is one of the names that appears in
the drop-down list for this parameter.
If the Value returned by this command is 2 or 3, it is a mixed
or public network (select this network name).
If the Value returned by this command is 1, it is a private
network (do not select this network name).
Available
Nodes
These two fields of the Cluster Management window are used to

configure failover behavior.
The order of the Configured Nodes list determines the failover
order. If a computer on the list fails, the CONTROL-M/Server
application is transferred to the next node on the list.
Use the Add and Remove buttons of the window to move nodes
from the Available Nodes list to the Configured Nodes list, and
to reorder nodes in the list.
Configured
Nodes
Disk Group
The CONTROL-M/Server application group in which the cluster

disk is defined.
Disk Name
The native ID of the cluster disk.
Resource
Disk Name
The virtual name assigned to the cluster disk in the

CONTROL-M/Server application group.
Indicates where CONTROL-M/Server will be installed.

Default: <OS_install_drive>\BMC Software\CONTROL-M Server
To modify the default destination, click Change.
Note: If your system supports clustering, do not change the disk assignment.
However, you may select a different destination directory on the specified disk
drive.
10-5
Table 10-1
Parameter
Description
Communication
Parameters
Local IP Host
Interface
Name
Name of the host machine of the CONTROL-M/Server. Default:

Local host name.
Note: When installing on a computer that supports clustering,
specify the Virtual Server Name.
Agent-toServer Port
Number
Listening port in the Server computer that receives data from all
Agent computers. The value specified must match the value
assigned to the Agent-to-Server Port Number parameter on all
Agent computers. Verify that this port number is not used for any
other purpose in this Server computer. Specify a numeric value
between 1025 and 65535. Default: 7005
Server-toAgent Port
Number
Listening port in the Agent computer that receives data from this
Server computer. The value specified must match the value
assigned to the Server-to-Agent Port Number parameter (for this
Agent) on the Agent computer. Verify that this port number is not
used in the Agent for any other purpose. Specify a numeric
value between 1025 and 65535. Default: 7006
Communicati
on Timeout
Maximum time (in seconds) that

CONTROL-M/Server attempts to communicate with an Agent
before assigning the Agent the status Unavailable.
Default: 120
Maximum
Retries
Number of communication retries to attempt during the time

period specified in the Communication Timeout parameter.
Default: 12
Communication
Parameters
(continued)
10-6
Table 10-1
Parameter
Description
Operational
Parameters
Maximum Job
State
Changes
Number of job state changes retained by

CONTROL-M/Server if communication with
CONTROL-M/EM is interrupted. If the number of job state
changes exceeds the value specified for this parameter,
CONTROL-M/Server will initiate a download when
communication with CONTROL-M/EM is resumed. Default: 1000
CONTROLM/EM TCP/IP
Port Number
CONTROL-M/Server communicates with CONTROL-M/EM

using a pair of consecutive TCP/IP ports (for example, 2370 and
2371).
The lower port (e.g. 2370) is used for data flow from
CONTROL-M/Server to CONTROL-M/EM.
The higher port (e.g. 2371) is used for data flow in the reverse
direction.
This parameter is used to specify the lower of the two port
numbers and must correspond to the value assigned to the
TCP/IP Port Number field in the definition of the
CONTROL-M/Server data center in the CONTROL-M/EM Data
Centers window.
Verify that the two port numbers are not used for any other
purpose on the Server platform.
The value for this parameter must be a number between 1024
and 65533. Default: 2370
CONTROLM/Server IPC
Port Number
IPC port number used for communication between

CONTROL-M/Server processes. Default: 9000
Statistics
Mode
Indicates the mode used by the ctmjsa utility to collect statistics:

MEMNAME Compiles job statistics for each CONTROL-M
MemName, MemLib and Node ID.
JOBNAME Compiles statistics for each
CONTROL-M Job Name and Node ID where the job was
submitted.
Default: MEMNAME.
Maximum
Server
Processes
Maximum number of requests from CONTROL-M/EM that the

CONTROL-M/Server gateway can process concurrently. Valid
values range from 1 to 1000. Default: 1
Minimum
Server
Processes
Minimum number of CONTROL-M/Server gateway processes

that will run concurrently.
If the number of requests from CONTROL-M/EM is less than
this number, the extra processes be created, and then wait for
additional requests.
Operational
Parameters
(continued)
Valid values range from 1 to 1000. Default: 1

10-7
Table 10-1
Parameter
Description
SQL Server
Configuration
Database
Server
Host Name
Name of the existing Database Server. Consult your database

administrator for this name.
To view this name, on the computer where MSSQL server is
installed, choose Start=>Programs=>Microsoft SQL Server
<version>=>Service Manager
Default: current computer.
SA Password
Password of the system administrator (SA) of the MSSQL

database.
CONTROLM/Server
DB Name
Name of the CONTROL-M/Server database.

Maximum length, 123 characters.
If you are installing a new CONTROL-M/Server database,
specify a new unique name for this database (not an existing
name in the database server).
Default: ctrlm
DB Owner
Name of the CONTROL-M/Server Database Owner (DBO).

Normally, this is also the user account of the CONTROLM/Server administrator.
Maximum length up to 123 alphanumeric characters.
If you are creating a new database, specify a new (unique)
name for the database administrator.
Default: ctrlm
DBO
Password
Password for the CONTROL-M/Server database owner (6 to 30

alphanumeric characters).
The first character must be a letter (A Z).
10-8
Table 10-1
Parameter
Description
SQL Server
Device
Parameters
Data Device
Logical Name
Name of the device on which the CONTROL-M/Server database

will be located. Default: ctrlm_data
Data Device
Physical Full
Path File
Name
Full path name where the CONTROL-M/Server database will be

located. Specify a new filename in an existing directory path on
the computer where the MSSQL Server is installed.
Data Device
Size
Amount of space (in MB) to be allocated for the data portion of

the CONTROL-M/Server database.
Default: 75
Log Device
Logical Name
Name of the device on which the CONTROL-M/Server database

log will be located. Default: ctrlm_log
Log Device
Physical Full
Path File
Name
Full path name where the CONTROL-M/Server database log will

be located. Specify a new filename in an existing directory path
on the computer where the MSSQL Server is installed.
Log Device
Size
Amount of space (in MB) to be allocated for the CONTROL-M

log database. Default: 25
Configuration for the CONTROL-M/Server Windows Service

The following fields are used to determine the behavior of the CONTROL-M/Server Windows Service.
Startup
Type
Specifies how the CONTROL-M/Server service will be started. It is recommended

that you install CONTROL-M/Server as an automatic service. Options for this field
are:
Note: If you are installing on a cluster environment, the service must be
configured as Manual. If you specify Automatic during this type of installation,
that change will be ignored, and it is forced to Manual.
Automatic
The service starts when the system starts. This is the default
setting.
Manual
The service can be started by a user or a dependent service.
10-9
Table 10-1
Parameter
Description
Log On As
Specifies the name of the user that will be used to run the
CONTROL-M/Server.
System
Account
Specifies that the service will log on to the system account,

rather than a user account. The CONTROL-M/Server service
runs using the native system account environment with full
privileges in the administrative group. This is the default setting.
Allow Service to Interact with Desktop - Check this option to
enable a desktop user interface for the service. The desktop
interface can be used by whoever is logged in locally when the
service is started. This option can be used only if the service is
running as a local System account.
This Account
Indicates a specific user and password under which the

CONTROL-M/Server service will run. Specify a user with full
privileges in the Administrative group, including the following
privileges:
logon as batch job
increase quotas
logon as a service
This field must include the domain as well as the user name, in
the format: <domain>\<user>
10-10
11
Silent Installation of
CONTROL-M/Server for Microsoft
Windows
11
Use the silent installation procedure to perform an installation without

user interaction.
The silent installation procedure receives information from files that you
prepare in advance. You can modify default values as required.
Note

CONTROL-M/Server.
11-1

Summary:
Use the following steps to modify the batch file and then run the
modified silent installation procedure:
Step 1
Using Windows Explorer, select the CD-ROM drive and under

<Drive_ID>, browse the FDnnnn directory. Right-click the silent.bat
file. Select Edit from the short-cut menu.
Step 2
The batch file is displayed in the default text editor, as in the following
example.
rem ** CONTROL-M/Server 6.1.03 Silent installation **
mkdir %temp%\ctmsrv_logs
msiexec /i "<CD-Drive>\<FDnnnn>\CONTROL-M Server.msi"
/qn DB_SERVER_HOSTNAME="<Enter value here>"
DATA_PHYSICAL_DEVICE_FULLPATH_FILE_NAME="<Enter value
here>" LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME="<Enter
value here>" DB_SA_PASSWORD="<Enter value here>"
CTM_SQL_SERVER_DB_NAME="<Enter value here>"
CTM_DB_OWNER="<Enter value here>"
CTM_DB_OWNER_PASSWORD="<Enter value here>" /l*v
"%temp%\ctmsrv_logs\Svr613_si_log.txt"
The batch file has three lines:
Step 3
A remark-line header
A line with the mkdir command
A line with the msiexec command. This line is the body of the file,
and contains the parameter definitions. The standard file contains
placeholders for the pathname and for mandatory parameter values.
These must be replaced by actual values.
Add parameters and their values to the third line of the file. For example:
msiexec /i "<CD-Drive>\<FDnnnn>\CONTROL-M Server.msi"
/qn <parameter>="<value>" <parameter>="<value>" /l*v
"%temp%\ctmsvr_logs\Svr610_si_log.txt"
11-2
Syntax rules
The parameters are inserted between the /qn term and the /l*v term.
Actual values must be enclosed in quotes.
A single space is used to separate parameter terms.
In the actual file, the following mandatory parameters have already
been inserted. (You must provide values for these parameters.)
DB_SERVER_HOSTNAME
DATA_PHYSICAL_DEVICE_FULLPATH_FILE_NAME
LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME
DB_SA_PASSWORD
CTM_SQL_SERVER_DB_NAME
CTM_DB_OWNER
CTM_DB_OWNER_PASSWORD
Note
If an optional parameter is not specified, the default value will be used.

Step 4
After editing is complete, save the silent.bat file to a temporary

directory.
Step 5
To run the silent installation, browse to the temporary directory, and

double-click the silent.bat file.
Step 6
When installation is complete, CONTROL-M/Server is added to the

Microsoft Windows Start =>Programs menu.
A log file named is created in the temp\ctmsrv_logs directory. The
default name of this file is Svr610_si_log.txt. Check this log file to
verify successful installation.
Note
The same batch file can be copied to other computers and used to create
several identical installations.
See Table 11-1 on page 11-4 for installation parameters and their
default settings.
11-3
If you are installing in a cluster environment, you must also assign

values for all parameters in Table 11-2 on page 11-7.
Sample batch files are shown on page 11-8.


Configuration.
Batch File Installation Parameter Default Settings
Table 11-1 describes the silent installation parameter settings. Table 11-2
lists additional parameters used to configure a Cluster Environment.
Table 11-1
Silent Installation Batch File Default Parameters (Part 1 of 4)
Parameter
Description
INSTALLDIR
Name of the installation directory. Default:

<Drive_ID>\Program Files\BMC Software\CONTROL-M Server\
where <Drive_ID> is the drive where Program Files are defined in
this computer
LOCAL_IP_HOST_INTERFAC
E_NAME
The IP host interface name of the Server platform currently issuing

job handling requests to the platform. Default: Local host name
AGENT_TO_SERVER_PORT_
NUMBER
Port number used by the CONTROL-M/Agent platform for receiving

data from the CONTROL-M/Server platform (Server-to-Agent port
number). Default: 7006
Note: Specify a numeric value from 1025 to 65535.
SERVER_TO_AGENT_PORT_
NUMBER
Port number used by the CONTROL-M/Server computer for

receiving data from the CONTROL-M/Agent platform (Agent-toServer port number). Default: 7005
COMM_TIMEOUT
Maximum length of time (in seconds) that CONTROL-M/Server

attempts to communicate with an Agent before assigning the Agent
the status Unavailable.
Default: 120
11-4
Table 11-1
Parameter
Description
MAXIMUM_RETRIES
Number of communication retries to attempt during the time period

specified in the Communication Timeout parameter.
Default: 12
MAX_JOB_STATE_
CHANGES
Number of job state changes retained by CONTROL-M/Server if

communication with CONTROL-M/EM is interrupted. If the number
of job state changes exceeds the value specified for this parameter,
CONTROL-M/Server will initiate a download when communication
with CONTROL-M/EM is resumed.
Default: 1000
ECS_PORT_NUMBER
CONTROL-M/Server communicates with CONTROL-M/EM using a

pair of consecutive TCP/IP ports (for example, 2370 and 2371).
The lower port (e.g. 2370) is used for data flow from CONTROLM/Server to CONTROL-M/EM.
The higher port (e.g. 2371) is used for data flow in the reverse
direction.
This parameter is used to specify the lower of the two port numbers
and must correspond to the value assigned to the TCP/IP Port
Number field in the definition of the CONTROL-M/Server data
center in the CONTROL-M/EM Data Centers window.
Verify that the two port numbers are not used for any other purpose
on the Server platform.
The value for this parameter must be a number between 1024 and
65533.
Default: 2370
IPC_PORT_NUMBER
IPC port number used for communication between

CONTROL-M/Server processes. Default: 9000
STATISTICS_MODE
Mode used by utility ctmjsa to collect summary statistics.

JOBNAME: compiles statistics for each CONTROL-M Job Name
and Node ID where the job was submitted.
MEMNAME: compiles them for each CONTROL-M Mem
Name/Mem Lib and Node ID. Default: MEMNAME
DB_SERVER_HOSTNAME
Host name of the machine where the MSSQL Server resides.

Default: current computer.
DB_SA_PASSWORD
Password of the system administrator (SA) of the database.
CTM_SQL_SERVER_DB_
NAME
Name of the CONTROL-M database. This name must be unique.

Default: ctrlm
CTM_DB_OWNER
Name for the CONTROL-M database owner. Default: ctrlm
11-5
Table 11-1
Parameter
Description
CTM_DB_OWNER_
PASSWORD
Password for the CONTROL-M database owner (6 to 30

alphanumeric characters). The first character must be a letter (A Z). If the specified password is longer than 30 characters, only the
first 30 are accepted. Default: password
DATA_DEVICE_LOGICAL_
NAME
Name of the device on which the CONTROL-M database will be

located. Default: ctrlm_data
DATA_PHYSICAL_DEVICE_
FULLPATH_FILE_NAME
Full path name where the CONTROL-M database will be located.

For example: <sql dir>\data\ctrlm_data
DATA_DEVICE_SIZE
Amount of space (in MB) to be allocated for the data portion of the
CONTROL-M database. Default: 75
LOG_DEVICE_LOGICAL_
NAME
Name of the device on which the CONTROL-M database log will be

located. Default: ctrlm_log
LOG_PHYSICAL_DEVICE_F
ULLPATH_FILE_NAME
Full path name where the CONTROL-M database log will be

located. For example: <sql dir>\data\ctrlm_log.
LOG_DEVICE_SIZE
Amount of space (in MB) to be allocated for the CONTROL-M log

database. Default: 25
SERVER_SERVICE_
STARTUP_TYPE
Specifies a start-up method for CONTROL-M/Server Microsoft

Windows services. It is recommended that you install CONTROLM/Server as an automatic service. Specify one of the following:
LOGON_ACCOUNT_TYPE
SERVICE_
AUTO_START
Services should start when the system

starts. Default.
SERVICE_
DEMAND_START
Services can be started by a user or a

dependent service.
User account under which the CONTROL-M/Server service will run.

Valid values:
1 - The services log on to the local system account, rather than a
user account. The services will run using the native system account
environment with full privileges in the administrative group. Default.
0 - Specific user and password under which the services will run.
When this option is chosen, you must specify the user account and
password using the THISACCOUNTUSER and
THISACCOUNTPASSWORD parameters (see below).
11-6
Table 11-1
Parameter
Description
THISACCOUNTUSER
The user account under which the CONTROL-M/Server service will

run. Specify a user account with full privileges in the administrative
group, including the following privileges:
logon as batch job
increase quotas
logon as a service
The value must have the format: <domain>\<user>.
Note: This parameter is used if the service will run under a different
user than the local system account (defined by specifying
LOGON_ACCOUNT_TYPE= "O, see above)
THISACCOUNTPASSWORD
Password of the user account under which the CONTROLM/Server service will run.
Note: This parameter is used if the service will run under a different
user than the local system account (defined by specifying
LOGON_ACCOUNT_TYPE= "O, see above)
SERVER_SERVICE_
INTERACTIVE_DESKTOP
Service interacts with Desktop - Specify whether the service

provides a user interface on a desktop that can be used by whoever
is logged in when the service is started. Valid values:
SERVICE_INTERACTIVE_PROCESS - Permit interaction with the
desktop. Default.
" " - Blank, do not permit interaction with the desktop.
Note: This option can be used only if the service runs as a local
system account (defined by specifying
LOGON_ACCOUNT_TYPE= "1", see above).
MSSQL_UPGRADE
Indicates that this silent installation is an upgrade procedure. When

this parameter is set to Y, the installation script runs an upgrade
procedure from version 6.1.01 instead of a normal installation
procedure.
Table 11-2 lists additional parameters used to configure a Cluster

Environment. These parameters must be specified if you are installing in
a cluster environment.
Table 11-2
Silent Installation Batch File Cluster Parameters (Part 1 of 2)
Parameter
Description
CLUSTER_VIRTUAL_SRV_NAME
Cluster Node virtual server name.
VIP
Cluster Node Virtual IP
11-7
Table 11-2
Silent Installation Batch File Cluster Parameters (Part 2 of 2)
Parameter
Description
CLUSTER_NETWORK_TO_USE
Network type to use
CONFIGURED_NODES
List of nodes to participate in clustering by order.
CLUSTER_DISK_GROUP
Virtual Group Disk name
CLUSTER_DISK_NAME
Virtual Disk name
RES_DISK_NAME
Virtual resource name holding the cluster disk.
Sample Customize Batch Files for Silent Installation

Note
In the examples below, some parameters may be set on separate lines for
clarity, in actual batch files, all the parameters make up a single long line
of code, separated by single spaces.
This example modifies the following parameters:
DB_SERVER_HOSTNAME
CTM_DB_OWNER
DATA_DEVICE_LOGICAL_NAME
DATA_PHYSICAL_DEVICE_FULLPATH_FILE_NAME
LOG_DEVICE_LOGICAL_NAME
LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME
A log file named my_silent_inst_log.txt is generated in the \temp\

directory.
rem ** CONTROL-M/Server 6.1.03 Silent installation **
mkdir %temp%\ctmsvr_logs
11-8
msiexec /i "<CD-Drive>\<Fnnnn>\CONTROL-M Server.msi"

/qn DB_SERVER_HOSTNAME="MSSQL_SRV_02"
CTM_SQL_SERVER_DB_NAME="my_ctrlm"
CTM_DB_OWNER="my_ctrlm"
DATA_DEVICE_LOGICAL_NAME="my_ctrlm_data"
DATA_PHYSICAL_DEVICE_FULLPATH_FILE_NAME="E:\Program
Files\Microsoft SQL Server\MSSQL\Data\my_ctrlm_data"
LOG_DEVICE_LOGICAL_NAME="my_ctrlm_log"
LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME="E:\Program
Files\Microsoft SQL Server\MSSQL\Data\my_ctrlm_log"
CTM_SQL_SERVER_DB_NAME="ctrlm"
CTM_DB_OWNER="ctrlm"
CTM_DB_OWNER_PASSWORD="password"
/l*v "%temp%\my_silent_inst_log.txt"
11-9
11-10
12
Installing or Upgrading
CONTROL-M/Agent for Unix
12
This chapter describes how to install CONTROL-M/Agent on a Unix

computer.
Procedure
Description
Check System Requirements
Hardware and software requirements for CONTROL-M/Agent
Steps to be performed before installing CONTROL-M/Agent
Configure NIS
How to create an entry in the Services map for

CONTROL-M/Agent if NIS is used at your site.
Upgrade with CONTROL-M

Option for Oracle Applications
Installed
Special steps that should be performed if you will be using

CONTROL-M/Agent together with CONTROL-M/Option for
Oracle Applications.
Upgrade with CONTROL-M

Option for Oracle Applications
Installed
Special steps that should be performed if you are upgrading

CONTROL-M/Agent from version 6.0.0x or earlier on a computer
where CONTROL-M/Option for PeopleSoft is installed.
Mount the CD-ROM Drive
How and where to mount the CD for local or remote installation.
CONTROL-M/Agent on Unix
Running the installation or upgrade procedure.
Set the Protocol Version for the

Upgraded CONTROL-M/Agent
Reset the communication protocol for the agent in

CONTROL-M/Server.
CONTROL-M/Agent for Unix in
Silent Mode
Running the installation without requiring user interaction.
12-1
Check System Requirements

Summary:
Ensure that your computer meets the following requirements before

installing CONTROL-M/Agent for Unix.
Table 12-1
System Requirements
Operating
System
Memory
128 MB
Disk Space
20 MB free disk space in the CONTROL-M/Agent home

directory. Additional disk space is required for job sysouts.
Media Drive
CD-ROM on the same platform type as target computer.
Communication Adapter
Any TCP/IP adapter
Software
CONTROL-M/Server version 6.1.03 or later
12-2
One of these operating systems (or binary compatible):

AIX (32-bit or 64-bit) 4.3.3, 5.1 or 5.2
Sun SPARCstation (Solaris) 2.6, 2.7 (32-bit or 64-bit),
2.8, and 2.9
HP-UX (32-bit or 64-bit) 11.0, and 11.11(11i)
Digital Unix OSF/1 (32-bit or 64-bit) 4.0f, and g
Compaq TRU64 (32-bit or 64-bit) 5.0, 5.1, 5.1a, and
5.1b
NCR 3.0.2
IRIX (Silicon Graphics) 6.5.2, 6.5.3, and 6.5.4
UnixWare SCO 7.0 and 7.1
Data General 4.2 (Intel Processor)
Linux Red Hat Advanced Server 2.1
Linux (SuSE) SLES 8 on Intel
Linux (SuSE) 7.3, 8.0, 8.1, 8.2, and 9 on Intel
Linux SuSE 7, SLES 7 and SLES 8 on z/Series
RedHat Enterprise Linux (RHEL) 3 on Intel and zSeries

Summary:
Use the following steps to ensure that you are ready to install
CONTROL-M/Agent on Unix.
Step 1
Ensure that the prerequisites described in the previous task are met.
Step 2
Define a CONTROL-M/Agent user.

Note
If CONTROL-M Option for Oracle Applications version 2.0.01 or earlier

is installed on the same computer, then you must install
CONTROL-M/Agent in a different Unix user account.
Step 3
Verify that your locale setting is English. (You can check this using the
locale command.)
You can change the locale setting later (after installation) to conform
with your environment. Note that all computers with CONTROL-M
components (CONTROL-M/EM, CONTROL-M/Server, or
CONTROL-M/Agent) must have the same locale setting.
Step 4
If you are upgrading from an earlier version of CONTROL-M/Agent for

Unix, verify that it is not running and that no jobs are currently executing
because CONTROL-M/Agent will not recognize these jobs after the
upgrade is complete.
If NIS is used at your site, continue with the next task Configure
NIS on page 12-4.
If you are upgrading CONTROL-M/Agent for Unix on a computer

where CONTROL-M Option for Oracle Applications is already
installed, continue with the next task: Upgrade with CONTROL-M
Option for Oracle Applications Installed on page 12-6.
Otherwise, skip to: Mount the CD-ROM Drive on page 12-8.
12-3
Configure NIS
Summary:
If NIS is used at your site, create an entry in the Services map for
CONTROL-M/Agent before proceeding with the installation. This entry
is created only once for all Agent platforms.
For AIX and Solaris
Whether an entry should be created in the Services map depends on

the services file search path. For more information, see Determining
the Search Path (Solaris Only) on page 12-5.
Request that your NIS administrator create the following entry in the
Services map:
<service_name> <port>/tcp #CONTROL-M/Agent
where:
<service_name>
Recommended value: ctmagent.
<port>
Value of CONTROL-M/Agent configuration parameter

Server-to-Agent Port Number. (Default value in
CONTROL-M/Server: 7006).
Example
ctmagent 7006/tcp #CONTROL-M/Agent
12-4
Determining the Search Path (Solaris Only)
For Solaris platforms, the search path for the services file determines if
you should create a CONTROL-M/Agent entry in the Services map.
The /etc/nsswitch.nis file contains an entry that determines the
precedence of the search path for the services file. Sample entry in
nsswitch.nis: services: files nis
Note
If the services entry in the nsswitch file contains the keyword files,
regardless of the order of the keywords, the system will look for
CONTROL-M/EM on the local file system. Therefore, do not create an
entry in the Services map for CONTROL-M/EM.
If you are upgrading CONTROL-M/Agent for Unix on a computer where

CONTROL-M Option for Oracle Applications is already installed,
continue with the next task: Upgrade with CONTROL-M Option for
Oracle Applications Installed on page 12-6.
Otherwise, continue with Mount the CD-ROM Drive on page 12-8.
12-5
Upgrade with CONTROL-M Option for Oracle Applications Installed

Summary:
The following steps must be performed before upgrade of

CONTROL-M/Agent, if CONTROL-M/Agent and CONTROL-M Option
for Oracle Applications ("the Option") are installed on the same Unix
computer and you want to upgrade CONTROL-M/Agent to version
6.1.03.
Step 1
Ensure that all jobs submitted to the Agent have ended. Otherwise, the
status of running and submitted jobs will become UNKNOWN.
Step 2
Create another Unix user account for the Option.
Step 3
Install the latest version of the Option on the new user account and
configure its environment variables.
Step 4
Copy all files from the <old_CONTROL-M_Option_dir>/DATA

directory to the <new_CONTROL-M_Option_dir>/DATA directory.
Step 5
Verify that the new Option is working properly.
Step 6
Before upgrading the Agent, modify its .cshrc file by removing all
references to the <old_CONTROL-M_Option_dir>/EXE directory.
Continue with Mount the CD-ROM Drive on page 12-8.
12-6
Upgrade with CONTROL-M Option for PeopleSoft Installed

Summary:
If CONTROL-M Option for PeopleSoft version 2.0.03 is installed under

the exe_<platform> directory of a version of CONTROL-M/Agent
version 6.0.0x or earlier, the PeopleSoft files in the old Agent
exe_<platform> directory are not moved to the new installation
directory during CONTROL-M/Agent upgrade to version 6.1.03.
Use the following procedure to enable CONTROL-M Option for
PeopleSoft to continue to work with CONTROL-M/Agent after upgrade
to version 6.1.03:
Step 1
Backup the following Option for PeopleSoft jar and environment files
that reside in the current CONTROL-M/Agent exe_<platform>
directory:
psjoa.jar
generated.jar
ctmpsft.jar
ctmpsft.env
Step 2
Perform the CONTROL-M/Agent upgrade process as described in the

CONTROL-M Installation Guide.
Step 3
Restore the files that were backed up in Step 1 into the new
CONTROL-M/Agent exe directory.
Step 4
If necessary, modify the CLASSPATH environment variable to point to

the new location of the CONTROL-M Option for PeopleSoft files.
Continue with the next task: Mount the CD-ROM Drive on page 12-8.
12-7
Mount the CD-ROM Drive

Summary:
You can mount the CONTROL-M/Agent installation CD (FD5449) on a

local drive on the CONTROL-M/Agent platform or a remote drive on the
same type of computer. If the drive is local, certain steps (described
below) are necessary to ensure that the drive is mounted and accessed
correctly.
Note
To install CONTROL-M/Agent for Linux on zSeries, the installation CD

must be loaded on the CD-ROM drive of a remote computer.
Using a Local CD-ROM Drive
If the CD-ROM drive is connected to a Solaris computer, no special

actions are needed. Otherwise, perform the following steps:
Step 1
Log in as user root.
Step 2
Create an empty directory for mounting the CD-ROM drive. (This

directory cannot be under the CONTROL-M/Agent installation
directory.)
Step 3
Connect the CD-ROM drive to the mount directory using the mount
command.
Note
The mount command is different for each Unix type. See Appendix A,
Mounting CDs on Unix Computers for information about using this
command on various Unix platforms.
We recommend that you use the ISO-9660 option (if available). Consult
your system administrator about the usage of the mount command.
12-8
Using a Remote CD-ROM Drive

Step 1
Log in as a root user on the remote machine.
Step 2
Create an empty directory (e.g., /cdromr) for the CD-ROM drive.

This directory cannot be under the CONTROL-M/Agent installation
directory.
Step 3
Mount the installation CD.

Note
The mount command is different for each Unix type. For more
information, see Appendix A, Mounting CDs on Unix Computers.
We recommend that you use the ISO-9660 option (if available). Consult
your system administrator about the usage of the mount command.
Step 4
List the /cdromr directory in the /etc/exports file to make it accessible to

the Network File Server (NFS) utility.
Note
The NFS export utility works differently for various Unix types. For
more information, consult your system administrator.
Step 5
Log in as a root user on the CONTROL-M/Agent computer.
Step 6
Create an empty directory (e.g., /cdrom) for mounting the remote

/cdromr directory.
Step 7
Use the following command to connect the remote /cdromr directory to

your local /cdrom directory:
mount <remote_machine>:/cdromr /cdrom
To perform a normal installation, continue with the next task: Installing

or Upgrading CONTROL-M/Agent on Unix on page 12-11.
12-9
To perform a silent (non-interactive) installation, continue with the next

task: Installing or Upgrading CONTROL-M/Agent for Unix in Silent
Mode on page 12-14.
12-10
Installing or Upgrading CONTROL-M/Agent on Unix

Summary:
Use this same procedure for installation or upgrade from an earlier

version of CONTROL-M/Agent for Unix.
Note
Before performing an upgrade installation, ensure that all jobs submitted

to the Agent have ended. Otherwise, the status of running and submitted
jobs will become UNKNOWN.
Step 1
Log in to the CONTROL-M/Agent computer as a root user.

Note
If NIS is active, the installation procedure will use it. You can check if
NIS is active by issuing the ypwhich command.
If the system returns the host name of the NIS server, NIS is running.
Step 2
Navigate to the home directory of the CONTROL-M/Agent user account

using the following command: cd <agent_home_dir>
Step 3
Specify the following command to begin the installation from the CD:
/<cd_path>/cd_inst
Note
The CD_INST command should be specified in uppercase or lowercase

depending on the options that were used to mount the installation CD.
Step 4
Follow the prompts to complete the installation. For more information

about these prompts and parameters, see Table 12-5 on page 12-19.
The following message indicates the installation has finished:
CONTROL-M/Agent installation procedure completed
successfully.
12-11
If you have just completed upgrading a previously existing agent,

continue with Set the Protocol Version for the Upgraded
CONTROL-M/Agent on page 12-13.


Configuration.
12-12

Use the following steps to set the Protocol Version for the upgraded
Agent in CONTROL-M/Server:
Step 1
Enter the command ctm_menu to display the CONTROL-M Main

Menu. From the menu, select Parameter Customization =>
Parameters for Communicating with Specific Agent Platforms.
To view/modify communication parameters, enter node ID
of Agent Platform:
Step 2
Enter the node ID of a CONTROL-M/Agent, for example, diana. The

Communicating with Specific Agent Platform (diana) menu is displayed.
Step 3
Specify 06 for the Communication Protocol Version for the agent.


Configuration.
12-13
Installing or Upgrading CONTROL-M/Agent for Unix in Silent Mode

Summary:
Use the following procedure to install or upgrade CONTROL-M/Agent

for Unix without user interaction (in silent mode).
Step 1
Copy the cd_inst.in file from /<cd_path>/FD5449/ on the

CONTROL-M/Agent CD (FD5449) to a temporary location.
Step 2
Edit the parameters in this file.

For more information about these parameters, see Table 12-2 on page
12-16.
The edited file should look something like this:
# installation type (N-New, U-Upgrade)
AGENT_INST=N
export AGENT_INST
# CONTROL-M/Agent account name
AGENT_USER=aguser
export AGENT_USER
# service name under which the agent will run
AGENT_SERVICE=ctmagtrn2
export AGENT_SERVICE
# CONTROL-M/Server hostname
AGENT_SRV_HOST=TLVL2K300
export AGENT_SRV_HOST
# backup CONTROL-M/Server hostname
AGENT_SRV_BCKP_HOST=TLVL2K300
export AGENT_SRV_BCKP_HOST
# Agent-To-Server port
AGENT_AS_PORT=7005
export AGENT_AS_PORT
# server-To-Agent port
AGENT_SA_PORT=7006
export AGENT_SA_PORT
# Max connection retry numbers
AGENT_MAX_RETR=10
export AGENT_MAX_RETR
# Connection timeout
AGENT_TIMEOUT=120
export AGENT_TIMEOUT
# Time between connection retries
AGENT_TIME_BTW_RETR=2
export AGENT_TIME_BTW_RETR
12-14
# Default printer
AGENT_DEFLT_PRNT=lpr
export AGENT_DEFLT_PRNT
# use INETD(I) or XINETD(X) . XINETD supported only on Linux . Optional
INETD=X
export INETD
# Agent FD number
fd_value=FD5449
# Locale of CONTROL-M/Agent account. Optional
LOCALE=en_US
export LOCALE
Step 3
Specify the following command:

<cd_path>/cd_inst -a -f <input_file>
Where <cd_path> is the location where the CD was mounted, and

<input_file> is the name of the file edited in Step 2.
Step 4
The following message marks the completion of the installation

procedure:
CONTROL-M/Agent installation procedure completed
successfully.



Configuration.
12-15
Table 12-2
CONTROL-M/Agent for Unix Silent Installation Parameters

(Part 1 of 2)
Parameter
Description
AGENT_INST
Mandatory. Valid values:

N new installation
U upgrade
AGENT_USER
Unix Agent username for the account in

which to install CONTROL-M/Agent.
Mandatory.
AGENT_SERVICE
Agent service name to be recorded in the

/etc/inetd.conf file.
If NIS is used at your site, specify the
service name recorded in the NIS services
map. See Configure NIS on page 12-4.
AGENT_SRV_HOST
Host name of the computer where

CONTROL-M/Server is installed.
AGENT_SRV_BCKP_HOST
Host name of the computer where the

backup CONTROL-M/Server is installed.
Specify none if you do not want to provide a
value for this parameter.
AGENT_AS_PORT
Agent-to-Server Port Number
AGENT_SA_PORT
Server-to-Agent Port Number
AGENT_MAX_RETR
Maximum number of attempts to reconnect

to CONTROL-M/Server when
communication fails.
AGENT_TIMEOUT
Timeout
AGENT_TIME_BTW_RETR
Time Between Retries
AGENT_DEFLT_PRNT
Default Printer
INETD
XINETD
If INETD is used on the current computer,

specify I for this parameter.
If XINETD is used on the current Linux
computer, you must specify this parameter
with a value of X.
fd_value
Indicates the serial number for the current

version of CONTROL-M/Agent for Unix.
For version 6.1.03, this parameter must
specify FD5449.
12-16
Table 12-2
CONTROL-M/Agent for Unix Silent Installation Parameters

(Part 2 of 2)
LOCALE
Optional. Indicates language compatibility.

For example, for American English, specify
en_US.
Note: This parameter can be used to
implement any LOCALE that is compatible
with LATIN1 languages.
Changes to System Files

The installation procedure modifies system files as follows:
Note
This information is for your information only. It describes actions that are
performed automatically by the CONTROL-M/Agent installation.
1. The following line is added to the /etc/inetd.conf file:
<service> <socket_type> tcp nowait root
<agent_exe> p_ctminetd -e I <agent_home>/ctm
Table 12-3 describes the variables in this line.

Table 12-3
Configuration CONTROL-M/Agent for Unix
<service>
Agent service-name specified during installation.

Default: ctmagent
<socket_type>
Socket type used for the service (stream for tcp).
<agent_exe>
Path of CONTROL-M/Agent executable files.
<agent_home>
Path of CONTROL-M/Agent user home directory.
2. If NIS is not used at your site, the following line is added to file
/etc/services:
<service> <port_number>/<protocol> #CONTROL-M Agent
12-17
Table 12-4 describes the variables in this line.

Table 12-4
Service Definition CONTROL-M/Agent for Unix
<service>
Agent service-name specified during installation.

Default: ctmagent
<protocol>
Protocol used for communication between the Server

platform and the Agent platform (TCP only).
<port_number>
Value specified for Server-to-Agent Port Number.
3. [AIX]: The following lines are added to file /etc/rc.nfs:

#Refresh the inetd process
refresh -s inetd
#End refresh the inetd process
12-18
Table 12-5
Installation Parameters - CONTROL-M/Agent on Unix (Part 1 of 3)
Parameter or
prompt
Description
Products Available
on this Media
This menu is displayed immediately after you run the CD_INST command.
Choose option 2 to continue with the Agent installation.
CONTROL-M/Agent
will be installed in
the directory (
/home1/ctmagent )
This prompt specifies the directory where CONTROL-M/Agent will be

installed. To change the installation directory, change directory to desired
one and rerun CD_INST script.
Enter
CONTROL-M/Agent
UNIX username
Specify the Agents user name, or press <Enter> to accept the default.
CONTROL-M/Agent
Installation Menu
Use this menu to indicate if you are performing a new installation or upgrade
of an agent from an earlier version of CONTROL-M/Agent for Unix.
File: <file1> is not

symbolic-link to
<file2>.
Confirm to continue
(y/n):
For Solaris computers:

If a system file that is modified during the installation procedure is not a
symbolic link, this message is displayed.
All /etc files must be symbolic links to the /etc/inetd directory.
For more information, see Changes to System Files on page 12-17.
Specify n to stop and make the symbolic link manually. If you specify y to
continue, a message similar to the following is displayed:
Notice: File /etc/services will be changed.
Do you have xinetd

installed [Y/N]
(default N):
For Linux computers only:

This prompt is displayed if the installation program does not recognize the
Internet services daemon that is running on your system:
Note: If you do not know whether your system uses xinetd, consult your
system administrator. Usually, xinetd is installed in the /usr/sbin directory
and its configuration file is /etc/xinetd.conf.
Answer N if your system uses inetd.
If you answer Y, the following prompt is displayed:
Please enter the full path of the xinetd configuration
file:
Enter the path and name of the xinetd configuration file.
12-19
Table 12-5
Parameter or
prompt
Description
Enter the Agent

service-name:[ctma
gent]
Specify the service-name to be recorded in the /etc/inetd.conf file.

If NIS is used at your site, the value specified should be the service name
recorded in the NIS services map (see Configure NIS on page 12-4).
The definition for this service must also include the Server to Agent port
number (described below).
Server to Agent Port

number
The listening port in the Agent platform that receives data from the Server
platform. The value specified must match the value assigned to the
Server-to-Agent Port parameter (for this Agent) on the Server platform.
Verify that this port number is not used for any other purpose in this Agent
platform.
Default: 7006. Specify a numeric value from 1025 to 65535.
Use the following command to check if a specific port is available:
where <portnumber> is the number of the desired port. If this command
returns no result, the port is available.
Note: This prompt is not displayed if NIS is active on your computer. In this
case, the port number is read from the services file, and the specified values
are displayed for your information.
CONTROL-M/Server
Host Name
The host name of the computer on which CONTROL-M/Server is installed.
Authorized
CONTROL-M/Server
Host Name
Specifies one or more CONTROL-M/Servers that will be authorized to

submit jobs to this agent. Use '|' to separate between host names.
CONTROL-M/Server
Port (Agent to
Server)
The listening port in the Server platform that receives data from all Agent
platforms. The value specified must match the value assigned to the same
parameter on the Server platform. Verify that the specified port number is
not used for any other purpose in the Server platform.
Default: 7005. Specify a numeric value from 1025 to 65535.
Use the following command to check if a specific port is available:
where <portnumber> is the number of the desired port. If this command
returns no result, the port is available.
Default Printer Path
Default printer service for job output (sysout) files, as defined on the NIS
server or in the systems etc/services directory. Ask your system
administrator if your computer is supported by an NIS server.
Default: Blank.
12-20
Table 12-5
Parameter or
prompt
Description
Maximum Retries
Determines how many times the Agent should attempt to connect with the
CONTROL-M/Server computer.
It is recommended that you accept the default value for this parameter
during installation. You can change the value later to fine-tune performance.
Timeout
Determines the timeout for TCP/IP communications with

CONTROL-M/Server.
Time Between
Retries
Time period between communications retries.

Tracking Timeout
Do you want to
define non English
locale for
$username [Y/N] (
default N ):
Specify N to use English.

Specify Y to use any other Latin-1 language. You will be prompted to
enter the designation for the desired language.
12-21
12-22
13
CONTROL-M/Agent for Microsoft
Windows
13
This chapter describes how to install or upgrade CONTROL-M/Agent for

Microsoft Windows:
A non-interactive (silent) installation (not upgrade) is also available for
CONTROL-M/Agent for Microsoft Windows in this book. For more
information, see Chapter 14, Silent Installation of CONTROL-M/Agent
for Microsoft Windows.
Note
For information about modifying installation parameters after the

installation is complete, see Chapter 4 of the CONTROL-M/Agent for
Microsoft Windows Administrator Guide.
13-1
Working with Multiple Agents on the Same Computer
You can install more than one CONTROL-M/Agent on the same

computer. Considerations for this type of configuration are provided
below.
Why use multiple Agents?
With multiple agents, you can allow more than one CONTROL-M/Server
to request jobs on the same computer. In this type of configuration, each
CONTROL-M/Agent is associated with a different
CONTROL-M/Server.
Port numbers
Each agent must use a different Server-to-Agent port number. During

installation, it is important to record the port that you specified for each
agent. You will need this port number when you define the
communication for that agent in CONTROL-M/Server.
Agent names
Each CONTROL-M/Agent is identified by a logical name. This name is

used in the command line for CONTROL-M/Agent utilities to indicate
which agent should handle the command.
The default agent is always named Default.
Default Agent
During installation a checkbox in the Agent Name window enables you

to specify if you are installing the Default agent. If no specific agent
name is specified in a CONTROL-M/Agent utility command, the Default
agent handles the commands.
The Default agent is also the only agent that is able to work with
CONTROL-M/Control Modules, or CONTROL-M Options. If one or
more of these components will be used, the Default Agent must be
installed before the Control Module or the Option.
13-2
Upgrading
If an agent from an earlier version is upgraded to version 6.1.03, that

agent is automatically designated as the Default agent.
Considerations for Control Modules
CONTROL-M/Agents use Control Modules to interact with the operating

system and with other applications (for example SAP).
For new installations:
When CONTROL-M/Agent is installed, the Control Module for the
operating system (OS) is installed together with the Agent. If you intend
to install other CONTROL-M/Control Modules (for example, SAP, FTP,
or Oracle Applications), they must be installed after
CONTROL-M/Agent on the relevant computer.
For upgrade installations:
When CONTROL-M/Agent is upgraded from an earlier version, the
upgraded agent automatically becomes the Default agent. In this case, no
changes need to be made to CONTROL-M/Control Modules or Options
(even if they existed before the upgrade).
Note
CONTROL-M/Control Modules (aside from the Control Module for the

OS) and CONTROL-M Options can work only with the Default
CONTROL-M/Agent. If you plan to install one or more of these
components on this computer, the Default CONTROL-M/Agent must be
installed before the Control Module or the Option.
13-3
Installation or Upgrade on a Microsoft Windows Cluster Environment
Review the following notes if you will be installing CONTROL-M/Agent

in a Microsoft Windows cluster environment:
No automated procedure is provided for upgrade of

CONTROL-M/Agent from version 6.1.01 on a cluster enviroment. In
this case, you will need to manually record the values of your agent
configuration parameters, and then uninstall the old version. After
uninstallation in complete, you can install the new 6.1.03 agent and
apply the recorded configuration.
You must verify that a disk resource, IP resource, and network

resource exist and are online in the group where you will be
installing CONTROL-M/Agent.
Multiple Agents can be installed on the same virtual server group. Or

in separate virtual server groups.
Silent installation of CONTROL-M/Agent is not supported for

Microsoft Windows cluster environments.
Upgrade installation of a CONTROL-M/Agent cannot be performed

in a Cluster environment. Only new installations are supported.
Installing CONTROL-M/Agent
Step 1
Log on to a user account belonging to the local Administrators group.
Step 2
Insert the FD5305 installation CD in the CD-ROM drive.

If the Autorun option is enabled, installation starts automatically and the
opening screen is displayed.
13-4
Click CONTROL-M/Agent.
Note
If the Autorun option is not enabled, browse to the FD5448 directory on

the CD-ROM drive, and double-click Setup.exe.
Step 3

The parameters and fields for this installation are described in Table
13-1, CONTROL-M/Agent Installation Parameters, on page 13-5.
Table 13-1
CONTROL-M/Agent Installation Parameters (Part 1 of 4)
Parameter
Description
Agent Name
Logical name of this Agent installation. This name is used to differentiate between
multiple installations of CONTROL-M/Agent on the same computer.
Note: If the current installation should be used as the default agent on this
computer, select the Default Agent checkbox in the Agent Name window.
Setup Type
Indicates the type of agent installation:

Default The installation procedure automatically uses the default parameter
settings described in Appendix A, Configuration Parameters, of the
CONTROL-M/Agent for Microsoft Windows Administrator Guide.
The only value you can change during the default installation is the primary
CONTROL-M/Server host name. For information about modifying
CONTROL-M/Agent configuration parameters after installation, see Interactive
Utilities in Chapter 4 of the CONTROL-M/Agent for Microsoft Windows
Custom Enables you to specify custom configuration for CONTROL-M/Agent.
Destination
Folder
Indicates the location in which the agent will be installed.

To change the installation directory, click Change and Browse to the desired
location.
Note: To install the CONTROL-M/Agent in a non-default directory, you must ensure
that this directory exists before running the installation procedure.
Primary
CONTROL-M/
Server Host
Indicates the hostname (not IP address) of the computer where

CONTROL-M/Server is installed.
Name (not IP address) of the computer hosting the CONTROL-M/Server that
receives and executes requests from this Agent.
Default: Computer on which the installation was made.
13-5
Table 13-1
Parameter
Description
Authorized
CONTROL-M/
Server Hosts
Names of all CONTROL-M/Server hosts authorized to send requests to this Agent,

including backup hosts. The primary CONTROL-M/Server host must be included if it
will send requests to this Agent. Use the | symbol to separate host names. Do not
include spaces between host names. Default: Name of the primary
CONTROL-M/Server host.
Note: Specify names, not IP addresses.
Agent-toServer
Port Number
Listening port in the Server computer that receives data from all Agent computers.
The value specified must match the value assigned to the Agent-to-Server Port
Number parameter on the Server computer. Verify that this port number is not used
in the Server for any other purpose. Specify a numeric value between 1025 and
65535. Default: 7005
Server-toAgent
Port Number
Listening port in this Agent computer that receives data from the Server computer.
The value specified must match the value assigned to the Server-to-Agent Port
Number parameter (for this Agent) on the Server computer. Verify that this port
number is not used for any other purpose in this Agent computer. Specify a numeric
value between 1025 and 65535. Default: 7006
TCP/IP
Timeout
Communication timeout in seconds. Specify a numeric value greater than or equal

to zero. Default: 60.
Default
Printer
Default printer for job sysout files. Type a printer name in the field box or select a
name from the list box. Default: Blank.
Logon
Domain
Domain where the logon is performed. Optional. Valid values:

A name you type in the field box or select from the list box. Account databases in
the specified domain are searched.
<.> (period). Only the local account database is searched,
<blank>. The local account database and all trusted domain account databases
are searched. Default.
Domain
Controller
Name of server managing access to resources and the database. Default: Blank.
Logon As
User
Indicates what environment will be used to run CONTROL-M jobs.

Selected Jobs run in using the environment of the job owner. In this case, the
job owners of the jobs to be run must have logon as batch job user rights.
Not selected Jobs are use the environment of the Agent service (Local System
Account, or This Account). For more information, see Logon As later in this table.
Default.
Add Job
Object
Statistics to
Sysout
Indicates how to handle job object processing statistics.

Selected Statistics are added to the sysout log file. Default.
Not selected Statistics are not added to the sysout log file.
13-6
Table 13-1
Parameter
Description
Clustering Parameters
Clustering supports several processors with a virtual addressing scheme.
Select a
group
Highlight one of the virtual server groups in the list. This is the group for which you
will select a Disk resource, IP resource, and Network resource.
Select the
Disk resource
Select one of the Disk resources that is available for the selected group.
Select the
Network
resource
Select one of the Network resources that is available for the selected group.
Cluster
Management
This display-only field indicates the order in which clusters will perform failover
handling.
Windows Service Definition Parameters

If the owner of any CONTROL-M jobs has a roaming profile and the Logon as User option was
selected as part of the clustering parameters, the Log On As field must be set to This Account.
If job output (sysout) will be copied to or from other computers, this field must be set to This
Account. Otherwise, the (local) System account logon mode is recommended.
Startup
Type
Specifies how the CONTROL-M/Agent service will be started. It is recommended

that you install CONTROL-M/Agent as an automatic service. Options for this field
are:
Automatic
The service starts when the system starts. Default.
Manual
Can be started by a user or a dependent service.
13-7
Table 13-1
Parameter
Description
Log On As
Specifies the name of the user that will be used to run

CONTROL-M/Agent.
System
Account
The service will log on to the system account rather than a user
account. CONTROL-M/Agent service runs using the native
system account environment. Default.
Allow Service to Interact with Desktop - Check this option to
allow CONTROL-M jobs to activate GUI-based applications (for
example, notepad.exe). The desktop interface can be used by
whoever is logged in locally when the service is started. Default.
This Account
Indicates a specific user and password under which the

CONTROL-M/Agent service will run. Specify a user with full
privileges in the Administrative group, including the following
privileges:
logon as batch job
increase quotas
logon as a service
This field must include the domain as well as the user name, in
the format: <domain>\<user>
13-8
Importing WIN Panel Functionality

Use the following procedure to ensure that Microsoft Windows job
parameters will be displayed in the Job Editing form in
CONTROL-M/EM and CONTROL-M/Desktop.
Note
This procedure must be performed on every computer that has

CONTROL-M/EM client component(s) installed.
Step 1
Ensure that the CONTROL-M application CD FD5448 is on a mapped

drive.
Step 2
In CONTROL-M/Desktop, choose Tools => Import Applications

Forms.
Step 3
A browse window is displayed. Navigate to the Forms directory on the

application CD.
Step 4
Select the windows.xml file, and click Import.
Step 5
Shut down and restart CONTROL-M/EM.

To install other CONTROL-M products in your scheduling solution,

continue with the installation procedure in the appropriate chapter of
this book.

in your solution, proceed to the Chapter 15, Post-Installation
Configuration.
13-9

Step 1

of Agent Platform:
Step 2

Step 3


Configuration.
13-10
14
Silent Installation of
CONTROL-M/Agent for Microsoft
Windows
14
Use the silent installation procedure to perform an installation without

user interaction.
The batch file that runs this procedure resides on the installation CD. You
can customize the installation parameters by modifying the batch file.
Interactive installation of CONTROL-M/Agent for Microsoft Windows is
described in Chapter 13, Installing or Upgrading CONTROL-M/Agent
for Microsoft Windows.
Before You Begin
Ensure that your computer meets the requirements described in Chapter

4, Pre-Installation Steps on Microsoft Windows.
14-1

Summary:
Step 1
Step 2
Use the following steps to modify the batch file and then run the
modified silent installation procedure:
Using Windows Explorer, select the CD-ROM drive and under
<Drive_ID>, browse the FD5448 directory.
To run a default silent installation, double-click the silent.bat file.

Skip to Step 7 on page 14-4 for subsequent steps. (For information
about the default settings, see Batch File Installation Default
Settings on page 14-6.)
To modify the batch file before running it, right-click the silent.bat
file. Select Edit from the popup menu, and continue with Step 2
(below).
The batch file is displayed in the default text editor, as in the following
example.
set
silent_log_file="%temp%\FD5448_Agent_silent_log.txt"
set silent_install_command=msiexec
REBOOT="ReallySuppress" /i "%~dp0CONTROL-M Agent
6.1.03.msi" /qn AGENT_NAME=""
CLUSTER_SETUP_TYPE="LOCAL" AG_SRV_USER="LocalSystem"
/l*v %silent_log_file%
Step 3
In the batch file, change the line

set silent_install_command=msiexec /i
"%~dp0CONTROL-M Agent 6.1.03.msi" /qn ...
to
"<Drive_ID>\FD5448\CONTROL-M Agent 6.1.03.msi"
/qn ...
Where <Drive_ID> is the location of the installation CD.

14-2
Step 4
Add parameters and their values to the following line of the file.
For example:
"<Drive_ID>\FD5448\CONTROL-M Agent 6.1.03.msi" /qn
<parameter>="<value>" <parameter>="<value>" /l*v
%silent_log_file%
Syntax rules
The parameters are inserted between the /qn term and the /l*v term.
Actual values must be enclosed in quotes.
A single space is used to separate parameters.
Note
If an optional parameter is not specified, the default value is used.

For more information about these parameters, see Table 14-1 on page
14-6.
If you are installing multiple agents on the same computer, you will need
to specify different values for the AGENT_NAME, AG_AGCMNDATA_VAL,
and TRACKER_EVENT_PORT parameters for each non-default agent on
that computer.
Step 5
After editing is complete, save the silent.bat file to a temporary

directory.
Step 6
To run the silent installation, browse to the temporary directory, and

double-click the silent.bat file.
14-3
Step 7
When installation is complete, CONTROL-M/Agent is added to the

Microsoft Windows Start =>Programs menu.
The following log file is created by the silent installation procedure:
%temp%\FD5448_Agent_silent_log.txt
Check this log file to verify successful installation.
Note
The same batch file can be copied to other computers and used to create
several identical installations. (You may have to update the ID of the
CD-ROM drive if it is mapped differently on the other computers.)
See Table 14-1 on page 14-6 for installation parameters and their
default settings.
Sample batch files are shown on page 14-9.



Configuration.
14-4

Step 1

of Agent Platform:
Step 2

Step 3


Configuration.
14-5
Batch File Installation Default Settings
Table 14-1 indicates the batch file default installation parameter settings.
These settings are used if any parameter is not specified in the batch file.
Table 14-1
Param.
Description
INSTALLDIR
Name of the installation directory. Default:

<Drive_ID>\Program Files\BMC Software\ CONTROL-M Agent\
where <Drive_ID> identifies the drive where Program Files are
defined in this computer
AG_CTMSHOST_VAL
Name of host computer for the primary CONTROL-M/Server that

handles this Agent. Default: Name of the computer where
installation is performed.
Note: Specify a computer name, not an IP address.
AG_CTMPERMHOSTS_VAL
List of authorized CONTROL-M/Servers, including the primary

CONTROL-M/Server. These hosts are all authorized to submit jobs
for processing. Syntax: host1|host2|...|hostn. The separator is a
vertical line. Embedded blanks are not allowed.
Example, TLVS2K038|VGW1K|FPB62G
Note: Specify a computer name, not an IP address.
AG_ATCMNDATA_VAL
Port number used by the CONTROL-M/Server platform for

receiving data from the CONTROL-M/EM platform (Agent-to-Server
port number). Default: 7005
AG_AGCMNDATA_VAL
Port number used by the CONTROL-M/EM platform for receiving

data from the CONTROL-M/Server platform (Server-to-Agent port
number). Default: 7006
AG_AGENT_TIMEOUT
TCP/IP Timeout (in seconds). Valid values: numeric value greater

than or equal to zero. Default: 60
AG_GON_AS_USER_VAL
Job submission method. Valid values:

Y Jobs are submitted only under the user and password
specified in the product registry. The CTMPWD utility is used to
set the user and password.
N Jobs are submitted under the current user and password.
Default.
14-6
Table 14-1
Param.
Description
AG_DOMAIN_VAL
Domain from which the log on will be performed. Valid values:

<domain_name>
The domain name.
" " (Blank)
The local account database and

all trusted domain account
databases are searched. Default.
. (period)
Specify a period to search only

the local account database.
AG_DFTPRT_VAL
Default printer for job output (sysout) files. Specify a printer name.
AG_DOMAIN_SERVER_VAL
Domain controller. Specifies the name of the server managing

access to the available resources and database.
AG_JO_STATISTIC_VAL
Flag that indicates whether job object statistics are sent to sysout.
Valid values:
Y Job object statistics are sent to sysout. Default.
N Job object statistics are not sent to sysout.
AGENTSERVICESTARTUPTYPE
CONTROL-M Agent service and CONTROL-M Tracker service start
up method. It is recommended that these services be started as
automatic services. Specify one of the following:
LOGONACCOUNTTYPE
SERVICE_AUTO_START
Services should start when the

system starts. Default.
SERVICE_DEMAND_START
Services can be started by a

user or a dependent service.
User account under which the CONTROL-M Agent and

CONTROL-M Tracker services will run.
Valid values:
1 The services log on to the local system account, rather than a
user account. The services will run using the native system
account environment with full privileges in the administrative
group. Default.
0 Specific user and password under which the services will
run. Specify a user account with full privileges in the
administrative group.
14-7
Table 14-1
Param.
Description
AGENTSERVICEINTERACTIVEDESKTOP
Service interacts with Desktop Specify whether the service
provides a user interface on a desktop that can be used by whoever
is logged in when the service is started. Valid values:
SERVICE_INTERACTIVE_PROCESS Permit interaction with
the desktop. Default.
" " Blank, do not permit interaction with the desktop.
Note: This option can be used only if the service runs as a local
system account (defined by specifying LOGONACCOUNTTYPE=
"1", see above).
AG_SRV_USER
User under which the CONTROL-M/EM service will run. Specify a

user account with full privileges in the administrative group, for
example, user_company.com\user.
Note: This option can be used only if the service is set to run under
a specified user account (defined by specifying
LOGONACCOUNTTYPE="0", see above).
AG_SRV_PASS
User password.
AG_SRV_PASS_CONF
User password confirmation.
TRACKER_EVENT_PORT
The tracker event port enables COTNROL-M/Agent to receive

updates regarding job status from all Control Modules that are
associated with the current CONTROL-M/Agent.
Default: 7009
AGENT_NAME
Logical name of this Agent installation. This name is used to

differentiate between multiple installations of CONTROL-M/Agent
on the same computer.
14-8
Sample Batch Files for Silent Installation

Note
In the examples below, some parameters may be set on separate lines for
clarity, in actual batch files, all the parameters make up a single long line
of code, separated by single spaces.
Example 1
Modify the silent installation batch file by setting the Agent-to-Server

and Server-to-Agent port numbers to 7010 and 7011, respectively, and
setting the Agent service start-up type to start manually, as follows:
rem ** CONTROL-M/Agent 6.1.03 Silent Installation **

"<Drive_ID>\FD5448\CONTROL-M_Agent.msi"
/qn AG_AGCMNDATA_VAL="7011" AG_ATCMNDATA_VAL="7010"
AGENTSERVICESTARTUPTYPE="SERVICE_DEMAND_START"
Example 2
Modify the silent installation batch file by setting the service logon
account type to disable interaction with the desktop. Set the primary
CONTROL-M/Server host to HOST_A1. Set the authorized
CONTROL-M/Servers permitted to handle the Agent, HOST_A1,
HOST_A2, and HOST_A3.

"<Drive_id>\FD5448\CONTROL-M Agent.msi" /qn
AGENTSERVICEINTERACTIVEDESKTOP=""
AG_CTMSHOST_VAL="HOST_A1"
AG_CTMPERMHOSTS_VAL="HOST_A1|HOST_A2|HOST_A3"
14-9
Example 3
Modify the silent installation batch file by setting the service logon
account type to Logon As User account and by specifying user andy
(domain andrew.com), with password advance24:

"<Driver_ID>\FD5448\CONTROL-M Agent.msi" /qn
LOGONACCOUNTTYPE="0" AG_SRV_USER="andrew.com\andy"
AG_SRV_PASS="advance24" AG_SRV_PASS_CONF="advance24"
14-10
15
15
After you have installed all the necessary CONTROL-M products at your
site, there are certain configuration tasks that must be performed. These
tasks ensure that the various elements of the CONTROL-M scheduling
solution are active and able to communicate with each other.
15-1
Step 1 On Unix Computers

Perform the following steps on each Unix computer on which you
installed CONTROL-M components:
1.0.1
Log in to the unix account for CONTROL-M/EM.
Step 1.1 Check the Database Server

1.1.1
If the Database was installed on Unix, use one of the following

commands to verify that the database server is active:
For Sybase: isql -U <em_user> -P <password>

For Oracle: sqlplus <em_user>/<password>
where <em_user> is the user name under which CONTROL-M/EM was

installed, and <password> is that users password for CONTROL-M/EM
(Default: empass).
If the database server is active an appropriate prompt is displayed.
1.1.2
Type quit to exit the database server.
Step 1.2 Start CONTROL-M/EM Components

1.2.1
Use the following steps to verify that the Orbix service is active.
A:
Enter the root_menu command.
B:
You are asked for the CONTROL-M/EM user name and password.
Enter them in order to continue.
C:
Select and display the Activation Menu from the list of available
menus.
D:
Select the Check All option.
15-2
1.2.2
Select the Start All option from the Activation Menu (the same menu as
in the previous step) to activate the CONTROL-M/EM components.
Step 1.3 Starting CONTROL-M/Server

Before starting CONTROL-M/Server, verify that:
You are logged in as the CONTROL-M/Server user.
The Sybase or Oracle database server used for the

CONTROL-M/Server database is running. (You can check this using
the Check All option in the CONTROL-M Manager menu - accessed
using the ctm_menu command.)
If database mirroring was initialized in a different window during the

current session, open a new shell by specifying the command: csh
Note
You can also start CONTROL-M/Server using the CONTROL-M

Manager menu. For more information see the CONTROL-M/Server for
Unix Administrator Guide.
Use the following command to start CONTROL-M/Server:

start_ctm
During startup, the following message may appear:

Check ctm/prflag/SU file, or run init_prflag on CTM
server.
If this message is displayed, specify the following commands:

shut_ctm
init_prflag
start_ctm
15-3
Step 1.4 Check the CONTROL-M/EM to CONTROL-M Port

Number
In this step, you will get the number of the port that is used by
CONTROL-M/Server to listen for communication from
CONTROL-M/EM. This number will be needed later (when creating a
CONTROL-M definition in CONTROL-M/EM).
1.4.1
Enter the following command, to open the CONTROL-M main menu:

ctm_menu
1.4.2
The following menu is displayed:

CONTROL-M Main Menu: Select one of the following menus:
1 - CONTROL-M Manager
2 - Database Creation
3 - Database Maintenance
4 - Database Mirroring
5 - Security Authorization
6 - Parameter Customization
7 - Node Group
8 - Agent Status
9 - Troubleshooting
q - Quit
15-4
1.4.3
Choose option 6 to display the Parameter Customization menu.

Parameter Customization Menu
----------------------------Select one of the following options:
1
2
3
4
Communication and Operational Parameters

System Parameters and Shout Destination Tables
Default Parameters for Communicating with Agent Platforms
Parameters for Communicating with Specific Agent Platforms
q - Quit
1.4.4
Choose option 1 (Communication and Operational Parameters). The

following menu is displayed:
Communication Parameters:
1)
2)
3)
Local IP Host Interface Name:

Agent-to-Server Port Number:
Communication Protocol:
a)
q)
n)
Modify all of the above

Quit
Next page
Enter command or item number you wish to change [n]:
Enter n, to display the Operational Parameters menu.

Operational Parameters:
1.4.5
1)
2)
3)
4)
5)
6)
7)
Input Process Communication Port Number:

Maximum Job State Changes:
CONTROL-M/EM TCP/IP Port Number:
Statistics Mode:
CONTROL-M/EM RELVER param:
Maximum server processes (CS):
Minimum server processes (CS):
a)
p)
q)
Modify all of the above.

Previous
Quit
Note the value of option 3 (CONTROL-M/EM TCP/IP Port Number).

You will need to specify this port number later when creating a
CONTROL-M definition in CONTROL-M/EM.
15-5
Step 2 On Microsoft Windows Computers

Step 2.1 Register CONTROL-M/EM Server Components
2.1.1
On the Windows desktop, click the Administration Facility icon.
2.1.2
Specify the username and password for the CONTROL-M/EM Database

administrator, and click Login.
2.1.3
The Administration Facility window is displayed.
15-6
2.1.4
Choose Component => New Component from the menu.
A:
In the Type field, choose GUI Server to register the

CONTROL-M/EM GUI server.
B:
In the Machine Type field indicate the type of computer on which

the GUI server was installed. (Unix or Windows).
Note: Specify Windows for the GUI server on any Microsoft
Windows operating system (including Windows 2000).
C:
In the Machine name field specify the host name of the computer on
which you installed the CONTROL-M/EM GUI server.
D:
Set the Desired State to UP.
For more information about this dialog box, see Chapter 3 of the
CONTROL-M/Enterprise Manager Administrator Guide.
2.1.5
Repeat Step 2.1.4 to register the Global Alert Server (GAS).
2.1.6
Repeat Step 2.1.4 to register the Global Condition Server (GCS).
15-7
Step 2.2 Create CONTROL-M Definitions in CONTROL-M/EM

2.2.1
On the Microsoft Windows desktop click the CONTROL-M/EM icon:
2.2.2
Enter the CONTROL-M/EM username and password. You are also

requested for the Hostname. This refers to the hostname of the computer
on which you installed the CONTROL-M/EM GUI Server.
2.2.3
Use the following steps to create a CONTROL-M definition for each

CONTROL-M/Server that will communicate with CONTROL-M/EM.
A:
Choose Tools => Communication => Administration. The

Communication Administration window is displayed.
15-8
B:
Click New. The CONTROL-M Definition window is displayed.
C:
Fill in all mandatory fields in this window.
Specify the port number (default: 2370) that is used by

CONTROL-M/Server to listen for communication from
CONTROL-M/EM. (This is the port number that was checked
earlier in Step 1.4 on page 15-4.)
Ensure that the Enable checkbox in the upper left-hand corner of

the CONTROL-M Definition window, is selected.
15-9
Step 2.3 Register Gateways for Communication With

CONTROL-M/Server
2.3.1
Return to the Administration Facility window.
2.3.2
Choose Component => New Component from the menu bar. The
Component dialog box is displayed.
A:
In the Type field, choose Gateway.
B:
In the Name field choose the same name as the CONTROL-M name
defined in Step C on page 15-9.
C:
Set the Desired State to UP.
D:
In the Machine name field, specify the host name of the computer
on which you installed the GUI server.
For more information about the fields in this dialog box, see Chapter 3 of
the CONTROL-M/Enterprise Manager Administrator Guide.
15-10
Step 2.4 Create CONTROL-M Definitions in

CONTROL-M/Desktop
In this step you will create a separate CONTROL-M definition with the
same properties for each CONTROL-M that was defined in Step 2.2.3 on
page 15-8.
This will ensure that CONTROL-M/Desktop will allow creation of job
processing definitions for the CONTROL-M/Server.
2.4.1
Click
to open CONTROL-M/Desktop.
Repeat Step 2.4.2 through Step 2.4.5 for each CONTROL-M/Server that
will communicate with CONTROL-M/EM.
2.4.2
Select Edit => CONTROL-M Definitions. The following window is

displayed:
2.4.3
Click Add. The following dialog box is displayed:
15-11
2.4.4
Fill in the fields in this dialog box as described in the following table.
Table 15-1
Fields in the CONTROL-M Dialog Box
Field
Description
Name
Name of the CONTROL-M. You must use the same name as

was specified for this CONTROL-M when it was defined for
CONTROL-M/EM (in Step 2.2 on page 15-8).
Type
Type of computer on which the CONTROL-M is installed.
Version
Version of the CONTROL-M at the specified installation.
Uppercase
Only
Indicates if all parameters in the Job Editing form for this

CONTROL-M must be in uppercase. For most installations this
option should not be selected.
Start Day of
the Week
Indicates the first day of the week for use in the Week Days
field in the Job Editing form.
Note: This field is used to ensure that the display of calendars
for this CONTROL-M is properly adjusted. Use the ctmsys
utility to ensure that the start day of the week for the
CONTROL-M installation is the same as in this field.
Installed
Products
For OS/390 (MVS) platforms only:

Indicate which other INCONTROL products are installed with
CONTROL-M on the OS/390 platform.
2.4.5
Click OK to add the CONTROL-M to CONTROL-M/Desktop.
2.4.6
After all CONTROL-M installations have been defined, click OK to save

the changes and close the CONTROL-M Definitions window.
15-12
Step 2.5 Show Extra Keyboard Help in Programs

For CONTROL-M/EM components installed on
Microsoft Windows 2000 computers:
The Microsoft Windows 2000 Show Extra Keyboard Help in Programs
feature is supported by CONTROL-M/EM. When this feature is disabled
(the default setting), you must press Alt to enable the access keys for
menus and buttons. When the feature is enabled, the access keys are
identified by an underline under the appropriate letter.
To enable this feature:
2.5.1
Choose Start => Settings => Control Panel to display the Control
Panel.
2.5.2
Double-click the Accessibility Options icon to display the Keyboard

panel of the Accessibility Options window.
2.5.3
Select the Show Extra Keyboard Help in Programs check box.
2.5.4
Close the Accessibility Options window and the Control Panel.
Step 3 Check Communication with

CONTROL-M/Agent
Use the following steps on Unix or Windows to check communication
between CONTROL-M/Server and CONTROL-M/Agent:
Note
If the responses to the commands below indicate that communication is

not working. Verify that the same port numbers were specified for this
communication in the CONTROL-M/Server and CONTROL-M/Agent.
3.0.1
Run the following command from the CONTROL-M/Server account or

computer:
15-13
ctm_diag_comm <agentname>
Output similar to the following is displayed:

Executing ctmping <agentname>
CONTROL-M/Server to CONTROL-M/Agent Communication Diagnostic Report
------------------------------------------------------------------CTMS User Name
:
CTMS Local IP Host Interface Name :
CTMS Platform Architecture
:
FD Number
:
Server-Agent Comm. Protocol
:
Agent Platform Name
:
Agent Status
:
:
:
Unix ping to Agent Platform
:
ctmping to agent
:
3.0.2
ctmserveruser
<servername>
Solaris
FD5335
TCP
<agentname>
available
7006
7005
Succeeded
Succeeded
Run the following command from the CONTROL-M/Agent account or

computer:
ag_diag_comm

This procedure runs for about 30 seconds. Please wait
CONTROL-M/Agent Communication Diagnostic Report

----------------------------------------------Agent User Name
Agent Platform Architecture
FD Number
Agent Version
Agent Platform Name
Server Host Name
Authorized Servers Host Names
Server-Agent Comm. Protocol
Unix Ping to Server Platform
Agent Ping to Control-M/Server
NIS is
NIS Service Name
NIS Protocol
Service "ctmagtrn2" is
Netstat protocol
Protocol consistency check
15-14
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
<agentuser>
Solaris
FD5449_AGENT
6.1.03
<agentname>
<ctmservername>
<ctmservername>
7006
7005
tcp
Succeeded
Succeeded
Running
ctmagent
tcp
Active
tcp
Ok
16
Troubleshooting
16
This chapter describes various problems that you may encounter during
installation of CONTROL-M products, and how to resolve them.
The troubleshooting procedures in this chapter are divided into the
following categories:
CONTROL-M/EM Installation on Unix

CONTROL-M/Server for Unix
Oracle Database Cleanup
Sybase Database Issues
Troubleshooting
16-1
CONTROL-M/EM Installation on Unix

If the installation of CONTROL-M/EM and/or Sybase Server fails, the
following procedures can help you correct installation problems.
Error messages during installation
The following table describes various messages that may appear during
installation and how to handle them.
Table 16-1
CONTROL-M/EM Installation Error Message Handling
Message
Response
The CONTROL-M/EM account

contains one or more files.
Do you want to continue with the
installation? (Y/N)[n]:
These messages may be displayed if a previous installation

was aborted, leaving files in the CONTROL-M/EM directory.
If you did not previously install CONTROL-M/EM on this
computer, OR if CONTROL-M/EM was installed with a
Sybase database server, specify y and continue the
installation.
If this message is displayed after an aborted installation,
specify n to exit the installation and remove the files as
described below.
To remove files from the aborted installation:

1. Specify the following command:
clean_ora_inst.sh <DB_owner> <DB_pwd>
<DB_name>
where <DB_owner>, <DB_pwd>, and <DB_name> are
the owner, password, and database name specified
during Oracle database installation.
The clean_ora_inst.sh script deletes old Oracle
installation files and removes CONTROL-M/EM tables
from the database. If you wish to delete old installation
files but retain existing CONTROL-M/EM database
tables, specify the following command instead:
rm_ctmem_dirs.sh
2. Restart the installation procedure.
Note: If you are using an Oracle database server, do not
remove the tmp and oracle directories or the .oraenv.sh
and .oraenv.csh files, which were created during Oracle
installation.
16-2
Configure the Orbix Server
The Orbix Server should have been configured when it was installed.
However, if a message was displayed during installation that indicated
that there was a problem, you must configure the Orbix Server
interactively using the configure script, or silently using the default
Orbix configuration file.
To run the configure script, type configure at the prompt and press
<Enter>. You must answer a series of questions that are displayed. The
script is located in the $IT_PRODUCT_DIR directory.
Note
The default configuration file, orbix_prep_file, is located in the

$HOME/appl/lib/bin.<uxtype>/Orbix/ directory (Where <uxtype> is
hp10 for HP-UX, ibm4 for AIX, or sparc for Solaris).
To run configure silently, use the following command:
configure -useprep
$HOME/apple/lib/bin.<uxtype>/Orbix/orbix_prep_file
Cleanup After an Aborted Installation
If you quit CONTROL-M/EM installation before it completed, or if the

installation failed, you will need to clean up certain files and processes
before restarting the installation process.
Use the following steps to clean up leftovers from an aborted installation.
Step 1
Use the following command to check for CONTROL-M/EM processes

that were started during the aborted installation:
ps -ef | grep <install_dir>
Where <install_dir> is the home directory of the installation account.

Step 2
If any such processes are found, use the following command to stop each
of them:
Troubleshooting
16-3
kill <process_ID>
Note
For installations using an Oracle database server, do not stop the

LSTNR_<instance_name> process or any Oracle processes, which
begin with the prefix ora_ .
Step 3
For installations using an Oracle server:

3.A
Navigate to the CONTROL-M/EM user home directory.
3.B
Use the following command to delete any user tables created by

the aborted installation:
clean_ora_inst.sh <ora_usr> <ora_pwd> <ora_sid>
Where:
<ora_usr> is the CONTROL-M/EM user name specified in

the aborted installation (Default: emuser)
<ora_pwd> is the CONTROL-M/EM user password
specified in the aborted installation (Default: empass)
<ora_sid> is the Database Instance Name specified in the
aborted installation
The tmp and oracle subdirectories are not cleared, because they contain
files needed by the Oracle database server.
Note
The clean_ora_inst.sh script deletes old installation files and removes

CONTROL-M/EM tables from the database. If you wish to delete old
installation files but retain existing CONTROL-M/EM database tables,
specify the following command instead:
rm_ctmem_dirs.sh
16-4
Step 4
Before repeating the installation procedure, exit the current terminal

environment and open a new terminal environment. Begin the new
installation procedure from the new environment.
Note
If you copied the CONTROL-M/EM installation CD to an installation

directory using the COPY_FROM_CD command, you do not need to
remove this directory. You can use this same directory as is for your
next run of the installation process.
Note
When you reinstall CONTROL-M/EM, you must supply the same

CONTROL-M/EM password that you specified during the aborted
installation.
Troubleshooting
16-5
CONTROL-M/EM Installation on Microsoft

Windows
Truncated Environment Path
During CONTROL-M/EM installation, variables are added to the

beginning of the Microsoft Windows environment path. If these additions
result in a path containing more than 1,023 characters, characters beyond
the 1,023rd are truncated.
Solution:
Although the path is truncated, the full path statement is saved to a text
file in the CONTROL-M/EM home directory. This file is called
__prevpath.txt. You can recover all path statements from this file
MSSQL Memory Management
MSSQL Server 2000 may consume a large number of system resources

(memory) when managing the CONTROL-M/EM database.
Use the following steps to limit the amount of memory used by the
CONTROL-M/EM database:
16-6
Step 1
Choose Start => Programs => Microsoft SQL Server => Enterprise
Manager. The SQL Server Enterprise Manager window is displayed.
Step 2
Choose Tools => SQL Query Analyzer. The SQL Query Analyzer
window is displayed.
Troubleshooting
16-7
Figure 16-1 SQL Query Analyzer Window
Step 3
In the upper frame of this window, specify the following command:

sp_configure "max server memory","<n>"
where <n> is half the RAM (in MB) on your computer.
Step 4
On the next line, type:

reconfigure
Step 5
Click
to submit the commands.
The following message is displayed in the bottom frame of the window

of the SQL Query Analyzer window:
DBCC execution completed.
Configuration option changed. Run the RECONFIGURE
statement to install.
16-8
It is not necessary to run the Reconfigure command a second time. This

was already handled in the previous step.
Step 6
Exit the SQL Query Analyzer window.
Troubleshooting
16-9
Check Startup Options for CONTROL-M/EM Services

Depending on which components were installed on the computer, all or
some of the Services listed in Table 16-2 are added to the computer.
Table 16-2
CONTROL-M/EM Services
Service
Component
IT iona_services.locator.<domain> OrbixE2A
Orbix E2A Server
IT iona_services.naming.<domain> OrbixE2A
IT iona_services.node_daemon.<domain> OrbixE2A
NuTCRACKER Service
Gateway, Global Conditions Server
CONTROL-M/EM Administration Agent
This service should be listed if one or

more of the following components is
installed:
GUI Server, gateway, Global Conditions
Server, and Global Alert Server
OracleEM920EM6131TNSListener
Oracle Database Server - Oracle

installations only. These services are
added to the computer during Oracle
database installation.
OracleServiceEM613
These services should start automatically with system boot.

To enable these services to start automatically:
Step 1
Choose Start => Settings => Control Panel => Administrative

Tools => Services.
Step 2
Verify that for each CONTROL-M/EM service the Status column

indicates Started, and the Startup column indicates Automatic.
Step 3
If the startup column for one of these services indicates Manual,

double-click the entry and change the startup setting to Automatic.
16-10
Services that do not need to be started automatically
For installations using an Oracle database server, additional services are

added to the computer, but are not required to be up and running
following reboot. For all CONTROL-M/EM installations, the following
service is added:
OracleEM920EM6131ClientCache
For installations including CONTROL-M/EM server components, the

following services are added:
OracleEM920EM613ClientCache
OracleEM920EM613Agent
OracleEM920EM613DataGatherer
OracleEM920EM6131HTTPServer
OracleEM920EM6131PagingServer
OracleEM920EM6131SNMPPeerEncapsulator
OracleEM920EM6131SNMPPeerMasterAgent
Note
All these services should remain in Manual mode.
Troubleshooting
16-11
CONTROL-M/Server for Unix

Common Installation Problems
Table 16-3 describes common installation problems and diagnostic

procedures.
Table 16-3
CONTROL-M/Server for Unix Troubleshooting
Problem
Solution
After running the CD_INST script,

installation files did not load
completely.
Perform the following checks:

Do you have sufficient disk space on your computer?
Was the installation CD was removed by mistake?
Specify the CD_INST command again.
After running the install/custom

script, you decided to quit the
installation without building the
database.
Your parameter changes up to the point you quit are retained.

When you wish to complete the installation, rerun the script
from the home directory of the CONTROL-M user account.
Installation fails when trying to build

the Sybase database server.
Check the following log files for the failure reason:

sybase/init/logs/srvbuild<date>.<number>
<CTM-M_home_dir>/ctm/tmp/ctm_new_db.<number>.log
On HP-UX, you may need to install Sybases EBF9682 patch
for Sybase version 12.
Installation fails when trying to build

the Oracle database server.
Check the following Oracle log files for the reason for failure:
oracle/product/9.2.0/install/crdb1.log
Note: When using an existing Oracle database server (not a
new database server), only the crbd5.log file will exist.
Also check the following log files:
<CONTROL-M_home_dir>/log/ create_server.log
<CONTROL-M_home_dir>/log/ createdb.log
<CONTROL-M_home_dir>/log/out_log_file
Poor performance for CONTROL-M

when installed with an Oracle
database server on AIX
Use the tuning instructions in Appendix H, Tuning Steps for

Oracle on AIX, to enable better performance on the AIX
computer.
16-12
Cleanup After an Aborted Installation
If you quit CONTROL-M installation before it completed, or if the

installation failed, the installation may have created database processes.
These processes should be removed to release all allocated resources, and
so that the necessary processes can be created later when you reinstall
CONTROL-M/Server.
To cleanup an installation that used a existing Oracle database, skip to
Oracle Database Cleanup on page 16-15.
To cleanup an installation that used a dedicated Sybase database, skip to
Dedicated Sybase Database Cleanup on page 16-15.
To cleanup an installation that used a existing Sybase database, skip to
Existing Sybase Database Cleanup on page 16-15.
Automatic Port Check
You can modify the (default) communication ports. Before displaying

each set of parameters, the customization program automatically checks
default port assignments in the parameter set. The following message
may appear once or more times for each screen of parameters displayed:
The port <portID> you specified for the <comtype>
is used by another application.
The installation will continue using this port that can later be configured.
Where <portID> is the address of the default port, and <comtype> is the
communications interface to which it is assigned.
Conflicting port assignments should be changed on the editing screen
during the customization process. If you exit the parameter screen
without changing these port assignments, the following message appears:
The port for the <comtype> (<portID>) is being used.
The installation has generated an alternate free port.
Press enter to accept port <altport> generated by the installation,
or type a different port number (default: <altport>) :
Where <altport> is an alternative, free communications port. Press

<Enter> to accept the alternate port, or type the address of another free
port and press <Enter> to reassign the port.
Troubleshooting
16-13
For some communications port variables, the following prompt will

appear:
Invalid <comtype> port <portID>: Address already in use
Please try again in 5 minutes or change the port number
Enter <comtype> port number? (default: <portID>) :
Enter an alternative port address, or press <Enter> to retry the existing

address.
16-14
Oracle Database Cleanup

If the installation of Oracle fails or is problematic, run the following
script from the $HOME directory of the CONTROL-M/Server or
CONTROL-M/EM user account:
uninstall_oracle.sh
Sybase Database Issues

Dedicated Sybase Database Cleanup
If you need to clean up after a failed installation with a dedicated Sybase

database (for example, so that you can install using an existing Sybase
Adaptive server instead), remove all database files that were created by
the failed installation (including the $SYBASE/data directory).
Note
If installation with a dedicated Sybase database failed, no cleanup is

necessary. All you need to do is rerun the install/custom script.
Existing Sybase Database Cleanup

Step 1
Log in to the Sybase database server as the sa user.
Step 2
Use the sp_helpdb command determine if the database was created by

the failed installation.
Step 3
If the database was created, use the following command to drop (remove)
it:
drop database <database_name>
Troubleshooting
16-15
Step 4
Specify the following command to check which devices were dropped

from the server:
sp_helpdevice
go
Step 5
If data or log devices associated with the CONTROL-M database are still
listed, drop them using the following command:
sp_dropdevice <device_name>
go
Step 6
If the database was installed using files, delete the files associated with
the dropped elements. Do not delete raw partitions.
16-16
17
Uninstalling CONTROL-M
Components
17
This chapter contains procedures for removing various CONTROL-M

components from your computers.
Table 17-1
Uninstallation Procedures
Uninstalling CONTROL-M/EM On Unix Computers
page 17-2
Uninstalling CONTROL-M/EM On Microsoft Windows
page 17-6
Uninstalling CONTROL-M/Server on Unix Computers
page 17-11
Cleanup for Sybase Database Servers
page 17-12
Uninstalling CONTROL-M/Server on Microsoft Windows
page 17-13
Uninstalling CONTROL-M/Agent for Unix
page 17-14
Uninstalling CONTROL-M/Agent for Microsoft Windows
page 17-17
17-1
Uninstalling CONTROL-M/EM On Unix Computers

Using the uninstall procedure, you can remove some or all
CONTROL-M/EM components on a computer.
Note
This uninstall procedure removes ALL CONTROL-M/EM components

from the local computer. If you want to remove only selected
components, use the Remove Component option of the Installation
Procedure.
Step 1
Stop all CONTROL-M/EM processes running on the Unix computer.

On a Windows computer on which the Administration facility is
installed, start the Administration facility. Change the Desired
State of all CONTROL-M/EM components on the Unix
computer to Down.
1.A
The components that you can shut down using the Administration
facility are:
GUI Server
Gateway
1.B
The Desired States of any CONTROL-M/EM components on

other computers that are connected with the components that will
be uninstalled must also be changed to Down for the duration of
the uninstall.
1.C
From the <CONTROLM_EM_HOME> directory on the Unix

computer (the one on which you are removing
CONTROL-M/EM), enter the following command to display the
root menu:
root_menu
1.D
Press 1. The Activation Menu is displayed:
17-2
Press 7 to run the stop_all script. This script shuts down the
database server (if it is installed on this computer), the Orbix
Locator and Naming processes, and the administration agent on
the local computer.
1.E
Note
For more information about using the Administration facility, see the
Maintenance chapter in the CONTROL-M/Enterprise Manager
Depending on which CONTROL-M/EM components are installed on the
computer some or all of the bulleted utility processes, below, may be
running. Stop the processes, as necessary.
Step 2
ecs.util
ecs.cli
ecs.ctl
copydefcal
copydefjob
defcal
defjob
defjobconvert
deftable
deldefjob
duplicatedefjob
exportdefcal
exportdefjob
exportdeftable
updatedef
To ensure that all CONTROL-M/EM and database server processes have

been stopped, enter the following command:
ps -ef |grep <Unix_account_username>
A list of the processes that are currently running under the account are
displayed. Kill any CONTROL-M/EM processes that are still running.
Step 3
Remove the CONTROL-M/EM account and its contents by entering the

following command:
17-3
rm -rf * .*
If the database server was installed under the CONTROL-M/EM

account, it was removed in the previous step. If so, the uninstall
procedure is complete.
However, if the database server was installed under a different
account on the same computer, you must follow the manufacturers
instructions to remove it. When the database server is removed, the
uninstall procedure is complete.
Step 4
If the database server is installed on a different Unix computer and

you want to remove only the CONTROL-M/EM database, continue
with Step 4.
Log on to the database server host computer as the CONTROL-M/EM

administrator.
If CONTROL-M/EM components are installed on this computer (in
addition to the database), continue with Step 5.
If no CONTROL-M/EM components are installed on this computer
(other than the CONTROL-M/EM database), go to Step Step 8.
Step 5
From the <CONTROLM_EM_HOME> directory on the database

server Unix computer, enter the following command to display the root
menu:
root_menu
The root menu is displayed:
Root Menu
--------------Select one of the following options:
17-4
1
2
3
4
5
Step 6
Activation Menu
Troubleshooting Menu
New Window
Database Creation Menu
Database Maintenance Menu
Press 4. The Database Creation Menu is displayed:

Database Creation Menu
---------------------Select one of the following options:
1 - Build Database
2 - Delete Database
p - Previous Menu
q - Quit
Enter option number --->
Step 7
Press 2 to select the Delete Database option. A brief interactive session is

started, during which you are prompted for the name of the
CONTROL-M/EM database. When the session ends, the database has
been removed and the uninstall procedure is finished.
Step 8
Use the database servers database removal tool to remove the

CONTROL-M/EM database. When the database has been removed, the
uninstall procedure is finished.
For more information, see the database server documentation.
17-5
Uninstalling CONTROL-M/EM On Microsoft Windows

Using the uninstall procedure, you can remove some or all
CONTROL-M/EM components on a computer.
Step 1
Use the Administration facility to shut down all CONTROL-M/EM

components.
Step 2
Select Start => Settings => Control Panel => Add/Remove Programs.
Select CONTROL-M/Enterprise Manager from the application list.
Click Remove (or Add/Remove).
Follow the prompts to complete the uninstallation.
Step 3
Select the required uninstallation type:

Select Full Uninstall to remove all CONTROL-M/EM components.
For Sybase installations, this option removes the Sybase Client, if it

was installed, and the CONTROL-M/EM database.
For MSSQL Server installations, this option removes the

CONTROL-M/EM database. It does not remove the MSSQL client.
Select Custom Uninstall to select which components should be

removed. Click Next.The Select Components window is displayed.
If you choose to remove the CONTROL-M/Enterprise Manager
Database:
For Oracle installations, this option removes the CONTROL-M/EM

database tables. The tablespace is not removed.
For Sybase installations, this option removes the CONTROL-M/EM

database completely, including data.
For MSSQL installations, this option removes the CONTROL-M/EM

database. It does not remove the MSSQL client.
17-6
If an Oracle or Sybase database client was installed with

CONTROL-M/EM, it is not removed if any of the following components
remain on the computer:
CONTROL-M/EM Database
GAS
GCS
Gateway
GUI Server
Reporting Facility
Step 4
If you are performing a Full Uninstall or removing the

CONTROL-M/EM database, you are prompted for the administrator
username and password.
Step 5
If you are removing the CONTROL-M/EM database from a Sybase

server or you selected Full Uninstall (including removal of a Sybase
database), one or both of the following messages are displayed:
Click OK for each message.

Step 6
If you are performing a Full Uninstall or removing the Reporting

facility, the following dialog box is displayed.
17-7
Note
Actuate is a report generator that is embedded in CONTROL-M/EM. Do

not remove Actuate if other programs on your computer use it.
If you do not want to remove Actuate, click No and continue with

Click Yes if you want to remove Actuate.
Step 7
The Confirm File Detection dialog box is displayed.
Step 8
Click Yes to remove the Actuate User Desktop. The following window
may be displayed.
17-8
Step 9
Click Yes to All. The following window is displayed:
Click Yes to continue. A checklist window is displayed.

Note
The checklist in this window applies only to removal of Actuate.

Step 10
Click OK. The following note is displayed:
Step 11
Click OK. The Actuate Uninstall Program dialog box is displayed.
Step 12
Click Yes to remove the Actuate User Desktop directory. The following
message is displayed:
17-9
Step 13
Click OK. The Actuate User Desktop has been removed.
Step 14
Follow the prompts to continue removal of CONTROL-M/EM

components.
Step 15
After reboot, remove the <CONTROL-M/EM_HOME> directory, if

required. (If a warning message was issued for this problem).
17-10
Uninstalling CONTROL-M/Server on Unix Computers

The ctm_uninstall utility can be used to undo CONTROL-M/Server
installation. The following actions are performed by this utility:
Shut down of all processes that are up and running.

Shut down of the CONTROL-M Database server, if it is running.
Removal of all files from the CONTROL-M home directory.
Running the utility

Step 1
Log in to a root user account.
Step 2
Navigate to the home directory of the CONTROL-M/Server user.
Step 3
Enter the following command to run the uninstall utility:

./ctm/scripts/ctm_uninstall
A series of status messages are issued by the utility. The following
message indicates that the uninstall procedure is complete:
Uninstall Procedure completed successfully
Step 4
Log out of the root user account.
In some cases, the uninstall procedure may abort before deleting the
CONTROL-M database, or may not remove all database elements.
Follow the necessary steps to check the database server and remove any
remaining elements.
For Sybase databases, go to page 17-12.

For Oracle databases, run the uninstall_oracle script in the $HOME
directory of the CONTROL-M user.
17-11
Cleanup for Sybase Database Servers

Summary:
Use the following steps to clean up Sybase database files after

uninstalling CONTROL-M/Server on a Unix computer.
Step 1
Log in to the Sybase database server as the sa user.
Step 2
Specify the following command to check which devices were dropped

from the server:
sp_helpdevice
go
Step 3
If data or log devices associated with the CONTROL-M database are still
listed, drop them using the following command:
sp_dropdevice <device_name>
go
Step 4
If the database was installed using files, delete the files associated with
the dropped elements. Do not delete raw partitions.
Step 5
Restart the database server. Dropped devices will not be deleted until you
restart the database server.
17-12
Uninstalling CONTROL-M/Server on Microsoft Windows

Summary:
Use the following steps to uninstall CONTROL-M/Server for Microsoft

Windows:
Step 1
Verify that no jobs are running on the server and no utilities are executing
on the server.
Step 2
Shut down the CONTROL-M/Server application using the following

command:
shut_ctm
Step 3
Select Start => Settings => Control Panel => Add/Remove Programs.
Select CONTROL-M/Server from the application list. Click Remove
(or Add/Remove).
Step 4
A window prompts you to confirm the uninstall. Click Yes to remove

CONTROL-M/Server.
Step 5
When uninstall is complete, close the Add/Remove Programs window.
17-13
Uninstalling CONTROL-M/Agent for Unix

You can use the ag_uninstall utility to uninstall CONTROL-M/Agent for
Unix. This utility removes all files from the CONTROL-M/Agent home
directory. Before running ag_uninstall, verify that no jobs are running on
the Agent platform and no CONTROL-M/Agent utilities are executing
on the Server platform.
Note
Uninstalling CONTROL-M/Agent for Unix will also remove all

CONTROL-M/Control Modules (for example, SAP, or Oracle
Applications) that are associated with that Agent. This procedure does
not remove CONTROL-M Options.
Step 1
Log on to the CONTROL-M/Agent platform as root.
Step 2
Use the following command to go to the CONTROL-M/Agent home

directory: cd <agent_path>
Step 3
Specify the command: ./ctm/scripts/ag_uninstall

Enter CONTROL-M/Agent UNIX username [<agent_user>]:
Step 4
Specify the CONTROL-M/Agent user name. A prompt similar to the

following is displayed.
Uninstall Procedure will back out CONTROL-M under
user: agmpe1
home directory: /home/agmpe1.
Do you want to continue? [y]:
Step 5
Specify y to continue. For each installed CM, a prompt similar to the

following is displayed:
The CM OS will be uninstalled.
17-14
If you need to backup OS related data,

press N and rerun this script later.
Do you want to uninstall OS (Y/N)[Y]:
17-15
Step 6
Specify y to continue or n to exit the uninstall procedure. If you specify

y, the following prompt is displayed:
--------------------------Uninstall Procedure Started
--------------------------Uninstall Procedure will remove CONTROL-M/Agent
service name from /etc/inetc.conf.
Do you want to continue? [y]
Step 7
Specify y to remove the Agent service entry from the /etc/inetd.conf file.
Removing the CONTROL-M/Agent service name from
/etc/inetd.conf.
Shutting down CONTROL-M/Agent.
Control-M/Agent Tracker is not running
Uninstall Procedure will remove all files in the home
directory "/home1/ctminst" of the user "ctminst".
Do you wish to continue? [y]
Step 8
If you enter y, the following messages are displayed:

Removing the contents of <agent_name> directory.
Uninstall Procedure completed successfully
You can delete the CONTROL-M/Agent controlm group
account from the /etc/passwd file if no other
CONTROL-M is installed on the same machine.
17-16
Uninstalling CONTROL-M/Agent for Microsoft Windows

Summary:
Use the following steps to remove CONTROL-M/Agent for Microsoft

Windows. This procedure will also remove all CONTROL-M/Control
Modules that are associated with the Agent that is uninstalled.
Note
This uninstall procedure deletes all files, including user-created files,

from CONTROL-M/Agent directories. Back up all relevant data before
running this procedure.
To make the uninstall procedure work faster, delete all files in the sysout
and backup directories before running the procedure.
Step 1
Verify that CONTROL-M jobs are not running on the computer and that
utilities invoked by CONTROL-M/Agent are not being processed by
CONTROL-M/Server.
Step 2
Choose Start => Settings => Control Panel => Add/Remove Programs
Step 3
2.A
Select CONTROL-M Agent from the Currently installed

programs list.
2.B
Click Remove.
The Add/Remove confirmation window displays the prompt:

Are you sure you want to completely remove 'CONTROL-M/Agent (<agentname>)'
and all its components?
Click Yes.
Step 4

Uninstall will remove Agent <AgentName> directories.
Please backup files from these directories that you want to keep.
Click OK to continue or Cancel to stop the Uninstall procedure.
Click OK
17-17
17-18
This appendix describes mount procedures for the various Unix

platforms that CONTROL-M supports.
For AIX computers, see page A-2.

For HP-UX computers, see page A-3.
For Solaris computers, see page A-6.
For COMPAQ Tru64 (Digital Unix) computers, see page A-6.
For Linux computers, see page A-8.
On most systems, you must log in to the computers root account to

mount a CD. After mounting the CD, log out of the root account before
you proceed with the installation procedure.
Note
You cannot run CONTROL-M installation routines from the root user
account. You must log out of the root user after mounting the CD.
A-1
Mounting Installation CDs on an AIX Computer

Step 1
Step 2
Insert the CD in the CD-ROM drive.
Step 3
Use the following command to create a directory (mount point) to be

used to access the CD:
mkdir <CD_path>
where <CD_path> is the name of the directory. Record this directory

name for future reference.
Note
This path must not be under the home directory of the CONTROL-M
user account.
Step 4
Use the following command to mount the CD.

mount -rv cdrfs /dev/cd0 <CD_path>
Note
You may need to replace cd0 with cd1. For more information, contact
your system administrator.
To Unmount a CD on AIX
Use the following command to unmount a CD:

umount <CD_path>
A-2
Mounting Installation CDs on an HP-UX

Computer
Step 1
Step 2
Step 3
Use the following command to create a directory (mount point) to be

used to access the CD:
mkdir <CD_path>
where <CD_path> is the name of the directory. Record this directory

name for future reference.
Note
This path must not be under the home directory of the CONTROL-M
user account.
You cannot specify the root directory for CONTROL-M product
installation CDs.
Step 4
Use the following command to display device paths on your computer:
/usr/sbin/ioscan -fnkC disk
A table of data is displayed. Search the Description column to find the

cell that describes the CD-ROM drive (the exact listing may vary).
Record the value from the Driver S/W State column in the same row as
the CD-ROM drive reference. This is the path to the CD-ROM device.
Step 5
If you are mounting one of the Oracle database CDs that are included
with CONTROL-M, continue with Step 5.
If you are mounting a CONTROL-M installation CD, continue with

Step 6.
To mount an Oracle CD:
A-3
5.A
Search for the /etc/pfs_fstab file. If this file does not exist, create
it and continue with Step 5.B.
5.B
Add the following line to the /etc/pfs_fstab file:

<cdrom_mark> <CD_path> pfs-rrip xlat=unix 1 0
where
<cdrom_mark> is the path to the CD-ROM device. This is the
cell value obtained in Step 4.
<CD_path> is the CD-ROM logical name. This is the value you
determined in Step 3.
If there is already a line that contains the <CD_path> in the
pfs_fstab file, but that line is not correct, delete it before adding
the new line described above.
Example
If <cdrom_mark> is /dev/dsk/c0t0d0 and <CD_path> is /cdrom, the

line to enter would be:
/dev/dsk/c0t0d0 /cdrom pfs-rrip xlat=unix 1 0
5.C
Enter the following commands to mount the CD:

nohup /usr/sbin/pfs_mountd &
nohup /usr/sbin/pfsd &
/usr/sbin/pfs_mount <CD_path>
Mount procedure is complete.

To mount additional CDs, you need not repeat the first two
configuration commands. Use the following command to mount
subsequent CDs in a session:
/usr/sbin/pfs_mount <CD_path>
A-4
Step 6
To mount a CONTROL-M installation CD:

6.A
Enter the following mount command:

/usr/sbin/mount -o cdcase <cdrom_mark> <CD_path>
where
<cdrom_mark> is the path to the CD-ROM device. This is the
cell value obtained in Step 4.
<CD_path> is the CD-ROM logical name. This is the value you
determined in Step 3.
Example
If <cdrom_mark> is /dev/dsk/c0t0d0 and <CD_path> is /cdrom, the

mount command would be:
mount -o cdcase /dev/dsk/c0t0d0 /cdrom
To Unmount a CD on HP-UX

For Oracle CDs:
/usr/sbin/pfs_umount <CD_path>
For CONTROL-M CDs:

/usr/sbin/umount <CD_path>
A-5
Mounting Installation CDs on a Solaris

Computer
The CD mount procedure is handled automatically by the Solaris
operating system.
eject
Mounting Installation CDs on a COMPAQ Tru64

Computer
Step 1
Log in as the root user.
Step 2
To locate the CD-ROM device:

For Tru64 version 4.x:
2.A

file /dev/rrz*c | grep RRD
2.B

eop/dev/rrz4c: character special (8/4098)
SCSI #0 RRD47 disk #32 (SCSI ID #4) (SCSI
LUN #0) offline
The device name is then /dev/rrz*c where * is the number that
appears after rrz in the output.
A-6
For Tru64 version 5.x:

2.A

/sbin/hwmgr -view devices
2.B
HWID: Device Name

Mfg
Model
Location
--------------------------------------------------------------------4: /dev/kevm
31: /dev/disk/floppy0c
3.5in floppy
fdi0-unit-0
39: /dev/disk/cdrom0c
COMPAQ
CDR-8435
bus-0-targ-0-lun-0
40: /dev/disk/dsk0c
COMPAQ
BB009222B5
bus-2-targ-0-lun-0
41: /dev/disk/dsk1c
COMPAQ
BB00921B91
bus-2-targ-1-lun-0
42: /dev/ntape/tape0
DEC
TLZ10
(C) DEC bus-2-targ-5-lun-0
Find the device name for the CD-ROM on the table. In the example,
the device name is /dev/disk/cdrom0c.
Step 3
Step 4
Step 5
Enter the following command:

mkdir <CD_path>
Step 6
Enter the following commands to mount the CD:

For Oracle installation CDs supplied with CONTROL-M:
mount -t cdfs -r -o nodefperm,noversion,rrip
<device_name> <CD_path>
For CONTROL-M installation CDs:

mount -r <device_name> <CD_path>
Where <device_name> is the logical name of the CD-ROM drive you

determined in Step 2, and <CD_path> is the directory you created in
Step 5.
A-7
To Unmount a CD on COMPAQ Tru64
Use the following command to unmount the CD:

umount /<CD_path>
Mounting Installation CDs on a Linux Computer

If CD-ROM is mounted automatically, you do not need to do anything.
If the CD-ROM is not mounted automatically, follow this procedure:
As a root user, enter the following command:
mount -t iso9660 -o map=off /dev/cdrom /cdrom
where /dev/cdrom represents the CD-ROM device on the agent's

machine and /cdrom represents the mount directory.
A-8
This appendix describes the various CONTROL-M/EM components that

can be installed.
The following tables describe each component, and include installation
considerations for that component.
Table B-1
Client Components
Component
Description
CONTROL-M/EM
Graphical User
Interface (GUI)
Central point of control for the CONTROL-M scheduling system. From each
CONTROL-M/EM GUI you can view job status in any part of the enterprise
system, issue requests, modify job parameters, restart jobs and handle any
type of exception to ensure efficient production job flow.
Installation notes:
This component must be installed on at least one computer in your datacenter.
This component can be installed only on Microsoft Windows.
CONTROL-M/
Desktop
Used to define and manage job processing definitions, Scheduling tables and
calendars.
Installation notes:
Command-Line
Interface
A collection of utilities that can be used to perform various job handling and
maintenance tasks.
The CLI does not include the Ctl.exe and Util.exe utilities.
Installation notes:
B-1
Table B-2
Administrator Components
Component
Description
Administration
Facility
Application used to manage server components of CONTROL-M/EM (see

Table B-3) and to maintain the CONTROL-M/EM database.
Installation notes:
This component can be installed only on Microsoft Windows. The Ctl.exe,
ServerUtil.exe, and RSI.exe utilities are installed together with the
Administration Facility. However, the util.exe utility is not installed with the
Administration facility.
Reporting Facility
This component enables you to produce reports from information that is

extracted from the CONTROL-M/EM Database.
Installation notes:
This component can be installed only on Microsoft Windows. It is
recommended, but not necessary, to install it on each CONTROL-M/EM Client
workstation.
When the Reporting facility is installed, the installation procedure also adds
Actuate User Desktop version 6.0 to your computer (if the necessary version
was not already installed). This application is placed in the following location:
<disk>\Actuate\Ver6\
Where <disk> is the same disk on which CONTROL-M/EM is being installed.
Table B-3
Server Components (Part 1 of 3)
Component
Description
CONTROL-M/EM
Global Alerts
Server (GAS)
Process that identifies and distributes alerts between CONTROL-M

installations and CONTROL-M/EM workstations. The GAS connects to each
CONTROL-M/EM gateway to receive alerts from CONTROL-M and transmit
them to the CONTROL-M/EM GUIs.
Installation notes:
You can install more than one GAS, if desired.
When the GAS is installed, the GUI Server component is also installed
automatically on the same computer.
Global Conditions
Server (GCS)
Identifies and distributes global condition flags that are used to maintain job
dependencies between CONTROL-M installations.
Installation notes:
You can install more than one GCS. However only one GCS can be active at a
time.
When the GCS is installed on Microsoft Windows, the Gateway component is
also installed automatically on the same computer.
B-2
Table B-3
Component
Description
CONTROL-M/EM
Gateways
Used to communicate between various CONTROL-M/EM components and the

CONTROL-M/EM database. The Gateway also handles communication
between CONTROL-M installations and CONTROL-M/EM.
On Microsoft Windows computers, the Util.exe utility packages are installed
with the Gateway.
For OS/390 CONTROL-M installations, two additional components are
installed on the OS/390 platform: the CONTROL-M Application Server and
IOAGATE.
Installation notes:
The CONTROL-M/EM Gateway must be installed on at least one Unix or
Microsoft Windows computer in your datacenter.
If CONTROL-M/EM components are distributed across multiple computers, the
Gateway is installed automatically on each Microsoft Windows computer with
any of the following components:
CONTROL-M/EM Database
Regardless of how many times the Gateway components is installed, it must
be registered (using the Administration Facility) once for each CONTROL-M
installation that is connected to CONTROL-M/EM. This registration procedure
is described in detail in Chapter 15, Post-Installation Configuration.
B-3
Table B-3
Component
Description
GUI Server
Distributes scheduling information to CONTROL-M/EM client components on

various workstations and handles job-related requests.
Installation notes:
CONTROL-M/EM GUI Server must be installed on at least one Unix or
Microsoft Windows computer in your datacenter.
Each GUI Server is used to manage one or more CONTROL-M/EM GUIs on
various workstations.
Working with Multiple GUI Servers
CONTROL-M/EM can also be configured using multiple GUI Servers. For
example, if the workload of a particular user is exceptionally heavy, it may be
desirable to connect a users workstation to a separate Server to reduce the
negative impact on the productivity of other users.
Users connected to the same GUI Server share the same ViewPoint filters can
perform the same functions. This reduces the workload of each individual GUI
and enhances productivity by enabling data sharing between workstations.
On Unix computers, the GUI Server is always installed with the GAS.
B-4
Table B-4
Third Party Components (Part 1 of 2)
Component
Description
Database Server
One Sybase Adaptive Server, Oracle Server, or MSSQL Server must be

available in the environment. This server hosts the CONTROL-M/EM database
(described below). An existing database server can be used, or a dedicated
server can be installed to support the CONTROL-M/EM database.
Installation notes:
On Microsoft Windows, the database server must already be installed in your
network before CONTROL-M/EM installation.
MSSQL Server is not packaged with CONTROL-M/EM.
Sybase Adaptive Server for Windows is not supplied with CONTROL-M/EM.
However, the CONTROL-M/EM installation process can create a database
on an existing Sybase server on Windows or Unix.
Oracle installation CDs are provided with CONTROL-M/EM for Windows.
The new Oracle instance and/or database schema must be created before
CONTROL-M/EM installation.
For Unix installations:
MSSQL is currently unavailable on Unix.
Sybase Database Server for Unix is supplied on a separate installation CD.
The CONTROL-M/EM installation process can create a Sybase server and
database.
Oracle installation CDs are provided for all supported Unix operating
systems. The new Oracle instance and/or database schema must be
created before CONTROL-M/EM installation.
For more information about possible database configurations, see Step 2 on
page 1-4.
For more information about the CDs supplied with the CONTROL-M/EM
installation package, see Table 1-5, Installation CDs by Computer Type, on
page 1-9.
Database Client
When CONTROL-M/EM components are distributed across several computers,

the databases Client application is installed to enable communication with the
database server.
A Sybase client is automatically installed when needed during
CONTROL-M/EM installation. (Sybase Client is not installed if Sybase
Server or Client 12.x is installed locally.)
The MSSQL Client is not packaged with CONTROL-M/EM, and must be
installed separately.
The Oracle Client can be installed using the Oracle installation package that
is provided with CONTROL-M/EM. For more information, see Chapter 5,
Installing an Oracle Database on Unix, or Chapter 6, Installing an Oracle
Database on Microsoft Windows.
B-5
Table B-4
Third Party Components (Part 2 of 2)
Component
Description
CONTROL-M/EM
Database
A repository of all data related to the functioning of the scheduling/CS

environment.
This database is periodically synchronized with the databases that are
maintained by CONTROL-M/Server on the platforms that are connected to
CONTROL-M/EM.
Installation Notes:
Only one CONTROL-M/EM Database should be installed.
When the CONTROL-M/EM Database is installed, the Gateway component is
also installed automatically on the same computer.
Orbix E2A Server
The Orbix E2A Server (version 6.0.2) is a set of processes that facilitates
communication between the GUI Server and the Global Alerts Server, and all
connected CONTROL-M/EM GUIs.
This component must be installed once.
Installation notes:
The Orbix client is automatically installed when you choose to install any of the
following CONTROL-M/EM components:
Global Alert Server
GUI Server
CONTROL-M/EM GUI
CONTROL-M/Desktop
B-6
Unix Operating System RequirementsC

This appendix describes the operating system versions and patches that
are required by CONTROL-M/EM and CONTROL-M/Server.
Note
Required patches and operating system versions should be checked using

the check_req.sh script. This appendix is provided for additional
information.
The following table contain describes each component, and includes
installation considerations for that component.
C-1
Table C-1
Unix Operating System Requirements for CONTROL-M (Part 1 of 7)
Operating
System
Requirements
AIX
Patches required with AIX 5L (5.1, or 5.2)

Ensure that you have installed maintenance level 01 or later.
After installation of this maintenance level, xlC.rte is version 5.0.2.1 and
xlC.aix50.rte is version 5.0.2.2.
For Oracle installation on AIX version 5.1:

Patches
Maintenance level 01 with the IY26778, IY28766, IY28949, and IY22854
patches.
-or Maintenance level 02 with the IY29965, and IY30150 patches.
Packages
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.perfstat
bos.perf.libperfstat
Files Required by Compilers

If VisualeAge C++ is not installed on the computer,
upgrade xlc.aix50.rte to version 5.0.2.3 or later by installing
xlC.aix50.rte that can be found in the IY17826 APAR.
If VisualeAge C++ prior to version 5.0.2 is installed on the computer,
upgrade the compile to 5.0.2 and ensure that the IY17826 APAR is installed
completely.
If VisualeAge C++ version 5.0.2 is installed on the computer, ensure that the
IY17826 APAR is installed completely.
Note: It is recommended in all cases to have xlC.msg.en_US.rte version 5.0.2.0.
After the upgrade process:
The xlC.rte should be 5.0.2.1 or higher.
The xlC.aix50.rte should be 5.0.2.3 or higher.
C-2
Table C-1
Operating
System
AIX
(continued)
Requirements
How do I check It?

Use this command to check which patches are installed on your computer:
/usr/sbin/instfix -ia -ivk <patch number>
Use this command to check which packages are installed on your computer (for
APARs and PTFs):
lslpp -w | grep -i "software title"
If you are installing an Oracle Database:

To determine if your window manager meets the necessary requirements, enter the
xclock& command. If a clock is not displayed, then your window manager is not
configured correctly.
C-3
Table C-1
Operating
System
Requirements
HP-UX
HP-UX version 11.0, utilizing the long filenames option

The following patches must also be installed on machines running HP-UX version
11.0:
PHSS_21075 (varargs.h and +DA2.0W)
PHSS_21947 or later (linker patch)
PHSS_21950 or later (LIBCL patch)
PHSS_22543 or later (runtime patch)
Other Patches (for Sybase 12 on HP-UX version 11.0)
Extension patch bundle 9808

PHNE_16017
PHNE_16599
PHNE_16470
PHKL_15689
PHKL_17091
PHCO_16629
PHCO_19391
PHSS_16404
PHSS_18072
Other Patches (for Oracle on HP-UX version 11.0)
PHCO_23792 s/b PHCO_26960

PHCO_24148 s/b PHCO_25707 s/b PHCO_27608
PHKL_24268 s/b PHKL_27178
PHKL_24729
PHNE_24715 s/b PHNE_26771
PHSS_23670 s/b PHSS_26138
PHSS_24627
PHSS_22868
Note: s/b means "superseded by" this indicates that only one of the patched in that
line is necessary.
C-4
Table C-1
Operating
System
HP-UX
(continued)
Requirements
Other Patches (for Oracle on HP-UX version 11.11)
PHNE_27745
PHNE_28568
PHKL_25506
PHSS_26560
PHSS_26946
PHSS_28849
PHSS_26946
PHSS_26560
PHCO_28427
PHCO_24402
How do I check It?

Use the following command to check if a patch is installed on HP-UX version 11.0:
swlist -l fileset -a state | grep <patch_name>
C-5
Table C-1
Operating
System
Requirements
Solaris
Operating System and Patches for CONTROL-M/Server:

Solaris 2.7 (Supported for CONTROL-M/Server only) with:
106980-09 patch or later (thread lib)
106327-08 or later (Sun C++ 5.1 runtime).
Solaris 2.8 (also known as 5.8) with:
108434-01 or later
108435-01 or later (Sun C++ 5.x runtime)
108827-12 or later.
Solaris 2.9 (also known as 5.9)
Operating System and Patches for CONTROL-M/EM:

108434-13 or later
108435-13 or later (Sun C++ 5.x runtime)
108528-27 or later
108652-76 or later
108773-18 or later
108827-12 or later.
108921-19 or later
108940-57 or later
108987-13 or later
108989-02 or later
108993-31 or later
109147-27 or later
109326-12 or later
110386-03 or later
110615-10 or later
111023-03 or later
111111-03 or later
111308-04 or later
111310-01 or later
111317-05 or later
112003-03 or later
112396-02 or later
112438-02 or later
112472-01 or later
113648-03 or later
115827-01 or later
116602-01 or later
113096-03 or later
112785-30 or later
C-6
Table C-1
Operating
System
Solaris
(continued)
Requirements
Other Patches (for Sybase version 12)

On Solaris 2.7 (supported for CONTROL-M/Server only):
106541-03
106327-05
106300-06
Other Patches (for Oracle)

X-windows must be installed on the system from where the Installer is run. Use
any Sun-supported X-windows server that supports Motif (for example, dtwm,
twm, olwm).
Solaris Operating System Packages: SUNWarc, SUNWbtool, SUNWlibm,
SUNWlibms, SUNWsprot, SUNWtoo, SUNWhea.
The following executables must be present in the /usr/ccs/bin directory: make, ar,
ld, nm.
How do I check It?

Use the following command to check the version of the Solaris operating system on
your computer:
uname -a
Use the following command to check for patches on your computer:
showrev -p | grep <name_of_patch>
<name_of_patch> is the name of the patch that you are checking for.
Use the following command to check for packages on your computer:
pkginfo | grep <name_of_package>
<name_of_package> is the name of the package that you are checking for.
C-7
Table C-1
Operating
System
Requirements
Compaq
Tru64
Operating System:
Compaq Tru64 version 5.1B.
(Supported for
CONTROL-M/
Server only)
Operating System Packages:

Use the latest patch kit from Compaq.
Operating System Patches
The OSFLIBA, OSFPGMR, and OSFCMPLRS subsets are part of the Compaq
Tru64 UNIX operating system distribution
For Oracle installation

Only Tru64 version 5.1B is supported.
You must have patchkit 2 or higher.
How do I check It?

Use the following command to check the version of the Compaq (Digital Unix)
operating system on your computer:
/usr/sbin/sizer -v
Use either of the following commands to check for packages on your computer:
/usr/sbin/setld -i | more
grep -i <product_name>
Checking for patches:
If you installed patches on the current computer, use the following commands:
/usr/sbin/dupatch -track -type kit
Note: If you never installed patches you can't get information about patches.
C-8
This appendix describes how to estimate the size of the CONTROLM/EM database. This information is required when installing
CONTROL-M/EM.
If you are interested in calculating the size of the database to be used by
CONTROL-M/Server, see Appendix E, CONTROL-M/Server Database
Size.
To calculate the estimated database space requirement, add the space
required for these database components:
Empty database schema 20 MB.

Job definition data (see Job Definition Data on page D-3).
Dynamic system data (see Dynamic System Data on page D-5.)
Database index 70% of the space needed for the other components.
Note
Many factors affect the required size of the CONTROL-M/EM database.

The recommendations in this appendix are only guidelines that are based
on typical requirements. It is the customers responsibility to consider
local configuration requirements and to make any necessary
modifications to these calculations.
D-1
Example
This example uses the input data and results from later examples. The
total disk space is calculated in the table below. The Total shows the
approximate disk space required for the CONTROL-M/EM database.
Database Area
Result in MB
Database schema (empty)
20.00
Job definition data
5.48
Dynamic system data
5.55
Subtotal (Data area of the database)
30.03
Database index (70% of the subtotal)
21.02
Total:
51.05
D-2
Job Definition Data
The space required for job definition data is calculated by determining

the size of the average job and multiplying that size by the total number
of job definitions.
To estimate the disk space for job definition data, build a profile for the
average job. This profile is based on the average space required for every
definition element that can be included in a job. Multiply the size of this
profile by the total number of jobs defined in the system.
Table D-1 shows the disk space required for each job definition element.
Table D-1
Job Definition Elements and Disk Space Requirements
Job definition element
Disk space
Basic job definition
300 bytes
Prerequisite condition
55 bytes
Control resource
40 bytes
Quantitative resource
40 bytes
AutoEdit variable
40 bytes
Do Action
180 bytes
D-3
Example
In this example, the average job contains 5 prerequisite conditions,

1 control resource, zero quantitative resources, 3 AutoEdit variables, and
2 Do actions. The maximum number of jobs in our sample system is
5,000.
The average job space calculation is shown below. The Total indicates the
space this average job will occupy in the job processing definitions area
of the database.
Job Definition Item
Calculation
Result
300 bytes
300
5 * 55 bytes
275
Control resource
1*
40 bytes
40
0 * 40 bytes
AutoEdit variable
3 * 40 bytes
120
Do action
2 * 180 bytes
360
Total:
1095 bytes
The total size of the job definition area is calculated by multiplying the
size of the average job by the total number of jobs in the system. In this
example, the size of the databases job processing definition area is:
1,095 bytes * 5,000 jobs = 5.48 MB (approximately)
D-4
Dynamic System Data
The dynamic system data portion of the CONTROL-M/EM database

consists of the following components:
Objects produced by running the New Day procedure. The space

required is calculated by multiplying the number of data centers in
the network by 400 K, the space required for each set of objects.
An active jobs area. The size of this area is determined by

multiplying the average job size by the maximum number of jobs
that can be scheduled on the busiest day. For more information, see
Job Definition Data on page D-3.
An area for storing alert messages. The space required is calculated

by multiplying the number of alerts in the system by 90 bytes (the
average size of an alert record).
To estimate the disk space for dynamic system data, add the amounts
required for the three components described above.
Example
In this example, the database contains data for 5 data centers. The
average job size is 1095 bytes (as calculated in Example on page D-4,
The maximum number of jobs scheduled on any day is 2,000. The
number of alerts in the system is 15,000.
The dynamic system data space calculation is shown below. The Total
indicates the approximate space required for the dynamic system data
area of the database.
Database Area
Calculation
Result
New Day procedure objects
5 * 400 K bytes
2.00
Active jobs area
2000 * 1095 bytes
2.20
Alerts
15,000 * 90
1.35
Total:
5.55 MB
D-5
Database Memory Requirements
It is recommended that you allocate for the database the same amount of
memory as the database disk space usage. This ensures that all the data is
located in the machine real memory thereby increasing processing speed.
The minimum amount of memory required is at least 20% of the
database disk space as calculated according to the instructions in this
chapter.
Note
Regardless of the actual disk space usage, the minimum amount of

memory required is at least 40 MB. The database will not function with
less than 40 MB of real memory.
Be sure that memory calculations are performed in accordance with the
actual physical RAM installed on the target machine.
D-6
CONTROL-M/Server Database Size E

This appendix describes how to estimate the size of the
CONTROL-M/Server database.
Note
If you are interested in calculating the size of the database to be used by

CONTROL-M/EM, see Appendix D, CONTROL-M/EM Database
Size.
The database is comprised of:
Job processing definitions

Active Jobs file
Database Memory requirements
Note
Many factors affect the required size of the CONTROL-M database. The
recommendations in this appendix are only guidelines that are based on
typical requirements. It is the customers responsibility to consider local
configuration requirements and to make any necessary modifications to
these calculations.
E-1
All jobs in the system have job processing definitions. The Active Jobs
file contains the jobs that are scheduled to run, the status of the current
job situation, log records for the last n days, and log records for the last n
executions of each job. The database size is affected by the jobs that are
defined and run at a particular time, the running of cyclical jobs, the
maximum number of jobs per day, and so forth.
Job Definitions
To estimate the disk space for job processing definitions, build a
profile for the average job. This profile contains all the definitions that
you can include in a job. Then multiply the size of this average job by the
total number of jobs in the system.
Table E-1 lists typical job items and the disk space required for each
item.
Table E-1
Job items and Disk Space Requirements
Job Item
Disk Space
2000 bytes
Do action
650 bytes
AutoEdit variable
350 bytes
Control resource
180 bytes
200 bytes
300 bytes
Example
In this example, the average job contains 3 Do actions, 1 AutoEdit

variable, 3 Control resources, 1 Quantitative resource, and 1prerequisite
condition. Maximum number of jobs in the system: 7,000.
The database space calculation is shown below. The Total indicates the
space this average job will occupy in the job processing definitions area
of the database.
E-2
Table 5-2
Job Definition Calculation
Job Definition Item
Calculation
Result
2,000 bytes
2,000
Do Actions
3 * 650 bytes
1,950
AutoEdit Variable
1* 350 bytes
350
Control Resources
3 *180 bytes
540
Quantitative Resource
1 * 200 bytes
200
Condition size
1 * 300 bytes
300
Total:
5,340 Bytes
The total size of the job definition area is calculated by multiplying the
size of the average job by the number of jobs in the system. In this
example, the size of the databases job processing definition area is:
5,340 bytes * 7,000 jobs = 37,380,000 Bytes
Calculating the Size of the Active Jobs File

The Active Jobs file consists of the following components:
Active jobs, that is jobs scheduled to run that day.
Job execution log for the last D days. (Default for D: 2. This value
can be modified.) Each job execution log requires 5,000 bytes.
Final execution status for the last E executions of each job. (Default
for E: 21. This value can be modified.) Each final execution status
requires 700 bytes.
Daily execution status, that is, the status of all executions on that day.
Each execution status requires 190 bytes.
E-3
The size of the Active Jobs file is obtained by adding the size required for
each of these components.
1. Active Jobs
Determine the number of bytes required to store the average job
(for example: 5,340 bytes). Multiply this number by the maximum
number of jobs that run each day. (At most sites, not all of the jobs
are executed each day.)
2. Job Execution Log
Multiply the number of execution days (D) by the maximum number
of job executions per day. Multiply the result by 5,000 bytes.
3. Final Execution Status
Multiply the number of final executions to keep (E) by the total
number of jobs defined. Multiply the result by 700 bytes.
4. Daily Execution Status
Multiply the maximum number of executions each day by 190 bytes.
(If there are cyclical jobs with short intervals, the number of
executions per day can exceed the number of jobs in the system.)
5. Add the results obtained in steps 1 through 4 to obtain the number of
bytes required for the Active Jobs file.
6. To obtain the total including the database index:
for Sybase and MSSQL databases, multiply the sum from Step 5
by 2.2
for Oracle databases, multiply the sum from Step 5 by 1.7
Example
This example estimates the size of a CONTROL-M database.

Job Option
Value
Number of history days
2 (default)
Number of executions history
21 (default)
Maximum number of active jobs
100
E-4
Job Option
Value
Maximum job executions per day
1,000
Total number of jobs defined
100
Number of DO actions
Number of AutoEdit variables
Number of Control resources
Number of Quantitative resources
Number of conditions (In and Out)
Total size of Job definition in MB
0.51
Total size of Active Job file in MB
11.63
Total database size in MB
for Sybase/MSSQL: 25.6

for Oracle: 19.8
Sample Active Jobs File Calculation
1. Active Jobs file

Average job * maximum number of jobs (using * as a multiplication
sign)
5,340 * 100 = 534,000 bytes
where 5,340 is the size of an average job and the Active Jobs file
contains a maximum of 100 jobs.
2. Job Execution log
D * maximum number of executions per day *5,000
2 * 1,000 * 5,000 = 10,000,000 bytes
where D, the number of days to save each log, is 2 (the default) and a
maximum of 1,000 jobs are executed each day.
E-5
3. Final Execution Status

E * maximum jobs in the system * 700
21 * 100 * 700 = 1,470,000 bytes
where E, the number of status records to keep, is 21 (the default) and
where there are 100 defined jobs in the system
4. Daily Execution Status
Maximum number of executions per day * 190
1000 * 190 = 190,000 bytes
5. Add the results of steps 1 through 4 to obtain the size of the Active
Jobs file.
534,000 + 10,000,000 + 1,470,000 + 190,000 = 12,194,000
Table E-3
Parameter
Description
Number of days
to keep each job
execution log
The job execution log stores information about

job execution start and end times and about
job behavior. Each job execution log requires
5000 bytes.
Default: 2
Number of final
execution status
records to keep
for each job
Each record Indicates the final status of an

executed job. The size of each final status
record is 700 bytes.
Default: 21
Max active jobs

per day
Maximum length of the list of jobs that can be

run during a day.
Max job
executions per
day
Maximum number of job executions that can be

performed each day.
Number of DO
Actions
Indicates job dependencies that rely on Do

condition statements. Specify the value for an
average job, not the number of all Do
statements in your system.
E-6
Active Jobs File Parameters
Table E-3
Active Jobs File Parameters
Parameter
Description
Number of
AutoEdit
variables
AutoEdit variables are used to transfer

information between jobs. Specify the value for
the average job, not the number of AutoEdit
variables in your system.
Number of
Control resources
Specify the number of Control resources for

the average job.
Number of
Quantitative
resources
Specify the number of Quantitative resources

(such as backup tapes or printers) for the
average job.
Number of In and
Out conditions
Specify the number of prerequisite conditions

for the average job.
To calculate database disk space
The database index requires approximately 70% of the space

required for the data for Oracle, and 120% for Sybase or MSSQL.
The empty database schema requires 15 MB.
Add the size of the Job Processing definitions area and the size of the
Active Jobs File. Multiply the result by 1.7 (Oracle) or 2.2 (Sybase or
MSSQL) and add 15 MB.
This result of this calculation is the size of the CONTROL-M database. It
is recommended that you allocate twice the space that would be required
for the database on your busiest day in order to ensure adequate space
that may be required for CONTROL-M operations.
Note
These database size calculations are based on typical estimates. It is the

customers responsibility to properly modify these calculations.
E-7
Database Memory Requirements

In addition to the database space requirements, the database also
consumes memory. Below are the guidelines to follow when calculating
memory requirements for the database.
1. It is recommended that amount of memory allocated for the database
be equal to the database disk space requirements. This ensures that
all the data is located in real memory, thereby minimizing disk I/O
activity.
Memory access is much faster than physical disk access. Therefore,
we recommend placing as much data as possible in memory.
The minimum required amount of memory is approximately 20% of
the database disk space requirements as calculated according to the
database size calculations described in this chapter.
2. Regardless of disk space requirements, at least 60 MB of real
memory is required. The database will not function with less than
60 MB of real memory.
Increasing database memory reduces Input/Output operations and
makes the database perform faster. Make sure that memory
calculations are performed in accordance with the actual physical
RAM installed on the target machine.
E-8
New Database Schema on an Existing

Oracle (Unix)
F
This appendix describes how to install a new Oracle database schema for
CONTROL-M using an existing Oracle installation on Unix.
Note
This procedure does not install Oracle Client or reconfigure any existing
Oracle client. It is recommended only for advanced users, and should be
performed only in consultation with BMC Software Technical Support.
This procedure is for CONTROL-M products using an existing Oracle
installation on a Unix computer.
F-1

Summary:
Review the following restrictions and directions before you begin the
installation procedure.
Oracle client software must already be installed and configured to

connect the local Unix user to the target database instance.
The CONTROL-M user account must have permission to read and

execute the existing Oracle software files (in the installation referred
to in the previous bullet).
The installation procedure prompts you for the name and password
of the database administrator (DBA) of the existing database instance
on which the new schema will be created.
When you install a CONTROL-M database on an existing Oracle

instance, that instance must run Oracle software releases certified by
BMC Software for use with CONTROL-M. At this time, CONTROL-M
version 6.1.03 supports Oracle Database Server version 9.2.0, or 8.1.7.4.
However, the Oracle client must be version 9.2.0.4.
Continue with the next task Run the Oracle Pre-Installation Script on
page F-3.
F-2
Run the Oracle Pre-Installation Script

Summary:
In this task, you will run the Oracle pre-installation script. This script
check prerequisites for Oracle installation and determines certain system
settings and defaults for the database to be installed.
Step 1
Log in as the root user. You will run the Oracle pre-installation script as
the root user.
Step 2
Navigate to the CONTROL-M/EM or CONTROL-M/Server user home

directory.
Step 3

<CD_path>/orapreinst.sh
Note
The orapreinst.sh script is located on the CONTROL-M Oracle

Installation Package for Unix CD (FD5380), not in the files copied from
the Oracle CDs.
The orapreinst.sh script finds and removes any temporary files from
earlier Oracle installations, and creates a tmp directory for the current
Oracle installation.
If temporary Oracle files were found, the following message is displayed:
Oracle temporary components were detected.
In order to continue with installation, they should be
deleted.
Do you wish to delete these components? [y/n]y
Enter y.
Step 4
F-3
Checking version of the operating system...

done
Which CONTROL-M product are you about to install ?
1. CONTROL-M/Server
2. CONTROL-M/EM
Enter your choice :
Select the CONTROL-M product for which you are creating a database,
and press <Enter>. This is the product you selected in Step 4. This
selection determines the default settings that will be used to create the
database.
Step 5
A message similar to the following is displayed:

Enter the Oracle configuration file path and name
(default: /<CD_path>/<config_path>) :
Where the value of <config_path> is:

ora_defs_controlm for a CONTROL-M/Server database
ora_defs_ctmem for a CONTROL-M/EM database.
Press <Enter> to accept the default file path and name.
Note
If you are upgrading a CONTROL-M database from a previous version,

enter the following path for this prompt:
<ctm_home_dir>/install/ora_defs_ctm
where <ctm_home_dir> is the existing CONTROL-M product home
directory.
Step 6

Saving current Oracle products configuration.
Enter the oracle installation directory (default:
/<install_dir>) :
F-4
Where <install_dir> is the user directory you created on the local

computer for CONTROL-M/Server or CONTROL-M/EM installation.
Press <Enter> to install Oracle in the default directory, or enter a
different directory path.
Step 7

Done.
Creating Oracle Inventory pointer file
(/var/opt/oracle/oraInst.loc)
orapreinst.sh execution ended successfully.
On AIX systems, the path shown is /etc/oraInst.loc.

Step 8
Log out of the root account.
Continue with the next task Installing the Database Schema on page
F-6.
F-5
Installing the Database Schema

Step 1
Log in as the CONTROL-M/Server or CONTROL-M/EM administrator

(depending on which product you are installing).
Step 2
Insert the CONTROL-M Oracle Installation Package for Unix (FD5380)

in the CD-ROM drive. Mount the CD-ROM drive.
Step 3
From the home directory of the CONTROL-M product user account,

enter the following command:
where <hostname> is the name (or the IP address) of the computer

from which the installation is being performed.
It is recommended to run a small application (such as xclock) at this time
to ensure that the specified display settings are working.
Step 4
From same directory, enter the following command:

setenv USE_EXISTING_ORACLE Y
Step 5
Use the following command to run the installation script:

inst_oracle
Step 6
The Oracle Installation Type menu is displayed:

CONTROL-M ORACLE DATABASE INSTALLATION TYPE
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
3) Existing
- Install an Oracle client to Use an existing Oracle

database
(use your existing Oracle software copy !!!)
4) Client only
- Install an Oracle client for communication with

an existing CONTROL-M database.
(use your existing Oracle software copy !!!)
q) quit
Enter the installation type you wish to perform on this machine :
Option 4 is displayed only when CONTROL-M/EM is installed.

F-6
Step 7
Choose 3 or 4 and press <Enter>.
Step 8
A menu is displayed showing the Oracle installations that have been

identified as possible targets (the menu below is for illustrative
purposes):
The following Oracle installations were discovered on this server :
1. /home2/oratest/oracle/product/9.2.0
2. /home/ora_dba/product/9.2.0
3. /opt/oracle/9.2.0
O. Other un-discovered installation
Q. Quit
Please select the installation you want to use for CONTROL-M or select O for
manually typing an Oracle installation path :
Type a number from the list to select a local existing Oracle

installation.
To specify an existing Oracle installation that is not on the list, type

O. If you selected O, the following message is displayed:
Please type in the full path of the ORACLE_HOME of the

Oracle installation
you would like to use
Step 9
Step 10
Type the full path to the <ORACLE_HOME> directory and press Enter
to continue.
A menu is displayed showing the network connection aliases that have
been identified as possible targets (the menu below is for illustrative
purposes):
Identified network connection aliases :
1.
2.
3.
4.
PINCTEST
INST1_HTTP
CTM
EM613
O. Other network alias

Q. Quit
Please select one of the displayed network aliases as your target database or
select O for manually typing a network alias :
F-7
Type a number from the list to select a network alias to an existing

database instance.
To specify an existing database instance that is not on the list, type O and
enter a valid network alias.
Press <Enter> to continue.
Step 11
The following menu is displayed:

+++++++++++++++++++++++++++++++++++++++++++
+
<product> CLIENT_AND_DB
+
+
+
+
Oracle Database Parameters
+
+++++++++++++++++++++++++++++++++++++++++++
1)
2)
3)
4)
5)
6)
7)
8)
a)
b)
r)
q)
<product> database user :

<product> database user password :
Oracle SYSTEM password :
<product> data tablespace name :
<product> data tablespace size :
<product> data tablespace file name (full path) :
<product> index tablespace size :
<product> index tablespace file name (full path) :
emuser
######
#######
em613
50 MB
20 MB
Modify all parameters

Build <product> database
<- Return to start
Quit
Enter command or item number you wish to change :
Review and, if necessary, modify the values for the parameters in this
menu. Table F-1 on page F-9 describes the parameters in this menu.
F-8
Table F-1
Oracle Database Parameters
Parameter
Description
Database user
Name of the database user to be created. This is the

user used to log on to the CONTROL-M product.
CONTROL-M/EM default: emuser
Database user
password
Password for the database user (6 to 30 characters,

alphanumeric). The characters are not displayed for
security reasons.
CONTROL-M/EM default: empass.
CONTROL-M/Server default: password.
SYSTEM
password
Password for the Oracle superuser that manages the

existing Oracle instance. Default: manager.
Data tablespace
name
Name of the data tablespace that will be created on the

existing Oracle database instance. This tablespace will
contain the database data.
CONTROL-M/Server default: ctrlm
Data tablespace
size
The default size of the data tablespace containing the

database data.
Data tablespace
file name
The full path and filename for the Data file of the
database.
The specified path must be an existing path for which
the administrator of the existing Oracle instance has
READ and WRITE permission.
The filename must not be the name of an existing file.
This file will be created during installation of the
database.
Example:
<ctm_home>/oracle/oradata/em_dat.dbf
Index tablespace
size
The default size of the index tablespace depends on the

size of the database chosen.
Index tablespace
file name
The full path and filename for the Index file of the
database.
The specified path must be an existing path for which
the administrator of the existing Oracle instance has
READ and WRITE permission.
The filename must not be the name of an existing file.
This file will be created during installation of the
database.
Example:
<ctm_home>/oracle/oradata/em_ind.dbf
F-9
Note
Even if you do not modify any other parameters, you must modify the
parameters relating to the existing database which do not have default
values.
Step 12
When you are satisfied with the values of the database parameters,
specify option b to build the database.
Build the Database

When you specify the b (Build) option in the installation parameter
menu, the Oracle infrastructure for the CONTROL-M/Server or
CONTROL-EM database is built and installed.
Step 1
The following messages are displayed during database creation:

############################################
############################################
INSTALLING <product> DATABASE
############################################
############################################
Starting Database creation. This may take a while ...
Oracle Database Creation in progress. 99 percent already completed
################################################
Installation of Oracle Database Ended successfully
################################################
Note
The messages shown above, are displayed for a custom or default

installation. Different messages may be displayed for Existing and Client
installations.
F-10
Run the Oracle Post-Installation Script

The following procedure removes the temporary directories and files
created by Oracle database server setup.
Step 1
Step 2
Navigate to the CONTROL-M user home directory.

Note
The orapostinst script is located on the CONTROL-M Oracle

Installation Package CD, not in the files copied from the Oracle CDs.
Step 3
Enter the following command, and press <Enter>.

<CD_path>/orapostinst.sh
Where <CD_path> is the directory on which the CONTROL-M Oracle

Installation Package was mounted.
Step 4
If necessary, confirm the removal of files by entering y and press

<Enter>.
Step 5
Log out of CONTROL-M product and root accounts.
F-11
F-12
New Database Schema on an Existing

Oracle (Microsoft Windows)
G
This appendix describes how to install a new Oracle database schema for
CONTROL-M using an existing Oracle installation on Microsoft
Windows.
This same procedure can be used to check the settings for an existing
client on the current computer.
Note
This procedure does not install Oracle Client or reconfigure any existing
Oracle client. It is recommended only for advanced users, and should be
performed only after consultation with BMC Software Technical
Support.
G-1

Summary:
Step 1
Step 2
Follow this procedure to install a new Oracle database schema using an

existing Oracle installation.
Review the following restrictions and directions before you begin the
installation procedure:
Oracle client software must already be installed (especially sqlplus

and the Oracle ODBC driver) and configured to connect the local
user to the target database instance.
The installation procedure prompts you for the name and password
of the database administrator (DBA) of the existing database instance
on which the new schema will be created.
When you install a CONTROL-M/EM database on an existing

Oracle instance, that instance must run Oracle software releases
certified by BMC Software for use with CONTROL-M/EM. At this
time, CONTROL-M/EM version 6.1.03 supports Oracle Database
Server version 9.2.0, 9.0.1, or 8.1.7.4. However, the Oracle client
must be version 9.2.0.x.
If there is more than one Oracle product installed on your computer,

select the Oracle Home you wish to use for the installation:
2.A
From the Start menu, select Programs => Oracle Installation

Products => Home Selector.
2.B
Select the Oracle Home you wish to use.
2.C
Exit the Home Selector.
Step 3
From the Start menu, select Run. Enter the name regedit and click OK
to run the Registry Editor.
Step 4
In the Registry Editor windows tree (left pane), select

HKEY_LOCAL_MACHINE=>SOFTWARE=>ORACLE.
G-2
Step 5
Right-click in the right-hand pane of the Registry Editor window, and

choose New => String Value. Overwrite the dummy text with the string
USE_EXISTING_ORACLE.
Step 6
If Autorun functionality has not been disabled, a startup window is

displayed.
If Autorun is disabled on your computer, use Windows Explorer to

select the CD-ROM drive. Select OracleInstallationFiles =>
executables => OracleInstallationDriver and double-click
setup.exe.
Step 7
The installation procedure checks the registry information, detects the

changes you made, and displays the following window:
Step 8
Click Next. The following window is displayed:
G-3
Select from the list of existing Oracle Homes. CONTROL-M database

operation requires sqlplus, so only Oracle Homes that are installed with
sqlplus are displayed.
Note
The selected Oracle Home must be an installation of Oracle version

9.2.0.x.
Step 9
G-4
Select the connect string to use when establishing a connection to the

Oracle Home. To use an existing connect string that does not appear on
the list, choose Other and enter a connect string.
Step 10
G-5
10.A
In the Username text box, specify the name of the database

owner.
10.B
In the Password text box, specify the password of the database

owner.
10.C
Reenter the password in the Confirm text box.

Note
The database user name specified in this window must be unique (not the
same as any existing user name for the Oracle database server).
G-6
Step 11
11.A
In the Username text box, enter the username of the Oracle

Administrator (the value for this parameter is usually SYSTEM.
However, your Database administrator may have modified it.)
11.B
In the Password text box, specify the password of the Oracle

Server Administrator (Default: MANAGER).
11.C
Re-enter the password in the Confirm text box.
11.D
Click Next to continue.

Note
If you have not already, obtain the values for this window now from your
database administrator.
G-7
Step 12
Select the desired tablespace size. For more information on these sizes,
see Table G-1.
Table G-1
Default Tablespace Size Settings
Database Element
Small
Medium
Large
Data Tablespace
50
250
500
Index Tablespace
20
100
200
Total Database Size (MB)
70 MB
350 MB
700 MB
G-8
Step 13
13.A
In the Name text box, specify Data Files Component Tablespace

Name (Default: <instance_name>_EM_USERS).
13.B
In the Location text box, specify the path for the Data Files
component (For example:
D:\Oracle\oradata\<instance_name>\data01.dbf).
13.C
In the Size text box, specify the size for the Data Files
component (Defaults: 50, 250, or 500 - depending on the selected
database size).
Note
The tablespace name and location specified in steps A and B (above)

must be new and unique for the current database installation. The path
specified must exist on the Database Server host computer.
G-9
Step 14
14.A
In the Name text box, specify Index Files Component

Tablespace Name (Default: <instance_name>_EM_INDEX).
14.B
In the Location text box, specify the path for the Index Files
component (For example,
D:\Oracle\oradata\<instance_name>\index01.dbf).
14.C
In the Size text box, specify the size for the Index Files
component (Defaults: 20, 100, or 200 - depending on the selected
database size).
Note
The tablespace name and location specified in steps A and B (above)

must be new and unique for the current database installation. The path
specified must exist on the Database Server host computer.
G-10
Step 15
This window lists various parameters for the Oracle database that will be
installed. Compare these values with the values of the pre-installation
planning sheet, verify that the list is correct, and click Next to continue
with the installation.
Step 16
The following window is displayed:
The procedure is complete.
G-11
G-12
This appendix describes special tuning that should be performed when

you install an Oracle database server on an AIX computer.
Note
The tuning steps that are described in this appendix should be performed
on the computer on which the Oracle database server was installed
(whether or not this is the same computer on which ENTERPRISE/CS
components were installed).
Memory contention occurs when processes require more memory than is
available. To cope with the shortage, the system pages programs and data
between memory and disks.
Controlling Buffer-Cache Paging Activity
Excessive paging activity degrades performance substantially, and can

become significant with databases created on JFS files. In this situation, a
large number of SGA data buffers might also have analogous JFS buffers
containing the most frequently referenced data. The behavior of the file
system buffer cache manager can have a significant impact on
performance. It can cause an I/O bottleneck, resulting in lower overall
system throughput.
In AIX, tuning buffer-cache paging activity is possible but must be done
carefully and infrequently.
H-1
There are four tunable AIX system parameters:

minfree
Minimum free-list size. Below this point, page stealing engages

to replenish the free list.
maxfree
Maximum free-list size. Above this point, page stealing

terminates.
minperm
Minimum number of buffer pages for file I/O.
maxperm
Maximum number of buffer pages for file I/O.
Note
You must be root to change the above limits with the vmtune
command. The AIX vmtune utility is operating-system version specific.
If you run the vmtune command executable from one release on a
different release, an operating system failure might result.
Tuning minfree and maxfree
You can base minfree on the working set size of the programs that
need a quick response. Basically, you need to have enough pages in the
free list so that the loaded program does not need to replenish the free
list. You can set the size of the working set for a program with the vmstat
command. maxfree should be greater than minfree by max(8,
maxpgahead).
For instance, if you find that minfree should be 128 and maxpgahead
is 16, you can use the following command:
/usr/lpp/bos/samples/vmtune -f 128 -F 144
to set minfree to 128 and maxfree to 144.
H-2
Tuning the AIX File Buffer Cache
The purpose of the AIX buffer cache is to reduce disk access frequency
when JFS files are used. If this cache is too small, disk usage increases
and potentially saturates one or more disks. (See also Controlling
Buffer-Cache Paging Activity, for the implications of increasing this
parameter). On the other hand, precious memory is wasted if the cache is
too large.
You can configure the AIX buffer cache by adjusting the minperm and
maxperm parameters. In general, if the buffer hit ratio is low (less than
90%, see sar -b), increasing minperm could help. If maintaining a
high buffer hit ratio is not critical, decreasing minperm increases the
physical memory available. Refer to your AIX documentation for more
information on this topic.
The performance gain cannot be quantified easily, because it depends on
the degree of multiprogramming and I/O characteristics of the workload.
Tuning minperm and maxperm
AIX provides a mechanism for the administrator to loosely control the

ratio of page frames used for files versus those used for computational
(working or program text) segments by adjusting the minperm and
maxperm values according to these guidelines:
If the percentage of real memory occupied by file pages falls below

minperm value, the page-replacement algorithm steals both files and
computational pages, regardless of repage rates.
If the percentage of real memory occupied by file pages rises above

maxperm value, the page-replacement algorithm steals only file
pages.
If the percentage of real memory occupied by file pages is between

minperm and maxperm, the VMM normally steals only file pages,
but if the repaging rate for file pages is higher than the repaging rate
for computational pages, computational pages are stolen as well.
H-3
The following algorithm calculates the default values:
minperm (in pages) = ((number of page frames)-1024) * 0.2

maxperm (in pages) = ((number of page frames)-1024) * 0.8
The following command:

vmtune -p 5 -P 20
changes minperm to 5% of the total number of page frames, and

maxperm to 20% of the total page frames, as opposed to the defaults of
20% and 80%, respectively. If the database files are on raw devices, then
minperm and maxperm can be set to low values (such as 5% and 20%,
respectively). This is because the AIX file buffer cache is not used for
raw devices. The memory might be better used for other purposes (such
as the Oracle System Global Area).
H-4
Working with CONTROL-M Databases

that are not Case-Sensitive
I
BMC Software recommends that CONTROL-M databases be configured
as case sensitive. This appendix describes various considerations that you
should be aware of if you choose to use a database server that is not case
sensitive.
Warning
You should avoid working with non-case-sensitive databases. Beginning

with the next version, BMC Software will no longer support work with
non-case-sensitive CONTROL-M databases.
CONTROL-M/EM
Versions 6.1.01 and 6.1.02 of CONTROL-M/EM support work only with
a case-sensitive database server. These versions did not allow installation
with non-case-sensitive database servers.
Versions 1.5.xx, 5.0.xx, 6.0.xx, and 6.1.03 of CONTROL-M/EM work
with case-sensitive databases. Although the installation process for these
versions also enables you to install CONTROL-M/EM with a non-casesensitive database server, nevertheless, BMC Software recommends that
you work with case-sensitive database servers.
I-1
CONTROL-M/Server
In previous versions of CONTROL-M/Server, case sensitivity depended
on the database server configuration. The CONTROL-M/Server database
is case sensitive if the database server is configured as case sensitive, and
not case sensitive if the database server is configured as non-casesensitive.
If you are running CONTROL-M/Server in a mode that is not case
sensitive, review and make adjustments to your job definitions, calendar
names, table names, commands, and so on, to avoid the severe problems
that can be caused by case sensitivity conflicts.
Implications of Changing from Case-Sensitive

to Non-Case-Sensitive Mode
The procedure of moving from a case-sensitive database to one that is not
case sensitive is very delicate. The change process includes a serious
likelihood of data loss. This is especially true when there are data fields
and values that are different only because the cases sensitivity of the
individual characters within them is not identical.
Warning
The process of moving from a case-sensitive database to a non-casesensitive database is not recommended.
If a CONTROL-M version 6.1.03 database is installed on an MSSQL
database server, the database is built as a case-sensitive database,
regardless of the setting of the MSSQL server. When you work with
Sybase database servers, however, the case sensitivity of the CONTROLM version 6.1.03 database will always match the configuration of the
Sybase database server.
Sybase database servers can be configured as either of the following:
I-2
Case sensitive The database server differentiates between

lowercase letters and uppercase letters (for example, a and A are
considered as having different values).
Non-case-sensitive The database server does not differentiate

between lowercase letters and uppercase letters (for example, a and A
are considered as having the same values).
Note
If you are running databases under both CONTROL-M/Server and

CONTROL-M/EM, BMC Software recommends that you configure both
databases to identical case sensitivity. This will help avoid possible data
loss or other severe problems that may be caused by case sensitivity
conflicts when data is exchanged between the two components.
Implications of Changing from Non-CaseSensitive to Case-Sensitive Mode

When you are operating in a non-case-sensitive mode, data such as the
name of a job can be entered in one case and referred to in a different
case. For example, if you entered a job named MYJOB, you can then
refer to the same job as myjob or MyJob. This is because case is ignored
in a non-case-sensitive database, and any reference that uses the same
characters in the same order produces the same result.
I-3
In case-sensitive mode, data that was entered in one case can be referred
to only by using the same case. The same spelling in a different case is
considered a different value. In the examples shown in the preceding
paragraph, because MYJOB, myjob, and MyJob, do not use the
identical case for every character in the job name, each refers to a
different job.
Warning
If you attempt to transfer data in a non-case-sensitive database, to a casesensitive database, you must first ensure that you include all the required
data under only one of the job names. Thereafter, you should not use a
variant of that particular job name unless you understand that doing so
will create a different data set.
Example 1
A job is defined using the ctmdefine utility and the job name is specified
as MyJob.
The ctmorder utility is used to order the above job and this time the job is
specified as myjob.
In non-case-sensitive mode the ctmorder utility orders the job.
However, in case-sensitive mode the job is not ordered and the following
error message is issued:
job not found in table
Example 2
Two scheduling tables are defined: Tab1 and Tab2
Tab1 is associated with a user daily job named MyDay.

Tab2 is associated with a user daily job named MYDAY.
If you are operating in non-case-sensitive mode, the ctmudly utility will

order both tables when myday (another variant using the same characters
but with different case) is specified as the name of the user daily job.
I-4
However, in case-sensitive mode, if you specify myday as the name of

the user daily job, neither table is ordered. Specifying MyDay as the
name of the user daily job will order only the Tab1 table. Specifying
MYDAY as the name of the user daily job will order only the Tab1 table.
I-5
I-6
This appendix describes configuration procedures for running

CONTROL-M/EM, CONTROL-M/Desktop, CONTROL-M/Server,
CONTROL-M/Agent, and CONTROL-M/eTrigger with different
languages.
CONTROL-M provides different levels of support for the following
languages:
Japanese
Western European Languages
English (USA)
English (British)
Spanish
German
French
J-1
Japanese
CONTROL-M can run on Japanese-enabled operating systems.
The CONTROL-M components, such as the CONTROL-M/EM GUI and
CONTROL-M/Desktop, do not accept Japanese characters in any free
text fields or parameters and display values only in English. For example,
Japanese job sysouts do not display correctly. Therefore, in these cases,
job sysout analysis is not possible.
For a list of Japanese-enabled operating systems compatible with
CONTROL-M, see the release notes.
Configuration Procedure Task Flow

Table J-1 lists:
the tasks for configuring language support

the computers on which the tasks should be performed
links to the instructions for performing the task
These tasks can be performed in any order.

Table J-1
Configuration Tasks for Japanese Language Support
Perform on Computers Running

Components of These Products
Task
Page
Pre-installation tasks for

Japanese Support on
Microsoft Windows
CONTROL-M/EM
CONTROL-M/Desktop
CONTROL-M/Server
CONTROL-M/Agent
CONTROL-M/eTrigger
Language Settings on page

4-5
Configuration Tasks for

Japanese Support on Unix
CONTROL-M/EM
CONTROL-M/Desktop
CONTROL-M/Server
CONTROL-M/Agent
CONTROL-M/eTrigger
J-3
J-2
Configuration Tasks for Japanese Support on Unix

Summary:
Perform this task to enable CONTROL-M components to run on Unix

operating systems that support Japanese.
Before You Begin
This task must be performed after installation or upgrade on every Unix

computer running CONTROL-M components including:
CONTROL-M/EM
CONTROL-M/Desktop
The Reporting facility
CONTROL-M/Server
CONTROL-M/Agent
CONTROL-M/eTrigger
CONTROL-M control modules
To Configure the Environment on Unix

Step 1
For all CONTROL-M components to communicate properly with each

other, you must set the Locale for all product components.
Warning
Discrepancies between Locale settings, especially those involving

different character sets, can corrupt data while data is passed from one
component to another.
Ensure that the required language locale is present on the computer.
1.A
To get a list of locales available on your computer, enter the

command: locale -a
J-3
1.B
Table J-2
Check that C, c, POSIX, or an English locale (according to

Table J-2) is displayed. If none of these locales is displayed, ask
your Unix administrator to install it.
ISO English Character Set Locale Settings for Unix (for Use with Japanese
Operating Systems)
Language
AIX
Solaris
Compaq (OSF)
HP-UX
English
(USA)
en_US.ISO8859-1
en_US.ISO8859-1
en_US.ISO8859-1
en_US.iso88591
English
(British)
en_GB.ISO8859-1
en_GB.ISO8859-1
en_GB.ISO8859-1
en_GB.iso88591
Step 2
Configure the user account by performing the following.

2.A
Set the following values in the .cshrc file. If necessary, add lines
for these environment variables.
Note
The lines should be added in the same order as the environment variables
are listed in Table J-3 on page J-5.
J-4
Table J-3
Unix Environment Variables for Japanese in the .cshrc File
Environment
Variable
Description / Value
LC_ALL
This environment variable should be (an empty string).

Set this variable by adding the following line to the .cshrc
file:
setenv LC_ALL
LC_CTYPE
LANG
LC_COLLATE
LC_MESSAGES
These environment variables should be C (or c, as defined

on the computer).
Note: If the C (or c) locale is not present, you can use
POSIX or one of the English locales that appear in Table
J-2 on page J-4.
Set these variables by adding the following lines to the
.cshrc file:
setenv LC_CTYPE C
setenv LANG C
setenv LC_COLLATE C
setenv LC_MESSAGES C
2.B
Run the following command to apply the new settings to the

environment:
source ~/.cshrc
Where to Go from Here
You have performed the configuration tasks in the Unix environment for
Japanese. Perform the remaining procedures listed in Table J-1 on page
J-2 as relevant at your site.
J-5
Western European Languages

Overview
This section contains instructions for configuring CONTROL-M/EM,
CONTROL-M/Server, CONTROL-M/Agent, and database servers
(Oracle, Sybase, and MSSQL) to enable the support of Western European
language special characters for the following components:
The CONTROL-M/EM GUI

CONTROL-M/Desktop
CONTROL-M/Server utilities
CONTROL-M/Agent utilities
CONTROL-M/eTrigger
These components can accept characters in English, German, Spanish,

and French from the Latin-1 character set (ISO 8859-1) in almost all text
fields and parameters.
Note
For a list of parameters that support Western European Language special

characters, see J-47.
J-6
The following characters are not supported for any parameter under any
circumstances:
Warning
Customization tasks must be performed on every computer or Unix

account running CONTROL-M/EM, CONTROL-M/Server,
CONTROL-M/Agent, and CONTROL-M/eTrigger. This effort must be
coordinated by administrators for each of these products across the entire
enterprise. Problems can occur if not all products are configured the same
way.
Compatibility with Prior Versions

CONTROL-M/EM can communicate in English with
CONTROL-M/Servers from versions prior to version 6.1.03 that do not
handle Western European language special characters, as well as
CONTROL-M for OS/390 installations. This communication is possible
because the Gateway detects the type and version of the connected
CONTROL-M/Servers (and other CONTROL-M installations such as
OS/390) and translates the data accordingly.
Before You Begin
Customization tasks must be performed on every computer or Unix

account running CONTROL-M/EM, CONTROL-M/Server,
CONTROL-M/Agent, and CONTROL-M/eTrigger. This effort must
be coordinated by administrators for each of these products across
the entire enterprise. Problems can occur if not all products are
configured the same way.
J-7
Locale settings must be the same on every computer or Unix account

running CONTROL-M/EM, CONTROL-M/Server,
CONTROL-M/Agent, and CONTROL-M/eTrigger. The tasks in this
section provide instructions for checking and setting the locale.
Warning
Conflicts between the locale settings on each computer and Unix

account, especially when involving different character sets, may cause
data corruption.
Upgrade and Migration Considerations
When upgrading or migrating to CONTROL-M version 6.1.03, the

upgrade and migration processes do not automatically configure the
database for ISO Latin-1 language support.
When working with an existing Sybase database server: The upgrade

and migrate procedures do not configure the database server when
using a database that was created by a previous installations or one
that was created by the customer.
When working with an existing MSSQL database server, and when

upgrading: The database must be configured as case-sensitive when
configuring for foreign languages. For more information, see
Appendix I, Working with CONTROL-M Databases that are not
Case-Sensitive.
J-8
Additional Resources
For additional information, see the following guides:
Task
Topic and Book
List of the parameters that support

Western European Language special
characters
Parameters that Support Western

European Language Special
Characters on page J-47
Indications of which parameters do

not support Western European
Language special characters
Individual parameter descriptions in

the CONTROL-M Job Parameter and
Variable Reference Guide
Upgrade and migration instructions
CONTROL-M Upgrade Guide
CONTROL-M/eTrigger customization
instructions
Use Locale topic in Chapter 4 of the

CONTROL-M/eTrigger Administrator
Guide
Configuration Procedure Task Flow

Table J-4 lists:
the tasks for configuring language support

the computers on which the tasks should be performed
links to the instructions for performing the task
These tasks can be performed in any order.
J-9
Table J-4
Configuration Tasks for Western European Language Support
Perform on Computers Running

Components of These Products
Task
Page
General Configuration on Microsoft

Windows
CONTROL-M/EM
CONTROL-M/Desktop
CONTROL-M/Server
CONTROL-M/Agent
CONTROL-M/eTrigger
J-12
General Configuration on Unix
CONTROL-M/EM
CONTROL-M/Desktop
CONTROL-M/Server
CONTROL-M/Agent
CONTROL-M/eTrigger
J-18
Additional CONTROL-M/EM
Configuration
CONTROL-M/EM
J-22
Additional CONTROL-M/Agent
Configuration on Unix
CONTROL-M/Agent on Unix
J-25
Database Configuration
Any one database client that connects to the

Database Server (Oracle, Sybase, or
MSSQL)
J-26
Note
Troubleshooting tips are provided on page J-44.
Additional Considerations
Product / Component
Comments
CONTROL-M/Desktop
When CONTROL-M/Desktop is first installed, its

language is set according to the local settings of
the computer. When CONTROL-M/Desktop
connects to the GUI Server the first time,
CONTROL-M/Desktop language settings will
automatically be updated to match those of
CONTROL-M/EM.
J-10
Product / Component
Comments
CONTROL-M control
modules
No additional language configuration is

necessary for control modules. Language
configuration for control modules is handled
when CONTROL-M/Agent is configured for
language support.
CONTROL-M eTrigger
For instructions on setting the Use Locale

parameter, see the CONTROL-M/eTrigger
J-11
General Configuration on Microsoft Windows

Summary:
Perform this task to enable specification of Western European special

characters from the Latin-1 character set.
Before You Begin
This task must be performed on every Microsoft Windows computer

running components of the following products:
CONTROL-M/EM
CONTROL-M/Desktop
CONTROL-M/Server
CONTROL-M/Agent
CONTROL-M/eTrigger
To Configure the Environment on Microsoft Windows

Step 1

other, you must set the Locale for all product components to the same
value.
Warning

Ensure that the required language locale is present on the computer using
the procedure relevant to your operating system.
J-12
Microsoft Windows 2000

1.A
Choose Settings => Control Panel => Regional Options from

the Start menu.
1.B
On the Input Locales tab, add the desired language to the list of
installed input locales. Click OK.
Microsoft Windows XP and 2003
Step 2
1.A
Choose Settings => Control Panel => Regional and Language

Options from the Start menu.
1.B
Using the Details field in the Languages tab, add the desired
language to the list of installed input locales. Click OK.
Configure the Command Prompt window code page.

2.A
Open a Command Prompt window by choosing Run from the

Start menu and typing cmd. Press Enter.
2.B
To set the code page for the currently active Command Prompt
window, type chcp 1252 and press Enter.
Active Code Page: 1252 is displayed.
Note
Step 2.B must be done each time you open a Command Prompt window
for the purposes of configuring Western European language support. For
instructions on setting the Command Prompt code page on a permanent
basis, see page J-16.
J-13
Step 3
Configure the font of the Command Prompt window.

3.A
Right-click on the upper-left corner of the Command Prompt

window and select the Properties option.
3.B
Set the font on the Font tab to Lucida Console and click OK.
3.C
At the prompt, select the Save properties for future windows

with same title option to save the properties as a default. These
changes will be set automatically each time a Command Prompt
window is opened. Click OK.
J-14
You have performed the general configuration tasks in the Microsoft

Windows environment. Perform the remaining procedures listed in Table
J-4 on page J-10 as relevant at your site.
J-15
Setting the Default Microsoft Windows Command Prompt Code Page

Summary:
This optional task sets the default code page to 1252 for all Microsoft
Windows Command Prompt windows.
If this task is not performed, the code page must be set manually each
time a Microsoft Windows Command Prompt window is opened.
To Set the Default Code Page Using the Microsoft Windows Registry
Warning
BMC Software recommends that only users experienced with the

Microsoft Windows Registry attempt to edit it, and only after backing it
up first.
Step 1
Define the following entry in the Microsoft Windows Registry:

User Key: [HKEY_LOCAL_MACHINE\Software\Microsoft\CommandProcessor]
Value Name: AutoRun
Data Type: REG_SZ (String Value)
Value Data: chcp 1252
If the AutoRun entry does not exist, create it:

Click the right mouse button inside the right pane.
Select New --> String Value.
Specify AutoRun as the entry name.
If the entry exists with another value that you want to keep:
Create a batch file containing the original value on the first line
and the command chcp 1252 on the second line.
J-16
Save the batch file in a location that is included in the path

environment variable.
Specify the batch file name as the entry value data.
Note
Alternatively, you can create a .reg file to update the Microsoft Windows
registry:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\Software\Microsoft\CommandProcessor]
"CompletionChar"=dword:00000000
"DefaultColor"=dword:00000000
"EnableExtensions"=dword:00000001
"AutoRun"="chcp 1252"
You have completed setting the default code page. Perform the remaining
sub-steps under Step 2 on page J-13.
J-17
General Configuration on Unix

Summary:
Perform this task to enable specification of Western European special

characters from the Latin-1 character set.
Before You Begin
This task must be performed on every computer or Unix account running

components of the following products:
CONTROL-M/EM
CONTROL-M/Server
CONTROL-M/Agent
To Configure the Environment on Unix

Step 1

other, you must set the Locale for all product components to the same
value.
Warning

Ensure that the required language locale is present on the computer.
1.A
To get a list of locales available on your computer, enter the

command: locale -a
1.B
Check that the desired language appears according to Table J-5.

If the desired locale does not appear, ask your Unix administrator
to install it on the computer.
J-18
Table J-5
ISO Latin-1 Character Set Locale Settings for Unix
Language
AIX
Solaris
Compaq (OSF)
HP-UX
English
(USA)
en_US.ISO8859-1
en_US.ISO8859-1
en_US.ISO8859-1
en_US.iso88591
English
(British)
en_GB.ISO8859-1
en_GB.ISO8859-1
en_GB.ISO8859-1
en_GB.iso88591
German
de_DE.ISO8859-1
de_DE.ISO8859-1
de_DE.ISO8859-1
de_DE.iso88591
French
fr_FR.ISO8859-1
fr_FR.ISO8859-1
fr_FR.ISO8859-1
fr_FR.iso88591
Spanish
es_ES.ISO8859-1
es_ES.ISO8859-1
es_ES.ISO8859-1
es_ES.iso88591
Note
When configuring CONTROL-M/Agent on operating systems not listed

in Table J-5, use the locale setting for the operating system that
corresponds to the one selected for CONTROL-M/EM and
CONTROL-M/Server. Contact your Unix administrator for additional
assistance.
Step 2
Configure the user account by performing the following.

2.A
Set the following values in the .cshrc file. If necessary, add lines
for these environment variables.
Note
The lines should be added in the same order as the environment variables
are listed in Table J-6 on page J-20.
J-19
Table J-6
Unix Environment Variables for Western European Languages

in the .cshrc File
Environment
Variable
Description / Value
LC_ALL
This environment variable should be (an empty string).

file:
setenv LC_ALL
LC_CTYPE
and
LANG
These environment variables should be set to the value of

the required language locale. See Table J-5 on page J-19
for Unix locales.
Set these variables by adding the following lines to the
.cshrc file:
setenv LC_CTYPE <locale_name>
setenv LANG <locale_name>
LC_COLLATE
This environment variable should be C for all languages

(or c, as defined on the computer). To check if the C locale
is present, use the locale -a command.
J-5 on page J-19.
file:
setenv LC_COLLATE C
LC_MESSAGES
For CONTROL-M/Server only:

This environment variable should be C (or c, as defined on
the computer) for all languages on accounts where
CONTROL-M/Server is installed. To check if the C locale is
present, use the locale -a command.
J-5 on page J-19.
file:
setenv LC_MESSAGES C
J-20
The following examples reflect the values that will be set after
applying the values to the environment in the next step.
LC_ALL=
LC_CTYPE=de_DE.ISO8859-1
LANG=de_DE.ISO8859-1
LC_COLLATE=C
LC_MESSAGES=C
2.B
Run the following command to apply the new settings to the

environment:
source ~/.cshrc
You have performed the general configuration tasks in the Unix

environment. Perform the remaining procedures listed in Table J-4 on
page J-10 as relevant at your site.
J-21
Additional CONTROL-M/EM Configuration

Summary:
Perform this task on computers running CONTROL-M/EM components

to enable specification of Western European special characters from the
Latin-1 character set.
Before You Begin
This task must be performed on every computer or Unix account running

components of the following products:
CONTROL-M/EM
CONTROL-M/Desktop
To Configure the CONTROL-M/EM Environment

Step 1
Set the following system parameters by choosing Tools => System

Parameters in the Administration facility.
J-22
Table J-7
Setting System Parameters
Parameter
Section
Description
Language
General
This parameter defines the language for the

entire CONTROL-M enterprise. Valid values
are:
use_account_locale for the local system
locale as defined on the account or
computer.
English for both American and British
English.
German for German.
French for French.
Spanish for Spanish.
These values are not case-sensitive.
EBCDIC_cp
Gateway
This parameter, which is relevant for

CONTROL-M for OS/390 users only, defines
the EBCDIC code page to which ASCII data will
be translated.
Note: The same character set code should be
defined in CONTROL-M for OS/390.
Valid values are:
0 for the default translation table created in
the previous version of CONTROL-M.
1047 for English (USA)
285 for English (British)
273 for German
297 for French
284 for Spanish
Notes:
Using the Comp. Name field, you can set the
scope for this parameter. Specify either a
specific CONTROL-M name in the Comp.
Name field, or specify an asterisk (*) for all
CONTROL-Ms. For instructions on modifying
system parameters, see the instructions for
displaying and modifying system parameters in
the CONTROL-M/Enterprise Manager
J-23
Step 2
If CONTROL-M components were running when these system

parameters were modified, recycle the components.
You have completed the additional configuration tasks for

CONTROL-M/EM. Perform the remaining procedures listed in Table J-4
on page J-10 as relevant at your site.
J-24
Additional CONTROL-M/Agent Configuration on Unix

Summary:
Perform this task on Unix accounts running CONTROL-M/Agent

components.
Before You Begin
This task must be performed on every Unix account running

CONTROL-M/Agent components.
To Configure the CONTROL-M/Agent Environment on Unix
Run the ctmagcfg interactive utility to set the Locale parameter in the
CONFIG.dat file to one of the values in Table J-5, ISO Latin-1
Character Set Locale Settings for Unix, on page J-19.
Note
When configuring CONTROL-M/Agent on operating systems not listed

in Table J-5, ISO Latin-1 Character Set Locale Settings for Unix, on
page J-19, use the locale setting for the operating system that
corresponds to the one selected for CONTROL-M/EM and
CONTROL-M/Server. Contact your Unix administrator for additional
assistance.
You have completed the additional configuration tasks for

CONTROL-M/Agent on Unix. Perform the remaining procedures listed
in Table J-4 on page J-10 as relevant at your site.
J-25
Database Configuration
Summary:
This task configures the database servers and clients.

Configure the database server and clients for the desired language
according to the database vendor.
Select the Procedure for Your Database

Task
Reference
Oracle Configuration
page J-27
page J-31
MSSQL Configuration for the CONTROL-M/EM Database
page J-39
MSSQL Configuration for the CONTROL-M/Server Database
page J-39
MSSQL Configuration for Clients
page J-42
J-26
Oracle Configuration
Summary:
Run this procedure for your Oracle database to support Western

European language special characters.
Before You Begin
Perform this task once, on any computer with a database client that
connects to the Oracle database server.
Note
Do not perform this task for all database clients.
To Configure Oracle
Step 1
Check the database configuration from within an SQLPLUS session.

1.A
Check the character set currently in use with the following

command:
select value from nls_database_parameters
where parameter='NLS_CHARACTERSET';
Depending on the output displayed, take the appropriate actions
as indicated in Table J-8.
Table J-8
Possible Character Sets Outputs and Corresponding Actions for Oracle
Output
Description and Action
VALUE
-----------------------WE8ISO8859P1
The current character set is compatible with the ISO Latin-1

character set. No changes are necessary. Continue with Step 1.C
below.
VALUE
-----------------------US7ASCII
The current character set is not compatible with the ISO Latin-1
character set, but can be changed. Continue with Step 1.C below.
Any other output
The current character is not compatible. To find out if character set

conversion is possible without data loss, continue with Step 1.B .
J-27
1.B
To verify that character set conversion is possible without data

loss, run the Oracle Scanner utility (csscan.exe located in the
Oracle binaries directory). This utility simulates the new
character sets and generates a report containing the (system or
user) objects that will be affected if the character set is changed.
For the latest version of the utility and more information on
running it, see the Oracle OTN site at
http://otn.oracle.com/software/tech/globalization/index.html.
If the conversion completes successfully and no problems are
indicated in the generated report, continue with the following
steps. If problems are listed in the report, contact BMC Software
Technical Support.
1.C
Check the sort order:

select * from nls_database_parameters Where
parameter in ('NLS_COMP','NLS_SORT');
The output should be similar to the following, indicating the
binary sort order:
PARAMETER
VALUE
-------------------------- ----------NLS_SORT
BINARY
NLS_COMP
BINARY
If the sort order is different, contact BMC Software Technical
Support. Do not continue customizing Western European
language support.
J-28
Skip the remaining steps if, after checking the database configuration
in Step 1, the current database configuration is compatible with the
ISO Latin-1 character set and a binary sort.
Step 2
Shut down all components and applications that may connect to the
database server, including the following:
Step 3
GUI Server
Gateway
Global Conditions Server (GCS)
CONTROL-M/Server
Global Alerts Server (GAS)
Export the data by running the command appropriate for the application
(as a safety precaution):
Application /
Component
CONTROL-M/EM
Command
Unix:
ecs util -U<user> -P<password> -export -type all -file
<export_file>
Microsoft Windows:
util -U<user> -P<password> -export -type all -file
<export_file>
CONTROL-M/Server
Step 4
ctm_backup_bcp
Log in to the SQLPLUS application with administrator privileges using

the following commands:
sqlplus /nolog
connect / as sysdba
Step 5
Shut down the database using the command:

SHUTDOWN IMMEDIATE;
J-29
Step 6
Run the following command sequence to configure the database

character set:
STARTUP MOUNT;
ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE OPEN;
ALTER DATABASE CHARACTER SET INTERNAL_USE WE8ISO8859P1;
Step 7
Shut down and restart the database for the changes to take effect by
running the following commands:
SHUTDOWN IMMEDIATE
STARTUP;
Step 8
Restart all components that you shut down.
You have completed the configuration tasks for your database server.
Perform the remaining procedures listed in Table J-4 on page J-10 as
relevant at your site.
J-30
Summary:
Run this procedure for your Sybase Adaptive server to support Western
Before You Begin
Perform this task once on the SA account of the Sybase Adaptive server.
To Configure Sybase
Step 1
Check the character set by running the following commands within the
isql session.
1.A
Check the character set by running the following command:

sp_configure "default character set id"
go
If the output is a number other than 1, you will have to configure
the character set.
1.B
Check the sort order by running the following command:

sp_configure "default sortorder id"
go
If the output is a number other than 50, you will have to
configure the sort order.
J-31
Skip the remaining steps if, after checking the database configuration
in Step 1, the current database configuration is compatible with the
ISO Latin-1 character set and a binary sort.
Warning
If the database server was originally configured for the Roman-8

character set, and extended ASCII characters (characters with an ASCII
value greater than 128) were used, some data might be lost when
reconfiguring the database. Contact BMC Software technical support.
Step 2
Step 3
GUI Server
Gateway
CONTROL-M/Server
Export the data by running the command appropriate for the application:
Application /
Component
CONTROL-M/EM
Command
Unix:
ecs util -U<user> -P<password> -export -type all -file
<export_file>
Microsoft Windows:
<export_file>
CONTROL-M/Server
J-32
ctm_backup_bcp
Step 4
Drop the database by running the command appropriate for the

application.
Application /
Component
CONTROL-M/EM
Command
Unix:
ecs util -U<user> -P<password> -clean_database
Microsoft Windows:
util -U<user> -P<password> -clean_database
CONTROL-M/Server
Step 5
Skip this step.
To configure the character set and/or the sort order, perform the
following steps.
Note
Changing of the character set and sort order of the database server (Step
5.A through Step 5.D) affects all databases associated with the database
server. You cannot retain the original sort order and character set for a
database on the same database server that does not relate to
CONTROL-M/EM or CONTROL-M.
To handle this situation, install another database server and create a new
database for use with CONTROL-M/EM or CONTROL-M/Server, as
necessary. The sort order and character set for the new database server
should be configured according to Step 5.A through Step 5.D.
5.A
Change to the directory where the Sybase Adaptive server is

installed:
Unix: cd $SYBASE/charsets/iso_1
Microsoft Windows: cd %SYBASE%\charsets\iso_1
5.B
Run the following command:

charset -U<username> -P<password> -S<server
name> binary.srt
J-33
5.C
Run the following command from within an ISQL session to

change the character set:
sp_configure "default character set id",1
5.D
Run the following command to change the sort order:

sp_configure
Step 6
"default sortorder id",50
Rebuild the database.

Application /
Component
CONTROL-M/EM
Action
Run the following command according to the operating
system:
Unix:
ecs util -U<user> -P<password> -build_schema
Microsoft Windows:
util -U<user> -P<password> -build_schema
CONTROL-M/Server
Step 7
Use the CONTROL-M Main menu to rebuild the

database using the Database Creation menu
described in the Maintenance chapter in the
CONTROL-M/Server Administrator Guide.
Import the data.

Application /
Component
CONTROL-M/EM
Command
Unix:
ecs util -U<user> -P<password> -import -replace -type
all -file <export_file>
Microsoft Windows:
util -U<user> -P<password> -import -replace -type all
-file <export_file>
<export_file> is the name of the file exported in Step 3
on page J-32.
CONTROL-M/Server
J-34
ctm_restore_bcp
Step 8
J-35
MSSQL Configuration for the CONTROL-M/EM Database

Summary:
Run this procedure for your CONTROL-M/EM MSSQL database to

support Western European language special characters.
To Configure the MSSQL Server Database

Step 1
Log in as a regular user to the database that you want to configure for
Western European language support.
Step 2
Check the character set, code page, and sort order of the database
configuration by running the following command from within the isql
session:
declare @X varchar(40)
SELECT @X=CAST(DATABASEPROPERTYEX( db_name() , 'Collation' ) AS VARCHAR)
SELECT 'Database Collation: ' + description FROM ::fn_helpcollations()
WHERE name=@X
SELECT 'Database Code Page ' + CAST(COLLATIONPROPERTY(@X, 'CodePage')
As VARCHAR)
Check the following database collation attributes. If an attribute does not

match, you have to reconfigure the database.
Attribute
Value
Character Set
Latin1-General
Sort Order
binary sort
Database Code Page
1252
If all the attributes match, you do not need to reconfigure the database.
Skip the remaining steps and perform the instructions for MSSQL
Configuration for Clients on page J-42.
Step 3
GUI Server
Gateway
J-36
Step 4
Export the data by running the following command:

<export_file>
Step 5
Drop the database by running the following command.

util -U<user> -P<password> -clean_database
Step 6
Configure the database server for the ISO-1 character set, code page
1252, and the binary sort order.
6.A
Find the database name using the command:

select
6.B
db_name()
Verify that the database is empty using the query:

Select count(*) from sysobjects where
type='U' and name <>'dtproperties'
Note
If the database is not empty (meaning, the output from the previous query
is not equal to 0), contact BMC Software technical support.
6.C
Use the following command to verify that no other user is

connected to this specific database:
select count(*) from master..sysprocesses
where dbid=DB_ID()
Note
If other users or applications are currently connected to the database

(meaning, the output from the previous query is not equal to one you),
request that all users disconnect and shut down all connected
applications.
J-37
6.D
Log in as a system administrator and run the following

command:
Alter database <database name> Collate
Latin1_General_BIN
Step 7
Rebuild the database by running the following command:

util -U<user> -P<password> -build_schema
Step 8
Load the data by running the following command:

util -U<user> -P<password> -import -replace -type all
-file <export_file>
<export_file> is the name of the file exported in Step 4 on page J-44.

Step 9
Configure the MSSQL clients using the instructions provided in
MSSQL Configuration for Clients on page J-42.
J-38
MSSQL Configuration for the CONTROL-M/Server Database

Summary:
Run this procedure for your CONTROL-M/Server MSSQL database to

support Western European language special characters.
Before You Begin
Perform this task once, on any computer with a database client that
connects to the MSSQL database server.
Note
Do not perform this task for all database clients.
To Configure the MSSQL Server

Step 1
Log in as a regular user to the database that you want to configure for
Western European language support.
Step 2
Check the character set, code page, and sort order of the database
configuration by running the following command from within the isql
session:
declare @X varchar(40)
SELECT @X=CAST(DATABASEPROPERTYEX( db_name() , 'Collation' ) AS VARCHAR)
SELECT 'Database Collation: ' + description FROM ::fn_helpcollations()
WHERE name=@X
SELECT 'Database Code Page ' + CAST(COLLATIONPROPERTY(@X, 'CodePage')
As VARCHAR)
J-39
Check the following database collation attributes. If an attribute does not

match, you have to reconfigure the database.
Attribute
Value
Character Set
Latin1-General
Sort Order
binary sort
Database Code Page
1252
If all the attributes match, you do not need to reconfigure the database.
Skip the remaining steps and perform the instructions for MSSQL
Configuration for Clients on page J-42.
Step 3
Step 4
CONTROL-M/Server
Export the data by running the following command:

ctm_backup_bcp
Step 5

ctmmakedb -existing
This process deletes the MSSQL database and rebuilds it configured for
Western European language special characters.
Step 6
Load the data by running the following command.

ctm_restore_bcp
Step 7
J-40
Configure the MSSQL clients using the instructions provided in
MSSQL Configuration for Clients on page J-42.
J-41
MSSQL Configuration for Clients

Summary:
Run this procedure for your MSSQL database clients to support Western
Before You Begin
Perform this task on every computer with an MSSQL database client,

including:
Gateway
GUI Server
CONTROL-M/Server
Global Condition Server (GCS)
Global Alert Server (GAS)
To Configure MSSQL Clients

Step 1
Choose Start -> Programs -> Microsoft SQL Server -> Client
Network utility. The SQL Server Client Network Utility dialog box is
displayed.
Step 2
Select the DB-Library Options panel.
J-42
Step 3
Clear the checkmark for the Automatic ANSI to OEM conversion field.
Step 4
Check the Use international settings field.
Step 5
Click OK.
You have completed the configuration tasks for your database clients.
J-43
Troubleshooting
This section provides troubleshooting tips and techniques related to
Western European language special character support.
When attempting to connect to CONTROL-M/Server, the following error message is
issued to the CONTROL-M/EM Gateway or CONTROL-M/Server log:
GATEWAY OLDER THAN 613 CANNOT CONNECT TO A DATA CENTER 613 OR
ABOVE
Explanation
Until CONTROL-M version 6.1.03, data passed between

CONTROL-M/Server and the Gateway was translated between EBCDIC
and ASCII as necessary. As of version 6.1.03, all data is passed as is, in
ASCII.
If CONTROL-M/Server versions are not defined correctly in
CONTROL-M/EM, the Gateway will not successfully connect to the
CONTROL-M/Server.
In this case, a CONTROL-M/Server version 6.1.03 (or non-server
CONTROL-M installation such as OS/390) is defined as a version prior
to version 6.1.03 in CONTROL-M/EM.
Action
Use the Communication Status window in the CONTROL-M/EM

Administration facility to redefine the CONTROL-M/Server components
as version 6.1.03 or later.
The status of a CONTROL-M/Server version 6.1.0x is Up, but there is no
communication or synchronization.
Explanation
Until CONTROL-M version 6.1.03, data passed between

CONTROL-M/Server and the Gateway was translated between EBCDIC
and ASCII as necessary. As of version 6.1.03, all data is passed as is, in
ASCII.
J-44
If CONTROL-M/Server versions are not defined correctly in

CONTROL-M/EM, the Gateway will not successfully connect to the
CONTROL-M/Server.
If a CONTROL-M/Server version earlier than version 6.1.03 (or
non-server CONTROL-M installation such as OS/390) is defined as
version 6.1.03, the CONTROL-M/Server remains up but communication
is down.
Action
Use the Communication Status window in the CONTROL-M/EM

Administration facility to redefine all CONTROL-M/Server components
to the correct 6.1.0x version.
Communication cannot start up between CONTROL-M/EM version 6.1.02 and
CONTROL-M/Servers 6.1.03.
Explanation
While the Gateway can detect whether a CONTROL-M/Server is the

correct version and function accordingly, CONTROL-M/Server can only
communicate with CONTROL-M/EM components that are version
6.1.03 or later. If the CONTROL-M/EM version is 6.1.02 or earlier,
Western European languages will not be supported.
Action
Check that all CONTROL-M/EM components are version 6.1.03 or later.

If necessary, upgrade CONTROL-M/EM. For upgrading, see the
J-45
Data inconsistencies exist between CONTROL-M components

Explanation
Language configuration settings (such as Locale) are not the same on all
computers and Unix accounts running CONTROL-M/EM and
CONTROL-M components across the enterprise.
Action
Configure the same language for all CONTROL-M components.
J-46

Characters
This section lists parameters that support Western European language
special characters.
Note
Discrepancies between the language support for a parameter for OS/390

and other platforms is noted where relevant.
Table J-9

Characters (Part 1 of 3)
Parameters
Sub-parameter
Application
Application Type
Author
Auto Edit (Set Var)
Name
Auto Edit (Set Var)
Value
Calendar Description
Calendar Name
Command
Condition Name
Confcal
Special characters are not supported in OS/390
Control Resources
Resource Name
CONTROL-M
Days Calendar (Month Days Calendar)
Description
Do AutoEdit
Name
Do AutoEdit
Value
Do Condition Name
Do ForceJob
Job Name
J-47
Table J-9

Parameters
Sub-parameter
Do ForceJob
SCD Table
Do Mail
cc
Do Mail
Message
Do Mail
Subject
Do Mail
To
Do Shout
Destination
Do Shout
MSG
Do Sysout
Prm
Do Sysout
From Class
Doc Lib
Doc Mem
File Name
From Class
Group
In Condition
Name
Job Name
Mem Lib
Mem Name
Node Group
Node ID
On Code
On Statement
On Statement
J-48
On Codes
Table J-9

Parameters
Sub-parameter
On Statement
Proc Step
On Statement
Program Step
Out Condition
Name
Over Lib
Owner
Password
Path
Periodic Calendar Values
Special characters are only supported by OS/390
Quantitative Resources
Name
Scheduling Table
Name
Scheduling Tag
Name
Shout
Message
Shout
To (Destination)
Step Range
Name
Sysout
From Class
Sysout
Parameter
User Daily
User Name
Week Days Calendar
J-49
J-50
Index
Index
Symbols
$IT_PRODUCT_DIR directory 16-3
A
aborting installation. cleanup 16-2
accounts
CONTROL-M/EM 2-22, 3-17
CONTROL-M/Server 2-24, 3-19
Add Job Object Statistics to Sysout
CTM/Agent for Windows 13-6
Administration facility
diskspace (Windows) 4-5
registering components 15-6
registering gateways 15-10
administrators
database password 7-10
DB server password 8-7
unix account 2-22, 2-24, 3-17, 3-19
AG_AGCMN DATA_VAL
CTM/Agent for Windows (silent) 14-6
AG_AGENT_TIMEOUT
AG_ATCMN DATA_VAL
AG_CTMPERM HOSTS_VAL

AG_CTMSHOST _VAL
AG_DFTPRT_VAL
AG_DOMAIN_ SERVER_VAL
AG_DOMAIN_VAL
AG_GON_AS_ USER_VAL
AG_JO_ STATISTICS_ VAL
AG_SRV_PASS
AG_SRV_PASS_ CONF
AG_SRV_USER
agent communication parameters
CONTROL-M/Server installation 9-15
Agent Name parameter
AGENT SERVICE STARTUP TYPE
AGENT_AS_PORT
CTM/Agent for Unix 12-16
AGENT_DEFLT_PRNT
Index

AGENT_INST parameter
AGENT_MAX_RETR
AGENT_NAME
AGENT_SA_PORT
AGENT_SERVICE
AGENT_SRV_BCKP_HOST
AGENT_SRV_HOST parameter
AGENT_TIME_BTW_RETR
AGENT_TIMEOUT
AGENT_TO_SERVER_PORT_NUMBER
CTM/Server for Windows 11-4
AGENT_USER
AGENTSERVICEINTERACTIVEDESKTO
P
CTM/Server for Unix 9-16
AIX
boot procedure 9-12
checking available memory 2-10
configuring NIS 12-4
setting AIO 2-14
support versions for CTM/Agent 12-2
tuning for Oracle database performance
H-1
Allow Service to Interact with Desktop
10-10
architecture
CONTROL-M components 1-3
ASYNC I/O State to be configured at system
start 2-15
authorization
CONTROL-M/Server user 10-3
installation requirements 4-7
Authorized CONTROL-M/ Server Hosts
Automatic startup type
CTM/Server for Windows service 10-9
Available Nodes. CONTROL-M/Server 10-5
B
Backup Socket Port Number 7-12
Sybase 7-10
Backup Socket port number. Sybase 9-19
Basic Client Components
description 8-5
batch file
silent installation (CTM/Server) 11-2
BMC Software, contacting ii
boot procedure
AIX 9-12
Compaq Tru64 9-13
CONTROL-M/Server 9-12
HP-UX 9-13
Solaris 9-13
C
CD_INST command
CONTROL-M/Server for Unix 9-4
troubleshooting 16-12
cd_inst.in file. silent install CTM/Agent for
Unix 12-14
CDs
oracle installation (Windows) 6-3

changing previous installation 17-17
Check Interval (Available) parameter 9-15
check_req.sh script 2-6, 3-5
checking
operating system requirements 2-6, 3-5
Oracle DB server 15-2
requirements for CTM/Agent 12-2
Sybase DB server 15-2
clean_ora_inst.sh script 16-4
cleanup. aborted installation 16-2
CLI. see command-line interface
Client and Administrator Components 8-5
Client Only. Oracle installation 5-1
clients
CONTROL-M/EM clients 8-3
CONTROL-M/EM silent installation
8-10
MSSQL database 1-6
Orbix (Windows) 8-9
cluster configuration
CTM support on windows 4-3
Cluster Management parameter
CLUSTER_DISK_GROUP
CLUSTER_DISK_NAME
CLUSTER_NETWORK_TO_USE
CLUSTER_VIRTUAL_SRV_NAME
COMM_TIMEOUT parameter. CTM/Server
for Windows 11-4
command-line interface
commands
communication
CTM Server to Agent 9-15
communication parameters
Communication protocol parameter 9-15,
9-16
communication timeout
CONTROL-M/Server for Windows 10-6
compact installation
Compaq Tru64
boot procedure 9-13
kernel parameters for Oracle 3-16
kernel parameters for Sybase 2-18
configuration
see also parameters
AIX 2-15
Compaq Tru64 (with Oracle) 3-16
Compaq Tru64 (with Sybase) 2-18
CONTROL-M environment 15-1
HP-UX kernel 2-13, 3-11
languages J-1
NIS 12-4
Oracle DB server 3-2
Orbix 16-3
Solaris (with Oracle) 3-14
Solaris (with Sybase) 2-16
Sybase SQL server 2-2
configured nodes
CTM/Server for Windows (silent) 11-8
control modules
operating system 13-3
with ctm agents 13-2
CONTROL-M
components 1-3
Index
data center definitions 15-8

diskspace requirements 2-11, 3-10
memory requirements 2-10
post-installation tasks 15-1
uninstall utility 17-11
windows requirements 4-2
controlm
administrator group 3-19
CONTROL-M database
Oracle configuration 3-2
owner name (DBO) 2-5
Sybase configuration 2-2
CONTROL-M Option for Oracle
with CTM/Agent for Unix 12-3, 12-6
CONTROL-M/Agent
communication protocol 9-15
communication timeout 9-15
communication with CTM/Server 9-15
description 1-3
installing on Unix 12-1
installing on Windows 13-1
multiple agents 13-2
silent install (Unix) 12-14
silent installation (Windows) 14-1
silent parameters (Unix) 12-16
status checking 9-15
Windows parameters 13-5
CONTROL-M/Control Modules
description 1-3
CONTROL-M/Desktop
CONTROL-M definitions 15-11
description B-1
job editing form 13-9
CONTROL-M/EM
Administration Facility 15-6
administrator account 2-22, 3-17
client installation 8-3
components B-1
CONTROL-M definitions 15-8
description 1-3
installation parameters (Unix) 7-8
job editing form 13-9
services list 16-10
silent client installation 8-10
starting components 15-2
TCP/IP port number 9-17
troubleshooting installation 16-2
workstation gateways B-3
CONTROL-M/EM Administration Agent
service 16-10
CONTROL-M/EM data tablespace file name
parameter description F-9
CONTROL-M/EM data tablespace name
install parameter F-9
CONTROL-M/EM data tablespace size
parameter description F-9
CONTROL-M/EM database
default tablespace sizes G-8
memory requirements D-1, D-6
size D-1
CONTROL-M/EM Database Log Device
Name
disk init 7-11
CONTROL-M/EM Database Name 7-12,
8-7
CONTROL-M/EM Database Owner (DBO)
Sybase 7-10
CONTROL-M/EM database user
CONTROL-M/EM GUI
CONTROL-M/EM GUI server
CONTROL-M/EM index tablespace file

name
CONTROL-M/EM index tablespace size
CONTROL-M/EM server components
multiple server installation B-4
CONTROL-M/EM SYSTEM password
CONTROL-M/EM TCP/IP Port Number
CONTROL-M/Enterprise Manager. see
CONTROL-M/EM
CONTROL-M/eTrigger
description 1-3
CONTROL-M/Server
administrator account 2-24, 3-19
boot procedure (Unix) 9-12
database name 9-21
database owner (Sybase) 9-18
database size 9-18
description 1-3
installation types (Unix) 9-14
parameters and prompts (Unix) 9-14
parameters and prompts (Windows) 10-5
post installation tasks (Unix) 9-10
starting 15-3
TCP/IP port number 9-17
troubleshooting installation (Unix)
16-12
CONTROL-M/Server database
data device name 9-22
log device name 9-22
CONTROL-M/Server DB Name 10-8
CONTROL-M/Server for Microsoft
Windows
silent installation 11-1
CONTROL-M/Server Host Name
in CTM/Agent configuration 12-20

CONTROL-M/Server IPC Port Number
10-7
CONTROL-M/Server Port. CTM/Agent
parameter 12-20
CONTROL-M/Agent
uninstall utility 17-14
cp command
server startup 9-13
CTM_DB_OWNER
CTM_DB_OWNER_PASSWORD
ctm_etcservices command 9-11
custom installation
CONTROL-M/EM 8-5
Custom option
dedicated Oracle installation 5-1
customer support iii
D
daemon. Orbix Node-daemon 8-8
data centers
definitions (in CTM/Desktop) 15-11
definitions (in CTM/EM) 15-8
Data Device Logical Name
data device name. Sybase 9-22
Data Device path parameter 7-11
Data Device Physical Full Path File Name
Data Device Size
data device type parameter
CONTROL-M/EM 7-11
Index
Data File Component. Oracle (Windows)

6-7
Data General
supported versions (CTM/Agent) 12-2
data physical device/path.Sybase 9-19
data tablespace
Oracle DB size 5-11
data tablespace file name
Oracle parameter 5-13
data tablespace name
data tablespace size
DATA_DEVICE_LOGICAL_NAME
parameter. CTM/Server for Windows 11-6
DATA_DEVICE_SIZE parameter.
DATA_PHYSICAL_DEVICE_FULLPATH_
FILE_NAME parameter
DATA_PHYSICAL_DEVICE_FULLPATH_
FILE_NAME parameter. CTM/Server for
Windows 11-6
database
see also MSSQL
see also Oracle
see also Sybase
Oracle configuration 3-2
owner name (DBO) 2-5
sybase configuration 2-2
Database (Data Portion) Size
Sybase 7-10
database administrator
installation tasks 1-7
database administrator password
CONTROL-M/EM 7-10
database clients
components requiring them 8-2
database files location 8-7
database instance name

database logs
database owner
CONTROL-M/EM (Windows) 8-8
CONTROL-M/EM with Sybase 7-10
password 6-6
Database redo log file 5-14
database rollback segments tablespace
parameters 5-15
database server
requirements B-5
supported versions 4-6
Database Server Administrator Password 8-7
Database Server Host Name
Oracle installation 6-6
Database Server Name 8-6
Database Server Properties
CONTROL-M/EM on Windows 8-8
Oracle on Windows 6-7
Database Server Type 8-6
database size parameter
Oracle (Unix) 5-11
parameters (Unix) 5-15
database temporary tablespace parameters
5-16
database user
install parameter 5-12
Database User Properties. Oracle on
Windows 6-6
databases
configuration options 1-4
installation CDs 1-9
installing Oracle on Unix 5-1
installing Oracle on Windows 6-1
date setting
Oracle database server 9-3
DB Owner
DB_SA_PASSWORD parameter
DB_SA_PASSWORD parameter.
DB_SERVER_HOSTNAME parameter
DB_SERVER_HOSTNAME parameter.
DBO password
default 7-10
DBO. see database owner
dedicated installation
CONTROL-M/EM with Sybase 7-9
database configuration 1-4
Oracle 5-1, 6-1
Default Agent
Default option
default printer
Agent 12-20
defaults
Default ctm agent 13-2
Desktop. see CONTROL-M/Desktop
destination
Destination Directory. CONTROL-M/EM
8-5
destination folder
devices

Sybase database 7-11
Digital Unix. see Compaq Tru64
directories
see also path
Oracle home 5-12
tmp directory 5-11
Disk Group. CONTROL-M/Server 10-5
disk init
description 2-19
diskspace
CONTROL-M/Agent for Unix 12-2
CTM on windows 4-5
databases on windows 4-6
MSSQL 4-6
Oracle requirements 3-10
Sybase requirements 2-11
DNS 9-16
documentation
accessing online xxii
conventions xxiii
online xxii
printed xxii
related publications xx
release notes xxiii
domain controller
Dual IP addresses 9-16
E
ECS_PORT_NUMBER parameter.
editing
silent.bat file 11-2
English J-12, J-18, J-22
ENTERPRISE/CS. see CONTROL-M/EM
Index
environment path. Windows 2000 16-6

environment variables 4-5
etc/services file
port numbers 9-11
examples
silent install CTM/Agent for Unix 12-14
silent.bat files for CTM/Server 11-8
existing installation
Oracle 5-1, 6-2
description B-2
Global Condition server
graphical user interface. see GUI
GUI B-1
see also CONTROL-M/EM GUI
GUI Server. see CONTROL-M/EM GUI
Server
failover installation
port numbers 9-16
fd_value parameter. CTM/Agent for Unix
12-16
FIFO_DO_ADAPTIVE parameter
COMPAQ Tru64 (for Oracle) 3-16
filename
data tablespace 5-13
database system tablespace 5-15
index tablespace 5-14
redo logs 5-14
files
database file location 8-7
French J-12, J-18, J-22
Full Installation. CONTROL-M/EM 8-5
hardware requirements
CTM on windows 4-2
Oracle on Unix 3-8
Sybase on Unix 2-9
help
Win 2000 extra keyboard help option
15-13
hostnames
Oracle database 5-12
Orbix (on Windows) 8-9
remote Sybase 9-21
Sybase server 7-12
HostOrbix parameter
silent EM client installation 8-12
HP-UX
boot procedure 9-13
kernel parameters 2-13, 3-11
G
GAS. see Global Alerts Server
gateways
registering 15-10
GCS. see Global Condition server
German J-12, J-18, J-22
Global Alert server
I
IBM. see AIX
importing
application forms 13-9
Index Component
Oracle parameters (Windows) 6-7
index tablespace, size and filename 5-11
INETD parameter. CTM/Agent for Unix
12-16
Input Mailbox Key parameter 9-17
inst_oracle script 5-7
install/custom script
INSTALL/LOAD script 7-5
installation
CD selection 1-8
database size D-1
diskspace requirements 2-11, 3-10
preparing on windows 4-1
required resources (people) 1-7
silent (Server on Windows) 11-1
installation formats
multiple CONTROL-M/EM servers B-4
Installation on Existing Server. Oracle 6-2
installation types
installation with Sybase (Unix)
shell scripts 7-6
using Configure for Orbix Server 7-6
Installation_Parameters.txt file 7-7, 8-3
INSTALLDIR parameter
CTM/Agent silent installation 14-6
Installed Products fields
CONTROL-M definition 15-12
installing
changing 17-17
CONTROL-M/Agent on Unix 12-1
CONTROL-M/Agent on Windows 13-1
CONTROL-M/EM on Unix 7-1

CONTROL-M/Server on Unix 9-1
CONTROL-M/Server on Windows 10-1
modifying 17-17
Oracle DB on Unix 5-1
Oracle DB on Windows 6-1
removing 17-17
uninstalling 17-17
instance name
Oracle on Unix 5-12
Interprocess communication port number
9-17
interval
polling agent status 9-15
Inventory pointer file. Oracle 5-6
IP
dual addresses 9-16
IPC_PORT_NUMBER parameter.
IRIX. CTM/Agent support for... 12-2
J
Japanese J-2
job editing form
job output
default printer 14-7
job processing definition
size in bytes D-3
JOBNAME statistics mode
jobs
statistics mode 9-17
status changes 9-17
Index
K
kernel parameters
Compaq Tru64 (with Oracle) 3-16
Compaq Tru64 (with Sybase) 2-18
HP-UX (for Oracle) 2-13, 3-11
Solaris (with Oracle) 3-14
Solaris (with Sybase) 2-16
ksi_alloc_max parameter
HP-UX (for Oracle) 3-12
L
language setting
languages
Japanese J-2
support J-1
Western European J-12, J-18, J-22
windows setting 4-5
Linux
xinetd setting 12-19
LISTENER port number 5-16
Load balancing
dual IP addresses 9-16
LOAD script (CONTROL-M/EM) 7-5
Local IP Host Interface Name
LOCAL_IP_HOST_INTERFACE_NAME
LOCALE parameter. CTM/Agent for Unix
12-17
location
database files (Windows) 8-7
Installation_Parameters.txt file 8-3
Oracle data file (Windows) 6-7

Oracle index component (Windows) 6-7
Oracle system component (Windows)
6-7
redo log files (Windows) 6-8
rollback component (Windows) 6-8
temporary component (Windows) 6-8
location and size 6-8
Locator. Orbix service 8-8
locks. Sybase configuration 2-4
Log Database Size 9-18
Log Device Logical Name
Log device name. Sybase 9-22
Log Device Physical Full Path File Name
Log Device Size
Log device type
CONTROL-M/EM on Unix 7-11
log files
CTM/Server silent installation 11-3
Oracle database 3-2
redo logs (Oracle) 5-14
silent client installation 8-12
Log On As parameter
CTM/Agent service 13-8
Log Physical Device/Path Name 7-11, 9-19
Log Size 8-7
LOG_DEVICE_LOGICAL_ NAME
parameter. CTM/Server for Windows 11-6
LOG_DEVICE_SIZE parameter.
LOG_PHYSICAL_DEVICE_FULLPATH_
FILE_NAME parameter
10
LOG_PHYSICAL_DEVICE_FULLPATH_
FILE_NAME parameter. CTM/Server for
Windows 11-6
Logon As User
Logon Domain
LOGON_ACCOUNT_TYPE parameter.
LOGONACCOUNTTYPE parameter
M
Machine name field
CTM/EM Component window 15-7
Machine Type field
maintaining
CONTROL-M/Agent 17-17
previous installation 17-17
Manual startup type
Master Device Type
CONTROL-M/EM 7-11
CTM/Server 9-20
Master Physical Device/Path Name
CONTROL-M/EM 7-11
CTM/Server 9-20
MAX_JOB_STATE_CHANGES
MAX_PER_PROC_STACK_SIZE
max_thread_proc parameter
HP-UX (for Oracle) 2-13, 3-12
maxdsiz parameter
maxdsiz_64bit parameter
maxfree parameter
AIX tuning H-2

Maximum job state changes
Maximum number of requests I/O. AIO
2-15
Maximum number of servers. AIO 2-15
Maximum Retries parameter
CTM/Server for Windows (Silent) 11-5
Maximum Server Processes
maxperm parameter
AIX tuning H-2
maxssiz parameter
maxssiz_64bit parameter
maxswapchunks parameter
maxuprc parameter
media
MEMNAME statistics mode
memory
CONTROL-M/EM database D-1, D-6
for CTM on windows 4-4
how to check 2-10
MSSQL management 16-6
Oracle requirements 3-9
Sybase on Unix 2-10
messages
see also prompts
CONTROL-M/EM installation 7-8
Index
11

Microsoft Windows
cluster configuration 10-5
CTM diskspace requirements 4-5
database requirements 4-6
environment path 16-6
extra keyboard help 15-13
installation preparation 4-1
installing CONTROL-M/Agent 13-1
installing CONTROL-M/EM 8-1
installing CONTROL-M/Server 10-1
installing Oracle 6-1
language setting 4-5
service startup 11-6
software requirements 4-4
minfree parameter
AIX tuning H-2
Minimum number of servers. AIO 2-15
Minimum Server Processes
minperm parameter
AIX tuning H-2
mirroring 9-12
msgmap parameter
msgmni parameter
msgseg parameter
msgtql parameter
msiexec command
CTM/Server for Windows (Silent) 11-2
MSSQL
files locations 8-7
memory management 16-6
requirements 4-6
server name 8-6, 10-8
MSSQL_UPGRADE parameter.
msvcp60.dll in a cluster environment 4-4
msvcrt.dll in a cluster environment 4-4
N
names
see also directories
see also hostnames
see also path
see also usernames
CONTROL-M/EM database 8-7
database server 8-6
ncallout parameter
NCR
ncsize parameter
Network File Server. see NFS
Network to Use. CONTROL-M/Server 10-5
NEW_WIRE_METHOD parameter
nfile parameter
nflocks parameter
NFS
mounting the CTM/Agent CD 12-9
ninode parameter
12
NIS
configuring 12-4
CTM/Agent configuration
CONTROL-M/Agent for Unix
configuration 12-17
nkthread parameter
nodes
port number for Orbix 8-8
nproc parameter
nsswitch.nis file 12-5
NuTCRACKER Service 16-10
O
ODBC version 4-4
operating systems
checking 2-6, 3-5
Operational Parameters
CONTROL-M/Server (Unix) 9-17
ora_defs_controlm directory 5-5
ora_defs_ctmem directory 5-5
Oracle
AIX tuning H-1
checking 15-2
checking for active processes 7-5
database size 5-11
date setting 9-3
diskspace requirements 3-10
existing database 3-3
installation directories (Windows) 6-3
installation parameters (Unix) 5-11
installation parameters (Windows) 6-5
installation procedure (Unix) 5-7
installation procedure (Windows) 6-3
installation types 6-1
inventory pointer file 5-6

log files 3-2
postinstallation script 5-10
preinstallation script 5-5
preparation 3-1
services (troubleshooting) 16-10
supported configurations 1-5
supported versions (Windows) 4-6
Tablespace 3-4
troubleshooting 16-12, 16-15
Western European languages
configuration J-27, J-31, J-36, J-39,
J-42
Oracle Client installation (Windows) 6-2
Oracle home directory
Oracle installation Type
Microsoft Windows 6-5
Oracle LISTENER port number 5-16
Oracle Server host name
Oracle Server TCP/IP Port Number 6-6
Oracle SYSTEM password 5-15
OracleEM920EM6131ClientCache service
16-11
OracleEM920EM6131HTTPServer service
16-11
OracleEM920EM6131PagingServer service
16-11
OracleEM920EM6131SNMPPeerEncapsula
tor service 16-11
OracleEM920EM6131SNMPPeerMasterAg
ent service 16-11
OracleEM920EM613Agent service 16-11
OracleEM920EM613ClientCache service
16-11
OracleEM920EM613DataGatherer service
16-11
Index
13
OracleServiceEM613 service 16-10

OracleUpgradeParams.txt file 6-5
oraInst.loc file 5-6
orapostinst.sh script 5-10, F-11
orapreinst.sh script 5-5
Orbix E2A
diskspace 4-5
information for silent installation 8-10
installation 7-8
Server Parameters 8-8
services 16-10
orbix_prep_file 16-3
OSFCMPLRS subset
Digital Unix C-8
OSFLIBA subset
Digital Unix C-8
OSFPGMR subset
Digital Unix C-8
Output Mailbox Key parameter 9-17
owner
CONTROL-M database 2-5
P
parameters
see also configuration
clusters (CTM/Server - silent install)
11-7
CONTROL/EM installation (Unix) 7-8
CONTROL-M/Agent for Windows 13-5
CTM/Agent for Unix (Silent) 12-16
CTM/Server for Windows (silent) 11-4
Oracle installation (Unix) 5-11
Oracle installation (Windows) 6-5
passwords
CONTROL-M/EM database owner 8-8
database owner 6-6

DB server administrator 8-7
DBO 9-18
DBO (CONTROL-M/Server for
Windows) 10-8
Oracle server (Windows) 6-7
Oracle SYSTEM account 5-15
Oracle user 5-12
Sybase administrator 7-10
path
see also directories
Sybase data files 9-19
PER_PROC_DATA_SIZE
PER_PROC_STACK_SIZE
performance
Oracle database on AIX H-1
polling interval parameter
CONTROL-M/Server (Unix) 9-15
port numbers
Agent-to-Server 9-16
backup socket 9-19
checking 16-13
CONTROL-M/EM TCP/IP 9-17
CTM/Agent for Unix 12-16, 12-20
CTM/Agent for Windows 13-6, 14-6
CTM/EM to CTM/Server port 15-4
inter process communication 9-17
multiple CTM agents 13-2
Oracle LISTENER 5-16
Orbix (Unix) 7-8
Orbix (Windows) 8-8
query socket 9-19
recording port usage 9-11
Server-to-Agent 9-15
Sybase query socket 7-10
port numbers Oracle server 6-6
PortOrbixLocator parameter
14

post-installation
configuration 15-1
Oracle script 5-10
preinstallation
Oracle script 5-5
preparing
CTM on Windows 4-1
CTM with Oracle on Unix 3-1
CTM with Sybase on Unix 2-1
prevpath.txt file 16-6
Primary CONTROL-M/ Server Host
privileges
CONTROL-M/Server administrator
10-3
product support iii
Program Folder. CONTROL-M/EM 8-5
prompts
see also messages
Protocol Version parameter 9-15
protocol version. after agent upgrade 12-13,
13-10, 14-5
prtconf command 2-10
Q
Query Socket Port Number
CONTROL-M/EM 7-10, 7-12
Query Socket Port number
R
RAM. see memory
raw partitions
minimum size (Sybase) 2-3

Oracle databases 3-2
Sybase usage 2-2
RBS Tablespace
Oracle DB size 5-11
recording port usage 9-11
RedHat Linux
Redo Log files
Oracle on Unix 5-11
regional settings. language 4-5
remote CD mount
Remote Sybase host name 9-21
removing
CONTROL-M products 17-17
Oracle Server files 5-10, F-11
Reporting facility
requirements
CONTROL-M/Agent for Unix 12-2
CTM on windows 4-2
databases on windows 4-6
diskspace 2-11, 3-10
diskspace on windows 4-5
memory 2-10, 3-9
RES_DISK_NAME parameter. CTM/Server
for Windows 11-8
Resource Disk Name. CONTROL-M/Server
10-5
resources
see also requirements
for installation 1-7
retries
Agent communication 9-15
Retry Interval parameter
return codes
Index
15
RHEL Linux
rm_ctmem_dirs.sh command 16-4
roaming profiles
Rollback Component
Oracle parameters 6-8
rollback segments 5-15
S
SA Password
SA. see administrators
SCO
Search Path. NIS on Solaris 12-5
security
see also authorization
installer privileges 4-7
Select a group parameter
Select Components Window 8-6
Select the Disk resource parameter
Select the Network resource parameter
semmap parameter
semmni parameter
Solaris with Oracle 3-15
semmns parameter
semmnu parameter
semmsl parameter
semopm parameter

semvmx parameter
Solaris with Sybase 2-17
Server Communication Parameters 9-16
Server Components setup type 8-6
SERVER_SERVICE_
INTERACTIVE_DESKTOP
SERVER_SERVICE_ STARTUP_TYPE
SERVER_TO_AGENT_PORT_NUMBER
servers
CONTROL-M/EM B-4
database B-5
Server-to-Agent port number
SERVICE_AUTO_START
SERVICE_DEMAND_START
SERVICE_INTERACTIVE_PROCESS
services
CONTROL-M/EM 16-10
Orbix E2A Server 16-10
startup options 16-10
Services map
NIS 12-4
setenv command 5-7
setup types
16

setup.iss file 8-11
setup_XP.iss file 8-11
SHM_MAX parameter
SHM_MIN parameter
SHM_MNI parameter
SHM_SEG parameter
shmmax parameter
Compaq Tru64 with Sybase 2-18
shmmin parameter
shmmni parameter
shmseg parameter
Show extra keyboard help. Windows 2000
15-13
silent installation
CONTROL-M/EM client 8-10
silent.bat file
size
CONTROL-M/EM database (Windows)
8-7
data tablespace 5-13
Database system tablespace 5-15

index tablespace 5-13
Oracle database components 5-11
Oracle system component (Windows)
6-7
redo log files (Windows) 6-8
redo logs 5-14
rollback component (Windows) 6-8
temporary component (Windows) 6-8
SLES Linux
CTM/Agent support 12-2
software requirements
CTM on Windows 4-4
Solaris
configuring NIS 12-4
kernel parameters (for Oracle) 3-14
kernel parameters (for Sybase) 2-16
Spanish J-12, J-18, J-22
SQL Server Configuration
SQL Server Device Parameters 10-9
ssm-threshold parameter
Compaq Tru64 with Sybase 2-18
Start Day of the Week
start_ctm command 15-3
starting
CONTROL-M/EM 15-2
startup options
services 16-10
Startup Type
CTM/Agent service 13-7
State of fast path. AIO 2-15
statistics mode
Index
17

STATISTICS_MODE parameter.
status
CONTROL-M/Agent polling 9-15
maximum changes 9-17
Sun. see Solaris
support, customer iii
SuSE Linux
CTM/Agent support 12-2
Svr610_si_log.txt file 11-3
Sybase
administrator password 7-10
checking 15-2
checking for active processes 7-5
configuration 2-2
configuration with
database clients 8-2
database device parameters 7-11
database server name 8-6
devices 2-19
diskspace requirements 2-11
existing SQL server 2-4
old configuration files 7-9
parameters (with EM on Unix) 7-10
preparation 2-1
raw partitions 2-2
server properties 8-8
Sybase files location 8-7
Sybase Interface Directory 7-12
location 7-12
Sybase Server Host Name 7-12
Sybase Server Name 7-12
Sybsystemprocs Device Type
CONTROL-M/EM 7-11

syntax
CTM/Agent silent.bat (Windows) 14-3
System account
CONTROL-M/Server for Windows user
10-10
Oracle password 5-15
system administrator
installation tasks 1-7
System Component
system requirements
see also requirements
check_req script 2-6, 3-5
Solaris C-6
System Tablespace
Oracle DB size 5-11
szDir parameter
T
tablespaces
index 5-14
installation parameters 5-13
listing 3-4
Oracle database 3-4
Oracle DB size 5-11
owner 3-4
size of Oracle on Windows 6-6
TCP/IP port number
CONTROL-M/EM 9-17
TCP/IP Timeout
technical support iii
TEMP environment variable (Windows) 4-5
Tempdb Database Size 9-18
Tempdb Device Type 9-20
Tempdb Physical Device/Path Name 9-20
temporary component
18

Temporary Tablespace
Oracle DB size 5-11
This Account
CONTROL-M/Server for Windows
service 10-10
THISACCOUNTPASSWORD parameter.
THISACCOUNTUSER parameter.
Time Between Retries parameter
timeout
Timeout parameter
communication with Agent 9-15
tmp directory
TRACKER_EVENT_PORT. CTM/Agent
for Windows 14-8
Tracking Timeout parameter
environment path 16-6
MSSQL memory management 16-6
Type field
typical installation
U
uninstallation (Windows)
description 17-2, 17-6
uninstalling
remove 17-17
Unix

installing CONTROL-M/Agent 12-1
installing CONTROL-M/EM 7-1
installing CONTROL-M/Server 9-1
installing Oracle 5-1
UnixWare SCO
upgrading
CONTROL-M/Agent on Unix 12-1
upgrade parameter path (Oracle) 6-5
Uppercase Only field
user connections. Sybase configuration 2-4
user password
usernames
Oracle database on Windows 6-6
Oracle server (Windows) 6-7
V
version
agent communication protocol 12-13,
13-10, 14-5
Version field
versions
Oracle database 1-5
VIP parameter. CTM/Server for Windows
11-7
Virtual IP Address. CONTROL-M/Server
10-5
Virtual Server Name. CONTROL-M/Server
10-5
vmstat command 2-10
vmtune utility
AIX tuning H-2
Index
19
vps_ceiling parameter
W
Western European languages
configuration J-3, J-12, J-18, J-22
configuring Oracle J-27, J-31, J-36,
J-39, J-42
special characters J-6
Windows. see Microsoft Windows
windows.xml file 13-9
With customization option
Without customization option
Workstation gateway
description B-3
X
xinetd
with CTM/Agent 12-19
XINETD parameter. CTM/Agent for Unix
12-16
Y
ypwhich command 12-11
20
END USER LICENSE AGREEMENT

NOTICE
BY OPENING THE PACKAGE, INSTALLING, PRESSING "AGREE" OR "YES" OR USING THE PRODUCT, THE ENTITY OR
INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT
AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE PRODUCT TO
BMC OR YOUR BMC RESELLER, AND IF YOU ACQUIRED THE LICENSE WITHIN 30 DAYS OF THE DATE OF YOUR ORDER
CONTACT BMC OR YOUR BMC RESELLER FOR A REFUND OF LICENSE FEES PAID. IF YOU REJECT THIS AGREEMENT,
YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT.
This Agreement ("Agreement") is between the entity or individual entering into this Agreement ("You") and BMC Software Distribution,
Inc., a Delaware corporation located at 2101 CityWest Blvd., Houston, Texas, 77042, USA or its affiliated local licensing entity ("BMC").
"You" includes you and your Affiliates. "Affiliate" is defined as an entity which controls, is controlled by or shares common control with
a party. THIS AGREEMENT WILL APPLY TO THE PRODUCT, UNLESS (1) YOU AGREED TO A WEB BASED LICENSE
AGREEMENT WITH BMC WHEN ORDERING THE PRODUCT, IN WHICH CASE THAT WEB BASED LICENSE AGREEMENT
GOVERNS THE USE OF THE PRODUCT, OR (2) IF YOU DID NOT AGREE TO A WEB BASED LICENSE AGREEMENT WITH BMC
WHEN ORDERING THE PRODUCT AND YOU HAVE A WRITTEN LICENSE AGREEMENT WITH BMC, THEN THAT WRITTEN
AGREEMENT GOVERNS THE USE OF THE PRODUCT. THE ELECTRONIC AGREEMENT PROVIDED WITH THE PRODUCT AS
PART OF THE INSTALLATION OF THE PRODUCT WILL NOT APPLY. In addition to the restrictions imposed under this Agreement,
any other usage restrictions contained in the Product installation instructions or release notes shall apply to Your use of the Product.
PRODUCT AND CAPACITY. "Software" means the object code version of the computer programs provided, via delivery or electronic
transmission, to You. Software includes computer files, enhancements, maintenance modifications, upgrades, updates, bug fixes, and
error corrections.
"Documentation" means all written or graphical material provided by BMC in any medium, including any technical specifications,
relating to the functionality or operation of the Software.
"Product" means the Software and Documentation.
"License Capacity" means the licensed capacity for the Software with the pricing and other license defining terms, including capacity
restrictions, such as tier limit, total allowed users, gigabyte limit, quantity of Software, and/or other capacity limitations regarding the
Software. For licenses based on the power of a computer, You agree to use BMCs current computer classification scheme, which is
available at http://www.bmc.com or can be provided to You upon request.
ACCEPTANCE. The Product is deemed accepted by You, on the date that You received the Product from BMC.
LICENSE. Subject to the terms of this Agreement, as well as Your payment of applicable fees, BMC grants You a non-exclusive,
non-transferable, perpetual (unless a term license is provided on an order) license for each copy of the Software, up to the License
Capacity, to do the following:
(a) install the Software on Your owned or leased hardware located at a facility owned or controlled by You in the country where You
acquired the license;
(b) operate the Software solely for processing Your own data in Your business operations; and
(c) make one copy of the Software for backup and archival purposes only (collectively a "License").
If the Software is designed by BMC to permit you to modify such Software, then you agree to only use such modifications or new
software programs for Your internal purposes or otherwise consistent with the License. BMC grants You a license to use the
Documentation solely for Your internal use in Your operations.
LICENSE UPGRADES. You may expand the scope of the License Capacity only pursuant to a separate agreement with BMC for such
expanded usage and Your payment of applicable fees. There is no additional warranty period or free support period for license
upgrades.
RESTRICTIONS: You agree to NOT:
(a) disassemble, reverse engineer, decompile or otherwise attempt to derive any Software from executable code;
(b) distribute or provide the Software to any third party (including without limitation, use in a service bureau, outsourcing environment,
or processing the data of third parties, or for rental, lease, or sublicense); or
(c) provide a third party with the results of any functional evaluation or benchmarking or performance tests, without BMCs prior written
approval, unless prohibited by local law.
TRIAL LICENSE. If, as part of the ordering process, the Product is provided on a trial basis, then these terms apply: (i) this license
consists solely of a non-exclusive, non-transferable evaluation license to operate the Software for the period of time specified from BMC
or, if not specified, a 30 day time period ("Trial Period") only for evaluating whether You desire to acquire a capacity-based license to
the Product for a fee; and (ii) Your use of the Product is on an AS IS basis without any warranty, and BMC, ITS AFFILIATES AND
RESELLERS, AND LICENSORS DISCLAIM ANY AND ALL WARRANTIES (INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT) AND HAVE NO
LIABILITY WHATSOEVER RESULTING FROM THE USE OF THIS PRODUCT UNDER THIS TRIAL LICENSE ("Trial License").
BMC may terminate for its convenience a Trial License upon notice to You. When the Trial Period ends, Your right to use this Product
automatically expires.
If You want to continue Your use of the Product beyond the Trial Period, contact BMC to acquire a
capacity-based license to the Product for a fee.
TERMINATION. This Agreement shall immediately terminate if You breach any of its terms. Upon termination, for any reason, You must
uninstall the Software, and either certify the destruction of the Product or return it to BMC.
OWNERSHIP OF THE PRODUCT. BMC or its Affiliates or licensors retain all right, title and interest to and in the BMC Product and all
intellectual property, informational, industrial property and proprietary rights therein. BMC neither grants nor otherwise transfers any
rights of ownership in the BMC Product to You. BMC Products are protected by applicable copyright, trade secret, and industrial and
intellectual property laws. BMC reserves any rights not expressly granted to You herein.
CONFIDENTIAL AND PROPRIETARY INFORMATION. The BMC Products are and contain valuable confidential information of BMC
("Confidential Information"). Confidential Information means non-public technical and non-technical information relating to the BMC
Products and Support, including, without limitation, trade secret and proprietary information, and the structure and organization of the
Software. You may not disclose the Confidential Information to third parties. You agree to use all reasonable efforts to prevent the
unauthorized use, copying, publication or dissemination of the Product.
WARRANTY. Except for a Trial License, BMC warrants that the Software will perform in substantial accordance with the Documentation
for a period of one year from the date of the order. This warranty shall not apply to any problems caused by software or hardware not
supplied by BMC or to any misuse of the Software.
EXCLUSIVE REMEDY. BMCs entire liability, and Your exclusive remedy, for any defect in the Software during the warranty period or
breach of the warranty above shall be limited to the following: BMC shall use reasonable efforts to remedy defects covered by the
warranty or replace the defective Software within a reasonable period of time, or if BMC cannot remedy or replace such defective copy
of the Software, then BMC shall refund the amount paid by You for the License for that Software. BMCs obligations in this section are
conditioned upon Your providing BMC prompt access to the affected Software and full cooperation in resolving the claim.
DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES ABOVE, THE PRODUCT IS PROVIDED "AS IS." BMC, ITS
AFFILIATES AND LICENSORS SPECIFICALLY DISCLAIM ALL OTHER WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. BMC
DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT
ALL DEFECTS CAN BE CORRECTED.
DISCLAIMER OF DAMAGES. IN NO EVENT IS BMC, ITS AFFILIATES OR LICENSORS LIABLE FOR ANY SPECIAL, INDIRECT,
INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT, SUPPORT,
AND/OR THE PRODUCT (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER USAGE TIME, AND DAMAGE
OR LOSS OF USE OF DATA), EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF ANY
NEGLIGENCE OF BMC OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR CONTRACT
LAW.
LIMITS ON LIABILITY. BMCS AGGREGATE LIABILITY FOR DAMAGES IS LIMITED TO THE AMOUNT PAID BY YOU FOR THE
LICENSE TO THE PRODUCT.
SUPPORT. If Your order includes support for the Software, then BMC agrees to provide support (24 hours a day/7 days a week)
("Support"). You will be automatically re-enrolled in Support on an annual basis unless BMC receives notice of termination from You
as provided below. There is a free support period during the one year warranty period.
(a) Support Terms. BMC agrees to make commercially reasonable efforts to provide the following Support: (i) For malfunctions of
supported versions of the Software, BMC provides bug fixes, patches or workarounds in order to cause that copy of the Software to
operate in substantial conformity with its then-current operating specifications; and (ii) BMC provides new releases or versions, so long
as such new releases or versions are furnished by BMC to all other enrolled Support customers without additional charge. BMC may
refuse to provide Support for any versions or releases of the Software other than the most recent version or release of such Software
made available by BMC. Either party may terminate Your enrollment in Support upon providing notice to the other at least 30 days prior
to the next applicable Support anniversary date. If You re-enroll in Support, BMC may charge You a reinstatement fee of 1.5 times what
You would have paid if You were enrolled in Support during that time period.
(b) Fees. The annual fee for Support is 20% of the Softwares list price less the applicable discount or a flat capacity based annual fee.
BMC may change its prices for the Software and/or Support upon at least 30 days notice prior to Your support anniversary date.
VERIFICATION. If requested by BMC, You agree to deliver to BMC periodic written reports, whether generated manually or
electronically, detailing Your use of the Software in accordance with this Agreement, including, without limitation, the License Capacity.
BMC may, at its expense, audit Your use of the Software to confirm Your compliance with the Agreement. If an audit reveals that You
have underpaid fees, You agree to pay such underpaid fees. If the underpaid fees exceed 5% of the fees paid, then You agree to also
pay BMCs reasonable costs of conducting the audit.
EXPORT CONTROLS. You agree not to import, export, re-export, or transfer, directly or indirectly, any part of the Product or any
underlying information or technology except in full compliance with all United States, foreign and other applicable laws and regulations.
GOVERNING LAW. This Agreement is governed by the substantive laws in force, without regard to conflict of laws principles: (a) in
the State of New York, if you acquired the License in the United States, Puerto Rico, or any country in Central or South America; (b) in
the Province of Ontario, if you acquired the License in Canada (subsections (a) and (b) collectively referred to as the "Americas
Region"); (c) in Singapore, if you acquired the License in Japan, South Korea, Peoples Republic of China, Special Administrative
Region of Hong Kong, Republic of China, Philippines, Indonesia, Malaysia, Singapore, India, Australia, New Zealand, or Thailand
(collectively, "Asia Pacific Region"); or (d) in the Netherlands, if you acquired the License in any other country not described above.
The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed in its entirety.
ARBITRATION. ANY DISPUTE BETWEEN YOU AND BMC ARISING OUT OF THIS AGREEMENT OR THE BREACH OR
ALLEGED BREACH, SHALL BE DETERMINED BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS
INITIATED IN THE AMERICAS REGION, THE ARBITRATION SHALL BE HELD IN NEW YORK, U.S.A., UNDER THE CURRENT
COMMERCIAL OR INTERNATIONAL, AS APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE
DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN SINGAPORE,
SINGAPORE UNDER THE CURRENT UNCITRAL ARBITRATION RULES. IF THE DISPUTE IS INITIATED IN A COUNTRY
OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION SHALL BE HELD IN AMSTERDAM,
NETHERLANDS UNDER THE CURRENT UNCITRAL ARBITRATION RULES. THE COSTS OF THE ARBITRATION SHALL BE
BORNE EQUALLY PENDING THE ARBITRATORS AWARD. THE AWARD RENDERED SHALL BE FINAL AND BINDING UPON
THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY COURT, AND MAY BE ENFORCED IN ANY COURT OF
COMPETENT JURISDICTION. NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY FROM
SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER THE PARTIES AND THE SUBJECT MATTER
OF THE DISPUTE AS NECESSARY TO PROTECT EITHER PARTYS CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY
OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS SHALL BE CONDUCTED IN CONFIDENCE, AND THE
PARTY PREVAILING IN ARBITRATION SHALL BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS FEES AND
NECESSARY COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY.
U.S. GOVERNMENT RESTRICTED RIGHTS. The Software under this Agreement is "commercial computer software" as that term is
described in 48 C.F.R. 252.227-7014(a)(1). If acquired by or on behalf of a civilian agency, the U.S. Government acquires this
commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as
specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the Federal Acquisition Regulations ("FAR") and its
successors. If acquired by or on behalf of any agency within the Department of Defense ("DOD"), the U.S. Government acquires this
commercial computer software and/or commercial computer software documentation subject to the terms of this Agreement as
specified in 48 C.F.R. 227.7202 of the DOD FAR Supplement and its successors.
MISCELLANEOUS TERMS. You agree to pay BMC all amounts owed no later than 30 days from the date of the applicable invoice,
unless otherwise provided on the order for the License to the Products. You will pay, or reimburse BMC, for taxes of any kind, including
sales, use, duty, tariffs, customs, withholding, property, value-added (VAT), and other similar federal, state or local taxes (other than
taxes based on BMCs net income) imposed in connection with the Product and/or the Support. This Agreement constitutes the entire
agreement between You and BMC and supersedes any prior or contemporaneous negotiations or agreements, whether oral, written or
displayed electronically, concerning the Product and related subject matter. No modification or waiver of any provision hereof will be
effective unless made in a writing signed by both BMC and You. You may not assign or transfer this Agreement or a License to a third
party without BMCs prior written consent. Should any provision of this Agreement be invalid or unenforceable, the remainder of the
provisions will remain in effect. The parties have agreed that this Agreement and the documents related thereto be drawn up in the
English language. Les parties exigent que la prsente convention ainsi que les documents qui sy rattachent soient rdigs en anglais.
SW EULA Int 030102
Notes
*43988*
*43988*
*43988*
*43988*
*43988*

Control-M Installation Guide 6.1.03 PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Control-M Installation Guide 6.1.03 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

CONTROL-M

March 31, 2004

Restricted Rights Legend

Contacting BMC Software

United States and Canada

Outside United States and Canada

(01) 713 918 8800

(01) 713 918 8000

BMC Software, Inc.

713 918 8800 or

713 918 8000

Support Web Site

Support by Telephone or E-mail

Before Contacting BMC Software

operating system and environment information

BMC Software, Inc., Confidential and Proprietary Information

sequence of events leading to the problem

commands and options that you used

product error messages

BMC Software, Inc., Confidential and Proprietary Information

CONTROL-M Installation Guide

Choose Which CONTROL-M Products to Install . . . . . . . . . . . . . . . 1-2

Pre-Installation Steps for Unix with a Sybase Database

Prepare for Database Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Pre-Installation Steps for Unix with an Oracle Database

Choose a Files or Raw Partitions for the Oracle Database . . . . . . . .3-2

Pre-Installation Steps on Microsoft Windows

Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

Installing an Oracle Database on Unix

Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

Installing an Oracle Database on Microsoft Windows

Oracle Database Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

Installing CONTROL-M/EM on Unix

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

Installing CONTROL-M/EM for Microsoft Windows

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

CONTROL-M Installation Guide

Silent Installation of a CONTROL-M/EM Basic Client . . . . . . . 8-10

Installing CONTROL-M/Server for Unix

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Installing CONTROL-M/Server for Microsoft Windows

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Silent Installation of CONTROL-M/Server for Microsoft Windows

Silent Installation of CONTROL-M/Server for Microsoft Windows

Installing or Upgrading CONTROL-M/Agent for Unix

Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Installing or Upgrading CONTROL-M/Agent for Microsoft Windows

Installing CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

BMC Software, Inc., Confidential and Proprietary Information

Silent Installation of CONTROL-M/Agent for Microsoft Windows

Silent Installation of CONTROL-M/Agent for Microsoft Windows

On Unix Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-2

CONTROL-M/EM Installation on Unix . . . . . . . . . . . . . . . . . . . . .16-2

Uninstalling CONTROL-M Components

Uninstalling CONTROL-M/EM On Unix Computers . . . . . . .17-2

Mounting CDs on Unix Computers

Mounting Installation CDs on an AIX Computer . . . . . . . . . . . . . . A-2

CONTROL-M Installation Guide

Mounting Installation CDs on a COMPAQ Tru64 Computer . . . . . A-6

Unix Operating System Requirements

CONTROL-M/EM Database Size

CONTROL-M/Server Database Size