Control-M Messages

20001 Number versions to keep warning

Invalid system parameters. ${%s}. The VMAdditionalJobsRelateFields Control-M/EM system parameter keeps additional fields, which are used by the Version machines. The system parameter is set with invalid field name.

20002 Invalid system parameters. ${%s}

20003 GUI Server. The Mail server did not respond.

20004 GUI Server. Failed to send ${%s} e-mail notification to ${%s} from sender ${%s} via e-mail server ${%s}.

The GUI Server failed to send an email notification from the sender via the email server.

20005 Failed to create history record for workspace '${%s}' (ws-id=${%s}); operation will proceed, but this workspace's notes will not be audited.

Failed to create a workspace history record for auditing.

24001 Failed to refresh alert list in memory. Alert list will be refreshed in the next refresh cycle. (WARNING).

X-Alert message. Your database might be experiencing problems, or the ALARM table might not exist. During each specified period of time, the GUI Server 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 GUI Server refreshes deleted alerts in the next refresh period.

24002 Failed to load new alert (alert number = alertNumber, data center = dataCenter, severity = severity, order id = orderID). (ERROR)

X-Alert message. A new alert might contain invalid data. The GUI Server 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 GUI Server fails to create a new alert in memory according to the data received from the database.

The following variables appear in this message:

• 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.

24003 Failed to update alert (alert number = alertNumber, data center = dataCenter, severity = severity, order id = orderID). (ERROR)

X-Alert message. An alert in the database might contain invalid data.

The GUI Server receives the indication from Gateway that the specified alert is updated in the database. Due to lack of data or invalid data in the alert, the GUI Server fails to create a new alert in memory according to the data received from the database.

The following variables appear in this message:

• 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)

X-Alert message. The GUI Server fails 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)

X-Alert message. Problems with the database cause the GUI Server 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 GUI Server failed to load alerts from the database when starting. Exiting... (SEVERE)

X-Alert message. Your database might be experiencing problems. The GUI Server fails to load alerts from the database when starting.

The GUI Server shuts down.

25001 Condition could not be sent to data center dataCenter (reason = reason, odate = date, condition = condition). (WARNING).

X-Alert message. The specified condition cannot be distributed to the requested data center.

The variables in this message are:

• dataCenter - the data center name

• reason - an explanation of the failure:

• Fails to connect to the target data center

• Stops trying to send because the maximum number of retries was reached

• Stops 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 is not distributed to the specified data center and production flow may be negatively affected.

26001 DO Remedy is not Supported on platformName for service serviceName (ERROR)

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.

26002 DO SIM is not Supported on platformName for service serviceName(ERROR)

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 is sent (describing the service problem).

26003 BIM Server is not installed (SEVERE)

X-Alert message. The BIM Server is not installed.

26004 Mail Server didn't respond (SEVERE)

X-Alert message. The Mail Server does not respond.

26005 Failed to create ticket in Remedy

BIM. Failed to create a ticket in Remedy.

26006 Service missing or invalid due time, check properties of service ${%s}

BIM. Service missing due time

27001 Forecast Server is not installed (SEVERE)

X-Alert message. The Forecast Server is not installed.

27002 SLS Server Disconnection

Connection to Self Service server is lost.

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

The category value in the ACTIONS_AUTH database table is invalid.

The variables in this message are:

• category: Defines one of the following categories where the authorized actions belong:

  • OPER

  • CTMSEC

  • CONFIG

  • DATABASE

• destination: Defines the component that handles the request.

• request: Defines the name of the request

The Configuration Management Server rejects the request.

28002 Bad or Unknown Auth Level: level, for Destination: destination, request: request

The authorization level value in the ACTIONS_AUTH database table is invalid.

The variables in this message are:

• level : Defines one of the following authorization level values:

  • BROWSE

  • UPDATE

  • FULL

• destination: Defines the component that handles the request.

• request: Defines the name of the request.

The Configuration Management Server rejects the request.

28003 Bad or Unknown Request. Destination: destination, request: request

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

The variables in this message are:

• destination - the component that handles the request

• request - the name of the request

The Configuration Management Server rejects the request.

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

The user does not have permission to perform the request.

The variables in this message are:

• destination - the component that handles the request

• request - the name of the request

The Configuration Management Server rejects the request.

28005 Failed To Locate Component

Fail To Get Component Details. Machine: host, Type: type, Name: component; Code: error

The Configuration Management Server fails to locate the target component for the CTL request.

The variables in this message are:

• host - the component host

• type - the type of the component

• component - the name of the component

• error - the internal error code

The Configuration Management Server rejects the request.

28006 CTL Error

CTL Request Failed. Machine: host, Type: type, Name: component; Code: error

The Configuration Management Server fails to send the CTL request to the target component.

The variables in this message are:

• host - the component host

• type - the type of the component

• component - the name of the component

• error - the internal error code

The Configuration Management Server rejects the request.

28007 XML Parse Error.

An attempt to parse an XML input document fails.

The Configuration Management Server rejects the request.

28008 Handler Not Found For Request: name.

The request is not Supported by the Configuration Management Server.

In this message, name is the name of the request.

The Configuration Management Server rejects the request.

28009 XML Distributor Internal Error: message

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

The polling ID cannot be found in the Configuration Management Server repository.

The polling request is denied.

28011 Gate Error Received: error.

The Configuration Management Server receives an error from Control-M.

In this message, error is the error received from Control-M.

28012 Gate Protocol Error: error.

An internal CMS Gate communication error occurs 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.

A request sent by the Configuration Management Server to the Control-M Configuration Agent does not reply within the time specified by the AdminRequestTimeout parameter.

The variables in this message are:

• name - the Control-M name

• request - the internal request sent by the Configuration Management Server to the CMS Gate

The request times out.

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

A request sent by the Configuration Management Server and the Control-M Configuration Agent is lost. The requested completion status is unknown.

The variables in this message are:

• name - the Control-M name

• request - the internal request sent by the Configuration Management Server to the CMS Gate

A communications error occurred.

28015 CMS Gate Discover Failed, Reason: reason; Host: host, Port: port.

A CMS Gate discover operation fails. Possible reasons are incorrect host or port parameters, or the Control-M Configuration Manager on Control-M is not running.

The variables in this message are:

• 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.

28016 CMS Failed Sending Command To Control-M: name; RC: rc.

The Configuration Management Server fails to send the request to Control-M Communication and the Control-M Configuration Manager cannot be established.

The variables in this message are:

• name - the Control-M name

• rc - the internal error code

The Configuration Management Server rejects the request.

28017 Component Info Parsing Error. Request: request

The Configuration Management Server fails to extract component information from the input XML document.

In this message, request is the request name.

The Configuration Management Server rejects the request.

28018 Component With The Same Key Already exists. Key: key

An attempt to create a component fails, as 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

The Configuration Management Server rejects the request.

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

The requested component is not found in the Configuration Management Server repository.

The variables in this message are:

• type - the component type

• host - the name of the host on which the component is installed

• name - the logical name of the component

The Configuration Management Server rejects the request.

28020 SQL Operation Failed, RC: rc, Message: text

The Configuration Management Server encounters an error while accessing the EM database.

The variables in this message are:

rc - the internal error code

text - the SQL error message, if available

The Configuration Management Server rejects the request.

28021 Set Desired State Failed, RC: rc

An attempt to change the desired state fails. In this message, rc is the internal error code.

The Configuration Management Server rejects the request.

28022 Unable to perform the operation. Reason: Control-M name not found (It was probably deleted by another console)

The Control-M (the destination of the request) is not defined in the Configuration Management Server repository.

In this message, name is the name of the requested Control-M.

The Configuration Management Server rejects the request.

28023 Control-M With The Same Name Or Code Already exists. Name: name, Code: code

An attempt to define a new Control-M fails, since a Control-M with the same name or code already exists.

The variables in this message are:

• name - the new Control-M name

• code - the Control-M short name

The Configuration Management Server rejects the request.

28024 Invalid Or Unknown Operation On Control-M; Operation: action

An internal Configuration Management Server error occurs.

In this message, action is the operation name.

28025 Value cannot be empty for field: fieldName

The required fieldName field in a request is left empty.

The Control-M Configuration Manager displays this message.

28026 Bad value for field: fieldName, bad value is: value

The fieldName field in a request contains an invalid value.

The Control-M Configuration Manager displays this message.

28027 Failed to login as user: userName, rc: rc, message: text

You cannot log in to the database as the userName user (usually the administrator). This may be due to an incorrect username or password.

The variables in this message are:

• userName - the name of the user for whom the log in fails

• rc - the issued return code

• text - the displayed message text explaining why the log in failed, generated by the database vendor

The Control-M Configuration Manager displays this message.

28028 The following request failed: requestName, rc: rc, Message: text

The requestName user request fails.

The Control-M Configuration Manager displays this message.

28029 Invalid number for deleted old alerts. rc: rc, Message: text, Deleted: deletedNum

Old alerts delete 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).

The variables in this message are:

• rc - the return code that is issued

• text - the displayed message text

• deletedNum - the returned number of deleted alerts

The Control-M Configuration Manager displays this message.

28030 A parameter with the same key already exists for paramName

The user tries to add a system parameter that already exists in the PARAMS table.

The parameter is not added to the PARAMS table.

28031 Can't update, parameter's details do not exist: paramName

The user tries to update the paramName system parameter, which does not exist in the database.

The parameter does not update in the PARAMS table.

28032 Fail To Save Desired State In Database.

The Configuration Management Server fails to update the state of Control-M in the EM database.

The Configuration Management Server rejects the request.

28033 Invalid State Code.

An internal XML document receives an invalid state code.

The Configuration Management Server rejects the request.

28034 Invalid Or Unknown Process Type.

An internal XML document receives an invalid or unknown process type.

The Configuration Management Server rejects the request.

28035 Missing Mandatory Value tag.

A mandatory tag or value is missing.

In this message, tag is the missing tag name.

The Configuration Management Server rejects the request.

28036 Invalid Or Unknown OS Type.

An internal XML document receives an invalid or unknown operating system type.

The Configuration Management Server rejects the request.

28037 User Not Registered

The user token is not valid.

The Configuration Management Server rejects the request.

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

The Control-M Configuration Agent is not connected to the Configuration Manager.

The variables in this message are:

• name - the Control-M name

• 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 cannot be completed.

28039 Failed to connect to Control-M/Enterprise Manager Configuration Agent

A connection cannot be established with the Control-M/EM Configuration Agent.

28040 The CMS external pluggable command mechanism encountered an unexpected error. ${%s} rc: ${%s}.

28041 Low Database Space. Database device deviceName is ${%s} percent full, lack of database space may risk EM functionality. (WARNING)

X-Alert message. The database space (data or log segments) has already reached the capacity of 90% (default value).

A warning is issued.

28042 Request for Machine Specification failed

A machine specification request has exceeded the maximum amount of <${%s} attempts and cannot be obtained. This does not affect the system, although there may be a lack of data when generating the Managed Servers report via Control-M Reports.

28043 ManageSSL Request Invokation Failure

When trying to configure Control-M/EM to work in SSL and configuration fails.

28044 CMS [HCU request for <${%s}> <${%s}> failed, <${%s} ${%s}>.

HCU Request Invokation Failure.

28045

Get Web Server URLs request for <${%s}> <${%s}> failed, <${%s} ${%s}>.

Get Web Server URLs Request Invokation Failure

28050 The request to elevate Control-M version failed${%s}.

Elevate Control-M Failure

28051 The request to rename Control-M failed${%s}.

Failure to rename Control-M

28052 Error while load install packages from ${%s}, error: ${%s}.

Get Install Packages Error

28053 Package ${%s} not found in repository ${%s}.

Invalid Package Name

28054 DB is unavailable

The database is currently unavailable.

28055 ${%s}.

Archive Server ARCHIVE_NOT_READ_1

28056 ${%s}.

Archive Server ARCHIVE_NOT_READ_ALL

28057 ${%s}.

Failed to create component.

28058 Component ${%s} crashed due to JVM memory limit, size was set to ${%s}MB.

Component ${%s} crashed due to JVM memory limit, size was set to ${%s}MB.

28059 Apache Kafka is not available.

28060 This utility can be activated on BMC Postgres only. Ask on-site DBA for Postgres file system status.

28061 Syntax error in - Field: "${%s}", with value: "${%s}", ${%s}

28062 Bad or Unknown Auth Policy: ${%s}, for Destination: ${%s}, request:${%s}

28063 To log in, all users must upgrade their Control-M clients to the latest version.\r\n\r\nWarning: ${%s} , rc: ${%s},\r\nMessage: ${%s}

Compatibility Mode has been turned off successfully with a warning.

28070 A more recent Def Conf Item update of the same name already exists

Item name: ${%s}, item type: ${%s}, item sub-type: ${%s}

28071 Up-to-date item name: ${%s}, item type: ${%s}, item sub-type: ${%s}

Def Conf Item is up-to-date

28070 A more recent Def Conf Item update of the same name already exists.

Item name: ${%s}, item type: ${%s}, item sub-type: ${%s}

28072 Checksum calculation error for data: ${%s}, checksum: ${%s}

28073 Incorrect maximum number value: ${%s}, for returned items was requested

28074 Server failed to read def conf item id: ${%s}, name: ${%s}.

28090 Synchronization status: Synchronized

28091 Synchronization status: Pending deletion

28092 Synchronization status: In Progress

28093 Synchronization status error: Unknown status

28094 Synchronization status error: Control-M Server is down

28095 Synchronization status error: Control-M Server cannot be connected

28096 Synchronization status error: Control-M Server did not respond

28097 Synchronization status error: Control-M Server responded with error message: ${%s}

28098 Synchronization status error: An internal error occurred while trying to sync with Control-M Server

28120 Synchronization status: Synchronized

28121 Synchronization status: In Progress

28122 Synchronization status: Partially

28123 Synchronization status: Unknown status

28124 Synchronization status: Failed

28125 New component of Web Server in distribted EM with WI is not allowed. Key: ${%s}

29001 EM - Control-M name Communication Service Timed Out. timeout= time, type= type, instance= ID (ERROR)

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 output, log or download.

The variables in this message are:

• name - the Control-M name

• time - the length of the timeout, in seconds

• type - the type of requested service

• ID - the internal service ID

The service is canceled by the Gateway.

29002 Definition Upload Timeout

Upload of folderName Aborted (time-out), no answer from Control-M name. timeout= time, instance= ID

A service that was uploading a definition folder timed out. This message appears together with general timeout message 29001. The final status of the upload is unknown.

The variables in this message are:

• folderName - the definition folder name.

• name - the Control-M name.

• time - the length of the timeout, in seconds.

• ID - the internal service ID.

The service is cancelled by the Gateway.

29003 Download of folderName Aborted (time-out), no answer from Control-M name.

A service that was downloading a definition folder timed out. This message appears together with general timeout message 29001. The status of the folder in Control-M/EM is unknown.

The variables in this message are:

• folderName - the definition folder name

• name - the Control-M name

The service is canceled by the Gateway.

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

A service that was downloading a definition folder aborts. The status of the folder in Control-M/EM is unknown.

The variables in this message are:

• folderName - the definition folder name.

• name - the Control-M name.

The service is cancelled by the Gateway.

29005 Gateway Client (name) CommEMBufferSize =maxSize Actual = actualSize. (WARNING)

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 or Global Conditions Server) is full. The buffer size is determined by the value of the CommEMBufferSize system parameter.

The variables in this message are:

• 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.

29006 Gateway Control-M name CommCTMBufferSize = maxSize Actual = actualSize. (WARNING)

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 determined by the value of the max_mf_queue_size parameter in the Defaults.rsc file.

The variables in this message are:

• name - the Control-M 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.

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)

X-Alert message. The Gateway receives a request from the Control-M/Server to update an active job, but the job is 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 on the Control-M/Server.

The variables in this message are:

• name - the Control-M name

• 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

29008 Active Download Failure. Control-M name, Odate date, Net Name (netName), Sequence Number number (ERROR)

X-Alert message. A request to download Active Jobs from Control-M fails. For additional details, check the Gateway log file.

The variables in this message are:

• name - the Control-M name

• 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 again.

29009 Create Alert Failure. (ERROR)

X-Alert message. The Gateway fails to insert an alert into the database. The following alert parameters are displayed:

• Control-M

• Memname

• Jobname

• OID

• Msg

• Sev

• Run As

• Time

• Appl

• Sub-application

• HostId

• Type

• Closed_from_EM

• Ticket

• Run

For descriptions of these parameters, see Control-M Parameters .

The alert discards.

29010 Update Alert Failure. (ERROR)

X-Alert message. The Gateway fails to update an alert in the database. The following alert parameters are displayed:

• Control-M

• Memname

• Jobname

• OID

• Msg

• Sev

• Run As

• Time

• Appl

• Sub-application

• HostId

• Type

• Closed_from_EM

• Ticket

• Run

• Handled

• ChangedBy

• UpdTime

• Notes

For descriptions of these parameters, see Control-M Parameters.

The update is rejected.

29011 Gateway - GCS Communication Service Timed Out. Control-M name timeout= time, instance= ID, Condition= condition (ERROR)

X-Alert message. A service for distributing global conditions timed out.

The variables in this message are:

• name - the Control-M name

• time - the length of the timeout, in seconds

• ID - the internal service ID

• condition - the condition name

The service is canceled by the Gateway. Its status in the Global Conditions Server (GCS) is unknown.

29012 Gateway - GCS Communication Service Aborted In Gateway. Control-M name, instance= ID, Condition= condition (ERROR)

X-Alert message. A service for distributing global conditions aborted, because communications with the Global Conditions Server (GCS) closed.

The variables in this message are:

• name - the Control-M name

• ID - the internal service ID

• condition - the condition name

The service is canceled 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.

29013 Processing Of Updates Timed Out, Probably Database Slow Response Time. Control-M name, Timeout=time. (WARNING)

X-Alert message. An update arriving from Control-M/Server is not processed for a considerable period of time.

The actual job status in Control-M/EM might be delayed.

29014 Processing Of Updates Timed Out, Probably Database Slow Response Time Or Internal Error. Control-M name, Timeout=time. (ERROR)

X-Alert message. An update arriving from Control-M/Server is not processed for a considerable period of time.

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)

