Control M

CONTROL-M/Server and CONTROL-M/Agent
Installation Guide
Supporting
CONTROL-M/Server for UNIX and Windows version 6.3.01 CONTROL-M/Agent for UNIX and Windows version 6.3.01
December 2006
www.bmc.com
Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
Copyright November 21, 2006 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. IBM is a registered trademark of International Business Machines Corporation. DB2 is a registered trademark of International Business Machines Corporation. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can

read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to support@bmc.com. Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
sequence of events leading to the issue commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
CONTROL-M/Server and CONTROL-M/Agent Installation Guide
Contents
Chapter 1 Introduction 11 Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Chapter 2 Planning for CONTROL-M/Server 15 17 17 19 20 21 23 25 25 25 26 31 32 32 33 34 39 39 40 41 42 44 45 46 46 47 47 48 48 49
East Asian (CJK) language considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating system levels and patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing a CONTROL-M/Server account on UNIX . . . . . . . . . . . . . . . . . . . . . . . Windows requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required privileges and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Installing CONTROL-M/Server
Installing CONTROL-M/Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the automatic startup procedure for CONTROL-M/Server . . . . . . . . Installing CONTROL-M/Server on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . Considerations for a Microsoft Windows cluster environment . . . . . . . . . . . . . . . Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4 Installing CONTROL-M/Agent on UNIX
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CD-ROM drive considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactive installation or upgrade of CONTROL-M/Agent on UNIX . . . . . . . . . . . . Silent installation or upgrade of CONTROL-M/Agent on UNIX . . . . . . . . . . . . . . . . Modifying the automatic startup procedure for CONTROL-M/Agent . . . . . . . . . . . Information for upgrades from version 6.2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changes to system files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade with CONTROL-M Option for Oracle Applications installed . . . . . . . . Upgrade with CONTROL-M Option for PeopleSoft installed . . . . . . . . . . . . . . . . Post installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Agent from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5 Installing CONTROL-M/Agent on Microsoft Windows
Considerations for a Microsoft Windows cluster environment . . . . . . . . . . . . . . . . . . 50

Contents 5
Working with multiple agents on the same computer . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Considerations for control modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Interactive installation or upgrade of CONTROL-M/Agent on Windows . . . . . . . . . 52 Importing WIN panel functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Setting the protocol version for the upgraded CONTROL-M/Agent . . . . . . . . . . . . . 55 Silent installation of CONTROL-M/Agent for Microsoft Windows . . . . . . . . . . . . . . 55 Post installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Chapter 6 Post installation procedures 59
On UNIX and Windows computers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Setting a CONTROL-M/Agent permanent connection to CONTROL-M/Server. . 59 On UNIX computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Using NFS with CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Setting the protocol version for the upgraded CONTROL-M/Agent . . . . . . . . . . 60 Setting CONTROL-M/Agent file permissions for NFS . . . . . . . . . . . . . . . . . . . . . . 60 On Windows computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Updating CONTROL-M/Agent system path information on cluster installations. 61 Appendix A Installing Sybase on UNIX 63
HP Itanium requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Installing a dedicated database server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Cleaning up a failed dedicated installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Installing on an existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Verifying existing Sybase components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Performing the existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Cleaning up a failed existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Installing a Sybase client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Cleaning up a failed client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Performing a silent installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Setting Sybase installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Checking the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Using build_db to recover CONTROL-M/Server after a dedicated Sybase server failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Appendix B Installing Oracle on UNIX 77
Preparing for installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Copying the Oracle CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Preparing the installer CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Running the Oracle pre-installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Installing a dedicated database server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Installing on an existing database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Verification of existing Oracle components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Performing the existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Cleaning up a failed existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Installing a CONTROL-M/Server tablespace using an existing Oracle client . . . . . . 84
Performing post-installation cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Oracle installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix C Appendix D Mounting CDs on UNIX computers Checking and modifying UNIX parameters
85 86 88 91 93 97
Checking memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Modifying system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Appendix E CONTROL-M/Server database size 105
Job definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Calculating the size of the active jobs file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Database memory requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Appendix F Uninstalling CONTROL-M/Server and database servers 111 111 112 112 112 113 115
Uninstalling CONTROL-M/Server from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/Server from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling the NutCRACKER service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Sybase database server . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling a CONTROL-M Oracle database server . . . . . . . . . . . . . . . . . . . . . . . . . Index
Contents
Tables
CONTROL-M components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installation checklist for CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Supported and supplied databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Database server configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 UNIX requirements for CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Limits for CONTROL-M/Server accounts on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Windows requirements for CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Installation resource requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 CONTROL-M/Server UNIX database and application installation parameters . . 29 CONTROL-M/Server Windows cluster installation parameters . . . . . . . . . . . . . . . 35 CONTROL-M/Server Windows database and application parameters . . . . . . . . . 36 Minimum system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Kernel parameter requirement for CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . 40 Installation Parameters - CONTROL-M/Agent on UNIX . . . . . . . . . . . . . . . . . . . . . . 43 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 CONTROL-M/Agent Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Silent installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Sybase installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Sybase database server parameters - minimum values . . . . . . . . . . . . . . . . . . . . . . . . . 67 Sybase database UNIX interactive installation parameters . . . . . . . . . . . . . . . . . . . . 71 Sybase database UNIX silent installation parameters . . . . . . . . . . . . . . . . . . . . . . . . 73 Oracle installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Oracle Database UNIX installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Checking available memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Kernel parameters additional values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Kernel parameters values for all platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Kernel parameters HP-UX with Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Kernel parameters HP-UX with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Asynchronous I/O parameters AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Kernel parameters Solaris with Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Kernel parameters Solaris with Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Kernel parameters Linux with Sybase and Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Displaying kernel parameter values Linux with Sybase and Oracle . . . . . . . . . . . 103 Job items and Disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Job definition calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Active jobs file calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Active jobs file parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Tables
10
Chapter
Introduction
This guide contains the information that you need to install the latest version of CONTROL-M/Server. A brief illustration of CONTROL-M/Server and how it fits into the CONTROL-M environment is shown in Figure 1. Figure 1 The CONTROL-M scheduling solution
Chapter 1
Introduction
11
Table 1 lists the full set of components for the CONTROL-M solution (shown in Figure 1) in the order they should be installed. Table 1
Product CONTROL-M/ Enterprise Manager CONTROL-M/Server
CONTROL-M components
Description The central GUI-based control center from which you can manage all scheduling and workflow activities. The engine (on a UNIX or Microsoft Windows computer) used to schedule jobs in a data center. Each CONTROL-M/Server can manage multiple CONTROL-M/Agents on various platforms. Software for job submission and execution. An Agent must exist on each computer that is used to execute CONTROL-M jobs, unless the remote hosts feature for CONTROL-M/Server is used as noted below.
CONTROL-M/Agent
NOTE
As of version 6.3.01 of CONTROL-M, jobs can be submitted to remote hosts without having CONTROL-M/Agents installed on the remote host machines. If you use this feature, you may decide not to install separate CONTROL-M/Agents.

For details about this feature and when to use it, see the CONTROL-M Concepts Guide. For information about configuring remote hosts, see the CONTROL-M/Enterprise Manager Administrator Guide and the CONTROL-M/Server for UNIX and Microsoft Windows Administrator Guide.
This book provides instructions for installing CONTROL-M/Server and CONTROL-M/Agent. A typical CONTROL-M/Server installation includes:

A database server (Oracle, Sybase, or MSSQL). CONTROL-M/Server on UNIX or Windows.
NOTE
In addition to the printed release notes that accompany this product, up-to-date, essential, installation and service information that becomes available after this product is shipped will be placed on the BMC Software Customer Support Web site at: http://www.bmc.com/support/ BMC Software recommends that you access this location before you begin the installation of this product.
12
Installation checklist
Table 2
1
Installation checklist for CONTROL-M/Server

Description Select the database type and configuration: Sybase, Oracle, or MSSQL Dedicated or Existing Ensure that you have all the resources necessary for the installation. Identify the installation CDs. Where to go Database server configurations on page 16.
Check Step
Required privileges and passwords on page 23. Release Notes supplied with this version of CONTROL-M/Server. Operating system levels and patches on page 19.
Perform pre-installation checks. Note: A pre-installation check is provided for UNIX installations.
Install a database server and clients Install CONTROL-M/Server.
List of supported database servers and clients in Table 3 on page 15. Chapter 3, Installing CONTROL-M/Server Chapter 6, Post installation procedures
Perform post installation procedures. Migrate CONTROL-M/Server data from previous version (optional).
CONTROL-M Migration Guide
NOTE
The version of CONTROL-M/Server being installed must be the same or later than the version of CONTROL-M/Agent. For example, CONTROL-M/Server 6.3.01 works with CONTROL-M/Agent 6.3.01 or earlier.
Chapter 1
Introduction
13
14
Chapter
Planning for CONTROL-M/Server

CONTROL-M/Server can be installed on a new database server (dedicated installation) or on a database server that already exists on site (existing installation). A dedicated installation refers to installation of a database server and client supplied by BMC Software. An existing installation refers to installation of a database client supplied by BMC Software and connecting it to a database server owned by the customer.
NOTE
BMC Software recommends using the BMC-supplied database server and clients where possible.
Select your database configuration before installing CONTROL-M/Server. The following database server and client installations are available for both UNIX and Windows. Table 3 Supported and supplied databases
UNIX Database component Sybase server Supported Version 12.5.x Supplied Supported Version 12.5.3.4 N/A for HP Itanium. Version 12.5.3.1 for all other platforms. Version 12.5.2 N/A Windows Supplied N/A
Sybase client Oracle 10 server Oracle 10 client
Version 12.5.2
N/A N/A N/A N/A
Version 10.1.0.x Version 10.1.0.3 N/A Version 10.1.0.x Version 10.1.0.3 N/A N/A Versions 2000 and 2005
MSSQL (English only) N/A
Chapter 2
15
Table 4
Database server configurations
Database type Description Sybase
Sybase can be used with CONTROL-M/Server on UNIX systems only. A CONTROL-M Sybase database server or an existing Sybase database server with 8K paging must be installed before installing CONTROL-M/Server. A Sybase client must be installed separately on each UNIX account that hosts CONTROL-M/Server. Oracle can be used with CONTROL-M/Server on UNIX systems only. A CONTROL-M Oracle database server or an existing Oracle full enterprise edition database server must be installed before installing CONTROL-M/Server. An Oracle client must be installed on each UNIX account that hosts a CONTROL-M/Server that is connected to a database server that resides on a different account or computer.
Oracle
Note:
An Oracle Database Server version 10.1.0.1, 10.1.0.2, or 10.1.0.3 on AIX, Solaris, or HP-UX is not compatible with any Oracle client on Linux. An Oracle Database Server version 10.1.0.1, 10.1.0.2, or 10.1.0.3 on Linux is not compatible with any Oracle client on AIX, Solaris, or HP-UX. The following methods can be used to overcome these incompatibilities:
Upgrade to Oracle Database Server version 10.1.0.4 or 10.1.0.5, 10.2.01. For UNIX and Linux, you can install an Oracle patch described under Workaround to Oracle Compatibility problem for UNIX and Linux in the Release Notes accompanying this version of CONTROL-M/Server. An MSSQL based installation must always be performed using an existing English language MSSQL database server. MSSQL is not provided by BMC Software. In addition to the database server, MSSQL clients must be installed on any computer that hosts a CONTROL-M/Server. The MSSQL Client is not part of the CONTROL-M/Server installation package and must be installed before CONTROL-M/Server is installed. If you install CONTROL-M/Server on a computer with an existing MSSQL server, there is no need to install the MSSQL Client.
MSSQL
16
East Asian (CJK) language considerations
East Asian (CJK) language considerations

Support for East Asian languages (Simplified Chinese, Traditional Chinese, Japanese, and Korean) is provided at the database level. When installing a dedicated (supplied by BMC Software) Oracle or Sybase database server, you must choose the custom option. During the custom installation, you are explicitly asked if CJK character support is required. When creating a CONTROL-M/Server database on an existing Sybase or Oracle database server, CJK s are inherited automatically from the database server. When creating a CONTROL-M/Server database on an existing MSSQL database server with CJK support already present, you are explicitly asked if CJK character support is required for the new CONTROL-M/Server database. For more information regarding CJK support, see the CONTROL-M Language Customization Guide.
UNIX requirements
Software and database compatibility information is listed at: http://www.bmc.com/supportu/PAC_utility/index.cfm. Ensure that hardware, memory, and disk space meet the minimum requirements for CONTROL-M/Server as described in Table 5. Consult the CONTROL-M Language Customization Guide to adjust locale settings to your UNIX platform. Several UNIX system parameters must be modified before installing CONTROL-M/Server. For detailed information, see Modifying system parameters on page 98.
Chapter 2
17
UNIX requirements
Table 5
Resource Hardware
UNIX requirements for CONTROL-M/Server (Part 1 of 2)

System specification AIX Requirement IBM RISC System/6000 Note: For Oracle installations, hardware must be 64-bit. HP-UX HP 9000/700 or HP 9000/800. Note: For Oracle installations, hardware must be 64-bit. Solaris Sun SPARCstation Note: For Oracle installations, hardware must be 64-bit. Linux Intel Pentium 32 bit
Memory
CONTROL-M/Server Recommended: with Sybase 512 MB RAM for the first 10,000 jobs. Add 60 MB for each additional 10,000 jobs processed on a daily basis. Minimum: 256 MB RAM CONTROL-M/Server Recommended: with Oracle 1 GB RAM for the first 10,000 jobs. Add 60 MB for each additional 10,000 jobs processed on a daily basis. Minimum: 512 MB RAM
CONTROL-M/Server CONTROL-M/Server 522 MB for a new installation. files on AIX diskspace CONTROL-M/Server 277 MB for a new installation. BMC Software files on HP-UX recommends that CONTROL-M/Server 239 MB for a new installation. three times the amount of RAM in the files on Solaris system be reserved for swap space.
18
Operating system levels and patches
Table 5
Resource
UNIX requirements for CONTROL-M/Server (Part 2 of 2)

System specification Sybase Server Aix: 750 MB HP-UX: 850 MB Solaris: 700 MB Linux: 650MB Database Small: 310 MB Medium: 500 MB Large: 1900 MB Master, Systemproc, and Tempdb. 500 MB Requirement Oracle 10.1 3 GB for the Oracle Server, and 400 MB in the /tmp directory. Database Small: 1.1 GB Medium: 1.45 GB Large: 2.3 GB
Database diskspace
Operating system levels and patches

Run the check_req.sh script to verify that the operating system version, maintenance level (patches), and UNIX kernel parameters are compatible with CONTROL-M/Server requirements. The following procedure describes how to obtain and run the check_req.sh script.
1 Check the localhost mapping. A Ensure that the host name of the computer on which you are performing the
installation is not mapped to localhost (reserved IP address 127.0.0.1), by running the following command:
grep 127.0.0.1 /etc/hosts
B If the host name of the computer is mapped to localhost, remove it by editing

the /etc/hosts file.
2 Download the pre_req.tar.Z file from the following Web location:

ftp://ftp.bmc.com/pub/control-m/opensystem/PANFT.6.3.01.001
Chapter 2
19
Preparing a CONTROL-M/Server account on UNIX
NOTE
The check_req.sh file is also located in the pre_req directory on the CONTROL-M/Server installation CD. However, due to changes that are applied to the operating systems, this file may not be up to date. BMC Software recommends that you download the latest version of this script from the location shown above.
If you downloaded the pre_req.tar.Z file from the Web, follow the instructions in the accompanying readme file. If you are using the check_req.sh file on the installation CD, continue with the steps below.
3 Log in as a root user. 4 Mount the CONTROL-M/Server installation CD. For details of mount procedures
for your UNIX platform, see Appendix C, Mounting CDs on UNIX computers on page 93.
5 Use the following command to start this script from the CONTROL-M/Server
installation CD: <cdPath>/pre_req/check_req.sh
6 Follow the prompts and fill in information as necessary.

