CONTROL-M Enterprise Manager - Administrator Guide 6.1.00 PDF

CONTROL-M/Enterprise
Manager
Administrator Guide
Version 6.1.00 Beta
September 30, 2001
Copyright 2001 BMC Software, Inc. 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. All other registered trademarks or trademarks belong to their
respective companies.
ECS-6100B-A0105A
Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. UNPUBLISHEDRIGHTS RESERVED UNDER THE
COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure by the U.S. Government is
subject to restrictions set forth in FAR Section 52.227-14 Alt. III (g)(3), FAR Section 52.227-19, DFARS
252.227-7014 (b), or DFARS 227.7202, as amended from time to time. Send any contract notices to
Contractor/Manufacturer:
BMC Software, Inc.
2101 CityWest Blvd.
Houston TX 77042-2827
USA
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain
general information about the company, its products, special events, and career opportunities. For a complete
list of all BMC Software offices and locations, go to http://www.bmc.com/corporate/offices.html.
USA and Canada
Outside USA and Canada
Address
Telephone
(01) 713 918 8800
Fax
(01) 713 918 8000
BMC Software, Inc.

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

800 841 2031
Fax
713 918 8000
Customer Support
You can obtain technical support by using Response Online (support from the Web) or Response On Demand.
To expedite your inquiry, please see Before Contacting BMC Software, below.
Response Online
You can obtain technical support from BMC Software 24 hours a day, seven days a week by accessing the
technical support Web site at http://www.bmc.com/support.html. From this site, you can
read overviews about support services and programs that BMC Software offers
find the most current information about BMC Software products
search a database for problems similar to yours and possible solutions
order or download product documentation
report a problem or ask a question
subscribe to receive e-mail notices when new product versions are released
find worldwide BMC Software support center locations and contact information, including e-mail addresses,
fax numbers, and telephone numbers
Response On Demand
In the USA and Canada, if you need technical support and do not have access to the Web, call 800 537 1813.
Outside the USA and Canada, please contact your local support center or your local sales office for assistance.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that a technical support analyst
can begin working on your problem immediately:
product information
product name
product version (release number)
license number and password (trial or permanent)
operating-system and environment information
machine type
operating system type, version, and service pack or program temporary fix (PTF)
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, and service pack or
PTF
sequence of events leading to the problem
commands and options that you used
messages received (and the time and date that you received them)
product error messages

messages from the operating system, such as file system full
messages from related software
BMC Software, Inc., Confidential and Proprietary Information
iii
iv
CONTROL-M/Enterprise ManagerAdministrator Guide
Contents
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1
Overview
Introducing CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

CONTROL-M/EM Components Summary . . . . . . . . . . . . . . . . . . . 1-3
CONTROL-M/EM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Administrator Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
CONTROL-M/EM Related Products . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Time Zone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Chapter 2
Defining CONTROL-M Installations
Communication Administration Window . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3
Maintaining CONTROL-M/EM
Component Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Starting and Stopping CONTROL-M/EM Components . . . . . . . . . . 3-4
Stopping CONTROL-M/EM Processes . . . . . . . . . . . . . . . . . . . . . . 3-5
Automatic Program Startup and Shutdown . . . . . . . . . . . . . . . . 3-6
Cleanup of Old Global Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Gateway Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
CONTROL-M/EM Administrator Password . . . . . . . . . . . . . . . . . . 3-12
OS/390 Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Configuring ENTERPRISE/CS for Use with a Firewall . . . . . . . . . . 3-14
Running the assign_ports Script . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Hostname and Port Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Chapter 4
Managing CONTROL-M/EM Using the Administration Facility
Component Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Contents
Administration Facility Window . . . . . . . . . . . . . . . . . . . . . . . . .4-7

Starting and Stopping Components . . . . . . . . . . . . . . . . . . . . . . .4-13
Registering Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15
Updating Information about Registered Components . . . . . . . . .4-21
Selecting and Filtering Components . . . . . . . . . . . . . . . . . . . . . .4-21
Administration Facility Check Intervals . . . . . . . . . . . . . . . . . . .4-26
Using the Agents Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-27
Filtering the Agents Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-31
Truncating the Agents Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-31
Displaying and Modifying System Parameters . . . . . . . . . . . . . . . . .4-33
Database Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
Removing Old Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
Extending the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44
Checking Available Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47
SQL Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47
Print Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47
Chapter 5
Managing CONTROL-M/EM with the Root Menu
CONTROL-M/EM Root Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Activation Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
Database Creation Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6
Database Creation on Sybase Adaptive Server . . . . . . . . . . . . . .5-7
Database Creation on Oracle Server . . . . . . . . . . . . . . . . . . . . . .5-17
Database Maintenance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27
Export/Import Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29
Custom Export/Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32
Database Check Utility (db_check) . . . . . . . . . . . . . . . . . . . . . . .5-36
Chapter 6
Security
CONTROL-M/EM Workstation Security . . . . . . . . . . . . . . . . . .6-1

CONTROL-M Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
CONTROL-M/EM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
User and Group Authorization Windows . . . . . . . . . . . . . . . . . . . . . .6-10
User Authorizations General Panel . . . . . . . . . . . . . . . . . . . . .6-15
Group Authorizations General Panel . . . . . . . . . . . . . . . . . . . .6-17
User/Group Authorizations Jobs Panel . . . . . . . . . . . . . . . . . .6-19
User/Group Authorizations Privileges Panel . . . . . . . . . . . . . .6-22
User/Group Authorizations Scheduling Tables Panel . . . . . . .6-25
User/Group Authorizations Resources and Calendars Panel . .6-27
vi
Chapter 7
Troubleshooting
Troubleshooting Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Database Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Gateway Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Global Conditions Server Parameters . . . . . . . . . . . . . . . . . . . . . 7-15
Configuring Orbix2000 Parameters . . . . . . . . . . . . . . . . . . . . . . 7-18
DIAG Diagnostics Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
DIAG Debug Message Logging . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Initialization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Using DIAG with a GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Chapter 8
Customization
Defining CONTROL-M Installations . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Customizing System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Alert Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Defaults File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
SQL Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Appendix A
SNMP Interface
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTROL-M/EM and SNMP Traps . . . . . . . . . . . . . . . . . . . . . . .
SNMP Trap Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing CONTROL-O/Server . . . . . . . . . . . . . . . . . . . . .
Customizing HP-OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing NetView for AIX . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing Tivoli Management Environment Console . . . . .
Customizing CONTROL-M/Links for Distributed Systems . .
Appendix B
A-2
A-3
A-3
A-5
A-6
A-7
A-10
A-13
A-17
Menus and Line Commands
CONTROL-M/EM Root Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

CONTROL-M/EM Activation Menu . . . . . . . . . . . . . . . . . . . . . . . .B-3
CONTROL-M/EM Database Creation Menu . . . . . . . . . . . . . . . . . .B-5
CONTROL-M/EM Database Maintenance Menu . . . . . . . . . . . . . . .B-5
CONTROL-M/EM Troubleshooting Menu . . . . . . . . . . . . . . . . . . . .B-6
Database Troubleshooting Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-6
Gateway Troubleshooting Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7
Additional Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8
Contents
vii
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Appendix C
System Parameters
viii
Figures
Figures
Figure 1-1
Figure 1-2
Figure 2-1
Figure 2-2
Figure 3-1
Figure 4-1
Figure 4-2
Figure 4-3
Figure 4-4
Figure 4-5
Figure 4-6
Figure 4-7
Figure 4-8
Figure 4-9
Figure 4-10
Figure 4-11
Figure 6-1
Figure 6-2
Figure 6-3
Figure A-1
Figure A-2
CONTROL-M/EM Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Multi-Platform Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
The Communication Administration Window . . . . . . . . . . . . . . 2-2
The CONTROL-M Definition Window . . . . . . . . . . . . . . . . . . . 2-2
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Tree Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Administration Facility Options Dialog Box . . . . . . . . . . . . . . . 4-15
Component Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Filter Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Agents Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
CONTROL-M/EM System Parameters Window . . . . . . . . . . . . 4-34
Update/View Parameter Window . . . . . . . . . . . . . . . . . . . . . . . . 4-37
CONTROL-M/EM Database Extend (Sybase and MSSQL) . . . 4-45
CONTROL-M/EM Extend Database (Oracle) . . . . . . . . . . . . . . 4-46
User Authorization Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Users and Groups Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Field Column List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Editing the tecad_snmp File . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Editing the tecad_snmp.baroc File . . . . . . . . . . . . . . . . . . . . . . A-16
Figures
ix
Tables
Tables
Table 1-1
Table 1-2
Table 2-1
Table 3-1
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Table 4-5
Table 4-6
Table 4-7
Table 4-8
Table 4-9
Table 4-10
Table 4-11
Table 4-12
Table 4-13
Table 5-1
Table 5-2
Table 5-3
Table 5-4
Table 5-5
Table 5-6
Table 5-7
Table 6-1
Table 6-2
Table 6-3
Table 6-4
CONTROL-M/EM Components . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Time Zone Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
CONTROL-M Definition Window Fields . . . . . . . . . . . . . . . . . 2-3
Hostname Modification Locations. . . . . . . . . . . . . . . . . . . . . . . 3-19
Component Type Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Color for Component Type Icons . . . . . . . . . . . . . . . . . . . . . . . 4-13
Component ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Running on... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Fields of the Filter Properties Dialog Box . . . . . . . . . . . . . . . . . 4-25
Agents Log Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Agents Log Message Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Agent Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
CONTROL-M/EM System Parameters Window Columns . . . . 4-35
CONTROL-M/EM Database Window (Sybase and MSSQL) . 4-45
CONTROL-M/EM Extend Database Dialog Box (Oracle). . . . 4-46
Root Menu - Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Activation Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Database Creation Menu Options . . . . . . . . . . . . . . . . . . . . . . . 5-7
Sybase Database Environment Components . . . . . . . . . . . . . . 5-8
Oracle Database Environment Components . . . . . . . . . . . . . . . 5-17
Database Maintenance Menu Options . . . . . . . . . . . . . . . . . . . . 5-27
Custom Export/Import Menu Options . . . . . . . . . . . . . . . . . . . . 5-33
Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Jobs Panel Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Tables
xi
Table 6-5
Table 6-6
Table 6-7
Table 6-8
Table 6-9
Table 6-10
Table 6-11
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 7-5
Table 7-6
Table 7-7
Table 7-8
Table 8-1
Table 8-2
Table 8-3
Table 8-4
Table A-1
Table A-2
Table A-3
Table A-4
Table A-5
Table B-1
Table B-2
Table B-3
Table B-4
Table B-5
Table B-6
Table B-7
Table B-8
Table C-1
Table C-2
Table C-3
Table C-4
Table C-5
Table C-6
Table C-7
Table C-8
Column Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Privileges Panel Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calendar Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Menu Options . . . . . . . . . . . . . . . . . . . . . . . . .
Database Troubleshooting Menu Options . . . . . . . . . . . . . . . . .
Gateway Troubleshooting Menu Options. . . . . . . . . . . . . . . . . .
Set Debug Parameters Menu Options. . . . . . . . . . . . . . . . . . . . .
Gateway Log Filename Parameters . . . . . . . . . . . . . . . . . . . . . .
Global Conditions Server Parameters G . . . . . . . . . . . . . . . . . .
DIAG Initialization (.ini) File Parameters . . . . . . . . . . . . . . . . .
DIAG Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alert Data Processing Parameters . . . . . . . . . . . . . . . . . . . . . . .
Parameters for the Global Conditions Distribution Facility. . . .
Sybase Adaptive Server Parameters. . . . . . . . . . . . . . . . . . . . . .
Oracle Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SNMP Trap Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTROL-M/EM Customization Parameters . . . . . . . . . . . . .
SNMP Parameter Modification Command Terms . . . . . . . . . . .
Trap Message Formatting Variables . . . . . . . . . . . . . . . . . . . . . .
Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Root Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activation Menu and Line Commands. . . . . . . . . . . . . . . . . . . .
Database Creation Menu and Line Commands . . . . . . . . . . . . .
Database Maintenance Menu and Line Commands . . . . . . . . . .
Troubleshooting Menu and Line Commands . . . . . . . . . . . . . . .
Database Troubleshooting Menu . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Troubleshooting Menu and Line Commands . . . . . . .
CONTROL-M/EM Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enterprise License Manager and Client Parameters. . . . . . . . . .
Global Alerts Server Parameters . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GUI Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Conditions Server Parameters . . . . . . . . . . . . . . . . . . . .
6-21
6-22
6-26
6-28
6-28
6-30
6-31
7-3
7-6
7-7
7-9
7-13
7-16
7-23
7-24
8-3
8-5
8-8
8-9
A-3
A-5
A-6
A-9
A-11
B-2
B-3
B-5
B-5
B-6
B-6
B-7
B-8
C-2
C-4
C-7
C-9
C-10
C-13
C-14
C-14
xii
About . . .
About This Book

This book contains detailed information about CONTROL-M/Enterprise
Manager (CONTROL-M/EM). It is intended for production
management personnel. Use this book with the CONTROL-M/Enterprise
Manager User Guide (version 6.1.00 Beta), the CONTROL-M/Desktop
User Guide (version 6.1.00 Beta), the CONTROL-M Job Parameter
and AutoEdit Variable Reference Guide, the CONTROL-M/Enterprise
Manager Utilities Reference Guide, and the CONTROL-M/Enterprise
Manager Installation Guide (version 6.1.00 Beta).
Note
This book assumes that you are familiar with your host operating system.
xiii
How This Book Is Organized

This book describes the usage and maintenance of
CONTROL-M/Enterprise Manager. It also includes details for
customizing, managing, securing, and troubleshooting the product.
Chapter/Appendix
Description
Chapter 1
Overview
Provides an overview of CONTROL-M/Enterprise
Manager components, administrator
responsibilities, and related products.
Chapter 2

Explains how to define CONTROL-M Installations.
Chapter 3
Provides information about various features and
functions required to maintain the CONTROL-M/EM
environment.
Chapter 4
Managing CONTROL-M/EM Using the

Administration Facility
Provides information about starting up and shutting
down CONTROL-M/Enterprise Manager
components and maintaining the database.
Chapter 5

Explains how to manage CONTROL-M/Enterprise
Manager and the CONTROL-M/Enterprise
Manager database and database server from a
Unix command line.
Chapter 6
Security
Provides information about granting user
authorizations and how to maintaining a secure
environment.
Chapter 7
Troubleshooting
Describes the various problem-solving tools in the
Troubleshooting menu and the DIAG diagnostic
facility.
Chapter 8
Customization
Describes customization of
CONTROL-M/Enterprise Manager system defaults
and database server configuration settings.
xiv
Chapter/Appendix
Description
Appendix A
SNMP Interface
Describes how to interface
CONTROL-M/Enterprise Manager with various
network management applications.
Appendix B

Lists and describes the various commands and
menus used with CONTROL-M/Enterprise
Manager.
Appendix C
System Parameters
Lists and describes the system parameters that
influence the functioning of
CONTROL-M/Enterprise Manager.
Index
xv
Related Documentation
The following BMC publications are also relevant to
CONTROL-M/EM.documentation:related publications
CONTROL-M/Enterprise Manager User Guide describes

CONTROL-M/EM concepts, features, facilities, and operating
instructions. It can be used as a learning guide as well as a reference
guide.
CONTROL-M/Desktop User Manual describes an application

used to define and manage CONTROL-M job processing definitions,
Scheduling tables, and calendars.
CONTROL-M/Enterprise Manager Installation Guide describes the

tasks that the CONTROL-M/EM administrator must perform to
install CONTROL-M/EM components on Windows and Unix
machines.
CONTROL-M Job Parameter and AutoEdit Variable

Reference Guide describes the parameters used for creating job
processing definitions.
CONTROL-M/Enterprise Manager Utilities Reference Guide

describes the utilities used for creating and managing objects in the
job production environment and maintaining various aspects of
CONTROL-M Administrator Guides are supplied for various

CONTROL-M platforms. These guides describe installation, setup,
security, and utilities (for example, Unix, OpenVMS, AS/400, and
Windows).
CONTROL-M User Manual (for OS/390) is a complete guide to

the functions and facilities of the CONTROL-M Production Control
System, and how to use them in a mainframe environment.
CONTROL-M Server/Agent Migration Guide describes how to

migrate to CONTROL-M Server/Agent Technology from
CONTROL-M 2.1.LC platforms.
xvi
Online and Printed Books

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

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

last-minute product information.documentation:release notes
The latest versions of the release notes are also available on the Web at
http://www.bmc.com/support.on-line support:release notes
documentation:conventionsdocument
conventionsConventions
The following abbreviations are used in this guide:
Abbreviationdocum
ent
conventions:abbrevi
ations
Description
CONTROL-M/EM
CONTROL-M/Enterprise Manager
Net
CONTROL-M/EM Network
WS-GTW
CONTROL-M/EM workstation gateway
DC-GTW
Data center gateway (for MVS data centers, this is

referred to as ECSGATE or IOAGATE)
<home-directory>
Directory in which CONTROL-M/EM is installed
xviii
The following conventions are used in this guidedocument

conventions:symbols:
<key>
When describing keystrokes, angle brackets are

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

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

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

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

literal examples, and JCL scripts are
presented in this typeface.
Boldface
In instructions, boldface type highlights information

that you enter. File names, directory names and
paths, dialog box names, and Web addresses also
appear in boldface type.
Italics
Italic type is used to emphasize important terms.

The titles of BMC Software product documentation
are also displayed in italic type.
One-Step Procedures
The symbol
denotes one-step instructions.
xix
Ellipsis
An ellipsis ( . . . ) indicates that you can repeat the

preceding item or items as many times as
necessary.
Option Symbol
A vertical bar ( | ) separating items indicates that

you must choose one item. In the following
example, you would choose a, b, or c:
a|b|c
xx
Overview
This guide is primarily for the CONTROL-M/Enterprise Manager

(CONTROL-M/EM) administrator. Using this guide you can learn to
monitor and maintain your CONTROL-M/EM network. Information
about maintaining the CONTROL-M/EM database is also included in
this book.
Many CONTROL-M/EM maintenance tasks are carried out with the
Administration facility. In addition, some maintenance tasks can be
carried out for Unix-based installations using the root menu. Both tools
are covered in this guide.
This guide addresses security. Administrators can refer to this book for
information on defining users and workstations and assigning them
access privileges.
Introducing CONTROL-M/EM
CONTROL-M/Enterprise Manager is a software product that runs
primarily on Windows and Unix workstations to provide centralized
control of the job scheduling production environment for the entire
enterprise. The CONTROL-M/EM advanced graphical user interface
(GUI) enables you to view production flows for the entire active
environment.
Overview
1-1
CONTROL-M/Enterprise Manager works together with CONTROL-M

Production Control Systems and the CONTROL-R Automated Job
Restart System (that is available on OS/390 platforms only).
With CONTROL-M/EM, you can optimize CONTROL-M production
throughput simply and efficiently, even in a cross-platform production
environment. CONTROL-M installations, which include one or more
computers, are managed by one CONTROL-M. One CONTROL-M/EM
network can control multiple CONTROL-M installations on various
types of platforms.
Figure 1-1
CONTROL-M/EM Network
1-2
The following section introduces you to the components that comprise

CONTROL-M/EM Components Summary

The CONTROL-M/Enterprise Manager environment consists of a
database, a database server and some or all of the CONTROL-M/EM
integrated components listed in Table 1-1. Setting up an
CONTROL-M/EM environment includes installing an
CONTROL-M/EM server and one or more of these components:
Table 1-1
CONTROL-M/EM Components (Part 1 of 3)
Component
Description
CONTROL-M/EM
Server
Process that handles communication

between CONTROL-M/EM GUI
workstations and other components of
CONTROL-M/EM. For more information,
see page 3-2.
CONTROL-M/EM
Graphical User
Interface (GUI)
Central point of control for the enterprise

production scheduling system. From each
CONTROL-M/EM GUI you can view the
status of jobs in any part of the enterprise
system, issue requests, modify job
parameters, restart jobs, and handle any
type of exception to ensure efficient
production job flow. For more information,
see page 3-2.
Installation Notes
Must be installed on a Windows

computer.
You can install more than one
CONTROL-M/EM GUI, if desired.
Overview
1-3
Table 1-1
Component
Description
Installation Notes
Relational
Database
Management
Server
(RDBMS)
One Sybase Adaptive Server or Oracle

Server or Microsoft SQL (MSSQL) Server.
If MSSQL is used, it must already

be installed on your network.
MSSQL is not packaged with
CONTROL-M/EM. You must
supply MSSQL if you want to use
it.
If Sybase Server is used in an
installation on Windows, it must
already be installed on your
network. Sybase Adaptive Server
is not supplied with
CONTROL-M/EM installed on
Windows.
CONTROL-M/EM
Database
A repository of current data related to the

functioning of the CONTROL-M/EM
environment, the CONTROL-M/EM GUIs,
and security.
CONTROL-M/EM
Global Conditions
Server
(GCS)
Process that identifies and distributes

global conditions used to create job
dependencies between CONTROL-M
installations.

GCS, if desired, but only one
can be active at a time.
CONTROL-M/EM
Global Alerts
Server (GAS)
Process that identifies and distributes

alerts between CONTROL-M installations
and CONTROL-M/EM workstations. The
Global Alerts Server connects to each
CONTROL-M/EM gateway to receive
alerts from CONTROL-M and transmit
them to the CONTROL-M/EM GUIs.

GAS, if desired.
CONTROL-M/EM
Gateways
(WS-GTW)
CONTROL-M/EM workstations and

CONTROL-M installations communicate
with each other through dedicated
gateways on the CONTROL-M/EM
platforms. For OS/390 CONTROL-M
installations, an additional component
called MVS Gateway for Enterprise
Controlstation or IOAGATE is provided to
run on the OS/390 platform.
One gateway is needed for each

CONTROL-M installation.
1-4
Table 1-1
Component
Description
Installation Notes
CONTROL-M/
Desktop
Application used to define and manage job

processing definitions, Scheduling tables
and calendars.
Installed automatically with the

CONTROL-M/EM GUI.
Administration
Facility
Application used to manage

CONTROL-M/EM components and
maintain the CONTROL-M/EM database
Installed automatically with the

CONTROL-M/EM gateway.
CONTROL-M/EM components can be installed on:
a single Windows computer.

separate Windows computers.
a combination of Unix and Windows computers.
The CONTROL-M/EM GUI must be installed on a Windows
computer. All other CONTROL-M/EM components can be installed
on Unix computers.
These computers are referred to as CONTROL-M/EM workstations. For

more information, see Administrator Responsibilities on page 1-8.
Figure 1-2 illustrates two CONTROL-M installations connected to a
single CONTROL-M/EM workstation. Many CONTROL-M installations
and many workstations may exist together.
Overview
1-5
Figure 1-2
Multi-Platform Enterprise
Each CONTROL-M is connected to the CONTROL-M/EM environment

through a dedicated gateway on a CONTROL-M/EM workstation. Using
network communication, CONTROL-M/EM automatically controls the
transfer of information between all CONTROL-M installations and all
workstations.
1-6
CONTROL-M/EM Database
The CONTROL-M/EM database is a repository of data relating to the
functioning of CONTROL-M/EM on the workstation. The database is
maintained using a dedicated or shared Sybase Adaptive Server, MSSQL
Server, or Oracle Server. MSSQL and Sybase Adaptive Server are not
supported as a dedicated installation on Windows computers.
Note
Prior to CONTROL-M/EM version 6.1.00 Beta, CONTROL-M/EM

database functions were divided between two databases, the Server
database and the Users database. As of CONTROL-M/EM version 6.1.00
Beta, these functions are combined in a single database.
The CONTROL-M/EM database contains the following information:
Copies of the job processing definitions in the CONTROL-M

databases of the various CONTROL-M installations.
Current active environment of jobs and resources in all

CONTROL-M installations connected to CONTROL-M/EM.
Communication status of CONTROL-M installations and

CONTROL-M/EM components, together with related configuration
information.
ViewPoints, Collections, Hierarchies, and Filters defined for all

CONTROL-M/EM GUIs.
Security data for all CONTROL-M/EM workstations, components,

and users.
Current operational status of CONTROL-M/EM components on the

network.
For more information about the CONTROL-M/EM database, see

Chapter 1 of the CONTROL-M/Enterprise Manager User Guide.
Overview
1-7
Administrator Responsibilities
CONTROL-M/EM has three areas of administrative responsibility. Each
area has certain privileges, functions, and responsibilities, and is
accessed by a specific user name (title). The CONTROL-M/Enterprise
Manager Administrator Guide describes the responsibilities of these
three administrator-users:
CONTROL-M/EM Administrator
The CONTROL-M/EM administrator (also known as the Database
Owner or DBO) effectively owns all CONTROL-M/EM programs
and database files. In addition to being a regular user, the
CONTROL-M/EM administrator is responsible for:
Maintaining the CONTROL-M/EM database and all
CONTROL-M/EM files. For more information, see Chapter 5,
Managing CONTROL-M/EM with the Root Menu, and
Chapter 3, Maintaining CONTROL-M/EM.
Starting and stopping CONTROL-M/EM components (except
GUIs). For more information, see Starting/Stopping
CONTROL-M/EM Components in Chapter 3, Maintaining
CONTROL-M/EM.
Adding CONTROL-M/EM users to the system. For more
information, see CONTROL-M/EM Security in Chapter 6,
Security.
Defining CONTROL-M installations to CONTROL-M/EM. For
more information, see Chapter 2, Defining CONTROL-M
Installations.
Providing and maintaining CONTROL-M/EM security using the
Users and Groups Authorization facility. For more information,
see Chapter 6, Security.
Performing diagnostic functions, when necessary, to optimize
CONTROL-M/EM performance. For more information, see
Chapter 3, Maintaining CONTROL-M/EM..
1-8
The CONTROL-M/EM administrator is defined during installation

of its database.
Database System Administrator (sa or SYSTEM)

This administrator has the user name sa (for Sybase Adaptive
Server), sa (for MSSQL Server), or SYSTEM (for Oracle Server).
This user is defined in the database server. Responsibilities include
maintaining the database server and database (for example, backup
and restore). This user name is not a system name; it is a login name
for the database. The password for this user is required by several
CONTROL-M/EM utilities related to database maintenance.
Windows Administrator
The Windows administrators responsibilities include defining
Windows users and performing various system security functions.
Overview
1-9
CONTROL-M/EM Related Products

The CONTROL-M/EM system includes the BMC Software products
listed below. Which of these products you should install depends on the
types of CONTROL-M installations at your site:
OS/390 Gateway for CONTROL-M/Enterprise Manager (also

referred to as IOAGATE)
Add-on component for an OS/390 version of CONTROL-M. This
software enables CONTROL-M/EM to communicate with
CONTROL-M on a mainframe.
CONTROL-M or CONTROL-M/SERVER
Production control and tracking product that runs in each
CONTROL-M installation.
CONTROL-M/Agent
Production platform-based product used when CONTROL-M
Server/Agent Technology is implemented.
Note
You can also create and run jobs for specified applications (for example
SAP or Oracle Applications). For more information, see the User Guide
for the appropriate CONTROL-M Control Module.
1-10
Time Zone Support

As of version 6.1.00 of CONTROL-M, you can specify a timezone for a
job. Using the Time Zone parameter in the job processing definition, you
can choose a predefined time zone according to which the job will run.
Note
You can add a timezone to the predefined list. For more information, see
Adding and Modifying Time Zone Definitions on page 1-14.
If no time zone is specified for a job, it will be ordered and implemented
according to the time zone of the CONTROL-M/Server that ordered the
job.
Time Zone jobs in the Active Jobs File
In previous versions of CONTROL-M, the Active Jobs file contained

only jobs that were ordered for the current working day. As of version
6.1.00, jobs may be ordered before their working day began, and they
may remain in the Active Jobs file after their specified scheduling date.
This can result is a larger Active Jobs file and therefore slower
processing. To avoid this problem, see Recommended Method for
Ordering Jobs with Specific Time Zones on page 1-13.
Defining a job for a specific Time Zone
To define a job to be executed in a specific time zone, specify the

appropriate value for the time zone parameter in the job processing
definition. Table 1-2 describes the values whose definitions are supplied
with CONTROL-M.
Table 1-2
Value
Time Zone Values
Description
HAW
Hawaii (GMT-10:00)
PST
Pacific Standard Time (GMT-08:00)
Overview
1-11
Table 1-2
Value
Time Zone Values
Description
MST
Mountain Standard Time (GMT-07:00)
CST
Central Standard Time (GMT-06:00)
EST
Eastern Standard Time (GMT-05:00)
GMT
Greenwich Mean Time (GMT+00:00)
WET
Western European Time (GMT+01:00)
CET
Central European Time (GMT+02:00)
EET
Eastern European Time (GMT+03:00)
HKG
Hong Kong (GMT+08:00)
TOK
Tokyo (GMT+09:00)
MEL
Melbourne (GMT+10:00)
Special notes for job definitions with time zones:
Newly defined jobs with specified time zones must be saved at least
48 hours before their intended execution dates (in order to ensure
that they are ordered automatically by the appropriate New Day
Procedure or User Daily).
If they must run today they should be ordered manually (for
example, using the ctmorder utility).
Specified Odates are calculated according to the working date (not

the actual date). This means that if a job is defined as working on the
5th of the month at 3:00 A.M., and the working day begins at 5:00
A.M., then the job will actually be run at 3:00 A.M. on the morning of
the 6th (which is still part of the working day of the 5th).
In addition to time zones, you can also order a job that is intended for
execution on a future date. For more information, see the odate and
odate_option parameters in any of the following
CONTROL-M/Server utilities:
ctmudly
ctmudchk
1-12
ctmorder
ctmcreate
For more information about these utilities, see the appropriate
CONTROL-M/Server Administrator Guide.
It is recommended not to combine jobs that have time zone