X-Alert message. An update arriving from Control-M/Server is not processed for a considerable period of time.

Gateway will restart itself in order to try and recover from this situation.

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

X-Alert message. Internal error in Gateway during data processing.

Gateway will restart itself in order to try and recover from this situation.

29017 DO_MAIL message too long, message truncated. Folder Id: folderID. (WARNING)

X-Alert message. A specific job data includes the DO_MAIL option and the message length exceeds the maximum length allowed. When this job's data arrives from Control-M/Server to Control-M/EM the gateway truncates the message in order to fit into the relevant database field. The data arrives 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

29018 DO_MAIL message too long, message truncated. Folder Id: folderIDOrder Id: folderID. (WARNING)

X-Alert message. A specific job data includes the DO_MAIL option and the message length exceeds the maximum length allowed. When this job's data arrives from Control-M/Server to Control-M/EM the gateway truncates the message in order to fit into the relevant database field. The data arrives as part of an Active Job file job update.

The job data which arrives from Control-M/Server is processed in Control-M/EM. However, the message is truncated once inserted into the Control-M/EM database. In addition, the following message appears in 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

29019 Workload Sync Error

Workload Sync Service error. There was a failure to check-in a workspace. Control-M Workload data may not be up to date.

29020 Workload Update Error

Workload Update Service error. There was a failure to check-in a workspace. Control-M workload data may not be up to date. Received message: ${%s}

29021 Workload Update Canceled

Workload Update Service canceled. There was a failure to check-in a workspace. Control-M workload data may not be up to date.

35001 Control-M/EM Manual Failover completed, now running on ${%s}

High availability. Failover completed.

35002 Control-M/EM Manual Fallback completed, now running on ${%s}

High availability. Fallback completed.

35003 Control-M/EM Auto-Failover completed, now running on ${%s}

High availability. Failover completed.

35005 Failover failed

High availability. Control-M/EM manual failover has failed.

35006 Fallback failed

High availability. Control-M/EM fallback has failed.

35011 Set secondary as primary has failed

High availability. Control-M/EM active host switch has failed.

35012 Set secondary as primary failed

Control-M/EM must run on the secondary host.

35013 Missing High Availability parameters

Failed to get High availability from Control-M/EM database

35014 Failed to update Database

Failed to update high availability

35015 Can't set primary as secondary while Control-M/EM Fallback or Failover did not end.

35016 Set secondary as primary unavailable during data replication.

Can't set primary as secondary while Control-M/EM Start Replication did not end

35017 Can not perform Failover/Fallback for Control-M/EM while the last Fallback or Failover action did not end.

Failover/Fallback cannot run as already started.

35018 Can not perform Failover/Fallback for Control-M/EM while Control-M/EM Postgres Replication did not end.

Failover/Fallback cannot run during data replication.

35019 Primary Control-M/EM Configuration Agent on ${%s} is not responding.

35020 Primary Control-M/EM HA server is not responding.

Primary Control-M/EM HA server is not responding.

35021 Secondary Control-M/EM HA server is not responding.

Secondary Control-M/EM HA server is not responding.

35022 Failed updating database.

35023 Failed to sync to configuration file

High Availability. The following files could not be synced:

${%s}.${%s}]

35024 Moving to stand-by host

High Availability. Control-M/EM auto-failover is starting now.

35028 Distributed EM Configuration Agent is unavailable

High Availability. Distributed Control-M/EM Configuration Agent on ${%s} is not responding.

35029 Active EM Configuration Agent is unavailable

High Availability. Active Control-M/EM Configuration Agent on ${%s} is not responding.

35030 Stand-by EM Configuration Agent is unavailable

Non-active Control-M/EM Configuration Agent on ${%s} is not responding. No High-Availability.

35032 Installed Fix-Pack levels don't match

No high availability. Fix-Pack level ${%s} on primary does not match fix-pack level ${%s} on secondary.

40001 EM Server failed to write audit action to the EM database (action = action, user = userName, return_code = rc, db error = error (ERROR)

X-Alert message. The Control-M/EM server fails to write an audit action to the Control-M/EM database.

The variables in this message are:

• action - the audit action that was not written to the database

• userName - the name of the user who requested the action

• rc - the return code that is issued

• 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.

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)

X-Alert message. The Control-M Configuration Manager fails 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.

40003 Performing this operation requires you to provide details about your activity.

40004 User does not have authorization to perform login.

40005 Client used to login is not compatible with server version

40006 Delete Confirmation: Do you want to delete the selected item(s) including the descendants?

40007 Do you want to delete the selected item(s) including the descendants (total {1} items)?

Delete Confirmation

40008 Do you want to ${1} ~${2} ~{ '}~${3}~{'} ^the ^${4} ^selected ^${2}^(s){?} ${5}

Action Confirmation

40009 Operation is being cancelled. Any changes will be discarded.

Cancel Annotation

40100 LDAP authentication can not be configured

Directory service authentication is not set. EM internal authentication is active.

40101 User can not be authenticated in LDAP

User's directory access name is not well defined.

40120 User and password entered by the user not accepted by RSA Authentication Manager.

40121 Login information OK, but user is required to repeat login using next token-code

40122 User is required to change PIN used by RSA Authentication Manager

40201 Database server is unavailable for more than number minutes. (WARNING)

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 on even when the database is not available. This message appears after the database has been down for one hour.

40202 Communication with the database server was lost and can not be recovered. Server is shutting down in ${%s} minutes. (ERROR)

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.

40203 Database server is unavailable for more than ${%s} seconds. Server is shutting down (WARNING) for CMS (SEVERE) for all other components

X-Alert message. The Control-M/EM server component issues this message when it does not have communication with the database for more than number seconds.

The server component shuts down.

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

X-Alert message. The Control-M/EM server component issues this message when it detects that it loses communication with the database server and 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.

40205 Server failed to read system parameter type: paramType, name: paramName. (ERROR).

X-Alert message. The Control-M/EM server component fails to read a system parameter from the PARAMS table, which might be due to a problem with the database. This message does not display when the system parameter is missing from the PARAMS table, which is a normal and valid scenario.

The variables in this message are:

• 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.

40206 LDAP Directory Server is unavailable

LDAP Directory Server is unavailable. Returned message: ${%s}.

40401 Scheduling group with this scheduling folder name already exists. Change the scheduling folder name or the scheduling folder library.

The folder name specified for the new sub application is already being used. Relevant when working with MVS.

The system is unable to create a new folder.

40402 Scheduling group with this scheduling folder name already exists. Change the scheduling folder name.

The folder name specified for the new sub application is already being used. Relevant when working with MPM.

The system is unable to create a new folder.

40403 A regular scheduling folder with this name already exists. Change the scheduling folder name or the scheduling folder library.

The folder name specified for the new sub application is already being used for a regular folder. Relevant when working with MVS.

The system is unable to create a new folder.

40404 A regular scheduling folder with this name already exists. Change the scheduling folder name.

The folder name specified for the new sub application is already being used for a regular folder. Relevant when working with MPM.

The system is unable to create a new folder.

40405 Lock Folder Failed

The folder containing this job is locked.

This operation cannot be completed.

40406 Unauthorized user

You are not authorized to perform this operation.

40407 Create scheduling group failed.

40408 SMART table '${%s}' includes a Rule-Based Calendar definition that can only be edited through the Server account.${endl}The Table Editing Form will be opened in read-only mode.

40409 This entity no longer exists in Enterprise Manager database and${endl}may have been deleted.

40410 You cannot modify this SMART table's type since it contains sub-tables.

40411 Table Already Exists

Table '${%s}' already exists in Enterprise Manager database.${endl}Would you like to load it?

40412 Enterprise Manager application is currently disconnected You need to login in order to view details of Rule-Based Calendar.

40413 Not all selected calendars were copied.${endl}A Rule-Based Calendar of a Server level can only be copied into same Server platform and version.

40601 A server failure has occurred while locating the job definition.

40602 Could not locate the job definition due to the following reasons: ${endl} - The job's parent table '${%s}' is currently unlocked. ${endl} - The job does not exist or cannot be uniquely identified.${endl}To view the job history, you should either reload the table or work with an online workspace.

Different jobs are matched with history chain

40603 Could not locate job's definition.${endl}Job was either deleted or not written to the database.

Job is not under database

40604 Restoring '${%s}' requires that the '${%s}' table, with ${%s} jobs, be loaded into the local workspace.${endl}Click Yes to load the table, No to skip to the next selected item, or Cancel to abort the operation.

Load table to restore

40605 Job was modified when its parent table was unlocked.${endl}The selected version might possibly be associated with a different job. It is recommended to review the job's details in the JEF to ensure they are valid within the current environment.${endl}Do you want to proceed with the restore operation?

Job history may belong to a different job

40606 Could not restore a job into a table that is locked by another user.

Abort restore operation

40607 Could not restore a SMART table that exists in the database or resides within the workspace.

Abort restore operation

40608 Processing is involved with large size of definitions.${endl}In order to commit query you need to refine filter criteria.

40609 Could not restore a job that belonged to a SMART table into an existing or a loaded table.

Abort restore operation

40610 Could not locate an historic version of a job.

40611 Before restoring a definition ensure that all parameters are valid within the current environment.${endl}Proceed with the restore operation?

Confirm Restore Operation

40612 Job was modified when its parent table was unlocked.${endl}The selected version might possibly be associated with a different job. It is recommended to review the job's details in the JEF to ensure they are valid within the current environment.${endl}Do you want to proceed with the restore operation?

Confirm Restore Operation

40613 Restore operation can only be applied into a local workspace.${endl}If the current workspace is not a local or contains an unlocked parent table a new local workspace is required.

Can not complete restore action

40614 Confirm Restore Operation

The selection contains items that were created after your specified date and time.${endl}If you plan to delete these definitions by performing a Write action, click Delete.${endl}If you want to restore these definitions to the workspace, click Restore.

40615 Your selection contains item(s) that cannot be loaded into the local workspace due to their "Restore Ability" status.${endl}These will be excluded from the selection.

Restore Unavailable

40616 Restore:${endl}Restore job(s) of table '${1}' ~succeeded ^failed ${2}

Action Report Entry

40617 Confirm Restore Operation

The selected item was created and deleted after the specified date.${endl}The latest version will be placed into the local workspace that can be later written to database.

Confirm Restore Operation

40618 Restore operation can only be applied into a local workspace.${endl}If the current workspace is not a local or contains an unlocked parent table a new local workspace is required.${endl}Operation will be applied into a new local workspace.

40619 Restore Operation

Cannot complete operation.${endl}The Server is not defined in Control-M Configuration.

40620 Restore Operation

Display definition changes made since specified date and time.

40621 Restore Operation

The current workspace contains a parent job table and is unlocked.${endl}Either lock the table or reload the table from the database.

40622 Restore Operation

No - Cannot locate version that matches specified date & time

40623 Restore Operation

Modified - item no longer matches specified filter

40624 Restore Operation

Modified - item was changed and now matches specified filter

40625 Restore Operation

Type;Change Type;Restore Ability;Latest Version;Deletion Time;Deleted By User;Deleted By Hostname;Job Name;Member Name;Member Library;Group;Application;Description;Version Number;Changed User;Changed Time;Table Name;Server;Job ID;Task Type;Node ID;Table ID;Creation Time;

40626 The selection contains entities from the same parent table '${%s}' that was deleted more than once.${endl}You can only select entities from one table existence.

40627 The requested version cannot be restored because its parent name has been changed.

.

40628 The Restore operation is running.${endl}Do you want to cancel the process?

40801Server failed to load active net. (server, collection). (ERROR)

X-Alert message. The GUI Server fails 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.

40802 Server failed to load archived net. (server, collection, net). (ERROR)

X-Alert message. The GUI Server fails 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.

40803 GUI Server failed to load active net. Net table was not found in database. (server, collection). (WARNING)

X-Alert message. The GUI Server fails 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 Server failed to load archived net. Net table was not found in database. (server, collection, net). (WARNING)

X-Alert message. The GUI Server fails 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.

40900 Periodic calendar (calendar_Control-M | calendar_name) used in periodic statistics definition ' periodic_stats_def_name' was not found. (ERROR)

X-Alert message. This message relates to the Control-M/EM periodic statistics mechanism, which uses an undefined periodic calendar. 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.

41001 The soft limit of resource parameter parameter is too low. Soft limit should be equal to or larger than requested value.

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 host resources might affect proper operation of Control-M/EM processes.

Update the relevant OS resource soft limit according to the value indicated in the X-Alert message.

After updating the OS resource soft limit:

41002 Both soft and hard limits of resource parameter parameter are too low. Limits values should be equal to or larger than requested value.

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 host resources might affect proper operation of Control-M/EM processes.

50001 Invalid character at position position. Input: string.

Job validation encounters an invalid character in one of a job's fields.

The variables in this message are:

• position - the position of the character in the string

• string - the entire string

50002 Field contains invalid value string.

Job validation encounters 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.

An invalid character uses a delimiter in one of the job fields. A valid delimiter character expects a certain position in the character string.

The variables in this message are:

• character - the expected delimiter character

• position - the position of the character in the string

• string - the entire string

50004 Maximum length for that value should be maxLength

The value inserted into one of the job's fields exceeded the maximum length of that field.

In this message, maxLength is the maximum length of the value.

50005 Invalid value number - out of range.

The numeric value inserted into one of the job's fields is out of range.

In this message, number is the numeric value that the user enters.

50006 Invalid character character at position position. Input: string

Job validation encounters a value containing an invalid character in one of the job's fields.

The variables in this message are:

• character - the invalid character

• position - the position of the character in the string

• string - the entire string

50007 The value contains invalid characters. Input string.

Job validation encounters a value containing an invalid character in one of the job's fields.

In this message, string is the entire string.

50008 The value is too short. Input string.

Job validation encounters a value that is too short in one of the job's fields.

In this message, string is the entire string.

50009 Invalid value: string

Job validation encounters an invalid string in one of the job's fields.

In this message, string is the entire string.

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

Job validation encounters lower-case characters in one of the job's fields.

In this message, string is the entire string.

50011 The field must have a value.

Job validation discovers a mandatory field is 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

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.

50013 When the Tag Relationship is set to 'And', at least one scheduling tag must be selected.

Job validation discovers that the Tag Relationship in a job is set to 'And', but no scheduling tag is selected.

50014 Field fieldName - The specified value is too long. Specify a shorter value.

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.

50015 Field value must be unique.

50016 Too many items (Maximum ${%s})

50017 Calendar name for ^distributed ~z/OS {Server version} ${%s} may not exceed ${%s} characters.

60001 Failed to establish connection with Server

This error may be caused by any of the following cases:

• The Server Name is invalid

• The Control-M/EM Server is not responding

You attempt to log in to Control-M, but log in fails.

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 connection with Control-M/EM is lost.

60003 Invalid username or password: Make sure: - The user is defined properly - The given password is correct

You attempt to log in to Control-M/EM, but log in fails because the username or password is incorrect.

60004 User is not authorized for that action

You attempt to perform an action for which you do not have authorization.

60005 Your password is about to expire

Your password is about to expire.

60006 User account is locked

You attempt to log in to Control-M/EM, but the attempt fails because your account is locked.

This might occur because:

• The system administrator has manually locked your account.

• You try to log in to the system several times and failed, exceeding the maximum number of failed log in attempts.

60007 Login Failed: This error may be caused by any of the following: (Edit and save the file. Restart the application to apply the new settings.)

You attempt to log in to Control-M/EM, but login fails.

ServerName is the logical name of the server that was chosen during login. The default name is the name of the machine where Control-M/Server runs.

60009 Login Failed: Ensure Server under context serverName has the correct version.

You attempt to log in to Control-M/EM, but the log in attempt fails because there was a version mismatch between the Control-M/EM server and the application that you tried to run (for example, Control-M).

In this message, serverName is the logical name of the server that was chosen during log in. The default name is the name of the machine where Control-M/Server is running.

60010 Login Failed: This error may be caused by any of the following:- User userName is not defined properly.- The specified password is incorrect.

You attempt to log in to Control-M/EM, but log in fails. This might be due to one of the following reasons:

• The userName username is not defined properly

• The specified password is incorrect

60011 Login Failed: Password has expired

You attempt to log in to Control-M/EM, but the log in fails because your password has expired.

60012 Serialization might fail (WARNING)

The draft file was saved in an environment different than this:${endl}The draft environment supported Control Resources for SMART Tables of Control-M Distributed version 700 FP2 and later.${endl}${endl}Loading might fail.

60013 Serialization might fail

The draft file was saved in an environment different than this:${endl}The draft environment did not support Control Resources for SMART Table of Control-M Distributed version 700 FP2 and later.${endl}${endl}Some jobs might be invalid.

60100 Invalid regular expression value. Please check the pattern matching rules in the documentation.

Invalid regular expression value. Please check the pattern matching rules in the documentation.

60201 Application encountered a system security restriction.${endl}The following actions are required:${endl}1. Assign the current user higher privileges through User Account Control (UAC).${endl}2. Uninstall CONTROL-M EM Web Launch using the Windows Control Panel - Add/Remove Programs.${endl}3. Re-deploy CONTROL-M EM Web Launch.

60202 Initialization fail

Application encountered an error that is either related with a deployment failure or a system security fault.${endl}The following actions are required:${endl}1. Uninstall CONTROL-M EM Web Launch using the Windows Control Panel - Add/Remove Programs.${endl}2. Re-deploy CONTROL-M EM Web Launch application.

Application encountered an error that is either related with a deployment failure or a system security fault.${endl}The following actions are required:${endl}1. Uninstall CONTROL-M EM Web Launch using the Windows Control Panel - Add/Remove Programs.${endl}2. Re-deploy CONTROL-M EM Web Launch application.

60203 Deployment can't be completed

The existing instance '{0} {1} ({2})' can't be updated with a lower version of {3}.${endl}Application now exists.${endl}Uninstall CONTROL-M EM Web Launch using the Windows Control Panel - Add/Remove Programs.

60701 Forecast/BIM Rules were modified by user '${%s}'.${endl}Do you want to save your changes and override last changes?

60702 Failed to get Forecast/BIM Rule from BIM server.${endl}Maybe this rule was deleted.

60703 Another Service Assumptions window is already open.${endl}Please close it in order to open another service's Assumptions window.