If the operating system and patches meet CONTROL-M/Server requirements, you are advised that the product can be installed. Otherwise a list of missing requirements is displayed.
Preparing a CONTROL-M/Server account on UNIX

The CONTROL-M/Server account should conform to the following criteria: 1. The CONTROL-M/Server account must include a home directory with sufficient disk space for installation of CONTROL-M/Server components as shown in Table 5 on page 18. 2. The HOME environment variable must be set to the HOME directory. 3. The user must be the owner of the HOME directory. 4. The initial program for the user must be defined as either csh or tcsh.
20
Windows requirements
5. On Oracle, the administrator group name must be dba.
Setting limits for the CONTROL-M/Server account on UNIX

UNIX computers have predefined limits that are designed to restrict or prevent the excessive use of resources by a single process. If a process exceeds its specified limit, the operating system may kill the process without cleanup and without generating diagnostics. To avoid premature termination of running processes, use the limits specified in Table 6. You can check the current limits in your computer by issuing the limit command. On some operating systems, this command is reserved for Super Users only. Table 6
Parameter datasize
Limits for CONTROL-M/Server accounts on UNIX

Description Maximum size of the data segment of a process. Maximum values:

Solaris: 2GB HP-UX: 4GB (using third and fourth quarter enabled) AIX: 2GB
stacksize coredumpsize
The maximum size of the stack segment of a process. BMC Software recommends 400 MB on all UNIX computers. Maximum size that a core dump can reach. BMC Software recommends that this value be set to datasize so that a complete core dump can be generated if a failure occurs. Maximum number of descriptors in use by a single process. Recommended value: 2048 Note: This parameter should not be set to unlimited.
descriptors
memoryuse
Maximum amount of memory to be used by a single process. BMC Software recommends that this value be set to "unlimited."
Software and database compatibility information is listed at: http://www.bmc.com/supportu/PAC_utility/index.cfm. The user installing CONTROL-M must have administrator privileges.
Chapter 2
21
Table 7
Parameter Hardware
Windows requirements for CONTROL-M/Server

Description Computer: Pentium IV 1 GHz or higher Display: 16-bit (65536) colors or higher
Memory
CONTROL-M/Server server components RAM: 512 MB RAM of real memory CONTROL-M/Server client components RAM 256 MB RAM (minimum) 512 MB RAM (recommended for up to 40,000 jobs) 1 GB RAM (recommended for more than 40,000 jobs)
CONTROL-M/Ser ver diskspace Database diskspace (on NTFS disks)
Full CONTROL-M/Server installation: 850 MB Client installation (including the Reporting Facility): 200 MB Server 100 MB Overhead Schema Client
Database type MSSQL Server 2005
Small: 150MB Small: 100 MB 25 MB Medium: 400 MB Medium: 200 MB Large 500 MB Large 350 MB
Related Software
CONTROL-M/Server Internet Explorer version 5.5 or later
Environment Variables
A reference to the WINNT\System32 folder must be in the PATH environment variable. For Windows 2003 this folder is: WINDOWS\System32. The TEMP environment variable must indicate a path that exists on your computer.
Language Settings When working with non-English versions of Windows, set the system locale and language settings to English as follows, before installing CONTROL-M/Server: 1. Select Western Europe and United States in Control Panel => Regional and Language Options for the system to receive all messages in English. 2. Select English(US) in Control Panel => Regional and Language Options => to set the locale to English. After installation you can reconfigure your computer for work with a non-English language. For more information, see the CONTROL-M Language Customization Guide.
22
Required privileges and passwords

In addition to hardware and software requirements, ensure that the resources listed in Table 8 are available before installing CONTROL-M/Server. Table 8
Resource Database administrator
Installation resource requirements

Requirement Required for:

Administrator passwords for existing database servers Information about the location of SQL servers and data files
System administrator (Root user privileges)
Required 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 Running the check_req.sh script Running the orapreinst.sh and orapostinst.sh scripts
CONTROL-M/Server database owner
You are prompted to provide a database owner user name and password during the installation.
Chapter 2
23
24
Chapter
Installing CONTROL-M/Server
NOTE

The CONTROL-M/Server that you are about to install is compatible with CONTROL-M/EM version 6.3.01 or later. BMC Software recommends that you verify that you have installed or upgraded to CONTROL-M/EM version 6.3.01 before installing this version of CONTROL-M/Server.
Installing CONTROL-M/Server on UNIX

Interactive installation
1 Ensure that a database has been installed and is running for CONTROL-M/Server. NOTE
For Oracle installations: If Oracle is down, you must log in to the Oracle database server account and perform the following commands: source .oraenv.csh sqlplus "/as sysdba" startup exit If the Oracle Listener is down, perform the following additional command: lsnrctl start <listenerName> For Oracle databases supplied by BMC Software, <listenerName> is LSTNR_C<instanceName>
Chapter 3 Installing CONTROL-M/Server
25
Silent installation
2 Prepare all the information you need for the installation. Explanations about
parameters are provided in Table 9 on page 29.
3 Log in as the root user. 4 Mount the CONTROL-M/Server installation CD.

For information about mounting a CD, see Appendix C, Mounting CDs on UNIX computers on page 93.
5 Log in to the CONTROL-M/Server account. 6 Use the following command to run the installation script.
<cdPath>/Unix/setup.sh <cdPath> is the path of the mounted CD.
7 Follow the instructions on the screen. Respond to the prompts as necessary until
the following message is displayed. Installation of CONTROL-M/Server completed successfully
8 To start working with CONTROL-M/Server, you must close the current session
and open a new one.
Silent installation
WARNING
CONTROL-M/Server can be installed silently only if the database component was also installed silently.
Silent installation is used to install CONTROL-M/Server from a batch file. The following stages are involved:
Preparing the batch file This is accomplished by running a silent installation preparatory procedure from the installation CD. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. However no installation is performed. Instead, the information you enter is stored in a batch file.
26
Silent installation
Running the prepared batch file When the prepared batch file is run, CONTROL-M/Server is installed using the parameters you specified in the previous step. You can reuse this batch file to silently install CONTROL-M/Server on other computers.
To prepare the silent installation batch file 1 Ensure that a database has been installed and is running for CONTROL-M/Server
as described in Performing a silent installation on page 69(for Sybase) or Performing a silent installation on page 86(for Oracle).
NOTE
For Oracle installations: If Oracle is down, you must log in to the Oracle database server account and perform the following commands: source .oraenv.csh sqlplus "/as sysdba" startup exit If the Oracle Listener is down, perform the following additional command: lsnrctl start <listenerName> For Oracle databases supplied by BMC Software, <listenerName> is LSTNR_C<instanceName>
2 Prepare all the information you will need for the installation.
Parameter explanations are provided in Table 9 on page 29.
3 Log in as the root user. 4 Mount the CONTROL-M/Server installation CD. 5 Log in to the CONTROL-M/Server account. 6 Set the environment variable BMC_SILENT_INSTALL to value Y. See Operating
system levels and patches on page 19 for your UNIX environment.
7 Issue the following command to activate the silent installation script:

<cdPath>/setup.sh <cdPath> is the path of the mounted CD.
8 Follow the interactive menu instructions specifying parameter values as requested.

Chapter 3 Installing CONTROL-M/Server 27
Silent installation
The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS.CTL. If you want to change parameter values, manually modify them in the parameters file.
To install silently 1 Log in to the CONTROL-M/Server account. 2 Set the following environment variables (see Operating system levels and patches on
page 19 for your UNIX environment):
ORG_DBO_PASSWORD to <temporaryPassword> DBO_PASSWORD to <newDboPassword> <temporaryPassword> is the temporary password given to the dbo during the database installation. <newDboPassword> is the dbo password that will be set.
3 Issue the following command:

<cdPath>/setup.sh -r <parameterPath> <cdPath> is the path of the mounted CD. <parameterPath> is the full path to the silent installation file that was created in step 7of To prepare the silent installation batch file on page 27.
4 To start working with CONTROL-M/Server, you must close the current session
and open a new one.
5 Perform the post-installation configuration tasks specified in Chapter 6, Post

installation procedures,.
28
Silent installation
Table 9
CONTROL-M/Server UNIX database and application installation parameters (Part 1 of 2)

Silent installation parameter name
Active installation parameter name

Database Owner Password Local IP Host Interface Name
Description
Set a password for the CONTROL-M/Server database owner. The password must begin with a letter (A-Z, a-z) followed by 5 to 29 alphanumeric characters (includes underscores).
[SETP]/BMC/SERVER Host interface name of the TCP/IP network interface card on /LOCAL_IP_HOST the CONTROL-M/Server platform. This name is used for communication with CONTROL-M/Server and is typically the host name of the CONTROL-M/Server computer. The default value for this parameter is the default host interface name defined in the CONTROL-M/Server computer operating environment. This parameter can also be specified by its IP address (for example, 192.123.186.20). It should be modified only if the CONTROL-M/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 single computers 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). Note: When installing on a computer that supports clustering, specify the Virtual Server Name.
Agent-to-Server Port Number
[SETP]/BMC/SERVER Listening port in the Server computer that receives data from /AGENT_TO_SERVE all Agent computers. The value specified must match the value R_PORT 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 1024 and 65535. Default: 7005
Server-to-Agent Port Number
[SETP]/BMC/SERVER Listening port in the Agent computer that receives data from /SERVER_TO_AGEN this Server computer. The value specified must match the value T_PORT 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 1024 and 65535. Default: 7006
29
Silent installation
Table 9
CONTROL-M/Server UNIX database and application installation parameters (Part 2 of 2)

Silent installation parameter name SETP]/BMC/SERVER /IPC_PORT

Inter Process Communication Port Number
Description
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. Range: 1025-32767 Default: 6005
CONTROL-M/EM [SETP]/BMC/SERVER CONTROL-M/EM TCP/IP Port Number. TCP/IP Port /OUTPUT_SPN CONTROL-M communicates with CONTROL-M/EM using a Number [SETP]/BMC/SERVER pair of consecutive TCP/IP ports (for example, 2370 and 2371). The lower port passes data from CONTROL-M to /INPUT_SPN CONTROL-M/EM. The higher port passes data in the reverse direction. This parameter 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. Range: 1024-32767 Default: 2370. Configuration Agent Port Number SETP]/BMC/SERVER The CONTROL-M/Server Configuration Agent port number. /CTM_CONFIG_AGE Default: 2369 NT_PORT_NUMBER [SETP]/BMC/END_US Progress log file ER_LOG_FILE [SETP]/BMC/DEV_US Trace log file ER_LOG_FILE
Record port usage

The /etc/services file contains a description of the usage of each port on the CONTROL-M/Server platform. Ports reserved for CONTROL-M/Server use should be record here. Proper maintenance of this file helps prevent conflicting usage of ports by various applications.
1 To save all operations and communications parameters in the file etc/services, run
the following command under a root user: ctm_server/scripts/ctm_etcservices
2 At the message prompt, type y to update the /etc/services file.

30 CONTROL-M/Server and CONTROL-M/Agent Installation Guide
Modifying the automatic startup procedure for CONTROL-M/Server
Modifying the automatic startup procedure for CONTROL-M/Server

The database server and CONTROL-M/Server should be running at all times on the primary server platform. BMC Software recommends that they be started at system startup time. You can modify the startup procedure to ensure that the database server, CONTROL-M/Server, and the CONTROL-M/Server Configuration Agent are started during system startup. The command to copy the necessary startup instructions to your system startup directory is listed below.
NOTE
Do not perform this procedure when installing CONTROL-M/Server on a mirror (backup) environment.
For AIX
cp <ctmHomeDir>/ctm_server/data/rc.<controlmUser> /etc/ Open the /etc/inittab file in an editor, and append the following line at the end of the file. <controlmUser>:2:respawn:/etc/rc.<controlmUser>
EXAMPLE
For a user called controlm, specify the following command:
cp /home/controlm/ctm_server/data/rc.ctm630 /etc
and in file /etc/inittab add:

controlm:2:respawn:/etc/rc.ctm630
For HP-UX
cp <ctmHomeDir>/ctm_server/data/rc.<controlmUser> /sbin/init.d/<controlmUser> ln -s /sbin/init.d/<controlmUser>/sbin/rc2.d/S98<controlmUser>
EXAMPLE
cp /home/controlm/ctm_server/data/rc.ctm630 /sbin/init.d/ctm630
ln -s /sbin/init.d/ctm630 /sbin/rc2.d/S98ctm630
31
Installing CONTROL-M/Server on Microsoft Windows
For Solaris
cp <ctmHomeDir>/ctm_server/data/rc.<controlmUser> /etc/rc2.d/S98<controlmUser>
EXAMPLE
cp /home/controlm/ctm_server/data/rc.ctm630 /etc/rc2.d/S98ctm630
For Linux
cp <ctmHomeDir>/ctm_server/data/rc.<controlmUser> /etc/rc.d/rc2.d/S98<controlmUser>
EXAMPLE
cp /home/controlm/ctm_server/data/rc.ctm630 /etc/rc.d/rc2.d/S98ctm630
For SuSE, run the following command after coping the file:
>SuSEconfig
Installing CONTROL-M/Server on Microsoft Windows

CONTROL-M/Server on Microsoft Windows must run on an MSSQL database (Sybase and Oracle are not supported). You must ensure that an MSSQL database server and necessary client software are installed before installing CONTROL-M/Server. A silent installation procedure is also available to install CONTROL-M/Server. This procedure lets you set up a batch file with all the necessary parameter information to install CONTROL-M/Server using a single command. This is especially useful when the product needs to be installed on several computers. For more information, see Silent installation on page 34.
Considerations for a Microsoft Windows cluster environment

Review the following notes if you will be installing CONTROL-M/Server in a Microsoft Windows cluster environment:
32
Do not share the IP and Network Name resources that identify the cluster with a CONTROL-M/Server. Disk, IP, and Network Name resources must be online in the virtual server group where CONTROL-M/Server is to be installed. Agents that share the same IP and Network name resources must be associated with separate CONTROL-M/Servers. Silent installation of CONTROL-M/Server is not supported for Microsoft Windows cluster environments.
1 Ensure that all pre-installation hardware, software, and database requirements are
in place as described in Chapter 2, Planning for CONTROL-M/Server.
NOTE
If you are installing CONTROL-M/Server over a network, you must ensure that the network drive has been mapped; otherwise, the installation will fail.
2 Log in as a user that has administrator privileges on the current computer.

CONTROL-M/Server runs as a Windows Service. If the Windows Service is not defined to run on the local user, this user must have the following this account privileges:

act as part of operating system logon as batch job increase quotas replace a process level token logon as a service
NOTE
Depending on your Windows security settings, you may receive a Microsoft warning about running the BMC Software installation file. You can safely ignore this message.
3 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, run the Setup.exe file manually.
33
Silent installation
4 Follow the prompts to complete the installation.

The parameters for this installation are described in Table 10 on page 35 and Table 11 on page 36.
NOTE
If Microsoft Data Access Components (MDAC) are not already installed on your computer, it is installed with this installation of CONTROL-M/Server.
Silent installation
NOTE
Silent installation of CONTROL-M/Server is not supported for Microsoft Windows cluster environments.
Silent installation is used to install CONTROL-M/Server from a batch file. The following stages are involved:
Running the prepared batch file When the prepared batch file is run, CONTROL-M/Server is installed using the parameters you specified in the previous step. You can reuse this batch file to silently install CONTROL-M/Server on other computers.
To prepare the silent installation batch file 1 If the installation CD will be accessed through a network, you must first map the
CD drive and assign a drive letter.
2 Insert the installation CD into the mapped drive, navigate to the installation folder,
and run the following command: <drive>\prep_silent.bat
34
Silent installation
3 After selecting the type of installation required and entering the necessary
parameters values at the prompts, select Save & Exit to save the parameters. The parameters are saved to: %TEMP%\BMC_CTMSRV_silent.bat.
To install silently 1 Log in to the target computer using an ID with administrator privileges. 2 If the BMC_CTMSRV_silent.bat file will be accessed through a network, you
must first map the CD drive and assign a drive letter.
3 Open a command prompt window, navigate to the path where the

