CTGDJB001W
The command did not complete successfully. See previous messages or error logs for details.
Explanation:
One or more errors occurred during the execution of the command.
Operator response:
Check the previous messages displayed by the tdisrvctl command, or look at the error logs for more details.
CTGDJB002E
Unknown value passed for '-op' option.
Explanation:
An illegal operation parameter was passed.
Operator response:
Check the tdisrvctl command usage for allowed options.
CTGDJB003E
The server hostname does not support Tombstones.
Tombstone support is not available in pre-6.1 servers.
Explanation:
The tdisrvctl command tried obtaining Tombstones from a pre-6.1 server. Tombstone support has been introduced from v6.1 onward.
Operator response:
Connect to a version 6.1 or later server for viewing Tombstones.
CTGDJB004E
Incorrect command usage.
Explanation:
The tdisrvctl command was invoked by passing unsupported command line options, or unexpected end of argument list was encountered or there was an incorrect usage of the command line options.
Operator response:
Check the tdisrvctl command usage and try invoking the tdisrvctl command with valid arguments.
CTGDJB005E
Unable to get Tombstone manager.
Explanation:
The tdisrvctl command was unable to connect to the Tombstone manager in the remote server. Probable reason being that the Tombstone feature was incorrectly configured on the server.
Operator response:
Check the remote server API and Tombstone manager settings on the remote server and try executing the tdisrvctl command again.
CTGDJB006E
Only a single Config can be specified.
Explanation:
The tdisrvctl command was invoked by passing multiple Configs as a parameter to an option which allows only a single Config to be specified.
Operator response:
Invoke the tdisrvctl command by passing only a single Config at a time.
CTGDJB007E
No value specified for option name option.
Explanation:
The tdisrvctl command was invoked by passing an option whose value had not been specified. The value is also required.
Operator response:
Check the tdisrvctl command usage, and invoke the tdisrvctl command again with the correct option and associated value.
CTGDJB008E
Only a single AssemblyLine can be specified.
Explanation:
The tdisrvctl command was invoked by passing multiple AssemblyLines as a parameter to an option which allows only a single AssemblyLine to be specified.
Operator response:
Invoke the tdisrvctl command by passing only a single AssemblyLine at a time. Check the tdisrvctl command usage.
CTGDJB010E
The value for the age option has to be an integer greater than zero (days).
Explanation:
The tdisrvctl command was invoked by passing a non-integer or a negative value for the age (in days) option.
Operator response:
Invoke the tdisrvctl command by passing a valid integer (greater than 0) for the specified option of Tombstone.
CTGDJB011E
Conflicting Tombstone option passed. Use keyword 'all' or specify a set of Tombstone attributes.
Explanation:
The tdisrvctl command with Tombstone option was invoked with contradictory options. Cannot ask for 'all' attributes and 'specific' attributes together.
Operator response:
Either specify the specific Tombstone attibutes that should be displayed, or ask to be shown all attributes. Not both. See tdisrvctl command usage.
CTGDJB012E
The 'all' keyword should be the last argument passed.
Explanation:
The tdisrvctl command with Tombstone option was invoked with incorrect options. The 'all' keyword has to be the last argument passed.
Operator response:
See the tdisrvctl command usage.
CTGDJB014E
The option switch option is mandatory.
Explanation:
The tdisrvctl command was invoked with a mandatory option not specified.
Operator response:
See the tdisrvctl command usage.
CTGDJB015E
Could not locate Config Config name.
Explanation:
Unable to locate the Config specified by user.
Operator response:
Check whether the Config name specified is correct and exists on the remote machine.
CTGDJB016I
Connected to server hostname and port.
Explanation:
This is an informational message only.
CTGDJB017I
Config started: Config name
Explanation:
This is an informational message only.
CTGDJB018I
Config already running: Config name
Explanation:
This is an informational message only.
CTGDJB019E
Could not start Config: Config name
Explanation:
Unable to start Config. An internal error occurred because the remote IBM TDI server was not properly setup or the configuration was incorrect. This may also occur because the configuration file was password protected, and the user did not specify a password in the tdisrvctl command. Also, if the Config path is incorrect or not fully qualified, tdisrvctl will not be able to locate the Config.
Operator response:
See the tdisrvctl command error logs for help. Verify the configuration on remote server is properly set up. Additionally, verify the Config file is password protected. If so, then specify the password in the tdisrvctl start option using the -e switch. Also, ensure that the fully qualified path of the Config file is mentioned exactly as it appears on the remote machine.
CTGDJB020I
AssemblyLine running: AssemblyLine name.
Explanation:
This is an informational message only.
CTGDJB021I
AssemblyLine started: AssemblyLine name.
Explanation:
This is an informational message only.
CTGDJB022E
AssemblyLine AssemblyLine name not found.
Explanation:
Unable to find user specified AssemblyLine. The Assembly Name passed may be incorrect or misspelled.
Operator response:
Check whether the AssemblyLine specified exists in the configuration on the remote server.
CTGDJB023E
Could not start AssemblyLines on the server hostname and port.
Explanation:
Some exceptions occurred while starting the AssemblyLines.
Operator response:
Check whether the Configurations and AssemblyLines are correctly set up on the remote server. Also check the tdisrvctl error logs for more information on the errors.
CTGDJB028E
The Config Config name is not loaded.
Explanation:
The user specified stopping of components of a configuration which is already not loaded on the server.
Operator response:
Check whether the Configuration name is correct. Also check the tdisrvctl error logs for more information on the errors.
CTGDJB029I
Config stopped: Config name.
Explanation:
This is an informational message only.
CTGDJB030E
Could not stop Config: Config name.
Explanation:
Some exceptions occurred while stopping the configuration.
Operator response:
Check the tdisrvctl error logs for more information on the errors.
CTGDJB031I
AssemblyLine stopped: AssemblyLine name.
Explanation:
This is an informational message only.
CTGDJB032E
Could not stop AssemblyLine: AssemblyLine name.
Explanation:
Some exceptions occurred while stopping the AssemblyLine.
Operator response:
Check the tdisrvctl error logs for more information on the errors.
CTGDJB033E
AssemblyLine already stopped: AssemblyLine name.
Explanation:
The user specified AssemblyLine is already not running.
Operator response:
Check the tdisrvctl error logs for more information on the errors.
CTGDJB034E
Error occurred while stopping AssemblyLines.
Explanation:
Some exceptions occurred while stopping the AssemblyLines.
Operator response:
Check the tdisrvctl error logs for more information on the errors.
CTGDJB039E
Cannot connect to server hostname and port.
Explanation:
Unable to connect to server. This error might occur for one or more of the following reasons: If the server is not running, or the machine on which the server is running is not accessible, or the remote server API engine over RMI is not running, or if remote server API accepts only SSL connections, and the SSL parameters / certificates in the trust and key stores may be incorrect.
Operator response:
Check the tdisrvctl error logs for more information on the reason for connection errors. Try connecting again.
CTGDJB040I
The server hostname and port has been shutdown.
Explanation:
This is an informational message only.
CTGDJB041I
Config Config name reloaded.
Explanation:
This is an informational message only.
CTGDJB042E
Config Config name is not running.
Explanation:
The user tried reloading a Config that is not running / loaded. Only already loaded Configs can be reloaded. If the Config is not loaded, then start the Config instead of trying to reload it.
Operator response:
Give the tdisrvctl -op start command instead of reload command, or check the name of the Config.
CTGDJB043E
One or more Configs could not be reloaded on the server hostname and port. Check the previous messages or error logs for details.
Explanation:
There were some errors encountered while reloading Configs. One or more Configs failed to reload.
Operator response:
Check the tdisrvctl command error logs for details on the errors.
CTGDJB044I
All the specified Configs have been successfully reloaded on the server hostname and port.
Explanation:
This is an informational message only.
CTGDJB045E
The operator switch option occurred more than once.
Explanation:
The tdisrvctl command was invoked with the same parameter passed more than once. Options can be passed only once. Fox example, the user may have passed the '-h' option twice, which is not allowed.
Operator response:
Pass each option only once.
CTGDJB046E
Unknown option operator switch encountered.
Explanation:
The tdisrvctl command was invoked with an unknown option.
Operator response:
See the tdisrvctl command usage and invoke the command with the allowed options only.
CTGDJB047E
The operator switch option was not specified. This is a mandatory option.
Explanation:
The tdisrvctl command was invoked without specifying the -op option.
Operator response:
See the tdisrvctl command usage and invoke the command with the correct and mandatory options specified.
CTGDJB048E
It is mandatory to specify Config. 'all' keyword is not allowed with -c option.
Explanation:
Instead of passing the Config name, the user asked for ALL Configs. This is not allowed. User must specify the configuration name.
Operator response:
Specify the explicit Config name when invoking the tdisrvctl command. See tdisrvctl command usage.
CTGDJB049I
Usage:
tdisrvctl [general_options] -op operation [operation_specific_options]
general_options:
-h host remote server IP address or hostname(default is localhost)
-K keystore name of the SSL key database file
-p port port number(default is 1099)
-P key_pwd key file password
-s dir Specifies the working directory where the solution directory is located.
-T truststore name of the SSL trust store database file
-u userID username(for custom authentication)
-v run in verbose mode
-w user_pwd user password(for custom authentication)
-W trust_pwd trust file password
-? display command usage
operation:
event send custom notification event
prop manage Config properties
queryop query an AssemblyLine for operations
reload reload running Configs
report generate Config report or list Configs on remote server
shutdown shutdown the server
srvinfo view IBM TDI server information
status view status of Configs or AssemblyLines
start start specific Config or AssemblyLines
stop stop specific Config or AssemblyLine
tombstone view Tombstone entries for specific Config or AssemblyLine
deletetombstone delete a tombstone entry
debug debug components in a running AssemblyLine
To get help for a specific operation:
tdisrvctl -op operation -?
Explanation:
This is an informational message only.
CTGDJB050I
The usage for reload operation is:
tdisrvctl [general_options] -op reload -c config_list
where:
-c config_list comma separated list of Configs to reload
Explanation:
This is an informational message only.
CTGDJB051I
The usage for shutdown operation is:
tdisrvctl [general_options] -op shutdown [-o return_code] [-f]
where:
-o return_code shutdown server with specified return code
-f force a controlled shutdown and exit all AssemblyLines
Explanation:
This is an informational message only.
CTGDJB052I
The usage for srvinfo operation is:
tdisrvctl [general_options] -op srvinfo
Explanation:
This is an informational message only.
CTGDJB053I
The usage for status operation is:
tdisrvctl [general_options] -op status [-c config_list | all]
[-r AL_list | all]
[-listen ]
where:
-c config_list comma separated list of Configs or keyword 'all'
-r AL_list comma separated list of ALs or keyword 'all'
-listen start receiving the logs of a running Config or AssemblyLine
Example:
To see the status of all loaded Configs and ALs
tdisrvctl [general_options] -op status
To see the status of all running ALs
tdisrvctl [general_options] -op status -r all
To see the status of all components of a particular loaded Config
tdisrvctl [general_options] -op status -c Config.xml -r all
Note:
- The keyword 'all' indicates all Configs or AssemblyLines.
- The -listen option requires exactly one Config or AssemblyLine to be specified.
Explanation:
This is an informational message only.
CTGDJB054I
The usage for the start operation is:
tdisrvctl [general_options] -op start -c config
[-e password]
[-r AL_list | all]
[-s ]
[-r AL_list -alop opname [{attr1:value1;attr2:value2;attrN:valueN}]|
-f filename]
[-m config_run_name -o storeName1=value1, storeName2=value2, storenameN=valueN]
[-t ]
[-listen ]
[-sync ]
where:
-c config name of config to start
-e password password of the config file if it is password protected
-r AL_list comma separated list of AssemblyLines to start or keyword 'all'
-s simulate mode run AssemblyLine in simulate mode
-alop opname AssemblyLine operation with required attributes and their values
-f filename filename to specify the operations
-m config run name run name of config
-o property file list comma separated list of property store names and values
-t start a temporary Config
-listen receive the logs of the specified Config or AssemblyLine
-sync execute AssemblyLine synchronously
Note:
- The -c option is mandatory.
- The keyword 'all' indicates all AssemblyLines.
- The -t option expects the Config specified in the -c option to be located on the client machine.
- The -listen option requires exactly one Config or AssemblyLine to be specified.
- The -listen option executes an AssemblyLine synchronously. There is no need to combine it with the -sync option.
- The -sync option requires exactly one AssemblyLine to be specified.
Explanation:
This is an informational message only.
CTGDJB055I
The usage for stop operation is:
tdisrvctl [general_options] -op stop -c config
[-r AL_list | all]
[-f]
where:
-c config name of Config
-r AL_list comma separated list of ALs to stop or keyword 'all'
-f force a controlled shutdown of AssemblyLines
Note:
- The -c option is mandatory.
- The keyword 'all' indicates all AssemblyLines.
Explanation:
This is an informational message only.
CTGDJB056I
The usage for tombstone operation is:
tdisrvctl [general_options] -op tombstone -c config
[-r AL_name]
[-age n]
[[attribute_list] | all ]
where:
-age n display tombstone record for the last 'n' days
(default is 1 day)
-c config name of Config
-r AL_name name of Aseembly Line
all show all Tombstone attributes
attribute_list:
-ct component type
-cn component name
-cfg configuration name
-guid Tombstone entry's guid
-et event type
-ex exit code
-stime component's start time
-ctime Tombstone create time
-desc error description
-um user message
-stat statistics (valid for ALs only)
Example:
To see the last 2 days Tombstone entries (all attributes) for Config C1.xml
tdisrvctl [general_options] -op tombstone -c C1.xml -age 2 all
Note:
- The -c option is mandatory.
- Only one of the -r or -t option is allowed. Not both.
Explanation:
This is an informational message only.
CTGDJB057E
The Config Config name is not loaded on the server hostname and port.
Explanation:
A Config that is not loaded on the server was specified for the 'report' option. Reports can only be generated if the specified Config is loaded on the server.
Operator response:
Check that the Config name specified is correct and that the Config is loaded on the server. Use the tdisrvctl 'status' option to obtain a list of the currently loaded Configs on the server. Alternatively, load the Config on the server and then fire the tdisrvctl command with the 'report' option.
CTGDJB058I
The Config folder on server hostname and port is empty.
Explanation:
This is an informational message only.
CTGDJB059I
The usage for report operation is:
tdisrvctl [general_options] -op report [-c config | -l]
where:
-c config name of the Config whose report is to be generated
-l list the Configs in the remote server's Config folder
Note:
- The specified Config must be already loaded on the remote server.
- Only one of the -c or -l option is allowed. Not both.
Explanation:
This is an informational message only.
CTGDJB060E
The server hostname does not support 'config' folder. The 'config' folder support is not available in pre-6.1 servers.
Explanation:
The tdisrvctl command tried obtaining Config listing from a pre-6.1 server. 'config' folder support has been introduced from v6.1 onwards.
Operator response:
Connect to a v6.1 or later server for obtaining listing of Configs in the 'config' folder.
CTGDJB061I
The usage for event operation is:
tdisrvctl [general_options] -op event -e event_name [-s source]
[-d data]
where:
-e event_name name of the event to send
-s source the name of the source invoking the
event (default tdisrvctl)
-d data the data (message) to be passed to an
event listener (default is null)
Note:
- All events sent from tdisrvctl (-e option) are automatically prefixed by the string "user".
Example:
To send an event "user.process.X.completed" from "admin"
tdisrvctl -h hostname -op event -e "process.X.completed" -s admin -d "Admin triggered event".
Explanation:
This is an informational message only.
CTGDJB062I
The event event name successfully sent.
Explanation:
This is an informational message only.
CTGDJB063I
The usage for prop operation is:
tdisrvctl [general_options] -op prop -c config [-l] |
[ [-o store] [[-g key | all] | [-s key=value [-e]] | [-d key]] ]
where:
-c config name of the Config to use
-l list all the configured property stores
-o name of the property store to use
-g key get the value of the specified key (or keyword 'all'
implying get all keys)
-s key=value set the key to the specified value
-e encrypt the value when putting in the store (can
be used with -s option only)
-d key delete the specified key from the store
Note:
- The -c option is mandatory. The specified Config should be a loaded Config on the remote server.
- The -l, -g, -s, and -d options are mutually exclusive, and cannot be used together.
- The -e option can be used with only the -s option.
- The -o option is mandatory when using the -d option.
Examples:
To list all property stores for Config C1.xml
tdisrvctl -op prop -c C1.xml -l
To get all properties for Config C1.xml
tdisrvctl -op prop -c C1.xml -g all
To get all properties for Config C1.xml from store MyStore
tdisrvctl -op prop -c C1.xml -o MyStore -g all
To set a property MY_PROP to value MY_VALUE for Config C1.xml in store MyStore
and mark it as protected
tdisrvctl -op prop -c C1.xml -o MyStore -s "MY_PROP=MY_VALUE" -e
Explanation:
This is an informational message only.
CTGDJB064E
Only one of the options -l, -g, -s, and -d can be specified. They cannot occur together.
Explanation:
The tdisrvctl command was invoked with options that are not allowed together. For example, the -l option is used for specifying the list of property stores, and hence cannot be used along with the -o option.
Operator response:
See the usage of the tdisrvctl "prop" option and invoke the command with the appropriate arguments passed.
CTGDJB065E
The property store (-o option) is not specified.
Explanation:
The tdisrvctl command prop option was invoked without specifying the property store (-o option).
Operator response:
See the usage of the tdisrvctl "prop" option and invoke the command with the appropriate arguments passed.
CTGDJB066E
Property store property store name does not exist.
Explanation:
The tdisrvctl command prop option was invoked with a property store name that does not exist (or was misspelled).
Operator response:
Fire the tdisrvctl command with prop option and -l switch to see the list of available property stores.
CTGDJB067I
The property key property key does not exist.
Explanation:
The tdisrvctl command prop option was invoked with a property key name that does not exist (or was misspelled).
Operator response:
Check the property key name, or view all the available properties by using the -g option with the "all" keyword.
CTGDJB068E
The server hostname does not support remote client event notification. This feature is not available in pre-6.1 servers.
Explanation:
The tdisrvctl command was used to send an event notification to a pre-6.1 server. User event notification support has been introduced from v6.1 onwards.
Operator response:
Connect to a v6.1 or later server for sending remote client event notifications.
CTGDJB069E
The server hostname does not support common APIs for IBM TDI Property management. This feature is not available in pre-6.1 servers.
Explanation:
The tdisrvctl command was used for property store management of a pre-6.1 server. Common APIs for IBM TDI property store management were introduced from version 6.1 onwards.
Operator response:
Connect to a version 6.1 or later server for remote IBM TDI property store management.
CTGDJB070I
The property key name has been set and committed.
Explanation:
This is an informational message only.
CTGDJB071I
The property key name successfully deleted.
Explanation:
This is an informational message only.
CTGDJB072I
The usage for query operation is:
tdisrvctl [general_options] -op queryop -c config -r AL_name
where:
-c config name of a loaded configuration
-r AL_name valid AssemblyLine in the specified configuration
Explanation:
This is an informational message only.
CTGDJB073I
Return Code: return code.
Explanation:
This is an informational message only.
CTGDJB074I
Determining whether Tombstone is supported.
Explanation:
This is an informational message only.
CTGDJB075I
Server version: version.
Explanation:
This is an informational message only.
CTGDJB076I
Start Date:date.
Explanation:
This is an informational message only.
CTGDJB077I
End Date :date.
Explanation:
This is an informational message only.
CTGDJB078I
Config ID :Config ID.
Explanation:
This is an informational message only.
CTGDJB079I
Number of Tombstones found: number of tombstones.
Explanation:
This is an informational message only.
CTGDJB080I
Determining whether remote client event notification is supported.
Explanation:
This is an informational message only.
CTGDJB081I
Server version: version.
Explanation:
This is an informational message only.
CTGDJB082I
Determining whether IBM TDI Properties is supported.
Explanation:
This is an informational message only.
CTGDJB083I
Server version: version.
Explanation:
This is an informational message only.
CTGDJB084I
In displayPropertyStoreList method.
Explanation:
This is an informational message only.
CTGDJB085I
In displayPropertyValues method.
Explanation:
This is an informational message only.
CTGDJB086I
In setTDIPropertyValue method.
Explanation:
This is an informational message only.
CTGDJB087I
In deleteTDIProperty method.
Explanation:
This is an informational message only.
CTGDJB088I
The server is: server name.
Explanation:
This is an informational message only.
CTGDJB089E
Config instance not started. Exception occurred: exception
Explanation:
See message.
Operator response:
Review the exception to find further details on the error.
CTGDJB090I
In viewServerInformation method.
Explanation:
This is an informational message only.
CTGDJB091I
In sendEventNotification method.
Explanation:
This is an informational message only.
CTGDJB092I
In viewStatus method.
Explanation:
This is an informational message only.
CTGDJB093I
In startComponents method.
Explanation:
This is an informational message only.
CTGDJB094I
In stopComponents method.
Explanation:
This is an informational message only.
CTGDJB095I
In viewAllALStatus method.
Explanation:
This is an informational message only.
CTGDJB096I
Number of running Configs:number of Configs.
Explanation:
This is an informational message only.
CTGDJB098I
Number of running Configs:number of Configs.
Explanation:
This is an informational message only.
CTGDJB099I
Attempting to connect to IBM TDI server: hostname: port.
Explanation:
This is an informational message only.
CTGDJB100I
Using custom authentication. Username: username.
Explanation:
This is an informational message only.
CTGDJB102I
In shutdownServer method. Return code return_code passed to method.
Explanation:
This is an informational message only.
CTGDJB103I
Determining whether Config folder feature is supported.
Explanation:
This is an informational message only.
CTGDJB104I
Server version: version.
Explanation:
This is an informational message only.
CTGDJB105I
In reloadConfigs method.
Explanation:
This is an informational message only.
CTGDJB106W
Duplicate argument: ''token''. Argument is ignored.
Explanation:
The user passed duplicate arguments while calling the command. The command has discarded the extraneous ones.
Operator response:
Refer the help for command, and pass appropriate command line parameters while invoking the command.
CTGDJB107I
Parsing general options.
Explanation:
This is an informational message only.
CTGDJB108I
General Options: options.
Explanation:
This is an informational message only.
CTGDJB109E
Unable to determine server version. Cannot continue.
Explanation:
The tdisrvctl utility was unable to determine the IBM TDI server version. It needs to know this to detect whether Tombstone Manager is present or not.
Operator response:
Check the remote IBM TDI server version that you are connecting to using tdisrvctl. The tombstone support has been introduced in the IBM TDI 6.0 version of the product.
CTGDJB110E
Unable to obtain Tombstones.
Explanation:
Some exception occured while trying to obtain tombstones. This could be because of some error in connecting to the remote IBM TDI server, or because of some other error while communicating with the IBM TDI server.
Operator response:
Check the error logs for other error messages, or try again.
CTGDJB111E
Invalid age: age value.
Explanation:
The tdisrvctl command was invoked by passing a non-integer or a negative value for the age (in days) option.
Operator response:
Invoke the tdisrvctl command by passing a valid integer (greater than 0) for the specified option of Tombstone.
CTGDJB112E
Error while processing shutdown return code.
Explanation:
There was an error in converting the shutdown code into an integer value.
Operator response:
Ensure that the passed shutdown code is an integer value.
CTGDJB113E
Unable to determine server version. Cannot continue.
Explanation:
The tdisrvctl utility was unable to determine the server version, so as to detect if event notification APIs are supported in this particular server release or not.
Operator response:
Connect to a v6.1 or later server for sending remote client event notifications.
CTGDJB114E
Error while trying to obtain list of property stores for Config: Config name.
Explanation:
The tdisrvctl utility encountered an internal error while trying to obtain the list of configured property stores from the remote IBM TDI server. This may have occured because the property store list in the remote server has got corrupted, or maybe an incompatible version of the remote IBM TDI server is being used.
Operator response:
Check if the property stores list can be correctly seen in the ibmditk. Also, check the Problem Determination Guide for problems related to the property store. Ensure that the version of tdisrvctl and the version of the remote IBM TDI server match. The property store feature has been introduced in version 6.1 of IBM TDI.
CTGDJB115E
Error while trying to obtain list of property stores for Config: Config name.
Explanation:
The tdisrvctl utility encountered an internal error while trying to obtain the list of configured property stores from the remote IBM TDI server. This may have occured because the property store list in the remote server has got corrupted, or maybe an incompatible version of the remote IBM TDI server is being used.
Operator response:
Check if the property stores list can be correctly seen in the ibmditk. Also, check the Problem Determination Guide for problems related to the property store. Ensure that the version of tdisrvctl and the version of the remote IBM TDI server match. The property store feature has been introduced in version 6.1 of IBM TDI.
CTGDJB116E
Error while trying to obtain property for Config:Config name.
Explanation:
The tdisrvctl utility encountered an internal error while trying to obtain the properties of a particular store from the remote IBM TDI server. This may have occured because the property store list in the remote server has got corrupted, or maybe an incompatible version of the remote IBM TDI server is being used.
Operator response:
Check if the property values can be correctly seen in the ibmditk. Also, check the Problem Determination Guide for problems related to the property store. Ensure that the version of tdisrvctl and the version of the remote IBM TDI server match. The property store feature has been introduced in version 6.1 of IBM TDI. Also have a look at the output messages of the tdisrvctl command.
CTGDJB117E
Error while trying to set property for Config:Config name.
Explanation:
The tdisrvctl utility encountered an internal error while trying to set a property in a particular store in the remote IBM TDI server. This may have occured because the property store in the remote server has got corrupted, or maybe an incompatible version of the remote IBM TDI server is being used.
Operator response:
Check if the property values can be correctly set in the ibmditk. Also, check the Problem Determination Guide for problems related to the property store. Ensure that the version of tdisrvctl and the version of the remote IBM TDI server match. The property store feature has been introduced in version 6.1 of IBM TDI. Also have a look at the output messages of the tdisrvctl command. Try again.
CTGDJB118E
Error while trying to delete property ''key name'' for Config:Config name
Explanation:
The tdisrvctl utility encountered an internal error while trying to delete a property in a particular store in the remote IBM TDI server. This may have occured because the property store in the remote server has got corrupted, or maybe an incompatible version of the remote IBM TDI server is being used. This would also happen in-case the particular property store is READ-ONLY.
Operator response:
Check if the property values can be correctly set in the ibmditk. Also, check the Problem Determination Guide for problems related to the property store. Ensure that the version of tdisrvctl and the version of the remote IBM TDI server match. The property store feature has been introduced in version 6.1 of IBM TDI. Also have a look at the output messages of the tdisrvctl command. Ensure that the particular property store is not READ-ONLY. Try again.
CTGDJB119E
The KEY=VALUE format should have been specified for property key and value
Explanation:
The tdisrvctl command was invoked incorrectly.
Operator response:
See the command usage and try again. Very double quotes are used to group arguments that have spaces.
CTGDJB120E
Unable to retrieve server information.
Explanation:
The tdisrvctl utility encontered an internal error while trying to obtain the remote IBM TDI server host details.
Operator response:
Ensure that the remote IBM TDI server is of version 6.0 or above. Also ensure that there are no connection errors while connecting to IBM TDI server, and the IBM TDI server has its remote server API engine is turned on.
CTGDJB121E
Error while sending custom event notification: event name=event name, event source=event source, event data=event data.
Explanation:
The tdisrvctl utility encountered an error while trying to send a custom notification event.
Operator response:
Have a look at the log trace, or the server logs to find out the problem. Ability to send custom notification was added in IBM TDI version 6.1. Ensure that you are using a compatible version of IBM TDI server. Try sending the event again.
CTGDJB122E
Unable to get the Config info or stop the Config.
Explanation:
The tdisrvctl utility was unable to obtain handle to the remote Config to stop.
Operator response:
Check the exception, or previous messages. Also have a look at the server logs. Try again.
CTGDJB123E
Unable to get details for AssemblyLines.
Explanation:
The tdisrvctl utility was unable to get details for AssemblyLines. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured. The AssemblyLine or the Config could also be corrupted.
Operator response:
Check the exception trace, or the command output. Also check the server logs. Try again.
CTGDJB125E
Unable to get list of all running Configs.
Explanation:
The tdisrvctl utility encountered an error while trying to obtain the list of all running configs. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured.
Operator response:
Ensure that the tdisrvctl and remote IBM TDI server versions match. Also look into the exception trace and the server logs. Try again.
CTGDJB126E
Unable to get list of all Configs.
Explanation:
An internal error occured while trying to obtain the list of all configs. This occurred because of m_Session.listAllConfigurations() method threw an error.
Operator response:
Ensure that the tdisrvctl and remote IBM TDI server versions match. Also look into the exception trace and the server logs. Try again.
CTGDJB127E
Error while getting assembly line details.
Explanation:
The tdisrvctl utility was unable to get details for AssemblyLines. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured. The AssemblyLine or the Config could also be corrupted.
Operator response:
Check the exception trace, or the command output. Also check the server logs. Try again.
CTGDJB128E
Error while getting Connector library details.
Explanation:
The tdisrvctl utility was unable to get details for Connector Library. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured. The Config could also be corrupted.
Operator response:
Check the exception trace, or the command output. Also check the server logs. Try again.
CTGDJB129E
Error while getting Parser library details.
Explanation:
The tdisrvctl utility was unable to get details for Parser Library. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured. The Config could also be corrupted.
Operator response:
Check the exception trace, or the command output. Also check the server logs. Try again.
CTGDJB130E
Error while getting script library details.
Explanation:
The tdisrvctl utility was unable to get details for Script Library. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured. The Config could also be corrupted.
Operator response:
Check the exception trace, or the command output. Also check the server logs. Try again.
CTGDJB131E
Error while getting function library details.
Explanation:
The tdisrvctl utility was unable to get details for Function Library. This may happen because the IBM TDI server version does not match the tdisrvctl utility version, or some other internal server error occured. The Config could also be corrupted.
Operator response:
Check the exception trace, or the command output. Also check the server logs. Try again.
CTGDJB132E
Unable to determine server version. Cannot continue.
Explanation:
The tdisrvctl utility was unable to determine the server version, so as to detect if config folder feature is supported in this particular server release or not.
Operator response:
Connect to a v6.1 or later server for viewing configs in the config folder.
CTGDJB133E
Unable to get list of all Configs.
Explanation:
An internal error occured while trying to obtain the list of all configs. This occurred because of Session.listAllConfigurations() method threw an error.
Operator response:
Ensure that the tdisrvctl and remote IBM TDI server versions match. Also look into the exception trace and the server logs. Try again.
CTGDJB134E
Error while retrieving list of loaded Configs.
Explanation:
An internal error occured while trying to obtain the list of all loaded configs on the remote IBM TDI server. This occured because Session.getConfigInstances() method threw an error.
Operator response:
Ensure that the tdisrvctl and remote IBM TDI server versions match. Also look into the exception trace and server logs. Try again.
CTGDJB135W
Already reached the end of argument list.
Explanation:
While parsing the arguments, the tdisrvctl utility encountered an unexpected end of arguments.
Operator response:
Check the command usage and try again.
CTGDJB136I
Argument at index index: value.
Explanation:
This is an informational message only.
CTGDJB137I
Configuration: configuration name.
Explanation:
This is an informational message only.
CTGDJB138E
AssemblyLine AssemblyLine name not found.
Explanation:
Unable to find user specified AssemblyLine. The Assembly Name passed may be incorrect or misspelled.
Operator response:
Check whether the AssemblyLine specified exists in the configuration on the remote server.
CTGDJB139I
No operations exposed by the AssemblyLine.
Explanation:
This is an informational message only.
CTGDJB140E
The Config Config name is not loaded.
Explanation:
The Config specified for the 'queryop' option is not loaded on the server.
Operator response:
Verify the Config name is correct.
CTGDJB141E
The server hostname does not support deletion of tombstones.
Delete tombstone support is not available in pre-7.0 servers.
Explanation:
The tdisrvctl command tried deleting tombstones from a pre-7.0 server. Deletion of tombstones has been introduced from v7.0 onward.
Operator response:
Connect to a version 7.0 or later server for deleting tombstones.
CTGDJB142I
The usage for the tombsone deletion operation is:
tdisrvctl [general_options] -op deletetombstone -guid 'GUID # '
where:
-guid 'GUID # ' is the unique identifier for the tombstone to be deleted.
Note:
- GUID for a tombstone can be obtained by viewing a tombstone
Explanation:
This is an informational message only.
CTGDJB143I
Tombstone with guid GUID successfully deleted.
Explanation:
This is an informational message only.
CTGDJB144I
Temp configs cannot be run with password specified.
Explanation:
The tdisrvctl command was invoked by specifying the -t (temp config) option in a combination with the -e (password) option, but temp configs cannot be started with a password.
Operator response:
Remove either the -t or -e option in order to successfully run the command.
CTGDJB145E
It is mandatory to specify an AssemblyLine name. 'keyword' keyword is not allowed.
Explanation:
Instead of passing the AssemblyLine name, the user asked for ALL AssemblyLines. This is not allowed. User must specify the AssemblyLine name.
Operator response:
Specify the explicit AssemblyLine name when invoking the tdisrvctl command. See tdisrvctl command usage.
CTGDJB146E
Option 'option' is not allowed for operation 'option'.
Explanation:
The user specified an option which is not supported for the specified operation.
Operator response:
See tdisrvctl command usage.
CTGDJB147I
Listening for AssemblyLine messages...
Explanation:
This is an informational message only.
CTGDJB148I
Listening for Config messages...
Explanation:
This is an informational message only.
CTGDJB149I
In debugComponents method.
Explanation:
This is an informational message only.
CTGDJB150E
The AssemblyLine AssemblyLine name is not running.
Explanation:
The user specified debugging of components of an AssemblyLine that is not running on the server.
Operator response:
Check whether the AssemlyLine name is correct. Also check the tdisrvctl error logs for more information on the errors.
CTGDJB151E
Could not set debug mode to component name component.
Explanation:
The user specified a component that does not exist in the specified AssemblyLine.
Operator response:
Check whether the component name is correct. Also check the tdisrvctl error logs for more information on the errors.
CTGDJB152I
The usage for the debug operation is:
tdisrvctl [general_options] -op debug -c config -r assembly_line
[-alc al_component]
-on/off
where:
-c config config instance ID
-r assembly_line name of the AssemblyLine
-alc al_component name of the AssemblyLine component
-on flag to enable debug mode
-off flag to disable debug mode
Note:
- The -c and -r options are mandatory and require exactly one Config/AssemblyLine to be specified.
- If -alc option is not specified all components in the specified AssemblyLine will be affected.
Examples:
To view the Debug mode value of the components in the AssemblyLines of a specified Config
tdisrvctl -op report -c config
To enable the debug mode for all components in the running AssemblyLine al2
tdisrvctl -op debug -c config_name -r al2 -on
To disable the debug mode for specified components in the running AssemblyLine al3
tdisrvctl -op debug -c config_name -r al3 -alc fread,httpServer,myconn -off
Explanation:
This is an informational message only.
CTGDJB153I
AssemblyLine AssemblyLine name completed successfully.
Statistics: AssemblyLine statistics
Explanation:
This is an informational message only.
CTGDJB154I
AssemblyLine AssemblyLine name failed with exception: exception
Statistics: AssemblyLine statistics
Explanation:
This is an informational message only.
CTGDJB155I
Last AssemblyLine Entry: Entry object
Explanation:
This is an informational message only.
CTGDJB156W
Could not retrieve last AssemblyLine Entry: exception
Explanation:
The last Entry of the executed AssemblyLine cannot be retrieved from the Server. Probably it contains Attribute values which do not implement the java.io.Serializable interface.
Operator response:
Check the configuration of the AssemblyLine.
CTGDJB501I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB502E
Unable to create Action Manager Thread for
[AM_ID]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for AssemblyLine Not Executed For Specified Time type of trigger).
Operator response:
Check the exception trace following this message in the logs. Ensure that the time units were correctly specified.
CTGDJB503E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution view.
Operator response:
Verify that the remote TDI server associated with this Solution view is running, and remote Server API engine is enabled on that server. If SSL is not enabled at the remote TDI Server end, then ensure that the IP address of the machine running Action Manager is mentioned in the api.remote.nonssl.hosts property in the global.properties or solution.properties file of the remote TDI Server. If SSL is enabled at the remote TDI Server end, then ensure that the Action Manager key store and trust store are set up correctly. Refer to the TDI Installation and Administrator Guide for steps on how to configure TDI for SSL.
CTGDJB504E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB505E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register an AssemblyLine terminate listener.
Explanation:
The Action Manager was unable to create a thread because it could not register an AssemblyLine terminate listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB506I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine
Explanation:
This is an informational message only.
CTGDJB507I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB508I
AssemblyLine AssemblyLine name has not run since time seconds. Starting execution of associated actions.
Explanation:
This is an informational message only.
CTGDJB509I
Rule rule name has already been triggered earlier. Awaiting the next run of AssemblyLine AssemblyLine name.
Explanation:
This is an informational message only.
CTGDJB510I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB511I
Action Manager initialization completed.
Explanation:
This is an informational message only.
CTGDJB512I
Started Health AssemblyLine Manager.
Explanation:
This is an informational message only.
CTGDJB513I
Action Manager initialization started.
Explanation:
This is an informational message only.
CTGDJB514E
Property property name
is not set.
Explanation:
The Action Manager was unable to initialize because the required property action.manager.prop.file was not set. This property is required for finding the location of the Action Manager configuration file am_config.properties.
Operator response:
Ensure that in the startAM.bat(sh) file the action.manager.prop.file property is being set to point to the location of the am_config.properties file.
CTGDJB515E
Unable to load the am_config.properties file. Check the value of action.manager.prop.file property. Current value is: file path
Explanation:
The Action Manager was unable to initialize because the property action.manager.prop.file in the startAM.bat(sh) file is pointing to an invalid location of am_config.properties.
Operator response:
Ensure that in the startAM.bat(sh) file the action.manager.prop.file property is being set to point to the location of the am_config.properties file. See the associated exception trace.
CTGDJB516E
Unable to load the amc.properties file. Current value of com.ibm.di.amc.properties.file.location property is: file path
Explanation:
The Action Manager was unable to initialize because the property com.ibm.di.amc.properties.file.location in the am_config.properties file is pointing to an invalid location of amc.properties. The Action Manager needs to load the amc.properties to obtain SSL (and other) details of the Administration and Monitoring Console.
Operator response:
Ensure that in the am_config.properties file the com.ibm.di.amc.properties.file property is being set to point to the location of the amc.properties file. See the associated exception trace. Also ensure that forward slashes are used in specifying the path.
CTGDJB517I
SSL Trust Store: trust store path
Explanation:
This is an informational message only.
CTGDJB518I
SSL Key Store: key store path
Explanation:
This is an informational message only.
CTGDJB519I
Initializing connection to database.
Explanation:
This is an informational message only.
CTGDJB520E
Unable to initialize database.
Explanation:
The Action Manager was unable to initialize connection to database. This may occur if there is an error in the JDBC URLs specified in the am_config.properties. The Action Manager connects to the Administration and Monitoring Console's database using Derby in network mode. If the specified Derby database does not exist, or is booted in embedded mode, then Action Manager cannot connect to the database. To create the database, the Administration and Monitoring Console must have been started at least once. Action Manager will start the database in network mode, in case its not running in network mode already.
Operator response:
Ensure that the JDBC settings in the am_config.properties file are correct, and
pointing to the Administration and Monitoring Console's Derby database. Ensure that the Administration and Monitoring Console is not already connected to
the database in Embedded mode. The recommended procedure is as follows:
1) Ensure that the Administration and Monitoring Console's database exists. If not, start the Administration and Monitoring Console. On starting the Administration and Monitoring Console for the first time, the
Derby database is automatically created.
2) Shutdown the Administration and Monitoring Console and reconfigure it to connect to the database in network mode (if not already
configured for network mode).
3) Start Action Manager. Action Manager will start the database in network mode.
4) Start the Administration and Monitoring Console, which will also connect to the same database over network mode.
CTGDJB521W
Action Manager was unable to read property com.ibm.di.amc.am.healthAL.interval.time. Health AssemblyLine triggering interval set to a default value of 30 minutes.
Explanation:
The Action Manager was unable to read the com.ibm.di.amc.am.healthAL.interval.time property from the am_config.properties file. This property is used to determine the triggering interval for Health AssemblyLines of Solution Views. If this property is not defined, then Action Manager will attempt to trigger all configured Health AssemblyLines every 30 minutes (unless the Health AssemblyLine is not running already, in which case it will not trigger a new run of the Health AssemblyLine).
Operator response:
Ensure that there is a valid time value (in seconds) specified for the com.ibm.di.amc.am.healthAL.interval.time property in the am_config.properties file.
CTGDJB522I
Creating Action Manager threads.
Explanation:
This is an informational message only.
CTGDJB523E
Unable to obtain connection to database.
Explanation:
The Action Manager was unable to obtain a connection to database. This may occur if there is an error in the JDBC URLs specified in the am_config.properties. The Action Manager connects to the Administration and Monitoring Console's database using Derby in network mode. If the specified Derby database does not exist, or is booted in embedded mode, then Action Manager cannot connect to the database. To create the database, the Administration and Monitoring Console must have been started at least once. Action Manager will start the database in network mode, in case its not running in network mode already. This could also happen, if the database shutdown (maybe because the Administration and Monitoring Console was shutdown). This will happen, only if the Administration and Monitoring Console had booted the database, and now the Administration and Monitoring Console has been shutdown. It is recommended that to avoid this situation, start Action Manager first, and then start the Administration and Monitoring Console.
Operator response:
Ensure that the JDBC settings in the am_config.properties file are correct, and
pointing to the Administration and Monitoring Console's Derby database. Ensure that the Administration and Monitoring Console is not already connected to
the database in Embedded mode. The recommended procedure is as follows:
1) Ensure that the Administration and Monitoring Console's database exists. If not, start the Administration and Monitoring Console. On starting the Administration and Monitoring Console for the first time, the
Derby database is automatically created.
2) Shutdown the Administration and Monitoring Console and reconfigure it to connect to the database in network mode (if not already
configured for network mode).
3) Start Action Manager. Action Manager will start the database in network mode.
4) Start the Administration and Monitoring Console, which will also connect to the same database over network mode.
CTGDJB524I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On termination of AssemblyLine.
Explanation:
This is an informational message only.
CTGDJB525I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On receiving Event.
Explanation:
This is an informational message only.
CTGDJB526I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On specific property value.
Explanation:
This is an informational message only.
CTGDJB527I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On query of AssemblyLine result.
Explanation:
This is an informational message only.
CTGDJB528I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On server API failure.
Explanation:
This is an informational message only.
CTGDJB529I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On elapsed time interval since last execution of AssemblyLine.
Explanation:
This is an informational message only.
CTGDJB530E
Exception while constructing Action Manager threads.
Explanation:
The Action Manager was unable to create listener threads because some internal error occurred. See the logs, or accompanying exception trace for more information.
Operator response:
See the associated exception trace for reasons of error. Try running Action Manager again.
CTGDJB531I
Action Manager threads created.
Explanation:
This is an informational message only.
CTGDJB532I
Database modification listener started.
Explanation:
This is an informational message only.
CTGDJB533I
Checking for any Action Manager rule updates.
Explanation:
This is an informational message only.
CTGDJB534E
Error occurred while running Database modification listener.
Explanation:
The Action Manager's database listener thread, that checks if any Action Manager rule has been modified from the Administration and Monitoring Console, encountered a database exception while trying to read data from the database. This could have happened if the database has been shutdown, or some other internal error occurred.
Operator response:
Verify that the database is running. Look at the exception trace in the log.
CTGDJB535E
Error occurred while trying to delete data from the AM_UPDATE_DETAILS table.
Explanation:
The Action Manager's database listener thread, that checks if any Action Manager rule has been modified from the Administration and Monitoring Console, encountered a database exception while trying to delete data from the AM_UPDATE_DETAILS table in the database. This could have happened if the database has been shutdown, or some other internal error occurred.
Operator response:
Verify that the database is running. Look at the exception trace in the log.
CTGDJB536I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On termination of AssemblyLine.
Explanation:
This is an informational message only.
CTGDJB537I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On receiving Event.
Explanation:
This is an informational message only.
CTGDJB538I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On specific property value.
Explanation:
This is an informational message only.
CTGDJB539I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On query of AssemblyLine result.
Explanation:
This is an informational message only.
CTGDJB540I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On server API failure.
Explanation:
This is an informational message only.
CTGDJB541I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On elapsed time interval since last execution of AssemblyLine.
Explanation:
This is an informational message only.
CTGDJB542E
Error occurred while constructing Action Manager thread for rule: rule name
Explanation:
The Action Manager's real time listener thread, that checks if any Action Manager rule has been modified from the Administration and Monitoring Console, encountered an exception while trying to create an Action Manager thread for the modified rule. See the associated log messages and exception trace for more information.
Operator response:
Look into the log messages and exception trace for more information. Modify the particular rule again using the Administration and Monitoring Console.
CTGDJB543E
Error occurred while trying to insert data into the AM_UPDATE_DETAILS table.
Explanation:
Action Manager writes into the AM_UPDATE_DETAILS table, to indicate that a rule has been modified, so that the database modification listener thread can pick up this modification notification, and appropriately modify listener threads. An error occurred while trying to insert information in the AM_UPDATE_DETAILS table. This may have occurred if the database is down, or due to some other internal error.
Operator response:
Verify that the database is running. Look at the exception trace in the log.
CTGDJB544E
Error occurred while trying to delete all data from the AM_UPDATE_DETAILS table.
Explanation:
On startup, the Action Manager clears all the data from the AM_UPDATE_DETAILS table, since it is anyways going to construct all threads again. Due to some database error, Action Manager was unable to clear the data from this table.
Operator response:
Verify that the database is running. Look at the exception trace in the log.
CTGDJB545I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB546I
Created Action Manager thread for
[Config]: Config instance
Explanation:
This is an informational message only.
CTGDJB547I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB548I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB549I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB550E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for AssemblyLine Terminated type of trigger). This may occur, because the database is down, or some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs. Ensure that the database is running in network mode. It is recommended to start Action Manager first, and the Administration and Monitoring Console later. Action Manager will start the database in network mode, to which the Administration and Monitoring Console can later connect.
CTGDJB551E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB552E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine terminate listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB553E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register AssemblyLine terminate listener.
Explanation:
The Action Manager was unable to create a thread because it could not register an AssemblyLine terminate listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB554I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine
Explanation:
This is an informational message only.
CTGDJB555I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB556I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB557I
DBConnectionFactory instance created.
Explanation:
This is an informational message only.
CTGDJB558I
Derby network server already running.
Explanation:
This is an informational message only.
CTGDJB559I
Unable to ping Derby network server. Attempting to start.
Explanation:
This is an informational message only.
CTGDJB560I
Started Derby network server.
Explanation:
This is an informational message only.
CTGDJB561E
Unable to start Derby network server. Database unavailable.
Explanation:
The Action Manager was unable to start Derby network server. This may occur if there is an error in the JDBC URLs specified in the am_config.properties. The Action Manager connects to the Administration and Monitoring Console's database using Derby in network mode. If the specified Derby database does not exist, or is booted in embedded mode, then Action Manager cannot connect to the database or start the database in network mode. To create the database, the Administration and Monitoring Console must have been started at least once. Action Manager will start the database in network mode, in case its not running in network mode already.
Operator response:
Ensure that the JDBC settings in the am_config.properties file are correct, and
pointing to the Administration and Monitoring Console's Derby database. Ensure that the Administration and Monitoring Console is not already connected to
the database in Embedded mode. The recommended procedure is as follows:
1) Ensure that the Administration and Monitoring Console's database exists. If not, start the Administration and Monitoring Console. On starting the Administration and Monitoring Console for the first time, the
Derby database is automatically created.
2) Shutdown the Administration and Monitoring Console and reconfigure it to connect to the database in network mode (if not already
configured for network mode).
3) Start Action Manager. Action Manager will start the database in network mode.
4) Start the Administration and Monitoring Console, which will also connect to the same database over network mode.
CTGDJB561W
Error while closing database Statement.
Explanation:
Action Manager encountered some database error which caused statement.close() API to fail.
Operator response:
Ensure that the database is running in network mode, and see the exception trace for more details.
CTGDJB562W
Error while closing database ResultSet.
Explanation:
Action Manager encountered some database error which caused resultSet.close() API to fail.
Operator response:
Ensure that the database is running in network mode, and see the exception trace for more details.
CTGDJB563W
Error while closing database Connection.
Explanation:
Action Manager encountered some database error which caused connection.close() API to fail.
Operator response:
Ensure that the database is running in network mode, and see the exception trace for more details.
CTGDJB564I
Rule rule name not triggered since event data did not match.
Explanation:
This is an informational message only.
CTGDJB565I
Rule rule name not triggered since event source did not match.
Explanation:
This is an informational message only.
CTGDJB566I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB567E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for Event Received type of trigger). This may occur, because the database is down, or some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs. Ensure that the database is running in network mode. It is recommended to start Action Manager first, and the Administration and Monitoring Console later. Action Manager will start the database in network mode, to which the Administration and Monitoring Console can later connect.
CTGDJB568E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB569E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine terminate listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB570E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register specified Event listener.
Explanation:
The Action Manager was unable to create a thread because it could not register an event listener as per the user specified parameters.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB571I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine
Explanation:
This is an informational message only.
CTGDJB572I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB573I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB574W
Unable to get list of running AssemblyLines for Solution View: Solution View. Ignoring Health AssemblyLine for this Solution view.
Explanation:
The Action Manager was unable to determine the list of running AssemblyLines for this Solution view. For this reason, it ignored any health AssemblyLine defined for this Solution view. This may happen if there is an error in the Config instance associated with this Solution view.
Operator response:
Ensure the remote server API is on. Verify that the Config instance associated with this Solution view is running. Action Manager will ignore the Health AssemblyLine for this Solution view, until the next interval.
CTGDJB575W
Unable to obtain Config Instance associated with the Solution View: Solution View. Ignoring Health AssemblyLine for this Solution view.
Explanation:
The Action Manager was unable to obtain a handle to the Config instance associated with this Solution view. This may happen because the Config is not loaded on the server.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. Also, Verify that the Config instance associated with this Solution view is running. No action required, if the user does not expect the Config to be loaded currently. Action Manager will ignore the Health AssemblyLine for this Solution view, until the next interval.
CTGDJB576E
Unable to obtain list of Health AssemblyLines for Solution Views.
Explanation:
The Action Manager was unable to read the list of Health AssemblyLines from the CONFIG_VIEW_HEALTH_AL_DETAILS table in database. Some internal database error may have occurred.
Operator response:
Ensure that the database is running in network mode, and the CONFIG_VIEW_HEALTH_AL_DETAILS table is not corrupted. Try again.
CTGDJB577I
Updating Health AssemblyLine status in database for Solution view
Solution View ID.
[HealthAL Result]: result.
[HealthAL Status]: status_description.
Explanation:
This is an informational message only.
CTGDJB578E
Error updating Health AssemblyLine status in database for Solution view
Solution View ID.
[HealthAL Result]: result.
[HealthAL Status]: status_description.
Explanation:
The Action Manager was unable to update the Health AssemblyLine status in CONFIG_VIEW_HEALTH_STATUS table in database. Some internal database error may have occurred.
Operator response:
Ensure that the database is running in network mode, and the CONFIG_VIEW_HEALTH_STATUS table is not corrupted / locked. See accompanying exception trace.
CTGDJB579I
Creating Health AssemblyLine Listener thread for
[Solution View]: Solution View ID.
[Config]: Config instance.
[AssemblyLine]: AssemblyLine name.
Explanation:
This is an informational message only.
CTGDJB580W
Unable to obtain session with remote TDI server for Health AssemblyLine: AssemblyLine name.
Explanation:
The Action Manager was unable to obtain a session with the remote TDI server for the Solution view associated with this Health AssemblyLine. The remote TDI server may have shut down.
Operator response:
Ensure that the remote TDI server is running, and the remote server API is on. Action Manager will ignore the Health AssemblyLine for this Solution view, until the next interval.
CTGDJB581E
Unable to create base listener for Health AssemblyLine: AssemblyLine name.
Explanation:
The Action Manager was unable to create a Health AssemblyLine terminate listener thread because it could not create a DIEventListener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB582E
Unable to register stop AssemblyLine listener for Health AssemblyLine: AssemblyLine name.
Explanation:
The Action Manager was unable to create a Health AssemblyLine terminate listener thread because it could not register an Health AssemblyLine stop listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB583E
Unable to start Health AssemblyLine:AssemblyLine name
Explanation:
The Action Manager was unable to run the Health AssemblyLine because of some internal error. See exception trace.
Operator response:
See the accompanying exception trace.
CTGDJB584E
Result work entry is null in Health AssemblyLine: AssemblyLine name. No Health status update will be done in database.
Explanation:
The Health AssemblyLine returned a null work entry object.
Operator response:
Check the Health AssemblyLine.
CTGDJB585I
In Health AssemblyLine AssemblyLine name
healthAL.result attribute value is: attribute_value.
Explanation:
This is an informational message only.
CTGDJB586I
In Health AssemblyLine AssemblyLine name
healthAL.status attribute value is: attribute_value.
Explanation:
This is an informational message only.
CTGDJB587I
Terminating Health AssemblyLine thread for
[Solution View]: Solution View ID
[Config]: Config instance
[AssemblyLine]: AssemblyLine name
Explanation:
This is an informational message only.
CTGDJB588E
Unable to obtain handle to AssemblyLine object for Health AssemblyLine: AssemblyLine name
Explanation:
The Action Manager was unable to obtain a handle to Health AssemblyLine. This may have occurred because the Health AssemblyLine terminated before the Stop Event listener was registered, or the AssemblyLine does not exist.
Operator response:
Put a sleep() of about 5 to 10 seconds to slow down the execution of the Health AssemblyLine and try again. Ensure the health AssemblyLine exists in the specified Config.
CTGDJB588W
Unable to remove event listener registered for AssemblyLine terminate events for
[Solution View]: Solution View ID
[Config]: Config instance
[AssemblyLine]: AssemblyLine name
Explanation:
Due to an internal error, Action Manager was unable to remove event listener configured for listening to Health AssemblyLine termination events.
Operator response:
Ensure that the remote TDI server is of the version 6.1.1 or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB589I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB590E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for Property Value listener type of trigger).
Operator response:
Check the exception trace following this message in the logs. Ensure that the time units were correctly specified.
CTGDJB591E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB592E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to obtain Config Instance: Config Instance.
Explanation:
The Action Manager was unable to create a thread because it could not obtain a handle to the Config instance on the remote server.
Operator response:
Verify that the Config Instance associated with this Solution View is loaded.
CTGDJB593E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
[Config Instance]: Config Instance.
Unable to obtain handle to TDI Properties object.
Explanation:
The Action Manager was unable to create a thread because it could not obtain a handle to the TDI Properties object.
Operator response:
Verify that the remote TDI Server is of version 6.1.1 or higher. Try reloading the Config and try again.
CTGDJB594I
Created Action Manager thread for
[Config]: Config instance
Explanation:
This is an informational message only.
CTGDJB595I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB596E
Error in
[Rule]: rule name
[Solution View]: Solution View name
The property values cannot be compared since one of the property is not a valid integer.
[Key]: property name
[Current Value]: property value
[Compared to value]: value
Explanation:
The Action Manager was unable to check triggering condition because the property value or the value to be compared to are not integers.
Operator response:
Ensure that the specified property has an integer value, and that the value to be compared to is also a valid integer.
CTGDJB597E
Error in
[Rule]: rule name
[Solution View]: Solution View name
Unable to determine triggering condition.
Explanation:
The Action Manager was unable to determine triggering condition because an error occurred. Check the exception trace for more details.
Operator response:
See the accompanying exception for more details.
CTGDJB598I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB599I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB600E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for Query AssemblyLine result type of trigger).
Operator response:
Check the exception trace following this message in the logs. Ensure that the time units were correctly specified.
CTGDJB601E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB602I
The Config instance Config instance is not running. Will obtain handle to AssemblyLine later.
Explanation:
This is an informational message only.
CTGDJB603E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB604E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register AssemblyLine listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and the remote server API is on. See the accompanying exception trace.
CTGDJB605I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine
Explanation:
This is an informational message only.
CTGDJB606I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB607I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB608W
Unable to obtain handle to AssemblyLine object for AssemblyLine: AssemblyLine name
Explanation:
This may have happened because the AssemblyLine does not exist, or some internal error occurred.
Operator response:
Check the AssemblyLine and the accompanying exception trace.
CTGDJB609E
Result work entry is null in AssemblyLine: AssemblyLine name. Rule will not be triggered.
Explanation:
The AssemblyLine returned a null work entry object.
Operator response:
Check the AssemblyLine.
CTGDJB610E
No value found for attribute attribute name. in result work entry. Rule will not be triggered.
Explanation:
The AssemblyLine work entry does not contain a value for the specified attribute.
Operator response:
Check the AssemblyLine.
CTGDJB611I
Attribute attribute name value is attribute value.
Explanation:
This is an informational message only.
CTGDJB612E
Error in
[Rule]: rule name
[Solution View]: Solution View name
The attribute values cannot be compared since one of the values is not a valid integer.
[Attribute]: Attribute name
[Current Value]: Attribute value
[Compared to value]: value
Explanation:
The Action Manager was unable to check triggering condition because the attribute value or the value to be compared to are not integers.
Operator response:
Ensure that the specified attribute has an integer value, and that the value to be compared to is also a valid integer. Check the AssemblyLine and the Action Manager rule definition.
CTGDJB613W
Unable to obtain handle to AssemblyLine object for AssemblyLine:
AssemblyLine name
Cannot obtain result work entry.
Explanation:
This may have happened because the AssemblyLine does not exist, or some internal error occurred.
Operator response:
Check the AssemblyLine and the accompanying exception trace.
CTGDJB614E
An error occurred while executing an action.
[Solution View]: Solution View name
[Rule]: Rule name
[Action Order]: sequence order
[Action Type]: action type
Explanation:
Action Manager encountered an error when executing actions. See the accompanying messages or exception trace to get more details.
Operator response:
See the error messages or exception trace.
CTGDJB615I
Action successfully executed.
[Solution View]: Solution View name
[Rule]: Rule Name
[Action Order]: sequence_order
[Action Type]: action_type
Explanation:
This is an informational message only.
CTGDJB616E
An error occurred while executing an action.
[Solution View]: Solution View name
[Rule]: Rule Name
Explanation:
Action Manager encountered an error when executing actions. See the accompanying messages or exception trace to get more details.
Operator response:
See the error messages or exception trace.
CTGDJB617E
Unable to insert/commit into AM_RUN_HISTORY table.
Explanation:
Action Manager encountered an error when storing the action execution details into AM_RUN_HISTORY table.
Operator response:
See the error messages or exception trace.
CTGDJB618E
Unable to obtain rule information from AM_ACTION_DETAILS_RULE table.
Explanation:
Action Manager encountered an error when reading the action details from AM_ACTION_DETAILS_RULE table in database.
Operator response:
See the error messages or exception trace.
CTGDJB619E
Unable to obtain rule information from AM_RULES_MASTER table.
Explanation:
Action Manager encountered an error when reading the action details from AM_RULES_MASTER table in database.
Operator response:
See the error messages or exception trace.
CTGDJB620I
Triggering rule rule name of Solution view Solution View.
Explanation:
This is an informational message only.
CTGDJB621E
Unable to obtain log information from AM_ACTION_DETAILS_WRITE_LOG table.
Explanation:
Action Manager encountered an error when reading the log action details from AM_ACTION_DETAILS_WRITE_LOG table in database.
Operator response:
See the error messages or exception trace.
CTGDJB622I
[Message]: log message
[Description]: log description
Explanation:
This is an informational message only.
CTGDJB623E
Unable to write log information to AM_LOGS table.
Explanation:
Action Manager encountered an error when writing the log action to AM_LOGS table in database.
Operator response:
See the error messages or exception trace.
CTGDJB624E
Unable to read action information from AM_ACTION_DETAILS_COPY_PROPERTY table.
Explanation:
Action Manager encountered an error when reading action information from AM_ACTION_DETAILS_COPY_PROPERTY table in database.
Operator response:
See the error messages or exception trace.
CTGDJB625E
Unable to obtain Config instance for Config: Config instance.
Explanation:
Action Manager could not obtain Config instance for Copy Property Action. Check if the specified Config instance is loaded on the TDI Server.
Operator response:
See the error messages or exception trace.
CTGDJB626E
Unable to copy properties.
Explanation:
Action Manager could not execute the copy property action. See accompanying exception.
Operator response:
See the error messages or exception trace. Verify that the destination property store is not read-only.
CTGDJB627E
Unable to obtain property information.
Explanation:
Action Manager encountered an error when reading action information from AM_ACTION_DETAILS_PROPERTY_MODIFY table in database.
Operator response:
See the error messages or exception trace.
CTGDJB628E
Unable to obtain Config instance for Config: Config instance.
Explanation:
Action Manager could not obtain Config instance for Modify Property Action. Check if the specified Config instance is loaded on the TDI Server.
Operator response:
See the error messages or exception trace.
CTGDJB629E
Unable to modify property to new value: value.
Explanation:
Action Manager could not execute the modify property action. See accompanying exception.
Operator response:
See the error messages or exception trace. Verify that the destination property store is not read-only.
CTGDJB630E
Unable to obtain Event information.
Explanation:
Action Manager encountered an error when reading action information from AM_ACTION_DETAILS_NOTIFY_EVENT table in database.
Operator response:
See the error messages or exception trace.
CTGDJB631E
Unable to send Event notification.
Explanation:
Action Manager encountered an error when trying to send an Event notification.
Operator response:
See the error messages or exception trace.
CTGDJB632E
Unable to enable rule.
Explanation:
Action Manager encountered an error when trying to read rule information from database.
Operator response:
See the error messages or exception trace.
CTGDJB633E
Unable to disable rule.
Explanation:
Action Manager encountered an error when trying to read rule information from database.
Operator response:
See the error messages or exception trace.
CTGDJB634E
Unable to enable rule rule name
Explanation:
Action Manager encountered an error when trying to update rule information in AM_RULES_MASTER table in database.
Operator response:
See the error messages or exception trace.
CTGDJB635E
Unable to disable rule rule name
Explanation:
Action Manager encountered an error when trying to update rule information in AM_RULES_MASTER table in database.
Operator response:
See the error messages or exception trace.
CTGDJB636E
Unable to enable rule.
Explanation:
Action Manager encountered an error when trying to update rule information in database.
Operator response:
See the error messages or exception trace.
CTGDJB637E
Unable to disable rule.
Explanation:
Action Manager encountered an error when trying to update rule information in database.
Operator response:
See the error messages or exception trace.
CTGDJB638E
Unable to obtain AssemblyLine information.
Explanation:
Action Manager encountered an error when trying to read AssemblyLine information from AM_ACTION_DETAILS_AL table in database.
Operator response:
See the error messages or exception trace.
CTGDJB639E
Unable to obtain session for stopping AssemblyLine AssemblyLine name with remote TDI server.
Explanation:
Action Manager encountered an error when trying to obtain session for remote TDI server associated with this AssemblyLine.
Operator response:
The remote TDI server may be down, or remote server API engine may not be running.
CTGDJB640E
Config Config instance is not loaded on the remote server.
Explanation:
Action Manager could not obtain Config instance while attempting to stop the specified AssemblyLine (Stop AssemblyLine Action). Since, Config is not loaded, the AssemblyLine cannot be running. Action Manager has ignored this action.
Operator response:
See explanation. Check the action information.
CTGDJB641E
Unable to stop AssemblyLine: AssemblyLine name.
Explanation:
Action Manager could not stop the specified AssemblyLine. See the associated exception for details.
Operator response:
See associated exception trace.
CTGDJB642E
AssemblyLine: AssemblyLine name is not running on the Config instance: Config instance
Explanation:
Action Manager could not stop the specified AssemblyLine since it was already not running on the specified Config instance.
Operator response:
See explanation.
CTGDJB643E
Unable to obtain AssemblyLine information.
Explanation:
Action Manager encountered an error when trying to read AssemblyLine information from AM_ACTION_DETAILS_AL table in database.
Operator response:
See the error messages or exception trace.
CTGDJB644E
Unable to obtain session for starting AssemblyLine AssemblyLine name with remote TDI server.
Explanation:
Action Manager encountered an error when trying to obtain session for remote TDI server associated with this AssemblyLine.
Operator response:
The remote TDI server may be down, or remote server API engine may not be running.
CTGDJB645I
Config Config instance is not loaded on the remote server. Attempting to load it now.
Explanation:
This is an informational message only.
CTGDJB646E
Unable to start Config instance Config instance
Explanation:
Action Manager encountered an error when trying to load Config on the remote machine.
Operator response:
Ensure that the complete path of the Config was specified (forward slashes), and it exists on the remote machine.
CTGDJB647E
Unable to start AssemblyLine AssemblyLine name
Explanation:
Action Manager encountered an error when trying to start AssemblyLine on the remote machine.
Operator response:
Ensure that the AssemblyLine exists in the specified Config.
CTGDJB648I
TDI Session Generator Created.
Explanation:
This is an informational message only.
CTGDJB649I
Trying to establish connection to: server : port.
Explanation:
This is an informational message only.
CTGDJB650I
Custom Authentication with username: username.
Explanation:
This is an informational message only.
CTGDJB651E
Unable to obtain session with remote TDI Server:
server : port.
Explanation:
Action Manager was unable to obtain session with remote TDI server. The server may be down, or the remote server API engine may be OFF. Also, possible that Custom Authentication is on, or SSL is on, and the configuration is incorrect.
Operator response:
Ensure the remote TDI server can be contacted via remote server API. Users can check connection details with tdisrvctl utility.
CTGDJB652I
Started Action Manager Status Update thread.
Explanation:
This is an informational message only.
CTGDJB653E
Unable to update status of Action Manager.
Explanation:
The Action Manager was not able to update the status of Action Manager in the FLAG_HOLDER table in database. Some internal database error may have occurred.
Operator response:
Ensure that the database is running in network mode, and the FLAG_HOLDER table is not corrupted. Try again.
CTGDJB654I
ServerConfigHandler created.
Explanation:
This is an informational message only.
CTGDJB655E
ServerStatusListener thread unable to update server status.
Explanation:
The ServerStatusListener thread was unable to update current status of remote server.
Operator response:
Ensure that the database is running in network mode. See accompanying exception trace.
CTGDJB656E
Unable to create ConfigLoadReloadListener thread for
[SERVER_ID]: Server ID.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering a config load reload event.
Operator response:
Ensure the remote server API is on. See the accompanying exception trace.
CTGDJB657E
Unable to create ConfigLoadReload Thread for
[SERVER_ID]: Server ID.
Unable to register ConfigLoadReloadListener.
Explanation:
The Action Manager was unable to create a thread because it was unable to register a DIEventListener with remote server.
Operator response:
Ensure the remote server API is on. See the accompanying exception trace.
CTGDJB658E
Unable to remove EventListener for
[SERVER_ID]: Server ID.
Unable to remove event listener.
Explanation:
The Action Manager was unable to remove event listener registered with remote server.
Operator response:
Verify that remote server associated with the Solution view is running. See accompanying exception trace.
CTGDJB659I
Started AMCServerModificationListener thread.
Explanation:
This is an informational message only.
CTGDJB660E
Unable to create ServerStatusListener threads.
Explanation:
The Action Manager was unable to create ServerStatusListener threads.
Operator response:
See the accompanying exception trace. Try running Action Manager again.
CTGDJB661I
Checking for any Administration and Monitoring Console Server updates.
Explanation:
This is an informational message only.
CTGDJB662E
Unable to obtain connection to the Administration and Monitoring Console database.
Explanation:
The Action Manager was unable to obtain a connection to the Administration and Monitoring Console database. This may occur if there is an error in the JDBC URLs specified in the am_config.properties. The Action Manager connects to the Administration and Monitoring Console's database using Derby in network mode. If the specified Derby database does not exist, or is booted in embedded mode, then Action Manager cannot connect to the database. To create the database, the Administration and Monitoring Console must have been started at least once. Action Manager will start the database in network mode, in case its not running in network mode already. This could also happen, if the database shutdown (maybe because the Administration and Monitoring Console was shutdown). This will happen, only if the Administration and Monitoring Console had booted the database, and now the Administration and Monitoring Console has been shutdown. It is recommended that to avoid this situation, start Action Manager first, and then start the Administration and Monitoring Console.
Operator response:
Ensure that the JDBC settings in the am_config.properties file are correct, and
pointing to the Administration and Monitoring Console's Derby database. Ensure that the Administration and Monitoring Console
is not already connected to the database in Embedded mode. The recommended procedure is as follows:
1) Ensure that the Administration and Monitoring Console's database exists. If not, start the Administration and Monitoring Console.
On starting the Administration and Monitoring Console for the first time, the Derby database is automatically created.
2) Shutdown the Administration and Monitoring Console and reconfigure it to connect to the database in network mode (if not already
configured for network mode).
3) Start Action Manager. Action Manager will start the database in network mode.
4) Start the Administration and Monitoring Console, which will also connect to the same database over network mode.
CTGDJB663E
Unable to obtain connection to the Administration and Monitoring Console database.
Explanation:
The Action Manager was unable to obtain a connection to database. This may occur if there is an error in the JDBC URLs specified in the am_config.properties. The Action Manager connects to the Administration and Monitoring Console's database using Derby in network mode. If the specified Derby database does not exist, or is booted in embedded mode, then Action Manager cannot connect to the database. To create the database, the Administration and Monitoring Console must have been started at least once. Action Manager will start the database in network mode, in case its not running in network mode already. This could also happen, if the database shutdown (maybe because the Administration and Monitoring Console was shutdown). This will happen, only if the Administration and Monitoring Console had booted the database, and now the Administration and Monitoring Console has been shutdown. It is recommended that to avoid this situation, start Action Manager first, and then start the Administration and Monitoring Console.
Operator response:
Ensure that the JDBC settings in the am_config.properties file are correct, and
pointing to the Administration and Monitoring Console's Derby database. Ensure that the
Administration and Monitoring Console is not already connected to
the database in Embedded mode. The recommended procedure is as follows:
1) Ensure that the Administration and Monitoring Console's database exists. If not, start the
Administration and Monitoring Console. On starting the Administration and Monitoring Console for the first time, the
Derby database is automatically created.
2) Shutdown the Administration and Monitoring Console and reconfigure it to connect to the database in network mode (if not already
configured for network mode).
3) Start Action Manager. Action Manager will start the database in network mode.
4) Start the Administration and Monitoring Console, which will also connect to the same database over network mode.
CTGDJB664E
Exception while constructing Action Manager threads.
Explanation:
The Action Manager was unable to create listener threads because some internal error occurred. See the logs, or accompanying exception trace for more information.
Operator response:
See the associated exception trace for reasons of error. Try running Action Manager again.
CTGDJB665I
ServerStatusListener thread started for server
[SERVER_NAME]: Server Name.
Explanation:
This is an informational message only.
CTGDJB666I
ConfigLoadReloadListener thread started for server
[SERVER_NAME]: Server Name.
Explanation:
This is an informational message only.
CTGDJB667E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB668E
ServerStatusListener unable to check server restart status.
Explanation:
The Action Manager was unable to check whether server has been restarted.
Operator response:
Verify that the remote TDI server is running and remote Server API engine is enabled on that server.
CTGDJB669I
[SERVER_NAME]: Server Name has been restarted in polling interval.
Rule threads will be terminated and re-created.
Explanation:
This is an informational message only.
CTGDJB670E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB671E
Action Manager was unable to create Action Manager Thread for the following rule:
[Rule]: rule name
[Reason]: Unable to connect to server Server Name.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and remote Server API engine is enabled on that server.
CTGDJB672E
Error occurred while trying to delete data from the AM_SERVER_UPDATE_DETAILS table.
Explanation:
The ServerModificationListener thread, checks if any servers registered with the Administration and Monitoring Console has been modified. This thread has encountered a database exception while trying to delete data from the AM_SERVER_UPDATE_DETAILS table. This could have happened if the Administration and Monitoring Console database has been shutdown, or some other internal error occurred.
Operator response:
Verify that the database is running. Look at the exception trace in the log.
CTGDJB673E
Config Config instance is not loaded on the remote server so ActionManager cannot query the AssemblyLine result.
Explanation:
The Query AssemblyLine trigger starts the AssemblyLine in the user specified time interval and on AssemblyLine termination inspects the result. Here the config associated with the AssemblyLine is not loaded on server and so ActionManager cannot start the AssemblyLine.
Operator response:
Load the config on the remote server.
CTGDJB674E
Unable to start AssemblyLine AssemblyLine name
Explanation:
Action Manager encountered an error when trying to start AssemblyLine on the remote machine.
Operator response:
Ensure that the AssemblyLine exists in the specified config.
CTGDJB675I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB676E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for Query AssemblyLine result type of trigger).
Operator response:
Check the exception trace following this message in the logs. Ensure that the time units were correctly specified.
CTGDJB677E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and that the remote Server API engine is enabled on that server.
CTGDJB678I
The Config instance Config instance is not running. Will obtain handle to AssemblyLine later.
Explanation:
This is an informational message only.
CTGDJB679E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine listener.
Operator response:
Ensure that the remote TDI server is a 6.1.1 server, and that the remote server API is on. See the accompanying exception trace.
CTGDJB680E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register AssemblyLine listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server, and the remote server API is on. See the accompanying exception trace.
CTGDJB681I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine name
Explanation:
This is an informational message only.
CTGDJB682I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB683I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB684W
Unable to obtain handle to AssemblyLine object for AssemblyLine: AssemblyLine name
Explanation:
Failure to obtain a handle for this AssemblyLine may indicate that the AssemblyLine does not exist or some internal error occurred.
Operator response:
Check the AssemblyLine and the accompanying exception trace.
CTGDJB685E
Result work entry is null in AssemblyLine: AssemblyLine name. Rule will not be triggered.
Explanation:
The AssemblyLine returned a null work entry object.
Operator response:
Check the AssemblyLine.
CTGDJB686E
No value found for attribute attribute name. in result work entry. Rule will not be triggered.
Explanation:
The AssemblyLine work entry does not contain a value for the specified attribute.
Operator response:
Check the AssemblyLine.
CTGDJB687I
Attribute attribute name value is attribute value.
Explanation:
This is an informational message only.
CTGDJB688E
Error in
[Rule]: rule name
[Solution View]: Solution View name
The attribute values cannot be compared since one of the values is not a valid integer.
[Attribute]: Attribute name
[Current Value]: Attribute value
[Compared to value]: value
Explanation:
The Action Manager was unable to check the triggering condition because the attribute value or the value to be compared to are not integers.
Operator response:
Ensure that the specified attribute has an integer value, and that the value to be compared to is also a valid integer. Check the AssemblyLine and the Action Manager rule definition.
CTGDJB689W
Unable to obtain handle to AssemblyLine object for AssemblyLine:
AssemblyLine name
Cannot obtain result work entry.
Explanation:
This may have happened because the AssemblyLine does not exist, or some internal error occurred.
Operator response:
Check the AssemblyLine and the accompanying exception trace.
CTGDJB690I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: Inspect AssemblyLine Exit code.
Explanation:
This is an informational message only.
CTGDJB691I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On AssemblyLine start
Explanation:
This is an informational message only.
CTGDJB692I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On config load
Explanation:
This is an informational message only.
CTGDJB693I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On config unload
Explanation:
This is an informational message only.
CTGDJB694I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: Timer
Explanation:
This is an informational message only.
CTGDJB695E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (AssemblyLine start type trigger). This may occur because the database is down, or because some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs. Ensure that the database is running in network mode.
CTGDJB696E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and that the remote Server API engine is enabled on that server.
CTGDJB697E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering an AssemblyLine start listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and that the remote server API is on. See the accompanying exception trace.
CTGDJB698E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register AssemblyLine start listener.
Explanation:
The Action Manager was unable to create a thread because it could not register an AssemblyLine start listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and that the remote server API is on. See the accompanying exception trace.
CTGDJB699I
Rule rule name terminated.
Explanation:
This is an informational message only.
CTGDJB700I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB701E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for a config load type of trigger). This may occur, because the database is down, or because some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs. Ensure that the database is running in network mode.
CTGDJB702E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and that the remote Server API engine is enabled on that server.
CTGDJB703E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering a config load listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and that the remote server API is on. See the accompanying exception trace.
CTGDJB704E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register config load listener.
Explanation:
The Action Manager was unable to create a thread because it could not register a config load listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and that the remote server API is on. See the accompanying exception trace.
CTGDJB705I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine
Explanation:
This is an informational message only.
CTGDJB706I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine
Explanation:
This is an informational message only.
CTGDJB707I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB708E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (config unload type of trigger). This may occur because the database is down, or because some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs. Ensure that the database is running in network mode.
CTGDJB709E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to connect to remote TDI server.
Explanation:
The Action Manager was unable to create a thread because it could not connect to the remote TDI server associated with this Solution View.
Operator response:
Verify that the remote TDI server associated with this Solution View is running, and that the remote Server API engine is enabled on that server.
CTGDJB710E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to create base listener.
Explanation:
The Action Manager was unable to create a thread because it could not create a DIEventListener for registering a config unload listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and that the remote server API is on. See the accompanying exception trace.
CTGDJB711E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Unable to register config unload listener.
Explanation:
The Action Manager was unable to create a thread because it could not register a config load listener.
Operator response:
Ensure the remote TDI server is a 6.1.1 server or higher, and that the remote server API is on. See the accompanying exception trace.
CTGDJB712I
Created Action Manager thread for
[Config]: Config instance
[AssemblyLine]: AssemblyLine name
Explanation:
This is an informational message only.
CTGDJB713I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB714E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (timer type of trigger). This may occur because the database is down, or because some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs. Ensure that the database is running in network mode.
CTGDJB715I
Killing Action Manager thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
This is an informational message only.
CTGDJB716I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB717I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB718I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB719W
The Action manager RMI Registry is starting on default port port
Explanation:
The Action Manager registry is starting on the default port because is either not specified in the am.properties file OR the port specified is zero.
Operator response:
Check the am_config.properties file whether a valid port is provided for Action Manager registry.
CTGDJB720I
The Action Manager RMI registry is started on port port.
Explanation:
This is an informational message only.
CTGDJB721E
An exception occured while starting the Action Manager RMI Registry: exception
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB722W
The client information provided data value is not sufficient for extracting the client name and client version.
Explanation:
The client information should be provided as 'clientName_clientVersion'
Operator response:
The client information is not in the expected format; therefore the client name and client version cannot be retrieved.
CTGDJB723I
The System Security Manager is null. Using the Action Manager custom security manager instead.
Explanation:
This is an informational message only.
CTGDJB724I
The Action manager is resetting the System Security Manager to null.
Explanation:
This is an informational message only.
CTGDJB725I
Creating Action Manager thread for
[Solution View]: Solution View name
[Rule]: rule name
[Trigger Type]: On local variable.
Explanation:
This is an informational message only.
CTGDJB726E
Unable to create Action Manager Thread for
[Action Manager Rule Id]: Action Manager Rule ID
[Rule]: rule name
[Solution View]: Solution View name.
Explanation:
One or more errors occurred while trying to read the database for creating the Action Manager listener thread (for Action Manager local variable type of trigger). This may occur, because the database is down, or some internal database related error occurred.
Operator response:
Check the exception trace following this message in the logs.
CTGDJB727I
Rule rule name triggered.
Explanation:
This is an informational message only.
CTGDJB728E
Unable to modify local variable to new value: value
Explanation:
Action Manager could not execute the modify local action. See accompanying exception.
Operator response:
See the error messages or exception trace.
CTGDJB729E
An exception occurred while getting rule name details: exception
Explanation:
Refer to logs for additional details.
Operator response:
Refer to logs for additional details.
CTGDJB730E
An exception occurred while executing rule rule name: exception
Explanation:
Refer to logs for additional details.
Operator response:
Refer to logs for additional details.
CTGDJB731I
The rule rule name has no actions to be backed up.
Explanation:
This is an informational message only.
CTGDJB732E
An exception occurred while backing up the original values for rule rule name: exception
Explanation:
Refer to logs for additional details.
Operator response:
Refer to logs for additional details.
CTGDJB733I
The client info client info used for connecting with Action Manager is invalid.
Explanation:
This is an informational message only.
CTGDJB734I
The table AM_ACTION_DETAILS_WRITE_LOG is empty.
Explanation:
This is an informational message only.
CTGDJB735E
The API Listener is not able to create the Action Manager thread because of the exception: exception.
Explanation:
See message.
Operator response:
Refer to logs for additional details. Try again to create the API Failure Trigger.
CTGDJB736E
Action Manager was unable to obtain the Action Manager logs to be attached with the email.
Explanation:
Action Manager was unable to obtain the Action Manager logs to be attached with the email. The email will be sent without the logs.
Operator response:
Examine the am_logging.properties for the location of the Action Manager log file. Refer to logs for additional details.
CTGDJB737E
Action Manager was unable to obtain the host and port information of the SMTP server.
Explanation:
Action Manager was unable to obtain the host and port information of the SMTP server. As a result, the Send email action cannot be executed.
Operator response:
Specify the SMTP host and port information in the am_config.properties file. If authentication is required for the SMTP server, specify user and password properties.
CTGDJB738E
Action Manager was unable to create and send an email message.
Explanation:
This is an informational message only.
CTGDJB739E
Action Manager was unable to obtain the host and port information of the SMTP server from the Action Manager config file.
Explanation:
Action Manager was unable to obtain the host and port information of the SMTP server. As a result, the Send email action cannot be executed.
Operator response:
Specify the SMTP host and port information in the am_config.properties file. If authentication is required for the SMTP server, specify user and password properties. Refer to logs for additional information.
CTGDJB740E
Property java.util.logging.config.file is not set in startAM.bat(sh).
Explanation:
Action Manager was unable to initialize because the required property java.util.logging.config.file was not set. This property is required for finding the location of the Action Manager logging file am_logging.properties.
Operator response:
Ensure that in the startAM.bat(sh) file the java.util.logging.config.file property is being set to point to the location of the am_logging.properties file.
CTGDJB741E
Unable to load the am_logging.properties file. Check the value of java.util.logging.config.file property in the startAM.bat(sh). The current value is set to file path.
Explanation:
Action Manager was unable to initialize because the property java.util.logging.config.file in the startAM.bat(sh) file is pointing to an invalid location.
Operator response:
Ensure that in the startAM.bat(sh) file the java.util.logging.config.file property is being set to point to the location of the am_logging.properties file. See the associated exception trace.
CTGDJB742I
The target computer is the same as the Action Manager host.
Explanation:
This is an informational message only.
CTGDJB743W
The user name or keystore is set to property value and the password or keystore password is set to property value.
Explanation:
The target computer login details are not provided.
Operator response:
The user name and password of the target computer or the keystore and keystore password used for authenticating a user with the target computer should be provided.
CTGDJB744E
Failed to connect to the target computer using protocol protocol.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB745I
Failed to connect to the target computer using any of the supported protocols. Action Manager is assuming that command command is to be executed on localhost.
Explanation:
This is an informational message only.
CTGDJB746E
An error error occurred while executing the command command on action manager host hostname.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB747I
The command command is executed successfully on host hostname.
Explanation:
This is an informational message only.
CTGDJB748E
The command command execution failed on host hostname with exit code Integer.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB749E
An error occurred while executing the command command on host hostname: error
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB750E
The command command is not executed.
Explanation:
Verify the correctness of the command and the computer details.
Operator response:
Verify the correctness of the command and the computer details.
CTGDJB751E
An error was encountered while retrieving data from the database: error.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB752E
Failed to establish a connection with the target computer.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB753E
An error occurred while executing the command command.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB754W
Cannot rollback the properties changes because the config instance id is null.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB755E
An error occurred while rolling back the properties: error message
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB756E
An error occurred while rolling back the database changes: error message
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB757E
An error occurred while backing up the property: error message
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB758E
No command specified in the execute command action.
Explanation:
The execute command action is supposed to execute a command on the target computer. There is no command specified by the user.
Operator response:
Specify a valid command which needs to be executed on the target computer.
CTGDJB759E
Action Manager was unable to obtain local variable variable name.
Explanation:
The Action Manager was unable to obtain the specified local variable.
Operator response:
Restart Action Manager and verify that the database is running.
CTGDJB760E
Unable to obtain local variable information.
Explanation:
Action Manager encountered an error when reading action information from database.
Operator response:
See the error messages or exception trace.
CTGDJB761E
An error occurred while terminating thread for rule rule name: error.
Explanation:
Action Manager encountered an error when terminating a rule thread. from database.
Operator response:
See the error messages or exception trace.
CTGDJB762E
An error occurred while starting thread for rule rule name: error.
Explanation:
Action Manager encountered an error when starting a rule thread. from database.
Operator response:
See the error messages or exception trace.
CTGDJB763W
An error occurred while closing the database connection: error.
Explanation:
Action Manager encountered an error when closing a database connection. from database.
Operator response:
See the error messages or exception trace.
CTGDJB764W
An error occurred while checking for server updates: error
Explanation:
Action Manager encountered an error while checking for server updates. from database.
Operator response:
See the error messages or exception trace.
CTGDJB765I
An error occurred while closing the input stream of file file name: error.
Explanation:
Action Manager encountered an error while closing the input stream of a file. from database.
Operator response:
See the error messages or exception trace.
CTGDJB766E
An error occurred while starting thread: error
Explanation:
Action Manager encountered an error when starting a thread. from database.
Operator response:
See the error messages or exception trace.
CTGDJB767W
An error occurred while rolling back the database changes: error.
Explanation:
Action Manager encountered an error when rolling back the database changes.. from database.
Operator response:
See the error messages or exception trace.
CTGDJB768I
Action Manager trying to connect to hostname host using protocol protocol.
Explanation:
This is an informational message only.
CTGDJB769I
Action Manager failed to connect to hostname host using protocol protocol.
Explanation:
This is an informational message only.
CTGDJB770I
Password is null, hence failed to connect to hostname host using protocol protocol.
Explanation:
This is an informational message only.
CTGDJB771I
Failed to connect to hostname host using protocol protocol because either password or keystore or keystore password is not provided.
Explanation:
This is an informational message only.
CTGDJB772E
Failed to start Action Manager because an exception occurred: exception
Explanation:
An exception occurred while starting Action Manager. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB772I
Exiting Action Manager with error code error code.
Explanation:
This is an informational message only.
CTGDJB774E
An error occurred while initializing truststores: exception
Explanation:
An exception occurred while initializing truststores. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB775E
An error occurred while initializing keystores: exception
Explanation:
An exception occurred while initializing keystores. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB776E
An error occurred while initializing Action Manage RMI: exception
Explanation:
An exception occurred while initializing RMI. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB777E
Unable to establishing a connection to the database. An exception occurred: exception
Explanation:
An exception occurred while initializing DB Connection. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB778E
Unable to execute the rule rule name. An exception occurred: exception
Explanation:
An exception occurred while executing the rule. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB779E
An error occurred while rolling back the database changes for rule rule name: exception
Explanation:
An exception occurred while rolling back db changes. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB780E
An error occurred while rolling back the actions for rule rule name: exception
Explanation:
An exception occurred while rolling back actions. Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB781E
An error occurred while retrieving actions: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB782E
An error occurred while retrieving trigger types for Rule Id rule id: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB783E
An error occurred error message while retrieving rules for Server Id server id.
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB784E
An error occurred while retrieving rules for Config URL URL: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB785E
An error occurred while retrieving the Server version: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB786E
An error occurred while checking the Server version: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB787E
An error occurred while getting the Server name for Server Idserver id: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB788E
An error occurred while getting the triggered triggers: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB789E
An error occurred while getting the Rule Id for rule rule name: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB790E
An error occurred while getting the Config Instance for Solution View solution view name: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB791E
An error occurred while getting the Solution Id for Solution View solution view name: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB792E
An error occurred while getting the Solution View name for Solution Id solution id: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB793E
An error occurred while getting the action details for Rule Id rule id: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB794E
An error occurred while enabling/disabling a rule with Rule id rule id: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB795E
An error occurred while retrieving actions for rule with Rule ID rule id: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB796E
An error occurred while initializing of String encryption decryption utility: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB797I
Encryption scheme encryption scheme is not supported.
Explanation:
This is an informational message only.
CTGDJB798I
The string being encrypted is empty or null.
Explanation:
This is an informational message only.
CTGDJB799E
An error occurred while encrypting a string: error
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB800I
The string being decrypted is empty or null.
Explanation:
This is an informational message only.
CTGDJB801E
An error occurred while decrypting: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB802E
An error occurred while decrypting property: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB803E
An error occurred while encrypting property: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB804E
An error occurred while killing Action Manager thread: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB805W
An error occurred while executing command command: error message
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB806E
The hostname hostname is unknown. Exception occurred: exception
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB807E
An error occurred while unregistering the listener: error
Explanation:
Refer logs for additional information.
Operator response:
Refer logs for additional information.
CTGDJB808I
Executing the SQL command for rolling back the action.
Explanation:
This is an informational message only.
CTGDJB809I
Rolling back the properties changes made by force trigger.
Explanation:
This is an informational message only.
CTGDJB810E
An error occurred while rolling back the database transaction: error
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB811E
A threading exception has occured.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB812E
An error occurred while trying to kill the QueryAL listener thread.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB813E
A threading exception has occured.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB814E
A threading exception has occured.
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB815W
An exit code for the command execution cannot be displayed.
Explanation:
The exit code for the command execution cannot be displayed since the command may have spawned a daemon process or there may have been an error during command execution.Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.
CTGDJB816E
An error occurred while getting values for local Action Manager variable : error message
Explanation:
Refer to the logs for additional information.
Operator response:
Refer to the logs for additional information.