60704 Invalid regular expression value. Please check the pattern matching rules in the documentation.

60705 New deadline should be after the service order time.

60706 Connection to BIM server is lost

60707 Disconnected from BIM or Forecast Server

60708 Failed to get assumptions of service '${%s}' (${%s})${endl}Service might not exist any longer.

70001 Large amount of resources

The list loads with more than ${%s} items.

70002 Required Field

The field '${%s}' is required

70003 Form validation failed

The form validation fails.

70004 Save Changes

Do you want to save the changes?

70005 Multi Delete. Are you sure you want to delete these ${%s} items?

70006 Are you sure you want to delete '${%s}'?

70007 The user is not authorized for the action pertaining to the GUI.

70008 The number of matches exceeds the current list limit.

Partial lists of results are displayed.

70009 Field length exceeds limit

The field ${%s} length exceeds the limit of ${%s} characters.

70010 Are you sure you want to hide the Alerts window?${endl}This will not disconnect you from the Global Alerts Server.

70011 Connection with Global Alerts Server was closed.

70012 No jobs are currently using the control resource.

70013 View joblist not available

Viewing a job list is supported only for jobs running on Control-M for O/S 6.1.00 or higher.

70014 Invalid character

The field ${%s} contains an invalid character.

70017 Failed to ${%s}${endl}The request failed: '${%s}'

70018 Failed to open ViewPoint.

ViewPoint wil be closed.${endl}${endl}Reason:${endl}${%s}${endl}${endl}See log file for more details.

70019 ViewPoint wil be closed.${endl}${endl}Reason:${endl}${%s}${endl}${endl}See log file for more details.

70020 Failed to get service information.${endl}Close and reopen ViewPoint in order to continue analyze the service.

70021 Service is unavailable.

BMC Batch Impact manager exceeded the limit of concurrent 'Business Service Analysis' ViewPoints with scenario.{endl}Please try again later or consult your system administrator.

72001 The destination year already exists.

he destination year already exists, Overwrite?

72002 February 29th

Please note that the date 'February 29th' received an arbitrary value

72003 Periodic statistics deletion?

Are you sure you want to delete the selected periodic statistics definition?

72004 Perodic statistics definition has been modified.

The period statistics definition has been updated. Do you want to save your changes?

72005 Failed updating the periodic statistics.

72006 You must select different versions

72007 Version was not found.

72008 Failed to inherit conditions of job ${%s} from table ${%s}

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

An attempt to log in to the Control-M Configuration Manager failed. This is often due to an incorrect username or password, or selecting the wrong server name from the list.

The variables in this message are:

• serverName - the name of the Control-M Configuration Manager to which you are trying to login.

• userName - the name of the user who requested the action.

The Configuration Management Server displays this message and allows another attempt to log in.

74002 Invalid database type: Actions on the database are not allowed since there was a problem in getting database details

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

A system parameter was not selected for an action, but 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.

74004 Missing parameter

A value is missing for a parameter.

74005 CMC Exception was raised: Action performed: action Exception message: text

The Control-M Configuration Manager raised an exception while attempting to perform an action.

The variables in this message are:

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.

74006 Unknown Database type: type. Action will terminate.

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

A value is missing.

74008 Value out of range

Value for ${%s} is out of range.

74009 Invalid file name

The filename ${%s} is invalid.

74010 Action failed: Action has failed for unknown reason. Please refer to the application logs for additional information

An action fails, due to an unknown error.

In this message, action is the action that fails.

The Control-M Configuration Manager displays this message. Normal processing continues.

74011 File already exists

The filename specified already exists.

74013 Failed to send request to the Server: Failed action: action.

The Control-M Configuration Manager client fails to send a request to the Configuration Management Server.

In this message, action is the request action that fails.

Processing continues without completing the request. The action that fails is displayed.

74014 Dialog validation error

You click 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.

74015 The connection to the server is lost. The connection will be restored when available.

The connection to the Configuration Management Server is lost.

74016 The connection to the server was restored.

The connection to the Configuration Management Server restores after it was lost.

74017 Control-M Configuration Manager: Your password has expired. Please refer to the Control-M/EM documentation for further information.

You try to log in to the Control-M Configuration Manager, but are unsuccessful because your password has expired.

You cannot log in.

74018 Control-M Configuration Manager: Your password will expire shortly. Please refer to the Control-M/EM documentation for further information.

You log in to the Control-M Configuration Manager and receive a message that your password expires soon.

Normal processing continues.

74019 Control-M Configuration Manager: The account is locked.

You try to log in to the Control-M Configuration Manager, but the user account is locked.

You cannot login.

74020 Control-M Configuration Manager: Post login failed: reason

Actions that are performed automatically after the log in to the Control-M Configuration Manager fails.

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.

A Control-M Configuration Manager action succeeds. The server returns a message, which is presented to the user.

The variables in this message are:

• action - the name of the action that succeeded

• text - the text of the displayed message

Normal processing continues.

74022 Duplicate component was identified

A duplicate component is identified by the system. The duplicate component does not display.

74023 Action Confirmation

Are you sure you want to ${%s} ~${2} ~{ ('}~${3}~{')} ^the ^${4} ^selected ^${2}^(s){?} ${%s}

Are you sure you want to ${%s} ~${2} ~{ ('}~${3}~{')} ^the ^${4} ^selected ^${2}^(s){?} ${%s}

74024 Audit Confirmation

Performing this operation requires you to provide details about your activity.

75001 Failed to load database parameters from Enterprise Manager ${endl}Exiting Application

75002 Control-M/EM fails to retrieve the database hostname and port.

Control-M Reports cannot open because it cannot connect to the Control-M/EM database.

75003 Either the database is not running or the OLEDB driver is not installed or registered.

Check the log file for more information.

Control-M Reports failed to connect to the Control-M/EM database and cannot open because it cannot connect to the Control-M/EM database.

The possible causes are as follows:

• The database is not running on the host and port specified in "More Details"

• The OLEDB driver is not installed or configured correctly

• Incorrect hostname and port were used to connect to the database

.

76001 over length

INFORMATION - argumnet over length${endl}${endl}The value of annotation arguments should not exceed the maximum length of:${endl}-action_reason (128), -action_note (255).${endl}___________________________________________________________________________________${endl}

81001 Node JVM Heap Memory usage is higher than 80%, this can affect Workflow Insights dashboards performance.It might be solved by increasing node memory or by adding an additional node to the cluster.

81002 Node free disk space is under 10%, this can affect future Workflow Insights data ingestion.It might be solved by increasing node disk space or by adding an additional node to the cluster.

81003 Snapshot creation failed

Cluster data backup failed ${%s} times because the last backup is still running. Last successful backup: '${%s}' A new data backup attempt occurs every ${%s} minutes. If the issue does not resolve itself, it is recommended to increase the 'snapshot interval' at ${%s} in all cluster nodes and then recycle the Workflow Insights service.

81004 Snapshot creation failed

Cluster data backup failed ${%s} times. Last successful backup: '${%s}' Failure reason: ${%s}.

81005 Snapshot creation failed

Cluster data backup failed ${%s} times. Last successful backup: '${%s}' Failure reason: ${%s}.

81006 Node free disk space is under 20%, this can affect future Workflow Insights data ingestion.It might be solved by increasing node disk space or by adding an additional node to the cluster.

81007 Snapshot creation failed

Cluster data backup has failed. Ensure that the opensearch and Workflow Insights services were Recycled after defining the 'Cluster backup location' setting.

81008 Snapshot creation failed

Workflow Insights data is not backup up for ${%s}. Last successful backup started at: '${%s}'.

81009 Snapshot creation failed

Cluster data backup has failed. Ensure that the opensearch and Workflow Insights services were configured as described in the documentation.

81010 Snapshot location invalid

Workflow Insights data is not backed up because the 'Cluster backup location' setting has not been defined or contain invalid path. To initiate Cluster backup, define the 'Cluster backup location' setting and follow the recycle procedure described in the documentation.

81011 Data Export target path invalid

Workflow Insights data cannot be exported since 'WIExportTargetPath' contains an invalid path: '${%s}'. Modify the path to allow the data export process.

81012 Data Export task invalid

Workflow Insights data export failed to process export task '${%s}'.

81013 Data Export publish task failed

Workflow Insights service failed to publish export tasks to kafka.

81014 Data Export read failed

Workflow Insights service failed to get documents to export. Message: '${%s}'.

81015 Workflow Insights service failed to add the index time pipeline.

81016 Workflow Insights service failed to write the export file '${%s}'.

81017 Workflow Insights service failed to rollover index '${%s}'

Ended not ok

Job has ended not ok.

DATA CENTER %s WAS DISCONNECTED

Control-M/Server has disconnected from EM.

4900 WORKLOAD workloadName UPLOADED FROM CTM|EM

The workload (workloadName) has been uploaded from Control M\EM.

4901 WORKLOAD workloadName DELETED FROM CTM|EM

The workload (workloadName) has been deleted from Control M\EM.

4902 SUCCESSFULLY SAVED WORKLOAD(S) WITH TYPE type

There are two kinds of workload(s) updates requests from the Control-M\EM.

• FUL: All workloads are sent from Control M\EM and should be saved by the Control-M\Server.

• UPD: Certain workload is sent from Control-M\EM and should be saved by the Control-M\Server.

4903 WORKLOAD workloadName HAS BECOME state

The workload (workloadName) has changed its state to either Inactive, or Active.

4904 WORKLOADS ORDER LIST WAS UPLOADED FROM THE CTM\EM

A new order list of workloads is uploaded from Control-M\EM.

4905 MAXIMUM JOBS LIMIT FOR WORKLOAD workloadName HAS BEEN CHANGED TO number

The maximum jobs policy of workload (workloadName), which indicates how many jobs of that workload can be submitted concurrently, has been changed to (number).

4906 MAXIMUM RESOURCE LIMIT FOR WORKLOAD workloadName HAS BEEN CHANGED TO number

The maximum quantitative resource policy of workload (workloadName), which indicates how many quantitative resources can be used by jobs of that workload, has been changed to (number).

4907 THE HOST GROUP HAS BEEN CHANGED TO hostGroup DUE TO MAPPING POLICY OF WORKLOAD workloadName

A job's host group has been changed to new host group (hostGroup), because of a mapping policy of workload (workloadName), in which this job is a member.

4908 THE HOST GROUP HAS BEEN RESTORED TO DEFINITION

A job's host group has been changed back to its original definition. This happens probably when a job is no longer a member of a workload, or the workload(s) or is a member, but does not have mapping policy.

4909 JOB IS NOW A MEMBER OF THE FOLLOWING WORKLOADS listOfWorkloadsNames

Specifying a list of workload names, of which a job has become a member.

When a job is first entered or is already present in the active environment The workflows of jobs and SMART folders that are scheduled to execute on the current Control-M day., and the list of workloads (which it is already a member) have been changed.

4913 JOB IS NOT ASSOCIATED WITH A WORKLOAD

Usually printed, when a job enters the active environment either for the first time or is present, but is no longer associated with a workload(s) because of changes in workload filter definitions or job definitions.

4914 ACCOUNT <Account_name>, APPLTYPE <Application_type>, AGENT <agent_name> is Disabled|Unavailable. [Message from Agent follows]

This message appears in the output of WHY request to indicate that the Account where the job is submitted is disabled or is unavailable. If the account is unavailable, this message will be followed by message 5226.

4920 MAXIMUM JOBS LIMIT FOR HOST hostname HAS BEEN CHANGED TO number

The maximum jobs limitation of host (hostName), which indicates how many jobs can be submitted concurrently to that host, has been changed to (number).

4921 MAXIMUM CPU LEVEL FOR HOST hostname HAS BEEN CHANGED TO number

The CPU level limitation (in percentage) of host (hostName), which indicates not to submit any job to that host if its CPU usage is above the level specified, has been changed to (number).

4922 DIFFERENT CPU USAGE HAS BEEN REPORTED FROM HOST hostName AS newCpuUsage

When there is a CPU level limitation, (control the jobs' submission to a certain host), each time the CPU usage goes below or above the level specified, reported by the host of course, this message generates.

On a periodic basis, a message is received from the host specifying the current CPU usage.

5003 MAXRETRY REACHED FOR processID. SUPERVISOR IS SHUTTING DOWN

Control-M is shutting down. The supervisor tries to activate the Control-M processID process (Tracker, Submitter, and so forth) the number of times specified in the MAXRETRY Control-M system parameter, and fails.

Control-M is shutting down.

5006 Control-M LOG CLEANUP ENDED. DAYS= days

The New Day procedure performs 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

A cyclic job or cyclic SMART folder changes to a non-cyclic job or SMART folder, which executes at the same time as the New Day procedure. This is because Control-M cannot determine the action to take regarding this job/SMART folder while executing.

The cyclic job or cyclic SMART folder completes its current cycle and changes to a non-cyclic job or SMART folder.

5011 Control-M LOG CLEANUP STARTED

The Control-M log cleanup process starts.

The New Day procedure begins the partial cleanup of the Control-M log.

5014 Control-M AGENTS CLEANUP STARTED

Control-M/Server sends cleanup requests to all Agents. This action occurs during the New Day procedure or when invoking the ctmagcln utility to all Agents. The request appears in the following format:

ctmagcln -agent "*"

Agents are requested to clean the old output and status/backup files according to the Maximum Days to Retain Output Files parameter. Control-M/Server sends the cleanup requests to all Agents.

5015 Control-M AGENTS CLEANUP ENDED. DAYS= days

Control-M/Server finishes sending cleanup requests to all Agents. This action occurs 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) sent to Agents is determined by the value assigned to the Maximum Days to Retain Output Files parameter. The execution of the ctmagcln utility finished successfully.

5016 Control-M AGENT agent WAS NOT CLEANED

Control-M/Server fails to send the New Day cleanup request to the specified Agent.

Control-M/Server attempts to send the request to the rest of the available Agents.

5017 Control-M AGENT(S) CLEANUP FAILED

Control-M/Server fails to send the New Day cleanup request to the requested Agents. No Agents are cleaned.

Execution of the ctmagcln utility fails.

5018 Control-M AGENT agent CLEANED SUCCESSFULLY. DAYS= days

Control-M/Server successfully sent the New Day cleanup request to the specified Agent. This action occurs when invoking the ctmagcln utility to a specific Agent. The specified number of days that is sent to this Agent is determined by the value assigned to Maximum Days to Retain Output Files parameter.

5019 STATISTICS INFORMATION CLEANUP STARTED.

The New Day procedure or the ctmruninf utility starts 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}

Active Jobs starts/ends downloading to Control-M.

Control-M processes are suspended during Active Jobs download.

5034 STATISTICS INFORMATION CLEANUP ENDED. MODE= purgeMode. LEAVE= purgeLimit

The New Day procedure or the ctmruninf utility successfully performs 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 finishes successfully.

5035 STATISTICS INFORMATION CLEANUP FAILED

Control-M/Server fails to perform a partial cleanup of Control-M job statistics.

Execution of the ctmruninf utility stops.

5040 NEW DAY PROCEDURE STARTED

The New Day procedure is submitted.

While this procedure executes all other Control-M processes are suspended.

5041 ACTIVE JOBS FILE CLEANUP ENDED

The New Day procedure finishes cleaning up Active Jobs. This message is sent at the end of the New Day procedure after Active Jobs cleans the old jobs and loads new job orders.

Control-M processing returns to Run status and inserts new jobs into the Active Jobs until the download to Control-M/EM starts.

5043 QUANTITATIVE RESOURCE INTEGRITY ERROR. resourceName n1 n2

Due to an internal accounting problem, there is a discrepancy between the specified quantitative resource (resourceName) actual usage count (n1) 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

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

Due to an internal accounting problem, the specified control resource (resourceName) appears to be used in Exclusive mode by more than one job.

5047 ALLOW SUBMISSION FOR PARAMETER EXCEEDED

During the New Day procedure, this job deletes from Active Jobs because it exceeds the amount of days allowed in Active Jobs, according to the Allow submission for (MAXWAIT) job definition value. Details about the Allow Submission for parameter can be found in Keep Active for.

5048 NEW DAY PROCEDURE TIME HAS ARRIVED

The New Day procedure should run at this time.

Active Jobs download stops, so that the New Day procedure can begin.

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

The last run date of the specified User Daily job (userDaily) cannot be retrieved from the database. When a new User Daily job runs for the first time, the last run date is nonexistent and cannot be accessed. At the end each run, a new last run date is automatically generated.

5061 USER DAILY userDaily STARTED

The specified User Daily job (userDaily) starts.

5062 USER DAILY userDaily ENDED

According to the scheduling criteria, the specified User Daily job (userDaily) finishes ordering the associated jobs.

5063 CALENDAR calName, NOT FOUND OR NOT COMPLETE

You attempt 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 does not download.

5064 USER DAILY userDaily STOPPED - DATE PROBLEM. LAST lastDate, NEXT nextDate

The specified User Daily job (userDaily) cannot run due to a date inconsistency.

The inconsistent date may be due to one of the following reasons:

• The User Daily job has already 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.

5065 ORDERED %s: jobNumber; DAILY userDaily, ODATE odate

Where %s is one of the following values:

• JOB

• Sub folder

• SMART folder

The specified job (jobNumber) with an order_date of order_date is entered into the Active Jobs by the specified User Daily job (userDaily).

5066 DAILY userDaily FAILED TO ORDER JOBNAME jobName

he specified User Daily job (userDaily) fails to order the requested job (jobName).

The failure to order jobs may be due to the following:

• Database problem (such as a communication problem or space problem)

• Data inconsistency in the database

• Security violation

• Scheduling criteria of the job, which does not match the ordering date

The system action depends on the cause of the problem:

• If it is a security violation for a specific job, or a mismatch in scheduling criteria, Control-M continues to check/order the jobs that relate to this User Daily job.

• If it is a database problem or an internal problem, the User Daily job might stop ordering the rest of the jobs.

5067 ONE OR MORE JOBS IN DAILY userDaily WERE NOT ORDERED

At least one or more jobs within the specified User Daily job (userDaily) are not ordered as the scheduling criteria does not match the specified ordering date. For more information, see the NOT_ORDERED_ JOB_ALERT configuration parameter in Configuration parameters.