specifications with jobs that do not specify a time zone in the same
Scheduling table or Group Scheduling table.
When a job is considered for ordering by the New Day procedure, it

is ordered if its scheduling date occurrs within the next 48 hours.
When a job is ordered by a User Daily job, it will be ordered only if
it's scheduling criteria are satisfied for the current working date. For
this reason, it is recommended that you arrange the jobs for each
time zone in a separate table. For more information, see the
recommended method described below.
Recommended Method for Ordering Jobs with Specific Time Zones
Jobs with specified timezones may be ordered as early as 48 hours before

their actual run. Since these jobs must normally be ordered from the New
Day procedure, this can result in an unusually large number of jobs in the
Active Jobs file for a long time.
To avoid this problem:
1. Create a separate scheduling table for each time zone that you will be
using and place the jobs definitions for that time zone in that table.
2. Define a User Daily job (using the ctmudly utility) for each
scheduling table that was created in Step 1.
Specify a time for the User daily that corresponds to just after the
beginning of the working day in that time zone.
In the -odate parameter, specify the working date for the time
zone (usually either the current CONTROL-M/Server working
date, or the next day).
Overview
1-13
In the -odate_option parameter, specify run_date, to indicate

that the odate value should be used to determine the working day
on which the jobs should run.
3. List the User Daily jobs in the ctmorder section of the New Day
Procedure.
This method ensures that the appropriate jobs are ordered only when they
become necessary, thus resulting in a smaller Active Jobs file and faster
processing.
Adding and Modifying Time Zone Definitions
The time zone definitions to be used by CONTROL-M are kept is the

TimeZone.dat file in the CONTROL-M_ home/data directory. The
default time zones are described above in Table 1-2, Time Zone
Values, on page 1-11.
You can add or modify line in this file as long as you conform to the
following format:
xxx (GMThh:mm)
xxx
Three-character time zone designation. This is the value that

should be specified in the Time Zone parameter of relevant job
processing definitions.
Plus or Minus sign to indicate whether the time zone is earlier or

later than Greenwich Mean Time
hh:mm
The number of hours and minutes that the specified time zone
differs from Greenwich Mean Time.
Note: The only valid values for mm are 00 or 30.
Example
To create a time zone for New York that is five hours earlier than
Greenwich Mean Time, specify:
NYC (GMT-05:00)
1-14
Notes
Similar TimeZone.dat files are used by CONTROL-M/Server and

CONTROL-M/EM. It is highly recommended that you keep these
files synchronized, so that all TimeZone.dat files have the same
content.
If a time zone is deleted from the TimeZone.dat file, job definitions

that specify that time zone will become invalid. This will also happen
if the three-character name for the time zone is modified in the
TimeZone.dat file but not in the job processing definition.
Overview
1-15
1-16
Defining CONTROL-M Installations 2

Each CONTROL-M installation in the job scheduling production
environment must be identified to CONTROL-M/Enterprise Manager
(CONTROL-M/EM) and included in the CONTROL-M/EM database.
The CONTROL-M/EM administrator defines CONTROL-M
installations and specifies relevant details about how the installations
communicate with CONTROL-M/EM. CONTROL-M installations are
defined with the Communication Administration window.
Communication Administration Window

The Communication Administration window is used to create, modify,
and delete CONTROL-M definitions in the CONTROL-M/EM database.
To define a new CONTROL-M using the Communication Administration window:
1. Log on to CONTROL-M/EM as the CONTROL-M/EM

administrator.
2. Choose Tools => Communications => Administration. The
Communication Administration window is displayed.
2-1
Figure 2-1
The Communication Administration Window
3. Click New. The CONTROL-M Definition window opens.

Figure 2-2
The CONTROL-M Definition Window
2-2
4. Specify parameter values in the fields.

Table 2-1
CONTROL-M Definition Window Fields
Field
Description
Enable
Specifies whether the CONTROL-M/Enterprise

Manager GUI is connected to the gateway that is
defined for this CONTROL-M installation.
CONTROL-M
Descriptive name for the CONTROL-M (maximum 20

characters; for example, HQ, PARIS, DIVISION-007).
The name should describe the specified
CONTROL-M installation and be easily recognized by
users.
Note: This name cannot contain blank spaces.
Code
Unique three-character code (for example, 999, NYC,

USA) used by CONTROL-M/EM and communication
software to identify each CONTROL-M.
Version
Version of CONTROL-M communication used. Refer

to the CONTROL-M release notes for the correct
version to include in this field.
AS/400: When defining an AS/400 data center, select
224 (or 225, if available).
Platform
List box value that specifies the CONTROL-M

platform type (for example, OS/390, Unix).
CONTROL-R
Installed
Specifies that CONTROL-R is installed in the

CONTROL-M installation (currently available in
CONTROL-M for OS/390).
Protocol
Specifies the type of protocol used to communicate

with the CONTROL-M (such as TCP). The options
that are available depend on the capabilities of the
CONTROL-M to which CONTROL-M/EM is
connected.
TCP/IP Host Name
Host name of the CONTROL-M.
2-3
Table 2-1
CONTROL-M Definition Window Fields
Field
Description
TCP/IP Port Number
TCP/IP port for communicating with CONTROL-M.

For all CONTROL-M installations other than OS/390,
the same port number must be specified here and in
the CONTROL-M communication parameter
CONTROL-M/EM TCP/IP Port Number.
Note: For CONTROL-M installations prior to versions
2.2.x, this parameter was called Output TCP/IP
Socket Port Number.
For OS/390 CONTROL-M installations, the same port
number must be specified here and in the ECSPARM
parameter PORT. For more information, see Set
IOAGATE Installation Parameters in Section 1,
Installation Procedure, in the OS/390 Gateway for
Enterprise Controlstation Installation and Security
Guide.
Contact
Name of person responsible for this CONTROL-M

installation. Optional.
Description
Optional text field.
Gateway TCP/IP
Host Name
Host name of the workstation containing the

CONTROL-M/EM gateway (WS-GTW) connected to
the CONTROL-M installation.
This field is updated automatically when the gateway
for the CONTROL-M installation is started.
Gateway TCP/IP Port

Number
Port number on the workstation containing the

WS-GTW used to connect to the CONTROL-M
installation.
This field is updated automatically when the gateway
for the CONTROL-M is started.
5. Click OK.
6. After defining new CONTROL-M installations, start the gateways
for each of these installations on the CONTROL-M/EM
workstation(s) hosting the CONTROL-M/EM Gateway Application
(WS-GTW). For more information, see Chapter 3, Maintaining
CONTROL-M/EM.
2-4
To modify CONTROL-M installation information:

administrator.
3. Select the CONTROL-M installation to update.
4. Click Update.
5. The CONTROL-M Definition window is displayed.
6. Change the desired values.
7. Click OK.
8. After updating details of a CONTROL-M installation (except the
Description or Contact field), restart the gateway for the
CONTROL-M using the Activation menu on the appropriate
CONTROL-M/EM workstation. Verify that the CONTROL-M is
connected. Its gateway must be restarted on the CONTROL-M/EM
workstation(s) containing the CONTROL-M/EM Gateway
Application (WS-GTW).
See Chapter 3, Maintaining CONTROL-M/EM, for more
information.
To enable/disable a CONTROL-M installation:
When a CONTROL-M installation is enabled, CONTROL-M/EM will

attempt to communicate with the CONTROL-M when the gateway is
restarted.
administrator.
2-5
3. Select the CONTROL-M installation that you want to enable or

disable.
4. Click Enable/Disable.
-orClick Update and select the Enable check box in the
CONTROL-M Definition window. Click OK.
To delete a CONTROL-M installation:

administrator.
3. Select the CONTROL-M installation definition to delete.
4. Click Delete.
A message similar to the following is displayed:
5. Click OK.
To refresh the Communication Administration window display:
Another user may change the status of a CONTROL-M installation as

displayed in the Communication Administration window. Click
Refresh to update the display in the window to show the current status of
the CONTROL-M in the communication database.
2-6
2-7
2-8
This chapter describes various features and functions required to

maintain the CONTROL-M/Enterprise Manager (CONTROL-M/EM)
environment. The following topics are included:
Component Descriptions
Starting and Stopping CONTROL-M/EM Components
Cleanup of Old Global Conditions
Gateway Log
CONTROL-M/EM Administrator Password
OS/390 Performance Analysis
Configuring ENTERPRISE/CS for Use with a Firewall
Hostname and Port Changes
Component Descriptions
Database Server (DB server)
A Sybase Adaptive Server, Oracle Server, or MSSQL Server that enables
the application to access the database. The database server is started as a
service on the computer on which it is installed. The database server
must be active before any of the other components is started.
3-1
Workstation Gateway (WS-GTW)

Process that handles communication between CONTROL-M/EM
workstations and CONTROL-M data center gateways (DC-GTW). A
WS-GTW can run only if the Database Server is running. WS-GTWs are
started/stopped by choosing Start => Programs => Enterprise
Controlstation => Administration Facility on the computer on which it
is installed.
Global Conditions Server (GCS)
Process that identifies and distributes global conditions used to create job
dependencies between CONTROL-M installations. The Global
Conditions Server can run only if the database server is running. The
GCS is started/stopped by choosing Start => Programs => Enterprise
Controlstation => Administration Facility on the computer on which it
is installed.
CONTROL-M/EM Graphic User Interface (GUI)
Central point of control for the enterprise production scheduling system.
An CONTROL-M/EM GUI can run only if the database server is
running. The CONTROL-M/EM GUI is started by choosing Start =>
Programs => Enterprise Controlstation => Enterprise
Controlstation on the computer on which it is installed. It is stopped by
choosing File => Exit. For more information, see Chapter 3,
Starting/Stopping CONTROL-M/EM, in the Enterprise Controlstation
User Guide.
CONTROL-M/EM Server
Process that handles communication between CONTROL-M/EM GUI
workstations and other CONTROL-M/EM components. The
CONTROL-M/EM Server can run only if the database server is running.
The CONTROL-M/EM Server must be started from the Administration
facility. For information, see Chapter 3, Starting/Stopping
CONTROL-M/EM, in the Enterprise Controlstation User Guide.
3-2
Global Alerts Server (GAS)

Process that identifies and distributes Alerts between CONTROL-M
installations and CONTROL-M/EM workstations. The Global Alerts
Server can run only if the database server is running. The GAS is started
from the Administration facility. For information on the Global Alerts
Server, see Chapter 11, Monitoring Alerts, in the Enterprise
Controlstation User Guide.
CONTROL-M/Desktop
Application that defines and manages job processing definitions,
Scheduling tables, and calendars. As a standalone application,
CONTROL-M/Desktop does not require the Database server to be
running. CONTROL-M/Desktop is started by choosing Start =>
Programs => Enterprise Controlstation => CONTROL-M/Desktop
or by choosing CONTROL-M/Desktop from the Tools menu in the
CONTROL-M/EM GUI. For information, see the CONTROL-M/Desktop
User Guide.
Orbix 2000 Server
Process that facilitates communication between the CONTROL-M/EM
Server and all connected CONTROL-M/EM GUIs, and between the
Global Alerts Server and Global Alerts Client windows. The Orbix
Daemon Server is started automatically as a service on the computer on
which it is installed.
CONTROL-M/EM installs the following components as manual
services. These components can be started as services using the
Administration Facility.
Global Conditions Server

Global Alerts Server
CONTROL-M/EM Server
Sybase Adaptive Server_<Server Name>
Orbix 2000 Server (Locator and Naming Services)
3-3
Starting and Stopping CONTROL-M/EM

Components
Starting any component requires the CONTROL-M/EM database to be
active. For components that are started automatically when accessed by a
user, the computer on which the component is installed must also be
active.
CONTROL-M/EM components are started and stopped using one of the
following methods:
The CONTROL-M/EM database server, the Orbix 2000 Server, and

the Administration agent are started/stopped automatically when the
Windows computer where the component is installed is
started/stopped.
The CONTROL-M/EM database server, the Orbix 2000 Server, and

the Administration agent are started/stopped automatically when a
script is run at startup and shutdown on a Unix machine.
A component is started/stopped automatically when a user

opens/closes the associated feature on an CONTROL-M/EM
workstation.
The Global Conditions Server, Global Alerts Service,

CONTROL-M/EM server, and CONTROL-M/EM Gateway are
started/stopped manually, from the workstation Start menu.
3-4
Stopping CONTROL-M/EM Processes

Normally, CONTROL-M/EM administrators and users are not authorized
to stop a running CONTROL-M/EM process on a computer running
Microsoft Windows. However, when troubleshooting, you may need to
stop an CONTROL-M/EM process.
To stop an CONTROL-M/EM process on a computer running Microsoft
Windows, you must have the required Windows security privileges. The
EnablePriv utility opens the Windows Task Manager window with the
privileges needed to stop CONTROL-M/EM processes. From this
window, you can stop any CONTROL-M/EM process.
Note
When the EnablePriv utility is used, you can shut down any process
running on the computer. Therefore, use the EnablePriv utility with
caution to avoid interfering with crucial system activity or crashing the
computer.
To stop an CONTROL-M/EM process:
1. Close the Task Manager window, if it is open. The EnablePriv
utility does not work if the Task Manager is open before the utility is
run.
2. Choose Start => Run to display the Run dialog box. Type
driveletter:\Ecsnt\MaintAgent\EnablePriv.exe taskmgr.exe in the
Open text box and click OK. The Task Manager is displayed.
3. In the Processes panel, select the CONTROL-M/EM process to be
stopped, such as maint.exe, the Administration Agent process. Click
End Process to stop the process.
4. Choose File => Exit Task Manager to close the Task Manager
window.
3-5
Automatic Program Startup and Shutdown

Generally, the programs essential to CONTROL-M/EM operation that
are installed on a Unix computer must be started manually after the
computer is booted up and stopped prior to shutdown. However, you can
automatically start and stop selected programs using scripts that you
create. It is your responsibility to create the scripts including parameters
that are described in this section.
Note
The programs that can be started and stopped automatically are the
Administration agent, the database server, and the Orbix Server
(IT Naming and IT Locator services). These programs are compose the
basic infrastructure on which CONTROL-M/EM runs. Automating their
startup and shutdown provides greater system stability.
You must supply different parameters for each of the supported Unix
platforms. Instructions for AIX are on page 3-7. Instructions for HP-UX
are on page 3-9. Instructions for Solaris are on page 3-10.
Note
You need to specify a command only if the program that the command
affects is installed on the computer.
For example, start_server is performed only on a computer on
which the database server is installed.
3-6
AIX
Start Programs
1. Change directories to \etc\.

2. Create a text file and save it in \etc\ with the name inittab.
Note
If there already is an initab file in \etc\, add the commands in Step 3 on

page 3-7 to the existing file.
3. Add one or more of the following commands:
su -<ecs_account> "-c start_orbix2000_services"

su -<ecs_account> "-c start_server"
su -<ecs_account> "-c ecs maint"
Stop Programs
1. Change directories to \etc\.

2. Create a text file and save it in \etc\ with the name rc.shutdown.
Note
If there already is an rc.shutdown file in \etc\, add the commands in Step

3 on page 3-7 to the existing file.
su -<ecs_account> "-c stop_orbix2000_services"
su -<ecs_account> "-c stop_server -U
<db_server_administrator_name> -P
<db_server_administrator_name>"
3-7
ecs ctl -U <CONTROL-M/EM_database_owner> -P

<CONTROL-M/EM_database_owner_password> -C Maint_Agent
-M <hostname> -cmd stop
3-8
HP-UX
Start Programs
1. Change to the \sbin\rc3.d directory.

2. Open a text editor and create a script with a name that conforms to
the following convention:
S<number><name> (for example: S123start)
su -<ecs_account> -c "start_orbix2000_services"
su -<ecs_account> -c "start_server"
su -<ecs_db_owner_account> -c "ecs maint"
Stop Programs
1. Change to the \sbin\rc2.d directory.

K<number><name> (for example: K123stop)
su -<ecs_account> -c "stop_orbix2000_services"
su -<ecs_account> -c "stop_server -U
3-9
Solaris
Start Programs
1. Change to the \etc\rc3.d directory.

S<number><name> (for example: S123start)
su -<ecs_account> -c "start_orbix2000_services"
su -<ecs_account> -c "start_server"
su -<ecs_account> -c "ecs maint"
Stop Programs
1. Change to the \etc\rc2.d directory.

K<number><name> (for example: K123stop)
su -<ecs_account> -c "stop_orbix2000_services"
su -<ecs_account> -c "stop_server -U
3-10
Cleanup of Old Global Conditions

The CONTROL-M database can retain old prerequisite conditions for up
to one year. However, prerequisite conditions are usually not required for
triggering jobs for more than a few days.
Retaining a large number of old prerequisite conditions in the
CONTROL-M database may degrade performance during download of
the Active environment from the CONTROL-M installation. Retaining
old Global prerequisite conditions can cause an overall degradation in
system performance.
It is highly recommended that when you define a CONTROL-M
installation, you also create a job processing definition in the
CONTROL-M installation to clean up old prerequisite conditions on a
regular basis. This can be accomplished using the CONTROL-M
ctmcontb utility, as demonstrated in the following example:
Figure 3-1
Example
Week Days
2,3,4,5,6
AutoEdit Assignment
%%A=%%CALCDATE %%DATE -10
%%B=%%CALCDATE %%DATE -5
%%A=%%SUBSTR %%A 3 4
%%B=%%SUBSTR %%B 3 4
Command Line
ctmcontb deletefrom %%A %%B
Note
This cleanup procedure is performed in CONTROL-M for OS/390 sites

using the IOACLRES utility. For more information, see the
INCONTROL for OS/390 Utility Guide.
3-11
Gateway Log
By default, all information and error messages displayed by a WS-GTW
are saved in a special log file, in directory
<home-directory>/ECS_HOME_NAME/log/. The Gateway Log file
name contains the following format:
Name of the CONTROL-M installation.

Current date.
Sequential number for the day. Default: 0.
To see the name of the current log file, open the Command Prompt
window running the gateway.
CONTROL-M/EM Administrator Password

The CONTROL-M/EM administrator (also known as the Database
Owner or DBO) effectively owns all CONTROL-M/EM programs and
database files. The CONTROL-M/EM administrator is responsible for
starting and stopping all CONTROL-M/EM components (except
CONTROL-M/EM GUIs). See Administrator Responsibilities on page
1-8, for a description of the administrator responsibilities.
The CONTROL-M/EM administrator user name and password are
defined during installation of the CONTROL-M/EM database. The user
name and password are required for accessing the CONTROL-M/EM
Server, Global Alerts Server, Global Conditions Server, Maintenance
facility, and CONTROL-M/EM gateways. During installation of these
components, the CONTROL-M/EM user name and password are stored
in the windir\system32\mcs.ini file on the appropriate computers.
Note
If you change the CONTROL-M/EM administrator password, you must

stop and restart the gateway for the change to be effective.
3-12
If you want to change the password of the CONTROL-M/EM

administrator, you need to obtain the encrypted equivalent of the
password and insert it into the mcs.ini file. You can do this using the
cryptocli utility described in the Administration Utilities chapter of the
Enterprise Controlstation Utilities Reference Guide.

Each mainframe gateway can be set to enable you to view information
about mainframe-workstation communication statistics. Such
information can help determine the source of communication problems.
To output communication statistics to mainframe Sysout:
Start the mainframe gateway with the following command:

S
ECSGATE,DEBUG=nnn
-or-
Modify the mainframe gateway with the following command:

F
ECSGATE,DEBUG=nnn
where nnn = 122 for download performance information, or 123 for an

information request (such as Log, Sysout) performance information.
3-13
Configuring ENTERPRISE/CS for Use with a

Firewall
ENTERPRISE/CS components can be spread across multiple machines,
and may be separated by firewalls.
To enable ENTERPRISE/CS components to communicate through a
firewall, you will need to:
1. Run the assign_ports script to assign port numbers for
ENTERPRISE/CS components that will make connections through
the firewall.
2. Using the firewall interface to open the necessary ports for incoming
communication to ENTERPRISE/CS components.
Running the assign_ports Script

The assign_ports script must be run on every computer that hosts the
components that you want to protect with firewall.
Note
The assign_ports script works on computers running Unix and on

computers running Microsoft Windows.
3-14
The assign_ports script can assign ports for the following

ENTERPRISE/CS components:
GUI Server
Global Alert Server
CLI utility
Orbix Naming Service
Orbix Locator
ENTERPRISE/CS GUI
CONTROL-M/Desktop
Use the following steps to run the assign_ports script:

Step 1
Ports can only be assigned for most components when they are not
active. Verify that components to be assigned ports are not active.
Note
Orbix components do not need to be stopped in order to assign ports for

them.
Step 2
On a computer that hosts one or more of the components in the above

bulleted list, enter the following command:
assign_ports
Step 3
The following text is displayed:

Configure ENTERPRISE/CS components for firewall
-------------------------------------------------------------------------------------------Welcome to the configuration utility of ENTERPRISE/CS components.
This application will walk you through the process
of configuring the following ENTERPRISE/CS components:
GUI Server
Global Alert Server
CLI utility
Orbix Naming Service
Orbix Locator
ENTERPRISE/CS GUI
CONTROL-M/Desktop
Press any key to begin :
3-15
Step 4
Press any key to continue. The following text is displayed:

ENTERPRISE/CS components
----------------------------Using a comma-separated list, select the set
of services you wish to configure in this installation.
[1] GUI Server
[2] Global Alert Server
[3] CLI utility
[4] Orbix Naming Service
[5] Orbix Locator
[6] ENTERPRISE/CS GUI
[7] CONTROL-M/Desktop
[8] No components, exit.
(For example: 1,3):
Note
The ENTERPRISE/CS GUI and CONTROL-M/Desktop are displayed in

the assign_ports script menu only when the script is run on computers
running Microsoft Windows.
Step 5
Specify the numbers of the components that you want to enable for use
with the firewall. Separate these numbers with commas.
Example
To configure the GUI Server, the Global Alert Server, and the Orbix
Naming Service, enter:
1,2,4
Step 6
Press <Enter>. The a message similar to the following is displayed for

each selected component:
Components [1]:
CLI utility communication port
----------------------------------------------CLI utility port [23077]:
Note
If you selected option 5 (Orbix Locator), a message is displayed

indicating the port that is already assigned to this component. You can
either keep the currently assigned port and open it in the firewall, or you
can assign a new port number for this component at this time.
3-16
Step 7
Press <Enter> to accept the default port value (in square brackets), or
type a different port number and then press <Enter>.
Note
When assigning a port to an Orbix component, certain additional

information messages are displayed.
When you have specified ports for all selected components, the word
Done is displayed, and the regular command prompt is displayed.
Registering the Assigned Ports with the Firewall
After assigning ports to all the necessary components (using the

assign_ports script):
Open these ports for incoming communication.

Verify that all ports on the current computer are open for outgoing
communication.
If communication between certain ENTERPRISE/CS components
and the Database server that is used by ENTERPRISE/CS will pass
through a firewall, the port that is used by the Database server must
be opened for incoming communication in the firewall.
This is relevant for the following ENTERPRISE/CS components:
GUI Server
Global Alert Server
Global Condition Server
Gateway
Reporting Facility
Command Line Interface (only for ctl requests)
3-17
If communication between certain ENTERPRISE/CS components

and a ENTERPRISE/CS gateway component will pass through a
firewall, the port that is used by the gateway must be defined using
the HostPort system parameter and then opened for incoming
communication in the firewall.
This is relevant for the following ENTERPRISE/CS components:
GUI Server
Global Alert Server
Global Condition Server
Command Line Interface (only for ctl requests)
For more information about the HostPort parameter, see See
HostPort on page C-2.
For information about how to register port numbers in your firewall, see
the documentation provided with your firewall software.
3-18
Hostname and Port Changes

The hostnames and port numbers of computers on which
CONTROL-M/EM server components are installed are recorded in
various CONTROL-M/EM parameters and files. If you change the
hostnames or port numbers of these computers or change the computer
on which one of these server components is installed, you must change
the hostname and port number wherever they are recorded. If you fail to
do so, those components may not be recognized by the
CONTROL-M/EM database.
Table 3-1 lists various CONTROL-M/EM server components and the
places where their hosts names are recorded.
Access and modify system parameters from the CONTROL-M/EM
System Parameters window of the Administration facility. For
information on modifying system parameters, see Displaying and
Modifying System Parameters on page 4-33. System parameters are
described in Appendix C, System Parameters.
The Defaults.rsc file is located in the site/resource/ directory on Unix
computers.
The Sybase Interfaces file is located in the /home/ DBOname/sybase/
directory. Modify this file by choosing Modify Interfaces File from the
Database Maintenance menu.
Table 3-1
Hostname Modification Locations
Server Component
Location
Global Conditions
Server
Defaults.rsc. Modify hostname in the line:

GCS
*
hostname
hostname
Enterprise License
Manager
hostname: LMGUI_LicenseHost parameter

port: LMGUI_LicensePort parameter
Database Server
Sybase: Interfaces file (on Unix), sql.ini file (on

Windows)
Oracle: tnsnames.ora file
MSSQL: sql.ini file
3-19
Table 3-1
Hostname Modification Locations
Server Component
Location
SNMP server
Snmphost parameter
Datacenter
Hostportlist parameter
3-20
Managing CONTROL-M/EM Using the

4
The status of remote CONTROL-M/EM components can be monitored
and modified from a central location using the CONTROL-M/EM
Administration facility. The Administration facility can also be used to
monitor and modify the CONTROL-M/EM database.
Each component to be monitored must be registered in the
Administration facility. For more information about component
registration, see Registering Components on page 4-15.
Note
The ENTERPRISE/CS Administrator account is the only user account

that has permission to use the Administration facility.
You can use the Administration facility to:
View and change the state of ENTERPRISE/CS components

registered in the Administration facility.
View a log of activities carried out by ENTERPRISE/CS

components that are registered in the Administration facility.
View and change the state of Administration agents.
View and modify the values of CONTROL-M/EM system

parameters.
4-1
Monitor and maintain the ENTERPRISE/CS database.
The Administration facility is installed together with a gateway, although

gateways can be installed alone. The Administration facility is part of a
default installation, as well as a part of other installation packages. You
can install the Administration facility only on a Windows computer.
Administration agents are installed automatically on each computer that
hosts one or more ENTERPRISE/CS components.
Each Administration agent interacts with the ENTERPRISE/CS
components on the computer on which it is installed. The agent supplies
component status information to the Administration facility window. The
agent also implements changes to the component that are specified by the
administrator using the Administration Facility window. Administration
agents are not visible to system users, interaction with the agents is
available only using the Administration Facility window.
Note
Administration Facility agents are implemented as services on Windows

and as daemons on Unix. Agents start automatically when Windows is
booted. Agent daemons on Unix must be restarted manually or by using a
script when the computer is rebooted. For information about manual
restart, see Activation Menu on page 5-3.
4-2
The Administration Facility window and agents communicate by writing

entries in the ENTERPRISE/CS database, that can be read and acted
upon. The agents write the current state (started, stopped, and so on) of
the components to the database and whether there are any warnings or
messages pertaining to the components. Using the Administration
Facility window, you can specify that a component be started or stopped.
This is the components desired state. This desired state is written to the
database by the window. The agent reads the desired state and starts or
stops the component, as requested.
Example
The agent on computer Mktg5 writes to the ENTERPRISE/CS database

that gateway GTW10 is stopped. The Administration facility window
checks the database and updates the window with this information. The
administrator sees the state of the gateway and changes the desired state
of the gateway to Up. The window writes the desired state to the
database. The agent reads the update information from the database and
starts the gateway so that its current state is compatible with the desired
state. The agent updates the database that the gateway has been started.
The Administration Facility window polls the database and updates the
information in the display window to indicate that gateway GTW10 has
started.
4-3
To access the Administration facility:

1. Double-click the Administration facility icon on the Windows
desktop.
-orChoose Programs => ENTERPRISE/CS => Administration

facility from the Start menu.
The Administration facility logon dialog box is displayed.
2. Enter the CONTROL-M/EM Administrator account username

and password in the dialog box.
3. Click OK. The Administration facility window is displayed.
4-4
From the Administration facility window, you can start and stop
components in the network, receive messages from agents about
components that are not functioning properly, and modify the view to see
only components that interest you.
4-5
Component Types
The Administration facility is used to administer the following
ENTERPRISE/CS component types:
GUI Server. Central point of control for the enterprise production

management system. An CONTROL-M/EM GUI server can run only
if the Database server is running.
Multiple GUI servers can be registered in the Administration facility
and can be active simultaneously.
Gateway. Handles communication between

CONTROL-M/Enterprise Manager and CONTROL-M. Multiple
gateways can be registered in the Administration facility and can be
active simultaneously.
Global Conditions Server. Identifies and distributes global

conditions that are used to create job dependencies between
CONTROL-M installations. The Global Conditions server can run
only if the Database server is running.
Multiple Global Conditions servers can be registered in the
Administration facility, but only one can be active at any given time.
Global Alerts Server. Process that identifies and distributes Alerts

between CONTROL-M installations and CONTROL-M/EM
workstations. The Global Alerts server can run only if the Database
server is running. It is started automatically when a user opens an
associated Global Alerts client window on an CONTROL-M/EM
workstation.
4-6
Administration Facility Window

All registered components are managed using the Administration facility
window. The Administration facility window has two panes (display
areas). The left pane displays the components registered with the
Administration facility in tree view. The right pane displays the same
components in a detailed table view.
Tree View (Left Pane)
Information about components that are running on each computer can be

viewed with either of the following display types:
Machine - Component Types view option. Name of host computer

-> Type of component -> Name of component
Component Types - Machine view option. type of component ->

Name of host computer -> Name of component
4-7
Figure 4-1
Tree Views
4-8
To select a tree view:
Click
for Computer => Component Type view or

Component Type => Computer view.
for
-orChoose View => Tree View, and select the desired view option.
Note
The tree view of the Administration Facility window can be expanded

and contracted by clicking on the + and - signs at each level of the
hierarchy. Clicking on a + symbol expands a branch of the tree, exposing
the nodes underneath. Clicking a - symbol hides the nodes of the branch.
4-9
Table View (Right Pane)
Each row of the table view of the Administration Facility window

contains information about one component in the network.
Note
To sort rows according to a column in the table, click on the column

header (title).
The following table describes the columns in the table view of the
Administration Facility window.
Column Title
Description
Component Type
Type of component in the row. For more information

about component types, see Component Types on
page 4-6.
Name
Name of the component. Relevant to gateways only.
Running On
Name of the computer where the component is

installed.
Current State
Current state of the component, as reported by the

appropriate Administration Facility agent.
Desired State
Desired state of the component, as specified by the

administrator.
4-10
Column Title
Description
Last Checked
The time when the components state was last checked

by the Administration Facility agent.
Message
Messages that were generated about the component by

the Administration Facility agents.
Agent Status
Reports the operational status of the Administration

agent on the component host computer.
Component States
Current State
The current state is the state most recently reported for each registered
component by its Administration agent. Current states are displayed in
the Administration facility window. The possible states that can be
displayed for a component are:
State
Description
Up
The component is active (started).
Down
The component is not active (stopped).
Hanging
The component is not functioning, but it has not shut down.
Warning
The component appears to be malfunctioning.
Desired State
The desired state is determined by the administrator in the

Administration facility window. The possible states that can be specified
for a component are:
State
Description
Up
The component should be active (started).
Down
The component should be inactive (stopped).
Ignored
No desired state is specified for this component. As long as

this state is not changed, the Administration facility does not
attempt to modify the state of this component.
4-11
Icons and Colors
The Administration Facility window uses icons and colors to help you
quickly determine the states of the components on your network. These
are described in Figure 4-1 on page 4-8.
Tree View
In the tree view, the top two levels (computers and component types) are
marked by high-level status icons: green check marks
or red
exclamation points
.
A check mark indicates that the current state of all components of

the computer or component type match the desired state for those
components.
An exclamation point indicates that the current state does not match
the desired state of at least one component of the computer or
component type.
At the bottom level in the tree view, each component is marked by an

icon that describes the state of that component.
A green Up arrow
indicates that both the components current
state and desired state are Up.
A transparent (the same color as the window background color)

Down arrow
indicates that both the components current state
and desired state are Down.
A yellow arrow
indicates that the current state of the component
is Warning. The direction of the yellow arrow indicates the current
state of the component.
A red arrow
indicates that the current state and the desired state
of the component are not the same, and that the Administration
Facility agent for the component has not successfully started or
stopped the component to match the desired state. The direction of
the red arrow indicates the current state of the component.
4-12
A diamond
indicates that the components current state is
Ignored. Diamonds are always transparent.
Table View
Each row in the window table describes a component in the network. An

icon is included in the Component Type column, to help identify the
component type.
Table 4-1
Component Type Icons
Icon
Component Type
Gateway
GUI Server
Each of these icons is colored to indicate the status of the component.

Table 4-2
Color for Component Type Icons
Color
Description
Green
Current state and desired state are both UP.
Transparent
Current state and desired state are both DOWN.
Red
Current state and desired state do not match.
Yellow
Current state of the component is WARNING.
Starting and Stopping Components

ENTERPRISE/CS components that are registered in the Administration
facility can be stopped or started through the Administration facility
window. The Administration Facility agent, located on the computer
together with the component, implements the desired action.
Use one of the following methods to start or stop a component using
the Administration facility window:
4-13
Select the component by clicking the component icon in the tree

view or the table view. Click Up
to start the component; click
Down
to stop the component. To ignore the state of the
component, click Ignore
.

view or the table view. Choose Component => Update Component
from the menu to display the Component dialog box. Select Up,
Down, or Ignored from the Desired State list box. Click OK.
By double-clicking the component icon in the tree view or in the

table view to display the Component dialog box. Select Up, Down,
or Ignored from the Desired State list box. Click OK.
Note
Select the Ignored option from the Desired State list in the Component
if you do not care whether the component is up or down.
After performing any of the above procedures, the new desired state is
displayed in the Desired State column in the table view, and the
CONTROL-M/EM database is updated to indicate the desired status. The
relevant Administration Facility agent detects the update request and
attempts to start or stop the component, as requested.
The agent attempts to change the component state until either the desired
state matches the current state, until Ignored is selected as the desired
state, or until it has performed the number of attempts determined by the
ActiveRetries parameter. For information on modifying the value of this
parameter, see Table C-5, Maintenance Parameters, on page C-10.
The agent makes each attempt to start the component at an interval of
time that you can modify from the Administration Facility Options
dialog box. The range of time is from three to ten minutes. The default
value is three minutes.
To change the Component Restart interval:
4-14
1. Choose Tools => Options. The Options dialog box is displayed.

Figure 4-2
Administration Facility Options Dialog Box
2. Specify a value from 3 to 10 minutes in the Component Restart

Interval text box.
3. Click OK.
Registering Components
There are two methods for registering ENTERPRISE/CS components in
the Administration facility. The Build From Network method registers
all components that are running but which have not yet been registered.
The New Component method enables you to add individual components
manually.
4-15
An ENTERPRISE/CS component located on the network does not have

to be registered in the Administration facility in order to run.
Note
To delete (unregister) a registered component, select the component in

the Administrator Facility window, and press <Delete>.
-orSelect the component and then choose Delete Component from the
Component menu.
-orSelect the component, and click
To register new components in the Administration facility with Build

from Network:
Click
on the toolbar.
-or-
Choose Component => Build From Network from the menu.

The process may take a few minutes, depending on the size of the
network.
Note
The Build from Network automatically specifies attribute information

for each component in the network. This information can be altered
manually by selecting the component in the Administration facility
window and performing Update Component. For more information, see
Updating Information about Registered Components on page 4-21.
To register new components in the Administration facility one at a
time:
4-16
1. Choose Component => New Component from the menu. The

Component dialog box is displayed.
-orClick
Figure 4-3
. The Component dialog box is displayed.
Component Dialog Box
4-17
2. Enter information about the component to be registered. The fields of

the Component dialog box are described in Table 4-3, Component
ID, on page 4-19.
3. Click OK.
4-18
Component Dialog Box
The Component dialog box contains the following fields:

Table 4-3
Component ID
Field
Description
Type
Component type. Valid values:

gateway
GAS (Global Alert Server)
GCS (Global Condition Server)
GUI Server
Name
Unique name for the component.
Table 4-4
Running on...
Field
Description
Machine Type
Type of platform on which the component is installed

(such as Unix).
Machine Name
Unique name for the host computer of the component.
Table 4-5
State
Field
Description
Current
State
Current state of the component. This setting cannot be modified

by the user.
Desired
State
Preferred state for the component. Valid values:

Up (start)
Down (stop)
Ignored
Last
Update
Time when the Administration Facility agent last updated the

database with component information. This state cannot be
modified by the user.
4-19
Table 4-5
State
Field
Description
Text
Message
Message about the component, recorded in the database by the

Administration Facility agent. This value cannot be modified by
the user.
Check
Interval
Time interval after which the Administration agent checks the

component and reports its status to the CONTROL-M/EM
database. Default: 10 seconds.
This state applies only to this component and its agent. (It is not
automatically applied to other components of the same type.)
Table 4-6
Startup
Field
Description
Command
Command line used for starting the component. This value is

entered automatically, based on the component type,
component name, and computer type. This value cannot
normally be modified by the user.
Override
Manually
Allows the user to modify the Command line.
Additional
Parameters
Additional parameters added to the command line (for

example, debugging, trace).
4-20
Updating Information about Registered Components

Component information is updated from the Component dialog box. The
Component dialog box is described in Registering Components on
page 4-15. Use one of the following methods to access this dialog box:

view or in the table view. Choose Component => Update
Component from the menu. The Component dialog box is
displayed. Add or modify information as necessary. Click OK.
-or-
Display the Component dialog box by double-clicking the

components icon in the tree view or in the table view.
-or-
Select the component by clicking the components icon in the tree

view or in the table view.
-or-
Click
For more information about fields of the Component dialog box, see
Component Dialog Box on page 4-19.
Selecting and Filtering Components

By default, the Administration Facility window displays all registered
components. However, you can choose to display only selected
components using the Filter Manager. To filter the Administration
Facility window, create a new filter or select an existing one. The
window displays all registered components that meet the criteria
specified in the filter. The name of the current filter is displayed in the
window title bar.
4-21
To create a filter:
1. Choose Tools => Filter Manager to display the Filter Manager
dialog box.
2. Click New.
3. The Filter Properties dialog box is displayed.
4-22
Figure 4-4
Filter Properties Dialog Box
4. Enter a unique name for the new filter.

5. Fill in the desired criteria in the dialog box. For information about
the fields in this dialog box., see Table 4-7, Fields of the Filter
Properties Dialog Box, on page 4-25.
6. Click OK. The Filter Manager dialog box is displayed.
7. Select the name of the new filter. Click Set Filter to apply the
selected filter.
To select an existing filter:
dialog box.
2. Select the name of the filter you want.
3. Click Set Filter to apply the filter. Components that match the filter
criteria are displayed in the Administration Facility window.
4-23
To modify an existing filter:

dialog box.
2. Select the name of a filter to modify.
3. Click Update to display the Filter Properties dialog box.
4. Make the desired changes in the Filter Properties dialog box. For
information about the fields in this dialog box, see Table 4-7, Fields
of the Filter Properties Dialog Box, on page 4-25.
5. Click OK to return to the Filter Manager dialog box. The changes
to the filter are saved.
6. Select the filter name and click Set Filter in the dialog box to display
the modified filter.
-orSelect a different filter to modify and return to Step 3.
All filter criteria are optional. If a variable is not necessary for a filter
definition, do not enter any information in the field for that variable.
Note
The All Components filter is the default filter. It displays all registered
components in the network. It cannot be deleted or modified. When the
All Components filter is selected, the Update and Delete buttons in the
Filter Manager dialog box are not available.
4-24
Table 4-7
Fields of the Filter Properties Dialog Box
Field
Description
Filter Name
Name of the filter.
Machine
Name
Name or mask of the computer (or computers) whose

components are to be displayed. For example, Saturn%
specifies all computers whose names start with Saturn.
Component
Type
Component types to be displayed.
Component
Name
Name or mask of the components to be displayed.
Current
State
Current component state. Valid values: Up, Down, Hanging,

Ignored, and Warning.
Desired
State
Desired component state. Valid values: Up, Down, and

Ignored.
Note
Multiple components or computers can be specified using wildcards. The

wildcards recognized by the Filter Manager are % or ?, where %
represents any single-character or multi-character string, and ? represents
any single character. Wildcards can appear at any place in the text string.
4-25
Administration Facility Check Intervals

Two types of intervals can be specified for the Administration facility.
Administration Facility Window interval. The amount of time

between periodic checks of the CONTROL-M/EM database by the
Administrator facility. These checks are performed to detect
messages and component state changes recorded by Administration
Facility agents.
Administration Facility Agent interval. The amount of time

between periodic checks of each components state by the
Administration Facility agent. The agent records changes and
relevant messages in the CONTROL-M/EM database.
To modify the Administration Facility Window interval:
Choose Tools => Options. In the Options dialog box, enter a number
between 1 and 3600 (seconds) in the Database Polling Interval text
box. Click OK. The Options dialog box is displayed in Figure 4-2 on
page 4-15.
To modify the Administration Facility Agent interval:
Open the Component dialog box for the selected component, as

described in Updating Information about Registered Components on
page 4-21. Enter a value between 1 and 3600 (seconds) in the Check
Interval text box. Click OK. The Component dialog box is displayed in
Figure 4-3 on page 4-17.
Note
The default value for both intervals is 10 seconds. Setting an interval

shorter than this is not recommended.
4-26
Using the Agents Log

The Agents Log contains records of actions performed by the various
Administration agents on the network. The Agents Log window can be
filtered so that it shows only records that conform to specific criteria.
To display the Agents Log:
Choose Tools => Agents Log.

Figure 4-5
Agents Log
Records in the Agents log contain the information listed in Table 4-8:
4-27
Table 4-8
Agents Log Information
Heading
Description
Agent
Name of the component or computer.
Time
Time when the event occurred.
Events
A description of an event. The most common log messages are

described in Table 4-10.
Click Clear to empty the Agents Log.

Note
When the log is cleared, all entries in the log are deleted. For more
information, see Filtering the Agents Log on page 4-31.
Agent Log Messages
Messages displayed in the Agent Log describe the activities of the

Administration agents.
Many messages include a variable or a code that identifies the
component that prompted the message. The codes are described in
Table 4-9:
Table 4-9
Agents Log Message Codes
Heading
Description
<component>
Variable that is replaced with the type of CONTROL-M/EM

component for the message. For a gateway, the logical
name of the gateway is also displayed.
PID
process identification number of the component in the

CTLPort
Port number which the component uses to listen to the

CONTROL-M/EM environment.
4-28
Each message in the Agent Log has a detail level assigned to it. The
CONTROL-M/EM administrator can modify the value of the
LogInfoLevel parameter to specify that only messages with a specified
detail level (or lower) should be displayed. For information on the
LogInfoLevel, see Table C-5, Maintenance Parameters, on page C-10.
The parameter is modified using the System Parameters window of the
Administration facility, described on page 4-33.
Table 4-10
Agent Log Messages (Part 1 of 2)
Detail
Level
Message
Description
Starting checks for <component>.
The agent has begun to check the state of the

specified component.
Checks for <component>

terminated.
The agent has finished checking the state of the

specified component.
No commreg details for

<component>.
The Administration agent can not find the specified

component in the table that enables communication
with the component. This may be because the
component was recently started and has not yet
attempted to establish communication with
CONTROL-M/EM.
<component> PID=<PID_number>
CTLPort=<port_number> is OK.
The status of the component was successfully

changed to the specified desired state.
CTLPort=<port_number> is
Ignored.
The status of the component is Ignored.
CTLPort=<port_number> SHOULD
BE DOWN! Trying to stop.
The Administration agent is attempting to stop the

process of the specified component. This attempt is
repeated until either a number of retries are
performed or the process is successfully stopped. If
the specified number is reached, as specified by
the StopTries parameter, the Agent attempts to kill
the process.
BE DOWN! Trying to terminate.
The Administration agent is attempting to kill the

process of the specified component. This continues
until a number of unsuccessful retries are
performed. When the retries are exhausted, manual
intervention is required.
4-29
Table 4-10
Agent Log Messages (Part 2 of 2)
Detail
Level
Message
Description
BE DOWN! All retries failed. Check
manually.
The Administration agent has made five

unsuccessful attempts to kill the process. This
value is not configurable.
BE UP! Trying to activate.
The Administration agent is attempting to activate

the process of the specified component.
BE UP! Waiting for restart interval
to expire.
The Administration agent is waiting for the time

interval to expire between an attempt to start a
component and the next attempt.
BE UP! Activate retries exhausted.
The Administration agent has made the maximum

number of unsuccessful attempts to start the
component. The administrator must identify and
correct the problem that is preventing the
component from working, change the components
desired state to Ignored for a brief period, and
again specify the desired state to Up.
Logon to database successful.
The agent has logged on to the database.
No components found.
The agent did not find any components.
MaintAgent stopped manually.
The Administration agent was stopped by a user

using the ctl utility.
Shut down in progress.
The Administration agent and the CONTROL-M/EM

components on the host machine are shutting
down. This is done using ctl -shutdown.
4-30
Filtering the Agents Log

By default, the Agents Log displays activities of all Agents in the
network. Use the filter options to display a select sample of entries.
Selecting the Filter check box engages the filter options.
The options are:
Filter
Option
Agent
Description
Component name or computer name for which to display log
records.
Note: A mask can be specified for this field using wildcards. The
wildcards recognized by the Agent Log filter are % and ?. Where:
% represents any number of alphanumeric characters, and ?
represents any single alphanumeric character. Wildcards can
appear at any place in the text string.
Entry
Text
An alphanumeric string that should appear in the Events column

of the displayed Agent log records. Wildcards can be used to
obtain a range of cases.
For example, %Start% would select all records that have the
string Start anywhere in the Activities column of the Agents log.
The filter is case-sensitive.
Click Apply to apply the filter.

Truncating the Agents Log
You can limit the number of days that entries are kept in the Agents Log.
Specifying a number of days that entries are saved deletes all entries that
are older than the specified number of days. The default is 3.
To change the number of days that entries are kept in the Agent log:
1. Choose Tools => Options. The Options dialog box is displayed. for
an illustration of the dialog box, see Figure 4-2 on page 4-15.
2. Specify a number (of days) in the Delete Log Entries Older Than n
days text box.
4-31
3. Click OK.
4. Stop and restart the administration agent. The Agents log is
truncated. For information on starting and stopping the
administration agent, see Gateway Verification Utility (check_gtw)
on page 7-11 or Activation Menu on page 5-3 (Unix, only).
4-32
Displaying and Modifying System Parameters

CONTROL-M/EM system parameters are used to configure the
programs behavior in a wide range of operations. All CONTROL-M/EM
system parameters can be displayed and modified using the
Administration facility. Each parameter is associated with a specific area
of CONTROL-M/EM operation.
All system parameters are listed and described in Appendix C, System
Parameters.
To display the CONTROL-M/EM System Parameters window:
4-33
Choose Tools => System Parameters. The CONTROL-M/EM System

Parameters window is displayed.
Figure 4-6
CONTROL-M/EM System Parameters Window
The columns of this window are described in Table 4-11.
4-34
Table 4-11
CONTROL-M/EM System Parameters Window Columns
Heading
Description
Type
Name of the CONTROL-M/EM component that is configured

by the parameter. This value cannot be modified by the user.
Note: Some parameter groups (such as General
parameters) are not associated with any one component.
Name
Name by which the parameter is recognized by

CONTROL-M/EM processes.
Component
Name of an CONTROL-M/EM component type that is

affected as a result of the condition that is created. Any
CONTROL-M/EM component type can be chosen and
modified from the Component list box in the Update/View
Parameter window, shown in Figure 4-7 on page 4-37.
This element is used only to create conditional parameter
settings. Default: *.
Comp. Name
Name of a data center (CONTROL-M installation). The

Comp. Name text box of the Update/View Parameter
window, shown in Figure 4-7 on page 4-37, can hold 50
characters of text. This element is used only to create
conditional parameter settings. Default: *.
Host
The host name of the specified computer. If you want to

modify this value, an entry of up to 100 characters can be
entered in the Host Name text box of the Update/View
Parameter window, shown in Figure 4-7 on page 4-37.
This element is used only to create conditional parameter
settings. Default: *.
Value
The value of the parameter. If you want to modify this value,

an entry of up to 100 characters can be entered in the Value
text box of the Update/View Parameter window shown in
Figure 4-7 on page 4-37.
System parameters are modified using the Update/View Parameter

window. Two kinds of modifications can be made.
The value of a parameter can be modified, so that the new value

applies in all circumstances.
4-35
The value of a parameter can be modified so that the modification

takes effect only when a specified network configuration is used. The
conditional value is substituted for the default value when a
condition you created is met.
Use the latter method when an CONTROL-M/EM component is hosted

by a machine with particular requirements or abilities.
Note
Multiple conditions can be specified for a single parameter.

If you specify a parameter value to be used only when a certain condition
is met:
The alternate value is used if the condition is met.

The default value is used if the condition is not met.
To modify an CONTROL-M/EM System Parameter unconditionally:

1. In the open CONTROL-M/EM System Parameters window,
double-click the table row corresponding to the parameter that you
want to modify. The Update/View Parameter window is displayed.
The information corresponding to the parameter whose row you
clicked is displayed in the fields of the window.
The fields in this window correspond to the columns of the
CONTROL-M/EM System Parameters window having essentially
the same names. For a description of these fields, see Table 4-11,
CONTROL-M/EM System Parameters Window Columns, on page
4-35.
The only exceptions are the Modify Value Only, Modify Condition,
and Add Condition options, which are explained in the following
steps.
4-36
Figure 4-7
Update/View Parameter Window
2. The Modify Value Only option is selected by default. Select this

option if another option is already selected.
3. Replace the value displayed in the Value text box with any valid
value for the selected parameter. None of the other fields can be
modified.
4. Click Save. The CONTROL-M/EM System Parameters window is
displayed. The value you specified will appear in the Value cell of
the table row you selected.
4-37
To specify a conditional value for an CONTROL-M/EM system

parameter:
double-click the table row of the parameter for which you want to
specify a conditional value. The Update/View Parameter window is
displayed.
Figure 4-8
2. Select the Modify Condition option button. The Component,

Comp. Name, and Host Name fields become available.
3. Change one or more of the following variables:
To specify a value to be used only with a specific component

(such as the gateway), select the component type from the
Component list box.
4-38
If you selected the gateway component type from the

Component list box, you can specify to which gateway you are
referring by entering its name in the Comp. Name text box. The
Comp. Name text box is used only when gateway is chosen
from the Component list box.
To specify which computer the component you selected is

running on, enter the computers logical name in the Host Name
text box. IP addresses are not supported in this text box.
4. Specify a value in the Value text box. The Type and Name fields
cannot be modified.
5. Click Save. A new row is displayed in the parameter table of the
CONTROL-M/EM System Parameters window with the condition
and the value that you specified.
Note
You cannot add a condition to the default row for the parameter that you
selected. To add a conditional setting, you must add a new row to the
table. As a result, both the default row and the conditional row are
displayed in the table.
Example
The Global Alerts Server (GAS) is installed on two different computers

in your network, CMPMAIN and CMPBKUP. Generally, only the GAS
on CMPMAIN is active.
The NumberOfLogFiles GAS parameter (which determines the number
of log files in use) is set to 3. This indicates that every GAS in the
network maintains three log files. However, the GAS on CMPBKUP is
used as a GAS host only for short periods when CMPMAIN is down for
maintenance. You want to indicate that only one log file is needed for the
GAS on CMPBKUP.
After displaying the Update/View Parameter window, add a new entry
to the system parameters table, with the Comp. Name CMPBKUP and
the Value 1. This indicates that, when active, the GAS on CMPBKUP
maintains one log file. Any other GAS on the system maintains the usual
three log files, when active.
4-39
To modify a conditional setting for a parameter:

double-click the table row corresponding to a parameter for which
you have already specified a conditional setting. The Update/View
Parameter window is displayed.
Figure 4-9
2. Select the Add Condition option. The Component, Comp. Name,

and Host Name fields become available.
3. Change one or more of the following variables:
If you want to specify that a parameter has a specific value only

when a specific component is being used (such as the gateway),
select the component type from the Component list box.
4-40
If you selected the Gateway component type from the

Component list box, you can specify to which gateway you are
referring by entering its name in the Comp. Name text box. The
Comp. Name text box is used only when Gateway is chosen
from the Component list box.
If you want to specify which computer the component you

selected is running on, enter the computers logical name in the
Host Name text box. IP addresses are not supported in this text
box.
4. Specify a value in the Value text box. The Type and Name fields
cannot be modified.
5. Click Save. The modifications are displayed in the cells of the
selected row in the parameter table of the CONTROL-M/EM System
Parameters window.
Example
The Global Alerts Server (GAS) is installed on two different computers

in your network, CMPMAIN and CMPBKUP. Generally, only the GAS
on CMPMAIN is active.
The NumberOfLogFiles GAS parameter (which determines the number
of log files in use) is set at 3. This indicates that every GAS in the
network maintains three log files. The GAS on CMPBKUP is used as a
GAS host only for short periods when CMPMAIN is down for
maintenance, and you have created a conditional parameter setting for
NumberOfLogFiles that maintains only one log file.
Recently, CMPBKUP was upgraded with a larger hard drive, and you
want the GAS to maintain two logs files, when active.
Click on the conditional parameter setting in the systems parameter table
to display the Update/View Parameter window, and modify the Value
to 2, without changing the value for Comp. Name, CMPBKUP. When
the GAS on CMPBKUP is active, it now maintains two log files. Any
other GAS on the system maintains the usual three log files, when active.
Note
Parameter entries that you added to the system parameters table in the
CONTROL-M/EM System Parameters window can be deleted by
4-41
selecting the row and pressing the Delete key. Default parameter rows
cannot be deleted.
4-42
Database Administration
The ENTERPRISE/CS database requires periodic maintenance to ensure
efficient operation of ENTERPRISE/CS. The Administration facility
includes tools for performing this maintenance. These tools are located
on the Database menu.
Each database task in this menu is described below.
Removing Old Alerts

Alerts posted to the Global Alert Client window must be periodically
erased from the CONTROL-M/EM database.
1. To remove old alerts, choose Database => Remove Old Alerts.
2. Click the Date list box. A calendar is displayed:
4-43
3. Click on the selected date. The calendar is closed and the date is
entered automatically into the Date list box.
4. Click OK.
All alerts posted prior to the specified date are deleted from the
CONTROL-M/EM database. If an alert was posted prior to the specified
date, but was updated after that date, it is not erased.
Extending the Database

Extend Database is used to increase the size of the data or log segment
of the CONTROL-M/EM database. It is recommended to extend the
database if the amount of free space falls below 20%. Use the
Check Space function (page 4-47) to monitor the amount of free space
remaining
Different dialog boxes are displayed depending on the type database
server by which the database is hosted.
Note
When CONTROL-M/EM is connected to an MSSQL database, the

Extend Database function is not available.
4-44
To increase the size of a data or log segment:

1. Choose Database => Extend Database. The CONTROL-M/EM
Database Extend dialog box is displayed.
Figure 4-10 CONTROL-M/EM Database Extend (Sybase and MSSQL)
2. Enter the required information described in Table 4-8 in the fields of

the CONTROL-M/EM Database Extend dialog box:
Table 4-12
CONTROL-M/EM Database Window (Sybase and MSSQL)
Element
Description
Data or Log
Specifies either the Data or the Log segment to extend.
Size
Specifies a size (in MB) for the database segment.
File Name
Specifies the path and name for the segment that is being
modified.
If you are using an Oracle Database Server, the CONTROL-M/EM

Database Extend dialog box that is displayed is shown in Figure
4-11 on page 4-46.
4-45
Figure 4-11 CONTROL-M/EM Extend Database (Oracle)
Table 4-13
CONTROL-M/EM Extend Database Dialog Box (Oracle)
Element
Description
Table Space
Name
Type of the tablespace to extend or create.
Extension
Size (MB)
Specifies the size (in MB) that the database segment will be
extended.
Extend
Existing File
Extends an existing database file.
Add New File
Creates a new database file.
Data File
Name
Specifies the path and name for the segment that is being
extended or created.
3. Click OK to implement the new database segment.

Note
You must specify the password for the DBA superuser to access this
window. This option can be selected while CONTROL-M/EM is active.
4-46
Checking Available Space

It is recommended that the amount of available space in the
CONTROL-M/EM database be checked on a regular basis with the
Check Space option. If the available space falls below 20%, the database
should be extended or old downloads should be deleted.
There is no recommended frequency for checking database space. It
should be noted, however, that CONTROL-M/EM may not function
properly when the database is full.
Note
When CONTROL-M/EM is connected to an MSSQL database, the

Check Space function is not available.
SQL Client
Starts an interactive SQL session so that you can issue direct SQL
commands and perform troubleshooting and fixes under special
circumstances.
Note
This option should only be used when specifically requested by BMC

Software Technical Support.
Print Server Configuration

Captures the configuration parameters of the Sybase Adaptive Server and
writes them to a file that can be printed. Prompts for a file name. This is
not available for the Oracle Server.
4-47
4-48
Managing CONTROL-M/EM with the

Root Menu
5
Selected CONTROL-M/EM administration tasks can be carried out from
the Unix command line if the CONTROL-M/EM database or other
CONTROL-M/EM components are hosted on Unix computers. For
example, if the database is on a Unix computer, tasks listed in the
Database Maintenance menu can be performed .
CONTROL-M/EM Root Menu

Managerial tasks performed in CONTROL-M/EM are authorized only
for the CONTROL-M/EM administrator or database administrator. The
CONTROL-M/EM administrator was defined during installation and is
protected by a password. These managerial tasks are accessible from the
CONTROL-M/EM root menu. For more information, see the description
of each function.
5-1
To access the root menu:

Note
The database server be running for the root menu and the root menu
submenus to be displayed.
1. From the Unix prompt of a CONTROL-M/EM host computer, enter
the following command:
root_menu
You are prompted for the CONTROL-M/EM administrator username
and password.
2. Enter the appropriate username and password. The following menu is
displayed:
Root Menu
--------------Select one of the following options:
1
2
3
4
5
Activation Menu
Troubleshooting Menu
New Window
Database Creation Menu
Database Maintenance Menu
The menu options are described Table 5-1.

Table 5-1
Root Menu - Description
Option
Description
Activation Menu
Displays the Activation menu, described on page