BMC_CTMSRV_silent.bat file now resides, and run the silent installation by issuing the following command: <path>\BMC_CTMSRV_silent.bat
4 After the installation is complete, check the information in the

%TEMP%\ctmsrv630_silent_log.txt file to ensure that the installation ended successfully. Table 10 CONTROL-M/Server Windows cluster installation parameters

Clustering Parameters
Description
Select a group Highlight the virtual server group for which this CONTROL-M/Servers IP address and the Network Name were created. Select the Disk resource for this CONTROL-M/Server. Select the Network Name resource that was created for this CONTROL-M/Server. This display-only field indicates the order in which clusters will perform failover handling.
Select the Disk resource Select the Network resource
Cluster Management
Note: A CONTROL-M/Server cluster installation cannot be installed silently.
35
Silent installation
Table 11
CONTROL-M/Server Windows database and application parameters (Part 1 of 3) Silent installation parameter name
INSTALLDIR

Destination Folder
Description
The folder you specify in this window becomes the home folder for CONTROL-M/Server. All selected components are installed in subdirectories under this folder. Default: <drive>:\Program Files\BMC Software\CONTROL-MServer
Database Server Name
CTMSRV_DATABASE Name of the MSSQL database server. _SERVER_NAME Set a name for the CONTROL-M/Server database schema owner. The name must begin with a letter (A-Z, a-z) followed by up to 7 alphanumeric characters (includes underscores). Set a password for the CONTROL-M/Server database owner. The password must begin with a letter (A-Z, a-z) followed by 5 to 29 alphanumeric characters (includes underscores).
Database Owner Login CTMSRV_DBO_USER _NAME
Database Owner Password
CTMSRV_DBO_PASS WORD
Database Administrator Login Database Administrator Password CONTROL-M/Server Database Name Database Size Data Device Physical Full Path File Name Data Device Size
CTMSRV_DBA_USER_ Name of the database administrator. NAME CTMSRV_DBA_PASS WORD Password of the database administrator.
CTMSRV_DATABASE Name for the CONTROL-M/Server database. The _NAME name must begin with a letter (A-Z, a-z) followed by up to 29 alphanumeric characters (includes underscores). CTMSRV_COMBO_D BSIZE Size of CONTROL-M/Server database (small, medium, large). Default: medium.
CTMSRV_DATA_DEV Specify a new filename that includes the full path to the ICE_PATH physical device where the CONTROL-M/Server database resides. CTMSRV_DATA_SIZE Amount of space (in MB) to allocate for the data portion of the database. You must take into consideration the number of jobs in the Active Jobs file. CTMSRV_LOG_DEVI CE_PATH_ CTMSRV_LOG_SIZE Specify a new filename that includes the full path to the physical device where the CONTROL-M/Server database log resides. Amount of space (in MB) to allocate for the transaction log. The recommended amount is 1/3 of the data device size.
Log Device Physical Full Path File Name Log Device Size
36
Silent installation
Table 11
Description
Local IP Host Interface CTMSRV_LOCAL_IP_ Host interface name of the TCP/IP network interface Name HOST_INTERFACE_N card on the CONTROL-M/Server platform. This name AME is used for communication with CONTROL-M/Server and is typically the host name of the CONTROL-M/Server computer. The default value for this parameter is the default host interface name defined in the CONTROL-M/Server computer operating environment. This parameter can also be specified by its IP address (for example, 192.123.186.20). It should be modified only if the CONTROL-M/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 single computers 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). Note: When installing on a computer that supports clustering, specify the Virtual Server Name. Agent-to-Server Port Number CTMSRV_AGENT_TO Listening port in the Server computer that receives data _SERVER_PORT_NUM 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 1024 and 65535. Default: 7005 CTMSRV_SERVER_T O_AGENT_PORT_NU M 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 1024 and 65535. Default: 7006
Server-to-Agent Port Number
37
Silent installation
Table 11
CTMSRV_IPC_PORT_ NUM

Inter Process Communication Port Number
Description
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. Range: 1025-32767 Default: 6005
CONTROL-M/EM TCP/IP Port Number
CTMSRV_CTMEM_PO CONTROL-M/EM TCP/IP Port Number. RT_NUM 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 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. Range: 1024-32767 Default: 2370.
38
Chapter
Installing CONTROL-M/Agent on UNIX

4
This chapter describes how to install and upgrade CONTROL-M/Agent on UNIX.
NOTE

For the most current operating system compatibility information for this version, see http://www.bmc.com/supportu/PAC_utility/index.cfm.
System requirements
Ensure that your computer meets the following requirements: Table 12
Memory Disk Space Java Runtime Environment
Minimum system requirements

Value 128 MB 50 MB free disk space in the CONTROL-M/Agent home directory. Additional disk space is required for job sysouts. Version 1.4 This requirement is necessary only for running Agent utilities. It is not required to run Agent jobs.
Requirement
Chapter 4 Installing CONTROL-M/Agent on UNIX
39
Preparing for the installation
Preparing for the installation

To ensure that you are ready to install CONTROL-M/Agent on UNIX 1 Check that the prerequisites described in System requirements on page 39 are
met.
2 Kernel parameter values must be modified as specified in Table 13.

Table 13
Parameter
Kernel parameter requirement for CONTROL-M/Agent

Additional values Increase the current parameter value by 1 for each Agent to be installed on the computer.
semmni semmns
3 Define a CONTROL-M/Agent user account.

CONTROL-M/Agent must be installed on a user account that is located on the local file system. The user can be a local user or an NIS user, but the account home directory must be located on a local disc and not on NFS. The permissions of the account home directory must allow read and execute permissions to all users and full permission to the account owner (755 as a minimum).
NOTE
The proclog and sysout directories can be placed on NFS as part of the post installation process. For more information see Setting CONTROL-M/Agent file permissions for NFS on page 60.
4 Ensure that the IPC subsystem is enabled. You can check its status by issuing the
ipcs -a command.
5 Verify that your locale is set to English before beginning the installation. (You can
check this using the locale command.) You can change this setting after the installation process is complete.
NOTE

All computers in the CONTROL-M environment must be set to the same locale. 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.
40
CD-ROM drive considerations
CD-ROM drive considerations

You can mount the CONTROL-M/Agent installation CD 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
The mount command is different for each UNIX type. For more information, see Appendix C, Mounting CDs on UNIX computers. BMC Software recommends that you use the ISO-9660 option (if available). Consult your system administrator about the usage of the mount command.
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:
1 Log in as user root. 2 Create an empty directory for mounting the CD-ROM drive. (This directory cannot
be under the CONTROL-M/Agent installation directory.)
3 Connect the CD-ROM drive to the mount directory using the mount command.
Using a remote CD-ROM drive

1 Log in as a root user on the remote computer. 2 Create an empty directory (For example, /cdromr) for the CD-ROM drive. This
directory cannot be under the CONTROL-M/Agent installation directory.
3 Mount the installation CD. 4 List the /cdromr directory in the /etc/exports file to make it accessible to the
Network File Server (NFS) utility.
41
Interactive installation or upgrade of CONTROL-M/Agent on UNIX
NOTE
The NFS export utility works differently for various UNIX types. For more information, consult your system administrator.
5 Log in as a root user on the CONTROL-M/Agent computer. 6 Create an empty directory (e.g., /cdrom) for mounting the remote /cdromr
directory.
7 Use the following command to connect the remote /cdromr directory to your local
/cdrom directory: mount <remoteMachine>:/cdromr /cdrom

1 Ensure that the installation CD is mounted. For information about mounting a CD,
see Appendix C, Mounting CDs on UNIX computers..
2 Log in as the root user. 3 Navigate to the home directory of the CONTROL-M/Agent user account using the
following command: cd $CONTROLM.
4 Before performing an upgrade installation: A ensure that CONTROL-M/Agent is not running B on AIX, you must run slibclean before beginning the upgrade 5 Use the following command to run the installation script:
<cdPath>/Unix/setup.sh <cdPath> is the path of the mounted CD. Follow the instructions on the screen, filling in parameter values and fields as necessary. The parameters and fields for this installation are described in Table 14. If a previous version of CONTROL-M/Agent is detected, an upgrade is performed. In this case, the parameters values from the previous version are used.
42
Upon completion of the installation, the following message is displayed: Installation of CONTROL-M/Agent completed successfully
NOTE
The installation log can be found in the home directory of the CONTROL-M/Agent account, for example: $CONTROLM/BMCINSTALL/log/DRKAI.6.3.01_user.log $CONTROLM is the path of the CONTROL-M/Agent user account.
Table 14
Installation Parameters - CONTROL-M/Agent on UNIX

Silent installation parameter name SRV_2_AGT_PORT Description 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 1024 and 65535. Default: 7006 The host name of the computer on which CONTROL-M/Server is installed. If the CONTROL-M/Server is in a cluster, the CONTROL-M/Server Network Name is required.
Active installation parameter name Server to Agent Port number
Primary CONTROL-M/Server Host
CTRLM_HOST
Authorized CONTROL-M/Server Host Agent-to-Server Port Number
AUTHORIZED_CTRLM Specifies one or more CONTROL-M/Servers that will _HOSTS be authorized to submit jobs to this agent. Use '|' to separate between host names. AGT_2_SRV_PORT 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 1024 and 65535. Default: 7005. Set the locale to the local language. The locale must be already defined on the system. This parameter is used only with latin1 characters sets.
Locale
AGT_LOCALE
43
Silent installation or upgrade of CONTROL-M/Agent on UNIX
Silent installation or upgrade of CONTROL-M/Agent on UNIX

Silent installation is used to install or upgrade CONTROL-M/Agent from a batch file. The following stages are involved:
Running the prepared batch file When the prepared batch file is run, CONTROL-M/Agent is installed using the parameters you specified in the previous step. You can reuse this batch file to silently install CONTROL-M/Agent on other computers.
To prepare the silent installation or upgrade batch file 1 Prepare all the information you will need for the installation.
Parameter explanations are provided in Table 14 on page 43.
2 Log in as the root user. 3 Navigate to the CONTROL-M/Agent home directory. 4 Set the environment variable named BMC_SILENT_INSTALL to Y as follows:
For sh, ksh, and bash shell users: BMC_SILENT_INSTALL=Y export BMC_SILENT_INSTALL For csh/tcsh shell users: setenv BMC_SILENT_INSTALL Y
5 Activate the installation script with the following command:

<cdPath>/Unix/setup.sh
44
Modifying the automatic startup procedure for CONTROL-M/Agent
6 Follow the interactive menu instructions specifying parameter values as requested.

If a previous CONTROL-M/Agent installation is detected, the current parameters and their values are displayed. The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS.CTL The parameters file is also saved to BMCINSTALL/installed/agent on each Agent installed using the silent installation procedure.
7 The installation parameters file should be copied to a network location that is

accessible to all computers on which a silent installation will be performed.
NOTE
In a new installation you can modify parameter values by editing the parameter file using a text editor. For an upgrade installation, you must add each parameter and its value to the parameters file.
To install silently 1 Log in as the root user. 2 Navigate to the CONTROL-M/Agent home directory. 3 Use the following command to run the installation script:
<cdPath>/Unix/setup.sh -respond <parameterPath> <cdPath>is the path of the mounted CD. <parameterPath> is the full path to the parameter file that was created in Step 1.
Modifying the automatic startup procedure for CONTROL-M/Agent

As with CONTROL-M/Server, BMC Software recommends that you start CONTROL-M/Agents automatically at system startup time. You should consult your system administrator for the correct commands with regard to CONTROL-M/Agent on the platform you are using.
45
Information for upgrades from version 6.2.0.1
During installation of CONTROL-M/Agent, a ready-made startup script, rc.agent_user, is placed in the $CONTROLM/ctm/scripts/ directory. $CONTROLM is the path of CONTROL-M/Agent user home directory. You can copy this script (renaming it if necessary) to the operating system startup directory as described in Modifying the automatic startup procedure for CONTROL-M/Server on page 31.
NOTE
CONTROL-M/Agents that were shut down manually are not restarted by the automatic startup procedure during a shutdown-restart operation.
Information for upgrades from version 6.2.0.1

The section specifies the changes that are performed to your system when CONTROL-M/Agent is upgraded from a previous version.
Changes to system files

The installation procedure modifies system files as follows:
NOTE
The following is for your information only. It describes actions that are performed automatically by the CONTROL-M/Agent installation.
1. The following line is removed from the /etc/inetd.conf file or the /etc/xinetd.conf file: <service><socketType> tcp nowait root <agentExe> p_ctminetd -e I $CONTROLM/ctm/ <service> Agent service-name specified during installation. Default: ctmagent <socketType> Socket type used for the service (stream for tcp). <agentExe> Path of CONTROL-M/Agent executable files. $CONTROLM/ Path of CONTROL-M/Agent user home directory. 2. The following line is removed from file /etc/services: <service> <portNumber>/<protocol> # CONTROL-M Agent
46
Upgrade with CONTROL-M Option for Oracle Applications installed
<service>Agent service-name specified during installation. Default: ctmagent <portNumber>Value specified for Server-to-Agent Port Number. <protocol>Protocol used for communication between the Server platform and the Agent platform (TCP only)
Upgrade with CONTROL-M Option for Oracle Applications installed

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 this new version.
1 Ensure that all jobs submitted to the CONTROL-M/Agent have ended. Otherwise,
the status of running and submitted jobs will become UNKNOWN.
2 Create another UNIX user account for the Option. 3 Install the latest version of the Option on the new user account and configure its
environment variables.
4 Copy all files from the <oldControl-mOption>/DATA directory to the

<newControl-mOption>/DATA directory.
5 Verify that the new Option is working properly. 6 Before upgrading the Agent, modify its .cshrc file by removing all references to the
<oldControl-mOption>/EXE directory.
Upgrade with CONTROL-M Option for PeopleSoft installed

Use the following procedure to enable the installed CONTROL-M Option for PeopleSoft to work with CONTROL-M/Agent after the upgrade:
1 Perform the CONTROL-M/Agent upgrade process as described in the

CONTROL-M Installation Guide (this book).
2 If necessary, modify the CLASSPATH environment variable to point to the new

location of the CONTROL-M Option for PeopleSoft files.
47
Post installation
Post installation
See Setting the protocol version for the upgraded CONTROL-M/Agent on page 60.
Uninstalling CONTROL-M/Agent from UNIX

Use the following procedure to completely remove all CONTROL-M/Server components from UNIX:
1 Log in to the CONTROL-M/Agent computer as user root. 2 Navigate to the CONTROL-M/Agent home directory. 3 Use the following command to run the uninstallation script from the home
directory: ${HOME}/BMCINSTALL/uninstall/ctma_uninstall.sh [-silent] If the -silent parameter is used, uninstall is performed immediately. If not, you are asked to confirm the your intention to uninstall. The uninstall procedure performs the following tasks:
shuts down and uninstalls CONTROL-M/Agent uninstalls all CONTROL-M Control Modules uninstalls all detected fix packs and patches
48
Chapter
Installing CONTROL-M/Agent on Microsoft Windows

5
This chapter describes how to install and upgrade CONTROL-M/Agent for Microsoft Windows.
NOTE

For the most current operating system compatibility information for this version, see: http://www.bmc.com/supportu/PAC_utility/index.cfm. Ensure that your computer meets the following requirements: Table 15
Resource Operating Systems
System requirements (Part 1 of 2)

Requirement 2000 Server 2000 Advanced Server 2000 Datacenter 2000 Professional 2003 Standard Edition 2003 Enterprise Edition 2003 Enterprise Edition on Itanium 64-bit XP Professional 128 MB
Memory
Chapter 5
49
Table 15
Resource
System requirements (Part 2 of 2)

