Professional Documents
Culture Documents
Control M Server For Unix Admin Guide PDF
Control M Server For Unix Admin Guide PDF
Unix
Administrator Guide
Version 6.0.03
Telephone
Fax
Fax
iii
Customer Support
You can obtain technical support by using Response Online (support from the Web) or Response On Demand.
To expedite your inquiry, please see Before Contacting BMC Software, below.
Response Online
You can obtain technical support from BMC Software 24 hours a day, seven days a week by accessing the
technical support Web site at http://www.bmc.com/support.html. From this site, you can
Response On Demand
In the USA and Canada, if you need technical support and do not have access to the Web, call 800 537 1813.
Outside the USA and Canada, please contact your local support center or your local sales office for assistance.
product information
product name
product version (release number)
license number and password (trial or permanent)
iv
messages received (and the time and date that you received them)
product error messages
messages from the operating system, such as file system
full
messages from related software
vi
Contents
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Overview
Contents
vii
Utilities
viii
ctmldnrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82
ctmloadset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86
ctmlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-91
ctmordck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
ctmorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96
ctmpasswd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
ctmping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103
ctmpsm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-106
ctmrpln . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
ctmruninf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-124
ctmshout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-127
ctmshtb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-129
ctmstats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-130
ctmstvar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-133
ctmsuspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-134
ctmsys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-135
ctmudchk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-145
ctmudlst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-147
ctmudly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-149
ctmvar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-150
ctmwhy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-154
ctm2snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-155
ecactltb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157
ecaqrtab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-158
Chapter 3
Security
Contents
ix
Maintenance
Customization Parameters
Chapter 6
User Exits
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Appendix B
Glossary
Index
Contents
xi
xii
Figures
Figures
Figure 1-1
Figure 1-2
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 2-8
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
Figure 4-1
Figure 4-2
Figure 4-3
Figure 4-4
Figure 4-5
Figure 4-6
Figure 4-7
Figure 4-8
Figure 4-9
Figure 4-10
Figure 4-11
Figure 4-12
Figures
xiii
Figure 4-13
Figure 4-14
Figure 4-15
Figure 7-1
Figure 7-2
Figure 7-3
Figure 7-4
Figure 7-5
Figure 7-6
xiv
Tables
Tables
Table 1-1
Table 1-2
Table 1-3
Table 1-4
Table 1-5
Table 1-6
Table 1-7
Table 1-8
Table 1-9
Table 1-10
Table 1-11
Table 1-12
Table 1-13
Table 1-14
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 2-9
Table 2-10
Table 2-11
Table 2-12
Table 2-13
Table 2-14
Tables
xv
Table 2-15
Table 2-16
Table 2-17
Table 2-18
Table 2-19
Table 2-20
Table 2-21
Table 2-22
Table 2-23
Table 2-24
Table 2-25
Table 2-26
Table 2-27
Table 2-28
Table 2-29
Table 2-30
Table 2-31
Table 2-32
Table 2-33
Table 2-34
Table 2-35
Table 2-36
Table 2-37
Table 2-38
Table 2-39
Table 2-40
Table 2-41
Table 2-42
Table 2-43
Table 2-44
Table 2-45
Table 2-46
Table 2-47
Table 2-48
Table 2-49
Table 2-50
Table 2-51
Table 2-52
Table 2-53
Table 2-54
xvi
Table 2-55
Table 2-56
Table 2-57
Table 2-58
Table 2-59
Table 2-60
Table 2-61
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 3-7
Table 3-8
Table 3-9
Table 3-10
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Table 4-5
Table 4-6
Table 4-7
Table 4-8
Table 4-9
Table 4-10
Table 4-11
Table 4-12
Table 4-13
Table 4-14
Table 4-15
Table 4-16
Table 5-1
Table 5-2
Table 5-3
Table 5-4
Table 5-5
Table 5-6
Tables
xvii
Table 5-7
Table 5-8
Table 5-9
Table 5-10
Table 5-11
Table 5-12
Table 5-13
Table 5-14
Table 5-15
Table 5-16
Table 5-17
Table 5-18
Table 5-19
Table 5-20
Table 6-1
Table 6-2
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 7-5
Table 7-6
Table A-1
Table B-1
xviii
About . . .
HP-UX 9000 10.2 (Sybase only), 11.0 and 11i with 64-bit support
Digital Unix (OSF) 4.0f with 64-bit support, and 5.0a, 5.0b and 5.1
xix
Overview
Introduces key features and concepts of CONTROL-M.
Chapter 2
Utilities
Provides a detailed description of CONTROL-M utilities.
Operating instructions and examples are included for each
utility.
Chapter 3
Security
Discusses security concepts of CONTROL-M and
ENTERPRISE/CS. Provides instructions for the security
utility included with CONTROL-M.
Chapter 4
Maintenance
Describes how to perform various functions related to
startup/shutdown of CONTROL-M/Server, maintenance of
the CONTROL-M database, setting CONTROL-M
parameters and troubleshooting.
Chapter 5
Customization Parameters
Describes parameters used to customize and configure the
CONTROL-M/Server installation.
Chapter 6
User Exits
Describes user-defined procedures that can be used to
modify certain information before it is processed.
Chapter 7
Appendix A
Appendix B
Glossary
Index
xx
Related Publications
xxi
Notational Conventions
The following abbreviations and terms are used in this guide:
ENTERPRISE/CS = Enterprise Controlstation.
The following table describes conventions used in this guide.
<key>
{Option A|Option B}
[Option]
<variable>
cd
<controlm_path>
xxii
Wildcards or
Mask Characters
xxiii
xxiv
Overview
Enterprise Controlstation
This component is the central point of control for production
operations. It provides the graphical user interface to the production
control and scheduling system. From this workstation (referred to as
the ENTERPRISE/CS workstation), you can view the status of
jobs in any part of the system. You can issue requests, modify job
parameters, and handle exceptions to ensure smooth production job
flow.
Overview
1-1
1-2
Description
CONTROL-M Database
Server-Agent Interaction
Load Balancing
Overview
1-3
Topic
Description
Failover Planning
Runtime Statistics
CONTROL-M Log
Automatic Problem
Detection Tools (APDT)
CONTROL-M Administrator
Heartbeat Monitor
Watchdog Facility
User Exits
CONTROL-M Database
The CONTROL-M database is the repository of operational data relating
to the functioning of the CONTROL-M data center. One database exists
for each CONTROL-M data center. The database is maintained by
CONTROL-M/Server, using a dedicated or shared SQL server.
The CONTROL-M database contains the following information:
CONTROL-M log.
BMC Software, Inc., Confidential and Proprietary Information
1-4
Server-Agent Interaction
CONTROL-M/Agent handles requests from CONTROL-M/Server. A
request can consist of:
Overview
1-5
1-6
Table 1-1
Communication Statuses
Status
Description
Available
Unavailable
Disabled
Overview
1-7
Interrupted Communication
If communication is interrupted between CONTROL-M/Server and one
or more Agent platforms, CONTROL-M/Server sends a special Shout
message to ENTERPRISE/CS. All jobs that were running on the affected
Agent platform(s) are reclassified in the Active Jobs file as Unknown.
The status of the Agent platform is changed to Unavailable.
If processing on the Agent platform was not interrupted, any job
submitted to a platform prior to the interruption continues executing.
When communication between CONTROL-M/Server and an Agent
platform is restored, CONTROL-M checks the status of any jobs that
were running on the Agent platform and updates the status in the Active
Jobs file. If a job completed execution during the period of interrupted
communication, CONTROL-M/Server retrieves its completion status
from the Agent platform.
Time-Related Functions
The time value used for any CONTROL-M function is determined by the
system time on the Server platform. This applies to the following:
Examples
1-8
Load Balancing
Under the Agent Technology implementation of CONTROL-M, you
have the additional option of scheduling jobs using the CONTROL-M
load-balancing feature. This feature enables you to submit a job to a
node group rather than to a specific Agent platform. This node group
represents a user-defined list of Agent platforms that are capable of
executing a given job. CONTROL-M/Server uses a load-balancing
algorithm to determine which of these Agent platforms is best able to
handle execution of the job at that moment and submits the job to that
node.
BMC Software, Inc., Confidential and Proprietary Information
Overview
1-9
Failover Planning
As CONTROL-M is integrated in the production environment of the data
center, it becomes increasingly important to ensure that interruptions of
CONTROL-M functionality are as short as possible.
A properly designed and executed failover plan ensures that
CONTROL-M functions are resumed as soon as possible if a recovery is
necessary.
Failover planning for CONTROL-M should provide for the following
contingencies:
1-10
Overview
1-11
1-12
Odate is the scheduling date assigned to a job when the job is ordered.
See Date Definition Concepts in Chapter 2 of the Enterprise
Controlstation User Guide for more information regarding this date.
2. The message FORMATTING AJF is displayed in the
ENTERPRISE/CS Communication Status window for the data
center.
3. A selective cleanup of the Active Jobs file is performed. 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.
Note
A job for which the Max Wait parameter is specified that ends with a
status of NOTOK is not deleted from the Active Jobs file until the Max
Wait parameter is exceeded.
BMC Software, Inc., Confidential and Proprietary Information
Overview
1-13
1-14
10. CONTROL-M begins downloading the new Active Jobs file to the
ENTERPRISE/CS workstation.
Note
Scheduling Jobs
The New Day procedure is the master scheduler for production jobs.
It orders production jobs according to their job processing definitions,
and can also order User Daily jobs that, in turn, order regular production
jobs.
In a site with a relatively small number of production jobs, the simplest
and most straightforward method of scheduling jobs is to order them
directly via the New Day procedure.
It is preferable to order jobs using User Daily jobs if two or more of the
following conditions exist:
Overview
1-15
Figure 1-1
User
Daily
Scheduling
Table Name
SYSTEM
UDAILIES
SYSTEM
TABLE1
UDAILY1
UDAILY1
PAYABLES
RECEIVABLES
UDAILY2
INVENTORY
New Day
Procedure
1
CONTROL-M
Monitor
4
UDAILY1
UDAILY2
6
Scheduling
Table Name
Job
UDAILIES
UDAILY1
UDAILIES
UDAILY2
TABLE1
TABLE1
PROD_JOB1
PAYABLES
PROD_JOB3
PAYABLES
PROD_JOB4
RECEIVABLES
PROD_JOB5
INVENTORY
PROD_JOB6
INVENTORY
PROD_JOB7
PROD_JOB2
1-16
Overview
1-17
1-18
Overview
1-19
Script File
Job Name
ACCUDAILY1
Application
USER_DAILIES
Task Type
Job
Description
Scheduling Table
ACCTDAILY
Author
michelle
Owner
bill
Mem Name
udaily
Mem Lib
/usr/bill/bin
AutoEdit
Assignments
%%PARM1 = UDAILY1
You can manually order the User Daily job ACCUDAILY1 whenever
you want to order the jobs in the ACCOUNTING Scheduling table and
the jobs in the ACCGROUP Group Scheduling table, or you can assign
Scheduling table ACCTDAILY to User Daily name SYSTEM, in which
case ACCUDAILY1 is ordered by the New Day procedure.
When ACCUDAILY1 submits the script file with the parameter $1 set to
UDAILY1, the command actually executed by the script is:
ctmudly
UDAILY1
1-20
Each User Daily job has its own Date Control record, enabling the User
Daily job to maintain control over its last running date. The last running
date of the User Daily job is recorded in the Date Control record in a
field called UDLAST. The Date Control record is analyzed to determine
the current running date, the last running date, and possible error
situations.
The ctmudlst utility can be used to change the UDLAST field in the Date
Control record. Changing this date field affects the scheduling of jobs as
described below.
Use of the Date Control Record by User Daily Jobs
When a User Daily is run, UDLAST (the last running date of the User
Daily job, recorded in the Date Control record) is compared to Odate
(the current installation working date).
Overview
1-21
If UDLAST and Odate are equal, it means that the User Daily job
has already run today. In that case, a message is issued to the
CONTROL-M log, and the User Daily job does not order any jobs.
If, for any reason (e.g., hardware problems), the New Day procedure
did not run for one or more days, it is not necessary to run it for days
missed. However, production jobs (including User Daily jobs) whose
job processing definition includes the parameter Retro will be
ordered automatically for all the dates on which they were supposed
to be ordered. Retroactive ordering of jobs is performed according to
each jobs scheduling criteria.
For example, if the computer did not operate from the 20th to
the 23rd, then a job which was originally scheduled to run on the
20th will not have run on that day. When it is finally run on the 24th,
the New Day procedure determines whether or not its associated jobs
should be retroactively scheduled to run using the logical date of
the 20th. For additional information, refer to the Retro parameter in
Chapter 5, Job Processing Parameters, of the Enterprise
Controlstation User Guide.
Note
1-22
Overview
1-23
Table 1-2
Option
Description
Order
Force
For more information regarding the use of the Order and Force options,
see Ordering/Forcing Jobs in the Job Processing Definitions Chapter of
the Enterprise Controlstation User Guide.
1-24
Example
Figure 1-2
Shout Destination tables are created and maintained using the ctmsys
utility (described in Chapter 2, Utilities).
Designation of the active Shout Destination table can be performed using
one of the following methods:
Overview
1-25
Using utility ctmshtb. This utility accepts the name of the Shout
Destination table to make active.
This second method is especially useful. By defining CONTROL-M
jobs that execute the ctmshtb utility at specified times, the active
Shout Destination table designation can be changed automatically
according to the schedule that suits your requirements. ctmshtb is
described in Chapter 2, Utilities.
1-26
Table 1-3
Logical Name
Destination Type
Address Type
Overview
1-27
Table 1-3
Physical Name
O, L, and E
Note
All Shout messages are recorded in the CONTROL-M log. You would
select the log as a destination only when you do not wish to send the
message to any additional destination.
Runtime Statistics
CONTROL-M includes an option for accumulating and collating runtime
statistics for each defined job. These statistics are used for the following
purposes:
1-28
Overview
1-29
1-30
CONTROL-M Log
The CONTROL-M log contains a complete audit trail of every event
occurring in the CONTROL-M production environment. CONTROL-M
logs every item of meaningful information about its operation and about
the jobs under its supervision. Notification of both routine procedures
and error occurrences are recorded in the log.
Among the types of entries recorded in the CONTROL-M log are
messages regarding the following:
Overview
1-31
1-32
If the New Day procedure starts before you reset the clock, the New
Day procedure will start working before the clock is advanced, and
will continue normally (even if the clock is advanced while the New
Day procedure is in process). For more information about the New
Day procedure, see page 1-13.
Overview
1-33
Time-Dependent Shouts
Shout messages scheduled between 2:00 a.m. and 3:00 a.m. will be
issued, even though there may not be a delay in production since the
time frame for production is smaller.
The above also applies to jobs which have shout messages scheduled
at a later time (e.g., 6:00 a.m.). These jobs may be considered late
because of the tighter production time frame.
Jobs whose scheduled time overlaps the time gap created by the clock
shift may need manual intervention. For example, it is possible that a job
with a FROM value of 2:15 a.m. and an UNTIL value of 2:45 a.m. may
not be submitted at all. These jobs should be manually adjusted. A cyclic
job may have to be deleted and then resubmitted to continue the
processing cycle during the current day.
CONTROL-M Log File
The CONTROL-M Log file will not contain entries with timestamps
between 2:00 a.m. and 3:00 a.m. Any scripts and/or programs that rely
on log entry time should be checked for possible discrepancies as a result
of advancing the clock.
1-34
If the New Day procedure starts before 1:00 am, no special action
should be taken. The New Day procedure will run only once
(between 00:00 and 00:59).
If the New Day procedure starts exactly at 1:00 a.m., computer time
should not be turned back to 1:00 a.m. to avoid another New Day
process. A second New Day procedure requires manual intervention.
It is advisable to wait until 2:01 a.m., for example, and turn the clock
back to 1:01 a.m.
Time-Dependent Shouts
Shout messages scheduled between 1:00 a.m. and 2:00 a.m. may be issued
twice.
Time-Dependent Schedules (FROM-UNTIL or Cyclic Jobs)
Overview
1-35
The CONTROL-M Log file may contain entries with times earlier than
previous entries, due to the time shift. The same considerations that apply
to advancing the clock forward, should be applied to moving the clock
backwards.
CONTROL-M Administrator
The aim of the CONTROL-M administrator is to ensure the smooth and
efficient running of CONTROL-M with minimum interruptions and
optimal usage of available resources. To achieve this aim, the
responsibilities of the CONTROL-M administrator can be summarized as
follows:
1-36
Heartbeat Monitor
CONTROL-M contains an integral Heartbeat monitor that verifies that
TCP/IP communication with ENTERPRISE/CS is functional and that
ENTERPRISE/CS is responsive to messages from CONTROL-M.
This feature complements the ENTERPRISE/CS Heartbeat monitor that
verifies that communication with CONTROL-M is functional and that
CONTROL-M is responsive to messages from ENTERPRISE/CS.
The CONTROL-M Heartbeat monitor can operate in either of two
modes. These modes are described in Table 1-4.
Table 1-4
Mode
Description
Active Mode
Passive Mode
Overview
1-37
Parameter
Description
CTM_PRM_KPA_ACTIVE
Whether or not the CONTROL-M Heartbeat monitor
operates in active (Y) or passive (N) mode. Default: Y.
CTM_PRM_KPA_BETWEEN_MSGS
Amount of time (in seconds) to wait after receiving a
response to a heartbeat check before issuing the next
heartbeat check. Default: 300 seconds.
CTM_PRM_KPA_ROUNDTRIP_TIMEOUT
Time (in seconds) to wait for a response after issuing
a heartbeat check before declaring a communication
failure and initiating corrective actions. Default: 300
seconds.
Example
CTM_PRM_KPA_ACTIVE
CTM_PRM_KPA_BETWEEN_MSGS
CTM_PRM_KPA_ROUNDTRIP_TIMEOUT
Y
300
300
1-38
Table 1-6
Tool
Description
Event logger
Watchdog
ctmdbcheck
ctmdbtrans
ctmlog
Overview
1-39
IOALOG events
These are analogous to ctmlog events and involve reading and
writing to the IOA database.
DBASE events
These are associated with database access and involve reading and
writing to the CONTROL-M database.
Note
If not manually archived, these log files can occupy a large amount of
disk space. Careful selection of events to be logged will prevent
unnecessary large log files. For information about how to maintain the
log files, see Managing Log Files on page 1-41.
To configure the Event logger, insert the following commands in the
config.dat file (the text must be entered in uppercase):
CTM_LOGGER_SEVERITY {INFO|WARNING|ERROR}
CTM_LOGGER_CATEGORY {IOALOG|DBASE}
Table 1-7
Keyword
Description
INFO
WARNING
ERROR
1-40
Example
If no values are specified, no limits are placed on the size of the log file.
If values are specified, the size of the log file is checked and when the
limit is reached, the file is renamed logger.1. Entries continue to be saved
in the default logger file, and when the file next reaches its limit, the file
is renamed logger.2, and so on, until the maximum number of specified
generations is reached. The oldest file is deleted when another log file
exceeds the limit.
To set size and generation limits, specify the following parameters in the
config.dat file:
LIMIT_LOG_FILE_SIZE <file-size>
LIMIT_LOG_VERSIONS <number>
BMC Software, Inc., Confidential and Proprietary Information
Overview
1-41
Table 1-8
Variable
Description
LIMIT_LOG_FILE_SIZE
LIMIT_LOG_VERSIONS
Example
To set a limit to the size of the log file to 10 MB and to limit the number
of generations of the log file to 3, specify the following parameters in the
config.dat file:
LIMIT_LOG_FILE_SIZE 10
LIMIT_LOG_VERSIONS 3
Stack Trace
A stack trace is a useful debugging aid in working out how program
control reached a specific point. The stack trace is a file containing a
record of the events leading up to a process that abends.
CONTROL-M records the progression of the invocations called by
functions. If a process crashes, CONTROL-M generates a stack trace
sequence of functions that were called, leading up to the unexpected
error.
The stack trace is output to a proclog file, providing information about
the process that aborted. The log file generated contains information
relevant to Technical Support and is located in the directory:
<controlm_path>/ctm/proclog/<process_name>.<proc_ID>
The variables in this command line are described in the following table:
1-42
<controlm_path>
<process-name>
<process-ID>
Example
controlm/ctm/proclog/CS_LOG.6509
Overview
1-43
Watchdog Facility
CONTROL-M contains a special Watchdog (WD) facility which
automatically monitors various CONTROL-M processes and resources,
essential to the running of CONTROL-M, and sends an appropriate alert
when there is a problem. The Watchdog facility can also be used to
automatically execute user-defined scripts or CONTROL-M utilities.
(See Chapter 2, Utilities.)
If a Watchdog facility-monitoring check fails, appropriate error messages
can be sent to special error handlers such as CONTROL-O/Server and
ENTERPRISE/CS (see below). The Watchdog facility automatically sends
these messages to the CONTROL-M IOALOG and PROCLOG.
The Watchdog facility is enabled by configuration parameters defined in
the ~controlm/ctm/data/config.dat file. For additional information, see
Configuration Parameters on page 5-22.
Certain parameters in the config.dat file indicate general information
about the Watchdog facility. These parameters are listed in Table 1-9.
Table 1-9
Parameter
Description
WD_CTMEXIT_NUMBER
WD_USEREXIT_NUMBER
1-44
Heartbeat Check
Parameter
Description
WD_HEARTBEAT_INTERVAL
WD_HEARTBEAT_TIMEOUT
Exit 1
Runs a Disk Space utility to check the amount of free disk space on a
specified device and sends an error message if it is below a specified
amount. See ctmdiskspace in Chapter 2, Utilities, for a complete
description
Overview
1-45
Exit 2
Runs a Database Usage utility to check data and log usage in the
CONTROL-M database and sends an error message if it is above a
specified percentage. See ctmdbspace in Chapter 2, Utilities, for a
complete description.
The parameters for these two built-in Watchdog system user exits are
described in Table 1-11.
Note
Valid values for <n> in the parameters in Table 1-11 are either 1 or 2.
Table 1-11
Parameter
Description
WD_CTMEXIT_<n>_CMD_LINE
Contains parameters to be
passed to the exit script.
WD_CTMEXIT_<n>_ERROR_MSG
WD_CTMEXIT_<n>_INTERVAL
WD_CTMEXIT_<n>_RUN_STATE
WD_CTMEXIT_<n>_SCRIPT_FILE
WD_CTMEXIT_<n>_SUSPEND_STATE
WD_CTMEXIT_<n>_TIMEOUT
1-46
Parameter
Description
WD_USEREXIT_<n>_CMD_LINE
Contains parameters to be
passed to the exit script.
WD_USEREXIT_<n>_ERROR_MSG
WD_USEREXIT_<n>_INTERVAL
WD_USEREXIT_<n>_RUN_STATE
WD_USEREXIT_<n>_SCRIPT_FILE
WD_USEREXIT_<n>_SUSPEND_STATE
WD_USEREXIT_<n>_TIMEOUT
Overview
1-47
Example
Error Handlers
If a Watchdog facility check fails, the error message specified for that
check is sent to the defined error handler. Two other error-handling
options are available: CONTROL-O/Server and a user defined script.
These options are enabled via the parameters in the config.dat file
described in Table 1-13.
Note
Parameter
Description
WD_ALIVE_MSG
WD_CTO_HOSTNAME
1-48
Table 1-13
Parameter
Description
WD_CTO_TIMEOUT
WD_ERROR_HANDLER_SCRIPT_FILE
WD_ERROR_HANDLER_TIMEOUT
WD_INTERVAL
Example
Overview
1-49
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 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 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 users actions. Exits can also be used
to trigger other actions prior or subsequent to execution of a
CONTROL-M job.
For more information, see Chapter 6, User Exits.
Processing Overhead
CONTROL-M provides a wide variety of mechanisms that can be used
to control job scheduling. When determining which mechanisms to use,
it helps to be aware of the different levels of processing overhead that
each mechanism requires.
Table 1-14 lists certain basic scheduling features and their relative levels
of processing overhead. By choosing the right features for your job
processing definitions, you can ensure that your CONTROL-M processes
are fast and efficient.
Table 1-14
Feature
Relative Processing
Overhead
Very low
In (prerequisite) conditions
Low
Control Resources
Medium
1-50
Table 1-14
Feature
Relative Processing
Overhead
Quantitative Resources
High
Very High
Overview
1-51
1-52
Utilities
2
General maintenance can be performed using the utilities described in
this chapter. Some of these utilities generate reports, which are useful for
managing the data center, and for planning job processing definitions and
calendars.
Note
Many of these utilities are intended for use only by the CONTROL-M
administrator. Because they require extensive authorization in the
CONTROL-M database, they may not work if submitted by a regular
user.
All utilities described in this chapter are included with CONTROL-M.
These utilities are run either from the system prompt or submitted as
batch jobs (except where noted).
Utilities that can be submitted as batch jobs can also be defined as
CONTROL-M jobs. This enables you to utilize the CONTROL-M job
handling features such as automatic scheduling and the use of AutoEdit
variables (see examples in this chapter). Refer to Accessing Utilities
From Other Unix Users in this chapter before using this feature.
Note
Utilities
2-1
Table 2-1 lists the available utilities. Detailed information about each
utility is provided later in this chapter.
Table 2-1
Utility
Description
ctm_agstat
ctm_backup_bcp
ctm_restore_bcp
ctmcontb
ctmcreate
ctmdbapasswd
ctmdbbck
ctmdbcheck
ctmdbrst
ctmdbspace
ctmdbtrans
ctmdefine
ctmdiskspace
ctmexdef
ctmfw
ctmgrpdef
ctmjsa
ctmkilljob
ctmldnrs
2-2
Table 2-1
Utility
Description
ctmloadset
ctmlog
ctmordck
ctmorder
ctmpasswd
ctmping
ctmpsm
ctmrpln
ctmruninf
ctmsec
ctmshout
ctmshtb
ctmstats
ctmstvar
ctmsuspend
Utilities
2-3
Table 2-1
Utility
Description
ctmsys
ctmudchk
ctmudlst
ctmudly
ctmvar
ctmwhy
ctm2snmp
ecactltb
ecaqrtab
Utility
Requires
CTM
Active
ctm_agstat
Requires
SQL
Active
Executable
By User
Other Than
CTM Admin
Executable
As Batch
Job
ctm_backup_bcp
ctm_restore_bcp
ctm_restore_aut
Supports
AutoEdit
Variables
Executable
From Agent
Platform
(Batch Jobs)
ctmcontb
ctmcreate
ctmdbapasswd
2-4
Table 2-2
Utility
Requires
CTM
Active
Requires
SQL
Active
Executable
By User
Other Than
CTM Admin
Executable
As Batch
Job
ctmdbbck
ctmdbrst
ctmdbcheck
ctmdbspace
ctmdbtrans
ctmdefine
ctmdiskspace
ctmexdef
ctmfw
ctmgrpdef
ctmjsa
ctmkilljob
ctmlog
ctmordck
ctmldnrs
ctmloadset
ctmorder
ctmping
X
X
ctmrpln
ctmruninf
X
X
ctmstvar
ctmsys
ctmstats
ctmshtb
ctmsuspend
Executable
From Agent
Platform
(Batch Jobs)
ctmpsm
ctmshout
Supports
AutoEdit
Variables
Utilities
2-5
Table 2-2
Utility
Requires
SQL
Active
Executable
By User
Other Than
CTM Admin
Executable
As Batch
Job
ctmudchk
ctmudlst
ctmudly
ctmvar
ctmwhy
Supports
AutoEdit
Variables
Executable
From Agent
Platform
(Batch Jobs)
ctm2snmp
ecactltb
ecaqrtab
Report
Description
2-6
Table 2-3
Report
Description
CONTROL-M Log
Lists entries in the CONTROL-M log for specified (or all) CONTROL-M/Server processes.
See ctmlog on page 2-91.
User Daily:
Associated Job
Processing Definitions
Prerequisite Conditions
Control Resources
Status
Quantitative Resources
Status
Summary Statistical
Data
Global AutoEdit
Variables
Utilities
2-7
2-8
For SYBASE
For ORACLE
SYBASE
ORACLE_BASE
DSLISTEN
ORACLE_HOME
DSQUERY
ORACLE_SID
DSCONSOLE
NLS_LANG
MIRROR_DSLISTEN
MIRROR_DSQUERY
Use the following formats to define the shared library path variables in
the users environment, depending upon the Server platform type:
Utilities
2-9
Table 2-5
Platform
Path Variable
AIX
LIBPATH <ctm_owner>/sybase/lib:<ctm_owner>/ctm/exe_AIX
HP-UX 10
SHLIB_PATH
<ctm_owner>/sybase/lib:<ctm_owner>/ctm/exe_HP-UX-10
Solaris
LD_LIBRARY_PATH
<ctm_owner>/sybase/lib:<ctm_owner>/ctm/exe_Solaris
Compaq
TRU64 Unix
LD_LIBRARY_PATH
<ctm_owner>/sybase/lib:<ctm_owner>/ctm/exe_OSF1
Table 2-6
Platform
Path Variable
AIX
LIBPATH
<ctm_owner>./oracle/product/8.1.5/lib:<ctm_owner>/ctm/exe_A
IX
HP-UX 10
LIBPATH
<ctm_owner>./oracle/product/8.1.5/lib:<ctm_owner>/ctm/exe_H
P-UX-10
Solaris
LD_LIBRARY_PATH
<ctm_owner>./oracle/product/8.1.5/lib:<ctm_owner>/ctm/exe_S
olaris
Compaq
TRU64 Unix
LD_LIBRARY_PATH
<ctm_owner>./oracle/product/8.1.5/lib:<ctm_owner>/ctm/exe_O
SF1
In both Table 2-5 and Table 2-6 above, <ctm_owner> refers to the Unix
user account under which CONTROL-M/Server is installed.
Setting environmental variables
Using csh or tcsh
When using csh or tcsh, specify the following command for each
variable:
setenv <variable-name> <value>
2-10
Sybase Example
setenv CONTROLM /home/controlm/ctm
setenv SYBASE /home/controlm/sybase
setenv DSLISTEN CTRLM
setenv DSQUERY CTRLM
setenv DSCONSOLE CTRLM
setenv MIRROR_DSQUERY MIRROR
setenv MIRROR_DSLISTEN MIRROR
setenv CONTROLM_USER ctrlm
setenv CONTROLM_DATABASE ctrlm
setenv LD_LIBRARY_PATH /home/controlm/ctm/exe_Solaris:
/home/controlm/sybase/bin
Oracle Example
setenv CONTROLM /home/ora_ctm/ctm
setenv ORACLE_HOME /home/ora_ctm/oracle/product/8.1.5
setenv ORACLE_SID ctrlm
setenv ORACLE_BASE /home1/ora_ctm/oracle
setenv NLS_LANG AMERICAN_AMERICA.WE8ISO8859P1
setenv CONTROLM_USER ctrlm
setenv CONTROLM_DATABASE ctrlm
setenv LD_LIBRARY_PATH /home/controlm/ctm/exe_OSF1:
/home/controlm/oracle/product/8.1.5/lib
When using other shells (for example, sh, ksh), specify the following
command for each variable:
<variable-name>=<value>; export <variable-name>
Utilities
2-11
Sybase Example
CONTROLM=/home/controlm/ctm; export CONTROLM
SYBASE=/home/controlm/sybase; export SYBASE
DSLISTEN=CTRLM; export DSLISTEN
DSQUERY=CTRLM; export DSQUERY
DSCONSOLE=ctrlm; export DSCONSOLE
MIRROR_DSQUERY=MIRROR; export MIRROR_DSQUERY
MIRROR_DSLISTEN=MIRROR; export MIRROR_DSLISTEN
CONTROLM_USER=ctrlm; export CONTROLM_USER
CONTROLM_DATABASE=ctrlm; export CONTROLM_DATABASE
LIBPATH=/home/controlm/ctm/exe_HP-UX-10; export
LIBPATH
Oracle Example
CONTROLM=/home/controlm/ctm; export CONTROLM
CONTROLM_USER=ctrlm; export CONTROLM_USER
CONTROLM_DATABASE=ctrlm; export CONTROLM_DATABASE
LIBPATH=/home/controlm/ctm/exe_HP-UX-10; export
LIBPATH
Specify the following command for each variable from user controlm:
echo $<variable-name>
Example
echo $SYBASE
2-12
Use the following command to modify the path when using csh or tcsh:
set path=($path ~<controlm_owner>/ctm/exe_<OS_ID>)
Description
<controlm_owner>
<OS_ID>
Example
set path=($path ~controlm/ctm/exe_Solaris)
Using Other Shells
Use the following command to modify the path when using other shells
(for example, sh, ksh):
PATH="$PATH: <controlm_path>/ctm/exe_<OS_ID>"
Description
<controlm_path>
<OS_ID>
Example
PATH="$PATH: controlm/ctm/exe_HP-UX-10"
Utilities
2-13
Read/Write Permissions
Permission Type
Directory
<controlm-directory>/.controlm
prflag/
2-14
Utilities
ctm_agstat
This utility enables you to list or update an Agents status, or to delete an
inactive Agent. (See Communication Status of Agent Platforms on
page 1-7.)
To invoke the ctm_agstat utility, specify the following command:
ctm_agstat ACTION( {LIST|LIST_INACT|UPDATE|DELETE} )
[AGTNAME(<agent name>)]
[STATUS( {*SAME | AVAILABLE | DISABLED} )]
[QUIET( {*YES | *NO} )] [DEBUG(<debug level>)]
Parameter
Description
ACTION
<agent
name>
STATUS
QUIET
<debug
level>
Utilities
2-15
Examples
2-16
ctm_backup_bcp
The ctm_backup_bcp utility exports data from the CONTROL-M
database to directory <controlm>/ctm/backup_db. Each database table
is backed up as a separate ASCII file.
To invoke the ctm_backup_bcp utility:
Example 1
ctm_backup_bcp
BMC Software, Inc., Confidential and Proprietary Information
Utilities
2-17
In this case, CONTROL-M does not display the confirmation prompt and
does not issue messages. Only dots are displayed.
2-18
ctm_restore_bcp
The ctm_restore_bcp utility imports the CONTROL-M database from the
bcp_backup directory. The content of this directory was created by the
ctm_backup_bcp utility.
To invoke the ctm_restore_bcp utility:
Example 1
ctm_restore_bcp
Restoring contents of database.
This procedure DELETES any information in main
database
Please confirm [y/n]: y
BMC Software, Inc., Confidential and Proprietary Information
Utilities
2-19
In this case, CONTROL-M does not display the confirmation prompt and
the restoring contents messages. Only dots are displayed.
2-20
ctmcontb
The ctmcontb utility performs operations on the Prerequisite Conditions
table. These operations include:
Variable
Description
<Condition Name>
<Condition Date>
<Output>
Utilities
2-21
Variable
Description
<Condition Name>
<Condition Date>
Variable
Description
<Condition Name>
<Condition Date>
2-22
Variable
Description
<Condition Name>
<From Date>
<To Date>
Example 1
Utilities
2-23
Example 3
2-24
ctmcreate
ctmcreate is an API (Application Program Interface) utility that allows an
ad hoc job to be inserted directly into the Active Jobs file. The job does
not have to be defined in the CONTROL-M database. The function
performed by this utility is equivalent to the Force function in
ENTERPRISE/CS.
The ctmcreate utility can also be used to define jobs for specific
applications such as SAP and Oracle Applications. For more information,
see Creating Application-specific Jobs on page 2-31.
To invoke the ctmcreate utility, specify the following command:
ctmcreate-tasktype {JOB|DETACHED|COMMAND|DUMMY|GROUP} \
[-group <group name>] \
[-application <application name>] \
[ -group_ord <grp_orderno|ALONE|LAST>\
[ -adjust_cond {Y|N}\
[ -nodegrp <node ID/group> ] \
[ -memlib <directory name> ] \
[ -memname <file name> ] \
[ -cmdline <command line text> ] \
[ -jobname <name of job> ] \
[ -schedtab <name of scheduling table> ] \
[ -owner <user name of job owner> ] \
[ -author <user name of the job creator>] \
[ -odate <scheduling date>|ODAT ]\
[ -maxrerun <maximum reruns> ]\
[ -timefrom <earliest submission time> ]\
[ -timeuntil <latest submission time> ]\
[ -priority <job priority> ]\
[ -critical {Y|N} ]\
[ -cyclic {Y|N} ]\
[ -intervalfrom {START|END}]\
[ -confirm {Y|N} ]\
[ -taskclass {DISTRIBUTION|DECOLLATION}|SAP|OAP ]\
[ -interval <minutes> ]\
[ -overlib <alternate directory> ]\
[ -maxwait <days> ]\
[ -description <job description> ]\
[ -docmem <file name> ]\
[ -doclib <directory name> ]\
[ -incond (<condition1> <date1> {AND|OR}
-incond <condition2>) <date2> {AND|OR}
-incond <condition3>) <date3> {AND|OR}]\
[ -outcond <cond> <date> {ADD|DEL} ]\
[ -autoedit <variable name> <expression> ]\
[ -quantitative <quantitative resource> <quantity> ]\
[ -sysout {RELEASE|DELETE|COPY|MOVE} [<parameter>] ]\
[ -control <control resource> {E|S} ]\
[ -shout {OK|NOTOK|RERUN|LATESUB|LATETIME| EXECTIME} <destination> R|U|V}
<message> [<time>] ]\
[ -on <statement> <code>\
[ -dook ]\
[ -donotok ]\
BMC Software, Inc., Confidential and Proprietary Information
Utilities
2-25
[ -dorerun ]\
[ -doshout <destination> {R|U|V} <message> ]\
[ -dostopcylic]\
[ -domail <destination> <cc> <urgency> {R|U|V} <subject> <message>\
[ -docond <condition> <date> {ADD|DEL} ]\
[ -doautoedit <variable name> <expression> ]\
[ -doforcejob <table name> <job name> <odate> ]\
[ -dosysout {RELEASE|DELETE|COPY|MOVE}[<parameter>]]\
[ -debug <level> ] \
[ -quiet ]
Each of the parameters of this utility, except for group_ord, debug and
quiet, is described in detail in Chapter 5 of the Enterprise Controlstation
User Guide.
Parameter
Description
-group_ord
ALONE
LAST
-quiet
Table 2-13 lists each parameter available for the utility and the name by
which the parameter appears in the User Guide.
2-26
Table 2-13
Utility Parameter
ENTERPRISE/CS
Parameter
Utility Parameter
ENTERPRISE/CS
Parameter
adjust_cond
Adjust condition
interval
Interval
application
Application
intervalfrom
autoedit
AutoEdit
Assignments
jobname
Job Name
cmdline
Command Line
maxrerun
Max Rerun
confirm
Confirm Submission
maxwait
Max Wait
control
Control Resources
memlib
Mem Lib
critical
Critical
memname
Mem Name
cyclic
Cyclic
nodegrp
Node ID/Group
description
Description
odate
doautoedit
Do AutoEdit
on
On Statement/Code
doclib
Doc Lib
outcond
Out Conditions
docmem
Doc Mem
overlib
Over Lib
docond
Do Cond
owner
Owner
doforcejob
Do Forcejob
priority
Priority
domail
Do Mail
quantitative
Quantitative Resources
donotok
Do NOTOK
schedtab
Scheduling Table
dook
Do OK
shout
Shout
dorerun
Do Rerun
sysout
Sysout Handling
doshout
Do Shout
taskclass
Task Class
dostopcyclic
Do Stop Cyclic
tasktype
Task Type
dosysout
Do Sysout
timefrom
Time
group
Group
timeuntil
Time
incond
In Conditions
Utilities
2-27
The length of the command line, after decoding, must not exceed 999
characters.
All fields of each parameter (as specified in the syntax on page 2-25)
must contain values. If no value is desired for a parameter field, a
null string "" must be specified in the relevant position in the
parameter specification.
For example
The -domail parameter has the following syntax:
-domail <destination> <cc> <severity> <subject> <message>
2-28
The order of the parameters does not affect the outcome of the job,
with the exception of -on and -do... parameters.
Utilities
2-29
Example 1
-incond pk_oly_ok \"\"
2-30
-group SUPPLY
-application SUPPLIES \
-memlib /users/ctm/ -memname PROLYPAR -nodegrp UNIXGRP \
-jobname PROLYPAR \
-owner suppman \
-odate 19981130 \
-timeuntil 1800 \
-priority AA -critical N \
-confirm Y \
-doclib /users/supply/doc/
-docmem prolypardoc \
-incond pk_oly_ok ODAT AND \
-incond pk_olp_ok ODAT AND \
-outcond pk_oly_ok ODAT DEL \
-outcond pk_olp_ok ODAT DEL \
-outcond pk_olypar ODAT ADD \
-autoedit %%PARM1 "%%CALCDATE %%ODATE -2" \
-quantitative tape 2 -quantitative cpu 50 \
-sysout MOVE /test/logs/ \
-control disk2 E \
-shout OK oper2 U "Daily summary completed" \
-on "COPY JWINFO_2507" "%COPY-E-OPENIN, error" \
-dosysout MOVE /oper/openerr
The ctmcreate utility can be used to define jobs for specific applications
such as SAP and Oracle Applications. These jobs are defined by setting
the TASKCLASS parameter to SAP or OAP.
Utilities
2-31
2-32
Table 2-14
SAP Parameters
Type
Minimum
Maximum
account
80
archive_info
archive_object
10
archive_sapobject
10
asap
host
80
job_mode
10
job_in_file
80
jobcount
language
print_archmode
print_authorization
68
print_banner
print_banner_page
print_copies
255
print_destination
print_expiration
print_immediately
print_numcolumns
255
print_numlines
130
print_recipient
32
print_release
program
80
Utilities
2-33
Table 2-14
SAP Parameters
Type
Minimum
Maximum
polling_interval
80
spool
80
step_num
999
r3_owner
80
variant
80
waitonly
Table 2-15
OAP Parameters
Type
Minimum
Maximum
ioa_appl
30
-display_output
-notification_<n>
where n is 1 - 30
30
username
30
-ver
respname
30
respapp
50
tasktype
20
progname
30
appname
50
printername
100
printstyle
20
printcopies
profile_<n>
80
80
where n is 1 - 30
description
2-34
Table 2-15
OAP Parameters
Type
Minimum
Maximum
waitchild
security_groupname
80
parm<n>
80
80
where n is 1-100
stageparm<n>
where n is 1-100
Utilities
2-35
ctmdbapasswd
The ctmdbapasswd utility enables the administrator to change the
database password of a dedicated CONTROL-M/Server. Only an
administrator can change a database password.
Specify the following command to invoke the ctmdbapasswd utility:
ctmdbapasswd
1. Enter the old password for the System Administrator account. The
system will prompt you to enter the new password:
Please enter the new password for System
Administrator account:
2. Enter the new password for the System Administrator account. Make
sure that the password has at least 6 characters. You will not see your
entry on the screen. The system will then prompt you to reenter the
password:
Enter again to verify:
2-36
ctmdbbck
The ctmdbbck utility backs up the CONTROL-M database.
Note
-or
the full path name of a file to be created by the backup procedure for
Sybase or Oracle
Device
AIX
/dev/rmt0
HP-UX
/dev/rmt/0m
Solaris
/dev/rmt/0mn
/dev/nrmt0h
Utilities
2-37
Example
ctmdbbck tapedump2
2-38
ctmdbcheck
The ctmdbcheck utility displays information about the memory capacity
and the status of the CONTROL-M database. To invoke the ctmdbcheck
utility, specify the following command:
ctmdbcheck
The ctmdbcheck utility can also be used with the following syntax to
monitor the database and the transaction log:
ctmdbcheck [-d <db_threshold_%>] [-l <log_threshold_%>][-n]
ctmdbcheck [general_threshold_%]
Utilities
2-39
Table 2-16
ctmdbcheck Parameters
Parameter
Description
db_threshold
_%
log_threshold
_%
general_
threshold_%
ctmdbcheck Output
Field
Description
db total
data
log
Data used
Log used
2-40
Table 2-18
Field
Description
Tablespace
Size
Percent Free
Database is OK.
WARNING: Database is more than half full.
ATTENTION: Database log segment is more than 90% full.
ATTENTION: Database is more than 80% full.
Example 1
This example uses the ctmdbcheck utility to check the status of a Sybase
database without specifying any parameters (that is, no shout messages
will be issued for this run on the utility, even if database is over the
desired threshold).
Utility Input
ctmdbcheck
Utility Output
db total = 25000.0 KB (data= 19500.00 , log= 5500.00)
data used = 3696 KB (18%).
log used = 0 KB (0%).
Checking database...
Database is OK.
Example 2
This example uses the ctmdbcheck utility to check the status of an Oracle
database without specifying any additional parameters.
Utility Input
ctmdbcheck
BMC Software, Inc., Confidential and Proprietary Information
Utilities
2-41
Utility Output
Tablespace
-------------------MADONA6A
MADONA6A_INDX
RBS
Size
----120M
40M
90M
% Free
------77%
99%
68%
Checking database...
Database is OK.
Example 3
Utility Input
ctmdbcheck -d80
Utility Output
Message Warning: DB is more than 80% full, urgency U NodeID
Shout to user 'ECS' 'SUCCESS'
db total = 25000.0 KB (data= 19500.00 , log= 5500.00)
data used = 21250 KB (85%).
log used = 0 KB (0%).
Checking database...
Database is OK.
linda
Utility Input
ctmdbcheck -l80
Utility Output
db total = 25000.0 KB (data= 19500.00 , log= 5500.00)
data used = 21250 KB (85%).
log used = 0 KB (0%).
Checking database...
Database is OK.
2-42
This command is similar to the example above except that here the Log
partition is being checked. No warning message is generated because 0%
is less than the specified threshold of 80%.
Example 4
Utility Input
ctmdbcheck 50
Utilities
2-43
ctmdbrst
ctmdbrst restores the CONTROL-M database.
To invoke the ctmdbrst utility, specify the following command:
ctmdbrst [<Backup Device>]
where <Backup Device> is the device from which the database should
be restored. The device specified for this parameter must be either a valid
device defined in Sybase, or the full path name of a file to be used as
input for the ctmdbrst utility. A list of devices can be obtained using the
option List Backup Devices from the Database Maintenance menu.
Note
CONTROL-M must be shut down before invoking this utility. Make sure
that no other users or processes are connected to the SQL Server.
The default backup device is tapedump2, which points to one of the
following devices:
Operating System
Device
AIX
/dev/rmt0
HP-UX
/dev/rmt/0m
Solaris
/dev/rmt/0mn
/dev/nrmt0h
Example
2-44
ctmdbspace
ctmdbspace checks the data and log usage in the CONTROL-M database
and displays the usage. The utility returns a failed status if the usage
exceeds the specified limit.
Note
Utilities
2-45
ctmdbtrans
The ctmdbtrans utility lists the active transactions in the database. A
transaction is defined as the unit of work performed by CONTROL-M in
the database. Each transaction is assigned a unique name identifying that
specific unit of work.
You may be asked by technical support to run this utility and to provide
them with the output for debugging purposes.
To see which transactions are active in the database, specify the
following command:
ctmdbtrans
2-46
ctmdefine
ctmdefine is an API (Application Program Interface) utility that adds a
job processing definition to a Scheduling table, or creates a new Group
Scheduling table in the CONTROL-M database. This utility can be used
when converting job scheduling information from other job control
products to CONTROL-M. The function performed by this utility is
equivalent to the manual process of creating job processing definitions,
described in Chapter 7, Job Processing Definitions, in the Enterprise
Controlstation User Guide.
The ctmcreate utility can also be used to define jobs for specific
applications such as SAP and Oracle Applications. For more information,
see Defining Application-specific Jobs on page 2-57.
Note
Group Scheduling tables can also be defined using the ctmgrpdef utility
(described on page 2-75).
When creating new Scheduling tables or job processing definitions, the
following considerations are applicable:
If the job name specified when using this utility already exists in a
job processing definition in the Scheduling table, the new job
processing definition does not overwrite the existing one. Both job
processing definitions will appear in the table, each with a different
internal job number.
If the Scheduling table specified when using this utility does not
exist, the utility creates it.
Utilities
2-47
2-48
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[ -dorerun ] \
[ -doshout <destination {R|U|V} <message> ] \
[ -docond <condition> <date> {ADD|DEL} ] \
[ -doautoedit <variable name> <expression> ] \
[ -doforcejob <table name> <job name> <odate> ] \
[ -dosysout {RELEASE|DELETE|COPY|MOVE}[<parameter>]]] \
[ -domail <destination> <cc> {R|U|V} <subject> <message>]\
[ -dostopcyclic ] \
-days <days string> ] \
-weekdays <weekdays string> ] \
-month {ALL|JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC} {Y|N}] \
-date <mmdd> ] \
-dayscal <calendar name> ] \
-weekcal <calendar name> ] \
-confcal <calendar name> ] \
-shift {<|>} ] \
-cal_andor {AND|OR} ] \
-retro {Y|N} ] \
-debug <level> ] \
-quiet ] \
-TAG <tagname>
]\
-RELATIONSHIP
AND|OR
]
Each parameter included in the above syntax, except debug and quiet, is
described in detail in Chapter 5, Job Processing Parameters, in the
Enterprise Controlstation User Guide.
Parameter
Description
debug
quiet
Table 2-19 lists each parameter of the ctmdefine utility, and the name
under which the parameter appears in the Enterprise Controlstation User
Guide.
Utilities
2-49
Table 2-19
Utility Parameter
ENTERPRISE/CS
Parameter
Utility Parameter
ENTERPRISE/CS
Parameter
adjust_cond
Adjust Condition
interval
Interval
application
Application
intervalfrom
autoedit
AutoEdit Assignments
jobname
Job Name
cal_andor
AND/OR
maxrerun
Max Rerun
cmdline
Command Line
maxwait
Max Wait
confcal
Conf Calendar
memlib
Mem Lib
confirm
Confirm Submission
memname
Mem Name
control
Control Resources
month
See below
critical
Critical
nodegrp
Node ID/Group
cyclic
Cyclic
on
On Statement/Code
date
Dates
outcond
Out Conditions
days
Days
overlib
Over Lib
dayscal
Days Calendar
owner
Owner
description
Description
priority
Priority
doautoedit
Do AutoEdit
quantitative
Quantitative Resources
doclib
Doc Lib
relationship
Relationship
docmem
Doc Mem
retro
Retro
docond
Do Cond
shift
Shift
doforcejob
Do Forcejob
shout
Shout
donotok
Do NOTOK
sysout
Sysout Handling
domail
Do Mail
table
Scheduling Table
dostopcyclic
Do Stopcyclic
tag
Schedule Tag
dook
Do OK
taskclass
Task Class
dorerun
Do Rerun
tasktype
Task Type
doshout
Do Shout
timefrom
Time
dosysout
Do Sysout
timeuntil
Time
group
Group
weekcal
Weekdays Calendar
incond
In Conditions
weekdays
Weekdays
BMC Software, Inc., Confidential and Proprietary Information
2-50
Note
For the -month parameter, specify the first three letters of a month (for
example, JAN) or ALL for all months (the default is none). To specify
two or more individual months, use a separate -month parameter for
each month. See Months parameter.
The following syntax rules apply for this utility:
The length of the command line, after decoding, must not exceed 999
characters.
Utilities
2-51
2-52
The default for the -month parameter is ALL Y. This means that if
you wish to define a job that should run only in one specific month,
you must first indicate that it should not run on any month. For
example:
-month ALL N -month NOV Y
The order of parameters does not affect the outcome of the job, with
the exception of -on and -do... parameters.
All fields of each parameter (as specified in the syntax on page 2-48)
must contain values. If no value is desired for a parameter field, a
null string "" must be specified in the relevant position in the
parameter specification.
For example
The -domail parameter has the following syntax:
-domail <destination> <cc> <severity> <subject> <message>
Utilities
2-53
2-54
Example 1
Utilities
2-55
Example 2
2-56
The ctmdefine utility can be used to define jobs for specific applications
such as SAP and Oracle Applications. These jobs are defined by setting
the TASKCLASS parameter to SAP or OAP.
Utilities
2-57
Table , , on page 2-58 lists the SAP parameters. The parameters for
SAP applications are described in detail in the
CONTROL-M Option for R/3 Administrator Guide version 3.0.04.
Table 2-21, Oracle Applications Parameters, on page 2-59 lists the
Oracle Applications parameters. The parameters for Oracle Applications
are described in detail in the CONTROL-M Option for Oracle
Applications Administrator Guide version 2.0.01 or later.
When the ctmcreate command line is processed, the application-specific
parameters are used to create special AutoEdit variables with the
specified values. These AutoEdit variables are used to pass information
to the CONTROL-M Option for the specified application. The
parameters are added as AutoEdit variables in the command line. For
more information, see the ERP Job Parameters appendix in the
CONTROL-M/Desktop User Guide.
In the tables below:
Table 2-20
SAP Parameters
SAP Parameters
Type
Minimum
Maximum
account
80
archive_info
archive_object
10
archive_sapobject
10
asap
host
80
job_mode
10
job_in_file
80
2-58
Table 2-20
SAP Parameters
SAP Parameters
Type
Minimum
Maximum
jobcount
language
print_archmode
print_authorization
68
print_banner
print_banner_page
print_copies
255
print_destination
print_expiration
print_immediately
print_numcolumns
255
print_numlines
130
print_recipient
32
print_release
program
80
polling_interval
80
r3_owner
80
spool
80
step_num
999
variant
80
waitonly
Table 2-21
OAP Parameters
Type
Minimum
Maximum
ioa_appl
30
-display_output
Utilities
2-59
Table 2-21
OAP Parameters
Type
Minimum
Maximum
-notification_<n>
where n is 1 - 30
30
username
30
respname
30
respapp
50
tasktype
20
progname
30
appname
50
printername
100
printstyle
20
printcopies
profile_<n>
80
description
80
waitchild
security_groupname
80
parm<n>
80
80
where n is 1-30
where n is 1-100
stageparm<n>
where n is 1-100
2-60
Utilities
2-61
ctmdiskspace
ctmdiskspace checks the amount of free disk space on a device and
displays the result. The utility returns a failed status if the current free
space is below the specified limit.
ctmdiskspace can be included in the CONTROL-M Watchdog process.
For more information, see Watchdog Facility on page 1-44.
Use the following command to invoke the ctmdiskspace utility:
ctmdiskspace -limit <amount> -path <path_name> [-quiet]
ctmdiskspace Parameters
Parameter
Description
amount
path_name
-quiet
Note
More than one -path <path_name> statement can be specified for each
run of the ctmdiskspace utility.
Example 1
2-62
Example 2
Utilities
2-63
ctmexdef
The ctmexdef utility exports job processing definitions from the
CONTROL-M database to a flat (ASCII) file. This file can then be used
as input for either the ctmcreate utility or the ctmdefine utility.
The ctmexdef utility can be used to:
ctmexdef Parameters
Parameter
Description
<table_name>
<jobname>
<memname>
CREATE
2-64
Table 2-23
ctmexdef Parameters
Parameter
Description
DEFINE
<output_file_
name>
Example
Utilities
2-65
ctmfw
The CONTROL-M File Watcher utility (ctmfw) detects the following file
processes:
The ctmfw utility cannot be used to monitor files larger than 4GB.
The ctmfw utility runs as a process on a client machine. The process
waits for the creation or deletion of specified file(s).
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 File Watcher 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 deletion, ctmfw must first detect the existence of the file
before it can detect its deletion.
The ctmfw utility can also be run from the command line.
The ctmfw utility can be invoked to detect either a single file or multiple
files.
2-66
Utilities
2-67
Table 2-24
ctmfw Parameters
Param
Description
filename
Path of the file to be detected. The file name can include mask
character * to represent any number of characters (including no
characters). In this case, enclose the full path name in quotation
marks (for example, c:\ctm\a*.txt). When including an * as part
of a file name in a Rules file, (see page 2-70), the name should
not be enclosed in quotation marks. When a wildcard is used, the
ctmfw utility does not monitor the size of the file.
mode
CREATE
DELETE
min_size
sleep_int
mon_int
min_detect
wait_time
2-68
Return Codes
The return codes listed in Table 2-25 are issued by the ctmfw utility after
detecting if a file is created or deleted in the specified time frame.
Table 2-25
Return Code
Description
Utilities
2-69
Table 2-26
Parameter
Description
INTERVAL
FROM_TIME
2-70
Figure 2-1
ON_FILEWATCH Statements
#******************************************************************
# Mandatory Parameters
INTERVAL <60>
# Sleep interval (seconds)
FROM_TIME <0000>
# Starting time for all files (hhmm)
MIN_SIZE <0>
# Minimum size for all files (bytes)
MIN_DETECT <3>
# Number of iterations for all files
WAIT_TIME <0>
# Time limit for all files (minutes)
# ON_FILEWATCH statements
ON_FILEWATCH <filename> [mode] [min_size] [min_detect] [wait_time]
[from_time] [cyclic_interval]
THEN
<action>
ELSE
<action>
END_ON
#******************************************************************
# indicates comments.
Default values are shown for all mandatory parameters.
from_time is the time from which to watch for the specified file
action.
cyclic_interval is the interval between multiple operations of
detecting the file (in minutes). This interval must be greater than the
value for wait_time. If the cyclic_interval is 0, only one attempt to
detect the file will be performed. Default: 0.
<action> refers to any of the actions described in Table 2-27.
Note
Table 2-27
Action
Description
DO_CMD <command>
DO_OK
Utilities
2-71
If the file is detected and the size remains static within the time
frame (CREATE) or the file has been deleted (DELETE), the DO
commands in the THEN block are executed.
ctmfw terminates when either all the files in the Rules file have been
processed or a DO_OK/DO_NOTOK action is executed.
Note
2-72
Example 1
#******************************************************************
INTERVAL 10
ON_FILEWATCH /controlm/datafile.txt CREATE
THEN
DO_COND datafile 0101 +
DO_CMD move /ctm/datafile.txt /ctm/workfile.txt
ELSE
DO_COND datafile 0101 END_ON
ON_FILEWATCH /ctm/tempfile.txt DELETE
THEN
DO_COND tempfile 0101 END_ON
#*******************************************************************
Utilities
2-73
Example 2
Value
Job Name
FileWatch
Mem Name
FileWatch
Owner
<control_m_user>
From Time
1900
Command line
On Statement/Code processing:
Stmt
Code
COMPSTAT=0
Do Cond
Stmt
Code
COMPSTAT=1
Do Shout
2-74
ctmgrpdef
The ctmgrpdef utility creates a definition for a new Group Scheduling
table.
Group Scheduling tables are used for jobs whose processing should be
treated as a single unit. The definition created via this utility contains
values for parameters that affect handling of the entire group.
For more information about parameters of a group definition, see the
description of the Group Editing form in the CONTROL-M/Desktop User
Guide.
Use the following command to invoke ctmgrpdef:
ctmgrpdef
-GROUP
<group_name>
-APPLICATION
<appl_name>
-TAG <tagname>
[ -MAXWAIT
<maxwait>
]
[ -DAYS
<daystr>
]
[ -WEEKDAYS
<weekdaystr>
]
[ -MONTH
ALL|JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC Y|N ]
[ -DATE
<MMDD>
]
[ -DAYSCAL
<days calendar> ]
[ -WEEKCAL
<week calendar> ]
[ -CONFCAL
<conf calendar> ]
[ -CAL_ANDOR
AND|OR
]
[ -SHIFT
>|<
]
[ -ADJUST_COND Y|N ]
[ -OWNER
<username> ]
[ -AUTHOR
<username> ]
[ -DEBUG
<level> ]
[ -QUIET ]
[ -TIMEFROM
<earliest submission time> ]
[ -TIMEUNTIL
<latest submission time> ]
[ -PRIORITY
<job priority> ]
[ -CONFIRM
Y|N ]
[ -DESCRIPTION <string> ]
[ -DOCMEM
<filename> ]
[ -DOCLIB
<directory name> ]
[ -INCOND
<condition> <dateref>|ODAT AND|OR ]
[ -OUTCOND
<condition> <dateref>|ODAT ADD|DEL ]
[ -AUTOEDIT
<varname> <expression> ]
[ -SHOUT
OK|NOTOK|LATESUB|LATETIME|EXECTIME
<destination> <urgency R|U|V> <message> [<time>] ]
[ -ONGROUPEND {OK|NOTOK}
[ -DOOK ]
[ -DONOTOK ]
[ -DOSHOUT
<destination> <urgency R|U|V> <message> ]
[ -DOCOND
<condname> <dateref>|ODAT ADD|DEL ]
[ -DOAUTOEDIT <varname> <expression> ]
[ -DOFORCEJOB <tablename> <jobname> <odate>|ODAT ]
[ -DOMAIL
<destination> <cc> {R|U|V} <subject> <message> ]
Utilities
2-75
At least one Schedule tag must be specified (using the -TAG parameter)
for each run of the ctmgrpdef utility. Definition of additional tags is
optional.
Parameters not in the user guide are described in Table 2-28.
Table 2-28
cmtgrpdef Parameters
Parameter
Description
debug
quiet
2-76
ctmjsa
ctmjsa compiles runtime data from the Statistical Details table and
records it in the Statistics Summary table of the CONTROL-M database.
Each time it is run, this utility:
Scans the statistical data for jobs that terminated with a status of OK.
The jobs scanned can be limited to a range of dates as described
below.
Computes the average run time and standard deviation for each job
for which data was found.
Utilities
2-77
Table 2-29
ctmjsa Parameters
Parameter
Description
<From Date>
<To Date>
-<Delta1>
-<Delta2>
<Date>
-list
<Filter>
-MEMNAME <memname>
-MEMLIB <memlib>
-NODEID <nodeid>
2-78
Note
Example 1
The following commands compile statistical data for the 5-day period
from June 21, 2000 through June 25, 2000 (assuming this data is
available). In the second command, the hyphens indicate the beginning
of unsigned parameter values; they are not minus signs.
ctmjsa 000621 000625
ctmjsa -3 -1 000624
Example 2
The following command compiles statistical data using all data currently
available:
ctmjsa ""
Utilities
2-79
Example 3
This command displays summary data for all jobs whose Mem Name
parameter starts with pgmac: ctmjsa -list -MEMNAME "pgmac*"
A report similar to the following is displayed:
JOBNAME
NODEID
CPU [sec]
ELAPSED
(sec)
MEMNAME
MEMLIB
pgmacct1
prod.acct.pgm
diana
0.19
233.15
pgmacct2
prod.acct.pgm
verdi
0.12
6.12
pgmacct3
prod.acct.pgm
diana
0.05
170.45
pgmacct4
prod.acct.pgm
diana
0.34
145.23
2-80
ctmkilljob
The ctmkilljob utility terminates a specified CONTROL-M job and all its
processes. ctmkilljob terminates only jobs that are currently executing.
Note
ctmkilljob Parameters
Parameter
Description
orderid
nodeid
memlib
memname
jobname
If the action was successful, the utility responds with the statement:
Job was killed.
The parameters specified for ctmkilljob must indicate one unique job. If
more than one job fits the description specified in the command, you are
informed that a unique name must be entered to carry out the action.
Reenter the command with parameters that specify one unique job.
Utilities
2-81
ctmldnrs
ctmldnrs creates and loads the Manual Conditions file. This file contains
prerequisite conditions that are required by jobs in the Active Jobs file
but which will not be available (that is, added to the
Conditions/Resources table) unless there is some form of manual
intervention.
For example:
2-82
Utilities
2-83
Table 2-31
Parameter
Description
ADDMODE
OUTPUT
<Filename>
IGNOREIN
IGNOREOUT
IGNORECODES
<Condition
Name>
Note
2-84
Parameter
Description
<Filename>
<Condition Name>
Example 1
Example 3
The following command loads all conditions from the default input
Manual Conditions file to the Conditions/Resources table:
ctmldnrs -LOAD
Utilities
2-85
ctmloadset
The ctmloadset utility is used to record current resource usage on an
Agent platform in the Quantitative Resources table. This utility is
typically invoked by a cyclic job that runs on the Agent platform and
measures usage of a certain resource on the platform. Usage data is then
used to update the Quantitative Resources table on the server platform.
ctmloadset is used when load balancing is implemented. The
load-balancing algorithm uses the data recorded in the Quantitative
Resources table to determine to which Agent platform a job should be
submitted.
CONTROL-M maintains the following information regarding usage of
each Quantitative resource:
Item
Description
Total Used
Used by
CONTROL-M
Used by Others
Specify the value for Total Used for a resource. ctmloadset subtracts
the value for Used by CONTROL-M from the value you specify
and places the remainder in the field Used by Others.
Specify the value for Used by Others for a resource. This value is
added to the value Used by CONTROL-M to calculate the value
Total Used for the resource.
2-86
ctmloadset Parameters
Parameter
Description
TOTAL
Indicates that the load value provided specifies the total usage
of the resource by all jobs (both CONTROL-M jobs and
non-CONTROL-M jobs).
When this option is specified, the utility calculates the usage of
the resource by non-CONTROL-M jobs and updates the table
accordingly.
OTHERS
Indicates that the load value provided specifies the units of the
resource used by one or more non-CONTROL-M jobs.
<QR name>
<Load
value>
Example 1
A node group contains three Agent platforms: diana, jacklin and ruby.
Each platform is defined in the Quantitative Resource table as having
200 units of resource CPU_load, representing the load on the platforms
CPU.
Utilities
2-87
The Total Used for diana is set to 80% of 200, or 160. Since the usage by
CONTROL-M jobs is currently 75 units, ctmloadset calculates that the
Other (non-CONTROL-M usage) is 160 75, or 85.
As a result, the Quantitative Resources table now contains the following
values:
Resource
Max
Total Used by
CONTROL-M
Total Used by
Others
CPU@jacklin
200
120
80
CPU@ruby
200
150
50
CPU@diana
200
75
85
Free
40
2-88
Type
Max-Avail
Reserved
Used
Free
CPU@diana
50
30
20
Example 3
Type
Max-Avail
Reserved
Used
Free
CPU@diana
50
42
Example 4
Type
Max-Avail
Reserved
Used
Free
CPU@diana
50
36
14
Utilities
2-89
Example 5
The following command specifies that the current total usage of the
Quantitative resource CPU@diana by all jobs is 48 units:
ctmloadset TOTAL CPU@diana 48
Type
Max-Avail
Reserved
Used
Free
CPU@diana
50
48
2-90
ctmlog
ctmlog is used to create a report from entries in the CONTROL-M log or
to delete entries in the CONTROL-M log.
Specify one of the following commands to invoke the ctmlog utility:
ctmlog <Action> <Action Option> \
<From date> <From Time> <To Date> <To Time>
[<Output> [<Report Width>] ]
ctmlog <Action> <Action Option> ""
[<Output> [<Report Width>] ]
Valid values for <Action> and <Action Option> are listed in Table 2-34.
All other parameters of this utility are described in Table 2-35.
Note
All actions are limited to log entries in the range specified using the time
and date parameters.
Table 2-34
Action
Action Option
listss
<subsystem>
list
None.
Utilities
2-91
Table 2-34
Action
Action Option
listord
<Order ID>
listjob
<Job no.>
listmsg
<msgid>
delete
None
listjobname
<jobname>
Table 2-35
ctmlog Parameters
Parameter
Description
<From Date>
<From Time>
<To Date>
<To Time>
<Output>
<Report Width>
2-92
Example 1
Utilities
2-93
ctmordck
The ctmordck utility lists job processing definitions associated with a
specific User Daily name and indicates the security status of each job
with regard to the owner of the User Daily job (that is, whether or not the
CONTROL-M security mechanism will allow jobs associated with a
User Daily name to run with the authorizations currently assigned to the
owner of the User Daily job).
This utility displays the following fields:
Column
Description
TB
FL
UA
Note
2-94
Table 2-37
ctmordck Parameters
Parameter
Description
<User Name>
<User Daily>
<Output>
Example
The following command generates a list for user SYSTEM and the User
Daily SYSTEM. The list is directed to the udlist file:
ctmordck SYSTEM SYSTEM /ctm/user1/udlist
Date: 10-NOV-2000.
Page: 1
User SYSTEM , Daily SYSTEM Ordering list
JOBNAME
---------CTMLOG HAN
PURGE JOB
user3-DAIL
user2-DAIL
user1-DAIL
JEAN-UD
JOB-STATUS
GD-TEST1
GD-TEST2
GD-TEST3
GD-user4
GD-user5
No. AUTHOR
--- -----2066 root
2067 root
2033 BARRY
2032 STEVE
2031 STEVE
2000 jean
2068 root
20 jean
21 jean
22 jean
2008 jean
2009 jean
OWNER
----root
root
user3
user2
user1
jean
root
user1
user2
user3
user4
user5
TB
-Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
FL
-N
N
N
N
N
N
N
N
N
N
N
N
UA
-Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Utilities
2-95
ctmorder
ctmorder orders or forces one or more jobs from a Scheduling table in the
CONTROL-M database.
Ordered jobs are placed in the Active Jobs file if their scheduling
criteria are met.
Forced jobs are placed in the Active Jobs file regardless of their
scheduling criteria.
If two jobs with the same name exist in a Scheduling table and you use
the ctmorder utility to force a job with that name, only the first job is
forced.
Note
If the ctmorder utility is running when the New Day procedure begins, it
is automatically suspended until New Day procedure is ended.
Syntax
Note
2-96
Parameter
Description
-schedtab
-jobname
Utilities
2-97
Table 2-38
Parameter
Description
-odate
-force
-seqno
-ingrouporderid
last
alone
-debug level
-quiet
2-98
Table 2-38
Parameter
Description
-noduplication
-autoedit
<expression>
Note
The following command orders all jobs contained in the Scheduling table
ACCT100 whose job name begins with ga. Any jobs placed in the
Active Jobs file will have the date March 15, 2000 as their original
scheduling date:
Utilities
2-99
Example 3
The following command forces all jobs contained in the Scheduling table
ACCT100 whose job name is prodyjob. Any jobs placed in the Active
Jobs file will have the date December 31, 2000 as their original
scheduling date:
ctmorder -schedtab ACCT100 -jobname prodyjob
-odate 20001231 -force y
Example 4
The following command forces the third job contained in the Group
Scheduling table ACCT200 whose job name parameter consists of
prodyjob. This job is placed in the Active Jobs file and will have the
date December 31, 2000 as its original scheduling date. This job is
added to an active group whose orderid is B2.
ctmorder -schedtab ACCT200 -jobname prodyjob
\
-odate 20001231 -force y -seqno 3 -ingrouporderid B2
Example 5
\
\
2-100
Example 6
\
\
\
\
Utilities
2-101
ctmpasswd
The ctmpasswd utility enables the administrator to change the
CONTROL-M Users password for accessing the database. Only an
administrator can change the password.
To invoke the ctmpasswd utility, specify the following command:
>ctmpasswd
1. Enter the old password for the CONTROL-M account. The system
will prompt you to enter the new password:
Please enter the new password for CONTROL-M
account:
2. Enter the new password for the CONTROL-M account. Make sure
that the password consists of at least 6 characters. Note that you will
not see your entry on the screen. The system will then prompt you to
enter the password again:
Enter again to verify:
2-102
ctmping
The ctmping utility detects and collects configuration information about
CONTROL-M/Agents. This utility can also connect Agents that are
already in the database, and test communication between them and the
CONTROL-M/Server.
Note
Parameter
Description
-nodeid
-file
Utilities
2-103
Table 2-39
Parameter
Description
-discover
-debug
-quiet
Example 1
2-104
Example 3
To connect and test communication with the Agent jacklin and collect
configuration information needed for the discovery process, specify the
following command:
ctmping -nodeid jacklin -discover y
To connect and test communication with the Agent jacklin and generate
a debug trace without displaying the results on screen, specify the
following command:
ctmping -nodeid jacklin -debug 1 -quiet
Only the return code of the utility will indicate if it was successful. The
debug trace information is saved to the following file:
ctm-home\ctm\proclog\ping<PID>.<PID>
Utilities
2-105
ctmpsm
The ctmpsm utility can be invoked interactively to display the
CONTROL-M Production Support menu. This menu is used to perform
functions affecting jobs or conditions in the active environment of the
data center. It provides an alternative to using the ENTERPRISE/CS GUI
and enables you to perform many of the GUI functions directly in the
data center.
Note
The ctmpsm utility can also be invoked by the Command Line Interface,
as described in Command Line Invocation on page 2-115.
To invoke the ctmpsm utility interactively:
Resource Map
------------
1)
2)
3)
4)
List
List
List
List
All
All (Show Started/Ended)
All (Show Application)
All (Show Mem Name)
5)
6)
7)
8)
9)
10)
List
List
List
List
List
List
61)
62)
63)
64)
65)
Control Resources
Quantitative Resources
Prerequisite Conditions
Control Resources Usage
Quantitative Resources Usage
Scheduling Functions
-------------------71) Scheduling Tables
72) Order Tables/Jobs
Q) Quit
Enter Option:
2-106
Active Jobs File functions provide various views of the Active Jobs
file. Each view displays information about the jobs and provides
options to perform such actions on the jobs as Hold, Free, Delete,
Rerun, Why, Confirm, View or modify job details, and view the
CONTROL-M log.
Perform various tasks using information in the Active Jobs file. These
options are described in Table 2-40 below.
Table 2-40
Code
Option
Description
List All
List All
(Show Started/Ended)
Lists all jobs in the Active Jobs file. Indicates which jobs have
started or ended execution.
List All
(Show Application)
Lists all jobs in the Active Jobs file. Indicates the application to
which each job belongs.
List All
(Show Mem Name)
Lists all jobs in the Active Jobs file. Indicates the Mem Name for
each job.
Lists jobs in the Active Jobs file that have a completion status of
Ended NOTOK.
List Submitted/
Executing Jobs
Lists jobs in the Active Jobs file that are currently executing.
Utilities
2-107
Table 2-40
Code
Option
Description
Lists jobs in the Active Jobs file that are waiting to begin
executing based on the time specified in their Time From
parameter.
10
Lists jobs in the Active Jobs file that are waiting for confirmation.
40
List Application/Group
Tree
41
42
All Active Jobs file options display the following menu at the bottom of
the screen:
Figure 2-4
2-108
Table 2-41
Option
Action
Description
Hold
Hold a job.
Free
Delete
Rerun
Rerun a job.
Undelete
Why
Details
LO
LogOrd
LJ
LogJob
Confirm
S1
S2
Sysout
Statistics
View script/JCL
Force OK
Dependencies Jobs
GH
GF
GD
GR
Utilities
2-109
Table 2-41
Option
Action
Description
GU
Note: The R (Rerun) option and the Global options (GH, GF, GD, GR, and GU) affect only
jobs and not group scheduling tables.
Resource Table Options
Table 2-42
Code
Option
Description
61
Control Resources
62
Quantitative Resources
63
Prerequisite Conditions
64
65
Quantitative Resources
Usage
Code
Option
Description
71
Scheduling Tables
72
Order Tables/Jobs
2-110
Scheduling Tables
----------------Table name
1) supply
2) temp
3) inventory
4) Payroll
5) inventory
6) RE_SYSOUT
Daily name
Quarterly
GROUP
Monthly
SYSTEM
vitaly
Table type
GROUP
REGULAR
GROUP
GROUP
REGULAR
U#) Update table #
J#) List jobs
#
Q) Quit.
Option []:
The options in Table 2-44 are available from the above screen.
Note
If a table that is associated with more than one User daily is modified
using ENTERPRISE/CS and then uploaded to CONTROL-M, that table
is removed from all User dailies except the one that is associated with it
in ENTERPRISE/CS.
Table 2-44
Code
Option
Description
Add
Remove
Deletes a specific Scheduling table and all its associated jobs (for
example, specify R RE_SYSOUT to delete table RE_SYSOUT).
Utilities
2-111
Table 2-44
Code
Option
Description
D#
Delete #
F#
Force table #
List jobs #
U#
Update table #
Updates the User Daily name for a specific Scheduling table (for
example, specify U6 to update the User Daily name for table
RE_SYSOUT).
When the List Jobs # option is selected, output similar to the following
is displayed:
2-112
Figure 2-6
Jobname:DAYS_CAL_N,
Jobname:DAYS_30_FE,
Jobname:DAYS_28_29,
Jobname:NO_CALENDA,
Jobname:DATES_0101,
Jobname:DATES_2902,
Jobname:DAYS_CAL_M,
Jobname:DAYS_CAL_P,
Jobname:DAYS_CAL_W,
Jobname:CALENDAR_O,
Jobname:wdays_all ,
Jobname:wdays_1_2_,
Memname:DAYS_CAL_NONE
Memname:DAYS_30_FEB
Memname:DAYS_28_29_FEB
Memname:NO_CALENDAR
Memname:DATES_0101_0202
Memname:DATES_2902
Memname:DAYS_CAL_MINUS
Memname:DAYS_CAL_PLUS
Memname:DAYS_CAL_WITHOUT
Memname:CALENDAR_ONLY
Memname:WDAYS_ALL
Memname:WEEKDAYS_1_2_3
Q) Quit.
F#) Force job #
M#) Month Schedule Plan # Y#) Year Schedule Plan for job #
Option []:
The options in Table 2-45 are available from the above screen.
Table 2-45
Code
Option
Description
F#
Force job #
M#
Y#
The ctmpsm utility can display the sysout for a specified order ID and
runcount.
To display the sysout for a given order ID and runcount, invoke the
following command:
ctmpsm -listsysout <order ID> [-sysoutnumber <number>]
Utilities
2-113
Parameter
Description
<order ID>
<number>
Examples
To display the most recent sysout of the job whose order ID is 1234,
specify the following command:
ctmpsm -listsysout 1234
To display the second sysout of the job whose order ID is 1234, specify
the following command:
ctmpsm -listsysout 1234 -sysoutnumber 2
The ctmpsm utility redirects the display of the sysout of a job to the
viewer defined by parameter CTMPSM_VIEWER. This parameter is
specified in the ctm/config.dat file. If no viewer is specified, the more
viewer opens in the active screen.
If the viewer opens in a new window, the DISPLAY environment
variable should be set to your host name. For more consult your Unix
Administrator.
To specify the CTMPSM_VIEWER parameter in the config.dat file,
type the following:
CTMPSM_VIEWER <viewer command>
2-114
Example
The format and valid values for each mode of the ctmpsm utility
command line interface are described in Table 2-46.
Table 2-46
Mode
Description
CHILD
Lists dependent jobs with IN conditions that are created by the job whose order
ID is specified in this command.
Syntax:
ctmpsm -CHILD <order_ID> [<tasktype>]
IMPORT_CAL
LISTCAL
order_ID
tasktype
B=batch job
D=detached
C=command
U=dummy
Calen_year
Utilities
2-115
Mode
Description
LISTALL
Lists jobs in the Active Jobs file. The list can be filtered by time, application, and
member name. The list can be sorted by order ID or job name.
Syntax:
ctmpsm -LISTALL [TIME|APPLICATION|MEMNAME|ALL|ALLFIELDS] [SORT {ORDERID|JOBNAME}]
In addition to the order ID and the job name, one of the following fields can also
be included in the LISTALL output:
TIME _ Time execution started and ended.
APPLICATION _ Application to which the job belongs.
MEMNAME _ Member name for the job.
ALL Includes ODAT and TIME fields.
ALLFIELDS Includes ODAT, MEMNAME, and APPLICATION fields.
SORT indicates the order in which the jobs should be listed. Valid orders are:
ORDERID, and JOBNAME.
LISTJOB
List in Active Jobs file with a specified status. Jobs can be restricted by status:
OK, NOTOK, executing, cyclic, waiting for the end of a time interval, waiting for
confirmation.
ctmpsm -LISTJOB {OK|NOTOK|EXECUTING|CYCLIC|
WAITTIME|WAITCONFIRM} [-SORT {ORDERID|JOBNAME}]
OK _ Jobs with a completion status of Ended OK.
NOTOK _ Jobs with a completion status of Ended NOTOK.
EXECUTING _ Jobs that are currently executing.
CYCLIC _ Jobs that are cyclic.
WAITTIME _ Jobs waiting to begin executing based on the time specified in their
Time From parameter.
WAITCONFIRM _ Jobs waiting for confirmation.
SORT indicates the order in which the jobs should be listed. Valid orders are:
ORDERID, and JOBNAME.
LISTGROUP
Lists jobs in the specified group that are associated with the specified
application.
ctmpsm -LISTGROUP <application> <group>
Wildcards can used as part of the specified application or group names.
* represents any number of characters.
? represents any single character.
2-116
Mode
Description
LISTAJFTAB
Lists jobs in the Active Jobs file that were ordered from the specified scheduling
table.
ctmpsm -LISTAJFTAB <table_name>
Wildcards can used as part of the specified table name.
* represents any number of characters.
? represents any single character.
SCHEDTAB
Lists Scheduling tables and jobs defined in the CONTROL-M database, and
allows you to add or delete Scheduling tables.
Syntax
ctmpsm -SCHEDTAB {-LISTTABLE <table_name>|-UPDATE <row_number>
<udaily_name>|-ADD <table_name> <udaily_name>|-DUDAILY <row_number>|REMOVE <table_name>|-LISTJOBS <row_number>}
The options in this command are described below:
-LISTTABLE
-UPDATE
-ADD
-DUDAILY
-REMOVE
-LISTJOBS
Utilities
2-117
Mode
Description
LISTSYSOUT
List the sysouts for an order ID. The list can be restricted by runcount number.
Syntax:
ctmpsm -LISTSYSOUT <order_ID> [SYSOUTNUMBER {<number>|ALL}]
order_ID
number
LISTDETAILS
Lists the details of the job associated with the specified order ID.
Valid syntax is:
LISTDETAILS <orderid>
UPDATEAJF
Performs a specified command or updates conditions for a job in the Active Jobs
that is associated with a specified order ID.
Syntax
ctmpsm -UPDATEAJF <order ID> <command>
Where command is one of the following:
HOLD _ Set a jobs status to HELD.
FREE _ Free a previously held job.
DELETE _ Mark a job for deletion.
UNDELETE _ Undelete a job marked for deletion.
RERUN _ Rerun a job.
CONFIRM _ Confirm submission of a job.
FORCEOK _ Force a jobs status to be OK.
CONDADDIN <cond> <date> <AND|OR> _ Add the specified IN condition with
the specified date reference. You can include one or more additional IN
conditions by using the AND or OR conjunctional parameter.
CONDADDOUT <cond> <date> <+|-> _ Add the specified OUT condition with
the specified date reference. Use + to indicate that the condition must be
present. Use - to indicate that the condition must not be present.
CONDDELIN <cond> _ Delete the specified IN condition.
CONDDELOUT <cond> _ Delete the specified OUT condition.
Note: Conditions specified using this mode are applied only to the specified
instance of the job in the Active Jobs file. Subsequent orders of that job are not
affected by these changes.
2-118
Mode
Description
UPDATEGROUP
Applies a specified command to jobs in the specified group that are associated
with the specified application.
Applies a specified command to jobs in the Active Jobs file that were ordered
from the specified table.
Utilities
2-119
ctmrpln
ctmrpln creates a report that lists all or a selection of jobs in a specified
Scheduling table, and indicates when the jobs are scheduled to run. In
addition, it enables you to test the effect of different calendars on the
scheduling of jobs in the table.
Each report can be created in one of three formats, as described in
Table 2-47:
Table 2-47
Format
Description
Daily Report
Monthly Report
Yearly Report
Description
2-120
Char
Description
Parameter
Description
<Report_type>
<Calendar>
DM (or
D)
DJ
MM (or
M)
MJ
<Name>
Utilities
2-121
Table 2-48
Parameter
Description
<Schedtab>
<Jobname>
<Date>
<Output>
Example 1
2-122
Example 2
Utilities
2-123
ctmruninf
ctmruninf displays runtime data from the Statistical Details table of the
CONTROL-M database. An option is available to delete data from this
table. The jobs scanned for both options can be limited to a range of
dates as described below.
Note
The parameters for the above commands are described in Table 2-49.
Table 2-49
Parameter
Description
-list
-delete
<From Date>
<To Date>
2-124
Table 2-49
Parameter
Description
<Filter>
-total
Example 1
The following command displays runtime data for the period January 21,
2000 through January 25, 2000 (assuming that this data is available):
ctmruninf -list 20000121000000 20000125000000
Utilities
2-125
Example 2
The following command causes the utility to display and total runtime
data for all jobs on Agent platform diana.
ctmruninf -list "" -NODEID "diana" -total
JOBNAME
ORDERID
---------- -------acct12
00000007
gen786
0000000b
acct14
00000011
acct15
00000012
---------- -------printed : 2
RUN#
---1
1
1
1
---0.50
NODEID
-----------diana
diana
diana
diana
-----------555.35
MEMNAME
---------pgmacct
genx
pgmacct
pgmacct
----------
MEMLIB
CPU
ELAPSED
-------------- ----- ------prod.acct.pgm
0.19 233.15
prod.general
0.12
6.12
prod.acct.pgm
0.05 170.45
prod.acct.pgm
0.14 145.23
-------------- ----- -------
Example 3
The following command deletes the statistical data for January 31, 2000
ctmruninf -delete 20000131000000 20000131235959
2-126
ctmshout
ctmshout issues Shout messages to an indicated destination. It can be
entered directly or from a job script. See Shout Destination Tables on
page 1-24, for more information about Shout message destinations.
Specify the following command to invoke the ctmshout utility:
ctmshout [-ORDERID <Order_ID>] [-NODEID <Node_ID>]
-USER <Destination> [-USER <Destination>]\
-MESSAGE <Message_text> [-MESSAGE <Message_text>]
[-SEVERITY <{R|U|V}>]
Table 2-50
ctmshout Parameters
Parameter
Description
<Order_ID>a
<Node_ID>
<Destination>
<Message_text>
<{R|U|V}>
Utilities
2-127
The following command sends the message File not found to the
Alerts window in ENTERPRISE/CS and associates it with a job whose
Order ID is 1234:
ctmshout -ORDERID 1234 -USER ECS -MESSAGE "File not found" \
-SEVERITY V
Example 2
Example 3
The following illustrates the use of the ctmshout utility in a job script
command to send the Shout message Job started to the Alerts window
in ENTERPRISE/CS.
The job processing definition for a certain job contains the following
AutoEdit Assignment parameter:
%%PARM1 = %%ORDERID
The script used to execute the job contains the following command:
ctmshout -O $1 -USER ECS -MESSAGE "Job started" \
-SEVERITY R
2-128
ctmshtb
ctmshtb sets the active Shout Destination table. The Shout Destination
table associates physical output destinations with logical destination
names specified in Shout and Do Shout statements in job processing
definitions. For more information, refer to Shout Destination Tables in
Chapter 1, Overview.
Activation of this utility changes the active Shout Destination table to the
table specified.
You can add, delete and modify Shout Destination tables using the
ctmsys utility, described earlier in this chapter. The ctmsys utility can
also be used to specify the active Shout Destination table interactively.
Specify the following command to invoke the ctmshtb utility:
ctmshtb <Table>
The following command sets the current active Shout Destination table
designation to SHIFTMAN:
ctmshtb SHIFTMAN
Utilities
2-129
ctmstats
ctmstats displays and deletes statistical data from the Statistical
Summary table of the CONTROL-M database. The data scanned for both
options can be limited to a range of dates. The Statistical Summary table
is created via the ctmjsa utility.
Note
Table 2-51
Parameter
Description
-list
-delete
<From Date>
Starting date of statistical data to be displayed/deleted. The date is specified in yyyymmddhhmmss format.
<To Date>
2-130
Table 2-51
Parameter
Description
<Filter>
-total
Example 1
The following command displays statistical data for the period January
21, 1999 through January 25, 1999 (assuming that this data is available):
ctmstats -list 19990121000000 19990125000000
Utilities
2-131
TIMESTAMP
-------------19990122141214
19990122032025
19990121123111
19990121113512
JOBNAME
---------acct12
gen786
acct14
acct15
NODEID
-----------diana
diana
diana
diana
MEMNAME
---------pgmacct
genx
pgmacct
pgmacct
MEMLIB
AVG CPU AVG ELAPSED
-------------- ------- ----------prod.acct.pgm
0.19
233.15
prod.general
0.12
6.12
prod.acct.pgm
0.05
170.45
prod.acct.pgm
0.14
145.23
Example 2
The following command displays statistical data for all jobs on Agent
platform diana:
ctmstats -list "" -NODEID diana -total
Example 3
The following command deletes the statistical data for January 31, 1999:
ctmstats -delete 19990131000000 19990131235959
2-132
ctmstvar
The ctmstvar utility displays the current value of an AutoEdit variable or
function. Specify the following command to invoke the ctmstvar utility:
ctmstvar <order id> <autoedit string>
Table 2-52
ctmstvar Parameters
Variable
Description
<order id>
<autoedit string>
Utilities
2-133
ctmsuspend
ctmsuspend suspends and restores CONTROL-M/Server
non-communication processes for mass batch uploads/downloads from
ENTERPRISE/CS. During suspension mode, CONTROL-M inactivates
its job processing functions by suspending the TR, SL, NS, and LG
processes. For more information, see CONTROL-M/Server Processes
on page 4-43. Requests for job processing during this mode are
suspended until execution of ctmsuspend restoration mode.
This utility should be invoked before executing the Mass Upload or
Mass Download features on the ENTERPRISE/CS Graphical User
Interface.
Specify the following command to invoke the ctmsuspend utility:
ctmsuspend {-s|-r}
Table 2-53
cmtsuspend Options
Var
Description
-s
-r
Example
2-134
ctmsys
The ctmsys utility is an interactive utility for maintaining the following
CONTROL-M parameters:
q)
Quit
Enter option:
The options in this menu and in all other menus provided by this utility
can be selected by typing the option number or command letter and
pressing Enter.
Each option appearing in the main menu is described below.
Utilities
2-135
Create/Modify a Table
Set Active Table
List Tables
Delete Table
q)
Enter option:
2-136
Step 2
q) Quit
entry #
Logical Name
------------
Physical Name
-------------
n) New entry
d#) Delete
Enter option:
Utilities
2-137
Item
Description
Destination Type
Address Type
Logical Name
Physical Name
1. Specify n.
The following prompts appear:
Dest. Type: (U)ser (M)ail (T)erminal c(O)nsole
(L)og (P)rogram (E)NTERPRISE/CS:
BMC Software, Inc., Confidential and Proprietary Information
2-138
Utilities
2-139
2. Specify a new physical name for the entry. The table is redisplayed
with the modified entry.
To delete an existing entry in the table:
2. Specify the name of the table to set as the active Shout Destination
table.
The following message is displayed:
Table <table name> is now active.
Press ENTER to continue.
2-140
To specify the active Shout Destination table via a batch job, run the
ctmshtb utility, described earlier in this chapter.
To list existing Shout Destination tables:
Utilities
2-141
System Parameters
2-142
Utilities
2-143
Figure 2-8
p) Previous Page
s) Save and Return to Main Menu
c) Cancel
Enter command, or item number you wish to change [p]:
Step 3
2-144
ctmudchk
ctmudchk checks whether all the jobs which should have been ordered by
a User Daily job are in the Active Jobs file. This utility facilitates
recovery from the interruption of a User Daily job.
When using the ctmudchk utility, the New Day procedure must not be
running (that is, the status of the data center in the Communication Status
window of ENTERPRISE/CS must not be Formatting AJF).
Use the following command to invoke the ctmudchk utility:
ctmudchk -DAILY <User Daily name> -ACTION {LIST|ORDER}
-FILE <File Name>
ctmudchk Parameters
Parameter
Description
-DAILY
-ACTION
-FILE
LIST
ORDER
Example 1
Use the following command to check the Active Jobs file for jobs which
are ordered by the User Daily whose name is payroll. The Job Name and
Scheduling table are listed for each job that is not in the Active Jobs file.
ctmudchk -DAILY payroll -ACTION LIST
BMC Software, Inc., Confidential and Proprietary Information
Utilities
2-145
Example 2
Use the following command to check the Active Jobs file for jobs which
are ordered by the User Daily whose name is admin1. The utility orders
each job that is not in the Active Jobs file.
ctmudchk -DAILY admin1 -ACTION ORDER
Return Codes
2-146
ctmudlst
The ctmudlst utility is used to display or modify UDLAST (the User
Daily last run date). See Date Control Record (UDLAST) on page 121, for more information.
When using the ctmudlst utility, the New Day procedure must not be
running (that is, the status of the data center in the Communication Status
window of ENTERPRISE/CS must not be Formatting AJF).
To invoke the ctmudlst utility, specify one of the following commands:
ctmudlst LIST <User Daily>
ctmudlst LIST ""
ctmudlst UPDATE <User Daily> <Date>
ctmudlst Parameters
Parameter
Description
LIST
UPDATE
<User Daily>
<Date>
Example 1
The following command lists the last run date for User Daily payroll:
ctmudlst LIST payroll
Utilities
2-147
Example 2
The following command changes the last run date for User Daily
inventory to Aug. 10, 1998:
ctmudlst UPDATE inventory 19980810
2-148
ctmudly
ctmudly orders jobs for a specific User Daily name.
The utility orders all Scheduling tables associated with a specific User
Daily name. Each job in the ordered Scheduling tables whose Scheduling
criteria are satisfied is placed in the Active Jobs file.
See User Daily Jobs on page 1-18, for more information and examples.
To invoke the ctmudly utility, specify the command:
ctmudly <User Daily>
where <User Daily> is a User Daily name associated with one or more
Scheduling tables. This parameter is case-sensitive.
Example
The following command orders all Scheduling tables whose User Daily
parameter is prod:
ctmudly prod
Utilities
2-149
ctmvar
The ctmvar utility defines, deletes, modifies and displays AutoEdit
variables. This utility can be applied to variables that are:
Special notes:
Syntax
2-150
Table 2-57
Parameter
Description
-action
SET
DELETE
LIST
Utilities
2-151
Table 2-57
Parameter
Description
-var
Notes:
This parameter cannot be specified together with -action
LOAD.
For more information about AutoEdit variables, see the
AutoEdit chapter in the Enterprise Controlstation User Guide.
-varexpr
-filename
2-152
Table 2-57
Parameter
Description
-quiet
-debug
Sets a debug level for the utility. This parameter is used for
maintenance and troubleshooting purposes. The level, a
numeric value from 0 to 5, must be used only if requested and
specified by Technical Support.
Note: Performance is somewhat slower and requires a larger
number of resources when operating in debug mode. It is
recommended that you activate debug mode only when
absolutely necessary and revert to normal mode as soon as
possible.
Examples
Utilities
2-153
ctmwhy
ctmwhy displays a report stating why a job waiting in the Active Jobs
file is not being submitted for execution. This utility is equivalent to the
Why option available from the Job Node menu in the Enterprise
Controlstation window.
To invoke the ctmwhy utility, specify the command:
ctmwhy <Order ID>
where <Order ID> is the Order ID of a job waiting in the Active Jobs
file (as displayed in the Job Details window of ENTERPRISE/CS).
Note
Specify the following command to determine why the job with Order ID
A4X is not being submitted for execution:
ctmwhy A4X
Specify the following command to determine why the job with Order
ID 11 is not being submitted for execution. The Order ID in this example
is expressed as a base 10 number:
ctmwhy "37"
2-154
ctm2snmp
The ctm2snmp utility enables the user to send messages to various
Network Management applications (for example, HP-OpenView,
NetView for AIX, and Tivoli Management Environment Console) via
SNMP traps. See the SNMP Interface appendix in the Enterprise
Controlstation Administrator Guide for a description of SNMP traps.
SNMP traps issued via CONTROL-M consist of the fields described in
Table 2-58.
Table 2-58
Field
Description
SEVERITY
SEND TIME
USER NAME
MSG TEXT
Table 2-59
ctm2snmp Parameters
Parameter
Description
-host_name
-severity
-message
Message to be sent.
Utilities
2-155
The following entry must be added to the /etc/services/ file (if not
already present):
snmp-trap 162/udp # snmp monitor trap port
2-156
ecactltb
ecactltb displays a list of Control resources and the status of each
resource.
To invoke the ecactltb utility, specify the following command:
ecactltb [<Output>]
<Output> is the full path name to which the report should be sent
(optional). If this parameter is not specified, the output is routed to the
default output device.
Example
Utilities
2-157
ecaqrtab
ecaqrtab performs operations on the Quantitative Resources table. These
operations include:
ecaqrtab Parameters
Parameter
Description
LIST
ADD
DELETE
UPDATE
<QR_Name>
2-158
Table 2-60
ecaqrtab Parameters
Parameter
Description
<Max>
<Output>
Table 2-61 describes the fields that are displayed for each Quantitative
resource that matches the specified resource name or mask.
Table 2-61
Parameter
Description
QR name
Type
Max Avail
Reserved
Used
Free
Example
Utilities
2-159
2-160
Example
The following command specifies that the new maximum availability for
the existing Quantitative resource linerje2 on platform diana is 12 units:
ecaqrtab UPDATE linerje2@diana 12
Utilities
2-161
2-162
Security
3
CONTROL-M includes security features that protect CONTROL-M
against unauthorized usage or modification. These features enhance the
standard Unix security, and provide an additional application-level
security layer.
Using CONTROL-M security, you can specify actions that each
ENTERPRISE/CS user or CONTROL-M user is authorized to perform.
These authorizations used to perform security checks each time one of
the following actions is attempted:
Ordering a job.
Commands affecting jobs in the Active Jobs file (for example, Hold,
Confirm, Rerun).
Security
3-1
Security Levels
Security Level
Description
Restricted
Unrestricted
3-2
Entities Authorization
User actions performed on various CONTROL-M entities (for
example, prerequisite conditions).
Security
3-3
Action
Description
Delete
Read
Update
OrderTable
Delete
3-4
Action
Authorization
Order
Order a job.
Force
Force a job.
Rerun
Hold
Confirm
Delete
Why
Security
3-5
Table 3-3
Action
Authorization
Sysout
Log
Statistics
Select the Zoom & Save option from the job Details menu.
Terminate Job
Select the Kill job option from the job Details menu.
3-6
Entities Authorization
Entities Authorization determines a users authorization to perform
actions on certain CONTROL-M entities. These entities are accessed
either directly from the ENTERPRISE/CS workstation or via utilities on
CONTROL-M Server or Agent platforms. Table 3-4 describes the
entities that are controlled by these authorizations.
Table 3-4
Entities Authorization
Entity
Authorization
Access
Condition
ENTERPRISE/CS
ctmcontb
Control
Control resources
ENTERPRISE/CS
Resource
Quantitative resources
ENTERPRISE/CS
ecaqrtab
Calendar
ENTERPRISE/CS
Log
CONTROL-M log
ctmlog
Security
3-7
3-8
Summary of Authorizations
The following tables summarize the authorizations required to perform
various actions under CONTROL-M.
Table 3-5
Who
Authorization
Table 3-6
Who
Authorization
CONTROL-M account
owner
Table 3-7
Who
Authorization
ENTERPRISE/CS user
Security
3-9
Table 3-8
Who
Authorization
ENTERPRISE/CS user
Table 3-9
Authorization Do Forcejob
Who
Authorization
Table 3-10
Who
Action
Authorization
ENTERPRISE/CS
user
All actions
Edit JCL/Script
3-10
If there are no authorizations defined for the specific user, the user
inherits the authorizations specified for the group.
Security
3-11
ctmsec
-or-
3-12
Figure 3-1
+-----------------------------------------------+
|
CONTROL-M SECURITY MAINTENANCE UTILITY
|
|
Main Menu
|
+-----------------------------------------------+
1)
2)
3)
4)
5)
q)
User Maintenance
Group Maintenance
Scheduling Table Authorization
Active Jobs File Authorization
Entities Authorization
Quit
Enter option:
User Maintenance
The User Maintenance option of the ctmsec utility is used to add,
delete, or modify specific users in the CONTROL-M Security database.
Note
Security
3-13
Figure 3-2
Description
For passing Global conds.
Group
Group1
Group2
3-14
Security
3-15
3-16
Security
3-17
Group Maintenance
Each ENTERPRISE/CS user with a user account on the Server platform,
who is defined in the CONTROL-M Security database, can be defined as
part of a group. Belonging to a group is optional. All users belonging to a
group inherit the authorizations defined for the group.
Select Option 2 from the Security Maintenance Main menu to display the
Group Maintenance menu.
Figure 3-3
3-18
Security
3-19
Group: Group1
Modify Group Information
----------------------1) Description :
s) Save
and return to menu
c) Cancel and return to menu
Enter command, or specify item number to modify:
3-20
2. Specify the user or group for whom you are defining authorizations.
If the user or group is not defined in the CONTROL-M/Server
database, the following message is displayed:
User/Group name is not defined in the CONTROL-M
Security database.
Security
3-21
Figure 3-4
Quit
Enter option:
3-22
Save
and return to menu
Cancel and return to menu
The Y setting enables authorization for the action (for example, Read), N
disables the authorization, and (D)efault uses the authorization defined
for the users group. If the user was previously authorized for this
scheduling table, the users current authorizations are displayed;
otherwise, all authorizations are set to N.
3. To modify an authorization, type the number preceding the
authorization. Press <Enter> to toggle the authorization between N,
Y and D.
Type s to save your changes and return to the previous menu.
Modifications are not saved until you perform this action.
-orType c to cancel all changes and return to the previous menu.
To delete Scheduling Table authorizations for the specified user/group:
Security
3-23
Specify the user or group for whom you are defining authorizations.
If the user or group is not defined in the CONTROL-M/Server
database, the following message is displayed:
User/Group name is not defined in the CONTROL-M
Security database.
Press ENTER to continue:
BMC Software, Inc., Confidential and Proprietary Information
3-24
2. Press <Enter> to return to the Main menu. The Active Jobs File
Authorization menu is displayed:
Figure 3-5
Quit
Enter option:
To list owners for whom the user has Active Jobs File authorizations:
Node1
Owner2
Node2
To create or modify Active Jobs File authorizations for the specified user:
Security
3-25
3. Specify the node group of the Agents where the job can be scheduled
to run (maximum 30 characters, case-sensitive).
Note
A value must be specified for the Node Group prompt. (Null is not a
valid value.) To indicate all node groups, specify an asterisk (*) for this
prompt.
A list similar to the following is displayed:
Owner: Owner1, Node Group: Node1 User/Group: User1
Create/Modify Active Jobs File Authorization
-------------------------------------------1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
s)
c)
Order
:Y
Force
:Y
Rerun
:Y
Hold
:N
Confirm
:N
Delete
:Y
Why
:N
Sysout
:N
Log
:N
Statistics
:N
Zoom & Save
:N
Kill job
:N
Save
and return to menu
Cancel and return to menu
3-26
The Y setting enables authorization for the action (for example, Read), N
disables the authorization, and (D)efault uses the authorization defined
for the users group. If the user was previous authorized for this
owner and node, the users current authorizations are displayed;
otherwise, all authorizations are set to N.
4. To modify an authorization, type the number preceding the
authorization. Press <Enter> to toggle the authorization between N,
Y and D.
5. Type s to save your changes and return to the previous menu.
-orType c to cancel all changes and return to the previous menu.
To delete Active Jobs File authorizations for the specified user:
2. Specify the name of the Job owner for whom authorizations should
be deleted (or press <Enter> to return to the menu).
The following prompt is displayed
Node Group:
3. Specify the name of the Node group of the Job owner for whom
authorizations should be deleted (or press <Enter> to return to the
menu).
The user authorizations for this owner on the Node group are deleted
from the Security database, and the Active Jobs File Authorization
menu is displayed.
Security
3-27
Entities Authorization
This option is used to assign authorizations to a user or group to perform
actions relating to CONTROL-M entities.
For more information about the types of authorization that can be granted
using this option, see Entities Authorization on page 3-7.
To maintain Entities authorizations:
2. Specify the user or group for whom you are defining authorizations.
3-28
Figure 3-6
Quit
Enter option:
To list Entity categories for which the user or group has authorizations:
Security
3-29
3-30
Security
3-31
User Authorization
The user authorization options of the ctmsec command are used to list,
update, delete, and copy users in the CONTROL-M Security database.
3-32
Group Authorization
Group authorization options of the ctmsec command are used to copy,
list, modify, and delete groups in the CONTROL-M Security database.
-GROUP_DELETE <group>
<table>
<table>
Note
Security
3-33
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
{Y|N|D}]
Entities Authorization
The entity authorization options of the ctmsec command are used to
assign authorizations to users and groups to perform actions relating to
CONTROL-M entities.
3-34
The file created using the EXPORT option of the ctmsec utility, can be
modified before security definitions are imported either back to the same
installation, or to a different CONTROL-M installation. This is different
from the file that is created using the Backup Security Definition Tables
option of the Security Authorization Menu (which cannot be modified).
For more information about exporting CONTROL-M Security Definition
tables, see Security Authorization Menu on page 4-29.
Use the following command to export CONTROL-M Security Definition
tables:
ctmsec -EXPORT <filename>
Security
3-35
Example
ctmsec -EXPORT /home/controlm/securedata
This procedure will work only with a file that was created using the
-EXPORT option of the ctmsec utility. If your input is a file created using
the Backup Security Definition Tables option of the Security
Authorization menu, then you must import using the Restore option in
that same menu. for more information, see Table 4-7, Security
Authorization Menu, on page 4-29.
3-36
where <filename> is the full path name of the file created by the
option chosen in step 1.
Note
Security
3-37
3-38
Maintenance
Maintenance
4-1
4-2
Periodic Maintenance
The following procedures should be performed on a regular basis:
Maintenance
4-3
This is the same script used by the Check Database option. Possible
messages generated by this script relating to the amount of available
space in the CONTROL-M database are:
WARNING: Database is more than half full
ATTENTION: Database is more than 80% full
ATTENTION: Database log segment is more than 90% full
4-4
For Oracle:
<controlm_path>/oracle/admin/<$CONTROLM_DATABASE>/b
dump/alert_<$CONTROLM_DATABASE>.log
Maintenance
4-5
4-6
Menu Item
Description
CONTROL-M Manager
Database Creation
Database Maintenance
Database Mirroring
Security Authorization
Parameter
Customization
Node Group
Agent Status
Troubleshooting
Quit
Maintenance
4-7
4-8
Table 4-2
Menu Item
Description
Check All
Start All
Start Database
Start
CONTROL-M/Server
Stop All
Stop Database
Stop
CONTROL-M/Server
Stops CONTROL-M/Server.
Quit
Maintenance
4-9
q - Quit
Table 4-3
Menu Item
Description
Show Database
Parameters
4-10
Table 4-3
Menu Item
Description
Delete Database
Erase Database
Contents
Maintenance
4-11
Table 4-3
Menu Item
Description
Check Database
4-12
Figure 4-4
Archive Mode
Activates Oracle archive mode. In this mode, Oracle database logs are
written to a special backup destination when they are full, and before
they are overwritten by new information.
If you specify the same device for each backup, make sure the previous
backup is copied to the appropriate media for archive purposes.
Two types of back up can be performed, depending on the archive mode:
Maintenance
4-13
If you choose to use Archive mode, it should be a choice for long term
use. If this option is activated and deactivated frequently, the archived
logs will not provide useful information for database restoration.
Note
Backup Database
Step 2
Enter the name of the backup device. 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. Use the option List Backup
Devices (seeList Backup Devices on page 4-19) to display a list of
valid devices.
The backup procedure backs up the Sybase database.
Oracle Backup
4-14
Step 1
Step 2
You have the choice between two types of Oracle database backup; Hot
or Cold.
Cold Backup
Can be used to restore the database to the state it was in when the
backup was performed.
Can be used to restore the database to the state it was in after the last
completed transaction (the last COMMIT command executed).
Maintenance
4-15
Requires that the directory you specify exist prior to starting the
backup.
Note
Enter the directory in which the archive process will store its Control
files.
The backup procedure shuts down CONTROL-M/Server before
beginning the backup, and starts it again after the backup is completed.
The procedure displays informational messages indicating its progress.
Restore Database
4-16
Press <Enter> to accept the default or enter the name of your backup
device. The backup device must be either a valid device defined in
Sybase, or the full path name of a backup file to be used as input for the
ctmdbrst utility. Use the option List Backup Devices to display a list of
valid devices. For more information on this option, seeList Backup
Devices on page 4-19.
Oracle Restore
Press <Enter> to accept the default directory, or type the name of the
directory in which the backup was saved.
3. If Archive mode is not active at your site, a restore is automatically
performed using the information from the most recent Cold backup.
If Archive mode is active, a restore is automatically performed using
the information from the most recent Hot backup.
For details about Hot and Cold backups, see Step 3 on page 4-15.
Maintenance
4-17
If you wish 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 above.
Warning
4-18
This menu option is relevant only for sites using a Sybase database
server.
This menu option is relevant only for sites using a Sybase database
server.
Adds a backup device to the list of devices available for backing up the
CONTROL-M database.
Note
This menu option is relevant only for sites using a Sybase database
server.
The following prompt is displayed:
Enter <dev_logical_name> {disk|tape} <device_name> <[size_in_MB]>
Maintenance
4-19
Table 4-4
Variable
Description
<dev_logical_name>
{disk | tape}
<device_name>
<size_in_MB>
This device can be either a disk file or a tape drive. (Backups to disk files
are faster and do not require operator intervention.)
Enter the required parameters for the new device.
Example
cont tape cont_dev
This menu option is relevant only for sites using a Sybase database
server.
Deletes a device from the list of backup devices. The following prompt is
displayed:
Enter <dev_logical_name>:
Enter the logical name of the device to delete from the list. Upon
completion of the process, the following message is displayed:
Device dropped (return status = 0)
4-20
Table 4-5 describes the menu options that can be used to extend the size
of different segments of the CONTROL-M database. These options can
be used while CONTROL-M/Server is active or when it is shut down.
See Checking Available Space in the CONTROL-M Database on page
4-4 for additional information.
Table 4-5
Option
Description
Extend Temporary
Database Size
Extend Rollback
Tablespace Size
Note
This option extends the size of the data segment only. The size of the log
segment is not extended.
To extend the size of the data segment of the CONTROL-M
database:
Maintenance
4-21
For Oracle:
Enter size of database extension in MB (default
10):
The entered value is: 10
1 - /disk2/controlm/oracle/oradata/ctrlm/rbs01.dbf
0 - New Data File
Your choice ? (0/1) [0]:
For Oracle:
4-22
SVRMGR> Connected.
SVRMGR> Statement processed.
SVRMGR> Server Manager complete.
Extend Temporary Database Size
For Oracle:
Enter size of database extension in MB (default
10):
The entered value is: 10
1 - /disk2/controlm/oracle/oradata/ctrlm/temp01.dbf
0 - New Data File
Your choice ? (0/1) [0]:
3. Supply a full path name or press <Enter> to accept the default. [0]
New Data File is the default in Oracle.
BMC Software, Inc., Confidential and Proprietary Information
Maintenance
4-23
The file specified must not exist. The local file system where the file
will be located must have enough free space to accommodate the size
specified above. Upon completion of the process, the following
message is displayed:
For Sybase:
Extension request succeeded
For Oracle:
SVRMGR> Connected.
SVRMGR> Statement processed.
SVRMGR> Server Manager complete.
Extend Database Log Size (Sybase) or
Extend Rollback Tablespace Size (Oracle)
The size of the log segment of the database should be approximately 1/3
of the data segment size.
To extend the size of the log segment of the CONTROL-M database:
1. Select option Extend Database Log Size from the Database
Maintenance menu (Sybase). In Oracle, select the Extend Rollback
Tablespace Size option from the Database Maintenance menu. The
following prompt is displayed:
Enter size of transaction log extension in MB
(default 10):
For Oracle:
BMC Software, Inc., Confidential and Proprietary Information
4-24
3. Supply a full path name or press <Enter> to accept the default. The
file specified must not exist. The local file system where the file will
be located must have enough free space to accommodate the size
specified above.
Upon completion of the process, the following message is displayed:
For Sybase:
Extension request succeeded
For Oracle:
SVRMGR> Connected.
SVRMGR> Statement processed.
SVRMGR> Server Manager complete.
Show Database Parameters
Maintenance
4-25
Check Database
4-26
Table 4-6
Option
Description
Check Mirroring
Status
Initialize
Mirroring
Maintenance
4-27
Table 4-6
Option
Description
Disable
Mirroring
Use Mirror
Database
Restore
CONTROL-M
Database from
Mirror
Initialize
Failover
Start Failover
Stop Failover
Quit
4-28
Table 4-7
Option
Description
Security
Maintenance
Utility
Backup Security
Definition
Tables
Maintenance
4-29
Table 4-7
Option
Description
Restore
Security
Definition
Tables
Quit
Note
4-30
Figure 4-7
q - Quit
All the parameters that appear in these menus are described in:
Table 4-8
Customization Parameters
Option
Description
Communication and
Operational Parameters
Parameters for
Communicating With
Specific Agent Platforms
Quit
Note
For parameter changes to take effect, you must shut down and restart
CONTROL-M/Server.
Maintenance
4-31
Communication Parameters:
1)
2)
a)
q)
n)
Operational Parameters:
1)
2)
3)
4)
5)
6)
7)
a)
p)
q)
4-32
Maintenance
4-33
4-34
Polling Interval:
Communication Timeout:
Maximum Retries:
Retry Interval:
Server-to-Agent Port Number:
Communication Protocol Version:
Use of this option does not require communication with the Agent
platforms. There is no verification that the specified Agent platform
exists at the time this option is used.
Maintenance
4-35
Communication Timeout:
Maximum Retries:
Retry Interval:
Server-to-Agent Port Number:
Communication Protocol Version:
Check Interval(Available)
4-36
Option
Description
Quit
This option is used to view, create or modify a node group. When this
option is selected, the following prompt is displayed:
Node Group Name:
Specify the name for a new node group or specify the name of an
existing node group whose member list you want to view or modify. The
following menu is displayed:
Maintenance
4-37
q -
Quit
Add Node ID
Delete Node ID
4-38
q - Quit
Enter option number --->
Option
Description
Discover Agent
Quit
The first four options in the above table do not require communication
with the Agent platforms. They do not verify that the Agent platforms
exist. As a result, the following may occur:
The Change options can be used to modify the status of a nonexistent platform.
Maintenance
4-39
Troubleshooting Menu
The Troubleshooting menu is used to perform a variety of diagnostic
activities. Selecting CONTROL-M Main Menu => Troubleshooting
displays the following:
Figure 4-14 Troubleshooting Menu
Troubleshooting Menu
----------------------------Select one of the following options:
1
2
3
4
5
12
13
14
15
16
6
7
8
9
10
11
q - Quit
Enter option number --->
Table 4-11
[]:
Option
Description
Set Diagnostics
Level
Determines the sleep time for all CONTROL-M/Server processes or for any
specific process. For details, see Set Sleep Time on page 4-45.
Show Process
Flags (prf)
4-40
Table 4-11
Option
Description
Show All
Processes (shctm)
Show
Communication
Environment
Reset
CONTROL-M
Active
Environment
Truncate Database
Log
Truncates the CONTROL-M database log. This option should be used if the
Sybase message Cant allocate space for <text> in database <name>
because the log segment is full occurs in one of the log files located in
directory ~controlm/ctm/proclog/.
Troubleshooting
Report
Check Kernel
Configuration
For Solaris platforms, checks whether the current configuration settings of the
kernel comply with requirements for CONTROL-M/Server.
If all parameters are configured correctly, the following message is displayed:
Check kernel configuration for <system>
terminated successfully
If one or more parameters are not configured correctly, the parameters are
listed followed by:
Check kernel configuration for <system>
terminated unsuccessfully
Note: This option is not relevant for AIX platforms.
List Active
Transactions
Runs the ctmdbtrans utility to list the active transactions in the database.
A transaction is a unit of work performed by CONTROL-M in the database.
Each transaction is assigned a unique name identifying that specific unit of
work.
You may be asked by technical support to run this option and to provide them
with the output for debugging purposes.
Maintenance
4-41
Table 4-11
Option
Description
Erase Proclog
Files
Erases the contents of the current process log file for all active
CONTROL-M/Server processes or for any specific active process.
The following prompt is displayed:
Enter <process-name> [SU,TR,SL,CO,NS,LG,ALL]
Specify the two-character code for a specific process or ALL for all current
process log files. See Set Diagnostics Level earlier in this table for more
information about process log files.
Show Calendar
Names
Interactive SQL
Commands
Starts an interactive SQL session that enables you to issue Sybase Database
commands to perform actions in the CONTROL-M database. To end this
session, enter the command: quit.
This option should only be used when requested by Technical Support.
Communication
Diagnostic Report
Force Download
Check directory
permissions
Checks the current directory and all sub-directories under it for permissions
and displays a report similar to the following:
Quits the Troubleshooting menu and returns to the CONTROL-M Main menu.
4-42
CONTROL-M/Server Processes
Code
Description
SU
Supervisor.
TR
Tracker.
SL
NS
CO
Communication gateway.
CD
CS
LG
WD
Watchdog process.
RT
: []:
Maintenance
4-43
Table 4-13 describes the parameters that are set when responding to these
prompts.
Table 4-13
Parameter
Description
<diagnostic-level>
<controlm_path>/ctm/proclog/<proces
s-name>_LOG.<process-ID>
For example:
~controlm/ctm/proclog/SU_LOG.5609
The variables in this pathname are:
<module_number>
<controlm_path>
Home directory of
CONTROL-M/Server account
owner.
<process_name>
<process-ID>
ID of the CONTROL-M/Server
process.
Process Name
4-44
---------------------------------1)
2)
3)
4)
5)
6)
7)
Y
Y
Y
Y
Y
Y
Y
Maintenance
4-45
8) TR (Tracker) Logs:
9) CD (New Day Procedure) Logs:
10) CO (Communication Gateway) Logs:
11) CS (Communication with ENTERPRISE/CS) Logs:
12) LG (Agent Utilities) Logs:
13) NS (Communication with Agents) Logs:
14) Database Error Log:
15) Logs of Failed Jobs within the Last 24 Hours:
16) Logs of All Jobs run within the Last 24 Hours:
R)
Q)
Y
Y
Y
Y
Y
Y
Y
Y
N
To change the information included in the report, enter the number of the
item to change and switch the flag from Y to N. Default options include
all information. Enter R to generate the report.
The generated report is compressed and placed in the CONTROL-M
users home directory.
<controlm_path >/ctmtsrpt.<mmddyyhhmm>.tar.Z
where:
<controlm_path>
<mmddyyhhmm>
When selected, the Show Process Flags option displays the status of
CONTROL-M/Server processes as recorded in the CONTROL-M
database.
A table similar to the following is displayed:
PROCNAME
CD
CO
LG
NS
RT
SL
SU
TR
WD
PROCID
21176
21199
21178
21180
21166
21182
21167
21184
21185
PROCSTAT
R
R
R
R
R
R
R
R
R
PSTAT_REQ
R
R
R
R
R
R
R
R
R
SLEEP_TIME
60
60
360
120
60
60
60
30
30
DIAG_LVL
0
0
0
0
0
0
0
0
0
4-46
PROCNAME
PROCID
PROCSTAT and
PSTAT_REQ
DIAG_LVL
5703
5620
5645
5691
5705
5609
5712
5714
5713
5610
0:02
0:00
0:00
0:00
0:00
0:01
0:01
0:01
0:01
0:01
/usr1/controlm/ctm/exe_AIX/p_ctmco
/usr1/controlm/ctm/exe_AIX/p_ctmns
/usr1/controlm/ctm/exe_AIX/p_ctmlg
/usr1/controlm/ctm/exe_AIX/p_ctmtr
/usr1/controlm/ctm/exe_AIX/p_ctmsl
/usr1/controlm/ctm/exe_AIX/p_ctmsu
/usr1/controlm/ctm/exe_AIX/p_ctmcd
/usr1/controlm/ctm/exe_AIX/p_ctmwd
/usr1/controlm/ctm/exe_AIX/p_ctmcs
/usr1/controlm/ctm/exe_AIX/p_ctmrt
Note
The operating system identifier (in the above example, AIX) in the path
of the run module varies according to the type of Unix running on the
Server platform.
Maintenance
4-47
The following additional columns are displayed for the CS process (the
last line in the list above):
4-48
Table 4-15
Process
Sleep Time
SU
60
TR
30
SL
30
NS
120
CO
60
CD
60
LG
360
WD
360
RT
60
The sleep time setting for CONTROL-M processes can affect the
functionality of CONTROL-M and the performance of your data center.
Sleep time is the length of time that a process lies dormant before
waking up to check if any request to perform an action was received.
When modifying certain CONTROL-M process sleep time settings, it is
important to consider the number of jobs that are processing, the job
schedule plan, and the overall load on the machine.
Maintenance
4-49
Table 4-16
Process
Task
Sleep Time
Initial
Settings
SU
Supervisor
60
TR
Job Tracking
15
SL
Job Selector
30/60
NS
Communication
120
No effect.
CO
Communication
60
No effect.
CD
60
No effect.
LG
Utilities
360
No effect.
WD
Watchdog
30
No effect.
RT
Inter-process
Communication Router
60
No effect.
4-50
Customization Parameters
System parameters.
Communication parameters.
Operational parameters.
Agent Communication parameters.
Database parameters.
Mirroring parameters.
Performance parameters.
Configuration parameters.
Customization Parameters
5-1
Parameter Coordination
For CONTROL-M/Server to communicate with Agent platforms and
with the ENTERPRISE/CS workstation, the values assigned to certain
parameters described in this chapter must be coordinated with values
assigned to parameters on these systems. These parameters are listed in
the following tables.
Table 5-1
CONTROL-M/Server
Parameter
ENTERPRISE/CS
Parameter
Default Value
2370
Table 5-2
CONTROL-M/Server
Parameter
CONTROL-M/Agent
Parameter
Default Value
Communication Protocol
Communication Protocol
TCP
7005
7006
Authorized
CONTROL-M/Servers
5-2
Parameter Descriptions
System Parameters
CONTROL-M system parameters are assigned default values during
installation. These parameters can be modified using the ctmsys utility,
described in Chapter 2, Utilities. CONTROL-M system parameters are
listed below. Modifiable parameters are identified by an asterisk (*). All
other parameters are display only.
Table 5-3
Parameter
Description
DBO
Password
Computer
System
Operating
System
CONTROL-M
Version
Database
Version
Sysout Log
Directory *
Executable
Path
Customization Parameters
5-3
Table 5-3
Parameter
Description
Day Time *
Example
+0600 Specifies that the hours between midnight and 6:00
a.m. are considered part of the previous dates work day
(that is, system date February 10th, 5:59 a.m. is still the
CONTROL-M work day February 9th).
-2200 Specifies that the hours between 10 p.m. and
midnight are considered part of the next dates work day
(that is, at 10:00 p.m. on system date February 10th, the
CONTROL-M date changes to February 11th).
CONTROL-M
Date
Statistics *
Maximum
Retries *
5-4
Table 5-3
Parameter
Description
Start Day of
the Week *
Day of the week on which the work week at your site starts.
Valid values: 0 (Saturday), 1 (Sunday), , 6 (Friday). This
parameter affects the usage of the job processing parameter
Weekdays (described in Chapter 5 in the Enterprise
Controlstation User Guide). Default: 2 (Monday).
Active Shout
Table *
Full
Security *
Maximum
Days
Retained by
CONTROL-M
Log *
Max.Days to
Retain
Sysout Files *
Number of days that job sysout files are retained for jobs
executed by Agent platforms. After this period, all job sysout
files are deleted by the New Day procedure. Default: 2.
Customization Parameters
5-5
Table 5-3
Parameter
Description
Ignore New
Day
Conditions *
Secure Socket
Layer
After assigning the new CONTROL-M date, the New Day procedure
performs a selective cleanup of prerequisite conditions. By default, any
prerequisite condition whose reference date (month and day) is equal to
the new CONTROL-M date is deleted. This is done to prevent jobs from
being triggered by any prerequisite conditions remaining from the
previous year.
This cleanup function of the New Day procedure can conflict with user
intentions under certain circumstances. For example, if a job processing
definition contains the parameter Out Conditions with the Date field
containing the value Next, a prerequisite condition is created with a
reference date one or more days in the future. This prerequisite condition
would normally be deleted by the New Day procedure before it can be
used to trigger the submission of a job.
BMC Software, Inc., Confidential and Proprietary Information
5-6
The Ignore New Day Conditions parameter can be modified using the
ctmsys utility.
When this parameter is set to Y, CONTROL-M searches for a file called:
<home_dir>/ctm/data/dbs_ignrcond.dat
Customization Parameters
5-7
You can create and maintain this file using any text editor available at
your site. Place one prerequisite condition prefix on each line in the file.
Note
bra_fn_01 14/01
bra_fn_01 15/01
prq_rs_21rpts 14/01
prq_rs_21rpts 15/01
pre_prn_01 14/01
pre_prn_01 15/01
pre_prn_02 14/01
pre_prn_02 15/01
srt_def_a 14/01
srt_def_a1 14/01
srt_def_a 15/01
srt_def_a1 15/01
bra_fn_01 14/01
prq_rs_21rpts 14/01
prq_rs_21rpts 15/01
pre_prn_01 14/01
pre_prn_01 15/01
pre_prn_02 14/01
pre_prn_02 15/01
srt_def_a 14/01
srt_def_a1 14/01
srt_def_a 15/01
5-8
Example 2
Communication Parameters
Communication parameters are modifiable during installation. You can
also modify these parameters afterwards using the Parameter
Customization menu, described in Chapter 4, Maintenance.
Valid Communication parameters are described in Table 5-4.
Table 5-4
Parameter
Description
Local IP Host
Interface Name
Customization Parameters
5-9
Table 5-4
Parameter
Description
Agent-to-Server
Port Number
Communication
Protocol
5-10
If one or both of these parameters contain a logical host name, you can
determine the IP address mapped to the logical host name by specifying
the following command at the Unix prompt:
arp <host_name>
The system responds with the IP address mapped to the host name on the
local machine.
Note
Even if the same logical host name is specified for these two parameters,
the host name can be mapped to different IP addresses on the Server
platform and the ENTERPRISE/CS workstation. Use the arp command
(see above) to verify that the host name on each machine is mapped to
the same IP address.
You can also ensure that both machines are using the same address by
specifying the actual IP address of the network interface card for each of
these parameters. The IP address specified must be a local address on the
Server platform.
Operational Parameters
Operational parameters are modifiable during installation. You can also
modify these parameters afterwards using the Parameter Customization
menu, described in Chapter 4, Maintenance.
The operational parameters are described below:
Customization Parameters
5-11
Table 5-5
Parameter
Description
Input Process
Communication
Port Number
Maximum Job
State Changes
ENTERPRISE/CS
TCP/IP Port
Number
ENTERPRISE/CS
Release Version
Statistics Mode
5-12
Table 5-5
Parameter
Description
Minimum Server
Processes
Maximum Server
Processes
Customization Parameters
5-13
Table 5-6
Parameter
Description
Polling Interval
Communication
Timeout
Example
If the value of Communication Timeout is 120 and
Maximum Retries is 12, CONTROL-M/Server attempts to
communicate with the Agent platform once every 10
seconds (120/12) during the timeout period.
Maximum
Retries
Retry Interval
Server-to-Agent
Port Number
Communication
Protocol
Version
5-14
Database Parameters
Sybase
Parameter
Description
CONTROL-M
Database Owner
DBO Password
Database
Administrators
Password
Database (Data
Portion) Size
Customization Parameters
5-15
Table 5-7
Parameter
Description
Query Socket
Port Number
-andBackup Socket
Port Number
Master Device
Type
Master Physical
Device/Path
Name
For Master Device Type FILE: Full path name where the
master Sybase database will be located.
Default: <controlm_home_dir>/sybase/data/master.dat
For Master Device Type RAW: Physical device name of
the raw partition on which the Sybase database will be
located.
Data Device
Type
Data Physical
Device/Path
Name
For Data Device Type FILE: Full path name where the
CONTROL-M database will be located.
Default: /<controlm_home_dir>/sybase/data/ctrlm_ux.dat
For Data Device Type RAW: Physical device name of the
raw partition in which the CONTROL-M database will be
located.
5-16
Table 5-7
Parameter
Description
Log Physical
Device/Path
Name
For Log Device Type FILE: Full path name where the
CONTROL-M database log will be located.
Default: /<controlm_home_dir>/sybase/data/ctrlm_log.d
at
For Log Device Type RAW: Physical device name of the
raw partition in which the CONTROL-M database log will
be located.
Sybase
Interface
Directory
Sybase Server
Name
Remote Sybase
Host Name
CONTROL-M
Database Name
CONTROL-M
Database Data
Device Name
CONTROL-M
Database Log
Device Name
Oracle
Customization Parameters
5-17
Table 5-8
Parameter
Description
CONTROL-M Database
Instance name
Database User
User Password
Tablespace size
Size of CONTROL-M
database log files
Name of the
Tablespace data file
CONTROL-M Listener
port number
5-18
Table 5-8
Parameter
Description
CONTROL-M SYSTEM
tablespace file
location
CONTROL-M SYSTEM
tablespace size
CONTROL-M RBS
(Rollback Segment)
tablespace file
location
CONTROL-M RBS
tablespace size
CONTROL-M TEMP
tablespace file
location
CONTROL-M TEMP
tablespace size
CONTROL-M INDEX
tablespace file
location
CONTROL-M INDEX
tablespace size
Customization Parameters
5-19
Mirroring Parameters
Parameters for database mirroring are specified when mirroring is
initialized, either during CONTROL-M/Server installation or any time
afterwards. You can modify these parameters by mirror initialization
using the Database Mirroring menu described in Chapter 4,
Maintenance.
Database mirroring parameters are described in Table 5-9.
Table 5-9
Parameter
Description
CONTROL-M Mirror
Database Owner
(Sybase and Oracle)
DBO Password
(Sybase and Oracle)
Mirror Sybase
Server Name
(Sybase)
Mirror
Sybase/Oracle Host
Name (Sybase and
Oracle)
Mirror
Sybase/Oracle Port
Number (Sybase
and Oracle)
5-20
Table 5-9
Parameter
Description
CONTROL-M Mirror
database name
(Sybase)
Mirror Oracle
Instance name (SID)
(Oracle)
CONTROL-M Mirror
tablespace name
(Oracle)
CONTROL-M Mirror
database data
device name
(Sybase)
CONTROL-M Mirror
database log device
name (Sybase)
CONTROL-M Mirror
Database Data
Device Name
(Sybase)
CONTROL-M Mirror
Database Log
Device Name
(Sybase)
Performance Parameters
Special parameters are available for tuning CONTROL-M performance.
These parameters affect how jobs are selected for both scheduling and
post-processing. Table 5-10 describes the performance parameters in the
CONTROL-M <controlm>/ctm/data/config.dat file where <controlm>
is the CONTROL-M home directory.
Customization Parameters
5-21
Table 5-10
Performance Parameters
Parameter
Description
PRIORITY_SL_SCAN
SL_BREAK_INT
PP_THRESHOLD
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.
For more information, see Sleep Time Considerations on page 4-49.
Configuration Parameters
The following tables contain the current parameters in the
CONTROL-M/Server configuration parameter file (config.dat) and
CONTROL-M/Agent configuration parameter file (agconfig.dat). The
config.dat file resides in directory <controlm>/ctm/data/ on the Server
platform. The agconfig.dat file resides on the Agent platform.
5-22
Parameter Name
ALARM_DEST
AUTOEDIT_INC_
SEC
{SYSTEM|GLOBAL|GROUP|LOCAL}
Indicates which AutoEdit variables are sent to the
Agent for each submitted job.
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.
LOCAL Only Local AutoEdit variables are sent to
the Agent.
Default: LOCAL
CTM_DB_
TIMEOUT
{300 3600}
Timeout value (in seconds) for long database
transactions. Default: 600
CTM_GROUP_
ADJUST_DUMMY
{Y|N}
When this parameter is set to Y, and 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. Default: N
Customization Parameters
5-23
Table 5-11
Parameter Name
CTM_GROUP_
RECHECK
{Y|N}
Indicates if group conditions should be checked for
each job in a Group Scheduling table after the groups
conditions have been satisfied.
N (default) group conditions are ignored when
ordering specific jobs in a group.
Y group conditions are checked for each job in the
group (in addition to conditions specified for the
job).
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
CTM_SLP_
SUSPEND
{30 1200}
During the New Day Procedure and Download of the
Active Jobs file to ENTERPRISE/CS, the ctmcreate,
ctmudly, and ctmorder utilities are suspended. They
stay suspended until the Download or New Day
Procedure is complete or until the specified timeout
period. Default: 30 minutes
CTM_SNMP_
SEND_FORMAT
{S,M}
Indicates whether Single (S) or Multiple (M) variable
format is used for SNMP traps. For more information,
see ctm2snmp on page 2-155. Default: S
CTM_WRITE_
CONSOLE
{YES, NO}
If this parameter is set, critical alerts are sent to the
console of the Server in addition to being sent as
Shout messages to ENTERPRISE/CS. Default: NO
CTMLOG_DEL_CHK
{YES, NO}
When this parameter is set to Y, the use of the ctmlog
utility for delete operation to Control-M is restricted.
Administrator only.
Default: N
CTMORDER_FORCE
{Y, N}
The default action of the utility is to order, not force,
jobs in the Active Jobs file. This action can be
modified by adding keyword Force to the command
that invokes the utility. To change the default to force,
set this parameter to Y. Default: N
5-24
Table 5-11
Parameter Name
CYCLIC_MAXWAIT
CYCLIC_RERUN
{OK, NOTOK}
If a cyclic job ends NOTOK and this parameter is set
to OK, the cyclic job will be rerun. If set to NOTOK,
the job will not be rerun. Default: OK.
IOALOG_DEL_INT
{1 24}
During the New Day procedure, old IOALOG records
are removed. The default is to delete the old records
in hourly bundles. If set to 24, all the old logs are
deleted in one bundle. Default: 1.
RUNINF_PURGE_
LIMIT
{0 65K}
Number of Run Information records to keep for a
given MemName/MemLib/NodeID. If
RUNINF_PURGE_MODE is 0, the New Day
Procedure deletes all Run Information records for
each unique name except the last n records, where n
is the value of this parameter. Default: 20.
RUNINF_PURGE_
MODE
{0, 1}
New Day Procedure algorithm for cleaning Run
Information records. If set to 1, the New Day
procedure will keep records for the last two days only.
If 0, it uses the RUNINF_PURGE_LIMIT value.
Default: 0.
STATS_TIME
STATS_TIME
SERVER or AGENT
Customization Parameters
5-25
Table 5-12
Performance Parameters
Parameter Name
PP_THRESHOLD
{1 99999}
Maximum number of jobs that can wait in the post
processing queue before the Selector process is
interrupted and post-processing is initiated. Default: 10.
PRIORITY_SL_
SCAN
{0, 1}
Indicates whether to disable (0) or enable (1) the use of
the a jobs Priority in the selection process. Disabling
priority increases performance. Default: 0.
SL_BREAK_INT
{0 99999}
The maximum number of jobs to scan in the selection
process before checking for jobs in the post processing
queue. Default: 100.
Table 5-13
Communication Parameters
Parameter Name
CMN_PRM_CD_IPC_
IN
CMN_PRM_CD_IPC_
OUT
CMN_PRM_CD_MAX
_DBU
{1000 65K}
CONTROL-M accumulates all updates to the
database before sending them to ENTERPRISE/CS.
This parameter determines the maximum number of
updates to accumulate before requesting a
Download. Default 1000.
CMN_PRM_CD_MAX
_SERVICE
{60 32K}
Sets the maximum number of requests that can be
queued by CONTROL-M/Server that originate from
ENTERPRISE/CS gateways. Default: 60.
5-26
Parameter
Name
CTM_PRM_KPA
_ACTIVE
{Y, N}
Indicates whether the Heartbeat monitor operates in active
(Y) or passive (N) mode. Default: Y (Active)
CTM_PRM_KPA
_BETWEEN
_MSGS
{n}
Time in seconds between heartbeat checks. Default: 300.
CTM_PRM_KPA
_ROUNDTRIP_
TIMEOUT
{n}
Time in seconds to wait for a confirmation from
ENTERPRISE/CS. If confirmation does not arrive, a
timeout is generated and the connection is severed.
Default: 300.
Table 5-15
Parameter Name
CTM_PRM_ENABLE_UE
{Y, N}
Indicates whether CONTROL-M user exits and
Watchdog process exits are enabled.
(See Watchdog Process Parameters
(config.dat) on page 5-31.) Default: Y
CTM_PRM_ENABLE_
UExxx (101-106)
{Y, N}
Indicates whether the associated UExxx user exit
is enabled. For more information, see User Exits
on page 1-50. The following user exits are
available:
UE101 Job Ordering User Exit
UE102 Job Submission User Exit
UE103 Before New Day Procedure User Exit
UE104 After New Day Procedure User Exit
UE105 Before User Daily User Exit
UE106 After User Daily User Exit
Default: N
Customization Parameters
5-27
Table 5-15
Parameter Name
CTM_PRM_SCRIPT_
UExxx
CTM_PRM_TIMEOUT_
UExxx
{n}
Time in seconds to wait for a user exit script to
run before it is terminated. Default: 20.
Parameter Name
COMM_TRACE
{0, 1}
Debug trace for communication. Default: 0.
COMTIMOUT
{20-360}
Communication timeout in seconds. Default: 120.
COMTRYNO
{1-20}
Communication retry value. Default: 12.
DEBUG_LEVEL
OS_PRM_HOSTNAME
PROTOCOL
{TCP, UDP}
Communication protocol. Default: TCP
Parameter Name
AG_PORT_NUM
AGENT_DIR
PRINTER_NAME
CTM_PRM_DONT_
DELETE
{YES}
At the end of job execution, temporary scripts
generated from jobs are deleted. If this value is set to
Yes, temporary scripts are not deleted.
BMC Software, Inc., Confidential and Proprietary Information
5-28
Table 5-17
Parameter Name
CTM_PRM_KSH_
FLAGS
{-v,-x}
Flags to include when running a job that is written in
Korn Shell. Default: x.
CTM_PRM_SH_
FLAGS
{-v,-x}
Flags to include when running a job that is written in
Borne Shell. Default: x.
CTM_SU_PATH
CTM_PARM_ENC
CTMS_ADDR_
MODE
{IP}
If this parameter is set to IP, the IP address is saved
in CTMS_HOSTNAME instead of the host name. Use
this parameter when CONTROL-M runs on a platform
with more than one network card.
Customization Parameters
5-29
Table 5-17
Parameter Name
CTMS_
COMVERSION
CTMS_HOSTNAME
CTMS_PORT_NUM
EXIT_STATUS_DIR
SYSOUT_NAME
{JOBNAME | MEMNAME}
If this parameter is set to JOBNAME, parameter
Jobname is used in the sysout file instead of
parameter Memname. Default: MEMNAME.
SYSOUT_MODE
TRANSLATE_$0
{Y | N}
If this parameter is set to N, $0 is not translated in a
script before it is run. Otherwise, $0 is replaced by a
file name before the script is run. Default: Y
5-30
The following parameters are used for the Watchdog Process. (For
more information, see Watchdog Facility on page 1-44.) Parameter
CTM_PRM_ENABLE_UE must be set to Y to enable the WD process.
General Parameters
Table 5-18
Parameter Name
WD_INTERVAL
{n}
Amount of time in minutes between each set of
Watchdog checks. If the checks take longer than the
specified time, the time interval is saved and the
longest interval time is included in the message sent
automatically to the error handler(s) once every 50
intervals. Default: 5.
WD_HEARTBEAT_
INTERVAL
{n}
Nth interval in the Watchdog process to check
CONTROL-M processes. If this parameter is set to 5,
the Watchdog process sends a message to each of
the primary CONTROL-M processes every 5th
interval and awaits a response. Default: 5
WD_HEARTBEAT_
TIMEOUT
{n}
Maximum time (in seconds) to wait for a response
from each of the CONTROL-M processes, after
issuing a Heartbeat check, before sending a message
to the error handlers. Default: 360.
WD_CTMEXIT_
NUMBER
{n}
Total number of CONTROL-M system exits to run.
Default: 2.
WD_USEREXIT_
NUMBER
{n}
Total number of user exits to run. Default: 0.
WD_ALIVE_MSG
Customization Parameters
5-31
Table 5-18
Parameter Name
WD_CTO_
HOSTNAME
WD_CTO_TIMEOUT
{1-10}
Maximum time (in second) to send messages to
CONTROL-O/Server before terminating the
communication. Default: 10 seconds.
WD_ERROR_
HANDLER_
SCRIPT_FILE
WD_ERROR_
HANDLER_
TIMEOUT
{n}
Maximum time in seconds to wait for the error handler
script to run before terminating the script. Default: 5.
Parameter Name
WD_CTMEXIT_#_CMD_LINE
WD_CTMEXIT_#_ERROR_MSG
5-32
Table 5-19
Parameter Name
WD_CTMEXIT_#_INTERVAL
WD_CTMEXIT_#_RUN_STATE
{Y, N}
Specify whether (Y) or not (N) to run the
utility in Run (that is, normal) mode. A Y
must be specified for either this parameter
or for parameter
WD_CTMEXIT_#_SUSPEND _STATE for
the utility to be run. Default: N.
WD_CTMEXIT_#_SCRIPT_FILE
WD_CTMEXIT_#_SUSPEND
_STATE
{Y, N}
Specify whether (Y) or not (N) to run the
utility in Suspend mode (that is, during New
Day procedure or download, when the
database inaccessible). A Y must be
specified for either this parameter or for
parameter WD_CTMEXIT_#_RUN _STATE
for the utility to be run. Default: N.
WD_CTMEXIT_#_TIMEOUT
{n}
Maximum time (in seconds) that the utility
is allowed to run. If the utility runs longer
than the time indicated, it will terminate
and an error message will be sent.
Mandatory. Default: 5 seconds.
Customization Parameters
5-33
Table 5-20
Parameter Name
WD_USEREXIT_#_CMD_LINE
WD_USEREXIT_#_ERROR_
MSG
WD_USEREXIT_#_INTERVAL
WD_USEREXIT_#_RUN_
STATE
{Y, N}
Specify whether (Y) or not (N) to run the
script in Run (that is, normal) mode. This
parameter or WD_CTMEXIT_#_SUSPEND
_STATE must be set to Y for the script to be
run. Default: N.
WD_USEREXIT_#_SCRIPT_
FILE
WD_USEREXIT_#_SUSPEND_
STATE
{Y, N}
Specify whether (Y) or not (N) to run the
script in Suspend mode (that is, during New
Day procedure or download, when the
database inaccessible). This parameter or
WD_CTMEXIT_#_RUN _STATE must be set
to Y for the script to be run. Default: N.
WD_USEREXIT_#_TIMEOUT
{n}
Maximum time in seconds that the script is
allowed to run. If the script runs longer than
the time indicated, it will terminate and an
error message will be sent. Mandatory.
Default: 5.
5-34
User Exits
User Exits
6-1
Table 6-1
User Exit
Description
CTMUE101
CTMUE102
CTMUE103
CTMUE104
CTMUE105
CTMUE106
Note
A special category of user exits can be defined for the Watchdog facility.
For more information, see Watchdog Facility on page 1-44.
6-2
Parameter Name
Valid
Values
CTM_PRM_ENABLE_UE
{Y, N}
CTM_PRM_ENABLE_UExxx
{Y, N}
CTM_PRM_SCRIPT_UExxx
string
CTM_PRM_TIMEOUT_UExxx
{n}
Description
User Exits
6-3
User exits are implemented only if they have been enabled by setting the
appropriate configuration parameters (described in Table 6-2, Exit
Configuration Parameters, on page 6-3).
1. A flat text file is produced containing parameters to be processed by
CONTROL-M.
2. The name of the text file is passed as the $1 parameter to the user
exit script in the ue_exit directory.
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).
4. CONTROL-M continues processing using the modified text file.
6-4
User Exits
6-5
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
6-6
User Exits
6-7
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
6-8
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
User Exits
6-9
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
6-10
User Exits
6-11
6-12
Failover Planning
You can implement either one of the following levels of failover
capability:
7-1
Mirror Database
Database Mirroring
You can rebuild the CONTROL-M primary database from the mirror
database.
Database mirroring can be initialized any time after CONTROLM/Server has been installed.
7-2
Menu Option
Description
Check
Mirroring
Status
Initialize
Mirroring
Disable
Mirroring
7-3
Table 7-1
Use Mirror
Database
Restore
CONTROL-M
Database from
Mirror
To prepare the mirror database, verify the requirements listed here, and
perform the specified configuration steps.
Note
Database and account names that you create must conform to Sybase
naming conventions.
1. Verify that the Sybase SQL Server used for mirroring will be
running, both when initializing mirroring, and whenever
CONTROL-M/Server is operational.
2. When building a database from scratch, you will need the password
of the Sybase system administrator for installation.
3. Determine the following parameter values:
Sybase Host Name - Host name of the machine that runs the
Sybase SQL Server to be used for mirroring.
7-4
If you change the value of any of these parameters, the change will
not be implemented until you shut down and restart Sybase SQL
Server. For more information about Sybase parameters see
descriptions of dsedit, sp_configure, and reconfigure in the Sybase
Commands Reference Manual.
4. The following details are needed to construct the database:
Unix system paths or raw partitions for the temp and log
datafiles. These paths must be unique.
Sybase device names for the temp and log databases. These
names must be unique for the database server. Use the
sp_helpdevice command to view existing devices on the
database server.
If you will be building a database, you must supply values for the
database owner, database name, devices and file/partition paths:
7-5
7-6
To prepare the mirror database, verify the requirements listed here, and
perform the specified configuration steps.
Note
Database and account names that you create must conform to Oracle
naming conventions.
1. Verify that the Oracle SQL Server and the listener for the mirror
database will be running, both when initializing mirroring, and
whenever CONTROL-M/Server is operational.
2. When building a database from scratch, you will need the password
of the Oracle system administrator for installation.
3. Determine the following parameter values:
Oracle Host Name - Host name of the machine that runs the
Oracle SQL Server to be used for mirroring.
Oracle Port Number - TCP/IP query port number for the Oracle
SQL Server used for mirroring.
4. The tablespace name and database owner name must each be unique
for a particular Oracle SQL Server. However, the tablespace name
and the DBO name can be identical to each other. Therefore, when
selecting names for the CONTROL-M mirror database, verify that
the tablespace name and owner name are each unique for the
particular Oracle SQL Server.
7-7
If you will be building a database, you must supply values for the
database owner and tablespace name:
7-8
Failover Server
7-9
A failover server can be implemented any time after CONTROLM/Server has been installed.
The secondary CONTROL-M/Server installation should be built on a
separate computer and database server, independent of the platforms
server that host the primary CONTROL-M/Server and its database.
Requirements and preparatory steps for the failover server are described
in Preparing a Failover Server on page 7-12.
Several administrative functions are used to initialize, enable, and restore
database mirroring. They are described in . These functions are accessed
from the Database Mirroring menu of the CONTROL-M/Server Main
Menu (see The Database Mirroring Menu on page 7-13).
For a description of server failover, recovery, and restoration procedures,
see Recovering from Primary CONTROL-M/Server Failure (Server
Failover) on page 7-33.
7-10
Table 7-2
Menu Option
Description
Initialize Failover
Start Failover
Stop Failover
Disable Failover
7-11
7-12
Step 2
Step 3
7-13
Step 4
[]:
The options of the Database Mirroring menu are divided into procedures
implemented on the primary CONTROL-M/Server, and procedures
implemented on the secondary, failover CONTROL-M/Server. Table 7-3
summarizes the Database mirroring options.
Note
Table 7-3
Option
Description
Check Mirroring
Status
7-14
Table 7-3
Initialize Mirroring
Disable Mirroring
Use Mirror
Database
Restore
CONTROL-M
Database from
Mirror
Option
Description
Initialize Failover
Start Failover
Stop Failover
Disable Failover
7-15
This section describes the procedures for initializing the mirror database
and failover server.
7-16
Step 2
Verify that:
Step 3
Step 4
Step 5
If you are initializing database mirroring for the first time, you must
select the build option to create the mirror database. You cannot use the
copy option until the mirror database has been built.
Step 6
7-17
Mirroring Parameters:
1)
2)
3)
4)
5)
a|A)
b|B)
q|Q)
ctmfox
######
80 MB
/home/ctm600us/sybase
jordan
4100
FoxDb
Mirroring Parameters:
1)
2)
3)
4)
5)
6)
7)
8)
9)
a|A)
b|B)
q|Q)
Step 7
7-18
Option
Description
a
or a
specific
number
Verify that the Mirroring Parameters match the port, host, and database
values of the target mirror database server. Modify the values as
necessary. Table 7-4 describes the parameters. Parameter values must
conform to Sybase naming conventions.
If mirroring has already been implemented, the parameter values shown
generally reflect the settings of the existing mirror database server.
However, some parameters may have been changed since the last
database initialization.
Continue with Step 10 on page 7-23.
Table 7-4
Parameter
Description
CONTROL-M
Mirror Database
Owner
DBO Password
7-19
Table 7-4
Parameter
Description
Mirror Database
(Data Portion)
Size
Sybase
Interface
Directory
Mirror Sybase
Host Name
Mirror Sybase
Port Number
Mirror Sybase
Server Name
CONTROL-M
Mirror Database
Name
CONTROL-M
Mirror Database
Data Device
Name
CONTROL-M
Mirror Database
Log Device
Name
Data Physical
Device Path
Name
Log Physical
Device Path
Name
7-20
Step 8
Mirroring Parameters:
1)
2)
3)
4)
5)
Mirroring Parameters:
1)
2)
3)
4)
5)
6)
Step 9
7-21
Option
Description
a
or a
specific
number
Verify that the Mirroring Parameters match the port, host, and database
values of the target mirror database server. Modify the values as
necessary. Parameters are described in Table 7-5. Parameter values must
conform to Oracle naming conventions.
If mirroring has already been implemented, the parameter values shown
generally reflect the settings of the existing mirror database server.
However, some parameters may have been changed since the last
database initialization.
Table 7-5
Parameter
Description
CONTROL-M Mirror
Database Owner
Database Owner
Password
7-22
Table 7-5
Parameter
Description
Tablespace name
Step 11
When you are satisfied with the values of all the parameters, specify b
and press <Enter>.
7-23
Note the system parameters that need to be changed, then press <Enter>
to complete the copy/rebuild procedure. You will need to manually
change these system settings after the copy/build procedure.
The initialization process continues with Step 13.
For Oracle Database Servers:
If the database you wish to build does not exist on the secondary
database server, the following message is displayed:
ATTENTION !!!
The data tablespace file location is on the Server Host Machine
Enter the data tablespace file name with full
path:/home/ctm600uo/oracle/oradata/hurr224uo.dbf
Enter the full path and name of the tablespace file, or press <Enter> to
accept the default path and file . The filename must conform to Oracle
naming conventions.
The following messages are displayed:
Creating CONTROL-M/Server database schema...
copying database contents.......
7-24
7-25
Step 13
Exit the current session and start a new login session, or specify the
command source ~/.cshrc to reset user environment variables in the
current window.
Step 15
Restart CONTROL-M/Server.
7-26
Step 2
Step 3
Step 4
Verify that:
Step 5
Step 6
7-27
Step 7
7-28
7-29
Step 2
Step 3
Exit the current session and start a new login session, or specify the
command source ~/.cshrc to reset user environment variables in the
current window.
Step 5
7-30
Step 2
Step 3
Exit the current session and start a new login session, or specify the
command source ~/.cshrc to reset user environment variables in the
current window.
7-31
Step 7
7-32
These procedures assume that a failover server has already been installed
and initialized on a secondary platform. Two procedures are used during
failover situations:
Verify that:
Step 2
Step 3
Step 4
7-33
Step 7
Step 8
Step 2
7-34
the Database Mirroring menu, type 8 to select Stop Failover and press
<Enter>.
Step 3
Step 6
Step 7
7-35
ctm_menu Option
Database
Utility
Action
Build Database
All
make_db
Initialize Mirroring
Delete Database
All
Erase Database
All
ctm_clean_db
Initialize Mirroring
Restore Database
All
ctmdbrst
Initialize Mirroring
Sybase
addumpdev
No action necessary
Sybase
deldumpdev
No action necessary
All
ctm_db_extend
Initialize mirroring
Extend Temporary
Database Size
Sybase
ctm_tempdb_extend
Extend Temp
Tablespace Size
Oracle
ctm_tempdb_extend
Extend Rollback
Tablespace Size
Oracle
ctm_rollback_extend
Sybase
ctm_logdb_extend
Sybase
ctm_cleanlog
Initialize Mirroring
Troubleshooting Menu
Truncate Database Log
7-36
Table 7-6
ctm_menu Option
Database
Utility
Action
All
reset_gd
Initialize Mirroring.
All
clean_ajf
7-37
7-38
Message Prefixes
Code
Server Process
SU
Supervisor
TR
Tracker
SL
NS
CO
Communication gateway
CD
CS
LG
WD
Watchdog process
CTM
Enterprise Controlstation
Example
TR5103 COMSTAT=OK. STATUS CHANGED TO OK
A-1
Messages
5000
5001
5002
5003
5004
System Action:
A-2
5006
5007
5008
5009
User Response: If the job should continue executing as a cyclic job modify the
job processing parameter Cyclic accordingly.
A-3
5010
5020
5030
5040
A-4
5041
5042
User Response: If the New Day procedure has already run today, no user
action is required. If the last running date of the New Day procedure is later than
todays date, run the ctmudlst utility and modify the last running date.
5043
5044
A-5
5045
5046
5047
5060
5061
A-6
5062
5063
System Action:
User Response: If the User Daily job has already been run today, no user
action is required. If the last running date of the User Daily job is later than
todays date, run the ctmudlst utility (see Chapter 2, Utilities) to modify the
last running date according to your requirements.
5065
A-7
5070
User Response: Define a home directory for the job owner; then rerun the job.
A-8
5080
Mem Lib <mem_lib> does not exist the path/library was not found.
Mem Name <mem_name> does not exist the script was not found.
User <userr_name> does not exist there was a security violation.
Owner <owner_name> does not exist there was a security violation
Owner <owner_name> is not allowed to execute this script there was
a security violation
The script <script_name> does not have execute permissions there
was a security violation
System Action:
A-9
5100
5101
STARTED ON <node_ID>
Explanation:
This information message indicates that the job began
executing on the specified Agent platform.
5102
User Response: Either rerun the job, or force the job if the job processing
definition has changed since the last New Day procedure or User Daily job.
5103
SYSOUT LOST
The jobs sysout file cannot be located.
DISAPPEARED
The job that was executing cannot be located by CONTROL-M.
COMSTAT=OK
The jobs completion code indicated that the job ended OK.
COMSTAT=NOTOK
The jobs completion code indicated that the job ended not OK.
A-10
5104
DUMMY
The job submitted is one of dummy format
NOT SUBMIT
Job Submission failed. This might have resulted from a Server/Agent
communication problem.
5105
5106
User Response: Rerun the job or force the job on a different Agent platform.
5110
User Response: Determine why the file was not found. Create the file or
correct the pathname specified for the AutoEdit variable.
A-11
5120
5121
5122
5123
5124
A-12
5125
The sysout file is not opened, the job is not analyzed, and the
User Response: Check if the file is missing, and rerun the job if applicable. If
other information in the system indicates that the job has run successfully (for
example, other output data, new files), use available maintenance utilities to
adjust condition values to the state in which they would be if the job had been
analyzed.
5126
A-13
5128
User Response: Try to correct the print queue problem. If you cannot, notify
your ENTERPRISE/CS administrator.
5129
User Response: Check if the file actually exists. If it does, check the job
owners authorization (both system and CONTROL-M authorization). If
necessary, contact your ENTERPRISE/CS administrator.
5132
5133
ENDED OK
Explanation:
This information message indicates that the job has terminated
with status OK. Following job execution and post-processing, CONTROL-M
has analyzed the results and has assigned the completion status OK to the job.
A-14
5134
ENDED NOTOK
Explanation:
The job has terminated with a final status of NOTOK.
Following job execution and post-processing, CONTROL-M has analyzed the
results, and assigned a final status of NOTOK to the job, indicating that a
problem occurred during job processing.
User Response: Examine the job log (SYSOUT) to determine why the job
terminated with a status of NOTOK.
5135
5160
User Response: Determine what happened to the sysout. Once the cause of the
problem has been corrected, resubmit the job.
A-15
5161
5163
5164
5165
A-16
5201
5202
5204
5205
5206
A-17
5207
5208
5209
5210
5211
5212
A-18
5213
5214
5215
5216
<shout_text>
Explanation:
The Shout message <shout_text> was issued to the
CONTROL-M log. The text in this message is issued by a Shout statement and
is written to the CONTROL-M log.
5217
No action is taken.
User Response: Determine the source of the problem (missing job processing
definition, missing Scheduling table, incorrectly specified Do Forcejob
statement, and so forth). Correct the problem and re-execute the Force.
A-19
5218
No action is taken.
5221
A-20
5222
A-21
5223
5224
A-22
5250
User Response: Either modify the script file protection accordingly, or grant
the owner execution privileges.
5252
5260 5330
5351
A-23
5352
5353
5354
5355
5356
5357
A-24
5401
5402
5403
5404
5405
5406
5407
5500 5599
A-25
A-26
Field
Description
Characters
Logtime
Message time
Logdate
Message date
Subsystem
Jobname
10
Jobno.
4 (integers)
Orderno
4 (integers)
Owner
30
Odate
Msgid
Message
Text of message
66
Tasktype
Memname
Member name
30
B-1
B-2
Glossary
Glossary
Active Jobs File (AJF)
The Active Jobs file lists all jobs scheduled for submission in the
current day. Each job in the Active Jobs file is not submitted
until all conditions contained in the job processing definition for
the job are satisfied. The Active Jobs file is contained in the
CONTROL-M database.
Agent Platform
Calendar
CONTROL-M
CONTROL-M (Primary)
Database
CONTROL-M Date
Glossary
CONTROL-M Log
CONTROL-M Platform
CONTROL-M/Agent
CONTROL-M/Server
Conditions/Resources
Table
Control Resource
Enterprise
Controlstation or
ENTERPRISE/CS
Force
Gateway
General Daily
Procedure
Global Condition
Heartbeat Monitor
Job Processing
Definition
Load Balancing
Glossary
Manual Conditions
File
Mirror Database
Node Group
Node ID
Odate (Original
Scheduling Date)
Order
Prerequisite
Conditions or
Conditions
Quantitative Resource
Scheduling Table
Server Platform
Sleep Time
Glossary
User Exits
Watchdog Process
Index
Index
A
account parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-58
ACTION parameter
ctmudchk utility 2-145
ctmvar utility 2-151
Active Jobs file
ad hoc jobs 2-25
ctmpsm utility 2-107, 2-109
downloading 4-42, 4-48
erasing contents 4-48
forcing download 4-42
listing job details 2-107
New Day procedure 1-13
options 2-108
security 3-5, 3-24
Active shout table
system parameter 5-5
ad hoc jobs
creating 2-25
Add Backup Device option
Database Maintenance menu 4-19
adding
backup devices 4-19
groups 3-18
prerequisite conditions 2-21
users 3-13
AG_PORT_NUM
agent parameter 5-28
agconfig.dat file
description 5-22
Agent communication parameters
defaults 4-34
description 5-13
modifying 4-35
Agent platform
deleting 2-15
status 2-15
Agent platforms
communication parameters 5-13
communication status 1-6, 2-103, 4-38,
A-11
configuration information 2-103
ctmping utility 2-103
definition 1-2
disabled A-22
identification 1-6
Shout messages to 2-138
Agent Status menu
description 4-38
AGENT_DIR
agent parameter 5-28
Agent-to-Server
port number 5-10
Index
ALARM_DEST
server parameter 5-23
application security 3-1
appname parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-60
Archive Mode option
Database Maintenance menu 4-13
archive_info parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-58
archive_object parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-58
archive_sapobject parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-58
arp command
IP address locator 5-11
asap parameter
SAP jobs (ctmcreate) 2-33
SAP jobs (ctmdefine) 2-58
ASCII files
ctm_restore_bcp utility 2-19
ctmexdef utility 2-64
authorization. See security
Authorization menu, Security 4-29
Authorized CONTROL-M/Servers file
host names 1-12
overview 1-9, 1-12
usage A-9
AutoEdit variables
ctmstvar utility 2-133
ctmvar utility 2-150
quote marks 2-29, 2-52, 2-76, 2-133
AUTOEDIT_INC_ SEC parameter 5-23
Available status
agent platform 1-7
B
backing up
CONTROL-M database 2-37
backup
Oracle 4-14
Sybase 4-14
Backup Database
option
Database Maintenance menu 4-14
Backup Socket port number
Sybase 5-16
batch mode
Security Maintenance utility 3-32
binary files
ctmdbrst utility 2-17, 2-19
C
CDROM name
Oracle parameter 5-18
character set
Sybase SQL server 7-6
Check Database option
Database Maintenance menu 4-26
Check Kernel Configuration parameter 4-41
checking
free disk space 2-62
User Daily jobs 2-145
waiting jobs 2-154
CHILD mode
ctmpsm utility 2-113
cleanup. See maintenance
closing. See stopping
CMN_PRM_CD_IPC_IN
communication parameter 5-26
CMN_PRM_CD_IPC_OUT
communication parameter 5-26
CMN_PRM_CD_MAX_DBU
communication parameter 5-26
CMN_PRM_CD_MAX_SERVICE
communication parameter 5-26
Cold backup
archive mode 4-13
COMM_TRACE
agent parameter 5-28
server parameter 5-28
communication
see also interaction
agent parameters 4-34
agent platforms 5-13
Available status 1-7
ctmping utility 2-103
defaults for parameters 4-34
Diagnostic report 4-42
Disabled status 1-7
interruptions 1-8
parameter defaults 4-34
parameter descriptions 5-9
parameter modification 4-32, 4-35
status 1-6, 2-103, 4-38, A-11
Timeout parameter 5-14
Unavailable status 1-7
Communication protocol parameter
description 5-10
version 5-14
Computer system
system parameter 5-3
COMTIMOUT
agent parameter 5-28
COMTRYNO
server parameter 5-28
Condition Date parameter
ctmcontb utility 2-21
Condition Name parameter
ctmcontb utility 2-21
conditions. See prerequisite conditions
Conditions file, Manual 2-82
config.dat file
Event logger configuration 1-40
parameters 5-21
user exit parameters 6-3
watchdog parameters 5-31
configuration
CONTROL-M/Agent 1-12
Configuration parameter, Check Kernel 4-41
configuration parameters
agconfig.dat file 5-22, 5-28
description 5-22
Watchdog parameters 5-31
Control resources
deleting 4-48
listing 2-157
reserved A-17
CONTROL-M
administrator 1-36
Authorized Servers file 1-9
failover planning 1-10
log B-1
main menu 4-6
maintenance 4-3
menu system 4-6
sample job flow 1-2
security facility 3-1, 3-7
Index
CONTROL-M database
backing up 2-37, 4-14
checking data usage 2-45
checking integrity 2-39, 4-4
creation menu 4-10
defining jobs 2-47
extending 4-21
maintenance 4-4
Oracle parameters 5-18, 7-23
overview 1-4
owner parameter (Sybase) 5-15, 7-19
parameters 4-25, 5-15, 5-17
percent utilization 2-39
recovery procedure 7-29
restoring 2-44, 4-16
statistics 2-77, 2-124
Sybase parameter 5-17, 7-20
CONTROL-M date
Day Time parameter 5-4
description 1-13
Odate 1-13
CONTROL-M log
cleanup by New Day procedure 1-14
deleting entries 2-91
description 1-31
fields B-1
listing entries 2-91
messages A-1
recorded times 1-8
Shout destination 1-27
Shout utility 2-138
CONTROL-M Mirror database parameters
5-21
CONTROL-M SYSTEM tablespace
parameters 5-19
CONTROL-M version
system parameter 5-3
CONTROL-M/Agent
see also Agent platforms
configuration 1-12
description 1-2
discovery 1-6
interrupted communication 1-8
CONTROL-M/Server
see also Server
agent interaction 1-5
backup server 7-33
host name 1-12, 5-9, 5-28
messages and codes A-1
parameters 5-1
processes 2-134, 4-43
recovery 1-11
Shout messages 2-138
starting 4-2, 4-8
stopping 4-2, 4-8
TCP/IP port number 5-12
Windows NT 1-9
creating
see also ctmcreate, defining
ad hoc jobs 2-25
application-specific jobs 2-31
CONTROL-M database 4-10
files 2-66
Manual Conditions file 2-82
csh command
environment variables 2-10
path modification 2-13
CTLTABCOUNT
messages and codes A-6
CTM_AGSTAT utility
Agent status 2-15
description 2-15
ctm_backup_bcp utility
comparison with ctmdbbck 2-17
exporting database data 2-17
CTM_CB_TIMEOUT
server parameter 5-23
CTM_GROUP_ADJUST_DUMMY
server parameter 5-23
CTM_GROUP_RECHECK
server parameter 5-24
ctm_menu command 4-6
CTM_PARM_ENC
agent parameter 5-29
CTM_PRM_DONT_DELETE
agent parameter 5-28
CTM_PRM_ENABLE_UExxx
user exit parameter 5-27, 6-3
CTM_PRM_KPA_ACTIVE
communication parameter 5-27
Heartbeat monitor 1-38
CTM_PRM_KPA_BETWEEN_MSGS
Heartbeat monitor 1-38
CTM_PRM_KPA_ROUNDTRIP_...
communication parameter 5-27
Heartbeat monitor 1-38
CTM_PRM_KSH_FLAGS
agent parameter 5-29
CTM_PRM_SCRIPT_UExxx
user exit parameter 5-28, 6-3
CTM_PRM_SH_FLAGS
agent parameter 5-29
CTM_PRM_TIMEOUT_UExxx
user exit parameter 5-28
wait interval 6-3
ctm_restore_bcp utility
ASCII files 2-19
comparison with ctmdbrst 2-19
importing database data 2-19
CTM_SLP_SUSPEND
server parameter 5-24
CTM_SNMP_SEND_FORMAT
server parameter 5-24
CTM_SU_PATH
agent parameter 5-29
CTM_WRITE_CONSOLE
server parameter 5-24
ctm2snmp utility
message distribution 2-155
ctmcontb utility
prerequisite conditions 2-21
ctmcreate utility
ad hoc jobs 2-25
application-specific jobs 2-31
Oracle Applications parameters table
2-34
SAP parameters table 2-33
ctmdbapasswd utlity
database password maintenance 2-36
ctmdbbck utility
database backup 2-37
ctmdbcheck utility
database status 2-39
problem detection 1-39
vs ctmdbused command 2-39
ctmdbrst utility
comparison with ctm_restore_bcp 2-19
database size 2-17
database, restoring the 2-44
ctmdbspace utility
space verification 1-46, 2-45
ctmdbtrans utility
problem detection 1-39
ctmdbused command
database utilization 2-39
ctmdefine utility 2-47
application-specific jobs 2-57
Oracle Applications parameters table
2-59
SAP parameters table 2-58
ctmdiskspace utility
disk space check 1-45, 2-62
ctmexdef utility
export job definitions 2-64
ctmfw utility 2-66
ctmjsa utility 2-77
job statistics 1-30
ctmkilljob utility
job termination 2-81
Index
ctmldnrs utility
Manual Conditions file 2-82
ctmloadset utility
load balancing 1-10
resource usage 2-86
ctmlog utility
CONTROL-M log 2-91
problem detection 1-39
CTMLOG_DEL_CHK
configuration parameter 5-24
ctmordck utility
job processing definition list 2-94
ctmorder utility
description 2-96
forcing a job 2-98
CTMORDER_FORCE
server parameter 5-24
ctmpasswd utility
database passwords 2-102
ctmping utility
Agent configuration information 2-103
communication status 1-7
Watchdog facility 1-48
ctmpsm utility
Active Jobs file 2-107
job listing 2-113
mode descriptions 2-113
Production Support menu 2-106
Resource Table options 2-110
scheduling function options 2-110
Scheduling tables 2-111
syntax 2-113
ctmrpln utility
description 2-120
ctmruninf utility 1-30
Statistical Details table 2-124
CTMS_ADDR_MODE
agent parameter 5-29
CTMS_COMVERSION
agent parameter 5-30
CTMS_HOSTNAME
agent parameter 5-30
CTMS_PORT_NUM
agent parameter 5-30
ctmsec utility 3-11
see also Security Maintenance utility
User Maintenance option 3-13
ctmshout utility
message distribution 2-127
ctmshtb utility 1-26
Shout destination table 2-129
ctmstats utility 1-30
statistical summary table 2-130
ctmstvar utility
AutoEdit variables 2-133
ctmsuspend utility
ENTERPRISE/CS communication
2-134
ctmsys utility
parameter modification 5-7
system parameters 2-135
ctmudchk utility
ordering jobs 2-145
User Daily job check 2-145
ctmudlst utility
Date Control record 1-21
description 2-147
messages and codes A-5, A-7
ctmudly utility
User Daily jobs 1-18, 2-149
CTMUE101 user exit
job ordering 6-5
CTMUE102 user exit
job submission 6-7
CTMUE103 user exit
New Day procedure 6-9
CTMUE104 user exit
New Day procedure 6-10
CTMUE105 user exit
User Daily jobs 6-11
BMC Software, Inc., Confidential and Proprietary Information
D
DAILY parameter
ctmudchk utility 2-145
Daily report
ctmrpln utility 2-120
data
CONTROL-M database 1-4
data center
description 1-2
data device name
Sybase parameter 5-17, 7-20
data device type
Sybase parameter 5-16
data device, physical
Sybase parameter 5-16, 7-20
database
backup 2-17
CONTROL-M 1-4
log files 5-18
mirroring A-4
parameters 5-15, 5-17
password maintenance 2-36
recovery procedure 7-29
restoration 2-17
server 4-9
size 2-17, 5-15, 7-20
Index
DEBUG_LEVEL
agent parameter 5-28
server parameter 5-28
defining
see also creating, ctmdefine
application-specific jobs 2-57
CONTROL-M jobs 2-47
deleting
backup devices 4-20
CONTROL-M log entries 2-91
files 2-66
groups 3-18
prerequisite conditions 1-14, 2-21, 4-48,
5-6
statistics 1-14, 2-124
users 3-13
dependencies. See prerequisite conditions
description parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-60
diagnostic level
setting 4-49
Disabled status
communication 1-7
Disappeared status
agent platform 1-7
messages and codes A-10, A-16
discovery process 1-6, 2-103
disk space
see also df command
downloading
Active Jobs file 4-42, 4-48
Drop Backup Device option
Database Maintenance menu 4-20
F
failover
levels 7-1
overview 1-10
server platform 1-11
FILE parameter
ctmudchk utility 2-145
File Watcher utility 2-66
file, Manual Conditions 2-82
filename parameter
ctmvar utility 2-152
first database log file
Oracle parameter 5-18
forcing a job
authorization 3-5
ctmorder utility 2-98
failure A-18, A-19
forcing a table
failure A-20
forcing download
Active Jobs file 4-42
Full Security parameter
description 5-5
usage 3-2
GROUP
value for AUTOEDIT_INC_SEC 5-23
group scheduling
Autoedit variables 2-150
New Day procedure 1-17
groups
see also node ID
assigning users to 3-11
H
Heartbeat monitor
active mode 1-37
description 1-37
parameters 1-38
passive mode 1-37
home directory
messages and codes A-8
host name
agent platforms 1-6
CONTROL-M/Agent 1-12
host parameter
SAP jobs (ctmcreate) 2-33
SAP jobs (ctmdefine) 2-58
Hot backup
archive mode 4-13
G
GCSERV user
global condition security 3-8
General Daily. See New Day procedure
general threshold %
ctmdbcheck utility 2-43
GLOBAL
value for AUTOEDIT_INC_SEC 5-23
global conditions
security considerations 3-8
global variables
batch utility (ctmvar) 2-150
I
identification
agent platforms 1-6
Ignore Conditions file
description 5-7
mask characters 5-7
Ignore New Day Conditions parameter
description 5-6
usage 1-14
IMPORT_CAL mode
ctmpsm utility 2-113
Index
In conditions
see prerequisite conditions
Index tablespace file
Oracle parameter 5-19
init_prflag 4-48
Input process communication port number
operational parameter 5-12
install_mirror script 7-17
interaction
see also communication
Server-Agent 1-5
ioa_appl parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-59
IOALOG events
problem detection 1-40
IOALOG_DEL_INT
server parameter 5-25
IP address
arp command 5-11
communication parameter 5-9
Jobno field
CONTROL-M log B-1
jobs
CTMUE101 user exit 6-5
CTMUE102 user exit 6-7
Disappeared status 1-7
order options 1-24
ordering 6-5
ordering by New Day procedure 1-14
ordering manually 1-23
retroactive ordering 1-22
sample flow 1-2
scheduling 1-15
submitting 6-7
terminating 2-81
User Daily 1-18
jobs ordering
manually 2-96
jobs submission
failure A-16
J
job status
Disappeared A-11
messages and codes A-10
job submission
error messages A-9
job_in_file parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-58
job_mode parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-58
jobcount parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-59
Jobname field
CONTROL-M log B-1
L
language parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-59
Last Run date
Date Control record 1-21
level, Restricted security 3-2
LIBMEMSYM file
AutoEdit variable A-11
List All Devices option
Database Maintenance menu 4-19
BMC Software, Inc., Confidential and Proprietary Information
10
M
maintainence
CONTROL-M menu 4-6
maintaining
CONTROL-M database 2-17, 4-4
database passwords 2-36, 2-102
New Day procedure 1-14
security 3-11, 4-29
Sybase SQL server 4-4
system parameters 2-135
Manual Conditions file 2-82
mask characters
Ignore Conditions file 5-7
Master Device Type
Sybase parameter 5-16
Master physical device
Sybase parameter 5-16
Index
11
N
Network Management applications
ctm2snmp utility 2-155
New Day procedure
Active Jobs file 1-13
CTMUE103 user exit 6-9
CTMUE104 user exit 6-10
Daylight Savings Time 1-35
description 1-13
group scheduling 1-17
ordering jobs 1-14
prerequisite conditions cleanup 5-6
purging log files 1-32
restarting 4-41
scheduling 1-15
sysout files cleanup 1-14
UDLAST parameter 1-14
BMC Software, Inc., Confidential and Proprietary Information
12
Node group
load balancing 1-9
menu 4-36
modifying 4-36
usage 1-9
Node ID
agent platforms 1-6
O
Odate
CONTROL-M log B-1
ctmcontb utility 2-21, 2-22
ctmcreate utility 2-28
ctmdefine utility 2-51
ctmorder utility 2-98
ctmpsm utility 2-110
Date Control record 1-21
Date parameter 5-4
description 1-13
New Day procedure 1-13
working date 1-21
ON_GROUP_END OK actions
New Day procedure 1-17
operating system
system parameter 5-3
operational parameters
description 5-11
modifying 4-32
Oracle
backing up 4-14
database logs 4-13
Oracle Applications
job parameters (ctmcreate) 2-34
Oracle SQL server
home directory 5-18
host parameter 5-19, 7-22
listner port number 5-18, 7-23
parameters 5-18, 7-22
ordering jobs
authorization 3-5
job security 3-5
New Day procedure 1-14
Orderno field
CONTROL-M log B-1
OS_PRM_HOSTNAME
agent parameter 5-28
server parameter 5-28
output
see reports
see sysout files
Owner field
CONTROL-M log B-1
P
parameter, Check Kernel Configuration 4-41
parameters
see also variables
CONTROL-M/Server 5-1
coordination 5-2
customization 5-1
Customization menu 4-30
database 5-15
performance 5-21
Sybase database 5-15
system 5-3
PARM1 AutoEdit variable
User Daily jobs 1-20
PARMn parameter
Oracle Applications 2-35
Oracle Applications (ctmcreate) 2-35
Oracle Applications (ctmdefine) 2-60
passwords
database 2-102
path modification
tcsh command 2-13
permission. See security
pinging
ctmping utility 2-103
Index
13
14
problem detection
IOALOG events 1-40
log file size monitor 1-39
tools 1-38
Process log file
erasing contents 4-42
process, discovery 1-6, 2-103
processes
CONTROL-M/Server 4-43
suspending 2-134
proclog file
stack trace output 1-42
Production Support menu 2-106
profile_ parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-60
progname parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-60
program parameter
SAP (ctmcreate) 2-33
SAP (ctmdefine) 2-59
Protocol
communication parameter 5-10, 5-28
communication with agents 1-6
Protocol Version parameter
description 5-14
Q
Quantitative resources
agent platform usage 2-86
ctmloadset utility 2-86
deleting 4-48
discrepancy A-5
listing 2-158
maintaining 2-158
reserved A-18
Query Socket
port number 5-16
QUERY_SPN field
mirror database 7-4
quiet parameter
ctmvar utility 2-153
quotation marks
AutoEdit variables 2-29, 2-52, 2-76,
2-133
R
R/3See SAP
r3_owner parameter
SAP jobs (ctmdefine) 2-59
SAP jobs(ctmcreate) 2-34
raw partitions. See partitions
RBS tablespace file
Oracle parameter 5-19
read permission
assigning 2-14
reading. See downloading
recovery
see also failover
data center failure 7-33
database failure 7-29
failover planning 1-10
relationship parameter
New Day procedure 1-17
release version
ENTERPRISE/CS parameter 5-12
Remote Sybase host name
database parameter 5-17, 7-20
removing. See deleting
reordering jobs
User Daily 2-145
reporting
CONTROL-M log entries 2-91
Index
15
reports
ctmcontb utility 2-21
ctmlog utility 2-92
ctmordck utility 2-95
ctmrpln utility 2-120
description 2-6
ecactltb utility 2-157
ecaqrtab utility 2-159
resources
see Control resources
see Quantitative resources
Resource Table options
ctmpsm utility 2-110
respapp parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-60
respname parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-60
Restore Database option
Database Maintenance menu 4-16
restoring
CONTROL-M database 2-44, 4-16
ctmdbrst utility 2-44
Restricted security level 3-2
Retro parameter
job processing 1-22
Retry Interval parameter
description 5-14
Rollback segment tablespace file
Oracle parameter 5-19
RUNCNT
rerun counter A-10
RUNINF_PURGE_LIMIT
server parameter 1-14, 5-25
RUNINF_PURGE_MODE
server parameter 5-25
runtime statistics 1-28
S
SAP
job parameters (ctmcreate) 2-33
job parameters (ctmdefine) 2-58
Savings Time, Daylight 1-33
SCHEDTAB mode
ctmpsm utility 2-117
scheduling function options
ctmpsm utility 2-110, 2-111
scheduling jobs
New Day procedure 1-15
performance parameters 5-21
scheduling tables
authorization 3-21
ctmpsm utility 2-113
defining jobs 2-47
listing jobs 2-120
security 3-4
scope
AutoEdit variables 2-150
script, install_mirror 7-17
Secure Socket Layer
ctmsys utility 2-142
16
security
Active Jobs file 3-5
agent platform 3-8
application 3-1
assigning users to groups 3-11
authorization problem A-15
authorizations 3-2, 3-9
CONTROL-M entities 3-7
ctmsec maintenance utility 3-11
database 3-11
export defintion tables 4-29
Global conditions 3-8
import definition tables 4-29
job script execution denied A-23
job status 2-94
levels 3-2
permission assignment 2-14
Restricted security level 3-2, 5-5
Scheduling tables 3-4
Security Authorization menu 4-29
Servers file 1-9
setting levels 5-5
summary 3-9
table access denied A-23
Unrestricted security level 3-2, 5-5
user ID not authorized A-23
Security Authorization menu 4-29
security level, Restricted 3-2
Security Maintenance utility
Active Jobs file 3-24
adding groups 3-18
adding users 3-13
batch mode 3-32
deleting groups 3-18
deleting users 3-13
description 3-11
entity authorization 3-28
menu 4-29
Scheduling table authorization 3-21
security, application 3-1
security_groupname parameter
Oracle Applications (ctmcreate) 2-35
Oracle Applications (ctmdefine) 2-60
server
see also CONTROL-M/Server
see also Oracle SQL Server
see also Sybase SQL Server
failover 1-11
Server process
message prefix A-1
Server-to-Agent
port numbers 5-14
setting. See customizing
Shout Destination tables
active table 2-129
ctmsys utility 2-135
description 1-24
maintenance 2-135
specifying destinations 1-28
Shout facility
description 1-24
Shout messages
agent platforms 2-138
ctmshout utility 2-127
Daylight Savings Time 1-34, 1-35
ENTERPRISE/CS 2-138
invalid destination A-17
Show Database Parameters option
Database Maintenance menu 4-25
SID mirror
Oracle parameter 5-21
size monitor
log files 1-39
size of database log files
Oracle parameter 5-18
SL_BREAK_INT
performance parameter 5-22
server parameter 5-26
Index
17
Sleep Time
considerations 4-49, 5-22
resetting 4-48
SNMP traps
ctm2snmp utility 2-155
space usage
database 2-45
spool parameter
SAP jobs (ctmcreate) 2-34
SAP jobs (ctmdefine) 2-59
SQL server
see also Oracle SQL server
see also Sybase SQL server
SSL
see also Secure Socket Layer
stack trace
debugging 1-42
problem detection 1-39
proclog file 1-42
stageparm parameter
Oracle Applications (ctmdefine) 2-60
stageparm parameter
Oracle Applications (ctmcreate) 2-35
Start Day of the Week parameter 5-5
starting
CONTROL-M/Server 4-2, 4-8
Sybase SQL server 4-9
Statistical Details table
ctmjsa utility 1-30
Statistical Summary table
ctmstats utility 2-130
statistics
compiling 2-77
ctmjsa utility 1-30
deleting 1-14, 2-124
listing 2-77, 2-124
overview 1-28
runtime 1-28
summary mode 5-12
systems parameter 1-29, 5-4
viewing 2-130
Statistics Mode parameter
description 1-29, 2-77, 5-12
Statistics Summary table
ctmjsa utility 1-30
statistics, runtime 1-28
STATS_TIME
server parameter 5-25
step_num parameter
SAP jobs (ctmcreate) 2-34
SAP jobs (ctmdefine) 2-59
stopping
CONTROL-M/Server 4-2, 4-8
ctmkilljob utility 2-81
Sybase SQL server 4-9
SUBMITTED AT time
CONTROL-M log 1-8
Subsystem field
CONTROL-M log B-1
Support menu, Production 2-106
Sybase
backing up 4-14
Sybase interface directory
database parameter 5-17
Sybase parameter
log physical device 5-17, 7-20
Master physical device 5-16
owner 5-15, 7-19
Sybase SQL server
character set 7-6
considerations 7-4, 7-7
database mirroring 7-4
database name 5-17
database parameters table 5-15
dedicated 7-4
maintenance 4-4
starting 4-9
stopping 4-9
18
synchronization
database 7-36
mirror database 7-36
sysout files
cleanup by New Day procedure 1-14
copy error A-13
days retained 5-5
delete failure A-14
lost A-15
move failure A-13
open error A-13
release failure A-14
sysout log directory
system parameter 5-3
Sysout Log Directory parameter 5-3
SYSOUT_MODE
agent parameter 5-30
SYSOUT_NAME
agent parameter 5-30
SYSTEM
value for AUTOEDIT_INC_SEC 5-23
system parameters
description 5-3
maintenance 2-135
System User Daily
UDLAST parameter 1-14
System user password
Oracle parameter 5-19
T
table. See Scheduling tables
table security
access denied A-23
Tablespace
data file 5-18
Oracle SQL server 7-7
size 5-18
user 5-18
Tasktype field
U
UDLAST parameter
description 1-21
New Day procedure 1-14
User Daily 1-14
ue_exit directory
user exits 6-4
Index
19
Unavailable status
agent platform 1-7
Unknown status
agent platform 1-8
unordered jobs
listing 2-145
User Daily jobs 2-145
Unrestricted security level
description 3-2
UPDATEAJF mode
ctmpsm utility 2-118
UPDATEGROUP mode
ctmpsm utility 2-119
UPDATETABLE mode
ctmpsm utility 2-119
User Daily
AutoEdit variable %%PARM1 1-20
ctmordck utility 2-94
CTMUE105 user exit 6-11
CTMUE106 user exit 6-11
Date Control record 1-21
example 1-19
interruptions 1-23
reordering jobs 2-145
scheduling 1-15
workflow 1-18
User Daily jobs
checking 2-145
ctmudly utility 2-149
last run date 2-147
listing job definitions 2-94
unordered jobs list 2-145
user exits
see also exits
configuration parameters 5-27, 6-3
location 6-1
Watchdog facility 1-47
workflow 6-3
user ID
see also owner
unauthorized A-23
User Maintenance option
ctmsec utility 3-13
User password
Oracle parameter 5-18, 7-22
userexits
enabling 6-3
username parameter
Oracle Applications (ctmcreate) 2-34
Oracle Applications (ctmdefine) 2-34,
2-60
utilities
ctm_backup_bcp 2-17
ctm_restore_bcp 2-19
ctm2snmp 2-155
ctmcontb 2-21
ctmcreate 2-25
ctmdbapasswd 2-36
ctmdbbck 2-37
ctmdbcheck 2-39
ctmdbrst 2-44
ctmdbspace 2-45
ctmdbtrans 2-46
ctmdefine 2-47
ctmdiskspace 2-62
ctmexdef 2-64
ctmfw 2-66
ctmgrpdef 2-75
ctmjsa 2-77
ctmkilljob 2-81
ctmldnrs 2-82
ctmloadset 2-86
ctmlog 2-91
ctmordck 2-94
ctmorder 2-96
ctmping 2-103
ctmpsm 2-106
ctmrpln 2-120
ctmruninf 2-124
ctmsec 3-13
BMC Software, Inc., Confidential and Proprietary Information
20
ctmshout 2-127
ctmshtb 2-129
ctmstats 1-30, 2-130
ctmstvar 2-133
ctmsuspend 2-134
ctmsys 2-135
ctmudchk 2-145
ctmudlst 2-147
ctmudly 2-149
ctmvar 2-150
ctmwhy 2-154
ecactltb 2-157
ecaqrtab 2-158
environment variables 2-9
Oracle variables 2-10
output destination 2-7
reference table 2-4
reports 2-6
summary table 2-2
Sybase variables 2-10
user access to 2-9
V
var parameter
ctmvar utility 2-152
varexpr parameter
ctmvar utility 2-152
variables. See AutoEdit variables.
Environment variables, and parameters
variant parameter
SAP (ctmcreate) 2-34
SAP jobs (ctmcreate) 2-34
SAP jobs (ctmdefine) 2-59
verifying
database integrity 2-37
User Daily jobs 2-145
viewing
see also listing
statistics 2-130
W
waitchild parameter
Oracle Applications (ctmcreate) 2-35
Oracle Applications (ctmdefine) 2-60
waitonly parameter
SAP jobs (ctmcreate) 2-34
SAP jobs (ctmdefine) 2-59
Watchdog facility
configuration parameters 5-31
description 1-44
error handlers 1-48
parameters 5-31
predefined exits 1-45
problem detection 1-39
user exits 1-47
Watcher utility, File 2-66
WD_ALIVE_MSG parameter
Watchdog facility 1-48
WD_CTMEXIT__CMD_LINE parameter
Watchdog exit 1-46
WD_CTMEXIT__ERROR_MSG parameter
Watchdog exit 1-46
WD_CTMEXIT__INTERVAL parameter
Watchdog exit 1-46
WD_CTMEXIT__RUN_STATE parameter
Watchdog exit 1-46
WD_CTMEXIT__SCRIPT_FILE parameter
Watchdog exit 1-46
WD_CTMEXIT__SUSPEND_STATE
Watchdog exit 1-46
WD_CTMEXIT__TIMEOUT parameter
Watchdog exit 1-46
WD_CTMEXIT_NUMBER parameter
Watchdog facility 1-44
WD_CTO_HOSTNAME parameter
Watchdog facility 1-48
WD_CTO_TIMEOUT parameter
Watchdog facility 1-49
Index
21
WD_ERROR_HANDLER_SCRIPT_FILE
Watchdog facility 1-49
WD_ERROR_HANDLER_TIMEOUT
Watchdog facility 1-49
WD_HEARTBEAT_INTERVAL exit
Heartbeat check 1-45
WD_INTERVAL parameter
Watchdog facility 1-49
WD_USEREXIT__CMD_LINE parameter
Watchdog exit 1-47
WD_USEREXIT__ERROR_MSG
Watchdog exit 1-47
WD_USEREXIT__INTERVAL parameter
Watchdog exit 1-47
WD_USEREXIT__RUN_STATE parameter
Watchdog exit 1-47
WD_USEREXIT__SCRIPT_FILE
Watchdog exit 1-47
WD_USEREXIT__SUSPEND_STATE
Watchdog exit 1-47
WD_USEREXIT__TIMEOUT parameter
Watchdog exit 1-47
WD_USEREXIT_NUMBER parameter
Watchdog facility 1-44
Windows NT
CONTROL-M/Server 1-9
workflow
CONTROL-M jobs 1-2
New Day procedure 1-13
scheduling jobs 1-15
User Daily jobs 1-18
write permission
assigning 2-14
Y
Yearly report
ctmpln utility 2-120
22
Notes
*100037648*
*100037648*
*100037648*
*100037648*
*100037648*