CTGDKK001E
Missing required parameter: parameter name.
Explanation:
A required parameter is not specified in the configuration.
Operator response:
Specify the required parameter.
CTGDKK002E
Parameter parameter name must be a number greater than number.
Explanation:
The value of the parameter is not appropriate.
Operator response:
Specify a proper value for the parameter in the configuration.
CTGDKK003E
Parameter parameter name must be a number greater than or equal to number.
Explanation:
The value of the parameter is not appropriate.
Operator response:
Specify a proper value for the parameter in the configuration.
CTGDKK004E
Parameter parameter name must be a number less than or equal to number.
Explanation:
The value of the parameter is not appropriate.
Operator response:
Specify a proper value for the parameter in the configuration.
CTGDKK005E
Parameter parameter name must be a number.
Explanation:
The provided value for the parameter is not a number.
Operator response:
Specify a number value for the parameter.
CTGDKK006E
Cannot create connection to Agent Controller.
Explanation:
Cannot create connection to the remote host on which the Agent Controller runs.
Operator response:
Verify that the host of the Agent Controller is accessible.
CTGDKK007I
Waiting number of milliseconds milliseconds for monitoring client...
Explanation:
This is an informational message only.
CTGDKK008I
Monitoring client has arrived.
Explanation:
This is an informational message only.
CTGDKK009E
No monitoring client has arrived.
Explanation:
No monitoring client has arrived within the predefined time window.
Operator response:
Make sure a client starts to monitor the Logging Agent, registered by the Connector, before the configured timeout expires.
CTGDKK010I
Waiting for monitoring client...
Explanation:
This is an informational message only.
CTGDKK011I
Monitoring client has arrived.
Explanation:
This is an informational message only.
CTGDKK012I
Started monitoring remote agent.
Explanation:
This is an informational message only.
CTGDKK013I
Remote Logging Agent is dead.
Explanation:
This is an informational message only.
CTGDKK014I
Data from dead agent depleted.
Explanation:
This is an informational message only.
CTGDKK015I
Logging Agent Life Monitoring thread interrupted.
Explanation:
This is an informational message only.
CTGDKK016I
Connection to remote AgentController disrupted.
Explanation:
This is an informational message only.
CTGDKK017E
Error while processing incoming data from the Logging Agent: exception
Explanation:
Could not read a Common Base Event out of the incoming data buffer.
Operator response:
Analyze the exception for more information. Check if the remote Logging Agent is functioning properly.
CTGDKK018E
Error while processing incoming data from the Logging Agent: exception
Explanation:
Could not read a Common Base Event out of the incoming character data.
Operator response:
Analyze the exception for more information. Check if the remote Logging Agent is functioning properly.
CTGDKK019W
Received invalid data from the remote Logging Agent.
Explanation:
The incoming data does not conform to the expected format.
Operator response:
Check if the remote Agent Controller is functioning properly and is compatible with the RAC Connector.
CTGDKK020I
Data Processor waiting for data...
Explanation:
This is an informational message only.
CTGDKK021E
Cannot parse the ConnectionTimeout parameter.
Explanation:
An illegal value for the ConnectionTimeout parameter has been passed.
Operator response:
The ConnectionTimeout value must be a positive number.
CTGDKK101E
The 'configFile' parameter must be set to use the GLA Connector.
Explanation:
The required parameter configFile is not set in the GLA Connector.
Operator response:
Specify the path to the adapter configuration file in the configFile parameter.
CTGDKK102E
The adapter configuration file is not valid: exception message.
Explanation:
The given configuration file is not valid. See the exception message for more information.
Operator response:
Correct the adapter configuration file and try again.
CTGDKK103I
The adapter configuration file is validated.
Explanation:
This is an informational message only.
CTGDKK104I
The adapter configuration file is started.
Explanation:
This is an informational message only.
CTGDKK105E
The execution of the adapter configuration file failed: Exception message
Explanation:
An Exception occurred during the execution of the adapter configuration file. See the Exception message for more information.
Operator response:
See the Exception message for more information.
CTGDKK106E
There is no registered GLAConnector matching the specified in the TDIOutputter 'tdi_correlation_id' parameter: Correlation ID.
Explanation:
The Hashtable of the TDIOutputter does not contain a Connector registered to the specified 'tdi_correlation_id'.
Operator response:
Specify a correct value in the TDIOutputter 'tdi_correlation_id' parameter.
CTGDKK107E
There are more than one configured TDIOutputters in the adapter configuration file.
Explanation:
The GLAConnector allows only one TDIOutputter to be configured in the adapter configuration file.
Operator response:
Put only one TDIOutputter in the adapter configuration file.
CTGDKK108E
An exception occurred while converting the XML file to Document object: exception message
Explanation:
There are several possible reasons for this exception. A DocumentBuilder may not have been able to be created which satisfied the configuration requested. An IO error occurred. Or, a parse error occurred.
Operator response:
See the Exception message for more information.
CTGDKK109E
The given adapter configuration file does not have a configured TDIOutputter.
Explanation:
The GLAConnector needs a TDIOutputter to be configured in the adapter configuration file in order to receive the CBE objects.
Operator response:
Set a TDIOutputter in the adapter configuration file and try again. Refer to the GLAConnector documentation about how to configure the TDIOutputter.
CTGDKK301E
The 'com.ibm.di.log.interface' parameter must be set to use the Log Connector.
Explanation:
The required parameter com.ibm.di.log.interface was not specified in the Log Connector.
Operator response:
Use a Logger with the com.ibm.di.log.interface parameter in the Connector.