Requirement 50 MB free disk space in the CONTROL-M/Agent home drive. Additional disk space is required for job sysouts. Version 1.4 This requirement is necessary only for running Agent utilities. It is not required to run Agent jobs.
Disk Space
Java Runtime Environment
NOTE
BMC Software recommends that you install at least one instance of CONTROL-M/Agent on the CONTROL-M/Server computer.
A non-interactive (silent) installation and upgrade procedure is also available for CONTROL-M/Agent for Microsoft Windows in this book. For more information, see Silent installation of CONTROL-M/Agent for Microsoft Windows.
NOTE
For information about modifying installation parameters after the installation is complete, see the CONTROL-M/Agent for Microsoft Windows Administrator Guide.

Review the following notes if you will be installing CONTROL-M/Agent in a Microsoft Windows cluster environment:
Interactive upgrade installation on a cluster environment is supported from version 6.1.03 only. Multiple Agents can be installed on the same virtual server group or in separate virtual server groups. Select an Agent name that is different from the cluster Network Name or the name of one of its nodes. Do not share the IP and Network Name resources that identify the cluster with an Agent.
50
Working with multiple agents on the same computer
Agents that share the same IP and Network name resources must be associated with separate CONTROL-M/Servers. Disk, IP, and Network Name resources must be online in the virtual server group where CONTROL-M/Agent is to be installed. Silent installation and silent upgrade of CONTROL-M/Agent is not supported for Microsoft Windows cluster environments.
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 discussed below.
Why use multiple Agents? With multiple agents, more than one CONTROL-M/Server can 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. All CONTROL-M Control Modules work with the default agent. Some CONTROL-M Control Modules work with non-default agents.
Chapter 5
51
Considerations for control modules
Upgrading a multiple agent environment When upgrading a multiple agent installation, you must run the installation program a separate time for each agent you want to upgrade. Each time you run the program, you are prompted to select the logical name of an agent that has not yet been upgraded to the current version. You must upgrade all agents first before installing additional agents. The Default agent from the previous version will remain as the Default agent in the new version.
Considerations for control modules

CONTROL-M/Agents use Control Modules to interact with the operating system and with third party applications (for example, SAP).
New CONTROL-M/Agent Installation 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 additional CONTROL-M Control Modules (for example, SAP, AFT, or Oracle Applications), they must be installed after CONTROL-M/Agent is installed.
CONTROL-M/Agent Upgrade No changes need to be made to CONTROL-M Control Modules or CONTROL-M Options that existed before the upgrade.
Additional Control Modules All CONTROL-M Control Modules work with the default agent.
Interactive installation or upgrade of CONTROL-M/Agent on Windows

1 Log in to a user account belonging to the local Administrators group. 2 If CONTROL-M/Agent is monitored by an application (for example, BMC
Software Patrol Agent) that ensures it remains running, you must shut down the monitoring application before beginning an upgrade installation.
3 Insert the installation CD in the CD-ROM drive.
52
Interactive installation or upgrade of CONTROL-M/Agent on Windows
If the Autorun option is enabled, installation starts automatically and the opening screen is displayed. If the Autorun option is not enabled, browse to the Windows folder on the CD-ROM drive, and double-click Setup.bat.
NOTE
Depending on your Windows security settings, you may receive a Microsoft warning about running the BMC Software installation file. You can safely ignore this message.
4 Follow the prompts to complete the installation.

The parameters and fields for this installation are described in Table 16. Table 16
Parameter Agent Name
CONTROL-M/Agent Installation parameters (Part 1 of 2)

Description 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. Type of Agent installation on a cluster enabled environment: Cluster: Installs an Agent in a cluster enabled environment. Local: Installs an Agent locally without joining it to the existing cluster environment.
Setup Type
Destination Folder Primary CONTROL-M/ Server Host
Indicates the location in which the Agent will be installed. To change the installation folder, click Change and Browse to the desired location. Indicates the host name of the computer where CONTROL-M/Server is installed. Name of the computer hosting the CONTROL-M/Server that submits requests to this Agent. If the CONTROL-M/Server is in a cluster, the CONTROL-M/Server Network Name is required. Note: Specify a name, not an IP address. Default: Computer on which the installation was made.
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. Note: Specify names, not IP addresses. Default: Name of the primary CONTROL-M/Server host.
Agent-toServer Port Number
Listening port in the Server computer that receives data this Agent. The value specified must match the value assigned to the Agent-to-Server Port Number parameter on the Server. Verify that this port number is not used in the Server for any other purpose. Specify a numeric value between 1024 and 65535. Default: 7005
Chapter 5
53
Importing WIN panel functionality
Table 16
Parameter
CONTROL-M/Agent Installation parameters (Part 2 of 2)

Description Listening port of this Agent that receives data from the Server. The value specified must match the value assigned to the Server-to-Agent Port Number parameter (for this Agent) on the Server. Verify that this port number is not used for any other purpose. Specify a numeric value between 1024 and 65535. Default: 7006 Select a group Select the Disk resource Select the Network resource Cluster Management Highlight the virtual server group for which this Agents IP address and the Network Name were created. Select the Disk resource for this Agent. Select the Network Name resource that was created for this Agent. This display-only field indicates the order in which clusters will perform failover handling.
Server-toAgent Port Number Clustering Parameters
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.
1 Ensure that the CONTROL-M/Agent application CD is on a mapped drive. 2 In CONTROL-M/Desktop, choose Tools => Import Applications Forms. 3 A browse window is displayed. Navigate to the Windows\Forms folder on the
application CD.
4 Select the windows.xml file and click Import. 5 Shut down and restart CONTROL-M/EM.
54
Setting the protocol version for the upgraded CONTROL-M/Agent

Use the following steps to set the Protocol Version for the upgraded Agent in CONTROL-M/Server:
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. The following prompt is displayed: To view/modify communication parameters, enter node ID of Agent Platform:
2 Enter the node ID of a CONTROL-M/Agent, for example, diana. The

Communicating with Specific Agent Platform (diana) menu is displayed.
3 Specify 06 for the Communication Protocol Version for the agent.
Silent installation of CONTROL-M/Agent for Microsoft Windows

The silent installation procedure can be used to install CONTROL-M/Agent as a batch job instead of using the interactive installation procedure. This requires placing the parameters that you would normally enter in interactive mode into a file that is accessed by the silent installation procedure. The silent installation procedure can be used to install a single Agent each time it is run.
1 Prepare the installation parameters:

A. Log in using a user ID having Administrator privileges on the current computer. B. Insert the Installation CD. C. Browse to the Windows folder of the CD-ROM drive. D. Run (double-click) the prep_silent.bat file. The parameters are saved in the following file: %TEMP%\DRNDN.6.3.01Silent.bat
Chapter 5
55
2 Run the silent installation procedure:

A. Ensure that the installation CD used in Step 1 is still available. B. Run the following command: %TEMP%\DRNDN.6.3.01Silent.bat C. Check the %TEMP%\DRNDN6.3.01_silent_log.txt file to ensure that the installation ended successfully. The silent installation procedure adds a CONTROL-M Agent <vv.rr.mm> entry to the Start => Programs menu.
NOTE
The same batch file can be copied to other computers and used to create several identical installations. If necessary, you can modify the CD source mapping by altering the Auto_CD_ Image variable in the DRNDN.6.3.01Silent.bat file. UNC mapping can also be used.
Table 17 Parameter
Silent installation parameters (Part 1 of 2) Description

Logical name of this Agent installation. This name is used to differentiate between multiple installations of CONTROL-M/Agent on the same computer. Name of the installation folder. Default: <drive>\Program Files\BMC Software\CONTROL-M Agent\ <drive> identifies the drive where Program Files are defined in this computer 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. 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.
AgentName
DestinationFolder
CTMAG_ServerHostName
CTMAG_PermittedServers
CTMAG_AgentToServerPort
Port number used by the CONTROL-M/Server platform for receiving data from the CONTROL-M/Server platform (Agent-to-Server port number). Default: 7005 Note: Specify a numeric value from 1024 to 65535.
56
Table 17 Parameter
Silent installation parameters (Part 2 of 2) Description

Port number used by the CONTROL-M/Server platform for receiving data from the CONTROL-M/Server platform (Server-to-Agent port number). Default: 7006 Note: Specify a numeric value from 1024 to 65535.
CTMAG_ServerToAgentPort
CTMAG_TCP_Timeout CTMAG_LOGON_AS_USER
TCP/IP Timeout (in seconds). Valid values: numeric value greater than or equal to zero. Default: 60 Job submission method. Valid values are:
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.
CTMAG_DOMAIN
Domain from which the log in will be performed. Valid values: <domainName> " " (Blank) . (period)
CTMAG_DFTRRT CTMAG_DOMAIN_SERVER CTMAG_JO_STATISTIC
Default printer for job output (sysout) files. Specify a printer name. Domain controller. Specifies the name of the server managing access to the available resources and database. 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.
CTMAG_SRV_USER
User under which the CONTROL-M/Server 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).
CTMAG_SRV_PASS CTMAG_TRACKER_EVENT_P ORT
User password. The tracker event port enables CONTROL-M/Agent to receive updates regarding job status from all Control Modules that are associated with the current CONTROL-M/Agent. Default: 7009
Chapter 5
57
Post installation
Post installation
Perform the following post installation tasks:
Setting a CONTROL-M/Agent permanent connection to CONTROL-M/Server on page 59 Updating CONTROL-M/Agent system path information on cluster installations on page 61.
58
Chapter
Post installation procedures
On UNIX and Windows computers

Setting a CONTROL-M/Agent permanent connection to CONTROL-M/Server
Set the following parameters to enable CONTROL-M/Agent to open a permanent connection to CONTROL-M/Server:
Allow Agent to open a persistent CONTROL-M/Server connection (standard installation parameter). ALLOW_COMM_INIT (silent installation parameter). PERSISTENT_CONNECTION
On UNIX computers
Using NFS with CONTROL-M/Server
1 Verify that CONTROL-M/Server is shut down. 2 Copy the ctm_server/proclog, ctm_server/proclog.save, ctm_server/status, and
ctm_server/temp directories to NFS.
Chapter 6 Post installation procedures
59
3 Delete the copied directories from the local disk. 4 Place a soft link on the local disk under the $HOME/ctm/ directory to point to the
new NFS location for each of the copied directories.
5 Start CONTROL-M/Server.

Use the following steps to set the Protocol Version for an upgraded Agent in CONTROL-M/Server:
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. The following prompt is displayed: To view/modify communication parameters, enter node ID of Agent Platform:
2 Enter the node ID of a CONTROL-M/Agent, for example, diana. The

Communicating with Specific Agent Platform (diana) menu is displayed.
3 Specify 06 for the Communication Protocol Version for the agent.
Setting CONTROL-M/Agent file permissions for NFS

If you have chosen to put the sysout directory on an NFS file system, add the following line to the ctm/data/OS.dat file and restart the Agent: SYSOUT_MODE 666 If you have chosen to put the proclog directory on an NFS file system, add the following line to the ctm/data/OS.dat file and restart the Agent: PROCLOG_MODE 666 The permissions on NFS for both the sysout directory and the proclog directory must be 777.
60
On Windows computers
On Windows computers
Updating CONTROL-M/Agent system path information on cluster installations
On Windows computers with cluster-enabled CONTROL-M/Agents, you must refresh the path on all failover nodes of the Agent. This allows Agent utilities run from the command line to use the correct path from the specific node. Perform the following steps to update the Windows path environment variables. This ensures that all path specifications for CONTROL-M/Agents are updated in the current Windows environment:
1 Choose Start => Settings => Control Panel => System 2 Click Environment Variables in the Advanced tab. 3 Click OK.
Chapter 6 Post installation procedures
61
Updating CONTROL-M/Agent system path information on cluster installations
62
Appendix
Installing Sybase on UNIX

This chapter describes how to install an Sybase database on UNIX for use with CONTROL-M/Server. Table 18 describes the different ways that CONTROL-M/Server can be installed with a Sybase Database. Installation can be performed using interactive mode or silent mode.
NOTE
Subsequent installation of CONTROL-M/Server must use the same mode (interactive or silent) that was used to install Sybase.
Table 18
Sybase installation types

Explanation Installs a CONTROL-M Sybase database server, initiates an instance, and defines database devices on the instance. The following types of dedicated installation are available:

Installation Type Dedicated Server
Default Uses default values for all parameters. Custom Allows modification of installation parameters.
Existing Server
Installs a CONTROL-M Sybase client on the local computer and defines database devices on an existing Sybase database server. The existing database server must use 8K paging. Installs a CONTROL-M Sybase client that enables connection to a remote Sybase server. This installation type can be performed only after database devices have been defined on the Sybase database server.
Sybase Client
Appendix A
63
HP Itanium requirements
HP Itanium requirements
On HP Itanium, the Sybase database server and CONTROL-M/Server must reside on separate UNIX accounts. (On other UNIX platforms, the Sybase database server and CONTROL-M/Server can reside on the same account.)
To install a Sybase database server for CONTROL-M/Server on HP Itanium 1 On the first account, perform a Installing a dedicated database server to install
the Sybase database server.
2 On the second account, perform a Installing on an existing database server to

initiate a new instance and install database devices on the instance. CONTROL-M/Server must be installed to this account.
Installing a dedicated database server

The CONTROL-M Sybase database server can be installed in a raw partition or on a regular file system. If you want to use raw partitions for the CONTROL-M/Server database devices, prepare them before installation of the Sybase database server. Consult your system administrator for more information. Ensure that asynchronous I/O is turned on. On Solaris operating systems this is the default. For AIX, see AIX on page 100. Use the following procedure to perform the installation:
1 If you use the Custom installation, determine the value for each installation
parameter before you begin. These parameters are listed in Table 20 on page 71. If you select the Default installation, these parameters will automatically receive the default value shown in Table 20 on page 71
2 Mount the CONTROL-M Sybase database CD from the root user and log off the
root user before continuing with the installation.
<cdPath>/setup.sh <cdPath> is the path of the mounted CD.
64
Cleaning up a failed dedicated installation
5 When asked to select the "CONTROL-M component for which you want to install
the Sybase component," select CONTROL-M/Server.
6 Select Default or Custom installation mode.

If you are using raw partitions, you must choose the Custom installation. The guidelines governing raw partitions are as follows:
The CONTROL-M/Server database devices can be installed on two to five raw partitions. The data and log files must each have their own partition. tempdb, systemprocs, and master database can each be assigned a separate partition. However, BMC Software does not recommend using a raw partition for tempdb. Data, log, and tempdb sizes can be specified in the Data Device Size, Log Device Size, and Temporary Device File Size parameters of the Custom installation. systemprocs and master database sizes are determined internally.
7 Follow the instructions on the screen, filling in the prompts as necessary. Upon
completion of the installation, the following message is displayed: Installation completed successfully
Cleaning up a failed dedicated installation

If the dedicated Sybase installation failed, no cleanup is necessary before re-running the installation script.
Installing on an existing database server

The Existing installation mode installs a CONTROL-M Sybase client on the local computer and defines database devices on the existing Sybase database server. Before beginning the installation, obtain the necessary database names and passwords from your database administrator The existing Sybase database server must be running during the installation of CONTROL-M/Server.
Appendix A
65
Verifying existing Sybase components
Verifying existing Sybase components

1 Obtain the following for the new CONTROL-M/Server database from your
database administrator:
database name database server administrator login database server administrator password Sybase server host name Sybase server query port number
2 Verify that the Sybase Database server is installed and running by issuing the
following command: isql -U <systemAdministratorLoginName> -P <systemAdministratorPassword> -S <serverName> <systemAdministratorLoginName> is the name of the system administrator account. Default: sa. <systemAdministratorPassword> is the system administrator password. <serverName> is the name of the target Sybase database server.
3 Use the following commands to verify that the database name is unique for the
Sybase database server: sp_helpdb go When creating more than one CONTROL-M/Server installation on the same Sybase database server, the database name and the database owner name must be unique for each installation.
4 Verify that the device file you want to define does not exist by running the
following command on the remote server: ls filename
66
Performing the existing installation
5 Use the following command to check the parameters in Table 19 on page 67 for
correct values: sp_configure parameter_name go Table 19
Parameter max memory number of locks 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 database, including all CONTROL-M/Server installations.
Sybase database server parameters - minimum values