5069 JOB %s WILL NOT BE ORDERED DURING UPCOMING SYSTEM DAILY - %s

During the PRE ORDERING activity, 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 (such as communication problem or space problem)

• Data inconsistency in the database

• Security violation

• Scheduling criteria of the job does 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, 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.

5070 ONE OR MORE JOBS WILL NOT BE ORDERED DURING UPCOMING SYSTEM DAILY

During the PRE ORDERING activity, at least one or more jobs within the specified User Daily job (userDaily) were not ordered because its scheduling criteria does not match the specified ordering date. For more information, see the NOT_ORDERED_ JOB_ALERT configuration parameter in Configuration parameters.

5080 FAILED TO SUBMIT JOB FileName. reason

The requested job FileName cannot be submitted for one of the following reasons:

UNIX:

• Path Does Not Exist: The path or library cannot be found.

• Mem Name memName Does Not Exist: The script cannot be found.

• User userName Does Not Exist: There is a security violation.

• Run_As User % Does Not Exist: There is a security violation.

• Run_As User % Is Not Allowed To Execute This Script: There is a security violation.

• The Script scriptName Does Not Have Execute Permissions: There is a security violation.

Windows:

• There are currently no log in servers available to service the login request.

• Log In Failure: Unknown username or bad password.

• Log In Failure: User account restriction.

• Log In Failure: Account login time restriction violation.

• Log In Failure: User not allowed to log on to this host.

• Log In 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.

• Log In Failure: The user has not been granted the requested login type at this host.

• A specified log in session does not exist. It may have been terminated.

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.

5100 ENDED AT time. OSCOMPSTAT rc. RUNCNT runCounter

The job ends its execution at the specified time (time) with the given return code (rc) and the given run count of the job (runCounter).

5101 STARTED AT startRun ON hostID

The job begins executing at the specified time (startRun) on the specified Agent platform (HostID).

5102 DISAPPEARED AT time. RUNCNT runCounter

After the job is submitted, it cannot be located by the system and the job's status changes to Disappeared at the specified time (time). The job's status and the location of the 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.

5105 SUBMITTED TO hostID

The job submits for execution to the specified Agent platform (HostID).

5106 DISAPPEARED AT dateTime. RUNCNT count. node name IS status

The user changes the status of the host to Disabled or the job is in an unknown state for more than UNKNOWN_TIMEOUT seconds. The Control-M/Server changes the state of the job submitted for that host to Disappeared and the status to Ended Not OK.

The variables in this message are:

• dateTime - the date and time that the job disappeared

• count - the job's run count

• host - one of the following:

• AGENT

• REMOTE HOST

• Agent used by the Agentless Host

• ACCOUNT

• name - the name of the Agent, Agentless Host, agent used by the Agentless Host, agent used by the Agentless Host, or CM Account name

• status - one of the following:

• DISABLED

• UNAVAILABLE

5110 LIBMEMSYM FILE pathName NOT FOUND

The file specified in a %%LIBMEMSYM variable (pathName) is not found. %%LIBMEMSYM may be used to refer to a list of variable assignments contained in a file in the data center. The file referred to in this instance is not found.

5120 %s STATE CHANGED TO %s

Control-M changes 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 folder

• SMART folder

5132 STATUS SET TO jobStatus AS A RESULT OF DO {OK | NOTOK | RERUN}

The job completion status (jobStatus) changes as a result of End Job Ok, End Job Not Ok, or Rerun job post-processing actions.

5133 ENDED OK

The job completes with status OK. Following job execution and post-processing, Control-M analyzes the results and assigns the completion status OK to the job.

5134 ENDED NOTOK

The job terminates with a final status of NOTOK.

Following job execution and post-processing, Control-M analyzes the results and assigns a final status of NOTOK to the job, indicating that a problem occurs during job processing.

5136 JOB STATE CHANGED TO RETRY - SUBMIT

Control-M attempts to submit the job to the Agent platform, but the submission failed due to the Agent not responding. The job's state changes to Retry and the job is resubmitted.

Control-M attempts to submit the job.

5141 EMAIL TO %s FAILED

Control-M/Server fails to send the email to the recipient email address that is resolved by the %s variable.

The recipient email address is incorrect or the mail server cannot send the email for a different reason.

5164 DUMMY. STATUS CHANGED TO OK

The job assigns a status of Ended OK because it is a dummy job.

5166 INVALID TIME ZONE timeZone. STATUS CHANGED TO FAILED TO SUBMIT

The Time Zone parameter (timeZone) has an invalid value. Valid time zone values are listed in the timezone.dat file.

The job status changes from Failed to Submit.

5169 Message from Agent: <message>

Control-M/Server receives this message from Agent (version 7.0.00 or higher), when the job ends NOTOK or disappeared.

5199 CONDITION 'condName' 'condDate' ALREADY EXISTS

The job tries 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.

5201 SHOUT TO destination PERFORMED

A Shout message was issued to the specified destination (destination).

5202 SHOUT TO destination FAILED

An attempt to issue a Shout message to the specified destination (destination) is not successful because it is possible that either the terminal is not connected or an invalid destination is specified.

The Shout message is not issued.

5203 Control RESOURCE resourceName RESERVED

The control resource defined for this critical job (resourceName) is not available yet as it may be used by another job. 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}

The control resource resourceName allocates the specified job in Shared (S) or Exclusive (E) mode.

5206 Control RESOURCES RELEASED

All control resources allocated for the job order are released because the job terminates.

The control resource is now available for other jobs in the system.

5207 QUANTITATIVE RESOURCE resourceName QUANTITY resourceQuantity RESERVED

Quantitative resource resourceName reserves in quantity resourceQuantity for the specified critical job and is ready to be allocated. The job waits until all the resource quantities are available for its run and is executed.

5208 QUANTITATIVE RESOURCE resourceName QUANTITY resourceQuantity ALLOCATED

Quantity resourceQuantity of quantity resource resourceName has been allocated for this job.

5209 CONDITION condName condDate ADDED

Following job termination, the specified prerequisite condition (condName), with the matching date reference (condDate) adds to the Control-M/Server database. This condition is now available for other jobs in the system.

5210 CONDITION condName condDate DELETED

Following job termination, the specified prerequisite condition (condName), with the matching date reference (condDate) deletes from the Control-M/Server database.

5211 %s JOB FAILURE. JOB %s, FOLDER %s

An operation to order or force the %s' job in the %s' folder fails.

• The failure may be due to the following:

• Problems with the job processing definition (such as job not found)

• Security verification problems

• Scheduling criteria of the job not matching

The job is not ordered or forced.

5212 JOB %s, FOLDER %s %s

The job %s in the folder %s is FORCED or ORDERED into Active Jobs.

The job is inserted into Active Jobs.

5214 QUANTITATIVE RESOURCES RELEASED

All allocated quantitative resources for the specified job are released.

The control resource is now available for other jobs in the system.

5215 ALL RERUNS HAVE BEEN PERFORMED. MAXRERUN = number

All the reruns have been performed and the job exceeded the number value of the maxrerun parameter. When the job's completion status sets 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.

The job will not continue to rerun, and will move to a post-processed state.

5217 folder '%s', job name '%s' not found

One of the following occurs:

• A Control-M/EM user attempts to force a job using the menu option in the Control-M/EM window

• A Control-M job attempts to execute an Order Job statement as part of its post-processing parameters.

The attempt to run job %s located in folder %s failed. Either the folder specified in folder %s does not exist in the Control-M/Server database, or the job specified in job %s does not exist in the specified folder %s.

%s can have one of the following values: Job, Sub folder or SMART folder

5219 CYCLIC ATTRIBUTE REMOVED DUE TO DOSTOPCYCLIC

Cyclic jobs usually run at regular intervals for as long as specified when the scheduling criteria is satisfied.

A cyclic job terminates due to a related On Statement/Code criteria that satisfies and performs a Do Stop Cyclic action, which prevents future operations of the current cyclic job.

5220 STATUS OF AGENT PLATFORM HostID CHANGED TO AVAILABLE

Control-M changes the communication status of the Agent platform identified by hostID from Unavailable to Available. The communication status of the Agent platform changes from Available to Unavailable due to failed communication. As a result of resumed communication, the status of the Agent platform returns to Available.

Control-M resumes sending job handling requests to the Agent platform.

5222 STATUS OF AGENT PLATFORM nodeID CHANGED TO UNAVAILABLE

ne of the following occurs:

• Control-M changes the communication status of the Agent platform identified by hostID from Available to Unavailable due to many communication timeouts. A communication failure occurs between the Server platform and the specified Agent platform.

• HostID is not specified correctly in the job processing definition or in the host 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 returns to Available. Otherwise, the status of the platform changes to Disabled.

5223 STATUS OF AGENT PLATFORM hostID CHANGED TO DISABLED

The communication status of the Agent platform identified by hostID changes to Disabled.

Control-M no longer attempts to communicate with the Agent platform and does not send job handling requests to the platform.

5225 STATUS OF ACCOUNT <Account_name>, APPLTYPE <Application_type>, AGENT <agent_name> CHANGED TO [AVAILABLE|DISABLED|UNAVAILABLE. Message from Agent follows]

The status of the account changes to Available, Disabled, or Unavailable. If the status changes to Unavailable, message 5226 follows this message.

5226 <message_id>: <message>

This message indicates why the status of an account is unavailable. This message follows message 5225 or 4914.

5228 SHOUT TO <shout to program logical name> STILL RUNNING. [JOB|SMART table|Sub table] PROCESSING CONTINUES.

The <shout to program logical name> has being running for 20 seconds, and the Control-M/Server continues to process the JOB|SMART folder|Sub folder now without waiting for the shout to complete.

5231 CYCLIC ATTRIBUTE OF THIS JOB CHANGED DUE TO STATUS=NOTOK

A run of the cyclic job or SMART folder ends NOTOK. As the CYCLIC_RERUN parameter is set to NOTOK, the job or SMART folder cyclic attribute changes and the job or SMART folder does not rerun. The Control-M/Server default behavior reruns a cyclic job or SMART folder when the job run ends NOTOK. The CYCLIC_RERUN parameter in the Control-M/Server configuration determines whether a cyclic job or SMART folder should rerun if that job or SMART folder ends NOTOK. The job or SMART folder state changes to post-processed and does not rerun.

5232 Warning: Cyclic job getting close to maximum allowed runs.

Control-M/Server verifies that the job or SMART folder recount has not crossed the default hard limit, which is 99900. A warning issues when the hard limit reaches 90%.

5233 Error: cyclic job run too many times and will not run any more

When the job or SMART folder rerun count reaches the hard limit, the job or SMART folder stops. The default hard limit value is set at 99900.

5250 ACCESS TO FOLDER %s IS NOT ALLOWED TO USER %s

A User Daily job, using the ctmudly utility, attempts to order a job from a folder %s, which is unauthorized by the specified user %s. This is a security violation message.

Accessing the folder is denied to the User Daily job.

5251 THIS RUN_AS USER IS NOT AUTHORIZED TO EXECUTE THE JOB SCRIPT

The Run As User job processing definition is not authorized to execute the script file specified by the job processing parameters.

The job terminates with a NOTOK status.

5252 USER %s NOT AUTHORIZED FOR RUN_AS USER %s

The user %s tries to perform an action on a job that is owned by the Run As User, but in the Control-M/Server security definition, this user is not authorized to perform this action for this user.

The action fails.

5301 SERVER INTERNAL ERROR TYPE type

An internal error occurs on the Control-M/Server during a request for the EM user to upload/delete a folder/calendar.

The user request is rejected.

5302 INCOMPATIBLE GATEWAY VER. DATA CENTER VER. CTMServerVersion. W.S. VER. gatewayVersion

There is incompatibility between the Control-M/Server version (CTMServerVersion) and the Control-M version (gatewayVersion), where the Gateway is defined.

During the SYNC operation between Control-M/EM Gateway and Control-M/Server, the Control-M/Server checks that the Gateway version is compatible. To communicate between Control-M/EM Gateway and Control-M/Server, the Control-M version, which is defined in Control-M/EM, should match the Control-M/Server version where the Gateway tries to connect.

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

5304 CANNOT {DELETE | FREE} <%s> orderNumber - <%s> NOT HELD

A delete or free action is requested for this job orderNumber, but as 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 folder or SMART folder

5305 ACTIVE JOBS FILE IS LOCKED, TRY AGAIN LATER

An attempt to perform an action such as Why/View statistics, view JCL/Edit JCL, and View Doc, on Active Jobs failed due to the fact that currently it is locked by another user or by the Control-M Monitor.

The user request is rejected.

5306 CANNOT action JOB orderNumber - JOB DOES NOT EXIST

The specified job (orderNumber) does not exist or could not be found in the Control-M/Server database and the requested action (action) cannot be performed.

The user request is rejected.

5309 CANNOT HOLD <%s> orderNumber - <%s> ALREADY HELD

A Hold request performs 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 folder or SMART folder

5310 JOB orderNumber IS NOT WAITING FOR CONFIRMATION

A confirmation request performs the requested job (orderNumber), but the job does not have Wait Confirmation status. A confirmation request is only valid for jobs that are in Wait Confirmation status.

The confirmation request is rejected.

5311 ERROR PROCESSING XML REQUEST. xmlMessage

The request cannot be processed due to xmlMessage.

The Control-M/Server encounters a problem while receiving or reading XML data from Control-M/EM to Control-M/Control Module.

The request is rejected.

5312 GATEWAY OLDER THAN 613 CANNOT CONNECT TO DATA CENTER 613 OR ABOVE

The Gateway version is not compatible with the Control-M/Server version.

This Gateway version tries to connect to a Control-M/Server version 6.1.03, but this Gateway version is an earlier version and the connection fails. Control-M/Server 6.1.03 can connect only to Control-M/EM 6.1.03 or higher.

Communication between Control-M/Server and Control-M/EM cannot be established.

5315 QUANTITATIVE RESOURCE resourceName IN USE - CANNOT DELETE

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 uses a certain quantity of the quantitative resource and the resource cannot be deleted.

The Delete request is rejected.

5316 QUANTITATIVE RESOURCE resourceName ALREADY EXISTS

An attempt was made to add quantitative resource resourceName, but this quantitative resource exists in the Control-M/Server database.

The Add request is rejected.

5317 QUANTITATIVE RESOURCE resourceName DOES NOT EXIST

A Control-M/EM user submits a request to delete, update, or allocate quantitative resource, but this quantitative resource does not exist in the Control-M/Server database.

It is possible that between the time the request is sent from the Control-M/EM Control Application to the time it is 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.

5318 VALUE OF CHANGE IS OUT OF RANGE

A Control-M/EM user submits a request to update a quantitative resource quantity but the result of the update operation is either negative or more than the total value.

The update request is rejected.

5319 OUTPUT DOES NOT EXIST FOR THIS JOB

A Control-M/EM user submits a request to a view of a job's output, but the specific output does not exist and cannot be viewed.

The output has not been generated or the existing output has been deleted (manually or automatically) after exceeding the number of days specified in the Maximum Days to Retain Output Files Control-M/Server parameter.

The requested is rejected.

5321 STATISTICS DO NOT EXIST FOR THIS FILE/MEMBER

A Control-M/EM user submits a request to view a job's statistics, but Control-M/Server failed to retrieve the statistical data of the job from the database.

The requested is rejected.

5323 SECURITY PROTECTION VIOLATION

A Control-M/EM user performs an unauthorized request action.

The Control-M/Server security mechanism issues this message. The request may be rejected for one or more of the following reasons:

• The 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 Control-M security. The user request is rejected.

5327 CANNOT POSTPROCESS JOB. JOB HELD BY SYSTEM

The post-processing action of this job cannot be performed and Control-M/Server changes the status of the 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 job's post-processing is not performed and the job status changes to HOLD by the Control-M/Server.

A message that the job is HELD is send to the job log.

5328 JOB orderNumber IS NOT IN EXECUTION STATE

Control-M/EM tries to perform a kill action on the orderNumber job, but the action fails because the job is not in executing mode. A kill action terminates a current run job together with its processes. This action terminates only jobs that are currently executing.

The user request is rejected.

5330 AGENT hostID/group IS UNAVAILABLE. REQUEST action FAILED

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 attempts to use one of the following options for the job:

• View Output

• View Documentation

• View JCL/Script

• Edit JCL/Script

Control-M/Server is unable to pass the request to the Agent platform because of a failed communication or the status of the Agent platform is Unavailable or Disabled.

The user request is not executed.

5351 QUANTITATIVE RESOURCE resourceName QUANTITY resourceQuantity DEFINED

A Control-M/EM user adds 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

A Control-M/EM user deletes the resourceName quantitative resource.

This quantitative resource removes from the Control-M/Server resources database.

5353 QUANTITATIVE RESOURCE resourceName QUANTITY INCREASED BY resourceQuantity

The maximum quantity of the resourceName quantitative resource increases by quantity resourceQuantity due to a Control-M/EM user request.

The new quantity value of this resource updates in the Control-M/Server resources database.

5354 QUANTITATIVE RESOURCE resourceName QUANTITY DECREASED BY resourceQuantity

The maximum quantity of the resourceName quantitative resource decreases by quantity resourceQuantity due to a Control-M/EM user request.

The new quantity value of this resource updates in the Control-M/Server resources database.

5355 QUANTITATIVE RESOURCE resourceName QUANTITY resourceQuantity RELEASED

The number of units (resourceQuantity) of the resourceName quantitative resource that allocate to a job are released and available for other jobs that require this resource.

The new quantity value of this resource is updated in the Control-M/Server resources database.

5358 FILE NOT FOUND

A Control-M/EM user submits a request to view or edit JCL or view doc, but the file (document or script file) does not exist.

The request is rejected.

5359 DIRECTORY NOT FOUND

A Control-M/EM user submits a request to view or edit a JCL script or to view a document, but the directory, which contains the requested file (document or script file) does not exist.

The request is rejected.

5360 SECURITY VIOLATION

The Control-M/Server security mechanism issues this message when a Control-M/EM user tries to submit an unauthorized request action.

• The request may be rejected for one or more of the following reasons:

• The Control-M/EM user does not have a user account on the Control-M/Server platform

• The Control-M/EM user does not have the required authority from the operating system on the Control-M platform to perform the requested function

