2.1 Messages from KDEC00001 to KDEC19999 : Messages

KDEC00001-E

The service request was interrupted. (HCSCCommonID = aa....aa, ServiceRequestID = bb....bb, RootApInfo = cc....cc)

aa....aa: HCSC message common ID

Displays the identification information (message common ID) allocated to each request from service requesters.

bb....bb: Service request ID

Displays the identification information (service request ID) allocated to each service component invocation processing within the HCSC server.

cc....cc: Root application information

Displays the root application information (IP address, process ID, and communication number) of performance analysis traces maintained by the current thread, with a string expression.

Description: An attempt to process the service component invocation request failed.
(S): Interrupts the service component call request.
(O): Reference the message log file, error message output before this message, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the service component <Output destination directory>call request. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00002-E

There is an error in the service, or an error occurred when calling the service.

Description: A service component responded with an error or an error occurred while a service component was being invoked.
(S): Cancels the request processing.
(O): Reference either the Fault message in the SOAP Envelope sent as response to the service requester, the Fault message in exceptions, or the Fault message in the response queue set for asynchronous acceptance, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00003-E

There is an error in the business process, or an error occurred when calling the business process.

Description: A business process responded with an error or an error occurred while a business process was being invoked.
(S): Cancels the request processing.
(O): Reference either the Fault message in the SOAP Envelope sent as response to the service requester, the Fault message in exceptions, or the Fault message in the response queue set for asynchronous acceptance, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00005-E

The HCSC server request was interrupted. (request = aa....aa, information = bb....bb)

aa....aa: Query contents

getServiceInfo: Operation status confirmation function

bb....bb: Query detailed information

When the query contents are getServiceInfo: Outputs the information of the parameter specified from the service requester.

Description: A query request to the HCSC server failed.
(S): Interrupts the query request to the HCSC server.
(O): Reference the message log file, error message output before this message, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the query request to the HCSC server. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00010-E

The specified parameter is invalid. (parameter = aa....aa)

aa....aa: Parameter name

Description: The specified parameter is not a valid string.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the contents of the string specified in the parameter.

KDEC00011-E

A required parameter has not been specified. (parameter = aa....aa)

aa....aa: Parameter name

Description: A required parameter is not specified.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the specified contents of the required parameter.

KDEC00012-E

The length of the specified parameter is invalid. (parameter = aa....aa)

aa....aa: Parameter name

Description: The length of the specified parameter is invalid.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the length of the string specified in the parameter.

KDEC00013-E

The same parameter has been specified more than once. (parameter = aa....aa)

aa....aa: Parameter name

Description: The same parameter is specified multiple times.
(S): Cancels the request processing.
(O): Make sure that the parameter is not specified more than once.

KDEC00014-E

The specified parameter is invalid. (parameter = aa....aa)

aa....aa: Parameter name

Description: An incorrect parameter is specified.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the contents specified in the parameter.

KDEC00016-E

The specified parameter value is outside the valid range. (parameter = aa....aa)

aa....aa: Parameter name

Description: The specified parameter value is outside the valid range.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the range of the numeric value specified in the parameter.

KDEC00018-E

The specified parameter differs from the telegram type. (parameter = aa....aa)

aa....aa: Parameter name

Description: The message type of the specified parameter is invalid.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the contents specified in the parameter. In the case of an asynchronous request reception (MDB/WS-R), make sure that the value specified in the message type of the parameter matches with the message type in the queue.

KDEC00019-E

The specified JMS property is invalid. (property = aa....aa, JMSMessageID = bb....bb)

aa....aa: Property name

bb....bb: JMSMessageID

Description: The specified property is invalid.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the contents or type of the property specified in the queue of the asynchronous request reception (MDB/WS-R). Discard this message.

KDEC00020-E

The specified message type is invalid. (JMSMessageID = aa....aa)

aa....aa: JMSMessageID

Description: The specified message type is invalid.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the message type specified in the queue of the asynchronous request reception. Discard this message.

KDEC00021-E

The header part of the DBQueue message has an invalid format. (information = aa....aa)

aa....aa: Detailed information

Description: The header part of the database queue message has an invalid format during an asynchronous request reception (database queue).
(S): Cancels the request processing.
(O): Check, and if necessary, revise the format of the header (binary data) of the DBQueue message, and then re-execute the service component call request. Discard this message.

KDEC00022-E

The telegram is not an XML schema.

Description: The message is not an XML schema.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the specified message. Additionally, check and if necessary, revise the response message of the service component. If the cause of the error is associated with operations, eliminate the cause of the error, and then re-execute the processing. Discard this message.

KDEC00023-E

The specified option is invalid. (option = aa....aa)

aa....aa: Option name

Description: An incorrect option is specified.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the contents specified in the header (binary data) of the DBQueue message. Discard this message.

KDEC00024-E

Sending the message to the ReplyToQueue failed because an exception was caught. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Exception detail message

Description: The message could not be sent to the response queue because an exception was caught.
(S): Cancels response transmission to the response queue.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00025-E

Closing the queue used for sending failed because an exception was caught. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Exception detail message

Description: The queue used for sending could not be closed because an exception was caught.
(S): Cancels response transmission to the response queue.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00026-E

Making the error message for the service requester failed because an exception was caught. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Exception detail message

Description: The error message response to the service requester could not be created because an exception was caught.
(S): Cancels the response to the service requester.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00027-E

Making the error message for the service requester failed because the fault message is invalid.

Description: The error message for the service requester could not be created because the information about the person setting up the Fault message was invalid.
(S): Cancels the response to the service requester.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00028-E

The detailed information of the fault message is not an XML schema.

Description: The detailed information of the Fault message is not an XML schema.
(S): Cancels the response to the service requester.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00029-E

A database access error occurred when the execution history was output. (information = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Output timing

bb....bb: HCSC message common ID

Description: An error occurred when the execution log was output.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00030-E

The execution history could not be output because information in the data container was invalid. (information = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Output timing

bb....bb: HCSC message common ID

Description: The execution log could not be output because the information in the data container was invalid.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00031-W

At the asynchronous request receptor, the response telegram was scrapped because the queue name for ReplyTo was not specified.

Description: The response message was discarded because the response queue name was not specified in the asynchronous standard reception.
(S): Terminates processing.

KDEC00032-E

The specified JMSMessage payload is invalid. (JMSException = aa....aa)

aa....aa: Exception detail message

Description: The specified JMS message payload is invalid or the processing could not be continued because JMSException was caught.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the message specified in the queue of the asynchronous request reception. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00033-E

The length of the telegram in the DBQueue is invalid. (information = aa....aa)

aa....aa: Detailed information

Description: The length of the message specified in the asynchronous request reception (database queue) queue is invalid.
(S): Cancels the request processing.
(O): Check, and if necessary, revise the length of the message specified in the queue of the asynchronous request reception (DBQueue).

KDEC00034-E

The message could not be sent because a RemoteException was caught. (error message = aa....aa)

aa....aa: Exception detail message

Description: The message could not be sent because RemoteException was caught.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00035-E

The message could not be sent because an exception was caught. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Exception detail message

Description: The message could not be sent because an exception was caught.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00036-E

Service requests cannot be accepted because the request receptor status is incorrect. (status = aa....aa)

aa....aa: Request reception status

1: Starting

3: Start error

4: Stopped

5: Stopping

6: Stop error

Description: The service component requests are not accepted because the request reception status is invalid.
(S): Cancels the request processing.
(O): Check the status of the request reception.

KDEC00037-E

The asynchronous WS-R service request was interrupted. (ClientID = aa....aa, JMSMessageID = bb....bb)

aa....aa: Client ID

bb....bb: JMSMessageID

Description: The asynchronous WS-R request was interrupted.
(S): Cancels an asynchronous acceptance (WS-R) request.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00038-E

The asynchronous DBQueue service request was interrupted. (ClientID = aa....aa, JMSMessageID = bb....bb)

aa....aa: Client ID

bb....bb: JMS_HITACHI_ShqMessageID

Description: The asynchronous database queue request was interrupted.
(S): Cancels an asynchronous acceptance (database queue) request.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00039-E

Initialization of the User reception service adapter failed. (reception name = aa....aa, Reception ID = bb....bb, information = cc....cc)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Detailed information

Description: An attempt to initialize the user-defined reception failed.
(S): Interrupts the initialization of user-defined reception.
(O): An attempt to initialize the user-defined reception has failed. If the displayed Information is a message ID, reference the log file to check the corresponding error message, and identify the cause of the error log. If the cause of the error is associated with operations, re-execute the processing. If the displayed information is not an exception name or the cause of the error has nothing to do with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00040-E

An attempt to read the file has failed. (reception name = aa....aa, Reception ID = bb....bb, file name = cc....cc, information = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: File name

dd....dd: Detailed information

Description: An attempt to read the file failed.
(S): Interrupts the initialization of user-defined reception.
(O): Check, and if necessary, revise the configuration of the user-defined reception, and make sure that the file specified in file name is included. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00041-E

A value in the definition file is invalid. (reception name = aa....aa, Reception ID = bb....bb, parameter = cc....cc)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Parameter name

Description: The value of the user-defined reception specified in the definition file is invalid.
(S): Interrupts the initialization of user-defined reception.
(O): Check the information entered when the user-defined reception is created. If the information is modified, re-create the user-defined reception. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00042-E

The specified operation was not found. (reception name = aa....aa, reception ID = bb....bb, operation name = cc....cc, namespace = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Operation name

dd....dd: Namespace

Description: The specified operation does not exist.
(S): Processing of the request is interrupted.
(O): Make sure that the request is made with the correct operation name for a user-defined reception. For a SOAP reception, make sure that the request is made with the correct operation name and namespace in the requested SOAP message format. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00043-E

The telegram format is not supported. (reception name = aa....aa, reception ID = bb....bb, operation name = cc....cc, namespace = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Operation name

dd....dd: Namespace

Description: The message format is not supported.
(S): Processing of the request is interrupted.
(O): Make sure that the request is made with the correct message format for a user-defined reception. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00044-W

An exception occurred but processing will continue. (reception name = aa....aa, Reception ID = bb....bb, information1 = cc....cc, information2 = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Exception name

dd....dd: Message acquired from the exception

Description: An exception occurred in the request reception, but the processing will continue.
(S): Resumes processing.
(O): If the cause of the exception can be identified from the exception name or the message acquired from the exception, take appropriate action. Collect the log and trace information, and then contact the maintenance personnel.

KDEC00045-W

The SOAP 1.2 SOAPFault information will be converted to the SOAP 1.1 format. The response telegram might lack some SOAPFault information. (fault = aa....aa)

aa....aa: SOAPFault information

Description: The SOAP 1.2 SOAP Fault will be converted to the SOAP 1.1 format. The response message might lack some SOAPFault information.
(S): The processing continues.
(O): To avoid missing the information, change the reception used during the SOAP1.2 service invocation to SOAP1.2.

KDEC00046-E

The specified soap header was not found. (reception name = aa....aa, reception ID = bb....bb, soap header element name = cc....cc, namespace = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: SOAP header element name

dd....dd: Namespace

Description

The SOAP header specified in the definition file does not exist in the SOAP reception.

(S)

Processing of the request is interrupted.

(O)

Check the SOAP header that was entered when the SOAP reception was created, and make sure that the correct SOAP header element name and namespace are used to make the request.

If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00047-E

A timeout occurred while invoking the service.

Description

A timeout occurred while a service was being invoked.

(S)

An error response is returned to the requester and the processing of the service continues.

(O)

See the message log and communication log to check the progress status of the request.

Eliminate the cause of the error, or check and, if necessary, revise the timeout value.

KDEC00048-E

A request cannot be executed because there are no free threads.

Description

A request cannot be executed because there are no free threads.

(S)

Processing is interrupted.

(O)

The processing of another request might have timed out. Take one of the following actions:

Eliminate the cause of the timeout.
Check and reset the timeout value (urecp-ftp.request-timeout).
Check and reset the maximum number of instances (urecp-ftp.pooled-instance.maximum) and maximum number of threads (urecp-ftp.timer-thread.maximum) for a reception.

If you use the csccompoconfig command to change the maximum number of instances, make sure that the maximum number of threads (urecp-ftp.timer-thread.maximum) matches the changed value of the maximum number of instances.

KDEC00049-W

The number of times the asynchronous request receptor (MDB(WS-R)) acquired the same JMS message from the queue exceeded the limit, and a rollback was performed. (JMSXDeliveryCount = aa....aa, JMSMessageID = bb....bb, RootApInfo = cc....cc)

aa....aa: Number of message delivery attempts

bb....bb: JMSMessageID

cc....cc: Root application information

Displays a string expression for the root application information (IP address, process ID, and communication number) of the performance analysis trace maintained in the current thread.

Description: The same JMS message, obtained from the queue by the asynchronous request reception (MDB (WS-R)), exceeded the specified count, and a rollback was performed.
(S): Processing continues.
(O): See the message log file and the error messages displayed before this message to eliminate the cause of the error. If you cannot eliminate the cause of the error immediately, stop the standard reception.

KDEC00050-E

A response message returned from a business process is invalid. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Detailed message

Description: The header message returned from a business process is invalid.
(S): Processing is interrupted.
(O): See the information in the detailed message, and then correct the header message to be returned from the business process according to the urecp_soap_attachment_response.xsd specifications.

KDEC00051-E

No work folder root folder exists. (root path = aa....aa)

aa....aa: Root path of the work folder

Description: The root folder of the work folder does not exist.
(S): Processing is interrupted.
(O): Create the root folder of the work folder, and then re-execute the processing.

KDEC00052-E

An attempt to create a work folder has failed. (work folder path = aa....aa)

aa....aa: Path of the work folder

Description: An attempt to create a work folder failed.
(S): Processing is interrupted.
(O): Eliminate the cause due to which a directory cannot be created in the work folder path displayed in the message, and then re-execute the processing.

KDEC00053-E

An attempt to read the file has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Detailed message

Description: An attempt to read the file that is to be sent to the service requester failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00054-E

The host name cannot be resolved. (host name = aa....aa)

aa....aa: Host name

Description: The host name could not be resolved.
(S): Processing is interrupted.
(O): Make sure that the specified host name can be resolved, and then re-execute the processing.

KDEC00055-E

An error occurred while the MIME header of an attached file was being analyzed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Detailed message

Description: The header information of the attached file sent from the service requester is invalid.
(S): Processing is interrupted.
(O): See the information in the detailed message, and then correct the message that is to be sent from the service requester.

KDEC00056-E

An error occurred while an attached file was being received. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Detailed message

Description: An attempt to receive the attached file sent from the service requester failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00057-E

A parameter value in the reception definition file is invalid. (parameter = aa....aa, value = bb....bb)

aa....aa: Parameter name

bb....bb: Value

Description

A parameter value in the reception definition file is invalid.

(S)

Processing is interrupted.

(O)

Check and, if necessary, revise the parameter value in the SOAP reception definition file in which the error occurred. Then, take one of the following actions:

Change the definition by using the cscmctl command, and then redeploy and restart the SOAP application.
Change the definition in the development environment, and then redeploy and restart the SOAP application.

KDEC00058-E

An attempt to read the definition file has failed. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Message with exception details

Description: An attempt to read the reception definition file failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then redeploy the reception definition file.

KDEC00059-E

A value in the JSON-XML converter definition file is invalid. (reception name = aa....aa, reception ID = bb....bb, parameter = cc....cc, value = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Parameter name

dd....dd: Value

Description: A value in the JSON-XML transformation definition file is invalid.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the contents of the JSON-XML transformation definition file.

KDEC00060-E

An attempt convert JSON to XML failed. (reception name = aa....aa, reception ID = bb....bb, operation name = cc....cc, telegram type = dd....dd, error message = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Operation name

dd....dd: Message type before transformation

JSON: JSON message
XML: XML message

ee....ee: Message with exception details

Description: An attempt to perform JSON-XML transformation failed.
(S): Processing is interrupted.
(O): Check the message log file and the error message that was output before this message, and then eliminate the cause of the error. In addition, check and, if necessary, revise the specified message and the response message from the service.

KDEC00061-E

The value specified for an element in the header text is invalid. (reception name = aa....aa, reception ID = bb....bb, operation name = cc....cc, element name = dd....dd, namespace = ee....ee, value = ff....ff)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Operation name

dd....dd: Element name

ee....ee: Namespace

ff....ff: Value

Description: The value of an element specified in the header message is invalid.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the specified message.

KDEC00062-E

The service selection definition file does not include any services that match the specified condition. (reception name = aa....aa, reception ID = bb....bb, file name = cc....cc, condition = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: File name

dd....dd: Condition

Description

A service that matches the condition specified in the service-selection definition file was not found.

For the condition, the information used for selecting the service to be called from the user-defined reception is displayed in the following format:

[condition]

If there are multiple conditions, they are separated by commas (,).

[condition],[condition] ...

(S)

Processing is interrupted.

(O)

Check and, if necessary, revise the value specified in the service-selection definition file.

KDEC00063-E

The conditions for calling a service are not set in the service selection definition file. (reception name = aa....aa, reception ID = bb....bb, file name = cc....cc)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: File name

Description: The conditions for calling a service are not set in the service-selection definition file.
(S): Processing is interrupted.
(O): Specify the conditions for calling a service in the service-selection definition file.

KDEC00064-E

The service selection definition file includes an invalid property. (reception name = aa....aa, reception ID = bb....bb, file name = cc....cc, key name = dd....dd, specified value = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: File name

dd....dd: Key name

ee....ee: Specified value

Description: A property specified in the service-selection definition file is invalid.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the value specified in the service-selection definition file.

KDEC00351-I

TP1/RPC reception has been initialized. (reception name = aa....aa, reception ID = bb....bb, information = cc....cc)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Manifest information

Description: The TP1/RPC reception is initialized.
(S): Processing continues.

KDEC00361-E

Processing will now be canceled because TP1/RPC reception failed to be initialized. (reception name = aa....aa, reception ID = bb....bb, information = cc....cc, exception = dd....dd, error message = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Manifest information

dd....dd: Exception name

ee....ee: Message with exception details

Description: The processing will be interrupted because an attempt to initialize the TP1/RPC reception failed.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00362-E

Processing will now be canceled because an error occurred during custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, error code = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Error message

hh....hh: Error code

Description

The processing will be interrupted because an error occurred during the custom reception framework processing.

(S)

Processing is interrupted.

(O)

See the message log file and the error messages displayed before this message to eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the service component invocation request. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

Also, if the error occurring during the custom reception framework processing contains the fault information, that fault information (KDEC00371-W) is output to the message log file. See that warning message and then eliminate the cause of the error.

KDEC00363-E

Processing will now be canceled because an internal error occurred during custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, exception = gg....gg, error message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Exception name

hh....hh: Message with exception details

Description: The processing will be interrupted because an internal error occurred during the custom reception framework processing.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00364-E

Processing will now be canceled because an error occurred during TP1/RPC reception processing. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, error code = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Error message

hh....hh: Error code

Description

The processing will be interrupted because an error occurred during the TP1/RPC reception processing.

(S)

Processing is interrupted.

(O)

See the message log file and the error messages displayed before this message to eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the service component invocation request. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00365-E

Processing will now be canceled because an internal error occurred during TP1/RPC reception processing. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, exception = gg....gg, error message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Exception name

hh....hh: Message with exception details

Description: The processing will be interrupted because an internal error occurred during the TP1/RPC reception processing.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00366-E

Processing will now be canceled because the length of the response message received from the custom reception framework is invalid. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, length = gg....gg, buffer size = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Length of the response message

hh....hh: Size of the area storing the response message

Description: The processing will be interrupted because the length of the response message received from the custom reception framework is invalid (more than the size of the area where the response message is stored).
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00371-W

This message is fault information regarding the error that occurred in custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, process instance ID = gg....gg, fault code = hh....hh, fault string = ii....ii, fault actor = jj....jj, fault name = kk....kk)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Process instance ID

hh....hh: FaultCode information

ii....ii: FaultString information

jj....jj: FaultActor information

kk....kk: Fault name (exception name)

Description: This message is the fault information for the error that occurred during the custom reception framework processing.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00372-W

aa....aa

aa....aa: Stack trace information

Description: This message is the stack trace information of the error that occurred during the custom reception framework processing or TP1/RPC reception processing.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00381-I

FTP reception has been initialized. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The FTP reception is initialized.
(S): Processing continues.

KDEC00382-E

Processing will now be canceled because FTP reception failed to be initialized. (reception name = aa....aa, reception ID = bb....bb, exception = cc....cc, error message = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Exception name

dd....dd: Message with exception details

Description

The processing will be interrupted because an attempt to initialize the FTP reception failed.

(S)

Processing is interrupted.

(O)

Eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00383-E

An attempt to read the definition file has failed. (reception name = aa....aa, reception ID = bb....bb, definition file path = cc....cc, exception = dd....dd, error message = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Path of the definition file

dd....dd: Exception name

ee....ee: Message with exception details

Description

An attempt to read the definition file failed.

(S)

Processing is interrupted.

(O)

Check the specified FTP reception configuration file.

Also, check the following files that are specified in the FTP reception configuration file:

FTP execution permission list definition file
FTP command permission list definition file
List command options definition file

KDEC00384-E

Processing will now be canceled because an error occurred during custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, error code = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Error message

hh....hh: Error code

Description

The processing will be interrupted because an error occurred during the custom reception framework processing.

(S)

Processing is interrupted.

(O)

See the message log file and the error message displayed before this message, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the service component invocation request. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

Also, if the error occurring during the custom reception framework processing contains the fault information, that fault information is output to the message log (KDEC00388-W). See that warning message, and then eliminate the cause of the error.

KDEC00385-E

Processing will now be canceled because an internal error occurred during custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, exception = gg....gg, error message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Exception name

hh....hh: Message with exception details

Description: The processing will be interrupted because an internal error occurred during the custom reception framework processing.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00386-E

Processing will now be canceled because an error occurred during FTP reception processing. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, error code = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Error message

hh....hh: Error code

Description

The processing will be interrupted because an error occurred during the FTP reception processing.

(S)

Processing is interrupted.

(O)

See the message log file and the error message displayed before this message, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the service component invocation request. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00387-E

Processing will now be canceled because an internal error occurred during FTP reception processing. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, exception = gg....gg, error message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Exception name

hh....hh: Message with exception details

Description: The processing will be interrupted because an internal error occurred during the FTP reception processing.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00388-W

This message is fault information regarding the error that occurred in custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, process instance ID = gg....gg, fault code = hh....hh, fault string = ii....ii, fault actor = jj....jj, fault name = kk....kk)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Process instance ID

hh....hh: FaultCode information

ii....ii: FaultString information

jj....jj: FaultActor information

kk....kk: Fault name (exception name)

Description

This message is the fault information for the error that occurred during the custom reception framework processing.

(S)

Processing is interrupted.

(O)

See the error message displayed just before this message, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the FTP reception. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00391-E

Only sort ID information (and not transfer path information) is contained in the path information specified for a transfer command argument. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, path = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Path specified in the argument

Description: The path information specified for a transfer command argument contains only the sort ID information and not the transfer path information.
(S): Processing is interrupted.
(O): Specify the correct path and then re-execute the processing.

KDEC00392-E

An attempt to create an intermediary file has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, intermediate file path = gg....gg, exception = hh....hh, error message = ii....ii)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Intermediate file path

hh....hh: Exception name

ii....ii: Message with exception details

Description: An attempt to create an intermediate file failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00393-E

An attempt to acquire transfer data from an FTP client has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, intermediate file path = gg....gg, exception = hh....hh, error message = ii....ii)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Intermediate file path

hh....hh: Exception name

ii....ii: Message with exception details

Description: An attempt to obtain the transfer data from an FTP client failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00394-E

An attempt to send transfer data to an FTP client has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, intermediate file path = gg....gg, exception = hh....hh, error message = ii....ii)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Intermediate file path

hh....hh: Exception name

ii....ii: Message with exception details

Description: An attempt to send the transfer data to an FTP client failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00395-E

A response message returned from a business process is invalid. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, response message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Detailed message

hh....hh: Response message

Description: A response message returned from a business process is invalid.
(S): Processing is interrupted.
(O): See the information in the detailed message, and then correct the response message returned from the business process.

KDEC00396-E

No work folder root folder exists. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, root path = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Root path of the work folder

Description: The root folder of the work folder does not exist.
(S): Processing is interrupted.
(O): Create the root folder of the work folder, and then re-execute the processing.

KDEC00397-E

An attempt to create a work folder has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, work folder path = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Path of the work folder

Description: An attempt to create a work folder failed.
(S): Processing is interrupted.
(O): Eliminate the cause due to which you cannot create a directory in the work folder path displayed in the message, and then re-execute the processing.

KDEC00398-W

An attempt to delete a work folder has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, work folder path = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Path of the work folder

Description: An attempt to delete a work folder failed.
(S): Processing continues.
(O): Eliminate the cause due to which you cannot delete the directory in the work folder path displayed in the message, and then use an operation command to delete the work folder.

KDEC00399-E

Access to FTP reception has been denied. (reception name = aa....aa, reception ID = bb....bb, service name = cc....cc, operation name = dd....dd, RootApInfo = ee....ee, client addr = ff....ff)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Service name

dd....dd: Service operation name

ee....ee: Root application information

ff....ff: IP address of the client

Description: An Access to an FTP reception was denied.
(S): Processing is interrupted.
(O): Change the access control settings for the business processes as and when required, restart the FTP reception, and then re-execute the processing.

KDEC00400-E

FTP reception has not been configured for the requested operations. (reception name = aa....aa, reception ID = bb....bb, service name = cc....cc, operation name = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Service name

dd....dd: Service operation name

ee....ee: Root application information

Description: An FTP reception has not been configured for the requested operations.
(S): Processing is interrupted.
(O): Check whether the requested operation is correct. As and when required, specify the settings for the operations required for an FTP reception.

KDEC00401-E

FTP reception denied an FTP command. (reception name = aa....aa, reception ID = bb....bb, service name = cc....cc, operation name = dd....dd, RootApInfo = ee....ee, FTP command = ff....ff)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Service name

dd....dd: Service operation name

ee....ee: Root application information

ff....ff: FTP command

Description: The FTP reception denied an FTP command.
(S): Processing is interrupted.
(O): Change the settings related to the FTP command execution list definition functionality as and when required, restart the FTP reception, and then re-execute the processing.

KDEC00402-E

Neither the -B parameter nor the -A parameter has not been specified for the SITE CSCTHR command. (reception name = aa....aa, reception ID = bb....bb, service name = cc....cc, operation name = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Service name

dd....dd: Service operation name

ee....ee: Root application information

Description: The -B argument or -A argument is not specified for the SITE CSCTHR command.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the arguments specified for the SITE CSCTHR command, and then re-execute the processing.

KDEC00403-E

Asynchronous communication is not supported. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: An Asynchronous communication is not supported.
(S): Processing is interrupted.
(O): Set the communication model for the operation information settings of the user-defined receptions in the development environment to synchronous, and then re-package the business processes.

KDEC00404-W

FTP reception will wait for the request to finish being processed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, client addr = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: IP address of the client

Description: Because A request is being processed, the FTP reception will wait for the processing to end.
(S): Processing continues.
(O): Wait until the KDEC00405-I message is output and the processing ends.

KDEC00405-I

Processing of the request that FTP reception was waiting on has finished. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, client addr = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: IP address of the client

Description: The processing of the request for which the FTP reception was waiting has finished.
(S): Processing continues.

KDEC00406-E

An error occurred during the beginning of a transaction. (reception name = aa....aa, reception ID = bb....bb, service name = cc....cc, operation name = dd....dd, RootApInfo = ee....ee, exception = ff....ff, error message = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Service name

dd....dd: Service operation name

ee....ee: Root application information

ff....ff: Exception name

gg....gg: Message with exception details

Description

An error occurred while a transaction was being started.

(S)

Processing is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00407-E

An error occurred while a transaction was being aa....aa. (reception name = bb....bb, reception ID = cc....cc, RequestID = dd....dd, service name = ee....ee, operation name = ff....ff, RootApInfo = gg....gg, exception = hh....hh, error message = ii....ii)

aa....aa: committed or rolled back

bb....bb: Reception name

cc....cc: Reception ID

dd....dd: Request ID

ee....ee: Service name

ff....ff: Service operation name

gg....gg: Root application information

hh....hh: Exception name

ii....ii: Message with exception details

Description

An error occurred while a transaction was being committed or rolled back.

(S)

Processing is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00408-W

The FTP reception response message contained an invalid character. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

Description: The FTP reception response message contained a character that cannot be used.
(S): The unusable characters in the message are replaced with question marks (?), and processing continues.
(O): Obtain the user-message trace as and when required, and check the messages specified in the FTP reception response message.

KDEC00409-W

The FTP reception response message is too long. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

Description: The FTP reception response message is too long.
(S): The latter part of the message is truncated so that the message fits into 1,024 or fewer characters, and processing continues.
(O): Collect the user-message trace as and when required, and check the messages specified in the FTP reception response message.

KDEC00410-W

No FTP reception definition file has been specified.

Default values will be used for FTP reception properties. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The FTP reception definition file is not specified. The default values will be applied to the FTP reception properties.
(S): Processing continues.
(O): As and when required, set up the FTP reception definition file for the FTP reception.

KDEC00411-E

One or more property values specified in the allowed FTP execution list definition file are invalid. (reception name = aa....aa, reception ID = bb....bb, definition file path = cc....cc, key name = dd....dd, specified value = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Path of the definition file

dd....dd: Key name

ee....ee: Specified value

Description

A property value specified in the FTP execution authorization list definition file is invalid.

(S)

Processing is interrupted.

(O)

Check the specified FTP execution permission list definition file.

Make sure that the tab characters are specified in appropriate locations. When the user name is enclosed within tab characters, make sure that the relationship between the start and end tab characters is correct.

KDEC00412-E

One or more values specified in the list command options definition file are invalid. (reception name = aa....aa, reception ID = bb....bb, definition file path = cc....cc, specified value = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Path of the definition file

dd....dd: Specified value

Description

A value specified in the list command options definition file is invalid.

(S)

Processing is interrupted.

(O)

Check the specified list command options definition file.

Make sure that the option string does not contain unusable characters.

KDEC00413-E

An attempt to send list data to an FTP client has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, intermediate file path = gg....gg, exception = hh....hh, error message = ii....ii)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Intermediate file path

hh....hh: Exception name

ii....ii: Message with exception details

Description: An attempt to send the list data to an FTP client failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00414-W

An attempt to delete a file in a common folder has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, common folder file path = gg....gg)

aa....aa: Reception na

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Path of the file in the common folder

Description: An attempt to delete a file in a common folder failed.
(S): Processing continues.
(O): Eliminate the cause due to which the file cannot be deleted from the file path of the common folder displayed in the message, and then delete the file from the common folder by using operation commands.

KDEC00415-E

An attempt to exclude a file has failed. (reception name = aa....aa, reception ID = bb....bb, RequestID = cc....cc, service name = dd....dd, operation name = ee....ee, RootApInfo = ff....ff, file path = gg....gg, exception = hh....hh, error message = ii....ii)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Request ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: File path

hh....hh: Exception name

ii....ii: Message with exception details

Description: An attempt to exclude a file failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC00421-I

Message Queue reception has been initialized. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The Message Queue reception is initialized.
(S): Processing continues.

KDEC00423-E

Processing will now be canceled because Message Queue reception failed to be initialized. (reception name = aa....aa, reception ID = bb....bb, error message = cc....cc)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Message with exception details

Description: Processing is interrupted because an attempt to initialize the Message Queue reception failed.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00424-E

The specified message type is invalid. (JMSMessageID = aa....aa)

aa....aa: JMSMessageID

Description

The specified message type is invalid.

(S)

Processing of the request is interrupted.

(O)

Review and, if necessary, revise the message type specified in the asynchronous request reception queue.

If the message sent when an exception occurs is invalid, destroy that message.

KDEC00425-E

The specified JMSMessage Body is invalid. (JMSMessageID = aa....aa, error message = bb....bb)

aa....aa: JMSMessageID

bb....bb: Message with exception details

Description

Processing cannot continue because the specified JMS message body is invalid, or JMSException was cached.

(S)

Processing of the request is interrupted.

(O)

Review and, if necessary, revise the messages specified in the asynchronous request reception queue.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00426-E

The asynchronous Message Queue reception service request was interrupted. (JMSMessageID = aa....aa, error message = bb....bb)

aa....aa: JMSMessageID

bb....bb: Message with exception details

Description

An error occurred during the routing of service components.

(S)

Processing of the request is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00441-E

The common folder does not contain the file to be acquired. (reception name = aa....aa, reception ID = bb....bb, common folder definition name = cc....cc, common folder file path = dd....dd, subfolder file path = ee....ee, name of file to be acquired = ff....ff, monitored folder = gg....gg, monitored subfolder = hh....hh, name of update completion notification file = ii....ii, RootApInfo = jj....jj)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Common folder definition name

dd....dd: Common folder file path

ee....ee: Subfolder of the common folder

If a subfolder is defined: Subfolder of the common folder
If no subfolder is defined: null

ff....ff: Name of the file to be acquired

gg....gg: Monitored folder file path

hh....hh: Subfolder of the monitored folder

If a subfolder is defined: Subfolder of the monitored folder
If no subfolder is defined: null

ii....ii: Name of the update completion notification file

jj....jj: Root application information

Description

The file to be acquired does not exist in the common folder.

(S)

Processing is interrupted.

(O)

Check the following:

The file to be acquired exists in the common folder.
The file to be acquired has the same name as the update completion notification file.
If subfolders are specified, they match each other.

KDEC00442-E

Processing will now stop because an error occurred during FileEvent reception processing. (reception name = aa....aa, reception ID = bb....bb, client ID = cc....cc, service name = dd....dd, service operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, error code = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: ervice name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Error message

hh....hh: Error code

Description: The processing will be interrupted because an error occurred during the file event reception processing.
(S): Processing is interrupted.
(O): See the message log file and check the error message displayed before this message, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the service component invocation request. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00443-E

An attempt to create a lock file failed. (reception name = aa....aa, reception ID = bb....bb, file path = cc....cc, RootApInfo = dd....dd)

aa....aa: Reception name

bb....bb: eception ID

cc....cc: Directory in which a lock file is to be created

dd....dd: Root application information

Description

An attempt to create a lock file failed.

(S)

Processing is interrupted.

(O)

Check and, if necessary, revise the access permission of the directory in which the lock file is to be created.

If the access permission is correct, collect the log and trace information, and then contact the maintenance personnel.

KDEC00444-E

An attempt to rename an update completion notification file failed. (reception name = aa....aa, reception ID = bb....bb, directory = cc....cc, file name = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Storage directory of the update completion notification file

dd....dd: Name of the update completion notification file

ee....ee: Root application information

Description: An attempt to rename an update completion notification file failed.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the storage directory of the update completion notification file and the access permission of this file. If the access permission is correct, collect the log and trace information, and then contact the maintenance personnel.

KDEC00445-W

An attempt to delete an update completion notification file failed. (reception name = aa....aa, reception ID = bb....bb, directory = cc....cc, file name = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Storage directory of the update completion notification file

dd....dd: Name of the update completion notification file

ee....ee: Root application information

Description: An attempt to delete an update completion notification file failed.
(S): Processing continues.
(O): If necessary, delete the update completion notification file.

KDEC00446-E

Processing will now stop because an error occurred during custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, ClientID = cc....cc, service name = dd....dd, service operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, error code = hh....hh)

aa....aa: Reception name

bb....bb: eception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Error message

hh....hh: Error code

Description: The processing will be interrupted because an error occurred during processing in the custom reception framework.
(S): Processing is interrupted.
(O): See the message log file and check the error message displayed before this message, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the service component invocation request. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00447-I

FileEvent reception was initialized. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The file event reception is initialized.
(S): Continues the request processing.

KDEC00448-E

Processing will now stop because an attempt to initialize FileEvent reception failed. (reception name = aa....aa, reception ID = bb....bb, exception = cc....cc, error message = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Exception name

dd....dd: Message with exception details

Description: The processing will be interrupted because an attempt to initialize the file event reception failed.
(S): Processing is interrupted.
(O): Eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00449-E

An attempt to read the definition file failed. (reception name = aa....aa, reception ID = bb....bb, definition file path = cc....cc, exception = dd....dd, error message = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Path of the definition file

dd....dd: Exception name

ee....ee: Message with exception details

Description: An attempt to read the definition file failed.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the access permission of the file-event-reception configuration file. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC00450-E

Processing will now stop because an internal error occurred during custom reception framework processing. (reception name = aa....aa, reception ID = bb....bb, client ID = cc....cc, service name = dd....dd, service operation name = ee....ee, RootApInfo = ff....ff, exception = gg....gg, error message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Exception name

hh....hh: Message with exception details

Description: The processing will be interrupted because an error occurred during processing in the custom reception framework.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00451-E

Processing will now stop because an internal error occurred during FileEvent reception processing. (reception name = aa....aa, reception ID = bb....bb, client ID = cc....cc, service name = dd....dd, service operation name = ee....ee, RootApInfo = ff....ff, exception = gg....gg, error message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Exception name

hh....hh: Message with exception details

Description: The processing will be interrupted because an error occurred during processing in the file event reception.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00452-E

An attempt to lock a file failed. (reception name = aa....aa, reception ID = bb....bb, client ID = cc....cc, file path = dd....dd, file name = ee....ee, RootApInfo = ff....ff, exception = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: File storage directory

ee....ee: File path

ff....ff: Root application information

gg....gg: Exception name

Description: An attempt to lock a file failed.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC00453-I

The file monitoring function will now start. (monitoring interval = aa....aa, starting delay = bb....bb)

aa....aa: File monitoring interval (minutes)

bb....bb: Amount of time to delay the start of file monitoring (minutes)

Description: The file monitoring function will start.
(S): Processing continues.

KDEC00454-W

A FileEvent reception definition file is not specified. The default values will be used for FileEvent reception properties. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: A file-event-reception definition file is not specified. The default values will be applied to the file-event-reception properties.
(S): Continues processing.
(O): If necessary, set a file-event-reception definition file for the file event reception.

KDEC00455-E

An attempt to initialize FileEvent reception failed because a required parameter is invalid. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: An attempt to initialize the file event reception failed because a required parameter was invalid.
(S): Processing is interrupted.
(O): Set true for fileevent-reception.monitored-file.enabled in the HCSC server runtime definition file.

KDEC00456-E

The monitored folder does not exist. (reception name = aa....aa, reception ID = bb....bb, file path = cc....cc, RootApInfo = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Path of the monitored folder (including subfolders if they are defined)

dd....dd: Root application information or null

Description: The monitored folder does not exist.
(S): Processing is interrupted.
(O): Specify the path of an existing directory. If the directory exists, check and, if necessary, revise the access permission.

KDEC00457-W

An attempt to initialize the FileEvent trace failed. (reception name = aa....aa, reception ID = bb....bb, cause = cc....cc, information = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Details of cause

dd....dd: Location of error

Description: An attempt to initialize the file event trace failed.
(S): Continues processing without outputting file event trace information.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00458-E

The common folder does not exist. (reception name = aa....aa, reception ID = bb....bb, common folder definition name = cc....cc, common folder file path = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Common folder definition name

dd....dd: Common folder file path (including subfolders if they are defined) or null

ee....ee: Root application information or null

Description: The common folder does not exist.
(S): Processing is interrupted.
(O): Make sure that the directory exists in the common folder file path. If the common folder file path is null, make sure that the definition corresponding to the common folder definition name is specified in the HCSC server runtime definition file.

KDEC00459-E

An attempt to initialize the file monitoring function failed. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Message with exception details

Description: An attempt to initialize the file monitoring function failed.
(S): Processing is interrupted.
(O): Restart the HCSC server. If the problem is not resolved, collect the log and trace information, and then contact the maintenance personnel.

KDEC00460-E

The file monitoring function stopped because an error occurred. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Message with exception details

Description: The file monitoring function stopped because an error occurred.
(S): Processing is interrupted.
(O): Restart the HCSC server. If the problem is not resolved, collect the log and trace information, and then contact the maintenance personnel.

KDEC00461-W

Processing to end the FileEvent trace failed. (reception name = aa....aa, reception ID = bb....bb, cause = cc....cc, information = dd....dd)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Details of cause

dd....dd: Location of error

Description: Processing to end the file event trace failed.
(S): Continues the end processing.
(O): Check whether the cause of the error is associated with operations. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC00462-E

An invalid response message was returned from a business process. (reception name = aa....aa, reception ID = bb....bb, client ID = cc....cc, service name = dd....dd, service operation name = ee....ee, RootApInfo = ff....ff, error message = gg....gg, response message = hh....hh)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Client correlation ID

dd....dd: Service name

ee....ee: Service operation name

ff....ff: Root application information

gg....gg: Detailed message

hh....hh: Response message

Description: An invalid response message was returned from a business process.
(S): Processing is interrupted.
(O): See the information in the detailed message, and then correct the response message that is to be returned from the business process.

KDEC00463-E

No common folder is defined. (reception name = aa....aa, reception ID = bb....bb, common folder definition name = cc....cc)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Common folder definition name

Description: No common folder is defined.
(S): Processing is interrupted.
(O): Make sure that the definition corresponding to the common folder definition name is specified in the HCSC server runtime definition file.

KDEC00464-E

The common folder does not contain the file to be acquired. (reception name = aa....aa, reception ID = bb....bb, common folder definition name = cc....cc, common folder file path = dd....dd, subfolder file path = ee....ee, name of file to be acquired = ff....ff, RootApInfo = gg....gg)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Common folder definition name

dd....dd: Common folder file path

ee....ee: Subfolder of the common folder

If a subfolder is defined: Subfolder of the common folder
If no subfolder is defined: null

ff....ff: Name of the file to be acquired

gg....gg: Root application information

Description: The file to be acquired does not exist in the common folder.
(S): Processing is interrupted.
(O): Make sure that the file to be acquired exists in the common folder. If subfolders are specified, make sure that they match each other.

KDEC00465-E

An attempt to rename the file to be acquired failed. (reception name = aa....aa, reception ID = bb....bb, directory = cc....cc, file name = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Storage directory of the file to be acquired

dd....dd: Name of the file to be acquired

ee....ee: Root application information

Description: An attempt to rename the file to be acquired failed.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the access permission of the file to be acquired. If the access permission is correct, collect the log and trace information, and then contact the maintenance personnel.

KDEC00466-W

An attempt to delete the file to be acquired failed. (reception name = aa....aa, reception ID = bb....bb, directory = cc....cc, file name = dd....dd, RootApInfo = ee....ee)

aa....aa: Reception name

bb....bb: Reception ID

cc....cc: Storage directory of the file to be acquired

dd....dd: Name of the file to be acquired

ee....ee: Root application information

Description: An attempt to delete the file to be acquired failed.
(S): Processing continues.
(O): If necessary, delete the file to be acquired.

KDEC00501-E

An error occurred during generation of the history writer.

Description: An error occurred during the generation of the execution log control.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00502-E

An error occurred during a service location search. (HCSCCommonID = aa....aa)

aa....aa: HCSC message common ID

Description: An error occurred while the location information for service components was being searched.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00503-E

An error occurred in the service routing. (HCSCCommonID = aa....aa)

aa....aa: HCSC message common ID

Description: An error occurred during the routing of service components.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00504-E

An error occurred during generation of the service adapter. (adapter name = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

Description: An error occurred during the generation of the service adapter or business process.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00505-E

An error occurred during output of the history writer. (information1 = aa....aa, information2 = bb....bb, HCSCCommonID = cc....cc)

aa....aa: Output timing

before: Before execution
after: After execution

bb....bb: Transmission destination

adapter: Execution of the adapter
multicast: Execution of multicast

cc....cc: HCSC message common ID

Description: An error occurred during the output of the execution log.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00506-E

An error occurred during execution of the service adapter. (adapter name = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

Description: An error occurred during the execution of the service adapter or business process.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00508-E

An error occurred during monitoring of the asynchronous queue. (type = aa....aa, queue name = bb....bb)

aa....aa: Queue type

reception: Queue for standard reception

bb....bb: Queue name

Description: An error occurred during the monitoring of the asynchronous queue.
(S): Executes the next queue monitoring process.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00509-I

Monitoring of the asynchronous queue will now start. (type = aa....aa, timer = bb....bb)

aa....aa: Queue type

reception: Queue for request reception

bb....bb: Monitoring timeout value

Description: The monitoring of the asynchronous queue has started.
(S): Resumes processing.

KDEC00510-I

Monitoring of the asynchronous queue ended. (type = aa....aa, result = bb....bb)

aa....aa: Queue type

reception: Queue for the standard reception

bb....bb: Termination result

no wait: No monitoring processing
normal: Normal termination
timeout: Monitoring timeout
cancel: Termination by cancellation
create QueueConnection error: Queue connection creation error

Description: The monitoring of the asynchronous queue ended.
(S): Terminates processing.

KDEC00511-I

Cancellation of monitoring of the asynchronous queue ended. (type = aa....aa, result = bb....bb)

aa....aa: Queue type

reception: Queue for the standard reception

bb....bb: Queue status

canceled: Cancellation is completed
cancel processing: Cancellation processing is being executed
timeout processing: Monitoring timeout processing is being executed
already stopped: Already stopped
no wait: Monitoring process is not performed

Description: The command for canceling the monitoring of the asynchronous queue has ended.
(S): Terminates processing.

KDEC00512-E

An error occurred during cancellation of monitoring of the asynchronous queue. (type = aa....aa)

aa....aa: Queue type

reception: Queue for the standard reception

Description: An error occurred while the monitoring of the asynchronous queue was being canceled.
(S): Terminates processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00513-W

Processing will continue through an InterruptedException occurred in the monitoring of the asynchronous queue. (type = aa....aa)

aa....aa: Queue type

reception: Queue for the standard reception

Description: The InterruptedException exception occurred during the monitoring of the asynchronous queue, but the monitoring will continue.
(S): Resumes processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00514-E

An exception occurred. (information = aa....aa)

aa....aa: Detailed information

create Queue connection: Creating a queue connection
close Queue connection: Closing the queue connection
ejb remove: Releasing the EJB object

Description: An exception occurred.
(S): Terminates processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00515-E

A RemoteException occurred. (adapter name = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

Description: The RemoteException exception occurred.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00516-E

A service request from the DBQueue receptor to the DBQueue adapter cannot be executed.

Description: A service component request from the database queue standard reception to the database queue adapter cannot be executed.
(S): Terminates processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00517-E

A value in the definition file is invalid. (adapter name = aa....aa, operation name = bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Operation name

When information is specified for each operation: operation-name
When information is not specified for each operation: null

cc....cc: Parameter name

Description: A value in the definition file is invalid.
(S): Cancels the data transformation processing and service component call.
(O): Check the information that was entered when the business process was created. Check the information about the called service (business process). If you have modified the information, re-create the business process. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00518-E

The message formats conflict. (adapter name = aa....aa, source FormatID = bb....bb, source message type = cc....cc, destination FormatID = dd....dd, destination message type = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Comparison source format ID

cc....cc: Comparison source message type

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (value): Unexpected message format

dd....dd: Comparison destination format ID

ee....ee: Comparison destination message type

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description: The message formats do not match.
(S): Cancels the data transformation processing and service component call.
(O): Check the message format ID in the information about the business process that was called. Check the data transformation and data format definitions. If the format ID is null, check the configuration of the user-defined reception. If the cause of the error is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00519-E

The specified data transform definition does not exist. (source FormatID = aa....aa, destination FormatID = bb....bb)

aa....aa: Format ID before transformation

bb....bb: Format ID after transformation

Description: The specified data transformation definition does not exist.
(S): Cancels the data transformation processing and service component call.
(O): Check the data transformation and data format definitions. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00520-E

An attempt to transform the data failed. (adapter name = aa....aa, source FormatID = bb....bb, source message type = cc....cc, destination FormatID = dd....dd, destination message type = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Format ID before transformation

cc....cc: Message type before transformation

XML: XML message
Binary: Binary message
ANY: Any message
NONE: No message
UNKNOWN (Value): Unexpected message format

dd....dd: Format ID after transformation

ee....ee: Message type after transformation

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description: An attempt at data transformation failed.
(S): Cancels the data transformation processing and service component call.
(O): Check the message format ID in the information about the service component that was called. Check the data transformation and data format definitions. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00521-E

An error occurred during execution of the multicast. (request service name = aa....aa, service name = bb....bb)

aa....aa: Service name entered from the requester

bb....bb: Service name with error

Description: An error occurred while the multicast was being executed.
(S): Interrupts the processing for the corresponding service component, and continues the multicast processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00522-E

The service group status is not running. (service name = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Service name

bb....bb: HCSC message common ID

Description: The service group is not running.
(S): Interrupts the processing for the corresponding service component, and continues the multicast processing.
(O): Start the service group for the corresponding service component. Check the service name, specified when sending the request, and then re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00523-W

The number of started threads is not the same as the specified number of threads. (specified thread number = aa....aa, started thread number = bb....bb)

aa....aa: Specified number of threads

bb....bb: Number of started threads

Description: The number of started threads is not the same as the specified number of threads.
(S): Continues the processing with the number of started threads.
(O): The memory may be insufficient. Increase the available space, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC00524-E

An unexpected exception occurred during parallel-multicast calling. (service group name = aa....aa, information = bb....bb)

aa....aa: Service group name

bb....bb: Maintenance information

Description: An unexpected exception occurred during a parallel-multicast invocation.
(S): Cancels the multicast processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC00525-E

An error occurred during generation of the message deliverer. (information = aa....aa)

aa....aa:Maintenance information

Description

An error occurred during the generation of a delivery control.

(S)

Cancels the HCSC server startup processing.

(O)

Check, and if necessary, revise the thread count of the parallel-multicast invocation that is specified in the HCSC server runtime definition file, and then specify the correct value.

If no problem exists with the specified value, the memory might be insufficient. Increase the available space, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC00526-E

An error occurred during the rollback of a transaction. (request service name = aa....aa, service name = bb....bb, information = cc....cc)

aa....aa: Service name entered from the requester

bb....bb: Service name with error

cc....cc: Maintenance information

Description: An error occurred during the rollback of a transaction for invoking individual services in a parallel-multicast invocation.
(S): Interrupts the processing for the corresponding service, and continues the multicast processing.
(O): Check, and if necessary, revise the transaction settings for the service platform, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC00527-E

An unexpected exception occurred during parallel-multicast calling. (service group name = aa....aa, request service name = bb....bb)

aa....aa: Service group name

bb....bb: Service name

Description: An unexpected exception occurred during a parallel-multicast invocation.
(S): Interrupts the processing for the corresponding service, and continues the multicast processing.
(O): Check the log and the trace information of the service invocation that is displayed in the service name, and eliminate cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC00528-E

An error occurred during processing of asynchronous EJB. (process-instance-ID = aa....aa)

aa....aa: Process instance identifier

Description: An error occurred during the asynchronous EJB processing.
(S): Processing of the request is interrupted.
(O): See the message log file, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing or process instance. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC01001-E

The service was not found in the location information. (service name = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Service name

bb....bb: HCSC message common ID

Description: The service component was not found in the location information.
(S): Cancels the request processing.
(O): Deploy and invoke the service (service adapter, business process, or service group). Check the service name, specified when sending the request, and then re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01002-E

The adapter status is not running. (adapter name = aa....aa, service name = bb....bb, HCSCCommonID = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Service name

cc....cc: HCSC message common ID

Description: The service adapter or business process is not running.
(S): Cancels the request processing.
(O): Start the service (service adapter or business process). Check the service name, specified when sending the request, and then re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01003-E

The adapter status is not stopping. (adapter name = aa....aa, service name = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Service name

Description: The service adapter or business process is still running.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01004-E

The service has already been registered in the location information. (service name = aa....aa)

aa....aa: Service name

Description: The service component is already registered in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01005-E

The adapter was not found in the location information. (cluster name = aa....aa, adapter name = bb....bb)

aa....aa: Cluster name

bb....bb: Service ID of the service adapter or the business process

Description: The service adapter or business process was not found in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01006-E

Database access based on the location failed.

Description: An attempt to access the location-based database failed.
(S): Cancels the location management start processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01007-E

Database access failed. (information = aa....aa)

aa....aa: Operation type

UPDATE: Update
INSERT: Register
SELECT: Reference
DELETE: Delete

Description: The location information for the same service name exists in the entered data.
(S): Cancels processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01008-E

An invalid value is specified for the location information. (information = aa....aa)

aa....aa: Item

Description: An invalid value is specified for the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01009-E

Location information required for the service type is not specified. (service type = aa....aa, information = bb....bb)

aa....aa: Service component type

bb....bb: Item

Description: The location information required for the service component type is not specified.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01011-E

Location information for the same service name exists in the entered data. (service name = aa....aa)

aa....aa: Service name

Description: The service component was not found in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01012-I

There is no inquiry information.

Description: The inquiry information does not exist.
(S): Resumes processing.

KDEC01013-E

Location information for the service name is registered more than once. (service name = aa....aa)

aa....aa: Service name

Description: The location information for the service name is registered more than once.
(S): Cancels processing.
(O): When using a database, reference the message log file, and make sure that no error has occurred. When you are not using a database, reference the message log file and the error information of the OS, and make sure that no error has occurred. If an error is occurring, take action against the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01015-W

Adapter creation failed because the location information and adapter status are incorrect. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description: An attempt to create a service adapter or business process failed because the location information and the status of the service adapter or business process are invalid.
(S): Continues processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01016-E

The service was not found in the location information. (service name = aa....aa)

aa....aa: Service name

Description: The service component was not found in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01017-E

Location information is invalid.

Description: The location information is invalid.
(S): Cancels processing.
(O): When using a database, reference the message log file, and make sure that no error has occurred in the database. When you are not using a database, reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against each error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC01018-E

The service group status is not running. (service group name = aa....aa, HCSCCommonID = bb....bb)

aa....aa: Service group name

bb....bb: HCSC message common ID

Description: The service group is not running.
(S): Cancels the request processing.
(O): Start the service group. Check the service group name specified when sending the request, and then re-execute the processing. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01019-E

The reception was not found in the reception information. (reception name = aa....aa, Reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The request reception was not found in the location information.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01020-E

The reception information for the same reception name already exists in the entered data. (reception name = aa....aa, Reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The request reception information with the same reception name and reception ID exists in the entered data.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01021-E

The reception has already been registered in the reception information. (reception name = aa....aa, Reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The request reception is already registered in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01022-E

The reception was not found in the reception information. (Reception ID = aa....aa)

aa....aa: Reception ID

Description: The reception ID was not found in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01023-E

The reception has not stopped. (reception name = aa....aa, Reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The service component cannot be determined from the routing.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01024-E

The reception name of the reception corresponding to the service is registered more than once. (reception name = aa....aa, Reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: An exception occurred in the rule implementation class.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01025-E

An attempt to access location information has failed.

Description: An attempt to access the location information failed.
(S): Cancels the location management start processing.
(O): Reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC01026-E

An attempt to access location information has failed. (information = aa....aa)

aa....aa: Operation type

UPDATE: Update
INSERT: Register
SELECT: Reference
DELETE: Delete

Description: The location information operations failed.
(S): Cancels processing.
(O): Reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC01501-E

An error was detected in the routing information. (service group name = aa....aa)

aa....aa: Service group name

Description: An error was detected in the routing information.
(S): Cancels processing.
(O): When using a database, reference the message log file and make sure that no error has occurred in the database. When you are not using a database, reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC01502-E

An error occurred during initialization of environment for parsing the routing definition XML.

Description: An error occurred during the generation of the environment for parsing the routing definition XML.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If the cause of the error has nothing to do with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01503-E

The service cannot be determined from the routing. (service group name = aa....aa)

aa....aa: Service group name

Description: The service component cannot be determined from the routing.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01504-E

An exception occurred in the rule class. (class name = aa....aa, rule kind = bb....bb)

aa....aa: Name of the implementation class where the exception occurred (display name for standard provision)

bb....bb: Rule type (Standard)

Description: An exception occurred in the rule implementation class.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01505-E

An error occurred during checking of the routing definition. (information = aa....aa)

aa....aa: Tag name where error was detected, or error contents

There is too much service group nesting.: Too many service groups are nested.
RuleType and RuleOrder combination.: The order of the specified rule attributes is invalid.
The file data length is invalid.: The length of the XML routing definition is invalid (the input is null or the size is 0).
A different type of service group is nested. (ServiceGroupName = service-group-name): Service-group-name is nested in a different service group.
All services tries to be deleted.: An attempt was made to delete all service components.

Description: An error occurred during the validity check of the routing definition.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01506-E

The rule class was not found. (class name = aa....aa, rule kind = bb....bb)

aa....aa: Name of the implementation class where the exception occurred (display name for standard provision)

bb....bb: Rule type (Standard)

Description: The rule implementation class was not found.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01507-E

The service group was not found. (service group name = aa....aa)

aa....aa: Service group name

Description: The service group was not found.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01508-E

The service group already exists. (service group name = aa....aa)

aa....aa: Service group name

Description: The service group already exists.
(S): Cancels processing.
(O): Check the location information, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01509-E

A database access error occurred. (service group name = aa....aa, information1 = bb....bb, information2 = cc....cc)

aa....aa: Service group name

bb....bb: Operation type

INSERT: Register
DELETE: Delete
UPDATE: Update

cc....cc: Database type

location: Location database
Routing: Routing database

Description: An error occurred during the database access based on routing control
(S): Cancels processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01510-E

The service group was not found in the location information. (service group name = aa....aa)

aa....aa: Service group name

Description: The service group was not found in the location information.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01511-E

The service group is running. (service group name = aa....aa)

aa....aa: Service group name

Description: The service group is running.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01512-E

The service group has stopped. (service group name = aa....aa)

aa....aa: Service group name

Description: The service group has stopped.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01513-E

An IO error occurred. (information = aa....aa)

aa....aa: Detailed information

Description: An I/O error occurred in routing control.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC01514-E

An error occurred in the environment for parsing the routing definition XML. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Exception detail message

In messages beginning with KECX, the routing definition XML might be incorrect.

Description

An error occurred in the environment for parsing the routing definition XML.

(S)

Cancels processing.

(O)

Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

If the message begins with KECX, see the manual Application Server: Message 11: KECX-KEDT, KEOS02000-29999, and KEUC-KFRM. In the case of messages KECX06025-E and KECX06028-E, check and, if necessary, revise the tags displayed as invalid.

KDEC01515-E

An information error was detected. (service group name = aa....aa, information1 = bb....bb, information2 = cc....cc)

aa....aa: Service group name

bb....bb: Operation type

DELETE: Delete

cc....cc: Information type

Routing: Routing information

Description: An error was detected in the service group definition information.
(S): Continues processing.
(O): When using a database, reference the message log file and make sure that no error has occurred in the database. When you are not using a database, reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC01516-E

The rule class result is invalid. (class name = aa....aa, rule kind = bb....bb, input array count = cc....cc, output array count = dd....dd)

aa....aa: Name of the implementation class where the exception occurred (display name for standard provision)

bb....bb: Rule type (Standard)

cc....cc: Input array count or null

dd....dd: Output array count or null

Description: The response of the rule implementation class is invalid.
(S): Cancels the request processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC01517-E

The type of specified service group is invalid. (service group name = aa....aa, service group type = bb....bb)

aa....aa: Service group name

bb....bb: Service group type

Rule: Routing rule
Multicast: Multicast

Description: The type of the specified service group is invalid.
(S): Cancels processing.
(O): There may be a processing in-progress that cannot be executed in the service group of the specified type. Check the type of the service group and processing contents.

KDEC01518-E

The specified service already exists in the service group. (service group name = aa....aa, service name = bb....bb)

aa....aa: Service group name

bb....bb: Service name

Description: The specified service already exists in the service group.
(S): Cancels processing.
(O): Specify a service name that does not exist in the specified service group name, and then re-execute the processing.

KDEC01519-E

The specified service was not found in the service group. (service group name = aa....aa, service name = bb....bb)

aa....aa: Service group name

bb....bb: Service name

Description: The specified service does not exist in the service group.
(S): Cancels processing.
(O): Specify a service name that exists in the specified service group, and then re-execute the processing.

KDEC01520-W

The service group has stopped because of an invalid parameter. (service group name = aa....aa, parameter = bb....bb)

aa....aa: Service group name

bb....bb: Parameter name

Description: The service group was stopped because a parameter is invalid.
(S): Continues processing.
(O): When the service group, in which parallel-multicast invocation is set in the service group type, is started, the value of the multicast-parallel-thread-count property of the HCSC server runtime definition file might be changed to 0. Check the service group type and the property value, correct the value of the multicast-parallel-thread-count property of the HCSC server runtime definition file, and then restart the HCSC server.

KDEC01521-E

The service group could not start because of an invalid parameter. (service group name = aa....aa, parameter = bb....bb)

aa....aa: Service group name

bb....bb: Parameter name

Description: The service group cannot be started because a parameter is invalid.
(S): Cancels processing.
(O): When 0 is set in the multicast-parallel-thread-count property of the HCSC server runtime definition file, you cannot start the service group in which the parallel-multicast invocation is set in the service group type. Check the service group type and the property value, and then correct the value of the multicast-parallel-thread-count property for the HCSC server runtime definition file. Then, restart the HCSC server and re-execute the command.

KDEC01522-E

A data access error occurred. (service group name = aa....aa, information1 = bb....bb, information2 = cc....cc)

aa....aa: Service group name

bb....bb: Operation type

UPDATE: Update
INSERT: Register
DELETE: Delete

cc....cc: Information type

location: location information
Routing: Routing information

Description: An error occurred during the database access based on routing control.
(S): Cancels processing.
(O): Reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC02001-E

Database access based on the execution history failed.

Description: An attempt to access the execution log-based database failed.
(S): Cancels the execution log information collection, inquiry, or deletion processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02002-W

An attempt to obtain the execution history has failed. (information = aa....aa)

aa....aa: Execution log item

Description: An attempt to obtain the execution log failed.
(S): Resumes processing.
(O): Check the message log file and eliminate the cause of the error. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02003-E

The execution history could not be inserted into the database.

Description: The execution log cannot be added to the database.
(S): Cancels the execution log collection processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02004-E

The execution history could not be fetched from the database.

Description: The execution log cannot be fetched from the database.
(S): Cancels the execution log inquiry processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02005-E

The execution history could not be deleted from the database.

Description: The execution log cannot be deleted from the database.
(S): Cancels the execution log deletion processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02501-E

A service call was interrupted by a data operation error. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Message ID of the error

Description: The invocation of a service component was interrupted due to a message data operation error.
(S): Cancels the service component call.
(O): An error occurred during the service component call. Reference the log file to check the error message indicated by the message ID, and then identify the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02502-E

A service call was interrupted by an invalid parameter. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Message ID of the error

Description: The invocation of a service component was interrupted because either the adapter definition or an argument from the requester is invalid.
(S): Cancels the service component call.
(O): An error occurred during the service component call. Reference the log file to check the error message indicated by the message ID, and then identify the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02503-E

A service call was interrupted by an exception in internal processing. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Message ID of the error

Description: The invocation of a service component was interrupted because an exception occurred in the internal processing.
(S): Cancels the service component call.
(O): An error occurred during the service component call. Reference the log file to check the error message indicated by the message ID, and then identify the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02504-E

A service call was interrupted by an unexpected error. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information1 = dd....dd, information2 = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Name of the exception

If an exception occurred: Name of the exception causing this error
If an exception did not occur: null

ee....ee: Detailed information

If an exception occurred: Message acquired from the exception
If an exception did not occur: Detailed information

Description: The invocation of a service component was interrupted because of an unexpected error.
(S): Cancels the service component call.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC02511-E

Initialization of the service adapter failed. (adapter name = aa....aa, information = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Message ID or exception name of the error

Description

An attempt to initialize the service adapter failed.

(S)

The service adapter start processing fails.

Cancels the service component call.

(O)

The adapter start processing failed. If the displayed Information is a message ID, reference the log file to check the corresponding error message, and identify the cause of the error log. If the cause of the error is associated with operations, re-execute the processing. If the displayed information is not an exception name or the cause of the error has nothing to do with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02512-E

An attempt to obtain the service adapter name has failed. (information = aa....aa)

aa....aa: Lookup name of the service adapter or the business process

Description: An attempt to obtain the lookup name of the service adapter or business process failed.
(S): The service adapter start processing fails.
(O): Check, and if necessary, revise the Naming Service settings. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02513-E

An attempt to read the file has failed. (adapter name = aa....aa, file name = bb....bb, information = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: File name

cc....cc: Detailed information

Description

An attempt to read the file failed.

(S)

The service adapter start processing fails.

Cancels the service call.

(O)

Check the adapter configuration to determine whether the file indicated in File name is included. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02514-E

A value in the definition file is invalid. (adapter name = aa....aa, operation name =bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Operation name

When information is specified for each operation: Operation name
When information is not specified for each operation: null

cc....cc: Parameter name

Description: A value in the definition file is invalid.
(S): The service adapter start processing fails.
(O): Check the information that was entered when the service adapter was created. Check information about the called service component. If the information has been modified, re-create the adapter. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02515-E

A value in the WSDL file is invalid. (adapter name = aa....aa, operation name = bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Operation name

When information is specified for each operation: Operation name
When information is not specified for each operation: null

cc....cc: Parameter name

Description: A value in the WSDL file is invalid.
(S): The service adapter start processing fails.
(O): Check information about the called service component. If the information has been modified, re-create the adapter. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02516-E

The specified operation was not found. (adapter name = aa....aa, operation name = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Operation name

Description: The specified operation was not found.
(S): Cancels the service component call.
(O): Check information about the called operations and then re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02517-E

An attempt to transform the data failed. (adapter name = aa....aa, source FormatID = bb....bb, source message type = cc....cc, destination FormatID = dd....dd, destination message type = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Format ID before transformation

cc....cc: Message type before transformation

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

dd....dd: Format ID after transformation

ee....ee: Message type after transformation

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description: An attempt to transform data failed.
(S): Cancels the service component call.
(O): Check the message format ID in the information about the service component that was called. Check the data transformation and data format definitions. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02518-E

The message formats conflict. (adapter name = aa....aa, source FormatID = bb....bb, source message type = cc....cc, destination FormatID = dd....dd, destination message type = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Comparison source format ID

cc....cc: Comparison source message type

XML: XML message
Binary: Binary message
ANY: Any message
NONE: No message
UNKNOWN (Value): Unexpected message format

dd....dd: Comparison destination format ID

ee....ee: Comparison destination message type

XML: XML message
Binary: Binary message
ANY: Any message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description: The message formats do not match.
(S): Cancels the service component call.
(O): Check the message format ID and message type in the information about the service component that was called. The service component that is called is may be a service component that does not allow absence of request messages, so check and if necessary, revise the service component type and request message. In the case of data transformation, check the data transformation definitions and data format definitions. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02519-W

An exception occurred but processing will continue. (adapter name = aa....aa, information1 = bb....bb, information2 = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Exception name

cc....cc: Message acquired from the exception

Description: An exception occurred in the service adapter, but the processing will continue.
(S): Resumes processing.
(O): If the cause of the exception can be identified from the exception name or the message acquired from the exception, take appropriate action. Collect the log and trace information, and then contact the maintenance personnel.

KDEC02520-E

The specified data transform definition does not exist. (adapter name = aa....aa, source FormatID = bb....bb, destination FormatID = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Format ID before transformation

cc....cc: Format ID after transformation

Description: The specified data transformation definition does not exist.
(S): Cancels the service component call.
(O): Check the format definition and data transformation definition that were specified when the adapter was created. If a required format definition or data transformation definition is missing, enter the definition and re-create the adapter. Check the data transformation and data format definitions. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02521-E

The adapter state is invalid. (adapter name = aa....aa, information = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Detailed information

Description

The status of the service adapter is invalid.

(S)

The service adapter start processing fails.

Cancels the service component call.

(O)

Restart the adapter. Collect the log and trace information, and then contact the maintenance personnel.

KDEC02523-E

An unsupported data conversion was executed. (adapter name = aa....aa, source FormatID = bb....bb, source message type = cc....cc, destination FormatID = dd....dd, destination message type = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Comparison source format ID

cc....cc: Comparison source message type

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

dd....dd: Comparison destination format ID

ee....ee: Comparison destination message type

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description: An unsupported data transformation was executed.
(S): Cancels the service component call.
(O): Check the data transformation supported by the adapter. Check the format definition and data transformation definition that were specified when the adapter was created. If a required format definition or data transformation definition is missing, enter the definition and re-create the adapter. Check the data transformation and data format definitions in the data transformation directory. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC02524-E

An attempt to validate a message has failed. (adapter name = aa....aa, FormatID = bb....bb)

aa....aa: Adapter name

bb....bb: Message format ID

Description: An attempt to validate a message failed.
(S): Cancels the service call.
(O): An attempt to validate the message format definition corresponding to the message format ID has failed. Either the user message to be sent or received is invalid or the defined format definition is invalid. Check the message log file and eliminate the cause of the error.

KDEC02525-W

The property contains an invalid value. The default value will be used. (adapterName = aa....aa, key = bb....bb, specified value = cc....cc, used value = dd....dd)

aa....aa: Adapter name

bb....bb: Key

cc....cc: Definition value

dd....dd: Used value

Description: A value defined in the client definition file is invalid. The default value will be used.
(S): The processing continues.
(O): Check and correct the client definition file settings.

KDEC02526-E

A value in the JSON-XML converter definition file is invalid. (adapter name = aa....aa, parameter = bb....bb, value = cc....cc)

aa....aa: Adapter name

bb....bb: Parameter name

cc....cc: Value

Description: A value in the JSON-XML transformation definition file is invalid.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the contents of the JSON-XML transformation definition file.

KDEC02527-E

An attempt convert JSON to XML failed. (adapter name = aa....aa, operation name = bb....bb, telegram type = cc....cc, information = dd....dd)

aa....aa: Adapter name

bb....bb: Operation name

cc....cc: Message type before transformation

JSON: JSON message
XML: XML message

dd....dd: Message acquired from the exception

Description: An attempt to perform JSON-XML transformation failed.
(S): Processing is interrupted.
(O): Check the message log file and the error message that was output before this message, and then eliminate the cause of the error. In addition, check and, if necessary, revise the specified message and the response message from the service.

KDEC02528-E

The value specified for an element in the header text is invalid. (adapter name = aa....aa, operation name = bb....bb, element name = cc....cc, namespace = dd....dd, value = ee....ee)

aa....aa: Adapter name

bb....bb: Operation name

cc....cc: Element name

dd....dd: Namespace

ee....ee: Value

Description: The value of an element specified in the header message is invalid.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the specified message.

KDEC03001-E

A service call was interrupted because a SOAP access error was detected. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Message acquired from the exception

Description

The invocation of a service component was interrupted because a SOAP communication error was detected.

(S)

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error. If the error was caused by any of the following operational problems, re-execute the processing:

Make sure that the service component is running.
Make sure that the correct service information was specified when the adapter was created.
Check the message log file for an entry of SOAP error information.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03002-E

A service call was interrupted because an EJB access error was detected. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Message acquired from the exception

Description

The invocation of a service component was interrupted because an error was detected in the EJB invocation.

(S)

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error. If the error was caused by any of the following operational problems, re-execute the processing:

Make sure that the service component is running.
Make sure that the correct service information was specified when the adapter was created.
Check the message log file for an entry of EJB error information.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03003-E

A service call was interrupted because an error was detected during asynchronous message sending. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, information = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Message acquired from the exception

Description

The invocation of a service component was interrupted because an error was detected during an asynchronous message sending.

(S)

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error. If the error was caused by any of the following operational problems, re-execute the processing:

Make sure that the queue exists.
Make sure that the queue attributes are correct.
Check the message log file for an entry of Reliable Messaging error information.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03005-E

A service call was interrupted because a custom service access error was detected. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, error message = dd....dd, code = ee....ee)

aa....aa: Service ID of the service adapter or the business process

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Error message set up by the custom adapter developer^#

When an error message has been set up: Error message set up by the custom adapter developer
When no error message has been set up: null

ee....ee: Error code set up by the custom adapter developer

When an error code has been set up: Error code set up by the custom adapter developer
When no error code has been set up: null

Description: The invocation of a service component was interrupted because an exception was detected from the custom protocol converter implemented by the custom adapter developer.
(S): Cancels the service component call.
(O): Check the message log file and eliminate the cause of the error. Check the error message and error code and then take appropriate action according to the custom adapter manual. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.
#: A custom adapter is an adapter that is provided with the product and implemented by using the General custom adapter and the custom adapter development framework.

KDEC03006-E

An undefined error occurred while the web service was executing. (fault code = aa....aa, fault string = bb....bb, fault actor = cc....cc)

aa....aa: faultcode value in the received SOAP Fault

bb....bb: faultstring value in the received SOAP Fault

cc....cc: faultactor value in the received SOAP Fault

Description: An undefined exception occurred while Web Service was being executed.
(S): Cancels the service component call.
(O): A user-undefined failure occurred during execution of Web Services. Check and, if necessary, revise the service component specifications, the soapfault-handling-mode definition in the HCSC server runtime definition, or the message sent to Web Services, and then re-execute the processing.

KDEC03007-E

A service call was interrupted. (HCSCCommonID = aa....aa, ServiceRequestID = bb....bb, RootApInfo = cc....cc)

aa....aa: HCSC message common ID

Displays the identification information (message common ID) allocated to each request from service requesters.

bb....bb: Service request ID

Displays the identification information (service request ID) allocated to individual service component invocation processing within the HCSC server.

cc....cc: Root application information

Displays the root application information (IP address, process ID, and communication number) of the performance analysis trace maintained by the current thread, with a string expression.

Description: The invocation of a service component was interrupted.
(S): Cancels the service component call.
(O): Reference the message log file, error message output before this message, and then eliminate the cause of the error.

KDEC03011-E

The service is not supported. (adapter name = aa....aa, operation name = bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Operation name

When information is specified for each operation: Operation name
When information is not specified for each operation: null

cc....cc: Item

encode-style: SOAP encoding style (Web Services or SessionBean)
binding-style: SOAP binding style (Web Services or SessionBean)
Attachment: Number of attachments in SOAP (Web Services)
content-type: Content type of SOAP attachments (Web Services)
message-type: Message type
namespace: Namespace qualifier (Web Services or SessionBean)

Description: The service is not supported.
(S): Cancels the service component call.
(O): Check the services supported by HCSC. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03012-E

The telegram format is not supported. (adapter name = aa....aa, telegram type = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Message format

XML: XML message
Binary: Binary message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description: The message format is not supported.
(S): Cancels the service component call.
(O): Check the format of the message that is to be sent to the service component and then re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03013-E

An attempt to make a telegram failed because an exception occurred. (adapter name = aa....aa, information = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Exception causing the error

Description: An attempt to generate a message failed because an exception occurred.
(S): Cancels the service component call.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03014-W

An exception occurred in the protocol converter but processing will continue. (adapter name = aa....aa, information1 = bb....bb, information2 = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Exception name

cc....cc: Message acquired from the exception

Description: An exception occurred in the service adapter, but the processing will continue.
(S): Resumes processing.
(O): If the cause of the exception can be identified from the exception name or the message acquired from the exception, take appropriate action. Collect the log and trace information, and then contact the maintenance personnel.

KDEC03015-E

An initialization error occurred in the protocol converter. (adapter name = aa....aa, information = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Name of the exception causing this error

Description

An initialization error occurred in the protocol converter.

(S)

Deployment of the service adapter fails.

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03016-E

The message type set in the custom adapter is invalid. (adapter name = aa....aa, message type = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Message format

XML: XML message
Binary: Binary message
ANY: Any message
NONE: No message
UNKNOWN (Value): Unexpected message format

Description

The message type set in the custom adapter^# is invalid.

(S)

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error.

Check the information about the custom adapter. If it differs from the information assumed by the custom protocol converter, correct the information, and then re-create the adapter.
Correct the specified message format to match the adapter's message format, and then re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

#

A custom adapter indicates a general-purpose custom adapter.

KDEC03017-E

The message has already been stored. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description

An attempt was made to set up a message in the message container by using the custom protocol converter, but the message had already been set up.

(S)

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error.

The custom adapter developer^# must check and, if necessary, revise the implemented custom protocol converter.
Re-create the adapter.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

#

A custom adapter is a General custom adapter.

KDEC03018-E

The message is invalid. (adapter name = aa....aa, information = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Code of the error

Description

An invalid message is set up in the message container, with the custom protocol converter.

(S)

Cancels the service component call.

(O)

Check the message log file and eliminate the cause of the error.

The custom adapter^# developer must check, and if necessary, revise the implemented custom protocol converter.
Re-create the adapter.
Check the message and then re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

#

A custom adapter is a General custom adapter.

KDEC03019-E

An unsupported data conversion is defined. (adapter name = aa....aa, operation name = bb....bb, standard FormatID = cc....cc, service FormatID = dd....dd)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Operation name

cc....cc: Standard format ID

dd....dd: Service format ID

Description

An unsupported data transformation is defined.

(S)

Deployment of the service adapter fails.

Cancels the service component call.

(O)

Check the data transformation supported by the adapter. Check the format definition and data transformation definition that were specified when the adapter was created. If a required format definition or data transformation definition is missing, enter the definition and re-create the adapter. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03020-E

The custom converter class name is not defined. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description

The custom converter class name is not defined.

(S)

Deployment of the service adapter fails.

(O)

Define a user-implemented class name in the property file for custom adapter development Frame Work (framework_properties.xml).

Re-create the adapter.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03021-E

An unexpected exception occurred during custom adapter processing. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID =cc....cc, information1 = dd....dd, information2 = ee....ee)

aa....aa: Custom adapter service ID

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Exception name or error name

ee....ee: Detailed information (Message acquired from the exception or the error)

Description: An unexpected exception occurred during the processing of the custom adapter.
(S): Cancels the service component call.
(O): Collect the log and the trace information, and contact the developer for the Java implementation of the custom adapter displayed with service ID of the custom adapter. If the custom adapter is a General custom adapter or an adapter that is provided with the product and implemented by using the custom adapter development framework, contact Maintenance Service.

KDEC03022-E

The telegram is invalid. (adapter name = aa....aa, information = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Detailed information

The telegram is not XML.
The SOAP Body was not found.
The Element inside SOAP Body was not found.
The endpointURL is invalid.

Description

The message is invalid.

(S)

Cancels the service component call.

(O)

Check the format of the message that is to be sent to the service component and then re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC03023-W

An attempt to parse Cookie failed. (adapter name = aa....aa, information1 = bb....bb, information2 = cc....cc)

aa....aa: Adapter name

bb....bb: Name of the exception

cc....cc: Message acquired from the exception

Description: An attempt to parse a Cookie failed.
(S): The processing continues.
(O): Check whether the Cookie sent from the service component contains an invalid string.

KDEC03024-E

An undefined error occurred when the web service was executing. (Code = aa....aa, Reason = bb....bb, Role = cc....cc, Node = dd....dd)

aa....aa: Code value of the received SOAP Fault

bb....bb: Reason value of the received SOAP Fault

cc....cc: Role value of the received SOAP Fault

dd....dd: Node value of the received SOAP Fault

Description: An undefined exception occurred while Web Service was being executed.
(S): The service component invocation is cancelled.
(O): A user-undefined failure occurred during execution of Web Services. Check and, if necessary, revise the service component specifications, the soapfault-handling-mode definition in the HCSC server runtime definition, or the message sent to Web Services, and then re-execute the Web Services.

KDEC03025-E

The specified soap header was not found. (adapter name = aa....aa, soap header element name = bb....bb)

aa....aa: Adapter name

bb....bb: SOAP header element name

Description: The SOAP header specified in the service adapter definition file was not found.
(S): The invocation of the service is interrupted.
(O): Check the SOAP header that was entered when the service adapter was created, and make sure that the request was made with the correct SOAP header element name and namespace. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC03026-E

The connection information is set more than once. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

Description: The connection information for a service request is set more than once.
(S): The invocation of the service is interrupted.
(O): Specify the connection information only once for a service request in a development environment business process.

KDEC03027-E

The service call of the specified connection was stopped. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, endpointURL = dd....dd)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Endpoint URL

Description: The invocation of a service for a specified connection was interrupted.
(S): The invocation of the service is interrupted.
(O): Make sure that the endpoint URL of the service specified for invoking the service adapter is correct.

KDEC03028-E

An endpointURL element was not found in the set connection information. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

Description: The endpointURL element was not found in the connection information set when the service request was made.
(S): The invocation of the service is interrupted.
(O): Specify the correct endpointURL element for the connection information in the development environment, and then re-package the service adapter.

KDEC03029-W

The host attribute was not found in the set cookie information when a service request was made. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, cookie information cookie name = dd....dd, cookie information path attribute = ee....ee)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Cookie information (cookie name)

ee....ee: Cookie information (path attribute)

Description: The host attribute was not found in the cookie information set when a service request was made.
(S): Processing continues.
(O): Make sure that the data transformation and mapping definitions of the business process are correct.

KDEC03030-W

The cookie information specified in the message cannot be sent because it is not the same as the cookie information issued by service being invoked. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, cookie information cookie name = dd....dd, cookie information host attribute = ee....ee, cookie information path attribute = ff....ff)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Cookie information (cookie name)

ee....ee: Cookie information (host attribute)

ff....ff: Cookie information (path attribute)

Description: The cookie information specified in the request message cannot be sent because this information is not the cookie information issued by the service being invoked.
(S): Processing continues.
(O): Make sure that the host name and path of the cookie information matches with that of the service to be invoked. The host name must be a complete match and the path name must be a forward match.

KDEC03031-E

An error occurred during parsing of the header message. (adapter name = aa....aa, information = bb....bb)

aa....aa: Adapter name

bb....bb: Message obtained from the exception that caused the error

Description

An error occurred during the parsing of the header message.

(S)

The invocation of the service is interrupted.

(O)

See the exception log file, and eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC03032-E

The combination of the specified QName and the header message is invalid. (adapter name = aa....aa, QName1 = bb....bb, QName2 = cc....cc)

aa....aa: Adapter name

bb....bb: String expression of QName

cc....cc: String expression of QName for the root element of the header message

Description

The specified QName and header message combination is invalid.

(S)

The invocation of the service is interrupted.

(O)

Collect the log and trace information, and then contact the custom adapter developer.

The custom adapter developer must check and, if necessary, revise the implemented protocol converter processing, and make sure that the QName and header message are specified. If these items are specified, check the consistency of the set QName and header message. If the cause of the error is not associated with operations, and then contact maintenance personnel.
If the custom adapter is of a type that is provided with the product and implemented by using the general-purpose custom adapter and the custom adapter development framework, contact maintenance personnel.

KDEC03033-E

A request message passed from a business process is invalid. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, RootApInfo = dd....dd, error message = ee....ee)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Root application information

ee....ee: Detailed message

Description: A request message passed from a business process is invalid.
(S): Interrupts the invocation of the service.
(O): See the information in the detailed message, and then correct the header message that is to be passed from the business process according to the adpsoap_attachment_request.xsd specifications.

KDEC03034-E

An attempt to read the file has failed. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, RootApInfo = dd....dd, error message = ee....ee)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Root application information

ee....ee: Detailed message

Description: An attempt to read the file that is to be sent to the service component failed.
(S): Interrupts the invocation of the service.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC03035-E

An attempt to receive an attached file failed because reception settings are not set. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, RootApInfo = dd....dd)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Root application information

Description: An attempt to receive an attached file failed because output-folder-name was not set in the header message passed from a business process.
(S): Interrupts the invocation of the service.
(O): Correct the header message that is to be passed from the business process according to the adpsoap_attachment_request.xsd specifications.

KDEC03036-E

An error occurred while the MIME header of an attached file was being analyzed. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, RootApInfo = dd....dd, error message = ee....ee)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Root application information

ee....ee: Detailed message

Description: The header information in the attached file sent from a service component is invalid.
(S): Interrupts the invocation of the service.
(O): Check the detailed message, and then correct the message that is to be sent from the service component.

KDEC03037-E

An error occurred while an attached file was being received. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, RootApInfo = dd....dd, error message = ee....ee)

aa....aa: Adapter name

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Root application information

ee....ee: Detailed message

Description: An attempt to receive an attached file sent from the service component failed.
(S): Interrupts the invocation of the service.
(O): Eliminate the cause of the error, and then re-execute the processing.

KDEC04501-E

An attempt to read the HCSC server settings file has failed. (file name = aa....aa)

aa....aa: File name

Description: An attempt to read the HCSC server settings file failed.
(S): Cancels processing.
(O): Make sure that the file displayed in file name exists, or it can be read.

KDEC04502-E

The HCSC server name is invalid. (name = aa....aa)

aa....aa: HCSC server name

Description: The name of the HCSC server is invalid.
(S): Cancels processing.
(O): Specify the correct HCSC server name in the command.

KDEC04503-E

The contents of the HCSC server settings file are invalid. (file name = aa....aa, parameter = bb....bb)

aa....aa: HCSC server settings file name

bb....bb: Parameter name

Description: The contents of the HCSC server settings file are invalid.
(S): Cancels processing.
(O): Check the settings specified in the settings file name described in file name, modify the contents, and then re-execute the processing.

KDEC04504-E

The HCSC server initialization failed.

Description

An attempt to initialize the HCSC server failed.

(S)

Interrupts the initialization of the HCSC server.

For restarting the HCSC server, retry the initialization of the HCSC server.

If another attempts to initialize the HCSC server fails, this message is output again.

(O)

Check the message log file, eliminate the cause of the error, and then re-execute the processing.

KDEC04505-E

Initialization of the HCSC server failed. (cause = aa....aa)

aa....aa: Detailed cause

Description: An attempt to initialize the HCSC server failed.
(S): Cancels the server start processing.
(O): Eliminate the cause of the error based on the indicated details, and then re-execute the processing.

KDEC04506-E

The HCSC server is not running. (status = aa....aa)

aa....aa: HCSC server status

1: Starting
2: Started
4: Stopped
5: Stopping

Description: The HCSC server is not running.
(S): Cancels processing.
(O): Check the status of the HCSC server.

KDEC04510-E

The reception is not terminating. (status = aa....aa)

aa....aa: Standard reception status

1: Starting
2: Started
3: Start error
4: Stopped
5: Stopping
6: Stop error

Description: The standard reception status is not Stopping.
(S): Cancels processing.
(O): Check the status of the standard reception.

KDEC04511-E

The reception has not stopped. (status = aa....aa)

aa....aa: Standard reception status

1: Starting
2: Started
3: Start error
5: Stopping
6: Stop error

Description

The standard reception is still running.

(S)

Cancels processing.

(O)

The action differs according to the command being executed while this message is displayed.

If the cscsvstop command is executed

Take action according to the standard reception status displayed in the message:

Standard reception status	Action
`1: Starting` `3: Start error` `5: Stopping` `6: Stop error`	Specify the `-stopfg force` option and execute the `cscrcptnstop` command to stop the standard reception, and then re-execute the `cscsvstop` command.
`2: Started`	Execute the `cscrcptnstop` command to stop the standard reception, and then re-execute the `cscsvstop` command.

Standard reception status

Action

1: Starting

3: Start error

5: Stopping

6: Stop error

Specify the -stopfg force option and execute the cscrcptnstop command to stop the standard reception, and then re-execute the cscsvstop command.

2: Started

Execute the cscrcptnstop command to stop the standard reception, and then re-execute the cscsvstop command.

If the cscrcptnstart command is executed

Specify the -stopfg force option and execute the cscrcptnstop command to stop the standard reception, and then re-execute the cscrcptnstart command.

KDEC04512-E

The reception is not starting. (status = aa....aa)

aa....aa: Standard reception status

1: Starting
2: Started
3: Start error
4: Stopped
5: Stopping
6: Stop error

Description: The standard reception is not starting.
(S): Cancels processing.
(O): Specify the -stopfg force option, and then execute the cscrcptnstop command to stop the standard reception.

KDEC04513-E

The reception is not terminating.

Description: The status of the user-defined reception is not Stopping.
(S): Cancels processing.
(O): Check the status of the user-defined reception.

KDEC04514-E

The reception has not stopped.

Description: The user-defined reception is still running.
(S): Cancels processing.
(O): Check the status of the user-defined reception. Note that while terminating the HCSC server, you need to terminate all the user-defined receptions.

KDEC04515-E

The reception is not starting.

Description: The user-defined reception is not starting.
(S): Cancels processing.
(O): Check the status of the user-defined reception. Wait until the processing to start the request reception ends, and then re-execute the processing.

KDEC04516-E

The specified content is invalid. (file name = aa....aa, information = bb....bb)

aa....aa: File name

bb....bb: Detailed information

Description: The contents of the file specified in the file name are invalid.
(S): Cancels processing.
(O): Check the contents defined in the file that is displayed in the file name. If the file name wherein an error was detected is the SOAP Fault operation definition file, check and if necessary, revise the contents of the definition.

KDEC04517-E

An attempt to change the HCSC status failed because DB access failed. (type = aa....aa, status = bb....bb)

aa....aa: Status type where update failed

1: HCSC server status
2: Request reception status

bb....bb: Status after update failed

1: Starting
2: Started
3: Start error
4: Stopped
5: Stopping
6: Stop error

Description

An attempt to update the HCSC server status (HCSC server or request reception) failed because the database access failed.

(S)

Continues processing.

(O)

Check the database access error in the message log and eliminate the cause of the error. After the error has been corrected, take the following action to recover the status:

If the error occurred during HCSC server start or stop processing:: Forcibly terminate the HCSC server.
If the error occurred during standard reception start or stop processing:: Forcibly terminate the standard reception.

KDEC04518-E

The HCSC server cannot be accessed because it is now terminating.

Description: The HCSC server status cannot be referenced because the HCSC server is stopping.
(S): Cancels processing.
(O): Re-execute the processing after HCSC server termination processing finishes.

KDEC04519-E

The HCSC server cannot be stopped because other commands are executing.

Description: The HCSC server cannot be stopped because other commands are running.
(S): Cancels processing.
(O): The HCSC server termination command cannot be executed while another command, such as a status display command, is executing. Wait until processing of the current command terminates, and then re-execute the processing.

KDEC04520-E

The HCSC server table version is invalid. (table version = aa....aa, table revision = bb....bb)

aa....aa: Table version number

bb....bb: Table revision number

Description: The HCSC server table version is invalid.
(S): Cancels processing.
(O): Check the HCSC server's table version. If it is invalid, re-execute setup.

KDEC04601-I

The HCSC server has started.

Description: The start processing (initialization) of the HCSC server applications is complete.
(S): Continues the processing to start the HCSC server applications.

KDEC04602-I

The HCSC server has terminated.

Description: The end processing of the HCSC server applications is complete.
(S): Continues the processing to terminate the HCSC server application.

KDEC04603-I

The reception has terminated.

Description: The end processing of the request reception for the HCSC server applications is complete.
(S): Continues the processing to terminate the HCSC server application standard reception.

KDEC04604-I

The reception has started.

Description: The start processing (initialization) of the request reception for the HCSC server applications is complete.
(S): Continues the processing to start the HCSC server application standard reception.

KDEC04605-I

Termination (message monitoring) of the reception was canceled.

Description: The stop processing (message monitoring) of the request reception was canceled.
(S): Continues the processing to terminate the HCSC server application standard reception.

KDEC04609-E

An attempt to change the HCSC server status has failed. (type =aa....aa, status = bb....bb)

aa....aa: Status type where update failed

1: HCSC server status
2: Request reception status

bb....bb: Status after update failed

1: Starting
2: Started
3: Start error
4: Stopped
5: Stopping
6: Stop error

Description

An attempt to update the HCSC server status (HCSC server or request reception) failed.

(S)

Continues processing.

(O)

A data access error has occurred. After referencing the message log file and removing the error, perform the following tasks to recover the status:

When an attempt to update the status fails during the HCSC server start or stop processing: Forcibly terminate the HCSC server.
When an attempt to update the status fails during the request reception start or stop processing: Forcibly terminate the request reception.

KDEC04611-W

The service emulation function was enabled.

Description: The service emulation function was enabled.
(S): Continues processing.

KDEC05001-E

An attempt to open a connection to the database has failed. (reason = aa....aa, SQL state = bb....bb, error code = cc....cc)

aa....aa: Cause of exception

bb....bb: Code identifying the exception

cc....cc: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description

An attempt to open a connection to the database failed.

(S)

Cancels database connection processing.

(O)

Check the message log file and eliminate the cause of the error. Check, and if necessary, revise the DB Connector information specified in the HCSC server setup definition file, the specified DB Connector settings, the settings for the JDBC driver in use, and the database settings in order to identify the cause of the error.

If the cause of the error is KDJE50012-E or KFDJ02005-E, make sure that the value of <transaction-support> that is set in the attribute of DB Connector is NoTransaction, and the DB Connector of NoTransaction is specified in the property (dbcon-nodisplayname) of the HCSC server setup definition file.

If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05002-E

An attempt to close a connection to the database has failed. (reason = aa....aa, SQL state = bb....bb, error code = cc....cc)

aa....aa: Cause of exception

bb....bb: Code identifying the exception

cc....cc: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description

An attempt to close a connection to the database failed.

(S)

Cancels database connection release processing.

(O)

Check the message log file and eliminate the cause of the error. Check, and if necessary, revise the DB Connector information specified in the HCSC server setup definition file, the specified DB Connector settings, the settings for the JDBC driver in use, and the database settings in order to identify the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05003-E

An attempt to retrieve database information has failed. (information ID = aa....aa, table name = bb....bb, reason = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information
71: Asynchronous adapter deployment information
80: Business process basic information

bb....bb: Table name

cc....cc: Cause of exception

dd....dd: Code identifying the exception

ee....ee: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description

An attempt to retrieve the database information failed.

(S)

Cancels processing.

(O)

Check the message log file and eliminate the cause of the error. Check, and if necessary, revise the DB Connector information specified in the HCSC server setup definition file, the specified DB Connector settings, the settings for the JDBC driver in use, and the database settings in order to identify the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05004-E

An attempt to update database information has failed. (information ID = aa....aa, table name = bb....bb, reason = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information

bb....bb: Table name

cc....cc: Cause of exception

dd....dd: Code identifying the exception

ee....ee: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description

An attempt to update the database information failed.

(S)

Cancels processing.

(O)

Check the message log file and eliminate the cause of the error. Check, and if necessary, revise the DB Connector information specified in the HCSC server setup definition file, the specified DB Connector settings, the settings for the JDBC driver in use, and the database settings in order to identify the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05005-E

An attempt to delete database information has failed. (information ID = aa....aa, table name = bb....bb, reason = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information
71: Asynchronous adapter deployment information

bb....bb: Table name

cc....cc: Cause of exception

dd....dd: Code identifying the exception

ee....ee: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description

An attempt to delete the database information failed.

(S)

Cancels processing.

(O)

Check the message log file and eliminate the cause of the error. Check, and if necessary, revise the DB Connector information specified in the HCSC server setup definition file, the specified DB Connector settings, the settings for the JDBC driver in use, and the database settings in order to identify the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05006-E

An attempt to insert database information has failed. (information ID = aa....aa, table name = bb....bb, reason = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information
71: Asynchronous adapter deployment information

bb....bb: Table name

cc....cc: Cause of exception

dd....dd: Code identifying the exception

ee....ee: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description

An attempt to add the database information failed.

(S)

Cancels processing.

(O)

Check the message log file and eliminate the cause of the error. Check, and if necessary, revise the DB Connector information specified in the HCSC server setup definition file, the specified DB Connector settings, the settings for the JDBC driver in use, and the database settings in order to identify the cause of the error.

If the cause of the error is KDJE50012-E or KFDJ02005-E, make sure that the value of <transaction-support> that is set in the attribute of DB Connector is NoTransaction, and the DB Connector of NoTransaction is specified in the property (dbcon-nodisplayname) of the HCSC server setup definition file.

If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05008-E

An attempt to execute an SQL statement has failed. (reason = aa....aa, SQL state = bb....bb, error code = cc....cc)

aa....aa: Cause of exception

bb....bb: Code identifying the exception

cc....cc: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description: An attempt to execute an SQL statement for the database failed.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05009-E

An error occurred during rollback of a transaction. (reason = aa....aa, SQL state = bb....bb, error code = cc....cc)

aa....aa: Cause of exception

bb....bb: Code identifying the exception

cc....cc: Vendor specific exception code of the SQLException object

For details about the exception, reference the error information for each database.

Description: An error occurred while a transaction was being rolled back.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05010-W

There is a contradiction in information in the database. (information ID = aa....aa, maintenance information = bb....bb)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information

bb....bb: Maintenance information of the table containing the contradiction

Description: A contradiction was detected in the database information.
(S): Resumes processing.
(O): Check the message log file, collect the log and trace information, and then eliminate the cause of the error.

KDEC05011-E

Database access initialization failed because of an invalid parameter. (parameter = aa....aa, value = bb....bb)

aa....aa: Parameter name of the HCSC server property

bb....bb: Parameter value of the HCSC server property

Description: An attempt to initialize the database access when the HCSC server is not running failed because of an invalid parameter.
(S): Cancels database connection processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the HCSC server setup. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05012-E

Database access initialization, before HCSC server startup, failed because loading of the JDBC driver failed. (JDBC name = aa....aa)

aa....aa: JDBC driver name

Description: An attempt to initialize the database access when the HCSC server was not running failed because the JDBC driver could not be loaded.
(S): Cancels database connection processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the HCSC server setup. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05013-E

Database access initialization, at HCSC server startup, failed because the attempt to obtain the data source failed. (DataSource name = aa....aa)

aa....aa: Data source name

Description: An attempt to initialize the database access when the HCSC server is running failed because the data source could not be obtained.
(S): Cancels database connection processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the J2EE server setup. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05014-E

Database access initialization, before HCSC server startup, failed because a required parameter was not specified. (parameter = aa....aa)

aa....aa: Parameter name of the HCSC server property

Description: An attempt to initialize the database access when the HCSC server was not running failed because a required parameter was not specified.
(S): Cancels database connection processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the HCSC server setup. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05015-E

The database contains no information. (table name = aa....aa)

aa....aa: Table name

Description

There is no information in the database.

(S)

Processing is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC05016-E

An attempt to lock the database failed. (information ID = aa....aa, table name = bb....bb, reason = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Information type ID

70: Cluster basic information
71: Asynchronous adapter deployment information

bb....bb: Table name

cc....cc: Cause of the exception

dd....dd: Code identifying the exception

ee....ee: Vendor-specific exception code for the SQLException object

For details on the exception, see the error information for the databases.

Description

An attempt to lock the database failed.

(S)

Processing is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC05101-E

An attempt to setup system management information has failed. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An attempt to set up the system management information failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then reset the system management information.

KDEC05102-E

An attempt to initialize system management information has failed. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An attempt to initialize the system management information failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then restart the HCSC server.

KDEC05103-E

An attempt to perform unset up of system management information has failed. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An attempt to remove the setup of the system management information failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then unset up the system management information again.

KDEC05104-E

An attempt to retrieve system management information has failed. (information ID = aa....aa, error code = bb....bb, error message = cc....cc)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information
71: Asynchronous adapter deployment information

bb....bb: Error code

cc....cc: Error message

Description: An attempt to reference the system management information displayed in the information type ID has failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then re-execute the operation.

KDEC05105-E

An attempt to update system management information has failed. (information ID = aa....aa, error code = bb....bb, error message = cc....cc)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information

bb....bb: Error code

cc....cc: Error message

Description: An attempt to update the system management information displayed in the information type ID has failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then re-execute the operation.

KDEC05106-E

An attempt to delete system management information has failed. (information ID = aa....aa, error code = bb....bb, error message = cc....cc)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information
71: Asynchronous adapter deployment information

bb....bb: Error code

cc....cc: Error message

Description: An attempt to delete the system management information displayed in the information type ID has failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then re-execute the operation.

KDEC05107-E

An attempt to insert system management information has failed. (information ID = aa....aa, error code = bb....bb, error message = cc....cc)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information
70: Cluster basic information
71: Asynchronous adapter deployment information

bb....bb: Error code

cc....cc: Error message

Description: An attempt to add the system management information displayed in the information type ID has failed.
(S): Cancels processing.
(O): Take action for the message displayed in the error code, and then re-execute the operation.

KDEC05108-W

There is a contradiction in system management information. (information ID = aa....aa, maintenance information = bb....bb)

aa....aa: Information type ID

10: HCSC basic information
30: Location information
31: BP format ID information
41: Routing rule set up (rule set up definition) information
51: Data transformation utility (data transformation definition) information
52: Data transformation utility (format definition) information
60: Execution log information

bb....bb: Maintenance information for the system management information with contradiction

Description: A contradiction was detected in the contents of the system management information displayed in the information type ID.
(S): Resumes processing.
(O): Reference the message log file, and make sure that no error has occurred. If error occurs, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC05201-E

The specified directory does not exist. (directory name = aa....aa)

aa....aa: Specified directory name

Description: The directory specified in the output destination path for storing the system management information of the HCSC server, does not exist.
(S): Cancels processing.
(O): Check the contents specified in the hcscserver-data-filepath property of the HCSC server setup definition file. If the specified contents are correct, check that the specified directory exists or the structure of the specified directory is correct. Once the problem is resolved, reset the HCSC server. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05202-E

The structure of the specified directory is invalid. (directory name = aa....aa)

aa....aa: Specified directory name

Description: The information for the same HCSC server name exists in the directory specified in the output destination path for storing the system management information of the HCSC server.
(S): Cancels processing.
(O): Check the contents specified in the hcscserver-data-filepath property of the HCSC server setup definition file. If the specified contents are correct, check the structure of the specified directory and make sure that the directory is valid. If a directory with the same HCSC server name already exists, save and then delete the already existing file, and after that set up the HCSC server. Once the problem is resolved, reset the HCSC server. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05203-E

An attempt to perform a file or directory operation has failed. (name = aa....aa, operation = bb....bb)

aa....aa: File name or Directory name

bb....bb: Operation

Create: create
Delete: delete
Reference: read
Update: write

Description

An attempt to perform a file or directory operation failed.

(S)

Cancels processing.

(O)

Check the displayed file or directory. Also check the access permission of the file or the directory.

If the problem is not resolved even after re-executing the operations of the corresponding file or directory, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05204-E

The record file is invalid. (file name = aa....aa)

aa....aa: File path

Description: The record file is invalid.
(S): Cancels processing.
(O): Restart the HCSC server, and then re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05205-E

The index file is invalid. (file name = aa....aa)

aa....aa: File path

Description: The index file is invalid.
(S): Cancels processing.
(O): Restart the HCSC server, and then re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05206-E

An attempt to rename a file or directory failed. (source name = aa....aa, destination name = bb....bb)

aa....aa: File path before change

bb....bb: change destination file path

Description: An attempt to rename a file or a directory failed.
(S): Cancels processing.
(O): Check the access permission of the file or the directory displayed in the file path before change. If the file or the directory that is displayed in the change destination file path exists, save the corresponding file or directory, and then delete this file or directory. Then, restart the HCSC server and re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05207-E

The file or directory does not exist. (name = aa....aa)

aa....aa: File path

Description: The file or the directory does not exist.
(S): Cancels processing.
(O): Restart the HCSC server, and then re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05208-E

The file or directory already exists. (name = aa....aa)

aa....aa: File path

Description

The file or the directory already exists.

(S)

Cancels processing.

(O)

If the file or directory displayed in the file path exists, save the corresponding file or directory, and then delete this file or directory.

If a backup file with a suffix name (.old) exists in the directory that contains the file displayed in the file path, delete .old from that file name.

Then, restart the HCSC server and re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and contact maintenance personnel.

KDEC05209-E

The specified name is not a file. (name = aa....aa)

aa....aa: File path

Description: The specified name is not a file.
(S): Cancels processing.
(O): Restart the HCSC server, and then re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05210-E

The specified name is not a directory. (name = aa....aa)

aa....aa: File path

Description: The specified name is not a directory.
(S): Cancels processing.
(O): Restart the HCSC server, and then re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05211-E

An attempt to obtain a lock has failed.

Description: An attempt to obtain a lock has failed.
(S): Cancels processing.
(O): The other operations being performed for the HCSC server might not be completed. Re-execute the operation after completing other operations. If the Component Container administrator is changed, make sure that change of the Service Coordinator administrator is also completed. If the problem is not resolved, restart the HCSC server, and then re-execute the operation. If the problem is not resolved even after restarting the HCSC server, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05212-E

A security exception occurred.

Description: A security exception occurred.
(S): Cancels processing.
(O): Check the contents of the security policy file of service platform, and make sure that the directory specified in the hcscserver-data-filepath property can be read and written. Then, restart the HCSC server and re-execute the operation. If the problem is not resolved, collect the log, trace and the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file, and then contact maintenance personnel.

KDEC05301-E

An unexpected error occurred in the exclusion management API. (cause = aa....aa)

aa....aa: Cause

Description: An unexpected error occurred in the exclusion management API.
(S): An exception is reported.
(O): Contact maintenance personnel.

KDEC05302-E

A java.io.FileNotFoundException occurred in the exclusion management API. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description

A java.io.FileNotFoundException exception occurred in the exclusion management API. The possible causes are as follows:

The target file does not exist.
The target file cannot be accessed.

(S)

An exception is reported.

(O)

See the cause described in the message and eliminate the error.

KDEC05303-E

An exception occurred while the constructor in the java.io.File. (parent path = aa....aa, child path = bb....bb, cause = cc....cc)

aa....aa: Parent directory path

bb....bb: File name path

cc....cc: Cause

Description: An exception occurred during the execution of the java.io.File constructor.
(S): An exception is reported.
(O): Contact maintenance personnel.

KDEC05304-E

A directory cannot be specified for the method of the exclusion management API. (file path = aa....aa, method name = bb....bb)

aa....aa: File path

bb....bb: Method name

Description: a directory cannot be specified for the method of the exclusion management API.
(S): An exception is reported.
(O): Make sure that the file path is specified correctly.

KDEC05305-E

A thread interrupted the retry processing of a lock or the creation of a write flag file. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: A thread interrupted the retry processing of a lock or the creation of a write flag file.
(S): An exception is reported.
(O): Contact maintenance personnel.

KDEC05306-E

An exception occurred with getCanonicalPath method in the java.io.File. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: An exception occurred with the getCanonicalPath method in java.io.File.
(S): An exception is reported.
(O): The specified file is incorrect. Check the file path.

KDEC05307-E

There is an inconsistency between the mode specified when a file was locked and the method that was invoked. (file path = aa....aa, lock mode = bb....bb, method name = cc....cc)

aa....aa: Full file path

bb....bb: Lock mode

cc....cc: Name of the invoked method

Description: There is an inconsistency between the mode specified when a file was locked and the method that was invoked.
(S): An exception is reported.
(O): The API usage is incorrect. Contact maintenance personnel.

KDEC05308-E

A timeout occurred during lock processing. (file path = aa....aa, lock mode = bb....bb, cause = cc....cc)

aa....aa: Full file path

bb....bb: Lock mode

cc....cc: Cause

Description: A timeout occurred during the lock processing.
(S): An exception is reported.
(O): Another process might be using the target file. After the file is used, re-execute the processing.

KDEC05309-E

An attempt to release a lock has failed. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: An attempt to release a lock failed.
(S): An exception is reported.
(O): Contact maintenance personnel.

KDEC05310-E

A java.io.SecurityException occurred in the exclusion management API. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: A java.io.SecurityException exception occurred in the exclusion management API.
(S): An exception is reported.
(O): Check the security manager settings.

KDEC05311-E

A java.io.IOException occurred in the exclusion management API. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: A java.io.IOException exception occurred in the exclusion management API.
(S): An exception is reported.
(O): Check the specified file, access permissions, and network status.

KDEC05312-E

The specified file or directory to delete does not exist. (file path = aa....aa)

aa....aa: Full file path

Description: The file or the directory to be deleted does not exist.
(S): An exception is reported.
(O): Another process might have already deleted the target file, or there might be a network problem. Check the status of the network.

KDEC05313-E

The acquisition of a lock failed because a write flag file already exists. (file path = aa....aa, lock mode = bb....bb)

aa....aa: File path

bb....bb: Lock mode

Description: An attempt to obtain a lock failed because a write flag file already exists.
(S): An exception is reported.
(O): The file to be read might be damaged. Delete the file.

KDEC05314-E

A directory for write flag files does not exist. (file path = aa....aa)

aa....aa: File path

Description

The directory for the write flag file does not exist.

(S)

An exception is reported.

(O)

Make sure that the file is specified correctly.

Also, make sure that you have the appropriate permissions to create a directory.

KDEC05315-E

Retry processing could not be performed during lock processing because an error occurred. (file path = aa....aa, lock mode = bb....bb, cause = cc....cc)

aa....aa: File path

bb....bb: Lock mode

cc....cc: Cause

Description: the retry processing could not be performed during the lock processing because an error occurred.
(S): An exception is reported.
(O): Contact maintenance personnel.

KDEC05316-E

A java.nio.file.NoSuchFileException occurred in the exclusion management API. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: A java.nio.file.NoSuchFileException exception occurred in the exclusion management API. The target file or directory might not exist.
(S): An exception is reported.
(O): See the cause of the error indicated in the message, and then make sure that the file or directory exists.

KDEC05317-E

A java.nio.file.AccessDeniedException occurred in the exclusion management API. (file path = aa....aa, cause = bb....bb)

aa....aa: Full file path

bb....bb: Cause

Description: A java.nio.file.AccessDeniedException exception occurred in the exclusion management API. The target file or directory might not be accessible.
(S): An exception is reported.
(O): See the cause of the error indicated in the message, and then make sure that the file or directory can be accessed.

KDEC05501-E

An attempt to specify telegram settings has failed. (telegram type = aa....aa)

aa....aa: Message type

XML: XML message
BINARY: Binary message
ANY: Any message
DOM: DOM
NODE_VALUE: Sub element
SUB_TREE: Sub tree

Description: An attempt to specify the message settings failed.
(S): Cancels processing.
(O): Check the message log file and take appropriate action according to the messages displayed before and after this message.

KDEC05502-E

An attempt to obtain a telegram has failed. (telegram type = aa....aa)

aa....aa: Message type

XML: XML message
BINARY: Binary message
ANY: Any message
DOM: DOM
NODE_VALUE: Sub element
SUB_TREE: Sub tree
COMMON: Internal common data
TELEGRAM: User message trace data

Description: An attempt to obtain a message failed.
(S): Cancels processing.
(O): Check the message log file and take appropriate action according to the messages displayed before and after this message.

KDEC05503-W

An exception occurred during checking of the telegram format. (exception = aa....aa)

aa....aa: Exception name

CSCDataTransformException: The message does not match the format definition.

Description: An exception was detected during the validity check of the message format.
(S): Continues processing.
(O): Check the message to determine whether its format matches the format definition. If the message format matches the format definition, reference the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05504-E

An attempt to specify format definition settings has failed. (information1 = aa....aa, information2 = bb....bb)

aa....aa: Maintenance information (Cache name)

bb....bb: Maintenance information (Format definition type)

XML: XML format
BINARY: Binary format

Description: An attempt to specify the format definition settings failed.
(S): Cancels processing.
(O): Check the message log file and take appropriate action according to the messages displayed before and after this message.

KDEC05505-E

An attempt to copy a telegram failed because an exception occurred. (exception = aa....aa)

aa....aa: Exception name

Description: An attempt to copy a message failed because an exception was detected.
(S): Cancels processing.
(O): Reference the message log file, and take appropriate action according to the messages that were displayed before and after this message. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC05506-E

An exception occurred during checking of the telegram format. (exception = aa....aa)

aa....aa: Exception name

Description: An exception was detected during the validity check of the message format.
(S): Cancels processing.
(O): Check the message to determine whether its format matches the format definition. If the message format matches the format definition, reference the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC06001-E

Startup processing failed because the definition file could not be read.

Description: the start processing failed because the definition file could not be read.
(S): Cancels the start processing.
(O): Check the message log file and take appropriate action according to the log message that was displayed before this message.

KDEC06002-E

An attempt to access a database has failed. (definition type = aa....aa, access type = bb....bb)

aa....aa: Definition type

FORMAT: Format definition
TRANSFORM: Data transformation definition

bb....bb: Access type

INSERT: Add
DELETE: Delete

Description: An attempt to access a database failed.
(S): Cancels processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC06003-E

The specified FormatID is invalid. (FormatID = aa....aa)

aa....aa: Format ID

When a format ID exists: Format ID
When the format ID is blank: null

Description: The specified format ID is invalid.
(S): Cancels processing.
(O): Check, and if necessary, revise the specified ID, and then re-execute the processing.

KDEC06004-E

The format definition file corresponding to the specified FormatID does not exist. (FormatID = aa....aa)

aa....aa: Format ID

Description: The format definition file corresponding to the specified format ID does not exist.
(S): Cancels processing.
(O): Check, and if necessary, revise the specified ID, and then re-execute the processing.

KDEC06005-E

The data transform definition corresponding to the specified FormatID does not exist. (source FormatID = aa....aa, destination FormatID = bb....bb)

aa....aa: Format ID before transformation

bb....bb: Format ID after transformation

Description: The data transformation definition file corresponding to the specified format ID does not exist.
(S): Cancels processing.
(O): Check, and if necessary, revise the specified ID, and then re-execute the processing.

KDEC06006-E

The format definition file corresponding to the specified FormatID already exists. (FormatID = aa....aa)

aa....aa: Format ID

Description: The format definition file corresponding to the specified format ID already exists.
(S): Cancels processing.
(O): Check, and if necessary, revise the specified ID, and then re-execute the processing.

KDEC06007-E

The data transform definition file corresponding to the specified FormatID already exists. (source FormatID = aa....aa, destination FormatID = bb....bb)

aa....aa: Format ID before transformation

bb....bb: Format ID after transformation

Description: The data transformation definition file corresponding to the specified format ID already exists.
(S): Cancels processing.
(O): Check, and if necessary, revise the specified ID, and then re-execute the processing.

KDEC06008-E

Data transformation failed. (information1 = aa....aa, information2 = bb....bb, information3 = cc....cc)

aa....aa: Maintenance information (Hash code of the message container or detailed message for the exception)

bb....bb: Maintenance information (Cache name or additional information)

cc....cc: Maintenance information (Message name after transformation (if blank: null) or method name (transform, notTransform, or notTransformWithDtSkip)

Description

The data transformation failed.

(S)

Cancels processing.

(O)

Check the message log file and take appropriate action according to the messages displayed before and after this message.

If the data transformation fails in the TP1/RPC reception or custom adapter^#, take appropriate action (as described below) based on the information output in maintenance information (method name).

If the maintenance information (method name) indicates transform or notTransform:

Check the maintenance information (detailed message for the exception) and the message log file, and take appropriate action according to the messages displayed before and after this message.
If the maintenance information (method name) indicates notTransformWithDtSkip:

Check the maintenance information (detailed message for the exception) and the message log file, and take appropriate action according to the messages displayed before and after this message.

For a TP1/RPC reception, check the value of the urecp-tp1rpc.dt-skip property in the TP1/RPC reception definition file and the format definition file, and confirm that the precautions for using the functionality to skip the structural transformation are observed. For a custom adapter, check the value of the custom-adapter.dt-skip property in the custom adapter definition file and format definition file, and confirm that the precautions for using the functionality to skip the structural transformation are observed.

#

A custom adapter is an adapter that is provided with the product and implemented by using the General custom adapter and the custom adapter development framework.

KDEC06009-E

An internal contradiction was detected while deleting information.

Description: An internal contradiction was detected while the information was being deleted.
(S): Cancels processing.
(O): When using a database, reference the message log file, and make sure that no error has occurred in the database. When you are not using a database, reference the message log file and the error information of the OS, and make sure that no error related to input and output of the file has occurred. If an error is occurring, take action against the error, and then restart the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC06010-E

The format definition file corresponding to the specified FormatID already exists. (FormatID = aa....aa, information = bb....bb)

aa....aa: Format ID

bb....bb: Details

Description

The format definition file corresponding to the specified format ID already exists.

(S)

Processing is interrupted if a format definition is being registered.

Processing continues if a business property is being deployed.

(O)

If the defined format ID does not begin with "REQ_", delete the target definition, add "REQ_" at the beginning of the format ID, and then re-execute the processing, or implement one of the following depending on the situation:

To register a format definition

Check and, if necessary, revise the specified ID or value in the detailed information, and then re-execute the processing.
To deploy a business process

Check the information for the deployed components with the csmlslocation command, and then un-deploy and re-deploy all the business processes with the duplicated format IDs.

KDEC06011-E

The format definition file of a different FormatType already exists for the specified FormatID. (FormatID = aa....aa, specified FormatType = bb....bb, existing FormatType = cc....cc)

aa....aa: Format ID

bb....bb: Specified format definition type

XML: XML format
BINARY: Binary format

cc....cc: Existing format definition type

XML: XML format
BINARY: Binary format

Description

The format definition file with a different format type already exists for the specified format ID.

(S)

Processing is interrupted if a format definition is being registered.

Processing continues if a business property is being deployed.

(O)

If the defined format ID does not begin with "REQ_", delete the target definition, add "REQ_" at the beginning of the format ID, and then re-execute the processing, or implement one of the following depending on the situation:

To register a format definition

Check and, if necessary, revise the specified ID or value in the detailed information, and then re-execute the processing.
To deploy a business process

Check the information for the deployed components with the csmlslocation command, and then un-deploy and re-deploy all the business processes with the duplicated format IDs.

KDEC06012-E

The format definition file corresponding to the specified FormatID does not exist. (FormatID = aa....aa, information = bb....bb)

aa....aa: Format ID

bb....bb: Detailed information

Description: The format definition file corresponding to the specified format ID does not exist.
(S): Cancels processing.
(O): Check, and if necessary, revise the specified ID or value in the detailed information, and then re-execute the processing.

KDEC06013-W

The format definition file corresponding to the specified FormatID is being used with other Business Process. (FormatID = aa....aa)

aa....aa: Format ID

Description: The format definition file corresponding to the specified format ID is being used in another business process.
(S): Cancels format definition deletion processing.
(O): Check, and if necessary, revise the specified ID and then re-execute the processing. If none of the business processes using the format definition is needed, delete all of these business processes.

KDEC06014-E

An attempt to access a data has failed. (definition type = aa....aa, access type = bb....bb)

aa....aa: Definition type

FORMAT: Format definition
TRANSFORM: Data transformation definition

bb....bb: Access type

INSERT: Add
DELETE: Delete

Description: An attempt to access data failed.
(S): Cancels processing.
(O): Check the message log file and take appropriate action according to the log message that was output before this message.

KDEC06501-W

The specified trace output path is invalid. (trace path = aa....aa, trace type = bb....bb)

aa....aa: Trace path

bb....bb: Trace type

method trace: Method trace
request trace: Request trace
telegram trace: User message trace

Description

The specified trace output destination is invalid.

(S)

When the trace output destination is specified: Outputs the trace to the default destination and resumes processing.
When the trace output destination is not specified: Creates the default directory and continues the processing.

(O)

When the trace output destination is specified: Specify the correct trace output destination in the HCSC server runtime definition file.
When the trace output destination is not specified: You are not required to take any action.

KDEC06502-W

The trace output path cannot be accessed. (trace path = aa....aa, trace type = bb....bb, cause = cc....cc)

aa....aa: Trace path

bb....bb: Trace type

method trace: Method trace
request trace: Request trace
telegram trace: User message trace

cc....cc: Details of the occurred exception

Description: The trace output destination cannot be accessed.
(S): Outputs the trace to the default destination and resumes processing.
(O): Check, and if necessary, revise the security attributes of the trace output destination.

KDEC06504-E

The message file was not found.

Description: The message file was not found.
(S): Cancels the start processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC06505-W

Initialization of the method trace failed. (cause = aa....aa, information = bb....bb)

aa....aa: Details of cause

bb....bb: Location of error

Description: An attempt to initialize the method trace failed.
(S): Resumes processing without outputting the method trace.
(O): If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC06506-W

Initialization of the request trace failed. (cause = aa....aa, information = bb....bb)

aa....aa: Details of cause

bb....bb: Location of error

Description: An attempt to initialize the request trace failed.
(S): Resumes processing without outputting the request trace.
(O): If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC06507-W

Closing the trace failed. (cause = aa....aa, information = bb....bb)

aa....aa: Details of cause

bb....bb: Location of error

Description: An attempt to end the trace failed.
(S): Resumes the termination processing.
(O): Check to see if the cause of the error is associated with operations. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC06509-W

The method trace is unavailable because the default method trace output path could not be obtained. (information = aa....aa)

aa....aa: Details of the occurred exception

Description: The method trace could not be output because the default method trace output destination could not be obtained.
(S): Resumes processing without outputting the method trace.
(O): Check, and if necessary, revise the security attributes of the Cosminexus log output destination, or specify another output destination.

KDEC06510-W

The request trace is unavailable because the default request trace output path could not be obtained. (information = aa....aa)

aa....aa: Details of the occurred exception

Description: The request trace cannot be output because the default request trace output destination could not be obtained.
(S): Resumes processing without outputting the request trace.
(O): Check, and if necessary, revise the security attributes of the J2EE Serber log output destination, or specify another output destination.

KDEC06511-W

Initialization of the telegram trace failed. (cause = aa....aa, information = bb....bb)

aa....aa: Details of cause

bb....bb: Location of error

Description

An attempt to initialize the user message trace failed.

(S)

Resumes processing without outputting the user message trace.

(O)

If the cause of the error is associated with operations, re-execute the processing.

If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC06512-W

The telegram trace is unavailable because the default telegram trace output path could not be obtained. (information = aa....aa)

aa....aa: Details of the occurred exception

Description: The user message trace cannot be output because the default user message trace output destination could not be obtained.
(S): Resumes processing without outputting the user message trace.
(O): Check and, if necessary, revise the security attributes of the Cosminexus log output destination, or specify another output destination.

KDEC06513-W

Initialization of the HCSC server exception log failed. (cause = aa....aa, information = bb....bb)

aa....aa: Detailed cause of the error

bb....bb: Location of the error

Description: An attempt to initialize the HCSC server exception log failed.
(S): Processing continues without the output of the HCSC server exception log.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06601-E

The message file was not found. (component name = aa....aa)

aa....aa: Component name

Description: The message file was not found.
(S): The start processing of the logger is interrupted.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06602-W

Initialization of the maintenance log failed. (component name = aa....aa, output file path = bb....bb, number of output files = cc....cc, size of output file = dd....dd, error message = ee....ee)

aa....aa: Component name

bb....bb: Output file path

cc....cc: Number of output files

dd....dd: Size of output files

ee....ee: Details

Description: An attempt to initialize the maintenance log failed.
(S): Processing continues by using the default maintenance log output destination.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06603-W

The default value for the maintenance log output path will be used. (component name = aa....aa, default value = bb....bb)

aa....aa: Component name

bb....bb: Default maintenance log output destination

Description: The default maintenance log output destination will be used.
(S): Processing continues by using the default maintenance log output destination.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06604-E

The maintenance log cannot be output because the default maintenance log output path cannot be used. (component name = aa....aa)

aa....aa: Component name

Description: The maintenance log cannot be output because the default maintenance log output destination cannot be used.
(S): An error is reported to the parent component.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06605-W

Initialization of the exception log failed. (component name = aa....aa, output file path = bb....bb, number of output files = cc....cc, size of output file = dd....dd, error message = ee....ee)

aa....aa: Component name

bb....bb: Output file path

cc....cc: Number of output files

dd....dd: Size of output files

ee....ee: Details

Description: An attempt to initialize the exception log failed.
(S): Processing continues by using the default exception log output destination.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06606-W

The default value for the exception log output path will be used. (component name = aa....aa, default value = bb....bb)

aa....aa: Component name

bb....bb: Default exception log output destination

Description: The default exception log output destination will be used.
(S): Processing continues by using the default exception log output destination.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06607-E

The exception log cannot be output because the default exception log output path cannot be used. (component name = aa....aa)

aa....aa: Component name

Description: The exception log cannot be output because the default exception log output destination cannot be used.
(S): An error is reported to the parent component.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06608-W

An attempt to stop the maintenance log failed. (component name = aa....aa, method name = bb....bb, error message = cc....cc)

aa....aa: Component name

bb....bb: Method name

cc....cc: Details

Description: An attempt to end the maintenance log failed.
(S): The end processing continues.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06609-W

An attempt to stop the exception log failed. (component name = aa....aa, method name = bb....bb, error message = cc....cc)

aa....aa: Component name

bb....bb: Method name

cc....cc: Details

Description: An attempt to end the exception log failed.
(S): The end processing continues.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06610-W

An error occurred during output of log data. (component name = aa....aa, log type = bb....bb, method name = cc....cc, error cause = dd....dd)

aa....aa: Component name

bb....bb: Log type (maintenance or exception)

cc....cc: Method name

dd....dd: Cause of the error

Description: An error occurred during the output of the log data.
(S): The applicable log is terminated.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06611-E

The logger startup failed. (component name = aa....aa)

aa....aa: Component name

Description: An attempt to start the logger failed.
(S): An error is reported to the parent component.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC06612-W

Initialization of the activity trace failed. (cause = aa....aa, information = bb....bb)

aa....aa: Details of cause

bb....bb: Location of error

Description: An attempt to initialize the activity trace failed.
(S): Continues processing without outputting activity trace information.
(O): If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log, and then contact maintenance personnel.

KDEC07001-E

An invalid command request was received. (information = aa....aa)

aa....aa: Debug information

Description: An invalid request was received.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC07002-E

A specified command parameter is invalid. (command = aa....aa, parameter = bb....bb)

aa....aa: Command type

Displays a string for identifying the request to the HCSC server.

bb....bb: Invalid parameter type

Description: The command parameter is invalid.
(S): Cancels processing.
(O): If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC07003-E

An unexpected exception occurred during command processing. (exception = aa....aa, message = bb....bb)

aa....aa: Exception type

bb....bb: Exception message

Description: An unexpected exception occurred during command processing.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC07004-I

The HCSC command was accepted. (command = aa....aa)

aa....aa: Command type

Displays a string for identifying the request to the HCSC server.

Description: The command was accepted.
(S): Continues processing.

KDEC07005-I

The HCSC command finished successfully. (command = aa....aa)

aa....aa: Command type

Displays a string for identifying the request to the HCSC server.

Description: The command processing is complete.
(S): Continues processing.

KDEC07006-E

The HCSC command failed. (command = aa....aa)

aa....aa: Command type

Displays a string for identifying the request to the HCSC server.

Description: The command processing failed.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC07007-E

An error occurred during the beginning of a transaction. (exception = aa....aa, error message = bb....bb)

aa....aa: Exception name

bb....bb: Message with exception details

Description

An error occurred during the beginning of a transaction.

(S)

Processing is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC07008-E

An error occurred while a transaction was being aa....aa. (exception = bb....bb, error message = cc....cc)

aa....aa: committed or rolled back

bb....bb: Exception name

cc....cc: Message with exception details

Description

An error occurred while a transaction was being committed or rolled back.

(S)

Processing is interrupted.

(O)

See the message log file, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC07501-E

Conversion to the specified character set failed. (user = aa....aa, client = bb....bb, character set = cc....cc, information = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Specified character set

dd....dd: Maintenance information

Description

An attempt at conversion to the specified character set failed.

(S)

The file cannot be transmitted and processing is interrupted.

(O)

Make sure that the following character sets match with the character set specified in the FTP command (OPTS UTF8 {ON|OFF}), or the character set specified in the FTP inbound adapter definition (server_charset_UTF8):

Character set for the transmission file name specified in the client
Character set for the file list responding with the LIST and NLST commands

KDEC07506-E

The specified user is not registered. (client = aa....aa, user = bb....bb)

aa....aa: IP address of the client

bb....bb: User name

Description: The user name specified in the authentication request from the client is not registered in the authentication information.
(S): Processing is interrupted.
(O): Specify a registered user name.

KDEC07507-E

The specified user is already authenticated. (client = aa....aa, user = bb....bb)

aa....aa: IP address of the client

bb....bb: User name

Description: The user name specified in the authentication request from the client is already authenticated.
(S): Processing is interrupted.
(O): The authentication is already complete, so continue the operations.

KDEC07508-E

A user is not specified. (client = aa....aa)

aa....aa: IP address of the client

Description: The user name is not specified in the authentication request from the client.
(S): Processing is interrupted.
(O): Specify the user name.

KDEC07509-E

A password is not specified. (client = aa....aa)

aa....aa: IP address of the client

Description: The password is not specified in the authentication request from the client (excluding the anonymous user).
(S): Processing is interrupted.
(O): Specify the password.

KDEC07510-E

Authentication failed. (client = aa....aa, user = bb....bb)

aa....aa: IP address of the client

bb....bb: User name

Description: The user name and the password specified in the authentication request from the client could not be authenticated.
(S): Processing is interrupted.
(O): Specify the correct user name and password.

KDEC07511-E

Authentication has not been performed. (client = aa....aa)

aa....aa: IP address of the client

Description: An attempt was made to transmit a file or list data without performing authentication.
(S): The transmission of the file or list data fails and processing is interrupted.
(O): Perform the appropriate authentication.

KDEC07512-E

The user is already registered. (user = aa....aa)

aa....aa: User name

Description: The user name is already registered.
(S): Processing is interrupted.
(O): Register a different user name.

KDEC07513-E

The user is not registered. (user = aa....aa)

aa....aa: User name

Description: The user name to be updated or deleted is not registered.
(S): The update or deletion operation fails and processing is interrupted.
(O): Specify the correct user name.

KDEC07514-E

The number of users exceeds the maximum. (maximum user = aa....aa)

aa....aa: Number of users that can be registered

Description: The number of users, which can be registered, exceeds the maximum.
(S): Processing is interrupted.
(O): Delete the unnecessarily registered users.

KDEC07515-E

One or more prohibited characters were specified.

Description: The Characters that cannot be used are specified in the user name or the password specified during the registration or update processing.
(S): Processing is interrupted.
(O): Specify the correct user name or password.

KDEC07516-E

The authentication information file does not exist. (file = aa....aa)

aa....aa: Authentication information file name

Description: The authentication information file does not exist.
(S): Processing is interrupted.
(O): Perform an overwrite installation for Service Coordinator. If this does not resolve the error, collect the log and trace information, and then contact maintenance personnel.

KDEC07517-E

Access to an authentication information file was denied. (file = aa....aa)

aa....aa: Authentication information file name

Description: The user does not have the permissions to access the authentication information file.
(S): Processing is interrupted.
(O): The user who has administrator privileges must execute the command.

KDEC07520-E

Another command is executing.

Description: An attempt was made to execute the csmftpaddusr, csmftpdelusr, or csmftplsusr commands while the csmftpaddusr or csmftpdelusr commands were being executed.
(S): Processing is interrupted.
(O): Wait for the execution of the other command to end and then re-execute the command.

KDEC07521-E

The number of logged-in users exceeds the maximum. (user = aa....aa, client = bb....bb, max-login users = cc....cc)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Maximum number of logged-in users

Description: The number of users who can log in to the FTP server exceeds the maximum number.
(S): The authentication fails and processing is interrupted.
(O): Log out the unnecessarily logged in users.

KDEC07522-I

The FTP server connected to an FTP client. (client = aa....aa)

aa....aa: IP address of the client

Description: The FTP server is connected to an FTP client.

KDEC07523-I

The FTP server disconnected from an FTP client. (client = aa....aa)

aa....aa: IP address of the client

Description: The FTP server disconnected from an FTP client.

KDEC07524-E

The FTP server disconnected from an idle FTP client. (client = aa....aa, idle-timeout = bb....bb)

aa....aa: IP address of the client

bb....bb: Timeout value

Description

The FTP server disconnected from an idle FTP client.

(S)

The FTP server is disconnected from the FTP client.

(O)

Take the following action:

If you are using FTPS, make sure that the FTPS mode settings for the server and client are the same. This error might occur if the server and client settings are different.
Log in to the FTP server again.

KDEC07525-E

The source file and the received file have different sizes. (user = aa....aa, client = bb....bb, file = cc....cc, FSIZE file size = dd....dd, received file size = ee....ee)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: File name

dd....dd: Size of the FSIZE command file

ee....ee: Size of the received file

Description

The size of the received file does not match the source file.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

KDEC07526-E

An error occurred during preparation to connect to the data connection. (user = aa....aa, client = bb....bb, server ip-address = cc....cc, server port = dd....dd, information = ee....ee)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: IP address of the server

dd....dd: Port number of the server

ee....ee: Maintenance information

Description

An error occurred during the preparation for establishing a data connection.

(S)

The file or list data transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server definition
FTP server status
Network status

KDEC07527-E

A timeout occurred during an attempt to connect to the data connection. (user = aa....aa, client = bb....bb, timeout = cc....cc)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Timeout value

Description

A timeout occurred during an attempt to establish a data connection.

(S)

If the number of data connection attempts has reached the retry count, the file or list data transmission processing ends. If the retry count is not reached, an attempt will be made again to establish a data connection.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

KDEC07528-I

Processing to connect to the data connection will be retried. (user = aa....aa, client = bb....bb, retry = cc....cc/dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Retry count

dd....dd: Maximum retry count

Description: An attempt will be made to re-establish a data connection.

KDEC07529-E

An attempt to connect to the data connection failed. (user = aa....aa, client = bb....bb, information = cc....cc)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Maintenance information

Description

An attempt to establish a data connection failed.

(S)

If the number of data connection attempts has reached the retry count, the file or list data transmission processing ends. If the retry count is not reached, an attempt will be made again to establish a data connection.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

KDEC07530-I

Connection to the data connection was successful. (user = aa....aa, client = bb....bb)

aa....aa: User name

bb....bb: IP address of the client

Description: The data connection was established successfully.

KDEC07531-E

An unsupported FTP command was received. (user = aa....aa, client = bb....bb, command = cc....cc)

aa....aa: User name

If the error occurs before the user logs in: <null>

bb....bb: IP address of the client

cc....cc: FTP command

Description: An unsupported FTP command was received.
(S): The file or list data transmission processing ends.
(O): Make sure that the FTP commands sent by the FTP client are supported by the FTP inbound adapter.

KDEC07532-E

The sequence of FTP commands is invalid. (user = aa....aa, client = bb....bb, command = cc....cc)

aa....aa: User name

If the error occurs before the user logs in: <null>

bb....bb: IP address of the client

cc....cc: FTP command

Description

The sequence of FTP commands is invalid.

(S)

The file or list data transmission processing ends.

(O)

Review and, if necessary, revise the status of the transmitting FTP client.

Also, see the protocol trace to identify the location of the error and then take action.

KDEC07533-E

A parameter or argument for an FTP command is invalid. (user = aa....aa, client = bb....bb, command = cc....cc, argument = dd....dd)

aa....aa: User name

If the error occurs before the user logs in: <null>

bb....bb: IP address of the client

cc....cc: FTP command

dd....dd: FTP command argument

Description

The contents of the FTP command argument are invalid.

(S)

The file or list data transmission processing ends, or the file or list data is transmitted with the settings disabled.

(O)

Review and, if necessary, revise the status of the transmitting FTP client.

Also, see the protocol trace to identify the location of the error and then take action.

KDEC07539-I

File transfer started. (user = aa....aa, client = bb....bb, mode = cc....cc, file = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Transmission type

APPE: APPE command
STOR: STOR command
RETR: RETR command

dd....dd: File name

Description: File transmission has started.

KDEC07540-I

File transfer finished. (user = aa....aa, client = bb....bb, mode = cc....cc, file = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Transmission type

APPE: APPE command
STOR: STOR command
RETR: RETR command

dd....dd: File name

Description: File transmission has finished.

KDEC07541-E

File transfer failed. (user = aa....aa, client = bb....bb, mode = cc....cc, file = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Transmission type

APPE: APPE command
STOR: STOR command
RETR: RETR command

dd....dd: File name

Description

File transmission failed.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

Also, take appropriate action according to the messages displayed before this message.

KDEC07542-E

An error response was returned to the client. (user = aa....aa, client = bb....bb)

aa....aa: User name

If the error occurs before the user logs in: <null>

bb....bb: IP address of the client

Description

An error response was returned to the client.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

Also, take appropriate action according to the messages displayed before this message.

KDEC07543-E

A network error occurred during the sending of a file. (user = aa....aa, client = bb....bb, file = cc....cc, information = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: File name

dd....dd: Maintenance information

Description

A network error occurred during the sending of a file.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

KDEC07544-E

A timeout occurred during the sending of a file. (user = aa....aa, client = bb....bb, file = cc....cc, timeout = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: File name

dd....dd: Timeout value

Description

A timeout occurred during the sending of a file.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status
Timeout value

KDEC07545-E

A network error occurred during reception of a file. (user = aa....aa, client = bb....bb, file = cc....cc, information = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: File name

dd....dd: Maintenance information

Description

A network error occurred during the reception of a file.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

KDEC07546-E

A timeout occurred during reception of a file. (user = aa....aa, client = bb....bb, file = cc....cc, timeout = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: File name

dd....dd: Timeout value

Description

A timeout occurred during the reception of a file.

(S)

The file transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status
Timeout value

KDEC07548-E

An attempt to invoke FTP reception failed. (resource adapter name = aa....aa, remote file path = bb....bb, reception ID = cc....cc, error code = dd....dd)

aa....aa: Resource adapter name

bb....bb: Remote file path

cc....cc: Reception ID of the FTP reception

If the reception ID cannot be obtained: <null>

dd....dd: Error code

01: The specified remote file path is invalid.
02: The FTP reception of the specified reception ID is not running.
03: The number of running FTP receptions has reached the upper limit, or the start processing of the FTP receptions is not complete.

Description

An attempt to invoke an FTP reception failed.

(S)

The file transmission processing is interrupted.

(O)

Take the following action for each error code:

01: Check the following information and eliminate the cause of the error:

Does the remote file path begin with a forward slash (/)?

Is the reception ID of the FTP reception enclosed within forward slashes?

Is a null string specified in the reception ID of the FTP reception?
02: Start the FTP reception.
03: Check the following information and eliminate the cause of the error:

Has the number of running FTP receptions reached the upper limit?

Is the start processing of the FTP receptions complete?

Is the HCSC server stopping?

KDEC07549-E

An error occurred during execution of FTP reception. (resource adapter name = aa....aa, reception ID = bb....bb)

aa....aa: Resource adapter name

bb....bb: Reception ID of the FTP reception

Description: An error occurred during the execution of an FTP reception.
(S): The file transmission processing is interrupted.
(O): Collect the log and trace information for the FTP inbound adapter and FTP reception, and then contact maintenance personnel.

KDEC07550-I

The following FTP receptions were activated at the FTP inbound adapter. (resource adapter name = aa....aa)

aa....aa: Resource adapter name

Description: The FTP receptions were linked to the FTP inbound adapter.

KDEC07551-E

Processing to start the FTP inbound adapter failed. (resource adapter name = aa....aa, error code = bb....bb)

aa....aa: Resource adapter name

bb....bb: Error code

01: The parsing of the definition file for log output failed.
02: An internal exception occurred.
03: An unspecifiable property value is set in the RAR properties file.
04: An error occurred during the input and output of the definition file.
05: An error occurred during the input and output of a file.
06: An attempt to create a definition file failed
07: The parsing of the definition file for transmission control failed.

Description

An attempt to start the FTP inbound adapter failed.

(S)

The processing to start the FTP inbound adapter fails and is interrupted.

(O)

Take the following action for each error code:

01: Perform an overwrite installation for Service Coordinator. If this does not resolve the error, collect the log and trace information, and then contact maintenance personnel.
02: Collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.
03: Review and, if necessary, revise the property values output in the messages KDEC07559-E, KDEC07593-E, or KDEC07596-E.
04: Check the following for the files and directories in <Service Platform installation directory>/CSC/inbound-adapter/ftp/config:

Are the access permissions specified correctly?

Is the disk space sufficient?
05: Check the following for the files and directories in <Service Platform installation directory>/CSC/inbound-adapter/ftp/config:

Are the access permissions specified correctly?

Is the disk space sufficient?
06: Collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.
07: If other messages are displayed before this message, take appropriate action according to those messages. If this does not resolve the error, collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.

KDEC07552-I

The FTP inbound adapter started. (resource adapter name = aa....aa)

aa....aa: Resource adapter name

Description: The start processing of the FTP inbound adapter is complete.

KDEC07553-E

Processing to stop the FTP inbound adapter failed. (resource adapter name = aa....aa)

aa....aa: Resource adapter name

Description: The stop processing of the FTP inbound adapter failed.
(O): Collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.

KDEC07554-I

The FTP inbound adapter was stopped. (resource adapter name = aa....aa)

aa....aa: Resource adapter name

Description: The stop processing of the FTP inbound adapter is complete.
(S): The stop processing is completed.

KDEC07555-E

Processing to activate FTP reception at the FTP inbound adapter failed. (resource adapter name = aa....aa, reception ID = bb....bb, error code = cc....cc)

aa....aa: Resource adapter name

bb....bb: Reception ID of the FTP reception

If the reception ID cannot be obtained: <null>

cc....cc: Error code

01: The reception ID of the FTP reception is not specified.
02: An FTP reception with the same reception ID is already associated or an FTP reception defining the GETINFO operation is already associated.

Description

An attempt to link an FTP reception and an FTP inbound adapter failed.

(S)

The start processing of the FTP reception fails and processing is interrupted.

(O)

Take the following action for each error code:

01: Review and, if necessary, revise the settings for the reception ID of the FTP reception.
02: Review and, if necessary, revise the FTP reception settings.

Check whether the specified ID is the same as that of the already associated FTP reception.

If this error occurs when you start an FTP reception defining the GETINFO operation, check whether the FTP reception with the GETINFO operation already defined, is being associated.

KDEC07556-I

Processing to activate FTP reception at the FTP inbound adapter finished successfully. (resource adapter name = aa....aa, reception ID = bb....bb)

aa....aa: Resource adapter name

bb....bb: Reception ID of the FTP reception

Description: An FTP reception was linked successfully with an FTP inbound adapter.

KDEC07557-E

Processing to deactivate FTP reception at the FTP inbound adapter failed. (resource adapter name = aa....aa, reception ID = bb....bb)

aa....aa: Resource adapter name

bb....bb: Reception ID of the FTP reception

Description: An attempt to cancel the link between an FTP reception and an FTP inbound adapter failed.
(O): Collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.

KDEC07558-I

Processing to deactivate FTP reception at the FTP inbound adapter finished successfully. (resource adapter name = aa....aa, reception ID = bb....bb)

aa....aa: Resource adapter name

bb....bb: Reception ID of the FTP reception

Description: The link between an FTP reception and an FTP inbound adapter was canceled successfully.
(S): The cancellation of the association is completed.

KDEC07559-E

A value specified in the RAR properties file is invalid. (resource adapter name = aa....aa, property name = bb....bb, value = cc....cc, range = dd....dd)

aa....aa: Resource adapter name

bb....bb: Property name

cc....cc: Specified value

dd....dd: Allowed range

[Minimum value - Maximum value]
[0.0.0.0-255.255.255.255|0:0:0:0:0:0:0:0-FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF]
[info|debug]
[length: Minimum value - Maximum value, Available character: "a-z","A-Z","_"]
[ON|OFF]
[true|false]

Description: A value specified in the RAR properties file is invalid.
(S): The processing to start the FTP inbound adapter fails and is interrupted.
(O): Specify the property value indicated by the property name specified in the RAR properties file within the range described in "range", and then start the FTP inbound adapter.

KDEC07560-E

An attempt to bind an IP address to a port failed. (ip-address = aa....aa, port = bb....bb)

aa....aa: IP address

bb....bb: Port number

Description

The IP address and the port number of the FTP server specified in the definition cannot be linked.

(S)

The invocation of the FTP inbound adapter fails, or the file transmission processing is interrupted.

(O)

Review and, if necessary, revise the following items:

FTP server definitions

Check whether the port number that is already being used is specified in the RAR properties file.

Check whether a non-existent IP address is specified in the RAR properties file.
FTP server status
Network status

KDEC07563-E

An internal error occurred. (information = aa....aa)

aa....aa: Maintenance information

Description: An internal error occurred.
(O): Collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.

KDEC07564-I

Usage: csmftplshistory servername [-csv csvfilename] [-date {printStartDate,[printEndDate]|[printStartDate],printEndDate}]

Description: This message describes the usage of the csmftplshistory command.

KDEC07565-E

The J2EE server was not found. (server name = aa....aa)

aa....aa: J2EE server name

Description: The specified J2EE server name was not found.
(S): Processing is interrupted.
(O): Specify the correct J2EE server name.

KDEC07567-E

A command option is invalid.

Description: A command option is invalid.
(S): Processing is interrupted.
(O): Specify the correct parameters.

KDEC07568-E

A CSV file cannot be output. (filename = aa....aa)

aa....aa: CSV file name

Description: The transmission log cannot be output to the CSV file specified in the option.
(S): Processing is interrupted.
(O): Make sure that the CSV file name specified in the option is correct.

KDEC07569-E

The transfer history file cannot be read. (filename = aa....aa)

aa....aa: Name of the transmission log file

Description: An attempt to read the transmission log file failed.
(S): Processing is interrupted.
(O): Make sure that the file displayed in the message can be read.

KDEC07570-I

Usage: csmftpaddusr -usr userName -pass password [-r]

Description: This message describes the usage of the csmftpaddusr command.

KDEC07571-I

Usage: csmftpdelusr -usr userName

Description: This message describes the usage of the csmftpdelusr command.

KDEC07572-I

Usage: csmftplsusr

Description: This message describes the usage of the csmftplsusr command.

KDEC07573-E

The length of the aa....aa parameter is 1-bb....bb characters.

aa....aa: Name of the command parameter

bb....bb: Maximum value of the parameter

Description: The length of the specified parameter is 0, or exceeds the maximum value.
(S): Processing is interrupted.
(O): Correct the length of the parameter to a specifiable range.

KDEC07574-E

The directory path specified in the environment variable is invalid. (environment variable = aa....aa, path = bb....bb, error code = cc....cc)

aa....aa: Environment variable

bb....bb: Directory path

cc....cc: Error code

01: Invalid characters are specified in the directory path, or the specified directory path is invalid.
02: The specified directory path exceeds the maximum length.
03: A file path is specified.

Description

The directory path specified in the environment variable is invalid.

(S)

Processing is interrupted.

(O)

Take the following action for each error code:

01: Make sure that valid characters are specified in the directory path, or that a valid directory path is specified.
02: Make sure that the directory path does not exceed the maximum length.
03: Make sure that a file path is not specified.

KDEC07575-E

Creation of the directory specified in the environment variable failed. (environment variable = aa....aa, path = bb....bb)

aa....aa: Environment variable

bb....bb: Path

Description

An attempt to create the directory specified in the environment variable failed.

(S)

Processing is interrupted.

(O)

Check the following:

Does the user have the permission to create the output destination directory?
Is the disk space sufficient?

KDEC07576-E

The -r option cannot be specified when specifying an anonymous user.

Description: the -r option cannot be specified for anonymous users.
(S): Processing is interrupted.
(O): Specify a user name other than that of an anonymous user.

KDEC07577-E

An attempt to write to the directory specified in the environment variable was denied. (environment variable = aa....aa, path = bb....bb)

aa....aa: Environment variable

bb....bb: Path

Description: The user does not have the write permissions for the directory specified in the environment variable.
(S): Processing is interrupted.
(O): Check whether the user can write to the output destination.

KDEC07578-E

Processing to start the command failed. (error code = aa....aa)

aa....aa: Error code

01: The log output definition file for the operation command does not exist.
02: An attempt to access the log output definition file for the operation command failed.
03: An attempt to parse the log output definition file for the operation command failed.

Description

An attempt to start the command failed.

(S)

Processing is interrupted.

(O)

Take the following action for each error code:

01: Perform an overwrite installation for Service Coordinator.
02: Make sure that the log output definition file for the operation command can be read.
03: Perform an overwrite installation for Service Coordinator.

KDEC07579-E

The user name is invalid. (user = aa....aa)

aa....aa: User name

Description: The user name specified in the USER command is not registered.
(S): Processing is interrupted.
(O): Specify the correct user name.

KDEC07580-E

The -pass option cannot be specified for anonymous users.

Description: the -pass option cannot be specified for anonymous users.
(S): Processing is interrupted.
(O): Specify a user name other than that of an anonymous user.

KDEC07581-E

The parameter is invalid. (parameter = aa....aa)

aa....aa: Command parameter

Description: The command parameter is invalid.
(S): Processing is interrupted.
(O): Specify the correct parameter.

KDEC07585-I

The command finished successfully. (resource adapter name = aa....aa)

aa....aa: Resource adapter name

Description: The command terminated normally.

KDEC07586-E

The command finished abnormally. (resource adapter name = aa....aa)

aa....aa: Resource adapter name

If an error occurs before processing is performed for the resource adapter: <null>

Description: The command terminated abnormally.
(S): Processing is interrupted.
(O): Take appropriate action according to the messages displayed before this message. If no message is displayed before this message, collect the log and trace information for the FTP inbound adapter, and then contact maintenance personnel.

KDEC07587-I

List-data transfer started. (user = aa....aa, client = bb....bb, mode = cc....cc, argument = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Type

NLST: NLST command
LIST: LIST command

dd....dd: Argument

Description: The transmission of list data has started.

KDEC07588-I

List-data transfer finished. (user = aa....aa, client = bb....bb, mode = cc....cc, argument = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Type

NLST: NLST command
LIST: LIST command

dd....dd: Argument

Description: The transmission of list data has finished.

KDEC07589-E

List-data transfer failed. (user = aa....aa, client = bb....bb, mode = cc....cc, argument = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Type

NLST: NLST command
LIST: LIST command

dd....dd: Argument

Description

The transmission of list data failed.

(S)

The list data transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

Also, take appropriate action according to the messages displayed before this message.

KDEC07590-E

A network error occurred during the sending of a list-data. (user = aa....aa, client = bb....bb, argument = cc....cc, information = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Argument

dd....dd: Maintenance information

Description

A network error occurred during the sending of the list data.

(S)

The list data transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status

KDEC07591-E

A timeout occurred during the sending of a list-data. (user = aa....aa, client = bb....bb, argument = cc....cc, timeout = dd....dd)

aa....aa: User name

bb....bb: IP address of the client

cc....cc: Argument

dd....dd: Timeout value

Description

A timeout occurred during the sending of the list data.

(S)

The list data transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTP server status
Network status
Timeout value

KDEC07592-E

Communication by a secure control connection failed. (user = aa....aa, client = bb....bb, server ip-address = cc....cc, server port = dd....dd, FTPS mode = ee....ee, information = ff....ff)

aa....aa: User name

If the error occurs before the user logs in: <null>

bb....bb: IP address of the client

cc....cc: IP address of the server

dd....dd: Port number of the server

ee....ee: FTPS mode

Implicit: Implicit FTPS
Explicit: Explicit FTPS
None: Normal FTP

ff....ff: Maintenance information

Description

The control connection communication in FTPS, which uses a secure protocol, failed.

(S)

The file or list data transmission processing ends.

(O)

Review and, if necessary, revise the following items:

FTPS-related property values from among the settings in the RAR properties file
Network status
FTP client settings

KDEC07593-E

A file path specified in the RAR properties file is invalid. (resource adapter name = aa....aa, property name = bb....bb, value = cc....cc)

aa....aa: Resource adapter name

bb....bb: Property name

cc....cc: Specified value

Description

The file path specified in the RAR properties file is invalid, or the file does not exist.

(S)

The processing to start the FTP inbound adapter fails and is interrupted.

(O)

Specify the full path for the property value indicated by the property name specified in the RAR properties file, and start the FTP inbound adapter.

You cannot specify the following file paths:

Path containing "//", "/./", and "/../"
Reserved device name of the OS

KDEC07594-E

An attempt to initialize FTPS settings failed. (resource adapter name = aa....aa, error code = bb....bb, information = cc....cc)

aa....aa: Resource adapter name

bb....bb: Error code

01: An attempt to read the specified file failed.
02: An attempt to obtain the key store failed.
03: The specified key cannot be processed.
04: The specified algorithm cannot be processed.
05: The specified type of key store cannot be processed.
99: An unexpected internal error occurred.

cc....cc: Maintenance information

Description

An attempt to initialize FTPS failed.

(S)

The processing to start the FTP inbound adapter fails and is interrupted.

(O)

Review and, if necessary, revise the FTPS settings in the RAR properties file based on the displayed error codes. If the problem is not resolved, contact maintenance personnel.

01: The specified key store cannot be read. Specify the correct file path. Also, make sure that the file for the specified key store exists and that the read attributes are set up correctly.
02: The possible causes are as follows:

The specified key store type is invalid.

Specify the JKS type key store.

The key store password is incorrect.

Specify the correct password.
03: The key password is incorrect. Specify the correct password.
04: The algorithm is invalid. Contact maintenance personnel.
05: The key store type is invalid. Contact maintenance personnel.
99: An unexpected internal error occurred. Review and, if necessary, revise the FTPS settings in the RAR properties file. If the problem is not resolved, contact maintenance personnel.

KDEC07595-E

The FTP command returned an error response because of the FTPS status. (user = aa....aa, client = bb....bb, FTPS mode = cc....cc, command = dd....dd, error code = ee....ee)

aa....aa: User name

If the error occurs before the user logs in: <null>

bb....bb: Client IP address

cc....cc: FTPS mode

Implicit: Implicit FTPS
Explicit: Explicit FTPS
None: Normal FTP

dd....dd: FTP command

ee....ee: Error code

01: The AUTH command was received with the settings for blocking FTPS.
02: The authentication is successful.
03: A secure protocol-based control connection is already established.
04: A secure protocol-based control connection is not established.

Description

The FTP command returned an error response because of the FTPS status.

(S)

One of the following is executed:

The file or list data transmission processing ends.
The file or list data transmission processing is performed with the settings disabled.

(O)

Take the following action for each error code:

01: The FTP inbound adapter was started with a normal FTP. Either allow the FTPS of the FTP inbound adapter, or use the normal FTP with the FTP client.
02: The FTP client must issue the AUTH command before issuing the USER and PASS commands.
03: The possible causes are as follows. Check the FTP client settings.

The AUTH command was issued in the Implicit mode

The AUTH command is already issued successfully in the Explicit mode
04: The possible causes are as follows:

The operations were performed with the normal FTP

Allow FTPS of the FTP inbound adapter and use FTPS with the FTP client.

An attempt to establish a secure connection failed

If other messages are displayed before this message, take action according to those messages.

If the problem is not resolved, review and, if necessary, revise the following items:

FTPS-related property values in the settings of the RAR properties file
Network status
FTP client settings

KDEC07596-E

The password specified in the RAR properties file is too short. (resource adapter name = aa....aa, property name = bb....bb)

aa....aa: Resource adapter name

bb....bb: Property name

Description: The length of the password specified in the RAR properties file is too short.
(S): The processing to start the FTP inbound adapter fails and is interrupted.
(O): The password must have atleast 6 characters. Specify the correct password.

KDEC10001-I

The HCSC command was accepted. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description: The command was accepted.
(S): Continues processing.

KDEC10002-I

The HCSC command finished successfully. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description: The command processing is complete.
(S): Continues processing.

KDEC10003-E

The HCSC command failed. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description: The command processing failed.
(S): Cancels processing.
(O): Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC10004-E

A specified command parameter is invalid. (command = aa....aa, parameter = bb....bb)

aa....aa: Command type

Displays command name or MBean name#Operation name of the HCSC server

bb....bb: Invalid parameter type

Description: The command parameter is invalid.
(S): Cancels processing.
(O): Check the specified parameter, and then re-execute the command.

KDEC10005-E

File access failed. (file name = aa....aa)

aa....aa: File name

Description: An attempt to access the file failed.
(S): Cancels processing.
(O): Check the file indicated as file-name.

KDEC10006-E

The command cannot execute because another HCSC command is executing. (command = aa....aa)

aa....aa: Command type of this command

Displays the HCSC server MBean name#Operation name.

Description: The command cannot be executed because another HCSC command is being executed. Alternatively, the processing cannot be executed as an attempt was made to simultaneously execute an operation or an HCSC command from the operating environment (window) for the same HCSC server.
(S): Cancels processing.
(O): Re-execute the command after the current command terminates. Wait until the other operations are finished, before re-executing the operation.

KDEC10007-E

The command cannot execute because the HCSC server is starting. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description: The command cannot be executed because the HCSC server is starting.
(S): Cancels processing.
(O): Terminate the HCSC server and then re-execute the command.

KDEC10008-E

The command cannot execute because the adapter and business process of the HCSC server has not been deleted. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description: The HCSC server setup cannot be removed because the service adapters and business processes have not been deleted.
(S): Cancels processing.
(O): Delete the adapter or business process, and then re-execute the command.

KDEC10009-W

Part of the processing failed but the command continued. For details, please check the message log. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description: Few processes failed, but the command continued to operate. For details, see the message log.
(S): Continues processing.
(O): Check the message log file, eliminate the cause of the error, and then re-execute the command.

KDEC10010-E

The connection to the J2EE server failed. (name = aa....aa)

aa....aa: J2EE server name

Description: The connection to the J2EE server failed.
(S): Cancels processing.
(O): Check the status of the J2EE server.

KDEC10011-E

A command issued to the J2EE server failed. (command = aa....aa, error message = bb....bb)

aa....aa: Command type

The following table shows correspondence between the displayed character string and the J2EE server command:

Displayed character string	Corresponding J2EE server command
`start`	`cjstartsv`
`stop`	`cjstopsv`
`deleteApp`	`cjdeleteapp`
`getAppProp`	`cjgetappprop`
`importApp`	`cjimportapp`
`listApp`	`cjlistapp`
`setAppProp`	`cjsetappprop`
`startApp`	`cjstartapp`
`stopApp`	`cjstopapp`
`getAttribute(State)`	`-` (collection of J2EE server status)

bb....bb: Error message

The following table lists the values (and corresponding statuses) that indicate the logical server status in error messages:

Value	Status
`0`	Stopped
`1`	Running
`2`	Abnormal termination
`3`	Stopping
`4`	Starting
`5`	Recovering
`6`	Communication error
`7`	Auto-stopping
`8`	Auto-restarting
`10`	Auto-stopping (recovering)
`11`	Auto-stopping (abnormal termination)
`12`	Auto-stopping (restarting)
`13`	Terminating forcibly
`14`	Terminating in a planned manner
`-1`	Unknown

Description: A command issued to the J2EE server failed.
(S): Cancels processing.
(O): Reference the J2EE server's message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC10012-E

A command issued to Cosminexus Reliable Messaging failed. (system name = aa....aa, command = bb....bb, name = cc....cc, error code = dd....dd, error message = ee....ee)

aa....aa: Reliable Messaging system name

bb....bb: Command type

Displays the Reliable Messaging command name.

cc....cc: Queue name or queue destination

dd....dd: Error code

ee....ee: Error message

Description

A command issued to Reliable Messaging failed.

(S)

Cancels processing.

(O)

Check the error code that was output, and eliminate the cause of the error.

The following table describes error codes that are output for each command:

Common for all commands

Error code	Cause	Action
HRM-00822	An internal error occurred.	Check the messages issued before and after this error, and eliminate the cause of the error. If the error cannot be corrected, collect the log and trace of Reliable Messaging, and then contact the maintenance personnel.
HRM-01201	The value of a method argument was null.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-01202	The value of a method argument was invalid.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-01203	An unsupported command was executed.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-01204	A method execution failed because CommandAdapter was in the close status.	Check the messages issued before and after this error, and eliminate the cause of the error. If the error cannot be corrected, collect the log and trace of Reliable Messaging, and then contact the maintenance personnel.
HRM-20010	The value specified in a command option was invalid.	Check the messages issued before and after this error, and eliminate the cause of the error. If the error cannot be corrected, collect the log and trace of Reliable Messaging, and then contact the maintenance personnel.
HRM-20011	The command format is invalid.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20012	The command failed.	Check the message log file, identify the message indicating the cause of the error, and then take appropriate action according to that message. After eliminating the cause of the error, re-execute the command.

hrmmkque command

Error code	Cause	Action
HRM-20000	The specified queue name exceeds 20 characters, which is the maximum.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20001	The specified queue name contains an invalid character.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20002	The specified queue name already exists.	Check to see if a queue having any of the following queue name used by HCSC already exists: CSC_cluster-name-service-ID CSCcluster-nameACPT_RCVQ CSCcluster-nameACPT_DBQ CSCcluster-nameTRNS_RCVQ CSC_cluster-name-linkage-target-cluster-name
HRM-20006	The system status is invalid.	Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command.
HRM-20036	A destination with the specified name does not exist.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20037	The queue-to-queue transfer function cannot be used because the function is now disabled.	Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command.
HRM-20060	Queue creation failed because the same queue name as RMDeadMessageQueueName was specified in the system status other than MANAGED_STATE.	Make sure that `RMDeadMessageQueueName` of Reliable Messaging does not match the following queue names used by HCSC: CSC_cluster-name-service-ID CSCcluster-nameACPT_RCVQ CSCcluster-nameACPT_DBQ CSCcluster-nameTRNS_RCVQ CSC_cluster-name-linkage-target-cluster-name
HRM-20061	Queue creation failed because an attempt was made to use the same name as a deleted queue with a different type.	First, restart Reliable Messaging, and then re-execute the command.
HRM-20062	Queue creation failed because an attempt was made to use the same name as a deleted queue with a different queue mode.	First, restart Reliable Messaging, and then re-execute the command.
HRM-20063	Creation of a shared receive queue failed because an attempt was made to use the same name as a deleted queue with a different maximum message length.	First, restart Reliable Messaging, and then re-execute the command.
HRM-20064	Queue creation failed because the version is not supported by the shared receive queue.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20065	Creation of a shared queue failed due to a database access error.	Either the database has been stopped or the corresponding share receive queue has been deleted. After eliminating the cause of the error, re-execute the command.
HRM-20100	The specified display name already exists.	Check and if necessary, revise the value of the display name of the specified queue, and then re-execute the command.

hrmdelque command

Error code	Cause	Action
HRM-20000	The specified queue name exceeds 20 characters, which is the maximum.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20001	The specified queue name contains an invalid character.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20003	A queue having the specified queue name does not exist.	This error code is output when deleting once again, and therefore, you are not required to take any action.
HRM-20006	The system status is invalid.	Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command.
HRM-20009	The specified queue cannot be deleted or its attributes cannot be changed because messages have been registered in that queue.	Wait until the messages have been sent and then delete the adapter, or forcibly delete the adapter.
HRM-20035	The current status does not allow changing of the queue configuration.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20037	The queue-to-queue transfer function cannot be used because the function is now disabled.	Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command.
HRM-20059	Queue deletion processing failed because the queue was monitored by a Message-driven Bean.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20066	Queue deletion processing failed because the queue was not suppressed or in shutdown status.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20067	Queue deletion processing failed because a transaction on that queue was under execution.	Re-execute the command after the transaction for the queue is committed.
HRM-20068	Queue deletion processing failed because the same queue name as RMDeadMessageQueueName was specified at a system status other than MANAGED_STATE immediately after the start of Reliable Messaging.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20072	Queue deletion failed due to shutdown status with an unknown queue type.	Collect the log and trace information, and then contact the maintenance personnel.

hrmmkaddr command

Error code

Cause

Action

HRM-20006

The system status is invalid.

Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command.

HRM-20037

The queue-to-queue transfer function cannot be used because the function is now disabled.

Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command.

HRM-20038

The specified destination name already exists.

Check whether the destination name shown as name already exists. Make sure that the destination name created by the user does not match the following destination name used by HCSC:

CSC service-ID

hrmdeladdr command

Error code	Cause	Action
HRM-20006	The system status is invalid.	Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command.
HRM-20036	A destination with the specified name does not exist.	This error code is output when deleting once again, and therefore, you are not required to take any action.
HRM-20037	The queue-to-queue transfer function cannot be used because the function is now disabled.	Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command.
HRM-20039	The specified destination cannot be deleted because it is referenced by a queue.	Re-execute the command. If re-execution of the command does not recover the error, collect the log and trace, and then contact the maintenance personnel.

hrmstartque command

Error code	Cause	Action
HRM-20000	The specified queue name exceeds 20 characters, which is the maximum.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20001	The specified queue name contains an invalid character.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20003	A queue having the specified queue name does not exist.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20006	The system status is invalid.	Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command.
HRM-20007	The command cannot be executed because the specified queue is in shutdown status.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20037	The queue-to-queue transfer function cannot be used because the function is now disabled.	Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command.

hrmstopque command

Error code	Cause	Action
HRM-20000	The specified queue name exceeds 20 characters, which is the maximum.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20001	The specified queue name contains an invalid character.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20003	A queue having the specified queue name does not exist.	There is no problem if this message was displayed during adapter deletion or cancellation of HCSC server setup. For any other case, collect the log and trace information, and then contact the maintenance personnel.
HRM-20006	The system status is invalid.	Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command.
HRM-20007	The command cannot be executed because the specified queue is in shutdown status.	Collect the log and trace information, and then contact the maintenance personnel.
HRM-20037	The queue-to-queue transfer function cannot be used because the function is now disabled.	Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command.
HRM-20041	The specified queue type is invalid.	Collect the log and trace information, and then contact the maintenance personnel.

KDEC10013-E

An attempt to connect to Cosminexus Reliable Messaging has failed. (system name = aa....aa, exception = bb....bb, message = cc....cc)

aa....aa: Reliable Messaging system name

bb....bb: Exception type

cc....cc: Error message

Description: An attempt to connect to Reliable Messaging failed.
(S): Cancels processing.
(O): Check the status of Reliable Messaging and the J2EE server. Alternatively, make sure that ejbserver.server.edition.settingforce= is specified in mserver.properties (Management Server environment configuration file). If this value is not specified, specify it and then restart Management Server.

KDEC10014-E

An unexpected exception occurred. (exception = aa....aa, message = bb....bb)

aa....aa: Exception type

bb....bb: Error message

Description: An unexpected exception occurred.
(S): Cancels processing.
(O): Check the exception type and error message, and eliminate the cause of the error. If the problem is not resolved, collect the log and trace information, and then contact Maintenance Service.

KDEC10015-E

An attempt to connect to a HCSC J2EE application has failed. (name = aa....aa, exception = bb....bb, message = cc....cc)

aa....aa: HCSC server name

bb....bb: Exception type

cc....cc: Error message

Description: A command request to an HCSC server failed.
(S): Cancels processing.
(O): Use the cmslsstate command to check the HCSC server status.

KDEC10016-E

The command cannot execute because the HCSC server is not running. (command = aa....aa)

aa....aa: Command type

Displays the HCSC server MBean name#Operation name.

Description

The HCSC server does not receive the operations from the command or the operating environment (window).

(S)

Cancels processing.

(O)

Start the HCSC server (if it is not already running), and then re-execute the command or operation.

If a timeout has occurred, eliminate the cause of the error, and then re-execute the command or operation.

KDEC10017-E

The queue cannot be deleted because a message remains in the queue. (name = aa....aa)

aa....aa: Queue name

Description: The queue cannot be deleted because a message remains in the queue.
(S): Cancels processing.
(O): Wait until the messages have been sent and then delete the adapter, or forcibly delete the adapter.

KDEC10020-E

A parameter of the setup file is invalid. (parameter = aa....aa)

aa....aa: Parameter identifier

Description: The contents of the HCSC server setup definition file are invalid.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC10021-E

The length of the parameter string is invalid. (parameter = aa....aa, length = bb....bb)

aa....aa: Parameter identifier

bb....bb: String length

Description: The length of the string specified in a parameter is invalid.
(S): Cancels processing.
(O): Specify the correct parameter, and then re-execute the command.

KDEC10022-E

The specified parameter is outside the valid range. (parameter = aa....aa)

aa....aa: Parameter identifier

Description: The value specified in a parameter is outside the valid range.
(S): Cancels processing.
(O): Specify the correct parameter, and then re-execute the command.

KDEC10023-E

The stipulated file in the adapter configuration was not found. (adapter name = aa....aa, file name = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: File name

Description: The specified file was not found in the service adapter or business process configuration.
(S): Cancels processing.
(O): Re-create the service adapter or business process.

KDEC10024-E

A parameter of the adapter definition file was not found. (adapter name = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: File name

cc....cc: Parameter identifier

Description: A parameter in the service adapter definition file for the service adapter or business process with the specified service ID was not found.
(S): Cancels processing.
(O): Re-create the service adapter or business process.

KDEC10025-E

The length of a parameter of the adapter definition file is invalid. (adapter name = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: File name

cc....cc: Parameter identifier

Description: The length of a parameter value in the service adapter definition file for the service adapter or business process with the specified service ID is invalid.
(S): Cancels processing.
(O): Re-create the service adapter or business process.

KDEC10026-E

A parameter value of the adapter definition file is invalid.(adapter name = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: File name

cc....cc: Parameter identifier

Description: A parameter value in the service adapter definition file for the service adapter or business process with the specified service ID is invalid.
(S): Cancels processing.
(O): Re-create the service adapter or business process.

KDEC10027-I

The HCSC command finished successfully. (command = aa....aa, delete num = bb....bb)

aa....aa: Command type

Displays command name or MBean name#Operation name of the HCSC server.

bb....bb: Deleted execution logs

Description: The command processing is complete.
(S): Continues processing.

KDEC10028-E

A setting in the Cosminexus usrconf.properties file is invalid. (parameter = aa....aa)

aa....aa: Property key

Description: The settings in usrconf.properties (user property file for J2EE servers) for the service platform are invalid.
(S): Cancels processing.
(O): Check the settings in usrconf.properties (user property file for J2EE servers) for the service platform. Check the property key value output to the message log, and then re-execute the processing.

KDEC10029-E

The specified adapter is already in place. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description: The specified service adapter or business process is already allocated.
(S): Cancels processing.
(O): Re-execute the processing after deleting the service adapter or business process.

KDEC10030-W

The specified adapter has already been deleted. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description: The specified service adapter or business process is already deleted.
(S): Resumes processing.

KDEC10031-E

The application attributes file is invalid. (application name = aa....aa, type = bb....bb, error message = cc....cc)

aa....aa: Application name

bb....bb: File type

1: File acquired using getAppProp
2: Definition file in adapter
3: System file for HCSC server
4: System file for request reception
5: Definition file in user-defined reception

cc....cc: Error message

Description: The property file is invalid.
(S): Cancels processing.
(O): For a custom adapter^#, check the adapter's cscadapter_property.xml. For any other adapter, collect the log and trace information, and then contact the maintenance personnel.
#: A custom adapter is an adapter that is provided with the product and implemented by using the database adapter, General custom adapter, or custom adapter development framework.

KDEC10033-E

The adapter cannot be deleted because it is starting. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description: An attempt to delete a service adapter or business process failed because the service adapter or business process is running.
(S): Cancels processing.
(O): Re-execute the processing after the service adapter or business process terminates.

KDEC10034-W

The queue has already been deleted. (queue name = aa....aa)

aa....aa: Queue name

Description: The transmission queue for the service adapter has already been deleted.
(S): Resumes processing.

KDEC10035-E

The combination of specified parameters is invalid. (command = aa....aa, parameter = bb....bb)

aa....aa: Command type

Displays MBean name#Operation name of the HCSC server.

bb....bb: Parameter identifier

Description: The combination of specified parameters is invalid.
(S): Cancels processing.
(O): Specify the correct parameter, and then re-execute the command.

KDEC10036-E

This HCSC command is not supported. (command = aa....aa)

aa....aa: Command type

Displays MBean name#Operation name of the HCSC server.

Description: The command is not supported.
(S): Cancels processing.

KDEC10037-E

The specified adapter was not found. (adapter name = aa....aa)

aa....aa: Service ID of the service adapter or the business process

Description: The specified service adapter or business process is not allocated.
(S): Cancels processing.
(O): Check if the service adapter or business process with the displayed service ID has been deployed.

KDEC10038-E

An attempt to import an adapter has failed. (adapter name = aa....aa, location = bb....bb, application = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Presence or absence of the location information

found: Location information is present
not found: Location information is absent

cc....cc: Presence or absence of application

found: Application is already deployed
not found: Application is not deployed

Description: An attempt to import a service adapter or business process failed.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC10039-E

Command execution failed because the adapter is waiting for input from another HCSC command. (adapter name = aa....aa, status = bb....bb)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Service adapter or business process status

starting: Starting
startfailed: An attempt to start has failed
stopping: Stopping
stopfailed: An attempt to stop has failed
deleting: Deleting

Description

The processing of operations from a command or an operating environment (window) failed because the service adapter or business process is waiting for input from another command.

(S)

Cancels processing.

(O)

Re-enter the command that is appropriate to the status of service adapter or business process.

starting/startfailed: Start or termination of service adapter or business process
stopping/stopfailed: Termination of service adapter or business process
deleting: Deletion of service adapter or business process

KDEC10040-E

The specified HCSC server was not found. (name = aa....aa)

aa....aa: Specified HCSC server name

Description: The specified HCSC server was not found.
(S): Cancels processing.
(O): Check to see if the HCSC server name specified in the command is correct. If it is correct, collect the log and trace information, and then contact the maintenance personnel.

KDEC10041-E

An attempt to create a database table has failed. (parameter = aa....aa, message = bb....bb)

aa....aa: SQL statement when an attempt to generate has failed

bb....bb: Exception message

Description: An attempt to create a database table failed.
(S): Cancels processing.
(O): Check the exception message and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the HCSC server setup. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC10042-W

An attempt to delete a database table has failed. (parameter = aa....aa, message = bb....bb)

aa....aa: SQL statement when an attempt to delete has failed

bb....bb: Exception message

Description: An attempt to delete a database table failed.
(S): The processing continues, but might be interrupted because of the cause of the error in the database.
(O): Check to see if the database table has been deleted. If necessary, re-execute the processing.

KDEC10043-W

An attempt to release the asynchronous request receptor queue has failed. (request receptor type = aa....aa)

aa....aa: Type of standard reception on which an attempt to release the queue control has failed

JMS: JMS standard reception
DBQ: DB queue standard reception
JMS/ DBQ: JMS standard reception and DB queue standard reception

Description: An attempt to release the control of the asynchronous standard reception queue failed.
(S): The standard receptions continue processing except the one on which the queue suppression release error occurred. The standard reception that failed no longer accepts queue requests, and the requests that have already been sent to the queue remain in the queue as is.
(O): Check the log messages that have been output before and after this message, eliminate the cause of the queue suppression release error, terminate the standard reception once, and then restart it. Alternatively, use the Reliable Messaging command to release the standard reception queue from the suppressed status.

KDEC10044-E

An attempt to access the database table has failed. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An attempt to access a database table has failed.
(S): Cancels processing.
(O): A database access error has occurred. Check the message log file and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC10045-E

The specified SQL script file is invalid. (information = aa....aa)

aa....aa: Detailed information

Description: The contents of the specified SQL script file are invalid.
(S): Cancels processing.
(O): Check the contents of the SQL script file specified in the HCSC server setup definition file. If the SQL script file is not specified, collect the log and trace information, and then contact Maintenance Service.

KDEC10046-E

An attempt to access the HCSC server runtime information file has failed.

Description: An attempt to access the HCSC server runtime definition file failed.
(S): Cancels processing.
(O): An error may have occurred at the HCSC server. Check the message log file. If an error has occurred, check the message, eliminate the cause of the error, and then set the HCSC server definition information again. If the error cannot be recovered after resetting the information, collect the log and trace information, and then contact the maintenance personnel.

KDEC10047-E

A server with the same name but different capitalization has already been set up. (name = aa....aa)

aa....aa: Name of the HCSC server that has been set up

Description: An HCSC server with the same name, but different capitalization has already been set up.
(S): Cancels processing.
(O): Check the name of the HCSC server that is being set up.

KDEC10048-W

The adapter status change was detected. (adapter name = aa....aa, location status = bb....bb, application status = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Service adapter or business process status of the location table

active: Started
inactive: Stopped
starting: Starting
startfailed: An attempt to start has failed
stopping: Stopping
stopfailed: An attempt to stop has failed
deleting: Deleting

cc....cc: Service adapter or business process applications status

For details, see the description related to checking the status of applications in Application Server Commands.

Description: A change was detected in the status of a service adapter or business process.
(S): Resumes processing.
(O): Check the status of the service adapter or business process.

KDEC10049-W

The request receptor status change was detected. (receptor status = aa....aa, application name = bb....bb, application status = cc....cc)

aa....aa: Request reception status

active: Started
inactive: Stopped
starting: Starting
startfailed: An attempt to start has failed
stopping: Stopping
stopfailed: An attempt to stop has failed

bb....bb: Name of the request reception application on which the status change was detected

cc....cc: Status of the request reception application on which the status change was detected

For details, see the description about checking the status of applications in Application Server Commands.

Description: A change was detected in the status of the request reception.
(S): Resumes processing.
(O): Check the status of the request reception.

KDEC10050-W

An attempt to access a database has failed. (information = aa....aa)

aa....aa: Details

Description: An attempt to access a database failed.
(S): Resumes processing.
(O): Check the database status.

KDEC10051-E

The command cannot execute because another HCSC command is executing.

Description: The command cannot be executed because another HCSC command is being executed. The processing cannot be executed as an attempt was made to simultaneously execute an operation or an HCSC command from the operating environment (window) for the same HCSC server.
(S): Cancels processing.
(O): Re-execute the command after the current command terminates. Wait until the other operations are finished, before re-executing the operation.

KDEC10052-E

The stipulated file in the reception configuration was not found. (Reception ID = aa....aa, file name = bb....bb)

aa....aa: Reception ID

bb....bb: File name

Description: The specified file was not found in the user-defined reception configuration.
(S): Cancels processing.
(O): Re-create the user-defined reception.

KDEC10053-E

A parameter of the reception definition file was not found. (Reception ID = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Reception ID

bb....bb: File name

cc....cc: Parameter identifier

Description: A parameter was not found in the reception definition file for user-defined receptions.
(S): Cancels processing.
(O): Check and, if necessary, revise the value of the parameter specified while the user-defined reception is created, and then re-create the user-defined reception.

KDEC10054-E

The length of a parameter of the reception definition file is invalid. (Reception ID = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Reception ID

bb....bb: File name

cc....cc: Parameter identifier

Description: The length of a parameter value in the reception definition file for user-defined receptions is invalid.
(S): Cancels processing.
(O): Check and, if necessary, revise the value of the parameter specified while the user-defined reception is created, and then re-create the user-defined reception.

KDEC10055-E

A parameter value of the reception definition file is invalid. (Reception ID = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Reception ID

bb....bb: File name

cc....cc: Parameter identifier

Description

The value of a parameter in the reception definition file for user-defined receptions is invalid.

(S)

Cancels processing.

(O)

Check and, if necessary, revise the parameter values in the reception definition file in which the error occurred. Then, take one of the following actions depending on the scope of the definition file:

Change the definition, and then restart the user-defined reception.
Change the definition, and then re-deploy the user-defined reception.
Re-create the user-defined reception in the development environment.

KDEC10056-W

The user defined reception started, but the called service did not start. (Reception ID = aa....aa, service name = bb....bb)

aa....aa: Reception ID

bb....bb: Service name invoked from the user-defined reception

Description: The user-defined reception started successfully, but the service component invoked from the user-defined reception did not start.
(S): Resumes processing.
(O): Check the status of the called service (service adapter, business process, or service group) connected to the user-defined reception, and then start the service.

KDEC10057-E

The specified reception is already in place. (Reception ID = aa....aa)

aa....aa: Reception ID

Description: The specified user-defined reception has already been allocated.
(S): Cancels processing.
(O): Delete the user-defined reception, and then re-execute the command.

KDEC10058-W

The specified reception has already been deleted. (Reception ID = aa....aa)

aa....aa: Reception ID

Description: The specified user-defined reception has already been deleted.
(S): Resumes processing.

KDEC10059-E

The same value is specified in the parameter. (command = aa....aa, parameter = bb....bb)

aa....aa: Command type

Displays command name or MBean name#Operation name the HCSC server.

bb....bb: Invalid parameter

.serial-number of the parameter is not output.

Description: The same value is specified in the parameter.
(S): Cancels processing.
(O): Check the parameter value, and then re-execute the command.

KDEC10060-E

An attempt to import a reception has failed. (Reception ID = aa....aa, location = bb....bb, application = cc....cc)

aa....aa: Reception ID

bb....bb: Presence or absence of location information

found: Location information is present
not found: Location information is absent

cc....cc: Presence or absence of application

found: Application is already deployed
not found: Application is not deployed

Description: An attempt to import the user-defined reception failed.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC10061-E

The reception cannot be deleted because it is starting. (Reception ID = aa....aa)

aa....aa: Reception ID

Description: An attempt to delete the user-defined reception failed because the user-defined reception is running.
(S): Cancels processing.
(O): Terminate the user-defined reception, and then re-execute the processing.

KDEC10062-E

Command execution failed because the reception is waiting for input from another HCSC command. (Reception ID = aa....aa, status = bb....bb)

aa....aa: Reception ID

bb....bb: User-defined reception status

starting: Starting
startfailed: An attempt to start has failed
stopping: Stopping
stopfailed: An attempt to stop has failed
deleting: Deleting

Description

The processing of the command failed because the user-defined reception is waiting for input from another command.

(S)

Cancels processing.

(O)

Re-enter the command corresponding to the status of the user-defined reception.

starting/startfailed: Start or terminate the user-defined reception
stopping/stopfailed: Terminate the user-defined reception
deleting: Delete the user-defined reception

KDEC10063-E

The specified reception was not found. (Reception ID = aa....aa)

aa....aa: Reception ID

Description: The specified user-defined reception was not allocated.
(S): Cancels processing.
(O): Make sure that the user-defined reception with reception-ID is deployed.

KDEC10064-W

The reception status change was detected. (Reception ID = aa....aa, location status = bb....bb, application status = cc....cc)

aa....aa: Reception ID

bb....bb: User-defined reception status of the location table

active: Started
inactive: Stopped
starting: Starting
startfailed: An attempt to start has failed
stopping: Stopping
stopfailed: An attempt to stop has failed
deleting: Deleting

cc....cc: J2EE application status

For details, see the manual Application Server Commands.

Description: A change was detected in the user-defined reception status.
(S): Resumes processing.
(O): Check the status of the user-defined reception.

KDEC10065-E

The command cannot execute because the reception of the HCSC server has not been deleted. (command = aa....aa)

aa....aa: Command type

Displays MBean name#Operation name of the HCSC server.

Description: The removal of the HCSC server setup failed because a user-defined reception has not been deleted.
(S): Cancels processing.
(O): Delete the user-defined reception, and then re-execute the command.

KDEC10066-W

An exception occurred during checking of the component status. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An error occurred during the checking of the component status.
(S): Resumes processing.
(O): Check the status of the service adapter or business process, request reception, and user-defined reception.

KDEC10067-W

An exception occurred during update of the adapter status. (adapter name = aa....aa, error code = bb....bb, error message = cc....cc)

aa....aa: Service ID of the service adapter or the business process

bb....bb: Error code

cc....cc: Error message

Description: An error occurred while the service adapter or business process status was being updated.
(S): Resumes processing.
(O): Check the status of the service adapter or business process.

KDEC10068-W

An exception occurred during update of the request receptor status. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An error occurred while the request reception status was being updated.
(S): Resumes processing.
(O): Check the status of the request reception.

KDEC10069-W

An exception occurred during update of the reception status. (Reception ID = aa....aa, error code = bb....bb, error message = cc....cc)

aa....aa: Reception ID

bb....bb: Error code

cc....cc: Error message

Description: An error occurred while the user-defined reception status was being updated.
(S): Resumes processing.
(O): Check the status of the user-defined reception.

KDEC10070-E

A communication error with the administration agent occurred. (command = aa....aa, error message = bb....bb)

aa....aa: Command type

The following table shows correspondence between the displayed character string and the J2EE server command:

Displayed character string	Corresponding J2EE server command
`start`	`cjstartsv`
`stop`	`cjstopsv`
`deleteApp`	`cjdeleteapp`
`getAppProp`	`cjgetappprop`
`importApp`	`cjimportapp`
`listApp`	`cjlistapp`
`setAppProp`	`cjsetappprop`
`startApp`	`cjstartapp`
`stopApp`	`cjstopapp`
`getAttribute(State)`	`-` (Collection of J2EE server status)

bb....bb: Error message

The following table lists the values (and corresponding statuses) that indicate the logical server status in error messages:

Value	Status
`0`	Stopped
`1`	Running
`2`	Abnormal termination
`3`	Stopping
`4`	Starting
`5`	Recovering
`6`	Communication error
`7`	Auto-stopping
`8`	Auto-restarting
`10`	Auto-stopping (recovering)
`11`	Auto-stopping (abnormal termination)
`12`	Auto-stopping (restarting)
`13`	Terminating forcibly
`14`	Terminating in a planned manner
`-1`	Unknown

Description: An error occurred during the communication with Administration Agent.
(S): Cancels processing.
(O): Make sure that the Administration Agent is active. If inactive, restart the Management Server and Administration Agent. If the failure cannot be recovered even after restart, contact maintenance personnel.

KDEC10071-E

A data access error occurred. (error code = aa....aa, error message = bb....bb)

aa....aa: Error code

bb....bb: Error message

Description: An error occurred during a data access.
(S): Cancels processing.
(O): Check the error message and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC10072-E

This command cannot be used. (command = aa....aa, reason = bb....bb)

aa....aa: Command type

Displays MBean name#Operation name of the HCSC server.

bb....bb: Reason

database is not used: Configuration in which the database is not used

Description: This command cannot be used because the HCSC server is set up with the configuration displayed in reason.
(S): Cancels processing.
(O): The input command cannot be used because the HCSC server is set up with the configuration displayed in reason.

KDEC10073-E

The combination of specified parameters is invalid. (parameter1 = aa....aa, value1 = bb....bb, parameter2 = cc....cc, value2 = dd....dd)

aa....aa: Property 1

bb....bb: Value of property 1

cc....cc: Property 2

dd....dd: Value of property 2

Description: The combination of properties and values specified in the HCSC server setup definition file or HCSC server runtime definition file is invalid.
(S): Cancels processing.
(O): Check, and if necessary, revise the contents specified in the HCSC server setup definition file or the HCSC server runtime definition file, and make sure that the properties and values are not defined in the combination that results in an error when specified. After this, reset the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC10074-E

A required parameter has not been specified. (parameter = aa....aa)

aa....aa: Property

Description: A required property is not specified in the HCSC server setup definition file.
(S): Cancels processing.
(O): Check, and if necessary, revise the contents specified in the HCSC server setup definition file, and make sure that all the properties that you must specify, are defined. Once the problem is resolved, reset the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC10075-E

A parameter value is not specified. (parameter = aa....aa)

aa....aa: Property

Description: A property value is not specified in the HCSC server setup definition file.
(S): Cancels processing.
(O): Check, and if necessary, revise the contents specified in the HCSC server setup definition file, and make sure that the value is specified in the properties. Once the problem is resolved, reset the HCSC server. If the error cannot be corrected, collect the log and trace information, and then contact the maintenance personnel.

KDEC10076-E

An attempt to start debugging the business process failed because the debugging process was started in an unexpected environment. (command = aa....aa)

aa....aa: Command type

Displays MBean name#Operation name of the HCSC server.

Description: An attempt to start the debugging of the business process failed because the debug process was started in an unexpected environment.
(S): The processing will be interrupted.
(O): Start debugging the business process in the prerequisite environment.

KDEC10077-E

The Cosminexus SOAP settings are invalid. (J2EEServer name = aa....aa)

aa....aa: J2EE server name

Description: The SOAP Communication Infrastructure or JAX-WS engine settings are invalid.
(S): The processing will be interrupted.
(O): Use usrconf.cfg to set up the SOAP Communication Infrastructure or the JAX-WS engine that is to be used.

KDEC10078-E

The current SOAP mode is different from the expected value. (J2EEServer name = aa....aa, expected value = bb....bb)

aa....aa: J2EE server name

bb....bb: Expected SOAP mode (SOAP1.1 mode or SOAP1.1/ 1.2 combined mode)

Description: The SOAP mode that has been set up differs from the SOAP mode expected on the service platform.
(S): The processing will be interrupted.
(O): Correct the SOAP Communication Infrastructure or the JAX-WS engine settings in the cluster according to the argument information.

KDEC10079-E

A RemoteException occurred. (exception = aa....aa, message = bb....bb)

aa....aa: Exception type

bb....bb: Error message

Description: The RemoteException exception occurred.
(S): The processing will be interrupted.
(O): Reference the error message, and then remove the cause of the error. If the cause of the error is an operational problem, re-execute the operation. If the cause of the error is not an operational problem, collect the log and trace, and then contact maintenance personnel.

KDEC10080-E

A socket connection timeout occurred. Make sure there are no problems in the debug settings or the network. (host name = aa....aa, port = bb....bb, timeout = cc....cc)

aa....aa: Host name

bb....bb: Port number

cc....cc: Connection timeout value

Description: A socket connection timed out when the debugging of the business process was running.
(S): The processing will be interrupted.
(O): Make sure that there are no problems in the debug settings or the network.

KDEC10081-E

A socket connection error occurred. Make sure there are no problems in the debug settings or the network. (host name = aa....aa, port = bb....bb, message = cc....cc)

aa....aa: Host name

bb....bb: Port number

cc....cc: Exception message

Description: An error occurred in the socket connection when starting the debugging of the business process.
(S): The processing will be interrupted.
(O): Make sure that there are no problems in the debug settings or the network.

KDEC10082-E

The specified file name does not exist in a common folder. (file name = aa....aa)

aa....aa: File name

Description: The specified file does not exist in the common folder.
(S): Processing is interrupted.
(O): Check the file name with the cscfscls command, and then re-execute the command.

KDEC10083-E

The work folder that HCSC server name shows does not exist. (HCSC server name = aa....aa)

aa....aa: HCSC server name

Description: The directory with the HCSC server name does not exist in the work folder root.
(S): Processing is interrupted.
(O): Specify the correct HCSC server name.

KDEC10084-E

The work folder that reception ID shows does not exist. (reception ID = aa....aa)

aa....aa: Reception ID

Description: The work folder indicated by the reception ID does not exist.
(S): Processing is interrupted.
(O): Specify the correct reception ID.

KDEC10085-E

An attempt to delete a file or directory has failed. (file path = aa....aa, message = bb....bb)

aa....aa: Absolute path of the file or directory

bb....bb: Exception message

Description: An attempt to delete a file or a directory failed.
(S): Processing is interrupted.
(O): After the other command or operation finishes, re-execute the command or operation.

KDEC10086-E

A common folder definition name has not been defined. (folder name = aa....aa)

aa....aa: Common folder definition name

Description: A common folder definition name has not been defined.
(S): Processing is interrupted.
(O): Review and, if necessary, revise the common folder definition name defined in the HCSC server runtime definition file.

KDEC10087-E

The specified directory does not exist. (directory path = aa....aa)

aa....aa: Absolute path of the directory

Description: The specified directory does not exist.
(S): Processing is interrupted.
(O): Review and, if necessary, revise the work folder root or the common folder definition name defined in the HCSC server runtime definition file.

KDEC10088-E

An attempt to acquire a lock has failed.

Description: An attempt to acquire a lock failed.
(S): Processing is interrupted.
(O): Stop the components that are using the same common folder, and then re-execute the command.

KDEC10089-E

An attempt to perform a file or directory operation has failed. (file path = aa....aa)

aa....aa: Absolute path of the file or directory

Description: An attempt to perform a file or directory operation failed.
(S): Processing is interrupted.
(O): Review and, if necessary, revise the access permissions for the common folder or work folder.

KDEC10090-W

An attempt to release a lock has failed. (command = aa....aa, file path = bb....bb)

aa....aa: Command type

MBean name#Operation name of the HCSC server is displayed.

bb....bb: Absolute path of the file

Description: An attempt to release a lock failed.
(S): Processing continues.
(O): If there are files for which the lock release process failed, re-execute the deletion process.

KDEC10091-W

An attempt to acquire information about file or directory has failed. (file path = aa....aa)

aa....aa: Absolute path of the file or directory

Description: An attempt to obtain the file or directory information failed. There is a possibility that the file or the directory might have been deleted by another process.
(S): Processing continues.

KDEC10092-E

A required parameter has not been specified. (reception ID = aa....aa, file name = bb....bb, parameter = cc....cc)

aa....aa: Reception ID

bb....bb: File name

cc....cc: Parameter identifier

Description

A required parameter is not specified in the reception definition file for user-defined receptions.

(S)

Processing is interrupted.

(O)

Review and, if necessary, revise the parameters in the definition file in which the error occurred. Take one of the following actions depending on the scope of the definition file:

Add the required definition and then restart the user-defined reception.
Add the required definition and then re-deploy the user-defined reception.
Re-create the definition file in the development environment.

KDEC10093-E

An error occurred because it differed from the value to which the set value had already been set. (key = aa....aa, specified value = bb....bb, already set value = cc....cc)

aa....aa: Key with an error

bb....bb: Specified value

cc....cc: Value that is already set

Description

An error occurred because the specified value differs from the value that is already set.

(S)

Processing is interrupted.

(O)

Check and then reset up the HCSC server configuration definition file or HCSC server setup definition file.

The mapping between the keys and the error items is as follows:

cluster-type: Cluster type

j2eeservername: J2EE server name

rm-use: : Use of Reliable Messaging

rm-systemname: RM system name

db-tbl-split-key: Table range splitting key

db-tbl-split-corcheck-use: Enhancement of the duplicaton check for a correlation set

KDEC10094-E

An error occurred because the specified value is already set. (key = aa....aa, specified value = bb....bb)

aa....aa: Key with an error

bb....bb: Specified value

Description

An error occurred because the specified value has already been set.

(S)

Processing is interrupted.

(O)

Check and then reset up the HCSC server configuration definition file, HCSC server setup definition file, or command arguments.

The mapping between the keys and the error items is as follows:

cscservername: HCSC server name

rm-systemname: RM system name

KDEC10095-E

The new reception information differs from the already set up HCSC Server reception information. (cluster name = aa....aa, current set up = bb....bb, new set up information = cc....cc)

aa....aa: Cluster name

bb....bb: Reception information that is already set up

cc....cc: Reception information specified during setup

Description: The HCSC server reception information that you want to set up does not match the already set up information.
(S): Processing is interrupted.
(O): Implement the HCSC server setup in such a way that reception information matches the already set up information.

KDEC10096-E

Please perform unsetup of the HCSC Server that has fewer reception types. (cluster name = aa....aa, minimum set up = bb....bb)

aa....aa: Cluster name

bb....bb: Minimum reception setup information

Description: First remove the setup of the HCSC servers that have fewer reception types.
(S): Processing is interrupted.
(O): When you cancel the HCSC server setup, first perform unsetup of the HCSC servers with fewer reception types.

KDEC10097-E

Make sure that the reception information for all HCSC Servers that have already been set up matches. (cluster name = aa....aa)

aa....aa: Cluster name

Description: Make sure that the reception types of the HCSC servers that are already set up match.
(S): Processing is interrupted.
(O): Match the reception types of the HCSC servers that have already been set up, and then re-execute the setup.

KDEC10098-E

The maximum number of HCSC Servers connected to each cluster has been exceeded. (cluster type = aa....aa, cluster name = bb....bb)

aa....aa: Cluster type

HA: HA cluster
LB: Load-balancing cluster

bb....bb: Cluster name

Description: The maximum number of HCSC servers that can be set for each cluster has been exceeded.
(S): Processing is interrupted.
(O): You can only set up two HCSC servers for HA, and 1,024 HCSC servers for LB. Rename the cluster and then re-execute the setup.

KDEC10099-W

No HTTP reception definition file has been specified. Default values will be used for HTTP reception properties. (reception name = aa....aa, reception ID = bb....bb)

aa....aa: Reception name

bb....bb: Reception ID

Description: The HTTP reception definition file is not specified. The default values will be used for the HTTP reception properties.
(S): Processing continues.
(O): As and when required, set up the HTTP reception definition file for the HTTP receptions.

KDEC10100-E

An error occurred while caching both the format definitions and data transform definitions. (adapter name = aa....aa, exception = bb....bb, error message = cc....cc)

aa....aa: Service ID of the serivce adapter or business process

bb....bb: Exception name

cc....cc: Message with exception details

Description: An error occurred while the format definitions and data transformation definitions were being cached in the service adapter or business process.
(S): Processing is interrupted.
(O): See the message log file, and then eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.

KDEC10101-E

The adapter status is invalid. (adapter name = aa....aa, expected status = bb....bb, status = cc....cc)

aa....aa: Service ID of the serivce adapter or business process

bb....bb: Expected status

cc....cc: Status

Description: The status of the service adapter or business process is invalid.
(S): Processing is interrupted.
(O): Correct the status of the components based on the information about the arguments, and then re-execute the processing.

KDEC10102-E

A table column does not match a parameter in the setup file. (parameter = aa....aa, table name = bb....bb, column name = cc....cc)

aa....aa: Parameter

bb....bb: Table name

cc....cc: Column name

Description: A table column does not match the value specified in a parameter of the HCSC server setup definition file.
(S): Processing is interrupted.
(O): Check the values coded in the HCSC server setup definition file and the columns of the table to be created, and then re-execute the setup.

KDEC10400-E

The command syntax is invalid.

Description: The usage of The command is incorrect.
(S): The command terminates abnormally.
(O): Check and, if necessary, revise the command parameters, and then re-execute the command.

KDEC10401-I

Usage: csmlsstate [<HCSCServerName>] [-d {prop|runtime}]

Description: This message describes the usage of the csmlsstate command.
(S): Returns the command's response.
(O): Check the command arguments and values, and then re-execute the command.

KDEC10403-I

Usage: csmlslocation [<HCSCServerName>] {-a <AdapterName> | -t <ServiceName> | -k {adp|bp|sg} | -all} [{-l | -r}] [-u <DBUserID> [-p <DBPassword>]]

Description: This message describes the usage of the csmlslocation command.
(S): Returns the command's response.
(O): Check the command arguments and values, and then re-execute the command.

KDEC10407-I

Usage:

Format1: csmlshistory [<HCSCServerName>] -c <ClientID> [-m <HCSCCommonID>] [-i <ServiceRequestID>] [-t <StartTime>,<EndTime>] [-rs <RequestServiceName>] [-s <ServiceName>] [-jm <JMSMessageID>] [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format2: csmlshistory [<HCSCServerName>] [-c <ClientID>] -m <HCSCCommonID> [-i <ServiceRequestID>] [-t <StartTime>,<EndTime>] [-rs <RequestServiceName>] [-s <ServiceName>] [-jm <JMSMessageID>] [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format3: csmlshistory [<HCSCServerName>] [-c <ClientID>] [-m <HCSCCommonID>] -i <ServiceRequestID> [-t <StartTime>,<EndTime>] [-rs <RequestServiceName>] [-s <ServiceName>] [-jm <JMSMessageID>] [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format4: csmlshistory [<HCSCServerName>] [-c <ClientID>] [-m <HCSCCommonID>] [-i <ServiceRequestID>] -t <StartTime>,<EndTime> [-rs <RequestServiceName>] [-s <ServiceName>] [-jm <JMSMessageID>] [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format5: csmlshistory [<HCSCServerName>] [-c <ClientID>] [-m <HCSCCommonID>] [-i <ServiceRequestID>] [-t <StartTime>,<EndTime>] -rs <RequestServiceName> [-s <ServiceName>] [-jm <JMSMessageID>] [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format6: csmlshistory [<HCSCServerName>] [-c <ClientID>] [-m <HCSCCommonID>] [-i <ServiceRequestID>] [-t <StartTime>,<EndTime>] [-rs <RequestServiceName>] -s <ServiceName> [-jm <JMSMessageID>] [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format7: csmlshistory [<HCSCServerName>] [-c <ClientID>] [-m <HCSCCommonID>] [-i <ServiceRequestID>] [-t <StartTime>,<EndTime>] [-rs <RequestServiceName>] [-s <ServiceName>] -jm <JMSMessageID> [-jc <JMSCorrelationID>] [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Format8: csmlshistory [<HCSCServerName>] [-c <ClientID>] [-m <HCSCCommonID>] [-i <ServiceRequestID>] [-t <StartTime>,<EndTime>] [-rs <RequestServiceName>] [-s <ServiceName>] [-jm <JMSMessageID>] -jc <JMSCorrelationID> [-l {new|all}] [-d {nml|ext|msg}] [-ul <UserTelegramLength>] [-r <RecordCount>] [-k {list|count}] [-u <DBUserID> [-p <DBPassword>]]

Description: This message describes the usage of the csmlshistory command.
(S): Terminates the command with an error.
(O): Check the command arguments and values, and then re-execute the command.

KDEC10408-I

Usage: csmdeletehistory [<HCSCServerName>] {-t <Time> | -d <Days>} [{-m <HCSCCommonID> | -c <ClientID> | -a <AdapterName>}] [-u <DBUserID> [-p <DBPassword>]]

Description: This message describes the usage of the csmdeletehistory command.
(S): Terminates the command with an error.
(O): Check the command arguments and values, and then re-execute the command.

KDEC10409-I

The HCSC command finished successfully.

Description: The command processing is complete.
(S): Continues processing.

KDEC10410-E

The HCSC command failed. (message = aa....aa)

aa....aa: Error message

Description: The command processing failed.
(S): Cancels processing.
(O): Check the error message and eliminate the cause of the error. If the cause of the error is associated with operations, re-execute the processing. If it is not associated with operations, collect the log and trace information, and then contact the maintenance personnel.

KDEC10411-I

Usage: csmlsreception [<HCSCServerName>] {-i <ReceptionID> | -s <ServiceName> | -all} [-u <DBUserID> [-p <DBPassword>]]

Description: This message describes the usage of the csmlsreception command.
(S): Returns the command's response.
(O): Check the command arguments and values, and then re-execute the command.

KDEC10501-E

The command cannot be executed because you do not have administrator privileges.

Description: The command cannot be executed because the user does not have administrator privileges.
(S): Cancels processing.
(O): Re-execute the command on a command prompt that you have executed as an administrator.

KDEC10502-E

An error occurred while the permissions were being checked.

Description: An error occurred while the permissions were being checked.
(S): Cancels processing.
(O): The memory may be insufficient. Increase the available space, and then re-execute the command. If the error cannot be corrected, contact the customer engineer.

KDEC11001-E

The UOC program returned an unexpected exception. (component ID = aa....aa, user class name = bb....bb, operation name = cc....cc, error message = dd....dd)

aa....aa: Invocation source service ID

bb....bb: UOC class name

cc....cc: Method name with error

dd....dd: Exception information (contents of Throwable#toString)

Description: The component-common UOC returned an unexpected exception.
(S): Processing is interrupted.
(O): Correct the class that caused the exception.

KDEC11002-E

The loading of a UOC program invoked by a component failed. (user class name = aa....aa, property file path = bb....bb, error message = cc....cc)

aa....aa: UOC class name

bb....bb: Path of the property file

cc....cc: Exception information (contents of Throwable#toString)

Description: An attempt to generate a class instance invoked by the component-common UOC failed.
(S): Processing is interrupted.
(O): Correct the class that caused the exception.

KDEC11003-E

The loading of the property file for UOC programs and components failed. (property file path = aa....aa, error message = bb....bb)

aa....aa: Path of the property file

bb....bb: Exception information (contents of Throwable#toString)

Description: An attempt to read the property file for the component-common UOC failed.
(S): Processing is interrupted.
(O): Correct the property file that caused the exception.

KDEC11101-E

An attempt to generate instances for the instance pool failed.

Description: An attempt to generate instances for the instance pool failed.
(S): Processing is interrupted.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC11201-E

The value specified for a parameter is invalid. (value = aa....aa, method name = bb....bb)

aa....aa: Setup-value

bb....bb: Method name

fully-qualified-class-name#method-name is displayed.

Description: The value specified for a parameter is invalid.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the specified value.

KDEC11202-E

An attempt to convert the data failed. (error message = aa....aa, method name = bb....bb)

aa....aa: Error message

bb....bb: Method name

fully-qualified-class-name#method-name is displayed.

Description: An attempt to perform data transformation failed.
(S): Processing is interrupted.
(O): If the cause of the error can be identified from the error message, eliminate the cause of the error from the specified message. If the cause of the error cannot be identified, collect the log and trace information, and then contact the maintenance personnel.

KDEC11301-I

csauseradd will now start.

Description: The csauseradd command will start.
(S): Processing continues.

KDEC11302-I

csauserdel will now start.

Description: The csauserdel command will start.
(S): Processing continues.

KDEC11303-I

csauserls will now start.

Description: The csauserls command will start.
(S): Processing continues.

KDEC11304-I

The password authentication information will now be registered. (user name = aa....aa)

aa....aa: User name

Description: The password authentication information will be registered.
(S): Processing continues.

KDEC11305-I

The password authentication information has been registered. (user name = aa....aa)

aa....aa: User name

Description: The password authentication information has been registered.
(S): Processing continues.

KDEC11306-I

The password authentication information will now be updated. (user name = aa....aa)

aa....aa: User name

Description: The password authentication information will be updated.
(S): Processing continues.

KDEC11307-I

The password authentication information has been updated. (user name = aa....aa)

aa....aa: User name

Description: The password authentication information has been updated.
(S): Processing continues.

KDEC11308-I

The password authentication information will now be deleted. (user name = aa....aa)

aa....aa: User name

Description: The password authentication information will be deleted.
(S): Processing continues.

KDEC11309-I

The password authentication information has been deleted. (user name = aa....aa)

aa....aa: User name

Description: The password authentication information has been deleted.
(S): Processing continues.

KDEC11310-I

csauseradd ended normally.

Description: The csauseradd command ended normally.
(S): Terminates processing.

KDEC11311-I

csauserdel ended normally.

Description: The csauserdel command ended normally.
(S): Terminates processing.

KDEC11312-I

csauserls ended normally.

Description: The csauserls command ended normally.
(S): Terminates processing.

KDEC11313-I

Usage:

csauseradd [-h] -user <UserName> -pass <Password> [-r] -f <Password Authentication Information Definition File Path>

Description: This message describes the usage of the csauseradd command.
(S): Terminates processing.
(O): Check the message for the command usage.

KDEC11314-I

Usage:

csauserdel [-h] -user <UserName> -f <Password Authentication Information Definition File Path>

Description: This message describes the usage of the csauserdel command.
(S): Terminates processing.
(O): Check the message for the command usage.

KDEC11315-I

Usage:

csauserls [-h] -f <Password Authentication Information Definition File Path>

Description: This message describes the usage of the csauserls command.
(S): Terminates processing.
(O): Check the message for the command usage.

KDEC11316-E

The command argument syntax is invalid. (command argument = aa....aa)

aa....aa: Invalid argument

Description: The command argument syntax is invalid.
(S): Terminates processing.
(O): Review and, if necessary, revise the command argument.

KDEC11317-E

An update of the file failed because the file was being updated by another command that was executed at the same time.

Description

An attempt to update the file failed because the file was being updated by another command that was executed at the same time.

(S)

Terminates processing.

(O)

Take one of the following actions:

If the csauseradd command was executed:

Check the current registration information by using the csauserls command. If necessary, re-execute the csauseradd or csauserdel command.
If the csakeyadd command was executed:

Check the current registration information by using the csakeyls command. If necessary, re-execute the csakeyadd or csakeydel command.

KDEC11318-E

A memory shortage occurred.

Description: A memory shortage occurred.
(S): Terminates processing.
(O): Increase the available memory, and then re-execute the processing.

KDEC11319-E

An unexpected exception occurred. (details = aa....aa)

aa....aa: Detailed information

Description: An unexpected exception occurred.
(S): Terminates processing.
(O): Contact maintenance personnel.

KDEC11320-E

An attempt to access the file failed. (details = aa....aa)

aa....aa: Detailed information

Description: File access failed.
(S): Terminates processing.
(O): Check the detailed information and eliminate the cause of the error, and then re-execute the processing.

KDEC11321-E

An attempt was made to register password authentication information that already exists. (user name = aa....aa)

aa....aa: User name

Description: An attempt was made to register password authentication information that already exists.
(S): Terminates processing.
(O): Check the user information by using the csauserls command, specify the correct user name, and then re-execute the command.

KDEC11322-E

An attempt was made to update password authentication information that does not exist. (user name = aa....aa)

aa....aa: User name

Description: An attempt was made to update password authentication information that does not exist.
(S): Terminates processing.
(O): Check the user information by using the csauserls command, specify the correct user name, and then re-execute the command.

KDEC11323-E

An attempt was made to delete password authentication information that does not exist. (user name = aa....aa)

aa....aa: User name

Description: An attempt was made to delete password authentication information that does not exist.
(S): Terminates processing.
(O): Check the user information by using the csauserls command, specify the correct user name, and then re-execute the command.

KDEC11324-E

One or more prohibited characters were specified. (command argument = aa....aa)

aa....aa: Invalid argument

Description

One or more prohibited characters were specified.

(S)

Terminates processing.

(O)

Take one of the following actions:

If the csauseradd command was executed:

Specify the correct user name and password.
If the csakeyadd command was executed:

Specify the correct key ID and passphrase.

KDEC11325-E

The length of the aa....aa argument is 1-bb....bb characters.

aa....aa: Invalid argument

bb....bb: Maximum number of characters allowed in the argument

Description: The length of the aa....aa argument must be in the range from 1 to bb....bb.
(S): Terminates processing.
(O): Revise the length of the specified argument to a specifiable range.

KDEC11326-E

csauseradd ended abnormally.

Description: The csauseradd command ended abnormally.
(S): Terminates processing.
(O): Check the error message that was displayed immediately before this message.

KDEC11327-E

csauserdel ended abnormally.

Description: The csauserdel command ended abnormally.
(S): Terminates processing.
(O): Check the error message that was displayed immediately before this message.

KDEC11328-E

csauserls ended abnormally.

Description: The csauserls command ended abnormally.
(S): Terminates processing.
(O): Check the error message that was displayed immediately before this message.

KDEC11329-I

csakeyadd will now start.

Description: The csakeyadd command will start.
(S): Processing continues.

KDEC11330-I

csakeydel will now start.

Description: The csakeydel command will start.
(S): Processing continues.

KDEC11331-I

csakeyls will now start.

Description: The csakeyls command will start.
(S): Processing continues.

KDEC11332-I

The public key authentication information will now be registered. (key ID = aa....aa)

aa....aa: Key ID

Description: The public key authentication information will be registered.
(S): Processing continues.

KDEC11333-I

The public key authentication information has been registered. (key ID = aa....aa)

aa....aa: Key ID

Description: The public key authentication information has been registered.
(S): Processing continues.

KDEC11334-I

The public key authentication information will now be updated. (key ID = aa....aa)

aa....aa: Key ID

Description: The public key authentication information will be updated.
(S): Processing continues.

KDEC11335-I

The public key authentication information has been updated. (key ID = aa....aa)

aa....aa: Key ID

Description: The public key authentication information has been updated.
(S): Processing continues.

KDEC11336-I

The public key authentication information will now be deleted. (key ID = aa....aa)

aa....aa: Key ID

Description: The public key authentication information will be deleted.
(S): Processing continues.

KDEC11337-I

The public key authentication information has been deleted. (key ID = aa....aa)

aa....aa: Key ID

Description: The public key authentication information has been deleted.
(S): Processing continues.

KDEC11338-I

csakeyadd ended normally.

Description: The csakeyadd command ended normally.
(S): Processing continues.

KDEC11339-I

csakeydel ended normally.

Description: The csakeydel command ended normally.
(S): Terminates processing.

KDEC11340-I

csakeyls ended normally.

Description: The csakeyls command ended normally.
(S): Terminates processing.

KDEC11341-I

Usage:

csakeyadd [-h] -keyfile <PrivateKey File Path> [-pass <Passphrase>] -keyid <key ID> [-r] -f <PublicKey Authentication Information Definition File Path>

Description: This message describes the usage of the csakeyadd command.
(S): Terminates processing.
(O): Check the message for the command usage.

KDEC11342-I

Usage:

csakeydel [-h] -keyid <key ID> -f <PublicKey Authentication Information Definition File Path>

Description: This message describes the usage of the csakeyde command.
(S): Terminates processing.
(O): Check the message for the command usage.

KDEC11343-I

Usage:

csakeyls [-h] -f <PublicKey Authentication Information Definition File Path>

Description: This message describes the usage of the csakeyls command.
(S): Terminates processing.
(O): Check the message for the command usage.

KDEC11344-E

An attempt was made to register public key authentication information that already exists. (key ID = aa....aa)

aa....aa: Key ID

Description: An attempt was made to register public key authentication information that already exists.
(S): Terminates processing.
(O): Check the contents of the registered public key authentication information by using the csakeyls command, specify the correct key ID, and then re-execute the command.

KDEC11345-E

An attempt was made to update public key authentication information that does not exist. (key ID = aa....aa)

aa....aa: Key ID

Description: An attempt was made to update public key authentication information that does not exist.
(S): Terminates processing.
(O): Check the contents of the registered public key authentication information by using the csakeyls command, specify the correct key ID, and then re-execute the command.

KDEC11346-E

An attempt was made to delete public key authentication information that does not exist. (key ID = aa....aa)

aa....aa: Key ID

Description: An attempt was made to delete public key authentication information that does not exist.
(S): Terminates processing.
(O): Check the contents of the registered public key authentication information by using the csakeyls command, specify the correct key ID, and then re-execute the command.

KDEC11347-W

An attempt to initialize the message log has failed. (prefix string of output file = aa....aa, method name = bb....bb, error cause = cc....cc)

aa....aa: Parameter used for initialization (output-destination-directory\message)

bb....bb: Method name of the Hitachi Trace Common library

cc....cc: Detailed message of the Hitachi Trace Common library

Description

An attempt to initialize the message log failed.

(S)

Complies with the message that is output next.

(O)

Check the detailed message and eliminate the cause of the error. If null is displayed for the detailed message, check the following and then eliminate the cause of the error:

Make sure that the absolute path is specified for the path of the message log output destination directory.
Make sure that a file can be created in the message log output destination directory.

KDEC11348-E

Log information cannot be output because an attempt to initialize the message log has failed.

Description: Log information cannot be output because an attempt to initialize the message log failed.
(S): Cancels the collection of message log information, and then cancels processing.
(O): See the messages displayed before this message, and then eliminate the cause of the error.

KDEC11349-W

An error occurred while outputting information to the message log. (method name = aa....aa, error cause = bb....bb)

aa....aa: Method name of the Hitachi Trace Common library

bb....bb: Detailed message of the Hitachi Trace Common library

Description: An error occurred during output of the message log.
(S): Cancels the collection of message log information and continues processing.
(O): Eliminate the cause of the error on the basis of the detailed message.

KDEC11350-W

aa....aa

aa....aa: Stack trace information

Description

This message indicates the stack trace information for the errors that occurred during command processing.

(S)

Processing is interrupted.

(O)

See the error message displayed just before this message, and then eliminate the cause of the error.

If the cause of the error is associated with operations, re-execute the processing.

If the cause of the error is not associated with operations, collect the log, and then contact maintenance personnel.

KDEC11351-E

One or more property values specified in the definition file are invalid. (file name = aa....aa, key name = bb....bb, specified value = cc....cc)

aa....aa: Path of the definition file

bb....bb: Key name

cc....cc: Specified value

Description: An invalid property value is specified in the definition file for user-authentication information management commands.
(S): Terminates processing.
(O): Correct the property value, and then re-execute the processing.

KDEC11352-W

The default value will be used for the message log output path. (default value = aa....aa)

aa....aa: Default value

Description: The default value will be assumed for the message log output path.
(S): Outputs trace information to the default output destination and continues processing.
(O): Make sure that the specified message log output path exists in the definition file for user-authentication information management commands. Alternatively, see the message that was displayed immediately before this message, and then eliminate the cause of the error.

KDEC11353-E

csakeyadd ended abnormally.

Description: The csakeyadd command ended abnormally.
(S): Terminates processing.
(O): Check the error message that was displayed immediately before this message.

KDEC11354-E

csakeydel ended abnormally.

Description: The csakeydel command ended abnormally.
(S): Terminates processing.
(O): Check the error message that was displayed immediately before this message.

KDEC11355-E

csakeyls ended abnormally.

Description: The csakeyls command ended abnormally.
(S): Terminates processing.
(O): Check the error message that was displayed immediately before this message.

KDEC11356-E

The specified file does not exist. (command argument = aa....aa, file path = bb....bb)

aa....aa: Command argument

bb....bb: File path

Description: The specified file does not exist.
(S): Terminates processing.
(O): Make sure that the file specified for the command argument exists.

KDEC19901-E

An internal error occurred. (class = aa....aa, method = bb....bb, information = cc....cc)

aa....aa: Class name (including the package name) in which the internal error occurred

bb....bb: Method name in which the internal error occurred

cc....cc: Maintenance information

Description: An internal error occurred.
(S): Cancels processing.
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC19902-W

A message assembly error occurred. (information = aa....aa)

aa....aa: Maintenance information

Description: An internal error occurred during message assembly when the log message was output.
(S): Resumes processing (depending on the processing that follows output of the intended message).
(O): Collect the log and trace information, and then contact the maintenance personnel.

KDEC19903-E

The Cosminexus installation directory was not found.

Description: An attempt to obtain the service platform installation directory failed.
(S): Cancels processing.
(O): Check to see if the COSMINEXUS_HOME system environment variable has been set. If the environment variable COSMINEXUS_HOME has been set, collect the log and trace information, and then contact the maintenance personnel.