Small < 80 MB 225 MB 30,000 60 Medium Large 80-200 MB > 200 MB 375 MB 30,000 100 750 MB 40,000 200
You must restart the database to implement the changes you make.

<cdPath> /setup.sh <cdPath> is the path of the mounted CD.
the Sybase component," select CONTROL-M/Server.
5 Select the Existing installation mode. 6 Follow the instructions on the screen, filling in the prompts as necessary. Upon
Appendix A
67
Cleaning up a failed existing installation

Uninstalling and cleanup is necessary before re-running the existing Sybase installation. You must first remove all database files that were created by the failed installation (including the $SYBASE/data directory).
To uninstall and cleanup the installation 1 Run the uninstall program (see Uninstalling a CONTROL-M Sybase database
server on page 112).
2 Log in to the Sybase database server as the sa user. 3 Use the sp_helpdb command to determine if the database was created by the
failed installation.
4 If the database was created during a failed installation, use the following command
to drop (remove) it: drop database <databaseName>
5 Specify the following command to check which devices were dropped from the
server: sp_helpdevice go
6 If data or log devices associated with the CONTROL-M database are still listed,
drop them using the following command: sp_dropdevice <deviceName> go
7 If the database was installed using files, delete the files associated with the
dropped elements. Do not delete raw partitions.
Installing a Sybase client

CONTROL-M/Server Sybase database client components can be installed on UNIX accounts to enable them to communicate with an existing CONTROL-M/Server installation. Use the following procedure to perform the installation:
68
Cleaning up a failed client installation
1 Prepare all the information you will need for the installation. Parameters are listed
in Table 20.
<cdPath> /setup.sh <cdPath> is the path of the mounted CD.
the Sybase component," select CONTROL-M/Enterprise Manager.
6 Select the Client installation mode. 7 Follow the instructions on the screen, filling in the prompts as necessary. Upon
Cleaning up a failed client installation

Run the uninstall program to clean up a failed installation (see Uninstalling a CONTROL-M Sybase database server on page 112).
Performing a silent installation

Silent installation is used to install Sybase from a batch file. The following stages are involved:
Running the prepared batch file

Appendix A Installing Sybase on UNIX 69
When the prepared batch file is run, Sybase is installed using the parameters you specified in the previous step.You can reuse this batch file to silently install Sybase on other computers.
To prepare the silent installation batch file 1 If you are installing database devices on an existing Sybase database server (see
Installing on an existing database server on page 65), ensure that the Sybase database server is running.
2 Prepare all the information you will need for the installation.
Explanations are provided in Table 20 Sybase database UNIX interactive installation parameters on page 71.
3 Log in as the root user. 4 Mount the Sybase installation CD. 5 Log in to the CONTROL-M/Server account. 6 Create the silent installation batch file: A Set the environment variable BMC_SILENT_INSTALL to value Y. See Operating
B Issue the following command:

<cdPath>/setup.sh
C Follow the interactive menu instructions, specifying parameter values as

requested. The installation parameters are saved to ${HOME}/BMCINSTALL/PRODUCTS.CTL. If you want to further change parameter values, you must manually modify each parameter and its value in the parameters file.
To install silently 1 Log in to the CONTROL-M/Server account. 2 Set the following environment variables (see Operating system levels and patches on
page 19 for your UNIX environment):
70
Setting Sybase installation parameters
DBO_PASSWORD to <temporaryPassword> SA_PASSWORD to <databaseAdministratorPassword> <temporaryPassword> is the temporary password given to the dbo during the database installation. <databaseAdministratorPassword> is the dba password that will be set.
3 Issue the following command:

<cdPath>/setup.sh -r <parameterPath> <cdPath> is the path of the mounted CD. <parameterPath> is the full path to the parameter file that was created in step 6 on page 70.
NOTE
For a dedicated installation, the SA_PASSWORD should be the new CONTROL-M/Server system administrator password for the Sybase database server. For an existing installation, SA_PASSWORD should be the privileged user password.

Table 20
Parameter Data Device Full Path File Name
Sybase database UNIX interactive installation parameters (Part 1 of 2)

Description Full path name, including the logical device name, of the CONTROL-M/Server database. You must specify a new file name in an existing directory path on the computer where the CONTROL-M Sybase database server is installed. Default: ${HOME}/sybase/data/<dbName>_data.dat. Amount of space in megabytes to allocate for the data portion of the CONTROL-M/Server database. The required space is determined by the number of jobs in the Active Jobs file. Default: 300 MB. CONTROL-M/Server database name.The name must begin with a letter (A-Z, a-z) followed by up to 29 alphanumeric characters or underscores. No spaces are allowed. CONTROL-M/Server default: ctrlm630.
Data Device Size
Database Name
Appendix A
71
Table 20
Parameter
Sybase database UNIX interactive installation parameters (Part 2 of 2)

Description Name for the CONTROL-M/Server database owner. The name must begin with a letter (A-Z, a-z) followed by up to 7 alphanumeric characters or underscores. Default: ctmuser Password for the CONTROL-M/Server database owner. The password must begin with a letter (A-Z, a-z) followed by 5 to 29 alphanumeric characters or underscores. No spaces are allowed. This password is not available to the general user. Name of the CONTROL-M Sybase database server administrator. Default: sa. Password of the CONTROL-M Sybase database server administrator. The name must begin with a letter (A-Z, a-z) followed by 5 to 29 alphanumeric characters or underscores. Default: manager. Size of the CONTROL-M/Server database in megabytes. Default: medium. Full path name, including the logical device name, of the database log. You must specify a new file name in an existing directory path on the computer where the CONTROL-M Sybase database server is installed. Default: ${HOME}/sybase/data/<dbName>_log.dat. Amount of space in MB to allocate for the transaction log. The recommended amount is 30% of the space allocated for the CONTROL-M/Server database. Default: 100 MB.
Database Owner Login
Database Owner Password
Database Server Administrator Login Database Server Administrator Password
Database Size Log Device Full Path File Name
Log Device Size
Master Device Full Path File Full path name of the CONTROL-M Sybase database server. Name Default: ${HOME}/sybase/ASE-12_5/data/master.dat Sybase Server Backup Port Number The port that the CONTROL-M Sybase database backup server uses for external communication. Default: 7104 (if this port is already in use, the port number is increased by 1 until an unused port is found). Host name of the Sybase Database server computer. Default: Name of the host on the local computer. The port that the Sybase database server computer uses for external communication. Default: 7102 (if this port is already in use, the port number is increased by 1 until an unused port is found).
Sybase Server Host Name Sybase Server Query Port Number
Sybsystemprocs Device Full Full path name of the CONTROL-M Sybase database server Path File Name system procedures database. Default: ${HOME}/sybase/ASE-12_5/data/sybsystemprocs.dat Temporary Device File Size Size of the temporary database in megabytes. Default: 80 MB. Temporary Device Full Path Full path name of the CONTROL-M Sybase database server File Name temporary database. Default: ${HOME}/sybase/ASE-12_5/data/tempdb.dat
72
Table 21
Parameter
Sybase database UNIX silent installation parameters (Part 1 of 3)

Description
[SETP]/BMC/DEV_USER_LOG_FILE Trace log file path [SETP]/BMC/END_USER_LOG_FILE End user progress log file path [SETP]/BMC/SYBASE/DATABASE_ SIZE [SETP]/BMC/SYBASE/DATABASE_ DATA_DEVICE_PATH Size of the CONTROL-M/Server database in megabytes. Default: 300 MB. Full path name, including the logical device name, of the CONTROL-M/Server database. You must specify a new file name in an existing directory path on the computer where the CONTROL-M Sybase database server is installed. Default: ${HOME}/sybase/data/<dbName>_data.dat Amount of space in megabytes to allocate for the data portion of the CONTROL-M/Server database. The required space is determined by the number of jobs in the Active Jobs file. Default: 300 MB Database log size. Full path name, including the logical device name, of the database log. You must specify a new file name in an existing directory path on the computer where the CONTROL-M Sybase database server is installed. Default: ${HOME}/sybase/data/<dbName>_log.dat Amount of space in megabytes to allocate for the transaction log. The recommended amount is 30% of the space allocated for the CONTROL-M/Server database. Default: 100 MB CONTROL-M/Server database name. Maximum length: 30 characters. The name must begin with an alphabetic character. No spaces are allowed. Default: ctrlm630 Name for the CONTROL-M/Server database owner. The name must begin with a letter (A-Z, a-z) followed by up to 7 alphanumeric characters (includes underscores). Default: ctmuser Database server administrator login name. The port that the CONTROL-M Sybase database backup server component uses for external communication. Default: 7104 (if this port is already in use, the port number is increased by 1 until an unused port is found). Master database size.
[SETP]/BMC/SYBASE/DATABASE_ DATA_DEVICE_SIZE
[SETP]/BMC/SYBASE/LOG_ DATABASE_SIZE [SETP]/BMC/SYBASE/DATABASE_ LOG_DEVICE_PATH
[SETP]/BMC/SYBASE/DATABASE_ LOG_DEVICE_SIZE
[SETP]/BMC/SYBASE/DATABASE_ NAME
[SETP]/BMC/SYBASE/DATABASE_ OWNER_NAME
[SETP]/BMC/SYBASE/DATABASE_ PRIVILEGE_USER_NAME [SETP]/BMC/SYBASE/DATABASE_ SERVER_BACKUP_PORT_NUMBE R
[SETP]/BMC/SYBASE/DATABASE_ SERVER_MASTER_DATABASE_SI ZE
Appendix A
73
Table 21
Parameter

Description
[SETP]/BMC/SYBASE/DATABASE_ Full path name of the CONTROL-M Sybase database SERVER_MASTER_DEVICE_PATH server. Default: ${HOME}/sybase/ASE-12_5/data/master.da [SETP]/BMC/SYBASE/DATABASE_ SERVER_MASTER_DEVICE_SIZE [SETP]/BMC/SYBASE/DATABASE_ SERVER_MEMORY_MODEL Master database device size (greater than or equal to master database size).
Existing Installation: set database size boundaries. Default size: medium. Dedicated Installation: optimize the database setting.
[SETP]/BMC/SYBASE/DATABASE_ SERVER_PORT_NUMBER
The port that the computer on which the CONTROL-M Sybase database server is installed uses for external communication. Default: 7102 (if this port is already in use, the port number is increased by 1 until an unused port is found.) System database size.
[SETP]/BMC/SYBASE/DATABASE_ SERVER_SYSTEM_DATABASE _SIZE [SETP]/BMC/SYBASE/DATABASE_ SERVER_SYSTEM_DEVICE_PATH [SETP]/BMC/SYBASE/DATABASE_ SERVER_SYSTEM_DEVICE_SIZE [SETP]/BMC/SYBASE/DATABASE_ SERVER_TEMPDB_DATABASE_SI ZE
System database device path. System database device size (greater or equal to System database size). Tempdb database size.
[SETP]/BMC/SYBASE/DATABASE_ Full path name of the CONTROL-M Sybase database SERVER_TEMPDB_DEVICE_PATH server temporary database. Default: ${HOME}/sybase/ASE-12_5/data/tempdb.dat [SETP]/BMC/SYBASE/DATABASE_ SERVER_TEMPDB_DEVICE_SIZE [SETP]/BMC/SYBASE/DATABASE_ SERVER_SYSTEMPROC_DATABA SE_SIZE [SETP]/BMC/SYBASE/DATABASE_ SERVER_SYSTEMPROC_DEVICE _PATH Size of the temporary database in megabytes. Default: 80 MB Systemproc database size.
Full path name of the CONTROL-M Sybase database server system procedures database. Default: ${HOME}/sybase/ASE-12_5/data/sybsystemprocs.d at Systemproc database device size (greater or equal to Systemproc database size).
[SETP]/BMC/SYBASE/DATABASE_ SERVER_SYSTEMPROC_DEVICE _SIZE
74
Checking the installation log
Table 21
Parameter

Description Host name of the computer on which the Sybase Database server is installed. Default: Name of the host on the local computer. The port that the computer on which the CONTROL-M Sybase database server is installed uses for external communication. Default: 7102
[SETP]/BMC/SYBASE/REMOTE_ DATABASE_SERVER_HOST [SETP]/BMC/SYBASE/REMOTE_ DATABASE_SERVER_PORT

An installation log is created in the home directory of the CONTROL-M/Server account: <ctmHome>BMCINSTALL/log/<prefix>.<versionNumber>_user.log <ctmHome> is the path of the CONTROL-M/Server user.
Using build_db to recover CONTROL-M/Server after a dedicated Sybase server failure

A dedicated Sybase can be reinstalled without having to reinstall CONTROL-M/Server.
To reinstall Sybase and recover the full CONTROL-M/Server data 1 Ensure that CONTROL-M/Server and all Sybase server processes are shut down. 2 Uninstall Sybase using the following command:
$HOME/BMCINSTALL/uninstall/sybase_uninstall.sh
3 Reinstall the dedicated Sybase server from the CD supplied by BMC Software. 4 Run the following utility to load the CONTROL-M/Server data to the newly
installed Sybase server (You will be required to supply the DBO password). $HOME/ctm_server/scripts/build_db/build_db.sh
Appendix A
75
Using build_db to recover CONTROL-M/Server after a dedicated Sybase server failure
76
Appendix
Installing Oracle on UNIX

This chapter describes how to install an Oracle database on UNIX for use with CONTROL-M/Server. Table 22 describes the ways that CONTROL-M/Server can be installed with an Oracle Database. Installation can be performed using interactive mode or silent mode.
NOTE
Subsequent installation of CONTROL-M/Server must use the same mode (interactive or silent) that was used to install Oracle.
Table 22
Dedicated
Oracle installation types

Explanation Installs full Oracle server and client software, initiates an instance, and inserts a CONTROL-M/Server database schema. The following types of dedicated installation are available:

Installation Type
Without customization Uses default values for all Oracle Database parameters. With customization Allows modification of installation parameters.
Existing
Installs an Oracle client only and inserts a CONTROL-M/Server database schema. The existing database server must be Oracle Full Enterprise Edition.
Existing databases supported are versions 9.2.0.4 and later, 10.1.0.2 and later, and 10.2.0.1 and later. The Oracle client supported for all these databases is version 10.1.0. Before beginning, ensure you have prepared everything necessary for the installation as described in Chapter 2, Planning for CONTROL-M/Server If you are migrating from an earlier version of CONTROL-M/Server, see the CONTROL-M/Server Migration Guide.
Appendix B Installing Oracle on UNIX 77
Preparing for installation
Preparing for installation

Table 23
1 2 3 4 5 6
Installation steps
Step Instruction
Create the UNIX account. Perform Copying the Oracle CDs on page 78. Before starting the installation process, ensure that no processes are running in the background on the CONTROL-M/Server account. Perform Preparing the installer CD on page 79. Perform Running the Oracle pre-installation script on page 79. Oracle Server Perform the Installing a dedicated database server on page 80 to install the full Oracle server and client software. 7 Oracle Client + tablespace Perform the Installing on an existing database server on page 81 to install a CONTROL-M Oracle database client on the local computer and a CONTROL-M/Server tablespace on the Oracle database server.
Perform the Performing post-installation cleanup on page 85.
Copying the Oracle CDs

The software CDs must be copied to the local user account. Select the correct Oracle installation CDs for the UNIX platform and database components required as listed in the version Release Notes. Copy the Oracle CDs using the copycd.ksh utility
1 Log in as the root user. 2 Download the copycd.ksh utility from the following BMC Software ftp site:
ftp://ftp.bmc.com/pub/control-m/opensystem/PANFT.6.3.01.001/
3 Use the following command to create a new temporary directory:

mkdir <oracleTempDirectory>
4 For each CONTROL-M Oracle software CD run the copycd.ksh utility as follows:
copycd.ksh <sourceDirectory> <targetDirectory> <sourceDirectory> is the path to the CD drive. <targetDirectory> is the directory on the local account.
5 Unmount and remove the last CD from the CD-ROM drive.

