CONTROL-M Administrator Guide
CONTROL-M Administrator Guide
Administrator Guide
Supporting
CONTROL-M/Enterprise Manager version 6.4.01
CONTROL-M/Server version 6.4.01
CONTROL-M/Agent version 6.4.01
September 2008
www.bmc.com
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC Telephone 713 918 8800 or Fax 713 918 8000
2101 CITYWEST BLVD 800 841 2031
HOUSTON TX 77042-2827
USA
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home.
From this website, you can
■ read overviews about support services and programs that BMC offers
■ find the most current information about BMC products
■ search a database for issues similar to yours and possible solutions
■ order or download product documentation
■ download products and maintenance
■ report an issue or ask a question
■ subscribe to receive proactive e-mail alerts when new product notices are released
■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and
telephone numbers
3
License key and password information
If you have questions about your license key or password, contact BMC as follows:
■ (USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to
[email protected].
■ (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send
an e-mail message to [email protected].
■ (Asia-Pacific) Contact your BMC sales representative or your local BMC office.
Contents 5
Defining a new CONTROL-M/EM component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Updating a previously defined component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Defining a CONTROL-M/Server and its Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Defining a CONTROL-M/Server (automatic discovery method) . . . . . . . . . . . . . . . . 57
Defining a CONTROL-M/Server (manual definition method) . . . . . . . . . . . . . . . . . . 57
Defining CONTROL-M/Agents and remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Planning your strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Defining a CONTROL-M/Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Using multiple agents on the same computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Associating more than one CONTROL-M/Agent on the same host to the same
CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Converting a remote host to a CONTROL-M/Agent. . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring and managing remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Testing communication channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Using Web Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Generating a Web Launch package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Deploying new packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Contents 7
Defining password requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Refreshing password-related system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Setting allowable password lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Setting password complexity rules (required character types). . . . . . . . . . . . . . . 161
Setting password reuse limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Implementing password expiration policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Implementing password policy for all users using the set_pwd_def_lifetime
script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Setting automatic account locking after consecutive failed logon attempts . . . . 165
Unlocking multiple accounts with the unlock_user script . . . . . . . . . . . . . . . . . . 166
Defining users and their authentication criteria to CONTROL-M/EM . . . . . . . . . . . 166
Manually modifying a user’s password criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Changing the DBO password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Defining a CONTROL-M/Agent account (Windows only) . . . . . . . . . . . . . . . . . . . . . . 170
Defining job owner and authentication settings for CONTROL-M/Agents and
remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Contents 9
Starting and stopping CONTROL-M/EM server components and
CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Starting and stopping CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
For UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
For Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Recycling CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Manually testing CONTROL-M/Server communication with Agents and remote
hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Viewing CONTROL-M/EM component activation history . . . . . . . . . . . . . . . . . . . . 272
Sending Control Shell commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Managing CONTROL-M/Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Setting whether a CONTROL-M/Server is managed or unmanaged from
CONTROL-M/EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Disabling and enabling a CONTROL-M/Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Deleting a CONTROL-M/Server definition from CONTROL-M/EM . . . . . . . . 275
Implementing Heartbeat Monitors and the Watchdog facility . . . . . . . . . . . . . . . 275
Managing CONTROL-M/Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Disabling a CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Setting debug on CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Setting CONTROL-M/Agent system parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 278
Contents 11
Part 5 Appendixes 379
Appendix A Configuring CORBA components 381
Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
CORBA overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Naming Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
What is an Interoperable Object Reference (IOR)? . . . . . . . . . . . . . . . . . . . . . . . . . 386
Advanced communication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Assigning ports when using a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
XML configuration file scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Configuring CORBA components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Specifying domain settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Specifying Naming Service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Assigning ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Specifying Advanced parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Index 543
Contents 13
14 CONTROL-M Administrator Guide
Figures
CONTROL-M/EM architectural structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CONTROL-M/Server and Agent architectural structure . . . . . . . . . . . . . . . . . . . . . . . 31
CONTROL-M Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Options dialog box for CONTROL-M Configuration Manager . . . . . . . . . . . . . . . . . . 45
CONTROL_M/EM Root Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
CONTROL-M Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
CONTROL-M System Maintenance Utility Main Menu . . . . . . . . . . . . . . . . . . . . . . . . 48
Recommended workflow for connecting CONTROL-M components . . . . . . . . . . . . 50
CONTROL-M/Agent Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Recommended workflow for setting up the scheduling environment . . . . . . . . . . . . 81
Using the Active Shout Destination Table to direct shouts . . . . . . . . . . . . . . . . . . . . . 91
Sample Rull.dat file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Sample Trace File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Recommended workflow for setting up authentication security . . . . . . . . . . . . . . . 150
Recommended workflow for setting up authorization security . . . . . . . . . . . . . . . . 179
CONTROL-M/Server Security dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Recommended workflow for implementing auditing . . . . . . . . . . . . . . . . . . . . . . . . . 212
Recommended workflow for setting up firewall security . . . . . . . . . . . . . . . . . . . . . 218
Transient connection model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Persistent connection model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Recommended workflow for configuring CONTROL-M for high availability . . . . 229
CONTROL-M/Server Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Recommended workflow for maintaining the CONTROL-M environment . . . . . . 264
Recommended workflow for maintaining and managing databases . . . . . . . . . . . . 283
CONTROL-M/Server Debug window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
CONTROL-M/Agent Debug window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Excerpt from a GCS_LOG File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Exception Alerts window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Recommended workflow for connecting CONTROL-M/Enterprise Manager
components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Naming Service directory illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Domain Settings panel—Domain Configuration (orbconfigure) wizard . . . . . . . . . 394
Naming Service panel—Domain Configuration (orbconfigure) wizard . . . . . . . . . 396
Show local settings—Naming Service panel (orbconfigure) wizard . . . . . . . . . . . . . 397
Ports panel—Domain Configuration (orbconfigure) wizard . . . . . . . . . . . . . . . . . . . 398
Summary panel—Domain Configuration (orbconfigure) wizard . . . . . . . . . . . . . . . 400
Advanced settings—Summary panel (orbconfigure) wizard . . . . . . . . . . . . . . . . . . 400
CONTROL-M Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figures 15
16 CONTROL-M Administrator Guide
Tables
Component icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Task summary: connecting components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
CONTROL-M Definition dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Parameters for manually defining a CONTROL-M/Server and its Gateway . . . . . . 59
Task summary: setting up the scheduling environment . . . . . . . . . . . . . . . . . . . . . . . . 96
Parameters for the Global Conditions distribution facility . . . . . . . . . . . . . . . . . . . . . 108
Fields and values of the Shout Destination table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
CONTROL-M General User Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Shell paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Shell parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
CTMBAT2UNC Utility Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Scripts before and after running CTMBAT2UNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Task summary: setting up the scheduling environment . . . . . . . . . . . . . . . . . . . . . . . 154
Application security levels for CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . 182
Task summary: setting up authorization security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Privileges tab access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Privileges and features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Scheduling table authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Scheduling table access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Access levels for conditions and resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Calendar access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Task summary: implementing auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Parameter values for activities to be audited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Task summary: configuring CONTROL-M for high availability . . . . . . . . . . . . . . . 231
Relevant worksheet tables by database server type . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Worksheet for database parameter values—Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Worksheet for mirroring parameters (when copying)—Sybase . . . . . . . . . . . . . . . . . 233
Worksheet for mirroring parameters (when building)—Sybase . . . . . . . . . . . . . . . . . 234
Worksheet for environment variables and alternative names— Sybase . . . . . . . . . 235
Worksheet for database parameter values—Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Worksheet for mirroring parameters—Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Worksheet for environment variables—Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Worksheet for database parameter values—MSSQL . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Worksheet for MSSQL Server mirroring parameters . . . . . . . . . . . . . . . . . . . . . . . . . 238
Worksheet for MSSQL environment variables—MSSQL . . . . . . . . . . . . . . . . . . . . . . 238
Worksheet for database parameter values— PostgreSQL . . . . . . . . . . . . . . . . . . . . . 239
Worksheet for mirroring parameters — PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . 239
Worksheet for environment variables and alternative names— PostgreSQL . . . . . 240
Additional required details—Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Tables 17
Additional required details—MSSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Additional required details—PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Utilities affecting the primary database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Task summary: maintaining the CONTROL-M environment . . . . . . . . . . . . . . . . . . 268
Fields in the CONTROL-M/Agent Debug dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 277
Fields in the CONTROL-M/Agent - Update System Parameter dialog box . . . . . . 279
Task summary: maintaining and managing databases . . . . . . . . . . . . . . . . . . . . . . . . 287
Database Maintenance menu options—from the Root Menu . . . . . . . . . . . . . . . . . . . 288
Database Maintenance Menu options—from the Main menu . . . . . . . . . . . . . . . . . . 289
Logical device description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Location of the dedicated database message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Location of the dedicated database message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
proclog utility parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Examples of diagnostic scenarios and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Diagnostic commands using the Control Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Persistent diagnostic record file (.ini file) parameters . . . . . . . . . . . . . . . . . . . . . . . . . 333
GCS Diagnostic Defaults.rsc file parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Communication trace diagnostic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Checks to make when CONTROL-M Configuration Agent Not Available . . . . . . . 346
Reasons indicative of a single condition issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Reasons indicative of a multiple condition issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Troubleshooting aspects related to Naming Service problems . . . . . . . . . . . . . . . . . 354
Troubleshooting aspects related to CORBA server problems . . . . . . . . . . . . . . . . . . 356
TAO information required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Troubleshooting Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Action codes for the GCS_LOG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Data flags for the GCS_LOG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Scopes in the XML configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Task summary: connecting components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
General parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Gateway parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Global Conditions Server (GCS) administration parameters . . . . . . . . . . . . . . . . . . . 429
Global Conditions Server (GCS) logging parameters . . . . . . . . . . . . . . . . . . . . . . . . . 431
Global Alerts Server (GAS) parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Configuration Agent parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
GUI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
GUI Server parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Exception handling (XAlerts) parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Configuration Management Server (CMS) parameters . . . . . . . . . . . . . . . . . . . . . . . . 450
Gateway parameters in the defaults.rsc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
CONTROL-M/Server system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
CONTROL-M/Server communication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
CONTROL-M/Server communication and debug parameters . . . . . . . . . . . . . . . . . 462
CONTROL-M/Server operational parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
CONTROL-M/Server parameters for communicating with agent computers . . . . 465
CONTROL-M/Server database parameters for the Sybase environment . . . . . . . . 468
CONTROL-M/Server database parameters for the Oracle environment . . . . . . . . . 471
CONTROL-M/Server database parameters for the MSSQL environment . . . . . . . . 473
CONTROL-M/Server database parameters for the PostgreSQL environment . . . . 475
Tables 19
20 CONTROL-M Administrator Guide
About this book
The CONTROL-M Administrator Guide is a single, inclusive guide that replaces the:
However, most of the utility descriptions from those earlier guides have been moved
to the CONTROL-M Utility Guide.
The examples provided in this guide assume the use of cshell. If your site uses a
different shell type, it is your responsibility to adjust the instructions to fit your site’s
needs.
NOTE
■ BMC Software recommends that before you use this book, you become familiar with the
concepts presented in the CONTROL-M Concepts Guide.
■ This book assumes that CONTROL-M is already installed and initially configured. The
installation and configuration tasks are described in the CONTROL-M Installation Guide.
■ This book does not discuss end-user tasks (for example, defining job processing
definitions or monitoring jobs in the production environment). Those tasks are described
in the CONTROL-M User Guide.
This guide is divided into parts, each covering a major CONTROL-M administration
area. Each part contains relevant chapters.
■ At the end of the conceptual information, immediately before the task descriptions
is a task summary table that identifies the top level tasks, the lower level tasks that
comprise the top level task, and the page numbers where those lower level tasks
begin.
Like most BMC documentation, this book is available in printed and online formats.
To request printed books or to view online books and notices (such as release notes
and technical bulletins), see the Customer Support website at
http://www.bmc.com/support_home. Most product shipments also include the
books on a documentation CD.
NOTE
Online books are formatted as PDF or HTML files. To view, print, or copy PDF books, use the
free Adobe Reader from Adobe Systems. If your product installation does not install the
reader, you can obtain the reader at http://www.adobe.com.
The software also offers online Help. To access Help, press F1 within any product or
click the Help button in graphical user interfaces (GUIs).
Conventions
This book uses the following special conventions:
■ Variable text in path names, system messages, or syntax is displayed in italic text:
testsys/instance/fileName
Syntax statements
The following example shows a sample syntax statement:
The following table explains conventions for syntax statements and provides
examples:
Item Example
Items in italic type represent variables that alias
you must replace with a name or value. If a
variable is represented by two or more databaseDirectory
words, initial capitals distinguish the second
and subsequent words. serverHostName
Chapter 1
Essentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 2
Connecting components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 3
Setting up and managing the scheduling environment . . . . . . . . . . . . . . . . . . . . . . 79
1
1 Essentials
This chapter presents the following topics:
CONTROL-M architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
CONTROL-M/EM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CONTROL-M/Server and Agent components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M Agent
Infrastructure processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Who is a CONTROL-M Administrator? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Key terms—user, owner, author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Starting and stopping infrastructure processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Starting and stopping infrastructure processes in Windows . . . . . . . . . . . . . . . . . 36
Starting and stopping infrastructure processes in UNIX and Linux . . . . . . . . . . . 36
Using CONTROL-M Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Starting CONTROL-M Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Understanding the display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Adjusting the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Filtering the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Viewing a component’s properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Changing your password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting your CONTROL-M Configuration Manager preferences . . . . . . . . . . . . . 44
Using interactive menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Using the CONTROL-M/EM Root Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Using the CONTROL-M/Server Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Using the CONTROL-M System Maintenance Utility Main Menu . . . . . . . . . . . . 47
CONTROL-M architecture
This section describes and illustrates the basic CONTROL-M/EM and
CONTROL-M/Server architectural structures. These structures communicate by
using the TCP/IP protocol.
Chapter 1 Essentials 27
CONTROL-M/EM components
CONTROL-M/EM components
Figure 1 on page 28 illustrates CONTROL-M/EM component architecture. A brief
description of the main CONTROL-M/EM components follows.
■ client components
— Command line utilities—Many functions that are available through the GUIs
are also available through the use of interactive and batch utilities. Utilities are
described in the CONTROL-M Utility Guide. Where appropriate, this guide also
describes certain interactive utility functions.
— Batch Impact Manager (BIM) server—monitors critical batch services when your
site uses the BMC Batch Impact Manager add-on.
— Forecast server—helps you predict job patterns in order to forecast schedules for
running jobs in the future, when your site uses the CONTROL-M/Forecast
add-on.
Chapter 1 Essentials 29
CONTROL-M/Server and Agent components
■ infrastructure components
— CORBA-based naming services, which enables the client to locate the server to
which it must connect. For more information, see Appendix A, “Configuring
CORBA components.”
■ CONTROL-M/Server
■ Agent computers
Chapter 1 Essentials 31
CONTROL-M/EM, CONTROL-M/Server, and CONTROL-M Agent Infrastructure processes
Agentless computer on which jobs can run. Each remote host is identified by its
node ID.
■ Control Modules
■ infrastructure components
CONTROL-M/EM processes
■ CONTROL-M/EM processes:
■ Databases
CONTROL-M/Server processes
CONTROL-M/Agent processes
■ p_ctmar
■ p_ctmag (Known as CONTROL-M/Agent Listener, which on Windows runs as a
service).
■ p_ctmat (Known as CONTROL-M/Agent Tracker)
■ ctmfw_service (Windows only, where it runs as a service; Known as CONTROL-M
File Watcher)
■ CONTROL-M/Agent (on Unix and Windows it runs as a service)
■ CONTROL-M FileWatcher (Windows only, where it runs as a service)
Chapter 1 Essentials 33
Who is a CONTROL-M Administrator?
The term CONTROL-M administrator can refer to anyone who has at least one of the
following sets of credentials:
■ accounts and passwords that allow you to log into CONTROL-M/EM with the
permissions and privileges (defined in the Privileges tab) needed to manage
CONTROL-M/EM, CONTROL-M/Server and CONTROL-M/Agent
■ database owner credentials that allow you to log into the database and run utilities
that update the database
■ Users
■ Owners
Owners are credentials under which jobs will be executed. For operating system
jobs, owners are accounts. For application jobs, owners are logical names that
reference the credentials of the application account (for example, for SAP, it will
reference user, password, host, port, and so on, for the SAP account).
Each job must be assigned an owner. The administrator determines which owners
a particular user is allowed to assign to a job.
■ Authors
Chapter 1 Essentials 35
Starting and stopping infrastructure processes in Windows
1. Choose Start => Control Panel => Administrative Tools => Services.
1. Choose Start => Control Panel => Administrative Tools => Services.
You can start and stop CONTROL-M/EM infrastructure processes using either of the
following methods:
NOTE
If not all CONTROL-M/EM server components are installed on one account (that is, you have
distributed your CONTROL-M/EM components), you need to include the startup and
shutdown commands in operating system startup and shutdown scripts of the host computer.
Add the following commands to the start-up script of your operating system as
appropriate:
su - ecs_account -c start_ns_daemon
su - ecs_account -c start_server
su - ecs_account -c start_cms
su - ecs_account -c start_config_agent
su - ecs_account -c start_web_server.sh
■ Add the following commands to the shut-down script of your operating system as
appropriate:
su - ecs_account -c stop_ns_daemon
su - ecs_account -c stop_cms
su - ecs_account -c stop_config_agent
su - ecs_account -c stop_web_server.sh
Chapter 1 Essentials 37
Starting and stopping infrastructure processes in UNIX and Linux
2 In the CONTROL-M/EM Root menu, enter the number for the Activation Menu
option.
3 In the Activation menu, enter the number of the appropriate start or stop process
option (or start all or stop all option).
4 Enter q to exit.
You can manually shutdown and startup infrastructure components using the
following methods:
■ CONTROL-M Manager Menu, which you access from the CONTROL-M Main
Menu (ctm_menu)
■ supplied utilities
2 Choose Desired State and then choose one of the following submenu options:
2 In the CONTROL-M Main menu, enter the number of the CONTROL-M Manager
option.
3 If change password fields are displayed, your password is soon due to expire. Fill
in your new password, and then confirm it.
Chapter 1 Essentials 39
Understanding the display
You can drag the headings and columns. You can also customize the console (for
more information, see “Setting your CONTROL-M Configuration Manager
preferences” on page 44).
IOAGATE
— If you can display and use the CONTROL-M Configuration Manager, it means
that the Configuration Manager Server is up and working.
— If the Configuration Manager Server is not up and working, you cannot display
and use the CONTROL-M Configuration Manager.
Chapter 1 Essentials 41
Adjusting the display
— To help you position the pane, while dragging the pane, move your cursor over
one of the postioning arrows that appears on the page. The area where the pane
will be positioned when you release the mouse is highlighted.
You can perform nested grouping of components (for example, you can group
components by desired state, and within desired state you can group them by
host)
— For each required grouping (beginning from the outer level and moving in),
right click on the column name (for example, State) and choose Group By This
Column.
The components are grouped as requested. A chart of the nested group levels
appears at the top of the detail pane.
— To eliminate a grouping from the nest, right click the group in the chart and
choose Ungroup.
1 Choose View => Component Filter to display a filtering row at the top of the detail
pane.
A Position the cursor in the upper right corner of the column and then click the
displayed icon
A Position the cursor in the upper right corner of the column and then click the
displayed icon
C Fill in the Custom AutoFilter by specifying two sets of logical operators and
values separated by the appropriate relationship (button). Click OK.
A Click Edit Filter in the right corner of the Status bar at the bottom of the
window.
B Fill in the Filter Builder dialog box using the following guidelines:
■ Click keywords (for example, And, Type, and begins with) to display valid
keywords, and make the appropriate selections.
■ To add an additional set of criteria, click the relationship (And or Or) value,
and choose Add Group.
C Click OK.
Chapter 1 Essentials 43
Viewing a component’s properties
To change your password at any other time, you must issue the request through the
CONTROL-M/EM or CONTROL-M/Desktop windows.
1 If the change password fields are not already displayed, in the CONTROL-M/EM
or CONTROL-M/Desktop window, choose Tools => Change Password.
2 Fill in your current and new passwords, and then confirm the new password.
3 Click OK.
NOTE
Alternatively, you can change passwords using the User Authorizations window, but this is
generally not recommended unless you are changing other password criteria, or changing the
passwords for other users. For more information, see “Manually modifying a user’s password
criteria” on page 169.
2 In the General panel, set your preferences for the available options. When setting
options, consider the following:
■ Long date format displays the month name in the date instead of using a
numeric date format, and displays the time.
4 Click OK.
Chapter 1 Essentials 45
Using the CONTROL-M/EM Root Menu
Many of the tasks described throughout the chapters of this book are performed from
these menus. This chapter provides instructions for accessing these menus, so that the
instructions do not need to be repeated for each task.
NOTE
The database server must be running for the Root Menu and its submenus to be displayed.
3 When prompted, enter the CONTROL-M/EM DBO user name and password.
Chapter 1 Essentials 47
Using the CONTROL-M System Maintenance Utility Main Menu
■ Enter the ctm_menu command to display the CONTROL-M Main Menu, and
then
— Enter the number of the System Parameters and Shout Destination Tables
option to display the CONTROL-M System Maintenance Utility Main Menu.
3 To use the CONTROL-M System Maintenance Utility Main Menu its submenus
2
2 Connecting components
This chapter presents the following topics:
Conceptual overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
CONTROL-M/Server definition and management . . . . . . . . . . . . . . . . . . . . . . . . . 51
CONTROL-M/Agents and remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CONTROL-M/EM Web Launch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Defining CONTROL-M/EM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Defining a new CONTROL-M/EM component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Updating a previously defined component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Defining a CONTROL-M/Server and its Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Defining a CONTROL-M/Server (automatic discovery method) . . . . . . . . . . . . . 57
Defining a CONTROL-M/Server (manual definition method) . . . . . . . . . . . . . . . 57
Defining CONTROL-M/Agents and remote hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Planning your strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Defining a CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Using multiple agents on the same computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Associating more than one CONTROL-M/Agent on the same host to the same
CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Converting a remote host to a CONTROL-M/Agent . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring and managing remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Testing communication channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Using Web Launch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Generating a Web Launch package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Deploying new packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Conceptual overview
Figure 8 highlights the basic recommended workflow for connecting CONTROL-M
components. This overview section explains concepts that are related to the
workflow.
For specific tasks that correspond to each phase of the workflow, see Table 2 on
page 54. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
Plan your
strategy
page 61
Define CONTROL-M/EM
components
page 54
Define CONTROL-M/
Server and its Gateway
page 56
Define CONTROL-M/
Agents and remote
hosts
page 61
■ Discovery/Define
When defining CONTROL-M/Servers and their gateways (which you do using the
CONTROL-M/Server Definition dialog box), you can choose either of the
following definition methods:
Using the CONTROL-M Configuration Manager, you can change the connection
mode (managed/unmanaged) of existing CONTROL-M/Servers. For more
information, see “Setting whether a CONTROL-M/Server is managed or unmanaged
from CONTROL-M/EM” on page 274.
■ You can place remote hosts under the control of any other CONTROL-M/Agents
installed on computers under the same CONTROL-M/Server.
You will need to define the following information for each remote host:
You can define specific settings for a host, or use the default settings. For more
information, see “Configuring and managing remote hosts” on page 68.
These settings specify the owners of the jobs that are running on the remote host,
and owner authentication parameters that are used for connecting to the remote
host. In a CONTROL-M job that is destined to be run on a remote host, you must
define each job owner that is specified.
Using a Web Launch package, the administrator can easily do the following from a
single point:
NOTE
When you use Web Launch for client deployment, CONTROL-M/Desktop, the
CONTROL-M/EM GUI, and CONTROL-M Configuration Manager are the only client
applications included in the deployment. The following client components do not get
included in the Web Launch package, and cannot be manually deployed or used:
Deployed Web Launch packages can exist side-by-side with other Web Launch
packages and with other regular CONTROL-M/EM installations. If a Web Launch
package is deployed on a computer where a client already exists, the Web Launch
package installs a new client; it does not upgrade the existing client. If desired,
however, you can remove the old client.
NOTE
If you will be using CONTROL-M Web Server, and the computer on which it is resident
contains multiple versions of Java, you must specify the location of the correct Java version
(1.5) in the environment variable called JAVA_HOME. For more information, see the relevant
Release Notes.
The first time that users deploy a package, they must access the package from a URL
generated with the package. From that time on, any updates will automatically be
deployed when the users start CONTROL-M/EM, CONTROL-M/Desktop, or
CONTROL-M Configuration Manager.
B At Type, select the type of component that you want to add. Valid values are:
Optional for the GAS and GUI servers, and not relevant for the GCS server.
When defining a BIM or Forecast_Server component, you must enter the name
of the GUI server with which the component will communicate.
Observe the following guidelines when choosing a name for a new server:
■ You can define multiple GUI servers and multiple GAS servers to run
simultaneously. (These capabilities allow you to balance job loads as needed in
your environment.) These servers can run on the same account or on different
hosts. Each instance of a GUI server (or GAS server) must have a unique name.
The GUI Server name and the GAS server name are used to reference both
components when using the CONTROL-M/EM client components.
■ You can specify any logical name for an instance of either component. For
example, you can enter the virtual host name of a cluster computer in which the
GUI Server (or Global Alerts Server) is installed, without specifying the node on
which the component is installed.
■ By default, the GUI Server is named according to its host name. Thus, if more
than one GUI Server exists on the same host, each instance must have a unique
name.
A At Platform, select the operating system for the host computer on which the
component runs.
4 At Check Interval, enter how frequently, in number of seconds, you want to check
the component’s state.
5 (optional) In the Startup box, indicate the mode in which the component should
start:
■ To use a startup command other than the default, select the Override Manually
check box and enter a command in the Command box.
■ If you want to use optional arguments for the startup command, enter them in
the Additional Parameters box.
When adding a new CONTROL-M/Server and its Gateway, you can use automatic
discovery or manual definition:
■ Manual definition requires that you supply all parameter values. For instructions,
see page 57.
NOTE
This method is valid only for CONTROL-M/Server versions 6.3.01 and higher.
B At CONTROL-M ID, accept the default unique code or enter a unique 3-digit
code identifying the CONTROL-M/Server.
C At CONTROL-M Host, enter the name of the host computer on which the
CONTROL-M is installed.
E Click Next.
4 When the Step 3 wizard panel is displayed, ensure that Activate Gateway is
selected.
2 Fill in the CONTROL-M Definition dialog box. Table 4 describes the essential
parameter values that you need to provide.
You should choose a name that is meaningful enough to identify your CONTROL-M.
For example, if the CONTROL-M handles workloads for Division 7, which is associated
with the company’s headquarters in Paris, you might use HQ_PARIS_DIVISION-07.
The name can be a maximum of 20 alphanumeric characters long. You can include
symbols, but do not use blank spaces.
ID unique 3-character code (such as 999 or NYC) that CONTROL-M/EM uses to identify
each CONTROL-M/Server
The code must be unique. It can consist of numerals and uppercase letters.
Platform operating system on which your CONTROL-M is installed. Note the following:
3 If you are defining a new CONTROL-M/Server, under Gateway, click New. You
must specify a Gateway when you set up your work environment. Otherwise, you
can define a new gateway, or modify or delete an existing gateway.
B Enter the name of the gateway. You can define multiple gateways for a
CONTROL-M/Server, but only one CONTROL-M can be up (started) at one
time. Additionally, each Gateway should be located on a separate computer.
C In the Platform field, select the operating system for the host computer on which
the component runs.
E In the Check Interval field, enter how frequently, in seconds, to check the
gateway’s state.
F (optional) In the Startup box, indicate the mode in which the gateway should
start:
■ To use a startup command other than the default, select the Override
Manually check box and enter a command in the Command box.
■ You want enter optional arguments for the startup command in the
Additional Parameters box.
Before proceeding, ensure that you comply with the following requirements and
guidelines.
— Can run all jobs assigned to the specific node ID which identifies the remote
computer
— Do not require CONTROL-M/Agent installation on the remote computer
— Do not require version updates
— Require less management
■ The main advantages of CONTROL-M/Agents over remote hosts are that agents
support counters and multiple types of shouts:
— If you define the CONTROL-M, the default state is Unmanaged, and you must
change it to Managed via the CONTROL-M Configuration Manager.
You can use SSH connections for remote hosts running UNIX, Windows,
OpenVMS, Z/OS USS (OpenEdition) and PASE (AIX environment) on AS/400:
NOTE
When you work with z/OS USS (OpenEdition) or PASE AS/400 remote hosts, set the
RJX_CONN_MODE system parameter in CONTROL-M/Agent to 0.
If you will be using more simultaneous connections than your current SSH server
settings allow, you must increase the value for these settings accordingly.
EXAMPLE
For an OpenSSH server, set the MaxStartups and LoginGraceTime parameters in the
sshd_config file.
You can use WMI connections with remote hosts running Windows 2003,
Windows XP, or a later version. WMI is part of the Windows operating system.
NOTE
If the CONTROL-M/Agent will be connecting to a remote host on Windows by using the
WMI connection method, ensure that the following requirements are satisfied:
■ The Log On as option for the CONTROL-M/Agent service is set to This account.
■ The user account that is running the CONTROL-M/Agent service is Administrator and
is defined as a Domain user.
■ Job owners are members of the Administrator group on the remote host.
Consider the following requirements when deciding which connection method to use
for remote hosts:
— To use On statements and the View JCL, Edit JCL, and View Sysout options, you
must define a directory named SYSOUT on the remote host. This directory must
be writable by all the job owners on that host. This directory must also be shared
so that the CONTROL-M/Agent user can access it for reading and writing.
When defining the properties of a remote host, specify the full local path (for
example, C:\shared documents\SYSOUT) of this directory so that the job output
will be written to it.
■ For Secured Shell (SSH) connections, you must ensure that an SSH Server is
installed and running on each remote host.
Defining a CONTROL-M/Agent
This procedure describes how you can add a CONTROL-M/Agent to an existing
CONTROL-M/Server, or modify an existing CONTROL-M/Agent.
NOTE
A CONTROL-M/Agent should be installed first before it is defined. For information about
installing CONTROL-M/Agents, see the CONTROL-M Installation Guide.
The Add CONTROL-M/Agent dialog box is displayed. Fill in the name for the
agent. Click Advanced.
2 In the appropriate dialog box, fill in the fields in the General, Persistent Connection
and Retry/Timeout tabs.
NOTE
When you modify server-to-agent connection parameters, port updates are made on both
the CONTROL-M/Server and the CONTROL-M/Agent side.
3 Click Test to check that your settings are correct and workable.
With multiple agents, more than one CONTROL-M/Server can request jobs on the
same computer. In this type of configuration, each CONTROL-M/Agent is
associated with a different CONTROL-M/Server.
■ Port numbers
Each agent must use a different Server-to-Agent port number. During installation,
it is important to record the port that you specified for each agent. You will need
this port number when you define the communication for that agent in
CONTROL-M/Server.
■ Agent names
■ Default Agent
During installation a checkbox in the Agent Name window enables you to specify
if you are installing the Default agent. If no specific agent name is specified in a
CONTROL-M/Agent utility command, the Default agent handles the commands.
All CONTROL-M Control Modules work with the default agent. Some
CONTROL-M Control Modules work with non-default agents.
When upgrading a multiple agent installation, you must run the installation
program a separate time for each agent you want to upgrade. Each time you run
the program, you are prompted to select the logical name of an agent that has not
yet been upgraded to the current version. You must upgrade all agents first before
installing additional agents. The Default agent from the previous version will
remain as the Default agent in the new version.
1 For each additional agent you are connecting, repeat the steps in “Defining a
CONTROL-M/Agent” on page 64, but ensure that you provide each agent with a
different logical host name and server-to-agent port number.
B Open the hosts file located in the etc directory and add the following line:
3 For each additional agent, change the value of the Logical Agent name system
parameter. You can do this using CONTROL-M Configuration Manager. For
instructions, see “Modifying CONTROL-M/Agent system parameters” on
page 409.
EXAMPLE
If two agents are installed on a computer called appserver with the IP address 11.22.33.44,
complete the following steps to associate the agents with a CONTROL-M Server on a UNIX
computer:
3. Change the Logical Agent name field for the second agent to appserver2.
1 Ensure that no jobs have been submitted to, or are running on, the required remote
host.
1 Ensure that no jobs have been submitted to, or are running on, the required remote
host.
3 From the CONTROL-M Main menu, enter the number of the Agent Status option.
4 In the Agent Status menu, enter the number of the Change Agent Platform Status to
Disabled option.
5 At the prompt, enter the name of the remote host you want to disable.
6 At the next prompt, enter the number of the Delete Agent Platform Entry option.
This will delete the remote host.
7 Use ctmping to discover the agent. For more information, see CONTROL-M Utility
Guide.
NOTE
Alternatively, you can run the CONTROL-M/Server ctmhostmap utility (described in the
CONTROL-M Utility Guide) to map a remote host.
2 Click the CONTROL-M/Agents that will use both a particular connection method
and a particular set of connection parameters to access remote hosts. (Later on, you
can add remote hosts with different settings than the defaults.)
■ For SSH, supply the SSH Server port number, select the encryption algorithm,
and if data should be compressed for transfer, click compression.
■ For WMI, specify the full path to a Sysout directory on the remote host that is
shared and has the name SYSOUT. For example, c:\temp.
5 Click Save.
1 In the CONTROL-M Configuration Manager, right click the remote host and
choose Properties.
4 Click Test to check that your modifications to the original settings are correct and
workable.
NOTE
Once you have defined default connection and host-owner authentication settings, you do not
need to perform this task unless you want to override the defaults for particular remote hosts.
If you submit a job to a remote host that you haven’t manually defined, CONTROL-M/Server
submits the job based on the default connection settings. Once the job has been submitted, the
new remote host appears in the CONTROL-M Configuration Manager.
NOTE
Alternatively, you can run the CONTROL-M/Server ctmhostmap utility (described in the
CONTROL-M Utility Guide).
2 Type the name of the remote host, and select the CONTROL-M/Agents that will
connect with the remote hosts. Click Next.
3 In Step 2 of the wizard, select the connection method, and fill in the required
connection parameters (for details, see “To map remote hosts to
CONTROL-M/Agents and define default connection settings” on page 68). Click
Test to check that your settings are correct and workable. Click Next.
4 To define an owner for running jobs on the host being defined, fill in the job owner
and authentication information in Step 3 of the wizard (for details, see “Defining
job owner and authentication settings for CONTROL-M/Agents and remote
hosts” on page 173). (If you already have an owner defined for this host, skip this
step, click Next, and proceed to step 6.)
5 Click Test to check that your settings are correct and workable. Click Next.
6 In Step 4 of the wizard, check the summary and if it is acceptable click Finish.
■ Run the CONTROL-M/Server ctmhostmap utility (described in the utilities chapter of the
CONTROL-M Utility Guide).
■ Run a mass conversion (described in Appendix E, “Mass conversion of agents and remote
hosts.”
2 Determine all owners that use the CONTROL-M/Agent computer. You will need
this information for step 5.
5 Fill in the rest of the remote host details as you would if you were defining a new
remote host. For details, see “To override default settings for a remote host” on
page 70.
In the CONTROL-M Configuration Manager, right click the remote host and choose
Show agents.
NOTE
Alternatively, you can run the CONTROL-M/Server ctm_diag_comm utility (described in the
CONTROL-M Utility Guide).
NOTE
Alternatively, you can run the CONTROL-M/Server ctm_diag_comm utility (described in the
utilities chapter of the CONTROL-M Utility Guide).
When the communication channel test is complete, a dialog box displays the result.
B If you have already generated a Web Launch package, decide whether you are
updating the existing package or creating a new instance of CONTROL-M/EM
client components to exist side-by-side with the previous instance (for example,
two different release levels).
NOTE
You cannot use a new Web Launch package to remove contents that have already been
deployed.
C On the computer on which you are creating the package, navigate to:
<emHomeDir>\bin
NOTE
If you are creating the package on a computer that contains a full installation, and the web
server that will be used to deploy the package is up, bring down the web server before
continuing with the next step.
To bring down CONTROL-M Web Server, perform one of the following as appropriate:
■ On Windows:
1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the CONTROL-M Web Server service, and choose Stop.
A Run empackui.exe which opens the Web Launch – Prepare Package dialog box.
B In the dialog box, fill in the Host Name and Port Number fields with the values for
the web server computer.
If you are creating the package on a computer that contains both client
components and server components (a full installation), the default values for
CONTROL-M Web Server computer are automatically inserted into these fields.
C If you are using CONTROL-M Web Server, ensure that the default port (18080)
is free and available or change the port. The following scripts can help you when
defining the port for CONTROL-M Web Server:
To check which port CONTROL-M Web Server is configured to use, run the
following script, as appropriate:
To change the default port, run one of the following scripts, as appropriate:
NOTE
■ The port and host values are embedded in the Web Launch package. If after
generating a Web Launch package you modify either value, you must
■ If you are using your own web server and creating multiple instances of Web
Launch packages, ensure that you are using different URLs for each instance.
D In the Instance field, supply an instance name for the Web Launch package, in
the format web_<name>, where <name> is the CONTROL-M/EM installation
instance name. The use of unique instance names enables users to access
different Web Launch packages (for example, a package for production and a
different package for testing). The following characters are not valid for use in
the Instance field: \/:*?"<>| and blank.
E Optionally, add a description. This description later appears at the bottom of the
Web Launch page when the user enters the URL. The following characters are
not valid for use in the Description field: " < > ( ) &
F If you are using certificate data from a security product, provide the file name
and password (optional).
NOTE
If you do not provide certificate data, the end user will receive a Publisher:
publisher unknown message when deploying the updates for the first time. This
does not affect Web Launch package deployment.
■ A URL that points to a BMC-supplied HTML web page that allows users to
access to the Web Launch package. (You should not edit or change the web
page HTML or icons.) The referenced URL is displayed only in full
installations, but whether or not it is displayed, its value is:
http://<host>:<port>/web-launch/
■ A .zip and a .tar file which can be used in the optional step below.
NOTE
Each time you generate a new package, the new .zip and .tar files override the earlier .zip
and .tar files.
3 If you created the Web Launch package in a different location than the instance of a
full CONTROL-M/EM installation, do the following:
A Stop the web server. To stop CONTROL-M Web Server, run one of the
following scripts, as appropriate:
■ On Unix: <emHome>/scripts/stop_web_server.sh
■ On Windows:
1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the CONTROL-M Web Server service, and choose Stop.
B If you are using a web server that was not supplied by BMC Software, create a
physical directory in the web server host and then define the directory as a
virtual directory called web-launch.
C Copy the appropriate package file (either the .zip file for Windows, or the .tar file
for UNIX) from
<clientHomeDir>\emweb\deploy
— On Unix: <emHomeDir>/appl/emweb/jetty/webapps/
— On Windows: <emHomeDir>\emweb\jetty\webapps\
■ If you are using a different web server, copy it to the physical directory you
created in substep 3B.
D Continue as follows:
■ For Windows, extract the files to the same directory mentioned in substep 3C.
■ For UNIX, uncompress the files to the same directory mentioned in substep
3C by entering tar -xvf <tarFilename>.
4 Start the web server. To start CONTROL-M Web Server, do one of the following, as
appropriate:
■ On Windows:
1. Choose Start => Control Panel => Administrative Tools => Services.
2. Right click the CONTROL-M Web Server service, and choose Start.
The Web Launch package is now ready for deployment on all computers.
NOTE
Users do not require administrative privileges to deploy packages.
Each time a new package is to be deployed, provide your users (for example, through
e-mail) with the following information they need to deploy the package. (You do not
need to provide this information for upgrades to existing packages; upgrades to
existing packages are automatically deployed when the user launches
CONTROL-M/EM, CONTROL-M/Desktop, or CONTROL-M Configuration
Manager.)
■ The URL that they must access for first-time deployment (generated when the
Web Launch package was created).
■ The Web Launch package will not overwrite their existing data.
■ They must perform the following steps the first time they deploy the Web
Launch package on computers containing CONTROL-M/EM clients, but they
will not need to perform these steps for subsequent upgrades:
2. In the Web Launch page, click to open any of the available applications
(CONTROL-M/Desktop, CONTROL-M/Enterprise Manager, or
CONTROL-M Configuration Manager). The package will be deployed across
the entire suite of CONTROL-M/EM applications.
NOTE
If the application links in the Web Launch page are not operational, it means that the
web browser does not recognize the host computer identified in the URL (the computer
containing the web server as a trusted site). In this case, the user must add the host
computer to the browser’s list of trusted sites, and click the link again.
■ When the installation is complete, the application is launched and users are
prompted to log in.
■ Web Launch adds the following links to the Start menu (in addition to the
links for launching CONTROL-M/Enterprise Manager GUI,
CONTROL-M/Desktop, and CONTROL-M Configuration Manager):
These links enable users to access the files related to the Web Launch
instance. (These files are not placed in the regular Windows\Program Files
directory.)
3
Setting up and managing the
3
scheduling environment
This chapter presents the following topics:
Conceptual overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Methods for automating daily job scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Automatic prerequisite condition cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Job version management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Global condition distribution time limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Alert processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Time zone support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Daylight Saving Time support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Load balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Shout facility and Shout Destination tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
CONTROL-M/EM periodic job statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Job statistics generated by CONTROL-M/Server . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Group scheduling table displays in ViewPoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
CONTROL-M/Agent FileWatcher (ctmfw) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
User exits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Shell scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Automating job scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Preparing for automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Customizing the New Day procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Setting up User Daily jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Defining jobs that use ctmorder to schedule other jobs. . . . . . . . . . . . . . . . . . . . . 103
Handling interruptions in User Daily job processing. . . . . . . . . . . . . . . . . . . . . . . . . . 103
Collecting and viewing application server information . . . . . . . . . . . . . . . . . . . . . . . 104
Implementing job version management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Defining quantitative resources, control resources, and global conditions . . . . . . . 107
Modifying the time limit on Global conditions distribution . . . . . . . . . . . . . . . . . . . . 107
Activating scripts with alert data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Implementing time zone support (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Setting up time zone support for jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Ensuring correct time zones for jobs in the Active Jobs file . . . . . . . . . . . . . . . . . 111
Conceptual overview
The main goal in setting up a scheduling environment is to model your production
batch processing flows. Figure 10 on page 81 highlights the basic recommended
workflow for setting up the scheduling environment. This overview section explains
concepts that are related to the workflow.
For specific tasks that correspond to each phase of the workflow, see Table 5 on
page 96. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
NOTE
This chapter assumes that the administrator is responsible for setting up the scheduling
environment at your site. However, at some sites, end-users with administrator privileges
perform some of the relevant tasks.
Automate job
scheduling
page 97
Implement DST
support (optional)
page 111
Implement load
balancing
page 113
Set up Shout
Destination tables
page 115
Implement job
statistics
page 122
Implement
user exits
page 129
Write scripts
page 131
Term Definition
ctmudly utility run by a User Daily job (command: ctmudly name) that
scans scheduling tables associated with the User Daily name,
and schedules jobs in the table that should be scheduled that
day
New Day procedure daily scheduling and housekeeping procedure run at New
Day time, that cleans up the database from the previous
day’s processing and loads new jobs to the Active Jobs file for
the current day’s processing
New Day time site-defined time when the new processing day begins and
CONTROL-M runs the New Day procedure
User Daily (name) logical name, associated with one or more scheduling tables,
that can be specified when the ctmudly utility is run
(command: ctmudly name)
User Daily job user-defined job that can be used to help automate the
ordering of production jobs by running the ctmudly utility
Date Control record record that indicates (in the UDLAST field) the date on
which the User Daily last ran
To automate daily job scheduling, maintenance, and cleanup, you can choose any of
the following methods, or a combination of them:
At the beginning of the New Day procedure, the procedure calculates a new
CONTROL-M working date, and displays the message FORMATTING AJF in the
CONTROL-M/EM Communication Status window for the CONTROL-M.
The following is a list of some of the more important cleanup and housekeeping
functions that the New Day procedure automatically initiates. You can adjust or
disabled many of them:
■ selective cleanup of the Active Jobs file—jobs that have already executed and
ended OK, and jobs whose parameter Max Wait has been exceeded (and are not
Held), are erased from the Active Jobs file
■ partial cleanup of the information in the JOBINF table that is specific to any one
instance of a job run
The New Day procedure can also schedule jobs (place job orders in the Active Jobs
file) if the job’s scheduling criteria are satisfied that day. The procedure only
schedules those jobs that belong to scheduling tables assigned to the reserved User
Daily called SYSTEM. (For more information, see“More about User Daily jobs” on
page 84.)
If your site has a small number of production jobs, using the New Day procedure
to schedule all of them might be advantageous. However, it is frequently more
efficient to use User Daily jobs with the New Day procedure.
■ User Dailies
User Dailies are optional, but when used, they are used with the New Day
procedure. Many sites prefer to split the task of job ordering among multiple User
Dailies. This is especially true if two or more of the following conditions exist:
— When you use User Dailies, the New Day procedure finishes more quickly.
— User Dailies enable you to schedule jobs at any time during the day. Thus, you
can prevent Product Name from having to load the full day’s production job
load at New Day time.
— You can delegate responsibility for User Dailies to other users at your site.
■ ctmorder utility
The ctmorder utility performs job scheduling from a scheduling table in the
CONTROL-M/Server database. You can define jobs that will automatically run
this utility.
In practice, most sites prefer a combined approach, using both the New Day
procedure and User Daily jobs.
■ When creating a scheduling table, you can associate a User Daily name with that
table.
Each scheduling table can have more than one User Daily name associated with it,
and you can associate a User Daily name with multiple scheduling tables.
■ A special User Daily name, SYSTEM, identifies the “master” User Daily. When the
New Day procedure runs, it scans all scheduling tables whose associated User
Daily name is SYSTEM. The New Day procedure looks for jobs in those tables that
should be ordered on that day, and then orders them.
EXAMPLE
Assume that a site uses scheduling tables TBL1 through TBL5. The administrator, Bill,
implements User Daily jobs for use with the New Day procedure as follows:
1. Bill edits the existing scheduling table definitions to associate User Daily names with the
tables:
■ He associates scheduling tables TBL1 and TBL2 with User Daily name UD1.
■ He associates TBL3 and TBL4 with UD2.
■ He associates TBL5 with UD3.
2. Bill creates scheduling table UDTABLE and associates it with User Daily name SYSTEM.
■ He creates job UDJob1, which runs the command ctmudly UD1 at 8:00 A.M.
■ He creates UDJob2 to run ctmudly UD2 at 2:00 P.M.
■ He creates UDJob3 to run ctmudly UD3 at 8:00 P.M.
Based on these settings, the New Day procedure scans UDTABLE during New Day
processing. The results are as follows:
■ At 8:00 A.M., User Daily job UDJob1 runs and schedules jobs from the TBL1 and TBL2
scheduling tables.
■ At 2:00 P.M., UDJob2 runs and schedules jobs from TBL3 and TBL4.
In general, you should not change the UDLAST field. In certain circumstances,
adjusting this date might be useful. For example, to enable the User Daily to run
again on a given day, you can adjust the UDLAST date to be earlier than the current
working date. When necessary, you can use the ctmudlst utility to update the
UDLAST date.
WARNING
Changing the UDLAST value can have unintended, harmful results. BMC Software
recommends that you contact BMC customer support before undertaking such a step.
Changing the value of Ignore New Day Conditions to Y, so that the New Day
procedure does not clean up old conditions would only be useful if your site has jobs
that are triggered by prerequisite jobs that ran the year before.
But changing Ignore New Day Conditions to Y could greatly increase the risk that jobs
will be prematurely triggered—jobs that are waiting for a prerequisite job that will
run in the future can be triggered by a job that ran in the past.
BMC Software provides a much better and safer alternative to enable you to retain
prerequisite conditions for more than one year without changing the default value of
the Ignore New Day Conditions parameter: You can have those conditions added to the
Conditions file with a date reference value of STAT—conditions with a STAT
reference are not automatically cleaned by the New Day procedure.
However, because you do have the capability to change the value of the Ignore New
Day Conditions parameter, to minimize the risks involved, CONTROL-M requires
that you perform an additional step if you do set Ignore New Day Conditions to Y: You
must identify the prefixes or masks of the conditions that should be ignored (that is,
not deleted) in the Ignore Conditions file (dbs_ignrcond.dat). Any conditions whose
prefixes or masks are not specified in the file are treated as if you did not change the
default.
Therefore, if your site will be retaining prerequisite conditions beyond one year, it is
recommended that you provide them with a prefix not used by conditions that
should be deleted on time.
Example
Assume the Ignore New Day Conditions parameter is set to Y and the Ignore
Conditions file contains the following prefixes:
prq_rs_*rpt
pre_prn
srt_def_?
If the new CONTROL-M working date is 15-01-00, the following table demonstrates
which prerequisite conditions will be deleted from the CONTROL-M/Server
database by the New Day procedure:
Conditions existing before executing New Conditions remaining after executing New
Day Procedure Day Procedure
bra_fn_01 14/01 bra_fn_01 14/01
bra_fn_01 15/01
pre_prn_01 15/01
srt_def_a1 15/01
By default, CONTROL-M/EM saves both the current version and the most recent
earlier version of your jobs.
Job version management also allows retention of deleted jobs for a specified period of
time. They are logically deleted (marked as deleted), but retained until they are
physically deleted. Until then, you can restore deleted jobs.
If job version management is implemented and active at your site, the CMS server
automatically deletes older job versions according to the relevant system parameter
settings, as follows:
■ If the retention period for a logically deleted table has passed, the CMS physically
deletes the whole table, with its jobs and their history.
■ If the retention period for a logically deleted job has passed, the CMS physically
deletes the job and its history from the table.
■ If the retention period for a logically deleted job’s history has passed, but the
retention period for the deleted job itself has not passed, the CMS physically
deletes the job’s history (but not the job).
■ For non-deleted jobs, if both the time limit for keeping past versions and number of
past versions to keep has been exceeded, the CMS physically deletes those versions
of the jobs which are expired according to both sets of deletion criteria.
Once you have implemented job version management, if you later switch it off, the
CMS immediately deletes all previously saved job versions (it ignores the time limit
and number of versions values that were defined to determine how long to keep the
job’s version history).
You can also manually delete job versions by running the ccmcli utility.
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 are excluded
from the limitation process (so that global conditions with these dates are distributed
without limitations).
Alert processing
The Alert Data Processing facility is used to activate processes based on data in a
generated Alert. By default, the data is sent from an alert to an SNMP trap. The
facility allows you to use the alert data as input to a script, in addition to or in place of
sending it to an SNMP trap. For information about SNMP, see Appendix D, “SNMP
interface.”
When Alert data is sent as input to a script, the parameters are sent in the following
format:
EXAMPLE
call_type: "I" alert_id: "394 " data_center: "c82 " memname: "tstjob "
order_id: "0001e" severity: "V" status: "Not_Noticed " send_time:
"20080207105553" last_user: " " last_time: " " message: "Ended not OK"
owner: "controlm " group: "tstgr " application: "tstapp " job_name:
"tstjob " node_id: "tlvd0082 " alert_type: "R" closed_from_em: " "
ticket_number: " " run_counter: "00005 "
EXAMPLE
A job run that should run by 10:00 a.m. in Houston, Texas (Central Standard Time) is ordered
by a CONTROL-M/Server in New York (Eastern Standard Time).
To ensure that the job is submitted on time, you could manipulate the Submit By time in the
job processing definition to compensate for the hour difference (for example, define the
submission time as 11:00 a.m.). However, making such adjustments manually can be an error
prone process.
A better method would be to define the job as belonging to the Central Standard Time, and
indicate the local time (Central Standard Time) by which the job should be submitted (10:00
a.m.).
Time zone support is especially useful when it impacts the day a job is ordered
during New Day processing. This often occurs only if the time zone for the computer
that will run the job is far ahead of the time zone of the CONTROL-M/Server
computer—so far ahead that the job must be ordered a day early so that it will be
available for execution on the correct day on the remote computer.
EXAMPLE
A job must be run at 6:00 a.m. Tokyo time (before the opening of the stock exchange in Tokyo).
However, the New Day procedure that schedules the job runs on a CONTROL-M/Server
computer in Paris at 7:00 a.m.
Without time zone support, the CONTROL-M/Server would run at 7:00 A.M. in Paris and
schedule the Tokyo job, but it would be 2:00 P.M. in Tokyo, well past the time for submitting
the job in Tokyo.
With time zone support implemented, CONTROL-M/Server in Paris will order the job the
day before. For example, to enable job submission at 6:00 a.m. on August 23 in Tokyo, the
CONTROL-M/Server in Paris will order the job during New Day processing on August 22.
The TimeZone.dat files contain a pre-supplied list of time zone definitions. You can
modify or add time zone definitions in these files, but you must keep the
CONTROL-M/EM and CONTROL-M/Server time zone files synchronized so that
they contain the same time zones.
For instructions, see “Implementing Daylight Saving Time support” on page 111.
Load balancing
The load balancing feature enables you to submit a job to a node group rather than to a
specific agent or remote host computer. (A node group is a user-defined list of agent
and remote host computers that are capable of running a given job.) After using a
load balancing algorithm to determine which agent or remote host computer in the
node group is best equipped to run the job at the moment, CONTROL-M/Server
submits the job to that node.
NOTE
You can also use the ctmshout utility to issue a Shout message to an indicated destination. For
more information, see the CONTROL-M Utility Guide.
The Shout Destination table contains a list of logical destinations and the equivalent
physical destination of each logical destination.
EXAMPLE
The system administrator defined two Shout Destination tables, DAYSHIFT and
NIGHTSHIFT:
■ In DAYSHIFT, the logical recipient SYS_MANAGER is equated to user Susan, who is the
daytime systems manager
When the DAYSHIFT Shout Destination table is active, Shout messages that are addressed to
SYS_MANAGER go to Susan’s terminal. At 5 P.M., a job runs and changes the active Shout
Destination table to NIGHTSHIFT. Starting then, Shout messages that are addressed to
SYS_MANAGER go to Robert’s terminal.
■ CONTROL-M/Forecast
■ BMC Batch Impact Manager
■ Critical path analysis for jobs
■ Statistics details in the Active tab in the job editing form in CONTROL-M/EM
NOTE
When right-clicking a job node in the CONTROL-M/EM GUI and selecting Statistics, the data
is displayed as follows:
The statistics that CONTROL-M/EM collects are periodic. This means that
CONTROL-M can accumulate different sets of a job’s statistics for different periods.
The periods are defined using periodic calendars.
EXAMPLE
A particular job that runs daily takes about 10 minutes to run on most days. However, on
Fridays, this job usually takes about 40 minutes to run, due to the processing load on that day.
Collecting a single set of statistics would give an inaccurate view of required processing time
(too much time for most days; too little time for Fridays).
However, if you define two periods in a periodic calendar—one period having all days but
Friday, and the other period having only Fridays—CONTROL-M/EM will collect two
separate, but very useful and representative, sets of statistics for the job.
The first set of statistics will then be used in calculations for all days but Fridays, and the
second set will only be used for Friday’s calculations.
■ The Shout job processing parameter can be specified to issue a message if the
execution time that is required by a job varies from its average runtime by more
than a stated interval. This message can help highlight possible errors. (The Shout
parameter is described in the CONTROL-M Parameter Guide.)
■ The following CONTROL-M for z/OS features also use CONTROL-M job statistics
(for more information, see the INCONTROL for z/OS Administrator Guide):
— Critical path and expected Due Out calculation for Deadline scheduling
— Shouting when a job is not submitted by the calculated Due In time
— Shouting when a job runs longer then expected
EXAMPLE
According to the filtering criteria for the ABC ViewPoint, only jobs having an In prerequisite
condition called CondA are displayed.
The scheduling group in the XYZ Group scheduling table has CondA as an In prerequisite
condition, but none of the jobs in that Group scheduling table have A as a prerequisite
condition.
By modifying the appropriate system parameter, you can display the Group
scheduling table in the ViewPoint, even though no jobs will be displayed in the table.
■ For a file transfer activity, when the file is detected, the job continues to monitor
the size of the file. When the file reaches a specified minimum size and does not
increase in size for a specified period of time, the FileWatcher utility either
completes with a status of OK or executes a specified DO action. DO actions can
consist of adding or deleting conditions or executing a command.
■ For file creation, file size is ignored if a wildcard is specified as part of the filename
unless the mon_size_wildcard parameter is set to Y.
■ For file deletion, ctmfw must first detect the existence of the file before it can detect
its deletion.
ctmfw utility can also be run from the command line, or be invoked to detect either a
single file or multiple files.
User exits
A user exit is a user-defined procedure that can be used to modify certain information
before it is processed. At certain points in processing, a flat text file is produced
describing information that is to be passed to the next step in a procedure. This text
file can be modified by a user-defined exit script before it is passed on for processing.
CONTROL-M/Server user exits can be used to enforce site standards (for example,
file naming conventions or valid date formats), and to apply security definitions to
limit certain user’s actions. Exits can also be used to trigger other actions prior or
subsequent to execution of a CONTROL-M job.
EXAMPLE
The following steps illustrate what happens when a user exit is enabled:
2. The name of the text file is passed as a parameter to the user exit script.
3. The user exit script is run. This script is often used to modify the contents of the text file.
However, it can also be used to perform any other action (for example, to copy
information from the text file to another location).
User exits are implemented only if they have been enabled by setting the appropriate
configuration parameters. For a summary of available user exits, see Table 8 on
page 129.
Shell scripts
You can write shell scripts to be run as CONTROL-M/Server jobs on an agent
computer.
NOTE
This chapter assumes that the administrator is responsible for setting up the scheduling
environment. However, at your site, users might perform some or all of these tasks.
■ To perform these tasks online, follow the instructions that are provided in the
CONTROL-M User Guide.
■ To perform these tasks in batch you can use any combination of:
For details, see the CONTROL-M/Enterprise Manager API Developer Guide and the
CONTROL-M Utility Guide.
2 Make sure that scheduling tables are associated with relevant User Dailies. For
instructions, see the CONTROL-M User Guide.
3 Define resources and conditions. These ensure that CONTROL-M/Server does not
submit a job unless all required resources are available. For instructions on
defining resources and conditions, see the CONTROL-M User Guide.
A Display the CONTROL-M System Maintenance Utility Main Menu (ctmsys). For
instructions on displaying the menu, see “Using the CONTROL-M System
Maintenance Utility Main Menu” on page 47.
B In the CONTROL-M System Maintenance Utility Main Menu, enter the number
of the System Parameters option to display the CONTROL-M System
Parameters menu.
2. At the prompt, enter the value of the New Day Time preceded by a + (for
example, +08:00).
2. At the prompt, enter the value for the number of days to retain log
information (for example, 4).
2. At the prompt, enter the value for the number of days to retain log
information (for example, 2).
G To define that the New Day procedure should ignore (not cleanup) conditions,
enter 8 to toggle the Ignore New Day Conditions system parameter to Y.
WARNING
BMC Software recommends that you not change the default. If you are considering
changing it, see “Automatic prerequisite condition cleanup” on page 86 before making
your decision.
1. Edit the following file in the home directory of the CONTROL-M owner
account:
~<controlm_owner>/ctm_server/data/dbs_ignrcond.dat
2. Ensure the file contains the list of prefixes of prerequisite conditions, and/or
including masks, that should not be deleted by the New Day procedure.
Prerequisite condition names are case-sensitive; the mask character * and ?
are supported.
■ Define whether the New Day procedure should cleanup (delete) job runtime
statistics, by running the ctmruninf utility. (You can also run this utility
manually, and use the utility to display runtime statistics summaries.)
■ Define whether the New Day procedure should cleanup (delete) SYSOUT files
and unneeded user exit status files from CONTROL-M/Agent computers
(using the ctmagcln utility.)
— By default, the New Day procedure cleans up the SYSOUT and User exit
status file (the AGENTS_CLEANUP_IN_NEWDAY configuration parameter is
set to Y).
3 If any scheduling tables should be ordered by the New Day procedure (instead of
User Daily jobs), associate them with the SYSTEM User Daily as follows:
B In the Scheduling Table Manager window, select the scheduling table and click
(Table Details).
C In the Scheduling Table dialog box, specify SYSTEM (uppercase only) in the
User daily field.
NOTE
If you are defining a z/OS scheduling table, any value you specify in the User daily field
is for documentation purposes only. To actually assign the scheduling table to the New
Day procedure or to a specific User Daily job, follow the instructions in the
CONTROL-M for z/OS User Guide.
NOTE
If your site will not be using User Daily jobs, you should associate with the User Daily name
SYSTEM those scheduling tables that you want scanned by the New Day procedure.
■ Do you want any of your scheduling tables scanned by the New Day procedure. If
so, they should be associated with the SYSTEM User Daily name.
■ If you are using User Dailies other than SYSTEM, how many will you use and
according to what criteria will you associate the scheduling tables to them?
Departmental control issues should be factored in. Also, it can be more efficient to
define multiple User Daily jobs, each to be scheduled at a different time during the
day. This ensures that jobs are not loaded to the Active Jobs file until close to the
time that they will need to be submitted.
■ Do you want to put all User Daily jobs in only one scheduling table or in multiple
scheduling tables (each scheduling table containing User Daily jobs should be
associated with the SYSTEM User Daily name).
■ Do you want the scheduling tables that contain User Daily jobs to contain any
other types of jobs?
2 Create the scheduling tables that will contain User Daily jobs, and associate them
with the SYSTEM User Daily, as follows:
C In the Scheduling Table dialog box, fill in the details for the new scheduling
table, as follows:
1. Choose the CONTROL-M and specify a name for the scheduling table.
NOTE
Each scheduling table is associated with the platform of its CONTROL-M.
2. If you are creating a z/OS scheduling table, specify the library name.
NOTE
If you are defining a z/OS scheduling table, any value you specify in the User daily field
is for documentation purposes only. To actually assign the scheduling table to the New
Day procedure or to a specific User Daily job, follow the instructions in the
CONTROL-M for z/OS User Guide.
D Click OK, which saves the scheduling table in the CONTROL-M/EM database
(and displays the name in the Scheduling Table Manager window).
3 Associate all other scheduling tables with the appropriate User Daily name
according to your planned implementation, as follows:
A In the Scheduling Table Manager window, select the scheduling table and click
(Table Details).
B In the Scheduling Table dialog box, specify in the User daily field the name of
the User Daily job (1-10 characters, case sensitive) that should order the table.
4 To apply the changes to the table definition in the CONTROL-M database, upload
the table by it in the Scheduling Table Manager and clicking . If you are
prompted for confirmation, confirm.
5 In the scheduling table(s) you created to hold User Daily jobs, define the User
Daily jobs that will invoke the ctmudly utility. The utility is invoked by the ctmudly
name command, where name is the User Daily name associated with scheduling
tables.
You can have User Daily jobs invoke the ctmudly utility in either of the following
ways:
■ You can define the User Daily job as a Command-type job, and have it issue the
ctmudly name command. Such a User Daily job can only invoke the utility for a
single User Daily name.
■ You can define the User Daily job as a Job-type job, and have it run a script that
issues the ctmudly name command. The script can contain multiple instances of
the ctmudly name command. The name can be stated explicitly in the script file
or it can be specified using AutoEdit Assignment statements.
Be sure to define appropriate scheduling criteria for the User Daily jobs. It is often
useful to define User Daily jobs in such a way that they are scheduled to run
sequentially, not concurrently.
Usage of the ctmorder utility is described in the CONTROL-M Utility Guide. For
information on defining jobs, see the chapter on defining jobs in the CONTROL-M
User Guide.
You will have to examine the outputs and logs related to the jobs that were in process
to decide what to do, but the utility can reorder the jobs that did not yet run.
Run the ctmudchk utility for the affected User Daily to order jobs that were not
ordered because of the interruption.
Before ordering the job, ctmudchk verifies that a job is not already present in the
Active Jobs file.
The CONTROL-M Main Menu options enables you to access a variety of functions
and utilities used to maintain CONTROL-M/Server.
2 In the CONTROL-M Main menu, enter the number for the View NodeID details
option. This invokes the ctmgetcm utility interactively.
■ Application type—name of the application server (for example, SAP). You can
use a mask character to specify more than one application (for example, O* to
retrieve information from OAP_11, OAP_11I, and OS). Specify * to retrieve
information from all applications.
NOTE
CONTROL-M/CM information is updated only after ctmgetcm is run, or each time ctmgetcm
is reconfigured.
Example 1
Example 2
You want to update the CONTROL-M/Server database with new information for all
applications with prefix O on the CONTROL-M/Agent sahara computer (and view
the update information.
2 To define how the job version management should work, for each of the following
system parameters, double click the parameter, set its value appropriately, and
click Save.
To deactivate version history, set the parameter to 1 (keep current version only).
NOTE
The CMS deletes a job version only when the limits set in both the
VMVersionsNumberToKeep and the VMMaxDaysRetainCurrentJobsHistory system
parameters are exceeded.
■ VMAdditionalJobsRelateFields—If you use the same job name (or mem name, in
CONTROL-M for z/OS) for multiple jobs, use this field to identify additional
key fields that CONTROL-M/EM can use to distinguish between different jobs
with the same name /mem name, so as not to confuse or switch their job
histories. Default: <empty>. Recommended key words—some combination of:
MEM_LIB, DESCRIPTION, NODE_ID, OWNER, DAYS_CAL, WEEKS_CAL,
CONF_CAL, CMD_LINE, FROM_TIME, TO_TIME, ACTIVE_FROM,
ACTIVE_TILL. Example: VMAdditionalJobsRelateFields = "DESCRIPTION
TIME_FROM"
B In the Control Shell dialog box, enter the REFRESH_HISTORY command and
click Apply.
For instructions on defining, viewing and deleting these items, see the chapter on
identifying data center resources to CONTROL-Ms and the chapter on establishing
job dependencies across CONTROL-Ms, in the CONTROL-M User Guide.
Modify the values of the parameters listed in Table 6 on page 108. These parameters
are defined in the \$HOME\appl\ecs\resource\Defaults.rsc file. The format for
parameter settings in the Defaults.rsc file is:
EXAMPLE
To specify that global conditions can be distributed within 28 days from their original
condition date, excluding 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
In this example, global conditions with special dates 0101 and STAT are distributed even after
28 days from their original scheduling date passed. All other global conditions are not
distributed after 28 days passed.
EXAMPLE
To remove all date limitations on the distribution of global conditions:
namevalue * limit_gcs_distrib_activate 0
1 Set the SendSnmp parameter to one of the following values to indicate where the
alert data should be sent:
2 If data is to be sent to the SNMP trap, (the value of SendSnmp is either 0 or 2):
A Set the value of the SendSnmpActive parameter to 1, or the SNMP data will not
be generated and there will be nothing to send to the SNMP trap. (If data is not
going to the SNMP trap, the value of the SendSnmpActive parameter should be
0. Default.)
B Identify the SNMP host in the SnmpHost parameter. This parameter can contain
a single host name, or a list of host names separated by semi-colon (;) delimiters.
Specific ports can be set using a colon. For example, dhost1;jhost2;myhost3:2000
3 If data will be sent to a script, specify the full path name of the script that is
activated when an alert is generated in the SendaAlarmToScript parameter. (This
script is activated only if the value of SendSnmp is either 1 or 2.)
NOTE
If the file does not exist, a message is displayed on the gateway trace. If the gateway is
started with Trace Level 3 (most detailed), a message is displayed when the data is sent to
the script.
EXAMPLE
Example for testing SNMP traps when enabling this parameter:
On UNIX:
# !/bin/sh
echo $* > /tmp/snmptest.out
On Windows:
echo %1% %2% %3% %4% %5% > c:\snmptest.out
This section provides the following procedures related to time zone support:
The TimeZone.dat files contain a pre-supplied list of 3-character time zones and
their corresponding time offsets from Greenwich Mean Time (GMT). For example,
the Eastern Standard Time time zone appears as EST GMT -05:00.
NOTE
■ If you edit time zone definitions, ensure that you maintain the same time zone names in
CONTROL-M/Server and CONTROL-M/EM time zone files.
■ For Daylight Saving Time support, you can also modify the format of the time zone
definitions in the CONTROL-M/Server files (only). For more information, see “Editing
definitions to support Daylight Saving Time” on page 112.
2 Ensure that the CONTROL-M/Server on which time zone support is needed has a
time zone defined for it. For instructions, see “Defining a CONTROL-M/Server
(manual definition method)” on page 57.
3 In the job processing definition of each job that requires time zone support,
indicate the time zone according to which the job should run. For instructions, see
the job definition chapter of the CONTROL-M User Guide.
Ensuring correct time zones for jobs in the Active Jobs file
Jobs with specified time zones can be ordered as early as 48 hours before their actual
run, and they might remain in the Active Jobs file after their specified scheduling
date. Because these jobs must normally be ordered from the New Day procedure, an
unusually large number of jobs can accumulate in the Active Jobs file for a long
period of time, which can result in slower processing. Use this procedure to avoid the
problem.
NOTE
■ BMC Software recommends that you do not 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.
■ You must save newly defined jobs with specified time zones at least 48 hours before their
intended execution dates to ensure that they are ordered automatically by the appropriate
New Day Procedure or User Daily.
If the jobs must run “today,” you should order them manually (for example, by using the
ctmorder utility).
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 (by using the ctmudly utility) for each scheduling table that
was created in Step 1.
■ Specify a time for the User daily that corresponds to a time 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).
■ 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.
2 Change the relevant time zone definition so that it includes Daylight Saving Time
adjustments.
■ The first part of the entry (timeZone (GMT±hh:mm)) indicates the regular time
zone value (for example, CET (GMT+02:00) ).
■ The FROM and TO values indicate the time frame during which Daylight
Saving Time is in effect. (For example, FROM 01.03 01:59 TO 24.10 02:00)
■ The second GMT value (following the FROM and TO values) indicates the
Daylight Saving Time time-offset relative to GMT (for example, (GMT+03:00) ).
This syntax is reversed for the southern hemisphere. The FROM and TO keywords
specify the start and end settings for daylight saving to take effect.
EXAMPLE
Bill needs to create a new time zone label for Japan, where the time is nine hours later than
Greenwich Mean Time (GMT). Daylight Saving Time begins March 1 at 01:59 and ends
October 24 at 02:00. Bill uses the following entry to create the new label (JST):
EXAMPLE
Although time zone definitions in the northern hemisphere are set to summer Daylight
Saving Time, definitions in the southern hemisphere are set to winter. In Sydney, Australia,
winter time (GMT+09:00) is from March 25 at 03:00 until October 1 at 02:00. All other dates
are GMT+10:00 (summer time). The time label for Sydney is defined as follows:
3 If a relevant time zone contains several countries, some of which observe Daylight
Saving Time and some of which do not (or if they change the clock on different
days), add additional time zone definitions to cover the variations.
Be sure to update the relevant job processing definitions, using the appropriate
variations.
NOTE
If you delete a time zone from TimeZone.dat or modify a three-character name in that file,
be sure to change any job processing definitions that specify that time zone. Otherwise,
those job processing definitions will be invalid.
NOTE
You can also perform the functions listed in this section using the ctmnodegrp utility. For
details, see the CONTROL-M Utility Guide.
To view the list of node groups and their node ids for a CONTROL-M/Server
■ To add a node group, in the Node Group Management window, click (Add
Node Group).
4 Fill in, or modify as needed, the values in the node group properties dialog box:
A Specify the node group name and select the application type. (Select the OS
application type if the node group is not for third-party applications.)
■ To add node IDs to the node group, select the node IDs in the Disassociated
Node ID field and click the right arrow to move them to the Associated Node
ID field.
■ To add and associate a node ID that is not yet defined in the enterprise,
specify the name (maximum: 50 characters) in the New Node ID field and
click the right arrow.
■ To remove (disassociate) node IDs from the node group, select the node IDs
in the Associated Node ID field and click the left arrow to move them to the
Disassociated Node ID field.
5 When done, click OK. CONTROL-M is immediately updated with the changes.
All node IDs are disassociated from the node group and the node group is deleted.
3 In the tree, select the node ID and click (Disassociate Node ID).
NOTE
■ If you disassociate the last remaining node ID from a node group, the node group is
also deleted.
■ You can disassociate all node IDs from a node group by deleting the node group. For
instructions, see “To delete a node group” on page 114
In the Node ID/Group field in the Execution tab, select the group. (If the groups do not
appear in the selection list, click Load; then select the group.)
For instructions on defining job processing definitions, see the CONTROL-M User
Guide.
You can create any number of Shout Destination tables, but only one of them can be
designated as the active Shout Destination table at any given time. By changing the
designation of the active table, you can change the actual recipients of messages sent
to specific logical recipients.
■ “To display the Shout Destination Tables menu of the ctmsys utility” on page 116
■ “To create or modify a shout destination table” on page 117
■ “To change the active shout destination table” on page 119
■ “To list existing shout destination tables” on page 120
■ “To delete an existing shout destination table by name” on page 120
1 Display the CONTROL-M System Maintenance Utility Main Menu (ctmsys). For
instructions on displaying the menu, see “Using the CONTROL-M System
Maintenance Utility Main Menu” on page 47.
2 In the CONTROL-M System Maintenance Utility Main Menu, enter the number of
the Shout Destination Tables option.
Enter option:
2 Enter the name of the table to be created or modified (or press <Enter> to accept
the default).
(If the name you specify is not the name of an existing Shout Destination table, a
new table will be created with the specified name.)
A display similar to the following is displayed. For an existing table, the display
lists the defined destinations.
Enter option:
Table 7 describes the fields and valid values of the Shout Destination table.
A Specify n.
D At the Logical Name prompt, specify the logical name for this destination.
Physical Name:
Dest Type:
Address Type:
Physical Name:
B Specify a new physical name for the entry. The table is redisplayed with the
modified entry.
NIGHT_SHIFT
Enter name of table to make active or q to quit [SYSTEM]:
2 Specify the name of the table to set as the active Shout Destination table.
The active Shout Destination table is changed immediately, affecting Shout and
Do Shout operations performed by CONTROL-M.
NOTE
To specify the active Shout Destination table using a job, run the ctmshtb utility, described in
the CONTROL-M Utility Guide.
NOTE
It is not possible to delete the active Shout Destination table.
ctmshtb <table>
TIP
To automate the process of making different Shout Destination Tables current at different
times (for example to automatically change between a Dayshift and Nightshift Shout
Destination Table), define CONTROL-M jobs to execute this utility at the required times.
■ ignores those job run instances with the 2 highest and 2 lowest elapsed run times
■ retains a maximum sample of 20 periodic statistics per job
■ retains periodic statistics for 100 days
■ performs purge of those periodic statistics whose retention period has passed
every 30 minutes.
1 In the CONTROL-M Configuration Manager, choose Tools => System Parameters =>
CONTROL-M/EM System Parameters to display the CONTROL-M/EM System
Parameters window.
2 To modify periodic statistic cleanup defaults, double click the system parameter
you are modifying, set its value appropriately, and click Save. Both of the following
parameters are CONTROL-M/EM system parameters of the CMS type.
2 In the CONTROL-M System Maintenance Utility main menu, enter the number for
the System Parameters option.
A If the Statistics parameter is not displayed, enter N (Next) to display the next
System Parameters page, until the Statistics parameter is displayed.
B If the Statistics parameter is set to Y, enter C (Cancel) to exit the page without
making changes.
2 In the CONTROL-M Main menu, enter the number for the Parameter Customization
menu option, which is used to maintain various groups of CONTROL-M/Server
parameters.
3 In the Parameter customization menu, enter the number for the Advanced
Communication and Operational Parameter option.
5 Enter one of the following values, as appropriate, for the Statistics Mode:
■ To compile statistics for each CONTROL-M Job Name, Scheduling table, and
Node ID where the job was submitted, enter JOBNAME.
■ To compile statistics for each CONTROL-M Mem Name/Mem Lib and Node
ID, enter MEMNAME (default).
TIP
BMC Software recommends that you define a CONTROL-M job to run the ctmjsa utility on a
daily basis.
A partial cleanup of the Statistical Details table is performed by the New Day
procedure.
■ The ctmruninf utility displays and deletes data from the Statistical Details table.
■ The ctmstats utility displays and deletes data from the Statistical Summary table.
For information regarding usage of these utilities, see the utility descriptions in the
CONTROL-M Utility Guide.
To override the default so that “empty” Group scheduling tables are displayed
for all users
(To filter out the “empty” group scheduling tables, reset the ViewpointPolicy system
parameter to its default value: SELECT_JOBS.)
NOTE
If ViewpointPolicy is set to SELECT_JOBS_AND_SG, users can still hide any empty group
scheduling tables displayed in the ViewPoint by choosing the Hide Empty Scheduling
Groups option from the View menu in CONTROL-M/EM.
To set whether empty group scheduling tables are displayed for specific users
3 In the Component Name field, specify the user name for which different behavior
is required.
NOTE
For other system parameters, Comp. Name identifies the data center. For the
ViewpointPolicy system parameter, Comp. Name indicates the user names of the exceptions.
4 Ensure that the Value field is defined as required for this specific user, and click
Save.
NOTE
You can override this default file for any GUI Server by creating a
pin_collection.{Logical_Name}.ini file in the same ini folder or directory..
NOTE
Ensure that each collection name is specified in the pin_collection.{Logical_Name}.ini file
on a separate line.
2 After being configured, the ctl and rsi utilities can be used to dynamically modify
which collections are pinned (for more information, see the CONTROL-M Utility
Guide). When using these utilities, the following commands are relevant:
NOTE
The CPIN and CUNPIN commands only affect the currently running GUI server. If you
wants your settings to remain after the server ends its current run, you should specify
whichever is applicable of these commands in the pin_collection.{Logical_Name}.ini file.
As a service, ctmfw takes its parameters (rules) during startup from the rull.dat file
whose full path name is specified in <CONTROL-M/Agent>\data\ctmfw.cfg.
To change one or more rules, change the contents of the rull.dat file or specify the full
path name of a different file.
NOTE
The rull.dat file provided with CONTROL-M/Agent is a sample file and should be changed to
reflect your requirements.
The full path name to the ctmfw.cfg configuration file must be specified under the
following Microsoft Windows registry key that is generated automatically by the
installation script:
HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\
CONTROL-M/FileWatcher\SYSPRM\File Watcher
Configuration File
<CONTROL-M/Agent_install_directory>\DATA\ctmfw.cfg
NOTE
BMC Software recommends that this default value not be changed.
The variable <ruleFileName> is the full path name of a rule file containing the File
Watcher rules. The following is a sample rule file.
Network Resources
The FileWatcher service running under the local system account cannot detect
network resources (files located on remote systems).
If you want the FileWatcher to detect network resources, configure the FileWatcher
Service to run under a regular user account.
When running as a service, ctmfw generates an execution log file. This file is saved in
the CONTROL-M/Agent proclog directory under the following name:
U_CTMFW_<process_id>.log
By default, logs in the proclog directory are retained for 3 days. If the “maximum
days to retain SYSOUT” parameter is set to a number higher than 3, logs are retained
for the number of days specified in that parameter.
NOTE
A special category of user exits can be defined for the Watchdog facility. For more
information, see “Watchdog facility exits” on page 528.
B Where relevant, enable specific user exits by setting the value of the relevant
CTM_PRM_ENABLE_UEnnn configuration parameters (where nnn is the
numeric part of the user exit name, valid values 101-106) to Y. (To disable specific
user exits, set the value to N.) Default: N.
3 In the user exit directory, define the scripts for the implemented user exits and
assign the scripts default file names in the format:
■ For Unix: ctm_exitnnn.sh, (where nnn is the numeric part of the user exit name,
valid values 101-106).
■ For Windows: ctm_exitnnn.bat, (where nnn is the numeric part of the user exit
name, valid values 101-106).
BMC Software recommends that you run each script manually to validate the script
syntax before running the script under CONTROL-M/Server.
#! <shell path>
NOTE
The command line of command type jobs must be in Bourne shell syntax only.
Note: In the SYSOUT file, the command arguments contain the value of the
variable and not the variable name.
Each command is prefixed by the '+' sign. This sign is later used during an
On statement post-processing phase of the jobs output to distinguish
between the different commands and their output.
-v This parameter causes CONTROL-M/Agent to parse the original script to a
temporary script. The script commands are appended with an identifying
string. This temporary script is then executed, where the -v switch causes
the shell to print each command before its output. The added identifying
string is later used during an On statement post-processing phase of the
job's output to distinguish between commands and their output.
n This CONTROL-M/Agent-specific flag is used to indicate that the script
should be executed as is and no commands will be included in the job’s
output. As a result no On-statement processing is possible.
For more information about the different flags, see the example on page 132.
NOTE
Arguments specified after the shell name are ignored by CONTROL-M/Agent with the
following exception: -x is supported when running a script under the Bourne shell or Korn
shell. If -x is specified as an argument after the shell name, it overrides any option set in the
CTM_PRM_SH_FLAGS or CTM_PRM_KSH_FLAGS parameters.
Example
The following script uses the app, dbadmin, and stx111 parameters. The app
parameter sets an environment variable. The script uses the dbadmin and stx111
parameters to call a utility that performs an action. The output of the job varies
depending on the shell flag.
EXAMPLE
#!/bin/sh
DBNAME=$1
export DBNAME
dbrefresh -U $2 -P $3
exit $?
■ If the -x flag was set when running the sample script, the job produces the
following output.
DBNAME=app
+ export DBNAME
+ dbrefresh -U dbadmin -P stx111
DB refreshed
+ exit 0
■ If the -v flag was set when running the sample script, the job produces the
following output.
#! /bin/sh -v
CTM_RSVD=
CTM_RSVD_START=
CTM_RSVD_END=
CTM0='/home2/ag620/refreshDB.sh'
CTM00=$0
DBNAME=$1 $CTM_RSVD
export DBNAME $CTM_RSVD
dbrefresh -U $2 -P $3 $CTM_RSVD
DB refreshed
exit $? $CTM_RSVD
■ If the n flag was set when running the sample script, the job produces the following
output.
DB refreshed
2 Specify the full path under which REXX is installed in the first line of the REXX
script.
EXAMPLE
#!/usr/local/bin/rxx
During the logon process, the user environment is set according to the shell type
specified in /etc/passwd.
■ When a csh or tcsh script is run, the .cshrc file of the job owner is executed as part
of the startup process for the script.
■ For all other shell types, the .profile file of the job owner is executed as part of the
startup process for the script.
NOTE
The .login file is not executed as part of the startup process.
1 When CONTROL-M executes job scripts, there is no terminal associated with the
job. Therefore, do not use commands in a script that query terminal characteristics
or take input from a terminal.
2 The shell script startup process sets the environment variables that will be
available when the script is run. Use the # ! statement to indicate the shell under
which the script is intended to run.
When writing scripts that access files, specify the file name in the script with a full
path or with a path relative to the home directory of the job owner.
Depending on the shell used, CONTROL-M/Agent does not process certain types
of script statements for comparison with the text specified in the Stmt
subparameter of the On Statement/Code parameter.
Therefore, in the Stmt subparameter, do not specify text contained in the following
script statements:
— For a Bourne shell, text in if, for, while, and case statements.
— For a csh shell, text in if statements.
EXAMPLE
No part of the following script line should be used in the Stmt subparameter of the On
Statement/Code parameter:
if [ ‘baseline’ - eq 0 ]; then
■ Continuation Lines
CONTROL-M/Agent does not process continuation lines for comparison with text
specified in the Stmt subparameter of the On Statement/Code parameter.
Therefore, in the Stmt subparameter do not specify text that occurs after the first
132 characters of a script statement.
■ HERE Documents
The term HERE document refers to lines of text in a script that are passed to a
command as input, but are not passed to the shell.
EXAMPLE
In the following script, line 1 and line 2 of a HERE document are passed to the specified cat
command:
cat > /tmp/junk << EOF_EOF
line 1
line 2
EOF_EOF
echo "DONE"
For more information about the On Statement/Code parameter, see the CONTROL-M
Parameter Guide. Job processing parameters are described in the CONTROL-M User
Guide.
COMPSTAT=<value>
EXAMPLE
Assume that a script exits with an exit code of 5.
This condition can be detected by defining the following On Statement/Code parameters:
Stmt: *
Code: COMPSTAT=5
When a script runs as a CONTROL-M/Server job using the –v flag (see Specifying the
shell type), it is parsed into a temporary script. In this case, any reference to $0 in the
script is resolved to the temporary script name rather than the original script name,
and the name of the original script is saved in the CTM0 variable. This differentiates
between a script run from the command line run and a script run from a
CONTROL-M/Server job.
To ensure that the $0 variable resolves to the original name as run from the command
line, not the temporary script name, set the Translate_$0 flag using the CONTROL-M
Configuration Manager. For more information, see “Modifying CONTROL-M/Agent
system parameters” on page 409.
The following example shows the dollar0.sh script, which is supposed to print out the
script name.
EXAMPLE
#!/bin/sh
echo $0
■ When the script runs as part of a CONTROL-M/Server job using the -v flag, the
name of the temporary script is printed.
#! /bin/sh -v
CTM_RSVD=
CTM_RSVD_START=
CTM_RSVD_END=
CTM0='/home/ag620/dollar0.sh'
CTM00=$0
echo $0 $CTM_RSVD
/tmp/ctm/CM_SH.11939
■ When the script runs in a CONTROL-M/Server job using the -v flag and the
Translate_$0 flag is set, the name of the original script is printed.
#! /bin/sh -v
CTM_RSVD=
CTM_RSVD_START=
CTM_RSVD_END=
CTM0='/home/ag620/dollar0.sh'
CTM00=$0
echo $CTM0 $CTM_RSVD
/home/ag6220/dollar0.sh
To correctly implement scripts for Windows, you need to consider and handle the
following factors:
This step ensures that job script statements will be written to the SYSOUT file.
These characters and embedded spaces should not be used inside the prompt text
string.
The following items describe how the On Statement/Code job processing parameter
interprets script lines:
■ Continuation Lines
CONTROL-M/Server does not process continuation lines for comparison with text
in a Stmt subparameter.
Therefore, do not specify script continuation line text in the Stmt subparameter.
Therefore, in subparameter Stmt, do not specify text that comes after the first 512
characters of a script statement.
For more information about the On Statement/Code parameter, see Chapter 7 of the
CONTROL-M Parameter Guide. Job processing parameters are described in Chapter 5
of the CONTROL-M User Guide.
COMPSTAT=<value>
Example
In this example, a REXX script exits with an exit code of 5, as shown below:
exit 5
Stmt: *
Code: COMPSTAT=5
If this directory is not defined as part of the operating system search path, specify the
full path when using one of these utilities.
_exit utility
This utility is similar to the UNIX exit built-in shell function.
Format
Examples
_sleep utility
This utility is similar to the UNIX sleep built-in shell function.
Format
NOTE
If _sleep is specified, you must specify a whole integer number.
Example
The owners of the jobs do not have to be logged on to provide the drive mappings for
the scripts.
Example
Two job owners, A and B, are executing ScriptA.bat and ScriptB.bat, respectively.
Owner A has drive M mapped to \\nt-A\share. Owner B has drive M mapped to
\\nt-B\share.
Table 12 describes these scripts before and after executing the CTMBAT2UNC utility.
NOTE
Under the current version of Microsoft Windows, command interpreters do not change a
current directory to a UNC path (for example, cd \\nt-A\share\jobs will not be
executed).
BMC Software recommends that you review the translated script after invoking the
ctmbat2unc utility.
availability
This part presents the following topics:
Chapter 4
Introduction to implementing CONTROL-M security . . . . . . . . . . . . . . . . . . . . . . 147
Chapter 5
Setting up CONTROL-M authentication security . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Chapter 6
Setting up CONTROL-M authorization security . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Chapter 7
Implementing CONTROL-M security auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Chapter 8
Setting up CONTROL-M firewall security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Chapter 9
Configuring CONTROL-M for high availability . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
4
Introduction to implementing
4
CONTROL-M security
This chapter presents the following topics:
■ Authorization security checks whether the user is authorized to access the requested
components and to perform the requested actions.
■ Auditing security flags problematic user actions and threats to the system.
With the exception of firewall security, the different types of security are
implemented in an integrated flow that encompasses CONTROL-M/EM,
CONTROL-M/Server, and CONTROL-M/Agent.
Security flow
1. CONTROL-M requests a user password to authenticate the user.
NOTE
If you use CONTROL-M at a z/OS site, CONTROL-M security also interacts with the
external security tools that are used at the site (such as RACF, ACF2/SAF, and TOP
SECRET).
5. Auditing security watches for and flags any problematic user actions or prohibited
attempts to access CONTROL-M components and scheduling entities.
NOTE
Firewall security is implemented for communication between components and, as such, is
outside this flow.
5
Setting up CONTROL-M
5
authentication security
Conceptual overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Password requirements and expiration warnings . . . . . . . . . . . . . . . . . . . . . . . . . 152
Administrator passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Setting the authentication method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Authenticating CONTROL-M/EM users against an LDAP or Active Directory
server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Implementing external plug-in authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Defining password requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Refreshing password-related system parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 160
Setting allowable password lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Setting password complexity rules (required character types) . . . . . . . . . . . . . . 161
Setting password reuse limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Implementing password expiration policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Implementing password policy for all users using the set_pwd_def_lifetime
script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Setting automatic account locking after consecutive failed logon attempts. . . . 165
Unlocking multiple accounts with the unlock_user script . . . . . . . . . . . . . . . . . . 166
Defining users and their authentication criteria to CONTROL-M/EM . . . . . . . . . . 166
Manually modifying a user’s password criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Changing the DBO password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Defining a CONTROL-M/Agent account (Windows only) . . . . . . . . . . . . . . . . . . . . 170
Defining job owner and authentication settings for CONTROL-M/Agents and
remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Conceptual overview
Figure 14 highlights the basic recommended workflow for setting up CONTROL-M
authentication security. This overview section explains concepts that are related to
the workflow.
For specific tasks that correspond to each phase of the workflow, see Table 13 on
page 154. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
Set the
authentication method
page 154
Define password
requirements
page 160
Define CONTROL-M/EM
user authentication
page 166
Manually modify a
user’s password criteria
page 169
page 173
Authentication methods
As part of the logon process, CONTROL-M/EM client components send user name
and password information to CONTROL-M/EM server components for
authentication. User passwords can be validated internally or externally.
Authentication security and data privacy and protection can be enhanced by using
Secure Sockets Layer (SSL) security.
Internal authentication
Internal authentication is performed within the product. It validates a client’s user
name and password against information stored in the server. The method of choice
for internal authentication is challenge-response.
External authentication
Some sites, especially those using centralized authentication mechanism, prefer to
perform their own authentication. CONTROL-M/EM allows those sites to implement
a plug-in that replaces CONTROL-M/EM authentication with their own
implementation.
■ LDAP/Active Directory
When using LDAP or Active Directory, you can connect in Secured Socket Layer
(SSL) mode. Doing so requires that you configure your LDAP or Active Directory
to work with SSL. (For details, see the CONTROL-M SSL Guide.)
■ Client–server authentication
Using certificates on the client and server side, SSL authenticates the connection
between the client and server components
By requiring keys that are not available to unauthorized users, SSL also protects
the system from deliberate data corruption.
SSL security and its implementation are described in the CONTROL-M SSL Guide.
■ password reuse rules—the number of password changes that a user must perform
before reusing a password.
— update this expiration value on a user-by-user basis using the General panel of
the Authorization window.
— run a script (set_pwd_def_lifetime) to determine how many days remain until
password expiration - which will then issue the password expiration warning if
necessary.
■ password locking for failed attempts—after how many failed user access attempts
should a user be locked out and prevented from trying to logon again.
Administrator passwords
During CONTROL-M/EM installation, a CONTROL-M administrator is defined with
full administrator privileges, and a DBO (Database owner) is defined with full DBO
privileges. They are assigned the same default passwords. You can assign these
entities to the same, or different people, and you can change the passwords
accordingly.
You can change the CONTROL-M/EM administrator password as you would for any
CONTROL-M/EM user. For instructions on changing the DBO password, see
“Changing the DBO password” on page 170.
3 Prepare the system for External authentication by setting the value of the
DirectoryServiceAuth system parameter to PrepExt.
At this stage another authentication method is still in use allowing you to complete
CONTROL-M/EM user definitions for external authentication.
4 Define the LDAP or Active Directory parameters for the CONTROL-M/EM users,
as follows:
B In the Users tab of the Authorizations window, select a user from the list and
click Update or click New to create a new user definition.
C Enter the user name and domain as they are defined in the LDAP or Active
Directory server in the LDAP Directory Service User and Domain Name field.
In the following example, the user em belongs to a group called adminuser, which
resides in the domain admins.bmc.com.
EXAMPLE
[email protected]
EXAMPLE
em.adminuser/[email protected]
NOTE
If any part of the user definition in LDAP or Active Directory includes @, /, or . characters,
these characters must be preceded by a backslash.
Examples:
■ If the group name in LDAP or Active Directory is admin/user, you must define it in
CONTROL-M/EM as em.admin\/user/[email protected].
■ If the user name in LDAP or Active Directory includes initials, for example EU, you
must define it in CONTROL-M/EM as emuser
EU\..adminuser/[email protected].
5 Define at least one emergency user, if you have not already done so. (Optional
step.)
You define an emergency user as you would any user (see step 4), except that you
must also do the following in the General tab of the User Authorizations window:
■ Select the Emergency User check box. (This check box is displayed only when
external authorization is enabled.)
6 Set the value for the PasswordEncode system parameter to 0 (clear text mode), so
that CONTROL-M/EM does not encrypt the password. (External applications,
such as LDAP or Active Directory, cannot read passwords if they are encrypted by
CONTROL-M/EM.)
NOTE
When the DirectoryServiceAuth system parameter is set to On, the AuthenticationMethod
system parameter is ignored.
8 To use the SSL protocol to communicate with LDAP or Active Directory, configure
your LDAP or Active Directory to work with SSL. For instructions, see the
CONTROL-M SSL Guide. (You can perform this optional step at any time. If you
perform it later, ensure that you rerun step 9.)
9 Refresh the servers with the changes. For instructions, see “Refreshing LDAP or
Active Directory system parameters” on page 157.
3 Prepare the system for internal authentication by setting the value of the
DirectoryServiceAuth system parameter to PrepInt.
4 Apply passwords for all CONTROL-M/EM users (in the General tab of the User
Authorization window).
7 Refresh the servers with the changes. For instructions, see “Refreshing LDAP or
Active Directory system parameters” on page 157.
NOTE
You should apply changes in any of the following scenarios:
To apply the changes to those servers, run the following refresh commands.
■ To apply your changes to the GUI Server, use the following command:
■ To apply your changes to the Global Alerts Server, use the following command:
■ To apply your changes to the Configuration Manager server, use the following
command:
The function definitions and related source and header files are contained in the
Plug-in SDK (Software Development Kit) – plugin-sdk.zip – in the tools folder on
the product CD. The following files are contained in plugin-sdk.zip:
The plug-in implementation authenticates the user and password and returns one
of the following return codes:
Warning and information messages can be written to the buffer and displayed in
the CONTROL-M/EM GUI.
NOTE
If the external authentication plug-in fails to load (for example, due to an incorrect system
parameter value, an incorrect interface version, or a general loading error), default internal
authentication is used. The CONTROL-M/EM Server diagnostic log identifies the
authentication method used by the server. If the plug-in fails to load, this log contains an
error message.
You can also define an emergency user for situations where the external authentication is
not available. For more information about the emergency user, see “Defining users and
their authentication criteria to CONTROL-M/EM” on page 166.
CONTROL-M/EM is provided with sample plug-in code that can be used and
adapted when you write your site’s plug in. The following is a list of supported
platforms and compilers used to build the sample plug-in code. BMC Software
recommends that you use the same compiler versions.
— <name>—the logical name (not the actual file name) of the external plug-in to
be used for authentication. The CONTROL-M/EM GUI Server, Global Alerts
Server, and Configuration Manager Server will load the plug-in and uses it to
authenticate the user name and password.
NOTE
To authenticate a user in an external system, the same user name must exist in
CONTROL-M/EM. The first stage of authentication checks that the user exists in
CONTROL-M/EM. If the user exists, the user's password is authenticated externally.
NOTE
Because the Global Alerts Server (GAS), the GUI Server (GSR), and the Configuration
Manager Server (CMS) handle security settings separately, if you modify certain
password-related system parameters while these servers are running, be sure to perform a
refresh to those servers. For instructions, see “Refreshing password-related system
parameters” on page 160
■ PasswordExpirationOnOff
■ PasswordLifetimeDays
■ WarningPasswordExpirationDays
■ NumberOfPasswordReplacements
■ NumberOfFailedLogins
■ LockAccountForMinutes
■ PasswordHistoryOnOff
■ To apply your changes to the GUI Server, use the following command:
■ To apply your changes to the Global Alerts Server, use the following command:
■ To apply your changes to the Configuration Manager server, use the following
command:
3 When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
By default, all four types of characters must be satisfied (the default value is:
PWD_DIGIT PWD_UPPER PWD_LOW PWD_NON_LETDIG).
3 When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
To set the number of times a user must change a password before reusing a
password
3 When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
■ Before password expiration—if the password has not yet expired, the following
warning message is generated:
Your password will expire in n days.
— When a user runs cli or XML utilities, this warning is returned and the process
continues.
■ After password expiration—if the password has expired, the following message is
generated:
Your password has expired. Please change the password.
— When a user attempts to run XML utilities or the cli utility, this message is
returned and the process exits.
3 Manually define the exceptions for these users to whom the site-wide expiration
limits should not apply. For instructions, see “Manually modifying a user’s
password criteria” on page 169.
NOTE
Warnings are issued only when certain utilities or scripts are run or a successful logon is
performed.
6 When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
By running the set_pwd_def_lifetime script, you can use the value defined in the
PasswordLifetimeDays system parameter to compute and reset the password
expiration date for each CONTROL-M/EM user (excluding BMC Batch Impact
Manager users).
This script performs the following, for each user, in the General tab of the User
Authorization window:
■ sets the value of Password will expire every n days to the value set in the
PasswordLifetimeDays system parameter. (If a user’s Password never expires
option was selected, the script clears this option.)
■ sets the user’s password expiration date to the date obtained by adding that
number of days to the current date.
■ On UNIX, select Users Administration Menu => Set Password Default Lifetime
from the Root menu.
2 If the script prompts you for the DBO user name and password, supply them. (This
happens if you do not include them in the command line.)
NOTE
■ A value of 0 (default) in the LockAccountForMinutes system parameter means that the
account will remain locked until it is manually unlocked by the administrator.
3 When you have finished changing all password-related parameters, refresh the
relevant servers. For instructions, see “Refreshing password-related system
parameters” on page 160.
■ On UNIX, select Users Administration Menu => Unlock User from the Root menu.
2 If the script prompts you for the -U and -P DBO values, supply them. (This
happens if you do not include them in the command line.)
When creating users, you can create them “from scratch,” or you can copy an existing
user (saving the details of an existing user under a new name).
NOTE
When you copy an existing user, the groups to which the existing user belongs are associated
with the new user, but the existing password is not copied. You can define the password for
the new user by using the General tab of the User Authorizations window.
2 To create a new user either from scratch or by copying the details of an existing
user, do the following in the Users tab of the Authorizations window
A. Click New.
B. In the New Name dialog box, enter the name of the user, and click OK.
B. Click Copy.
C. In the New Name dialog box, enter the name of the user and click OK.
3 In the Users tab of the Authorizations window, choose the user and click Update.
4 In the General tab of the User Authorization window, define the logon
authentication data for the user. Most information that you must provide in the
fields of the tab is intuitive.
Use the following pointers to help you when you define this information:
■ To identify the user to the system, specify a unique name without blanks in the
User Name field. You can include blanks when you identify the full user name
in the Full Name field.
EXAMPLE
To identify the user
■ If you enable external authentication (for details, see page 151 and page 158), an
Emergency User check box is displayed. Select this box if you want to provide
the user with the ability to circumvent external authentication.
■ If you select this box, you must specify a password in the Password and
Confirm Password fields.
■ The Password field is disabled when you use Active Directory authentication.
For more information, see “Authentication methods” on page 151.
■ If you do not want automatic password expiration, click Password Never Expires.
To force the user to change the password the next time the user logs on, click
User must change password at next login. For these changes to take effect, set the
appropriate system parameters. For more information, see “Implementing
password expiration policy” on page 163.
NOTE
By default (UserChangePassword system parameter = 1), all users can change their own
password using the Tools=> Change Password option.
To enable only users having Full or Update level access to the Authorizations privilege to
change their passwords using the Tools=> Change Password option, set the
UserChangePassword system parameter to 0. Generally, this value serves to restrict
password change authorization to CONTROL-M/EM administrators.
To delete a user
2 In the Users tab of the Authorizations window, choose the user and click Delete.
■ changing passwords
■ changing password expiration dates
■ locking and unlock a user’s account
2 In the Users tab of the Authorizations window, choose the user and click Update.
3 In the General panel of the User Authorizations window, perform the following as
needed:
A To modify the password value, type in the new password in both the Password
and Confirm Password fields.
NOTE
If a CONTROL-M/EM administrator uses the Authorization facility to set a password,
the password complexity, length, and reuse requirements are ignored.
B To modify the password expiration period, in the Password expiration area, set
appropriate value to the password management parameters.
C To lock or unlock the user’s account choose (or unselect) Lock account.
4 Click OK.
NOTE
The following step must be run on each computer on which CONTROL-M/EM is installed,
except those with only client components that do not have the Reporting Facility installed.
NOTE
<EMHomedir> here indicates the directory in which CONTROL-M was installed.
NOTE
This user name and encrypted password are stored in the mcs.ini file in the
EMHome/ini/ directory on every computer on which CONTROL-M/EM server components
are installed.
For more information on the cryptocli utility, see the CONTROL-M Utility Guide.
■ If the owner of any jobs run by CONTROL-M/Agent has a “Roaming Profile.” For
more information, see “Support for a Roaming Profile” on page 172.
■ If WMI jobs will run on remote hosts
If the job must access the network, the owner of the job must be a domain user with
access rights to the network
■ If the Logon As User parameter is set to Y, the owner of the job will be the owner
specified in the CONTROL-M job processing definition.
■ If Logon As User is set to N, the Listener Service should run from a user domain
account and the owner of the service will be an owner of the job.
NOTE
(Windows Vista or Windows 2008 only) If the Logon As User parameter is set to Y, the Agent
service should be set to This Account.
1 In the Services window, right-click on the relevant agent service and select
Properties.
2 In the Log On tab in the Properties window, select Local System account.
The service will run in the administrative group and in the native system account
environment. By installation default, the following options are selected:
These options enable the Listener service to open windows in the Microsoft Windows
desktop. However, the Local System Account cannot access files across a network
and cannot send a Shout message to an e-mail destination.
1 In the Services window, right-click on the relevant agent service and select
Properties.
3 In the This Account text box, specify account information. The account must be a
member of the Local Administrative Group. The format is <Domain>\<User>.
NOTE
The administrator selected as part of This Account, must have the following permissions in
the Local Security Settings window:
■ The profile must reside on the network. If the network path includes the
environment variable, CONTROL-M/Agent expands the path and loads the User
Profile from the expanded path.
■ After loading the user profile, CONTROL-M/Agent sets all environment variables
from the roaming profile:
NOTE
To eliminate the need to assign user rights to every job owner on every Microsoft Windows
computer running CONTROL-M/Agent, BMC Software recommends that you define a
domain-level group for all job owners. You can name this group CONTROL-M Job Owners.
Assign network access rights and the Logon as a batch job user right to this group.
NOTE
For CONTROL-M/Agent, job owners can be defined only for owners of jobs running on
CONTROL-M/Agent on Windows. These owners are relevant only when Logon_as_user=Y.
NOTE
If you are using the Key Authentication for the SSH connection method, you will be required
to provide Key name and Passphrase authentication parameters. You generate these values
using the CONTROL-M/Server ctmkeygen utility (described in the CONTROL-M Utility
Guide). Be sure you have these values before performing this procedure.
To filter the list, click Manual Load, enter the filter criteria at the bottom of the
dialog box, and click Load. You can specify asterisks as wildcards in the filtering
criteria.
B Specify the owner and the host (Node ID). To make this owner the default
owner of all agents or remote hosts, specify <All> in the Host field. Ensure that
you include the angle brackets when you specify <All>.
NOTE
If the connection method will be WMI, the job owner must belong to the local
Administrator group on the agent or remote host.
■ For WMI connections, click Use Password Authentication, and then fill in the
user name and password, and confirm the password. The user name should
include the domain.
— click Use Password Authentication and fill in and confirm the password
— click Use Key Authentication (SSH only), and fill in the Key Name and
Passphrase values generated by the CONTROL-M/Server ctmkeygen utility.
(For details about the ctmkeygen utility, see the utility description in the
CONTROL-M Utility Guide.)
D Click Test to check that your settings are correct and workable.
E Click OK.
■ To modify an owner-host combination, delete the owner-host line, and then add
new owner-host definition
4 Click Test to check that your settings are correct and workable.
5 Click Close.
6
Setting up CONTROL-M
6
authorization security
Conceptual overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
CONTROL-M/EM authorization security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
CONTROL-M/Server authorization security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
CONTROL-M/Agent security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Implementing CONTROL-M/EM authorization security. . . . . . . . . . . . . . . . . . . . . . 184
Creating and deleting group security definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 185
Defining which group profiles apply to a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Defining or modifying user or group authorization details . . . . . . . . . . . . . . . . . 186
Ensuring owner verification during New Day processing job ordering. . . . . . . 197
Authorizing non-administrators to manage application accounts . . . . . . . . . . . 200
Enabling passage of global conditions from GCS to CONTROL-M/Servers . . . . . . 202
Changing the default Global Conditions Server user name . . . . . . . . . . . . . . . . . 202
Implementing CONTROL-M/Server authorization security . . . . . . . . . . . . . . . . . . . 202
Adding, deleting and modifying users and groups . . . . . . . . . . . . . . . . . . . . . . . . 204
Assigning authorizations to users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Activating CONTROL-M/Server security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Implementing CONTROL-M/Agent and remote host authorization security . . . . 207
Implementing CONTROL-M/Agent job owner security (Windows only) . . . . 207
Implementing CONTROL-M/Agent remote host security . . . . . . . . . . . . . . . . . 208
Authorizing which CONTROL-M/Server utilities a CONTROL-M/Agent can
request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Conceptual overview
With CONTROL-M, you can establish a high degree of data security without
adversely affecting production.
Authorization security defines which data users are allowed to view and which
operations (including data modification) that users can perform. At the
CONTROL-M/EM and CONTROL-M/Server levels, you can define security for
individual users and for groups.
A group is an authorization profile that is relevant to more than one user. Users can
be associated with more than one group and obtain authorizations based on the
group profiles with which the user is associated.
SSL security ensures both data privacy (unauthorized users cannot view the data)
and data integrity (unauthorized updates cannot be performed) between the
following connection points:
When you are defining authorization security, mask characters are available for all
options. Mask characters * and $ are translated during runtime security checking.
(For example, if User1 is granted full Scheduling Table authorization for table ACC*,
CONTROL-M allows User1 to update or order any table whose name starts with
ACC.) Valid mask characters are as follows:
Figure 15 on page 179 highlights the basic recommended workflow for setting up
authorization security for CONTROL-M. This overview section explains concepts
that are related to the workflow.
For specific tasks that correspond to each phase of the workflow, see Table 15 on
page 184. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
Implement
CONTROL-M/EM
authorization security
page 184
Implement
CONTROL-M/Server
authorization security
page 202
Implement
CONTROL-M/Agent
and remote host security
page 207
■ entities (such as jobs, Viewpoints, calendars, and resources) that a user or group of
users can access
■ actions (such as view, modify, or delete) that a user or group of users can perform
on those entities
When you associate a user with the authorization profiles of groups, either of two
algorithms apply to the inheritance of those profiles:
■ When you define user privileges using the Privileges tab in the Authorization
window, authorization inheritance works as follows:
— Specifying the DEFAULT access level for a privilege causes the user to inherit
the authorization for that privilege from the group profile. If the user is
associated with multiple groups, the user inherits the highest access level
defined for that privilege in those groups.
— Specifying any other access level gives the user that level (group access levels
for that privilege are ignored).
■ When you define the other authorizations (authorizations other than Privileges),
the algorithm is a composite of the user and group authorizations. For each
authorization, you specify an entity name and an authorization. For each entity
defined for the user or related groups, the user inherits the highest authorization
defined for that entity.
■ end users can access and run utilities from CONTROL-M/Server accounts
CONTROL-M/Server security allows you authorize under which account a job can
run, based on the job’s owner, and which actions (for example, forcing another job or
running a utility) the job owners are authorized to perform in the
CONTROL-M/Server account.
NOTE
If needed, you can also define authorization security for applications by defining a Control
Module account as the owner. For an Operating System job, you use operating system
security.
These authorizations are used to perform security checks each time one of the
following actions is attempted in CONTROL-M/Server:
■ ordering a job
■ running a command that affects jobs in the Active environment (for example,
Hold, Confirm, Rerun)
■ If no authorizations are defined for the user, the user inherits the authorizations for
the group.
■ If authorizations are defined for a user, the user’s authorizations take precedence.
■ When defining an authorization for a user (for example, Scheduling Table), use of
the (D)efault setting enables the specific authorization (for example, Read) defined
for the group.
■ Authorizations that are not specifically defined for a group (or for a user not
belonging to a group) revert to the Full Security parameter setting. (The Full
Security parameter is described in Table 81 on page 454.)
■ If one or more authorizations have been assigned to a user in the security database,
that user can perform only those actions.
■ The owner of each job processing definition must be defined as a user on the agent
computer. Otherwise, CONTROL-M/Agent will not execute the job.
The value of the CONTROL-M system parameter Full Security (described in Table 81
on page 454) determines the security level.
CONTROL-M/Agent security
CONTROL-M/Agents are the components that actually process the jobs.
CONTROL-M/Agents use operating system security, which focuses on the owner
who is defined for each job.
For Unix: Upon receiving a job execution request, CONTROL-M/Agent submits the
job on behalf of the owner only if the owner is defined in the operating system
security.
You create users and define their authorizations from the User Authorizations
window; and you create groups and define their authorizations from the Group
Authorizations window.
Before you can define these authorizations, you must create the user or group.
For instructions on creating users and defining their logon authentication criteria, see
“Defining users and their authentication criteria to CONTROL-M/EM” on page 166.
This section describes how to create groups and how to define user and group
authorizations.
NOTE
When you are copying an existing group, the users that belonged to the existing group are not
associated with the new group.
3 In the New Name dialog box, enter the name of the group and click OK.
To delete a group
2 In the Groups tab of the Authorizations window, choose the group and click
Delete.
2 In the Users tab of the Authorizations window, choose the user and click Update.
■ To add the user to one or more groups, select the groups in the Not A Member of
list and click Add.
■ To remove the user from one or more groups, select the groups in the Member of
list and click Remove.
A In the Users tab of the Authorizations window, choose the user and click
Update.
A In the Groups tab of the Authorizations window, choose the group and click
Update.
To define or modify the authorizations for users and groups, you perform the
following tasks:
NOTE
The task of defining logon data (in the General tab of the User Authentication
window) is described in the Security Authentication chapter.
■ Defining which Active environment jobs the user or group can access and actions
the user or group can perform
The General tab of the Group Authorization window lists the members of the group,
but you cannot update these entries. To add or delete members from the Group, use
the Member Of tab in the User Authorization window. For more information, see
“Defining which group profiles apply to a user” on page 186.
1 Define a filter that determines which jobs the user or group can display in a
ViewPoint, as follows:
You determine whether to include or exclude jobs that match a set of criteria.
C To define sets of filtering criteria, perform the following as often as needed until
the filter is completely defined:
1. In the Edit area, select a Field and relational operator, and specify the value.
You can specify an asterisk as a wildcard.
NOTE
■ Each line in the Include in or Exclude from Jobs Filter list can include multiple
criteria. There is an AND relationship between all the criteria on a line. Only jobs
that satisfy all the criteria on a line are included or excluded by the Jobs filter.
2 Click the appropriate boxes to define the actions the user or group can perform.
The following categories are available:
NOTE
■ Some job processing parameters cannot be used as selection criteria.
■ The following job filtering fields are relevant to alerts and are used when you apply the
filter definition to alerts: Application, CTM Name (CONTROL-M name), Group, Job
Name, Member Name, and Owner.
■ Users can see jobs permitted by User Authorization filtering criteria and jobs permitted by
Group Authorization criteria for any group to which the user belongs. However, the jobs
actions permitted by any of those filters apply only to the jobs permitted by that filter.
Therefore, the user might be able to perform certain actions on some jobs but not other
jobs.
EXAMPLE
User Bob has permission to see jobs starting with a*, and is authorized to perform Free and
Hold actions with regard to those jobs.
User Bob belongs to the Tech Support group. Members of this group have permission to see
jobs starting with b*, and are authorized to perform Rerun and Confirm actions with regard to
those jobs.
User Bob also belongs to the DBA group. Members of this group have permission to see jobs
starting with c*, and are authorized to use the Log and Documentation browse features and
perform Confirm actions with regard to those jobs.
When Bob logs on to CONTROL-M/EM, he will see all jobs starting with the letter a, b, and c.
On the group of jobs starting with the letter a he will be able to perform Hold and Free actions.
On jobs starting with the letter b he can perform Rerun and Confirm actions. On jobs starting
with the letter c he can view the Log and Documentation and perform Confirm actions.
Table 16 lists the possible access levels that you can allow for the privileges you grant.
Table 17 lists the components for which you can grant privileges at the desired access
level.
NOTE
CONTROL-M/EM users with Full access to CONTROL-M/Server Attributes in the Privileges
tab can add, modify, copy, or delete user and group authorizations. Users with Browse access
can view authorizations.
Table 18 summarizes the actions that you can authorize users and groups to perform
on scheduling tables.
NOTE
In addition to the security checks described above, CONTROL-M checks authorization for
each job in the Scheduling table, as described in Table 18 on page 191.
1 In the Scheduling Table tab, click Add to display the Scheduling Tables dialog box.
3 Select the Access Level for these scheduling tables. Table 19 on page 192 describes
the access levels.
4 Click OK to add the scheduling tables to the list in the Scheduling Tables panel.
NOTE
When you define scheduling table access:
■ Click Update, and in the Scheduling Tables dialog box, modify the current
scheduling table access definition.
■ Click Delete.
NOTE
These Owner definitions provide additional filtering criteria that supplement the criteria you
defined using the Scheduling Table tab, and they apply only to users who have at least
Update access granted in the Scheduling Tables tab. For more information, see “Defining user
or group access to and authorizations for scheduling tables” on page 191.
A CONTROL-M/Server
B Owner (user ID) on whose behalf the user or group can execute the job.
C Node ID/Group. This field identifies the computers on which the user has
authority to change or run jobs.
■ The <local> Node ID/Group value should be used when the Node ID/Group
field in the job editing form is left empty.
■ The Node ID/Group field is not applied to jobs running on CONTROL-M for
z/OS.
2 Click Add.
NOTE
Prerequisite conditions, control resources, quantitative resources, and global conditions, are
collectively referred to as conditions and resources in this section.
1 In the appropriate condition or resource tab, click Add to display the new
condition or resource dialog box.
2 Provide the names of the CONTROL-M/Server and the condition or resource. You
can use pattern matching strings (and an * to denote all values).
NOTE
For global conditions
■ you do not provide a CONTROL-M/Server name
■ you provide a global condition prefix
3 Select the Access Level for these scheduling tables. Table 20 describes the access
levels.
4 Click OK to add the conditions or resources to the list in the condition or resource
panel.
NOTE
When you define conditions or resources access:
EXAMPLE
To authorize a user to modify prerequisite conditions that start with the letter C (for CTM1) or
D (for CTM2):
2. In the New Prerequisite Condition dialog box, specify CTM1 in the Control-M text box,
type C* in the Conditions text box, and choose Update in the Access Level list box. Click
OK.
4. In the New Prerequisite Condition dialog box, specify CTM2 in the Control-M text box,
type D* in the Conditions text box, and choose Update in the Access Level list box. Click
OK.
2 Click Update, and in the new conditions or resources dialog box, modify the
current conditions or resources access definition.
3 Click OK.
2 Click Delete.
3 Click OK.
1 In the Scheduling Table tab, click Add to display the New Calendars dialog box.
2 Provide the names of the CONTROL-M/Server and calendars. You can use pattern
matching strings (and an * to denote all values).
3 Select the Access Level for these calendars. Table 21 describes the access levels.
NOTE
When you define calendar access:
2 Click Update, and in the New Calendars dialog box, modify the current calendar
access definition.
3 Click OK.
2 Click Delete.
3 Click OK.
When a job is ordered during the New Day procedure or by a User Daily job, the
Author parameter of the job is compared to the owner of the job. The Author
parameter does not affect manual job order and job force requests.
The following modes for restricting modification of the Author parameter are set
using the AuthorSecurity system parameter:
Special terms that are used in the description of this topic are defined in Table 22.
Table 22 Terms
Term Description
New jobs Jobs that are
■ defined in CONTROL-M/Desktop during the current session
■ edited while CONTROL-M/Desktop is not connected to GUI server.
■ being written to CONTROL-M/EM the first time using a utility
■ edited while CONTROL-M/Desktop is connected to the GUI server but
the job’s scheduling tables are not locked. Scheduling tables are unlocked
using the Unlock option in the Scheduling Table Manager or the
Disconnect from GUI Server option in the Communications menu in
CONTROL-M/Desktop.
Existing or Jobs that were loaded from CONTROL-M/EM into CONTROL-M/Desktop
other jobs and whose associated tables are locked.
This is the default mode. Editing the author is fully enabled. Users can retain the
original author value when running utilities or performing a Write to
CONTROL-M/EM or, alternatively, modify the author to another user.
■ For new jobs: The Author parameter is automatically set to the user who is running
the utility or performing a Write to CONTROL-M/EM.
NOTE
If not currently connected to the GUI Server, the name is temporarily set to the username
string. This name is reset to the current CONTROL-M/EM user when the user connects to the
GUI server and the definition is written to CONTROL-M/EM.
■ For existing jobs that have been changed and whose associated tables are locked:
— In mode 2, the original Author parameter is retained.
— In mode 3, the Author parameter is set to the user who is running the utility or
performing a Write to CONTROL-M/EM.
NOTE
A prompt may be displayed indicating that the Author field will be automatically changed to
the current user, depending on the setting of Resolve job’s Author Field conflict in the
General panel of the Options dialog box in CONTROL-M/Desktop. The user can either
accept the change, or cancel the entire Write to CONTROL-M/EM.
In both these modes, the Author parameter is displayed in the job editing form but
cannot be modified.
NOTE
Even when the AuthorSecurity system parameter is set to restrictive modes (2 or 3), an online
CONTROL-M/EM administrator (meaning, one connected to a GUI Server) can modify the
value of the Author parameter. Depending on the setting of Resolve job’s Author Field
conflict in the General panel of the Options dialog box in CONTROL-M/Desktop, a prompt
may be displayed before the value is changed.
Other considerations
■ After AuthorSecurity is modified, all CONTROL-M/Desktops must reconnect to
the GUI Server (using the Communication menu) for the change to take effect.
■ It is not necessary to recycle (stop and restart) the GUI server after changing the
mode of the AuthorSecurity system parameter, but the user must disconnect and
reconnect to CONTROL-M/Desktop.
Yes – Ignore the conflicts and save based on the Author that the administrator set.
No – Accept the security mode restrictions as if the administrator is a regular user.
Cancel – Cancel the entire Write to CONTROL-M/EM.
NOTE
The messages described above may not be displayed, depending on the Resolve job’s Author
Field conflict setting in the General panel of the Options dialog box in
CONTROL-M/Desktop. In this case, CONTROL-M/EM accepts the restrictions of the
security mode and updates the Author for all conflicting jobs. For information about
displaying confirmations, see the CONTROL-M/Desktop User Guide.
The permissions set using this procedure supersede the privileges defined in the User
Authorization window.
3 To give access to groups and users, enter values for the following tags. You can use
expressions such as a* or LIKE Bob for any of the fields.
Tag Value
Name The name of the CONTROL-M/EM group or user to whom
administrative rights for the control module are granted.
control_m The CONTROL-M server with which the control module
interfaces.
node_id The name of the CONTROL-M agent node on which the
control module is installed.
application_type The type of control module.
NOTE
■ To add an additional group or user, respectively, repeat step 3.
■ The relationship between more than one filter in the file uses OR logic. Meaning,
groups or users can manage control modules that answer any of the criteria in the list
of filters.
You must execute the above command every time the cm_admin.xml file is
modified.
1 Perform the following to set the value of the restricted_cm_admin system parameter
to 0.
To allow the GCS to add or delete global conditions on any CONTROL-M where
CONTROL-M security is implemented, a special authorized user should be defined.
On MVS systems, this user should be defined manually (as GCSERV, unless the
default name was changed in CONTROL-M/EM) in CONTROL-M. For more
information, see the chapter entitled “Installing IOA” in the INCONTROL for z/OS
Installation Guide. On UNIX and Windows systems, a default authorized user already
exists in CONTROL-M/Server, under the name GCSERV.
The GCSERV user name is also the default definition of an authorized user name in
CONTROL-M/EM.
You can change the GCSERV default user name using the GCSCommUserId system
parameter. For more information, see Appendix B, “System parameters.”
Implementing CONTROL-M/Server
authorization security
CONTROL-M/Server authorization security definitions are stored in the Security
database.
■ use the CONTROL-M/Server Security dialog box (Figure 16 on page 203), which
you access from CONTROL-M Configuration Manager, to create security
definitions. (Alternatively, you can use the CONTROL-M/Server ctmsec utility,
described in the CONTROL-M Utility Guide.)
NOTE
■ To implement CONTROL-M for z/OS authorization security, you must use the ctmsec
utility; you cannot use the CONTROL-M Configuration Manager.
To define users and groups (and to assign them privileges), you must have Full
privileges.
NOTE
To add a user to a group, the Group must already be defined.
4 Click OK.
■ To update the user or group definition, click the Update icon and then edit the
details in the Update dialog box. (To move the user into a different group, select
the appropriate Group value in the Update dialog box.)
4 Click OK.
NOTE
For simplicity, the following steps will refer only to users, rather than users or groups.
However, the steps apply to both users and group.
2 In the CONTROL-M/Server Security dialog box, select the user for which you are
providing authorizations.
B To authorize the user for a scheduling table for which the user currently has not
authorizations:
C For each possible action (delete, read, update, order), select whether you want to
authorize (Yes/No/Default) the user for that action. Choose Default to apply the
group authorization setting. If you select Default and the user does not belong to
a group, the action will not be authorized (as if you selected No.)
4 Define authorizations that the job owner will have for the copies of the
previously-defined scheduling tables that are placed in the Active Jobs file, as
follows:
B To authorize an owner that is not currently authorized for the user’s scheduling
tables:
C Specify the Node on which the owner will be authorized to perform actions on
the scheduling tables in the Active Jobs file.
D Specify (Yes/No/Default) the actions (rerun, hold, confirm and so on) the
owner will be permitted to perform on the tables in the AJF. Choose Default to
apply the group authorization setting. If you select Default and the user does not
belong to a group, the action will not be authorized (as if you selected No.)
5 Define authorizations that the user will have for the specific entities in the Active
environment, as follows:
B For each type of action (add, edit. delete) for each entity (calendar, condition,
log, and so on), select whether you want to authorize (Yes/No/Default) the user
to perform the action on the entity. Choose Default to apply the group
authorization setting. If you select Default and the user does not belong to a
group, the action will not be authorized (as if you selected No.)
6 To delete authorizations that you have defined, select the object in the appropriate
tab, and click the (Delete) icon.
7 Click Apply to save the changes and leave the CONTROL-M/Server Security
dialog box open. You can then select another user and repeat the process. (Or click
OK to save the changes and close the dialog box).
1 Display the CONTROL-M System Maintenance Utility Main Menu (ctmsys). For
instructions on displaying the menu, see “Using the CONTROL-M System
Maintenance Utility Main Menu” on page 47.
2 In the CONTROL-M System Maintenance Utility Main Menu, enter the number of
the System Parameters option.
2 Choose Start => Settings =>Control Panel=> Administrative Tools => Local Security
Policy.
4 In the displayed panel, double-click User Rights Assignments to display the list of
user rights.
5 Double-click the user right you want to assign. The Local Security Policy Settings
window for that user right is displayed.
A If the user who should have the selected user right is not listed in this window,
click Add.
B In the bottom panel, enter the <domain>\<user_name> of the user and click
OK.
C When the specified user is displayed in the lower panel, click OK again.
On a WMI remote host, the job owner must have the following authorizations:
■ The user must have a write access to the SYSOUT directory on the remote host. To
determine the SYSOUT directory of the remote host, do as the following:
1. In the CONTROL-M Configuration Manager, right click the remote host and
choose Properties.
The SYSOUT directory for WMI connection is listed at the bottom of the
Connections area in the dialog box.
NOTE
Generally, WMI does not provide access to the network. To access the network, connect using
a domain user, and grant DELEGATE impersonation level to the user and to any computer
included in the chain of calls.
■ A job that runs on the agent may contain a command to run the ctmcreate
CONTROL-M/Server utility.
■ A user logs into the Agent account and manually runs the ctmcontb
CONTROL-M/Server utility.
The default CONTROL-M/Server utility list (listing all utilities) is located in the
AGUTILS_PERMIT file in the CONTROL-M/Server data/AGDEFS directory.
2 In the file, list the CONTROL-M/Server utilities that are allowed to be run on the
Agent. (You can copy names from the list in the AGUTILS_PERMIT file in the
CONTROL-M/Server data/AGDEFS directory.)
7
Implementing CONTROL-M security
7
auditing
Conceptual overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Servers for auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Audit records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Setting up auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Enabling auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Setting which activities will be audited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Refreshing the list of activities handled by each server. . . . . . . . . . . . . . . . . . . . . 215
Setting up or stopping automatic deletion of old audit records. . . . . . . . . . . . . . 215
Viewing audit records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Conceptual overview
The Audit facility generates and stores a record in the CONTROL-M/EM database
each time an audited activity is performed. You can use the Reporting facility to view
audit records.
For specific tasks that correspond to each phase of the workflow, see Table 23 on
page 213. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
Set up auditing
page 213
Viewing audit
records
page 216
If you change the value of the UserAuditContext system parameter while the GAS,
GSR, or CMS is running, you must refresh the list of activities that each server
handles.
Audit records
Audit records are stored in serial number order. They include the following
information:
For example, for Active Network activities, the following fields are included: data
center name, scheduling table name, job name, memname, and order ID.
NOTE
For operations that change data values (such as updating quantitative resources or Zoom &
Save), the value before the change is recorded in the Audit log.
Setting up auditing
This section explains how to use the UserAuditOn system parameter to enable
auditing, and UserAuditContext to control which activities (for example,
authentication, scheduling definition, or active job activities) to audit.
Enabling auditing
1 In the CONTROL-M Configuration Manager, choose Tools => System Parameters =>
CONTROL-M/EM System Parameters.
4 Click Save.
AUTH SCHED J_CONT J_INFO RES ALERT ACCOUNT CONFIG OPER CTMSEC
DB_MAINT
4 Click Save.
NOTE
CONTROL-M/EM clients, such as CONTROL-M/Desktop and CONTROL-M/EM GUI, have
their own authorization checking mechanism. If an action does not pass a check at the client
level, it is not sent to the CONTROL-M/EM server and a record for that action is not stored in
the auditing table of the CONTROL-M/EM database.
Using the CONTROL-M/EM System Parameters dialog box, which you access from
the CONTROL-M Configuration Manager, you can adjust the audit-related system
parameters as necessary.
2 Scroll to the relevant audit system parameter (all belong to the general type, in the
Type field) to see its currently defined value. The following is the list of audit
system parameters and what they do:
C Click Save.
5 When the next cleanup operation begins, verify that the cleanup is performed
according to the new values for the system parameters.
8
Setting up CONTROL-M firewall
8
security
This chapter presents the following topics:
Conceptual overview
Because CONTROL-M components can be spread across multiple computers,
firewall security at your site can disrupt the flow of communication between
CONTROL-M components outside the firewall and those inside the firewall.
Depending on your CONTROL-M and firewall configuration, the following flows
might be impacted:
Following the table, the remainder of the chapter provides step-by-step instructions
for completing the tasks.
Enable communication
between CONTROL-M/EM
clients and servers
page 222
Enable communication
between CONTROL-M/Server
and CONTROL-M/EM
page 223
Enable communication
between agents
and CONTROL-M/Server
page 224
■ open a port in the firewall and define that port to the Naming Service
■ open a port in the firewall and define that port to the server
NOTE
This applies to CORBA servers (GSR, GAS, BIM, FORECAST and CMS). It does not apply
to GCS server.
Some client actions (for example, opening a ViewPoint or uploading tables) require
that the server return communication (callback) to the client. By default (bidirectional
IIOP), the server can call back using the same port used by the client to communicate
with the server. BMC Software recommends that you not change this default.
■ If you change the default from bidirectional IIOP, and if callback is necessary, you
must open a port in the firewall and define it to the client to enable the client to
listen to communication from the server.
NOTE
Bidirectional communication is enabled only if both client and server are configured to use it.
■ transient connection
This type is the default model used with new and upgrade installations.
This optional connectivity model between the server and agent is recommended
for components on different sides of the firewall. It improves performance and
avoids potential problems when establishing a connection.
In the persistent connection model, the connection between the server and agent is
constant and can be initiated by both the server and agent. Upon startup of the agent,
the Agent Router process is started and acts as a broker between the other agent
components and the server.
A Open a port in the firewall and define it to the Naming Service (default Naming
Service port: 13075), to enable the Naming Service to listen for communication
from the client.
B Use the Ports panel of the Domain Configuration window (this window is often
called the orbconfigure GUI) to open ports in the firewall and define them to the
server components to enable the server to listen for communication from the
client. For instructions, see “Assigning ports” on page 398.
NOTE
If you are not using Windows, you can use the orbadmin utility instead of the
orbconfigure utility. For instructions on using the orbadmin utility, see the
CONTROL-M Utility Guide.
BMC Software recommends the following when opening and defining ports:
■ open and define a range of ports for client applications such as the
CONTROL-M/EM GUI, Desktop and CLI, so that more than one session can
run simultaneously on the same machine
4 Register the ports in your firewall. For information about how to register port
numbers in your firewall, see the documentation provided with your firewall
software.
NOTE
When you define a port in CONTROL-M/Server, two ports are actually defined (each for
communication flow in the opposite direction), and you must open both of them in the
firewall.
With a persistent connection, the connection between server and agent is constant
and can be initiated by either the server or the agent.
To set the communication mode to persistent between the server and the
agent
3 Select the Parameters for Communicating with Specific Agent computers option
and press <Enter>.
5 From the Parameters for Communicating with Specific Agent computers menu,
select Persistent Connection and press <Enter>.
7 Enter S (Save) to save the modified parameters and to transfer the current
connection configuration to the specified agent.
NOTE
When you save the changes, CONTROL-M/Server sets Persistent Connection with the new
value and attempts to connect to the specific agent. When a connection is established with the
agent, the new configuration is transferred to the agent. The updated agent is reset. This
process can take a few minutes.
To set the agent so that it does not attempt to connect to the server
4 Click Save.
9
Configuring CONTROL-M for high
9
availability
This chapter presents the following topics:
Conceptual overview
Ensuring high availability means ensuring that CONTROL-M is able to continue
functioning and processing your production environment without interruption. This
generally means having some kind of fallback mechanism in place that can replace
failed components.
■ application
■ database
■ server
The main methods of ensuring high availability are implementing any of the
following
http://www.bmc.com/supportu/documents/85/52/58552/58552.pdf
Plan your
strategy
page 231
Manage failures
page 251
For specific tasks that correspond to each phase of the workflow, see Table 25 on
page 231. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
Failover takes high availability one step further than mirroring. With failover, you
implement a secondary installation that includes a secondary (failover)
CONTROL-M/Server in addition to a secondary database. This provides fallback not
only in case of primary database disruption but in case of primary
CONTROL-M/Server disruption.
Once failover or mirroring has been implemented, if a disruption occurs, you must:
NOTE
Once you have implemented database mirroring, CONTROL-M keeps the primary and
secondary databases synchronized. However, if you run utilities to update the CONTROL-M
database, you must perform database initialization again (synchronize the primary and
secondary databases). For details, see “Periodically synchronizing the primary and mirror
database” on page 257.
Reviewing prerequisites
Before proceeding, review the following requirements and guidelines, which are
relevant to the tasks in this chapter:
■ Ensure that database and account names that you create conform to your database
vendor’s naming conventions.
■ Verify that the database server that you want to use for mirroring is running.
■ If you plan to build a mirror database from scratch, you will need the password of
the database vendor’s system administrator.
This section provides worksheets to help you collect this information. Be sure to fill in
the worksheets relevant to the type of database server.
Table 26 identifies by database server type and information type the relevant
worksheet table number and page.
You will need these values when you prepare the secondary (mirror) database server.
When you initialize the mirror database by copying, prepare the values in Table 28.
You will need these values when you initialize (by building) the mirror database.
This value is taken from the current size of the primary database.
It should not be modified. Verify that the secondary database
server can host a database of this size. Verify that this value is the
same as the primary database.
Sybase Interface Full path to the Sybase interfaces file on the primary system. This
Directory value is displayed and can be modified by changing the value of
the Installed Sybase root directory parameter.
Installed Sybase The Sybase alias name as listed in Sybase interfaces file.
server alias name
CONTROL-M Name of the Sybase device that will be created for the data
Mirror Database portion of the CONTROL-M/Server Mirror database.
Data Device Name
CONTROL-M Name of the Sybase device that will be created for the log portion
Mirror Database Log of the CONTROL-M/Server Mirror database.
Device Name
Data Physical Device Full path or physical device name where the mirror database will
Path Name be located on the secondary database server. Specifying a
pathname initiates a File-based installation. Specifying a device
name initiates an installation to a Raw partition.
Log Physical Device Full path or physical device name where the mirror database’s
Path Name log database will be located on the secondary database server.
Specifying a pathname initiates a File-based installation.
Specifying a device name initiates an installation to a Raw
partition.
You will need these values when initialize the failover server.
You will need these values when you prepare the secondary (mirror) database server.
You will need these values when you initialize the mirror database.
echo $ORACLE_SID
You will need these values when initialize the failover server.
You will need these values when you prepare the secondary (mirror) database server.
You will need these values when you initialize the mirror database.
You will need these values when initialize the failover server.
You will need these values when you build the mirror database.
This is relevant only when the PostgreSQL database used for the
mirror database is located on UNIX. The recommended location
should be a new and empty directory under <owner user home
directory>/pgsql.
Existing Database Valid values:
Table 39 Worksheet for environment variables and alternative names— PostgreSQL (part 1 of 2)
Field name Equivalent name To view the value Your value
Database Owner Login CONTROL-M In UNIX, run this command:
Mirror Database echo $CONTROLM_MIRROR_USER
Owner (DBO)
In Windows, go to this registry key:
MIRROR_DB Owner
Table 39 Worksheet for environment variables and alternative names— PostgreSQL (part 2 of 2)
Field name Equivalent name To view the value Your value
Database Name CONTROL-M In UNIX, run this command:
Mirror database echo
name $CONTROLM_MIRROR_DATABASE
If you change the value of any of these parameters, the change will not be
implemented until you shut down and restart the Sybase SQL Server.
3 If you will be building a database, you must supply values for the database owner,
database name, devices and file or partition paths:
■ Specifying existing owner name, database name, and device assignments will
erase and recreate these database elements.
■ Specifying new, unique values for owner name, database name, and device
assignments will build a new database on the server.
4 Every computer type uses a different character set for Sybase. If the character set
for the primary database and mirror database are not the same, the character set
for the primary database must be installed on the mirror Sybase SQL Server. Use
the sp_configure to configure the character set for the existing SQL Server.
2 If you will be building a database, you must supply values for the database owner
and tablespace name:
■ Specifying existing owner and tablespace will erase and recreate these database
elements.
■ Specifying new, unique values for owner and tablespace name will build a new
database on the server.
2 If you will be building a database, you must supply values for the database owner,
database name, devices and file or partition paths:
■ Specifying existing owner name, database name, and device assignments will
erase and recreate these database elements.
■ Specifying new, unique values for owner name, database name, and device
assignments will build a new database on the server.
■ Any filenames you specify for a file-based installation must not exist on the
mirror database server.
3 Every computer type uses a different character set for MSSQL. If the character set
for the primary database and mirror database are not the same, the character set
for the primary database must be installed on the mirror MSSQL Server.
2 If you will be building a database, you must supply values for the database owner,
database name and database location.
■ Specifying existing owner name, database name, and database location will
erase and recreate these database elements.
■ Specifying new, unique values for owner name, database name, and database
location will build a new database on the server.
3 Every computer type uses a different character set for PostgreSQL. If the character
set for the primary database and mirror database are not the same, the character set
for the primary database must be installed on the mirror PostgreSQL Server.
For information that will help you prepare the failover database server, see the
appropriate table:
■ $HOME/ctm_server/data/TimeZone.dat
■ The configuration of the following directories should be the same as the primary
CONTROL-M/Server installations:
■ $HOME/ctm_server/data/SSL
■ $HOME/ctm_server/data/Remedy
■ Add the secondary server host name to the list of authorized hosts of each
CONTROL-M/Agent.
■ The Database (Data Portion) Size parameter should be assigned the same value
as the current size of the primary database.
For information that will help you ensure this, see the appropriate table:
shut_ca
shut_ctm
For each iteration, replace the <remoteHostName> variable with the name of a
remote host from the report.
■ Disabling mirroring
NOTE
BMC recommends that the primary and mirror databases be hosted on separate servers.
The following are the general steps that you perform to initialize a mirror database.
1 If you haven’t already done so, prepare the secondary database server.
You can prepare the secondary database server from the CD provided with the
product, or from a CONTROL-M/Server that is not your primary
CONTROL-M/Server. (For a third-party database, prepare it as you prepared the
primary third-party database.)
For information that will help you prepare the secondary server, see the
appropriate table:
shut_ca
shut_ctm
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Initialize Mirroring
option.
D Either build the failover database from scratch by entering b (build), or copy an
existing database to build your failover database by entering c (copy).
G Perform any post-processing that the interactive utility instructs. (For example,
if you are installing on Sybase and are instructed execute the ~/.cshrc command,
do so.)
5 Check that mirroring is enabled by entering the number of the Check Mirroring
Status option in the Database Mirroring Menu on the primary
CONTROL-M/Server.
start_ca
start_ctm
NOTE
All processing is executed on the primary and mirror database.
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Use Mirror Database
option.
start_ca
start_ctm
All processing is performed on the mirror database only. You should now fix the
problem on the primary database.
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Restore CONTROL-M
Database from Mirror option.
start_ca
start_ctm
The primary database is restored and all processing is performed on the primary and
mirror database.
Disabling mirroring
If you decide that you do not want database mirroring to be performed, you can
disable it as follows:
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Disable Mirroring
option.
D Check that mirroring is disabled by entering the number of the Check Mirroring
Status option in the Database Mirroring Menu on the primary
CONTROL-M/Server.
start_ca
start_ctm
Implementing Failover
This section presents the following topics:
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number for the Check Mirroring
Status option, and verify that mirroring is disabled.
4 Initialize failover by entering the number of the Initialize Failover option in the
Database Mirroring menu.
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number for the Check Mirroring
Status option.
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Initialize Mirroring
option.
D Either build the failover database by entering b (build) (using the same exact
parameters used in the database of the secondary CONTROL-M/Server), or
copy an existing database to create your failover database by entering c (copy).
For information that will help you respond to the prompts, see the appropriate
table:
G Perform any post-processing that the interactive utility instructs. (For example,
if you are installing on Sybase and are instructed execute the ~/.cshrc command,
do so.)
8 Check that mirroring is enabled by entering the number of the Check Mirroring
Status option in the Database Mirroring Menu.
start_ca
start_ctm
WARNING
Do not start the failover (secondary) CONTROL-M/Server while the primary
CONTROL-M/Server is running.
NOTE
When moving from primary to secondary server or from secondary to primary server, jobs
that are in executing state on the default local agent are not recognized by the other server. If
there are jobs without an owner, both the primary and the secondary server must have the
same account name.
To avoid this situation from occurring, define a specific nodeid for a job.
NOTE
Parameters in the config.dat file are not copied from primary to secondary server or from
secondary to primary server. For example, if SMTP communication parameters are not
updated on the secondary database, all domail actions will fail.
shut_ca
shut_ctm
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Start Failover option.
start_ca
start_ctm
shut_ca
shut_ctm
2 Stop failover processing by performing the following on the host computer of the
failover CONTROL-M/Server:
B In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
C In the Database Mirroring menu, enter the number of the Stop Failover option.
3 Ensure that the primary Configuration Agent and CONTROL-M/Server are shut
down by entering the following commands on their host computer:
shut_ca
shut_ctm
Each time that you run this command, replace the <remoteHostName> variable with
the name of a remote host from the list that was generated in step A on page 246.
start_ca
start_ctm
shut_ca
shut_ctm
C In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
D In the Database Mirroring menu, enter the number of the Disable Mirroring
option.
shut_ca
shut_ctm
C In the CONTROL-M Main menu, enter the number for the Database Mirroring
option.
D In the Database Mirroring menu, enter the number of the Disable Failover
option.
start_ca
start_ctm
The following table lists CONTROL-M/Server utilities that affect the primary
database. Also included is the action to perform to get the mirror database in sync.
For more information about these utilities, see the CONTROL-M Utility Guide.
CONTROL-M
This part presents the following topics:
Chapter 10
Maintaining the CONTROL-M environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Chapter 11
Maintaining databases and CONTROL-M data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
10
Maintaining the CONTROL-M
10
environment
This chapter presents the following topics:
Conceptual overview
Figure 23 highlights the basic recommended workflow for maintaining the
CONTROL-M environment. This overview section explains concepts that are related
to the workflow.
For specific tasks that correspond to each phase of the workflow, see Table 44 on
page 268. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
page 268
Manage CONTROL-M/
Servers
page 274
Send Control
Shell commands
page 273
Manually test
communication
page 272
State Description
Up The component is active (started).
Down The component is not active (stopped).
Hanging The component is not responding.
Using the CONTROL-M Configuration Manager, you can view and change
component states.
NOTE
When a CONTROL-M/Server or its corresponding Configuration Agent is down, the
subcomponents (CONTROL-M/Agent, CONTROL-M Configuration Manager, control
modules, and remote hosts) are gray, indicating that their statuses are undetermined.
CONTROL-M/Server management
As part of CONTROL-M/Server management, you can do the following:
■ Passive mode—the Heartbeat does not initiate heartbeat check messages, but can
respond to a heartbeat check message sent through a TCP/IP connection.
The Watchdog facility uses a Heartbeat monitor to check that all the primary
CONTROL-M/Server processes are functioning. If any of these processes do not
respond to the check, the Watchdog facility sends a message to an error handler. (The
facility automatically logs messages to the CONTROL-M IOALOG and PROCLOG
files.)
An error handler is an object that contains and performs instructions for handling
errors about which it was notified. Generally, error handlers are scripts.
To enable the Watchdog facility to run utilities and use scripts, you must enable
certain user exits.
You can adjust the functioning of Heartbeat monitors and the Watchdog facility by
modifying system parameters.
If the connection is restored, the status of jobs is updated to reflect their current
status, either completed or still running. If the connection is not restored after the
specified number of attempts, the jobs end with NOT_OK status.
The SYSOUT and exit code for jobs are stored in files on the remote host. The files
reside in the user home directory of the job’s owner, in the directory specified by
RJX_SYSOUT_DIR. For more information about RJX_SYSOUT_DIR, see
“CONTROL-M/Agent parameters” on page 505.
■ If network connections are restored, these files are deleted, by default, when the
jobs end.
■ If network connections were not restored, you can check these files to see if the jobs
completed successfully or failed.
NOTE
The CONTROL-M Web Server cannot be started or stopped from the CONTROL-M
Configuration Manager. It is a Windows service, and can only be started and stopped
manually from the Windows Start menu. It is automatically restarted anytime you reboot the
computer on which it resides. For details, see “Starting and stopping infrastructure processes
in Windows” on page 36.
If you select multiple components, all of them must have a similar state.
2 Choose Desired State and then choose one of the following submenu options:
■ Recycle— stops the current instance and starts a new instance, using one action.
You can choose Recycle only if the state of the selected component is Up.
NOTE
You can also perform these operations by using the ccmcli utility. For more information, refer
to the CONTROL-M Utility Guide.
For UNIX
You can start the agent automatically (whenever the computer starts) or manually.
NOTE
■ This task should be performed by the UNIX system administrator.
■ If CONTROL-M/Agent was shut down before the computer was restarted, the agent does
not start automatically.
For Windows
1 In Microsoft Windows, select Start => Settings => Control Panel => Administrative
Tools.
1 In Microsoft Windows, select Start => Settings => Control Panel => Administrative
Tools.
Recycling CONTROL-M/Agent
Recycling stops the current instance of CONTROL-M/Agent and starts a new
instance, using one action.
To recycle CONTROL-M/Agent
If you select multiple components, all of them must have a similar state.
You can choose Recycle only if the state of the selected component is Up.
NOTE
Using CONTROL-M Configuration Manager, you can recycle a CONTROL-M/Agent
(version 6.4.01 or later), but you cannot bring up, bring down, or ignore a
CONTROL-M/Agent. The Desired State fields in the CONTROL-M Configuration Manager
remain empty for CONTROL-M/Agents. For information on starting and stopping
CONTROL-M/Agents, see “Starting and stopping CONTROL-M/Agent” on page 269.
You can manually stop and start CONTROL-M/Agent at any time. When
CONTROL-M/Agent version 6.4.01 or higher is up, you can recycle it from
CONTROL-M Configuration Manager.
2 Choose Recycle.
NOTE
A confirmation message appears only if the CONTROL-M/Agent has jobs in Executing state.
If you select Yes
■ (For Unix) the jobs remain in Executing state and continue to run after the agent is
restarted
■ (For Windows) the jobs turn to Disappeared status and do not run after the agent is
restarted
You can also perform these operations by using the ccmcli utility. For more
information, refer to the CONTROL-M Utility Guide.
TIP
Selecting the Show Auto Filter Row check box displays an empty row across all columns,
enabling you to manually enter a filter criteria.
EXAMPLE
If the CONTROL-M/EM component desired state is Up, but the actual state is Down, the
Agents Log can help troubleshoot the reasons why.
■ The commands for CONTROL-M/EM components that you can run from the
Control Shell are the same as those that you can run using the -cmdstr parameter
in the CTL command line utility. For more information about this utility, see the
section entitled CTL in the CONTROL-M Utility Guide.
■ The commands for CONTROL-M for z/OS components are the same that you can
run directly from CONTROL-M for z/OS.
NOTE
For CONTROL-M for z/OS:
If you right-click the CONTROL-M/Server for a CONTROL-M for z/OS installation, the
Control Shell selects the Global Monitor for that installation. All information displayed in
the dialog box, and the commands that you specify, apply to the Global monitor. (This is
because for CONTROL-M for z/OS installations, the CONTROL-M/Server entity in the
CONTROL-M Configuration Manager does not represent a single entity, but rather it
represents a collection of entities, for which the most central and important entity is the
CONTROL-M Global Monitor.)
2 To display the list of valid commands and requests for the selected component,
click Usage. (The list is displayed in the Result box.)
3 Enter the required command into the Specify... field. (The field displays the last
entered command, and for CONTROL-M for z/OS components, it displays a
drop-down list of previously entered commands.)
4 Click Apply.
Managing CONTROL-M/Servers
Managing CONTROL-M/Servers consists of the following tasks:
NOTE
CONTROL-M/Servers that are unmanaged have a current state of Unknown.
WARNING
Do not use the Unmanaged option except for special cases where the CONTROL-M
Configuration Manager is unable to connect to the CONTROL-M Configuration Agent.
NOTE
Depending on your CONTROL-M Configuration Manager setup, disabled
CONTROL-M/Servers may still appear in the CONTROL-M Configuration Manager —with a
status of Ignored.
1 Back up and then delete all the scheduling tables from the CONTROL-M/Server.
BMC Software recommends that you not alter the defaults. However, if you choose to
alter the defaults, the system parameters are described in Appendix B, “System
parameters.”
Implementing exits
For implementing Watchdog facility exits, see “Watchdog facility exits” on page 528.
Managing CONTROL-M/Agents
Managing CONTROL-M/Agents consists of the following tasks:
■ “Disabling a CONTROL-M/Agent”
Disabling a CONTROL-M/Agent
To stop CONTROL-M/Server from sending jobs to a specific CONTROL-M/Agent,
you can disable the agent. This leaves the agent processes running even though
CONTROL-M/Server will not send it jobs. Jobs assigned to the specific agent are held
in Wait state, until the agent is re-enabled.
If the disabled agent is part of a node group, that agent will be skipped when jobs in
the node group are assigned to an agent.
NOTE
The CONTROL-M/Agent that is being modified must be available.
The CONTROL-M/Agent Debug dialog box is displayed. You can also display this
dialog box by choosing Tools => CONTROL-M/Agent Debug if there is at least one
CONTROL-M/Agent version 6.4.01 and later that is using the CONTROL-M
Configuration Manager.
NOTE
Values are dimmed if you do not have authority to change them.
3 Click Apply to accept all changes and for them to take immediate effect.
In the event of an error, the original diagnostics level and communication trace
values are set in the corresponding combo boxes.
4 Click OK to accept all changes and for them to take immediate effect.
NOTE
The CONTROL-M/Agent that is being modified must be available.
NOTE
Values are dimmed if you do not have authority to change them.
4 Click Save for the changes to take immediate effect and to close the
CONTROL-M/Agent - Update System Parameter dialog box.
If a system parameter does not have a default value, "N/A" is displayed in the Default
Value column.
11
Maintaining databases and
11
CONTROL-M data
This chapter presents the following topics:
Conceptual overview
This chapter explains how to backup, restore, rebuild, and maintain your
CONTROL-M databases. Figure 24 on page 283 highlights the basic recommended
workflow. This overview section explains concepts that are related to the workflow.
For specific tasks that correspond to each phase of the workflow, see Table 47 on
page 287. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks. (For information about database utilities, refer
to the CONTROL-M Utility Guide.)
Accessing the
CONTROL-M/EM
Database
Maintenance menu
page 288
Accessing the
CONTROL-M/Server
Database
Maintenance menu
page 289
Create Server
database backups
page 292
Restore or rebuild
a Server database
page 286
page 299
Perform periodic
cleanup
page 308
CONTROL-M databases
Each CONTROL-M/Server has its own database. Each Server database contains the
job processing definitions (organized by scheduling tables) for which that Server is
responsible. In addition to the Definitions file, the CONTROL-M/Server database
also maintains an Active Jobs file, a Resources table and a Conditions table.
CONTROL-M/EM has its own database. This database allows you to control your
entire batch production enterprise. The Definition file of the CONTROL-M/EM
database contains a copy of all job processing definitions from all of your
CONTROL-M/Server databases. This database also includes the Active
Environment.
■ For CONTROL-M/EM, you can access these from the Root menu.
■ For CONTROL-M/Server, you can access these from the CONTROL-M Main
Menu (ctm_menu).
Hot backups
■ Hot backups are performed in archive mode, which is discussed in “Archive mode
(Oracle and PostgreSQL only)” on page 285. Running the database in Archive
mode requires extra disk space for control files.
Cold backups
You can use cold backups to restore the database to the state it was in when the
backup was performed. To perform a cold backup, archive mode must be disabled.
NOTE
■ You can run the ctm_backup_bcp utility even when the database is in archive mode.
If you enable archive mode, you should plan to keep it enabled for long term use. If
you enable and disabled it frequently, the archived log files will not provide useful
information for database restoration.
NOTE
If archive mode is enabled, database transactions might be performed more slowly, and
archive files will require more disk space.
NOTE
When a cold restore is performed, the restore file must be exported from the database with the
same encoding as the destination database.
If you rebuild the database with UTF8 encoding, you must manually configure the
environment settings, to enable the CONTROL-M/Server components to support this
encoding.
Manual database housekeeping and cleanup described in this chapter is intended for
special situations where you might want to clean out more data than is cleaned out by
the automatic clean up. For example, if disk space is low, you might want to remove a
larger than normal portion of a particular type of data.
If you find that you are performing manual cleanups frequently, especially the same
type of cleanup each time, you should consider adjusting the system parameters so
that automatic cleanup more closely matches the cleanup pattern you desire.
Maintaining Databases
You can use the following methods to maintain the CONTROL-M/EM and
CONTROL-M/Server databases.
— use the interactive Database Maintenance menu that you access from the Root
menu (described in this section).
— run the ecsutil from the command line (described in the CONTROL-M Utility
Guide.)
2 In the CONTROL-M/EM Root menu, enter the number for the Database
Maintenance option.
2 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
NOTE
Archiving, using the Archive Mode option described below, is only possible when
CONTROL-M is running with a dedicated database server.
Hot backups require that archive mode be enabled, but the backup procedure automatically
sets archive mode if it was not previously set. For more information about hot backups, see
“Types of backups (Oracle and PostgreSQL only)” on page 284.
2 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
3 In the Database Maintenance menu, enter the number for the Archive Mode option.
4 At the prompt for the destination directory, enter the name of the destination for
archived log files.
NOTE
Performing this procedure has the same effect as running the ctmdbbck utility. For more
information, see the CONTROL-M Utility Guide.
2 In the CONTROL-M Main Menu, enter the number for the Database Maintenance
option.
3 In the Database Maintenance menu, enter the number for the List Backup Devices
option, and write down the name of the device that you want to use.
NOTE
If the device you want is not listed, you can add it as instructed in “Adding a new
CONTROL-M/Server backup device” on page 294.
4 Return to the Database Maintenance menu, and enter the number of the Backup
Database option.
5 Enter the name of the backup device you wrote down in step 3.
The backup device must be either a valid device defined in the SQL database, or
the full path name of a file to be created by the backup procedure.
2 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
3 In the Database Maintenance menu, enter the number for the Backup Database
option.
4 Press Enter to accept the default directory, or enter the name of a different
directory where you want the backup to be saved.
■ If Archive mode is not active at your site, a cold backup (described in “Types of
backups (Oracle and PostgreSQL only)” on page 284) is automatically
performed.
■ If Archive mode is active, the following prompt is displayed:
Enter your choice for backup mode (Hot or Cold) [H/C]:
5 Select either H for hot backup or C for cold backup, and press Enter.
6 Enter the directory in which the archive process will store its control files.
The backup procedure begins. Informational messages report the progress of the
backup.
8 If you selected a cold backup in step 5 on page 293, when the backup is complete,
start CONTROL-M/Server.
2 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
3 In the Database Maintenance menu, enter the number for the Add Backup Device
option.
Enter <dev_logical_name> :
Enter <disk|tape> :
Enter <file_full_path_name|device name> :
<file_full_path_name| full path name (for disk) or a device name (for tape)
device_name>
Example
When prompted, specify the following values for the Add Backup Devices option in
the Database Maintenance Menu:
Prompt Value
Enter <dev_logical_name> : cont
Enter {disk|tape} : tape
Enter <device_name> : cont_dev
NOTE
You can drop or delete a backup device by choosing Drop Backup Device from the Database
Maintenance Menu and providing the device’s logical name.
NOTE
Performing this procedure has the same effect as running the ctmdbrst utility. For more
information, see the CONTROL-M Utility Guide.
2 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
3 In the Database Maintenance menu, enter the number for the Restore Database
option.
The backup device must be a valid device defined in the database, or the full path
name of a backup file to be used as input for the ctmdbrst utility.
If you do not know the name of the backup device, display the list of backup
devices by entering the number of the List Backup Devices option in the Database
Maintenance menu, and then note the name of the device.
■ If you want to perform a restore from a Cold backup and Archive mode is active,
deactivate Archive mode (using option 1 of the Database Maintenance menu) before
performing the steps described below.
1 Shut down CONTROL-M/Server, and make sure there are no other users or
processes connected to the SQL Server.
3 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
4 In the Database Maintenance menu, enter the number for the Restore Database
option.
5 Press Enter to accept the default directory, or type the name of the directory in
which the backup was saved.
WARNING
If you try to restore a dedicated Oracle database using the ctmdbrst utility without previously
having backed up the database, the database will become unavailable. To access the database,
enter the following procedure from the CONTROL-M/Server home directory command line:
sqlplus /nolog
connect / as sysdba
alter database mount;
alter database open;
exit
(For PostgreSQL only) - If a hot restore process failed, it is possible to revert back to the
file system as it existed before the restore process began. For details, see the following
instructions.
NOTE
The hot restore process uses the $HOME/pgsql/data/pg_xlog directory to recover the
database up until the point of failure. If this directory was damaged during the failure, the
database can only be recovered up until the last database log switch.
2 Go to the pgsql parent directory. On UNIX for example, this directory is the user
$HOME directory.
4 Rename it to pgsql.
Before rebuilding the database, back up the database data. (For instructions, see
“Backing up a CONTROL-M/Server database” on page 292.) You will use this
backup to restore the data at the end of the rebuild process.
■ The SQL database is running. For more information, see “Starting and stopping
CONTROL-M/EM server components and CONTROL-M/Server” on page 268.
2 In the CONTROL-M Main menu, enter the number for the Database Creation
option.
3 In the Database Creation menu, enter the number for the Build Database option.
4 Follow the prompts online, and specify or change the parameters as required.
Default values are provided for most of the parameters. Modify them as required.
For more information on the parameters, see Appendix B, “System parameters.”
NOTE
When rebuilding the database, working in an existing mode, the full path names of the log
and data devices must be different from the original path names.
5 In the Main Menu, enter the number of the Database Maintenance option.
6 In the Database Maintenance, enter the number of the Restore Database option to
load the data into the new database.
The backup device must be a valid device defined in the database, or the full path
name of a backup file to be used as input for the ctmdbrst utility.
If you do not know the name of the backup device, display the list of backup
devices by entering the number of the List Backup Devices option in the Database
Maintenance menu, and then note the name of the device.
2 In the CONTROL-M/EM Root Menu, enter the number for the Database
Maintenance option.
3 In the Database Maintenance menu, enter the number for the Export Database
option.
4 Specify the name of the file to which the database should be exported.
The database is exported to a file that you specify. The file is called
export_file_name.Z.
5 Enter q to exit the Database Maintenance menu and the Root menu.
2 In the CONTROL-M/EM Root Menu, enter the number for the Database
Maintenance option.
3 In the Database Maintenance menu, enter the number for the Import Database
option.
You are prompted for location of the export_file_name file that was created during
the procedure “Export the existing CONTROL-M/EM database” on page 154.
4 Enter the path and name for the export_file_name file. Do not include the .Z
extension.
5 Enter q to exit the Database Maintenance menu and the Root menu.
WARNING
If you quit the Root menu or its submenus while performing the database import, you must
perform “Rebuilding the database schema following import interruption” on page 300.
NOTE
You should only perform this procedure if an interruption occurred to the procedure:
“To import previously exported CONTROL-M/EM data” on page 299.
2 Enter the following command to uncompress the export_file_name file you created
during the procedure “Exporting and importing CONTROL-M/EM data” on
page 299:
uncompress export_file_name.Z
5 Import the database data to the new database using the following command:
Invoke the util utility with -export and -type audit, using the following syntax:
Invoke the util utility with -import, -replace, and -type audit, using the following
syntax:
For more information, see the description of the ctmsec utility in the CONTROL-M
Utility Guide.
2 If you are using an Oracle database, specify the database administrator password
and the user name.
The CONTROL-M/EM Database dialog box is displayed, showing the size and
free space of the database.
NOTE
If the available space falls below 20%, either extend the database or reduce the existing data.
■ To reduce the data, cleanup the database error log files. For instructions, see page 304.
NOTE
Alternatively, you can check the available space in the database from the Root menu. For
instructions on activating the Root menu, see page 46.
B Specify the new size (in MB) for the segment that you are extending.
C Specify the path and assign a file name for the segment you are extending.
NOTE
Ensure that a file with that name does not yet exist.
A Specify the name of the table space that you are extending.
B Specify the new size (in MB) for the segment that you are extending.
D Specify the path and file name for the segment you are extending.
NOTE
Alternatively, you can extend the database from the Root menu. For instructions on activating
the Root menu, see page 46.
Whether responsibility of maintaining the error log file goes to the CONTROL-M
administrator or the database administrator depends on whether your site is using
the dedicated database server provided with the installation, or an existing database
server.
■ When your site uses a dedicated database server provided during installation, it is
the responsibility of the CONTROL-M administrator to truncate this file on a
regular basis. The location of this file depends on the database type.
$ORACLE_BASE/admin/$ORACLE_SID/bdump/alert$ORACLE_SID.log
■ Trace log files are saved in files with the extension .trc
$ORACLE_BASE/admin/$ORACLE_SID/bdump/$ORACRR_SID_*.trc
2 In the CONTROL-M/EM Root Menu, enter the number for the Database
Maintenance option.
3 In the Database Maintenance menu, enter the number for the Erase Old Nets option.
4 Enter q to exit the Database Maintenance menu and the Root menu.
NOTE
(Windows only) Gateway automatically removes old archived networks.
The number of days alerts are kept in the database is set according to the
MaxDaysAlertRetained system parameter. Alerts older than the specified days are
automatically deleted, regardless of their status.
Should you want to delete additional alerts manually (for example, if disk space is
low), you can perform the following steps. (Alternatively, you can delete the using
the ccmcli utility. For details, see the CONTROL-M Utility Guide.)
2 In the Date field, choose the desired date and click OK, to delete all alerts posted
on or before the specified date from the CONTROL-M/EM database.
NOTE
To enable the deletions to take effect, refresh the Global Alerts Server server from the
Control Shell, as follows:
1. In the CONTROL-M Configuration Manager, right-click the Global Alerts Server, and
choose Control Shell. \
3. Click Apply.
where nn is the number of days to keep job history. Job version that have been kept
for more days will be deleted.
Output of the utility will list the number of old versions before the cleanup and
number of old versions remaining after the cleanup.
■ Regular alerts relate to job processing problems and are intended for the end user.
■ Exception alerts identify problems with component infrastructure, and are
intended for the administrator for diagnostics purposes.
UNIX
1 Display the CONTROL-M/EM Root Menu (root_menu). For instructions on
displaying the Root menu, see “Using the CONTROL-M/EM Root Menu” on
page 46.
2 In the CONTROL-M/EM Root Menu, enter the number for the Database
Maintenance option.
3 In the Database Maintenance menu, enter the number for the Erase Exception Alerts
option.
4 Enter q to exit the Database Maintenance menu and the Root menu.
Windows
1 Run the following script: purge_xalerts.bat
3 Confirm whether the exception alerts should be removed after the number of days
entered.
2 In the CONTROL-M/EM Root Menu, enter the number for the Database
Maintenance option.
3 In the Database Maintenance menu, enter the number for the Erase Audit Data
option.
4 Enter q to exit the Database Maintenance menu and the Root menu.
2 Enter the following command. If you do not specify -U and -P, you will be
prompted to enter the DBO user name and password.
2 In the CONTROL-M Main menu, enter the number for the Database Creation
option.
3 In the Database Creation menu, enter the number for the Check Database option.
2 In the CONTROL-M Main menu, enter the number for the Database Maintenance
option.
A In the Database Maintenance menu, enter the number for the Extend Database
Size option.
B At the prompt, specify a size value or press <Enter> to accept the default.
■ For Oracle: In the Database Maintenance menu, enter the number for the
Extend TEMP Tablespace Size option.
■ For Sybase: In the Database Maintenance menu, enter the number for the
Extend Temporary Database Size option.
B At the prompt, specify a size value that is approximately 10% of the data
segment size, or press <Enter> to accept the default.
■ For Oracle: In the Database Maintenance menu, enter the number for the
Extend Rollback Tablespace Size option.
■ For Sybase or MSSQL: In the Database Maintenance menu, enter the number
for the Extend Database Log Size option.
B At the prompt, specify a size value that is approximately 1/3 of the data
segment size, or press <Enter> to accept the default.
If, after you have issued the extension request, you get a warning about an unsafe
virtual device, or non-guaranteed recovery, disregard it.
WARNING
■ Using the ctmcontb utility to clean up a large number of prerequisite conditions from the
originating CONTROL-M/Server (and therefore all CONTROL-M/Servers to which they
were added) can degrade performance.
■ To prevent undesired mass deletion of prerequisite conditions during this type of cleanup
which might cause excessive traffic, ensure that you defined appropriate values for the
following distribution system parameters for the prerequisite conditions:
— LimitGCDistribActivate
— LimitGCDistribMaxDays
— LimitGCDistribExcludeDates
Whether responsibility of maintaining the error log file goes to the CONTROL-M
administrator or the database administrator depends on whether your site is using
the dedicated database server provided with the installation, or an existing database
server.
■ When your site uses a dedicated database server provided during installation, it is
the responsibility of the CONTROL-M administrator to truncate this file on a
regular basis. The location of this file depends on the database type.
$ORACLE_BASE/admin/$ORACLE_SID/bdump/alert$ORACLE_SID.log
■ Trace log files are saved in files with the extension .trc
$ORACLE_BASE/admin/$ORACLE_SID/bdump/$ORACRR_SID_*.trc
— On UNIX: $CONTROLM_SERVER/proclog
— On Windows: <ctm_installation>\proclog
■ the proclog file from the previous session is saved to one of the following locations:
— On UNIX: $CONTROLM_SERVER/proclog.sav
— On Windows: <ctm_installation>\proclog.sav
The higher the trace level, the larger the log files. If CONTROL-M/Server entities
operate for a long time using a trace level greater than zero, these log files utilize a
large amount of disk space.
Valid values:
Default: -1 (In the shipped config.dat, the default value is overridden by 10.)
How / where to set: See “Editing the config.dat file” on page 408.
Default: -1 (In the shipped config.dat, the default value is overridden by 10.)
How / where to set: See “Editing the config.dat file” on page 408.
The CONTROL-M/Server administrator should delete these log files when they are
no longer needed.
2 In the CONTROL-M Main menu, enter the number for the Troubleshooting option.
3 In the Troubleshooting menu, enter the number of the Erase Proclog Files option.
This option erases the contents of the current process log file either for all active
CONTROL-M/Server processes or for any specific active process.
4 Specify the 2-character code for a specific process, or ALL for all current process log
files. For more information, see “Troubleshooting menu analyzing options” on
page 367.
NOTE
This problem might in rare instances occur in CONTROL-M/Server versions prior to 6.3.01,
on Sybase only.
The master database log might become full if the trunc log on chkpt option is not
enabled. If this problem occurs, the Sybase error_log displays the following message:
You can resolve this problem using any of the following methods, as appropriate.
2 Enter the command, which dumps unnecessary information from the log:
To add more space to the log (a longer-term solution if the master log often
gets full)
To enable automatic log truncation (an ongoing solution that prevents the
problem but results in automatic loss of log data)
2 Enter the following commands to set the trunc log on chkpt option for the master database.
which will truncate the log as needed, so that it will never become full.
Chapter 12
Diagnostics: conceptual information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Chapter 13
Activating diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Chapter 14
Collecting diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Chapter 15
Processes of elimination and analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
12
12 Diagnostics: conceptual information
This section comprises diagnostics and troubleshooting in CONTROL-M. Various
fundamental diagnostic tasks are discussed in context, with examples of some of the
expected circumstances surrounding the issues. In many cases, troubleshooting
information relates to very specific issues that are particular to you and your site
requirements. For this reason, you can always search the CONTROL-M Knowledge
Base, accessible through the BMC website, under the heading “Support”.
Various situations require various diagnostic activities. One of these is that the
information gathered by default by a product is sufficient for analysis (First Failure
Data Capture). A second is that each time an action is performed, it fails. This requires
that you gather diagnostic information about the circumstances that occurred in your
system before, during and after the symptom displayed. To do this, you must set
certain diagnostic parameters and configurations to run, and then recreate the
situation where the symptom occurred. A third situation is where a problem recurs
but on a sporadic basis, with no clear pattern or the possibility to recreate it. This
requires that a diagnostic be activated (one which will not over-burden the system)
and left to run in the background for a few days.
There are several basic diagnostic mechanisms used when running diagnostic
actions.
An example of source level debugging is the “Diag” mechanism, which is used by the
majority of the CONTROL-M/EM component servers (GUI Server, Global Alerts
Server and so on).
Another dimension of source level debugging is the ability to choose to where the
information gathered is written. Basic source level debugging (persistent) is written
to a log file. Extended source level debugging (dynamic) means that you write a
diagnostic message into the memory of the process, using the advanced level
memory buffer. This gives you FFDC, and can provide invaluable insight into the
reasoning behind service, component or functional failure.
There are both advantages and disadvantages to each method, and you should make
your choice according to the specific issue and based on the nature of your
environment and your requirements.
Information captured in a log file covers the events that occurred over a longer period
of time, and can therefore provide more chronological details. Using the memory
buffer gives you a more detailed level of information, regarding when the problem
occurred, how it occurred, where it occurred and so on. However, the memory buffer
option is more limited in space, and information is cyclically overwritten, as often as
the configuration dictates.
For more information about basic source level debugging, see “Setting persistent
source level debugging diagnostics” on page 332. For more information about using
the advanced level memory buffer, see “Sample gsr_DiagLvls.ini file” on page 335.
Communication Traces
Communication Traces can be either log or trace files, which provide a
comprehensively detailed exchange of data between two or more servers. Said data is
structured in a specific manner, in order to give as much information as possible
about the occurrences between the servers. Examples of communication trace
activities include the Global Conditions Server log, or the .
Exception Alerts
This feature alerts you to system failures and enables you to handle these exception
alerts as necessary. Exception alerts (X-Alerts) are provided for the following types of
failures:
■ database
■ communications network
■ application errors and failures in CONTROL-M/EM background processes, such
as CONTROL-M/EM Server processes, that could impair production. An example
of such a background process error might be the failure of the Global Condition
Server to deliver a global condition to one or more of its target data centers.
Using system parameters, you can configure the exception handling mechanism by
determining
For more information about the types of issues that can be diagnosed prior to
contacting BMC Customer Support, please see Chapter 15, “Processes of elimination
and analysis.”
Documented in that chapter are several examples of common issues that can occur,
and procedures that follow a straightforward, methodological approach to
ascertaining the root cause behind them. In this way, a seemingly random or
unconnected symptom that displays as an error within your CONTROL-M
environment can be either easily dealt with, or the information gathered and
packaged to facilitate a clear channel of communication between you and BMC
Customer Support.
Following is a table designed to help you identify some of the more common issues of
this nature. These examples range across the broader sphere of the various
components and sub-components which constitute your CONTROL-M environment.
While the issues described in this table are considered “common”, they are all also
complex and severe enough to require that you work in conjunction with BMC
Customer Support to achieve a successful resolution.
NOTE
Issues can often be caused or be connected to more than one CONTROL-M component.
NOTE
For information regarding BMC Batch Impact Manager, or BMC Forecast, please refer to the
BMC CONTROL-M BSM Administrator Guide.
13
13 Activating diagnostics
This chapter describes the diagnostic procedures that exist within the framework and
architecture of CONTROL-M. These have been divided into sections according to
CONTROL-M or CONTROL-M/EM component. However some of the issues that
arise, and the subsequent diagnostic activity spans more than one component.
For the majority of the procedure and diagnostic capability described in this chapter,
BMC Software recommends that you consult BMC Customer Support prior to
activating any of the procedures.
For details of pre-diagnostic activities and procedures that check the cause of a
problem using a process of elimination, prior to running actual diagnostic utilities,
see Chapter 15, “Processes of elimination and analysis.”
The diagnostic procedures in this chapter have been categorized under the main
components of CONTROL-M:
Certain components use both source level debugging and communication traces.
These are detailed in the following sections.
NOTE
BMC Software recommends that you use the diagnostic facilities either as a precursor to
working with BMC Customer Support, or in conjunction with them.
■ GUI Server
■ CONTROL-M Forecast
■ Global Conditions Server (see “Diagnostics and the Global Conditions Server” on
page 335)
Source level debugging diagnostic settings can be modified on both a persistent and a
dynamic basis. It is advisable to modify using settings both methods. This means that
changes can take effect immediately, without having to restart your system. In this
way you do not lose production time, and when the system does restart, the settings
will still be in effect.
Persistent (long term) changes are made by modifying the parameters in the
component initialization (.ini) file. These remain set unless the file is altered.
Information can then be recorded regarding events that occur over a period of time.
Dynamic (immediate) changes are made by selecting a specific component from
within the CONTROL-M Configuration Manager, and modifying the diagnostic
settings accordingly.
The information collected when the DIAG diagnostics facility runs is collected in a
log file. You can then look through the log file for any unusual activity that can help
pinpoint the source of a problem.
The higher the level set, the more system resources are required. This can result in an
environment functioning slower than usual.
This issue is resolved by the advanced memory buffer, which is set at level 4 by
default, and prevents excessive slow-down in production.
NOTE
You should ensure that you also modify the persistent settings for the component. For more
information, see “Setting persistent source level debugging diagnostics” on page 332.
For more information about the Control Shell and its functionality, see
“Implementing job version management” on page 105.
For more information, see “Available diagnostic levels and advanced memory
buffer” on page 331.
<em_root>/ini/<component_name> DiagLvls.ini
The parameters that can be specified for setting persistent diagnostic levels are
described in Table 56.
NOTE
Certan parameters can be modified dynamically, using the Control Shell. These are indicated
clearly in Table 56. For more information, see “Setting dynamic source level debugging
diagnostics” on page 331.
A sample .ini file is displayed. See “Sample gsr_DiagLvls.ini file” on page 335.
Valid values:
■ 0 (non-cyclic)
■ 1 (cyclic)
Default: 0
NumOfFiles Maximum number of cyclic files to create.
Mandatory only if IsCyclic = 1.
Default: 0.
Default: 0
Example: MinimumDbgLvl 4 7 will set level 4 for the log file and 7 for
the memory buffer.
MemBufferSize Buffer size in kilobytes.
size
Valid values: 20 - 1000
The ctl utility can change the buffer size for the GUI Server and Global
Alerts Server during run time.
IsBufer Specifies if the memory buffer is used or disabled.
Valid values:
■ 0 – memory buffer is disabled
■ 1 – memory buffer is used
Default: 0
Valid values:
■ 0 – PID is not included in the file name
■ 1 – PID is included in the file name
Default: 0
PrintLevelMaps Specifies if the list of DIAG levels for the process or component should
be printed.
Valid values:
■ 0 – levels should not be printed
■ 1 – levels should be printed
Default: 0
FlushBufferSize Number of bytes the buffer holds before it is flushed (that is, before
size DIAG messages are automatically written to file).
Valid values:
■ 0 (off)
■ 1 (on)
Default: 1
MinimumDbgLvl 2 4
IsCyclic 1
NumOfFiles 5
NumOfMessages 25000
IsBuffer 1
MemBufferSize 5120
IsPIDUsed 1
PrintLevelMaps 1
DiagStacksOn 1
NumOfFormalObjects 100
@20 2 5
To set cyclic logging files on a dynamic basis, you must access the Control Shell
window for GCS, and modify the settings accordingly.
For information about accessing the Control Shell, see “Setting dynamic source level
debugging diagnostics” on page 331. For more information about the Control Shell
and its functionality, see “Implementing job version management” on page 105.
For information about setting cyclic log files, and activating persistent settings for the
GCS permanent log (GCS_LOG file), see Table 73 on page 431in Appendix B, “System
parameters.”
For more information about the GCS_LOG files, see “GCS_LOG files” on page 372.
Setting dynamic source level debug diagnostics for the GCS (GCS_DIAG)
To set cyclic diagnostic files on a dynamic basis, you must access the Control Shell
window for GCS, and modify the settings accordingly.
For information about accessing the Control Shell, see “Setting dynamic source level
debugging diagnostics” on page 331. For more information about the Control Shell
and its functionality, see “Implementing job version management” on page 105.
Setting persistent source level debug diagnostics for the GCS (GCS_DIAG)
Setting persistent diagnostics for the Global Conditions Server differs from other
CONTROL-M/EM components only because the file in which the settings are
modified is the Defaults.rsc file, as opposed to an .ini file. The Defaults.rsc file is
located:
■ On UNIX: home_directory/site/resource/
■ On Windows: home_directory\Gtwgcs\appl\site\resource
Table 57 displays the diagnostic parameters that determine the nature of the
diagnostic messages displayed and collected in the GCS diagnostic files (GCS_DIAG).
When set to default levels, only messages documenting more severe errors are
displayed in the file. As soon as the settings are modified to a higher diagnostic level,
more messages are displayed, encompassing a broader variety and severity of errors.
Note: If no value is specified for integer2, the level defined in the integer1 value is
applied for all modules.
db_diag_lvl Determines the message levels for database diagnostic messages related to the
Global Conditions server that are collected in the GCS_DIAG file.
Valid values:
■ 0 – no database message collection (except those collected by db_diag).
■ 1 - 5 – Each higher level collects the messages from all of the lower levels.
Default: 0
diag_size Maximum number of record lines in the GCS_DIAG file, where integer indicates the
number of rows permitted per file.
Default: 25,000
Default: 10
NOTE
BMC Software recommends that you change the values of these parameters only in
conjunction with BMC Customer Support.
3 Copy and paste the required command into the “Specify...” field, and click OK.
NOTE
BMC Software recommends that you use the diagnostic facilities either as a precursor to
working with BMC Customer Support, or in conjunction with them.
NOTE
Valid values range from 0 to 5, where 0 indicates no diagnostic activity, and 5 indicates the
highest level of diagnostic functionality.
NOTE
Valid values range from 0 to 4, where 0 indicates no diagnostic activity, and 4 indicates the
highest level of diagnostic functionality.
NOTE
The trace level can be set to ON by setting the value to 1 and can be set to OFF by setting
the value to 0.
6 Click OK.
14
14 Collecting diagnostic data
This section describes the method for collecting diagnostic data for
CONTROL-M/EM, CONTROL-M/Agent, CONTROL-M/Server, and related
applications. Diagnostic information collected using such methods can assist in
troubleshooting using the extensive data and information collected.
NOTE
Once collected, the diagnostic information can then be analyzed. For more information about
this, see Chapter 15, “Processes of elimination and analysis.”
The CONTROL-M Health Check utility scans and collects system information about
the CONTROL-M environment and its various components. This information is used
to troubleshoot and correct problems. The information gathered is packaged in a
compressed hierarchical format that allows for analysis of the collected information.
The hierarchy is important in determining the nature of the collected data.
■ Categories are different types of information from various parts of your system.
■ Profiles are used to group categories according to a common denominator.
The Health Check utility should always be used in conjunction with BMC Customer
Support.
For information about configuring, using and executing the Health Check utility, see
the CONTROL-M Utility Guide.
With this tool, you can send generated reports to interested parties using e-mail or
FTP to BMC Software (ftp://ftp.bmc.com/incoming). You can print the report to a
hierarchical XML file, or save the report as a text file. In addition, you can set the
agent debug level and download the most recent agent and CM patches.
This utility is located at /<agentDirectory>/ctm/exe/ and can be run from either the
command line or as a Java application. For more information, see the CONTROL-M
Utility Guide.
15
Processes of elimination and
15
analysis
Prior to engaging in the more complex methods of diagnostic activity which require
you to work in conjunction with BMC Customer Support, there are certain tasks that
you can perform yourself, where applicable. These are described in this chapter.
You are also encouraged to find more information about problems with or questions
about a BMC products at the Customer Support website at
http://www.bmc.com/support_home. You can search the Knowledge Base for
existing product resolutions, documentation, and FAQs. You can also view or
download product documents, find answers to frequently asked questions, and
download products and maintenance. If you do not have access to the web and you
are in the United States or Canada, contact Customer Support at 800 537 1813.
Outside the United States or Canada, contact your local BMC office or agent.
NOTE
If the procedures for processes of elimination do not reveal a solution to or clear source of
whatever issue you are experiencing, please contact BMC Customer Support.
Also discussed are basic diagnostic procedures that can be performed so that the
resulting log files can indicate to BMC Customer Support upon initial contact what
the nature and scope of the problem could be.
Once you have established that the above functions are configured correctly, the need
to investigate further is justified.
NOTE
To end the communication trace, specify TRACE_DISABLE_ALL.
There are constant “downloading, download failed” error messages that repeat
cyclically.
NOTE
To end the communication trace, specify TRACE_DISABLE_ALL.
Gateway “bounces”
The Gateway status changes from Up to Down and back again, frequently.
NOTE
Due to the apparent instability of the Gateway, you cannot use the Control Shell functionality.
-dbg 3
This causes a timeout to occur. Such actions can include such issues as not seeing
updates after a certain action has been performed, or an upload (or download) not
succeeding or taking longer than usual.
NOTE
To end the communication trace, specify TRACE_DISABLE_ALL.
After setting these traces and recreating the situation, you should run the Health
Check utility to collect the relevant data. For more information, see Chapter 14,
“Collecting diagnostic data.”
NOTE
This issue can also occur with components other than the GUI Server.
1 In the CONTROL-M Configuration Manager, select the row that displays the
CONTROL-M/EM Configuration Agent details.
4 If the GUI Server now comes up, no further diagnostics is required. Otherwise,
proceed to the next possibility.
NOTE
This issue can also occur with components other than the GUI Server.
1 Examine the Database status, displayed at the bottom left corner of the
CONTROL-M Configuration Manager window.
3 If the GUI Server now comes up, no further diagnostics required. Otherwise,
proceed to the next possibility.
NOTE
This issue can also occur with components other than the GUI Server.
4 If the GUI Server now comes up, no further diagnostics required. Otherwise,
proceed to the next possibility.
1 Check that:
■ In Windows, the TAO NT Naming Service is started. If not, start this service.
■ On UNIX, run the check_ns_daemon script to check if the Naming Service is up.
If not, bring the Naming Service up by using the start_ns_daemon script.
2 If the GUI Server now comes up, no further diagnostics required. Otherwise,
contact BMC Customer Support for directions on the best way to diagnose, and
analyze this problem.
2 If you can now log on, no further diagnostics required. Otherwise, proceed to the
next possibility.
An error message is displayed indicating possible reasons why the GUI Server is
down.
2 If you can now log on, no further diagnostics required. Otherwise, proceed to the
next possibility.
NOTE
See also “The GUI Server does not “come up” when it should” on page 349.
This could be an isolated problem between the GUI Server and the database.
1 Check the GUI Server log for the most recent instance of the wording
vendorMessage, and for any messages displayed immediately after an “equals”
symbol (“=”). Contact your Database Administrator with this information.
After your Database Administrator has resolved the issues arising from these
messages, continue with step 2.
NOTE
It is advisable to run both the PINGDB and CHECKDB scripts, as they will enable more
information about the situation to be available.
2 If you can now log on, no further diagnostics required. Otherwise, contact BMC
Customer Support for directions on the best way to diagnose, and analyze this
problem.
Use this file to determine whether this is a single or multiple condition issue.
Or check to see if the expected condition is absent completely from the file.
This can also indicate other things, for example, a problem with the Gateway.
Heavy If there is an unusual flow of messages in the GCS_LOG file; for example, a
condition non-systematic flow with large numbers of timestamps that are very close
distribution together in chronology, or a large number of messages with the word
activity REJECTED included, or evidence that the same conditions were sent over and
over again.
This might indicate that specific conditions are affected, or that all conditions
are affected.
2 If the GCS_LOG file does not identify the problem, run the GCS_DIAG diagnostic
procedure, and recreate the situation. Also, contact BMC Customer Support for
directions on the best way to diagnose, and analyze this problem.
3 If after this you have still not identified the problem or how to treat it, you have
two further options, which you can do in conjunction with BMC Customer
Support
■ Advance the diagnostic settings for the GCS and relevant Gateways, then run
the Health Check utility and recreate the situation.
EXCEPTION, TAO_Naming_Server::init
system exception, ID
'IDL:omg.org/CORBA/BAD_PARAM:1.0'
EXCEPTION, TAO_Naming_Server::init
system exception, ID
'IDL:omg.org/CORBA/BAD_PARAM:1.0'
EXCEPTION, TAO_Naming_Server::init
system exception, ID
'IDL:omg.org/CORBA/BAD_PARAM:1.0'
■ TIME_WAIT
■ FIN_WAIT_2
■ CLOSE_WAIT
Note: Use the netstat –na command to see the status of the
port.
Example
A valid endpoint value of a CORBA server which is set to
listen on port 4444 is:
–iiop://:4444/reuse_addr=0
system exception, ID
'IDL:omg.org/CORBA/INITIALIZE:1.0'
■ working directory
■ system32
■ PATH
catior -f name_of_file_containing_IOR_or_IOR_itself
You will obtain information about the object's reference, including the port number.
Use this procedure to ensure an application is actually listening on the port you
specified in the orbconfigure GUI Ports panel. If the port is not the one you specified,
the process probably was not recycled after the port was assigned.
■ When you run the CLI and Sweep utilities, the operations are completed, but the
utilities do not respond.
Problem
The GUI Server attempts to communicate with the CONTROL-M/EM GUI using an
IP address that is not accessible and therefore the callback action fails.
Initially, the CONTROL-M/EM GUI sends an IP address it wants the GUI Server to
use when talking back to it in the IOR (IOR is a CORBA term). This is a random IP
address received from the operating system.
However, if the computer on which the CONTROL-M/EM GUI is installed has either
multiple network adapters or uses VPN or NAT, the IP address that the
CONTROL-M/EM GUI gives the GUI Server might not be the correct one, and as a
result, the callback action fails.
The failed callback action cannot be resolved by using the CONTROL-M/EM GUI
host name instead of the GUI Server's because the CONTROL-M/EM GUI host name
might not be resolved successfully (for example, when using VPN), and it will not be
sent to the GUI Server as expected. The GUI Server's host name, however, is always
accessible to a CONTROL-M/EM GUI, therefore, the valid host name (the GUI
Server) is used instead.
Previously, you had to identify what the correct IP address is and then configure the
CONTROL-M/EM GUI to publish that IP address. The IP address can change
regularly and, since there might be more than one IP address from which to choose, it
is difficult to know which is the correct one.
Once you identify the correct IP address, the change is made using the orbadmin
utility or the orbconfigure application, causing the CONTROL-M/EM GUI to
advertise a known and accessible address.
When communication between the CONTROL-M/EM GUI and the GUI Server is
not bidirectional
Use the following procedure to tell the client application which IP address to prefer to
publish by specifying the preferred subnet mask. Using this method, you do not have
to specify the exact IP address generated dynamically, which might change upon
every VPN connection.
Once you have the subnet mask, you can specify the $IP variable, which the
application replaces during runtime using the specified subnet mask.
1 Identify the subnet mask of the dynamic IP addresses generated by the VPN
adapter or additional interface.
B Disconnect and reconnect to the network or VPN and note the IP address.
EXAMPLE
If the first time you connected the IP address was 192.68.12.6 and the second time you
connected the IP address was 192.68.12.24, your subnet mask is 192.68.12.0
2 Add the -PreferIPMask parameter to the config.xml file, using the following
orbadmin command:
Adding this variable to the default scope enables the other scopes to inherit the
information.
NOTE
You can define the -ORBListenEndpoints parameter in the default scope instead of each
individual scope (similar to the -PreferIPMask), but you must make sure to remove the
-ORBListenEndpoints parameter from the other scopes (GUI, CLI, sweep, and Desktop) so
as not to overwrite the value in the default scope.
The $IP variable receives its value according to the -PreferIPMask parameter. The
application publishes the first IP address that matches the subnet specified in
-PreferIPMask.
NOTE
If no IP address matches the specified subnet or the -PreferIPMask parameter is not
defined, $IP is set to the default IP address associated with the computer’s hostname.
This way there is no need to modify the configuration when you are not using the
VPN or other network adapter.
In the CORBA implementation used in CONTROL-M/EM, both the client and server
exchange their host names and try to access each other using them. If another
computer tries to access the computer with the alias, the call fails.
For some cases, adding the alias to every single computer’s /etc/hosts file helps. In
other cases, network concerns make this impossible. In this case, the preferable
solution is to define an alias on DNS/NIS, and then configure CONTROL-M/EM
with this alias. If this is not desirable, you can switch to using IP addresses instead.
If a dynamic interface is available to the system, you might need to explicitly specify
that CORBA should use that interface in the first page (listening interface) of the
orbconfigure GUI.
Troubleshoot firewall problems by looking at the messages in the firewall log. The
firewall should log traffic incoming to and outgoing from the suspect computer.
Consult the firewall vendor’s manual.
In rare cases, other network devices, including secondary firewalls, might interfere
with traffic. Contact your System Administrator and make sure this is not the case.
The existence of NAT in a network does not necessarily cause a problem. However,
the requirements described below are necessary when IP addresses for the same
computer are different on the client and server side.
All the following conditions must be true when choosing a host name for a computer
that communicates via CORBA in a NAT environment:
■ The server must know itself by the host name chosen for it.
■ Each client must know the server by that same host name.
■ Each client must know itself by the host name chosen for it.
■ The server must be able to see each client using that client’s chosen host name
NOTE
Variations such as myserver, myserver.domain and myserver.domain.com are not considered
to be the same host name.
For example, if a client is called client1, the command ping client1 must work both
on the client and server side.
If these requirements are met, configure the CONTROL-M/EM servers and clients to
use host names or virtual host names as required.
orbadmin ns status
2 Check the Naming Service corbaloc reference by using the following command:
3 Find the full path of the entry you require to delete by using the following
command:
orbadmin ns list
NOTE
The -nsdel command deletes all entries from the "--name" specified and below it.
Example
-nsdel -ORBInitRef NameService=corbaloc::1.2@lotus:13075/NameService --name “BMC
Software/ECS/GUI”
Normally there is no need to use the -nsdel command and manually delete entries
from the Naming Service, as servers clean their references when they shut down.
However, in cases where servers are stopped without the chance to clean up their
references, the problematic references will stay in the Naming Service repository.
orbadmin ns start
This command attempts to start the Naming Service and then attempts to resolve it
to verify that the process is running and ready to answer for requests.
2 To make sure that the failure reported by orbadmin was not a result of a short
resolve timeout, use the following command:
orbadmin ns status
The Naming Service does not accept certain CONTROL-M/EM parameters, such
as:
■ -BiDirPolicy
■ -APPSSL
■ -ThreadPoolSize
■ -RTTimeoutPolicy
iiop://hostname:13075
To make sure that this endpoint value is valid, that the port is free and that the
network interface is valid and identified
nslookup <hostname>
If nslookup fails, the computer does not identify itself as the network interface
specified in the endpoint (in this case, the computer's short hostname).
1 Allow the Naming Service to listen on all available network interfaces by removing
the listening host from the endpoint value by using the following command:
2 Make sure that the other servers running on this computer are accessible in the
network.
3 Find out which network interface is identified (the computer's explicit IP address,
a Fully Qualified Domain Name (FQDN), and so on).
4 Use the orbconfigure utility to set this valid value as the virtual hostname in the
Published address drop-down list.
If the steps above still do not solve the problem, send the output of the above steps
(including <logfile_fullpath>) plus the information detailed below to BMC Customer
Support.
generate_ior | catior –x
This command generates a dummy IOR, and then displays it after it has been parsed
by catior.
Examine the hostname. It is likely that it is different from the hostname you are using.
Example 1
The computer with a hostname of banzai was called the same IP address in NIS
(nslookup from a UNIX computer).
However, only banzai was mapped in the DNS windows computers are using.
Workaround
2 Add the mapping of the missing hostname to the Fully Qualified Domain Name
(FQDN).
Example 2
172.16.131.190 spot.isr.bmc.com
The -RTTimeoutPolicy parameter defines the maximum interval between the time a
client sends a request to a server until the time the reply is received by the client.
Relative round-trip timeouts are useful when the client requires short request-reply
intervals.
The GSR, as a client of the GUI (opening Viewpoints and invoking other types of
callback requests), does not tolerate slow servers or GUIs, as they affect its
performance adversely.
Setting a timeout value for a GUI Server affects only requests that the GUI Server
invokes as a CORBA client.
■ sending results of a callback action, such as Upload Table or Holding an active job
If the GUI, CLI, or the CONTROL-M/Desktop do not return a reply within the
timeout interval, a CORBA::TIMEOUT is raised on the server side, communication
with the slow client terminates, and a USER_NOT_FOUND exception is received on
the client side.
To prevent disconnections from slow clients, set the GSR AddJobsChunkSize system
parameter to 100 (the default chunk size is 1000).
Alternatively, modify the timeout value in the GSR scope (on the GSR computer) by
using the following command:
NOTE
BMC recommends decreasing the chunk size instead of increasing the timeout value.
Increasing the timeout may decrease the GSR's performance and memory efficiency since it
now tolerates slower clients and will take more time for it to identify "dead" clients that did
not disconnect properly.
If one or more parameters are not configured correctly, the parameters are listed
followed by:
Check kernel configuration for <system> terminated unsuccessfully
Check directory Checks the current directory and all sub-directories under it for permissions.
permissions
Reset Clears all components of the CONTROL-M/Server active environment (Active Jobs
CONTROL-M file, prerequisite conditions, and so on) and forces CONTROL-M/Server to start a
Active download of the entire Active Jobs file to CONTROL-M/EM. This option is described
Environment on page 369.
Truncate Database [UNIX only] [Sybase only] Truncates the CONTROL-M/Server database log. This
Log option should be used if the Sybase message “Can’t allocate space for <text> in
database <name> because the log segment is full” occurs in one of the log files located
in directory $CONTROLM_SERVER/proclog. Note: Option 8 only appears for
CONTROL-M/Server on UNIX.
Set Sleep Time Determines the sleep time for all CONTROL-M/Server processes or for any specific
process. For more information, see page 368.
Force Download Forces CONTROL-M/Server to start download of the entire Active Jobs file to
CONTROL-M/EM.
Quit Quits the Troubleshooting menu and returns to the CONTROL-M Main Menu.
Specify the desired sleep time (in seconds), and then specify the two-character code
for a specific process, or ALL for all CONTROL-M/Server processes.
NOTE
Shut down CONTROL-M/Server before selecting this option.
When selected from the Troubleshooting menu, the Reset CONTROL-M Active
Environment option performs the following actions (after confirmation by you):
It is also possible to reset the CONTROL-M/Server process sleep times and trace
level using the init_prflag utility. This utility performs the following actions:
■ The sleep times for all CONTROL-M/Server processes are reset to their initial
(installation) values.
Process of elimination
This section describes some of the more common checks that can be executed by you
prior to contacting BMC Customer Support. Some of these checks use a process of
elimination to attempt to determine the cause of a problem.
In cases where the cause of issues cannot be remedied relatively simply, also
discussed are basic diagnostic procedures that can be performed so that the resulting
log files can indicate to BMC Customer Support upon initial contact what the nature
and scope of the problem could be.
Below are described some common issues that occur, and the processes of elimination
that should be observed before taking diagnostic activity to the next level.
CTM_diag_comm <agentName>
■ If the computer where the agent resides cannot be reached, check the agent
name, or consult your IT department.
■ If the computer where the agent resides can be reached, but the agent itself
cannot be reached, then make sure that the value of the Server to Agent
parameter, on both CONTROL-M/Server and CONTROL-M/Agent, is the
same. If the value of this parameter is the same, then check that the
CONTROL-M/Server name exists in the Permitted server list in the
CONTROL-M/Agent.
1 On the CONTROL-M/Agent where the job was invoked run the following
command
ag_ping <serverName>
■ Ensure that the value of the Agent to Server parameter is the same on both
CONTROL-M/Server and CONTROL-M/Agent.
2 Re-start CONTROL-M/Server.
The environment variable for the logs is $ECS_LOG_PATH. The number and length of
cyclical log files are determined initialization file parameters for the monitored
component. When the last cyclical log file is full, DIAG removes the oldest file and
begins a new one.
Log files have a special naming convention that enables you to identify them readily:
■ If more than one GUI Server or Global Alerts Server exists, the format of the log file
for these components contains the name of the server immediately after the host
name. For example: gsr_log.host1.{GUI_Server_Name}.20040705.# 0282.txt
■ The 4-digit serial number for each file is incremented by 1 for successive files.
■ In UNIX: EMHome/log/
gtw_log.Control-M_name.date.num
GCS_LOG files
Diagnostic activity can be seen in the permanent GCS_LOG file for each process.
These log files show the flow of the conditions, their source and destination, when
each condition was sent, and all messages regarding condition activities. There are
four types of messages:
■ msg_diag: Types of message packets (dsects) that are displayed and written to the
GCS_LOG file. Condition transfer requests and messages related to inter-process
communication activities are displayed.
You can set the levels of what these messages should report and at what level of
detail, by accessing their corresponding system parameters. For more information,
see Appendix B, “System parameters.”
C< RECEIVING COND 09:50:07.139: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB
D> INSERT MSG:: 09:50:07.148: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <id> 1
D> INSERT DST 09:50:07.155: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB:: <dst> AAA <id> 1
D> INSERT DST 09:50:07.157: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB:: <dst> AAB <id> 1
I> SEND COND ATTEMPT 09:50:07.213: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAA
<tryno> 0
C> SENDING COND 09:50:07.213: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAA <tryno> 1::
<msg> CR08/18/387DABGCSERV 0009COND_15011104+
I< PENDING ACKNOWLEDGE 09:50:07.213: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAA
<tryno> 1
I> SEND COND ATTEMPT 09:50:07.213: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAB
<tryno> 0
C> SENDING COND 09:50:07.213: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAB <tryno> 1::
<msg> CR08/18/390DABGCSERV 0009COND_15011104+
I< PENDING ACKNOWLEDGE 09:50:07.214: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAB
<tryno> 1
C< RECEIVING COND 09:50:07.501: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> AAA
C< RECEIVING COND 09:50:07.534: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> AAB
I> COND REJECT 09:50:07.535: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> AAB <siid> 095007005
TOGGLED
C< RECV COND CONFIRMED 09:50:07.549: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAA
<tryno> 1
D> DELETE DST 09:50:07.552: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB:: <dst> AAA <id> 1
C< RECV COND CONFIRMED 09:50:07.662: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <dst> AAB
<tryno> 1
D> DELETE DST 09:50:07.665: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB:: <dst> AAB <id> 1
D> DELETE MSG:: 09:50:07.666: 1109 <cnd> COND_1501 <odat> 1104 <op> + <dc> DAB <id> 1
The global conditions traffic trace log can be configured to include the following
types of information:
■ Condition name, originating datacenter, destination datacenter, odate, add or
delete indicator, a timestamp, and other diagnostic data (see Table 67 on page 375).
■ Conditions arriving from gateways
The tracing message format facilitates problem tracking. The format supports
scripting and automation of research activities.
The Action code indicates the type of action associated with the problem.Each log
record includes one of the following action codes:
The Timestamp contains the date and time of the log record in
yyyymmddhhmmssms format.
The Data Flag indicates the type of information that follows the flag, and contains
one or more of the following data flags.
The Data file is the information of the type indicated by the Data Flag that precedes it.
NOTE
The maximum number of alerts that are displayed is determined by the
MaxXAlerts2Send2Client system parameter. If the number of alerts in the database is greater
than the number of alerts determined in the system parameter, a message is displayed in the
status bar. For more information, see “Exception handling parameters” on page 447.
To display alerts
1 In the CONTROL-M Configuration Manager, choose Tools -> Exception Alerts. The
Exception Alerts window opens.
■ To filter the alerts displayed in the Exception Alerts window, choose View ->
Alerts Filter and the criteria by which you want to filter.
■ To group the alerts in a hierarchical tree, choose View -> Alerts Group. Drag the
header column by which you want to group the alerts into the grouping area.
Repeat this procedure to group by additional columns.
■ To refresh the display, choose View -> Refresh. To set an interval at which the
display will automatically refresh, choose Tools -> Options and enter a value (in
seconds) for the refresh interval.
■ To export the alerts to a file, choose File -> Export and enter a file name and file
type.
■ To delete old alerts currently displayed in the Exception Alerts window, choose
Tools -> Remove Old Alerts and enter a value.
NOTE
Normally, alerts are removed based on the value set in the XAlertsMaxAge system
parameter. The Remove Old Alerts window does not update the value in the
XAlertsMaxAge system parameter. For more information, see “Exception handling
parameters” on page 447.
■ To view the details of a specific alert, select the alert and then choose X-Alert ->
Properties. The Alert Properties window appears showing additional
information for the specific alert.
To add a note to an alert, type the note in the Note field in the Properties window of
the alert.
Appendix A
Configuring CORBA components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Appendix B
System parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Appendix C
Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Appendix D
SNMP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Appendix E
Mass conversion of agents and remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
A
A Configuring CORBA components
This appendix presents the following topics:
Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
CORBA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Naming Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
What is an Interoperable Object Reference (IOR)? . . . . . . . . . . . . . . . . . . . . . . . . . 386
Advanced communication policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Assigning ports when using a firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
XML configuration file scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Recommended task summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Configuring CORBA components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Specifying domain settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Specifying Naming Service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Assigning ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Specifying Advanced parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Concepts
Figure 29 highlights the basic recommended workflow for connecting
CONTROL-M/Enterprise Manager components. This overview section explains
concepts that are related to the workflow.
For specific tasks that correspond to each phase of the workflow, see Table 69 on
page 392. Following the table, the remainder of the chapter provides step-by-step
instructions for completing the tasks.
Specify domain
settings
page 393
Assign
ports
page 398
Specify advanced
parameters
page 399
CORBA overview
Many CONTROL-M/EM server and client components communicate using the
CORBA (Common Object Request Broker Architecture) communication protocol created
by the Object Management Group to enable application components that are
distributed across a network to communicate with one another.
— GUI server
— GAS server
— CONTROL-M/Forecast server
— BMC Batch Impact Manager server
— CMS server (Configuration manager server)
— CONTROL-M/EM GUI
— CONTROL-M/Desktop
— CONTROL-M Reporting facility
— CONTROL-M Configuration Manager
— cli utility
— Sweep command line utility
— XML utilities
There might, however, be situations where the administrator will want to set or
modify CORBA configurations. The following are the more common situations:
Naming Service
The Naming Service runs in background mode based on parameter values stored in
the XML CORBA configuration file.
■ Listening port
If the configuration is changed, run the following commands to recycle the Naming
Service and update the information in the registry:
orbadmin ns stop
orbadmin ns start
NOTE
On Windows the Naming Service can be stopped only from the Services window. The
orbadmin ns stop command can not stop the Naming Service, because the CONTROL-M
Configuration Server depends on it.
Description
The CORBA Naming Service provides a tree-like directory for remote objects much
like a file system provides a directory structure for files.
To resolve a name is to determine the object associated with the name in a given
context. To bind a name is to create a name binding in a given context. A name is
always resolved relative to a context – there are no absolute names.
Because a context is like any other object, it can also be bound to a name in a naming
context. Binding contexts in other contexts creates a naming graph – a directed graph
with nodes and labeled edges where the nodes are contexts. A naming graph allows
complex names to reference an object. Given a context in a naming graph, a sequence
of names can reference an object. This sequence of names (called a compound name)
defines a path in the naming graph to navigate the resolution process.
The tree starts with a root node, it may have intermediate nodes, and it ends with the
actual objects stored by name at the leaves of the tree. The fully qualified name of an
object is the ordered list of its parent nodes, starting with the root node and ending
with the name of the object.
Figure 30 shows how three objects might be stored in a Naming Service directory. In
this illustration, the full name of the UserManager is BMC Software, ECS, palace, GAS,
UserManager.
BMC Software
ECS
hostname | EM_NAMING_CONTEXT
GSR | GAS
ObjectNameA IOR
ObjectNameB IOR
ObjectNameC IOR
Each CORBA client resolves the Naming Service to get the server's object references
so it can connect to the server directly. If the Naming Service is not found, an error
message is displayed (for example, the list of server names in the Login dialog box is
disabled to indicate no server contexts could be found).
CORBA clients search for the server name under the hierarchy described above and
get the IORs. Applications that refer to an object can invoke calls to that object.
NOTE
CORBA applications (both clients and servers) try to resolve the Naming Service according to
the value of the –ORBInitRef parameter that was previously specified in the config.xml file
and passed to the application during initialization.
Repository
The Naming Service saves the naming structure (including contexts and the objects
hierarchy) in readable data files under the $ECS_HOME/var directory.
See “Naming Service problems” on page 353 for information about the following:
■ Invalid Repository directory
CORBA uses IORs as the universal means of identifying an object. Object references
are opaque to the client-side application code and completely encapsulate everything
that is necessary to send requests, including the transport and protocol to be used.
Repository ID
The repository ID is a string that identifies the most derived type of the IOR at the
time the IOR was created. The repository ID enables you to locate a detailed
description of the interface in the Interface Repository (if the ORB provides one). The
ORB can also use the repository ID to implement type-safe down-casts.
Endpoint information
This field contains the information required by the ORB to establish a physical
connection to the server implementing the object. The endpoint information specifies
which protocol to use and contains physical addressing information appropriate for a
particular transport.
EXAMPLE
For the IIOP, the endpoint information contains an Internet domain name or IP address and a
TCP port number.
The endpoint information field may contain the address and port number of the
server that implements the object. However, in most cases, it contains the address of
an implementation repository that can be consulted to locate the correct server. This
extra level of reference permits server processes to migrate from computer to
computer without breaking existing references held by clients.
Object key
The object key contains proprietary information. All ORBs allow the server to embed
an application-specific object identifier inside the object key when the server creates
the reference. This object identifier is used by the server-side ORB and object adapter
to identify the target object in the server for each request it receives.
The client-side sends the object key as a string of binary data with every request it
makes. Therefore, it does not matter that the reference data is in a proprietary format.
It is never looked at by any ORB except the ORB hosting the target object (which is
the same ORB that created the object key).
The combination of endpoint information and object key can appear multiple times in
an IOR. Multiple endpoint-key pairs, known as multicomponent profiles, permit an
IOR to efficiently support more than one protocol and transport that share
information. An IOR can also contain multiple profiles, each containing separate
protocol and transport information. The ORB run time dynamically selects which
protocol to use depending on what is supported by both client and server.
“Stringified” IOR
A typical stringified IOR is illustrated here:
IOR:010000001400000049444c3a557365724d616e616765723a312e3000010000000000000
0680000000101020006000000766572656400e6cc2300000014010f004e5354416e6393000e
d6c700000001000000010000000100000001000000020002000000000000000800000000360
a0a54414f00010000001400000000360a0a00010001000000000001010900000000
You can obtain an object IOR by following the procedure described under “How to
verify that a CORBA server is listening on port X” on page 357.
Decoding an IOR
The catior utility accesses a stringified IOR, extracts and decodes readable
information from it, and prints the data to the standard output device.
Usage: catior -f filename
EXAMPLE
catior dumps the following output for the Stringified IOR shown above:
Host specification
CORBA Servers listen for clients requests on a specific interface specified by endpoint
-ORBListenEndpoints.
■ For multiple network cards, you can set a specific IP address to listen on, instead of
using the default IP address.
■ To create an endpoint on each network interface, omit the address from the
endpoint specification. The selected port is the same for all endpoints. A static port
or port range can also be specified for this type of endpoint. Network interface
detection only works on platforms that support this feature. If network interface
detection is not supported, the default network interface is selected.
In the Domain Settings panel of the Domain Configuration window, select the
correct address policy from the drop down list next to Listening host/address.
Bidirectional IIOP
Bidirectional IIOP
CORBA 2.3 added GIOP 1.2 and IIOP 1.2 to enable bidirectional communication. This
allows client and server to reverse roles without opening a separate connection that
may be blocked by a firewall. Therefore, bidirectional communication is important
for communication through firewalls.
For example, The Callback mechanism requires a server to also act as a client. GIOP
1.2 allows the server to initiate requests on the connection that was opened by the
client. This means that the server does not have to open a separate connection for a
callback, only to find itself blocked by a firewall.
NOTE
Bidirectional communication is enabled only if both client and server agree to use it.
NOTE
A CORBA server using a bidirectional policy can establish a connection with CORBA clients
that do not use a bidirectional policy. However, the server will use a separate connection for
callbacks.
You can set a relative round-trip timeout at the client ORB level by adding a
parameter to the configuration file in the relevant application scope.
EXAMPLE
To set a timeout of 10,000 milliseconds for the GUI application, use the command:
orbadmin variable modify -scope GUI -value 10000 -RTTimeoutPolicy
and restart the GUI.
All requests made using these settings will timeout if a reply is not received within
10,000 milliseconds. When a timeout occurs, the ORB will raise a CORBA::TIMEOUT
system exception. If a reply eventually arrives after the timeout period has expired, it
will be discarded by the client ORB.
If you set a timeout value for a CORBA Server, it will have an effect only if that
CORBA Server is also a CORBA Client.
Therefore, setting a timeout value for a GUI Server affects only requests the GUI
Server invokes as a CORBA client. Examples of such requests are:
■ updating the GUI with Viewpoint information.
■ sending results of a callback action, such as Upload Table or Holding an active job.
If the GUI or the Desktop does not return a reply within the timeout interval, a
CORBA::TIMEOUT is raised on the server side, communication with the slow client
(GUI, CONTROL-M/Desktop, or CLI) terminates, and a USER_NOT_FOUND
exception is received on the client side.
Setting a timeout value for GAS has no effect because the GAS does not function as a
CORBA client using callback objects.
When working with firewalls, assign a static port or a range of ports to each
CONTROL-M/EM application instead of using the default setting: random ports.
BMC Software recommends setting a range of ports for client applications such as the
CONTROL-M/EM GUI, Desktop and CLI, so that more than one session can run
simultaneously on the same machine.
The assigned ports should be open for incoming connections. All ports should be
open for outgoing connections on the client’s side. However, if both sides are using
bidirectional IIOP, there is no need to open all ports for outgoing connections on the
server’s side as well.
The scope named “default” contains parameter settings that apply to all scopes
(except the Naming Service scope, named ns) unless overridden by other scopes.
NOTE
Configuration changes made to running processes do not take effect until you recycle the
component.
WARNING
The orbconfigure wizard and orbadmin utility do not lock records while changing the
configuration file. Therefore, running multiple sessions of orbconfigure or orbadmin at the
same time can corrupt the local configuration.
A Ensure you have JRE version 1.4.1 or higher installed on your computer.
NOTE
java_home refers to the directory where the Java 2 Runtime Environment (JRE) was
installed. The Java 2 SDK (also called the JDK) contains the JRE, but at a different level in
the file hierarchy. For example, if the Java 2 SDK or JRE was installed in /home/user1,
java_home would be:
/home/user1/jre1.4.x [JRE]
/home/user1/jdk1.4.x/jre [SDK]
D Start the Domain Configuration (orbconfigure) wizard with one of the following
commands. This displays the Domain Settings panel of the wizard.
■ [UNIX] orbconfigure
■ [Windows] orbconfigure.vbs
■ To configure an existing domain, choose the domain name in the Domain Name
field drop down list.
2. In the New Domain dialog box, specify the new domain name click OK.
3 In the Listening Address field, select one of the following hostname addresses
where listening should take place:
■ All – All CORBA servers listen on all available network interfaces. This policy is
the default and is recommended for computers with multiple network adapters.
■ IP address – Select the IP address from the drop down list.
■ Short hostname – The value is displayed in a “read-only” text box.
■ Other – Specify the host/address in the adjacent text box or leave it empty. If
you leave it empty, this option is similar to All.
4 In the Published address field, select the appropriate object address type, and
where necessary, specify the appropriate value in the accompanying field:
■ Default (hostname)
■ IP address – If you select this value, select the IP address from the
accompanying drop down list.
■ Short hostname – The value is displayed in a “read only” textbox.
■ Fully qualified hostname – Specify the fully qualified host name in the text box.
■ Virtual hostname – Specify the virtual host name in the adjacent text box.
■ localhost
■ 127.0.0.1
CORBA clients obtain IORs to invoke requests on object references. The IOR
contains endpoint information, that is, the host and port number at which the
server listens for requests. The host can be encoded either in dotted-decimal
notation (such as 234.234.234.234) or as a host name (such as yoursite.com).
By default, the hostname published in the IOR is the default hostname returned by
system call gethostbyaddr().
The hostname encoded in the server’s IOR must be accessible for clients:
■ If clients can reach the server only by an IP address, the server IORs must use
that IP address instead of the default hostname.
■ If clients can reach the server only by an FQDN (Fully Qualified Domain Name),
the server IORs must use that FQDN instead of the default hostname.
■ If the hostname IP address changes dynamically, server IORs must use a virtual
hostname and a DNS to translate the virtual hostname into a valid IP address.
5 To enable one port to be used for communication in both directions, select the
Bidirectional IIOP (Internet Inter-ORB Protocol) check box.
NOTE
If you use bidirectional IIOP, the client or server to which you connect must also use this
policy.
6 If you are using Secure Sockets Layer (SSL) protocol instead of TCP/IP, select the
SSL check box. For information about SSL, see the CONTROL-M SSL Guide.
7 To use an internal TAO configuration file to change the default behavior of TAO:
B In the following field, enter, or browse to and select, the full path and name of
the (client-server) svc.conf file. The default configuration file is called
client_server.conf and is in the $HOME/etc directory.
8 Either click Next to fill in the parameters in the next panel, or keep clicking Next
until you arrive at the Summary panel and then click Finish.
3 In the Host field, specify the name or IP address of the computer running the
CORBA Naming Service.
4 In the Port field, specify the listening port (digits only) of the Naming Service.
5 To check if communication with the CORBA Naming Service is enabled, click Test.
6 To display and possibly modify in which file the local Naming Service settings are
saved, click Show local settings.
The Repository files path is the directory in which the Naming Service saves the
contexts and objects registered in it (to provide consistency between Naming
Service runs).
■ To save settings in repository files, click Repository files path, you and specify
(or browse to and choose) an existing Repository file directory. The default path
is $HOME/var.
■ To save the settings in TAO internal configuration files, choose Use TAO
internal configuration file, you must specify (or browse to and choose) the
configuration file to be used (for example, if you are using SSL).
7 Either click Next to fill in the parameters in the next panel, or keep clicking Next
until you arrive at the Summary panel.
8 When you display the Summary panel (after the last step or after filling in
parameters in other panels), you must choose whether to install or remove the
Naming Service as a Windows service. (If the naming service is already installed
on your computer, the Install as Windows service check box is selected. Otherwise, it
will be blank.)
9 Click Finish.
Assigning ports
The Ports panel is often used for assigning ports when the applications are behind
firewalls.
NOTE
You do not need to assign ports across firewalls for client applications (CONTROL-M/EM
GUI, CONTROL-M/Desktop, cli utility) if you are using bidirectional IIOP. For more
information see “Bidirectional IIOP” on page 389.
The Ports panel enables you to specify port numbers for the following applications.
3 For each component for which you are assigning a port, select one of the following
values, and where needed, specify required additional information.
■ Random – This is the default value and is recommended if the component is not
behind a firewall. The operating system selects a free port automatically.
■ Static – This value is suitable if there is never more than one instance of the
component running at the same time.
■ Range – Recommended value for components behind a firewall. Two text boxes
are displayed. Specify the lowest and highest ports in these text boxes.
4 Click Next to display the Summary panel, and then click Finish.
NOTE
Check that components were not active when you assigned their ports. If components were
active, stop and restart the components for changes to take effect.
2 Click Next until the Summary panel is displayed. It lists the current Domain,
Naming Service, and Listening Ports settings.
3 Click Advanced to display the Advanced settings panel. This panel contains the
current CORBA domain configuration values in tree format.
You can perform the following actions in the Advanced settings panel:
■ Add a New scope to the configuration file.
NOTE
Right-click the relevant node in the CORBA configuration tree to display the pop-up menu.
Click the New, Edit, or Delete option to display the appropriate dialog box. Unavailable
options are dimmed (grayed out).
4 When you are done making the Advanced setting changes, press OK in the
Advanced settings panel.
5 To save the current domain configuration values in the CORBA configuration file,
click Finish in the Domain Configuration wizard.
B
B System parameters
This section presents the following topics:
Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Parameter modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Component refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Modifying CONTROL-M/EM system parameters . . . . . . . . . . . . . . . . . . . . . . . . 405
Modifying CONTROL-M/Server system parameters . . . . . . . . . . . . . . . . . . . . . . 406
Modifying CONTROL-M/Agent system parameters . . . . . . . . . . . . . . . . . . . . . . 409
Modifying CONTROL-M for z/OS system parameters . . . . . . . . . . . . . . . . . . . . 409
Refreshing CONTROL-M/EM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Refreshing CONTROL-M/Server components . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Refreshing CONTROL-M/Agent components. . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
System parameter reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
CONTROL-M/EM parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
CONTROL-M/Server parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
CONTROL-M/Agent parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Concepts
Customization of CONTROL-M components is largely performed by modifying
component system parameter values. You can choose whether to accept provided
default component system parameter values or modify them at or after installation.
When you modify system parameters, you must be concerned with two issues:
■ How do you modify the parameter? For more information, see Parameter
modification.
Parameter modification
How you modify system parameters is a function of several factors:
Component refresh
Before a modified parameter value can take effect, the component that uses the value
needs to be refreshed.
■ Recycle—You need to recycle (stop and restart) the component (for example,
CONTROL-M/Server) for the change to take effect.
■ Manual—You need to perform an action that refreshes the parameter value (with
no need for recycling the component).
Tasks
This section describes the following topics:
NOTE
This procedure applies to all CONTROL-M/EM system parameters, except certain GCS and
Gateway parameters that appear in the default.rsc file. For instructions on modifying
parameters in the default.rsc file, see “Editing the Defaults.rsc file” on page 405.
1 In the CONTROL-M Configuration Manager, choose Tools => System Parameters =>
CONTROL-M/EM System Parameters.
■ An * in the Component column indicates that the system parameter affects all
types of components.
■ The Host Name column indicates the host name of the affected component.
■ The default value is displayed; you can request to restore the default value.
■ The refresh type is displayed. This lets you know if you need to perform a
manual refresh or recycle (or if the component is automatically refreshed).
For example, by editing the appropriate parameters in this file, you can configure
maximum communication wait time between Gateway and other components,
handle multiple gateway instances for the same CONTROL-M iteration and
configure speed and efficiency of downloads (setting memory buffer).
■ On UNIX: home_directory/site/resource/Defaults.rsc
■ On Windows: home_directory\Gtwgcs\appl\site\resource\Defaults.rsc
1 - CONTROL-M Manager
2 - Database Creation
3 - Database Maintenance
4 - Database Mirroring
5 - Security Authorization
6 - Parameter Customization
7 - Node Group
q - Quit
4 Continue entering appropriate menu option numbers until the interactive display
lets you fill in appropriate values.
The following is a list of menu sequences appropriate for specific types of parameters.
System parameters
CONTROL-M Main Menu => Parameter Customization => System Parameters and Shout
Destination Tables => System Parameters
Communication parameters
CONTROL-M Main Menu => Parameter Customization => (one of the following):
Operational parameters
CONTROL-M Main Menu => Parameter Customization => (one of the following):
CONTROL-M Main Menu => Parameter Customization => Parameters for Communicating
with Agent Platforms
Database parameters
Mirroring parameters
■ Performance parameter
■ Configuration parameters
■ Watchdog process parameters
■ Heartbeat Monitor parameters
■ User Exit parameters
NOTE
There are parameters listed under “CONTROL-M/Server parameters” on page 453 (but
which do not appear in the shipped config.dat) for which you can change the value by adding
the parameter—set to the value that you need—to config.dat. For such parameters, the
How/where to set row includes a “See ‘Editing the config.dat file’” link.
NOTE
This procedure explains how to use the CONTROL-M Configuration Manager to change
CONTROL-M/Agent system parameters. Alternatively, you can run the following utilities:
The CONTROL-M for z/OS System Parameters dialog box displays the system
parameters and values for the selected CONTROL-M. Note the following points
about the displayed columns:
NOTE
Ensure that your specified values (content and length) conform to product rules. The
values are checked against product rules when you save your modifications.
Changes are saved but CONTROL-M is not refreshed until you perform step 3.
NOTE
The type of refresh (automatic, manual, or recycle) required by CONTROL-M/EM system
parameters is listed in the detail line for each parameter in the System Parameters dialog box
in CONTROL-M Configuration Manager.
1 In the Configuration Manager, right-click the component (for example, the GUI
server), and choose Control Shell.
2 In the Control Shell dialog box, enter the appropriate REFRESH command and
click Apply.
EXAMPLE
After modifying CONTROL-M/EM job version management parameters
1. In the CONTROL-M Configuration Manager, right-click the GUI Server component and
choose Control Shell.
2. In the Control Shell dialog box, enter the REFRESH_HISTORY command and click
Apply.
Alternatively, you can refresh a component by entering the relevant line command.
For example, to apply changes to the GUI Server, you can use the following
command:
For some system parameters, you can update a running CONTROL-M/Server with
parameter changes by sending a refresh message to all CONTROL-M/Server
processes. In this case, you do not have to recycle CONTROL-M/Server. In the tables
under “CONTROL-M/Server parameters” on page 453, the Refresh Type indication
for such parameters is Manual.
For other system parameters, you must recycle (see Recycling CONTROL-M/Server
components) the relevant CONTROL-M/Server process for the changed parameter
values to take effect. The relevant process that requires recycling might be any of the
following:
■ CONTROL-M/Server (ctm/server)
■ CONTROL-M Configuration Agent (ctm/CA)
WARNING
Recycle a CONTROL-M/Server component only when stopping and starting that component
will not negatively impact processing in your production environment.
■ CONTROL-M/EM parameters
■ CONTROL-M/Server parameters
■ CONTROL-M/Agent parameters
CONTROL-M/EM parameters
The CONTROL-M/EM parameters influence the behavior of a wide range of
CONTROL-M/EM components and features. This section lists and describes the
following categories of CONTROL-M/EM parameters:
NOTE
For information on BMC Batch Impact Manager and CONTROL-M/Forecast parameters, see
the Business Service Management Solutions User Guide.
System parameters are modified using the System Parameters window of the
CONTROL-M Configuration Manager. For more information, see “Modifying
CONTROL-M/EM system parameters” on page 405.
NOTE
System parameters related to BMC Batch Impact Manager are described in the Business Service
Management Solutions User Guide.
General parameters
NOTE
After modifying these general parameters, stop and restart all Gateway components for the
changes to take effect.
Default: N
AllowListEMUserNames Determines whether users can view a list of user names (used by
CONTROL-M Control Module for Advanced File Transfer
configuration plug-in).
Valid values:
■ 0 - Not permitted
■ 1 - Permitted (default).
Valid values:
■ 0 - Only administrators are allowed to create reports (default)
■ 1 - All users are allowed to create reports
Valid values:
■ 0 - Disabled
■ 1 - Feature enabled
Valid values:
■ 0 - Disabled
■ 1 - Feature enabled (default)
Valid values:
■ 0: Cleanup is performed manually by the user as necessary
■ 1: Cleanup is automatic
Default: 1
Minimum value: 1
Default: 1
AuthenticationMethod Name of the external authentication plug-in.
Default: 100
bulk_def_storage_len Default value for storage length in bulk operation. Must be at least as
long as the longest field involved in the bulk operation.
Default: 264
ChallengeResponseTimeout Time interval in seconds after the server issues a challenge during
which a response received from the client will be accepted. If a response
is not received during this interval, the server sends a FAILURE
message and terminates the communication.
Default: 60
CGSCommUserIGd ID that GCS uses to identify itself to CONTROL-M. This user must be
defined in the CONTROL-M with add or delete condition privileges.
Default: GCSERV
CmsCtmNGRefreshInterval Sets the refresh interval in seconds for collecting node group data.
Default: 900
DatabaseCheckInterval Amount of time between database availability checks by certain server
components.
Default: 10
DatabasePoolSize Determines the maximum number of connections to the database
retained in the connection pool of each server component.
Default: 5
Default: 10
DatabaseRetryInterval The amount of time between the attempts detailed in DatabaseRetries.
Default: 10
DefaultAverageTime Average run time for jobs with no statistics. In the format HH:MM. This
value is often used if no statistics are available.
Default: 00:05
DeleteChunkSize Maximum number of rows to be deleted by a single SQL statement,
used by purge_runinfo and erase_audit_data scripts.
Default: 10000
Valid values:
■ PrepExt
■ On
■ PrepInt
■ Off
Default: Off
Default: <null>
Valid values:
■ TCP
■ SSL
Default: TCP
HandleAlertsOnRerun Determines how to handle alerts when a job is rerun.
Valid values:
■ 0 – Alerts for this job that are in the Alerts window before the job is
rerun are not automatically changed to HANDLED. If the rerun
fails, a new alert is displayed in the Alerts window.
■ 1 – Alerts for this job that are in the Alerts window before the job is
rerun are automatically changed to HANDLED.
Default: 0
HostPort Host name and port number for a specified component. This parameter
can have multiple values, each related to a different component or a
different host computer.
Default: null
Valid values:
■ cjk
■ latin1
Valid values:
■ use_account_locale — language set for the account and computer
us_english
■ english
■ german
■ french
■ spanish
Default: use_account_locale
LimitGCDistribActivate Enables and disables limitations on the distribution of global conditions
using the Global Conditions Distribution facility.
Valid values:
■ _ 1 – The Global Conditions Distribution facility distributes global
conditions according to limitations defined using the
LimitGCSDistribMaxDays and LimitGCSDistribExcludeDates
parameters.
■ _ 0 – The Global Conditions Distribution facility imposes no
limitations on the distribution of global conditions.
Default: _1
LimitGCDistribExcludeDates Dates for which global conditions are distributed, regardless of
limitations specified using the LimitGCSDistribMaxDays parameter.
Dates are specified in mmdd format and separated with commas.
Default: STAT
LimitGCDistribMaxDays The range of days within which conditions can be distributed.
Default: 7
LMGUI_Communication_Cfg License Manager address. Not yet implemented.
Default: null
LockAccountForMinutes Time interval, in minutes, after which an account that was
automatically locked is automatically unlocked. (Accounts locked by an
administrator are not unlocked automatically.)
Default: 0
Default: 2000
MaxPasswordLength The maximum number of characters for user passwords.
Default: 32
MaxUpdatedJobsToAudit Maximum number of updated jobs recorded in the Audit log when
writing a scheduling table to the CONTROL-M/EM database. If this
number is exceeded, or if any job in the scheduling table is added or
deleted, only one audit record is recorded at scheduling table level and
audit data is not recorded at the job level.
Default: 25
MinPasswordLength The minimum number of characters for user passwords.
Default: 6
NrHandledAlarms The maximum number of handled alerts saved in the database
(in addition to not-yet-handled alerts).
Default: 2000
Default: 10
PasswordComplexityOnOff Indicates if passwords need to comply with complexity rules.
Valid values:
■ 0 (no = off)
■ 1 (yes = on)
Default: 0
PasswordComplexityRules One, some, or all of the following values separated by a blank space.
Multiple values are joined by AND logic.
Valid values:
■ PWD_DIGIT: using digits is mandatory
■ PWD_UPPER: using letters in upper case is mandatory
■ PWD_LOW: using letters in lower case is mandatory
■ PWD_NON_LETDIG: non-alphanumeric characters are
mandatory
■ PWD_DIGIT PWD_UPPER PWD_LOW PWD_NON_LETDIG: all
of these rules to be satisfied. (Default)
PasswordEncode Indicates how user passwords are transmitted by clients to the server.
For more information, see “Authentication methods” on page 151.
Valid values:
■ 0 - Clear text (not encoded). Often used with External
Authentication.
■ 1 - Encrypted by the client.
■ 2 - Challenge-response. Recommended if SSL is not used.
Default: 2
Valid values:
■ 0 (off, password expiration is not checked).
Default: 0
PasswordHistoryOnOff Determines whether password history is recorded.
Valid values:
■ 0 (no). If set to 0, new passwords are not checked against previous
passwords.
■ 1 (yes)
Default: 0
PasswordLifetimeDays Provides the default value of n in the Password will expire every n
days option. Used in the password expiration date computation by the
set_pwd_def_lifetime script. For more information, see “Implementing
password expiration policy” on page 163.
Default: 60
PermitManualUnlock This parameter specifies whether non-administrators can manually
unlock their own scheduling tables (for example, if tables are locked
during an abnormal disconnect from the GUI Server).
Valid values:
■ 1 - Users can unlock their own tables
■ 0 - Only administrators can unlock the table
Default: 1
Default: 25000
Default: 21600
Default: script_name
When Alert data is sent as input to a script, the parameters are sent in
the following format:
On UNIX:
# !/bin/sh
echo $* > /tmp/snmptest.out
On Windows:
echo %1% %2% %3% %4% %5% > c:\snmptest.out
Valid values:
■ 0 - SNMP only
■ 1 - User-defined script only
■ 2 - SNMP and user-defined script
Default: 0
Note: Alert data is sent to SNMP (values 0 or 2) only if the value of the
SnmpSendActive parameter is set to 1.
SnmpHost Host name or list of host names (if a list, using semi-colons (;) as
delimiters) to send the SNMP trap on an alert. Specific ports can be set
using a colon (:) as a delimiter.
Default: <no_host>
Example: dhost1;jhost2;myhost3:2000
SnmpSendActive Determines whether SNMP messages for Active Alerts are generated.
Valid values.
Valid values:
■ 0—SNMP messages for Active alerts are not generated
■ 1—SNMP messages for Active alerts are generated
Default: 0
UnsupportedClientVersions For BMC Software Customer Support use only.
Default: 0
UserAuditContext Specifies the activities that are audited and recorded.
Valid values:
■ ALL – All of the activities listed below
■ NONE – None of the activities listed below
■ AUTH – Authentication (logon tries, logouts, password actions)
■ SCHED – Scheduling definition activities
■ J_CONT – Active network activities (control requests)
■ J_INFO – Active job information activities (order, force, hold ...)
■ RES – Quantitative and Control resource activities
■ ALERT – Alerts
■ ACCOUNT – Account management activities
■ AUTH SCHED J_CONT J_INFO RES ALERT ACCOUNT (Default)
Valid values:
■ 0 (no) - When 0, the UserAuditContext parameter is ignored.
■ 1 (yes)
Default: 0
VMAdditionalJobsRelateFields Additional job related key fields to be defined by a user.
BMC Software recommends that you not use the same job name (or
mem name, in CONTROL-M for z/OS) for multiple jobs. If you use the
same name for multiple jobs, use this field to identify additional key
fields that CONTROL-M/EM can use to distinguish between different
jobs with the same name/mem name, so as not to confuse or switch
their job histories.
Default: <empty>
Note: A job version is deleted only when all of the following are true:
■ The version exceeds VMVersionsNumberToKeep.
■ The version exceeds VMMaxDaysRetainCurJobsHistory.
■ Automatic cleanup has run, as determined by
VMCleanupIntervalMinutes.
For more information, see “Implementing job version management” on
page 105.
Default: 60
Gateway parameters
Valid values:
■ 0 - Alerts are not created.
■ 1 - Alerts are created
Default: 1
CommCtmBufferSize The number of bytes buffered in Gateway that are waiting to be sent to the
CONTROL/M Server. If the number of bytes are exceeded, communication
with CONTROL/M Server is terminated.
Default: 10000000
CommEMBufferSize The number of bytes buffered in Gateway that are waiting to be sent to
other EM Servers. If the number of bytes are exceeded in GSR,GAS,GCS
components, communication with CONTROL/M Server is terminated.
Default: 10000000
DeltaMaxActMinutes Age, in minutes, for a net to be considered valid for distribution of Global
Conditions.
Default: 2160
Valid values:
■ 0 - Alerts are not sent.
■ 1 - Alerts are sent.
Default: 1
EBCDIC_cp For MVS data centers: This parameter defines the EBCDIC code page to
which ASCII data is translated.
Valid values:
■ 0 - Instructs the gateway to use the translation table that was used by
the previous version.
■ 1047 for English (USA)
■ 285 for English (British)
■ 273 for German
■ 297 for French
■ 284 for Spanish
Default: 0
GatewayDefaultTraceOptions Enables you to set command line trace options for multiple gateways.
Default: <empty>
GtwCondDispatchErr For Customer Support use only.
Default: 2
GtwParallelProcessingMode Enables multi-threading processing mode. The value off indicates
single-thread processing.
Valid values:
■ on
■ off
Default: 0
Default: null
Default: 10
MaxDownHistDays Number of days that the list of downloads is saved. This list contains
abbreviated information about each download, such as date and time, net
name, and number of downloaded jobs and resources.
Default: 100
MaxOldDay Downloads are kept in the CONTROL-M/EM database for not more than
the number of days specified in this parameter.
Default: 2
Note: The number of downloads stored in the database is never more than
the smaller of the MaxOldDay value and the MaxOldTotal value.
MaxOldTotal Number of downloads that can be stored in a CONTROL-M/EM database.
If this number is exceeded, the oldest download is deleted.
Default: 4
MaxUploadBufferMPM For Customer Support use only.
Default: 60000
MaxUploadBufferMVS For Customer Support use only.
Default: 60000
RunInfoErrorLevel For BMC Software Customer Support use only.
Default: 0
RunInfoIgnoreDevCnt Indicates the maximum and minimum length of elapsed run time between
calculation discards.
Default: 2
RunInfoMaxSamples Indicates the maximum number of run samples to be kept per job.
Default: 20
Default: 100
RunInfoTimeCvtOpt The start and end times of a job kept in the database according to the time as
set in the CONTROL-M iteration.
Valid values:
■ None – no conversion is done, time is saved as received from CTM
■ GMT – converted to GMT
Default: None
RunInfoUpdCtx Configures the context in which run information is processed.
Valid values:
■ 0 - Gateway main thread
■ 1 - Separate thread
Default: 1
RunInfoWaitInterval Interval in seconds between processing of run details in the Gateway.
Default: 10
SSLRetries Number of times 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 or off (as
required). This parameter is relevant only when 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 the communication
protocol to SSL Enabled.
Default: 90
Valid Values:
0 - Do not use bulk copy
1- Use bulk copy wherever possible. Default
BulkSendIntSecs Interval (in seconds) between sending groups of conditions to a reconnecting
data center. Default: 60
BulkSendMax Maximum number of messages to send in a group to a reconnected data center.
Default: 100
CleanOldIntSecs Maximum time, in seconds, unused conditions wait in the database before they
are removed. These conditions may have no data center destinations. Default:
86400 (24 hours)
DoneGcDelIntSecs Interval, in seconds, after which GCS cleans already handled conditions from
memory and the database. Default: 120
DoneGcDelQuota during heavy periods of cleanup of old conditions, number of cleaned conditions
after which GCS will check to see if the time interval specified in the
balance_gcs_int_secs system parameter has been reached. Default: 50
Valid Values:
0 – Each time a new request conflicts with the current request, stop processing
the current request and start processing the new request.
1 – The first time a new request conflicts with the current request, stop processing
the current request and start processing the new request (as in value 0 above).
However, ignore all subsequent conflicting requests and continue processing the
second request.
2 – Continue processing the current request and ignore all conflicting requests.
■ If the request comes from CONTROL-M for z\OS versions 6.2 or earlier, or
CONTROL-M for AS-400, it works like the value 1.
■ For all other supported CONTROL-M types and versions, it works like the
value 0.
GcMaxRetries Maximum number of retries to send conditions to a data center that had
previously returned a temporary error. Default: 5
GcRetryIntSecs Interval (in seconds) between attempts to send conditions to a data center that
had previously returned a temporary error. Default: 180
Valid Values:
0 – If the request is from CONTROL-M/Server version 6.1.0 or higher, ignore the
Method for Handling Conflicting Conditions setting. Instead, handle all
requests until they are sent to all destinations.
1 – Always handle conflicting requests as specified in the Method for Handling
Conflicting Conditions option. Default.
Note: If CONTROL-M/EM or CONTROL-M/Server version 6.1.00 through
6.1.02 was used at your site and you used global conditions in job scheduling,
consider setting the value of this parameter to 0 (to ensure that the same method
that was used in version 6.1.01 or 6.1.02 is used in the current version).
ShortestSlptimeMicros Time interval, in microseconds, during which the process will check the socket
for new requests. This parameter takes effect when the time out of a previously
scheduled event has just been reached. Default: 1 (microsecond)
SlptimeRatio Value to be used in a ratio that determines the time that the process will wait for
outside requests before leaving to idle time processing. Default: 10
The actual wait time is determined by the time-out interval of the next scheduled
high priority production activity, divided by this SlptimeRatio value.
SrvrsPollIntSecs Interval (in seconds) between attempts to communicate with a gateway.
Default: 60
UpdCommIntSecs Interval (in seconds) between readings of the Communication Table in the
CONTROL-M/EM database for new data centers. Default: 60
Valid Values:
0 – No diagnostics
1 – Condition transfer, problem, and information received
2 – Condition transfer, problem, and information sent
3 – Value 1 + value 2 (Default)
DbLogLvl Logging information level for messages related to database activities. Diagnostic
information is displayed about condition transfer requests inserted or deleted in
the database or read from the database for recovery operations.
Valid Values:
0 – No diagnostics
1 – Messages about database writing (insert, update, delete)
2 – Value 1 plus database reading (recovery operations) activity (Default)
Valid Values:
0 – No diagnostics
1 – Condition actions based on conflict handling policies
2 – Value 1 plus communication problems (Default)
3 – Value 2 plus condition handling status messages
LogSize Maximum number of record lines in the GCS_LOG file. When the number of
record lines in the currently open GCS_LOG file reaches the value specified in this
parameter, the file is closed and a new GCS_LOG file is opened. Default: 25000
Valid Values:
0 – No diagnostics
1 – Condition transfer request messages (Default)
2 – Content of all messages sent to gateways by GCS
3 – Values 1 and 2
4 – Value 3 plus life check messages received by GCS
MaxLogs Maximum number of log files to be managed cyclically. When the number of
GCS_LOG files reaches the value specified in this parameter, the oldest file is
deleted, in order for a new GCS_LOG file to be created. Default: 5
NOTE
After modifying Global Alerts Server parameters, stop and restart all Global Alerts Server
components for the changes to take effect.
Default: 10
AlertsMapRefreshInterval Frequency, in seconds, at which the Global Alerts 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
DefaultUserTimeoutSec Time, in seconds, that a CONTROL-M/EM API client user token is valid, if
no value is supplied during API user registration. After this time, the Global
Alerts Server can invalidate the token.
Default: 900
FailCheckDBTimeOut Time, in seconds, until the Global Alerts Server checks to confirm whether
communication with the database server has been disrupted. If
communication is still disrupted after this period of time has passed,
communication is considered to be disrupted and the action indicated by the
StopIfDBConnectionFail parameter is implemented.
Note: This parameter is relevant only after the Global Alerts Server
determines that communication with the database server is disrupted.
Default: 5
GatewayOutgoingQueueSize Maximum number of bytes buffered in the GUI/GAS servers waiting to be
sent to CONTROL-M/Server. For example, as a result of a Save JCL request.
Default: 500000
MaxUserTimeoutSec Maximum amount of time, in seconds, that a CONTROL-M/EM API client
user token is valid. After this time, the Global Alerts Server can invalidate
the token.
Default: 10800
Valid values:
■ HANDLE_ON_CLOSE - The alert status is updated to Handled
automatically when the ticket is closed.
Default: HANDLE_ON_CLOSE
SockRecrMaxAtmp The maximum number of times that the Global Alerts Server can attempt to
create a socket.
Default: 10
StandartCheckDBTimeOut Interval, in seconds, between attempts by the Global Alerts Server to confirm
that communication with the database server is not disrupted.
Default: 60
StopIfDBConnectionFail Action to take if communication between the Global Alerts Server and the
database server is disrupted.
Valid values:
■ 0 — The Global Alerts Server is shut down until communication with the
database server is restored. When communication is restored, the
Configuration Agent restarts the Global Alerts Server.
■ 1 — The Global Alerts Server remains operational. However, during this
time, it has Warning status (as displayed in the CONTROL-M
Configuration Manager) and may not function.
Default: 0
NOTE
After modifying Configuration Agent parameters, stop and restart the Configuration Agent
component for the changes to take effect.
Note: After the specified number of retries are attempted without success, use
the CONTROL-M Configuration Manager to reset the unresponsive
component. Change the state of the unresponsive component to a state other
than Up, then change it to Up, and then try again to activate the component.
Default: 10
ComponentRestartInterval Frequency, in minutes, at which the Configuration Agent makes an attempt to
start a CONTROL-M/EM component that is not responding. This parameter
can be modified from the CONTROL-M Configuration Manager.
Default: 3
ComponentShowState Some CONTROL-M/EM components, such as the GUI Server, the gateways,
and the Global Conditions server, operate hidden from the user. These
components can be displayed in command prompt windows by setting this
parameter to 1, stopping the Configuration Agent, and restarting the agent.
Default: 0
LifeCheckRespTimeout Time, in seconds, that the Configuration Agent waits for a component to
respond to a life check.
Default: 30
LifeCheckRetries Number of life checks the Configuration Agent performs before the component
is treated as malfunctioning.
Default: 5
Default: 15
LogCleanInterval Interval, in minutes, between LogReg log cleaning operations by the
Configuration Agent.
Note: The Configuration Agent cleans the LogReg log every time it is activated.
Default: 360
LogCleanLevel Amount of detail the clean operation erases from the LogReg log.
Valid values:
■ 0 - No deletion
■ 1 - Cleans only the agent’s 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.
Default: 1
LogInfoLevel Level of detail in LogReg log entries recorded by the Configuration Agent.
Valid values:
■ 0 - No entry
■ 1 - Configuration Agent-related messages
■ 2 - Brief component and agent related messages
■ 3 - Detailed component and agent related messages
Default: 2
SockRecrMaxAtmp Maximum number of times that the Configuration Agent can attempt to create
a socket.
Default: 10
Valid values:
■ 0 - No entry
■ 1 - Configuration 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 Configuration 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 Configuration Agent tries to stop the component
using the Stop command before performing a kill operation.
Default: 2
GUI parameters
NOTE
After modifying GUI parameters, stop and restart the relevant GUI components for the
changes to take effect.
Valid values:
■ 0 (No) - CONTROL-M/EM and CONTROL-M/Desktop do not wait for
confirmation that the ORB was shut down.
■ 1 (Yes) - CONTROL-M/EM and CONTROL-M/Desktop wait for
confirmation that the ORB was shut down.
Default: 1
ProcessCommandsPerVP For Customer Support use only.
Number of GUI Server commands that CONTROL-M/EM can process at a
time for each ViewPoint. These commands include submitting, adding, and
updating jobs, and making refresh requests.
Default: 1
ProcessMFCommands For Customer Support use only.
Number of GUI Server commands CONTROL-M/EM can process at a time.
These commands are not related to specific ViewPoints and include
displaying pop-up windows and task bar messages in the
CONTROL-M/Enterprise Manager window.
Default: 10
ProcessVPsCommands For Customer Support use only.
Number of GUI Server commands CONTROL-M/EM can process at a time
for all ViewPoints. These commands include submitting jobs, adding jobs,
updating jobs, and refresh requests.
Default: 10
UserChangePassword Determines if a user can change his or her own password.
Valid values:
■ 0 - Only users who have Full or Update permission to modify security
definitions can change their own password.
■ 1 - All users can change their own password.
Default: 1
NOTE
If a CONTROL-M/EM administrator uses the Authorization facility to set a password, the
password complexity, length, and history requirements are ignored.
Valid values:
■ UPDATE_ACCESS – Only users with Update access can order or force
a job.
■ BROWSE_ACCESS – Users with Browse access or Update access can
order and force jobs.
Default: UPDATE_ACCESS
AddJobsChunkSize Chunk size of jobs during View Point opening.
Default: 1000
AllowQueryDBFieldValues Indicates whether Available Values options are displayed for certain fields
in the Job Editing form.
Default: 1 (On)
AuthenticationLevel Note: Do not change this parameter unless requested to do so by BMC
Software.
Default: 2
Valid values:
■ 1 (Permissive mode) - Editing the author is enabled. Users can retain
the original Author when running utilities or performing a Write to
CONTROL-M/EM, or, alternatively, change the author to another user.
Default: 1
BIMCommLoop Note: Do not change this parameter unless instructed to do so by BMC
Interval Software Customer Support.
BIMThreadPool Note: Do not change this parameter unless instructed to do so by BMC
IdleTime Software Customer Support.
BIMThreadPool Note: Do not change this parameter unless instructed to do so by BMC
MaxSize Software Customer Support.
BIMThreadPool Note: Do not change this parameter unless instructed to do so by BMC
MinSize Software Customer Support.
bulk_act_cond Bulk size in bulk operation for retrieve conditions.
Default: 250
bulk_act_grp Bulk size in bulk operation for retrieve scheduling groups.
Default: 100
Default: 250
bulk_act_res Bulk size in bulk operation for retrieving control or quantitative resources.
Default: 50
CloseOldDownloads Note: Do not change this parameter unless instructed to do so by BMC
Software Customer Support.
ConcurrentCollections The number of collections that can be read in parallel.
Note: If you increase the value of this parameter, monitor the system for
several days, especially during periods of heavy usage, to ensure that
performance is not degraded. You may want to increase the value of this
parameter gradually (for example, by one or two at a time), to avoid CPU
bottlenecks.
After modifying this parameter, stop and restart all GUI Server components
for the change to take effect.
Default: 4
ControlResourceLoadLimit The maximum number of control resources that can be loaded into memory
from the CONTROL-M/EM database at the same time. This parameter can
help control memory usage. However, if this parameter is set to -1, there is
no maximum limit.
Default: -1
DelayBeforePinning The number of seconds before the GUI Server begins processing the
pin_collection.ini file.
Default: 10
DeletedJobsLoadLimit The number of jobs displayed to the user in the “Deleted Jobs” dialog box
in the CONTROL-M/Desktop.
Default: 2000
Default: 1000
EMThreadPoolIdleTime Note: Do not change this parameter unless instructed to do so by BMC
Software Customer Support.
EMThreadPool Note: Do not change this parameter unless instructed to do so by BMC
MaxSize Software Customer Support.
EMThreadPool Note: Do not change this parameter unless instructed to do so by BMC
MinSize Software Customer Support.
ExcludedJobFields Identifies fields (database columns) that should not be downloaded from
the database when retrieving collections, thereby decreasing memory load
and improving response time.
Any or all of the following fields can be excluded. Use spaces, commas,
colons, or semicolons to separate multiple entries.
Warning: BMC Software recommends that you not exclude data (change
the value of this parameter to 1) without first consulting BMC Software
Customer Support. If you do change the value to 1, be sure to modify job
processing definitions do that they do no contain excluded data.
Valid values:
■ Database Column - Description
■ MAX_WAIT- Maximum Wait
■ ODATE - Order date
■ OWNER - Owner
■ DESCRIPTION- Description
■ CPU_ID - Node ID
Warning: BMC Software recommends that you not exclude data (change
the value of this parameter to 1) without first consulting BMC Software
Customer Support. If you do change the value to 1, be sure to modify job
processing definitions do that they do no contain excluded data.
Valid values:
■ 0 – Do not exclude control resources.
■ 1 – Exclude control resources.
Default: 0
ExcludeJobQuantRes Determines whether quantitative resources are downloaded from the
database when retrieving collections. If unneeded quantitative resources
are not downloaded, memory requirements are reduced and response time
is improved.
Warning: BMC Software recommends that you not exclude data (change
the value of this parameter to 1) without first consulting BMC Software
Customer Support. If you do change the value to 1, be sure to modify job
processing definitions do that they do no contain excluded data.
Valid values:
■ 0 – Do not exclude quantitative resources.
■ 1 – Exclude quantitative resources.
Default: 0
Note: This parameter is relevant only after the GUI Server determines that
communication with the database server is disrupted. After modifying this
parameter, stop and restart all GUI Server components for the change to
take effect.
Default: 5
LimitArchiveJobsInMem The maximum number of archive jobs in memory per GUI Server.
Default: 40000
MaxObsoleteJobs Note: Do not change this parameter unless instructed to do so by BMC
Software Customer Support.
MaxUserTimeoutSec Time, in seconds, that a CONTROL-M/EM API client user token can be
valid. Afterwards, the GUI Server can invalidate the token.
Note: After modifying this parameter, stop and restart all GUI Server
components for the change to take effect.
Default: 10800
NumberOfMyWorldJobs Total number of job nodes that are displayed when Local View is used. For
information about Local View, see the Alerts chapter in the CONTROL-M
User Guide.
Note: After modifying this parameter, stop and restart all GUI Server
components for the change to take effect.
Default: 100
PrereqConditionsLoadLimit The maximum number of prerequisite conditions that can be loaded into
memory from the CONTROL-M/EM database at the same time. This
parameter helps control memory usage. When PrereqConditionsLoadLimit
is -1, there is no maximum limit.
Default: -1
QuantResourceLoadLimit The maximum number of quantitative resources that can be loaded into
memory from the CONTROL-M/EM database at the same time. This
parameter helps control memory usage. When QuantResourceLoadLimit is
-1, there is no maximum limit.
Default: -1
Valid values:
■ CURRENT – The collection of jobs in the ViewPoint from which the
user opened the Network Neighborhood.
■ All Jobs – The collection includes all jobs, not only the jobs in the
current ViewPoint.
Default: CURRENT
SecuredExcludedFields Determines if the GUI Server is in Secure mode. If the GUI Server is in
Secure mode, user requests to view or modify fields that are included in the
Security filter of a ViewPoint are rejected.
Warning: BMC Software recommends that you not exclude data (change
the value of this parameter to 1) without first consulting BMC Software
Customer Support.
Valid values:
■ 0 - The GUI Server is not in Secure mode; it prompts the user for
confirmation whether to continue processing the request.
■ 1 - The GUI Server is in Secure mode; it denies the request because
opening any ViewPoint might involve a security breach. The user
cannot open any ViewPoint until the Authorization Filter for the user is
changed by the system administrator so that it no longer contains
excluded fields.
■ If a User Authorization filter includes only jobs for which the user is the
owner, but Owner is an excluded field, then a match on Owner is
assumed for every job in the Active Environment. This could cause
every job in the Active Environment to be loaded (if there are no other
exclusion criteria).
Default: 0
Note: After modifying this parameter, stop and restart all GUI Server
components for the change to take effect.
Note: After modifying this parameter, stop and restart all GUI Server
components for the change to take effect.
Default: 10
StopIFDBConnectionFail Action to take if communication between the GUI Server and the database
server is disrupted.
Note: After modifying this parameter, stop and restart all GUI Server
components for the change to take effect.
Valid values:
■ 0 – The GUI Server is shut down until communication with the
database server is restored. When communication is restored, the
Configuration Agent restarts the GUI Server.
■ 1 – The GUI Server remains operational. However, its status is Warning
(as displayed in the CONTROL-M Configuration Manager) and it may
not function.
Default: 0
UseQueriedCollectionForFind Determines the collection of jobs to be searched when performing a Find
from within a ViewPoint screen.
Valid values:
■ 1 (Yes) - When performing a find from within a ViewPoint, limit the
search to jobs that satisfy the QueriedCollection system parameter.
■ 0 (No) - Perform the search using all jobs.
Default: 1
For information about defining Group scheduling table filtering policy, see
“Group scheduling table displays in ViewPoints” on page 93 and
“Displaying empty Group scheduling tables in ViewPoints” on page 125.
Valid values:
■ SELECT_JOBS - Filtering criteria are applied only to the jobs. Only jobs
satisfying the filtering criteria, and only group scheduling tables
containing at least one such job, are passed and displayed. (No empty
scheduling groups are passed.)
■ SELECT_JOBS_AND_SG - Filtering criteria are applied both to jobs and
group scheduling tables. In addition to passing the same jobs and
group scheduling tables that are passed for the SELECT_JOBS value,
the Server also passes any group scheduling tables that match the
filtering criteria (and pass the security criteria) even if they are empty.
Default: SELECT_JOBS
ViewPointTimeoutForBIM The number of milliseconds within which the CONTROL-M/EM GUI
Server should receive a reply from the BMC Batch Impact Manager after
sending a request.
Default: 600000
UpdatesQueueLimit Default size of the updates queue for a ViewPoint.
Default: 5000
UpdatesQueueMaxLimit The maximum possible size of the updates queue for a ViewPoint.
Default:60000
Valid values:
■ 1 - Enable.
■ 0 - Disable
Default: 1
IdenticalXAlertTimeDelta Determines the interval, in minutes, within which an alert is defined as identical
to a previous matching alert.
Default: 30 minutes
Default: 0
XAlertsSendSnmp Determines whether an alert will be sent as an SNMP trap, to a script, both, or
neither.
Valid values:
■ 0 - Not active
■ 1 - Sent as an SNMP trap
■ 2 - Sent to a script
■ 3 Sent as an SNMP trap and to a script.
Default: 0
IdenticalXAlertHandling Determines whether identical alerts are sent as an SNMP trap or to a script.
Valid values:
■ 1 - Identical alerts are sent as an SNMP trap and to a script.
■ 0 - Identical alerts are not sent as an SNMP trap and to a script.
Default: 0
HandledXAlertHandling Determines whether handled alerts are sent as an SNMP trap or to a script.
Valid values:
■ 1 - Handled alerts are sent as an SNMP trap and to a script.
■ 0 - Handled alerts are not sent as an SNMP trap and to a script.
Default: 0
XAlertsMaxAge Determines, in days, how long XAlerts are saved before they are deleted by the
Configuration Management Server.
Default: 100
Example:
XAlertsmachine:7000;SNMPmachine;Scriptsmachine:7001
Default: null
XAlertsSend2Script Specify the full path and file name of the script to be sent. This parameter is used
only when the XAlertsSendSnmp system parameter is set to either 2 or 3.
Default: null
CmsXAlertsHost Specify the host or IP address on which the CMS is forced to receive XAlerts.
Note: If no value is entered for this parameter, the host name on which the CMS
is installed is used.
Default: null
CmsXAlertsPort Specify the port through which the XAlerts are received.
Default: 0
Note: The default value 0 means that any random port is used.
XAlertsDisableMsgIDs Specify the message IDs for which no XAlerts are sent. By default, no message
IDs are listed. Use a comma to separate multiple message IDs.
Default: none
XAlertsMinSeverityFilter Specify the severity level filter. XAlerts with a value equal to or greater than the
specified severity level are sent to the Exception Alerts window.
Valid values:
■ Warning
■ Error
■ Severe
Default: Warning
MaxXAlerts2Send2Client Note: Do not change this parameter unless instructed to do so by BMC Software
Customer Support.
Determines the maximum number of exception alerts sent from the CMS to the
Exception Alerts window.
Default: 2000
CMS parameters
Valid values:
■ TCP - A non-secure connection is established.
■ SSL - Connect using SSL only.
■ Auto - The system automatically detects the type of connection that
is established.
Default: TCP
CmsCtmRefreshInterval The Configuration Management Server (CMS) refreshes the status and
topology of the CONTROL-M/Servers on a regular basis. This system
parameter governs the length of time in seconds between each refresh
episode.
Default: 60
CmsEmRefreshInterval The CMS refreshes its internal image of CONTROL-M/EM component
status on a regular basis. This system parameter governs the length of
time in seconds between each refresh episode.
Default: 60
CmsGateAdditionalParams Note: Do not change this parameter unless instructed to do so by BMC
Software Customer Support.
DeletedJobsLoadLimit The maximum number of deleted jobs to be displayed to the user. If the
number of deleted jobs exceeds this value, the more recently deleted
jobs are displayed.
Default: 2000
MaxTableJobsToAudit The maximum number of jobs in the scheduling table to be audited.
Default: 1000
RemoteCmdTimeout The amount of time, in seconds, that the CMS will wait for a reply to a
remote request sent through the Configuration Management Server to
CONTROL-M/Server, CONTROL-M/Agent, and Control Modules,
before timing out.
An example of such a request is a ping agent request.
Default: 300
Default: 30
VMCleanupIntervalMinutes Interval, in minutes, between activations of automatic job history
cleanup by the CMS.
Default: 30
VMMaxDaysRetainCurJobsHistory The number of days after which the history of the current jobs should be
deleted automatically
Note: A job version is deleted only when all of the following are true:
■ The version exceeds VMVersionsNumberToKeep.
■ The version exceeds VMMaxDaysRetainCurJobsHistory.
■ Automatic cleanup has run, as determined by
VMCleanupIntervalMinutes.
For more information, see “Implementing job version management” on
page 105.
Default: 0
VMNumDaysRetainDeletedJobs The number of days to retain deleted jobs and their history. Deleted
tables will also be deleted according to this value.
Default: 180
NOTE
The tables in this section list the parameters located in the Defaults.rsc file. For instructions on
modifying these parameters, see “Editing the Defaults.rsc file” on page 405.
Default: 100
continue_not_responding Indicates how the new gateway handles multiple gateway instances for the
same CONTROL-M installation if all attempts to stop and kill the original
gateway are unsuccessful.
Valid values:
■ Y- Both gateway occurrences are allowed to run concurrently. This is not
recommended.
■ N- The original gateway continues in its “hubg” state. The new gateway
stops running.
Default: N
dal_rel_cache_size This only when instructed by BMC Software technical support.
dal_select_min_bulksize These parameters indicate the bulk size being used by the database access layer
dal_select_max_bulksize during bulk insert and choose SQL operation. Larger numbers cause the insert
dal_insert_min_bulksize and choose SQL operations to occur faster and more efficiently, at the expense
dal_insert_max_bulksize of virtual memory.
Defaults:
■ dal_select_min_bulksize: 10
■ dal_select_max_bulksize:
■ Sybase and Oracle: 50
■ MSSQL: 20
■ dal_insert_min_bulksize: 10
■ dal_insert_max_bulksize:
■ Sybase and Oracle: 100
■ MSSQL: 10
Valid values:
■ 1 - The gateway establishes connections in blocking mode.
■ 2 - The gateway establishes connections in non-blocking mode.
Default: 45
Valid values:
■ Y - The new gateway tries to kill the original gateway and, if successful,
continues to run. If the original gateway cannot be killed, the new gateway
handles the original gateway according to the continue_not_responding
parameter.
■ N - The new gateway tries to stop the original gateway (using the ctl utility)
and, if successful, continues to run. If the original gateway is not stopped
after 3 attempts, the new gateway handles the original gateway according to
the continue_not_responding parameter.
Default: N
nonBlockTimeout If a gateway is in non-block mode and part of a message is not received during
the number of seconds specified in this parameter, the gateway assumes
communication is down.
Default: 40.
This parameter is relevant only if the useNonBlock parameter is set to Y.
useNonBlock Indicates whether the gateway operates in blocking mode or non-blocking
mode. This mode determines whether the gateway receives entire messages or
parts of messages.
Valid values:
■ N - The gateway waits and receives for the entire message to arrive in
blocking mode, regardless of length of time.
■ Y - The gateway receives parts of messages (non-blocking mode).
Communication is assumed to be down if part of a message is not received
within the time interval specified in the nonBlockTimeout field.
Default: N
CONTROL-M/Server parameters
This section lists and describes the following categories of CONTROL-M/Server
parameters:
System parameters
Table 81 lists the CONTROL-M/Server system parameters. These parameters are
assigned default values during installation. For some of the parameters, you can use
the ctmsys utility to change the parameter value.
Default: SYSTEM
Note: The New Day procedure updates this value each time the procedure
runs.
Valid Values: dates in the format yyyymmdd (for example, 20080215 for
February 15, 2008)
This time is when the CONTROL-M date (Odate) changes and the New Day
procedure runs.
Valid Values: either of the following formats (where hh indicates hours and
mm indicates minutes):
■ +hhmm changes the CONTROL-M date at the specified time after midnight.
These values reflect 24-hour time. For example, 2200 is equivalent to 10 P.M.
Examples
If you use +0600, the hours between midnight and 6:00 A.M. are considered
part of the previous date’s work day. Thus, system date February 10, 5:59 A.M.
is considered part of the February 9 work day.
If you use -2200, the hours between 10 P.M. and midnight are considered part
of the next date’s work day. Thus, at 10:00 P.M. on system date February 10, the
CONTROL-M date changes to February 11.
Default: +0700
How / where to set: Use the ctmsys utility to change the parameter value.
Note: A user for whom one or more authorizations have been assigned in the
security database can perform only the actions for which the user is specifically
authorized.
Default: N
After this period, the New Day procedure deletes all job SYSOUT files.
This parameter also affects the number of days that old nets are saved. To view
SYSOUT files of jobs in old nets, in some cases SYSOUT files must be saved for
an extra calendar day.
Default: 1
How / where to set: Use the ctmsys utility to change the parameter value.
Note:
If this value exceeds 2, the syslogs might run out of space. Either delete the
transaction log or use ALTER DATABASE to increase the size of the segment.
For Sybase, if this value exceeds 4, increase the size of the temporary database.
BMC recommends using the following formula to determine the optimum size
for the database: 6% of the data portion size of the database multiplied by the
number of days to retain entries.
For example, if the data device size is 400 MB and you want to retain history for
10 days, enlarge the temporary database to 240 MB. For more information, see
“Extending the CONTROL-M/Server database” on page 309
Default: 2
How / where to set: Use the ctmsys utility to change the parameter value.
Default: 10
How / where to set: Use the ctmsys utility to change the parameter value.
Valid Values:
Default: Disabled
Default: 2 (Monday)
How / where to set: Use the ctmsys utility to change the parameter value.
Default: Y
How / where to set: Use the ctmsys utility to change the parameter value.
Communication parameters
Tables 82 and 83 list the CONTROL-M/Server communication parameters.
Note: This number must match the value assigned to the Agent-to-Server Port
Number parameter on the agent computer.
Default: 7447 (On UNIX, the default value is overridden during the value
given during installation.)
Default: TCP
How / where to set: For UNIX, see “Editing the config.dat file” on page 408. For
Windows, edit the Communication Protocol registry parameter.
Default: 6005
This name is typically the host name of the server computer. You should
modify this parameter only if the server computer contains more than one
network interface card (for example, Ethernet and Token-Ring).
Default: the default host interface name defined in the server computer
operating environment
Configuration Agent Port port number for the CONTROL-M/Server Configuration Agent
Default: 2369
Default: 1000
Default: Y
How / where to set: See “Editing the config.dat file” on page 408.
Default: 300
How / where to set: See “Editing the config.dat file” on page 408.
Default: 300
How / where to set: See “Editing the config.dat file” on page 408.
Default: 60 (seconds)
Default: 5
Default: gethostname
Operational parameters
Table 84 lists the general CONTROL-M/Server operational parameters.
This parameter is used to specify the lower of the two port numbers and must
correspond to the value assigned to field TCP/IP Port Number in the definition of
the CONTROL-M data center in the CONTROL-M Definition dialog box in the
CONTROL-M Configuration Manager. Verify that the two port numbers are not
used for any other purpose on the server computer.
Default: 2370
Default: 1000
Maximum Server Maximum number of communication server (CS) processes that communicate with
Processes the CONTROL-M/Server gateway process concurrently.
Default: 2
Minimum Server Minimum number of communication server (CS) processes that communicate with
Processes the CONTROL-M/Server gateway process concurrently.
Default: 2
Default: 5
How / where to set: See “Editing the config.dat file” on page 408.
Default: 20
How / where to set: See “Editing the config.dat file” on page 408.
Default: MEMNAME
The values specified for these parameters are used as the default values for
communication with each agent computer. You can change values for specific agent
computers individually.
Default: Y
Check Interval Interval (in seconds) between status checks for each CONTROL-M/Agent that
communicates with CONTROL-M/Server.
Default: 08
Communication Timeout Maximum length of time (in seconds) that CONTROL-M/Server should spend
attempting to communicate with an agent computer before assigning it
Unavailable status.
Example
If the value of Communication Timeout is 120 and Maximum Retries is 12,
CONTROL-M/Server attempts to communicate with the agent computer once
every 10 seconds (120/12) during the timeout period.
Default: 120
Default: 256
Maximum Disconnect Sets the maximum time in which the NS allows an agent to be disconnected
Time before it will initiate a session with it (although there's nothing to submit to it).
The MAX_DISCONNECT_TIME parameter is relevant only if the
ALLOW_COMM_INIT parameter on the agent is set to NO.
Default: 300
Maximum Retries Number of communication retries to attempt in the period of time specified
before assigning the Unavailable status to an agent computer.
Default: 12
Valid Values: Y or N
Default: N for a new agent installation and N for an agent that is known to
CONTROL-M/Server before upgrading to version 6.2.01 and above.
Default: 900
Retry Interval Length of time to wait (in seconds) between attempts to communicate with an
agent computer whose status is Unavailable.
Default: 90
Server-to-Agent Port Port number in the agent computer through which data is received from the
Number server computer. The value assigned to this parameter must correspond to the
value assigned to the Server-to-Agent Port Number field in the Configuration
file on the corresponding agent computer.
Default: 7006
Default: 900
Unavailability Shout Indicates messages with a high priority sent from an agent assigned
Urgency Unavailable status. Urgent message are sent with a special indication so that the
recipient of the message is aware of the urgency.
Valid values: R, U, or V
Default: R
Database parameters
Database configuration parameters are specified during installation, before the
CONTROL-M/Server database is created. You can subsequently change these
parameters and rebuild the CONTROL-M/Server database by using the Database
Creation menu, described in Chapter 11, “Maintaining databases and CONTROL-M
data.”
CONTROL-M Name for the CONTROL-M/Server database. This name must be unique.
Database Name
Default: ctrlm
CONTROL-M Sybase name for the CONTROL-M/Server database owner. The custom script
Database Owner creates this user in the database. This name is used by CONTROL-M when
accessing its database.
Default: ctrlm
Data Device Type Type of disk storage (raw partition or file system) used for the
CONTROL-M/Server database.
Default: FILE
Data Physical For Data Device Type FILE: Full path name where the CONTROL-M/Server
Device/Path Name database will be located.
For Data Device Type RAW: Physical device name of the raw partition in which the
CONTROL-M/Server database will be located.
Default: /<controlm_home_dir>/sybase/data/ctrlm_ux.dat
If the database will be located in a file system, the custom script allocates the
amount of space you specify plus an additional 33% to accommodate the Sybase
transaction log. For example, if you specify 60 MB, the amount of space actually
allocated is 80 MB.
Default: 50
Default: password
DBO Password Sybase password for the CONTROL-M/Server database owner (6 to 30 characters,
alphanumeric). The characters you enter are not echoed for security reasons. This
password is used by CONTROL-M processes and utilities to access the
CONTROL-M/Server database.
Default: password
Log Device Type Type of disk storage (raw partition or file system) used for the
CONTROL-M/Server database log.
Default: password
Log Physical For Log Device Type FILE: Full path name where the CONTROL-M/Server
Device/Path Name database log will be located.
For Log Device Type RAW: Physical device name of the raw partition in which the
CONTROL-M/Server database log will be located.
Default: /<controlm_home_dir>/sybase/data/ctrlm_log.da
If you want Sybase to use a raw partition, type y in response to the prompt.
An additional prompt will be displayed requesting the physical device name
(described below).
Default: FILE
Master Physical For Master Device Type FILE: Full path name where the master Sybase database
Device/Path Name will be located.
For Master Device Type RAW: Physical device name of the raw partition on which
the Sybase database will be located.
Default: <controlm_home_dir>/sybase/data/master.dat
Query Socket Port Sybase utilizes these two TCP/IP ports for communication between CONTROL-M
Number and Sybase SQL Server. The port numbers must be different from each other. If
-and- these port numbers are already used by an existing application, choose other
Backup Socket Port values, each in the range 1024 to 65534 inclusive.
Number
Default: 7102 and 7103
Sybase Interface Directory in which the Sybase interfaces file is located. This path should be visible
Directory to CONTROL-M.
When you choose to modify this value, the custom script reads the Sybase
interfaces file and displays a list of the available SQL servers. Specify the name of an
SQL server from the displayed list (contact your system administrator for this
information).
Default: SYBASE
CONTROL-M INDEX Full path name to the CONTROL-M INDEX tablespace file.
tablespace file location
Default: /<controlm_home_dir>/oracle/oradata/ctrlm/indx01.dbf
CONTROL-M Oracle utilizes this TCP/IP port for communication between CONTROL-M and
Listener port number Oracle SQL Server. The port must be dedicated to this purpose. Choose a number in
the range 1024 to 65534 inclusive.
CONTROL-M TEMP Full path name to the CONTROL-M TEMP tablespace file.
tablespace file location
Default: /<controlm_home_dir>/oracle/oradata/ctrlm/temp01.dbf
Name of the first Full path name of the first database log file.
database log file
Default: /<controlm_home_dir>/oracle/oradata/ctrlm/log01.dbf
Name of the second Full path name of the second database log file.
database log file
Default: /<controlm_home_dir>/oracle/oradata/ctrlm/log02.dbf
Oracle CDROM name Name of CDROM device containing the Oracle installation CDROM.
Oracle home directory Directory where Oracle binary files are stored.
Default: /<controlm_home_dir>/oracle
Oracle Server Host The host computer name of an existing Oracle server.
name
Size of CONTROL-M The size of each database log file. There are two files of equal size.
database log files
Default: 20 MB
Default: 250 MB
Default: controlm
Default: password
Default: password
CONTROL-M/Server Name for the CONTROL-M/Server database. This name must be unique.
Database Name
Default: ctrlm
Default: ctrlm
Default: password
Data Device Logical Name Name of the device on which the CONTROL-M/Server database will be
located.
Default: ctrlm_ux
Data Device Path Full path name for the CONTROL-M/Server database.
Default: c:\<sql_dir>\data\ctrlm_ux
Data Device Size Amount of space (MB) to allocate for the data portion of the
CONTROL-M/Server database.
Default: 75 (MB)
Log Device Logical Name Name of the device on which the CONTROL-M/Server database log will be
located.
Default: ctrlm_log
Default: c:\<sql_dir>\data\ctrlm_log
Log Device Size Amount of space (MB) to allocate for the CONTROL-M/Server database log.
Default: 25 (MB)
Port Number The database utilizes this TCP/IP port for communication between
CONTROL-M/Server and the PostgreSQL Server. If this port number is
already used by an existing application, choose another value, in the range
1024 to 65534 inclusive.
Default: 5432
CONTROL-M/Server Database name for the CONTROL-M/Server database owner. The installation
Database Owner script creates this user in the database. This name is used by
CONTROL-M/Server when accessing its database.
Valid values:
■ Small
■ Medium
■ Large
Database Server Home Full path name of the location in which the PostgreSQL database server
Directory (Windows only) resides: <CONTROL-M/Server path>/pgsql.
Mirroring parameters
Parameters for database mirroring (Table 90) are specified when mirroring is
initialized, either during CONTROL-M/Server installation or subsequently. You can
subsequently change these parameters by using the Database Mirroring menu
described in Chapter 11, “Maintaining databases and CONTROL-M data.”
CONTROL-M Mirror Name for the CONTROL-M/Server mirror database owner. The install_mirror
Database Owner script creates this user in the database. This name is used by CONTROL-M when
accessing the mirror database.
(Sybase, Oracle,
PostgreSQL) Note: After specifying this utility, you are prompted to enter the DBA password to
access the CONTROL-M/Server database server.
CONTROL-M Mirror Name of the Sybase device on which the CONTROL-M/Server mirror database
Database Data Device will be created.
Name
Default: ctm
(Sybase)
CONTROL-M Mirror Name of the Sybase device on which the CONTROL-M/Server mirror database log
Database Log Device will be created.
Name
Default: ctmlog
(Sybase)
CONTROL-M Mirror Name of the Sybase device on which the CONTROL-M/Server mirror database
database data device will be created.
name (Sybase)
Default: ctrlm_ux
CONTROL-M Mirror Name of the Sybase device on which the CONTROL-M/Server mirror database log
database log device will be created.
name (Sybase)
Default: ctrlm_log
CONTROL-M Mirror Name of the CONTROL-M/Server mirror database. This name must be unique.
database name
(Sybase, MSSQL, Default: ctrlm
PostgreSQL)
(Only for Sybase)
Mirror Sybase Server Name of the SQL server to which CONTROL-M will connect for mirroring. When
Name you choose to modify this value, the install_mirror script reads the Sybase
interfaces file and displays a list of the available SQL servers. Specify the name of
(Sybase) an SQL server from the displayed list (contact your system administrator for this
information).
Default: CTRLM2
Mirror Host Name Host name of computer that runs the instance of the database SQL Server used for
(Sybase, Oracle, mirroring.
PostgreSQL)
Mirror Port Number TCP/IP query port number for the database SQL Server used for mirroring. If you
(Sybase, Oracle, are using a CONTROL-M dedicated database SQL Server for the mirror database,
PostgreSQL) the Sybase/Oracle Port Number can be found in the QUERY_SPN field in the
<controlm_owner>/install/install_defs file, and for PostgreSQL, in the
<PostgreSQL Home>/data/postgresql.conf file.
Performance parameter
A special parameter in the CONTROL-M
~<controlm_owner>/ctm_server/data/config.dat file is available for tuning CONTROL-M
performance. This parameter affects how jobs are selected for both scheduling and
post-processing. Table 91 describes the performance parameter. The variable
<controlm> is the CONTROL-M home directory.
Default: 15
How / where to set: See “Editing the config.dat file” on page 408.
The sleep time setting for CONTROL-M processes can also affect the performance
and functionality of CONTROL-M. For example, setting the sleep time of the Selector
(SL) and/or Tracking (TR) process to 5, will improve performance, but CONTROL-M
will consume more CPU.
Configuration parameters
Table 92 describes the parameters in the CONTROL-M/Server configuration
parameter file (~<controlm_owner>/ctm_server/data/config.dat on the server
computer).
Valid values: Y, N
Note: You can speed up the New Day procedure by specifying N for this
parameter and running the ctmagcln utility. For more information, see the
CONTROL-M Utility Guide.
Default: Y
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
■ ECS—CONTROL-M/EM GI
■ IOALOG—CONTROL-M IOALOG files
■ CONSOLE—Server console
Default: ECS
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
■ SYSTEM—All the AutoEdit variables for each submitted job are sent to the
agent. These include System, Global, Group, and Local variables.
■ GLOBAL—Global, Group, and Local AutoEdit variables are sent to the agent
for each submitted job. System AutoEdit variables are not sent.
■ GROUP—Group and Local AutoEdit variables are sent to the agent for each
submitted job. System and Global variables are not sent.
Default: LOCAL
How / where to set: See “Editing the config.dat file” on page 408.
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
■ AJF – Ignore predecessor jobs in the Active Jobs file level. When selected, jobs
in the Group Scheduling table ignore conditions set by jobs in the active jobs
file that are not scheduled.
■ GROUP – Ignore predecessor jobs in the group level. When selected, jobs in
the Group Scheduling table ignore conditions set by jobs in the Group
Scheduling table that are not scheduled. Default.
Note: This parameter is relevant only when ADJUST_COND is set to Y. For more
information, see ADJUST_COND in the CONTROL-M Parameter Guide.
Default: GROUP
Default: 1
How / where to set: See “Editing the config.dat file” on page 408.
Default: 24 (hours)
CTM_CONFIG_AGENT_ For CONTROL-M/Agents and remote hosts for which CONTROLM/Server has
INITIAL_GET_HOSTNA not previously identified the operating system and Agent version, the frequency,
ME_INTERVAL in minutes, with which CONTROL-M/Server will try to retrieve that information
so that it is available to the end user via CONTROL-M Configuration Manager.
Default: 5 (minutes)
CTM_CONFIG_AGENT_ Determines the mode of the CONTROL-M/Server Configuration Agent.
MODE
Valid values:
■ 1 (READ_MODE): Only life check and information requests are honored, any
modifying request is rejected.
Default: 2
How / where to set: See “Editing the config.dat file” on page 408.
Default: 2369
Default: 0
Default: 1
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
■ Y—A dummy job waits for the prerequisite conditions expected by the job it
is replacing, and performs the post processing of the job. When a Group
Scheduling table is ordered, jobs in the group that should not be ordered at
this time are ordered as DUMMY jobs. This functionality is useful for data
centers that require identical job flow regardless of whether certain jobs in a
group are ordered for a specific instance of the group.
■ N—Out conditions of the jobs that were not ordered are ignored by the
ordered jobs in the group scheduling table.
Note: This parameter is relevant only when ADJUST_COND is set to Y. For more
information, see ADJUST_COND in the CONTROL-M Parameter Guide
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
Note: If N is specified for this parameter, groups are activated when the
necessary conditions exist, and remain active regardless of whether or not any of
those conditions are deleted.
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
If you use the same command for a specific jobname, this parameter is ignored.
Valid values: Y, N
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Default: 30
How / where to set: See “Editing the config.dat file” on page 408.
Default: 60 (seconds)
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: S, M
Default: S
How / where to set: See “Editing the config.dat file” on page 408.
■ N – the Next Run time of a job is in local computer time, not adjusted to time
zone.
■ Y – the Next Run time of a job is adjusted to the correct time zone.
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Default: NO
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Default: NO
Valid values: N, Y
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
■ KEEP – each job is removed when MAXWAIT days have passed regardless
of whether it ended OK.
■ NOT_KEEP – each job (non-cyclic and cyclic) is removed from the Active
Jobs file at the next run of the New Day procedure. Cyclic jobs are not
removed if they are executing when the New Day procedure begins. Instead,
they are removed at the run of the following New Day procedure.
Default: KEEP
How / where to set: See “Editing the config.dat file” on page 408.
Default: OK
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
Y – During the New Day Procedure, jobs with a specified time zone are ordered
only if they are scheduled for tomorrow’s Odate.
N – During the New Day Procedure, jobs with a specified time zone are ordered
only if they are scheduled for the current Odate.
Default: Y
How / where to set: See “Editing the config.dat file” on page 408.
Default: 1
How / where to set: See “Editing the config.dat file” on page 408.
Default: Y
NOT_ORDERED_JOB_A Type of Alert message to send to CONTROL-M/EM when a job is not ordered
LERT due to scheduling criteria.
Valid values:
■ 0 – One General Alert per User Daily: ONE OR MORE JOBS IN DAILY
<daily_name> WERE NOT ORDERED
Default: 0
How / where to set: See “Editing the config.dat file” on page 408.
Default: 2000
How / where to set: See “Editing the config.dat file” on page 408.
Default: 0.33
How / where to set: See “Editing the config.dat file” on page 408.
Default: 20
How / where to set: See “Editing the config.dat file” on page 408.
1 – Performs -DELETE cleanup. Only the amount of days that are specified are
kept. Default: The number of days kept is specified by the How Many Days to
Retain ioalog parameter.
Default: 0
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
Default: MEMNAME
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
Note: You can speed up the New Day procedure by specifying N for this
parameter and running ctmruninf -PURGE.
Default: Y
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
Default: SERVER
How / where to set: See “Editing the config.dat file” on page 408.
Default: 0 (unlimited)
How / where to set: See “Editing the config.dat file” on page 408.
Default: 80
How / where to set: See “Editing the config.dat file” on page 408.
Valid values:
■ 0 – User Daily job ends with an exit code of 0 even if not all jobs are ordered.
■ 1 – User Daily job ends with an exit code of 14 if not all jobs are ordered.
Default: 0
How / where to set: See “Editing the config.dat file” on page 408.
Default: 2 (seconds)
How / where to set: See “Editing the config.dat file” on page 408.
NOTE
The SYSOUT of a job can be attached to an e-mail message only if the job has completed
processing.
Valid values:
■ N – No. When specified, the SYSOUT of a job is not attached. This setting
overrides any specification made elsewhere.
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Note: If the SYSOUT file is larger than the specified maximum size, the
SYSOUT will not be attached to the e-mail message.
How / where to set: See “Editing the config.dat file” on page 408.
Default: 30 (seconds)
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: Y
How / where to set: See “Editing the config.dat file” on page 408.
Default: 5 (seconds)
How / where to set: See “Editing the config.dat file” on page 408.
Default: 25
Valid values: Y, N
Default: Y
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N
Default:
■ UE101 Job Ordering User Exit—ctm_exit101.sh
■ UE102 Job Submission User Exit—ctm_exit102.sh
■ UE103 Before New Day Procedure User Exit—ctm_exit103.sh
■ UE104 After New Day Procedure User Exit—ctm_exit104.sh
■ UE105 Before User Daily User Exit—Ctm_exit105.sh
■ UE106 After User Daily User Exit —Ctm_exit106.sh
How / where to set: See “Editing the config.dat file” on page 408.
Refresh Type:
■ UE101 Job Ordering User Exit—Manual
■ UE102 Job Submission User Exit—Manual
■ UE103 Before New Day Procedure User Exit—Recycle
■ UE104 After New Day Procedure User Exit—Recycle
■ UE105 Before User Daily User Exit—Manual
■ UE106 After User Daily User Exit —Manual
CTM_PRM_TIMEOUT_ Time to wait for a user exit script to run before it is terminated.
UExxx (101–106)
For UNIX: Time is measured in units of seconds
Default: 20
How / where to set: See “Editing the config.dat file” on page 408.
Refresh Type:
■ UE101 Job Ordering User Exit—Manual
■ UE102 Job Submission User Exit—Manual
■ UE103 Before New Day Procedure User Exit—Recycle
■ UE104 After New Day Procedure User Exit—Recycle
■ UE105 Before User Daily User Exit—Manual
■ UE106 After User Daily User Exit —Manual
■ General parameters
■ CONTROL-M/Server system exit parameters
■ Watchdog user exit parameters
General parameters
Default: ""
How / where to set: See “Editing the config.dat file” on page 408.
Default: 0 (In the shipped config.dat, this is overridden by the value 2.)
How / where to set: See “Editing the config.dat file” on page 408.
How / where to set: See “Editing the config.dat file” on page 408.
Default: 5 (In the shipped config.dat, this is overridden by the value 10.)
How / where to set: See “Editing the config.dat file” on page 408.
Default: 5 (In the shipped config.dat, this is overridden by the value 1.)
How / where to set: See “Editing the config.dat file” on page 408.
Default: 360
How / where to set: See “Editing the config.dat file” on page 408.
For example, if the value of this parameter is 6 (minutes), and the value of the
WD_CTMEXIT_1_INTERVAL parameter is 20, the script for system exit 1 will run
once every 120 minutes (20 x 6 minutes).
Default: 5 (In the shipped config.dat, this is overridden by the value 6.)
How / where to set: See “Editing the config.dat file” on page 408.
Default: 0
How / where to set: See “Editing the config.dat file” on page 408.
Default: ""
In the shipped config.dat on UNIX, the default values are overridden as
follows:
■ wd_ctmexit_1: -LIMIT "10 M" -PATH $HOME
■ wd_ctmexit_2: -LIMIT "90 M"
In the shipped config.dat on Windows, the default values are overridden as
follows:
■ wd_ctmexit_1: -LIMIT 10M -PATH C:\
■ wd_ctmexit_2: -LIMIT 90
How / where to set: See “Editing the config.dat file” on page 408.
Default: "" (In the shipped config.dat, for wd_ctmexit_1 and wd_ctmexit_2,
the default is overridden by "Low on database space.")
How / where to set: See “Editing the config.dat file” on page 408.
For example, if the value of this parameter is 20, and the basic time interval
unit (as defined in parameter WD_INTERVAL) is 5 minutes, the exit script will
be invoked every 100 minutes (20 x 5 minutes).
Default: 5 (In the shipped config.dat, this is overridden by the value 20.)
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N (In the shipped config.dat, this is overridden by the value Y.)
How / where to set: See “Editing the config.dat file” on page 408.
Default: "" (In the shipped config.dat, for both wd_ctmexit_1 and
wd_ctmexit_2, this is overridden by the value CTMDISKSPACE.)
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Default: 5 ms (In the shipped config.dat, this is overridden by the value 30.)
How / where to set: See “Editing the config.dat file” on page 408.
The # used in the following user exit parameters represents a separate number for
each user exit that can be included in the CONTROL-M Watchdog process (see
“Watchdog facility exits” on page 528). A user exit can be either a user supplied
script/executable file or a CONTROL-M utility.
Default: ""
How / where to set: See “Editing the config.dat file” on page 408.
Default: ""
How / where to set: See “Editing the config.dat file” on page 408.
For example, if the value of this parameter is 2, and the basic time interval unit
(as defined in parameter WD_INTERVAL) is 5 minutes, the exit script will be
invoked every 10 minutes (2 x 5 minutes).
Default: 5
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Default: ""
How / where to set: See “Editing the config.dat file” on page 408.
Valid values: Y, N
Default: N
How / where to set: See “Editing the config.dat file” on page 408.
Default: 5 ms
How / where to set: See “Editing the config.dat file” on page 408.
CONTROL-M/Agent parameters
This section lists and describes the following categories of CONTROL-M/Agent
parameters:
In this section, the information in the tables is listed alphabetically according to the
Agent system parameter names. Parameters that can be changed from the
CONTROL-M Configuration Manager are indicated by including the descriptive
names (as they appear in the CONTROL-M Configuration Manager) in parenthesis.
Valid values:
■ Started
■ Stopped
Default: Y
AGCMNDATA <Port number>/<Timeout> for the Server-to-Agent port. Port number
specifies agent computer port that receives data from the Server computer.
Verify that this port is not used for any other purpose. Must match
Server-to-Agent port number in CONTROL-M/Server. The timeout value
is the COMTIMOUT communication job-tracking timeout in seconds.
Mandatory. Example: 7006/30
Default: 7006
AGENT_DIR Location of files used by CONTROL-M/Server.
ALLOW_COMM_INIT Determines if the agent can open a connection to the server when working
in persistent connection mode.
(Allow Comm Init)
Valid values: Y, N
Default: Y
AR_AG_COMM_PORT Internal port used only when the agent is working in persistent connection
mode. This port is selected by the installation, which validates that it is
free. If this port is not free when the agent is started in persistent
connection mode, or when it is shifted from transient to persistent during
runtime, the agent automatically finds a new free port and updates the
parameter accordingly.
(Agent-to-Server Port Number) Port number specifies the Server computer port that receives data from the
agent computer. Verify that this port is not used for any other purpose.
This value must match the Agent-to-Server Port Number in
CONTROL-M/Server. The Timeout value is the COMTIMOUT
communication job-tracking timeout in seconds. Mandatory. Example:
7005/30. Note: Increasing the Timeout value reduces agent performance.
Default: 7005
AUTOEDIT_INLINE Flag that indicates whether all AutoEdit variables will be set as
environment variables in the script.
(AutoEdit Inline)
Valid values: Y (yes), N (no)
Default: Y
CM_APPL_TYPE Default control module.
Default: OS
CMLIST List of Control Modules. For internal use only.
COMM_TRACE Flag indicating whether communication packets that
CONTROL-M/Agent sends to and receives from CONTROL-M/Server
are written to a file. If set to 1, separate files are created for each session
(job, ping, and so forth). This parameter can only be changed after
completing the installation.
Default: 0 (off)
Default: SSL=N
COMMRETSLP Time in seconds (integer value} to wait between each attempt to attach to
the CONTROL-M/Server.
Default: 1
CTMPERMHOSTS <one or more TCP/IP addresses or DNS names separated by |>. Each
value identifies an authorized CONTROL-M/Server host where a backup
(Authorized CONTROL-M/Server is installed. (This parameter was previously called
CONTROL-M/Server Hosts) Mirror CONTROL-M/Server Host Name.) Specify this parameter if one or
more CONTROL-M/Servers have been designated as backups and can
connect to this agent in case of failover. For information about backup
server configuration, see the CONTROL-M Administrator Guide.
Mandatory. At least one primary host name should be specified. Example:
192.138.28.121|aristo.isr.bmc.com/mybksys1|192.138.28.123
CTMS_ADDR_MODE {IP}
(CTMS Address Mode) If this parameter is set to IP, the IP address instead of the host name is
saved in CTMS_HOSTNAME. Use this parameter when CONTROL-M
runs on a computer with more than one network card.
CTMSHOST CONTROL-M/Server host name. Name of the primary host running
CONTROL-M/Server.
(Primary CONTROL-M/Server
Host)
DBGLVL CONTROL-M/Agent diagnostic level (for use by Technical Support).
Determines types of diagnostic messages generated. This parameter is
normally set to zero (no diagnostics).
Default: 0
EVENT_TIMEOUT Job Tracking Timeout. Tracker event timeout in seconds.
Default: Latin-1
LISTEN_INTERFACE The network interface the agent is listening on. It can be set to a specific
hostname or IP address so that the agent port is not opened in the other
(Listen to Network Interface) interfaces.
However, it can differ when either a cluster installation or the agent host
name has aliases.
LOGKEEPDAYS Number of days to retain agent proclog files. After this period, agent
proclog files are deleted by the New Day procedure.
(Days To Retain Log Files)
Note: This parameter is relevant only if CONTROL-M/Server does not
pass a parameter that determines how many days to keep log files.
Default: 1
PERSISTENT_CONNECTION Determines if the agent is working in persistent or transient
communication mode.
Valid values: Y, N
Default: N
PROTOCOL_VERSION Server-Agent communication protocol version.
(TCP/IP Timeout) When the value of ‘TCP/IP timeout’ is changed, using the configuration
utility or CCM, the timeout part of the AGCMNDATA and
ATCMNDATA parameters are changed.
Default:120
TRACKER_EVENT_PORT Number of the port for sending messages to the Tracker process when jobs
end
(Tracker Event Port)
UTTIMEOUT Maximum time (in seconds) the agent waits after sending a request to
CONTROL-M/Server. This timeout interval should be longer than the
(Timeout for Agent utilities) TCP/IP Timeout.
Default: 120
Default: UTF-8
Default: $CONTROLM/runtime
Modifiable by ctmunixcfg: No
CTM_PRM_DONT_DELETE By default, temporary scripts generated from jobs are deleted at the
end of job execution. If this value is set to YES, temporary scripts are
(Temporary Scripts Saving) not deleted.
Default: No
Default: -x
Default: -x
Default: /bin/su
Modifiable by ctmunixcfg: No
PRINTER_NAME Default printer for job output (SYSOUT).
Default: 644
Modifiable by ctmunixcfg: No
RJX_CONN_MODE The RJX mode used in RJX jobs.
Default: 2
Modifiable by ctmunixcfg: No
Modifiable by ctmunixcfg: No
RJX_CONN_TOUT The time interval, in seconds, between attempts to restore the
connection.
(Time Interval between Restore
Connections) Default: 120 seconds
Modifiable by ctmunixcfg: No
RJX_DETAILS_TO_SYSOUT Determines whether to include details related to the remote
connection in the job SYSOUT of jobs executed on a remote host.
(Print Details to SYSOUT)
Valid values: Y, N
Default: Y
Modifiable by ctmunixcfg: No
RJX_OVMS_DEFAULT_QUEUE For a CONTROL-M/Agent submitting jobs to an OpenVMS remote
host, the default batch queue to which the CONTROL-M/Agent
(Default Queue for OpenVMS submits jobs.
Remote Host)
If this parameter is not specified, the CONTROL-M/Agent submits
jobs to sys$batch (the system’s default batch queue).
Default: sys$batch
Modifiable by ctmunixcfg: No
Default: Y
Modifiable by ctmunixcfg: No
RJX_SYSOUT_DIR A directory to store temporary files
(AgentLess Temporary Directory) These files are automatically removed to CONTROL-M/Agent when
the jobs end and the network connection is available or restored.
Default: period (.), which means that the files are stored in the user
home directory of the job’s owner in the remote host.
Modifiable by ctmunixcfg: No
SMTP_PORT_NUMBER The port number on which the SMTP server communicates.
Default: 25
Modifiable by ctmunixcfg: No
SYSOUT_MODE Octal value indicating file access mode of the SYSOUT (output) file.
777 indicates the highest level of access.
Default: 660
Modifiable by ctmunixcfg: No
SYSOUT_NAME {JOBNAME | MEMNAME}
If set to JOBNAME, parameter Jobname is used in the SYSOUT file
(Sysout Name) instead of parameter Memname.
Default: MEMNAME
Default: UTF-8
Default: Blank
Default: Blank
Default: Y
Default: Y
Valid values:
■ N – All procedures invoked by the job are run outside the job
object.
■ Y – All procedures invoked by the job are run inside the job
object.
Default: Y
Valid values:
■ Y – Jobs are submitted with the permissions and environment
variables of the specified user.
■ N – Jobs are submitted with the permissions and environment
variables of the local system account.
Default: 2
Modifiable by ctmwincfg: No
RJX_CONN_TRY maximum number of attempts to be made to restore the connection
Default: 3
Modifiable by ctmwincfg: No
RJX_CONN_TOUT time interval, in seconds, between attempts to restore the connection
Modifiable by ctmwincfg: No
RJX_DETAILS_TO_SYSOUT Determines whether to include details related to the remote
connection in the job SYSOUT of jobs executed on a remote host.
(Print Details to SYSOUT)
Valid values: Y, N
Default: Y
Modifiable by ctmwincfg: No
Modifiable by ctmwincfg: No
RJX_OVMS_SETVERIFY For a CONTROL-M/Agent submitting jobs to an OpenVMS remote
host, this parameter specifies whether or not to print commands in
(Save Commands in the SYSOUT in the SYSOUT of a job.
OpenVMS Remote Host)
Valid values:
■ Y – Implements SET VERIFY, which prints commands in the job
SYSOUT
■ N – Implements SET NOVERIFY, which does not print
commands in the job SYSOUT
■ E – Specifies that the verification value is taken from the
environment (acco
Modifiable by ctmwincfg: No
RJX_SYSOUT_DIR A directory to store temporary files
Default: period (.), which means that the files are stored in the user
home directory of the job’s owner in the remote host.
Modifiable by ctmwincfg: No
RUN_USER_LOGON_SCRIPT Indication if a user-defined logon script should be run by the
CONTROL-M/Agent before running the standard user logon script.
(Run user 'Logon Script')
Valid values:
■ Y – The user-defined logon script is run, if it exists.
■ N – The user-defined logon script is not run.
Default: N
Default: 25
Default: control@m
Modifiable by ctmwincfg: No
SYSOUT_NAME Determines the prefix for the SYSOUT file name.
Default: Memnam
Default: 2
Valid values: Y, N
Default: Y
Modifiable by ctmwincfg: No
■ Agent service
■ FileWatcher service
Valid values:
— Allow Service to Interact with Desktop – This option is valid only if the
service is running as a local system account. See “Defining a
CONTROL-M/Agent account (Windows only)” on page 170.
■ This Account – User account under which CONTROL-M Agent service will
run.
Valid values:
■ Automatic – Service should start when the system starts.
■ Manual – User or a dependent service can start service.
■ Disabled – User or a dependent service cannot start service.
Default: Automatic
C
C Exits
This section presents the following topics:
User Exits
This section describes the following topics:
The following is a sample text file in the format that is passed to the CTMUE101 exit:
JOBNAME daily_job
JOBNO 30
DESCRIPT
APPLIC STRESS
APPLGROUP STRESS
SCHEDTAB STRESS
AUTHOR ctm600
OWNER ctm600
PRIORITY 0
CRITICAL N
CYCLIC N
RETRO N
AUTOARCH N
TASKCLASS
CYCLICINT 0
TASKTYPE C
DATEMEM
NODEGRP
computer
NODEID
DOCLIB
DOCMEM
MEMLIB
MEMNAME
OVERLIB
CMDLINE ./stress_cmd_spl.ctm600
MAXRERUN 0
MAXDAYS 0
MAXRUNS 0
FROMTIME
UNTIL
MAXWAIT 0
DAYSTR ALL
WDAYSTR
MONTHSTR YYYYYYYYYYYY
AJFSONSTR NNNNNNNNNNNNN
CONF N
UNKNOWNTIM 0
DAYSCAL
WEEKCAL
CONFCAL
CAL_ANDOR O
SHIFT
ADJUST_COND
STARTENDCYCIND S
CREATIONUSERID ctm600
CREATIONDATETIME 20001113070229
CHANGEUSERID
CHANGEDATETIME
RELATIONSHIP
GROUPID 0
TABROWNO 1
Example
The following exit script changes the Days parameter (DAYSTR) for jobs that were
scheduled on the first day of the month, so that these jobs will be ordered on the
second day of the month.
#!/bin/ksh
cp $1 /tmp/ue101.$$
sed -e 's/DAYSTR 1/DAYSTR 2/' /tmp/ue101.$$ > $1
The following is a sample text file in the format that is passed to the CTMUE102 exit:
JOBNO 0
ORDERNO 19450
PRIORITY 1039
CRITICAL N
TASKTYPE C
CYCLIC N
CONFIRM_R N
CONFIRMED N
RETRO N
AUTOARCH N
TASKCLASS
HOLDFLAG N
STATUS N
STATE E
CYCLICINT 0
APPLGROUP dw_S_A_AAS
NODEGRP
NODEID fire
MEMLIB /mdw/oper/tgt/scripts/shells
MEMNAME dw##r#####
OVERLIB /mdw/oper/tgt/scripts/shells/overlib_all
CMDLINE sleep 30
ODATE 19960229
PROCID
RERUN_NO 0
OSCOMPSTAT 0
OSCOMPMSG
NEXTTIME
PREVDATE
NEXTDATE
STARTRUN
ENDRUN
MAXRERUN 0
FROMTIME
UNTIL
JOBNAME dwlnr21AAS
SCHEDTAB CREATED
OWNER ctm600
MAXWAIT 7
APPLIC DW_ln
RUNCOUNT 1
DAILYNAME ctm600
AJFSONSTR YYNNYNNNNNNNN
DESCRIPT Datawarehouse ln snapshot sort and form
DOCMEM dwlnr1
DOCLIB /mdw/cntlm/doc
MAXDAYS 0
MAXRUNS 0
UNKNOWNTIM 0
STARTENDCYCIND S
TRIGGER_TAG
GROUP_ORD 0
AUTHOR
Example
The following exit script checks if the job has a Owner of root and changes the Owner
for these jobs to nobody.
#!/bin/ksh
cp $1 /tmp/ue102.$$
sed -e 's/OWNER root/OWNER nobody/' /tmp/ue102.$$ > $1
The flat text file that is passed to the exit contains the name of the Daily (SYSTEM),
time, and original scheduling date (Odate) of the procedure.
The following is a sample text file in the format that is passed to the CTMUE103 exit:
DAILY_NAME SYSTEM
TIME 1300
ODATE 20001121
Example
The following exit script runs a procedure that performs various actions before the
New Day procedure is run.
#!/bin/ksh
/opt/controlm/scripts/run_pre_New_Day_proc
The following is a sample text file in the format that is passed to the CTMUE104 exit:
DAILY_NAME SYSTEM
TIME 1319
ODATE 20001121
Example
The following exit script runs a procedure that performs various actions after
completion of the New Day procedure.
#!/bin/ksh
/opt/controlm/scripts/run_post_New_Day_proc
The flat text file that is passed to the exit contains the name of the User Daily, time,
and original scheduling date (Odate) of the User Daily job.
The following is a sample text file in the format that is passed to the CTMUE105 exit:
DAILY_NAME my_daily
TIME 1321
ODATE 20001121
The flat text file that is passed to the exit contains the name of the User Daily, time,
and original scheduling date (Odate) of the User Daily job.
The following is a sample text file in the format that is passed to the CTMUE106 exit:
DAILY_NAME my_daily
TIME 1322
ODATE 20001121
NOTE
If the User Daily job fails, the User Exit 106 (UE106) will not be executed.
■ To run both the ctmdiskspace and ctmdbspace utilities, set the # to 2 (enables
both WD_CTMEXIT1 and CTMEXIT2).
A Specify the file name of the script or binary that resides in the
ctm_server/exe_<operatingSystem> directory in the WD_CTMEXIT_# _SCRIPT_FILE
parameter.
3 Define the number of basic time interval units that should pass before re-invoking
the exit script in the WD_CTMEXIT_# _INTERVAL parameter. Range: 1-1440.
Default: 20
The basic time interval unit is defined in parameter WD_INTERVAL. For example,
if the value of this parameter is 20, and the basic time interval unit (as defined in
parameter WD_INTERVAL) is 6 minutes, the exit script will be invoked every 120
minutes (20 x 6 minutes).
4 Define the number of minutes that should be allowed to pass before the exit script
is terminated in the WD_CTMEXIT_# _TIMEOUT parameter.
5 Define situation under which the exit script should or should not run, as follows:
■ If the exit script should be run when CONTROL-M/Server is running, set the
value of the WD_CTMEXIT_# _RUN_STATE parameter to Y. Otherwise, set the
value to or N.
■ If the exit script should be run when CONTROL-M/Server is suspended, set the
value of the WD_CTMEXIT_# _SUSPEND_STATE parameter to Y. Otherwise, set
the value to or N.
2 Specify the file name of the script or binary that resides in the
ctm_server/exe_<computer> directory in the WD_USEREXIT_# _SCRIPT_FILE
parameter.
5 Define the number of basic time interval units that should pass before rerunning
the exit script in the WD_USEREXIT_# _INTERVAL parameter. Range: 1-1440.
Default: 20
The basic time interval unit is defined in parameter WD_INTERVAL. For example,
if the basic time interval unit (as defined in parameter WD_INTERVAL) is 6
minutes, and you set the value of this parameter to 20, the exit script will be run
every 120 minutes (20 x 6 minutes).
6 Define the number of minutes that should be allowed to pass before the exit script
is terminated in the WD_USEREXIT_# _TIMEOUT parameter.
7 Define situation under which the exit script should or should not run, as follows:
■ If the exit script should be run when CONTROL-M/Server is running, set the
value of the WD_USEREXIT_# _RUN_STATE parameter to Y. (Otherwise, set the
value to or N.)
■ If the exit script should be run when CONTROL-M/Server is suspended, set the
value of the WD_USEREXIT_# _SUSPEND_STATE parameter to Y. (Otherwise, set
the value to or N.)
Example
2 Define the maximum time the Watchdog facility should wait for the user defined
script to run in the WD_ERROR_HANDLER_TIMEOUT parameter.
D
D SNMP interface
This appendix presents the following topics:
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
CONTROL-M/EM and SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
SNMP trap format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
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) on their local
computer and use the client to contact one or more SNMP servers (or agents) that
execute on remote computers.
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
server computer, usually a failure event (hardware or software, permanent or
temporary). Customization at the client site determines, according to the trap codes,
whether an Alert message appears on the manager’s 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.
The generated SNMP traps are enterprise-specific traps (that is, field generic-trap is
set to 6).
18 CLOSED FROM EM Initial value is empty. If the a Remedy ticket was closed from
CONTROL-M/EM, the value is Y.
19 TICKET NUMBER Remedy ticket number
20 RUN COUNTER When a job is executed more than once within a scheduling
day, this counter uniquely identifies each execution of that job.
This way you know exactly in what instance of the job’s
execution the remedy ticket was opened.
Customization
The customization procedures, described below, are required to support SNMP traps
issued by CONTROL-M/EM.
The Services file may need to be updated to include the SNMP monitor trap port. The
following entry must be added to the /etc/services file (on UNIX) or
WINDIR\system32\drivers\etc\Services file (on Microsoft Windows), if not already
present. After adding the line, verify that the host of the relevant network
management application is listening to the port number indicated in this line:
■ SnmpSendActive
■ SnmpHost
■ SendSnmp
For more information about these system parameters, see Table 70 on page 414.
E
Mass conversion of agents and
E
remote hosts
The following topic describes how to perform a mass conversion of
CONTROL-M/Agents to remote hosts:
For instructions on converting individual agents to remote hosts, see page 70.
For instructions on converting a remote host to a CONTROL-M/Agent, see page 67.
2 Determine all the owners that are used on the agent computers, as follows:
Log onto the database server and run the following SQL commands to determine
all the owners used on the agent computer:
Add one of the following on a separate line at the end of the commands:
EXAMPLE
To convert a node with the name cyborg on Oracle, log onto the sql database server and
run the following commands to determine all the owners used on cyborg:
3 Define all the owners, and their authentication settings, that you identified in step
2. You can do this using either of the following tools:
■ ctmsetown utility—you can run a script using the ctmsetown utility to define all
the owners used on the agent computers. For more information, see the
CONTROL-M Utility Guide.
4 For each agent, verify once more that no jobs have been submitted or are running.
6 Redefine each relevant agent as a remote host, using either of the following
methods:
■ Run the ctmhostmap utility with the -force option. For more information, see
CONTROL-M Utility Guide.
F
F Working with Remedy
The following topics in this section describe how to configure the connection to the
Remedy server:
1 Enter remedy_configure.
2 Select the appropriate menu items, and enter the required information.
The utility sets the Remedy server host name, port, user name, and password. The
configuration parameters, except for the encrypted password, are saved in the
RemedyConf.xml file.
For the location of the utility and the configuration file, see Table 103 and Table 104.
NOTE
When Remedy Server is configured to use a “port mapper” the Remedy port should be set to 0
(default), otherwise the port is the Remedy server port.
The other two sections contain configuration settings that are specific for each
Remedy server version. The first section is for Remedy 6, while the second is for
Remedy 7.
Each Remedy server version contains two Action configurations; one for opening the
incidents and one for closing them. Each Action configuration contains the form
name used for the specific action as shown in the following table. The schema name is
used for the form name.
Table 105 Form names used for opening and closing incidents (part 1 of 2)
Server Action Form name
Remedy 6 open HPD:HelpDesk
close HPD:HelpDesk
Table 105 Form names used for opening and closing incidents (part 2 of 2)
Server Action Form name
Remedy 7 open HPD:IncidentInterface_Create
close HPD:IncidentInterface
An incident form can either be created directly (the default process for Remedy 6) or
indirectly (the default process for Remedy 7) by the Remedy server. When the
indirect process is used to create an incident form, the Remedy sever first creates an
intermediate form that contains an ID number that identifies the real (target) form.
The intermediate form must be resolved to obtain the real form ID.
2 For the RealFormFieldID, specify a field ID number, that will contain the real form
ID.
When Remedy incidents are created, default values are used for each of the Remedy
incident fields. The default values are listed in the RemedyConf.XML file (for the
location of the configuration file, see Table 104). Each Remedy incident field consists
of the following attributes:
The Remedy field ID values for additional Remedy fields must be obtained from the
Remedy administrator.
The configuration file contains the following built-in Remedy fields that are
automatically populated by BMC Batch Manager and CONTROL-M/Server.
■ Summary
■ Note
■ Urgency
NOTE
The built-in fields are used to resolve the field ID in the Remedy form. When BMC Batch
Manager or CONTROL-M/Server creates an incident, the built-in fields are automatically
resolved, overwriting any values that may have been manually specified. For more
information about Remedy fields and parameters, see the Remedy documentation.
Index
Symbols
"Context" parameter Domain Settings panel 389
DIAG ini file 334 ADJUST_COND
#! statement 135 parameter 484
$0 reserved variable 137 Advanced button
%errorlevel% Summary Panel 400
exit code 141 Advanced settings panel
*default parameter actions 401
DIAG ini file 333 tree format 400
.bat AG_LOG_ON
DOS batch files 142 configuration parameter 506
.cmd AGCMNDATA
REXX-language 142 configuration parameter 506
.cshrc file 134 Agent communication parameters
.login file 134 description 464
.profile file 134 Agent platforms
_sleep utility 141 communication parameters 464
Shout messages to 118
AGENT_DIR
Index 543
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index 545
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index 547
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index 549
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index 551
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index 553
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index 555
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
V
-v flag 137
verify user
DIAG component prefix 372
ViewPoint is empty