• The 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 Control-M security

The request is rejected.

5361 THE SELECTED JOB/SMART FOLDER CANNOT BE DELETED DUE TO ITS CURRENT STATE.

A Control-M/EM user tries 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.

The request is rejected.

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

Due to a user request, the maximum quantity of the resourceName Quantitative resource decreases or increases by specified quantity (resourceQuantity).

The maximum number of units of resourceName Quantitative resource decreases or increases to maxQuantity.

5363 QR:'resourceName', QRTOTAL: maxQuantity defined

The user defines a new Quantitative resource called 'resourceName', and sets the maximum availability for this resource to maxQuantity.

The resource adds to the Control-M resources database.

5364 QR:'resourceName' deleted

Due to a user request, the resourceName Quantitative resource removes from the Control-M resources database.

The resource deletes from the Control-M resources database.

5366 <bypass_option> is rejected. <reason>

A Control-M/EM user tries to set/unset bypass <bypass_option> to a job.

5367 ACCOUNT<Account_name>, APPLTYPE <Application_type>, AGENT <agent_name> IS UNAVAILABLE REQUEST <request_name> FAILED The user request is not executed.

A user request to view/edit DOC/JCL is not executed because the status of the Account is Unavailable or Disabled.

5401 HELD BY USER userName

A specified user (userName) submits a Hold request and the job is now in Hold state.

The system performs one of the following actions:

• If the job is not executing, it is prevented from doing so even after the submission criteria is satisfied. The job remains in this state until it is released using the Free option.

• Any job that executes when a hold request is performed, remains in Executing status until freed.

• Once the job finishes executing, it cannot manually rerun, until it is released by means of the Free option.

5402 FREED BY USER userName

The job associated with the message releases 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

The job associated with the message was marked as deleted by the specified user (userName).

The system performs one of the following actions:

• If the job is not executing, it is prevented from doing so even after the submission criteria is satisfied. The job remains visible until the cleanup of Active Jobs has completed either during the New Day procedure or when cleanup is manually requested.

• If the job finishes executing, it cannot manually rerun after it is deleted.

5404 RERUN BY USER userName

The job associated with the message is rerun by the specified user (userName).

The system reruns the job.

5405 CONFIRMED BY USER userName

The job associated with the message, which waits for confirmation prior to submission, is confirmed by the specified user (userName).

The system checks the job submission criteria and handles the job.

5407 CREATED BY USER userName

The job associated with the message is placed in Active Jobs by the ctmcreate utility.

The job adds to the Active Jobs and is handled according to its submission criteria.

5408 UNDELETED BY USER userName

The job associated with the message is undeleted from its Delete state by the userName user.

The Undelete option causes the job to revert to its original state before the job was deleted.

5409 JOB KILLED BY USER userName

The userName user submits the Kill option on the job that is associated with this message. The Kill option terminates a current running job (and its processes).

The job and its process are terminated, and the job's status changes to NOTOK.

5410 JOB SET TO OK

The status of the job that is associated with this message is set to OK.

The job status was changed to OK.

5411 SET TO OK REQUEST SUBMITTED BY USER userName

The status of the job that is associated with this message is set to OK by the specified user (userName).

The job status was changed to OK.

5412 Bypass <bypass_option>set ON|OFF by user <Control-M/EM user name>

User <Control-M/EM username> successfully set bypass <bypass_option> of a job to [ON|OFF].

5413 ALL BYPASS OPTIONS ARE RESET TO OFF

All bypass options are automatically set by Control-M/Server to OFF.

5500 SERVICE NOT ALLOWED NOW - reason

A user request is sent from Control-M/EM to Control-M/Server to update this job's details (zoom and save actions), but this update action cannot be performed temporarily due to the fact that the job is in reason state.

The user request is rejected.

5506 OPERATION NOT SUPPORTED BY AGENT orderNumber

A Control-M/EM user performs a Kill request, but the request is rejected because the version of Control-M/Agent (where the job is submitted) does not Support the Kill option.

The user request is rejected.

5507 AGENT ENCOUNTERED ERROR { orderNumber| Write to File Failed }

A Control-M/EM user submits a Kill, View JCL/Script, or Edit JCL/script request for a job, but the request is rejected because there is a problem with the Agent where the job is submitted.

The problem can be an internal problem (while trying to transfer the request) or the Agent is unavailable.

The user request is rejected.

5508 MAXIMUM CONCURRENT SESSIONS LIMITATION REACHED

Control-M/Server reaches the maximum concurrent persistent sessions limitation with Agents.

There is either a new request from Control-M/Server to an Agent or a new request from an Agent to Control-M/Server that generated a new persistent connection session.

5520 Perform rollback in function: functionName

The Control-M/Server database fails to perform a request within the database and rollback occurs.

Rollback rolls back the current transaction and removes the updates made by the discarded transaction.

Rollback cancels the proposed changes in a pending database transaction.

5522 ERROR: RESOLVED VALUE FOR paramName IS LONGER THAN number CHARACTERS

The Control-M/Server is unable to resolve variables for the paramName parameter, since the calculated value is longer than the permitted number (number) of characters.

The request fails.

5524 START OF TRACKING ALL ACTIVE JOBS

The TR process (Tracker) starts 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 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}

The ctmjsa utility starts 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 in the database.

5700 Folder folderName, Jobname jobName

The jobName job was ordered and inserted into the Active Jobs file from folderName Folder.

The job has been inserted into Active Jobs.

5701 %s %s' ordered, file_name = %s', orderno= %s

The job %s and file_name %s are ordered and inserted into Active Jobs with % order number. This message is generated when Control-M successfully orders a job.

The job is inserted into Active Jobs.

5702 FileName not ordered

An order request is submitted for the file_name job, but Control-M/Server does not order the job (for example, due to scheduling criteria).

5703 FOLDER %s DOES NOT EXIST

An attempt is made to order or force a folder, but the folder %s is not defined in the Control-M/Server database. A possible cause is that the folder was created in Control-EM, but not uploaded to the Control-M/Server database.

The request is not performed.

5704 WARNING: CALENDAR or Rule-based calendar <CalendarName or Rule-based Calendar> UP TO DATE. REQUEST REJECTED

A Control-M/EM user attempts to submit an upload to the calName calendar, but changes are not made in the calendar definition since the last time it was uploaded to the Control-M/Server. 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 [FOLDER|CALENDAR|Rule-Based Calendar] [folderName|CalendarName|RuleBasedCalendarName] PREVIOUSLY MODIFIED BY Control-M. REQUEST REJECTED

An attempt is made to update a folder, Calendar or a rule-based calendar, but the folderName, CalendarName, RuleBasedCalendarName has already changed in the Control-M/Server database. A possible cause is that the folder, Calendar or rule-based calendar was created in Control-M/EM, but was later changed in Control-M/Server database.

The request is not performed.

5706 Sub folder SubFolderName not ordered (Reason)

An operation to order or force the SubFolderNameSub folder failed.

The failure may be due to the following:

• Problems with the sub-folder processing definition (such as sub-folder not found, error in the sub-folder scheduling criteria)

• Database problem (such as a communication problem or space problem)

• Scheduling criteria of the sub-folder, which does not match the ordering date

The sub-folder is not ordered or forced.

5707 DOVARIABLE '%s'='%s' performed

The DO variable action of the active job was performed.

The name variable is assigned the value value.

5708 order operation rolled back. Waiting for the end of New Day..

The server is suspended due to the New Day procedure or Download, while a job, sub-folder or folder is being ordered.

5710 %s: No matching Sub Folder definitions found for folder path %s

A request is made to order, force or view the scheduling plan of a job in sub-folder %s, but the specified job or sub-folder does not exist.

The request was not performed.

5711 SMART folder 'SmartFolderName' not ordered (Reason)

An order request is submitted for the SmartFolderName SMART folder, but Control-M/Server does not order the SMART folder.

• The failure may be due to the following:

• Problems with the SMART folder processing definition (such as SMART folder not found, error in the SMART folder's schedule parameters)

• Database problem (such as a communication problem or space problem)

• Scheduling criteria of the SMART folder, which does not match the ordering date

The SMART folder is not ordered or forced.

5720 INTO-FOLDER-ORD request is ignored for the regular job %s

You try to order or force a regular (defined within a regular folder) job into an existing SMART folder.

The job is not ordered.

5722 WARNING: FOLDER %s IS LOCKED. REQUEST REJECTED

Control-M/EM sends an Upload request after the folder %s was ordered by a User Daily job. This folder is locked and cannot be uploaded until the ctmuldy utility finishes ordering this folder.

The upload request is rejected.

5723 WARNING: FOLDER %s UP TO DATE. REQUEST REJECTED

A Control-M/EM user attempts to upload the folder %s, but changes have not been made in the folder definition since the last time it was uploaded to the Control-M/Server. The folder is up to date and there is no need to upload it to the Control-M/Server.

The upload request is rejected.

5740 User '%s' not allowed to order from folder '%s'

The user %s tries to order a job from the folder %s, but this user is not authorized to order this folder.

No jobs are ordered from the specified folder.

5741 User %s' not allowed to FORCE for Run_As user %s'

The specified user %s' tries to force a job whose owner is Run_As user %s', but is not authorized to do so.

The job is not forced.

5742 User %s' not allowed to ORDER for Run_As user %s'

The specified user %s' tries to order a job for Run_As user %s, but is not authorized to do so.

The job is not ordered.

5743 Security check failed

An unauthorized action is requested.

The requested action does not perform.

5744 Row number rowNumber does not match the requested job jobName. Can't force into a new Group.

A job sequence number (rowNumber) is specified when trying to force a job, but no job in the folder has this number.

The job is not forced.

5745 Folder '%s' job name '%s' not found

A request is made to order or force a job, but the specified job or folder does not exist.

The request does not perform.

5746 The SMART Folder, Sub-folder, SMART Folder job, or Sub-folder job failed to be ordered

Only jobs or sub-folders in new SMART folders are ordered without using the FORCE option. Jobs must be forced into existing SMART folders or sub-folders when using ALONE mode or LAST mode. sub-folders must be forced into existing SMART folders or sub-folders using LAST mode.

The job in the SMART folder or sub-folder is not ordered.

5747 The ordered SMART or Sub folder does not exist. %s

The job does not belong to either the LAST or the specified order number % SMART folder or sub-folder.

Control-M/Server processing continues.

5748 Job No %d does not belong to the SMART folder with orderno %d

The job %d does not belong to the SMART folder associated with the %d order ID.

The job is not ordered or forced.

5749 The SMART Folder l Sub folder already includes an instance of the job

A job included in a SMART folder/sub-folder cannot be added to the SMART folder/sub-folder.

The job is not forced.

5750 No RBC was found or all the SMART folder's RBC failed

No schedule rule based calendar (RBC) is found in the SMART folder, or no RBC's satisfy the scheduling criteria. When ordering a SMART folder, at least one of its RBC must satisfy all scheduling criteria.

The SMART folder is not ordered.

5751 Error in job's schedule parameters

The Control-M/Server is unable 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 sub application is not ordered.

5753 Error copying jobdef to AJF

An error occurs while trying to order a job and insert its definition into Active Jobs.

The job is not ordered.

5754 CONDITION condName WITH ORDER DATE condDate DOES NOT EXIST

A Control-M/EM user tries 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.

5755 CONDITION condName WITH ORDER DATE condDate ALREADY EXISTS

A Control-M/EM user tries 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.

5756 INVALID DATE FOR CONDITION condName condDate

An invalid order date (condDate) is detected while trying to add, delete, or change prerequisite conditions from Control-M/EM.

The requested action does not perform.

5757 ORDER FORCE FAILED DATE= orderDate

An invalid order date is detected when ordering or forcing a job from Control-M/EM.

The order or force request is rejected.

5758 FOLDER %s IS NOT UP TO DATE

An attempt was made to order, force, or delete the folder %s. However, the content of the folder in Control-M/EM and the content of the folder with the same name in the Control-M/Server database are different.

The requested action is not performed.

5759 Jobname jobName not ordered. Invalid Time Zone.

The jobName job ordering request cannot be fulfilled, due to an invalid value of the time zone definition of this job.

For more details about time zone values, see Time Zone and Job Ordering see: Job definition.

The order request does not perform.

5760 SYNC REQUEST TIMEDOUT

Communication between Control-M/EM and Control-M/Server fails.

The first stage of communication between Control-M/EM and Control-M/Server is a SYNC request for both sides and 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.

5761 SESSION CLOSED BY CO

The session between Control-M/EM and Control-M/Server closes due to the CO process.

The session between Control-M/EM and Control-M/Server may close due to a communication problem or a problem sending or receiving data between Control-M/EM and Control-M/Server. The connection between Control-M/EM and Control-M/Server closes.

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

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 fails, which may be due to a database problem.

The condName prerequisite condition does not add to or delete from the Control-M/Server database.

5763 FAILED TO DELETE CONDITION: condName DATEREF: condDate

An attempt to delete the condName prerequisite condition with a condDate date reference from the Control-M/Server database fails. Possible reasons for this failure are:

• There is no 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, but delete fails due to a database problem

The specified prerequisite condition with the specified date reference does not delete from the Control-M/Server database.

5764 Failed to perform DOFORCE. folder: %s, job: %s

Control-M/Server sends this message to Control-M/EM when there are insufficient privileges to perform an ordered job.

5765 Sub folder %s job cannot be ordered

The job in the sub-folder fails to be ordered.

Control-M/Server processing continues.

5766 Cannot order when wait for ODate is set

Cannot order when wait for ODate is set, but ODate occurs in the past.

5775 Initialize Sub folder %s job numbers retrieval failed

During handling of sub-folder ordering, retrieval of sub-folder job numbers initialization fails.

Control-M/Server processing continues.

5776 Retrieve next job details of Sub folder %s failed

The next job details of the sub-folder cannot be retrieved.

Control-M/Server processing continues.

5777 < functionName>: Failed to retrieve definition of job number < jobNumber>

Fails to retrieve job details of the given job number.

Control-M/Server processing continues.

5778 Force Sub folder %s alone is not permitted

Force sub-folder alone is not permitted.

Control-M/Server processing continues.

5801 Failed to delete records from folder FolderName with ORDERNO OrderNumber.

A user request is sent from Control-M/EM to Control-M/Server to update this job's details (zoom and save actions), but this update action cannot be performed.

The user request is rejected.

5803 Update folder FolderName FAILED.

You attempt to create an active job or SMART folder using Control-M/EM API, but the Control-M/Server fails to update this job in the database. This is likely to be a database problem.

The job or SMART folder is not created.

5807 SUBAPPLICATION and FOLDER should be the same for SMART folder entity.

The user attempts to create an active SMART folder using Control-M/EM API. The user specifies a different name for the sub application and for the folder parameters of the SMART folder.

The SMART FOLDER is not created.

5808 SUBAPPLICATION and FOLDER should be specified.

You attempt to create an active job using Control-M/EM API. You did not specify a value for the folder parameter of the job.

The job is not created.

5809 SMART FOLDER %s does not exist in the database.

Using Control-M/EM API, the user attempts to create an active job with the folder ID into an existing SMART folder in Active Jobs. The folder ID was not found in Control-M/Server Active Jobs.

The job is not created.

5810 FILE_PATH, CMDLINE, FILE_NAME and OVERRIDE PATH should not be specified.

You attempt to create an active SMART folder using Control-M/EM API. You specify one or more of the following parameters for the job sub-application:

• FILE_PATH

• CMDLINE

• FILE_NAME

• OVERRIDE PATH

The job sub-application is not created.

5811 FAILED to allocate isn.

You attempt to create an active job or job sub application using Control-M/EM API, but the Control-M/Server fails to allocate an order ID for this job. This is likely to be a database problem.

The job or job sub application does not create.

5812 No hosts found in HOSTGRP %s

Using the Control-M/EM API, you attempt to create an active job with the multiagent parameter set to Yes, but no Host ID was found in the job's HostGroupName HostGroup. Possible reasons for this are:

• The HostGroupName HostGroup is not defined in the Control-M/Server database, or no HostID is defined in this HostGroup

• There is a database problem

The job does not create.

5814 FAILED to setup the application type for HOSTGRP %s.

You attempt to create an active job using the Control-M/EM API, but the Control-M/Server fails to set the job's application type. Possible reasons for this are:

• The application type for the job's %s HostGroup in the Control-M/Server is different than the application type that the user has specified in the API

• There is a database problem.

The job does not create.

5815 Invalid ODATE date.

You attempt to create an active job or a job sub application using the Control-M/EM API but you specify an invalid date for the ODATE job parameter.

The job or job sub application does not create.

5816 OUTPUT FILE EXCEEDED LIMIT SIZE (CAN BE VIEWED FROM FILE SYSTEM)

The size of the Output file exceeds the limit (in KB) as defined by the OUTPUT_LIMIT_SIZE parameter.

The View Output action is rejected.

5817 Illegal specified folder path FolderName.

You attempt to create an active job sub-folder using the Control-M/EM API but you specified an invalid sub-folder name.

The sub-folder is not created.

5821 SMART folder name FolderName contains illegal character /

You attempt to create an active job SMART folder using the Control-M/EM API but you the FolderName that you specified contains the illegal character '/'.

The SMART folder is not created.

5830 Pre new day ordering for (SMART folder) entity (jobno)

Indicates that SMART folder/Sub folder/JOB and its nested entities (if it exists) was prepared during the PRE ORDER activity, and the PRE ORDER management table in the database (CMR_PRE_ORDER) was updated.

This message only indicates that the job was during PRE ORDER activity. It does not indicate that the job is ordered during the upcoming new day (whether the job is ordered or not).

5831 Pre new day ordered (SMART folder\Sub folder\JOB):jobno ; ODATE (odate)

Indicates that SMART folder/Sub folder/JOB was prepared during the PRE ORDER activity and orders during the upcoming new day.

5832 Pre new day ordering reset due to %s

Mark PRE ORDER as "RESET". It is Done as a result of an event that makes previous PRE ORDER obsolete. In this case PRE ORDER activity starts from the beginning, unless it is too close to new day (new day performs the ordering). Events that cause PRE ORDER “RESET” include the following:

• Workload change

• Calendar change

• Global RBC change

• New day time change

5902 Job: jobNumber USER EXIT102 failed. task type= taskType

The Job Submission Exit (CTMUE102) fails in relation to the jobNumber job with taskType tasktype. Possible reasons for this failure are:

• Control-M/Server fails 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 fails to create or write to the flat text file or fails to allocate required memory, the user exit script does not execute. 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 Active Jobs.

5903 User Daily SYSTEM USER EXIT103 failed. old_odat= date

The Before New Day Procedure Exit (CTMUE103) fails in relation to the User Daily SYSTEM job because the Control-M/Server fails to create, write to, read from, or delete the flat text file, which passes to the user exit script (date is the Control-M/Server date before the New Day procedure).

If Control-M/Server fails to create or write to the flat text file, the user exit script does not execute. Otherwise, the user exit executes. In any event, the New Day procedure runs.

5904 User Daily SYSTEM: USER EXIT CTMUE104 failed. old_odat= date

The After New Day Procedure Exit (CTMUE104) fails in relation to the User Daily SYSTEM job because the Control-M/Server does not create, write to, read from, or delete the flat text file, which passes to the user exit script (date is the Control-M/Server date after the New Day procedure).

If the Control-M/Server fails to create or write to the flat text file, the user exit script does not execute. Otherwise, the user exit executes and in any event, the New Day procedure completes.

5905 User Daily userDailyName: USER EXIT CTMUE105 failed. old_odat= date

The Before User Daily Exit (CTMUE105) fails in relation to the userDailyName User Daily job because the Control-M/Server fails to create, write to, read from, or delete the flat text file, which passes to the user exit script (date is the current Control-M/Server date).

If the Control-M/Server fails to create or write to the flat text file, the user exit script does not execute. Otherwise, the user exit is executed and in any event, the procedure of ordering the User Daily job continues.

5906 User Daily userDailyName: USER EXIT CTMUE106 failed. old_odat= date

The After User Daily Exit (CTMUE106) fails in relation to the userDailyName User Daily job because the Control-M/Server fails to create, write to, read from, or delete the flat text file, which is passed to the user exit script (date is the current Control-M/Server date).

If the Control-M/Server fails to create or write to the flat text file, the user exit script does not execute. Otherwise, the user exit is executed and in any event, the procedure of ordering the User Daily job completes.

5922 Illegal host type Host Type encountered for host HostName

The host HostName for a specific job, has an invalid Host Type.

The specific job is not submitted.

5935 BMC recommends that you enable archiving on your database.

Control-M/Server has detected that database archiving is not enabled, which is essential for restore from backup process (hot restore only).

5936 BMC recommends that you periodically perform hot backup to your database.

Control-M/Server has detected hot backup has not been done for its database. Hot backup does not require any down time and it ensures database recovery in case of system failure.

5937 Hot backup has not been done for over %d days.

Control-M/Server has detected that hot backup has not been done for its database for several days. It is important to perform hot backup every week to ensure DB recovery in case of system failure.

5950 Forced from Control-M %s

An informative message indicating an ordered job from a remote Control-M server.

5951 Forced by ordereid %s run-no %s

An informative message indicating an ordered job from a remote Control-M server.

6000 functionName: Stored Procedure failed (procName)

The executed stored procedure returns 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.

6002 User name does not have environment definition for varDescription (varName)

The specified environment variable does not exist.

You cannot start Control-M/Server or activate the Control-M/Server utility.

6003 functionName: Failed to update database statistics. rc= rc

Database statistics update fails.

Database statistics update fails and Control-M/Server processing continues. This may affect data fetch performance from the database.

6004 functionName: Failed to create cache table for process parameters

A cache table in relation to process parameters cannot create due to insufficient memory.

Control-M/Server fails to allocate memory for cache table parameters.

6005 functionName: Failed to create cache table record for process parameters

A cache table record in relation to process parameters cannot create due to insufficient memory.

Control-M/Server fails to allocate memory for cache table record parameters.

6006 functionName: Failed to create a duplicate cache table record for process parameters

A duplicate cache table record in relation to process parameters cannot be created due to insufficient memory.

Control-M/Server fails to allocate memory for a copy of cache table record parameters.

6007 functionName: Failed to create cache table for variable names

A cache table in relation to variable names cannot create because of insufficient memory.

Variables do not calculate correctly, which may occur in more than one flow. If this happens during job submission, the job does not submit. For more information, refer to Control-M/Server logs.

6008 functionName: Failed to create cache table for variable values

A cache table in relation to variable values cannot create because of insufficient memory.

Variables do not calculate correctly, which may occur in more than one flow. If this happens during job submission, the job does not submit. For more information, refer to Control-M/Server logs.

6009 functionName: Failed to expand cache table for variables for order number orderNumber. Variable Name varName, Variable Expression varExpression

A cache table in relation to variables with a specified order number, variable name, and variable expression cannot expand due to insufficient memory.

Variables do not calculate correctly, which may occur in more than one flow. If this happens during job submission, the job does not submit. For more information, refer to Control-M/Server logs.

6010 functionName: Failed to expand cache table for group and local variables

A cache folder in relation to sub application and local variables cannot expand due to insufficient memory.

Variables do not calculate correctly, which may occur in more than one flow. If this happens during job submission, the job does not submit. For more information, refer to Control-M/Server logs.

6011 functionName: Failed to retrieve global variables from the database

Global variables cannot be retrieved from the database.

Variables do not calculate correctly, which may occur in more than one flow. If this happens during job submission, the job does not submit. For more information, refer to Control-M/Server logs.

6012 functionName: Failed to retrieve {Job | Group} variables from the database for {Job | Group} order number orderNum

The specified variable with a specific order number cannot be retrieved from the database.

Variables do not calculate correctly, which may occur in more than one flow. If this happens during job submission, the job does not submit. For more information, refer to Control-M/Server logs.

6013 functionName: Failed to determine variable name level (job, group or global)

The variable %s level (job, sub application, or global) cannot be determined.

The specified variable does not calculate.

6014 functionName: Failed to delete global variable name

The specified global variable cannot delete.

The specified variable does not delete.

6015 functionName: Failed to delete global variable number

The specified variable cannot delete.

The specified variable does not delete.

6016 functionName: Illegal scheduling plan found in job name name job number number odate date

An illegal scheduling plan is found for the specified job.

The specified job is not ordered.

6017 functionName: Group order number number does not exist. Group name can not be ordered into the specified order number

The specified sub application order number does not exist. The attempt to order the specified sub application into this existing sub application fails.

The specified sub application is not ordered.

6018 functionName: Group entity name was not ordered successfully

The specified group cannot be ordered.

The specified group is not ordered.

6019 functionName: Failed to delete in condition(s) of job(s) in group name

When a sub application scope is defined and ordered, IN conditions for jobs within a sub application (which do not exist or are not added by other jobs) delete. Deletion of the IN conditions fail.

The sub application and its jobs order, but some or all of its jobs are in WAIT condition status.

6020 functionName: Attempt to order daily jobName while upload procedure is active

An attempt is made to order the specified daily job while an upload procedure is active.

The daily job is ordered.

6021 functionName: Failed to read group defName definition. Job jobName is not ordered

An attempt to read the specified sub application definition fails. This occurs while attempting to order a job into existing sub application.

The specified job does not order.

6022 functionName: Message received from Control-M/EM is not first in sequence

Control-M/Server receives 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

An illegal operation on the specified condition is received from the specified user. The operation should be performed on the specified condition name.

The specified request does not perform.

6024 functionName: Illegal response responseID received from Control-M/EM for scheduling folder folderName download operation

An illegal response is received from Control-M/EM in relation to specified folder download operation.

The specified folder does not download.

6025 functionName: Illegal response responseID received from Control-M/EM for host group groupName download operation

An illegal response is received from Control-M/EM for the specified host group download operation.

The specified host group does not download.

6026 functionName: Illegal response responseID received from Control-M/EM for calendar calName download operation

An illegal response is received from Control-M/EM for the specified calendar download operation.

The specified calendar does not download.

6027 functionName: Failed to handle partitioned folder folderName. Returned status is rc

During Control-M/Server startup, partitioned folders prepare for further usage.

Control-M/Server fails to start.

6028 functionName: Terminating process procName, process number procNumber

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

he process state of the Control-M/Server supervisor does not update. Possible states are:

• Running

• Suspended

• Terminated

6030 functionName: Failed to create alert file fileName during handling alert alertName

The specified alert file does not create 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

The lock acquired on the alert file while handling the specified alert does not release.

The specified alert is not handled.

6032 functionName: Failed to copy alert file fileName1 to fileName2

When the connection with Control-M/EM is down, alerts are saved in an alert file. When the connection with Control-M/EM returns, Control-M/Server reads this file and handles all the alerts contained therein. When the handling any of these alerts fails, the alert file copies to a backup file. The backup of this file fails.

6033 functionName: Failed to open alert file fileName, file name fileName return code rc

When the connection with Control-M/EM is down, alerts are saved in an alert file. When the connection with Control-M/EM returns, Control-M/Server reads this file and handles all the alerts contained therein. Reading the specified alert file fails.

6034 functionName: Failed to release lock lockID after handling alerts file

When the connection with Control-M/EM is down, alerts are saved in an alert file. When the connection with Control-M/EM returns, Control-M/Server reads this file and handles all the alerts contained therein. When writing to the alert file, the file is locked. When the alerts are handled, the lock releases. Releasing the lock fails.

Alerts are handled.

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

An OS object (a semaphore lock) does not release. This is a severe problem which may occur in more than one flow in Control_M/Server.

The system may become unstable.

6036 functionName: Failed to initialize process threads environment. Return status rc

The process threads environment does not initialize.

The process or utility does not start.

6037 functionName: Failed to initialize thread environment. Return status rc

The thread environment does not initialize.

The process or utility does not start.

6038 functionName: Failed to initialize thread database connection. Return status rc

The thread database connection does not initialize.

The process or utility does not start.

6039 functionName: Error occurred while thread termination. Return status rc

An error occurs when a thread terminates.

6040 functionName: Failed to reset Remote Host agent list for Remote Host hostName

Control-M/Server fails to reset the Agentless Host agent list for the hostName Agentless Host.

The hostName Agentless Host is not available. Normal Control-M/Server processing continues.

6041 functionName: Failed to extract Remote Host agent list for Remote Host hostName

Control-M/Server fails to extract the Agentless Host agent list in relation to the hostName Remote Host.

The hostName Agentless Host is not available.

6042 functionName: Failed to open file fileName for writing

Control-M/Server is unable to open the fileName file for writing.

The fileName file does not open.

6043 functionName: Failed to append Remote host agent name to the remote host agent names list of remote host hostName

Control-M/Server is unable to append an Agentless Host agent name to the Agentless Host agent names list of the hostName Agentless Host.

The hostName Agentless Host will not be handled correctly.

6044 functionName: Failed to clear remote host agent names list of remote host hostName

Control-M/Server cannot clear the Agentless Host agent names list of the hostName Agentless Host.

The hostName Agentless Host does not be handled correctly.

6044 functionName: Failed to clear remote host agent names list of remote host hostName

Control-M/Server cannot clear the Agentless Host agent names list of the hostName Agentless Host.

The hostName Agentless Host does not be handled correctly.

6045 functionName: Failed to retrieve data from folder folderName explanation

Control-M/Server cannot retrieve data from the folderName folder.

6046 functionName: { SSH | WMI } details not found for remote host hostName

Control-M/Server cannot find SSH or WMI Agentless Host definition parameter details for the hostName Agentless Host.

6047 functionName: Failed to get host name of machine on which Control-M/Server is running.

An attempt is made to get the host name of the machine (where Control-M/Server runs), but the attempt fails.

6048 functionName: Failed to fetch next remote host agent name from remote host agent names list of remote host hostName

An attempt is made to fetch the next Agentless Host name from the Agentless Host agent names list of the hostName host, but the attempt fails.

6049 functionName: Failed to clear availability remote host agent names list of remote host hostName

An attempt is made to clear the availability Agentless Host agent names list of the hostName host, but the attempt fails.

The hostName Agentless Host does not handle correctly.

6050 Failed to update remote host hostName status

Control-M/Server fails to update the status of the hostName Agentless Host.

The status of the hostName Agentless Host does not handle correctly.

6051 Failed to update status details of remote host hostName

Control-M/Server fails to update the status details of the hostName Agentless Host.

The status details of the hostName Agentless Host are not handled correctly.

6052 Failed to read agent agentName status while handling remote host hostName

Control-M/Server fails to read the status of the agentName agent, while handling the hostName Agentless Host.

The status of the hostName Agentless Host does not handle correctly.

6053 functionName: Agent agentName status file not found while handling remote host hostName

Control-M/Server cannot find the status file for the agentName agent while handling the hostName Agentless Host.

The Agentless Host status does not handle correctly.

6057 functionName: Failed to delete agent name agentName from agent names list of remote host hostName

Control-M/Server fails to delete the agentName agent from the agent names list of the hostName Agentless Host.

The hostName Agentless Host status does not handle correctly.

6058 functionName: Host hostID status file not found.

Control-M/Server fails to find the status file of the hostID host.

The requested operation on the hostID host is not handled.

6059 functionName: Failed to read host hostID status file. Read status status.

An error occurs while Control-M/Server attempts to read the status file of the hostID host.

The requested operation on the hostID host cannot be handled.

6060 functionName: Failed to delete agent agentName from the database.

An attempt to delete the agentName agent from the agent table in the database fails.

The agentName agent does not delete.

6061 functionName: Failed to initialize select on table CMS_RJX_NAMES while handling agent deletion agentName.

An attempt to initialize selection of the CMS_RJX_NAMES table while handling the agentName agent fails.

The agentName agent does not delete.

6062 functionName: Failed to add a host with hostID to remote hosts list while handling agent agentName deletion.

Control-M/Server fails to add a host to the Agentless Hosts list while handling the agentName agent deletion.

The agentName agent does not delete.

6063 functionName: Failed to update agent agentName details used by remote host hostName while handling agent agentName deletion.

6063 functionName: Failed to update agent agentName details used by Agentless Host hostName while handling agent agentName deletion.

6064 functionName: Failed to extract remote host name from remote host names list while handling agent agentName deletion.

Control-M/Server fails to extract the next Agentless Host while handling the agentName agent deletion.

The agentName agent does not deleted.

6065 functionName: Failed to extract parameters from trigger message messageText while handling agent deletion.

Control-M/Server fails to extract parameters while handling deletion of an agent.

6066 functionName: Illegal agent type received messageText while handling agent deletion.

Control-M/Server receives an illegal agent type while handling deletion of an agent.

6067 functionName: Failed to duplicate list listInfo listOrigin

Control-M/Server fails to duplicate a list.

6068 Delete local agent is prohibited.

An attempt is made to delete a local agent from Control-M/Server.

6069 Update remote hosts using agent agentName failed.

When normal agent status changes, all Agentless Hosts using this agent are updated. An attempt to update Agentless Hosts fails while handling the status of the agentName agent.

6070 Update remote hosts using agent agentName completed partially.

When normal agent status changes, all Agentless Hosts using this agent are updated. An attempt to update Agentless Hosts does not succeed for the Agentless Hosts while handling the status of the agentName agent.

6071 Add a new record to TR host list while handle host hostID failed.

The tracker process attempts to add a new entry in its hosts list. The hostID host is used by the tracker process to track jobs that are submitted to the host. An attempt to add the hostID host fails.

6072 Add a new record to TR host-job list while handle host hostID and order number orderNumber failed.

The tracker process attempts to add a new entry in its hosts list. The hostID host is used by the tracker process to track jobs that are submitted to the host. An attempt to add the hostID host 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.

An attempt to determine the difference between the memory agent Agentless Host list and Agentless Host status file agents list fails.

6074 Remote host hostName agents list file contains illegal line.

An illegal line is found in the hostName Agentless Host agents list status file.

The status of the Agentless Host does not handle correctly.

6075 Add job with order number orderNumber details to host hostID order number list failed.

An attempt is made to add the orderNumber order number job details to the hostID host 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 host hostID order number list. rc= rc.

An attempt is made to clean the hostID order number list, but the attempt fails.

6077 functionName: Remote host hostName map details not found

The hostName Agentless 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:

6078 functionName: Failed to get remote host hostName map details.

The hostName Agentless Host map cannot be obtained from the Control-M/Server database. This error may occur while handling job submissions, killing ordered 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.

6079 functionName: Illegal node status received status with trigger triggerName.

The status illegal node status occurs 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.

The type illegal node type occurs while handling data for the triggerName trigger.

The action specified by the trigger is not handled.

6081 Failed to load fileName file explanation.

An attempt is made to load the fileName file, but the attempt fails.

Default configuration parameters, as 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.

Control-M/Server requests an Agentless Host to perform a shoutType shout, but only mail shouts are permitted.

6083 functionName: Failed to get available agent for remote host hostName.

An attempt is made to obtain an available agent for the hostName Agentless Host, but the attempt fails.

The requested operation fails.

6084 Illegal node type type received while handle job with orderno orderNumber runcount count.

An illegal node type (type) is received while handling a job with the orderNumber order number and the count run count.

Job tracking fails.

6101 Utility aborted - User not authorized to execute the utility!

The utility may not be executed by a user other than the Control-M/Server Administrator, and aborts.

The utility aborts.

6102 Timeout waiting for LG process to change state to Running

This utility is suspended while the Control-M/Server state is Suspended and resumes running when it notices that the Control-M/Server state is Running. The utility waits for it to resume Running state, but the timeout limit is exceeded.

The utility aborts. If ordering performs, it continues with the ordering attempts of the rest of the jobs.

6103 Selector did not get out of suspension

The ordering utility is executed. This utility is suspended while the Control-M/Server state is Suspended and resumes running when it notices that the Control-M/Server state is Running. The utility waits for it to resume Running state, but the timeout limit is exceeded.

The utility aborts.

6104 Update user information in security table userName description userGroup nodeID

The ctmsec utility, which executes in a non-interactive mode, updates existing user information in the security definitions tables. The new information for this user is specified in the userName, description, userGroup, and HostID parameters.

The database table updates with the new information.

6105 Insert user information into security table userName description userGroup nodeID

The ctmsec utility, which executes in a non-interactive mode, tries to update user information in the security definitions tables. Since the user is not found, a new user is defined. The new user information is specified in the userName, description, userGroup, and hostID parameters.

The database table does not update with the new information.

6106 Update group information in security table groupName description - group- nodeID

The ctmsec utility, which executes in a non-interactive mode, updates existing group information in the security definitions tables. The new information of this group is specified in the groupName, description, group, and HostID parameters.

The database table updates with the new information.

6107 Insert group information into security table groupName description - group- nodeID

The ctmsec utility, which executes in a non-interactive mode, tries to update group information in the security definitions tables. Since the group is not found, a new group is defined. The new group information is specified in the groupName, description, group, and HostID parameters.

The database table updates with the new information.

6108 Failed to receive confirmation of successful message receiving

The utility performs an action, but the confirmation of a successful message reception fails. There is a possibility that the action performed by the utility may not complete.

The utility ends. There is a chance that it did not complete all its actions successfully.

6109 Failed in database operation while trying to find dependent jobs. Return Code = rc

You try to list job dependencies with the ctmpsm utility, but the utility fails in the database operation.

The list is empty.

6112 Unable to initialize

A process cannot initialize due to a system problem or lack of resources.

The process aborts with a failure exit status.

6114 Failed to get ControlM_USER from the environment

A utility fails to log into the primary database because it cannot obtain the ControlM_USER parameter from the environment.

A utility fails to log in to the database. The utility aborts with an error.

6116 Failed to get ControlM environment variable

A utility fails to log into the database because it cannot obtain the ControlM parameter from the environment.

A utility fails to log into the database and it aborts with an error.

6117 Failed to create temporary file fileName for writing. Error Number= errorNumber, Error Message= errorString

A utility fails to log into the database because it cannot create a temporary file (fileName).

A utility fails to log into the database. The utility aborts with an error.

6118 Failed to create temporary (fp) file fileName for writing

A utility fails to log into the database because it cannot create a temporary file (fileName).

A utility fails to log into the database. The utility aborts with an error.

6119 Failed to open file filename for reading

A utility fails to log into the database because it cannot not open a temporary file (fileName).

A utility fails to log into the database. The utility aborts with an error.

6120 Failed to get CTM_DATABASE_TYPE from the environment

A utility fails to log into the database because it cannot obtain the CTM_DATABASE_TYPE parameter from the environment.

A utility fails to log into the database. The utility aborts with an error.

6121 UnSupported database DBType

A utility fails to log into the database because the DBType value is incorrect.

A utility fails to login to the database. The utility aborts with an error.

6122 Failed to get envirVariable from the environment

A utility fails to log into the database because it cannot obtain the specified envirVariable from the environment.

A utility fails to log into the database. The utility aborts with an error.

6123 Cannot open directory directoryName

A utility fails to open the specified directory (directoryName). The files under this directory cannot be accessed.

The ctmsuspend utility failed and did not change the processes state.

6124 Cannot shutdown Control-M/Server...

The shut_ctm utility fails to shut down the Control-M/Server processes.

The ctmsuspend utility fails and cannot perform the required action.

6125 Restarting server...

Control-M/Server processes are about to restart.

The ctmsuspend utility executes the start_ctm utility.

6126 Cannot restart Control-M/Server...

Control-M/Server processes cannot restart.

The start_ctm utility fails. The Control-M/Server does not restart because the ctmsuspend utility failed to perform the required action.

6127 Failed to run ctmshout utility

The ctmshout utility fails to execute.

The message that indicates whether the operation of the ctmsuspend utility is successful does not insert into the IOALOG table. The ctmsuspend utility may fail to perform the required action.

6128 Failed to create database objects

Database tables and other database objects, such as indices and stored procedures, are not created successfully.

The ctmcreateschema utility fails and the Control-M/Server database is not created.

6129 Failed to insert initial values into database tables

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

The ctmcreateschema utility fails and the Control-M/Server database is not created.

6130 Failed to create database partitions tables

The CMR_IOALOG and CMR_JOBINF database partition tables do not create successfully.

The ctmcreateschema utility fails, and the Control-M/Server database are not created.

6131 Failed to update system and communication parameters in database tables

The Control-M/Server system and communication parameters do not store successfully in the database tables. Control-M/Server cannot start without those parameters.

The ctmcreateschema utility fails and the Control-M/Server database is not created.

6132 Failed to reset several Control-M/Server configuration parameters

The reset_t1 utility fails.

The ctmcreateschema utility fails and the Control-M/Server database is not created.

6133 functionName: Failed to retrieve output from the agent for orderno runcount output size. rc = rc

A utility fails to retrieve output from the Agent.

The utility aborts with a Failed exit status.

6134 functionName: Failed parsing fileName

A utility fails during an XML parsing.

The utility aborts with a Failed exit status.

6135 Invalid tagName request in xmlFile

A utility fails during an XML parsing while dumping into invalid tagName.

The utility aborts with a Failed exit status.

6136 functionName: Failed to retrieve element list for nodeName in the fileName

A utility fails while reading an element list for the nodeName node from the fileName XML file.

The utility aborts with a Failed exit status.

6137 Invalid calendarType

A utility fails while reading an invalid calendar type from an XML file.

The utility aborts with a Failed exit status.

6138 functionName: Invalid attributeName of attributeType.

A utility fails while reading an invalid attributeType attribute from an XML file.

The utility aborts with a Failed exit status.

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

The ctmpsm utility fails to insert a new calendar into the database.

The utility aborts with a Failed exit status.

6140 functionName: Failed to insert calendar calendarName, calendarYear into the database.

A utility fails to insert a new calendar into the database.

The utility aborts with a failed exit status.

6141 functionName: Failed to retrieve parent node of nodeName in the fileName

A utility fails while reading the parent node of the nodeName node from the fileName XML file.

The utility aborts with a failed exit status.

6142 functionName: CalendarName with year was imported successfully.

The ctm_psm utility is invoked and successfully imports the calendarName calendar.

The ctm_psm utility continues processing.

6143 functionName: Failed to convert arguments to UTF8.

6153 functionName: A conflict has occurred between the imported information specified in nodeGroup and applType and the information currently existing in the database.

The imported information specified in applType and hostGroup conflicts with the information that exists in the database.

The utility aborts with an error.

6154 functionName: Failed on input XML file initialization process. Message: messageDetails

The input XML file initialization process fails.

The utility aborts with an error.

6155 Error was found during XML file parsing. Error Type: errorType, File Name: fileName, Line: lineNum, Column: columnNum, Message: messageDetails

An error is found during XML file parsing.

The utility aborts with an error.

6157 Import tableName has successfully written to the database.

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 folder folderName into the database

The utility fails to insert the folderName folder into the database.

The utility aborts with an error.

6159 functionName: Request permission denied. Scheduling folder: folderName, Action: permissionType. Skip importing this folder.

The user does not have the specified permission type on the specified component to perform the request.

The ctmimptb continues processing the XML file.

6160 Scheduling folder folderName already exists in the database and overwrite was not specified. Skip importing this folder.

The ctmimptb utility does not import the folderName folder because the folder currently exists in the database, and overwrite is not specified.

The ctmimptb utility continues processing the XML file to import the next folder.

6161 functionName: Failed during XML file parsing. Message: messageDetails

The utility fails on XML file parsing.

The utility aborts with an error.

6162 functionName: Failed to delete scheduling folder folderName from the database

The utility fails to delete the folderName folder from the database.

The utility aborts with an error.

6163 functionName: Failed to delete jobs related to scheduling folder folderName from the database

The utility fails to delete jobs relating to the folderName folder from the database.

The utility aborts with an error.

6164 functionName: Failed to delete checksum of scheduling folder folderName from the database

The utility fails to delete the checksum of the folderName folder from the database.

The utility aborts with an error.

6165 functionName: Failed to insert tag tagName of scheduling group groupName into the database

The utility fails to insert the groupName sub application tag into the database.

The utility aborts with an error.

6166 functionName: Failed to insert dates of scheduling group tag into the database. Tag: tagName, Scheduling group: folderName, Date: Date.

The utility fails to insert date details of the tagName sub application into the database.

The utility aborts with an error.

6167 functionName: Failed to insert Job jobName for scheduling folder tableName into the database.

The utility fails to insert the jobName job into the database.

The utility aborts with an error.

6168 functionName: Failed to insert jobProcessingDefinitions for Job jobName for scheduling folder folderName into the database.

The utility fails to insert job processing definitions of jobName job for FolderName into the database.

The utility aborts with an error.

6169 functionName: Failed on processing componentType componentName - JOB is not defined.

The ctmimptb utility fails on processing the specified component due to undefined related job.

The ctmimptb utility aborts with an error.

6170 functionName: Failed on processing jobName - Scheduling Folder is not defined.

The ctmimptb utility fails processing the specified job that relates to the folder, which imports from a previous transaction.

The ctmimptb utility aborts with an error.

6171 functionName: scheduling folder folderName already exists in the database and overwrite was specified. Overwriting this folder.

The specified folder currently exists in the database and the ctmimptb utility is about to overwrite it because overwrite mode was specified.

The ctmimptb imports the specified folder.

6172 Import failed. Job definition folder folderName partially imported.

The ctmimptb utility fails and the folderName folder is partially imported into the database.

The ctmimptb utility aborts with an error.

6174 Import finished successfully.

All the job definition tables from the XML file import into the database successfully.

The ctmimptb utility finishes successfully.

6176 Import failed. No table was imported into the database.

The ctmimptb utility fails and a job definition table does not import into the database.

The utility aborts with an error.

6177 Import failed. Not all the job definition tables were imported.

The ctmimptb utility performs a partial import. Those job definition tables that are imported, are fully imported into the database.

The utility aborts with an error.

6178 Starting import of job definition tables from file: fullPathFileName Overwrite mode: mode

The ctmimptb utility starts to process the XML file to import the job definition tables.

The ctmimptb utility starts parsing the XML file for the import process.

6179 End of import of job definition tables.

The ctmimptb utility finishes processing the XML file to import the job definition tables.

The ctmimptb utility finishes 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

The specified function is unable to generate a message list for the requested message type. The request aborts, which the message generation attempts for Agent hostID.

Control-M/Server attempts to create a messageType message.

6201 functionName fail to initialize messageType header message to agent nodeID, request will be aborted

The specified function is unable to generate a header message from the messageType type. The request aborts for the attempted message generation of Agent hostID.

Control-M/Server attempts to create a messageType message.

6202 functionName fail to append messageType header message to agent nodeID, request will be aborted

The specified function is unable to append a header message from the messageType type. The request for which the message generation is attempted for Agent hostID is aborted.

Control-M/Server attempts to create a messageType message.

6203 functionName fail to create messageType message to agent nodeID, request will be aborted

The specified function is unable to generate a message from the messageType type. The request for which the message generation is attempted for Agent hostID is aborted.

Control-M/Server attempts to create a messageType message.

6204 functionName received from agent a corrupt message <<<< message>>>>

The specified function attempts to handle a message from the Agent, but it is corrupted.

Control-M/Server attempts to handle a request from the Agent.

6205 functionName fail to create temporary status file: fileName

The specified function attempts to create temporary status file for a job.

Control-M/Server attempts to create a new status file.

6206 functionName fail to write temporary status file: fileName

The specified function attempts to write a temporary status file for a job.

Control-M/Server attempts to write data to a status file.

6207 functionName fail to close temporary status file: fileName

The specified function attempts to close a job's temporary status file.

Control-M/Server attempts to close a status file.

6208 functionName fail to rename temporary status file: fileName1 to status file: fileName2

The specified function attempts to rename a job's temporary status file.

Control-M/Server attempts to rename a status file.

6209 functionName fail to make a message list from a message buffer, request will be aborted

The specified function is unable to make a message list from message buffer. The request for which the message list generation is attempted is aborted.

Control-M/Server attempts to create a message list from a message buffer.

6210 functionName fail to get header message, request will be aborted

The specified function is unable to locate a header message, and the request is aborted.

Control-M/Server attempts to fetch a header message from a message list.

6211 functionName unSupported request code (requestCode) received from agent nodeID

The specified function receives a request with an unSupported request code from Agent hostID.

Control-M/Server attempts to generate a request code sent by an Agent.

6212 functionName received termination request by user

The specified function receives a request to terminate from the shut_ctm utility.

Control-M/Server attempts to handle a request.

6213 functionName unSupported request code (requestCode) received from one of the server processes

The specified function receives a request with an unSupported request code from one of the server processes.

Control-M/Server attempts to generate a service from a request code sent by one of the Server processes.

6214 functionName null logical TCP session pointer, current service is aborted

The specified function tries to send a message to an Agent using a corrupted TCP session with this Agent, but the service aborts.

Control-M/Server attempts to send a message to an Agent.

6215 functionName failed to create a new physical protocol communication channel

The specified function fails to create a new communication channel of type protocol, and the request aborts.

Control-M/Server attempts to create a new communication channel.

6216 functionName communication error INET protocol type (protocol) is not Supported

The specified function fails to create a new communication channel of an unSupported protocol, and the request aborts.

Control-M/Server attempts to create a new communication channel.

6217 functionName communication error protocol mode (protocol) is not Supported

The specified function fails to create a new communication channel of an unSupported protocol, and the request aborts.

Control-M/Server attempts to create a new communication channel.

6218 functionName failed to create a new logical protocol communication channel

The specified function fails to create a new logical communication channel of type protocol, and the request aborts.

Control-M/Server attempts to create a new logical communication channel.

6219 functionName failed to up-class a physical communication channel to a physical protocol communication channel

The specified function has a corrupt physical communication channel, and the request is aborts.

Control-M/Server attempts to connect to a physical communication channel.

6220 functionName failed to connect to client (nodeID) at port (portNumber)

The specified function fails to connect to Agent hostID at TCP/IP port portNumber, and therefore the request is aborts.

Control-M/Server attempts to connect to a communication channel.

6221 functionName failed to disconnect session of logical TCP communication channel (channel) of physical session id (sessionID)

The specified function fails to disconnect a logical TCP communication channel (channel) with an Agent identified by sessionID. The operation attempts to continue.

Control-M/Server attempts to close a communication channel.

6222 functionName connected client name (nodeID) is already connected

The specified function receives a request to choose a persistent connection for disconnection when the maximum number of concurrent sessions are reached, but finds that the requested Agent for connection has already connected.

Control-M/Server attempts to choose a persistent session for disconnection when maximum concurrent sessions are already reached.

6223 functionName fail to get parameter agent parameter value for client name (nodeID) using default

The specified function fails to retrieve an Agent parameter value and tries to continue using the default value.

Control-M/Server attempts to check an Agent parameter value.

6224 Connected persistent sessions:

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_OUTPUT 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

Control-M/Server produces a printout of the status and statistics of the current connected persistent sessions.

6225 Disconnected persistent sessions:

Total concurrent sessions: sessions out of maxSsessions

Disconnected Agent: hostID

Duration: durationNum seconds

Control-M/Server produces a printout of the current disconnected persistent sessions.

6226 functionName failed to create a new disconnected session for client name (nodeID)

The specified function fails to create a new disconnected session when maximum concurrent sessions are reached.

Control-M/Server chooses a persistent session for disconnection when maximum concurrent sessions are reached.

6227 functionName failed to send alerts on event

The specified function fails to send alerts to Control-M/EM, the system console, and the IOALOG when the specified event occurs.

Control-M/Server attempts to send alerts to Control-M/EM, the system console, and the IOALOG.

6228 functionName operation (opCode) is not Supported

The specified function fails to register an event associated with an unSupported opCode operation, and the request aborts.

Control-M/Server attempts to register a callback event.

6229 functionName failed on SSL client operation server operation with physical session id (sessionID) sid= code

The specified function fails to complete an SSL operation with an Agent that is identified by sessionID and the request aborts.

Control-M/Server attempts to generate an SSL communication with an Agent.

6230 functionName failed to set SSL session option (option) with physical session id (sessionID)

The specified function fails to complete an SSL connection with an Agent that is identified by sessionID and the request aborts.

Control-M/Server attempts to generate an SSL communication with an Agent.

6231 functionName failed on SSL server operation client operation with physical session id (sessionID) sid= code

The specified function fails to complete an SSL operation with an Agent that is identified by sessionID and the request aborts.

Control-M/Server attempts to generate an SSL communication with an Agent.

6232 functionName process processName will terminate after receiving SIGTERM signal

The specified function receives a kill request for process processName.

Control-M/Server issues a kill process shell command.

6233 functionName got an invalid SSL profileType profile pointer while SSL protocol is enabled.

The specified function obtains a corrupted SSL profile for profileType and the process is aborts.

Control-M/Server attempts to initialize an SSL client or server profile.

6234 functionName got a negative value for PORTNUM entry in AGDEFS table

The specified function obtains an invalid value for a TCP/IP port number and the process is aborts.

Control-M/Server attempts to initialize the default agent port number.

6235 NS initialization failed process will be aborted

NS is unable to initialize due to various environmental issues and the process aborts.

Control-M/Server attempts to initialize the NS process.

6236 NS service manager failed to start default services, process will be aborted

NS fails to create a listener for Agent's request or Server process requests, and the process aborts.

Control-M/Server attempts to initialize the NS process.

6237 NS agent availability failed to start, process will be aborted

NS fails to start the Agent availability service and the process aborts.

Control-M/Server attempts to initialize the NS process.

6238 functionName failed to open INET listen channel for HOST: host on PORT: port

The specified function fails to open a new TCP/IP listener for Agent requests for host on TCP/IP port and the process is aborts.

Control-M/Server attempts to initialize the NS process.

6239 functionName failed to open CTMS listen channel for NAME: IPCCode

The specified function fails to open a new Inter Process Communication listener for the Server process requests and the process aborts.

Control-M/Server attempts to initialize the NS process.

6240 functionName failed to up-class an abstract channel to a communication channel (pointer)

The specified function has a corrupt communication channel and the request is aborts.

Control-M/Server attempts to open a new communication listener.

6243 functionName failed to delete host group hostGroup information from table databaseTable, code= rc

The deletion of the host group from the database fails.

The Control-M Configuration Manager displays an error message.

6244 functionName failed to insert host group hostGroup into table databaseTable, code= rc

The insertion of the host group to the database fails.

The Control-M Configuration Manager displays an error message.

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

A message from Control-M/Server to an Agent includes invalid data.

Control-M/Server frees the allocated memory for the message.

6301 functionName : Control-M Server to Control-M Agent message pointer is not initialized

A message from Control-M/Server to an Agent includes invalid data.

Control-M/Server frees the allocated memory for the message.

6302 functionName : Control-M Server to Control-M Agent Message buffer is not initialized

A message from Control-M/Server to an Agent includes invalid data.

Control-M/Server frees the allocated memory for the message.

6303 functionName : Control-M Server to Control-M Agent Messages list is not initialized

A message from Control-M/Server to an Agent includes invalid data.

Control-M/Server frees the allocated memory for the message.

6304 functionName : The value of 'CPU used' sent by the Control-M Agent is negative : CPU_used

The value of CPU_used that the Agent sends to Control-M/Server is negative.

Control-M/Server sets the value for CPU usage to 0.

6305 functionName : The value of 'elapse time' sent by the Control-M Agent is negative: time

The value of time that the Agent sends to Control-M/Server is negative.

Control-M/Server sets the value for elapsed time to 0.

6306 functionName : Control-M Server to Control-M Agent message type not found. Message type : messageType.

The message type sent from or to Control-M/Server is not found.

6307 functionName : Control-M Server to Control-M Agent message is empty

The message type sent by Control-M/Server or received by Control-M/Server is invalid.

Control-M/Server frees the allocated memory for the message.

6308 functionName : Gateway older than 613 cannot connect data center 613 or above

You are trying to connect a Gateway version 6.1.0 or lower to Control-M/Server version 6.1.3 or higher.

Control-M/Server refuses to connect to Control-M/EM.

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

The Control-M/Server receives an unknown service ID from Control-M/EM.

One of the following occurs:

• If Control-M/Server tries to connect to Control-M/EM, the server refuses to connect to Control-M/EM.

• If the Control-M/Server handles a user request, the user request is rejected.

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

The database transaction cannot commit.

In this message, valid values for rc are CM_FAIL or CM_EOF.

6311 functionName : Database fail to open a new transaction

The database cannot open a new transaction.

6312 functionName : Failed to clean statistic information. Return code = rc

Control-M/Server cannot 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

The database transaction cannot roll back.

In this message, the only valid value for rc is CM_FAIL.

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

Control-M/Server cannot clean the CNR_JOBINF table during the New Day procedure.

In this message, the only valid value for rc is CM_FAIL.

Control-M/Server sends an alert.

6315 functionName : Ignore Conditions file exceeded maxEntries entries

6316 functionName Failed to delete condition : condName, condDate

Control-M/Server cannot 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

Control-M/Server cannot allocate memory for AGSTAT information.

Control-M/Server writes an error message to the IOA log file.

6318 functionName Fail to open AGSTAT file

Control-M/Server cannot open the AGSTAT file.

Outputs are not cleaned during the New Day procedure.

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

Control-M/Server cannot send a New Day cleanup message to one of the Agents.

In this message, valid values for rc are:

The following occurs:

• Outputs are not cleaned during the New Day procedure for the specified Agent.

• Control-M/Server writes a message to the IOA log file.

6320 functionName Fail to fetch next record from AGSTAT table. Return code = rc

Control-M/Server cannot fetch the next record from the AGSTAT table for an Agent.

In this message, the only valid value for rc is CM_FAIL.

Outputs are not cleaned during the New Day procedure for this Agent.

6321 functionName Failed to translate local date and time information given specific Time Zone

Control-M/Server cannot translate the local date and time information, given a specific time zone.

Change to the next time zone.

6322 functionName Failed to perform new day process for time zone timeZone, odate odate

Control-M/Server cannot perform the New Day procedure for the specified time zone.

6323 functionName Failed to select jobs from active jobs file where time zone = timeZone

Control-M/Server cannot perform the New Day procedure for the specified time zone.

Move to the next time zone.

6324 functionName Failed to update the job's status on the active jobs list during new day

Control-M/Server cannot update the job's status to Wait Scheduling or Post Odat during the New Day procedure.

Perform a database rollback.

6325 functionName Failed to release control resources during new day process for order number orderNumber

Control-M/Server cannot release the control resource for a specific job during the New Day procedure.

Perform a database rollback.

6326 functionName Failed to release quantitative resources during new day process for order number orderNumber

Control-M/Server cannot release the quantitative resource for a specific job during the New Day procedure.

Perform a database rollback.

6327 functionName Failed to delete the file fileName

Control-M/Server fails to delete the fileName file.

6328 functionName Failed to update variables from Control-M Agent

Control-M/Server fails to update variables from the Agent.

6329 functionName Job have reached timeout for state jobState.

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

Control-M/Server fails 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

During the deletion of the status file, Control-M/Server fails to select post-process jobs.

Control-M/Server cannot delete the status file for these jobs.

6332 functionName A corrupted status file received from Control-M Agent

The status file received from the Agent contains corrupted information.

System processing continues. The status file is saved for debugging.

6333 functionName When a corrupted status file received, rename the file fileName1 to fileName2

A corrupted status file should be renamed.

The status file saves for debugging.

6334 functionName Unable to rename fileName1 to fileName2

A file cannot be renamed.

6335 functionName Failed to initialize connection to database

Control-M/Server fails to initialize a connection to the database.

Control-M/Server cannot start

6336 functionName Failed to check link to database server

The link to the database server cannot be checked when the Control-M/Server starts.

Control-M/Server cannot start.

6337 functionName Failed to open CMS_SYSPRM table

Control-M/Server cannot open the CMS_SYSPRM table.

Control-M/Server cannot start.

6338 functionName Failed to clean list

Control-M/Server fails to clean the dblog and ioalog lists in memory.

Control-M/Server cannot start the SL process.

6339 functionName Failed to close connection when the process is shutting down

Control-M/Server fails to close the connection to the database when the process shuts down.

6400 functionName: error allocating entity.

Control-M fails to allocate memory for an entity.

The catastrophe flag is raised and the process shuts down.

6401 functionName: error in mutex creation: rc

Control-M fails to create a mutex synchronization object.

The catastrophe flag is raised, and the process shuts down.

6402 functionName: error creating message Q rc

Control-M fails to create a message queue.

The catastrophe flag is raised and the process shuts down.

6403 functionName: error destroying mutex in cleanup rc

Control-M fails to destroy a mutex synchronization object during cleanup after thread entity creation. This cleanup takes place when some other severe error occurs.

The catastrophe flag is raised and the process shuts down.

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

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.

6405 functionName: error destroying mutex rc

A mutex synchronization object cannot be destroyed during process shutdown. This may happen if the destroyed mutex object is locked by a thread.

6406 functionName: error locking mutex rc

A mutex synchronization object cannot lock.

The catastrophe flag is raised and the process shuts down.

6407 functionName: error unlocking a mutex rc= rc

A mutex synchronization object cannot unlock.

The catastrophe flag is raised and the process shuts down.

6408 functionName: error creating threads dynamic array rc= rc

A threads data structure cannot create on startup.

The catastrophe flag is raised and the process shuts down.

6409 functionName: error allocating work Qs array

Memory cannot allocate on startup.

The catastrophe flag is raised and the process shuts down.

6410 functionName: error duplicating message for thread with index threadIndex rc= rc

A thread message cannot duplicate.

The catastrophe flag is raised and the process shuts down.

6411 functionName: error in sending message to Q type queueType thread threadIndex rc= rc

A message cannot be sent to a thread message queue.

The catastrophe flag is raised and the process shuts down.

6412 functionName: failed to get status of thread with index threadIndex rc= rc

A thread's status cannot be obtained.

The catastrophe flag is raised and the process shuts down.

6413 functionName: failed to add message to thread message Q rc= rc

A message cannot add to a thread message queue.

The catastrophe flag is raised and the process shuts down.

6414 functionName: thread message id messageID without destination

A thread message without a destination is found when the thread sent the messages that wait to commit.

The thread message was not sent. Processing continues.

6415 functionName: thread with index threadIndex has kpa problem

A thread does not update its keep alive flag.

The catastrophe flag is raised and the process shuts down.

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

A thread message is not created. The reason for this error may be due to a failure to allocate memory.

The catastrophe flag is raised and the process shuts down.

6417 functionName: error in priority Q creation rc= rc

A priority queue does not create during startup.

The catastrophe flag is raised and the process shuts down.

6418 functionName: error in signaling condition rc= rc

A condition synchronization object does not signal, which is necessary to notify a thread that it has messages waiting. This failure may cause a thread to remain in sleep mode and not wake up to handle its messages.

The catastrophe flag is raised, and the process shuts down.

6419 Unable to read CMS_SYSPRM

The selector process fails 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:

• Performs a cleanup of submission queue internal data structure.

• Marks the internal memory data structures that are to be refreshed when leaving the suspend mode.

A single failure to read this table is harmless because the process keeps trying to read it. A continuous failure, which does not resolve until the end of the New Day procedure, may cause late submission of jobs that wait in the submission queue when the New Day procedure begins (are ready to submit but do not submit).

The process remains in suspend mode and after a period of time tries to read the table again.

6420 functionName: Failed to initialize threads in main. rc = rc

A process fails to initialize its threads.

The process shuts down.

6421 functionName: Catastrophic failure while mainAction

A main thread detects that the catastrophe flag was set by one of its threads.

The process shuts down.

6422 functionName: Failure occurs - Threads have not changed their states. State = {SUSPEND | RUN}

Not all threads reach their desired state on startup. Threads start in suspend state. When all threads reach suspend state, the main thread sends a run message. The states of all threads change to run, and normal execution begins.

The process shuts down.

6423 functionName: Thread status pointer is not initialized

Thread information data is corrupt.

The catastrophe flag is raised and the process shuts down.

6424 functionName: failed in checking threads state rc= rc

The threads state cannot be checked.

The catastrophe flag is raised and the process shuts down.

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

The internal threads data structure cannot update during process startup.

The catastrophe flag is raised, and the process shuts down.

6426 functionName: main thread failed to wait for state change rc= rc

Sleep activity for the main thread stops prematurely. The reason for the sleep failure can be seen in previous messages in the log file.

The catastrophe flag is raised, and the process shuts down.

6427 functionName: error creating threads manager object rc= rc

Creation of the main threads data structure fails during process startup.

The process shuts down.

6428 functionName: failed to get kpa value for thread with index threadIndex

The main thread fails to read the keep alive value of one of the threads. This may be due to a failure in a mutex synchronization object.

The catastrophe flag is raised and the process shuts down.

6429 functionName: Unknown process state state

The transition of process state to thread state during a process state change fails due to an unknown process state.

6430 functionName: Failure while trying to send to all threads a change state message. with id state

The main thread fails to send a state message to all threads.

The process shuts down.

6431 functionName: Error adding thread work queue - array is full

The internal data structure work queue array is full.

The catastrophe flag is raised and the process shuts down.

6432 functionName: Cannot add thread message to queue - message is corrupt

The addition of a message to a thread message queue fails because the message is corrupt.

The catastrophe flag is raised and the process shuts down.

6433 functionName: Failed to pop a message from message queue rc= rc

A failure occurs when trying to pop a message from a thread message queue.

The catastrophe flag is raised and the process shuts down.

6434 functionName: Failure occurs - Submission and presub threads have not changed their states to SUSPEND. Going out

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 displays when the threads are not in suspend state, or when the check of their state fails.

The catastrophe flag is raised, and as a result, the process shuts down.

6435 functionName: Failure occurred - Refresh has was not been performed. rc = rc

The refresh (update of internal data structures from the database) process fails.

6436 functionName: validity check of hi_load_start value failed

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 a refresh can be performed.

6437 functionName: validity check of hi_load_end value failed, setting hi_load_end value to blank.

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 the current time is the end time.

6438 functionName: Failure occurred while trying to clean the message Q of main thread. rc = rc

Cleaning of certain messages from the main thread queue prior to a refresh (update of internal data structures from the database) fails.

The system continues to perform the refresh. The messages that are not cleaned cause redundant work to be performed.

6439 functionName: Failed while trying to send refresh message to the threadName thread

A refresh (update of internal data structures from the database) message is not sent to a thread.

This thread does not perform a refresh. The catastrophe flag may be raised and the process shuts down.

6440 functionName: error in sending message to thread work queue with index threadIndex rc= rc

A message cannot be sent to a thread work queue.

The catastrophe flag is raised and the process shuts down.

6441 Failed to create temporary file name under directory dirName, rc

Control-M/Server fails to create a temporary filename during a test agent operation.

The test agent operation aborts.

6442 functionName : Failed to serialize remote host, rc

A failure occurs while serializing Agentless Host details into a file during a test agent operation.

The test of the operation aborts.

6443 functionName: Failed to deserialize remote host, rc

A failure occurs while de-serializing Agentless Host details into a file during a test agent operation.

The test of the operation aborts.

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

Control-M/Server fails to update the AGSTAT file for a host ID. This message appears while discovering Agentless Hosts that are mapped to Default as the host ID, because of a change in the default host ID's settings.

The Agentless Host identified in this message is not re-discovered.

6445 functionName: Failed to locate file fileName rc= rc.

Failure to locate an internal tmp file during plugable configuration agent operation.

The Control-M Configuration Manager operation fails.

6500 functionName: Failed while initializing the thread, rc = rc. Going out.

A thread fails to perform all initializations that need to start working.

A thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6501 functionName: Failed while initializing the thread's prolog, rc = rc

A thread fails to perform major initializations. For example, creating data structures or establishing a connection to database.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

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

A thread fails to retrieve its message queue. A thread message queue is essential for a thread for handling messages coming from other threads.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6503 functionName: Failed while setting the thread status to status, rc = rc. Going out.

A thread fails to change its status.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6504 functionName: Failed while getting the thread's status, rc = rc. Going out.

A thread fails to obtain its current status.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6505 functionName: A thread has reached an unrecognized status status. Going out.

When fetching its status, a thread realizes that it is an invalid status.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6506 functionName: A thread has received an unrecognized message messageID

A thread receives 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.

Handling a submission of a job fails.

The job is not submitted.

6508 functionName: Failed while trying to mark a job orderNumber, as failed in submission rc = rc.

The submission thread fails to indicate that the job submits.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6509 functionName: Failed while popping job orderNumber, from submission queue, rc = rc.

The submission thread fails to pop the submitted job out of the submission queue.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6510 functionName: Failed while fetching a message from submission queue.

The submission thread fails to fetch a message from the submission queue.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

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

The submission thread fails to notify on submission failure for a job.

The thread goes down. As a result, the process goes down after it detects that the thread is no longer alive.

6512 functionName: A thread has failed to clean its message queue, rc = rc

6513 functionName: No destination is found to where a message should be sent, msg = messageData.

The communication thread does not find the destination where the message should be sent.

A message is not sent.

6514 functionName: Failed while creating dataStructure, rc = rc

An internal data structure cannot be created.

Catastrophic is set. This causes the process SL to terminate.

6515 functionName: Thread manager has failed to create the thread threadName, rc = rc.

Some of the threads are not created.

Catastrophic is set. This causes the process SL to terminate.

6516 functionName: Failed to create thread with invalid type type

A thread of an illegal type does not create.

Catastrophic is set. This causes the process SL to terminate.

6517 functionName: Process has failed to Initialize its prolog, rc = rc

A process fails to perform all initializations that are needed to start working.

Catastrophic is set. This causes the process SL to terminate.

6518 functionName: No job is marked as Fail in submission queue, rc = rc, Going out.

You expect to have a job which fails to submit, but no job was found.

Catastrophic is set. This causes the process SL to terminate.

6519 functionName: Failure occurred - Release resource failed, for a job orderNumber rc = rc.

A Job's allocated resources fails to release.

6520 functionName: Failed while sending condition message to thread thread for cond condition.

An update (for example, delete or add) regarding a condition is not sent to a thread. As a result, jobs which depend on this condition may not be affected by the action.

Catastrophic is set. This causes the process SL to terminate.

6521 functionName: Failed while sending control message to thread thread for resource resource.

An update (for example, delete or add) regarding a control resource was not sent to a thread. As a result, jobs which depend on this resource, may not be affected.

Catastrophic is set. This causes the process SL to terminate.

6522 functionName: Failed while trying to send quantitative message to thread thread for resource resource.

An update (for example, delete and add) regarding a quantitative resource was not sent to a thread. As a result, jobs which depend on this resource, may not be affected.

Catastrophic is set. This causes the process SL to terminate.

6523 functionName: Failed while sending order message for job orderNumber, to thread thread.

A message regarding a certain job is not sent to a thread. The message is regularly sent:

• When a job adds 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.

Catastrophic is set. This causes the process SL to terminate.

6524 functionName: Failed while sending order but not submit message for job orderNumber, to thread thread.

A message regarding a dummy or group type job is 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 handled.

Catastrophic is set. This causes the process SL to terminate.

6525 functionName: Failed while sending a change state SUSPEND to submission thread, rc = rc.

Before the presub thread performs a refresh, it requests the submission thread to move to SUSPEND mode. The request is not sent.

Catastrophic is set. This causes the process SL to terminate.

6526 functionName: Failed while sending a change state RUN to submission thread, rc = rc.

When a refresh ends, the presub thread sends a request to the submission thread to move to RUN mode. The request is not sent.

Catastrophic is set. This causes the process SL to terminate.

6527 functionName: Failed while sending a notification to submission thread, job orderNumber, rc = rc.

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 is not sent.

Catastrophic is set. This causes the process SL to terminate.

6528 functionName: Failed while handling a change state message for thread with index index, new status state, rc = rc.

A thread's state does not change after receiving a change state message.

6529 functionName: Failed while handling a KPA message for thread with index index, rc = rc.

A thread's KPA does not update after receiving a KPA message.

Eventually, the SL main thread goes down after detecting a KPA problem with one of its threads.

6530 functionName: Failed while sending Do not handle job Message, for job orderNumber, to thread thread, rc = rc.

A Do not handle job message does not successfully send to a thread.

Catastrophic is set. This causes the process SL to terminate.

6531 functionName: Failed while sending change status message to a thread with index index, new status status, rc = rc.

A change status message is not sent to a thread.

The message is not handled.

6532 functionName: Process has reached terminate state. Going out.

A process reaches 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.