Preparing the installer CD
If the copycd.ksh utility is not available you can copy the CDs using the following procedure:
1 Log in as the root user. 2 Use the following command to create a new temporary directory:
mkdir <oracleTempDirectory>
3 Do the following for each CONTROL-M Oracle software CD: A Insert the CD in the CD-ROM drive. B Mount the CD-ROM drive. C Use the following command to copy the contents of each Oracle CD to the new
directory: cp -R <cdPath>/* <oracleTempDirectory> The <cdPath> variable is the directory on which you mounted the installation CD.
D Unmount and remove the CD from the CD-ROM drive.
Preparing the installer CD

1 Insert the CONTROL-M Database Component installer for UNIX based on Oracle
10.1.0.3 CD in the CD-ROM drive.
2 Mount the drive.
Running the Oracle pre-installation script

This script determines the database software (server or client) to be installed and sets the required defaults.
1 Log in to the root user and navigate to the CONTROL-M/Server user home
directory. Ensure that no processes are running in the background on the CONTROL-M/Server account.
Appendix B
79
2 Enter the following command:

<cdPath>/orapreinst.sh The <cdPath> variable is the directory on which you mounted the installation CD.
3 Follow the directions on the screen. 4 Log off the root account.

This process installs a CONTROL-M Oracle database server on the local computer. The CONTROL-M Oracle database server can be installed on a raw partition or on a regular file system. If you want to use raw partitions for the CONTROL-M/Server database devices, 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. Oracle Database log files must not be placed on a raw partition. Consult your system administrator for more information about raw partitions. Use the following procedure to perform the installation:
1 Prepare the parameter information you need before beginning the installation.
Parameters are explained in Table 24, Oracle Database UNIX installation parameters on page 88. For information about the path to the Oracle installation CDs, see Copying the Oracle CDs on page 78.
2 Log in to the CONTROL-M/Server account. 3 Set the DISPLAY environment variable to the value <hostName>:0.0. See Operating
<hostName> is the name (or the IP address) of the computer from which the installation is being performed. At this time you should do the following:
A Run the xhost command to ensure that your computer can be accessed using a
UNIX emulation.
B Run a small application (such as xclock) to ensure that the specified display
settings are working.
80
4 Use the following command to run the installation script:

<cdPath>/inst_oracle
5 Select one of the following installation choices. If you are using raw partitions or
working with a UTF8 character set, you must choose Custom:
Default Installs a CONTROL-M Oracle database server with default database parameters on the local computer. A CONTROL-M/Server tablespace and user are also installed. Custom Installs a CONTROL-M Oracle database server on the local computer and prompts you to specify your own database parameters. A CONTROL-M/Server tablespace and user are also installed.
6 Follow the instructions on the screen, filling in parameter values as necessary. 7 After the Installation completed successfully message is displayed, continue with
Performing post-installation cleanup on page 85.

This process installs a CONTROL-M Oracle database client on the local computer and installs a CONTROL-M/Server tablespace on an existing Oracle database server. The location, port number, and name of the existing Oracle database server, as well as the name and password of the system administrator, must be specified in the installation parameters.
Verification of existing Oracle components

1 Obtain the following for the new CONTROL-M/Server database from your
database administrator:
database name system administrator login name system administrator password server name
2 Using the operating system account that installed the Oracle server, log in to the
computer where the Oracle database server is installed.
Appendix B
81
Verification of existing Oracle components
NOTE
The existing Oracle database instance must be running during installation and whenever CONTROL-M/Server is operating.
3 Obtain the correct dbaUser and dbaPassword from your database administrator
and use the following command to verify that Oracle is running: sqlplus <dbaUser>/<dbaPassword> <dbaUser> is the name of the DBA account (Oracle default: system). <dbaPassword> is the DBA account password (Oracle default: manager).
4 Verify that this database is served by an Oracle Listener port running on the same
computer on which the database is installed.
5 A unique tablespace name and a tablespace owner name (DBO) must be specified
for each CONTROL-M database. To display a list of existing tablespace names:
A Log in as the database administrator. B Type the following SQL instruction:

SQL> select tablespace_name from dba_tablespaces; To display a list of existing usernames:
A Log in as the database administrator. B Type the following SQL instruction:

SQL> select username from dba_users;
NOTE
When creating more than one CONTROL-M installation using the same Oracle database server, you must specify a unique tablespace name and tablespace owner name for each installation.
82

Parameters are explained in Table 24, Oracle Database UNIX installation parameters on page 88.
2 Log in to the CONTROL-M/Server account. 3 Set the environment variable DISPLAY to value <hostName>:0.0. See Operating
<hostName> is the name (or the IP address) of the computer from which the installation is being performed. At this time you should do the following:
A Run the xhost command to ensure that your computer can be accessed using a
UNIX emulation.
B Run a small application (such as xclock) to ensure that the specified display
settings are working.
4 Use the following command to run the installation script.

5 Select Existing installation. 6 Follow the instructions on the screen, filling in parameter values as necessary. 7 After the Installation completed successfully message is displayed, continue with

Uninstalling and cleanup is necessary before re-running the existing Oracle installation. You must first remove the database components that were created by the failed installation.
To uninstall and clean up the installation 1 Run the uninstall program (see Uninstalling a CONTROL-M Oracle database
server on page 113).
2 Log in to the Oracle database server account as the database administrator.

Appendix B Installing Oracle on UNIX 83
Installing a CONTROL-M/Server tablespace using an existing Oracle client
3 If a username was already created, use the drop user <userName> cascade;
command to delete it.
4 Depending on where and how the installation failed, a tablespace and a data file
may have been created. Use the following commands to check if a <tablespaceName> (tablespace name) and <datafileName> (data file name) were created for the failed installation. col name for a50 select t.name,d.name from v$tablespace t,v$datafile d where d.ts# =t.ts# ;
5 If a tablespace was created: A Use the drop tablespace <tablespaceName> command to delete the tablespace. B Delete that data file associated with the dropped tablespace. WARNING
Do not delete raw partitions.
Installing a CONTROL-M/Server tablespace using an existing Oracle client

This process uses an existing Oracle version 10.1.0 database software to install a CONTROL-M/Server tablespace on an Oracle database server. At this time, CONTROL-M/Server version 6.3.01 supports Oracle database server versions 9.2.0.4 and later, 10.1.0.2 and later, and 10.2.0.1 and later. The Oracle client supported for these database servers must be version 10.1.0.
WARNING
This is an advanced level option. It should be used with care and in consultation with BMC Software qualified DBA personnel.
The location and name of the existing Oracle installation, the system administrator name, and the system administrator password must be specified in the installation parameters.
84
Performing post-installation cleanup
Parameters are explained in Table 24, Oracle Database UNIX installation parameters on page 88.
2 Log in to the CONTROL-M/Server account. 3 Set the environment variable USE_EXISTING_ORACLE to value Y. See
Operating system levels and patches on page 19 for your UNIX environment.
4 Use the following command to run the installation script.

5 Select Existing installation. 6 Select an existing Oracle 10.1.0 installation. If a list of Oracle installation locations is
not available, or if a list is available and you select the Enter another value option, you are prompted to type a path to an Oracle installation.
7 Select a network connection alias. If a list of connection aliases is not available, or if

a list is available and you select the Enter another value option, you are prompted to type a connection alias.
8 Follow the instructions on the screen, filling in parameter values as necessary. 9 After the Installation completed successfully message is displayed, continue with
Performing post-installation cleanup

The following procedure removes the temporary directories and files created by an Oracle database server setup.
1 Log in as the root user. 2 Enter the following command:

<cdPath>/orapostinst.sh <cdPath> is the directory on which the CONTROL-M Oracle database component CD was mounted. The orapostinst script is located on the CONTROL-M Database Component installer for UNIX based on Oracle 10.1.0.3 CD, not in the files copied from the Oracle CDs.
Appendix B
85
3 If necessary, confirm the removal of files by entering y and pressing <enter>. 4 Log off the root user.

Silent installation is used to install Oracle from a batch file. The following stages are involved:
Preparing the parameters file This is accomplished by running a silent installation preparatory procedure from the installation CD. The preparatory procedure behaves like the interactive installation procedure and prompts you to enter the same information. However, no installation is performed. Instead, the information you enter is stored in a file.
Using the prepared parameters file When the prepared parameters file is used with the silent installation program, Oracle is installed using the parameters you specified in the previous step.
To prepare the silent installation batch file 1 Perform Oracle preinstallation as described in Running the Oracle pre-installation
script on page 79.
2 Select one of the installation types described in this chapter and perform the steps
required until reaching the inst_oracle command. Now run this command with the u flag. For example: <cdPath>/inst_oracle u The u flag prevents installation from being executed, and causes a parameter file to be generated instead. The following parameter file is generated in the $HOME/tmp directory:
10103_Install_def.PARAMS
3 Continue to the end of the installation screens. 4 Using any text editor, open the parameters file and add the following two lines:
APP_PASS=ctmspassword4dbo SYSTEM_PASSWD=<databaseAdministratorPassword>
86
<temporaryPassword> is the temporary password given to the dbo during the database installation. <databaseAdministratorPassword> is the dba password that will be set. For an existing installation, consult your database administrator.
5 Copy the parameter file to the computers on which you want to preform the silent
installation.
To install silently
The silent installation script performs all necessary pre-installation and postinstallation activities as well as the installation itself. A system requirement check should be run before beginning the installation.
NOTE
If the paths to $HOME in the parameter file are different from the paths on the computer on which you prepared the silent installation, you may need to edit these parameters in the parameter file.
1 Confirm you have the necessary system requirements and run the check_req.sh
script as specified in Operating system levels and patches on page 19.
2 Log in as root to the installation directory and run the following script:
<cdPath>silent_install_10.sh ora_home_dir=<oracleHome> paramfile=<parametersFileLocation> display=<DISPLAY>
<oracleHome> is the path to the UNIX account where Oracle will be installed. <parametersFileLocation> is the path and name of the parameters file. <DISPLAY> is the value of the DISPLAY environment variable required for an xterm display. For example: 172.16.1.1:0.0 Installation progress is displayed on the monitor. Upon completion, the Installation completed successfully message is displayed.
WARNING
No checks are performed on the contents of the parameter files. If any parameter is incorrect, the installation will fail.
Appendix B
87
Setting Oracle installation parameters
The results of the pre-installation, installation, and post-installation procedures are recorded in the following logs:
$HOME/silent_dir/orapreinst*.log $HOME/silent_dir/orapostinst*.log

Table 24 Oracle Database UNIX installation parameters (Part 1 of 4)
Description Size for the data files component: small (150 MB), medium (250 MB), or large (500 MB). Default: depends on the size (small, medium, or large) chosen for the database. Database log01 file name (full path) The default path to the first database log file is based on the Oracle database instance name. For example: When the instance name is ctrlm, the default path is: $HOME/oracle/oradata/ctrlm/ctmuserlog01.dbf. Database log02 file name (full path) The default path to the second database log file is based on the Oracle database instance name. For example: When the instance name is ctrlm, the default path is: $HOME/oracle/oradata/ctrlm/ctmuserlog02.dbf. Database redo log file size Each Oracle database has two redo log files. These files are used to record all (2 files) committed changes that are applied to the database, so that this information is available in case of a media failure. Size for each redo log file. Choose small (50 MB), medium (100 MB), or large (200 MB). Default: depends on the size (small, medium, or large) chosen for the database. Database rollback segments tablespace file name (full path) The default path to the rollback segments tablespace file is based on the Oracle database instance name. For example: When the instance name is ctrlm, the default path is: $HOME/oracle/oradata/ctrlm/ctmuserrbs.dbf. Database rollback segments tablespace size Default: 320 MB. Parameter or Prompt Data tablespace size
88
Table 24
Oracle Database UNIX installation parameters (Part 2 of 4)

Description Enter the database size: small, medium or large. Default: medium. Database sizes: small 990 MB, medium 1.410 GB, large 2.13 GB. If you use raw partitions, for each tablespace listed below, the size of each raw partition must be equal to the tablespace size plus 4 MB. System Tablespace 350 MB RBS Tablespace 320 MB Temporary Tablespace 200 MB Data Tablespace 500 MB SYSAUX Tablespace 360 MB Log Files 400 MB (two log files of 200 MB each)
Parameter or Prompt Database Size
Database system tablespace file name
The default path to the system tablespace file is based on the Oracle database instance name. For example: When the instance name is ctrlm, the default path is: $HOME/oracle/oradata/ctrlm/ctmusersystem01.dbf.
Database system tablespace size Database temporary tablespace file name (full path)
small (250 MB), medium (300 MB), or large (350 MB). Default: depends on the size (small, medium, or large) chosen for the database. The default path to the temporary tablespace file is based on the Oracle database instance name. For example: When the instance name is ctrlm, the default path is: $HOME/oracle/oradata/ctrlm/ctmusertemp01.dbf.
Database temporary tablespace file size Ctm data file name
small (50 MB), medium (100 MB), or large (200 MB). Default: depends on the size (small, medium, or large) chosen for the database. The default path to the data tablespace file is based on the Oracle database instance name. Default: $HOME/oracle/oradata/ctrlm/ctmuserdata01.dbf. For installation using an existing Oracle Database server, this parameter indicates the full path and file name 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 file name must not be the name of an existing file. This file will be created during installation of the database.
Ctm 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 (name should start with a letter followed by 1-24 alphanumeric characters). Default: ctmuser.
Appendix B
89
Table 24

Description Name of the CONTROL-M/Server database user to be created. This is the user used to log in to CONTROL-M/Server. The name must begin with a letter (A-Z, a-z) followed by up to 7 alphanumeric characters (includes underscores). Default: ctmuser.
Parameter or Prompt Ctm Database user
Oracle CDs path
Specify the full path name you used to copy the Oracle CDs to the local drive: <oracleHome>. Note: Do not specify Disk1 after the full path name (as was required in previous versions).
Oracle Database Instance Name
Instance name of the CONTROL-M/Server database.Default: ctrlm. How do I find this value on an existing Oracle server? Search for the listener.ora file in a location similar to the following: <oracleHome/oracle/product/10.1.0/network/admin/ <oracleHome> is the folder in which the Oracle server is installed. 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: The Oracle database instance name should not exceed 8 characters. The Oracle database instance name cannot begin with a numeral. The value "_" is not allowed for the SID_NAME For installation using an existing Oracle database server, this parameter indicates the instance name of the existing database. Get this value from the DBA.
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>. The <portNumber> variable is the number of the required 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).
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.
90
Table 24

Description
Parameter or Prompt
Oracle SYSTEM password Password for the Oracle SYSTEM account. Length: should start with a letter followed by 3-29 alphanumeric characters. Default: manager. Oracle SYSTEM User User name for the Oracle SYSTEM account. Default: SYSTEM. Note: This parameter is displayed only for an Existing Installation. Unicode (Y/N) Character set for the database: Default: N - Latin1 (WE8ISO8859P1), Y - UTF8. User password Password for the CONTROL-M/Server database user (4 to 30 characters, alphanumeric). The characters are not displayed for security reasons. Note: This password can be changed at a later time. For more information, see, Maintaining CONTROL-M/Server, in the CONTROL-M/Enterprise Manager Administrator Guide.
NOTE
Even if you do not modify any other parameters, you must modify the parameters relating to the existing database that do not have default values.

After installing Oracle database components, the following installation log directory is created in the home directory of the CONTROL-M/Server account:
<ctmHomeDirectory>/log <ctmHomeDirectory> is the path of the CONTROL-M/Server user.
The main installation log file is: trace.log
Appendix B
91
92
Appendix
Mounting CDs on UNIX computers

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.
AIX
To mount the CD: mount -rv cdrfs /dev/cd0 <cdPath> You may need to replace cd0 with cd1.
Use the following command to unmount the CD: umount <cdPath>
HP-UX
Use the following command to display device paths on your computer: /usr/sbin/ioscan -fnkC disk 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.
To prepare to mount an Oracle CD: A. Search for the /etc/pfs_fstab file. If this file does not exist, create it and continue with step B.. B. Add the following line to the /etc/pfs_fstab file: <cdromMark> <cdPath> pfs-rrip xlat=UNIX 1 0
Appendix C
93
<cdromMark> is the path to the CD-ROM device. This is the value obtained using the ioscan command (above). <cdPath> is the CD-ROM logical name. If there is already a line that contains the <cdPath> in the pfs_fstab file, but that line is not correct, delete it before adding the new line described above.
EXAMPLE
If <cdromMark> is /dev/dsk/c0t0d0 and <cdPath> is /cdrom, enter: /dev/dsk/c0t0d0 /cdrom pfs-rrip xlat=UNIX 1 0
To mount the Oracle CD: nohup /usr/sbin/pfs_mountd & nohup /usr/sbin/pfsd & /usr/sbin/pfs_mount <cdPath> 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 <cdPath>
To mount a CONTROL-M installation CD: /usr/sbin/mount -o cdcase <cdromMark> <cdPath>
EXAMPLE
If <cdromMark> is /dev/dsk/c0t0d0 and <cdPath> is /cdrom, enter: mount -o cdcase /dev/dsk/c0t0d0 /cdrom
To unmount the Oracle CD: /usr/sbin/pfs_umount <cdPath>
To unmount a CONTROL-M installation CD: /usr/sbin/umount <cdPath>
94
Solaris
The CD mount procedure is handled automatically by the Solaris operating system.
To unmount a CD: eject
Linux
If the CD is not mounted automatically, enter the following command: mount -t iso9660 -o map=off /dev/cdrom /cdrom /dev/cdrom represents the CD-ROM device on the agent's computer and /cdrom represents the mount directory.
Appendix C
95
96
Appendix
Checking and modifying UNIX parameters

D
This appendix describes how to check and modify CONTROL-M/Server memory and kernel system parameters.
Checking memory
The following table lists instructions for checking available memory on various UNIX platforms. Table 25
AIX
Checking available memory

How to check available RAM Use the following command to determine the amount of available memory in Kilobytes: lsattr -El mem0 Divide the result by 1024 to get the number of MB.
UNIX System
HP-UX
Log in as the root user and use the following command to check how much RAM is supplied with your computer: echo phys_mem_pages/D | adb /stand/vmunix /dev/kmem Divide the result by 256 to get the number of MB.
Solaris Linux
prtconf -v |grep Memory free
Appendix D
97
Modifying system parameters
Modifying system parameters

Several UNIX system (kernel) parameters must be altered before installing CONTROL-M/Server.
All platforms
The parameters values shown in Table 26 must be added to the values specified for them in any of the other tables. If higher values for these parameters have already been specified for the database server, the higher values should remain. Table 26
Parameter semmni semmns semmnu
Kernel parameters additional values

Additional values add 20 + the number of Agents and remote hosts that will be connected to CONTROL-M/Server + the number Agents with configuration definitions that differ from the default. For Solaris 8 and 9 (not Solaris 10) add 100 + 6 times the number agents connected to the server + the number utilities running simultaneously.
Table 27
Parameter semmnu
Kernel parameters values for all platforms

Value (NPROC - 4)
HP-UX
1 Log in as the root user. 2 Enter the following command to ensure that you are using an appropriate display
setting: setenv DISPLAY <hostName>:0.0
3 Type sam, select Kernel Configuration, and navigate to Configurable Parameters. 4 To change a parameter value: A Navigate to Modify Configurable Parameters in the Action Menu. B Enter the desired value in the Formula/Value field. If the default value is more
than required, do not change it.
98
HP-UX
Table 28
Parameter
Kernel parameters HP-UX with Sybase

Value 512. This value is appropriate for a CONTROL-M/Server installation with up to 50 CONTROL-M definitions, 80 concurrently open ViewPoints, and 30 concurrent users. Note: If your data center requires a larger configuration, contact BMC Software Customer Support for the correct value of this parameter. For more information about CONTROL-M definitions and ViewPoints, see the CONTROL-M/Enterprise Manager User Guide.
max_thread_proc
Table 29
Parameter
Kernel parameters HP-UX with Oracle (Part 1 of 2)

Value (NPROC*8) Eight times the value specified for the NPROC parameter. 1,073,741,824 2,147,483,648 134,217,728 bytes 1,073,741,824 16384 512. This value is appropriate for a CONTROL-M/Server installation with up to 50 CONTROL-M definitions, 80 concurrently open ViewPoints, and 30 concurrent users. Note: If your data center requires a larger configuration, contact BMC Software Customer Support for the correct value of this parameter. For more information about CONTROL-M definitions and ViewPoints, see the CONTROL-M/Enterprise Manager User Guide. ((NPROC*9)/10) (MSGTQL+2) NPROC 32,767 NPROC (NKTHREAD+16) ((8*NPROC+2048)+VX_NCSIZE) (15*NPROC+2048) 4096 (8*NPROC+2048) (((NPROC*7)/4)+16) 4096 (SEMMNI+2) 4096 (SEMMNI*2)
ksi_alloc_max maxdsiz maxdsiz_64bit maxssiz maxssiz_64bit maxswapchunks max_thread_proc
maxuprc msgmap msgmni msgseg msgtql ncallout ncsize nfile nflocks ninode nkthread nproc semmap semmni semmns
Appendix D
99
AIX
Table 29
Parameter semmnu semvmx shmmax
Kernel parameters HP-UX with Oracle (Part 2 of 2)

Value (NPROC - 4) 32,768 Half the amount of RAM (in bytes) on this computer. For information about determining the amount of RAM on your computer, see Checking memory on page 97. 1 512 32 64
shmmin shmmni shmseg vps_ceiling
AIX
Use the following steps to activate the RS/6000 Asynchronous I/O option:
1 Log in as the root user. 2 Enter the following command to ensure that you are using an appropriate display
setting: setenv DISPLAY <hostName>:0.0
3 Enter the following command:

smit aio
4 Select the Change/Show Characteristics of Asychronous I/O option.

Enter the parameter values shown in Table 30. Table 30
Parameter Minimum number of servers Maximum number of servers Maximum number of requests I/O Server priority ASYNC I/O state to be configured at system start State of fast path
Asynchronous I/O parameters AIX

Value 1 10 4096 39 Available Enabled
100
Solaris
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.
5 Click OK and wait for the operation to complete. 6 Click Done. Control returns to the main Asynchronous I/O menu. 7 Select the Configure Defined Asynchronous I/O option. 8 Press <F12> to exit from smit. 9 Log out. 10 Exit the shell prompt. NOTE
If State to be configured at system start is Available, the AIX system need not be rebooted at the end of the procedure.
Solaris
1 Log in as a root user. 2 Open the operating system configuration file /etc/system. 3 To set a kernel parameter, use the following command:
set <moduleName>:<moduleAbbreviation>info_<parameterName>=<value>
EXAMPLE
To set the shmseg parameter to 36, enter the following command: set shmsys:shminfo_shmseg=36
Appendix D
101
Linux
Table 31
Parameter shmmax
Kernel parameters Solaris with Sybase

Module name shmsys Module abbreviation Minimum value shm amount of available memory on this computer 10 32,768
shmseg semvmx
shmsys semsys
shm sem
Table 32
Parameter shmmax shmmin shmmni shmseg semmns
Kernel parameters Solaris with Oracle

Module name shmsys shmsys shmsys shmsys semsys Module abbreviation Minimum value shm shm shm shm sem 4,294,967,295 1 100 10 Twice the total number of Oracle processes (minimum: 1024). 100 260 100 32,768
semmni semmsl semopm semvmx
semsys semsys semsys semsys
sem sem sem sem
Linux
1 Log in as the root user. 2 The kernel parameters shown in Table 33 should be set to values greater than or
equal to those displayed in the table. Instructions on how to display the current parameter values are shown in Table 34. Table 33
Parameter semmsl semmns semopm semmni semvmx
Kernel parameters Linux with Sybase and Oracle (Part 1 of 2)

Value 250 32000 100 128 default set by system
102
Linux
Table 33
Parameter shmall shmmax shmmni file-max
Kernel parameters Linux with Sybase and Oracle (Part 2 of 2)

Value 2097152 half the size of physical memory 4096 65536 32768 - 61000
ip_local_port_range
Table 34
Parameter
Displaying kernel parameter values Linux with Sybase and Oracle

Command to display the parameter values
semmsl, semmns, semopm, /sbin/sysctl -a | grep sem semmni shmall, shmmax, shmmni file-max ip_local_port_range /sbin/sysctl -a | grep shm /sbin/sysctl -a | grep file-max /sbin/sysctl -a | grep ip_local_port_range
Changing kernel parameter values

Using a text editor, add the following lines to the /etc/sysctl.conf file (you will need to create the file if it does not already exist): kernel.shmall = 2097152 kernel.shmmax = 2147483648 kernel.shmmni = 4096 kernel.sem = 250 32000 100 128 fs.file-max = 65536 net.ipv4.ip_local_port_range = 32768 61000
NOTE
kernel.sem assigns values to four semaphore parameters in the following order: semmsl, semmns, semopm, semmni. All four values must be specified.
The values specified in the /etc/sysctl.conf file take effect after the next reboot. Alternatively, you can issue the following command to have the values in the /etc/sysctl.conf file take effect immediately without rebooting: /sbin/sysctl -p
Appendix D
103
Linux
104
Appendix
CONTROL-M/Server database size

This appendix describes how to estimate the size of the CONTROL-M/Server database. 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.
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.
Appendix E
105
Job definitions
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 35 lists typical job items and the disk space required for each item. Table 35
Job item Basic job definition Do action AutoEdit variable Control resource Quantitative resource Prerequisite condition
Job items and Disk space requirements

Disk space 2000 bytes 650 bytes 350 bytes 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. Table 36 Job definition calculations
Calculation 2,000 bytes 3 * 650 bytes 1* 350 bytes 3 *180 bytes 1 * 200 bytes 1 * 300 bytes Result 2,000 1,950 350 540 200 300 5,340 Bytes
Job Definition Item Basic job definition Do Actions AutoEdit Variable Control Resources Quantitative Resource Condition size Total:
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
106
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.
The size of the Active Jobs file is obtained by adding the size required for each of these components.
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.) 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. 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. 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.) Add the results obtained in steps 1 through 4 to obtain the number of bytes required for the Active Jobs file. To obtain the total including the database index: for Sybase and MSSQL databases, multiply the sum by 2.2 for Oracle databases, multiply the sum by 1.7
Appendix E
107
Example
This example estimates the size of a CONTROL-M database. Table 37
Job option Number of history days Number of executions history Maximum number of active jobs Maximum job executions per day Total number of jobs defined 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 Total size of Active Job file in MB Total database size in MB
Active jobs file calculations

Value 2 (default) 21 (default) 100 1,000 100 2 1 3 1 1 0.51 11.63 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 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 D, the number of days to save each log, is 2 (the default) and a maximum of 1,000 jobs are executed each day.
108
3. Final Execution Status E * maximum jobs in the system * 700 21 * 100 * 700 = 1,470,000 bytes 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 38
Parameter Number of days to keep each job execution log
Active jobs file parameters

Description 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 Each record indicates the final status of an executed job. The size of each final status record is 700 bytes. Default: 21 Maximum length of the list of jobs that can be run during a day. Maximum number of job executions that can be performed each day. 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. 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. Specify the number of Control resources for the average job. Specify the number of Quantitative resources (such as backup tapes or printers) for the average job. Specify the number of prerequisite conditions for the average job.
Number of final execution status records to keep for each job
Max active jobs per day Max job executions per day Number of DO Actions
Number of AutoEdit variables
Number of Control resources Number of Quantitative resources Number of In and Out conditions
Appendix E
109
Database memory requirements
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. BMC Software recommends that you allocate twice the space that would be required for the database on your busiest day 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.
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. BMC Software recommends 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. BMC Software recommends 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. Ensure that memory calculations are performed in accordance with the actual physical RAM installed on the target computer.
110
Appendix
Uninstalling CONTROL-M/Server and database servers

F
When uninstalling CONTROL-M/Server and related components from UNIX or Windows, CONTROL-M/Server must be uninstalled first, before uninstalling the database server.
Uninstalling CONTROL-M/Server from UNIX

Use the following procedure to completely remove all CONTROL-M/Server components from UNIX:
1 Log in to the CONTROL-M/Server account. 2 Use the following command to run the uninstallation script from the home
directory: ./BMCINSTALL/uninstall/ctms_uninstall.sh The uninstall procedure checks that no CONTROL-M/Server process is active before beginning the uninstallation process.
3 After CONTROL-M/Server has been uninstalled, you must delete its definition
from the CONTROL-M Configuration Manager.
Appendix F
Uninstalling CONTROL-M/Server and database servers
111
Uninstalling CONTROL-M/Server from Windows
Uninstalling CONTROL-M/Server from Windows

Use the following procedure to completely remove all CONTROL-M/Server components from Windows:
1 Use the CONTROL-M Configuration Manager to shut down all

CONTROL-M/Server components.
2 Select Start => Settings => Control Panel=> Add/Remove Programs. 3 Select CONTROL-M/Server from the "Currently installed programs" list. If
multiple instances are installed, each instance is listed separately in the Add/Remove Programs window.
4 Click Remove or Add/Remove to begin the uninstall procedure.
Uninstalling the NutCRACKER service

Uninstallation of the CONTROL-M/Server does not remove the third party NuTCRACKER Service which remains running even after a system reboot. This could prevent a future side-by-side installation using a previous version of CONTROL-M/Server. To avoid this problem, run the toolkit.msi file from the CONTROL-M/Server installation CD, and select removal of the NutCRACKER product.
Uninstalling a CONTROL-M Sybase database server

WARNING
Ensure that the database server is not shared with other CONTROL-M components (for example, CONTROL-M/Server) before uninstalling.
1 Shut down CONTROL-M/Server, CONTROL-M Configuration Agent, and the

database server using the following commands: Shut_ctm shut_ca
Uninstalling a CONTROL-M Oracle database server
shutdb
2 Log in to the CONTROL-M/Server account 3 Use the following command to run the uninstallation script:
./BMCINSTALL/uninstall/sybase_uninstall.sh
4 This script uninstalls the following components on the local computer:
The dedicated (default and custom installations) Sybase database server component including the CONTROL-M/Server database devices Sybase client components
If you re-install Sybase, you can re-associate CONTROL-M/Server with the new Sybase installation using the build_db utility (see the CONTROL-M/Server Administrator Guide).
NOTE
A CONTROL-M/Server database installed on an existing Sybase database server (existing installation) cannot be removed with this script.

WARNING
Ensure that the database server is not shared with other CONTROL-M components (for example, CONTROL-M/Server) before uninstalling.
1 CONTROL-M/Server must be uninstalled first before uninstalling the database

server (see Uninstalling CONTROL-M/Server from UNIX).
2 Log in to the CONTROL-M/Server account. 3 Use the following command to run the uninstallation script:
$HOME/BMCINSTALL/uninstall/uninstall_oracle.sh
4 This program uninstalls all installed Oracle server or Oracle client components in
the specified <oracleHome> folder.
Appendix F Uninstalling CONTROL-M/Server and database servers 113
NOTE
A CONTROL-M/Server database installed on an existing Sybase database server (existing installation) cannot be removed with this script.
114
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
Numerics
10103_Install_def.PARAMS file 86 authorization for installation 21 Authorized CONTROL-M/ Server Hosts CTM/Agent for Windows 53
A
administrator group name Oracle 21 AG_AGCMN DATA_VAL CTM/Agent for Windows (silent) 57 AG_AGENT_TIMEOUT CTM/Agent for Windows (silent) 57 AG_ATCMN DATA_VAL CTM/Agent for Windows (silent) 56 AG_CTMPERM HOSTS_VAL CTM/Agent for Windows (silent) 56 AG_CTMSHOST _VAL CTM/Agent for Windows (silent) 56 AG_DFTPRT_VAL CTM/Agent for Windows (silent) 57 AG_DOMAIN_VAL CTM/Agent for Windows (silent) 57 AG_GON_AS_ USER_VAL CTM/Agent for Windows (silent) 57 AG_JO_ STATISTICS_ VAL CTM/Agent for Windows (silent) 57 AG_SRV_PASS CTM/Agent for Windows (silent) 57 AG_SRV_USER CTM/Agent for Windows (silent) 57 Agent Name parameter CTM/Agent for Windows 53 Agent-to-Server Port Number CTM/Agent for Windows 53 CTM/Server for Windows 29, 37, 43 AIX boot procedure 31 how to check available RAM 97 minimum requirements 18 setting asynchronous I/O 100 architecture CONTROL-M components 11 Asynchronous I/O AIX parameters 100 authorization CONTROL-M/Server user 33
B
BMC Software, contacting 2 boot procedure AIX 31 CONTROL-M/Server 31
C
character support, CJK 17 check_req.sh script 19 checking operating system requirements 19 Chinese language considerations 17 CJK character support 17 cleanup failed Oracle installation on UNIX 83 failed Sybase installation 68 Oracle on UNIX post-installation 85 client installation for Sybase 68 cluster configuration CTM/Agent for Windows 35, 54 Cluster Management parameter CTM/Agent for Windows 35, 54 commands checking available memory 97 drop database (Sybase) 68 isql 66 ls filename 66 sp_configure 67 sp_dropdevice 68 sp_helpdb 68 compatibility information 17, 21 compatibility information, online 39, 49 configuration AIX 100 of database servers 16 Configure Defined Asynchronous I/O option 101 control modules operating system 52 CONTROL-M
Index
115
components 11 uninstalling Oracle server 113 CONTROL-M Option for Oracle with CTM/Agent for UNIX 47 CONTROL-M/Agent installing on UNIX 39 installing on Windows 49 multiple agents 51 Windows parameters 53 CONTROL-M/Desktop job editing form 54 CONTROL-M/Server account on UNIX 21 boot procedure (UNIX) 31 job editing form 54 UNIX requirements 18 Windows requirements 22 CONTROL-M/Server account UNIX 20 CONTROL-M/Server data file name parameter for Oracle 89 CONTROL-M/Server Data tablespace name parameter for Oracle 89 CONTROL-M/Server Database user parameter for Oracle 90 CONTROL-M/Server Host Name in CTM/Agent configuration 43 CONTROL-M/Server Port. CTM/Agent parameter 43 coredumpsize parameter 21 ctm_etcservices command 30 custom installation raw partitions 65 customer support 3 Database temporary tablespace file size parameter for Oracle 89 database temporary tablespace parameters for Oracle 89 databases installing Oracle on UNIX 77 installing Sybase on UNIX 63 server configurations 16 datasize parameter 21 DB_SERVER_HOSTNAME parameter. CTM/Server for Windows 36 dedicated installation Oracle 77 Sybase 63 default printer CTM/Agent for Windows (silent) 57 defaults Default ctm agent 51 descriptors parameter for UNIX account 21 destination folder CTM/Agent for Windows 53 device file check command 66 disk space requirements. See requirements diskspace CONTROL-M/Agent for UNIX 39, 50 DNS 29, 37 domain controller CTM/Agent for Windows (silent) 57 drop database command 68 Dual IP addresses 29, 37 dump size limit parameter 21
E
East Asian language considerations 17 echo command 97 environment variables for Windows 22 etc/services file port numbers 30
D
Data Device Full Path File Name parameter for Sybase 71 Data Device Size parameter for Sybase 71 data tablespace file name parameter for Oracle 89 data tablespace size for Oracle 89 data tablespace size parameter for Oracle 88 database instance name parameter for Oracle 90 Database log01 file name parameter for Oracle 88 Database log02 file name parameter for Oracle 88 Database Name parameter for Sybase 71 Database Owner Login parameter for Sybase 72 Database Owner Password parameter for Sybase 72 Database redo log file size parameter for Oracle 88 Database rollback parameters for Oracle 88 Database Server Administrator Password parameter for Sybase 72 Database Size (menu) parameter for UNIX 89 Database Size parameter for Sybase 72 Database system tablespace file name parameter for Oracle 89 Database system tablespace size parameter for Oracle 89
F
filename data tablespace 89 database system tablespace 89
H
HOME directory requirements 20 host names Oracle server 90 HP Itanium requirements 64 HP-UX how to check available RAM 97
116
minimum requirements 18 locale settings 22 locks, for Sybase server 67 Log Device Full Path File Name parameter for Sybase 72 Log Device Size parameter for Sybase 72 log files location of Oracle 91 Oracle 80 path for Oracle 88 redo logs for Oracle 88 silent installation 88 size of redo 88 Sybase end user progress 73 Sybase trace 73 trace.log for Oracle 91 LOG_PHYSICAL_DEVICE_FULLPATH_FILE_NAME parameter. CTM/Server for Windows 36 ls filename command 66 lsattr command 97
I
importing application forms 54 installation log Oracle 91 Sybase components 75 INSTALLDIR parameter CTM/Agent silent installation 56 installing Administrator privileges 21 CONTROL-M/Agent on Windows 39, 49 required resources 23 Sybase client 68 instance name Oracle on UNIX 90 Internet Explorer, version required 22 IP dual addresses 29, 37 isql command 66
M
Master Device Full Path File Name parameter for Sybase 72 Max Memory parameter for Sybase 67 max_thread_proc parameter HP-UX with Oracle 99 HP-UX with Sybase 99 maxdsiz parameter HP-UX with Oracle 99 maxdsiz_64bit parameter HP-UX with Oracle 99 Maximum number of servers AIX parameter 101 maxssiz parameter HP-UX with Oracle 99 maxssiz_64bit parameter HP-UX with Oracle 99 maxswapchunks parameter HP-UX with Oracle 99 maxuprc parameter HP-UX with Oracle 99 memory CONTROL-M/Server account 21 how to check available RAM 97 maximum for Sybase 67 memoryuse parameter for UNIX 21 messages CTM/Agent for UNIX 43 Microsoft Windows installing CONTROL-M/Agent 39, 49 mirroring 31 Modify Configurable Parameters option Action menu 98 modifying parameter values 98 msgmap parameter
J
Japanese language considerations 17 job editing form CTM/Agent for Windows 54 job output default printer 57
K
kernel parameters Solaris 101 Korean language considerations 17 ksi_alloc_max parameter HP-UX with Oracle 99
L
language settings CJK character support 17 Windows 22 Linux disk space requirement 19 hardware requirement 18 Oracle compatibility issue 16 LISTENER port number 90 Load balancing dual IP addresses 29, 37 Local IP Host Interface Name CTM/Server for Windows 29, 37
Index
117
HP-UX with Oracle 99 msgmni parameter HP-UX with Oracle 99 msgseg parameter HP-UX with Oracle 99 msgtql parameter HP-UX with Oracle 99 MSSQL server configuration 16 requirements 22 multiple agents 51
P
parameter file, 10103_Install_def.PARAMS 86 parameter values modifying 98 parameters CONTROL-M/Agent for Windows 53 CTM/Agent for UNIX 43 CTM/Agent for Windows (silent) 56 Oracle on UNIX 8891 Sybase 7175 passwords Database Owner Password for Sybase 72 Oracle SYSTEM account for UNIX 91 Oracle user for UNIX 91 required for installation 23 Sybase SA_PASSWORD 71 PATH environment variable for Windows 22 port numbers CTM/Agent for Windows 53, 57 multiple CTM agents 51 Oracle LISTENER 90 recording port usage 30 Sybase backup server 72, 73 Sybase server 72, 74 pre_req.tar.Z file 19 Primary CONTROL-M/ Server Host CTM/Agent for Windows 53 privileges CONTROL-M/Server administrator 33 privileges, for installer 21 product support 3 protocol version. after agent upgrade 55, 60 prtconf command 97
N
names multiple agents 51 ncallout parameter HP-UX with Oracle 99 ncsize parameter HP-UX with Oracle 99 nfile parameter HP-UX with Oracle 99 nflocks parameter HP-UX with Oracle 99 NFS mounting the CTM/Agent CD 41 ninode parameter HP-UX with Oracle 99 nkthread parameter HP-UX with Oracle 99 non-English versions of Windows 22 nproc parameter HP-UX with Oracle 99 Number of locks parameter for Sybase 67 Number of User Connections parameter for Sybase 67
O
operating systems requirements. See requirements Oracle administrator group name 21 CDs path parameter for UNIX 90 configuration 16 installation log file 91 installation parameters for UNIX 88 installing on UNIX 77 LISTENER port number 90 log files 80 preinstallation script for UNIX 79 tablespace name check 82 Oracle Database Instance Name parameter for UNIX 90 Oracle Server host name parameter for UNIX 90 Oracle SYSTEM password parameter for UNIX 91 Oracle SYSTEM User parameter for UNIX 91 orapostinst.sh script 85
R
raw partitions preparing for installation 80 size of 89 Sybase guidelines 65 RBS Tablespace, Oracle database size 89 recording port usage 30 redo log, file size 88 regional settings 17, 22 remote CD mount CTM/Agent for UNIX 41 requirements HP Itanium 64 installation resources 23 UNIX 18 Windows 22 resources required for installation 23 rollback segment parameters for Oracle 88 RS/6000 Asynchronous I/O option 100
118
S
SA_PASSWORD for Sybase 71 security See also passwords installer privileges 21 Select a group parameter CTM/Agent for Windows 35, 54 Select the Disk resource parameter CTM/Agent for Windows 35, 54 Select the Network resource parameter CTM/Agent for Windows 35, 54 semmap parameter HP-UX with Oracle 99 semmni parameter HP-UX with Oracle 40, 98, 99 Solaris with Oracle 102 semmns parameter HP-UX with Oracle 40, 98, 99 Solaris with Oracle 102 semmnu parameter HP-UX with Oracle 98, 100 semmsl parameter Solaris with Oracle 102 semopm parameter Solaris with Oracle 102 semvmx parameter HP-UX with Oracle 100 Solaris with Oracle 102 Solaris with Sybase 102 Server-to-Agent port number CTM/Agent for Windows 54 setup types CTM/Agent for Windows 53 shmmax parameter HP-UX with Oracle 100 Solaris with Oracle 102 Solaris with Sybase 102 shmmin parameter HP-UX with Oracle 100 Solaris with Oracle 102 shmmni parameter HP-UX with Oracle 100 Solaris with Oracle 102 shmseg parameter HP-UX with Oracle 100 Solaris with Oracle 102 Solaris with Sybase 102 silent installation Oracle on UNIX 86 Sybase 69 UNIX 26 Windows 34 size data tablespace 88 Database system tablespace 89 Solaris
how to check available RAM 97 kernel parameters 101 minimum requirements 18 sp_configure command 67 sp_dropdevice command 68 sp_helpdb command 68 sp_helpdevice command 68 stacksize parameter 21 support, customer 3 Sybase configuration 16 installation parameters 7175 installing client 68 installing server 64 server parameters 67 silent installation 69 uninstalling 112 Sybase Server Backup Port Number parameter 72 Sybase Server Host Name parameter 72 Sybase Server Query Port Number parameter 72 Sybsystemprocs Device Full Path File Name parameter 72 System account parameter for Oracle 91 system requirements. See requirements
T
tablespaces displaying names of 82 file name of temporary 89 rollback segments file name 88 size of temporary 89 unique name and owner requirement 82 technical support 3 Temporary Device File Size parameter 72 Temporary Device Full Path File Name parameter 72 Temporary Tablespace size 89 trace.log file 91 TRACKER_EVENT_PORT. CTM/Agent for Windows 57
U
uninstall_oracle.sh script 113 uninstalling CONTROL-M Oracle server from UNIX 113 CONTROL-M Sybase server 112 CONTROL-M/Server from UNIX 111 CONTROL-M/Server from Windows 112 failed Oracle installation on UNIX 83 failed Sybase installation 68 UNIX installation Oracle server 77 parameters for Oracle 88 parameters for Sybase 71, 73 silent 86 user connections, number of Sybase 67
Index
119
user password, Oracle installation parameter 91 usernames display existing 82 Oracle database on UNIX 90
V
verifying existing Oracle components 81 version agent communication protocol 55, 60 vps_ceiling parameter HP-UX with Oracle 100
W
windows.xml file 54 WINNTSystem32 folder, PATH environment variable 22
120
Notes
Third-Party Product Terms

The following terms apply to third-party products that are included with or in a BMC Software product as described in the BMC Software, Inc., License Agreement that is applicable to the product.
The Apache Software License, Version 1.1

This product includes the Apache software product found at (http://www.apache.org/), and the Apache software product is distributed to us pursuant to the following terms and conditions: Copyright (c) 1999 - 2003 The Apache Software Foundation. All rights reserved. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution if any, must include the following acknowledgement: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowlegement may appear in the software itself, if and wherever such third-party acknowlegements normally appear. 4. The names "Xerces", and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name without prior written permission of the Apache Group. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Apache Software License, Version 2.0

This product includes the Apache software product found at http://apache.org , and the Apache software product is distributed to us pursuant to the following terms and conditions:
Copyright (c) 2000-2004 The Apache Software Foundation. All rights reserved. TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: A. You must give any other recipients of the Work or Derivative Works a copy of this License; and B. You must cause any modified files to carry prominent notices stating that You changed the files; and C. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and D. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. E. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, 8. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 9. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 10. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
JiBX License
Copyright (c) 2003-2005, Dennis M. Sosnoski All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of JiBX nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
PuTTY Licence
PuTTY is copyright 1997-2005 Simon Tatham. Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith, and CORE SDI S.A. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Thai Open Source License

Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
!"##$%! !"##$%! !"##$%! !"##$%!

*57702*

Control M

Hochgeladen von

Dokumentinformationen

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

Hochgeladen von

Copyright:

Verfügbare Formate

CONTROL-M/Server and CONTROL-M/Agent

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

Considerations for a Microsoft Windows cluster environment . . . . . . . . . . . . . . . . . . 50

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

A database server (Oracle, Sybase, or MSSQL). CONTROL-M/Server on UNIX or Windows.

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

Installation checklist for CONTROL-M/Server

Install a database server and clients Install CONTROL-M/Server.

CONTROL-M Migration Guide

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

Planning for CONTROL-M/Server

Sybase client Oracle 10 server Oracle 10 client

N/A N/A N/A N/A

MSSQL (English only) N/A

Planning for CONTROL-M/Server

Database server configurations

Database type Description Sybase

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

East Asian (CJK) language considerations

East Asian (CJK) language considerations

Planning for CONTROL-M/Server

UNIX requirements for CONTROL-M/Server (Part 1 of 2)

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

Operating system levels and patches

UNIX requirements for CONTROL-M/Server (Part 2 of 2)

Operating system levels and patches

B If the host name of the computer is mapped to localhost, remove it by editing

2 Download the pre_req.tar.Z file from the following Web location:

Planning for CONTROL-M/Server

Preparing a CONTROL-M/Server account on UNIX

6 Follow the prompts and fill in information as necessary.

Preparing a CONTROL-M/Server account on UNIX

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

5. On Oracle, the administrator group name must be dba.

Setting limits for the CONTROL-M/Server account on UNIX

Limits for CONTROL-M/Server accounts on UNIX

Planning for CONTROL-M/Server

Windows requirements for CONTROL-M/Server

CONTROL-M/Ser ver diskspace Database diskspace (on NTFS disks)

Database type MSSQL Server 2005

CONTROL-M/Server Internet Explorer version 5.5 or later

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

Required privileges and passwords

Required privileges and passwords

Installation resource requirements

System administrator (Root user privileges)

CONTROL-M/Server database owner

Planning for CONTROL-M/Server

Required privileges and passwords

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

Installing CONTROL-M/Server on UNIX

Chapter 3 Installing CONTROL-M/Server

3 Log in as the root user. 4 Mount the CONTROL-M/Server installation CD.

CONTROL-M/Server and CONTROL-M/Agent Installation Guide

7 Issue the following command to activate the silent installation script: