Codigo de Errores en Control-M

Control-M Messages Manual
Supporting
Version 7.0.00 of Control-M/Enterprise Manager
Version 7.0.00 of Control-M/Server for UNIX and Microsoft Windows
Version 7.0.00 of Control-M/Agent for UNIX and Microsoft Windows
June 2010
www.bmc.com
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain
information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

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

Telephone +01 713 918 8800 Fax +01 713 918 8000
Copyright 2010- BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are
registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in
other countries. All other BMC trademarks, service marks, and logos may be registered or pending
registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
Linux is the registered trademark of Linus Torvalds.
Oracle is a registered trademark of Oracle Corporation.
UNIX is the registered trademark of The Open Group in the US and other countries.
BMC Software considers information included in this documentation to be proprietary and confidential.
Your use of this information is subject to the terms and conditions of the applicable End User License
Agreement for the product and the proprietary and restricted rights notices included in this documentation.
The information included in this documentation is the proprietary and confidential information of BMC
Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions
of the applicable End User License agreement for the product and to the proprietary and restricted rights
notices included in the product documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHEDRIGHTS RESERVED
UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data
and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR
Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS
252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101
CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer support
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this
website, you can
read overviews about support services and programs that BMC offers
find the most current information about BMC products
search a database for problems similar to yours and possible solutions
order or download product documentation
download products and maintenance
report a problem or ask a question
subscribe to receive proactive e-mail alerts
find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and
telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or
send an e-mail message to [email protected]. (In the subject line, enter SupID:yourSupportContractID, such
as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC

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

messages from the operating system, such as file system full
messages from related software
3
License key and password information
If you have questions about your license key or password, contact BMC as appropriate for your location:
(USA or Canada) Contact the Order Services Password Team at 1 800 841 2031, or send an e-mail message to
[email protected].
(Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send
an e-mail message to [email protected].
(Asia-Pacific) Contact your BMC sales representative or your local BMC office.
4 Control-M Messages Manual

Contents
About this book 7
Conventions .......................................................................................................................7
Syntax statements .............................................................................................................8
Related publications .........................................................................................................8
Chapter 1 Control-M/EM messages 11

Messages 24001 through 24099 .....................................................................................11
Chapter 2 Control-M/Server messages 59

Messages 5001 through 5099 .........................................................................................59
Messages 5900 through 5999 .......................................................................................102
Contents 5
Messages AP-1 through AP-99 ...................................................................................222
Chapter 3 Control-M/Agent messages 229

Messages AGT7901 through AGT7999 ......................................................................236

About this book
This book contains detailed product information and is intended for system
administrators and database administrators (DBAs).
Like most BMC documentation, this book is available in printed and online formats.
To request printed books or to view online books and notices (such as release notes
and technical bulletins), see the Customer Support website at http://www.bmc.com/
support_home. Most product shipments also include the books on a documentation
CD.
Note
Online books are formatted as PDF or HTML files. To view, print, or copy PDF
books, use the free Adobe Reader from Adobe Systems. If your product installation
does not install the reader, you can obtain the reader at http://www.adobe.com.
The software also offers online Help. To access Help, press F1 within any product or
click the Help button in graphical user interfaces (GUIs).
Conventions
This document uses the following special conventions:
All syntax, operating system terms, and literal examples are

presented in this typeface.
Variable text in path names, system messages, or syntax is displayed in italic text:
testsys/instance/fileName
This document uses a symbol to show menu sequences. For example, Actions =>
Create Test instructs you to choose the Create Test command from the Actions
menu.
About this Book 7

Syntax statements
Syntax statements
This topic explains conventions for showing syntax statements.
A sample statement follows:
COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName
Convention Example
Items in italic type represent variables that you alias

must replace with a name or value. If a variable databaseDirectory
is represented by two or more words, initial
capitals distinguish the second and subsequent serverHostName
words.
Brackets indicate a group of optional items. Do [tableName, columnName, field]
not type the brackets when you enter the [-full, -incremental, -level] (UNIX)
option. A comma means that you can choose
one or more of the listed options. You must use
a comma to separate the options if you choose
more than one option.
Braces indicate that at least one of the enclosed {DBDName | tableName}
items is required. Do not type the braces when UNLOAD device={disk | tape, fileName |
you enter the item. deviceName}
{-a | -c} (UNIX)
A vertical bar means that you can choose only {commit | cancel}
one of the listed items. In the example, you {-commit | -cancel} (UNIX)
would choose either commit or cancel.
An ellipsis indicates that you can repeat the columnName
previous item or items as many times as
necessary.
Related publications
The following related publications supplement this book and the online Help:
Document Description
Control-M Administrator Guide Describes the tasks that the Control-M administrator
must perform to define, monitor, and maintain the
Control-M environment
Control-M User Guide Describes Control-M concepts, features, facilities and
operating instructions

Document Description
Control-M Utility Guide Provides instructions for running command line
utilities that can be used to perform various Control-
M tasks
Control-M Parameter Guide Describes syntax and usage for all parameters and
variables that are included in Control-M job
processing definitions
About this Book 9


1
Control-M/EM messages
The following messages are issued by Control-M/EM. These messages may be
displayed in the Control-M/EM GUI or one of the Control-M/EM components.
Messages 24001 through 24099

This group includes messages for Control-M/EM.
24001 Failed to refresh alert list in memory. Alert list will be refreshed in the next
refresh cycle. (WARNING).
Explanation: X-Alert message. Your database might be experiencing problems,
or the ALARM table might not exist. During each specified period of time, the
Global Alerts Server (GAS) refreshes the list of the alerts saved in its memory
and deletes from its memory the alerts that were deleted by the Gateway from
the database, thereby synchronizing the list of alerts saved in the memory and
in the database.
When the problem is corrected, the GAS will refresh deleted alerts in the next
refresh period.
User response: It is likely that this is a database or database connectivity issue.

If the problem still exists, run the Control-M/Enterprise Manager Health Check
utility by typing em_data_collector from the command line and contact BMC
Customer Support. For more information about using the Health Check utility,
see the Control-M Utility Guide.
24002 Failed to load new alert (alert number = alertNumber, data center =
dataCenter, severity = severity, order id = orderID). (ERROR)
Explanation: X-Alert message. A new alert might contain invalid data. The
Global Alerts Server (GAS) receives an indication from the Gateway that a new
alert was inserted into the database. Due to invalid data in the alert or a lack of
important information, the GAS failed to create a new alert in memory
according to the data received from the database.

The variables in this message are:
alertNumber - the alert number
dataCenter - the data center that issued the alert
severity - the severity of the alert
orderID - the order ID of the specified alert
The new alert is not displayed by the Global Alerts Client.
User response: Run the Control-M/Enterprise Manager Health Check utility by

typing em_data_collector from the command line and contact BMC
24003 Failed to update alert (alert number = alertNumber, data center =

dataCenter, severity = severity, order id = orderID). (ERROR)
Explanation: X-Alert message. An alert in the database might contain invalid
data.
The Global Alerts Server (GAS) received the indication from Gateway that the
specified alert was updated in the database. Due to lack of data or invalid data
in the alert, the GAS failed to create a new alert in memory according to the
data received from the database.
alertNumber - the alert number
dataCenter - the data center that issued the alert
severity - the severity of the alert
orderID - the order ID of the specified alert
No update for this alert is displayed by the Global Alerts Client.

24004 Failed to read alert from database (alert number = alertNumber) because of
database problems. (ERROR)
Explanation: X-Alert message. The Global Alerts Server (GAS) failed to read
the new or updated alert from the database.

New alerts or alert updates are not displayed by the Global Alerts Client.

24005 Failed to load alerts for data center dataCenter because of database
problems. (ERROR)
Explanation: X-Alert message. Problems with the database cause the Global
Alerts Server (GAS) to fail in reading the alerts related to the specified Control-
M/Server after establishing the connection with it.
Alerts that are relevant for the specified Control-M/Server are not displayed by
the Global Alerts Client.

24006 GAS failed to load alerts from the database when starting. Exiting... (SEVERE)
Explanation: X-Alert message. Your database might be experiencing problems.
The Global Alerts Server (GAS) failed to load alerts from the database when
starting.
The GAS shuts down.
User response: Check the ALARM database table availability by performing a

select query on it.
Note
Executing SQL statements in the database may impact database integrity. If
you are not comfortable executing these statements, contact your DBA or BMC
Software.
If you cannot fix the problems, run the Control-M/Enterprise Manager Health
Check utility by typing em_data_collector from the command line and
contact BMC Customer Support. For more information about using the Health
Check utility, see the Control-M Utility Guide.


25001 Condition could not be sent to data center dataCenter (reason = reason,
odate = date, condition = condition). (WARNING).
Explanation: X-Alert message. The specified condition could not be distributed
to the requested data center.
dataCenter - the data center name
reason - an explanation of the failure:
Failed to connect to the target data center
Stopped trying to send because the maximum number of retries was

reached.
Stopped trying to send because the condition was older than the value
specified by the gc_unsent_wait parameter in the Global Conditions Server.
date - the order date.
The global condition was not distributed to the specified data center. Therefore,
production flow may be negatively affected.
User response: Check the communication between this data center and the
Gateway and correct any problems.
If the production flow was affected, consider adding this condition manually
on the target data center to restore desired flow.
If problems persist, run the Control-M/Enterprise Manager Health Check

utility by typing em_data_collector from the command line and contact BMC

26001 DO Remedy is not Supported on platformName for service serviceName

(ERROR)
Explanation: X-Alert message. The serviceName service has requested a DO
Remedy action, but DO Remedy actions are not Supported on the platformName
platform.

A Remedy ticket is not opened.
User response: Remove the DO Remedy definition from the BIM service action
list.
26002 DO SIM is not Supported on platformName for service serviceName(ERROR)

Explanation: X-Alert message. The serviceName service has requested a DO SIM
action, but DO SIM actions are not Supported on the platformName platform.
No SIM message describing the service problem is sent.
User response: Remove the DO SIM definition from the BIM service action list.
26003 BIM Server is not installed (SEVERE)

Explanation: X-Alert message. The BIM Server has not been installed.
User response: Install the BIM Server or remove the BIM job from the schedule.
26004 Mail Server didnt respond (SEVERE)

Explanation: X-Alert message. The Mail Server did not respond.
User response: Verify the EmailServer system parameter or the availability of
the mail server itself.

27001 Forecast Server is not installed (SEVERE)

Explanation: X-Alert message. The Forecast Server has not been installed.
User response: Install the Forecast Server.

28001 Bad or Unknown Auth Category: category, for Destination: destination,

request: request
Explanation: The category value in the ACTIONS_AUTH database table is
invalid.

category - the category to which the authorized actions belong. Valid values
are:
OPER
CTMSEC
CONFIG
DATABASE
destination - the component that handles the request.
request - the name of the request.
The Configuration Management Server rejects the request.
User response: Contact BMC Software Customer Support.
28002 Bad or Unknown Auth Level: level, for Destination: destination, request:
request
Explanation: The authorization level value in the ACTIONS_AUTH database
table is invalid.
level - the authorization level value. Valid values are:
BROWSE
UPDATE
FULL
28003 Bad or Unknown Request. Destination: destination, request: request

Explanation: The destination and request name pair are not found in the
ACTIONS_AUTH database table.

28004 Request Permission Denied. Destination: destination, request: request

Explanation: The user does not have permission to perform the request.
User response: Assign permission to the user to perform the specified request.
28005 Fail To Get Component Details. Machine: host, Type: type, Name:
component; Code: error
Explanation: The Configuration Management Server failed to locate the target
component for the CTL request.
host - the component host.
type - the type of the component.
component - the name of the component.
error - the internal error code.
User response: Verify that the requested component is up and running, and
perform the request again. If the request still fails, contact BMC Software
Customer Support.
28006 CTL Request Failed. Machine: host, Type: type, Name: component; Code:
error
Explanation: The Configuration Management Server failed to send the CTL
request to the target component.

host - the component host.
type - the type of the component.
component - the name of the component.
error - the internal error code.
User response: Verify that the requested component is up and running, and
perform the request again. If the request still fails, contact BMC Software
Customer Support.
28007 XML Parse Error.

Explanation: An attempt to parse an XML input document failed.
User response: Repeat the last action. If the request still fails, contact BMC
Software Customer Support.
28008 Handler Not Found For Request: name.

Explanation: The request is not Supported by the Configuration Management
Server.
In this message, name is the name of the request.
28009 XML Distributor Internal Error: message.

Explanation: An internal error occurred in the Configuration Management
Server.
In this message, message is the explanation of the error.
28010 XML Distributor Internal Error: ID does not exist

Explanation: The polling ID could not be found in the Configuration
Management Server repository.

The polling request is denied.
28011 Gate Error Received: error.

Explanation: The Configuration Management Server received an error from
Control-M.
In this message, error is the error that was received from Control-M.
User response: Check Control-M messages for more information.
28012 Gate Protocol Error: error.

Explanation: An internal CMS Gate communication error occurred in the
Configuration Management Server.
In this message, error provides additional information about the specific problem.
28013 CMS Gate Request Timeout, Control-M: name Request: request.

Explanation: A request sent by the Configuration Management Server to the
Control-M Configuration Agent was not replied to within the time specified by
the AdminRequestTimeout parameter.
name - the Control-M name.
request - the internal request sent by the Configuration Management Server

to the CMS Gate.
The request times out.
User response: Increase the value of the AdminRequestTimeout parameter and

submit the request again.
28014 CMS Gate Request Aborted, Control-M: name Request: request.

Explanation: A request sent by the Configuration Management Server and the
Control-M Configuration Agent has been lost. The requests completion status
is unknown.

request - the internal request sent by the Configuration Management Server

to the CMS Gate.
A communications error occurred.
User response:
Check that communications are operating properly, and then perform the
request again.
Check that the requested component is up and running, and perform the
request again.
28015 CMS Gate Discover Failed, Reason: reason; Host: host, Port: port.
Explanation: A CMS Gate discover operation failed. Possible reasons are
incorrect host or port parameters, or the Control-M Configuration Manager on
Control-M is not running.
reason - the reason for the failure, if available.
host - the Control-M host name.
port - the Control-M port.
The reason for the failure is explained in this message. No information is

received from the Configuration Management Server.
User response: Do the following:
Check the reason displayed in this message, and then perform the operation
again.
If the host and port parameters are correct, and Control-M Configuration
Manager is up and running, check the cmsg_log file located in <EM
INSTALL DIR>/log folder for more information.
28016 CMS Failed Sending Command To Control-M: name; RC: rc.

Explanation: The Configuration Management Server failed to send the request
to Control-M. Communication with the Control-M Configuration Manager
could not be established.
rc - the internal error code.

User response: Check that the Control-M is connected, and then perform the
request again.
28017 Component Info Parsing Error. Request: request

Explanation: The Configuration Management Server fail to extract component
information from the input XML document.
In this message, request is the request name.
User response: Repeat the last action. If the problem still occurs, contact BMC
28018 Component With The Same Key Already exists. Key: key
Explanation: An attempt to create a component failed, since a component with
the same key already exists in the Configuration Management Server
repository.
In this message, key is the component key. The key may be:
type, host, or name for Control-M/EM
type or name for Control-M
User response: Change the component key, and attempt to create the
component again.
28019 Unable to perform the operation. Reason: Component not found (It was
probably deleted by another console). Component details: type= type host=
host name= name
Explanation: The requested component was not found in the Configuration
Management Server repository.
type - the component type.
host - the name of the host on which the component is installed.
name - the logical name of the component.

User response: Refresh the Configuration Management Server view, and

perform the request again.
28020 SQL Operation Failed, RC: rc, Message: text

Explanation: The Configuration Management Server encountered an error
while accessing the EM database.
rc - the internal error code.
text - the SQL error message, if available.
User response: Try to access the database again. If the problem continues,
contact BMC Software Customer Support.
28021 Set Desired State Failed, RC: rc

Explanation: An attempt to change the desired state failed.
In this message, rc is the internal error code.
User response: Try to change the state again. If the problem continues, contact
BMC Software Customer Support.
28022 Unable to perform the operation. Reason: Control-M name not found (It was
probably deleted by another console)
Explanation: The Control-M that is the destination of the request was not
defined in the Configuration Management Server repository.
In this message, name is the name of the requested Control-M.
User response: Refresh the Configuration Management Server view, and

perform the request again.
28023 Control-M With The Same Name Or Code Already exists. Name: name,
Code: code
Explanation: An attempt to define a new Control-M failed, since a Control-M
with the same name or code already exists.

name - the new Control-M name.
code - the Control-M short name.
User response: Change the Control-M name or code, and retry.
28024 Invalid Or Unknown Operation On Control-M; Operation: action

Explanation: An internal Configuration Management Server error occurred.
In this message, action is the operation name.
28025 Value cannot be empty for field: fieldName

Explanation: The required fieldName field in a request was left empty.
The Control-M Configuration Manager displays this message.
User response: Make sure you fill in all required fields in the request.
28026 Bad value for field: fieldName, bad value is: value
Explanation: The fieldName field in a request contained an invalid value.
User response: Enter a valid value in the fieldName field.
28027 Failed to login as user: userName, rc: rc, message: text

Explanation: You could not log on to the database as the userName user
(usually, the administrator). This may be due to an incorrect user name or
password.
userName - the name of the user for whom the logon failed.
rc - the return code that is issued.
text - the displayed message text explaining why the logon failed, generated
by the database vendor.

User response: Follow the instructions in the message.
28028 The following request failed: requestName, rc: rc, Message: text
Explanation: The requestName user request failed.
User response: Check the displayed message for the next action to perform.
28029 Invalid number for deleted old alerts. rc: rc, Message: text, Deleted:
deletedNum
Explanation: Old alerts are deleted from the ALARM table on specified dates. If
the delete action fails for any reason, the number of deleted alerts returned
from the query may be invalid (such as a negative number).
text - the displayed message text.
deletedNum - the returned number of deleted alerts.
User response: Check the displayed message for the next action.
28030 A parameter with the same key already exists for paramName
Explanation: The user is trying to add a system parameter that already exists
into the PARAMS table.
The parameter is not added to the PARAMS table.
User response: Check the details of the parameter and correct them. Repeat the
attempt to add the parameter.
28031 Can't update, parameter's details do not exist: paramName

Explanation: The user is trying to update the paramName system parameter,
which does not exist in the database.
The parameter is not updated to the PARAMS table.
User response: Check the details of the parameter and correct them. Repeat the
attempt to add the parameter.

28032 Fail To Save Desired State In Database.

Explanation: The Configuration Management Server failed to update the state
of Control-M in the EM database.
User response: Check the Configuration Management Server log file.
28033 Invalid State Code.

Explanation: An internal XML document received an invalid state code.
28034 Invalid Or Unknown Process Type.

Explanation: An internal XML document received an invalid or unknown
process type.
28035 Missing Mandatory Value tag.

Explanation: A mandatory tag or value is missing.
In this message, tag is the missing tag name.
28036 Invalid Or Unknown OS Type.

Explanation: An internal XML document received an invalid or unknown
operating system type.
28037 User Not Registered

Explanation: The user token is not valid.

User response: Reconnect to the Configuration Management Server to receive a

valid token.
28038 CMS Gate is not connected to Control-M name. Verify that Control-M host
hostName and Admin Port port are correct, and Control-M Configuration
Agent is up and running
Explanation: The Control-M Configuration Agent is not connected to the
Configuration Manager.
hostName - the Control-M host name.
port - the port on which the Control-M Configuration Manager listens, as

defined by Control-M/EM.
The request can not be completed.
User response: Verify that Control-M host and port are correct, and that the
Control-M Configuration Manager is up and running.
28039 Failed to connect to Control-M/Enterprise Manager Configuration Agent.

Explanation: A connection could not be established with the Control-M/
Enterprise Manager Configuration Agent.
User response: Verify that the Control-M/Enterprise Manager Configuration
Agent on ${%s} is running.
28041 Database device deviceName is percentage percent full, lack of database

space may risk EM functionality. (WARNING)
Explanation: X-Alert message. The database space (data or log segments) has
already reached the capacity of 90% (default value).
A warning is issued.
User response: Extend the database size. Contact your DBA for assistance in
performing this action if you are not comfortable performing it yourself. For
Dedicated databases, this can be done through the Control-M Configuration
Manager GUI by selecting the Extend Database option from the Database menu
item.
It is possible to change the default threshold value by updating the

DBCheckSpaceWarningPct system parameter in the Control-M Configuration
Manager by selecting Tools:System Parameters.


29001 EM - Control-M name Communication Service Timed Out. timeout= time,

type= type, instance= ID (ERROR)
Explanation: X-Alert message. A communication service between the Gateway
and Control-M timed out. This service can be a request for an action, such as
hold or free, or a request for information, such as SYSOUT, log or download.
time - the length of the timeout, in seconds.
type - the type of requested service.
ID - the internal service ID.
The service is cancelled by the Gateway.
User response: Generally, a service timeout is an indication of a performance

problem. If the problem occurs again:
Enable the relevant trace on the specified Gateway by performing the

following steps:
Right-click the specified Gateway component using the Control-M

Configuration Manager GUI and choose Control shell.
Specify the TRACE_CLIENT control shell command and click Apply.
Specify the TRACE_CTM control shell command and click Apply.
Wait for the next occurrence of the same X-Alert to arrive (meaning that the
problem has been recreated).
Disable the traces on the Gateway by performing the following steps:

Specify the TRACE_DISABLE_ALL control shell command and click

Apply.
Run the Control-M/Enterprise Manager Health Check utility by typing

em_data_collector from the command line and contact BMC Customer

Support. For more information about using the Health Check utility, see the
Control-M Utility Guide.
Contact BMC Customer Support, providing the logs from the Control-M/
Enterprise Manager Server as well as the CO and CS logs from Control-M/
Server.
29002 Upload of tableName Aborted (time-out), no answer from Control-M name.

timeout= time, instance= ID
Explanation: A service that was uploading a definition table timed out. This
message appears together with general timeout message 29001. The final status
of the upload is unknown.
tableName - the definition table name.
User response: Retry the operation. If the problem occurs again, contact BMC
29003 Download of tableName Aborted (time-out), no answer from Control-M

name.
Explanation: A service that was downloading a definition table timed out. This
message appears together with general timeout message 29001. The status of
the table in Control-M/EM is unknown.
User response: Retry the operation. If the problem occurs again, contact BMC

29004 Download of tableName Aborted in Gateway, Control-M name.

Explanation: A service that was downloading a definition table aborted. The
status of the table in Control-M/EM is unknown.
User response: Retry the operation and check the Gateway log for additional
messages. If the problem occurs again, contact BMC Software Customer
Support.
29005 Gateway Client (name) CommEMBufferSize =maxSize Actual = actualSize.

(WARNING)
Explanation: X-Alert message. A message that cannot be sent over the
communication channel, because the TCP buffer is full, is temporarily written
into an internal buffer. This message indicates that the buffer for
communication with one of the Gateway clients (GUI Server, Global Alerts
Server, or Global Conditions Server) is full. The buffer size is determined by the
value of the CommEMBufferSize system parameter.
name - the Gateway client name.
maxSize - the maximum number of characters specified for the buffer.
actualSize - the actual size of the queue.
The problematic communication channel is closed and reopened.
User response: If necessary, increase the value of the CommEMBufferSize

system parameter in the Control-M Configuration Manager by selecting
Tools:System Parameters to a value 10% greater than actualSize.
29006 Gateway Control-M name CommCTMBufferSize = maxSize Actual =

actualSize. (WARNING)
Explanation: X-Alert message. A message that cannot be sent over the
communication channel, because the TCP buffer is full, is temporarily written
into an internal buffer. This message indicates that the buffer for
communication with the Control-M Server is full. The buffer size is determine
by the value of the max_mf_queue_size parameter in the Defaults.rsc file.

maxSize - the maximum number of characters specified for the buffer.
actualSize - the actual size of the queue.
The problematic communication channel is closed and reopened.
User response: If necessary, increase the value of the CommEMBufferSize

system parameter in the Control-M Configuration Manager by selecting
Tools:System Parameters to a value 10% greater than actualSize.
29007 Gateway Control-M name, Received Update, but job not found in EM
database, For Order_ID orderID (decimalOrderID) Update Sequence
Number number, Event Time time (ERROR)
Explanation: X-Alert message. The Gateway received a request from the Control-
M/Server to update an active job, but the job was not found in the Control-M/
EM database. This message indicates that the Control-M/EM database is not
completely synchronized with the Active Jobs File on the Control-M/Server.
orderID - the unique job order ID.
decimalOrderID - the job order ID in decimal format.
number - the sequence number of the update request.
time - the update time.
The Gateway rejects the update request.
User response: Force the Gateway to download the Active Jobs file by
performing the following steps:

Specify the DO_DOWNLOAD control shell command and click Apply.
Wait until the status of the gateway is switched back to Connected after
completing the Downloading phase.
If the problem persists, run the Control-M/Enterprise Manager Health


contact BMC Customer Support. For more information about using the
Health Check utility, see the Control-M Utility Guide.
29008 Active Download Failure. Control-M name, Odate date, Net Name
(netName), Sequence Number number (ERROR)
Explanation: X-Alert message. A request to download the Active Jobs File (AJF)
from Control-M failed. For additional details, check the Gateway log file.
date - the order date.
netName - the internal name of the net.
number - the sequence number of the update request.
The Gateway closes the communication channel with Control-M, reopens it

and tries to download the Active Jobs file again.
User response: If the problem is not resolved by itself after several retries, run
the Control-M/Enterprise Manager Health Check utility by typing
29009 Create Alert Failure. (ERROR)

Explanation: X-Alert message. The Gateway failed to insert an alert into the
database. The following alert parameters are displayed:
Control-M
Memname
Jobname
OID
Msg
Sev
Owner
Time
Appl

Group
NodeId
Type
Closed_from_EM
Ticket
Run
For descriptions of these parameters, see the Control-M User Guide.
The alert is discarded.
User response: Perform the required actions in order to handle this alert
according to the alert message displayed on the X-Alert window. If the problem
persists, run the Control-M/Enterprise Manager Health Check utility by typing
29010 Update Alert Failure. (ERROR)

Explanation: X-Alert message. The Gateway failed to update an alert in the
database. The following alert parameters are displayed:
Control-M
Memname
Jobname
OID
Msg
Sev
Owner
Time
Appl
Group
NodeId

Type
Closed_from_EM
Ticket
Run
Handled
ChangedBy
UpdTime
Notes
For descriptions of these parameters, see the Control-M User Guide.
The update is rejected.
User response: For additional details, check the Gateway log file. If the problem
persists, run the Control-M/Enterprise Manager Health Check utility by typing
29011 Gateway - GCS Communication Service Timed Out. Control-M name

timeout= time, instance= ID, Condition= condition (ERROR)
Explanation: X-Alert message. A service for distributing global conditions
timed out.
condition - the condition name.
The service is cancelled by the Gateway. Its status in the Global Conditions
Server (GCS) is unknown.
User response: For additional details, check the Gateway and GCS log files.
Verify that the specific condition is distributed as expected.

29012 Gateway - GCS Communication Service Aborted In Gateway. Control-M

name, instance= ID, Condition= condition (ERROR)
Explanation: X-Alert message. A service for distributing global condition
aborted, because communication with the Global Conditions Server (GCS)
closed.
condition - the condition name.
The service is cancelled by the Gateway. Its status in the Global Conditions
Server is unknown. The Gateway recovery mechanism will redistribute the
condition when connection with the Global Conditions Server resumes.
User response: Verify that the specific condition is distributed as expected.
29013 Processing Of Updates Timed Out, Probably Database Slow Response

Time. Control-M name, Timeout=time. (WARNING)
Explanation: X-Alert message. An update arriving from Control-M/Server has
not been processed for a considerable period of time.
The actual job status in Control-M/EM might be delayed.
User response: If the message repeats itself, run the Control-M/Enterprise

Manager Health Check utility by typing em_data_collector from the
command line and contact BMC Customer Support. For more information
about using the Health Check utility, see the Control-M Utility Guide.
29014 Processing Of Updates Timed Out, Probably Database Slow Response

Time Or Internal Error. Control-M name, Timeout=time. (ERROR)
Gateway will restart itself in order to try and recover from this situation.


29015 Processing Of All, Already Received Updates, Before Download Timed Out,
Probably Database Not Responding or Internal Error. Control-M name,
Timeout time. (ERROR)

29016 Unexpected Fatal Error During Update Processing. Control-M name.

(ERROR)
Explanation: X-Alert message. Internal error in Gateway during data
processing.

29017 DO_MAIL message too long, message truncated. Order Id: orderID.
(WARNING)
Explanation: X-Alert message. In the case in which a specific job data includes
the DO_MAIL option and the message length exceeds the maximum length
allowed. When this job's data arrived from Control-M/Server to Control-M/
EM the gateway truncates the message in order to fit into the relevant database
field. The data is arriving as part of an Active Job file job update.
The job data arriving from Control-M/Server will be processed in Control-M/

EM. However, the message will be truncated once inserted into the Control-M/
EM database. In addition, the following message would be issued on the
relevant Gateway log:
===> WARNING: do_mail_special : active DO_MAIL MESSAGE truncated.
===> WARNING: validate_message_length: DO_MAIL msg truncated at

location, orig length: length.
The relevant Gateway log is located under the Control-M/EM home directory
under the log folder. The name of the Gateway log has the following naming
convention:

gtw_log. DATA_CENTER_NAME. DATE. INSTANCE
User response: Fix the message length on the job definition by performing the
following steps:
Locate the relevant job according to the orderID specified in the X-Alert
message and track down the relevant job definition.
Using the Control-M/EM Desktop GUI, fix the length of the DO_MAIL
message to fit the maximal length. (In case the length has exceeded the limit,
saving the job definition will cause a validity error through a popup window.)
29018 DO_MAIL message too long, message truncated. Table Id: tableIDOrder Id:
orderID. (WARNING)
Explanation: X-Alert message. In the case in which a specific job data includes
the DO_MAIL option and the message length exceeds the maximum length
allowed. When this job's data arrived from Control-M/Server to Control-M/
EM the gateway truncates the message in order to fit into the relevant database
field. The data is arriving as part of an Active Job file job update.
In a case in which a specific job data includes the DO_MAIL option and the
message length exceeds the maximum length allowed. When this job's data
arrived from Control-M/Server to Control-M/EM the gateway truncates the
message in order to fit into the relevant database field. The data is arriving as
part of a job definition download.
The job data arriving from Control-M/Server will be processed in Control-M/

EM. However, the message will be truncated once inserted into the Control-M/
EM database. In addition the following message would be issued on the
relevant Gateway log:
===> WARNING: do_mail_special : definition DO_MAIL MESSAGE

truncated.
===> WARNING: validate_message_length: DO_MAIL msg truncated at

location, orig length: length.
The relevant Gateway log is located under the Control-M/EM home directory
under the log folder. The name of the Gateway log has the following naming
convention:
gtw_log. DATA_CENTER_NAME. DATE. INSTANCE
User response: Fix the message length on the job definition by performing the
following steps:
Locate the relevant job according to the tableID and orderID specified in the
X-Alert message and track down the relevant job definition.

Using the Control-M/EM Desktop GUI, fix the length of the DO_MAIL
message to fit the maximal length. (In case the length has exceeded the limit,
saving the job definition will cause a validity error through a popup window.)
Perform definition upload of this specific scheduling table onto Control-M/

Server to have the change take affect once the job is submitted.

40001 EM Server failed to write audit action to the EM database (action = action,
user = userName, return_code = rc, db error = error (ERROR)
Explanation: X-Alert message. The Control-M/EM Server failed to write an
audit action to the Control-M/EM database.
action - the audit action that was not written to the database.
userName - the name of the user who requested the action.
error - the error returned from the database explaining why the write action
failed.
The Control-M Configuration Manager displays an explanation of the write

failure.
User response: Your database may be experiencing Customer problems. If you

cannot fix the problems, contact BMC Software Customer Support.
40002 Control-M Configuration Manager failed to erase old audit records from the
EM database. Please, delete them manually via erase_audit_data script.
(return_code = rc, error = text (ERROR)
Explanation: X-Alert message. The Control-M Configuration Manager failed to
erase old audit records from the Control-M/EM database within the default
deletion period of 360 minutes.
Check the explanation displayed at the error variable in the X-Alert message.
User response: Use the erase_audit_data script to manually delete old

records.


40201 Database server is unavailable for more than number minutes. (WARNING)
Explanation: X-Alert message. The Central Management Server (CMS) warns
that it has had no communication with the database server for more than
number minutes. The default is 60 minutes.
The Central Management Server stays up even when the database is not
available. This message appears after the database has been down for one hour.
User response: Check the database server.
40202 Communication with the database server was lost and can not be
recovered. Server is shutting down in number minutes. (ERROR)
Explanation: X-Alert message. The Central Management Server (CMS) issues
this message when the connection to the database is lost and cannot be
recovered. The CMS remains active for number minutes after communication is
lost so that users can receive this message.
The Central Management Server remains active for number minutes. The
default is 2 minutes.
User response: Recycle the Central Management Server to reestablish the

connection. If the problem persists, run the Control-M/Enterprise Manager
Health Check utility by typing em_data_collector from the command line and
contact BMC Customer Support. For more information about using the Health
Check utility, see the Control-M Utility Guide.
40203 Database server is unavailable for more than number seconds. Server is
shutting down (WARNING) for CMS (SEVERE) for all other components
Explanation: X-Alert message. The Control-M/EM server component that
issued this message has not had communication with the database for more
than number seconds.
The server component shuts down.
User response: Check the database server. After it is available, verify that the
Control-M/EM server component has restarted. If the problem persists, do the
following:
Stop and restart the Control-M/EM Configuration Agent:

On UNIX platforms - log onto the Control-M/EM account and run the
following scripts:
stop_config_agent

start_config_agent
On Windows platforms - restart the Control-M/Enterprise Manager
Configuration Agent service.
Wait and see if the relevant server component has succeeded to start.

40204 Communication with the database server was lost and can not be
recovered. Server is shutting down. (ERROR) for CMS (SEVERE) for all
other components
Explanation: X-Alert message. The Control-M/EM server component that
issued this message detected that it has lost its communication with the
database server, and that this connection cannot be recovered.
The server component shuts down. If the server component is managed by the
Control-M Configuration Manager and its desired state is Up, it will reconnect
to the database when it restarts.
User response: Verify that the server component has restarted. If the problem
persists, do the following:
Stop and restart the Control-M/EM Configuration Agent:

On UNIX platforms - log onto the Control-M/EM account and run the
following scripts:
stop_config_agent
start_config_agent
On Windows platforms - restart the Control-M/Enterprise Manager
Configuration Agent service.
Wait and see if the relevant server component has succeeded to start.

40205 Server failed to read system parameter type: paramType, name:

paramName. (ERROR).
Explanation: X-Alert message. The Control-M/EM server component failed to
read a system parameter from the PARAMS table. This might be due to a
problem with the database. This message is not displayed when the system
parameter is missing from the PARAMS table, which is a normal and valid
scenario.

paramType - the context of the system parameter. This can be a component

type, task specific or a general parameter.
paramName - the name of the requested system parameter.
Either a default hard-coded value of the parameter is used, or the last value of
the parameter that was previously successfully read. Therefore, the system
behavior might be different from the behavior specified in the system parameter.
User response: Check that the database is available. If it is, check the log file of
the Control-M/EM server component that issued this message to see why it has
failed to read the parameter. If you cannot fix the problems, run the Control-M/
Enterprise Manager Health Check utility by typing em_data_collectorfrom
the command line and contact BMC Customer Support. For more information

40401 Scheduling group with this scheduling table name already exists. Change
the scheduling table name or the scheduling table library.
Explanation: The scheduling table name specified for the new scheduling
group is already being used. Relevant when working with MVS.
The system is unable to create a new scheduling group table.
User response: Specify a different scheduling table name or scheduling table

library for the new scheduling group.
40402 Scheduling group with this scheduling table name already exists. Change
the scheduling table name.
group is already being used. Relevant when working with MPM.
User response: Specify a different scheduling table name for the new
scheduling group.

40403 A regular scheduling table with this name already exists. Change the
scheduling table name or the scheduling table library.
group is already being used for a regular scheduling table. Relevant when
working with MVS.
User response: Specify a different scheduling table name or scheduling table

library for the new scheduling group.
40404 A regular scheduling table with this name already exists. Change the
scheduling table name.
group is already being used for a regular scheduling table. Relevant when
working with MPM.
User response: Specify a different scheduling table name for the new
scheduling group.
40405 Lock Table Failed

Explanation: The scheduling table containing this job is locked. This operation
cannot be completed.
User response:
40406 Unauthorized user

Explanation: You are not authorized to perform this operation.
User response:
40407 Create scheduling group failed.

Explanation: The group name specified does not match the group name of the
scheduling group as follows: ${%s}${end}.
User response: Change the group name or the scheduling groups group name
so that they are identical as follows: ${%s}${end}.


40601 Server call failure

Explanation: A server failure has occurred while locating the job definition.
User response:

40801 GUI Server failed to load active net. (server, collection). (ERROR)
Explanation: X-Alert message. The GUI Server failed to load an active net for a
specific Control-M Server when opening a ViewPoint.
No jobs for the specified Control-M Server are displayed. If the problem is due
to an unavailable database, the GUI Server stops responding.
User response: Your database might be experiencing problems. If you cannot fix
the problems, run the Control-M/Enterprise Manager Health Check utility by
40802 GUI Server failed to load archived net. (server, collection, net). (ERROR)
Explanation: X-Alert message. The GUI Server failed to load an archived net
for a specific Control-M Server when opening a ViewPoint.
No jobs for the specified Control-M Server are displayed. If the problem is due
to an unavailable database, the GUI Server stops responding.
User response: Your database may be experiencing Customer problems. If you

cannot fix the problems, contact BMC Software Customer Support.
40803 GUI Server failed to load active net. Net table was not found in database.
(server, collection). (WARNING)
Explanation: X-Alert message. The GUI Server failed to load an active net for a
specific Control-M Server when opening a ViewPoint, because the table with
the net data does not exist in the database.
No jobs for the specified Control-M Server are displayed in the ViewPoint.


40804 GUI Server failed to load archived net. Net table was not found in database.
(server, collection, net). (WARNING)
Explanation: X-Alert message. The GUI Server failed to load an archived net for
a specific Control-M Server when opening a ViewPoint, because the table with
the net data does not exist in the database.
No jobs for the specified Control-M Server are displayed in the ViewPoint.
User response: No action is required.

40900 Periodic calendar (calendar_Control-M | calendar_name) used in periodic

statistics definition ' periodic_stats_def_name' was not found. (ERROR)
Explanation: X-Alert message. This message is related to the Control-M/EM
periodic statistics mechanism, which is using a periodic calendar that is not
defined. The periodic calendar may have been deleted after the periodic
statistics definition which uses it was created. The variables in this message are:
periodic_stats_def_name - the name of the periodic statistics definition
calendar_Control-M - the name of the Control-M where the periodic

calendar is defined
calendar_name - the name of the periodic calendar
Statistics for jobs which are related to this periodic calendar (according to the
Job Filter in the periodic statistics definition) are collected and displayed as
though these jobs are not related to any periodic calendar.
User response: Open the Periodic Statistics Manager (in Control-M/EM

Desktop, Tools => Periodic Statistics Manager). Locate the indicated periodic
statistics definition. Determine which periodic calendar this periodic statistics
definition needs to use. Relate this periodic statistics definition to a calendar
which is defined in Control-M/EM. Periodic calendars can be viewed, created,
uploaded and managed using the Calendar Manager (In Control-M/EM
Desktop, Tools => Calendar Manager).

This group includes messages for the Control-M product.

41001 The soft limit of resource parameter parameter is too low. Soft limit should
be equal to or larger than requested value.
Explanation: X-Alert message. The current soft limit of parameter is lower than
expected. The following OS resources are being checked: Number of file
descriptors, Data segment size and memory size.
Lack of computer resources might affect proper operation of Control-M/EM

processes.
User response: Update the relevant OS resource soft limit according to the value
indicated in the X-Alert message.
After updating the OS resource soft limit:
1 Stop the configuration agent using root menu => stop config agent.
2 Restart the configuration agent using root menu => start config agent.
3 Rerun the Control-M/EM GUI server and the BMC Batch Impact Manager
server.
41002 Both soft and hard limits of resource parameter parameter are too low.
Limits values should be equal to or larger than requested value.
Explanation: X-Alert message. The current hard and soft limits of parameter are
lower than required. The following OS resources are being checked: Number of
file descriptors, Data segment size and memory size.
Lack of computer resources might affect proper operation of Control-M/EM

processes.
User response: Update the relevant OS resource hard and soft limits according
to the value indicated in the X-Alert message. Hard limit changes require
reboot.
After making a hard limit change:
1 Stop the configuration agent using root menu => stop config agent.
2 Restart the configuration agent using root menu => start config agent.
3 Rerun the Control-M/EM GUI server and the BMC Batch Impact Manager
server.


50001 Invalid character at position position. Input: string.

Explanation: Job validation encountered an invalid character in one of a job's
fields.
position - the position of the character in the string
string - the entire string
User response: Change the value of the field.
50002 Field contains invalid value string.

Explanation: Job validation encountered an invalid value in one of a job's
fields.
In this message, string is the entire string.
50003 Delimiter character expected at index position. Input: string.

Explanation: An invalid character was used as a delimiter in one of a jobs
fields. A valid delimiter character was expected at a certain position in the
character string.
character - the expected delimiter character
50004 Maximum length for that value should be maxLength

Explanation: The value that was inserted into one of a job's fields exceeded that
fields maximum length.
In this message, maxLength is the maximum length of the value.

50005 Invalid value number - out of range.

Explanation: The numeric value that was inserted into one of a job's fields was
out of range.
In this message, number is the numeric value that the user entered.
50006 Invalid character character at position position. Input: string.

Explanation: Job validation encountered an value containing an invalid
character in one of a job's fields.
character - the invalid character
50007 The value contains invalid characters. Input string.

Explanation: Job validation encountered an value containing an invalid
character in one of a job's fields.
50008 The value is too short. Input string.

Explanation: Job validation encountered an value that was too short in one of a
job's fields.
50009 Invalid value: string

Explanation: Job validation encountered an invalid string in one of a job's
fields.

50010 String should not contain lower-case characters. Input string

Explanation: Job validation encountered lower-case characters in one of a jobs
fields.
50011 The field must have a value.

Explanation: Job validation discovered that a mandatory field was missing
from a job.
50012 Conflict: Job with value in field1 [and field2] field[s], cannot have value in
the following fields: field3, field4 ... fieldn
Explanation: There are conflicts in the job definition. If a specific field has a
certain value, then other fields must be left empty.
In this message, field is the name of each specific field.
User response: Change the value of the specified field.
50013 When the Tag Relationship is set to 'And', at least one scheduling tag must
be selected.
Explanation: Job validation discovered that the Tag Relationship in a job was
set to 'And', but no scheduling tag was selected.
User response: Specify at least one scheduling tag for the job, or change the tag
relationship to 'OR'.
50014 Field fieldName - The specified value is too long. Specify a shorter value.
Explanation: The value that you specified in the fieldName field is too long. This
occurs when the number of characters that is displayed on the screen is not the
actual number of bytes used for the value of the field. This might happen when
writing in Asian languages.
User response: Enter a shorter value. If the value is still too long, try again until
the value that you enter is accepted as a valid value.


60001 Failed to establish connection with Server

This error may be caused by any of the following cases:
- The Server name is invalid
- CORBA is not configured properly
- The CORBA Naming Service is not running
- The Control-M/Enterprise Manager Server is not responding
Explanation: You attempted to log on to Control-M/EM, but the logon failed.
Ensure that Control-M/Server has a valid name. If the name was selected
from a combo box and not entered manually, the name is valid.
Ensure that CORBA is configured properly and the config.xml file in the
installationDirectory/etc/domains directory is not corrupted.
Ensure that the CORBA Naming Service is running. If the logon was done
through the Login dialog box and the server name was selected from a
combo box, then the CORBA Naming Service is running.
Ensure that the Control-M/EM Server is running.
60002 Connection with the Server lost

This error may be caused in the following cases:
- The Control-M/Enterprise Manager Server is not responding or stopped
running
- The CORBA Naming Service is not running
Explanation: The connection with Control-M/EM has been lost.
Ensure that the CORBA Naming Service is running.
60003 Invalid username or password:

Make sure:
- The user is defined properly
- The given password is correct
Explanation: You attempted to log on to Control-M/EM, but the logon failed
because the user name or password is incorrect.
User response: Enter the correct user name or password.
60004 User is not authorized for that action

Explanation: You attempted to perform an action for which you do not have
authorization.
User response: Obtain the correct authorization from the Control-M/EM
system administrator.

60005 Your password is about to expire

Explanation: Your password is about to expire.
User response: Change the password.
60006 User account is locked

Explanation: You attempted to log on to Control-M/EM, but the attempt failed
because your account is locked. This might occur because:
The system administrator has manually locked your account.
You tried to log on to the system several times and failed, exceeding the
maximum number of failed logon attempts.
User response: Ask the Control-M/EM system administrator to unlock the

account.
60007 Login Failed: This error may be caused by any of the following: .
- Server is not running under context serverName
- CORBA configuration file is not configured properly.
(Edit and save the file. Restart the application to apply the new settings.)
In this message, serverName is the logical name of the server that was chosen
during logon. The default name is the name of the machine where Control-M/
Server is running.
Ensure that the CORBA Naming Service parameters that are specified in the
CORBA configuration file point to the correct Naming Service location. The
CORBA configuration file is located in the installationDirectory/etc/
domains directory, and its default name is config.xml.
Note
If this error message was received from the logon dialog box and not from the
command line, then instead of manually editing the configuration file, you can
press Advanced in the logon dialog box to check the CORBA Naming Service
parameters.

60008 Login Failed: CORBA initialization failed

This error may be caused by any of the following:
- CORBA Naming Service is not running.
- CORBA configuration file is not configured properly.
(Edit and save the file. Restart the application to apply the new settings).
Ensure that the CORBA Naming Service is running.
Ensure that the CORBA Naming Service parameters that are specified in the
CORBA configuration file point to the correct Naming Service location. The
CORBA configuration file is located in the installationDirectory/etc/
domains directory, and its default name is config.xml.
Note
If this error message was received from the logon dialog box and not from the
command line, then instead of manually editing the configuration file, you can
press Advanced in the logon dialog box to check the CORBA Naming Service
parameters.
60009 Login Failed:

Ensure Server under context serverName has the correct version.
Explanation: You attempted to log on to Control-M/EM, but the logon attempt
failed because there was a version mismatch between the Control-M/EM
Server and the application that you tried to run (for example, Control-M/EM
GUI or Control-M/Desktop).
In this message, serverName is the logical name of the server that was chosen
during logon. The default name is the name of the machine where Control-M/
Server is running.
User response: Verify the correct version and ensure that this version has been
installed.
60010 Login Failed:

This error may be caused by any of the following:
- User userName is not defined properly.
- The specified password is incorrect.
This might be due to one of the following reasons:
The userName user name is not defined properly.
The specified password is incorrect.

Ensure that you have entered the correct user name and password.
Ensure that your account has not been locked by the Control-M/EM system
administrator.
60011 Login Failed:

Password has expired
Explanation: You attempted to log on to Control-M/EM, but the logon failed
because your password has expired.
User response: Obtain a new password.

70001 Large amount of resources

Explanation: The list was loaded with more than ${%s} items.
User response: It is recommended to set a Refresh Filter.
70003 Form validation failed

Explanation: The form validation failed.
User response: Review and correct the errors.
70007 User not authorized

Explanation: The user is not authorized for the action pertaining to the GUI.
User response:
70008 Limit exceed

Explanation: The number of matches exceeds the current list limit.
A partial lists of results are displayed.
User response: Refine the filter criteria or increase the list limit by adjusting the
DeletedJobsLoadLimit system parameter.
70009 Field length exceeds limit

Explanation: The field ${%s} length exceeds the limit of ${%s} characters.
User response:

70011 GAS disconnection

Explanation: The connection with the Global Alerts Server has been closed.
User response:
70012 No jobs using control resource

Explanation: No jobs are currently using the control resource.
User response:
70013 View joblist not available

Explanation: Viewing a job list is supported only for jobs running on Control-
M for O/S versuib 6.1.00 or later.
User response:
70014 Invalid character

Explanation: The field ${%s} contains an invalid character.
User response:

74001 Login failed: Failed to login to Control-M Configuration Server 'serverName'

with user 'userName'
Explanation: An attempt to log on to the Control-M Configuration Manager
failed. This is often due to an incorrect user name or password, or selecting the
wrong server name from the list.
serverName - the name of the Control-M Configuration Manager to which

you are trying to log on.
userName - the name of the user who requested the action.
The Configuration Management Server displays this message and allows

another attempt to log on.
User response: Supply accurate logon details.

74002 Invalid database type: Actions on the database are not allowed since there
was a problem in getting database details
Explanation: The Configuration Management Server sent an invalid database
type to the client.
The Control-M Configuration Manager displays this message and does not
allow actions that involve interaction with the database.
74003 System parameter not selected: Please select a system parameter for action
Explanation: A system parameter was not selected for an action that requires
one to be selected.
In this message, action is the action that is missing the parameter.
The Control-M Configuration Manager displays this message. Normal

processing continues.
User response: Select a system parameter from the displayed list before
applying an action on it.
74004 Missing parameter

Explanation: A value is missing for a parameter.
User response: Assign a value for ${%s}.
74005 CMC Exception was raised: Action performed: action Exception message:
text
Explanation: The Control-M Configuration Manager raised an exception while
attempting to perform an action.
action - the name of the action on which the exception was raised.
text - the text of the displayed message.
The Control-M Configuration Manager displays this message, following some

unexpected system behavior.
User response: If the problem occurs again, contact BMC Software Customer
Support.
74006 Unknown Database type: type. Action will terminate.

Explanation: An attempt was made to perform an action on a database, but no
valid database was defined (see message 74002).

In this message, type is the unknown database type.
The Control-M Configuration Manager displays this message, and does not
allow actions that involve interaction with the database.
74007 Missing value

Explanation: A value is missing.
User response: Assign a value to ${%s}.
74008 Value out of range

Explanation: Value for ${%s} is out of range.
User response: Enter a value within the ${%s} and ${%s}.
74009 Invalid file name

Explanation: The file name ${%s} is invalid.
User response: Enter a valid file name.
74010 Action failed: Action action has failed for unknown reason. Please refer to
the application logs for additional information.
Explanation: An action failed, due to an unknown error.
In this message, action is the action that failed.
The Control-M Configuration Manager displays this message. Normal

User response: Check the application logs for additional details about the
failure.
74011 File already exists

Explanation: The file name specified already exists.
User response: Specify a different file name.
74013 Failed to send request to the Server: Failed action: action.

Explanation: The Control-M Configuration Manager client failed to send a
request to the Configuration Management Server.
In this message, action is the request action that failed.

Processing continues without completing the request. The action that failed is
displayed.
User response: Solve the problem according to the instructions displayed in the
message.
74014 Dialog validation error

Explanation: You clicked OK to exit a dialog box, but there are errors in the
dialog box. General errors in the dialog box are presented. Specific text fields
errors are displayed separately for each field.
The dialog box does not close.
User response: Correct the errors and try again.
74015 The connection to the server is lost. The connection will be restored when
available.
Explanation: The connection to the Configuration Management Server has been
lost.
The information message will be displayed by the Control-M Configuration

Manager.
User response:
74016 The connection to the server was restored.

Explanation: The connection to the Configuration Management Server has been
restored after it was lost.
The information message will be displayed by the Control-M Configuration

Manager.
User response:
74017 Control-M Configuration Manager: Your password has expired. Please refer
to the Control-M/EM documentation for further information.
Explanation: You try to log on to the Control-M Configuration Manager, but
were unsuccessful because your password has expired.
You cannot log on.
User response: Refer to Control-M/EM documentation for instructions on how

to obtain a new password.

74018 Control-M Configuration Manager: Your password will expire shortly.

Please refer to the Control-M/EM documentation for further information.
Explanation: You log on to the Control-M Configuration Manager, and receive
a message that your password will expire soon.
Normal processing continues.
User response: Replace your password as soon as possible.
74019 Control-M Configuration Manager: The account is locked.

Explanation: You try to log on to the Control-M Configuration Manager, but
the user account is locked.
You cannot log on.
User response: Contact your system administrator for assistance.
74020 Control-M Configuration Manager: Post login failed: reason

Explanation: Actions that are performed automatically after the logon to the
Control-M Configuration Manager failed.
In this message, reason is the reason for the failure.
Some Control-M Configuration Manager actions may not function properly.
74021 Action succeeded: Action: action, Message returned: text.

Explanation: A Control-M Configuration Manager action succeeded. The
server returned a message, which is presented to the user.
action - the name of the action that succeeded.
text - the text of the displayed message.
Normal processing continues.
User response: Click OK to confirm
74022 Duplicate component was identified

Explanation: A duplicate component was identified by the system. The
duplicate component will not be displayed.
User response:


75002 Failed to retrieve database host and port.

Explanation: Control-M/EM failed to retrieve the database hostname and port.
The Reporting Facility cannot open because it cannot connect to the Control-M/
EM database.
User response: Manually reset the hostname and port using the Control-M
75003 The Reporting Facility is unable to connect to the database.

Explanation: Either the database is not running or the OLEDB driver is not
installed or registered.
Check the log file for more information.
The Reporting Facility fails to connect to the Control-M/EM database.
The Reporting Facility cannot open because it cannot connect to the Control-M/
EM database. The possible causes are as follows:
1 The database is not running on the host and port specified in More Details.
2 The OLEDB driver is not installed or configured correctly.
3 Incorrect hostname and port were used for connection to the database.
User response: The following responses correspond to the above causes:
1 Start the database on the specified host and port.
2 Install the appropriate vendor OLEDB driver in the client computer.
3 Manually reset the hostname and port using the Control-M Configuration
Manager.


2
Control-M/Server messages
The following messages are issued by Control-M/Server. These messages may be
displayed in the Control-M/EM, Control-M/Server log, or in the files contained in
the Control-M/Server proclog directory.

This group includes messages for Control-M/Server.
5003 MAXRETRY REACHED FOR processID. SUPERVISOR IS SHUTTING DOWN

Explanation: Control-M is shutting down. The supervisor tried to activate the
Control-M processID process (Tracker, Submitter, and so forth) the number of
times specified in the Control-M system parameter MAXRETRY, and failed.
Control-M is shutting down.
User response: Restart Control-M. If the problem persists, notify your BMC
Software Customer Support representative.
5006 Control-M LOG CLEANUP ENDED. DAYS= days

Explanation: The New Day procedure performed a partial cleanup of the Control-
M log. Data for the specified number of days (days) is retained, as determined
by the value assigned to the Maximum Days Retained by Control-M Log
system parameter.
New Day processing continues.
5009 RESET CYCLIC FLAG TO NO

Explanation: A job is being modified to a non-cyclic job. A cyclic job that is
executing at the time the New Day procedure is started is changed to a non-

cyclic job. This is because Control-M cannot determine what action to take
regarding this job while it is executing.
The job completes its current cycle and is changed to a non-cyclic job.
User response: If the job should continue executing as a cyclic job, modify the
Cyclic job processing parameter accordingly.
5010 MIRRORING HAS FAILED

Explanation: A failure of the mirroring database server has occurred. If you
installed the database mirroring option for Control-M, the instance of database
server that handles the Control-M mirror database must be running whenever
Control-M is running. This error message is displayed if the mirroring database
Server fails. In this event, the mirror database is no longer synchronized with
the Control-M/Server database.
User response: You can allow Control-M to continue operating without
updating the mirror database. However, to restore the mirroring function, you
must stop Control-M normally and then rebuild the mirror database using the
Database Mirroring => Initialize Mirroring option on the Control-M Main
menu.
5011 Control-M LOG CLEANUP STARTED

Explanation: The Control-M log cleanup process has started.
The New Day procedure begins the partial cleanup of the Control-M log.
5014 Control-M AGENTS CLEANUP STARTED

Explanation: Control-M/Server started sending cleanup requests to all Control-
M/Agents. This action occurred during the New Day procedure or when
invoking the ctmagcln utility to all Agents. The request appears in the
following format:
ctmagcln -agent "*".
Control-M/Agents are requested to clean the old sysout and status/backup

files according to the Maximum Days to Retain Sysout Files parameter.
Control-M/Server starts sending the cleanup requests to all Control-M/Agents.
5015 Control-M AGENTS CLEANUP ENDED. DAYS= days

Explanation: Control-M/Server finished sending cleanup requests to all Control-
M/Agents. This action occurred during the New Day procedure or when

invoking the ctmagcln utility to all Agents. The request appears in the
following format:
ctmagcln -agent "*".
The specified number of days (days) that was sent to Control-M/Agents is

determined by the value assigned to the Maximum Days to Retain Sysout Files
parameter.
The execution of the ctmagcln utility finished successfully.
5016 Control-M AGENT agent WAS NOT CLEANED

Explanation: Control-M/Server failed to send the New Day cleanup request to
the specified Control-M/Agent (agent).
Control-M/Server attempts to send the request to the rest of the available Control-
M/Agents.
User response: Verify that the specified node ID is valid. Determine the cause of
the failed communication and correct it. If the problem persists, contact BMC
5017 Control-M AGENT(S) CLEANUP FAILED

Explanation: Control-M/Server failed to send the New Day cleanup request to
the requested Control-M/Agent or Agents. All Agents were not cleaned.
Execution of the ctmagcln utility fails.
User response: Check that AGSTAT directory is accessible on the file system.
5018 Control-M AGENT agent CLEANED SUCCESSFULLY. DAYS= days

Explanation: Control-M/Server successfully sent the New Day cleanup request
to the specified Control-M/Agent (agent). This action occurred when invoking
the CTMAGCLN utility to a specific Agent. The specified number of days (days)
that was sent to this Agent is determined by the value assigned to Maximum
Days to Retain Sysout Files parameter.
5019 STATISTICS INFORMATION CLEANUP STARTED.

Explanation: The New Day procedure or the ctmruninf utility started to
perform a partial cleanup of Control-M job statistics. When the Control-M
Statistics system parameter is set to Y, Control-M retains statistical data
regarding the executions of each job.

The statistics cleanup is performed.
5030 ACTIVE JOBS FILE DOWNLOADED TO Control-M/EM {STARTED | ENDED}

Explanation: The Active Jobs file has started/ended downloading to the Control-
M/EM workstation.
Control-M processes are suspended during the Active Jobs file download.
5034 STATISTICS INFORMATION CLEANUP ENDED. MODE= purgeMode.

LEAVE= purgeLimit
Explanation: The New Day procedure or the ctmruninf utility has successfully
performed a partial cleanup of Control-M job statistics. The specified MODE
(purgeMode) and LEAVE (purgeLimit) parameters are determined by the values
of RUNINF_PURGE_MODE and RUNINF_PURGE_LIMIT, respectively.
Execution of the ctmruninf utility finished successfully.
5035 STATISTICS INFORMATION CLEANUP FAILED

Explanation: Control-M/Server failed to perform a partial cleanup of Control-
M job statistics.
Execution of the ctmruninf utility stops.
User response: Check for database errors. If the problem persists, contact BMC
5040 NEW DAY PROCEDURE STARTED

Explanation: The New Day procedure has been submitted.
While this procedure is executing, all other Control-M processes are suspended.
5041 ACTIVE JOBS FILE CLEANUP ENDED

Explanation: The New Day procedure has finished cleaning up the Active Jobs
file. This message is issued at the end of the New Day procedure after the
Active Jobs File was cleaned from the old jobs and loaded with new job orders.

Control-M processing returns to Run status and starts inserting new jobs into
the Active Jobs file until the download to Control-M/EM is started.
5043 QUANTITATIVE RESOURCE INTEGRITY ERROR. resourceName n1 n2

Explanation: Due to an internal accounting problem, there is a discrepancy
between the actual usage count (n1) of the specified quantitative resource
(resourceName), and the calculated sum of the usage of this resource by all jobs
(n2) in the Quantitative Resource table.
5044 Control RESOURCE resourceName INTEGRITY ERROR. USED= n1,

CTLTAB= n2
Explanation: Due to an internal accounting problem, there is a discrepancy
between actual usage count (n1) of the specified control resource (resourceName)
by all submitted and not-ended jobs, and the calculated sum of the usage of this
resource by all jobs (n2) in the Control Resource table.
5045 Control RESOURCE resourceName INTEGRITY ERROR. MODE

EXCLUSIVE, USED n
Explanation: Due to an internal accounting problem, the specified control
resource (resourceName) appears to be used in Exclusive mode by more than
one job.
User response: Allow the jobs using this resource to terminate. If the problem
persists, contact BMC Software Customer Support.
5047 MAXWAIT PARAMETER EXCEEDED

Explanation: During the New Day procedure, this job was deleted from the
Active Jobs file because it exceeded the amount of days it should remain in the
Active Jobs file according to the MAXWAIT job definition value. Details about
the MAXWAIT parameter can be found in the Control-M Parameter Guide.
5048 NEW DAY PROCEDURE TIME HAS ARRIVED

Explanation: This message indicates that the New Day procedure should be
run at this time.
Active Jobs file download is stopped, so that the New Day procedure can begin.

5060 LAST RUN DATE OF USER userDaily NONEXISTENT. STATUS = status

Explanation: The last run date of the specified User Daily job (userDaily) could
not be retrieved from the database. Usually, this is because the User Daily job
was run for the first time. When a new User Daily job is run (that is, the User
Daily job is run for the first time), the last run date is nonexistent and therefore
cannot be accessed. At the end of this run (as at the end of all runs), a new last
run date is automatically generated.
If the User Daily job was run for the first time, no action is required.
If not, contact BMC Software Customer Support if you suspect that the User
Daily job was not ordered properly.
5061 USER DAILY userDaily STARTED

Explanation: This message indicates that the specified User Daily job
(userDaily) started.
5062 USER DAILY userDaily ENDED

Explanation: This message indicates that the specified User Daily job
(userDaily) finished ordering the jobs associated with it, according to their
scheduling criteria.
5063 CALENDAR calName, NOT FOUND OR NOT COMPLETE

Explanation: The user attempted to download the calName calendar, but either
the calendar is not found or it does not contain all the relevant years in the Control-
M/Server database.
The calendar is not downloaded.
User response: Use Control-M/EM to either create the calendar or to verify that
all relevant years appear in the calendar.
5064 USER DAILY userDaily STOPPED - DATE PROBLEM. LAST lastDate, NEXT
nextDate
Explanation: The specified User Daily job (userDaily) cannot run due to a date
inconsistency.
The inconsistent date can be due to one of the following reasons:
The User Daily job has already been run today.
The last running date (lastDate) of the User Daily job is later than today's
date (nextDate).

The User Daily job stops executing.
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 today's date, run
the ctmudlst utility to modify the last running date according to your
requirements.
5065 ORDERED %s: jobNumber; DAILY userDaily, ODATE odate

Explanation: where %s is one of the following values:
JOB
Sub table
SMART table
The specified job (jobNumber) with an ODATE of odate has been inserted into
the Active Jobs file by the specified User Daily job (userDaily).
5066 DAILY userDaily FAILED TO ORDER JOBNAME jobName

Explanation: The specified User Daily job (userDaily) failed to order the
requested job (jobName).
The failure to order jobs can be can be due to one of the following:
Database problem (communication problem, space problem, and so on)
Data inconsistency in the database
Security violation
The scheduling criteria of the job do not match its ordering date
The system action depends on the cause of the problem:
If the problem is a security violation for a specific job, or mismatched

scheduling criteria, then Control-M continues to check/order the jobs that
relate to this User Daily job.
If it is a database problem or any kind of internal problem, the User Daily

job might stop ordering the rest of the jobs.
User response: Check the cause of this message:

Check the security definition for this table.
Check the alert definition for jobs that are not ordered due to their
scheduling criteria. For more information, see the NOT_ORDERED_
JOB_ALERT configuration parameter in the Control-M Administrator Guide.
Check the database error logs to search for any potential problem.
If none of the above causes match the problem and the problem persists,
5067 ONE OR MORE JOBS IN DAILY userDaily WERE NOT ORDERED

Explanation: At least one or more jobs within the specified User Daily job
(userDaily) were not ordered because that their scheduling criteria did not
match the specified ordering date. For more information, see the
NOT_ORDERED_ JOB_ALERT configuration parameter in the Control-M
Administrator Guide.
User response: If you suspect that a specific job should have been ordered that
day, check its scheduling criteria.
If you wish to disable this message from appearing again, check the option in
the NOT_ORDERED_JOB_ALERT configuration parameter.
5080 FAILED TO SUBMIT JOB memName. reason

Explanation: The requested job (memName) could not be submitted due to a
specific reason (reason). The reasons include:
For UNIX platforms:
Mem Lib memLib does not exist - The path/library was not found.
Mem Name memName does not exist - The script was not found.
User userName does not exist - There was a security violation.
Owner ownerName does not exist - There was a security violation.
Owner ownerName is not allowed to execute this script - There was a

security violation.
The script scriptName does not have execute permissions - There was a
security violation.
For Windows platforms:
There are currently no logon servers available to service the logon request.
Logon failure: unknown user name or bad password.

Logon failure: user account restriction.
Logon failure: account logon time restriction violation.
Logon failure: user not allowed to log on to this computer.
Logon failure: the specified account password has expired.
A specified privilege does not exist.
A required privilege is not held by the client.
The name provided is not a properly formed account name.
The specified user already exists.
The specified user does not exist.
Logon failure: the user has not been granted the requested logon type at
this computer.
A specified logon session does not exist. It may have been terminated.
For all Platforms:
Control-M/Server hostName is not authorized to run jobs on this Agent -

the Control-M/Server specified is not listed in the Authorized Control-M
Servers list for the Agent platform.
The job is not submitted.
User response: Examine the job processing definition to verify the information
that caused the problem. Either make the necessary corrections, provide the
necessary security authorizations, or add the Server platform to the Authorized
Control-M Servers list. Rerun the job.


5100 ENDED AT time. OSCOMPSTAT rc. RUNCNT runCounter

Explanation: This message indicates that the job ended its execution at the
specified time (time) with the given return code (rc) and the given run count of
the job (runCounter).
User response: No action is required, unless the return code of the job is not the
expected one. In that case, you should check the job log in order to find the
reason for the failure.
5101 STARTED AT startRun ON nodeID

Explanation: This message indicates that the job began executing at the
specified time (startRun) on the specified Agent platform (nodeID).
5102 DISAPPEARED AT time. RUNCNT runCounter

Explanation: After the job was submitted, it could not be located by the system
and therefore the jobs status changed to Disappeared at the specified time
(time). The job's status, and the location of its log, cannot be determined.
The job may have been stopped by a user, or the Agent platform on which the
job was running may have been rebooted.
The job is assigned the completion status NOTOK.
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.
5105 SUBMITTED TO nodeID

Explanation: This message indicates that the job was submitted for execution to
the specified Agent platform (nodeID).
5106 DISAPPEARED AT dateTime. RUNCNT count. node name IS status

Explanation: Either the user changed the status of the node to Disabled or the
job has been in unknown state for more than UNKNOWN_TIMEOUT seconds.
As a result, the Control-M/Server changed the state of the job submitted to that
node to Disappeared, and the status to Ended NOTOK.
dateTime - the date and time that the job disappeared.
count - the jobs run count.
node - one of the following:
AGENT

REMOTE HOST
Agent used by the remote host
ACCOUNT
name - the name of the agent, remote host, or agent used by the remote host,
agent used by the remote host, or CM Account name.
status - one of the following:
DISABLED
UNAVAILABLE
5110 LIBMEMSYM FILE pathName NOT FOUND

Explanation: The file that is specified in a %%LIBMEMSYM AutoEdit variable
(pathName) was not found. %%LIBMEMSYM can be used to refer to a list of
AutoEdit assignments contained in a file in the data center. The file referred to
in this instance was not found.
User response: Determine why the file was not found. Create the file or correct
the pathname specified for the AutoEdit variable.
5120 %s STATE CHANGED TO %s

Explanation: This message indicates that Control-M has changed the job's state
to jobState.
Control-M/Server continues to handle the job according to its new state.
%s may have one of the following values: JOB, Sub table and SMART table
5132 STATUS SET TO jobStatus AS A RESULT OF DO {OK | NOTOK | RERUN}

Explanation: This message indicates that the completion status of the job
(jobStatus) was changed as a result of DO OK, DO NOTOK, or DO RERUN post-
processing actions.
5133 ENDED OK
Explanation: This message indicates that the job has completed 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.

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 and sysout to determine why the job
terminated with a status of NOTOK.
5135 AUTHORIZATION PROBLEM - DOFORCE

Explanation: The DO FORCEJOB action of a job has failed, because the jobs
owner is not allowed to force the job specified in the DO FORCEJOB action.
The job is not forced. If the Jobname field of the DOFORCEJOB action is blank,
processing continues with the next job in the table.
5136 JOB STATE CHANGED TO RETRY - SUBMIT

Explanation: Control-M attempted to submit the job to the Control-M/Agent
platform, but the submission failed due to the Agent not responding. The job's
state was changed to Retry and the job was resubmitted.
Control-M attempts to submit the job.
User response: Check the communication between the Control-M/Server and

Agent. Check for error messages in the Control-M proclog directory.
5164 DUMMY. STATUS CHANGED TO OK

Explanation: This message indicates that the job was assigned a status of Ended
OK because it is a dummy job.
5166 INVALID TIME ZONE timeZone. STATUS CHANGED TO FAILED TO SUBMIT

Explanation: The Time Zone parameter (timeZone) has an invalid value. Valid
time zone values are listed in the timezone.dat file.
The job status is changed to Failed to submit.
User response: Specify a valid time zone or add the new time zone to the
timezone.dat file.

5199 CONDITION 'condName' 'condDate' ALREADY EXISTS

Explanation: This message indicates that this job tried to add a prerequisite
condition (condName) with the indicated order date (condDate), but this
condition already exists with the specified date in the database.
The condition is not added because it already exists.
User response: Check the condition name and the order date. Use the ctmlog
utility in order to check which job or action added this condition.

5201 SHOUT TO destination PERFORMED

Explanation: A Shout message was issued to the specified destination
(destination).
5202 SHOUT TO destination FAILED

Explanation: An attempt to issue a Shout message to the specified destination
(destination) was not successful. Possible reasons for the failure are that the
terminal is not connected or an invalid destination was specified.
The Shout message is not issued.
User response: Check the validity of the destination.
5203 Control RESOURCE resourceName RESERVED

Explanation: The control resource defined for this critical job (resourceName) is
not available yet (it may be in use by another job); therefore, the system has
reserved it for the specified critical job.
The job remains in Wait Resource state until the control resource becomes
available and allocated to this job.
5204 Control RESOURCE resourceName ALLOCATED. MODE: {S | E}

Explanation: The control resource resourceName has been allocated for the
specified job in Shared (S) or Exclusive (E) mode.

5206 Control RESOURCES RELEASED

Explanation: All control resources allocated for the job order have now been
released, because the job has terminated.
The control resource is now available for other jobs in the system.
5207 QUANTITATIVE RESOURCE resourceName QUANTITY resourceQuantity

RESERVED
Explanation: Quantitative resource resourceName has been reserved in quantity
resourceQuantity for the specified critical job, and is ready to be allocated. The
job will wait until all the resource quantities are available for its run, and will
then be executed.

ALLOCATED
Explanation: Quantity resourceQuantity of quantity resource resourceName has
been allocated for this job.
5209 CONDITION condName condDate ADDED

Explanation: Following job termination, the specified prerequisite condition
(condName), with the matching date reference (condDate), has been added to the
Control-M/Server database. This condition is now available for other jobs in
the system.
5210 CONDITION condName condDate DELETED

Explanation: Following job termination, the specified prerequisite condition
(condName), with the matching date reference (condDate), has been deleted from
5211 { FORCE | ORDER} JOB FAILURE. JOB jobName, TABLE tableName

Explanation: An operation to order or force the jobName job in the tableName
table failed.
The failure may have been due to problems with the job processing definition
(for example, job not found), security verification problems, scheduling criteria
of the job does not match, and so on.

The job is not ordered or forced.
User response: Check the job scheduling criteria, and check Control-M/Server
and operating system security restrictions.
5212 JOB jobName, TABLE tableName { FORCED | ORDERED}

Explanation: The jobName job, in the tableName table, was FORCED or
ORDERED into the Active Jobs file.
The job is inserted into the Active Jobs file.
5214 QUANTITATIVE RESOURCES RELEASED

Explanation: All allocated quantitative resources for the specified job have been
released.
The control resource is now available for other jobs in the system.
5215 ALL RERUNS HAVE BEEN PERFORMED. MAXRERUN = number

Explanation: When the job's completion status is set to Rerun using the Do
Rerun parameter, Control-M checks the number of reruns specified in the
Maximum parameter. If the number in the Maximum parameter is greater than
the number of reruns that have already been performed for the job, a rerun
(automatic rerun) process is performed for the job. This message indicates that
the all the reruns have been performed and the job exceeded the number value
of the maxrerun parameter.
The job will not continue to rerun, and will move to a post-processed state.
5217 table '%s', job name '%s' not found

Explanation: One of the following actions occurred:
A Control-M/EM user attempted to force a job using the menu option in the
Control-M/EM window
A Control-M job attempted to execute a DO FORCEJOB statement as part of

its post-processing parameters.
The attempt to run job jobName located in table tableName failed.

Either the table specified in tableName does not exist in the Control-M/Server
database, or the job specified in jobNname does not exist in the specified table
tableName.
%s can have one of the following values: Job, Sub table or SMART table
User response: Determine the source of the problem (missing job processing
definition, missing Scheduling table, incorrectly specified DO FORCEJOB
statement, and so on). Correct the problem and try to force the job again.
5219 CYCLIC ATTRIBUTE REMOVED DUE TO DOSTOPCYCLIC

Explanation: Cyclic jobs normally run a regular intervals for as long as
specified and the scheduling criteria are satisfied.
A cyclic job was terminated due to related On Statement/Code criteria that is

satisfied and performed a Do Stop Cyclic action that prevents future iterations
of the current cyclic job.
5220 STATUS OF AGENT PLATFORM nodeID CHANGED TO AVAILABLE

Explanation: Control-M changed the communication status of the Agent
platform identified by nodeID from Unavailable to Available. The
communication status of the Agent platform was changed from Available to
Unavailable due to failed communication. As a result of resumed
communication, the status of the Agent platform was returned to Available.
Control-M resumes sending job handling requests to the Agent platform.
5222 STATUS OF AGENT PLATFORM nodeID CHANGED TO UNAVAILABLE

Explanation: One of the following actions occurred:
Control-M changed the communication status of the Agent platform

identified by nodeID from Available to Unavailable due to repeated
communication timeouts. A communication failure has occurred between
the Server platform and the specified Agent platform.
nodeID was not specified correctly in the job processing definition or in the
node group.
Control-M tries to communicate with the Agent platform but does not send job
handling requests to the platform. If Control-M succeeds in communicating

with the Agent platform, the status of the platform is returned to Available;
otherwise, the status of the platform is changed to Disabled.
User response: Verify that the node ID specified in the job processing definition
or in the node group is valid. Determine the cause of the failed communication
and correct it.
5223 STATUS OF AGENT PLATFORM nodeID CHANGED TO DISABLED

Explanation: A user changed the communication status of the Agent platform
identified by nodeID to Disabled.
Control-M no longer attempts to communicate with the Agent platform and

does not send job handling requests to the platform.
User response: When desired, use the Agent Status menu via the ctm_menu
utility to change the status of the Agent platform to Available.
5231 CYCLIC ATTRIBUTE OF THIS JOB CHANGED DUE TO STATUS=NOTOK

Explanation: The Control-M/Server default behavior is to rerun a cyclic job in
case that the job ended NOTOK. The CYCLIC_RERUN parameter in the Control-
M/Server configuration determines whether a cyclic job should be rerun or not
if that job ends NOTOK.
This message indicates that the job ended NOTOK and because the
CYCLIC_RERUN parameter is set to NOTOK, the cyclic attribute of the job is
changed and the job will not rerun.
The job state is changed to post-processed and will not rerun.
5250 ACCESS TO TABLE tableName IS NOT ALLOWED TO USER userName

Explanation: A User Daily job (using the ctmudly utility) attempted to order a
job from a table (tableName) which is unauthorized to be ordered by the
specified user (userName). This is a security violation message.
Access to the scheduling table is denied to the User Daily job.
User response: Verify/modify user authorizations pertaining to the specific

scheduling table.
5251 THIS OWNER IS NOT AUTHORIZED TO EXECUTE THE JOB SCRIPT

Explanation: The owner of the job processing definition is not authorized to
execute the script file specified by the job processing parameters.

The job terminates with a NOTOK status.
User response: Either modify the script file protection accordingly, or grant the
owner execution privileges.
5252 USER userName NOT AUTHORIZED FOR OWNER ownerName

Explanation: The userName user tried to perform an action on a job that is
owned by the ownerName owner, but in the Control-M/Server security
definition, this user is not authorized to perform this action for this owner.
The action fails.
User response: Check the Control-M/Server security definition.

5301 SERVER INTERNAL ERROR TYPE type

Explanation: An internal error has occurred on the Control-M/Server side
during a request for the EM user side to upload/delete a table/calendar.
The user request is rejected.
User response: Try to perform the request again. If this error persists, contact
5302 INCOMPATIBLE GATEWAY VER. DATA CENTER VER. CTMServerVersion.

W.S. VER. gatewayVersion
Explanation: There is an incompatibility between the Control-M/Server
version (CTMServerVersion) and the Control-M version (gatewayVersion) which
the Gateway is defined.
During the SYNC operation between the Control-M/EM Gateway and Control-
M/Server, the Control-M/Server checks that the Gateway version is a
compatible version.
To achieve communication between the Control-M/EM Gateway and Control-

M/Server, the Control-M version that is defined in Control-M/Enterprise
Manager through the Tools => Communication => Administration => Control-
M Definition => Version sequence should match the Control-M/Server version
where the Gateway is trying to connect.

The Control-M/EM Gateway shuts down and communication between Control-

M/Server and Control-M/EM is not established.
User response: Set the Control-M/EM Gateway version to match the Control-M/
Server version. This can be done through the Tools => Communication =>
Administration => Control-M Definition => Version sequence in Control-M/
Enterprise Manager.
5304 CANNOT {DELETE | FREE} <%s> orderNumber - <%s> NOT HELD

Explanation: A delete or free action was requested for this job orderNumber, but
because this job is not in Held status, it cannot be deleted or freed.
The request is rejected.
<%s> can have one of the following values: Job, Sub table or SMART table
User response: Hold the job. Wait until the Requested Held status is changed to
Held, and then use the Free or Delete option.
5305 ACTIVE JOBS FILE IS LOCKED, TRY AGAIN LATER

Explanation: An attempt to perform an action such as Why/View statistics,
view JCL/Edit JCL, View Doc, and so on, on the Active Jobs file failed due to
the fact that currently it is locked by another user or by the Control-M Monitor.
User response: Try again later to perform the desired action.
5306 CANNOT action JOB orderNumber - JOB DOES NOT EXIST

Explanation: The specified job (orderNumber) does not exist or could not be
found in the Control-M/Server database, and therefore the requested action
(action) can not be performed on it.
User response: Check that this specific job exists in the Control-M/Server. If the
job does not exist in the Control-M/Server but you do see it in Control-M/EM,
check why the Control-M/EM data and Control-M/Server data are not
synchronized by trying to perform a force download. If the job does exist in the
Control-M/Server database with the same status as displayed in Control-M/
EM and this message persists, contact BMC Software Customer Support.
5309 CANNOT HOLD <%s> orderNumber - <%s> ALREADY HELD

Explanation: A Hold request was performed for this job (orderNumber), but the
job is already in Held status.
The Hold request is rejected.

<%s> can have one of the following values: Job, Sub table or SMART table
User response: Use the ctmpsm utility to check the status of the job in Control-
M/Server. The Control-M/EM data and the Control-M/Server data may not be
synchronized, and therefore you are not seeing updated statuses of jobs in
Control-M/EM. Try to perform a force download in order to update and check
the communication between the Control-M/Server and Control-M/EM.
5310 JOB orderNumber IS NOT WAITING FOR CONFIRMATION

Explanation: A confirmation request was performed for the requested job
(orderNumber), but the job does not have Wait Confirmation status. A
confirmation request is valid only for jobs that are in Wait Confirmation status.
The confirmation request is rejected.
User response: Use the ctmpsm utility to check the status of the job in the Control-
M/Server. The Control-M/EM data and the Control-M/Server data may not be
synchronized, and therefore you are not seeing updated statuses of jobs in
Control-M/EM. Try to perform a force download in order to update and check
the communication between the Control-M/Server and Control-M/EM.
5311 ERROR PROCESSING XML REQUEST. xmlMessage

Explanation: The request could not be processed due to xmlMessage.
The Control-M/Server encountered a problem while receiving or reading XML

data being transferred from Control-M/EM to the Control-M/Control Module.
User response: Check previous messages and messages in the proclog directory.
If the problem persists, contact BMC Software Customer Support
5312 GATEWAY OLDER THAN 613 CANNOT CONNECT TO DATA CENTER 613
OR ABOVE
Explanation: The Gateway version is not compatible with the Control-M/
Server version.
This Gateway version that is trying to connect to a Control-M/Server version

6.1.03, but this Gateway version is a earlier version, and therefore the
connection was not established. Control-M/Server version 6.1.03 can be
connected only to Control-M/EM version 6.1.03 or later.
Communication between Control-M/Server and Control-M/EM can not be

established.

1 Check that the Control-M/EM version is 6.1.03 or later. If it is not, upgrade it.
2 Use the Tools => Communication => Administration => Control-M

Definition => Version sequence in Control-M/EM to set the version to 6.1.03
or later.
5315 QUANTITATIVE RESOURCE resourceName IN USE - CANNOT DELETE

Explanation: An attempt was made to delete quantitative resource
resourceName, but this attempt failed because the resource is currently in use by
a Control-M job. An Active Job in Control-M is using a certain quantity of the
quantitative resource, and therefore the resource cannot be deleted.
The Delete request is rejected.
User response: Wait until the job finishes executing and the quantitative
resource is not in use by any other job, then try again to perform the Delete
action.
5316 QUANTITATIVE RESOURCE resourceName ALREADY EXISTS

Explanation: An attempt was made to add quantitative resource resourceName,
but this quantitative resource already exists in the Control-M/Server database.
The Add request is rejected.
5317 QUANTITATIVE RESOURCE resourceName DOES NOT EXIST

Explanation: A request to delete, update, or allocate quantitative resource
resourceName was performed by a Control-M/EM user, but this quantitative
resource does not exist in the Control-M/Server database.
It is possible that between the time the request was sent from the Control-M/
EM Control Application and the time it was processed by the Data Center
Gateway, another Control-M/Server action or Control-M/EM user deleted this
quantitative resource from the Control-M/Server Resources table.
The requested action is rejected.
User response: Verify that the Control-M/EM and Control-M/Server data are
synchronized.
To check the quantitative resource list in the Control-M/Server database, use

the ecaqrtab utility.

5318 VALUE OF CHANGE IS OUT OF RANGE

Explanation: A request to update a quantitative resource quantity was
performed by a Control-M/EM user, but the result of the update operation is
either negative or more than the total value.
The update request is rejected.
User response: Check that the value that was inserted is valid, and correct the
input. If you verify that your input is valid but the problem persists, contact
5319 SYSOUT DOES NOT EXIST FOR THIS JOB

Explanation: A Control-M/EM user performed a request to view a jobs sysout,
but this specific sysout does not exist and therefore cannot be viewed.
Either no sysout has yet been generated, or the existing sysout has been deleted
(manually or automatically) after exceeding the number of days that is
specified in the Maximum Days to Retain Sysout Files Control-M/Server
parameter.
The requested is rejected.
5321 STATISTICS DO NOT EXIST FOR THIS FILE/MEMBER

Explanation: A Control-M/EM user performed a request to view a jobs
statistics, but Control-M/Server failed to retrieve the statistic data of the job
from the database.
The requested is rejected.
User response: Search for more errors that may explain the core of the problem.
Check the files in the Control-M/Server proclog directory and the database
error log.
5323 SECURITY PROTECTION VIOLATION

Explanation: A Control-M/EM user tried to perform an unauthorized request
action.
This message is issued by the Control-M/Server security mechanism.
The request may be rejected for one or more of the following reasons:
This Control-M/EM user does not have a user account on the Control-M/
Server platform.

This Control-M/EM user does not have the required authority from the
operating system on the Control-M platform to perform the requested
function.
This Control-M/EM user does not have Control-M/Server authorization to

perform the requested function.
For more information about the Control-M/Server security mechanism, see the
Security chapter in the Control-M Administrator Guide.
5327 CANNOT POSTPROCESS JOB. JOB HELD BY SYSTEM

Explanation: The post-processing action of this job could not be performed;
therefore, Control-M/Server changes the status of this job to HOLD.
There can be several reasons for the failure to perform the post-processing
action, such as lack of disk space, a database problem, or an internal Control-M
problem, but check the Control-M logs in order to verify the cause of the problem.
The jobs post-processing is not performed and job status is changed to HOLD
by the Control-M/Server.
A message about the fact that the job is HELD is send to the job log.
User response: Search for more errors that may explain the core of the problem.
Check the files in the Control-M/Server proclog directory and the database
error log.
In case you cannot find the cause for this problem in the logs and this error
5328 JOB orderNumber IS NOT IN EXECUTION STATE

Explanation: Control-M/EM tried to perform a kill action on the orderNumber
job, but the action failed due to the fact that the job is not in executing mode. A
kill action terminates a job that is currently running, together with its processes;
this action terminates only jobs that are currently executing.
User response: Make sure that the kill action performed on jobs that are in
executing mode. It is possible that Control-M/EM is not refreshed, and
therefore the jobs status in Control-M/EM is not identical to the Control-M/
Server status.
Use the Control-M/Server ctmpsm utility to check the jobs status.

5330 AGENT nodeID/group IS UNAVAILABLE. REQUEST action FAILED

Explanation: A user request was not executed because of failed communication
with the Agent platform(s), or because the status of the Agent platform is
Unavailable or Disabled.
The user attempted to use one of the following options for the job:
View Sysout
View Documentation
View JCL/Script
Edit JCL/Script
Control-M/Server was not able to pass the request to the Agent platform
because of failed communication, or because the status of the Agent platform is
Unavailable or Disabled.
The user request is not executed.
Verify that the status of the Agent platform is not Disabled.
Determine the cause of the failed communication and correct it.

DEFINED
Explanation: A Control-M/EM user added the resourceName quantitative
resource, with a total quantity of resourceQuantity, to the Control-M/Server
database.
The quantitative resource is added to the Control-M/Server resources database.
5352 QUANTITATIVE RESOURCE resourceName DELETED

Explanation: A Control-M/EM user deleted the resourceName quantitative
resource.
This quantitative resource is removed from the Control-M/Server resources

database.

5353 QUANTITATIVE RESOURCE resourceName QUANTITY INCREASED BY

resourceQuantity
Explanation: The maximum quantity of the resourceName quantitative resource
has been increased by quantity resourceQuantity, due to a Control-M/EM user
request.
The new quantity value of this resource is updated in the Control-M/Server

resources database.
5354 QUANTITATIVE RESOURCE resourceName QUANTITY DECREASED BY

resourceQuantity
Explanation: The maximum quantity of the resourceName quantitative resource
has been decreased by quantity resourceQuantity, due to a Control-M/EM user
request.

resources database.

RELEASED
Explanation: The number of units (resourceQuantity) of the resourceName
quantitative resource that were allocated by a job have been released and are
now available for other jobs that require this resource.

resources database.
5358 FILE NOT FOUND

Explanation: A Control-M/EM user performed a request to view or edit JCL or
view doc, but the file (document or script file) does not exist.
User response: Verify the following:
the existence of the script file and script path that are defined in the job
definition.
the existence of the file and path on the Control-M/Agent platform to which
the job was submitted.

5359 DIRECTORY NOT FOUND

Explanation: A Control-M/EM user performed a request to view or edit a JCL
script or to view a document, but the directory that contains the requested file
(document or script file) does not exist.
User response: Verify the following:
the existence of the directory and path (doclib or memlib) that is defined in
the job definition.
the existence of the directory and path on the Control-M/Agent platform to

which the job was submitted.
5360 SECURITY VIOLATION

Explanation: A Control-M/EM user tried to perform an unauthorized request
action. This message is issued by the Control-M/Server security mechanism.
The request may have been rejected for one or more of the following reasons:
The Control-M/EM user did not have a user account on the Control-M/
Server platform.
The Control-M/EM user did not have the required authority from the
operating system on the Control-M platform to perform the requested
function.
The Control-M/EM user did not have Control-M/Server authorization to

perform the requested function.
For more information about the Control-M/Server security mechanism, refer to

the chapter about Security in the Control-M Administrator Guide.
5361 THE SELECTED JOB/GROUP CANNOT BE DELETED DUE TO ITS

CURRENT STATE.
Explanation: A Control-M/EM user tried to delete a job, but this job is not in a
state in which it can be deleted. For example, a job cannot be deleted when it is
in Executing state.

5362 QR:'resourceName', QRTOTAL: maxQuantity {decreased | increased}

(resourceQuantity)
Explanation: Due to a user request, the maximum quantity of the resourceName
Quantitative resource has been decreased or increased by specified quantity
(resourceQuantity).
The maximum number of units of resourceName Quantitative resource

decreased or increased to maxQuantity.
5363 QR:'resourceName', QRTOTAL: maxQuantity defined

Explanation: The user defined a new Quantitative resource called
'resourceName', and set the maximum availability for this resource to
maxQuantity.
The resource is added to the Control-M resources database.
5364 QR:'resourceName' deleted

Explanation: This message indicates that, due to a user request, the
resourceName Quantitative resource has been removed from the Control-M
resources database.
The resource is deleted from the Control-M resources database.

5401 HELD BY USER userName

Explanation: This message indicates that a Hold request was performed for this
job by a specified user (userName), and as a result the job is now in Hold state.
The system performs one of the following actions:
If the job has not yet started to execute, it is prevented from executing even
after all submission criteria are satisfied. The job remains in this state until it
is released using the Free option.

Any job that is executing when a hold request is performed will remain in
Executing status until it is freed.
If the job has finished executing, it cannot be manually rerun until released
by means of the Free option.
5402 FREED BY USER userName

Explanation: This message indicates that the job associated with the message
was released from its held state by a specified user (userName).
The system resumes the job processing at whatever point it was stopped by the
Hold option.
5403 DELETED BY USER userName

was marked as deleted by the specified user (userName).
The system performs one of the following actions:
If the job has not yet started to execute, it is prevented from executing even
after all submission criteria are satisfied. The job remains visible until after
the cleanup of the Active Jobs file, either during the New Day procedure or
when cleanup is manually requested.
If the job has finished executing, it cannot be manually rerun after it is deleted.
5404 RERUN BY USER userName

was rerun by the specified user (userName).
The system reruns the job.
5405 CONFIRMED BY USER userName

Explanation: This message indicates that the job associated with the message,
which was waiting for confirmation prior to submission, was confirmed by the
specified user (userName).

The system checks the job submission criteria and handles the job accordingly.
5407 CREATED BY USER userName

was placed in the Active Jobs file by the ctmcreate utility.
The job is added to the Active Jobs file, and is handled according to its
submission criteria.
5408 UNDELETED BY USER userName

was undeleted from its Delete state by the userName user.
The Undelete option causes the job to revert to its appearance and state before
the job was deleted.
5409 JOB KILLED BY USER userName

Explanation: The Kill option was performed by the userName user on the job
that is associated with this message. The Kill option terminates a job (and its
processes) that is currently running.
The job and its process are terminated, and the jobs status changes to NOTOK.
5410 FORCED OK BY USER userName

Explanation: This message indicates that the status of the job that is associated
with this message was forced to be OK by the specified user (userName).
The job status was changed to OK.


5500 SERVICE NOT ALLOWED NOW - reason

Explanation: A user request was sent from Control-M/EM to Control-M/
Server to update this jobs details (zoom and save actions), but this update
action could not be performed temporarily due to the fact that the job is in
reason state.
User response: Wait for the condition described in reason to pass, then reissue
the request.
5506 OPERATION NOT SUPPORTED BY AGENT orderNumber

Explanation: A Control-M/EM user performed a Kill request, but the request
was rejected due to the fact that the Control-M/Agent version to which the job
was submitted does not Support the Kill option. For example, Control-M/
Agent version 2.2.4 does not Support the Kill option.
5507 AGENT ENCOUNTERED ERROR { orderNumber| Write to File Failed }

Explanation: A Control-M/EM user performed a Kill, View JCL/Script, or Edit
JCL/script request for a job, but the request was rejected due to a problem that
was encountered with the Control-M/Agent to which the job was submitted.
The problem can be an internal problem (while trying to transfer the request) or
due to the fact that this Control-M/Agent is unavailable.
1 Check that the Control-M/Agent on which this job runs in is in Available

status.
2 Try to resubmit the request. If it fails again, check for any relevant error
message in the proclog directory of the Control-M/Server and the Control-M/
Agent.
3 In case the problem persists, contact BMC Software Customer Support.
5508 MAXIMUM CONCURRENT SESSIONS LIMITATION REACHED

Explanation: Control-M/Server has reached the maximum concurrent
persistent sessions limitation with Control-M/Agents.

There was either a new request from Control-M/Server to Control-M/Agent or

a new request from Control-M/Agent to Control-M/Server that generated a
new persistent connection session.
1 Increase the value of the Maximum Concurrent Sessions parameter by using

the Parameter Customization =>Default Parameters for Communicating
with Agent Platforms sequence in the ctm_menu utility.
Note
A persistent session uses an extra file descriptor. When you increase this
parameter, you need to make sure you have enough file descriptors per process
defined in your system. Please consult your system administrator.
2 Decrease the amount of persistent connection session Control-M/Agents

that are defined in this Control-M/Server.
5520 Perform rollback in function: functionName

Explanation: The Control-M/Server database failed to perform a requested
action within the database, and therefore a rollback action was performed.
Rollback rolls back the current transaction and causes all the updates made by
the transaction to be discarded.
The rollback action canceled the proposed changes in a pending database

transaction.
User response: Check for error messages in the proclog directory and in the
database error logs in order to determine the cause for the database rollback
action.
5522 ERROR: RESOLVED VALUE FOR paramName IS LONGER THAN number

CHARACTERS
Explanation: The Control-M/Server is unable to resolve AutoEdit variables for
the paramName parameter, since the calculated value is longer than the
permitted number (number) of characters.
The request fails.
User response: Modify the request so that the resolved AutoEdit variable that
appears in this message will fit the permitted number of characters.
5524 START OF TRACKING ALL ACTIVE JOBS

Explanation: The TR process (Tracker) started to perform its Track All action.
Track All is a Control-M/Server mechanism that periodically tracks all the jobs
in Submitted, Executing, or Unknown states on available Control-M/Agents.

Track All timing is determined by the number of seconds specified in the

Polling Interval parameter in the ctm_menu utility.
The TR process performs the Track All action.
5525 CTMJSA STARTED. MODE={MEMNAME | JOBNAME}

Explanation: The ctmjsa utility started using the Statistics Mode =
<MEMNAME or JOBNAME>.
The ctmjsa utility compiles runtime data from the Statistical Details table and
records it in the Statistics Summary table of the Control-M/Server database.
The run time data is recorded to the database.

5700 Scheduling table tableName, Jobname jobName

Explanation: The jobName job was ordered and inserted into the Active Jobs file
from the tableName Scheduling table.
The job has been inserted to the Active Jobs file.
5701 Job jobName ordered, memname = memName, orderno= orderNumber

Explanation: The jobName job and memName Mem name was ordered and
inserted into the Active Jobs file with orderNumber order number. This message
is generated when Control-M successfully orders a job.
The job is inserted to the Active Jobs file.
5702 Jobname jobName not ordered

Explanation: An order request was performed for the jobName job, but Control-
M/Server did not order the job (for example, due to scheduling criteria).
User response: Check previous messages or logs in the proclog directory in
order to see why the job was not ordered.

5703 TABLE tableName DOES NOT EXIST

Explanation: An attempt was made to order or force a table, but the tableName
table is not defined in the Control-M/Server database. A possible cause is that
the table was created in Control-EM, but not uploaded to the Control-M/Server
database.
The request is not performed.
User response: Determine why the table does not exist and correct the problem.
If you verified that the table exists in the Control-M/Server database, but this
message still appears when you try to order this table, contact BMC Software
customer Support.
5704 WARNING: CALENDAR calName UP TO DATE. REQUEST REJECTED

Explanation: A Control-M/EM user attempted to perform an upload to the
calName calendar, but no change had been made in the calendar definition since
the last time it was uploaded to the Control-M/Server. Therefore, the calendar
is already up to date, and there is no need to upload it to the Control-M/Server.
The upload request is rejected.
5705 TABLE tableName PREVIOUSLY MODIFIED BY Control-M. REQUEST

REJECTED
Explanation: An attempt was made to update a table, but the tableName table
was previously changed in the Control-M/Server database. A possible cause is
that the table was created in Control-M/EM, but was changed later in Control-
M/Server database.
User response: Determine why the table was changed in the Control-M/Server
database and correct the problem.
If you verified that the correct table exists in the Control-M/Server database,
download the tableName table from Control-M/Server database to the Control-
M/EM database.
If you verified that the correct table exists in the Control-M/EM database,
then force upload the tableName table from the Control-M/EM database to
5707 DO SETVAR 'name'='value' performed

Explanation: The DO AutoEdit action of the active job was performed.

The name AutoEdit was assigned the value value.
5720 INTO-GROUP-ORD request is ignored for the regular job jobName

Explanation: This warning message is issued if you try to order or force a
regular (non-group) job into an existing group.
The job is not ordered.
5722 WARNING: TABLE tableName IS LOCKED. REQUEST REJECTED

Explanation: An Upload request was sent by Control-M/EM after the
tableName table was ordered by the User Daily job. Therefore, this table is
locked and can not be uploaded until the ctmuldy utility finishes ordering this
table.
The upload request is rejected.
User response: Try to upload the table again after the User Daily job that is
associated with this table ends.
5723 WARNING:TABLE tableName UP TO DATE. REQUEST REJECTED

Explanation: A Control-M/EM user attempted to perform an upload or
download to the tableName table, but no changes had been made in the table
definition since the last time it was uploaded to the Control-M/Server.
Therefore, the table is already up to date, and there is no need to upload it to
the Control-M/Server.
The upload or download request is rejected.
5740 User userName not allowed to order from table tableName

Explanation: The userName user tried to order a job from the tableName
Scheduling table, but this user is not authorized to order this table.
No jobs from the specified table are ordered.
User response: Determine if this user should be allowed to order the requested
job. If so, grant the authorizations required to access this Scheduling table in the
Control-M/Server security definition.

5741 User userName1 not allowed to FORCE for owner userName2

Explanation: The specified user (userName1) tried to force a job whose owner is
userName2, but is not authorized to do so.
The job is not forced.
User response: Determine if user userName1 should be allowed to force jobs that
are owned by userName2. If so, use the Control-M/Server security definition to
grant the authorizations required to access this Scheduling table.
5742 User userName1 not allowed to ORDER for owner userName2

Explanation: : The specified user (userName1) tried to order a job whose owner
is userName2, but is not authorized to do so.
User response: Determine if user userName1 should be allowed to order jobs

that are owned by userName2. If so, use the Control-M/Server security
definition to grant the authorizations required to access this Scheduling table.
5743 Security check failed

Explanation: An unauthorized action was requested.
The requested action is not performed.
User response: Examine prior messages to determine what action was

requested. If the user should have been allowed to perform the requested
action, grant the necessary authorizations. Otherwise, take appropriate steps to
enhance data center security.
5744 Row number rowNumber does not match the requested job jobName. Can't
force into a new Group.
Explanation: A job sequence number (rowNumber) was specified when trying to
force a job, but no job in the table has this number.
User response: Determine the correct job sequence number and try to force the
job again.
5745 Scheduling table tableName, job name jobName not found

Explanation: A request was made to order or force a job, but the specified job
or Scheduling table does not exist.

User response: Determine if the job name and Scheduling table name are
correctly spelled. Reissue the command.
5746 The SMART Table, Sub-table, SMART Table job, or Sub-table job failed be
ordered
Explanation: Only jobs or Sub-tables in new SMART Tables can be ordered
without using the FORCE option. Jobs must be forced into existing SMART
Tables or Sub-tables when using ALONE mode or LAST mode. Sub-tables must
be forced into existing SMART Tables or Sub-tables using LAST mode.
The job in the SMART Table/Sub-table is not ordered.
User response: Correct the errors and reissue the command.
5747 The ordered group does not exist. Or the job does not belong to the group
with the given orderno.
Explanation: When ordering or forcing an individual job into an existing
group, the target group's order ID is required. This order ID should exist in the
Active Jobs file and should be an instance of the job's group. This message is
issued if the specified group is not active or if the job does not belong to the
specified group.
5748 Job No jobName does not belong to the group with orderno orderNumber
Explanation: The jobName job does not belong to the Group Scheduling table
associated with the orderNumber order ID.
5749 The SMART Table or Sub-table already includes an instance of the job
Explanation: A job already included in a SMART Table/Sub-table cannot be
added to the SMART Table/Sub-table.

5750 No TAG was found or all the Group's TAGs failed in the scheduling test.
The group groupID can not be ordered
Explanation: When ordering a group, at least one of its Schedule Tags must
satisfy all scheduling criteria. This message is issued if no Schedule Tags were
found in the group, or if no tags satisfy the scheduling criteria.
The group is not ordered.
User response: Define or modify one or more schedule tags for this group.
5751 Error in job's schedule parameters

Explanation: The Control-M/Server was not able to build an ordering plan for
this job due to a job scheduling parameter that has an invalid value, or a
mandatory parameter that has not been specified.
The job or group is not ordered.
User response: Check for messages in logs in the proclog directory that may
indicate the problem. Check the definition of the group and job, correct the
error and reissue the command.
5753 Error copying jobdef to AJF

Explanation: An error occurred while trying to order a job and insert its
definition into the Active Jobs file.
User response: Check previous messages or logs in the proclog directory in

order to determine the cause of the problem.
5754 CONDITION condName WITH ORDER DATE condDate DOES NOT EXIST
Explanation: A Control-M/EM user tried to delete a prerequisite condition
with the indicated order date, but this prerequisite condition could not be
found in the Control-M/Server database.
The condition is not deleted.
User response: Use the ctmcontb utility to check if this condition name and date
exist in the Control-M/Server database.
5755 CONDITION condName WITH ORDER DATE condDate ALREADY EXISTS

Explanation: A Control-M/EM user tried to add a prerequisite condition with
the indicated order date, but this condition already exists with the specified
date in the Control-M/Server database.

The condition is not added.
User response: Use the ctmcontb utility to check if this condition name and date
exist in the Control-M/Server database.
5756 INVALID DATE FOR CONDITION condName condDate

Explanation: An invalid order date (condDate) was detected while trying to
add, delete, or change prerequisite conditions from Control-M/EM.
User response: Specify the correct date and reissue the command.
5757 ORDER FORCE FAILED DATE= orderDate

Explanation: An invalid order date was detected when ordering or forcing a
job from Control-M/EM.
The order or force request is rejected.
5758 TABLE tableName IS NOT UP TO DATE

Explanation: An attempt was made to order, force, or delete the tableName
table. However, the content of the table in Control-M/EM and the content of
the table with the same name in the Control-M/Server database are different.
User response: If the Control-M/EM table is newer, upload the table to the
Control-M/Server. If the Control-M/Server table is newer, download the table
to Control-M/EM.
5759 Jobname jobName not ordered. Invalid Time Zone.

Explanation: The ordering request for the jobName job can not be fulfilled, due
to the an invalid value of the time zone definition of this job.
For more details about time zone values, refer to the Time Zones and Job
Ordering chapter in the Control-M Administrator Guide.
The order request is not performed.
User response: Check the time zone value in the job definition, and correct it
according to the valid values in the TimeZone.dat file in the Control-M_ home/
ctm/data directory.

5760 SYNC REQUEST TIMEDOUT

Explanation: Communication between Control-M/EM and Control-M/Server
was not established.
The first stage of the communication between Control-M/EM and Control-M/

Server is a SYNC request for both sides, and for some reason this request timed
out.
This message indicates a communication problem between Control-M/Server

and Control-M/EM.
Control-M/EM and Control-M/Server try to establish a connection.
User response: Check the following:
the possibility of a communication problem between Control-M/EM and

Control-M/Server.
the Gateway log and the Control-M/Server CD, CO, and CS proclog files in
order to search for more messages that may indicate why the
communication is not established.
whether the EM port is in use by any other application.
In case the problem persists and communication is not established, contact

5761 SESSION CLOSED BY CO

Explanation: The session between Control-M/EM and Control-M/Server has
been closed by the CO process.
The session between Control-M/EM and Control-M/Server can be closed due

to some communication problem or problem in sending or receiving data
between Control-M/EM and Control-M/Server.
The connection between Control-M/EM and Control-M/Server is closed.
User response: Check the Gateway log and the Control-M/Server CD, CO, and
CS proclog files in order to search for more messages that may indicate why the
session closed.
In case the problem persists and communication between Control-M/EM and

Control-M/Server is not stable, contact BMC Software Customer Support.

5762 FAILED TO { ADD | DEL} COND: condName, ODAT: condDate

Explanation: An attempt to add or delete the specified prerequisite condition
(condName) with the specified date reference (condDate) to or from the Control-
M/Server database has failed. The failure might be due to a database problem.
The condName prerequisite condition was not added to or deleted from the
Control-M/Server database.
User response: Check the Control-M logs and the Control-M/Server database
error logs for any potential problem.
5763 FAILED TO DELETE CONDITION: condName DATEREF: condDate

Explanation: An attempt to delete the condName prerequisite condition with
condDate date reference from the Control-M/Server database has failed.
Possible reasons for this failure are:
There is no such prerequisite condition with the specified date reference in

the Control-M/Server database to delete.
The specified prerequisite condition with the specified date reference exists
in the Control-M/Server database to delete; however, the deletion failed due
to a database problem.
The specified prerequisite condition with the specified date reference is not
deleted from the Control-M/Server database.
User response: Check the cause of this message. First check if the condName
prerequisite condition with condDate date reference exists in the Control-M/
Server database to delete. If there was not, no action is required. If the specified
condition to delete does exists, check the Control-M logs and the Control-M/
Server database error logs for any potential problem.
5764 Failed to perform DOFORCE. table: tableName, job: jobName

Explanation: This message is sent by Control-M/Server to Control-M/EM
when there are insufficient privileges to perform a DO FORCE action.
User response: Check security definitions to see if this is what caused the failure
of the DO FORCE action, and change the privileges.
5765 Sub-table < subTableName> job cannot be ordered

Explanation: The job in the Sub-table failed to be ordered.
Control-M/Server processing continues.
User response: Refer to Control-M/Server logs and contact BMC Software

Support.

5766 Sub-table < subTableName> job cannot be ordered

Explanation: The job in the table failed to be ordered.
Cannot order when wait for ODate is set, but ODate occurs in the past.
5775 Initialize Sub-table < subTableName> job numbers retrieval failed

Explanation: During handling of Sub-table ordering, retrieval of Sub-table job
numbers initialization failed.

Support.
5776 Retrieve next job details of Sub-table < subTableName> failed

Explanation: Fetch of the next job details of the given Sub-table failed.

Support.
5777 < functionName>: Failed to retrieve definition of job number < jobNumber>
Explanation: Failed to retrieve job details of the given job number.
User response: Refer to Control-M/Server logs.
5778 Force Sub-table < subTableName> alone is not permitted

Explanation: Force Sub-table alone is not permitted.
User response: For details about ordering Sub-tables, see the Control-M User
Guide.


5807 GROUP and SCHEDTAB should be the same for group entity.
Explanation: The user attempted to create an active job group using Control-M/
EM API. The user specified a different name for the group and for the group
scheduling table parameters of the job.
The job group is not created.
User response: Create an active job group with the same name for the group
and for the group scheduling table parameters.
5808 GROUP and SCHEDTAB should be specified.

Explanation: The user attempted to create active job using Control-M/EM API.
The user did not specify a value for the group or the scheduling table
parameters of the job.
The job is not created.
User response: Create an active job and specify a value for both the group and
the scheduling table parameters.
5809 GROUP groupID does not exist in the database.

Explanation: The user attempted, using Control-M/EM API, to create an active
job with the groupID order ID into an existing group in the Active Jobs file. The
groupID order ID was not found in the Control-M/Server Active Jobs file.
User response: Create an active job and specify the order ID of an existing
group in the Active Jobs file for the groupID parameter. If the group does not
exist in the Active Jobs file, order the group or create it before creating the
active job.
5810 MEMLIB, CMDLINE, MEMNAME and OVERLIB should not be specified.

Explanation: The user attempted to create an active job group using Control-M/
EM API. The user specified for the job group one or more of the following
parameters: MEMLIB, CMDLINE, MEMNAME and OVERLIB
The job group is not created.
User response: Create an active job group without specifying the MEMLIB,
CMDLINE, MEMNAME, and OVERLIB parameters.
5811 FAILED to allocate isn.

Explanation: The user attempted to create an active job or job group using Control-
M/EM API. However, the Control-M/Server failed to allocate an order ID for
this job. This failure is most likely due to a database problem.

The job or job group is not created.
User response: Check the Control-M logs and the Control-M/Server database
error logs for any potential problem.
5812 No nodes found in NODEGRP groupName.

Explanation: The user attempted, using the Control-M/EM API, to create
active job with the multiagent parameter set to Yes; however, no NodeID was
found in the jobs groupName NodeGroup. Possible reasons for this are:
The groupName NodeGroup is not defined in the Control-M/Server

database, or no NodeID is defined in this NodeGroup.
There is a database problem.
User response: Verify that the NodeGroup is defined in the Control-M/Server,

and that at least one NodeID is defined in this NodeGroup. If the problem
persists even though the NodeGroup and NodeID are defined in the Control-M/
Server, check the Control-M logs and the Control-M/Server database error logs
for any potential database problem.
5814 FAILED to setup the application type for NODEGRP groupName.

Explanation: The user attempted to create an active job using the Control-M/
EM API; however, the Control-M/Server failed to set the jobs application type.
Possible reasons for this are:
The application type for the jobs groupName NodeGroup in the Control-M/
Server is different than the application type that the user has specified in the
API.
There is a database problem.
User response: Check the application type for the groupName NodeGroup in the
Control-M/server, and correct it if needed. In addition, verify that the correct
application type is specified in the Control-M/EM API. If the problem persists
after verifying both issues, check the Control-M logs and the Control-M/Server
database error logs for any potential database problem.
5815 Invalid ODATE date.

Explanation: The user attempted to create an active job or a job group using the
Control-M/EM API; however, the user has specified an invalid date for the
ODATE job parameter.

The job or job group is not created.
User response: Specify a valid date for the ODATE parameter.
5816 SYSOUT FILE EXCEEDED LIMIT SIZE

Explanation: The size of the Sysout file exceeded the limit (in KB) defined by
the SYSOUT_LIMIT_SIZE parameter.
The View Sysout action is rejected.
User response: Either set the SYSOUT_LIMIT_SIZE to a specific larger number

of kilobytes, or return the value of the parameter to 0 (default), allowing an
unlimited Sysout file size.

5901 Job: jobNumber USER EXIT101 failed. task type= taskType

Explanation: The Job Ordering User Exit (CTMUE101) failed for the jobNumber
job with taskType tasktype. This is because the Control-M/Server failed to
create, write to, read from, or delete the flat text file, which is passed to the user
exit script.
If the Control-M/Server failed to create or write to the flat text file, the user exit
script is not executed. If the Control-M/Server successfully created or wrote to
the flat file, the user exit is executed. In any case, the job record is not modified.
The procedure of ordering the job continues using the job record from the
Scheduling definition table.
Verify that the Control-M/Server account owner has read and write
permissions to ~<controlm_owner>/ctm/ue_exit directory.
[For Unix] Verify that there are enough file descriptors available.
Verify that there is enough free disk space.
In case none of the causes listed above match the problem and the problem
persists, notify BMC Software Customer Support.
5902 Job: jobNumber USER EXIT102 failed. task type= taskType

Explanation: The Job Submission Exit (CTMUE102) failed for the jobNumber job
with taskType tasktype. Possible reasons for this failure are:

Control-M/Server failed to create, write to, read from, or delete the flat text
file, which is passed to the user exit script.
There is not enough available memory.
If the Control-M/Server failed to create or write to the flat text file or failed to
allocate required memory, the user exit script is not executed. Otherwise, the
user exit script is executed. In any case, the job record is not modified. The
procedure of submitting the job for execution continues using the job record
from the Active Jobs file.
permissions to ~<controlm_owner>/ctm/ue_exit directory
Verify that there is enough available memory.
5903 User Daily SYSTEM USER EXIT103 failed. old_odat= date

Explanation: The Before New Day Procedure Exit (CTMUE103) failed for the
User Daily SYSTEM job. This is because the Control-M/Server failed to create,
write to, read from, or delete the flat text file, which is passed to the user exit
script. date is the Control-M/Server date before the New Day procedure.
script is not executed. Otherwise, the user exit is executed. In any case, the New
Day procedure runs.

5904 User Daily SYSTEM: USER EXIT CTMUE104 failed. old_odat= date
Explanation: The After New Day Procedure Exit (CTMUE104) failed for the
User Daily SYSTEM job. This is because the Control-M/Server failed to create,
write to, read from, or delete the flat text file, which is passed to the user exit
script. date is the Control-M/Server date after the New Day procedure.
script is not executed. Otherwise, the user exit is executed. In any case, New
Day procedure completes.
5905 User Daily userDailyName: USER EXIT CTMUE105 failed. old_odat= date
Explanation: The Before User Daily Exit (CTMUE105) failed for the
userDailyName User Daily job. This is because the Control-M/Server failed to
exit script. date is the current Control-M/Server date.
script is not executed. Otherwise, the user exit is executed. In any case, the
procedure of ordering the User Daily job continues.
5906 User Daily userDailyName: USER EXIT CTMUE106 failed. old_odat= date
Explanation: The After User Daily Exit (CTMUE106) failed for the
userDailyName User Daily job. This is because the Control-M/Server failed to

exit script. date is the current Control-M/Server date.
script is not executed. Otherwise, the user exit is executed. In any case, the
procedure of ordering the User Daily job completes.

6000 functionName: Stored Procedure failed (procName)

Explanation: The executed stored procedure returned its error status.
One of the following occurs:
For the newday_proc_partitions and newday_partition_proc stored

procedures, handling the Control-M/Server log fails.
For the purge_cmr_runinf_1 stored procedure, the statistic cleanup

procedure fails.
6001 functionName: ERROR occurred. Marking mirror db as unused!!

Explanation: Updating of the mirror database failed. Mirroring is marked as
damaged.
Mirroring no longer functions.

6002 User name does not have environment definition for varDescription
(varName)
Explanation: The specified environment variable does not exist.
You cannot start Control-M/Server or activate the Control-M/Server utility.
User response: Try to log on again to the Control-M/Server account. If this does
not help, contact BMC Software Customer Support.
6003 functionName: Failed to update database statistics. rc= rc

Explanation: Updating of database statistics failed.
Updating of database statistics failed. Control-M/Server processing continues.

This may affect data fetch performance from the database.
User response: Contact the DB Administrator.
6004 functionName: Failed to create cache table for process parameters

Explanation: A cache table for process parameters could not be created due to
insufficient memory.
Control-M/Server failed to allocate memory for cache table parameters.
User response: Check available memory on the machine. If this is not the
problem, contact BMC Software Customer Support.
6005 functionName: Failed to create cache table record for process parameters
Explanation: A cache table record for process parameters could not be created
due to insufficient memory.
Control-M/Server failed to allocate memory for cache table record parameters.
6006 functionName: Failed to create a duplicate cache table record for process
parameters
Explanation: A duplicate cache table record for process parameters could not
be created because of insufficient memory.
Control-M/Server failed to allocate memory for a copy of cache table record

parameters.

6007 functionName: Failed to create cache table for autoedit variable names
Explanation: A cache table for AutoEdit variable names could not be created
because of insufficient memory.
AutoEdit variables are not calculated correctly. This can occur in more than one
flow. For example, if this happens during job submission, the job will not be
submitted. For more information, refer to Control-M/Server logs.
6008 functionName: Failed to create cache table for autoedit variable values
Explanation: A cache table for AutoEdit variable values could not be created
6009 functionName: Failed to expand cache table for autoedit variables for order
number orderNumber. Variable Name varName, Variable Expression
varExpression
Explanation: A cache table for AutoEdit variables with the specified order
number, variable name, and variable expression, could not be expanded
6010 functionName: Failed to expand cache table for group and local autoedit
variables
Explanation: A cache table for group and local AutoEdit variables could not be
expanded because of insufficient memory

6011 functionName: Failed to retrieve global autoedit variables from the database
Explanation: Global AutoEdit variables could not be retrieved from the
database.
6012 functionName: Failed to retrieve {Job | Group} autoedit variables from the
database for {Job | Group} order number orderNum
Explanation: The specified AutoEdit variable with a specific order number
could not be retrieved from the database.
6013 functionName: Failed to determine autoedit variable name level (job, group
or global)
Explanation: The AutoEdit variable %s level (job, group, or global) could not be
determined.
The specified AutoEdit variable is not calculated.
User response: Check the AutoEdit variable syntax.
6014 functionName: Failed to delete global autoedit variable name

Explanation: The specified global AutoEdit variable could not be deleted.
The specified AutoEdit variable is not deleted.
User response: Check the AutoEdit variable syntax. For more information, refer
to Control-M/Server logs
6015 functionName: Failed to delete global autoedit variable number

Explanation: The specified AutoEdit variable could not be deleted.
The specified AutoEdit variable is not deleted.
User response: Check the AutoEdit variable syntax. For more information, refer
to Control-M/Server logs.

6016 functionName: Illegal scheduling plan found in job name name job number
number odate date
Explanation: An illegal scheduling plan is found for the specified job.
The specified job is not ordered.
User response: Review the scheduling parameters of the specified job.
6017 functionName: Group order number number does not exist. Group name
can not be ordered into the specified order number
Explanation: The specified group order number does not exist. The attempt to
order the specified group into this existing group failed.
The specified group is not ordered.
6018 functionName: Group entity name was not ordered successfully

Explanation: The specified group could not be ordered.
The specified group is not ordered.
6019 functionName: Failed to delete in condition(s) of job(s) in group name

Explanation: When a group is ordered and the groups scope is defined, IN
conditions for jobs within the group which do not exist or which are not being
added by other jobs will be deleted. Deletion of the IN conditions failed.
The group and its jobs are ordered, but some or all of its jobs will be in WAIT
condition status.
6020 functionName: Attempt to order daily jobName while upload procedure is

active
Explanation: An attempt was made to order the specified daily job while an
upload procedure is active.
The daily job is ordered.
User response: Cancel the upload procedure.

6021 functionName: Failed to read group defName definition. Job jobName is not
ordered
Explanation: An attempt to read the specified groups definition failed. This
occurs while attempting to order a job into existing group.
The specified job is not ordered.
6022 functionName: Message received from Control-M/EM is not first in sequence

Explanation: Control-M/Server received a message from Control-M/EM which
is not first in a sequence.
The message is handled.
6023 functionName: Illegal condition operation opName received from user

userName. Condition name is condName
Explanation: An illegal operation on the specified condition is received from
the specified user. The operation is supposed to be performed on the specified
condition name.
The specified request is not performed.
6024 functionName: Illegal response responseID received from Control-M/EM for

scheduling table tableName download operation
Explanation: An illegal response was received from Control-M/EM for the
specified scheduling table download operation.
The specified scheduling table is not downloaded.

node group groupName download operation
specified node group download operation.
The specified node group is not downloaded.


calendar calName download operation
specified calendar download operation.
The specified calendar is not downloaded.
6027 functionName: Failed to handle partitioned table tableName. Returned

status is rc
Explanation: During Control-M/Server startup, partitioned tables are prepared
for further usage.
Control-M/Server failed to start.
6028 functionName: Terminating process procName, process number

procNumber
Explanation: The Control-M/Server supervisor process terminates the
specified process with the specified process number. This occurs because the
specified process did not respond to the supervisor process requests within a
predefined time.
6029 functionName: Failed to update supervisor (SU) process state

Explanation: The process state of the Control-M/Server supervisor was not
updated. Possible states are:
Running
Suspended
Terminated
6030 functionName: Failed to create alert file fileName during handling alert
alertName
Explanation: The specified alert file was not created during handling of the
specified alert.
The specified alert is not handled.

6031 functionName: Failed to release lock lockID (semaphore id) on alert file
fileName during handling alert alertName
Explanation: The lock acquired on the alert file while handling the specified
alert was not released.
The specified alert is not handled.
User response: Refer to the Control-M/Server logs and contact BMC Software
Customer Support.
6032 functionName: Failed to copy alert file fileName1 to fileName2

Explanation: When the connection with Control-M/EM is down, alerts are
saved in an alert file. When the connection with Control-M/EM is back, Control-
M/Server reads this file and handles all the alerts contained in it. When the
handling any of these alerts fails, the alert file is copied to a backup file. The
backup of this file failed.
Customer Support.
6033 functionName: Failed to open alert file fileName, file name fileName return
code rc
M/Server reads this file and handles all the alerts contained in it. Reading the
specified alert file failed.
Customer Support.
6034 functionName: Failed to release lock lockID after handling alerts file
M/Server reads this file and handles all the alerts contained in it. When writing
to the alert file, the file is locked. When the alerts are handled, the lock is
released. Releasing the lock failed.
Alerts are handled.
User response: Restart Control-M/Server and contact BMC Software Customer

Support.
6035 functionName: Failed to release lock (semaphore) id lockID

Explanation: An OS object (a semaphore lock) could not be released. This is a
severe problem which may occur in more than one flow in Control_M/Server.

The system may become unstable.
User response: Search for errors related to releasing semaphores in Control-M/

Server logs and contact BMC Software Customer Support.
6036 functionName: Failed to initialize process threads environment. Return

status rc
Explanation: The process threads environment could not be initialized.
The process or utility does not start.
User response: Search for errors related to initializing process threads in the
process or utility log and contact BMC Software Customer Support.
6037 functionName: Failed to initialize thread environment. Return status rc

Explanation: The thread environment could not be initialized.
User response: Search for errors related to initializing the threads environment
in the process or utility log and contact BMC Software Customer Support.
6038 functionName: Failed to initialize thread database connection. Return

status rc
Explanation: The thread database connection could not be initialized.
User response: Search for errors related to initializing the database thread
connection in the process or utility log and contact BMC Software Customer
Support.
6039 functionName: Error occurred while thread termination. Return status rc

Explanation: When a thread terminates, an error occurs.
User response: Search for errors related to thread termination in the process or
utility log and contact BMC Software Customer Support.
6040 functionName: Failed to reset Remote Host agent list for Remote Host
hostName
Explanation: Control-M/Server failed to reset the remote host agent list for the
hostName remote host.
The hostName remote host will not be available. Normal Control-M/Server


6041 functionName: Failed to extract Remote Host agent list for Remote Host
hostName
Explanation: Control-M/Server failed to extract the remote host agent list for
the hostName Remote Host.
The hostName remote host will not be available.
6042 functionName: Failed to open file fileName for writing

Explanation: Control-M/Server was unable to open the fileName file for
writing.
The fileName file will not be opened.
Check the Control-M/Server log files.
Contact BMC Software Customer Support.
6043 functionName: Failed to append Remote host agent name to the remote
host agent names list of remote host hostName
Explanation: Control-M/Server was unable to append a remote host agent
name to the remote host agent names list of the hostName remote host.
The hostName remote host will not be handled correctly.
Check the amount of free memory on the machine.
6044 functionName: Failed to clear remote host agent names list of remote host
hostName
Explanation: Control-M/Server was unable to clear the remote host agent
names list of the hostName remote host.

6045 functionName: Failed to retrieve data from table tableName explanation

Explanation: Control-M/Server was unable to retrieve data from the tableName
table.
Check the database errors in Control-M/Server and database files.
6046 functionName: { SSH | WMI } details not found for remote host hostName
Explanation: Control-M/Server was unable to find SSH or WMI remote host
definition parameter details for the hostName remote host.
User response: Define SSH or WMI details for the hostName remote host.
6047 functionName: Failed to get host name of machine on which Control-M/

Server is running.
Explanation: An attempt was made to get the host name of the machine on
which Control-M/Server is running, but the attempt failed.
User response: Verify that the host name of the machine on which Control-M/
Server is running is defined correctly.
6048 functionName: Failed to fetch next remote host agent name from remote
host agent names list of remote host hostName
Explanation: An attempt was made to fetch the next remote host name from the
remote host agent names list of the hostName host, but the attempt failed.
Check the hostName remote host parameters.
6049 functionName: Failed to clear availability remote host agent names list of
remote host hostName
Explanation: An attempt was made to clear the availability remote host agent
names list of the hostName host, but the attempt failed.
6050 Failed to update remote host hostName status

Explanation: Control-M/Server failed to update the status of the hostName
remote host.

The status of the hostName remote host will not be handled correctly.
6051 Failed to update status details of remote host hostName

Explanation: Control-M/Server failed to update the status details of the
hostName remote host.
The status details of the hostName remote host will not be handled correctly.
6052 Failed to read agent agentName status while handling remote host hostName
Explanation: Control-M/Server failed to read the status of the agentName agent,
while handling the hostName remote host.
The status of the hostName remote host will not be handled correctly.
6053 functionName: Agent agentName status file not found while handling
remote host hostName
Explanation: Control-M/Server was unable to find the status file for the
agentName agent while handling the hostName remote host.
The remote host status will not be handled correctly.
6057 functionName: Failed to delete agent name agentName from agent names
list of remote host hostName
Explanation: Control-M/Server failed to delete the agentName agent from the
agent names list of the hostName remote host.
The hostName remote host status will not be handled correctly.
6058 functionName: Node nodeID status file not found.

Explanation: Control-M/Server failed to find the status file of the nodeID node.
The requested operation on the nodeID node will not be handled.

6059 functionName: Failed to read node nodeID status file. Read status status.
Explanation: An error occurred while Control-M/Server attempted to read the
status file of the nodeID node.
The requested operation on the nodeID node will not be handled.
6060 functionName: Failed to delete agent agentName from the database.

Explanation: An attempt to delete the agentName agent from the agent table in
the database failed.
The agentName agent is not deleted.
6061 functionName: Failed to initialize select on table CMS_RJX_NAMES while

handling agent deletion agentName.
Explanation: An attempt to initialize selection of the CMS_RJX_NAMES table
while handling the agentName agent failed.
6062 functionName: Failed to add a node with nodeID to remote hosts list while
handling agent agentName deletion.
Explanation: Control-M/Server failed to add a node to the remote hosts list
while handling the agentName agent deletion.
Check available memory on the machine.

6063 functionName: Failed to update agent agentName details used by remote

host hostName while handling agent agentName deletion.
Explanation: Errors occurred while updating details for the agentName agent
that are used by the hostName remote host, while handing deletion of the
agentName agent.
6064 functionName: Failed to extract remote host name from remote host names
list while handling agent agentName deletion.
Explanation: Control-M/Server failed to extract the next remote host while
handling the agentName agent deletion.
6065 functionName: Failed to extract parameters from trigger message

messageText while handling agent deletion.
Explanation: Control-M/Server failed to extract parameters while handling
deletion of an agent.
6066 functionName: Illegal agent type received messageText while handling

agent deletion.
Explanation: Control-M/Server received an illegal agent type while handling
deletion of an agent.

6067 functionName: Failed to duplicate list listInfo listOrigin.

Explanation: Control-M/Server failed to duplicate a list.
Check the amount of free memory on the machine.
6068 Delete local agent is prohibited.

Explanation: An attempt was made to delete a local agent from Control-M/
Server.
User response: None. Do not attempt to delete a local agent.
6069 Update remote hosts using agent agentName failed.

Explanation: When normal agent status is changed, all remote hosts using this
agent are updated as well. An attempt to update remote hosts failed while
handling the status of the agentName agent.
Check machine available memory and Control-M/Server logs.
6070 Update remote hosts using agent agentName completed partially.

Explanation: When normal agent status is changed, all remote hosts using this
agent are updated as well. An attempt to update remote hosts did not succeed
for all the remote hosts while handling the status of the agentName agent.
6071 Add a new record to TR node list while handle node nodeID failed.
Explanation: The tracker process attempted to add a new entry in its nodes list.
The nodeID node is used by the tracker process to track jobs were submitted to
the node. An attempt to add the nodeID node failed.

6072 Add a new record to TR node-job list while handle node nodeID and order
number orderNumber failed.
Explanation: The tracker process attempted to add a new entry in its nodes list.
The nodeID node is used by the tracker process to track jobs were submitted to
the node. An attempt to add the nodeID node orderNumber order number failed..
6073 Determine different memory remote host agent list and remote host status
file agent list failed while handling remote host hostName.
Explanation: An attempt to determine the difference between the memory
agent remote host list and remote host status file agents list failed.
6074 Remote host hostName agents list file contains illegal line.
Explanation: An illegal line was found in the hostName remote host agents list
status file.
The status of the remote host is not handled correctly.
Check Control-M/Server logs.
6075 Add job with order number orderNumber details to node nodeID order
number list failed.
Explanation: An attempt was made to add the orderNumber order number job
details to the nodeID node order number list, which handles the tracking of
these order numbers. The status of the orderNumber job may only be updated by
using the track-all mechanism.

6076 Failed to clean node nodeID order number list. rc= rc.
Explanation: An attempt was made to clean the nodeID order number list, but
the attempt failed.
6077 functionName: Remote host hostName map details not found.

Explanation: The hostName remote host map is not found in the Control-M/
Server database. This error may occur while handling job submissions, killing
jobs, or viewing JCL.
The following occurs:
if this error occurs during job submission, the job is not submitted
if this error occurs while killing a job, the job is not killed
if this error occurs while viewing JCL, the view JCL function fails
User response: Define a map for the hostName remote host.
6078 functionName: Failed to get remote host hostName map details.

Explanation: The hostName remote host map could not be obtained from the
Control-M/Server database. This error may occur while handling job
submissions, killing ordered jobs, or viewing JCL.
if this error occurs during job submission, the job is not submitted
if this error occurs while killing a job, the job is not killed
if this error occurs while viewing JCL, the view JCL function fails
6079 functionName: Illegal node status received status with trigger triggerName.
Explanation: The status illegal node status was encountered while handling
data for the triggerName trigger.
The action specified by the trigger is not handled.

6080 functionName: Illegal node type received type with trigger triggerName.
Explanation: The type illegal node type was encountered while handling data
for the triggerName trigger.
The action specified by the trigger is not handled.
6081 Failed to load fileName file explanation.

Explanation: An attempt was made to load the fileName file, but the attempt
failed.
Default configuration parameters, described in the Control-M/Server logs, are

used.
6082 functionName: Only Mail shouts are allowed for remote hosts. Shout type
received shoutType while handling order number orderID.
Explanation: Control-M/Server requested a remote host to perform a shoutType
shout, but only mail shouts are permitted.
User response: Verify that you have requested only mail shouts from remote
hosts
6083 functionName: Failed to get available agent for remote host hostName.
Explanation: An attempt was made to get an available agent for the hostName
remote host, but the attempt failed.
The requested operation failed.

6084 Illegal node type type received while handle job with orderno orderNumber
runcount count.
Explanation: An illegal node type (type) was received while handling a job with
the orderNumber order number and the count run count.
Job tracking fails.

6100 Utility aborted - Running the utility will damage the mirroring
Explanation: Running the utility may damage the mirroring, since the
connection with the Mirror Server can not be established. The utility is aborted
(since it was executed by a user other than the Control-M/Server
Administrator), so mirroring will not be damaged.
The utility is aborted, and mirroring is not damaged.
User response: Determine the cause of the failed connection with the Mirroring
Server and correct it. If the problem persists, contact BMC Software Customer
Support.
6101 Utility aborted - User not authorized to execute the utility!

Explanation: The utility may not be executed by a user other than the Control-
M/Server Administrator, and therefore is aborted.
The utility is aborted.
User response: No user other than the Control-M/Server Administrator is

allowed to run this utility. Please refer to the Utility Reference Table in the Control-
M Administrator Guide.
6102 Timeout waiting for LG process to change state to Running

Explanation: This utility needs to be suspended while the Control-M/Server
state is Suspended and resume running only when it notices that the Control-M/
Server state is Running. In this case, the utility was waiting for it to resume
Running state, but the timeout limit was exceeded.

The utility is aborted. If ordering is performed, it continues with the ordering

attempts of the rest of the jobs.
User response: Check the Control-M/Server processes state with the prf utility
and retry again when the processes are back in Running state.
6103 Selector did not get out of suspension

Explanation: The ordering utility was executed. This utility needs to be
suspended while the Control-M/Server state is Suspended and resume running
only when it notices that the Control-M/Server state is Running. In this case,
the utility was waiting for it to resume Running state, but the timeout limit was
exceeded.
The utility is aborted.
User response: Check the Control-M/Server processes state with the prf utility
and retry again when the processes are back in Running state.
6104 Update user information in security table userName description userGroup

nodeID
Explanation: The ctmsec utility, executed in a non-interactive mode, updated
existing user information in the security definitions tables. The new
information for this user is specified in the userName, description, userGroup,
and nodeID parameters.
The database table was updated with the new information.
6105 Insert user information into security table userName description

userGroup nodeID
Explanation: The ctmsec utility, executed in a non-interactive mode, tried to
update user information in the security definitions tables. Since the user was
not found, a new user is defined. The new user information is specified in the
userName, description, userGroup, and nodeID parameters.
6106 Update group information in security table groupName description - group-

nodeID
Explanation: The ctmsec utility, executed in a non-interactive mode, updated
existing group information in the security definitions tables. The new
information of this group is specified in the groupName, description, group, and
nodeID parameters.

6107 Insert group information into security table groupName description -

group- nodeID
Explanation: The ctmsec utility, executed in a non-interactive mode, tried to
update group information in the security definitions tables. Since the group
was not found, a new group is defined. The new group information is specified
in the groupName, description, group, and nodeID parameters.
6108 Failed to receive confirmation of successful message receiving

Explanation: The utility performed an action, but the confirmation of a
successful message reception failed. There is a possibility that the action
performed by the utility may not be completed.
The utility ends. There is a chance that it did not complete all its actions
successfully.
User response: Restart Control-M/Server. All information is refreshed from the

database.
6109 Failed in database operation while trying to find dependent jobs. Return
Code = rc
Explanation: You tried to list job dependencies with the ctmpsm utility, but the
utility failed in the database operation.
The list is empty.
User response: Determine the cause of the database problem. Check the
database error log. If the problem persists, contact BMC Software Customer
Support.
6110 Start failover has failed

Explanation: The Start Failover procedure failed.
You tried to copy the saved site-specific information about the backup Server
platform to the Mirror database, and the attempt failed. This data is needed to
start Control-M on the backup Server using the Mirror database.

The Failover Server on the secondary platform is not ready to start.
User response: Check the connection to the Mirroring database. Do not start the
secondary Control-M/Server on the Failover Server.
6111 Stop failover has failed

Explanation: The Stop Failover procedure failed.
You tried to restore the site-specific information about the primary Server
platform to the Mirror database, and the attempt failed. This data is used to
restore the primary database.
The Failover Server on the secondary platform was not stopped.
User response: Check the connection to the Mirroring database. Do not

continue with restoring the primary database from the Mirror.
6112 Unable to initialize

Explanation: A process cannot be initialized due to a system problem or lack of
resources.
The process aborts with a failure exit status.
User response: Check the system error log, disk space, or database connectivity.
6113 Failed to get ControlM_MIRROR_USER from the environment

Explanation: A utility failed to log on to the mirror database because it could
not get the ControlM_MIRROR_USER parameter from the environment.
A utility failed to log on to the mirror database. The utility aborts with an error.
User response: Check that the ControlM_MIRROR_USER parameter is set in

the .cshrc file. Log on to the shell environment again. If this does not solve the
problem, use the Database Mirroring => Initialize Mirroring option.
6114 Failed to get ControlM_USER from the environment

Explanation: A utility failed to log on to the primary database because it could
not get the ControlM_USER parameter from the environment.
A utility failed to log on to the database. The utility aborts with an error.
User response: Check that the ControlM_USER parameter is set in the .cshrc
file. Log on to the shell environment again.

6115 Failed to get SYBASE from the environment

Explanation: A utility failed to log on to the database because it could not get
the SYBASE parameter from the environment.
User response: Check that the SYABSE parameter is set in the .cshrc file. Log on
to the shell environment again.
6116 Failed to get ControlM environment variable

Explanation: A utility failed to log into the database because it could not get the
ControlM parameter from the environment.
User response: Check that the ControlM parameter is set in the .cshrc file. Log
on to the shell environment again.
6117 Failed to create temporary file fileName for writing. Error Number=
errorNumber, Error Message= errorString
Explanation: A utility failed to log on to the database because it could not
create a temporary file (fileName).
A utility failed to log into the database. The utility aborts with an error.
User response: Check the reason that the file could not be created, and act based
on the error number (errorNumber) and error string (errorString) returned.
6118 Failed to create temporary (fp) file fileName for writing

Explanation: A utility failed to log on to the database because it could not
create a temporary file (fileName).
User response: Check the reason that the file could not be created. If the
problem persists, contact BMC Software Customer Support.
6119 Failed to open file filename for reading

Explanation: A utility failed to log on to the database because it could not open
a temporary file (fileName).
User response: Check the reason that file could not be opened. If the problem

6120 Failed to get CTM_DATABASE_TYPE from the environment

the CTM_DATABASE_TYPE parameter from the environment.
User response: Check that the CTM_DATABASE_TYPE parameter is set in

the .cshrc file. Log on to the shell environment again.
6121 UnSupported database DBType

Explanation: A utility failed to log on to the database because the DBType value
is incorrect.
User response: Correct the CTM_DATABASE_TYPE parameter in the .cshrc

file. Valid values are SYBASE or ORACLE. Log on to the shell environment
again.
6122 Failed to get envirVariable from the environment

the specified envirVariable from the environment.
User response: Check that the envirVariable is set in the .cshrc file. Log on to the
shell environment again.
6123 Cannot open directory directoryName

Explanation: A utility failed to open the specified directory (directoryName). The
files under this directory can not be accessed.
The ctmsuspend utility failed and did not change the processes state.
User response: Check the OS file system.
6124 Cannot shutdown Control-M/Server...

Explanation: The shut_ctm utility failed to shut down the Control-M/Server
processes.
The ctmsuspend utility failed and did not perform the required action.
User response: Check the shut_ctm process log in the proclog directory for
messages at debug level 0.

6125 Restarting server...

Explanation: Control-M/Server processes are about to be restarted.
The start_ctm utility is executed by the ctmsuspend utility.
6126 Cannot restart Control-M/Server...

Explanation: Control-M/Server processes cannot be restarted.
The start_ctm utility failed. The Control-M/Server did not restart because the
ctmsuspend utility failed to perform the required action.
User response: Check the start_ctm process log in the proclog directory for
6127 Failed to run ctmshout utility

Explanation: The ctmshout utility failed to execute.
The message that indicates whether the operation of the ctmsuspened utility
was successful or not was not inserted into the IOALOG table. There is a
chance that the ctmsuspend utility failed to perform the required action.
User response: Check the ctmshout process log in the proclog directory for
6128 Failed to create database objects

Explanation: Database tables and other database objects, such as indexes and
stored procedures, were not created successfully.
The ctmcreateschema utility failed, and the Control-M/Server database was not
created.
User response: Check connectivity with the database. Check the

create_db.mssql.out file in the Control-M temporary directory for error
messages. If the problem persists, contact BMC Software Customer Support.
6129 Failed to insert initial values into database tables

Explanation: Database tables were not initialized with the correct initial values
in order for Control-M/Server to function.

created.
User response: Check connectivity with the database. Check the insert_NT.out
file in the Control-M temporary directory for error messages. If the problem
6130 Failed to create database partitions tables

Explanation: The CMR_IOALOG and CMR_JOBINF database partition tables
were not created successfully.
created.
User response: Check connectivity with the database. Check the

create_parts.out file in the Control-M temporary directory for error messages. If
the problem persists, contact BMC Software Customer Support.
6131 Failed to update system and communication parameters in database tables

Explanation: The Control-M/Server system and communication parameters
were not stored successfully in the database tables. Control-M/Server could
not be started without those parameters.
created.
User response: Check connectivity with the database. Check the update_tb.out
file in the Control-M temporary directory for error messages. If the problem
6132 Failed to reset several Control-M/Server configuration parameters

Explanation: The reset_t1 utility failed.
created.
User response: Check connectivity with the database. Check the reset_t1,
init_prflag, and cleanlog utilities logs in the Control-M proclog directory for
error messages. If the problem persists, contact BMC Software Customer
Support.
6133 functionName: Failed to retrieve sysout from the agent for orderno
runcount sysout size. rc = rc
Explanation: A utility failed to retrieve sysout from Control-M/Agent.

The utility aborts with an exit status of Failed.
6134 functionName: Failed parsing fileName

Explanation: A utility failed during an XML parsing.
6135 Invalid tagName request in xmlFile

Explanation: A utility failed during an XML parsing while dumping into
invalid tagName.
6136 functionName: Failed to retrieve element list for nodeName in the fileName
Explanation: A utility failed while reading an element list for the nodeName
node from the fileName XML file.
6137 Invalid calendarType

Explanation: A utility failed while reading an invalid calendar type from an
XML file.
6138 functionName: Invalid attributeName of attributeType.

Explanation: A utility failed while reading an invalid attributeType attribute
from an XML file.

6139 functionName: Failed to commit when inserting calendar: calendarName,

calendarYear
Explanation: The ctmpsm utility failed to insert a new calendar into the
database.
6140 functionName: Failed to insert calendar calenarName, calendarYear into

the database.
Explanation: A utility failed to insert a new calendar into the database.
6141 functionName: Failed to retrieve parent node of nodeName in the fileName

Explanation: A utility failed while reading the parent node of the nodeName
node from the fileName XML file.
6142 functionName: CalendarName with year was imported successfully.

Explanation: The ctm_psm utility was invoked, and successfully imported the
calendarName calendar.
The ctm_psm utility continues processing.
6143 functionName: Failed to convert arguments to UTF8.

Explanation: A utility failed to convert arguments to Unicode format.
6153 functionName: A conflict has occurred between the imported information

specified in nodeGroup and applType and the information currently
existing in the database.
Explanation: The imported information specified in applType and nodeGroup
conflicts with the information currently existing in the database.

The utility aborts with an error.
User response: Change the information specified in applType and nodeGroup

from the XML input file of the ctmimptb utility to match the information
existing in the database using ctm_menu.
Note
You can change the information in the database, but you need to delete the
nodeGroup with all its content and to redefine it with the new applType.
6154 functionName: Failed on input XML file initialization process. Message:

messageDetails
Explanation: The input XML file initialization process failed.
User response: Search for errors related to the XML file initializing process in
the utility log, and contact Customer support.
6155 Error was found during XML file parsing. Error Type: errorType, File Name:
fileName, Line: lineNum, Column: columnNum, Message: messageDetails
Explanation: An error was found during XML file parsing.
User response: Search for the error related to the XML file parsing process in
the utility log, and contact Customer Support.
6156 Unable to identify the user name invoking this application.

Explanation: The utility failed to retrieve the user name parameter from the
environment.
User response: Contact your system administrator for assistance.
6157 Import tableName has successfully written to the database.

Explanation: The ctmimptb utility imported the specified job definition tables
into the database successfully.
The ctmimptb utility continues processing the XML file and a message is sent to
the next import stage.

6158 functionName: Failed to insert scheduling table tableName into the database
Explanation: The utility failed to insert the tableName scheduling table into the
database.
User response: Contact Customer Support.
6159 functionName: Request permission denied. Scheduling table: tableName,

Action: permissionType. Skip importing this table.
Explanation: The user does not have the specified permission type on the
specified component to perform the request.
The ctmimptb utility continues processing the XML file.
User response: Assign the specified permission type to the user who invokes
the utility and rerun the ctmimptb utility.
6160 Scheduling table tableName already exists in the database and overwrite
was not specified. Skip importing this table.
Explanation: The ctmimptb utility did not import the tableName scheduling
table because the table currently exists in the database, and overwrite was not
specified.
The ctmimptb utility continues processing the XML file to import the next table.
6161 functionName: Failed during XML file parsing. Message: messageDetails

Explanation: The utility failed on XML file parsing.
User response: Search for the error related to the XML file parsing in the utility
log and contact Customer Support.
6162 functionName: Failed to delete scheduling table tableName from the

database
Explanation: The utility failed to delete the tableName scheduling table from the
database.

6163 functionName: Failed to delete jobs related to scheduling table tableName

from the database
Explanation: The utility failed to delete jobs related to the tableName scheduling
table from the database.
6164 functionName: Failed to delete checksum of scheduling table tableName

from the database
Explanation: The utility failed to delete the checksum of the tableName
scheduling table from the database.
6165 functionName: Failed to insert tag tagName of scheduling group

groupName into the database
Explanation: The utility failed to insert the groupName scheduling group tag
into the database.
6166 functionName: Failed to insert dates of scheduling group tag into the
database. Tag: tagName, Scheduling group: tableName, Date: Date.
Explanation: The utility failed to insert date details of the tagName scheduling
group tag into the database.
6167 functionName: Failed to insert Job jobName for scheduling table

tableName into the database.
Explanation: The utility failed to insert the jobName job into the database.

6168 functionName: Failed to insert jobProcessingDefinitions for Job jobName

for scheduling table tableName into the database.
Explanation: The utility failed to insert job processing definitions of jobName
job for TableName into the database.
6169 functionName: Failed on processing componentType componentName -

JOB is not defined.
Explanation: The ctmimptb utility failed on processing the specified
component due to undefined related job.
The ctmimptb utility aborts with an error.
User response: Activate the ctmimptb utility with debug level 3 and contact
Customer Support.
6170 functionName: Failed on processing jobName - Scheduling Table is not

defined.
Explanation: The ctmimptb utility failed on processing the specified job that is
related to the scheduling table that was imported from a previous transaction.
User response: Activate the ctmimptb utility with debug level 3 and contact
Customer Support.
6171 functionName: scheduling table tableName already exists in the database

and overwrite was specified. Overwriting this table.
Explanation: The specified scheduling table currently exists in the database and
the ctmimptb is about to overwrite it because overwrite mode was specified.
The ctmimptb utility imports the specified scheduling table.
6172 Import failed. Job definition table tableName partially imported.

Explanation: The ctmimptb utility failed and the tableName table was partially
imported into the database.
User response: Search for the error in the utility log, and contact Customer
Support. After resolving the problem, perform one of the following steps in
order to complete the import:

If the ctmimptb utility is executed with specifying overwrite mode - rerun

the utility.
If the ctmimptb utility is not executed with specifying overwrite mode,

extract the specified table from the original XML file to a temporary file and
then rerun the ctmimptb utility in overwrite mode by using the input XML
file as the temporary file. If you have one or more additional job definition
tables to import in the original XML file, rerun the ctmimptb utility by using
the original input XML file but without specifying overwrite mode. If there
are one or more additional job definition tables to import in the original
XML file - rerun the ctmimptb utility using the original input XML file but
without specifying overwrite mode.
6174 Import finished successfully.

Explanation: All the job definition tables from the XML file were imported into
the database successfully.
The ctmimptb utility finished successfully.
6175 Import was partially successful.

Explanation: The ctmimptb utility rejected some imported job definition tables
from the XML file.
The ctmimptb utility finished successfully.
User response: Search for the reason for the rejection in the utility log.
6176 Import failed. No table was imported into the database.

Explanation: The ctmimptb utility failed and a job definition table was not
imported into the database.
User response: Search for errors in the utility log, and contact Customer
Support.
6177 Import failed. Not all the job definition tables were imported.
Explanation: The ctmimptb utility performed a partial import. Those job
definition tables that were imported, were completely imported into the
database.
User response: Search for errors in the utility log, and contact Customer
Support.

6178 Starting import of job definition tables from file: fullPathFileName Overwrite
mode: mode
Explanation: The ctmimptb utility started processing the XML file to import the
job definition tables.
The ctmimptb utility started parsing the XML file for the import process.
6179 End of import of job definition tables.

Explanation: The ctmimptb utility finished processing the XML file to import
the job definition tables.
The ctmimptb utility finished parsing the XML file for the import process.

6200 functionName fail to initialize a message list for messageType message to

agent nodeID, request will be aborted
Explanation: The specified function was unable to generate a message list for
the requested message type, and therefore the request for which the message
generation attempted for Agent nodeID is aborted.
Control-M/Server attempted to create a messageType message.
1 Check available memory on the machine.
2 Try to disable Agent nodeID.
3 If messages continue to appear, contact BMC Software Customer Support.
6201 functionName fail to initialize messageType header message to agent

nodeID, request will be aborted
Explanation: The specified function was unable to generate a header message
from the messageType type, and therefore the request for which the message
generation is attempted for Agent nodeID is aborted.

6202 functionName fail to append messageType header message to agent

nodeID, request will be aborted
Explanation: The specified function was unable to append a header message
from the messageType type, and therefore the request for which the message
generation is attempted for Agent nodeID is aborted.
6203 functionName fail to create messageType message to agent nodeID,

request will be aborted
Explanation: The specified function was unable to generate a message from the
messageType type, and therefore the request for which the message generation is
attempted for Agent nodeID is aborted.
6204 functionName received from agent a corrupt message <<<< message>>>>

Explanation: The specified function attempted to handle a message from a
Control-M/Agent, but found it to be corrupted.

Control-M/Server attempted to handle a request from Control-M/Agent.
User response: Check previous messages, and contact BMC Software Customer
Support.
6205 functionName fail to create temporary status file: fileName

Explanation: The specified function attempted to create temporary status file
for a job.
Control-M/Server attempted to create a new status file.
1 Check the disk and the disk space where Control-M/Server is installed.
2 Check the file system where Control-M/Server is installed.
6206 functionName fail to write temporary status file: fileName

Explanation: The specified function attempted to write a temporary status file
for a job.
Control-M/Server attempted to write data to a status file.
6207 functionName fail to close temporary status file: fileName

Explanation: The specified function attempted to close a jobs temporary status
file.
Control-M/Server attempted to close a status file.
6208 functionName fail to rename temporary status file: fileName1 to status file:
fileName2
Explanation: The specified function attempted to rename a jobs temporary
status file.

Control-M/Server attempted to rename a status file.
6209 functionName fail to make a message list from a message buffer, request
will be aborted
Explanation: The specified function was unable to make a message list from
message buffer, and therefore the request for which the message list generation
is attempted is aborted.
Control-M/Server attempted to create a message list from a message buffer.
6210 functionName fail to get header message, request will be aborted

Explanation: The specified function was unable to locate a header message, and
therefore the request is aborted.
Control-M/Server attempted to fetch a header message from a message list.
6211 functionName unSupported request code (requestCode) received from

agent nodeID
Explanation: The specified function received a request with an unSupported
request code from Agent nodeID.
Control-M/Server attempted to generate a request code sent by an Agent.

6212 functionName received termination request by user

Explanation: The specified function received a request to terminate from the
shut_ctm utility.
Control-M/Server attempted to handle a request.
User response: Start the Control-M/Server by executing the start_ctm utility.
6213 functionName unSupported request code (requestCode) received from one

of the server processes
Explanation: The specified function received a request with an unSupported
request code from one of the server processes.
Control-M/Server attempted to generate a service from a request code sent by

one of the Server processes.
Support.
6214 functionName null logical TCP session pointer, current service is aborted
Explanation: The specified function tried to send a message to an Agent using a
corrupted TCP session with this Agent, and therefore the service is aborted.
Control-M/Server attempted to send a message to an Agent.
Support.
6215 functionName failed to create a new physical protocol communication

channel
Explanation: The specified function failed to create a new communication
channel of type protocol, and therefore the request is aborted.
Control-M/Server attempted to create a new communication channel.
6216 functionName communication error INET protocol type (protocol) is not

Supported
channel of an unSupported protocol, and therefore the request is aborted.

6217 functionName communication error protocol mode (protocol) is not

Supported
channel of an unSupported protocol, and therefore the request is aborted.
6218 functionName failed to create a new logical protocol communication channel

Explanation: The specified function failed to create a new logical
communication channel of type protocol, and therefore the request is aborted.
Control-M/Server attempted to create a new logical communication channel.
6219 functionName failed to up-class a physical communication channel to a

physical protocol communication channel
Explanation: The specified function has a corrupt physical communication
channel, and therefore the request is aborted.
Control-M/Server attempted to connect to a physical communication channel.
Support.
6220 functionName failed to connect to client (nodeID) at port (portNumber)

Explanation: The specified function failed to connect to Agent nodeID at TCP/
IP port portNumber, and therefore the request is aborted.

Control-M/Server attempted to connect to a communication channel.
1 Check that Agent nodeID is up and running.
2 Check that TCP/IP port portNumber is correct.
3 Check that Agent nodeID exists. If Agent nodeID does not exist, then the next
time you shut Control-M/Server, delete CTM HOME/ctm/data/AGPRM/
nodeID and CTM HOME/ctm/data/AGSTAT/nodeID.
6221 functionName failed to disconnect session of logical TCP communication

channel (channel) of physical session id (sessionID)
Explanation: The specified function failed to disconnect a logical TCP
communication channel (channel) with an Agent identified by sessionID. The
operation attempts to continue.
Control-M/Server attempted to close a communication channel.
User response: If messages continue to appear, contact BMC Software Customer

Support.
6222 functionName connected client name (nodeID) is already connected

Explanation: The specified function received a request to choose a persistent
connection for disconnection when the maximum number of concurrent
sessions has been reached, but found that the requested Agent for connection
was already connected.
Control-M/Server attempted to choose a persistent session for disconnection

when maximum concurrent sessions have already been reached.
Support.
6223 functionName fail to get parameter agent parameter value for client name
(nodeID) using default
Explanation: The specified function failed to retrieve an Agent parameter value,
and therefore tries to continue using the default value.
Control-M/Server attempted to check an Agent parameter value.
1 Check that the Agent file CTM HOME/ctm/data/AGDEFS/AGDEFS exists,

and that the directories CTM HOME/ctm/data/AGPRM and CTM HOME/
ctm/data/AGSTAT exist.

6224 Connected persistent sessions:

--------------------------------------------------------------------------------
Total concurrent sessions: sessions out of maxSessions
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Physical Session (pointer): nodeID.port
Client Name: nodeID
Total services: servicesNum
Duration: durationNum seconds
Last activity: activityNum seconds
Service Name: SRVC_TYPE_SUBMIT active: num total: num
Service Name: SRVC_TYPE_EXIT_STATUS active: num total: num
Service Name: SRVC_TYPE_TRACE_ALL active: num total: num
Service Name: SRVC_TYPE_DOWN_SYSOUT active: num total: num
Service Name: SRVC_TYPE_DOWN_JCL active: num total: num
Service Name: SRVC_TYPE_UP_JCL active: num total: num
Service Name: SRVC_TYPE_UP_JCL active: num total: num
Service Name: SRVC_TYPE_UTIL active: num total: num
Service Name: SRVC_TYPE_TUNNEL active: num total: num
Service Name: SRVC_TYPE_AGENT_AVAILABILITY active: num total: num
Service Name: SRVC_TYPE_PASS_REPLY active: num total: num
Service Name: SRVC_TYPE_PASS active: num total: num
Service Name: SRVC_TYPE_AG_PING active: num total: num
Service Name: SRVC_TYPE_VERSION active: num total: num
Explanation: Control-M/Server produces a printout of the status and statistics
of the current connected persistent sessions.
User response: Issue the following command to produce the printout:
ctmipc -dest NS -msgid NSS [-data "PRT 0"]
6225 Disconnected persistent sessions:

--------------------------------------------------------------------------------
Total concurrent sessions: sessions out of maxSsessions
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Disconnected Agent: nodeID
Duration: durationNum seconds
--------------------------------------------------------------------------------
Explanation: Control-M/Server produces a printout of the current disconnected
persistent sessions.
User response: Issue the following command to produce the printout:
ctmipc -dest NS -msgid NSS -data "PRT 9"
6226 functionName failed to create a new disconnected session for client name
(nodeID)
Explanation: The specified function failed to create a new disconnected session
when maximum concurrent sessions were reached.

Control-M/Server chooses a persistent session for disconnection when

maximum concurrent sessions are reached.
6227 functionName failed to send alerts on event

Explanation: The specified function failed to send alerts to Control-M/EM, the
system console, and the IOALOG when the specified even occurred.
Control-M/Server attempted to send alerts to Control-M/EM, the system

console, and the IOALOG.

Support.
6228 functionName operation (opCode) is not Supported

Explanation: The specified function failed to register a event associated with an
unSupported opCode operation, and therefore the request is aborted.
Control-M/Server attempted to register a callback event.
Support.
6229 functionName failed on SSL client operation server operation with physical
session id (sessionID) sid= code
Explanation: The specified function failed to complete an SSL operation with an
Agent that is identified by sessionID, and therefore the request is aborted.
Control-M/Server attempted to generate an SSL communication with an Agent.
1 Check that your SSL keys (ctmkey.kdb and agkey.kdb) match.
6230 functionName failed to set SSL session option (option) with physical
session id (sessionID)
Explanation: The specified function failed to complete an SSL connection with
an Agent that is identified by sessionID, and therefore the request is aborted.

6231 functionName failed on SSL server operation client operation with physical
session id (sessionID) sid= code
Explanation: The specified function failed to complete an SSL operation with an
Agent that is identified by sessionID, and therefore the request is aborted.
6232 functionName process processName will terminate after receiving

SIGTERM signal
Explanation: The specified function received a kill request for process
processName.
Control-M/Server issued a kill process shell command.
6233 functionName got an invalid SSL profileType profile pointer while SSL
protocol is enabled.
Explanation: The specified function obtained a corrupted SSL profile for
profileType, and therefore the process is aborted.
Control-M/Server attempted to initialize an SSL client or server profile.

Support.
6234 functionName got a negative value for PORTNUM entry in AGDEFS table
Explanation: The specified function obtained an invalid value for a TCP/IP
port number, and therefore the process is aborted.
Control-M/Server attempted to initialize the default agent port number.

1 Check the disk space and file system.
2 Check that the Agent defaults file (CTM HOME/ctm/data/AGDEFS/

AGDEFS) exists, and use the ctm_menu utility to reset the default agent port
number.
6235 NS initialization failed process will be aborted

Explanation: NS is unable to initialize due to various environmental issues, and
therefore the process is aborted.
Control-M/Server attempted to initialize the NS process.

Support.
6236 NS service manager failed to start default services, process will be aborted
Explanation: NS failed to create a listener for Agents request or Server process
requests, and therefore the process is aborted.
1 Find a free port number, and use the ctm_menu utility to assign that new
port number to the Agent-to-Server Port Number parameter.
2 If messages continue to appear, find a free port number, and use the
ctm_menu utility to assign that new port number to the Inter Process
Communication Port Number parameter.
6237 NS agent availability failed to start, process will be aborted

Explanation: NS failed to start the Agent availability service, and therefore the
process is aborted.
Support.
6238 functionName failed to open INET listen channel for HOST: host on PORT:
port
Explanation: The specified function failed to open a new TCP/IP listener for
Agent requests for host on TCP/IP port, and therefore the process is aborted.

User response: Find a free port number, and use the ctm_menu utility to assign
that new port number to the Agent-to-Server Port Number parameter.
6239 functionName failed to open CTMS listen channel for NAME: IPCCode
Explanation: The specified function failed to open a new Inter Process
Communication listener for the Server process requests, and therefore the
process is aborted.
User response: Find a free port number, and use the ctm_menu utility to assign
that new port number to the Inter Process Communication Port Number
parameter.
6240 functionName failed to up-class an abstract channel to a communication

channel (pointer)
Explanation: The specified function has a corrupt communication channel, and
therefore the request is aborted.
Control-M/Server attempted to open a new communication listener.
Support.
6243 functionName failed to delete node group nodeGroup information from

table databaseTable, code= rc
Explanation: The deletion of the node group from the database failed.
The Control-M Configuration Manager displays an error message.
User response: Check other messages in the log file, database logs, and contact
6244 functionName failed to insert node group nodeGroup into table

databaseTable, code= rc
Explanation: The insertion of the node group to the database failed.
The Control-M Configuration Manager displays an error message.


6300 functionName : Inconsistent Control-M Server to Control-M Agent message

list
Explanation: A message from Control-M/Server to Control-M/Agent includes
invalid data.
Control-M/Server frees the memory allocated for the message.
Support.
6301 functionName : Control-M Server to Control-M Agent message pointer is

not initialized
invalid data.
Support.
6302 functionName : Control-M Server to Control-M Agent Message buffer is not

initialized
invalid data.
Support.
6303 functionName : Control-M Server to Control-M Agent Messages list is not

initialized
invalid data.
Support.

6304 functionName : The value of CPU used sent by the Control-M Agent is
negative : CPU_used
Explanation: The value of CPU_used sent by the Control-M/Agent to the Control-
M/Server is negative.
Control-M/Server sets the value for CPU usage to 0.
Support.
6305 functionName : The value of 'elapse time' sent by the Control-M Agent is
negative: time
Explanation: The value of time sent by the Control-M/Agent to the Control-M/
Server is negative.
Control-M/Server sets the value for elapsed time to 0.
Support.
6306 functionName : Control-M Server to Control-M Agent message type not

found. Message type : messageType.
Explanation: The message type sent from or to Control-M/Server is not found.
Support.
6307 functionName : Control-M Server to Control-M Agent message is empty

Explanation: The message type sent by the Control-M/Server or received by
the Control-M/Server is invalid.
Support.
6308 functionName : Gateway older than 613 cannot connect data center 613 or
above
Explanation: You are trying to connect a Gateway version 6.1.0 or earlier to
Control-M/Server version 6.1.3 or later.
Control-M/Server refuses to connect to Control-M/EM.
User response: Check the versions of Control-M/EM and Control-M/Server,

and connect Control-M/Server version 6.1.3 or later to a compatible version of
Control-M/EM.

6309 functionName : Unknown service ID received from Control-M EM

Explanation: The Control-M/Server receives an unknown service ID from
Control-M/EM.
One of the following has occurred:
If the Control-M/Server was trying to connect to Control-M/EM, the server

refuses to connect to Control-M/EM.
If the Control-M/Server was handling a user request, the user request is

rejected.
Support.
6310 functionName : Database transaction failed to commit. Return code = rc

Explanation: The database transaction could not commit.
In this message, valid values for rc are CM_FAIL or CM_EOF.
User response: Check the database logs, and contact on-site DBA Support.
6311 functionName : Database fail to open a new transaction

Explanation: The database could not open a new transaction.
6312 functionName : Failed to clean statistic information. Return code = rc

Explanation: Control-M/Server could not clean the statistic information table
during the New Day procedure.
In this message, the only valid value for rc is CM_FAIL.
Control-M/Server performs the following:
Writes to the CMR_IOALOG table that the attempt to clean statistic

information failed
Sends an alert to Control-M/EM
6313 functionName : Database transaction failed to rollback. Return code = rc

Explanation: The database transaction could not roll back.

6314 functionName : Failed to clean CMR_JOBINF table. Return code = rc

Explanation: Control-M/Server could not clean the CNR_JOBINF table during
the New Day procedure.
Control-M/Server sends an alert.
6315 functionName : Ignore Conditions file exceeded maxEntries entries

Explanation: The dbs_ignrcond.dat Ignore Conditions file contains more than
the maxEntries number of conditions.
Control-M/Server handles only the maxEntries number of conditions, and

ignores the remainder.
User response: Minimize the number of conditions in the dbs_ignrcond.dat file.
6316 functionName Failed to delete condition : condName, condDate

Explanation: Control-M/Server could not delete the specified condName
condition during the New Day procedure.
Control-M/Server performs a database rollback.
6317 functionName Fail to allocate memory for AGSTAT information

Explanation: Control-M/Server could not allocate memory for AGSTAT
information.
Control-M/Server writes an error message to the IOA log file.
User response: Contact your systems administrator.
6318 functionName Fail to open AGSTAT file

Explanation: Control-M/Server could not open the AGSTAT file.
Sysouts are not cleaned during the New Day procedure.

6319 functionName Agent nodeID newday cleanup failed. Return code = rc

Explanation: Control-M/Server could not send a New Day cleanup message to
one of the Agents.
In this message, valid values for rc are:
rc Explanation
CM_MBX_BUFFEROVF Buffer is too large
CM_MBX_FULL Could not send IPC message
CM_FAIL
Sysouts are not cleaned during the New Day procedure for the specified Agent.
Control-M/Server writes a message to the IOA log file.
User response: Contact your systems administrator for help in solving

connection problems.
6320 functionName Fail to fetch next record from AGSTAT table. Return code = rc
Explanation: Control-M/Server could not fetch the next record from the
AGSTAT table for an Agent.
Sysouts are not cleaned during the New Day procedure for this Agent.
Support.
6321 functionName Failed to translate local date and time information given
specific Time Zone
Explanation: Control-M/Server could not translate the local date and time
information, given a specific time zone.
Change to the next time zone.
Support.

6322 functionName Failed to perform new day process for time zone timeZone,
odate odate
Explanation: Control-M/Server could not perform the New Day procedure for
the specified time zone.
User response: Try to run the New Day procedure at a later time.
6323 functionName Failed to select jobs from active jobs file where time zone =
timeZone
Explanation: Control-M/Server could not perform the New Day procedure for
the specified time zone.
Move to the next time zone.
Support.
6324 functionName Failed to update the job's status on the active jobs list
during new day
Explanation: Control-M/Server could not update the job's status to Wait
Scheduling or Post Odat during the New Day procedure.
Perform a database rollback.
Support.
6325 functionName Failed to release control resources during new day process
for order number orderNumber
Explanation: Control-M/Server could not release the control resource for a
specific job during the New Day procedure.
Support.
6326 functionName Failed to release quantitative resources during new day

process for order number orderNumber
Explanation: Control-M/Server could not release the quantitative resource for
a specific job during the New Day procedure.
Support.

6327 functionName Failed to delete the file fileName

Explanation: Control-M/Server failed to delete the fileName file.
6328 functionName Failed to update autoedits from Control-M Agent

Explanation: Control-M/Server failed to update AutoEdits from Control-M/
Agent.
Support.
6329 functionName Job have reached timeout for state jobState.

Explanation: The jobState job timed out.
Control-M/Server declares the job as Disappeared.
6330 functionName Failed to read order number orderNumber from active jobs
list. Return code = rc
Explanation: Control-M/Server failed to read this order number from Active
Jobs list.
In this message, valid values for rc are CM_FAIL or CM_EOF.
The Tracker process cannot handle this job.
6331 functionName Failed to select post processed jobs from active jobs list
Explanation: During the deletion of the status file, Control-M/Server failed to
select post-process jobs.
Control-M/Server could not delete the status file for these jobs.
6332 functionName A corrupted status file received from Control-M Agent

Explanation: The status file received from Control-M/Agent contains
corrupted information.
System processing continues. The status file is saved for debugging.
Support.

6333 functionName When a corrupted status file received, rename the file
fileName1 to fileName2
Explanation: A corrupted status file should be renamed.
The status file is saved for debugging.
Support.
6334 functionName Unable to rename fileName1 to fileName2

Explanation: A file could not be renamed.
User response: Contact on-site DBA Support.
6335 functionName Failed to initialize connection to database

Explanation: Control-M/Server failed to initialize a connection to the database.
Control-M/Server could not start.
6336 functionName Failed to check link to database server

Explanation: The link to the database server could not be checked when the
Control-M/Server starts.
6337 functionName Failed to open CMS_SYSPRM table

Explanation: Control-M/Server could not open the CMS_SYSPRM table.
6338 functionName Failed to clean list

Explanation: Control-M/Server failed to clean the dblog and ioalog lists in
memory.
Control-M/Server cannot start the SL process.
Support.

6339 functionName Failed to close connection when the process is shutting down
Explanation: Control-M/Server failed to close the connection to the database
when the process shuts down.

6400 functionName: error allocating entity

Explanation: Control-M failed to allocate memory for an entity.
The catastrophe flag is raised, and as a result, the process shuts down.
User response: Check available memory on the machine.
6401 functionName: error in mutex creation: rc

Explanation: Control-M failed to create a mutex synchronization object.
6402 functionName: error creating message Q rc

Explanation: Control-M failed to create a message queue.
User response: Check available memory on the machine, and contact BMC
6403 functionName: error destroying mutex in cleanup rc

Explanation: Control-M failed to destroy a mutex synchronization object
during cleanup after thread entity creation. This cleanup takes place only when
some other severe error occurs.
User response: Respond as required for the previously displayed error

messages.

6404 functionName: asked to terminate a running thread id= threadID

Explanation: A running thread is destroyed by the threads manager. This only
occurs when the process shuts down due to an internal error.
The process shuts down.
User response: Check other messages in the log file, and contact BMC Software
Customer Support.
6405 functionName: error destroying mutex rc

Explanation: A mutex synchronization object could not be destroyed during
process shutdown. This may happen if the destroyed mutex object is locked by
a thread.
None
6406 functionName: error locking mutex rc

Explanation: A mutex synchronization object could not be locked.
6407 functionName: error unlocking a mutex rc= rc

Explanation: A mutex synchronization object could not be unlocked.
6408 functionName: error creating threads dynamic array rc= rc

Explanation: A threads data structure could not be created on startup.
6409 functionName: error allocating work Qs array

Explanation: Memory could not be allocated on startup.

6410 functionName: error duplicating message for thread with index threadIndex
rc= rc
Explanation: A thread message could not be duplicated.
6411 functionName: error in sending message to Q type queueType thread

threadIndex rc= rc
Explanation: A message could not be sent to a thread message queue.
6412 functionName: failed to get status of thread with index threadIndex rc= rc
Explanation: A thread's status could not be obtained.
6413 functionName: failed to add message to thread message Q rc= rc

Explanation: A message could not be added to a thread message queue.
Customer Support.
6414 functionName: thread message id messageID without destination

Explanation: A thread message without a destination was found when the
thread was sending the messages that were waiting to commit.
The thread message was not sent. Processing continues.
6415 functionName: thread with index threadIndex has kpa problem

Explanation: A thread did not update its keep alive flag.

Customer Support.
6416 functionName: error creating thread message with id messageID rc= rc

Explanation: A thread message was not created. The reason for this error is
probably a failure to allocate memory.
6417 functionName: error in priority Q creation rc= rc

Explanation: A priority queue was not created during startup.
6418 functionName: error in signaling condition rc= rc

Explanation: A condition synchronization object was not signaled, which is
necessary to notify a thread that it has messages waiting. This failure may cause
a thread to remain sleeping and not wake up to handle its messages.
Customer Support.
6419 Unable to read CMS_SYSPRM

Explanation: The selector process failed to read from the parameters table
while in suspend mode. Using the information in the parameters table, the
process detects that a new day is in progress, and if so:
1 Performs cleanup of submission queue internal data structure.
2 Marks internal memory data structures to be refreshed when leaving the

suspend mode.
A single failure to read this table is harmless because the process will keep
trying to read it. A continuous failure that is not resolved until the end of the
New Day procedure may cause late submission of jobs that were waiting in the
submission queue when the New Day procedure began (that is, were ready to
be submitted but were not submitted.

The process stays in suspend mode, and after a while tries to read the table again.
User response: In case of repeated messages of this kind, shut down Control-M/
Server and contact BMC Software Customer Support.
6420 functionName: Failed to initialize threads in main. rc = rc

Explanation: A process failed to initialize its threads.
Customer Support.
6421 functionName: Catastrophic failure while mainAction

Explanation: A main thread detects that the catastrophe flag was set by one of
its threads.
Customer Support.
6422 functionName: Failure occurs - Threads have not changed their states.
State = {SUSPEND | RUN}
Explanation: Not all threads reached their desired state on startup. Threads
start in suspend state; when all threads reached suspend state, the main thread
sends a run message, the states of all threads change to run, and normal
execution begins.
Customer Support.
6423 functionName: Thread status pointer is not initialized

Explanation: Thread information data is corrupt.
6424 functionName: failed in checking threads state rc= rc

Explanation: The threads state could not be checked.

Customer Support.
6425 functionName: error inserting thread entity to threads array rc= rc

Explanation: The internal threads data structure could not be updated during
process startup.
6426 functionName: main thread failed to wait for state change rc= rc
Explanation: Sleep activity for the main thread was stopped prematurely. The
reason for the sleep failure can be seen in previous messages in the log file.
Customer Support.
6427 functionName: error creating threads manager object rc= rc

Explanation: Creation of the main threads data structure failed during process
startup.
Customer Support.
6428 functionName: failed to get kpa value for thread with index threadIndex
Explanation: The main thread failed to read the keep alive value of one of the
threads. This is probably due to a failure in a mutex synchronization object.
Customer Support.
6429 functionName: Unknown process state state

Explanation: The transition of process state to thread state during a process
state change failed due to an unknown process state.

6430 functionName: Failure while trying to send to all threads a change state
message. with id state
Explanation: The main thread failed to send a state message to all threads.
Customer Support.
6431 functionName: Error adding thread work queue - array is full

Explanation: The internal data structure work queue array is full.
6432 functionName: Cannot add thread message to queue - message is corrupt

Explanation: The addition of a message to a thread message queue failed
because the message is corrupt.
6433 functionName: Failed to pop a message from message queue rc= rc

Explanation: A failure occurred when trying to pop a message from a thread
message queue.
6434 functionName: Failure occurs - Submission and presub threads have not
changed their states to SUSPEND. Going out
Explanation: When the main selector thread detects that a New Day procedure
is in progress, before cleaning the submission queue (the queue of jobs waiting
to be submitted) it verifies that the submission and presubmission threads are
in suspend state. This error is displayed when the threads are not in suspend
state, or when the check of their state fails.

6435 functionName: Failure occurred - Refresh has was not been performed. rc =
rc
Explanation: The refresh (update of internal data structures from the database)
process failed.
6436 functionName: validity check of hi_load_start value failed

Explanation: The value of the SL_HI_LOAD_START parameter in the
config.dat file is not valid.
The system processes this scenario, as the selector process is not in a high load
period, and therefore a refresh can be performed.
User response: Change the value of the SL_HI_LOAD_START parameter to be

a valid value.
6437 functionName: validity check of hi_load_end value failed, setting

hi_load_end value to blank.
Explanation: The value of the SL_HI_LOAD_END parameter in the config.dat
file is not valid.
The system assumes that no high load end time was set, and therefore the
current time is the end time.
User response: Change the value of the SL_HI_LOAD_END parameter to be a

valid value.
6438 functionName: Failure occurred while trying to clean the message Q of

main thread. rc = rc
Explanation: Cleaning of certain messages from the main thread queue prior to
a refresh (update of internal data structures from the database) has failed.
The system continues to perform the refresh. The messages that were not
cleaned cause redundant work to be performed.
6439 functionName: Failed while trying to send refresh message to the

threadName thread
Explanation: A refresh (update of internal data structures from the database)
message was not sent to a thread.
This thread does not perform a refresh. The catastrophe flag may be raised, and
as a result, the process shuts down.

6440 functionName: error in sending message to thread work queue with index
threadIndex rc= rc
Explanation: A message could not be sent to a thread work queue.
6441 Failed to create temporary file name under directory dirName, rc

Explanation: Control-M/Server failed to create a temporary file name during a
test agent operation.
The test agent operation is aborted.
Check preceding messages.
Check possible reasons for the failure to create a temporary file, such as
incorrect or missing permissions, lack of disk space, and so on.
6442 functionName : Failed to serialize remote host, rc

Explanation: A failure occurred while serializing remote host details into a file
during a test agent operation.
The test of the operation is aborted.
User response: Check preceding messages, and contact BMC Software

Customer Support.
6443 functionName: Failed to deserialize remote host, rc

Explanation: A failure occurred while de-serializing remote host details into a
file during a test agent operation.
The test of the operation is aborted.
User response: Check preceding messages, and contact BMC Software

Customer Support.
6444 functionName : Failed to update AGSTAT file of nodeID, rc

Explanation: Control-M/Server failed to update the AGSTAT file for a node ID.
Currently, this message appears while discovering remote hosts that are
mapped to Default as the node ID, because of a change in the default node IDs
settings.

The remote host identified in this message is not re-discovered.
Check for a reason why an update of the file named as the node ID in the data/
AGSTAT directory failed. Possible reasons are hardware problems or the
lack of free disk space.
Ping all remote hosts that are mapped to Default as the node ID (that is, that
have no specific mapping).
6445 functionName: Failed to locate file fileName rc= rc.

Explanation: Failure to locate an internal tmp file during plugable
configuration agent operation.
The Control-M Configuration Manager operation fails.
User response: Check the disk space and contact BMC Software Customer
Support.

6500 functionName: Failed while initializing the thread, rc = rc. Going out.
Explanation: A thread fails to perform all initializations needed, in order to
start working.
A thread goes down. As a result, the process goes down after it detects that the
thread is no longer alive.
Customer Support.
6501 functionName: Failed while initializing the thread's prolog, rc = rc

Explanation: A thread fails to perform major initializations such as creating
data structures, establishing a connection to database, and so on.
The thread goes down. As a result, the process goes down after it detects that
the thread is no longer alive.
Customer Support.

6502 functionName: Failed while fetching the thread's message queue, rc = rc

Explanation: A thread fails to retrieve its message queue. A thread message
queue is essential for a thread for handling messages coming from other
threads.
Customer Support.
6503 functionName: Failed while setting the thread status to status, rc = rc.
Going out.
Explanation: A thread fails to change its status.
Customer Support.
6504 functionName: Failed while getting the thread's status, rc = rc. Going out.
Explanation: A thread fails to get its current status.
Customer Support.
6505 functionName: A thread has reached an unrecognized status status. Going

out.
Explanation: When fetching its status, a thread realizes that it is an invalid
status.
Customer Support.
6506 functionName: A thread has received an unrecognized message messageID

Explanation: A thread has received a message, but cannot handle the message
because it does not belong to the thread.

The message was not handled. The thread continues.
6507 functionName: Failed while handling a submission of job orderNumber, rc

= rc.
Explanation: Handling a submission of a job has failed.
User response: Check other messages in the log file to help find a possible
reason.
6508 functionName: Failed while trying to mark a job orderNumber, as failed in

submission rc = rc.
Explanation: The submission thread fails to indicate that the job was submitted.
Customer Support.
6509 functionName: Failed while popping job orderNumber, from submission

queue, rc = rc.
Explanation: The submission thread fails to pop the submitted job out of the
submission queue.
Customer Support.
6510 functionName: Failed while fetching a message from submission queue.

Explanation: The submission thread has failed to fetch a message from the
submission queue.
Customer Support.

6511 functionName: Failed while notifying on submission failure, for job

orderNumber, rc = rc
Explanation: The submission thread fails to notify on submission failure for a
job.
Customer Support.
6512 functionName: A thread has failed to clean its message queue, rc = rc

Explanation: A thread fails to clean its message queue. This might occur while
performing a refresh action.
Customer Support.
6513 functionName: No destination is found to where a message should be sent,

msg = messageData.
Explanation: The communication thread does not find the destination where
the message should be sent.
A message is not sent.
reason and contact BMC Software Customer Support.
6514 functionName: Failed while creating dataStructure, rc = rc

Explanation: An internal data structure could not be created.
Catastrophic is set. This causes the process SL to terminate.
User response: Check memory available on the computer. Check other

messages in the log file, and contact BMC Software Customer Support.
6515 functionName: Thread manager has failed to create the thread threadName,
rc = rc.
Explanation: Some of the threads are not created.
User response: Check memory available on the machine. Check other messages
in the log file, and contact BMC Software Customer Support.

6516 functionName: Failed to create thread with invalid type type

Explanation: A thread of an illegal type was not created.
6517 functionName: Process has failed to Initialize its prolog, rc = rc

Explanation: A process has failed to perform all initializations needed, in order
to start working.
Customer Support.
6518 functionName: No job is marked as Fail in submission queue, rc = rc, Going

out.
Explanation: You expect to have a job which failed to be submitted, but no such
job was found.
User response: Check SL submission thread log for messages about jobs which
failed to be submitted.
6519 functionName: Failure occurred - Release resource failed, for a job

orderNumber rc = rc.
Explanation: Allocated resources of a job failed to be released.
User response: Try to release the job's resources manually. Check other
messages in the log file, and contact BMC Software Customer Support.
6520 functionName: Failed while sending condition message to thread thread for
cond condition.
Explanation: An update (delete, add, and so on) regarding a condition was not
sent to a thread. As a result, jobs which depend on this condition may not be
affected by the action.
Customer Support.

6521 functionName: Failed while sending control message to thread thread for
resource resource.
Explanation: An update (delete, add, and so on) regarding a control resource
was not sent to a thread. As a result, jobs which depend on this resource, may
not be affected.
Customer Support.
6522 functionName: Failed while trying to send quantitative message to thread

thread for resource resource.
Explanation: An update (delete, add, and so on) regarding a quantitative
resource was not sent to a thread. As a result, jobs which depend on this
resource, may not be affected.
Customer Support.
6523 functionName: Failed while sending order message for job orderNumber, to
thread thread.
Explanation: A message regarding a certain job was not sent to a thread. The
message is regularly sent:
When a job is added to the active table and needs to be handled.
When a job is already in the active table and needs to be post-processed.
When a job is post-processed and needs to be rerun (cyclic, or Do Rerun).
As a result, the job will not be handled.
Customer Support.
6524 functionName: Failed while sending order but not submit message for job
orderNumber, to thread thread.
Explanation: A message regarding a dummy or group type job was not sent to
a thread.
The message is regularly sent when a job is inserted to the active table and
needs to be handled. As a result, the job is be handled.

Customer Support.
6525 functionName: Failed while sending a change state SUSPEND to

submission thread, rc = rc.
Explanation: Before the presub thread performs a refresh, it requests the
submission thread to move to SUSPEND mode. The request was not sent.
Customer Support.
6526 functionName: Failed while sending a change state RUN to submission

thread, rc = rc.
Explanation: When a refresh ends, the presub thread sends a request to the
submission thread to move to RUN mode. The request was not sent.
Customer Support.
6527 functionName: Failed while sending a notification to submission thread,

job orderNumber, rc = rc.
Explanation: When a job is ready for submission, the presub thread adds it to
the submission queue. If the queue is empty, a notification message is sent to
the submission thread. The message was not sent.
Customer Support.
6528 functionName: Failed while handling a change state message for thread
with index index, new status state, rc = rc.
Explanation: A threads state did not change after receiving a change state
message.
Customer Support.
6529 functionName: Failed while handling a KPA message for thread with index
index, rc = rc.
Explanation: A threads KPA was not updated after receiving a KPA message.

Eventually, the SL main thread goes down after detecting a KPA problem with
one of its threads.
Customer Support.
6530 functionName: Failed while sending Do not handle job Message, for job
orderNumber, to thread thread, rc = rc.
Explanation: A Do not handle job message was not successfully sent to a
thread.
Customer Support.
6531 functionName: Failed while sending change status message to a thread

with index index, new status status, rc = rc.
Explanation: A change status message was not sent to a thread.
The message was not handled.
6532 functionName: Process has reached terminate state. Going out.

Explanation: A process has reached its terminate state. This can happen due to:
A user request (shut_ctm or ecaprflag).
A request from the main process of Control-M/Server for all processes to go

down, due to a problem.
Process is about to go out.
Ignore the message.
Check other messages in the log file, and contact BMC Software Customer
Support.
6533 functionName: Failed while preparing job orderNumber for submission, rc

= rc
Explanation: A failure occurred while preparing a job for submission. As a
result, the job is not submitted.

System processing continues, but the job is not submitted.
Customer Support.
6534 functionName: Failed during job submission, job orderNumber, because of

reason.
Explanation: The submission of a job from the SL process to the NS process
failed.
Customer Support.
6535 functionName: Failed to commit, when releasing resources for job

orderNumber which was not submitted, rc = rc.
Explanation: Resources of a unsubmitted job could not be released.
Resources are not released.
Check database messages in the database error log. These resources should
be released. This can be done either by restarting Control-M/Server or by
releasing the resources manually.
Check other messages in the log file, and contact BMC Software Customer
Support.
6536 functionName: No allocated resources were found in database, for job

orderNumber, although they should be.
Explanation: This is an abnormal situation, where no allocated resources were
found in the database for job. The job required resources in its submission
criteria, and was not submitted.
Customer Support.
6537 functionName: Comm. thread has failed to establish IPC, rc = rc. Going out.
Explanation: The communication thread failed to establish communication
with the RT (router) process.

A thread goes down. As a result, the process goes down after it detects that the
thread is no longer alive.
User response: Change the Control-M/Server IPC port and try to restart Control-
M/Server. If the problem reoccurs, check other messages in the log file, and
6538 functionName: Thread manager failed to close, during action, rc = rc.

Explanation: The process thread manager closes just before the process
terminates. During its closure, it asks all threads to shut down, and then
performs various cleanup actions. Even though the close procedure failed, the
process thread manager is not gracefully closed.
The specified process shuts down.
reason.
6539 functionName: Message messageID to be sent to an invalid thread number.

Explanation: Control-M/Server tried to send a message to an invalid thread.
The message is not sent.
Customer Support.
6540 functionName: Refresh action failed in process process during action

Explanation: A process fails to perform a refresh (periodic updating of internal
data structures from the database). In the selector process, there are two actions
which may perform a refresh:
Selection (by presub thread).
Post-processing (by pp thread).
One of the following occurs:
If a failure occurs in the presub thread while it is starting up, then a

catastrophic is set and the process goes down. If it during work time, the
process continues.
If a failure occurs in the pp thread, the process continues.
User response: Check for error messages regarding database problems in the
Control-M/Server logs.

6541 functionName: Failed to read from file fileName, rc= rc

Explanation: Failure to read internal tmp file during a plugable configuration
agent operation.
User response: Check the filename and directory permissions on the Control-M/
Server computer and contact BMC Software Customer Support.

6600 Job orderNumber is neither a SMART Table nor a Sub-table

Explanation: An error occurred when a SMART Table job/Sub-table job was
forced OK. The jobs SMART Table/Sub-table order number does not point to a
SMART Table/Sub-table.
The job is forced OK, but its SMART TableSub-table is not modified.
User response: Check which SMART Table/Sub-table that the job belongs to.
6601 Job jobName does not exist in CMR_IOALOG

Explanation: The error occurred during a Log request. The specified job was
not found in the CMR_IOALOG table.
The jobs log is not displayed.
User response: Check the number of days the log is retained.
6602 CS_info_req_view_sysout: error reading CMR_AJF (Orderno=

orderNumber, Runcount= runCounter). Trying CMR_JOBINF
Explanation: The error occurred during a View Sysout request. The Control-M/
Server CMR_AJF query failed.
Control-M/Server checks the CMR_JOBINF table.
Support.
6603 CS_info_req_view_sysout: Orderno orderNumber runcount runCounter

does not exist in CMR_JOBINF and CMR_AJF
Explanation: The error occurred during a View Sysout request.

Control-M/Server does not display sysout information.
User response: Check the value of the Maximum Days to Retain Sysout Files
parameter.
6604 Cannot allocate memory.

Explanation: The error occurred during a Why request. Control-M/Server
could not allocate memory.
Control-M/Server displays an error message and not the required output of the
Why request.
6605 cs_info_process_xml_request: GM_XML_DOM_Parser_create failed

Explanation: The error occurred during an XML request. Control-M/Server
Control-M/Server displays an error message and not does not process the XML
request.
6606 cs_info_process_xml_requests: GM_XML_DOM_tree_walker_create failed

Explanation: The error occurred during an XML request. Control-M/Server
Control-M/Server displays an error message and not does not process the XML
request.
6607 cs_irr_printf: printing line is too long

Explanation: Control-M/Server attempted to display a message that is longer
than maximum allowed length.
Control-M/Server displays a truncated message.
6608 ERROR: unknown ZOOM part

Explanation: Control-M/Server received an incorrect message as part of a Zoom-
and-Save request.

The Zoom-and-Save action failed.
6609 CS_ZS_update_stmt: unknown ACTION type

Explanation: Control-M/Server received an incorrect DO action as part of a
Zoom-and-Save request.
The incorrect DO action is ignored.
6610 CM_SRVC_read failed: unable to save triggers.

Explanation: Control-M/Server attempted to save triggers, but the request
failed.
Control-M/Server could not allocate memory.
6611 CM_SRVC_read failed: unable to save triggers for later handling.

Explanation: Control-M/Server attempted to save triggers for later handling,
but the request failed.
6612 CM_SRVC_read_nowait: unable to save triggers.

Explanation: Control-M/Server attempted to save triggers, but the request
failed.
6613 CM_SRVC_read_ipc: Add failed - unable to save GTW triggers.

Explanation: Control-M/Server attempted to save Gateway triggers, but the
request failed.

6614 CM_SRVC_read_ipc: Add failed - unable to save signal triggers.

Explanation: Control-M/Server attempted to save signal triggers, but the
request failed.
6615 CS_HNDL_user_req_hold: Failed to hold job.

Explanation: Control-M/Server requested a job to be held, but the request
failed.
Control-M/Server did not update the database.
6616 functionName: Failed to force ok job

Explanation: Control-M/Server attempted to force a job to OK status, but the
request failed.
User response: Contact your database administrator.
6617 functionName: Failed to free job

Explanation: Control-M/Server attempted to free up a job, but the request
failed.
6618 functionName: Failed to delete job

Explanation: Control-M/Server attempted to delete a job, but the request
failed.
6619 functionName: Failed to undelete job

Explanation: Control-M/Server attempted to undelete a job, but the request
failed.

6620 functionName: Failed to confirm job

Explanation: Control-M/Server attempted to confirm a job, but the request
failed.
6621 functionName: Failed to rerun job

Explanation: Control-M/Server attempted to rerun a job, but the request failed.
6622 cs_info_why_check_qr: Failed to retrieve Quantitative Resources.

Explanation: Control-M/Server attempted to retrieve quantitative resources,
but the request failed.
Control-M/Server could not retrieve information from the database.
6623 CS_info_req_list_sysout: error reading CMR_IOALOG (Orderno=

orderNumber)
Explanation: Control-M/Server attempted to retrieve information about the
orderNumber job from the CMR_IOALOG table, but the request failed.
Control-M/Server could not retrieve the requested information.
6624 CS_info_req_list_sysout: Failed to retrieve the log of Orderno orderNumber

Explanation: Control-M/Server attempted to retrieve the orderNumber job log
from the CMR_IOALOG table, but the request failed.
Control-M/Server could not retrieve the requested information.

6625 CS_info_req_view_sysout: Orderno orderNumber runcount runCounter

does not exist in CMR_JOBINF>
orderNumber job with the specified runCounter from the CMR_JOBINF table, but
the request failed because the specified job does not exist in that table.
The requested jobs sysout could not be displayed.
parameter.
6626 CS_info_req_view_sysout: error reading CMR_JOBINF (Orderno=

orderNumber, Runcount= runCounter)
orderNumber job with the specified runCounter from the CMR_JOBINF table, but
the request failed.
6627 CS_info_req_list_sysout: error reading CMR_AJF (Orderno= orderNumber)

orderNumber job from the CMR_AJF table, but the request failed.
The sysout could not be displayed.
6628 CS_info_req_list_sysout: Orderno orderNumber does not exist in

CMR_JOBINF
orderNumber job from the CMR_JOBINF table, but the request failed because the
specified job does not exist in that table.
parameter.
6629 CS_info_req_list_sysout: error reading CMR_JOBINF (Orderno=

orderNumber)
orderNumber job from the CMR_JOBINF table, but the request failed.

6630 CS_info_req_list_sysout: Failed to read Orderno orderNumber from

CMR_AJF
orderNumber job from the CMR_AJF table, but the request failed.
6631 unknown user info request type

Explanation: Control-M/Server received an incorrect message from Control-M/
EM.
The user request rejected.
6632 functionName: Invalid XML file. Cannot find HEADER

EM.
The user request was rejected.
6633 CS_ZS_update_job: Failed to update job

Explanation: Control-M/Server attempted to update a job during a Zoom-and-
Save request, but the update failed.
Control-M/Server tries to update the database again.
6634 CS_user_req: unknown user request type

EM.

6635 CS_resource_user_req_ctl: unknown operator

Explanation: Control-M/Server received an incorrect operator when
processing a request to update a control resource.
6636 CS_resource_user_req_qr - Invalid request

Explanation: Control-M/Server received an incorrect operator when
processing a request to update a quantitative resource.
6637 CS_upload: unknown upload type

Explanation: Control-M/Server received an incorrect upload request.
6638 CS_download: unknown download type

Explanation: Control-M/Server received an incorrect download request.
6639 CS_download_sch: download confirmation error

Explanation: Control-M/Server did not receive a download confirmation
message from Control-M/EM.
The message was ignored.
6640 Table is currently being used (tableName)

Explanation: An upload message was sent by Control-M/EM while the
requested table had already been ordered by the User Daily job.
The upload message was rejected.
User response: Try to upload the message again after the User Daily job
finishes.

6641 CS_download_cal: download confirmation error

Explanation: Control-M/Server did not receive a calendar download
confirmation message from Control-M/EM.
The message was ignored.
6642 functionName: Failed to send alert to Control-M/EM

Explanation: Control-M/Server could not send an alert to Control-M/EM.
6644 cd_db_init: Failed to read table CMS_CMNPRM

Explanation: Control-M/Server was unable retrieve a record from the
CMS_CMNPRM table.
The communication gateway process terminates.
6645 cm_ipr_msg_put_msg: message to be sent to Control-M/EM is corrupt

Explanation: Control-M/Server found a corrupted message before it was sent
to Control-M/EM.
The communication gateway process displays an error message and continues

processing.
User response: Force a download from the troubleshooting menu to Control-M/

EM.
6646 CM_open_session_FULL_DUPLEX: cm_bca_accept failed

Explanation: Control-M/Server could not establish an SSL connection with
Control-M/EM.

processing.
User response: Do the following
Check that your SSL keys match.
If the problem persists, contact BMC Software Customer Support.
6647 CM_open_session_FULL_DUPLEX: Unable to close session sessionName

Explanation: Control-M/Server could not close the sessionName SSL session.


processing. Communication with Control-M/EM is terminated.
User response: If the problem persists, contact BMC Software Customer

Support.
6648 com_jcr_pack_msg: failed to pack job data

Explanation: Control-M/Server failed to pack the zoom-and-save return code
that was received from Control-M into a message to be sent to Control-M/EM.
The communication process displays an error message and continues processing.

Support.
6649 com_jcr_add_jobdata: Cannot retrieve record from memory list

Explanation: Control-M/Server failed to retrieve a record from an internal
memory list containing job data.

Support.
6650 com_dwl_get_taskt: Illegal task type taskType

Explanation: Control-M/Server received an illegal task type from Control-M/
EM.

Support.
6651 CM_open_session: cm_bca_accept failed

Explanation: Control-M/Server could not establish an SSL connection with
Control-M/EM.
The communication process displays an error message.
Check that your SSL keys match.
If the problem persists, contact BMC Software Customer Support.

6652 cm_rcv: client name gracefully closed the connection

Explanation: Control-M/EM closed the connection to Control-M/Server.
The communication gateway process displays an error message.
User response: No action is necessary.
6653 com_jcr_add_jobdata: Failed to find job information when performing zoom-

and-save
Explanation: Control-M/Server could not find job-related information to send
to Control-M/EM during zoom-and-save.

Support.
6654 com_jvp_get_do_sz: Illegal DO type (DoType)

Explanation: Control-M/Server encountered the DoType invalid DO type value
during zoom-and-save.

Support.
6655 functionName: Failed to decrypt string string code: rc

Explanation: Decryption of informatin inside internal configuration files failed.
User response: Check that the Control-M/Server data files are not corrupt, and
contact BMC Customer Support.

6701 functionName: Failed to initialize Xerces library

Explanation: Control-M/Server Configuration Agent failed to initialize the
Xerces library.

The Control-M/Server Configuration Agent shuts down.
6702 functionName: DOM exception caught; message: message code: code

Explanation: The Control-M/Server Configuration Agent caught a DOM
exception.
message - the message text
code - the error code
The error is reported back to the Control-M Configuration Server.
6703 DOM implementation not Supported

Explanation: The Control-M/Server Configuration Agent attempted to
initialize DOM implementation, but the attempt failed.
User response: Check that there is sufficient memory on the machine. If this is
not the problem, contact BMC Software Customer Support.
6705 functionName: DOM builder creation failed

initialize the DOM builder, but the attempt failed.
6706 functionName: DOM writer creation failed

initialize the DOM writer, but the attempt failed.

6709 functionName: XML length is zero

Explanation: The XML response message generated by the Control-M/Server
Configuration Agent is empty.
The Control-M/Server Configuration Agent will not send an XML response to

the Control-M Configuration Server.
6710 functionName: Communication is down

Explanation: There is no communication between the Control-M/Server
Configuration Agent and the Control-M Configuration Server.
User response: Check the Control-M/Server Configuration Agent port
definition on the Control-M/Server Configuration Manager.
This port definition should be the same as the

CTM_CONFIG_AGENT_PORT_NUMBER parameter, whose default value is
2369. This parameter is defined in the config.dat file, which is located in the
CTMServerInstallation/CTM_Server/Data directory.
Use the netstat -na command to verify that this port is not in use by any other
application.
Use the shut_ca utility in the Control-M/Server account if you do not want to
establish a connection between the Control-M/Server configuration Agent and
the Control-M Configuration Server. This will prevent error messages from
displaying in the log file.
6711 functionName: Failed to send message: rc

Explanation: The Control-M/Server Configuration Agent attempted to send a
response to the Control-M Configuration Server, but the attempt failed. A
return code of 5 is displayed, indicating that communication is down.
User response: Check the communication between the Control-M/Server
Configuration Agent and Control-M Configuration Server.
In case the communication is down, check the Control-M/Server Configuration

Agent port definition on the Control-M/Server Configuration Manager.
This port definition should be the same as the

CTM_CONFIG_AGENT_PORT_NUMBER parameter, whose default value is
2369. This parameter is defined in the config.dat file, which is located in the
CTMServerInstallation/CTM_Server/Data directory.
Use the netstat -na command to verify that this port is not in use by any other
application.

6712 functionName: Header size is too short: (size = size)

Explanation: The length of a request header (size) sent from the Control-M
Configuration Server to the Control-M/Server Configuration Agent is too
short.
The request is not handled.
6713 Error occurred while parsing XML request. Probably XML text does not
match schema. Message: messageText Node name: nodeName
Explanation: An XML request sent from the Control-M Configuration Server to
the Control-M/Server Configuration Agent is not valid.
6714 functionName: DOM document creation failed

Explanation: The Control-M/Server Configuration Agent attempted to create a
DOM document, but the attempt failed.
6720 Security Group 'group' already exists

Explanation: The Control-M/Server Configuration Agent cannot add or update
the specified security group because this group is already defined in the
database.
The request to create or update a security group is aborted.
User response: Use a different security group name.
6721 User 'user' already exists

Explanation: The Control-M/Server Configuration Agent cannot add or update
the specified security user because this user is already defined in the database.
The request to create or update a security user is aborted.
User response: Use a different security user name.
6722 Security Group 'group' does not exist

Explanation: The Control-M/Server Configuration Agent cannot delete or
update the specified security group because this group is not defined in the
database.

The request to delete or update a security group is aborted.
User response: Use a different security group name.
6723 User 'user' does not exist

Explanation: The Control-M/Server Configuration Agent cannot delete or
update the specified security user because this user is not defined in the
database.
The request to delete or update a security user is aborted.
User response: Use a different security user name.
6724 Failed to create Security group, name ='name'

Explanation: The Control-M/Server Configuration Agent cannot create the
specified security group.
The request to create a security group is aborted.
Check that the database is up and running.
Check the database error log.
Check previous messages, and contact BMC Software Customer Support.
6725 Failed to create Security group

Explanation: The Control-M/Server Configuration Agent cannot create a new
security group.
The request to create a security group is aborted.
User response: Check the parameters that were entered for this request, and
6726 Failed to create user, name ='user'

security user.
The request to create a security user is aborted.

6727 Failed to create user

security user.
The request to create a security user is aborted.
6728 Failed to delete user, name ='user'

Explanation: The Control-M/Server Configuration Agent cannot delete the
specified security user.
The request to delete a security user is aborted.
6729 Failed to delete user

security user.
6730 Failed to delete Security group, name ='name'

security group.

6731 Failed to delete Security group

security group.
6732 Failed to update user, name ='user'

Explanation: The Control-M/Server Configuration Agent cannot update the
security user.
The request to update a security user is aborted.
6733 Failed to update user

security user.
The request to update a security user is aborted.
6734 Failed to update Security group, name ='name'

security group.
The request to update a security group is aborted.
6735 Failed to update Security group

security group.

The request to update a security group is aborted.
6736 Failed to update User or Security group (name = 'name') attributes

security attributes for the specified user or group.
The request to update security attributes is aborted.
6737 User or Security group (name = 'name') does not exist

Explanation: The Control-M/Server Configuration Agent cannot update or
view the security attributes for the specified user or group.
The request to update or view security attributes is aborted.
6738 Database error error

Explanation: The Control-M/Server Configuration Agent failed to start a
database transaction.
The security request is aborted.

6739 Failed to update Table ('table') attributes for User or Security Group
(name='name')
Explanation: The Control-M/Server Configuration Agent failed to update table
attributes for the specified user or security group.
6740 Failed to update Active(Owner='owner' NodeId='nodeID') attributes for User

or Security Group (name='name')
Explanation: The Control-M/Server Configuration Agent failed to update
active attributes for the specified user or security group.
6741 Failed to update Entity('entity') attributes for User or Security Group

(name='name')
Explanation: The Control-M/Server Configuration Agent failed to update
entity attributes for the specified user or security group.
The request to update entity attributes is aborted.

6742 Failed to view user or group attributes

Explanation: The Control-M/Server Configuration Agent failed to view user or
group attributes.
The request to view security attributes is aborted.
6744 Control-M/Server works in restricted mode. Request reqName is rejected.

Explanation: The Control-M/Server Configuration Agent cannot perform the
request because it is operating in restricted mode.
The Control-M/Server Configuration Agent rejects the request.
User response: Change the configuration agent work mode. This mode is set via
the CTM_CONFIG_AGENT_MODE configuration parameter.
6750 Ping to Control-M/Agent failed

Explanation: An attempt to ping Control-M/Agent by the Control-M
Configuration Manager failed.
The ping is not performed. Normal processing continues.
User response: Check the extended message that accompanies the ping failure
message. Possible explanations are:
Control-M/Server is down
Control-M/Server is not authorized to work with the Control-M/Agent
6751 Update Control-M/Agent nodeid nodeID failed

Explanation: An attempt to update the parameters or status of a Control-M/
Agent failed. This message can appear during three different scenarios:
After a test agent operation from the Control-M Configuration Manager. The
failure may cause the agent to remain in some intermediate state.
After a set parameters operation, if one of the steps of the set parameters
has failed.
In this case, if the persistency property of the agent was changed then the
server and the agent may be not synchronized.
After an agent operation which is not test agent or set parameters,

which indicates a failure to update the Agent status file in the Control-M/
Server.

Control-M/Server failed to update the Control-M/Agent status or parameters.
User response: Do one of the following:
Scenario A
Verify the correctness of the agent status and agent parameters.
Scenario B
Check that the server and agent are synchronized in terms of the persistency
property.
Scenario C
Check for a reason an update to the file named as the nodeid under data/
AGSTAT directory failed. Check for disk space, file authorizations, etc.
6752 Access Control-M/Agent data for nodeid nodeID failed

Explanation: Control-M/Server failed to get Control-M/Agent parameters.
Support.
6753 Delete Control-M/Agent nodeid nodeID status file failed

Explanation: Control-M/Server failed to delete the nodeID node ID.
Node ID deletion can fail during
status file deletion
parameters file deletion (for Control-M/Agent)
mapping deletion (for a remote host)
This message can appear in different scenarios:
during cleanup after a test agent operation
during a request from the user to delete an agent
during a request from the user to delete remote host
during a request to add a remote host for a node ID that was previously a
regular Control-M/Agent.

The node ID is not deleted.
User response: Check for a reason a deletion could have failed:
Check for the possible failure to delete the file named as the node ID in the
data/AGSTAT directory, in the data/AGPRM directory, or in the data/
AGSTAT_RJX directory. Check disk space, file authorizations, and so on.
Check for database problems
6754 Delete Control-M/Agent nodeid nodeID parameters file failed

Explanation: An attempt to delete the Control-M/Agent parameters file failed.
Deletion of a parameters file is one of the operations involved in the procedure
to delete an agent. If the parameters file cannot be deleted, the agent deletion
operation continues with other procedures, such as status file deletion and
remote hosts discovery.
The parameters file is not deleted.
Check possible deletion failure of the file named as the node ID in the data/
AGPRM directory.
6755 functionName Activation of ctmgetcm for Agent nodeID failed

Explanation: The ctmgetcm utility retrieves the details of the control modules
that are installed on a Control-M/Agent.
This utility is executed at every specific time interval (configurable) by the

Control-M/Server Configuration Agent. The information retrieved by this
utility is displayed in the Control-M Configuration Manager.
This message is displayed when the activation of the ctmgetcm utility fails.
The Control-M Configuration Manager uses the information about the control
modules that was obtained during the last successful retrieval from the agent.
Support.
6756 Failed to read CM information for Control-M/Agent nodeID from the

database, rc
Explanation: The Control-M/Server Configuration Agent failed to read
information about control modules from the Control-M/Server database.

The Control-M/Server Configuration Agent replies with an error to the life

check request from the Control-M Configuration Manager. As a result, the
Control-M Configuration Manager fails to retrieve topology and status
information from Control-M/Server.
Check the database log.
6757 functionName: Failed to retrieve Control-M/Server version from versions file

Explanation: The Control-M/Server Configuration Agent failed to retrieve
version information from Control-M/Server installed versions file.
The Control-M/Server Configuration Agent returns an unknown Control-M/

Server version to the Control-M Configuration Manager.
6758 functionName : Failed to open Control-M/Server versions file fileName

Explanation: Control-M/Server Configuration Agent failed to open the Control-
M/Server installed versions file.

6759 functionName Corrupt versions file: invalid value value found for product
prodName
Explanation: Control-M/Server Configuration Agent encountered a corrupt
installed versions file

6760 Control-M/Server cannot generate a full xml response

Explanation: The Control-M/Server Configuration Agent received invalid data
from the Control-M Configuration Server.
The request is aborted.

6761 There is no connection to the database

request because there is no connection to the database.
The Control-M/Server Configuration Agent returns an error to the Control-M

User response: Check the connection to the database.
6762 Failure to allocate memory for object during activity

Explanation: The Control-M/Server Configuration Agent failed to allocate
memory for the requested activity.

Check that there is sufficient memory on the machine to perform the

requested activity.
Check previous messages.
6763 Could not create action for request reqName

Explanation: The Control-M/Server Configuration Agent failed to handle the
reqName request.

6764 Failed to read table CMS_CMNPRM

Explanation: The Control-M/Server Configuration Agent failed to read the
CMS_CMNPRM table from the database.
The Control-M/Server Configuration Agent fails to respond to a

synchronization request from Control-M Configuration Manager. As a result,
the Control-M Configuration Manager fails to retrieve topology and status

6765 Failed to read table CMS_SYSPRM

Explanation: The Control-M/Server Configuration Agent failed to read the
CMS_SYSPRM table from the database.
The Control-M/Server Configuration Agent fails to respond to synchronization

and life check requests from the Control-M Configuration Manager. As a result,
6766 Failed to retrieve hostName

Explanation: The ctmcreate utility failed to retrieve the hostName Control-M/
Server.
User response: Ask your system administrator to verify the name of the Control-
M/Server machine.
6767 Received Illegal Time Zone

Explanation: The Control-M/Server Configuration Agent failed to calculate the
local time zone.
The Control-M/Server Configuration Agent fails to respond to a

synchronization request from Control-M Configuration Manager. As a result,
Check the time zone on the Control-M/Server.
6768 Failed to update gateway port

Explanation: The Control-M/Server Configuration Agent failed to update the
Control-M/Enterprise Manager Gateway port as requested by the Control-M

The previous value of the Gateway port is written in Control-M/Server database.
6769 Failures while setting debug level

Explanation: The Control-M/Server Configuration Agent failed to set the
Control-M/Server debug level.
The debug level for Control-M/Server processes is set incorrectly.
User response: Check the details provided in this message regarding the nature
of the problem and the processes for which the failure occurred
6770 functionName Could not translate last update lastUpdateTime to GMT Time
Zone
Explanation: The Control-M/Server Configuration Agent failed to translate the
last time a node ID was updated to GMT.
The last update times for some of the node IDs displayed in Control-M
Configuration Manager are incorrect.
Support.
6771 Failed to prepare temporary parameters for agent ping for agent nodeID rc
Explanation: The Control-M/Server Configuration Agent failed to prepare
temporary agent parameters for performing a test agent operation.
The test agent operation fails.
Support.
6772 Another request is currently being served for Control-M/Agent nodeID.

Please try again in a few seconds.
Explanation: The Control-M/Server Configuration Agent cannot perform a
request that impacts the specified Control-M/Agent because it is busy
performing another request for that agent.
The requested agent operation fails.
User response: Wait several seconds and repeat the operation.

6773 Cannot retrieve the list of node groups

Explanation: The Control-M/Server Configuration Agent cannot retrieve the
list of node groups.
The request to get node groups is aborted.
6778 Update state of node with Discovering state is prohibited.

Explanation: The user tried to change the state of a node ID that is in
Discovering state.
Updating a node ID while it is in Discovering state is not allowed. This may

occur while enabling or disabling a node ID with the Control-M/Server
Configuration Agent or the ctm_menu utility.
The attempt to enable or disable a node ID fails.
User response: Wait until the node ID is no longer in Discovering state before
performing the desired action.
6787 Node Group nodeGroup already exist.

Explanation: A node group cannot be added when a node group already exists
User response: Change the node group name.
6788 Failure occurred while checking existence of Node Group nodeGroup.

Explanation: The failure occurred while attempting to validate the existence of
the node group.
BMC Customer Support.
6789 Failed to add node group to the database, code: rc.

Explanation: The operation of adding a node group failed.

6790 Node Group nodeGroup does not exist.

Explanation: The node group does not exist. This message might appear for
node group operations such as delete or update.
User response: Make sure that the proper node group was given.
6793 Failed to delete node group from database, code: rc

Explanation: The operation of deleting a node group failed.
6794 Failed to update node group nodeGroup in the database (deletion failure),
code: rc
Explanation: The operation of updating a node group failed in the deletion
phase.
6795 Failed to update node group nodeGroup in the database (insertion failure),
code: rc.
Explanation: The operation of updating a node group failed in the insertion
phase.

6801 Remote Host hostName is not defined

requested remote host operation because the specified host is not a known
remote host.
The Control-M/Server Configuration Agent responds with an error to the

related remote host request from the Control-M Configuration Manager, and
the operation fails.
User response: Define the node ID as a remote host before requesting a remote
host operation.

6802 Remote Host hostName is already defined

Explanation: The Control-M/Server Configuration Agent cannot add a remote
host because the remote host already exists.
The request to add a remote host fails, and the Control-M/Server

Configuration Agent sends an error message to the Control-M Configuration
Manager.
6803 Remote Host hostName can not be defined because a Control-M/Agent on

that host is already connected.
Explanation: The Control-M/Server Configuration Agent cannot add a remote
host when an agent is connected to that host.
The request to add a remote host fails, and the Control-M/Server

Configuration Agent sends an error message to the Control-M Configuration
Manager.
6807 Cannot retrieve owner or host for owner 'owner', host 'host'
Explanation: The Control-M/Server Configuration Agent cannot retrieve
information about the requested owner or host.
The request is aborted.
6808 Failed to add owner 'owner' and host 'host'

Explanation: The Control-M/Server Configuration Agent cannot add the
specified owner and host.
The request to add an owner is aborted.

6809 Owner 'owner' is already defined for host 'host'

Explanation: The specified owner and host have already been defined in the
database.
User response: Add the owner and host that have not been defined in the
database.
6810 The passphrase key key and owner owner on host host is incorrect
Explanation: The Control-M Server Configuration Agent cannot perform a
request to add or update an owner because the passpharase for this key differs
from the one defined on the database.
The request to add or update an owner is aborted.
User response: Set the correct passphrase and key to add or update owner
requests.
6811 Owner 'owner' is not defined for host 'host'

request to delete or update an owner because the specific owner and host are
not defined in the database.
The request to delete or update an owner is aborted.
User response: The request to delete or update an owner should include

parameters that have already been defined in the database.
6812 Failed to update owner 'owner' and host 'host'

request to update the specified owner.
The request to update an owner is aborted.

6813 Failed to delete owner 'owner' and host 'host'

request to delete the specified owner.
The request to delete an owner is aborted.
6814 Failed to add owner 'owner' and host 'host' because the key 'key' does not
exist in database
request to add a specific owner because the key does not exist in the database.
User response: The request to add an owner should include a key that has
already been defined in the database.
6815 Cannot retrieve the list of key names

Explanation: The Control-M/ Server Configuration Agent cannot retrieve the
list of key names.
The request to get a list of key names is aborted.
6820 Control-M/Server is not authorized

Explanation: The Control-M/Server is not authorized by the Control-M/Agent.
The Control-M/Server cannot communicate with the Control-M/Agent.
User response: Configure the Control/M Agent properly.
6821 Host is inaccessible

Explanation: The Control-M Agent cannot reach a remote host.

The Control-M/Server cannot reach the remote host by using this Control-M/
Agent.
User response: Check the remote host computer.
6822 No remote service on remote host

Explanation: The Control-M/Agent cannot reach the remote host because the
needed service does not run on the Control-M/Agent computer.
The Control-M/Agent cannot reach the remote host and marks it as unavailable.
User response: Check the remote host computer.
6823 Invalid user or bad password

Explanation: The Control-M/Server failed to authenticate the supplied
username and password/key.
User response: Perform the action that follows each scenario:
Failed to connect to WMI remote host:
Check that the correct username and password have been supplied.
Check that the WMI services are running.
Verify that the user has administrator privileges on the remote host.
Failed to connect to SSH remote host:
Check whether one of the following SSH key types are being used:
OpenSSH or SSH2.
If OpenSSH is being used:
1 Create a key with the openSSH option.
2 Store the public key in the $HOME/.ssh/authorized_keys file. In older

OpenSSH, the public keys should be stored inside the $HOME/.ssh/
authorized_keys2 file.
If SSH2 is being used:
1 Create a key with the SSH2 option.
2 Copy it to the remote hosts $HOME/.ssh2 directory as a separate file. For

example, key1 pub.

3 Add the line Key key1.pub to the $HOME/.ssh2/authorization file.
6824 The passphrase for private key and owner on the remote host is incorrect.
Explanation: The remote host cannot be accessed because user credentials
cannot be reached due to passphrase.
User response: Use the correct passphrase.
6825 To run jobs using WMI protocol, the agent must be installed on either
Windows XP, Windows 2003 or higher.
Explanation: The WMI configured remote host cannot be accessed when the
agent Windows OS level is too low.
User response: Use an agent on a proper Windows OS in order to work with the
remote host.
6826 The Control-M/Agent services should run under the This Account logon
option. Currently, it is the Local System Account
Explanation: The remote host cannot be accessed because Control-M/Agent
services do not run under This Account.
User response: Configure the Control-M/Agent properly.
6827 Server-Agent Protocol version 07 or higher is required to connect to

remote hosts.
Explanation: The remote host cannot be accessed by a Control-M/Agent whose
protocol version is configured too low.
User response: Use the Control-M/Agent 6.4 and above and configure the
Control-M/Agent properly.
6828 Failed to update Server to Agent port. Port is busy.

Explanation: The Control-M/Agent cannot switch ports, because a new port is
being used by another process.
A message appears stating that the Control-M/Server is working with a old port.
User response: Use another port.

6829 Credential validations is inapplicable for Control-M/Agent for UNIX /Linux.

Explanation: The remote host cannot be accessed due to bad credentials.
The Control-M/Server cannot reach the remote host and marks it as unavailable.
User response: Use correct credentials.
6830 The Logon as a batch job privilege has not been granted to the user.
Explanation: The Control_M/Agent user has not been granted Logon as a
batch job privleges.
User response: Set privleges correctly on the Control-M/Agent computer.
6831 The SeTcbPrivelege (act as part of OS) privelge has not been granted.
Explanation: The Control-M/Agent cannot be used because the SeTcbPrivilege
(act as part of OS) privilege has not been set on the Control-M/Agent
computer.
User response: Set privileges correctly on the Control-M/Agent.
6832 Undefined user or wrong password

Explanation: The Control-M/Agent cannot be used due to an incorrect user or
password.
User response: Use correct credentials.
6833 Access to CMD.exe is denied.

Explanation: The Control-M/Agent responded to the ping request with
Access to CMD.exe is denied.
6834 The credential validations are inapplicable for Control-M/Agent for

Windows without the Logon User mode.
Explanation: The Control-M/Agent must run in Logon as User mode in
order to be able to use the users credentials.

User response: Ensure that the Control-M/Agent runs with the Logon as
User set.
6835 The user cannot be tested because Nodeid nodeID does not exist.
Explanation: The test user operation failed because nodeid does not exist.
User response: Ensure the nodeid used exists.
6836 The user cannot be tested because failed to determine Nodeid nodeID
status, rc= rc.
Explanation: The test user operation failed because the Control-M/Server
failed to determine the nodeid status..
User response: Check other messages in the log file and contact BMC Software
Customer Support.
6837 Failed to serialize owner owner credentials.

failed to serialize owner credentials.
Customer Support.
6838 An internal error occured while testing the user.

Explanation: The test user operation failed because of an internal error in the
Control-M/Server.
Customer Support.
6839 A timeout occurred while waiting for a response from the agent.
Explanation: A timeout occurred while waiting for a response to a ping request
from the Control-M/Agent.
User response: Check that the Control-M/Agent is still running.
6841 The key does not exist.

Explanation: The test user operation failed because key owner credentials do
not exist.
User response: Use valid credentials.
6842 Failure to find key details.

failed to locate the key of owner credentials.
Customer Support.

6843 The Control-M/Agent must have protocol version 08 or higher for test user
functionality.
Explanation: The Control-M/Agent must have protocol version 08 or higher in
order to operate the test user functionality.
User response: Use agent with protocal version 08 and higher.
6850 The Configuration Agent plugin configuration file is corrupt:

extendedMessage.
Explanation: The Control-M Configuration Manager plugin information could
not be found in the configuration file.
User response: Check the permissions of the plugin configuration file and
6851 Failed to create temporary file names code: rc.

Explanation: The Control-M Configuration Manager operation failed because
the Control-M/Server failed to create temporary files.
User response: Check disk space on the Control-M/Server and contact BMC
6852 Failed to update temporary file with standard input content code: rc.
Explanation: The Control-M Configuration Manager plugin operation failed
because the Control-M/Server failed to write into temporary files.
User response: Check disk space on the Control-M/Server computer and
6853 Failed to activate plugin code: rc.

Explanation: The Control-M Configuration Manager plugin operation failed.
User response: Read details in the extended message and contact BMC Software
Customer Support.
6854 The ouput size exceeeds the limit (outputStringSize bytes).

Explanation: The Control-M Configuration ManagerControl-M Configuration
Manager plugin standard output size exceeds the limit.
Customer Support.
6855 Operation timed out (timeout seconds).

Explanation: The Control-M Configuration Manager plugin activation timed
out.
Customer Support.

6893 Failed to test Remote Host hostName

Explanation: The Control-M/Server Configuration Agent failed to perform the
test remote host procedure.
The Control-M/Server Configuration Agent sends an error message to the

Control-M Configuration Manager.
message. Possible explanations are:
Control-M/Server is down
Control-M/Server is not authorized to work with the Control-M/Agent
6894 Failed to ping Remote Host hostName

ping remote host procedure.

message.
6896 Failed to delete Remote Host hostName, rc

delete remote host procedure.

Control-M Configuration Manager. The remote host is not deleted.
Support.
6897 Failed to update Remote Host hostName, rc

update remote host details procedure.

Control-M Configuration Manager. The remote host is not deleted.
message. Possible causes for the failure are:
One of the agents mapped to the remote host is invalid (either the agent
does not exist, or it has protocol version 06 or lower).

Cannot update details for the Default remote host.
6898 Failed to get Remote Host hostName details, rc

get remote host details procedure.

Support.
6899 Failed to add Remote Host hostName, rc

Explanation: The Control-M/Server Configuration Agent failed to add a
remote host.
The remote host is not added.
Check the extended message that accompanies the add failure message, and
check previous messages.
Also check that the agents that are mapped to the new remote host are valid,
meaning that they exist in Control-M/Server and have protocol version 07
or higher.

6900 Cannot update CMR_UDLAST for Daily userDaily

Explanation: The Control-M/Server received a request from Control-M/EM to
upload a scheduling table assigned to the userDaily User Daily job. The Control-
M/Server failed to update the CMR_UDLAST table for this User Daily job.
The uploading of the scheduling table continues.
User response: Determine the cause of the database problem by checking the
database error log. If the problem persists, contact BMC Software Customer
Support. If the scheduling table was ordered during the upload, you may need
to double-check that all the intended jobs were ordered (remember that the
table might have been changed during the ordering, as a result of the upload).

6901 functionName: Error while creating dwl

Explanation: The Control-M/Server was unable to prepare an update message
for a job to be sent to Control-M/EM.
System processing continues. The update is not sent to Control-M/EM.
6902 functionName: Error while creating dwq

for a quantitative resource to be sent to Control-M/EM.
System processing continues. The update is not sent to Control-M/EM.
6903 functionName: Error while creating dwc

for a prerequisite condition to be sent to Control-M/EM.
The update is not sent to Control-M/EM.
6904 functionName: Error while creating dwe

for a control resource to be sent to Control-M/EM.
6905 functionName: Error while creating alr

Explanation: The Control-M/Server was unable to prepare an alert to be sent to
Control-M/EM. Such an alert is commonly used to notify Control-M/EM that
the agent status changed to unavailable or disabled.
6906 functionName: Failed to count how many jobs are in scheduling table
TableName. Skip table
Explanation: The ctmsweep utility failed to determine how many jobs are in
the tableName scheduling table.

The tableName scheduling table is not processed by the ctmsweep utility. The
ctmsweep utility continues to process the next scheduling table in its list.
User response: Check for error messages in the utility log and in the database
error log to determine the cause of the failure. Rerun the ctmsweep utility after
correcting the problem.
6907 functionName: Job not found in list

Explanation: The ctmsweep utility failed to find the job in its list of obsolete
jobs. Either message 6910 or message 6919 will also be displayed after this
message.
If message 6910 is displayed, the scheduling table is not processed by the

utility. The ctmsweep utility continues to process the next scheduling table in
its list. If message 6919 is displayed, the utility does not write the job in the
sweep_obsolete.txt report file. The ctmsweep utility continues to write the
report file, and aborts afterwards, without deleting any of the obsolete jobs and
tables.
User response: Check for error messages in the utility log and contact Customer
Support.
6908 functionName: The number of obsolete jobs is greater than the maximum
allowed (maxNumber)
Explanation: The ctmsweep utility found at least maxNumber of obsolete jobs in
Control-M/Server database. The maxNumber is determined by the
CTM_MAX_OBSOLETE_JOBS parameter in the Control-M/Server config.dat
file.
The ctmsweep utility does not process any more jobs. The utility continues to
the next step, writes the sweep_obsolete.txt report file, and then (if -Test was
not specified) deletes the obsolete tables and jobs.
User response: You can rerun the ctmsweep utility to process additional jobs.
6909 functionName: Failed to close file FileName

Explanation: The ctmsweep utility failed to close the FileName file.
User response: Check for error messages in the utility log.
6910 functionName: Failed to delete the obsolete jobs from scheduling table
TableName
Explanation: The ctmsweep utility failed to delete one or more obsolete jobs
from the tableName scheduling table.

No obsolete job is deleted from the tableName scheduling table. The ctmsweep
utility continues to delete the obsolete jobs in the next scheduling table in its list.
error log to determine the cause of the failure. After correcting the problem,
rerun the ctmsweep utility to delete the obsolete jobs from the TableName
scheduling table.
6911 functionName: Failed to delete obsolete scheduling table TableName

[(SpecificFailure)]
Explanation: The ctmsweep utility failed to delete the obsolete tableName
scheduling table. The specific failure is written in parentheses, as
[SpecificFailure], and it can be one of the following values:
from the CMS_JOBDEF table
from the CMS_IOACHK table
from the CMS_SCHEDT table
failed to commit transaction
No obsolete job is deleted from the tableName scheduling table. The ctmsweep
utility continues to delete the obsolete jobs in the next scheduling table in its list.
rerun the ctmsweep utility to delete the obsolete tableName scheduling table.
6912 functionName: Obsolete scheduling table TableName deleted successfully

Explanation: The ctmsweep utility succeeded in deleting the obsolete
TableName scheduling table.
The ctmsweep utility continues to delete the obsolete jobs in the next
scheduling table in its list.
6913 functionName: Failed to delete obsolete jobNo JobNumber

(jobname=JobName)
Explanation: The ctmsweep utility failed to delete an obsolete job (the job
number is JobNumber and the job name is JobName) from the Control-M/Server
database. Message 6910 is displayed after this message.

The ctmsweep utility does not delete the obsolete JobName that has the job
number JobNumber from the Control-M/Server database. The utility continues
to delete the obsolete jobs in the next scheduling table in its list.
rerun the ctmsweep utility to delete the obsolete jobs from the Control-M/
Server database.
6914 functionName: Failed to update the checksum of scheduling table TableName

Explanation: The ctmsweep utility failed to update the checksum of the
tableName scheduling table.
The ctmsweep utility does not delete any obsolete job from the tableName
scheduling table. The utility continues to delete the obsolete jobs in the next
rerun the ctmsweep utility, to delete the obsolete jobs from the TableName
scheduling table.
6915 functionName: NumOfJobs obsolete jobs from scheduling table TableName

deleted successfully
Explanation: The ctmsweep utility deleted NumOfJobs obsolete jobs from the
tableName scheduling table.
The ctmsweep utility continues to delete the obsolete jobs in the next
6916 functionName: Failed to check for obsolete criteria in all the tags of all the
groups
Explanation: The ctmsweep utility failed to check for obsolete criteria in all the
tags of all the groups in the database.
The ctmsweep utility aborts.
error log to determine the cause of the failure.
6917 functionName: Failed to check for obsolete criteria in all the tags of all the
jobs
tags of all the jobs in the database.

6918 functionName: Failed to check for obsolete criteria in all the jobs
jobs in the database.
6919 functionName: Failed to write report file FileName

Explanation: The ctmsweep utility failed to write the report file. Possible
reasons for the failure are as follows:
failed to open the report file for writing (lack of file description, user does
not have write permissions to the file)
failed to delete the previous report file
User response: Check for error messages in the utility log.
6920 functionName: Failed to delete all obsolete tables and jobs

Explanation: The ctmsweep utility failed to delete all the obsolete tables and
jobs from the database. The failure might be due to a database related failure or
because the utility reached the maximum allowed obsolete criteria. In the latter
case, message 6908 will be displayed as well.
The ctmsweep utility ends unsuccessfully (the return code of the utility is either
'partial success' or 'failure').
6921 functionName: Retrieving obsolete definitions from Control-M/Server

database using date criteria: ObsoleteDate
Explanation: The ctmsweep utility is retrieving obsolete jobs and scheduling
tables from the Control-M/Server database by using date criteria: ObsoleteDate

6922 functionName: Found NumOfTables tables that contain obsolete jobs

Explanation: The ctmsweep utility found NumOfTables tables that contain
obsolete jobs.
6923 functionName: Generate report file FileName

Explanation: The ctmsweep utility opened the FileName report file for writing.
6924 functionName: delete table TableName *

Explanation: The ctmsweep utility lists the TableName scheduling table as a
candidate for deletion.
6925 functionName: delete job TableName JobNumber MemName JobName

Explanation: The ctmsweep utility lists the JobNumber job number as a
candidate for deletion.
6926 functionName: Start to delete obsolete definitions from Control-M/Server

database ...
Explanation: The ctmsweep utility finished writing the sweep_obsolete.txt
report file and now begins deleting the obsolete scheduling tables and jobs
from the Control-M/Server database.
The ctmsweep utility continues to delete the obsolete scheduling tables and
jobs from the Control-M/Server database.
6927 functionName: User <UserName> is not permitted to [update|delete] table

TableName. Skip table
Explanation: The UserName user, who is running the ctmsweep utility, is not
permitted to update or delete the TableName scheduling table.
The scheduling table is not processed by the ctmsweep utility. The ctmsweep
utility continues normally to the next scheduling table in its list.
6940 < functionName>: Error in < subTable or subTableJob> < subTableName or

jobName> schedule parameters
Explanation: Failed to calculate Sub-table or Sub-table job scheduling plan.

The Sub-table or Sub-table job is not ordered. Control-M/Server processing

continues.
User response: Review Sub-table or Sub-table job scheduling parameters. Refer

to Control-M/Server logs.
6941 < functionName>: Failed to add order number < OrderNumber> of Sub-table
< SubTableName> to Sub-tables list
Explanation: Failed to add Sub-table order number to the Sub-tables order
number list
User response: Review Machine memory. Refer to Control-M/Server logs.
6942 < functionName>:Failed to retrieve ADJUST_COND for < TableName or

subTableName>
Explanation: Failed to retrieve ADJUST_COND for given table or Sub-table.
User response: Refer to Control-M/Server logs.
6943 < functionName>: Failed to count how many Sub-tables are in SMART
Table < TableName>
Explanation: Failed to calculate number of Sub-tables in the given <
TableName>.

Support.
6944 < functionName>: Failed to retrieve ancestor order numbers of Sub-tables

and SMART Table for order number < orderNumber>
Explanation: Failed to fetch ancestor order numbers (Sub-table or SMART
Table) for the given order number.
During handling, autoedits fail.

Support.
6945 < functionName>: Failed to add order number < orderNumber> to order
numbers list
Explanation: Failed to add given order number to a list of order numbers.

Messages AP-1 through AP-99
During handling, autoedits fail.
User response: Check memory on the computer, and refer to Control-M/Server

logs and contact BMC Software Support.
6946 < ActionDescription> is not supported for Sub-tables

Explanation: The described action is not supported for Sub-tables.
The action is aborted.
User response: For more details about this action, see the Control-M User Guide.

This group includes messages for the Control-M product.
AP-1 Initialize Module: 1 - This utility must be executed by Windows Administrator

Explanation: A permission failure occurred while running a Control-M
database utility.
User response: Verify that the user running the Control-M database utility has
administrator privileges on the Windows machine.
AP-2 Initialize DB Module: 1 - Failed to initialize database. return code = rc

Explanation: A database connectivity failure with the given return code rc
occurred while running a Control-M database utility.
User response: Check for relevant messages in the log file and database logs.
Contact BMC Customer Support.
AP-4 Connect DB Module: 1 - Failed to connect to the Database

Explanation: A database connectivity failure occurred while running a Control-
M database utility.
AP-4 Connect DB Module: 23 - Failed to set database login parameter parameter

= parameterName. return code = rc
Explanation: A database connectivity failure with the given return code rc
occurred while running a Control-M database utility becasue the
parameterName login parameter was not set.

AP-5 Save Parameters Module: 5 - Failed to write to file fileName

Explanation: A failure occurred when saving the internal file fileName while
running a Control-M database utility.
AP-5 Save Parameters Module: 9 - Failed to append parameter parameterName in

the DBUtils file. Action in the database passed successfully.
Explanation: A failure occurred when saving the internal parameter
parameterName, while running a Control-M database utility. This occurred even
though the Control-M database utility completed successfully.
AP-6 Execute Stored Procedure Module: 6 - SP storedProcedure - Failed to fetch

column columnName from tableName. return code= rc
Explanation: The execution of the stored procedure storedProcedure failed with
the given return code rc, while running a Control-M database utility.
AP-6 Execute Stored Procedure Module: 7 - SP storedProcedure - Failed to fetch

from dbu_monitor_table. return code= rc
the given return code rc, while running a Control-M database utility.
AP-6 Execute Stored Procedure Module: 8 - SP storedProcedure - Failed to

perform select from dbu_monitor_table. return code= rc
the given return code rc, while running Control-M database utility.
AP-7 Permission Module: 2 - This utility is not supported

Explanation: The user does not have the permission to run the Control-M
database utility on the specific configuration of the Control-M product.
AP-9 Get Environment Variable Module: 25 - Failed to retrieve process path.

return code=rc
Explanation: There is an internal error in the Control-M database utility which
failed to resolve the process path with the given return code rc.
User response: Contact BMC Customer Support.

AP-10 Execute Script Module: 4 - Failed to open output tmp file

Explanation: A Control-M database utility failed to open a temporary file.
AP-10 Execute Script Module: 9 - Failed to invoke command= command. return

code= rc
Explanation: A Control-M database utility failed to run the command with the
given return code rc.
AP-11 Validation of Input Parameters Module: 9 - Failed to check directory

directoryName. return code= rc
Explanation: A Control-M database utility failed with the given return code rc
during the input directory directoryName check.
AP-11 Validation of Input Parameters Module: 12 - Directory directoryName is not

empty
Explanation: A Control-M database utility failed to run with the given
directory directoryName.
User response: Rerun the Control-M database utility with an empty input
directory.
AP-11 Validation of Input Parameters Module: 19 - Parameter parameterName is

not valid. Full file path is required
Explanation: Validation of Input Parameters Module: 19 - Parameter
parameterName is not valid. Full file path is required
AP-12 Input Params Module: 10 - Failed to allocate memory

Explanation: A Control-M database utility failed to allocate memory.
User response: Check the available memory on the machine.
AP-12 Input Params Module: 11 - Parameter parameterName is mandatory

Explanation: A Control-M database utility failed because the parameterName
has not been set.
User response: Input the parameterNameRerun and then rerun the Control-M
database utility.

AP-12 Input Params Module: 13 - Incorrect value for parameter parameterName.

Valid values: values
Explanation: A Control-M database utility contains an invalid value for the
parameterName.
User response: Set a valid value for the parameterName and then rerun the Control-
M database utility.
AP-12 Input Params Module: 16 - Directory directoryName does not exist

Explanation: A Control-M database utility failed to run with the given
directoryName.
User response: Create a new input directory and then rerun the Control-M
database utility.
AP-12 Input Params Module: 20 - Missing value for parameter parameterName

Explanation: A Control-M database utility did not receive a parameterName.
User response: Define a value for parameterName and then rerun the Control-
M database utility.
AP-12 Input Params Module: 21 - The value of parameter parameterName exceeds

permitted length
Explanation: A Control-M database utility failed to run with the set
parameterName.
AP-12 Input Params Module: 22 - Incorrect attribute attribute

Explanation: A Control-M database utility received an incorrect attribute.
User response: Run the Control-M database utility with '-HELP' to view the
valid attributes.
AP-13 Read DB Utils Parameters Module: 4 - Failed to open file fileName. return
code= rc
Explanation: A Control-M database utility failed to open fileName with the
given return code rc.
AP-13 Read DB Utils Parameters Module: 9 - Failed to retrieve process path.

return code= rc
Explanation: An internal error occurred in the Control-M database utility while
failing to resolve the process path with the given return code rc.

AP-13 Read DB Utils Parameters Module: 22 - Missing value for parameter

parameterName
attempting to read the internal parameterName.
AP-13 Read DB Utils Parameters Module: 26 - Failed to read file fileName. return
code= rc
attempting to read the internal fileName. It failed with the given return code rc.
AP-15 Set Variable Module: 9 - Failed to set environment variable var. return
code= rc
attempting to set an internal environment variable var and failed with the given
return code rc.
AP-21 Operating System Resolve Module: 9 - Failed to convert path fullPath to

short path
Explanation: An internal error occurred in the Control-M database utility
running on the Windows platform, while attempting to convert a full path to a
short path. It failed with the given return code rc.
AP-23 Inquire Parameters Module: 12 - description

Explanation: Invalid input parameters were set for a Control-M database
utility.
User response: Correct the input parameters as indicated in the message and
rerun the Control-M database utility.
AP-24 Update Parameters Module: 4 - Failed to create file fileName

Explanation: A Control-M database utility failed to create the file fileName.
AP-24 Update Parameters Module: 5 - Failed to write to file fileName

Explanation: A Control-M database utility failed to update the internal file
fileName.

AP-26 Check Application Use Mirror Module: 27 - description

checking the Control-M database mode.


3
Control-M/Agent messages
The following messages are issued by Control-M/Agent. These messages might be
displayed in the Control-M/EM GUI, Control-M/Agent log, or in the files contained
in the Control-M/Server proclog directory.

This group includes messages for Control-M/Agent.
5167 password not found. Please define password for the user userName
Explanation: A password definition is missing for user userName.
User response: Use the CTMPWD utility to define a password for user
userName.
5167 Cannot convert the SYSOUT file: fileName

Explanation: The conversion of the SYSOUT to the desired encoding has failed.
User response: Use the following sequence of commands to change the
platform mode to CJK: ctmagcfg => advanced parameters => Foreign
Language Support.
5167 the GC_convertString failed to convert SYSOUT name

Explanation: An attempt was made to perform an operation requiring a
platform that Supports CJK languages, but the platform Supports only
LATIN-1 characters, and therefore the operation fails.
Language Support.

5167 the GC_getEncodingInfo failed to obtain encoding info

Explanation: An attempt was made to perform an operation requiring a
platform that Supports CJK languages, but the platform Supports only
LATIN-1 characters, and therefore the operation fails.
Language Support.
5167 Printer is not defined

Explanation: The printerName printer definition could not be found while
performing a RELEASE action on the SYSOUT.
User response: Define a printer, or check the printers name.
5167 Can not set the printer: printerName

Explanation: The printerName printer could not be used.
User response: Check the printerName printer settings for the correct name.
5167 Fail to submit ctmrjob. fileName does not exist, ProcIdPath

Explanation: An attempt was made to submit a job using the ctmrjob utility,
but the fileName file could not be found.
User response: Check job definitions.
5167 FAIL to find file fileName after number times

Explanation: An attempt was made to submit a job, but neither the fileName nor
fileName.tmp file could be found after several attempts.
User response: Check job definitions and available disk space, and job owner
permissions.
5167 Job already ended orderNum

Explanation: An attempt was made to kill a job with an order ID orderNum,
which already has ended.
User response: Check job definitions. The order number might be wrong.
5167 Unable to convert file name JCLFileName to user encoding

Explanation: One of the following occurred:
An attempt was made to perform an operation requiring a platform that

Supports CJK languages, but the platform Supports only LATIN-1
characters, and therefore the operation fails.
The UNIX user locale or encoding is incorrect.

Use the following sequence of commands to change the platform mode to

CJK: ctmagcfg => advanced parameters => Foreign Language Support.
Check the encoding and UNIX locale.
5167 Failed to attach BE Library CMName, error: message

Explanation: An attempt was made to perform an operation that required
attachments from the CMName control module library.
User response: Check that the CM library is installed properly.
5167 AG_ATTACH_connect failed

Explanation: An operation on the agent failed due to a connection problem.
User response: Check that the CM is installed correctly.
5167 Failed to Load Back End Name DLLName

Explanation: The CM is not installed correctly.
User response: Check that the CM is installed correctly.
5167 Host hostName is not authorized. Please add hostName to authorized

servers list
Explanation: An attempt was made to use the unauthorized hostName host.
User response: Use the following sequence of commands to add the hostName
host to the list of authorized servers: ctmagcfg => Authorized Control-M/
Server Hosts.
5167 Waiting for submission for number seconds - declared disappeared. The
job wasn't submitted within number seconds, please check the disk space.
Explanation: A job has been in submitted status too long (more than number
seconds). Control-M/Agent assumes that there is a problem with the job
submission, and the jobs status is changed to DISAPPEARED.
User response: Check the available disk space, and free up space if necessary.
5167 AG_NEWDAY_handle_request: ERROR: newday request failed. CTM Server

host hostName is not authorized to perform this action
Explanation: The Control-M hostName host is not authorized to work with the
specified Control-M/Agent.
Use the following sequence of commands to add the hostName host to the
list of authorized servers: ctmagcfg => Authorized Control-M/Server
Hosts.
Use a different server to perform the New Day procedure.

5167 AG_NEWDAY_handle_request: another newday is already running. Exiting...

Explanation: The New Day procedure cannot run when another New Day
procedure is already running. Control-M/Agent will deny a second New Day
request if one is already running. The request is rejected, but Control-M/Agent
continues functioning.
5167 FAIL: Waited for Agent submission more than number seconds
Explanation: A failure occurred while trying to save agent PROCID,
STARTTIME, and EXECUTING status to a cached dsect. Normal Control-M
operation continues. Ten attempts are made to submit the agent. If the
submission is not successful after 10 attempts, Control-M exits.
User response: Check the available disk space, and free up space if necessary.
5167 Failed to retrieve child process id from - fileName. Please check if the
process has already ended.
Explanation: An attempt was made to kill a job that has already ended.
Control-M/Agent continues functioning.
5167 SYSOUT e-mail to Destination address failed

Explanation: An attempt was made to send SYSOUT mail, but the attempt
failed.
User response: Check that the e-mail destination is correct.
5167 BE_job_add_ended_job: too many ended jobs in the list

Explanation: An attempt was made to add an ended job to the ended jobs list,
but the attempt failed.
User response: There is a connectivity problem with Control-M/Server. Solve
that problem and restart the Control-M/Agent.
5167 Error: File specified by overlib\memlib memname does not exist

Explanation: The specified overlib, memlib, or memname is not correct. The job
ended NOTOK.
User response: Check that overlib and memlib are defined correctly.
5167 Owner: name isn't defined for the remote host: hostName.
Explanation: The owner name does not have permissions for the hostName host.
Control-M/Agent rejects the requested action.
User response: Use the Control-M/Server Configuration Manager to configure
the Owners Authentication Settings, or use the ctmsetown utility to define the
user for the host.

5167 ERROR: Server sent disconnect message type 2

(SSH_DISCONNECT_PROTOCOL_ERROR): Too many authentication
failures for userName.
Explanation: The password that the job owner entered was incorrect.
User response: Enter the correct password.
5167 To run jobs using the WMI protocol the agent must be installed on
Windows XP or Windows 2003.
Explanation: A user attempted to submit WMI jobs when Control-M/Agent is
installed on a version of Microsoft Windows other than Windows XP or
Windows 2003.
The WMI jobs are not submitted.
User response: Install Control-M/Agent on Windows XP or Windows 2003.
5167 The Control-M/Agent services should run under 'This Account' Log On
option. Currently it is 'Local System Account'.
Explanation: A user attempted to submit WMI jobs while the Control-M/Agent
service is running under the Local System Account logon option.
The WMI jobs are not submitted.
User response: Run the Control-M/Agent service under the This Account
logon option.
5167 Authentication failed. Invalid user/password/key.

Explanation: A user submitted a job, but there was a problem logging on to the
SSH server.
The job was not submitted.
User response: Verify that the user, password, and public and private key pair
are correct.
5167 Cannot connect to host hostName. Access is denied. Verify that:

- user userName has administrator privileges on host hostName
- the authentication credentials set for this user in Control-M are correct
- that WMI services are running.
Explanation: An attempt was made to connect to the hostName host, but the
attempt failed.
The job fails.
Verify that user userName has administrator privileges on host hostName.

Verify that the authentication credentials set for this user in Control-M are
correct.
Verify that WMI services are running.
5167 The length of the command: cmd exceeds the size of the buffer: bufferSize.
Explanation: The length of the cmd command that the user entered exceeds the
defined size (bufferSize) of the buffer.
The command fails.
User response: Shorten the command until it is less than the size of the buffer,
and resend the command.
5167 The length of environment variables: varLength exceeds the size of the
buffer: bufferSize.
Explanation: The total amount of space that is allocated to environment and
AutoEdit variables is too small, and the size of the variable (varLength) exceeds
the size of the buffer (bufferSize).
User response: Decrease the number of variables for the site, or use the Control-
M AJC utility to turn off the AltEdit Inline variable.
5167 Server unexpectedly closed network connection

Explanation: A user attempted to submit a job, but the SSH server
unexpectedly closed the network connection.
The job ends NOTOK.
User response: Check the SSH server, and rerun the job.
5167 Connection reset by peer

Explanation: A user attempted to submit a job, but the connection was close by
the SSH server.
The job ends NOTOK.
User response: Check the SSH server, and rerun the job.
5167 Server refused our key

Explanation: A user submitted a job, but the SSH server did not accept the
specified key.
The job ends NOTOK.
User response: Verify that the public and private keys are defined correctly.

For Windows, follow the SSH Server Guide.
Verify UNIX file permissions:
600 for the authorization and authorized_keys.
700 for .ssh and .ssh2 directories.
755 for $HOME.
Failed to connect to agent with the logon as user option.
5167 Field File Name in Job Editing Form must include an extension for
running an Embedded Script job on Windows, for example .CMD.
Explanation: A user submitted a job with an embedded script on Windows
without the extension noted in the FileName field.
The job ends NOTOK.
User response: Specify an extension in the FileName field.
5167 Field FileName in Job Editing Form must include a .COM extension for
running an Embedded Script job on OpenVMS.
Explanation: A user submitted a job with an embedded script on a remote host
OpenVMS without an extension noted in the FileName field.
The job ends NOTOK.
User response: Specify an extension in the FileName field.

6823 Invalid user or bad password

Explanation: The Control-M/Server failed to authenticate the supplied
username and password/key.
User response:
Failed to connect to WMI remote host:

Messages AGT7901 through AGT7999
Check that the WMI services are running.
Verify that the user has administrator privileges on the remote host.
Failed to connect to SSH remote host:
Check whether one of the following SSH key types are being used:
OpenSSH or SSH2.
If OpenSSH is being used:
1 Create a key with the openssh option.
2 Store the public key in the $HOME/.ssh/authorized_keys file. In older

OpenSSH, the public keys should be stored inside the $HOME/.ssh/
authorized_keys2 file.
If SSH2 is being used:
1 Create a key with the SSH2 option.
2 Copy it to the remote hosts $HOME/.ssh2 directory as a separate file. For

example, key1 pub.
3 Add the line Key key1.pub to the $HOME/.ssh2/authorization file.

AGT7901 Failed to recycle the Control-M/Agent

Explanation: Failed to recycle the Control-M/Agent.
User response:
AGT7902 Failed to set Control-M/Agent debug level

Explanation: Failed to set Control-M/Agent debug level.
User response:
AGT7903 Action %s failed

Explanation: Action %s failed.
User response:

AGT7904 Failed to set Control-M/Agent configuration parameter

Explanation: Failed to set Control-M/Agent configuration parameter.
User response:
AGT7905 Failed to obtain Control-M/Agent configuration data

Explanation: Failed to obtain Control-M/Agent configuration data.
User response:
AGT7906 Failed to set Control-M/Agent configuration parameter.

Explanation: Failed to set Control-M/Agent configuration parameter.
User response: Verify that port %s is free.


49532
*119534*

Codigo de Errores en Control-M

Uploaded by

Copyright:

Available Formats

Codigo de Errores en Control-M

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Codigo de Errores en Control-M

Uploaded by

Copyright:

Available Formats

Control-M Messages Manual

United States and Canada

Outside United States and Canada

Copyright 2010- BMC Software, Inc.

Linux is the registered trademark of Linus Torvalds.

Oracle is a registered trademark of Oracle Corporation.

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

product error messages

4 Control-M Messages Manual

Chapter 1 Control-M/EM messages 11

Chapter 2 Control-M/Server messages 59

Chapter 3 Control-M/Agent messages 229

6 Control-M Messages Manual

All syntax, operating system terms, and literal examples are

About this Book 7

A sample statement follows:

COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName

Items in italic type represent variables that you alias

8 Control-M Messages Manual

About this Book 9

10 Control-M Messages Manual

Messages 24001 through 24099

User response: It is likely that this is a database or database connectivity issue.

Chapter 1 Control-M/EM messages 11

The variables in this message are:

alertNumber - the alert number

dataCenter - the data center that issued the alert

severity - the severity of the alert

orderID - the order ID of the specified alert

The new alert is not displayed by the Global Alerts Client.

User response: Run the Control-M/Enterprise Manager Health Check utility by

24003 Failed to update alert (alert number = alertNumber, data center =

The variables in this message are:

alertNumber - the alert number

dataCenter - the data center that issued the alert

severity - the severity of the alert

orderID - the order ID of the specified alert

No update for this alert is displayed by the Global Alerts Client.

User response: Run the Control-M/Enterprise Manager Health Check utility by

12 Control-M Messages Manual

User response: Run the Control-M/Enterprise Manager Health Check utility by

User response: Run the Control-M/Enterprise Manager Health Check utility by

The GAS shuts down.

User response: Check the ALARM database table availability by performing a

Messages 25001 through 25099

Chapter 1 Control-M/EM messages 13

The variables in this message are:

dataCenter - the data center name

reason - an explanation of the failure:

Failed to connect to the target data center

Stopped trying to send because the maximum number of retries was

date - the order date.

If problems persist, run the Control-M/Enterprise Manager Health Check

Messages 26001 through 26099

26001 DO Remedy is not Supported on platformName for service serviceName

14 Control-M Messages Manual

A Remedy ticket is not opened.