5-3.
Displays the Troubleshooting menu, described in
Chapter 7, Troubleshooting.
New Window
Opens an Xterm window.
5-2
Table 5-1
Root Menu - Description
Option
Description
Database Creation
Menu
Displays the Database Creation menu, described

on page 5-6.
Database Maintenance
Menu
Displays the Database Maintenance menu,

described on page 5-27.
Most of the functions in the Activation, Troubleshooting, Database

Creation, and Database Maintenance menus are available only to the
CONTROL-M/EM administrator.
Activation Menu
The Activation menu starts and stops the CONTROL-M/EM
Administration agent, the Orbix Server (Naming and Locator services),
and the database server. It also performs the Check All function.
Only Check All can be performed by any CONTROL-M/EM user. All
other Activation menu functions are available only to the administrator.
The Activation menu has certain limitations:
The menu options influence only local components.

For Stop Database Server to succeed, you must first stop the
Administration agent.
Orbix Server options are displayed on the Activation menu only
when the Orbix Server is installed locally.
5-3
Select Activation Menu from the root menu to display the following
menu:
Activation Menu
1
2
3
4
5
7
8
9
10
p
q
Check All
Start All
Start Database Server
Start Orbix Services
Start Administration Agent
Stop All
Stop Database Server
Stop Orbix Services
Stop Administration Agent
Previous Menu
Quit
Table 5-2
Activation Menu Options
Menu Option
Description
Check All
Checks the status of all CONTROL-M/EM core

components and displays the results. These components
include:
database server
gateway
Orbix ITLocator and ITNaming processes
GUI Server
Administration agents
Start All
Starts the database server, the Orbix Locator and Naming

processes, the Administration agent.
Start Database
Server
Starts the database server, if it is located on the local

computer.
Start Orbix
Services
Starts the Orbix Locator and Naming processes.

Note: This menu option appears only if the
CONTROL-M/EM GUI Server is installed on the same
computer.
Start
Administration
Agent
Starts the administration agent .
5-4
Table 5-2
Activation Menu Options
Menu Option
Description
Stop All
Stops the database server, the Orbix Locator and Naming

processes, and the administration agent.
Stop Database
Server
Stops the database server, if it is located on the local

computer.
Stop Orbix
Services
Stops the Orbix Locator and Naming processes.

Note: This menu option appears only if the
CONTROL-M/EM GUI Server is installed on the same
computer.
Stop
Administration
Agent
Stops the administration agent.
5-5

When the CONTROL-M/EM database is installed on a Unix computer,
you can perform some database management functions from the Unix
prompt.
Note
Alternately, you can perform many of these management functions from

the Administration facility (a part of the CONTROL-M/EM GUI) that is
installed on Microsoft Windows. For more information about the
Administration facility, see Chapter 4, Managing CONTROL-M/EM
Using the Administration Facility.
Select Database Creation Menu from the root menu. The following menu
is displayed:
Note
Only the CONTROL-M/EM administrator can use Database Creation

Menu options.

---------------------Select one of the following options:
1 - Build Database
2 - Delete Database
p - Previous Menu
q - Quit
Enter option number --->
The Database Creation menu options are described Table 5-3:
5-6
Table 5-3
Database Creation Menu Options
Build Database
Builds (or rebuilds) the entire CONTROL-M/EM

database environment from scratch, including the
master file, data file, log file, and devices.
-orAdds the CONTROL-M/EM database to an existing
database server and master file.
For a more information, see Build
page 5-11.
Database on
Delete Database
Deletes the CONTROL-M/EM database entirely

and removes the database files. After using this
option, CONTROL-M/EM cannot be run until after
the Build Database option is run.
Previous Menu
Displays the root menu.
One of the most crucial types of maintenance you may need to perform is
the restoration of a corrupted CONTROL-M/EM database. The database
can be reinstalled using one of the following methods:
Instructions for creating an CONTROL-M/EM database on a Sybase

Adaptive Server are presented below.
Instructions for creating an CONTROL-M/EM database on the

Oracle Server are presented in Database Creation on Oracle Server
on page 5-17.
Note
Lost CONTROL-M/EM data must be restored from a backup copy. It is

recommended that you frequently back up your data.
Database Creation on Sybase Adaptive Server

The CONTROL-M/EM database is created during CONTROL-M/EM
installation. You must recreate this database if it becomes corrupted.
5-7
However, the CONTROL-M/EM installation process installation process

installs the CONTROL-M/EM environment together with the database.
When a database installed on a Unix computer is corrupted, the existing
environment is not harmed. Do not use the installation to recreate the
CONTROL-M/EM database on a Unix computer.
Note
This section applies only if the CONTROL-M/EM database and the

database server are hosted on a Unix computer.
If you have installed your CONTROL-M/EM database and the database
server on Microsoft Windows, you must reinstall the database using the
CONTROL-M/EM installation process. For instructions, see Installing
CONTROL-M/EM with Sybase or MSSQL on Windows, in the
Enterprise Controlstation Installation Guide.
Database Environment
The CONTROL-M/EM database environment includes components in

Table 5-4.
Table 5-4
Sybase Database Environment Components
Component
Description
Database Server
(Sybase Adaptive
Server)
This process serves all users of the

CONTROL-M/EM application. The process reads
and updates the data stored in the database files.
The same server can also serve databases and
applications other than CONTROL-M/EM. This
process is typically named dataserver.
Sybase System
Procedures File
This file contains Sybase system procedures.
Master Database File
This file contains Sybase system information such

as device names, user names, and pre-defined
Sybase data.
Data File
This file is the CONTROL-M/EM database,

containing all job networks (active, old, simulation),
Scheduling tables, calendars, and so on. This file
also includes the database indexes.
5-8
Table 5-4
Sybase Database Environment Components
Component
Description
Log File (Sybase

Transaction Log)
The database server uses this file to recover from

failures and to ensure data integrity.
Database Devices
These are the physical storage locations for the

database. They can be either Unix or Windows
operating system files, or raw devices (raw partition
in Solaris, HP, and Windows, or logical volume in
AIX).
Each component of the database is built on a separate file or raw device.

The database can be built with some components on files and others on
raw devices.
If you build a component on a file, CONTROL-M/EM uses the following
default file names.
Master database file:
Sybase system procedures file:
CONTROL-M/EM database file:
Sybase transaction log file:
master.dat
systemprocs.dat
ecs600.dat
ecs600.log
For more information on allocating raw devices in your system, see the
appendix, Creating a Raw Device for the CONTROL-M/EM Database
in the Enterprise Controlstation Installation Guide.
Shared Sybase Adaptive Server
CONTROL-M/EM can be configured to use an existing Sybase Adaptive

Server for managing access to the CONTROL-M/EM database.
Before building the CONTROL-M/EM database using this configuration,
the following preliminary steps must be performed:
5-9
1. Obtain the password of the Sybase system administrator (sa).

2. Determine the location of the existing Sybase Interfaces file (for
Unix) or the sql.ini file (for Windows). This file must be copied to
the /tmp directory on the local computer where you build the
CONTROL-M/EM database, and must also be copied to the
/sybase/<platform>/ directory after installation. It will be necessary
to maintain this copy of the Interfaces file manually.
3. Perform the disk init procedure found in the Preparing for
Installation on Unix chapter of the Enterprise Controlstation
Installation Guide.
4. Obtain the Sybase device names for the CONTROL-M/EM database
and log.
5. Verify that the Sybase Adaptive Server is running.
6. Check that the following minimal values are defined for the database
server configuration parameters. If necessary, set them using
sp_configure or Alter Database:
User Connections
Open Objects
Size of tempdb
60
2000
50
Note
With this configuration, certain limitations apply when using the

CONTROL-M/EM root menu. Menu options such as Start Database
Server, Stop Database Server, and Delete Database are disabled
because the CONTROL-M/EM database is not under the exclusive
control of the CONTROL-M/EM administrator. Attempting to use these
menu options causes the message This command can only be executed
with a dedicated CONTROL-M/EM database server to be displayed.
5-10
Build Database
This option builds the CONTROL-M/EM database using one of the

configurations described in this chapter.
Note
The default values for the parameters used in this procedure are defined
for the installation. If Build Database was run at least once, or if
parameter values were changed using Show Parameters, the displayed
values are based on the values you last assigned.
Build Database is a complex procedure. To successfully build a database
with this option, the following procedure must be followed:
To Build a Database:
Note
You must be logged on as an CONTROL-M/EM Administrator user to

perform the following procedure.
1. Export the existing CONTROL-M/EM database using the following
command:
ecs util -U <ecs_admin_username> -P <password>
-export -type all -file <export_file_name>
2. Close the following:
CONTROL-M/Desktop
All open sql sessions
3. Shut down all the CONTROL-M/EM server components (GUI

Server, Global Alerts Server, and Global Conditions Server).
5-11
Do not shut down the database server.

Note
If you have a distributed installation, you must also shut down

components that are installed on computers other than the local
computer.
4. Enter the following command to start the root menu:
root_menu
Note
Do not leave the root menu or any of its submenus (by choosing q to
quit) at any time before completing this procedure. Doing so can cause
damage to your data.
When it is safe to quit, you will be instructed to do so.
If you quit (pressed q) to leave the root menu or one of its submenus
before reaching Step 16, you must perform the workaround beginning
with Step 17 on page 5-15.
5. Enter the CONTROL-M/EM administrator username and password
when prompted. The root menu is displayed:
5-12
Root Menu
1
2
3
4
5
Activation Menu
New Window
6. Enter 4 to display the Database Creation Menu.

1 - Build Database
2 - Delete Database
p - Previous Menu
q - Quit
7. Enter 2. The current CONTROL-M/EM database is deleted.

A series of messages are displayed describing the progress of the
Delete procedure. When deletion is complete, you are prompted to
press Enter. The Database Creation menu is displayed.
8. Enter 1 to build a new CONTROL-M/EM database. The Interfaces
File Parameters menu is displayed:
5-13
Interface File Parameters:

1)
2)
3)
4)
5)
CONTROL-M/EM Database Name:

Sybase Server Name:
Sybase Server Host Name:
Query Socket Port Number:8760
Backup Socket Port Number:8761
a) Modify all of the above

q) Quit
s) Save current settings
Enter command or item number you wish to change [s]:
9. Enter s. The Database Parameters menu is displayed:

Database Parameters
1) CONTROL-M/EM Database Owner (DBO):
2) DBO Password:
3) Database Administrators Password:
4) Database (Data Portion) Size:
5) Sybase Interface Directory:
6) Sybase Server Name:
7) CONTROL-M/EM Database Name:
8) CONTROL-M/EM Database Data Device Name:
9) CONTROL-M/EM Database Log Device Name:
q) Quit
b) Build CONTROL-M/EM database
Enter command or item number you wish to change [s]:
10. Enter b. The database build procedure begins.

Build Database procedure.
11. When Build is complete, the Database Creation menu is displayed
automatically.
5-14
12. Press p until you return to the root menu.

13. Press 5 to display the Database Maintenance menu:
------------------------Select one of the following options:
1
2
3
4
5
6
7
Export Database
Import Database
Custom Export/Import
Extend Database Size
Erase Alerts
Modify Interfaces File
Modify Database Name
p - Previous Menu
q - Quit
14. Press 2 to begin the Import procedure. You are prompted to locate
the <export_file_name> file you exported in Step 1 on page
5-11.
15. Enter the location of the <export_file_name> file. When the
procedure is complete, the Database Maintenance menu is displayed.
16. Press q to return to the Unix prompt.
Note
The CONTROL-M/EM build procedure is complete. However, if you

quit the root menu or its submenus prematurely, you must perform the
workaround beginning with Step 17.
17. Build the database schema using the following command:
5-15

-build_schema
18. Enter the following command to uncompress the
<export_file_name> file you exported in Step 1 on page 511:
uncompress <export_file_name>
19. When the file is uncompressed, enter the following command:
tar xvf <export_file_name>
20. Import the databse data to the new database using the following
command:
-import -type all -dir <export_file_name>
The Build Database procedure is complete.
5-16
Database Creation on Oracle Server

The CONTROL-M/EM database is created during CONTROL-M/EM
installation. You must recreate this database if it becomes corrupted.
However, the CONTROL-M/EM installation process installation process
installs the CONTROL-M/EM environment together with the database.
When a database installed on a Unix computer is corrupted, the existing
environment is not harmed. Do not use the installation to recreate the
CONTROL-M/EM database on a Unix computer.
Note
This section applies only if the CONTROL-M/EM database and the

database server are hosted on a Unix computer.
If you have installed your CONTROL-M/EM database and the database
server on Microsoft Windows, you must reinstall the database using the
CONTROL-M/EM installation process. For instructions, see Installing
CONTROL-M/EM with Oracle on Windows, in the Enterprise
Controlstation Installation Guide.
Database Environment
The CONTROL-M/EM database environment includes components

listed in Table 5-5:
Table 5-5
Oracle Database Environment Components
Component
Description
Database Server
(Oracle Server)
This process serves all users of the

CONTROL-M/EM application: the process reads
and updates the data stored in the database files.
The same server can also serve databases and
applications other than CONTROL-M/EM. This
process is typically named dataserver.
SYSTEM Tablespace
The SYSTEM tablespace contains the data

dictionary tables for the entire database.
5-17
Table 5-5
Oracle Database Environment Components
Component
Description
Data Tablespace
This database is the CONTROL-M/EM database,

containing all job networks (active, old, simulation),
Scheduling tables, calendars, and so on.
Index Tablespace
This file contains the database indexes.
Redo Log File
The database server uses this file to recover from

failures and assure data integrity.
Each component of the database is built on a separate file or raw device.

The database can be built with some components on files and others on
raw devices.
If you build a component on a file, CONTROL-M/EM uses the following
default file names.
SYSTEM database file:
CONTROL-M/EM database file:
Sybase transaction log files:
system01.dbf
ecs600data.dbf
log01.dbf, log02.dbf
Note
Tablespaces can be installed either as files or as raw devices.

For more information about allocating raw devices in your system, see
the appendix, entitled Creating a Raw Device for the
CONTROL-M/EM Database, in the Enterprise Controlstation
Installation Guide.
Shared Oracle Server
CONTROL-M/EM can be configured to use an existing Oracle Server

for managing access to the CONTROL-M/EM database.
Before building the CONTROL-M/EM database using this configuration,
the following preliminary steps must be performed:
5-18
1. Obtain the password of the Oracle system administrator (SYSTEM).

2. Create a new directory in the oracle\oradata directory of your
existing Oracle Server installation. Name the directory with the
instance name of the new database that you are creating.
3. Obtain the file names for the CONTROL-M/EM Data and Index
tablespaces.
4. Verify that the Oracle Server is running.
5. Check that the following minimal values are defined for the Oracle
Server configuration parameters. If necessary, set them using
sp_configure or Alter Database:
User Connections
Size of Temporary tablespace
Size of Rollback segments tablespace
150
50 MB
50 MB
Note
With this configuration, certain limitations apply when using the

CONTROL-M/EM root menu. Menu options such as Start Database,
Stop Database, and Delete Database are disabled because the
CONTROL-M/EM database is not under the exclusive control of the
CONTROL-M/EM administrator. Attempting to use these menu options
causes the message, This command can only be executed with a
dedicated CONTROL-M/EM database server, to be displayed.
The procedures used to create the CONTROL-M/EM database are

invoked from the Database Creation menu. This menu is accessed by
selecting the Database Creation option from the CONTROL-M/EM
root menu, described in CONTROL-M/EM Root Menu on page 5-1.
Only the CONTROL-M/EM administrator can use this option.
The Database Creation Menu contains the following options:
5-19

1 - Build Database
2 - Delete Database
p - Previous Menu
q - Quit
To select an option from the menu, press the number or letter appearing
to the left of the option. Each option in the Database Creation menu is
described below:
Build Database
Builds (or rebuilds) the entire CONTROL-M/EM database
environment from scratch, including the SYSTEM tablespace,
the Data tablespace, the Index tablespace, Redo log files and file
names or raw device names.
-orAdds the CONTROL-M/EM database to an existing database
server. For a full description of this procedure, see Build
Database on page 5-21.
Delete Database
Deletes the CONTROL-M/EM database entirely and removes
the database files. After using this option, CONTROL-M/EM
cannot be run until after the Build Database option is run.
5-20
Build Database
This option builds the CONTROL-M/EM database using one of the

configurations described in this chapter.
Note
The default values for the parameters used in this procedure are defined
for the installation. If Build Database was run at least once, or if
parameter values were changed using Show Parameters, the displayed
values are based on the values you last assigned.
Build Database is a complex procedure. To successfully build a database
with this option, the following procedure must be followed:
To Build a Database:
Note
You must be logged on as an CONTROL-M/EM Administrator user to

perform the following procedure.
1. Export the existing CONTROL-M/EM database using the following
command:
-export -type all -file <export_file_name>
2. Close the following:
CONTROL-M/Desktop
All open sql sessions
3. Shut down all the CONTROL-M/EM server components (GUI

Server, Global Alerts Server, and Global Conditions Server).
5-21
Do not shut down the database server.

Note
If you have a distributed installation, you must also shut down

components that are installed on computers other than the local
computer.
4. Enter the following command to start the root menu:
root_menu
Note
Do not leave the root menu or any of its submenus (by choosing q to
quit) at any time before completing this procedure. Doing so can cause
damage to your data.
When it is safe to quit, you will be instructed to do so.
If you quit (pressed q) to leave the root menu or one of its submenus
before reaching Step 16, you must perform the workaround beginning
with Step 17 on page 5-25.
5. Enter the CONTROL-M/EM administrator username and password
when prompted. The root menu is displayed.
Root Menu
1
2
3
4
5
Activation Menu
New Window
6. Enter 4 to display the Database Creation Menu:
5-22

1 - Build Database
2 - Delete Database
p - Previous Menu
q - Quit
7. Enter 2. The current CONTROL-M/EM database is deleted.

Delete procedure. When deletion is complete, you are prompted to
press Enter. The Database Creation menu is displayed.
8. Enter 1 to build a new CONTROL-M/EM database. The Oracle
Database Parameters menu is displayed:
5-23
CONTROL-M/EM MAKE DB
Oracle Database Parameters
1) Oracle database instance name: ecs600
2) CONTROL-M/EM database user: ecsuser
3) CONTROL-M/EM database user password: password
4) Oracle Server host name: <servername>
5) Oracle LISTENER port number: 1521
6) Oracle SYSTEM password: manager
7) CONTROL-M/EM data tablespace name: ecs
8) CONTROL-M/EM data tablespace size: 250 MB
9) CONTROL-M/EM data tablespace file name (full path):
/home1/ecstrn6/oracle/oradata/ecs600/ecsdata01.dbf
10) CONTROL-M/EM index tablespace size: 100MB
11) CONTROL-M/EM index tablespace file name (full
path):/home1/ecstrn6/oracle/oradata/ecs600/ecsindx01.d
bf
q) Quit
n) Next page
Enter command or item number you wish to change [n]:
9. Enter n. A second menu page is displayed.

10. Press b to build the database.
Build Database procedure.
11. When Build is complete, the Database Creation menu is displayed
automatically.
12. Press p until you return to the root menu.
13. Press 5 to display the Database Maintenance menu:
------------------------BMC Software, Inc., Confidential and Proprietary Information
5-24
Select one of the following options:

1
2
3
4
5
6
7
Export Database
Import Database
Erase Alerts
p - Previous Menu
q - Quit
14. Press 2 to begin the Import procedure. You are prompted to locate
the <export_file_name> file you exported in Step 1 on page
5-21.
15. Enter the location of the <export_file_name> file. When the
procedure is complete, the Database Maintenance menu is displayed.
16. Press q to return to the Unix prompt.
Note
The CONTROL-M/EM build procedure is complete. However, if you

quit the root menu or its submenus prematurely, you must perform the
workaround beginning with Step 17.
17. Build the database schema using the following command:
-build_schema
18. Enter the following command to uncompress the
<export_file_name> file you exported in Step 1 on page 521:
uncompress <export_file_name>
5-25
19. When the file is uncompressed, enter the following command:

tar xvf <export_file_name>
20. Import the databse data to the new database using the following
command:
ecs util -U <ecs_admin_username> -P <password> import -type all -dir <export_file_name>
The Build Database procedure is complete.
Database Parameters
Oracle Server configuration parameters are specified during installation

before the CONTROL-M/EM database is created. You can also modify
these parameters and rebuild the database using the Database Creation
menu, described on page 5-19. For descriptions of the Oracle Server
installation parameters, see CONTROL-M/EM with Oracle Server
installation chapters in the Enterprise Controlstation Installation Guide.
5-26

The procedures used to maintain the CONTROL-M/EM database are
invoked from the Database Maintenance menu, described below. This
menu is accessed by selecting the Database Maintenance option from the
CONTROL-M/EM root menu (described on page 5-1 of this chapter).
Only the CONTROL-M/EM Administrator can access this option.
The Database Maintenance menu contains the following options:
------------------------Select one of the following options:
1
2
3
4
5
6
7
Export Database
Import Database
Erase Alerts
p - Previous Menu
q - Quit
to the left of the option. Each option in the Database Maintenance menu
is described in Table 5-6.
Table 5-6
Database Maintenance Menu Options (Part 1 of 2)
Menu Option
Description
Export Database
Extracts the contents of the CONTROL-M/EM

database to a flat file.
Import Database
Inserts data into the CONTROL-M/EM database

from a flat file created using the Export Database
option.
5-27
Table 5-6
Database Maintenance Menu Options (Part 2 of 2)
Menu Option
Description
Custom
Export/Import
Displays a menu that enables you to customize the

parameters used for the Export Database and
Import Database options.
Extend
Database
Size
Extends the size of the CONTROL-M/EM database.

Selecting this option runs one of two utilities,
depending on the type of database server that is
installed. The utilities are dbextendSyb and
dbextendOra, for Sybase and Oracle, respectively.
When they are running you may be prompted for
the following information:
Password for the sa or SYSTEM user.
Name of the database that you want to extend.
Size in MB of the additional space to allocate.
Full name of the additional space in a file system
or raw partition.
Erase Alerts
Erases alerts that were posted to the Alerts

window.
Modify
Interfaces File
Activates the dsedit utility so that you can modify

the Interfaces file.
Modify
Database Name
Modifies the CONTROL-M/EM database name. A

prompt is displayed requesting the new name.
5-28
Export/Import Database
The Export Database utility copies the contents of the
CONTROL-M/EM database to a regular file using a format that is
independent of workstation type, configuration, or type of database.
The Import Database utility reads the data file created by the Export
Database utility and loads it into an existing CONTROL-M/EM
database, overwriting any existing data in the database.
Used together, these two utilities enable you to:
Back up and recover the CONTROL-M/EM database
Transfer the CONTROL-M/EM database from one kind of

workstation to another
Transfer the CONTROL-M/EM database from regular Unix files to a

raw device, or vice-versa
Note
When the database is exported to a file, you are prompted for a filename.
The extension .Z is appended to the filename. When specifying the name
of the file to import, do not include the .Z extension.
If the CONTROL-M/EM database uses an existing Sybase Adaptive
Server, you must supply the sa password for the database server to use
these utilities. The SYSTEM password is required for Oracle Server
users to use the utilities. In addition, the following conditions must exist
at the time the utilities are run:
The Sybase Adaptive Server must be started.

All WS-GTWs must be stopped.
All CONTROL-M/EM users must be logged off.
Each utility is described below.
5-29
Export Database
The Export Database utility is started by selecting the Export Database

option from the Database Maintenance menu.
The conditions described above must exist when the utility is run. The
utility takes the name of the file to which the database will be exported
from the Export/Import default parameters. Once started, the utility
prompts for the password of the database server administrator (if
required).
Most components of the database are exported, including
CONTROL-M/EM user names and passwords. The only database
components not exported are the Active network and any Old networks.
Note
All gateways and CONTROL-M/EM GUIs must be down when

exporting a database.
Import Database
The Import Database utility is started by selecting the Import Database

option from the Database Maintenance menu.
The conditions described above must exist when the utility is run. Once
started, the utility prompts for the following:
Password of the database server administrator (sa or SYSTEM), if

required.
Name of the file or device from which the database will be imported.
Note
All gateways and CONTROL-M/EM GUIs must be down when

importing a database.
5-30
The utility imports the data to the existing CONTROL-M/EM database.

All previous contents of the database, if any, are overwritten. If no
CONTROL-M/EM database exists on the workstation, use the Database
Creation menu options to create a database before running this utility.
Note
When this option is used to import a file into a database other than the
database from which the file was exported, the original passwords are
preserved.
5-31
Use the Custom Export/Import menu to customize the import and export
features. options 1-7 indicate whether a specific type of
CONTROL-M/EM data is included (Y) or not included (N) in the export
or import.
Export/Import Default Parameters Menu
------------------------------------1) Definition Tables..............
2) Calendars......................
3) System Tables..................
4) Data Centers...................
5) Users Tables...................
6) Alert..........................
7) Global Conditions..............
8) Maint..........................
9) Collections....................
10) View..........................
11) Filter........................
12) Log...........................
13) Hierarchy.....................
14) User Views....................
15) Net...........................
16) Default Net Name..............
17) Default Export Media..........
18) Default Device................
{ECS_HOME}/ExportImportFile.txt
N
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
All
File
e) Export Now
i) Import Now
r) Restore Default Parameters
p) Previous Menu
q) Quit
Enter item number you wish to change :
to the left of the option. A prompt is displayed requesting the new value
of the parameter. Enter e or i to activate the Export Database or Import
Database utility. These menu options are described in Table 5-7.
5-32
Table 5-7
Custom Export/Import Menu Options
Menu Option
Description
Definition Tables
Scheduling table definitions.

Valid values are:
Y
N
Calendars
Calendar definitions.
Valid values are:
Y
N
System Tables
System parameters and Alerts.

Valid values are:
Y
N
Data Centers
CONTROL-M installation definitions.

Valid values are:
Y
N
Users Tables
User definitions.
Valid values are:
Y
N
Alert
Existing alerts at time of export.

Valid values are:
Y
N
Global Conditions
Existing global conditions at time of export.

Valid values are:
Y
N
Maint
Administration Facility settings.

Valid values are:
Y
N
Collections
ViewPoint collections.
Valid values are:
Y
N
View
Defined ViewPoints.
Valid values are:
Y
N
5-33
Table 5-7
Custom Export/Import Menu Options
Menu Option
Description
Filter
ViewPoint filters.
Valid values are:
Y
N
Log
Log files.
Valid values are:
Y
N
Hierarchy
ViewPoint hierarchies.
Valid values are:
Y
N
User Views
User and group authorizations.

Valid values are:
Y
N
Nets
Active networks.
Valid values are:
Y
N
Default Net Name
Active tables from a specific date.

Valid values are:
Y
N
Default Export Media
Media to which the database is exported.

Valid values are:
Tape
File
Default Device
Default path to the export or import media.
5-34
Selecting this option displays the dsedit utility menu. This menu enables
you to modify the Sybase Interfaces file. For information about using
dsedit, see your Sybase Adaptive Server documentation.
5-35
Database Check Utility (db_check)

The db_check utility provides general database information. This
information includes the size of the database, availability of space, and
verification of database integrity. When invoked, information similar to
the following is displayed:
db total = 29000.0 KB (data= 23500.00 , log= 5500.00)
data used = 1928 KB (8%).
log used = 0 KB (0%).
Checking database...
Database is OK.
The db_check utility can also be used to provide automatic database and
transaction log monitoring. The following options are available:
db_check [-d<db threshold %>] [-l<log threshold %>] [n] [-h]
where db threshold % and log threshold % define percentages that,

when exceeded, generate shout messages warning that the
CONTROL-M/EM database or transaction log should be extended. The
-n parameter executes the script without verifying total database
integrity. The -h parameter displays the usage.
You are prompted for the CONTROL-M/EM administrator password
when using the db_check utility.
5-36
Security
6
CONTROL-M/Enterprise Manager (CONTROL-M/EM) and
CONTROL-M security mechanisms determine which information each
user can obtain or update, and which program functions are available to
the user. The security mechanisms of CONTROL-M/EM and
CONTROL-M together ensure a high degree of security while not
adversely affecting efficient production.
CONTROL-M uses these mechanisms to control the users ability to
manipulate jobs by controlling access to various system components.
CONTROL-M/EM Workstation Security

Security on the CONTROL-M/EM workstation complements the security
mechanism provided at each CONTROL-M and protects the integrity of
the CONTROL-M/EM programs and database on the workstation.
Workstation security is implemented with two mechanisms:
Integral workstation security mechanisms built into the workstation

operating system.
CONTROL-M/EM security provided by the CONTROL-M/EM

program.
The following techniques are available to secure CONTROL-M/EM at

the workstation level:
Security
6-1
Integral Workstation Security
Windows operating system:

Windows offers Workstation Log-in Protection. To access the
workstation itself (apart from any application), a Windows user must
provide a user name and password at the Windows prompt. Only
the Windows administrator can assign user names and passwords.
Unix operating system:
Workstation Log-on Protection

To access the workstation itself (apart from any application), a user
must provide a user name and password at the Unix shell prompt.
Only the Unix super-user can assign user names and passwords.
File Protection
The Unix super-user can limit access to Unix files (program and data
files) to specific users. This provides an additional level of protection
and security.
CONTROL-M/EM Security
CONTROL-M/EM security is handled by the CONTROL-M/EM

administrator. The following security measures are provided:
CONTROL-M/EM Log-on Protection

There is no connection between the workstation log on and the
CONTROL-M/EM log on. However, for simplicity and
maintainability, it is recommended that both log-ons use the same
user name.
CONTROL-M/EM Data Protection

The CONTROL-M/EM administrator can limit the data that each
user is authorized to view or modify. For details, see
CONTROL-M/EM Security on page 6-4.
6-2
CONTROL-M Security
CONTROL-M security authorizes the operations that each user is
allowed to perform for each CONTROL-M installation (such as holding
jobs and modifying scheduling tables). At OS/390 sites, this security
mechanism interfaces with the other security tools used at the site (such
as RACF, ACF2/SAF and TOP SECRET).
CONTROL-M/EM interfaces directly with CONTROL-M security. For
each CONTROL-M/EM user operation (such as Hold or Rerun), the
CONTROL-M/EM gateway (WS-GTW) transfers the requesting
CONTROL-M/EM user name to the CONTROL-M gateway
(CTM-GTW). CTM-GTW uses CONTROL-M security modules to check
the authorization of the user. If the user is not authorized, the operation is
rejected and the workstation issues an appropriate message.
For additional information, see the Installing CONTROL-M
Application Server Security chapter in the INCONTROL for OS/390
Security Guide and see the CONTROL-M Administrator Guides for other
platforms.
Passing Global Conditions Between CONTROL-M Installations
One area of security managed by CONTROL-M relates to the integrity of

prerequisite conditions. When CONTROL-M security is implemented in
a CONTROL-M, only an authorized user can add or delete prerequisite
conditions. (In OS/390 installations, CONTROL-M security is functional
when Exit 7 is implemented. In other installations, CONTROL-M
security is functional when the CONTROL-M system parameter, Full
Security, is set to Y.)
When an action (add or delete) on a global condition originates in a
CONTROL-M installation, CONTROL-M/EM repeats the action in other
CONTROL-M installations (in accordance with the users specifications
in the Global Conditions window). In each installation in which the
action is repeated, the addition or deletion of the condition is attributed to
a special user named GCSERV.
Security
6-3
If the CONTROL-M security mechanism is implemented in a

CONTROL-M to which global condition actions will be repeated, a user
named GCSERV must be defined in the CONTROL-M security facility.
User GCSERV should have authorization to add and delete prerequisite
conditions.
CONTROL-M/EM Security
Figure 6-1
User Authorization Window
CONTROL-M/EM contains a security mechanism called the

Authorization facility. Using the authorization facility, the
CONTROL-M/EM administrator can limit the entities that each user is
authorized to view or change. For example, a user may be limited to
modifying resources and jobs that relate to a specific CONTROL-M.
Access to the following entities and actions can be limited:
6-4
Jobs that the user can view or modify. This affects usage of all
windows that rely on access to information originating in the active
environment. For example, limiting the view to jobs from a single
CONTROL-M limits the view in the CONTROL-M/Enterprise
Manager ViewPoint window.
Resources and conditions that the user can view or change in the
resource windows. This does not relate to resources and conditions
displayed in the Job Details window. For example, in the Job
Details window, the user can see that a job is waiting for a
prerequisite condition, but this user might not be authorized to create
this condition using the Prerequisite Condition window.
Calendars and Scheduling tables that the user may view or modify.
Limiting access to Scheduling tables also determines which
Scheduling tables/jobs the user can order or force.
ViewPoint components that the user can use or modify.
Administrative responsibilities, such as CONTROL-M definitions

and User Authorizations that a user can access or modify and
Command Line Interface (CLI) utility privileges.
CONTROL-M/EM security can be defined for both single users and

groups. Generally, if you are a member of a group, you have the same
authorizations that are assigned to the group. Authorizations specifically
defined for you either are additional authorizations or take precedence
over group authorizations.
Security
6-5
The following rules apply when assigning authorizations to users:
Scheduling Tables, Calendars, and Resources

You have an authorization if that authorization has been granted to
any group of which you are a member. Authorizations specified in
the User Authorization Scheduling Table, Calendar, or Resources
windows are additional authorizations for the specific user.
Example
User JimA belongs to group Acct. Group Acct has Browse authority for
all Scheduling tables. User JimA is defined with Full authority for
CONTROL-M Figaro and Marius Scheduling tables. User JimA can
update and delete Scheduling tables for CONTROL-M Figaro and
Marius, but can only view Scheduling tables for other CONTROL-M
installations.
6-6
Privileges (ViewPoints, Collections, Filters, Hierarchies,

Authorization Definitions, Communication)
The user has the highest level of authorizations defined for any group
of which the user is a member (Default). Authorizations specified in
the User Authorization => Privileges window supercede any
Group authorizations for the specific user.
Example
User JimA also belongs to group Staff. Group Staff has Update
authority for all definitions (ViewPoints, Collections, Filter, and
Hierarchies) but only Browse authority for Authorization definitions and
Communication. User JimA is defined with Default authority for all
definitions and Update authority for Communication. User JimA can
create and modify ViewPoints and their components, as well as add,
modify, and delete CONTROL-M installations from the
Security
6-7
Jobs
The user has combined authorizations defined for all the groups of
which the user is a member. Authorizations specified in the User
Authorization => Job window are additional authorizations for the
specific user.
Example
User JimA belongs to group Acct. Group Acct has authorization for all
Browse and Control actions on jobs in the active environment. User
JimA is defined with authorization for Update actions. User JimA can
view jobs in the active environment in the CONTROL-M/Enterprise
Manager ViewPoint window and perform control actions (Hold, Free,
Confirm, and so forth) on these jobs. Additionally, he can edit both job
details and JCL for jobs in all CONTROL-M installations.
6-8
Authorization for certain operations requires a combination of

authorizations in both CONTROL-M/EM and CONTROL-M. For
example, for a user to Hold a job, the user must be authorized in
CONTROL-M/EM to access that job and authorized in CONTROL-M to
Hold jobs for that jobs owner.
CONTROL-M/EM users with at least Browse authority can display their
authorizations by choosing Tools => Authorizations. For more
information, see User and Group Authorization Windows on page 610.
Security
6-9
User and Group Authorization Windows

CONTROL-M/EM security is defined for both single users and groups.
Generally, if you are a member of a group, you have the same authorizations
to view or modify entities that is assigned to the group. Authorizations
specifically defined for a user take precedence over group authorizations.
CONTROL-M/EM provides separate windows for User authorizations
and Group authorizations.
The User and Group Authorization windows are divided into separate
panels for defining each of the CONTROL-M/EM security entities.
These entity panels are described on the following pages.
Note
Only an CONTROL-M/EM administrator with Definition privileges can

add or modify User or Group authorizations. Only users with at least
Browse authorization can access the Authorization facility. For
information on modifying authorizations, see User/Group
Authorizations Privileges Panel on page 6-22.
To access the User Authorizations or Group Authorizations window:

administrator.
2. Choose Tools => Authorizations. The Users and Groups window
is displayed:
6-10
Figure 6-2
Users and Groups Window
The Users and Groups window contains a list of system users and a list
of the groups that these users are members of for authorization purposes.
This window enables a properly authorized user to define new users and
groups, view or update the authorization levels of any user or group, and
to delete existing users or groups.
Table 6-1
Field Descriptions
Field
Description
User Name
CONTROL-M/EM log on name of the user. This

specifies to whom the authorization refers.
User Full Name
Full name of the user.
User Description
Description of the user.
Group Name
Identifying name for group.
Group Description
Description of the group.
Security
6-11
To define a new user or group:
1. Click the New button in the appropriate section of the Users and
Groups window. The New Name window is displayed.
2. Specify a name for the user or group in the New Name window and
click OK. The User Authorizations window or Group
Authorizations window is displayed accordingly.
6-12
3. Complete the details for the specified user or group in the General
panel described in User Authorizations General Panel on page 615 or Group Authorizations General Panel on page 6-17.
4. Define authorization levels in each of the entity panels.
5. Click OK to add the user or group to the CONTROL-M/EM Security
database.
To view or modify Authorizations for a specific user or group:
1. Select the user name or group name in the Users and Groups
window.
2. Click the corresponding Update button.
-orDouble-click the user name or group name.
Security
6-13
The User Authorizations window or Group Authorizations window is

displayed.
3. Modify details for the selected user or group as required.
4. Click OK to modify the user or group to the CONTROL-M/EM
database.
To delete an existing user or group:
1. Select the user name or group name in the Users and Groups
window.
2. Click the Delete button in the same window. A confirmation window
is displayed.
3. Click OK.
Note
User authorizations take effect the next time the specified user logs on to
CONTROL-M/EM.
The User Authorizations window and Group Authorizations window
contain the following panels:
Panel
Purpose (Part 1 of 2)
General (User)
Provides log on information about the user and associates

the user with one or more existing groups.
General (Group)
Describes the authorization group and a lists the member

user names that belong to the group.
Jobs
Specifies the jobs in the active environment that a user

can access and the actions that can be performed on
those jobs.
Privileges
Specifies (1) the actions that can be performed on

ViewPoints, Collections, Filters and Hierarchies, Alerts
and (2) the Authorization level, Communication, and
Command Line Interface (CLI) privileges a user can have.
6-14
Panel
Purpose (Part 2 of 2)
Scheduling
Tables
Specifies the Scheduling tables a user can access in

CONTROL-M/Desktop and the authorization levels for the
tables.
Resources and
Calendars
Specifies the resources, conditions, and calendars a user

can access.
Click the appropriate tab to display the desired panel. After completing
all the panels, click OK to add the user or group to the
CONTROL-M/EM Security database. A description of each
Authorization panel is displayed below.
User Authorizations General Panel
The User Authorizations General panel provides log on information about

the user and allows association of the user with one or more an existing groups.
Security
6-15
Table 6-2
Field Descriptions
Field
Description
User
CONTROL-M/EM user name (required). Specifies to

whom the authorization refers.
Full Name
Full name of the user.
Description
Description of the user.
Password
Password (minimum six characters) of the user. This

field is hidden or displayed as asterisks.
Confirm
Password
Password confirmation field. This field is hidden.
Member of
List of groups of which the user is a member.
Not member
of
List of groups of which the user is not a member.
To add the user to a group:
1. Select the group in the Not member of list.

2. Click Add. The group name is added to the Member of list and
deleted from the Not Member of list.
To add the user to multiple groups:
1. While holding down the CTRL key, select each group from the Not
member of list.
2. Click Add. The selected group names are added to the Member of
list and deleted from the Not Member of list.
To remove the user from a group or from multiple groups:
1. Select the group or groups from the Member of list.

2. Click Remove. The selected group names are added to the Not
Member of list and deleted from the Member of list.
6-16
Group Authorizations General Panel
The Group Authorizations General Panel provides a description of the

authorization group and a list of the member user names.
Generally, if a user is a member of a group, the user has the same
authorizations to view or modify entities that is assigned to the group.
Authorizations specifically defined for a user are either additional
authorizations or take precedence over group authorizations.
Security
6-17
Field Descriptions
Table 6-3
Field Descriptions
Field
Description
Group Name
Identifying name for group.
Description
Description of the group.
Member List
List of names of users who are members of this group. This

field cannot be modified. To add or delete a user from the
group, use the General panel in the User Authorizations
window.
6-18
User/Group Authorizations Jobs Panel
The Jobs panel is used to specify the jobs in the active environment that a
user can access and the actions that the user can perform on those jobs.
The Filter for Displayed Jobs and the Job actions are specified
independently.
Table 6-4
Jobs Panel Fields
Field
Description
Filter
Specifies the type of jobs the user can access.

Note: This field is not available in the Group
Authorizations window.
Browse actions
Specifies the type of active job information the user is

authorized to view.
Control actions
Specifies the Control actions the user can perform.
Update actions
Specifies the Update actions the user can perform.
Security
6-19
To enable job actions
Select the check box for each job action or feature that the user is
authorized to browse, control, or update.
-orTo select all the actions and features in a category, click the Select All
button for that category.
Note
Descriptions of each job action can be found in Chapter 12, Getting and
Updating Details, in the CONTROL-M/Enterprise Manager User
Guide.
To specify the types of jobs the user can access:
1. Click the Filter button. The Define authorization job selection

window is displayed:
The Define authorization jobs selection window contains an empty

table in which a maximum of five field=value combinations can be
specified. These combinations act as selection criteria for the jobs
that are displayed in the CONTROL-M/Enterprise Manager
ViewPoint window.
6-20
The field values are compared to the parameters in job processing

definitions (for example, Application, Group, Cyclic, etc.) to
determine if the job should be displayed. For a description of these
parameters, see Chapter 5, Job Processing Parameters, in the
CONTROL-M/Enterprise Manager User Guide.
The fields of the Define authorization job selection window are
described in Table 6-5.
Table 6-5
Column Descriptions
Column
Description
Field
Field to be checked in the job processing definition.

Each cell in the Field column is a list box. Click on the field to
display the window list box displayed in Figure 6-3.
Value
Value of the parameter listed in the cell of the Field column that
determines whether the job selection criteria are satisfied.
Figure 6-3
Field Column List
Note
Use the Tab key to skip to the next field. Use the arrow keys or the
vertical scroll bar to move through the options in a list box.
2. Specify from one to five pairs of field=value combinations. The
relationship between these criteria is a Boolean AND.
3. To clear any selection criterion, click its Reset button.
Security
6-21
4. Click OK.
User/Group Authorizations Privileges Panel
The Privileges panel is used to specify the actions that a user or group
can be perform on Collections, Hierarchies, Filters, ViewPoints, and
Alerts.
A description of each action and access level is given in the tables below.
Table 6-6
Privileges Panel Fields
Field
Description
Collections
Specifies the actions that can be performed on

Collections.
Hierarchies

Hierarchies.
6-22
Table 6-6
Privileges Panel Fields
Field
Description
Filters
Specifies the actions that can be performed on Filters.
ViewPoints

ViewPoints.
Alerts
Specifies whether Alerts can be monitored and the actions

that can be performed on them.
Authorizations
Definitions
Specifies the actions that can be performed in the

CONTROL-M/EM authorizations windows.
Communication
Specifies the actions that can be performed in the

Communication Administration window. The
Communication Administration window is used to
define CONTROL-M installations.
CLI
Grants authorization for using the Command Line

Interface (CLI) utility. For more information, see the
CONTROL-M Job Parameters and Variables Reference
Guide.
To set access levels for ViewPoints, Collections, Hierarchies, Filters, and Alerts:
Select an access level from the list box for each ViewPoint component or
for Alerts as follows:
Access
Level
Description
None
Denies access to the ViewPoint component.

Does not display alerts in the Alerts window.
Browse
Permits viewing the ViewPoint component in the ViewPoint

Manager only.
Enables user to see Alerts in the Alerts window.
Update
Permits defining the ViewPoint component using the ViewPoint

Manager and the ViewPoint Wizard.
Permits the user to update Alert status and delete Alerts.
Security
6-23
Access
Level
Description
Full
Permits defining and deleting the ViewPoint component.

Permits the user to update Alert status and delete Alerts.
Default
(User only) User authorization level is equal to the highest

authorization level granted to any of the groups the user in which
the user is a member. (Default)
Example: The user, BOB1, has an user authorization of Default
for Alerts. He belongs to the ACCT accounting group. The
members of ACCT have Update authorization for Alerts.
Therefore, BOB1 has Update authorization.
To set access levels for Authorizations Definitions:
Select an access level from the list box:

Access
Level
Description
None
Denies access to all Authorization panels.
Browse
Permits viewing Authorization panels only.
Update
Permits creation of new users and modification of existing users.
Full
Permits creating, modifying, and deleting users.
Default
(User only) Allows the user the highest level of authorization

defined for any group of which the user is a member. (Default)
To set access levels for Communication:
Select an access level from the list box:

Access
Level
Description
None
Denies access to the Communication Administration

window.
Browse
Permits viewing the Communication Administration window

and refreshing the display.
Update
Permits adding and modifying CONTROL-M information.
6-24
Access
Level
Description
Full
Permits adding, modifying, and deleting

CONTROL-M information.
Default
(User only) Allows the user the highest level of

authorization defined for any group of which the user is a
member. (Default)
User/Group Authorizations Scheduling Tables Panel
The Scheduling Tables panel is used to specify the Scheduling tables that
a user can access and the authorization levels for using the tables.
Authorization can be granted at CONTROL-M level (for all tables
belonging to the specified CONTROL-M site), library level for OS/390
sites only, and individual Scheduling table level.
Security
6-25
Table 6-7
Field Descriptions
Field
Description
Access Level
Defines the authorization level for the Scheduling Tables

specified in the fields below.
CONTROL-M
Specifies prefixes for CONTROL-M installations from

which the user can access Scheduling tables.
Library
[OS/390] Specifies prefixes for libraries from which the

user can access Scheduling tables.
Scheduling
Table Name
Specifies prefixes for Scheduling tables the user can

access.
To set authorization levels for Scheduling Tables:
1. Select an Access Level from the list box as follows:

Access
Level
Description
Browse
Permits viewing the specified Scheduling tables in

CONTROL-M/Desktop only.
Update
Permits modifying the specified Scheduling tables in

CONTROL-M/Desktop and adding new ones.
Full
Permits modifying and deleting the specified Scheduling tables

and adding new ones.
2. Specify all the CONTROL-M installations for the Scheduling tables

that will have the indicated Access Level.
Click the Add button to add a CONTROL-M prefix to the list.

Specify the prefix in the New CONTROL-M window and click
OK. Use * to denote all CONTROL-M installations.
Select the prefix and click the Delete button to delete a

CONTROL-M prefix from the list.
3. Specify all the libraries for the Scheduling tables that will have the
indicated Access Level. Use * to denote all Libraries.
6-26
4. Specify all the Scheduling table prefixes or full names that will have
the indicated Access Level. Use * to denote all Scheduling tables.
5. Repeat these steps for the other access levels.
Note
If any field is specified for an Access Level, all fields for that Access
Level must contain a value. Use an * to denote all CONTROL-M
installations, libraries, or Scheduling table prefixes.
User/Group Authorizations Resources and Calendars Panel
Security
6-27
The Resources and Calendars panel is used to specify which resources,

conditions, and calendars a user can access. See the chapter, Getting and
Updating Details, in the CONTROL-M/Enterprise Manager User Guide
for information about resources and conditions. For information about
Calendars, see the chapter, Job Processing Definitions, in the
Table 6-8
Resource Fields
Field
Description
Access
level
Defines the authorization level for the resources specified in

the field below.
Type
Specifies the type of resource specified in the field below.
Resource
List
Specifies prefixes for resources the user can access.
To set authorization levels for resources:
1. Select the type of resource from the list box.

2. Select an access level from the list box. Access levels are described
in Table 6-9.
Table 6-9
Access Levels
Access
Level
Description
Browse
Permits viewing the specified resources only.
Update
Permits modifying the specified resources and adding new ones.
Full
Permits modifying and deleting the specified resources and

adding new ones.
3. Specify all the resources that will have the indicated Access Level.
Click the Add button to add a resource prefix to the list. Specify
the prefix in the New Resource Prefix window, and click OK.
Use * to denote all resources.
6-28
Select the prefix and click the Delete button to delete a resource
prefix from the list.
4. Repeat Step 2 and Step 3 for other access levels.

5. Repeat Step 1 to Step 3 for other resource types.
Example
To set the access level of prerequisite conditions beginning with the letter
C or D as Update:
1. Select Prerequisite conditions from the Type list box.
2. Select Update from the Access level list box.
3. Click Add.
4. In the New resource prefix window, enter C and click OK.
5. Click Add again.
6. In the New resource prefix window, enter D and click OK.
7. Click OK.
The user is now authorized to modify prerequisite conditions beginning
with the letter C or D.
Security
6-29
Table 6-10
Calendar Fields
Field
Description
Access
level
Defines the authorization level for the Calendars specified in the

field below.
Calendar
List
Specifies prefixes for Calendars the user can access.
6-30
To set authorizations for Calendars:
1. Select an access level from the list box. Access Levels are described
in Table 6-11.
Table 6-11
Access Levels
Access Level
Description
Browse
Permits viewing the specified Calendars in

CONTROL-M/Desktop only.
Update
Permits modifying the specified Calendars in

Full
Permits modifying and deleting the specified Calendars in

2. Specify all the Calendars that will have the indicated Access Level.
Click the Add button to add a prefix to the list. Specify the
prefix in the New Calendar Prefix window and click OK. Use
* to denote all Calendars.
Select the prefix and click the Delete button to delete a Calendar
prefix from the list.
3. Repeat Step 1 and Step 2 for other access levels.
Security
6-31
6-32
Troubleshooting
This chapter describes methods of displaying CONTROL-M/Enterprise

Manager (CONTROL-M/EM) information that can be used to diagnose
and address performance problems.
The following topics are presented:
DIAG Diagnostics Facility
Troubleshooting
7-1
The Troubleshooting Menu option, accessed from the
CONTROL-M/EM root menu, can be used to perform a variety of
diagnostic functions. Most of the functions are available only to the
CONTROL-M/EM administrator.
Note
Troubleshooting for all currently-active Gateways and for the Global

Conditions Server(s) (GCS) on the network can be performed from a
single workstation. However, if a gateway is not currently running, you
must start it from its host computer.
To access the Troubleshooting Menu:
1. Log on to the workstation as the Unix user under whose home
directory CONTROL-M/EM was installed.
2. Type the root_menu command at the Unix prompt.
3. Enter the CONTROL-M/EM administrator username and password.
The root menu is displayed.
4. Select Troubleshooting Menu from the CONTROL-M/EM root
menu. The Troubleshooting Menu menu is displayed:
-------------------Select one of the following options:
1
2
3
4
5
Database Troubleshooting
Gateway Troubleshooting
Show Environment
Global Conditions Server Parameters
Configure Orbix2000 Parameters
p - Previous Menu
q - Quit
7-2
To select an option from the menu, press the letter/number appearing

before the option. Each option in the Troubleshooting Menu is
described Table 7-1, Troubleshooting Menu Options, on page 7-3:
Table 7-1
Troubleshooting Menu Options (Part 1 of 2)
Menu Option
Description
Database
Troubleshooting
Displays the Database Troubleshooting menu,

described below. This option can be selected from any
CONTROL-M/EM workstation and by any
CONTROL-M/EM user. For more information, see
Database Troubleshooting on page 7-5.
Gateway
Troubleshooting
Displays the Gateway Troubleshooting menu, described

below. This option acts on all gateways running
currently on the network.
This option is displayed on the menu only if the gateway
is installed on the computer where the menu is
accessed
For more information, see Gateway
Troubleshooting on page 7-7.
Show
Environment
Displays data about the CONTROL-M/EM environment,

such as hardware type, operating system version,
database server version, communication type, database
size, swap space, and workstation resources. This data
is used by Technical Support.
It is not necessary to log on as a root user to run this
program. However, t-*o see all available environment
information, run this program as the root user.
Alternatively, you can run this program from the
command line, without the aid of the root menu. Type
show_env, and press Enter.
Troubleshooting
7-3
Table 7-1
Troubleshooting Menu Options (Part 2 of 2)
Menu Option
Description
Global Conditions
Server Parameters
Displays the Global Conditions Server (GCS)

Parameters Screen, described below. This option is only
available from the workstation where the GCS is
installed.
This option is displayed on the menu only if the Global
Conditions Server is installed on the computer where
the menu is accessed.
For more information, see Global Conditions Server
Parameters on page 7-15.
Configure Orbix
2000 Parameters
Enables you to modify the hostname and port number

settings of the Orbix 2000 Server.
For more information, see Configuring
Orbix2000
7-4
The Database Troubleshooting menu is used to check the availability of
space in the CONTROL-M/EM database, view database server settings
and issue direct commands to perform database troubleshooting
functions. The Database Troubleshooting menu functions can be
performed on both the computer where the database server is installed
and from a remote computer.
Select Database Troubleshooting from the CONTROL-M/EM
Troubleshooting menu, to display the following menu:
-----------------------Select one of the following options:
1
2
3
4
Interactive SQL Commands

Check Available Space
View Server Settings
Truncate Database Log
p - Previous Menu
q - Quit
To select an option from the menu, press the number/letter appearing

before the option. Each of the options is described below:
Troubleshooting
7-5
Table 7-2
Database Troubleshooting Menu Options
Menu Option
Description
Interactive SQL
Commands
Starts an interactive SQL session. This enables the user

to issue direct SQL commands and perform
troubleshooting and fixes under special circumstances.
This option should only be used when specifically
requested by Technical Support.
Check Available
Space
Checks how much space remains for the file system

and data and log components of the database. This
option can be used to check if these database
components are in danger of becoming full. If necessary
the user can allocate more space for these components.
View Server
Settings
Displays parameters used by the database server.

Prompts for which parameters to view and whether the
user wants to view on-line or capture data in a file.
Truncate Database
Log
Truncates the CONTROL-M/EM database log.

Truncating erases the log completely.
This menu option appears only when the
CONTROL-M/EM database is installed on a Sybase
Adaptive Server.
7-6
The CONTROL-M/EM workstation gateway (WS-GTW) can be
executed in various debug modes. The Gateway Troubleshooting option
is used to view and set the different debug modes for a WS-GTW. This
option is available only to the CONTROL-M/EM administrator.
The Gateway Troubleshooting option is selected from the
Troubleshooting Menu option on the CONTROL-M/EM root menu,
following menu is displayed:
-----------------------Select one of the following options:
1 - Set Debug Parameters
2 - Stop Gateway Debug Mode
p - Previous Menu
q - Quit
Select an option from the menu by pressing the number or letter

appearing before the option. Each option is described Table 7-3:
Table 7-3
Gateway Troubleshooting Menu Options
Menu Option
Description
Set Debug Parameters
Displays a list of the different debug mode settings.

Changes to debug mode settings take effect
immediately after they are applied (a) to the
specified data center. For more information, see
Debug Mode on page 7-8.
Stop Gateway Debug

Mode
Stops gateway debugging. The script prompts for

the name of the data center; the default is All. This
option immediately disables all communication
tracing for the current execution of the WS-GTW (or
all WS-GTWs). For more information,
seeCommunication Tracing on page 7-11.
Troubleshooting
7-7
Debug Mode
Communication between the CONTROL-M/EM workstation gateway

(WS-GTW) and the graphical user interface (GUI) processes or
CONTROL-M host computers can be executed in various debug modes.
The Set Debug Parameters option on the Gateway Troubleshooting
menu lists the different modes in which this communication can be run
and allows the user to change the settings for each active WS-GTW.
Note
CONTROL-M/EM performance is somewhat slower and requires more

resources when operating in debug mode. It is recommended that the
user activate debug mode only when absolutely necessary and revert to
normal mode as soon as possible.
The Set Debug Parameters option displays the following menu:
Gateway - Set Debug Parameters Menu
----------------------------------1) Stop the Gateway...................... :
2) Do New Download....................... :
3) Stop Gateway Debug Mode (All)......... :
4) Set Database Debug Mode............... :
5) Set Debug Mode (GUI).................. :
6) Set Debug Mode (HOST)................. :
7) Truncate Communication Messages....... :
8) Include Keep Alive Messages........... :
9) Include Job Messages.................. :
10) Include Download Messages............. :
11) Include Active JCL.................... :
12) Include Link Level (HOST) Messages.... :
13) Include Link Level (GUI) Messages..... :
a) Apply to Gateway
c) Clear Flags From Screen
p) Return to Previous Menu
q) Quit
7-8

before the option. Each option is described below. After changing the
desired settings, select Apply (a) to apply the changes to the appropriate
gateway. You are prompted for the name of the gateway (data center).
Changes to the debug settings take effect immediately. Changes to
WS-GTW settings affect all users. Only the CONTROL-M/EM
administrator can access this menu.
Table 7-4
Set Debug Parameters Menu Options (Part 1 of 2)
Menu Option
Description
Stop the Gateway
Stops the gateway.
Do New
Download
Downloads the Active Environment from the

CONTROL-M database in the data center to the
Stop Gateway
Debug Mode (All)
Stops debug mode for the gateway. Both the Set

Debug Mode (GUI) and Set Debug Mode (Host)
parameters (described below) are set
to n. For more information, see Communication
Tracing on page 7-11.
Set Database
Debug Mode
Setting this parameter to a value between 1-9 produces

a trace of all database operations performed for the
WS-GTW. The Database Trace is written to the
Gateway Log file. For more information, see Gateway
Log on page 7-12.
Use this option only when instructed to do so by
Technical Support. This option can slow performance
and requires extra disk space.
Set Debug
Mode (GUI)
Setting this parameter to Y enables communication

tracing for the GUI: All messages transferred between
the WS-GTW and the GUI are written to the Gateway
Log file. For more information, see Gateway Log on
page 7-12. Communication tracing takes effect
immediately. Every time the gateway is restarted, you
must restart tracing, as well. For more information, see
Communication Tracing on page 7-11.
Troubleshooting
7-9
Table 7-4
Set Debug Parameters Menu Options (Part 2 of 2)
Menu Option
Description
Set Debug Mode

(Host)
Setting this parameter to Y enables communication

tracing for the data center. All messages transferred
between the WS-GTW and DC-GTW are written to the
Gateway Log file. For more information, see Gateway
Log on page 7-12. Communication tracing takes
effect immediately. Every time the gateway is restarted,
you must restart tracing, as well. For more information,
see Communication Tracing on page 7-11.
Truncate
Communication
Messages
Setting this parameter to Y truncates all trace messages

to a single line.
Include Keep Alive

Messages
Setting this parameter to Y includes trace messages

from the host computer. These messages indicate
whether the host is listening.
Include Job
Messages
Setting this parameter to Y includes trace message

about Active Job updates and downloads, and job
Scheduling definition updates and downloads.
Include Download
Messages
Setting this parameter to Y includes all download trace

messages related to communication, index creation,
and network creation.
Include Active
JCL
Setting this parameter to Y includes all JCL file data and

messages transmitted from an OS/390data center.
Include Link Level

(Host) Messages
Setting this parameter to Y includes all low level host

communication debugging messages. This parameter
should only be used at the request of Technical Support.
Include Link Level

(GUI) Messages
Setting this parameter to Y includes all low level GUI

communication debugging messages. This parameter
should only be used at the request of Technical Support.
Apply to Gateway
Applies the flags shown on the screen to a specific

gateway or to all gateways. You are prompted for the
name of the gateway. Specify All to apply the settings to
all gateways.
Clear Flags From

Screen
Clears all the parameter settings (flags) from the screen

(not from the database).
7-10
Gateway Verification Utility (check_gtw)
The Gateway Verification utility (check_gtw) is used to verify the

availability of the gateways. The utility checks all currently enabled data
centers to verify if their gateway is running. If any check fails, an Alert is
sent to the specified e-mail address. For a full description of check_gtw,
see the Administration Utilities chapter of the
CONTROL-M/Enterprise Manager Utilities Reference Guide.
Communication Tracing
Communication tracing is an analytical tool that enables you to save all

messages that are transferred between an CONTROL-M/EM workstation
gateway (WS-GTW) and a data center gateway (DC-GTW) or
CONTROL-M/EM GUI.
Note
Communication tracing should be used with caution because it slows

down communication between WS-GTWS and DC-GTWs.
Communication tracing can be enabled using any of the following
methods:
Set the Set Debug Mode (GUI) or Set Debug Mode (Host)
parameter to Y with Troubleshoot Menu => Gateway
Troubleshooting => Set Debug Parameters from the
CONTROL-M/EM root menu, described in CONTROL-M/EM
Root Menu on page 5-1. Message tracing takes effect immediately.
It is not necessary to stop and restart the WS-GTW. Messages are
written to the Gateway Log file, described in Gateway Log on
page 7-12.
Troubleshooting
7-11
Use the ctl utility, described in Gateway Verification Utility

(check_gtw) on page 7-11. Messages are written to the Gateway
Log file, described in Gateway Log on page 7-12. When enabled
using this method, tracing is not automatically continued the next
time the gateway is restarted. Debug parameters set with Gateway
Troubleshooting => Set Debug Parameters are ignored when using
this method: These debug parameters can be added to the trace by
selecting and applying them after the trace is active.
Communication tracing can be disabled using any of the following

methods:
Turn off (set to N) the Set Debug Mode (GUI) or Set Debug Mode
(Host) parameter with Gateway Troubleshooting => Set Debug
Parameters from the CONTROL-M/EM root menu. Tracing is
disabled immediately. Tracing is not enabled when the WS-GTW is
restarted.
Select the Gateway Troubleshooting => Set Debug Parameters =>

Stop Gateway Debug Mode (All) option from the
CONTROL-M/EM root menu. Tracing is disabled immediately and
both the Set Debug Mode (GUI) and Set Debug Mode (Host)
parameters are set to N. Tracing is not enabled when the WS-GTW is
restarted.
Select the Gateway Troubleshooting => Stop Gateway Debug

Mode option from the CONTROL-M/EM root menu. This option
can be used to disable tracing for all WS-GTWs on the computer.
Tracing is disabled immediately. Both the Set Debug Mode (GUI)
and Set Debug Mode (Host) parameters are set to N. Tracing is not
enabled when the WS-GTW is restarted.
Gateway Log
All information and error messages displayed by a WS-GTW are saved

in a special log file, located in the following directories:
<home-directory>/log/ (on Unix)
\$HOME\Gtwgcs\ECS_HOME_NAME\log (on Windows)
7-12
The Gateway Log file name has the following format:
gtw_log.<data center >.yyyymmdd.n.
where:
Table 7-5
Gateway Log Filename Parameters
Parameter
Description
<data_center>
Name of the data center.
yyyymmdd
Current date.
Sequential number for the day. Default: 0.
Core File
Whether in debug mode or normal mode, a dump file called core is

created if an error occurs which causes either a WS-GTW or GUI process
to stop. This file can be printed and analyzed by Technical Support staff.
For IOA 6.x.x
Performance information is obtainable from two sources: IOAGATE and

the CONTROL-M application server (CTMAS).
CTMAS performance information is equivalent to IOAGATE
performance information and it is extracted with modify commands to
CTMAS.
To start CTMAS with download and update statistics activated, CTMAS
JCL should have a DDNAME DATRCIN that points to a member that
includes the following line:
TRACE=122
To start download and update statistics after CTMAS has been

started:
Troubleshooting
7-13
Specify the following modify command:

F <CTMASID>,TRACE=122
where <CTMASID> is the identifier of the CTMAS started task. This

identifier is assigned by IOAGATE when it starts CTMAS. If, for
example, IOAGATE starts CTMAS with the command
S
CTMAS.CTMAS601
The part to the right of the period (CTMAS601) is the identifier.

For IOAGATE performance information, see Section 9 "IOAGATE",
"Command: STATALL," in the INCONTROL for OS/390, Version 6.0.01
Administration Guide.
For IOA 5.x.x
ECSGATE can be set to enable you to view information regarding

download and update communication statistics. This information can
help determine the source of communication performance problems.
To output statistics to mainframe Sysout:
Start ECSGATE with the following command:
S
ECSGATE,DEBUG=122
-orModify ECSGATE with the following command:

F
ECSGATE,DEBUG=122
7-14

The Global Conditions Server Parameters menu is used to view and
modify the parameter settings for the Global Conditions Server (GCS).
This option is available only to the CONTROL-M/EM administrator and
can only be accessed from the workstation where the GCS is installed.
To access the Global Conditions Server Parameters menu:
1. Sign on to the workstation as the Unix user under whose home
directory CONTROL-M/EM was installed.
2. Enter the root_menu command at the Unix prompt.
3. Enter the CONTROL-M/EM administrator log on name and
password.
4. Select Global Conditions Server Parameters from the
CONTROL-M/EM root menu.
When selected, Global Conditions Server Parameters displays the
following menu:
Global Conditions Server Parameters:
Diagnostics:
1) Communication Diagnostic Message Level.....0
2) Database Diagnostic Message Level..........0
Communication:
3) Gateway Connectivity Interval..............10
4) Refresh Communication Table Interval.......600
Conditions:
5) Send Condition Interval....................180
6) Maximum Send Condition Retries.............5
7) Delete Time for Sent Conditions............120
8) Delete Time for Unsent Conditions..........36000
9) Send Condition Group Interval..............60
10) Maximum Conditions in a Group..............100
11) Delete Time for Unused Conditions..........86400
12) Destination Status Interval................30
13) Method for Handling Conflicting Conditions.1
Troubleshooting
7-15
s)
r)
h)
p)
q)
Restore Default Parameters

Run Global Conditions Server
Help
Return to Previous Menu
Quit

before the option. These options are described Table 7-6, Global
Conditions Server Parameters G, on page 7-16.
Table 7-6
Global Conditions Server Parameters (Part 1 of 2)G
Parameter
Description
Communication
Diagnostic
Message Level
Level of GCS communication diagnostic messages.

These messages are written to log file gcs_log.###.
Diagnostic messages are written for both conditions
received (In) and conditions sent (Out). The following
levels are available:
0 No diagnostic messages (Default)
1 Both In and Out messages
2 In messages only
3 Out messages only
Database Diagnostic
Message Level
Level of GCS database diagnostic messages. These

messages are written to log file gcs_log.###. The
following levels are available:
0 No diagnostic messages (Default)
1 Database messages
Gateway
Connectivity Interval
Interval (in seconds) between attempts to

communicate with a gateway. Default: 10.
Refresh
Communication
Table Interval
Interval (in seconds) between readings of the

Communication Table in the CONTROL-M/EM
database for new data centers. Default: 600.
Send Condition
Interval
Interval (in seconds) between attempts to send

conditions to a data center that had previously
returned a temporary error. Default: 180.
Maximum Send
Condition Retries
Maximum number of retries to send conditions to a

data center that had previously returned a temporary
error. Default: 5.
7-16
Table 7-6
Global Conditions Server Parameters (Part 2 of 2)G
Parameter
Description
Delete Time for Sent

Conditions
Minimum time (in seconds) global conditions wait in

memory, after they have been sent to all connected
data centers, before they are removed. This waiting
period prevents conditions from being broadcast
again. Default: 120.
Delete Time for

Unsent Conditions
Time (in seconds) unsent global conditions wait in

memory before they are removed. Default: 36000 (10
hours).
Send Condition
Group Interval
Interval (in seconds) between sending groups of

conditions to a reconnecting data center.
Default 60.
Maximum
Conditions in a
Group
Maximum number of messages to send in a group to

a reconnected data center.
Default: 100.
Delete Time for

Unused Conditions
Maximum time (in seconds) unused conditions wait in

the database before they are removed. These
conditions may have had no data center destinations.
Default: 86400 (24 hours).
Restore Default
Parameters
Restore the parameters to their default settings
Run Global
Conditions Server
Start the GCS. The GCS can also be started using

the Activation Menu => Start Global Conditions
Server option from the CONTROL-M/EM root menu.
Destination Status
Interval
Interval (in seconds) between checks of the status of

conditions distribution to their respective destinations.
Default: 30. Increase for this value large systems.
Method for Handling

Conflicting
Conditions
A conflicting condition is a request to add or delete a

condition when the opposite action is currently in
process for a request for a condition with the same
name and date.
0 Stop distribution of the current condition and
start the distribution of the new condition.
1 The first conflicting condition is processed
(same as 0) but all subsequent conflicting
conditions are ignored. Default.
2 All conflicting conditions are ignored.
Troubleshooting
7-17
Configuring Orbix2000 Parameters

When selected, Configure Orbix2000 Parameters enables you to
modify the hostname and port number parameters for the Orbix Server or
the Orbix client. You are prompted with the following question:
Do you want to configure orbix server (s/c)? (s
for server, c for client , q for quit)
Make the appropriate selection.

If you are logged on host computer of the Server or client whose
parameters you are modifying, you can modify the port number only.
Note
Modifying other Orbix 2000 Server parameters requires considerable

knowledge of Orbix. Modifying these parameters only after consulting
BMC Software Technical Support.
7-18
DIAG Diagnostics Facility

The DIAG diagnostics facility collects information from specified
CONTROL-M/EM components for troubleshooting analysis. This
information is collected in a log file.
Note
Use the DIAG diagnostics facility only when you are instructed to do so
by a representative of the BMC Software Customer Support staff. Only
members of the support staff are qualified to use the data collected by the
DIAG facility. However, a Support Staff employee may request that you
run this facility and send the output to BMC Software for analysis.
DIAG Debug Message Logging

The DIAG diagnostics facility starts a debugging trace for a component
that you specify. Debugging messages are written to a log file that is
associated only with the component being debugged. The diagnostic
level, which determines the number and type of messages written to the
log file, is specified in the components DIAG initialization (.ini) file.
The range of values is 0-7, where 0 records only the most severe error
messages (such as notification of component failure).
Log messages are recorded in either a single log file of unlimited length
or a series of cyclical log files. DIAG creates log files automatically.
They are stored in the \$Homology directory of the local computer. The
environment variable for the logs is $ECS_LOG_PATH. You determine
the number and length of the cyclical log files using parameters in an
initialization file for the monitored component. For more information,
see Initialization Files on page 7-20. When the last cyclical log file is
full, DIAG begins to overwrite the messages in the first log file.
Troubleshooting
7-19
Log files have a special naming convention that enables you to identify
them readily:
Non-cyclic log file:
<prefix>_diag.<component_hostname>.txt
for example: gas_diag.ACCT12.txt
Cyclic log file:
<prefix>_diag.<component_hostname>.<date>.
<serial_number>.txt
for example: gas_DiagLvls.ACCT12.20010318.0001.txt
The log filename is case-sensitive.
The filename date format is YYYYMMDD.
The <prefix> variable is described in Syntax Rules on page

7-22.
The serial number for each file is four digits long, and is incremented
for successive files (0001, 0002, and so on).
Initialization Files
For most CONTROL-M/EM components, the DIAG facility is activated
by the presence of an .ini file that you create. For the GUI server only,
this facility can be activated and deactivated by a command.
Note
The DIAG facility for the GUI server is activated and deactivated from
the command line. However, the .ini file is still needed to configure the
facility. For more information about using DIAG with a GUI server, see
Using DIAG with a GUI Server on page 7-23.
7-20
This following information can be specified in an .ini file:
The level of message detail written to the output file (debug level)
Whether to use a cyclic log file or a fixed log file
The size of the cyclic log file (fixed log files are of unlimited size)
The component program file that is monitored. The name of this file
is supplied by BMC Software Technical Support.
Separate .ini files can be created for each component that must be
monitored. In addition, you can create a default file that contains a
default debug level value that applies to all components on the computer.
.ini files can be used in the following combinations:
A single default file for all components on the computer

Separate files for each component that you want to monitor
A default file for all components on the computer and individual
component files to address components that are exceptions
Note
When both a default .ini file and a separate component .ini files are used,
the values in the .ini component file override the default .ini file values.
.ini files are saved to the \$HOME\Ini directory on the computer on
which the component is installed. The .ini file environment path is
$ECS_INI_PATH.
Creating an Initialization (.ini) File
To create a file:
1. Open a text editor.
2. Enter the parameters and values supplied by BMC Technical
Support. Parameters are described in Table 7-7, DIAG Initialization
(.ini) File Parameters, on page 7-23.
3. Name the file according to the conventions described below and save
it to the \$HOME\Ini directory.
Troubleshooting
7-21
Naming Conventions
.ini files are text files using the following naming conventions:
Default .ini filename: DiagLvls.ini
Component .ini filename: <prefix>_DiagLvls.ini
Syntax Rules
Filename component prefixes are:
gas (Global Alerts Server)

gsr (GUI Server)
maint (Administration agent)
alertX Alerts window)
ecs (CONTROL-M/EM GUI)
mdesk (CONTROL-M/Desktop)
tbloader (Loader process)
vrfy (Verify User process)
ctl (ctl utility)
lm (License client)
The ini. filename and its contents are case-sensitive.
A parameter is followed by a space and the value:

<parameter> <value>
.ini file attributes are described in Table 7-7. A sample .ini file is
displayed in the example following Table 7-7.
7-22
Table 7-7
DIAG Initialization (.ini) File Parameters
Parameter
Description
IsCyclic
Indicates whether the file is cyclic. The default value is 0

(non-cyclic). Optional. If you do not include this variable
in the file, the file is not cyclic.
Valid Values:
0 (Default)
1
NumOfFiles
Maximum number of cyclic files to create. Mandatory

only if IsCyclic=1.
NumOfMessages
Maximum messages in each cyclical file. Mandatory

only if IsCyclic=1.
*default
Minimum debug level of the DIAG debug trace for the

component. Default: 0.
Valid values: 0-7.
<filename>
<debug_level>
A debug level is specified for a component with the

following syntax: <filename> <debug_level>.
Note: <filename> is supplied by Technical Support.
Example
IsCyclic 0
NumOfFiles 3
NumOfMessages 5000
gas_srv 7
gas_impl 7
*default 3
Using DIAG with a GUI Server

To use the DIAG facility with a GUI server, you must start the program
from a command line. You must still create an .ini file to configure the
DIAG facility.
Troubleshooting
7-23
DIAG is controlled with three commands (described in Table 7-8).

Table 7-8
DIAG Commands
Command
Description
DIAGON
Starts DIAG.
DIAGOFF
Stops DIAG.
DIAGL
Determines the debug level.

Syntax:
DIAGL <filename> <debug_level>

Where <filename> is the name of a file supplied by BMC
Software Technical Support and <debug_level> is a
number from 0-7.
Example:
DIAGL main 4
To enter a DIAG command on the GUI server host computer:

1. Choose Start => Enterprise Controlstation => GUI Server to
display the GUI Server window in Windows, or go to the GUI
Server window in Unix.
2. Enter one of the following commands:
DIAGON
DIAGOFF
3. Minimize the GUI Server window.
7-24
To enter a DIAG command for a GUI server on a remote computer:

1. Choose Start => Programs => Command Prompt to display the
Command Prompt window in Windows, or go to the command
prompt in Unix.
2. Enter the following command:
RSI <GUI_server_hostname>
The command prompt emulates the command prompt of the remote
machine.
3. Enter one of the following commands:
DIAGON
DIAGOFF
4. Type EXIT to end the RSI session.
Troubleshooting
7-25
7-26
Customization
Various CONTROL-M/Enterprise Manager (CONTROL-M/EM)

elements must be customized to suit the requirements of your
installation. The CONTROL-M/EM administrator and the database
server administrator can customize CONTROL-M/EM and the database.
The CONTROL-M/EM administrator is defined during installation and is
protected by a password.
This chapter describes the following CONTROL-M/EM elements and
their customization:
Customizing System Defaults:

Alert Data Processing
Defaults File (Global Conditions Distribution, duplicate index
entries, multiple index entries).
SQL Server Configuration

Sybase
Oracle
Customization
8-1
Not all aspects of CONTROL-M/EM customization are covered in this

chapter. For a description of administrator-modifiable system parameters,
see Appendix C, System Parameters. These parameters are modified
using the System Parameters window of the Administration facility. For
more information, see Displaying and Modifying System Parameters
on page 4-33.

Each data center (CONTROL-M) included in the centralized control of
the job production environment must be identified to CONTROL-M/EM
and included in the CONTROL-M/EM database. The CONTROL-M/EM
administrator defines the data centers and specifies how these data
centers communicate with CONTROL-M/EM. Choose Tools =>
Communications => Administration in the CONTROL-M/Enterprise
Manager GUI to define data centers.
Customizing System Defaults

Several operational features of CONTROL-M/EM can be customized to
suit users preferences. These features contribute to the ease and
efficiency of operating CONTROL-M/EM. The features are modified by
changing the values of the their operational parameters. System
parameters are described in Appendix C, System Parameters.
Parameters can be modified with the Administration facility. For
information about modifying the values of the parameters with the
Administration facility, see Displaying and Modifying System
8-2
Alert Data Processing

The Alert Data Processing facility is used to activate processes based on
data contained in a generated Alert. This facility allows the user to send
data from an Alert to an SNMP trap and/or as input to a script. For
information on SNMP, see Appendix A, SNMP Interface.
When Alert data is sent as input to a script, the parameters are sent in the
following format:
call_type: "<value>" alert_id: "<value>" data_center
"<value>" memname: "<value>" order_id: "<value>"
severity: "<value>" status: "<value>" send_time:
"<value>" last_user: "<value>" last_time: "<value>"
message: "<value>" owner: "<value>" group: "<value>"
application: "<value>" node_id: "<value>" job_name:
"<value>"
This facility is activated according to system parameters

SendAlarmToScript and SendSnmp, that are set with the System
Parameters window of the Administration facility.
Table 8-1
Alert Data Processing Parameters
Parameter
Description
SendAlarmToScript
Full path name of the script that receives the Alert

data. If the file does not exist, an appropriate
message is displayed on the gateway trace. If the
gateway is started with Trace Level 3 (most detailed),
an appropriate message is displayed when the data is
sent to the script.
For audio support, the full path name of the

audio script is: $ECS_HOME/scripts/play_alert
SendSnmp
Indicates where the data is to be sent:

0 Send data to SNMP only. Default.
1 Send data to script only.
2 Send data to both script and SNMP.
Note: For audio support, specify either 1 or 2.
Customization
8-3
Audio Support for Alerts
A special audio script (play_alert) is available for audio support for

Alerts. Audio support is available for local installations when the user
logs on to the console as an CONTROL-M/EM user. It is not available
for distributed installations and not available when using emulation
software (for example, Exceed).
To use audio support, activate the Alert Data Processing facility
specifying $ECS_HOME/scripts/play_alert in SendAlarmToScript
and specify 1 or 2 in SendSnmp. This script is only activated for new
Alerts.
Defaults File
The CONTROL-M/EM defaults file (Defaults.rsc) is used to customize
the parameters used by special CONTROL-M/EM facilities. These
facilities include:
Global Conditions Distribution

Duplicate Index Entries
Multiple IP Addresses
Network View Authorizations
Global Conditions Distribution
The Global Conditions Distribution facility enables the user to specify or

remove date limitations for distributing global conditions. The default
specifies that global conditions are distributed to data centers only within
seven days of their defined condition date.
With the Global Conditions Distribution facility, the user can indicate
whether to limit the distribution of global conditions, specify a range of
days for which global conditions can be distributed, and provide a list of
condition dates that should be excluded from the limitation process (so
that global conditions with these dates have no distribution limitation).
8-4
The Global Conditions Distribution facility is activated according to the

following parameters in the \$HOME\appl\ecs\resource\Defaults.rsc
file:
Table 8-2
Parameters for the Global Conditions Distribution Facility
Parameter
Description
limit_gcs_distrib_
max_days
Range of days for which conditions can be

distributed. Default: 7.
limit_gcs_distrib
_activate
Enable/Disable Global Conditions Distribution

facility. Valid values:
1 Enable distribution facility. Default.
0 Disable distribution facility. No limitations.
limit_gcs_distrib
_disable_dates
Dates to exclude from the distribution facility. Dates

are specified in MMDD format and separated with
commas. Default: STAT, 0101.
The format for parameter settings in the Defaults.rsc file is:

<group>
<parameter>
<value>
Example 1
To specify that global conditions can be distributed within 28 days from

their original condition date and exclude conditions with special dates
that indicate any date (0101 and STAT):
namevalue * limit_gcs_distrib_max_days 28
namevalue * limit_gcs_distrib_activate 1
namevalue * limit_gcs_distrib_disable_dates STAT, 0101
Example 2
To disable the Global Conditions Distribution facility and remove all date
limitations on the distribution of global conditions:
namevalue * limit_gcs_distrib_activate 0
Customization
8-5
Example 3
The addition or deletion of conditions in each data center is attributed to

a special Global Conditions Server userid (GCSERV). This default userid
can be changed with the comm_userid parameter in the Defaults.rsc
file. To change the default, add the following line to the file:
GCS * comm_userid <new GCS userid>
Duplicate Index Entries
The Duplicate Index Entries facility allows the CONTROL-M/EM

gateway to continue processing a CONTROL-M download even it
encounters duplicate index entries in a table.
When the CONTROL-M/EM gateway receives data with duplicate index
entries (such as Job ID, In Conditions, and so on), transmission is
terminated. CONTROL-M then attempts to download again and the error
cycle is repeated.
The Duplicate Index Entries facility is activated according to the
following parameter in the appl\ecs\resource\Defaults.rsc file:
namevalue * continue_with_dup 0
Values for this parameter are:

0
No change. Transmission is terminated. Default.
Duplicate data is inserted in the appropriate table in the database, but

no indexes are built for that table. Access to the table is slower
without indexes. A message identifying the duplicate data is displayed
during the download. Additionally, the duplicate entry is not displayed
in the CONTROL-M/EM GUI.
When duplicate index entries are encountered, the CONTROL-M/EM

gateway sends a message to the user recommending that the
continue_with_dup parameter be changed to 1. During the next
download, the new value becomes effective.
To recreate indexes, delete the duplicate data in CONTROL-M and
perform a new download.
8-6
Multiple IP Addresses
If the CONTROL-M/EM gateway runs on a computer with more than

one IP address, the gateway can be accessed with all the IP addresses of
the computer. The use_all_ip_address parameter, in the
appl/ecs/resource/Defaults.rsc file, specifies whether the gateway
should use only one IP address (0) or all the IP addresses (1). The default
is 0.
The format for parameter settings in the Defaults.rsc file is:
namevalue * use_all_ip_address 0
Network View Authorizations
The Network View Authorization window in the Security Facility

determines the users ability to access certain functions available under
CONTROL-M/EM. The type of access authorized is indicated by the
Access parameter. The Read Only mode permits the user to view
specified entities and perform Hold, Run and Delete actions on jobs in
the active environment.
To restrict this mode to only viewing the entities and not performing any
actions on jobs in the active environment, set parameter
act_view_only_option to 1 in the Defaults.rsc file. The default is 0.
namevalue * act_view_only_option
For additional information, see Chapter 6, Security.

Duplicate Out Conditions
If your site uses duplicate Out Conditions for a job, it is necessary to

comment out (#) the index (ix_o) entry for Out Conditions in the
lnko_p.td file in the appl\ecs\db_schema\desc\actdesc directory.
Customization
8-7
SQL Server Configuration

Certain parameters of the database servers used with CONTROL-M/EM
are modified during CONTROL-M/EM installation. The modifications
improve the performance of the database servers when they are used in
conjunction with CONTROL-M/EM.
Sybase
The SQL configuration parameters in Table 8-3 are modified or added to
the SYBASE.cfg file during CONTROL-M/EM installation to improve
the performance of the Sybase Adaptive Server:
:
Table 8-3
Sybase Adaptive Server Parameters
Parameter
Description
recovery interval
in minutes
Changing this parameter changes the overhead of the

recovery checkpoint in Sybase. The value is 10.
procedure cache
percent
This parameter defines the memory allocated to cache

procedures. If you use the import_def_table or
export_def_table utilities or you need more memory for
some other utility, increase this value. When the
CONTROL-M/EM database is 200 MB or less in size,
the value is 20. The value is 5 when the
CONTROL-M/EM database exceeds 200 MB in size.
number of
pre-allocated
extents
This parameter specifies the number of extents

allocated in a single trip to a page manager. By
increasing this number, the download takes less time.
The default value is not changed. When the database is
smaller than 80 MB. When the database is 80 - 200 MB,
the value is 8. When the database is larger than 200
MB, the value is 16.
8-8
Oracle
The Oracle Server configuration parameters in Table 8-4 are modified or
added to the initdatabasename.ora file during CONTROL-M/EM
installation to improve the performance of the Oracle Server:
Table 8-4
Oracle Server Parameters
Parameter
Description
log_checkpoint
_interval
Number of information blocks modified between the log

file checkpoint procedures.
Setting changed to 0. The procedure is performed only
when the log is full.
log_checkpoint
_timeout
Time, in seconds, between log file checkpoint

procedures.
Setting changed to 0. The procedure is performed only
when the log is full.
db_block_size
Number of bytes per block, partially determining the size

of the buffer cache. Setting changed to 4096.
db_block_buffers
Number of blocks in the buffer, partially determining the

size of the buffer cache. Setting depends on the size of
the database installed.
shared_pool_size
Size of the shared pool in bytes. Setting depends on the

size of the database installed.
log_buffer
Size of the log buffer, in bytes. Setting depends on the

size of the database installed.
sort_area_size
Amount of memory (in bytes) used for a sort. Setting

depends on the size of the database installed.
Customization
8-9
8-10
SNMP Interface
One of the most powerful components in the CONTROL-M/Enterprise

Manager (CONTROL-M/EM) management by exception arsenal is the
use of Alerts. By having jobs issue alert messages when an abnormal
situation is encountered, CONTROL-M/EM enables you to focus
attention on those areas requiring human intervention, while allowing
other production jobs to continue.
CONTROL-M/EM carries this concept one step further by enabling
alerts to be directed to a Network Management application, allowing the
network manager to be included in the list of alert recipients.
This chapter describes how to interface CONTROL-M/EM with the
following network management applications:
CONTROL-O/Server.
PATROL Enterprise Manager
HP-OpenView.
NetView for AIX.
Tivoli Management Environment Console.
CONTROL-M Links for Distributed Systems
SNMP Interface
A-1
Overview
The Simple Network Management Protocol (SNMP) helps network
managers locate and correct network problems (usually in a TCP/IP
network). Managers invoke an SNMP client (usually under a network
management application such as those listed above) on their local
machine and use the client to contact one or more SNMP servers (or
agents) that execute on remote machines.
SNMP uses a fetch-store (get-set) paradigm in which each server
maintains a set of conceptual variables that include simple statistics, such
as packet counters, as well as complex variables that correspond to
TCP/IP data structures, such as ARP cache and IP routing tables.
SNMP messages specify that the server should either retrieve values
from variables or store values in variables. The server translates the
requests to equivalent operations using local data structures. In addition
to the fetch-store protocol, a separate standard for a Management
Information Base (MIB) defines the set of variables that SNMP servers
maintain, as well as the semantics for each variable.
A special SNMP message type, called a trap message, is the only type
that is initiated by a server. A trap message informs the client about an
event that has occurred at the servers machine, usually a failure event
(hardware or software, permanent or temporary). Customization at the
clients site determines, according to the trap codes, whether an Alert
message should appear on the managers screen or whether the recording
of an event log message is sufficient. The trap message can carry
additional MIB variables, thereby providing additional information to the
client application.
A-2
CONTROL-M/EM and SNMP Traps

When an alert is posted to the Alerts window or an existing alert is
changed by an CONTROL-M/EM user, a standard SNMP trap message
can optionally be issued to the relevant network management
applications host.
CONTROL-M/EM functioning, including the generation of a trap message,
is not affected in any way if the management application is not active.
The generated SNMP traps are Enterprise-specific traps (that is, field
generic-trap is set to 6).
SNMP Trap Format

SNMP traps issued using CONTROL-M/EM consist of the following
fields:
Table A-1
SNMP Trap Format (Part 1 of 2)
Field
Description
CALL TYPE
Single character indicating the type of event that

triggered the alert:
I A new alert was issued.
U An existing alert by an CONTROL-M/EM user
was updated.
ALERT ID
Numeric value used as a key (index) to identify the

alert.
DATA CENTER
Name of the data center to which the job belongs.
MEMNAME
Mem Name of the job.
ORDER ID
Order ID of the job.
SEVERITY
Severity of the alert:

V Very urgent.
U Urgent.
R Regular.
STATUS
Values: Not noticed, Noticed, or Handled.
SEND TIME
Time/date that the alert was issued. Format:

YYYYMMDDHHMMSS.
SNMP Interface
A-3
Table A-1
SNMP Trap Format (Part 2 of 2)
LAST USER
Name of the last CONTROL-M/EM user who

changed the status or text of the alert.
LAST TIME
Time/date that the alert was last modified by the

user.
10
MSG TEXT
Full text of the alert.
11
OWNER
Owner of the job
12
GROUP
Group of the job
13
APPLICATION
Application of the job
14
JOB NAME
Name of the job
15
NODE ID
Identification number of the job
SNMP traps can be issued using either or both of the following formats:
Single Variable
Note
This was the only format available in previous releases of

CONTROL-M/EM.
The trap is contained in one SNMP variable. This variable is a string
consisting of the 16 fields (described above) separated by blanks.
There are three specific traps:
Specific-trap 1: Regular CONTROL-M/EM alerts.
Specific-trap 2: Urgent CONTROL-M/EM alerts.
Specific-trap 3: Very urgent CONTROL-M/EM alerts.
Multiple Variables
The trap consists of 11 distinct SNMP variables (as described above).
There is one specific trap type:
Specific-trap 10: CONTROL-M/EM alerts.
A-4
Customization
The customization procedures, described below, are required to support
SNMP traps issued by CONTROL-M/EM.
The following parameters must be modified in CONTROL-M/EM:
Table A-2
CONTROL-M/EM Customization Parameters
Parameter
Description
SnmpSendActive
Set this parameter to 1 to enable or 0 to disable sending

Alert traps from CONTROL-M/EM while in active
(production) mode.
SnmpHost
Change the string host_name to the name of the

network node manager host.
SendSnmp
Set this parameter as follows:

0 Send data to SNMP only. Default.
1 Send data to script only.
2 Send data to both script and SNMP.
SnmpSendFormat
Set this parameter as follows:

0 Single Variable format.
1 Multiple Variables format.
2 Both formats. Two traps are generated, one in each
format.
To modify each SNMP parameter:
1. Open an MS-DOS window.

2. Change your working directory to the Gtwgcs directory.
3. Specify the following command:
db_sys_params -U<user id> -P<password>
-N<name> -V<value>
The command parameters are described in Table A-3.
SNMP Interface
A-5
Table A-3
SNMP Parameter Modification Command Terms
Term
Description
<user id>
CONTROL-M/EM database user name (for

example, cemuser).
<password>
CONTROL-M/EM database user password.
<name>
Name of the parameter to be modified (Only one

parameter at-a-time).
<value>
Value to be assigned to the specified parameter.
Example
db_sys_params -U<CONTROL-M/EM_username>
-P<password> -NSendSnmp -V1
4. Repeat the command for each parameter to be modified.
How the network management application interprets trap codes (for
example, present as alerts, under an event category) is
determined by the customization of the network management
application itself.
Examples for customizing network management applications are
shown below. The application must first be customized so that it
recognizes the Enterprise ID of CONTROL-M/EM. Next, the
corresponding trap codes must be defined.
Customizing CONTROL-O/Server
For information about customizing CONTROL-O/Server, see the
section on SNMP trap configuration in the CONTROL-O/Server for
Windows NT Installation Guide.
A-6
Customizing HP-OpenView
The /usr/OV/conf/$LANG/trapd.conf file contains definitions for the
handling of SNMP traps and events. It includes how to format their log
entries and what action to take, if any, when they are logged. The formats
are also used to display messages in the OpenView Events window.
This file can be edited using the Options Event Configuration =>
SNMP option of HP OpenView Network Node Manager, or you can edit
this file with a text editor.
To support the SNMPTRAP feature of CONTROL-M/EM, add the
following entries to the trapd.conf file:
An Enterprise Definition for ECS_4D, using the private object-ID of

the product:
ECS_4D
1.3.6.1.4.1.954.1
Syntax of an Event Definition:

Trapname statement, consisting of the following parameters:
<trap_name>, <enterprise_obj-id>,
<generic_trap_num>, <specific_trap_num>,
<source_id>, <category>, <severity>
where <severity> is a number ranging from 1 through 5,
corresponding to the following levels:
normal (1)
warning (2)
minor (3)
major (4)
critical severity (5)
Example 1
Single Variable format:
SNMP Interface
A-7
ecs_alert_v
1.3.6.1.4.1.954.1
application alert events"
5
6 3
"
ecs_alert_u
1.3.6.1.4.1.954.1
4
6 2
"
ecs_alert_r
1.3.6.1.4.1.954.1
3
6 1
"
6 10
"
Example 2
Multiple Variables format:

ecs_alert
1.3.6.1.4.1.954.1
4
Statement Syntax
Format statement
This is the string which is displayed in trapd.log and in the Event
Browser window as a result of the trap described above. This is in
addition to the standard display of the alert which is based on the trap
statement.
To include information from the incoming trap, use the formatting

variables described in Table A-4.
A-8
Table A-4
Trap Message Formatting Variables
Cmd
Description
$n
Print the value of the nth variable.
$E
Print the enterprise as a text string.
$A
Print the name of the source of the trap.
$G
Print the generic trap.
$S
Print the specific trap.
$T
Print the time-stamp.
$*
Print the variable-bindings supplied by the trap as name-type:value

strings. Standard C language formatting symbols are also allowed.
Example 1
The following format statement:

shout from CONTROL-M/EM :\n$*
displays the text shout from CONTROL-M/EM together with
additional text strings which are sent as SNMP variables together with
the trap.
Example 2
This demonstrates how to display specific variables from the Multiple

Variables format trap:
shout from CONTROL-M/EM: Severity=$6, Data
Center=$3, Job=$4, Text=$11
Alternatively, you can invoke any other script or program that can
analyze the input variables and take appropriate action based on the
variables values.
SNMP Interface
A-9
Customizing NetView for AIX

1. Choose Options => Event Configuration => Trap Customization:
SNMP from the NetView main window.
2. Using the Event Configuration dialog box, insert an enterprise
definition for CONTROL-M/EM in the enterprise pane using the
private MIB object-id of the product, as follows:
A. Press the Add New Enterprise button in the Event Identification
pane.
The Add New Enterprise window is displayed.
B. Specify the Enterprise Name ECS_4D and the Enterprise ID
1.3.6.1.4.1.954.1; then press OK.
3. Select ECS_4D in the Event Identification pane. A window for
Generic and Specific events is displayed.
4. Define the three traps required for CONTROL-M/EM as described
below.
For Multiple Variables format traps:
A. Click the Add New Trap button. The Add New Trap
window is opened.
B. Select the event Enterprise Specific; then specify 10 in the
Specific Trap field.
C. Click the Add button.
For Single Variable format traps:
A. Perform steps a, b, and c (above) three times, specifying 1,
2, and then 3 in the Specific Trap field.
5. Format the message for each pair of Generic/Specific trap numbers
as follows:
A-10
A. Select a pair of Generic/Specific numbers in the Event

Identification pane. A Format Specification window is
displayed.
B. Select the Event Category Application Alert Events and choose
one of the severity levels described in Table A-5, Severity
Levels, on page A-11.
Table A-5
Severity Levels
Using format
Do this...
Multiple Variables
For Specific = 10, select the desired severity.
Single Variable
For Specific = 1, select severity Minor.

For Specific = 2, select severity Major.
For Specific = 3, select severity Critical.
C. In the Event Log Format field, insert a string to be displayed as

the event ticket of the alert.
To include information from the incoming trap, use formatting
commands as described in the Event Configuration online help.
D. Using the bottom bar, you can insert a string that will appear in
the alert window itself, using an xecho command.
Example 1
Single Variable format:

xecho
Shout
from CONTROL-M/EM:
text=$*
Example 2
Multiple Variables format:

xecho Alert from CONTROL-M/EM: Severity=$6,
Data Center=$3, Job=$4, Text=$11
SNMP Interface
A-11
Alternatively, you can invoke any other script or program that can
analyze the input variables and take appropriate action based on the
variables values.
For additional information on formatting commands for this string, see
the online help available in the Event Configuration window.
A-12
Customizing Tivoli Management Environment Console

1. Check for the existence of another SNMP monitoring agent on the
CONTROL-M/EM workstation.
2. Check the output of netstat -an for any other registered use of UDP
socket 162. If another product is using this socket, the Tivoli SNMP
Event Adapter cannot be configured.
3. Verify that the Tivoli SNMP Event Adapter software has been
installed on the CONTROL-M/EM workstation.
Note
Step 3 should be performed by the Tivoli systems administrator.

4. Edit the file tecad_snmp.conf to include the proper Event Server
Location:
Location
Format
Non-TME, non-secure
<hostname>
TME
@<EventServer>
TME in connected TMR
@<EventServer>#<RegionName>
An example for location TME in connected TMR is:

@server01#west
The default location for the file is /etc/Tivoli/tecad/etc. If the

$TECADHOME variable is set, the location for the file is
$TECADHOME/etc.
5. Edit the tecad_snmp.cds file to include the lines in Figure A-1. The
file tecad_snmp.cds is in the same directory as the file
tecad_snmp.conf.
SNMP Interface
A-13
Figure A-1
Editing the tecad_snmp File
#####################################################################
#
Enterprise Controlstation Traps
#
# kag
Apr 25, 1999
#
#
ENTERPRISE 1.3.6.1.4.1.954.1
#
GENERIC TYPE 6
#
SPECIFIC TYPES: 1 - Informational Alarm
#
2 - Minor Alarm
#
3 - Major Alarm
#
####################################################################
CLASS ECSAlert_Info
SELECT
1: ATTR(=,$ENTERPRISE), VALUE(PREFIX, "1.3.6.1.4.1.954.1") ;
2: $TYPE = 6 ;
3: $SPECIFIC = 1 ;
MAP
reason = $V3 ;
END
CLASS ECSAlert_Mnr
SELECT
2: $TYPE = 6 ;
3: $SPECIFIC = 2 ;
MAP
reason = $V3 ;
END
CLASS ECSAlert_Mjr
SELECT
2: $TYPE = 6 ;
3: $SPECIFIC = 3 ;
MAP
reason = $V3 ;
END
A-14
6. Edit the tecad_snmp.baroc file located in the

<Tivoli_Install_Directory>/tec/rb_dir/TEC_CLASSES directory
to include the lines in Figure A-2 on page A-16.
If the Tivoli installation is on a server other than the
CONTROL-M/EM workstation, this file will be located on the Tivoli
Server.
SNMP Interface
A-15
Figure A-2
Editing the tecad_snmp.baroc File
##########################################################
#
# Enterprise Controlstation SNMP TRAPS
# kag Apr 25 99
#
##########################################################
TEC_CLASS :
ECSAlert_Trap ISA Specific_SNMP_Trap
DEFINES {
enterprise: default = "ECSAlert";
};
END
TEC_CLASS :
ECSAlert_Info ISA ECSAlert_Trap
DEFINES {
severity: default = MINOR;
reason: STRING;
};
END
TEC_CLASS :
ECSAlert_Mnr ISA ECSAlert_Trap
DEFINES {
severity: default = WARNING;
reason: STRING;
};
END
TEC_CLASS :
ECSAlert_Mjr ISA ECSAlert_Trap
DEFINES {
severity: default = CRITICAL;
reason: STRING;
};
END
A-16
7. Either cold start or warm start the event adapter and the event
manager.
The easiest method is to warm start the event adapter using this
syntax:
kill -HUP <process_number>
The event manager can be restarted using wstopesrv and wstartesrv.
Customizing CONTROL-M/Links for Distributed Systems

For information about customizing CONTROL-M/Links for
Distributed Systems, see the section on SNMP trap configuration in
the CONTROL-M/Links for Distributed Systems Installation Guide.
SNMP Interface
A-17
A-18
Most of the functions available from CONTROL-M/Enterprise Manager

(CONTROL-M/EM) menus are also accessible via line commands. The
following tables identify the applicable line commands for each menu. A
valid CONTROL-M/EM database log-in name and password are
required for execution.
Additional line commands and utilities are described at the end of this
chapter.
B-1
CONTROL-M/EM Root Menu

Table B-1
Root Menu Options
CONTROL-M/EM
Root Menu
Description
Activation Menu
Displays the CONTROL-M/EM Activation menu. See
Chapter 5, Managing CONTROL-M/EM with the

Root Menu, for more information about the root
menu.
Troubleshooting
Menu
Displays the CONTROL-M/EM Troubleshooting menu.

See Chapter 5, Managing CONTROL-M/EM
with the Root Menu, for more information about the
root menu.
New Window
Opens an Xterm window with CONTROL-M/EM

environment variables. For more information, see
Chapter 5, Managing CONTROL-M/EM with the

Root Menu.
Database Creation
Displays CONTROL-M/EM database creation options.

For more information, see Chapter 5, Managing
CONTROL-M/EM with the Root Menu.

Database
Maintenance
Displays the Database Maintenance menu. For more

information, see Chapter 5, Managing
CONTROL-M/EM with the Root Menu.
B-2
CONTROL-M/EM Activation Menu

Table B-2
Activation Menu and Line Commands (Part 1 of 2)
Activation
Menu
Line
Command
Check All
check_all
Checks and displays the status of all

CONTROL-M/EM core components
(including the database server, Global
Conditions Server, WS-GTW, Orbix
Locator and Naming processes,
Global Alerts Server, GUI server,
License Client, and the maintenance
agents).
Start All
start_ all
Starts the database server, the Orbix

Locator and Naming processes, the
administration agent on the local
computer.
Start Database
Server
start_server
Starts the database server, if it is

located on the local computer.
Start
Orbix Services
start_orbix
_daemon
start_orbix2000
_services
Starts the Orbix Locator and Naming

processes on the local computer. This
menu item appears only if the
CONTROL-M/EM GUI Server is
installed on the same computer.
Start
Administration
Agent
start_admin
_agent
Starts the administration agent that is

Stop All
stop_all
Stops the database server, the Orbix

Locator and Naming processes, the
administration agent on the local
computer.
Description
Note: To run the stop_all line

command , you must supply the
username and password of the
CONTROL-M/EM administrator and
the password of the database server
administrator (DBA).
Stop Database
Server
stop_server
Stops the database server, if it is

B-3
Table B-2
Activation Menu and Line Commands (Part 2 of 2)
Activation
Menu
Line
Command
Stop Orbix
Services
stop_orbix
_daemon
Stop
Administration
Agent
Description
stop_orbix2000_
services
Stops the Orbix Locator and Naming

processes on the local computer. This
option appears only if the
CONTROL-M/EM GUI Server is
installed on the same computer.
stop_admin
_agent
Stops the administration agent that is

B-4
CONTROL-M/EM Database Creation Menu

Table B-3
Database Creation Menu and Line Commands
Database
Creation Menu
Description
Show Database
Parameters
Displays CONTROL-M/EM database parameters.
Build Database
Builds the CONTROL-M/EM database and server.
Delete Database
Deletes the CONTROL-M/EM database.
CONTROL-M/EM Database Maintenance Menu

Table B-4
Database Maintenance Menu and Line Commands
Database
Maintenance
Menu
Description
Export Database
Copies the CONTROL-M/EM database to a flat file.
Import Database
Restores the CONTROL-M/EM database from a file

created by Export Database or another export utility.
Custom
Export/Import
Displays the Import/Export Parameters menu.
Extend Database
Size
Extends the data portion of the CONTROL-M/EM

database.
Erase Alerts
Erases all alerts earlier than a given date/time.
Erase Old Nets
Erases an old network.
Modify Interfaces
File
Modifies the Sybase Interfaces file on the current

computer.
Modify Database
Name
Modifies the CONTROL-M/EM database name.
B-5
CONTROL-M/EM Troubleshooting Menu

Table B-5
Troubleshooting Menu and Line Commands
Troubleshooting
Menu
Description
Database
Troubleshooting
Displays the Database Troubleshooting menu. For more

information, see Database Troubleshooting on
page 7-5.
Gateway
Troubleshooting
Displays the Gateway Troubleshooting menu. For more

information, see Gateway Troubleshooting on
page 7-7.
Show
Environment
Displays details about the CONTROL-M/EM

environment.
Global Conditions
Server Parameters
Displays the Global Conditions Parameters Menu. For

more information, see Global Conditions Server
Database Troubleshooting Menu

Table B-6
Database Troubleshooting Menu
Database
Troubleshooting
Description
Interactive SQL
Commands
Starts an interactive SQL session.
Check Available
Space
Checks available space for Sybase devices.
View Server
Settings
Displays parameters used by the Sybase Adaptive

Server.
Truncate Database
Log
Truncates the CONTROL-M/EM database log file. This

option appears only when the CONTROL-M/EM
database is installed on a Sybase Adaptive Server.
B-6
Gateway Troubleshooting Menu

Table B-7
Gateway Troubleshooting Menu and Line Commands
Gateway
Troubleshooting
Description
Set Debug
Parameters
Displays the Gateway Set Debug Parameters menu and

begins a debug trace when the Set Debug Parameters
menu is closed.
Stop Gateway
Debug
Stops gateway debugging.
B-7
Additional Line Commands

Utilities
The following utilities are provided with the CONTROL-M/EM product.
Detailed descriptions of these utilities are located in the
CONTROL-M/Enterprise Manager Utilities Reference Guide.
A valid CONTROL-M/EM database logon name and password are
required to use these utilities.
Table B-8
CONTROL-M/EM Utilities
cli
Uploads, downloads, orders, and forces Scheduling

tables and jobs.
copydefcal
Copies Calendar definitions.
copydefjob
Copies a specified job processing definition to a

different Scheduling table and datacenter.
defcal
Inserts a Calendar directly into the CONTROL-M/EM

database.
defjob
Inserts a job processing definition directly into a

Scheduling table.
defjobconvert
Converts non-XML DefJob input files into XML-based

input files for use with the Enterprise Controlstation
6.1.00 Beta version of DefJob.
deftable
Imports Scheduling table and Group Scheduling table

definitions from a file.
deldefjob
Deletes a specified job definition.
duplicatedefjob
Creates a copy of a job processing definition in the

same Scheduling table and datacenter while enabling
you to modify selected job parameters.
exportdefcal
Exports Calendar definitions to a text file.
exportdefjob
Exports a job processing definition directly from a

Scheduling table to a text file.
exportdeftable
Exports Scheduling table definitions to a text file.
B-8
Table B-8
CONTROL-M/EM Utilities
serverutil
Imports MCS data into the CONTROL-M/EM database

during an upgrade.
skeletonconvert
Converts job processing definition skeleton files used

with versions of Enterprise Controlstation prior to 6.0.01
to files that are compatible with CONTROL-M/EM 6.1.00
Beta.
updatedef
Modifies existing job processing definitions, Scheduling

tables, and Group Scheduling tables.
util
Multi-purpose utility that performs various database

management functions:
B-9
B-10
System Parameters
The system parameters described in this appendix influence the behavior

of a wide range of CONTROL-M/Enterprise Manager
(CONTROL-M/EM) components and features. The function of each
parameter is described and its default, if any, is listed.
As the CONTROL-M/EM administrator, you can change the value of
certain parameters. However, some parameters must be modified only
with the instruction of BMC Softwares Technical Support staff. These
parameters are duly noted.
System parameters are modified using the System Parameters window
of the Administration facility. To learn how to modify a parameter, see
Displaying and Modifying System Parameters on page 4-33.
System parameters are grouped according to the component or process
that they most directly affect. They are displayed in the System
Parameters window by group, and the tables in this appendix are
organized in the same way.
General parameters are described in Table C-1, General

Parameters, on page C-2.
Gateway parameters are described in Table C-2, Gateway

Enterprise License Manager and License Client parameters are

described in Table C-3, Enterprise License Manager and Client
System Parameters
C-1
Global Alerts Server parameters are described in Table C-4, Global

Alerts Server Parameters, on page C-9.
Parameters related to the Administration facility and to the

administration agent are described in Table C-5, Maintenance
GUI Server parameters are described in Table C-6, GUI Server

System parameters are described in Table C-7, System Parameters,

on page C-14.
Global Conditions Server parameters are described in Table C-8,

Global Conditions Server Parameters, on page C-14.
Table C-1
General Parameters (Part 1 of 2)
Parameter
Description
HandleAlertsOnRerun
CONTROL-M/EM automatically generates an Alert

for each Restart or Rerun job. Valid values: 1 (yes),
0 (no).
Default: 0
HostPort
Hostname and port number for a specified

component. Values are specified using the
Update/View Parameter window, described on
page 4-37. There can be multiple values for this
parameter, each related to a different component or
a different host computer.
The format for the parameter value is:
<host name>:<port number>. For example:
CTMhost1:1530
For more information about the Update/View
Parameter window, see Displaying and Modifying
System Parameters on page 4-33.
Default: null
NrHandledAlarms
Maximum number of Handled alerts displayed in

the Alerts window. When NrHandledAlarms is set
to 0, no Handled alerts are deleted.
Default: 0
C-2
Table C-1
General Parameters (Part 2 of 2)
Parameter
Description
SendAlarmToScript
Full path name of the script that is activated when

an alert is generated. This script is activated only if
the value of SendSnmp is either 1 or 2
Default: script_name
SendSnmp
Indicates where Alert data is to be sent.

SNMP only (0)
User defined script only (1)
SNMP and user defined script (2).
Default: 0
SnmpHost
Hostname for SNMP alerts.

Default: no_host
SnmpSendActive
Generates SNMP messages for Active Alerts (1) or

doesnt generate SNMP messages for Active Alerts
(0).
Default: 0
SnmpSendDemo
Generates SNMP messages for Demo Alerts (1) or

does not generate SNMP messages for Demo
Alerts (0).
Default: 0
SnmpSendFormat
Determines the SNMP message format.

0 - Single Variable format
1 - Multiple Variable format
2 - Both formats
Default: 2
System Parameters
C-3
Table C-2
Gateway Parameters (Part 1 of 3)
Parameter
Description
AlertOnAbend
Flag indicates whether to (1) send alerts for jobs

that end NOTOK. Alerts are not sent when the
value is 0.
Default: 1
DeltaMaxActMinutes
Age, in minutes, for a net to be considered valid for

distribution of Global Conditions.
Default: 2160
DownCreAlerts
Flag that indicates whether to send alerts for

downloaded jobs that ended NOTOK when they
are run.
0 - Alerts are not sent.
1 - Alerts are sent.
The AlertOnAbend parameter must be set to 1 for
DownCreAlert to be operational.
Default: 1
GtwCondDispatchErr
For Technical Support use only.

Default: CTM5050 CTM5301 CTM5311 CTM5312
CTM5323
GtwLogDestFileType
Log file destination type.

Valid values:
0=Sequetial
1=Cyclic
Default: 1
GtwLoggerOn
Toggles the Logger facility on or off.

0=Logger off
1=Logger on
Default: 1
GtwLogMsgFile
Name of the log file.

Default: ECSMessages.txt
GtwLogNofFiles
Number of log files in use.

Default: 5
GtwLogNofMsgs
Number of messages in a log file.

Default: 1000
C-4
Table C-2
Parameter
Description
GtwLogQSize
Number of messages in the Messages queue.

Default: 300
GtwLogRefreshInter
Refresh interval, in seconds, for the Logger

component to read its database tables.
Default: 500
GtwLogThrowMsgs
Flag indicates whether to delete log messages

when the log file queue is full.
0=not deleted
1=delete
Default: 1
HostPortList
List of CONTROL-M/EM GUIs that are connected

to the gateway. List format:
datacenter1=<host>:<port>;datacenter2=
<host>:<port>
Default: null
InsertAlertTries
Number of times that the gateway attempts to insert

an alert into CONTROL-M/EM. The number
includes the initial attempt and can be any whole
number equal to or greater than 1.
Default: 1
MaxDownHistDays
Number of days that the list of downloads is saved.

This list contains abbreviated information about
each download, such as the date and time, net
name, and number of jobs and resources in the
download.
Default: 100
MaxOldDay
Downloads are kept in the CONTROL-M/EM

database for not more than the number of days
specified in this parameter.
Note: The number of downloads stored in the
database is never more than the smaller of the
MaxOldDay value and the MaxOldTotal value.
Default: 1
System Parameters
C-5
Table C-2
Parameter
Description
MaxOldTotal
Total number of downloads that can be stored in

the CONTROL-M/EM database.
If this number is exceeded, the oldest download is
deleted.
Default: 1
MaxUploadBufferMPM

Default: 18000
MaxUploadBufferMVS

Default: 18000
SSLPassword
Password for the Key database file that holds SSL

encryption keys.
Default: password
SSLRetries
The number of times that CONTROL-M/EM

attempts to establish communication with the
gateway before turning SSL on or off. SSL can
either be enabled or disabled when
CONTROL-M/EM initially tries to connect to the
gateway. After making the specified number of
attempts, SSL is toggled on (if it was off) or off (if it
was on) during the previous series of attempts.
This parameter is relevant only when SSL or SSL
Enabled communication is selected. It does not
work when only TCP/IP is selected.
Default: 2
SSLSyncTime
Replaces the value of the Sync_Timeout parameter

(in the Defaults.rsc file) that determines the period
of time between attempts to establish
communication with the gateway when changing
communication protocols to SSL or SSL Enabled.
Default: 90
C-6
Table C-3
Enterprise License Manager and Client Parameters (Part 1 of 2)
Parameter
Description
LMGUIServerCTLTimeSev

Default: 1
LMGUIServerUpdTimeout

Default: 1800
LMGUI_Communication
_Cfg
Encrypted host name and port number that

CONTROL-M uses to contact the Enterprise
License Manager server. This encrypted
information is passed to the CONTROL-M
installations that are connected to the
Enterprise License Manager.
Default: null
LMGUI_LastReportTime
Clock time that the License Client last reported

to the Enterprise License Manager.
Default: null
LMGUI_LicenseHost
Host name of the Enterprise License Manager

computer.
Default: AAAAAAA
LMGUI_LicensePort
Port number of the Enterprise License

Manager computer.
Default: 1613
LMGUI_MaxGui
Total number of CONTROL-M/EM GUIs

connected to the CONTROL-M/EM GUI
servers on the network. This parameter
receives its value from the License Client. This
value is recalculated each time the License
Client reports.
Default: 0
LMGUI_PollingInterval
Frequency, in minutes, at which the License

Client determines the number of
CONTROL-M/EM GUIs on the network. The
result provides a value for the LMGUI_MaxGui
parameter.
Default: 5
System Parameters
C-7
Table C-3
Enterprise License Manager and Client Parameters (Part 2 of 2)
Parameter
Description
LMGUI_ReportInterval
Frequency, in minutes, at which the License

Client reports the value of the LMGUI_MaxGui
parameter to the Enterprise License Manager.
Default: 1440
LMGUI_Severity_1_List

Default: 2,3,6

Default: 4,5

Default: 1,7,8,9
C-8
Table C-4
Global Alerts Server Parameters
Parameter
Description
AlertsMapRefreshInterval
Frequency, in seconds, at which the GAS

updates its database about which Alerts were
deleted and why. The update occurs only when
both the specified time has passed and one or
more alerts have been deleted.
Default: 60
LogTablesRefreshInterval
Log facility refresh rate, in minutes. Changing

this parameter refreshes the Logger at the
specified interval while the GAS is operating.
Default: 120
NumberOfLogFileMessage
Number of Alert messages that are stored in

each log file. When the last log file is full,
entries in the first log file are overwritten by
new messages. Successive log files are
overwritten, as necessary.
Default: 500
NumberOfLogFiles
Number of log files that are maintained by the

GAS.
Default: 3
System Parameters
C-9
Table C-5
Maintenance Parameters (Part 1 of 3)
Parameter
Description
ActivateRetries
Number of times that the Administration agent

tries to start an inactive component. Minimum
setting: 3.
Note: After the specified number of retries are
attempted without success, you must use the
Administration facility to reset the unresponsive
component. Change the unresponsive
components desired state to a setting other
than Up, then change it to Up, and then
resume your attempts to activate the
component.
Default: 10
ComponentRestartInterval
The frequency, in minutes, at which the

administration agent makes an attempt to start
an CONTROL-M/EM component that is not
responding. The valid range of time is from 3 to
10 minutes.
This parameter can be modified from the
Administration Facility Options dialog box. For
directions, see Starting and Stopping
Components on page 4-13.
Default: 3
ComponentShowState
Many CONTROL-M/EM components, including

the GUI server, the gateway, and the Global
Conditions Server, operate hidden from the
users view. These components can be
displayed in command prompt windows by
setting this parameter to 1, stopping the
Administration agent, and restarting the agent.
Default: 0
LifeCheckRespTimeout
Time, in seconds, that the Administration agent

waits for a component to respond to a life
check. Minimum: 15
Default: 30
C-10
Table C-5
Parameter
Description
LifeCheckRetries
Number of life checks the Administration agent

performs before the component is considered
to be malfunctioning. Minimum: 1
Default: 5
LifeCheckRetryTime
Interval, in seconds, before a prior life check is

performed after a life check to which there was
no response.
Default: 15
LogCleanInterval
Interval, in minutes, between the LogReg log

cleaning operations performed by the
administration agent.
Note: The administration agent cleans the
LogReg log every time that it is activated.
Default: 360
LogCleanLevel
Indicates the amount of detail the clean

operation erases from the LogReg log.
0=no deletion
1=cleans only the agents own log messages
2=cleans all log messages
Default: 1
LogHistoryDays
Number of days that log entries are retained

before they can be cleaned from the log.
Minimum: 0
Default: 1
LogInfoLevel
Level of detail in LogReg log entries recorded

by the Administration agent.
0=no entry
1=administration agent-related messages
2=brief component and agent related
messages
3=detailed component and agent related
messages
Default: 2
System Parameters
C-11
Table C-5
Parameter
Description
StdoutLogInfoLevel
Level of detail of standard output messages

reported by the administration agent.
0=no entry
1=administration agent-related messages
2=brief component and agent related
messages
3=detailed component and agent related
messages
Default: 2
StopGracePeriodSec
Time, in seconds, that a component is given to

shut down following a Stop command. When
this time is exceeded, the administration agent
again tries to stop the component. If the
number of retries specified by the StopTries
parameter is exceeded, the agent kills the
component.
Default: 45
StopTries
Number of times that the agent tries to stop the

component using the Stop command before
performing a kill operation to stop it. Minimum:
1
Default: 2
C-12
Table C-6
GUI Server Parameters
Parameter
Description
MaxUserTimeoutSec
Time, in seconds, that a CONTROL-M/EM API

client user token is valid. After this time, the
GUI Server can invalidate the token.
Default: 10800
NumberOfLogFileMessage
Maximum number of messages stored in each

log file. When the last log file is full, entries in
the first log file are overwritten by new
messages. Successive log files are
overwritten, as necessary.
Default: 500
NumberOfLogFiles
Number of log files that are maintained for

each component by the Logger.
Default: 3
LogTablesRefreshInterval
Frequency, in seconds, at which the GUI

Server retrieves component context updates
from the CONTROL-M/EM database.
Component contexts are used by
CONTROL-M/EM to determine whether a
component event is inserted in the log file and
how it would be presented.
Default: 120
NumberOfMyWorldJobs
Total number of job nodes that are displayed

when Local View is used. Valid range:
2-30,000. For more information about Local
View, see the Alerts chapter in the
Default: 100
System Parameters
C-13
Table C-7
System Parameters
Parameter
Description
SysInit1

Default: 283862c273524c18
Table C-8
Parameter
Description
GcsLogDestFileType
Log file destination type.

0=Sequetial
1=Cyclic
Default: 1
GcsLoggerOn
Activates the Logger facility.

0=Logger off
1=Logger on
Default: 1
GcsLogMsgFile
Name of the log file.

Default: ECSMessages.txt
GcsLogNofFiles
Number of log files in use.

Default: 5
GcsLogNofMsgs
Number of messages in a log file.

Default: 1000
GcsLogQSize
Number of messages in the Messages queue.

Default: 300
GcsLogRefreshInter
Refresh interval, in seconds, for the Logger

component to read its database tables.
Default: 500
GcsLogThrowMsgs
Flag that indicates whether to delete log

messages when the log file queue is full.
0=no deletion
1=delete
Default: 1
C-14
Index
Index
Symbols
!IXGEN_DONT_EDIT_THIS! xvi, xvii,
xviii, xix
*default 7-23
.ini files. See initialization files
A
ACF2 6-3
act_view_only_option 8-7
act_view_only_option parameter
Defaults.rsc file 8-7
action statements. See Do statements
ActivateRetries C-10
activation menu
administration agent 5-3
check all option 5-4
description 5-3
menu options B-3
options 5-4
starting options 5-4
starting the administration agent 5-3
stopping options 5-5
stopping the administration agent 5-3
Active environment
downloading 7-9
Active Jobs file

time zones 1-11
adding
time zones 1-14
administration agent
agents log 4-27
communicating with 4-3
description 4-2
logging 4-27
modifying restart intervals 4-15
starting 4-2
starting and stopping 5-3
administration agents
DIAG component prefix 7-22
Administration facility 4-1
administered components 4-6
agent log 4-27
agent polling interval 4-26
build from network 4-15
communicating with the agent 4-3
Component dialog box 4-19, 4-21
component icons 4-13
component registration 4-15, 4-21
component restart interval 4-15
component states 4-11
creating a filter 4-22
current state 4-3
database administration 4-43
Index
database polling interval 4-26

deleting a registered component 4-16
description 4-1
desired state 4-3
display filter criteria 4-25
filter definition wildcards 4-25
filter manager 4-21
Filter Properties 4-23, 4-25
filtering components 4-21
functions 4-1
gateway administration 4-6
Global Alerts Server 4-6
Global Conditions Server 4-6
GUI 4-5, 4-12
icons 4-12
ignored state 4-14
logging on to CONTROL-M/EM
database 4-3
logon requirements 4-4
modifying a filter 4-24
modifying defaults settings 4-26
modifying polling intervals 4-26
modifying the display 4-7
options dialog box 4-15, 4-26
registering components 4-15, 4-21
responsibility 1-8
selecting a filter 4-23
selecting components 4-21
starting 4-4
table view 4-10
tree view 4-7
window 4-5, 4-10
administrator responsibilities
customization 8-1
agents log
clearing 4-28
deleting 4-28
displaying 4-27
filtering 4-31
messages 4-28
truncating 4-31
window contents 4-27
AIX
starting programs automatically 3-7
stopping programs automatically 3-7
ALERT ID
SNMP trap A-3
alert processing
audio support 8-4
description 8-3
gateway check errors 7-11
removing from database 4-43
SendAlarmToScript 8-3
SendSnmp 8-3
SNMP interface A-1
SNMP trap or script 8-3
AlertOnAbend C-4
alerts
See also messages
Alerts window
AlertsMapRefreshInterval C-9
Application
SNMP trap A-4
assign_ports 3-14
authorization
See also License Manager
authorization. See security
B
batch utilities
listed B-8
build database menu
Sybase Server 5-11, 5-21
C
calendars
security 6-31
CALL TYPE
SNMP trap A-3
Central European Time 1-12
Central Standard Time 1-12
CET time zone 1-12
check_gtw utility
description 7-11
cleanup. See maintenance
cli utility
description B-8
clock
time zone support 1-11
closing. See exiting
collapsing. See stepping out
communication
between gateway and GCS 7-16
defining CONTROL-M installations 2-1
gateway log 3-12
IP addresses 8-4
message level (GCS) 7-16
multiple gateway IP addresses 8-7
OS/390 performance data 3-13
reading the communication table 7-16
security 6-24
trace messages 7-11
tracing 7-11
truncate messages 7-10
communication tracing 7-11
description 7-11
starting 7-12
stopping 7-12
component state
administration facility polling interval
4-26
agent polling interval 4-26
current state 4-3, 4-11
default polling interval 4-26
description 4-11
desired state 4-3, 4-11
down 4-11
hanging 4-11
ignored 4-11, 4-14
up 4-11
warning 4-11
ComponentRestartInterval C-10
ComponentShowState C-10
conditions
See also prerequisite conditions
configuring
hostname 3-19
port number 3-19
continue_with_dup parameter 8-6
CONTROL-M
administering 2-1
CONTROL-M/EM 1-2, 1-5
defining 2-1
deleting definitions 2-6
disabling definitions 2-5
enabling definitions 2-5
performance analysis 7-13
TCP/IP host name 2-3
TCP/IP port number 2-4
troubleshooting 7-13
version 2-3
CONTROL-M/Agent 1-10
CONTROL-M/Desktop 1-5
starting 3-3
CONTROL-M/EM
components 1-3
connectivity 1-3
CONTROL-M/Desktop 1-5
CONTROL-M/EM Server 1-3
graphical user interface (GUI) 1-3
platforms xiii
related products 1-10
starting components 3-4
Index
stopping components 3-4

workstation gateways 1-4
CONTROL-M/EM administrator
changing the password 3-12
responsibilities 1-8, 6-2
CONTROL-M/EM components
administration facility 4-15
automatic start 3-4
manual start 3-4
manual stop 3-4
starting 3-4, 4-13
states of operation 4-11
stopping 4-13
CONTROL-M/EM database
administering 4-43
administration facility logging 4-3
administration facility polling interval
4-26
alerts 4-43
checking available space 4-44, 4-47
contents 1-7
data segment 4-44
database troubleshooting 7-3
description 1-4, 1-7
duplicate index entries facility 8-6
extending 4-44
isql queries 4-47
log segment extension 4-44
maintenance with the GUI 4-43
removing alerts 4-43
show environment 7-3
CONTROL-M/EM GUI
description 1-3
starting 3-2
CONTROL-M/EM GUI Server. See GUI
Server
CONTROL-M/EM processes
stopping with EnablePriv 3-5
CONTROL-M/EM Server
starting/stopping 3-2
CONTROL-M/EM server
description 1-3
starting 3-2
CONTROL-M/Enterprise Manager. See
CONTROL-M/EM
CONTROL-M/Links
SNMP customization A-17
CONTROL-O/Server
SNMP traps A-6
CONTROL-R
in a CONTROL-M definition 2-3
with CONTROL-M/EM 1-2
copydefcal utility B-8
copydefjob utility B-8
creating
See also defining
ENTERPRISE/CS database 5-7
CST time zone 1-12
ctl
CTMAS 7-13
custom import/export
database maintenance menu 5-32
options 5-33
customizing
security 8-1
system defaults 8-2
D
data centers
defining 8-2
administrator responsibilities 5-1
checking available space 4-47
extending 4-44
performing queries with isql 4-47
database creation menu
build database option 5-7, 5-20

delete database option 5-7, 5-20
description 5-6
menu options B-5
Oracle Server 5-19
database maintenance
administrator responsibilities 1-9
checking available space 4-47, 7-6
extending 4-44
isql queries 4-47
removing alerts 4-43
truncating database log 7-6
custom export/import 5-28
database server parameters 5-10
description 5-27
export database option 5-27
extend database option 5-28
import database option 5-27
menu options B-5
modify database name 5-28
modify Interfaces file 5-28
Oracle Server parameters 5-19
database server
automating starting 3-6
automating stopping 3-6
debug mode 7-9
disabling commands 5-19
disabling start, stop, and delete
commands 5-10
modifying hostname 3-19
modifying port number 3-19
requirements 1-4
SQL commands 7-6
starting 3-1
stopping 3-1, 5-3
viewing server settings 7-6
database troubleshooting
menu options 7-5, B-6
DATACENTER
SNMP trap A-3
datacenter
datacenter definition. See CONTROL-M
definition
db threshhold % parameter 5-36
db_block_buffers parameter
Oracle Server 8-9
db_block_size parameter
Oracle Server 8-9
db_check utility
db threshhold % parameter 5-36
log threshold % parameter 5-36
db_sys_params utility A-5
debugging
See also troubleshooting xiii
Apply to Gateway 7-10
Clear Flags from Screen 7-10
CONTROL-M/EM GUI 7-9
database server 7-9
gateway 7-7
gateway debug mode description 7-8
Keep Alive messages 7-10
messages 7-10
Set Active JCL 7-10
stopping gateway debug mode 7-9
Defaults.rsc file
act_view_only_option parameter 8-7
comm_userid parameter 8-6
continue_with_dup parameter 8-6
description 8-4
limit_gcs_distrib parameter 8-4
use_all_ip_address parameter 8-7
defcal utility B-8
defining
See also creating
CONTROL-M installations 2-1
jobs for time zones 1-12
Index
time zones 1-14

defjob utility B-8
defjobconvert utility B-8
deftable utility B-8
deldefjob utility B-8
Delete Time for Sent Conditions
Global Conditions Server parameter
7-17
Delete Time for Unsent Conditions
7-17
Delete Time for Unused Conditions
7-17
DeltaMaxActMinutes C-4
dependencies
See also In conditions
See also job dependencies
See also Out conditions
Desktop. See CONTROL-M/Desktop
Destination Status Interval
7-17
DIAG diagnostics facility
commands 7-24
component ini file 7-21, 7-22
customer support 7-19
debugging 7-19
default ini file 7-21, 7-22
description 7-19
DIAGL command 7-24
DIAGOFF command 7-24
DIAGON command 7-24
ini file naming conventions 7-22
initialization file contents 7-21
line commands 7-24
log files 7-20
logging 7-19
running 7-19
using with GUI server 7-23
DIAGL command 7-24

Diagnostic Message Level
7-16
DIAGOFF command 7-24
DIAGON command 7-24
displaying
See also viewing
DownCreAlerts parameter C-4
dsedit
modifying Interfaces file 5-35
opening 5-35
duplicate index entries facility 8-6
duplicate out conditions
customizing 8-7
E
Eastern European Time 1-12
Eastern Standard Time 1-12
ECSGATE 1-10
EET time zone 1-12
EnablePriv utility 3-5
ENTERPRISE/CS
custom export 5-28
custom import 5-28
Unix platform 5-1
ENTERPRISE/CS administrator
ENTERPRISE/CS components
using with firewall 3-14
ENTERPRISE/CS database
corruption 5-7
creating 5-7
database file 5-18
erase alerts option 5-28
exporting 5-30
extending 5-28
importing 5-28, 5-29, 5-30
restoring 5-7
Sybase 5-8, 5-17

Sybase environment 5-8
Sybase transaction log files 5-18
SYSTEM tablespace file 5-18
erasing alerts
error messages. See alerts
EST time zone 1-12
expanding. See stepping in
exportdefcal utility B-8
exportdefjob utility B-8
exportdeftable utility B-8
exporting
F
File Name parameter
See also memname
filters
wildcards 4-25
firewall
assign_ports script 3-14
configuring for use 3-14
focusing. See zooming
Full Security parameter 6-3
G
GAS. See Global Alerts Server
gateway communication
log 3-12
multiple IP addresses 8-7
OS/390 performance data 3-13
trace messages 7-11
Gateway Connectivity Interval
7-16
gateway log
core file 7-13

description 7-12
filename format 7-13
gateway troubleshooting
description 7-7
menu options B-7
set debug parameters 7-7
stop gateway debug mode 7-7
Gateway Verification utility. See check_gtw
utility
gateways
administration 4-6
checking (check_gtw) 7-11
connectivity with GCS 7-16
core file for logging errors 7-13
debug mode description 7-8
debugging 7-7
gateway log 7-12
securing 6-3
starting 3-2
stopping 7-9
stopping debug mode 7-9
troubleshooting 7-3, 7-7
GCS. See Global Conditions server
GCSERV user
changing 8-6
Global conditions security 6-3
Global Alerts server
administration 4-6
description 1-4
starting 3-3
starting/stopping 3-3
Global conditions
automating cleanup 3-11
cleaning up 3-11
cleanup benefits 3-11
deleting 3-11, 7-17
distribution 8-4
Index
distribution parameters 7-16, 7-17

groups 7-17
handling conflicts 7-17
modifying 8-4
security 6-3
Global Conditions server
configuring 7-15
description 1-4
hostname 3-19
parameters 7-4, 7-16
Parameters menu 7-15, 7-16
port number 3-19
starting 3-2
troubleshooting 7-15
GMT time zone 1-12
Greenwich Mean Time 1-12
GROUP
SNMP trap A-4
Group Authorizations
description 6-10
General panel 6-17
Jobs panel 6-19
Privileges panel 6-22
Resources and Calendars panel 6-28
Scheduling Tables panel 6-25
groups
See also node ID
GtwCondDispatchErr C-4
GtwLogDestFileType C-4
GtwLoggerOn C-4
GtwLogMsgFile C-4
GtwLogNofFiles C-4
GtwLogNofMsgs C-4
GtwLogQSize C-5
GtwLogRefreshInter C-5
GtwLogThrowMsgs C-5
GUI server
administration 4-6
DIAG usage 7-23
H
Handling Conflicting Conditions
7-17
HAW time zone 1-11
Hawaii time zone 1-11
HKG time zone 1-12
Hong Kong time zone 1-12
host debugging 7-10
hostname
changing 3-19
changing in Defaults.rsc 3-19
changing in the Sybase Interfaces file
3-19
HostPort C-2
HostPortList
description C-5
modifying 3-20
hours
HP-UX
starting programs automatically 3-9
stopping programs automatically 3-9
I
ID.Seeuser ID
importing
In conditions
See also prerequisite conditions
index entries
modifying 8-4
initialization files
DIAG 7-20
DIAG file syntax rules 7-22
DIAG ini file 7-21
syntax rules for DIAG ini files 7-22
InsertAlertTries C-5
installation
types 1-5
Interfaces file
changing hostname 3-19
modifying 3-19, 5-14
modifying with dsedit 5-35
parameters menu 5-14
IOAGATE
performance analysis 7-13
IP addresses
modifying 8-4
multiple IP addresses description 8-7
IsCyclic 7-23
isql
starting a session 4-47
J
JOB NAME
SNMP trap A-4
job parametersSee also specific parameter
name
joining. See concatenation
L
LAST TIME
SNMP trap A-4
LAST USER
SNMP trap A-4
library
See also doclib
Licence Manager. See Enterprise License
Manager
license client

License Manager
hostname and port number 3-19
LifeCheckRespTimeout C-10
LifeCheckRetries C-11
LifeCheckRetryTime C-11
limit_gcs_distrib parameters
global conditions distribution 8-4
limit_gcs_distrib_activate
limit_gcs_distrib_disable_dates
limit_gcs_distrib_max_days
LMGUI_Communication_Cfg C-7
LMGUI_LastReportTime C-7
LMGUI_LicenseHost C-7
LMGUI_LicensePort C-7
LMGUI_MaxGui C-7
LMGUI_PollingInterval C-7
LMGUI_ReportInterval C-8
LMGUI_Severity_n_List C-8
LMGUIServerCTLTimeSev C-7
LMGUIServerUpdTimeout C-7
loader
location. See moving
log threshold % parameter 5-36
log_buffer parameter
Oracle Server 8-9
log_checkpoint_interval parameter
Oracle Server 8-9
log_checkpoint_timeout parameter
Oracle Server 8-9
LogCleanInterval C-11
LogCleanLevel C-11
LogHistoryDays C-11
LogInfoLevel
description C-11
Index
modifying 4-29
logon
security 6-2
logs
See also messages xiii
cyclical files 7-19
DIAG messages 7-19
gcs_log.### log file 7-16
monitoring with db_check 5-36
single-file 7-19
transaction log 5-36
logs. See output
LogTablesRefreshInterval C-9, C-13
low-level node. See job node
M
maintenance
See also Administration facility
See also database maintenance
global conditions 3-11
prerequisite conditions 3-11
maintenance agent. See administration agent
MaxDownHistDays C-5
Maximum Conditions in a Group
7-17
Maximum Send Condition Retries
7-16
MaxOldDay C-5
MaxOldTotal C-6
MaxUploadBufferMPM C-6
MaxUploadBufferMVS C-6
MaxUserTimeoutSec C-13
MEL time zone 1-12
Melbourne time zone 1-12
MEMNAME
SNMP trap A-3
messages
See also alerts

See also logging xiii
See also shout messages
modifying
See also changing
See also creating
See also editing
See also updating
Global Conditions distribution 8-4
index entries 8-4
IP addresses 8-4
network view security 8-4
time zones 1-14
Mountain Standard Time 1-12
MSG TEXT
SNMP trap A-4
MST time zone 1-12
MVS. See OS/390
mySAP. See SAP
N
naming conventions
DIAG ini file 7-22
DIAG log files 7-20
NetView for AIX
SNMP traps A-10
Network Management applications
HP-OpenView A-7
interfacing with CONTROL-M/EM A-1
NetView for AIX A-10
Tivoli Management Environment
Console A-13
Network View Authorization window
Read Only mode 8-7
New Day procedure
Node ID
SNMP trap A-4
nodes
10
See also job nodes

NrHandledAlarms C-2
NumberOfLogFileMessage C-9, C-13
NumberOfLogFiles C-9, C-13
NumberOfMyWorldJobs C-13
NumOfFiles 7-23
NumOfMessages 7-23
O
odate
open objects parameter
Sybase Server 5-10
Option parameter. See Sysout Handling
or. See and/or
Oracle Applications
application support 1-10
Oracle Server
configuration 8-9
data tablespace description 5-18
database creation menu 5-19
database environment 5-17
database parameters menu 5-24
dataserver process 5-17
file 5-18
index tablespace description 5-18
initdatabasename.ora file 8-9
modifying configuration parameters
5-19
modifying parameters 5-24
raw device 5-18
redo log file description 5-18
sharing 5-18
SYSTEM tablespace description 5-17
tsnames.ora file 3-19
user connections parameter 5-19
Orbix Server
description 7-18
hostname modification 7-18
parameter modification 7-18
parameters 7-4
port number modification 7-18
starting 3-3
stopping 3-3
Order ID
SNMP trap A-3
output. See alsoSYSDATA
output. See alsosysout
overview. See Net Overview
OWNER
SNMP trap A-4
P
Pacific Standard Time 1-11
parameters
See also job definition parameters xiii
parameters. See alsosystem parameters xiii
Parm parameter. See Sysout Handling
passwords
changing 3-12
Path parameter
See also memlib
port numbers
changing 3-19
prerequisite conditions
cleanup 3-11
deleting 3-11
security 6-3, 6-28
printing
capturing configuration parameters 4-47
PST time zone 1-11
R
R/3. See SAP
Index
11
RACF 6-3
raw device
Oracle Server 5-18
Sybase Server 5-9
reading
See also copying
See also downloading
See also uploading
Refresh Communication Interval Table
7-16
removing. See deleting
resolution. See zooming
resources
See also Control resources
See also quantitative resources
security 6-28
Restore Default Parameters
7-17
root menu
activation option 5-2
database creation option 5-3
database maintenance option 5-3
description 5-1
ENTERPRISE/CS administration 5-1
menu options B-2
new window option 5-2
starting 5-2
troubleshooting menu 5-2, 7-2
Run Global Conditions Server
7-17
S
SAP
application support 1-10
scheduling
Scheduling tables
See also Group Scheduling tables
authorization to access 6-25
security 6-26
script 3-14
security
authorization definitions 6-24
authorization facility 6-4
calendars 6-31
changing password 3-12
collections 6-23
communication 6-24
CONTROL-M 6-3
CONTROL-M/EM 6-1
CONTROL-M/EM customization 8-1
CONTROL-M/EM data protection 6-2
CONTROL-M/EM log on protection
6-2
CONTROL-M/EM user operations 6-3
data center 6-3
database server customization 8-1
define authorizations selection window
6-21
description 6-24
enabling job actions 6-20
file protection 6-2
filters 6-23
firewall configuration 3-14
gateway 6-3
hierarchies 6-23
Integral Workstation Security 6-1
job access 6-20
logon 6-2
network view authorizations 8-4
operating system 6-1
passwords 3-12
privileges panel 6-22
resources 6-28
security mechanisms 6-1
12
Unix 6-2
user authorizations 6-3
ViewPoints 6-23
Windows-based 6-2
workstation level 6-1
Send Condition Group Interval
7-17
Send Condition Interval
7-16
SEND TIME
SNMP trap A-3
SendAlarmToScript 8-3, C-3
SendSnmp 8-3, A-5, C-3
Set Debug Parameters menu
description 7-8
gateway debugging 7-9
options 7-9
setting. See customizing
Setvar. See AutoEdit Assignment
SEVERITY
SNMP trap A-3
shared_pool_size parameter
Oracle Server 8-9
Shout parameter
See also Do Mail parameter
See also Do Shout parameter
size
See also zooming
size of rollback segments parameter
Oracle Server 5-19
size of tempdb parameter
Sybase Server 5-10
size of temporary tablespace parameter
Oracle Server 5-19
skeletonconvert B-9
SNMP
See also SNMP compatibility xiii
alerts A-1
CONTROL-M/EM parameters A-5
description A-2
interfacing with CONTROL-M/EM A-1
network manager A-1
product compatibility A-1
trap format A-3
trap message A-2
traps A-3
variable format A-4
SNMP customization
CONTROL-M/EM A-5
CONTROL-M/Links A-17
CONTROL-O/Server A-6
HP-OpenView A-7
NetView for AIX A-10
parameters A-5
Tivoli A-13
SNMP server
SnmpHost
description A-5, C-3
Snmphost
modifying 3-20
SnmpSendActive A-5, C-3
SnmpSendDemo C-3
SnmpSendFormat A-5, C-3
Solaris
automatic program start 3-10
automatic program stop 3-10
sort_are_size parameter
Oracle Server 8-9
sorting. See filtering
sp_configure
modifying Oracle Server parameters
5-19
setting database server parameters 5-10
SQL server configuration
Oracle 8-9
Index
13
Sybase 8-8
sql.ini
modifying 3-19
SSLPassword C-6
SSLRetries C-6
SSLSyncTime C-6
starting
administration agent 3-6, 5-3
automatically 3-6
CONTROL-M/EM components 3-4,
4-13
CONTROL-M/EM server 3-2
CTMAS 7-13
database debug mode 7-9
database server 3-1, 3-6
DIAG diagnostics 7-20
DIAG for GUI server 7-24
GUI debugging 7-9
host debugging 7-10
Orbix Server 3-6
root menu 5-2
troubleshooting menu 7-2
STATUS
SNMP trap A-3
StdoutLogInfoLevel C-12
stepping in and out
See also collapsing
See also expanding
StopGracePeriodSec C-12
stopping
administration agent 3-6, 5-3
automatically 3-6
CONTROL-M/EM components 3-4,
4-13
CONTROL-M/EM Server 3-2
CTMAS 7-13
database server 3-1, 3-6, 5-3

DIAG for GUI server 7-20, 7-24
EnablePriv utility 3-5
gateway 7-9
gateway debug mode 7-9
maintenance agent 3-5
Orbix Server 3-6
StopTries C-12
agent log 4-29
Sybase Server
configuration parameters 8-8
creating on Unix 5-8, 5-17
data file description 5-8
database corruption 5-8, 5-17
database creation menu 5-11, 5-21
database devices 5-9
dataserver process 5-8
default file names 5-9
Interfaces file 5-10
log file description 5-9
master database file 5-8
master.dat 5-9
open objects parameter 5-10
printer configuration 4-47
raw device 5-9
raw file 5-9
sharing 5-9
size of tempdb parameter 5-10
sql.ini file 5-10
Sybase system procedures file 5-8
systemprocs.dat 5-9
user connections parameter 5-10
SYBASE.cfg file 8-8
syntax
rules for DIAG ini files 7-22
SysInit1 C-14
sysout
14
mainframe statistics output 7-14

system parameters
conditional values 4-36
gateway C-1
general C-1
Global Alerts Server C-2
Global Conditions Server 7-4, C-2
GUI server C-2
License Manager C-1
maintenance C-2
modifying 4-35
modifying conditional settings 4-40
modifying values conditionally 4-36
modifying values unconditionally 4-35
multiple conditions 4-36
purpose C-1
System Parameters window 4-33
Update/View Parameter window 4-37
system parameters. See alsoparameters xiii
system parameters window
contents 4-34
description 4-34
T
tables
See also Group Scheduling tables
See also Prerequisite Condition tables
See also Resource tables
See also Scheduling tables
task manager
Enable Priv utility 3-5
TCP/IP
CONTROL-M host name 2-3
CONTROL-M port number 2-4
WS-GTW host name 2-4
WS-GTW port number 2-4
templates. See skeletons
time
time zone
CONTROL-M support 1-11
time zones
default values 1-11
TimeZone.dat file
modifying 1-14
Tivoli Management Environment Console
SNMP traps A-13
tnsnames.ora
modifying 3-19
TOK time zone 1-12
Tokyo time zone 1-12
troubleshooting
See also debugging xiii
CONTROL-M communication 7-13
gateway log 7-12
Troubleshooting menu
database troubleshooting 7-3
gateway troubleshooting 7-3
menu options B-6
options 7-3
U
Unix
ENTERPRISE/CS administration 5-1
updatedef utility B-9
user authorizations
description 6-4, 6-10
General panel 6-15
Jobs panel 6-19
Privileges panel 6-22
Scheduling Tables panel 6-25
specifying authorizations 6-20
Index
15
user connections parameter

Sybase Server 5-10
user ID
See also owner
util utility B-9
utilities
check_gtw 7-11
util B-9
TCP/IP port number 2-4

workstation security
Unix 6-2
Windows 6-2
WS-GTW. See gateways
X
Xterm window
opening 5-2
V
variables. See AutoEdit variables
verify user
viewing
See also display
ViewPoint
collection security 6-23
filter security 6-23
hierarchy security 6-23
security 6-23
ViewPoint window
security 6-5
VMS. See OpenVMS
W
Western European Time 1-12
WET time zone 1-12
wildcard characters
filters 4-25
Windows administrator
workstation gateway
description 1-4
log 3-12
TCP/IP host name 2-4
16
Notes
*100037645*
*100037645*
*100037645*
*100037645*
*100037645*

CONTROL-M Enterprise Manager - Administrator Guide 6.1.00 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CONTROL-M Enterprise Manager - Administrator Guide 6.1.00 PDF

Uploaded by

Copyright:

Available Formats

CONTROL-M/Enterprise

Version 6.1.00 Beta

September 30, 2001

Copyright 2001 BMC Software, Inc. All rights reserved.

Restricted Rights Legend

Contacting BMC Software

USA and Canada

Outside USA and Canada

(01) 713 918 8800

(01) 713 918 8000

BMC Software, Inc.

713 918 8800 or

713 918 8000

Before Contacting BMC Software

operating-system and environment information

sequence of events leading to the problem

commands and options that you used

product error messages

BMC Software, Inc., Confidential and Proprietary Information

BMC Software, Inc., Confidential and Proprietary Information