2.14 Messages from KDEH20000 to KDEH30999
This section describes the messages from KDEH20000 to KDEH30999.
-
KDEH20000-I
Message Queue - Adapter started. (version = aa....aa, adapter name = bb....bb)
aa....aa: Version information for the Message Queue adapter
bb....bb: Adapter name
- Description
-
The FTP adapter started.
-
KDEH20001-E
The processing to start Message Queue - Adapter has failed. (adapter name = aa....aa)
aa....aa: Adapter name
- Description
-
An attempt to start the FTP adapter failed.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
See the messages displayed before this message, and eliminate the cause of the error.
-
KDEH20002-E
An internal error occurred during the processing to start Message Queue - Adapter. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Internal method name
cc....cc: Exception information
- Description
-
An internal error occurred during the starting of the Message Queue adapter.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH20100-E
An internal error occurred during the processing to start Message Queue - Adapter. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Internal method name
cc....cc: Exception information
- Description
-
An internal error occurred during the starting of the Message Queue adapter.
- (S)
-
Processing is cancelled.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH20500-I
Analysis of the Message Queue - Adapter configuration has started. (adapter name = aa....aa)
aa....aa: Adapter name
- Description
-
The parsing of the Message Queue adapter definitions started.
-
KDEH20501-I
Analysis of the Message Queue - Adapter configuration ended normally. (adapter name = aa....aa)
aa....aa: Adapter name
- Description
-
The parsing of the Message Queue adapter definitions ended normally.
-
KDEH20502-E
An error occurred during analysis of the Message Queue - Adapter configuration file. (adapter name = aa....aa, configuration file name = bb....bb)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter communication-configuration definition file
- Description
-
An error occurred during the parsing of the Message Queue adapter communication-configuration definition file.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Check the messages displayed before this message and take an appropriate action.
-
KDEH20503-E
The Message Queue - Adapter configuration file does not exist. (adapter name = aa....aa, configuration file name = bb....bb)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter communication-configuration definition file
- Description
-
The Message Queue adapter communication-configuration definition file does not exist.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Create the Message Queue adapter communication-configuration definition file in the development environment, and then re-package the Message Queue adapter.
-
KDEH20504-E
The XML schema file does not exist. (adapter name = aa....aa, XML schema file name = bb....bb)
aa....aa: Adapter name
bb....bb: Name of the XML schema file used for parsing the Message Queue adapter communication-configuration definitions
- Description
-
The XML schema file used for parsing the Message Queue adapter communication-configuration definitions does not exist.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
The XML schema file for parsing the Message Queue adapter communication-configuration definitions might have been deleted, or Service Coordinator might not have been installed in the runtime environment. Check the Service Coordinator installation directory.
-
KDEH20505-E
The specified operation name is already defined. (adapter name = aa....aa, configuration file name = bb....bb, operation name = cc....cc, line number = dd....dd)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter communication-configuration definition file
cc....cc: Operation name
dd....dd: Line number specifying the duplicated operation name
- Description
-
The operation name is already defined.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Correct the Message Queue adapter communication-configuration definition file in the development environment, and then re-package the Message Queue adapter.
-
KDEH20506-E
An error occurred while the Message Queue - Adapter configuration file was being authenticated. (adapter name = aa....aa, configuration file name = bb....bb, line number = cc....cc, exception information = dd....dd)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter communication-configuration definition file
cc....cc: Number of the line where the error occurred
dd....dd: XML Processor message ID + Message text
- Description
-
An error occurred during the validation of the Message Queue adapter communication-configuration definition file.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Based on the XML Processor message ID that has been output, check the contents coded for the message ID in"Application Server XML Processor User Guide", correct the Message Queue adapter communication-configuration definition file, and then re-package the Message Queue adapter.
-
KDEH20507-E
An internal error occurred in Message Queue - Adapter. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Internal method name
cc....cc: Exception information
- Description
-
An internal error occurred during the processing of the Message Queue adapter.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH20508-E
The execution environment properties file does not exist. (adapter name = aa....aa, file name = bb....bb)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
- Description
-
The Message Queue adapter runtime-environment property file does not exist.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Create the Message Queue adapter runtime-environment property file, and then restart the Message Queue adapter.
-
KDEH20509-E
The execution environment properties file cannot be accessed. (adapter name = aa....aa, file name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Exception information
- Description
-
The Message Queue adapter runtime-environment property file cannot be accessed. A possible cause is that the security manager does not permit the reading of the file.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Code the appropriate permissions in the security policy file so that you can access the Message Queue adapter runtime-environment property file. Take the appropriate action and then restart the Message Queue adapter.
-
KDEH20510-E
An attempt to read the execution environment properties file has failed. (adapter name = aa....aa, file name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Exception information
- Description
-
An attempt to read the Message Queue adapter runtime-environment property file failed.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH20511-W
An attempt to close the execution environment properties file has failed. (adapter name = aa....aa, file name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Exception information
- Description
-
An attempt to close the Message Queue adapter runtime-environment property file failed.
- (S)
-
Processing continues.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH20512-W
The default value will be assumed because a property value specified in the execution environment properties file is invalid. (adapter name = aa....aa, file name = bb....bb, key name = cc....cc, specified value = dd....dd, default value = ee....ee)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Key name
dd....dd: Specified value
ee....ee: Default value
- Description
-
The default value is assumed because a property value specified in the Message Queue adapter runtime-environment property file is incorrect.
- (S)
-
The default value is set up and processing continues.
- (O)
-
Specify the correct property value, and then restart the Message Queue adapter.
-
KDEH20513-E
The execution environment properties file contains an invalid escape sequence. (adapter name = aa....aa, file name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Exception information for java.lang.IllegalArgumentException
- Description
-
The Message Queue adapter runtime-environment property file contains an invalid Unicode escape sequence.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Correct the Message Queue adapter runtime-environment property file, and then restart the Message Queue adapter.
-
KDEH20514-E
The aa....aa property does not exist in the execution environment properties file. (adapter name = bb....bb, file name = cc....cc)
aa....aa: Key name
bb....bb: Adapter name
cc....cc: Name of the Message Queue adapter runtime-environment property file
- Description
-
A property indicated in a key name in the Message Queue adapter runtime-environment property file does not exist.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Correct the Message Queue adapter runtime-environment property file, and then restart the Message Queue adapter.
-
KDEH20515-E
A property value specified in the execution environment properties file is invalid. (adapter name = aa....aa, file name = bb....bb, key name = cc....cc, specified value = dd....dd)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Key name
dd....dd: Specified value
- Description
-
A property value specified in the Message Queue adapter runtime-environment property file is invalid.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Correct the Message Queue adapter runtime-environment property file, and then restart the Message Queue adapter.
-
KDEH20516-E
The Message Queue - Adapter configuration file name element was not found in the Message Queue - Adapter environment file. (adapter name = aa....aa, environment file name = bb....bb)
aa....aa: Adapter name
bb....bb: Name of the environment-definition file
- Description
-
The element ("adpmq_deffile") of the Message Queue adapter communication-configuration definition file name was not found in the Message Queue adapter environment-definition file.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Correct the Message Queue adapter environment-definition file in the development environment, and then re-package the Message Queue adapter.
-
KDEH20517-W
A file path specified in the execution environment properties file is invalid. (adapter name = aa....aa, file name = bb....bb, key name = cc....cc, error code = dd....dd)
aa....aa: Adapter name
bb....bb: Name of the Message Queue adapter runtime-environment property file
cc....cc: Key name
dd....dd: Cause code
Cause code
Contents
11
The UNC format is specified.
12
A relative path is specified.
13
The specified file path contains a parent directory expression, current directory expression, or a symbolic link.
14
The length of the specified path string is invalid.
15
An error occurred during the directory check.
16
The character encoding is not supported.
17
An I/O error occurred.
18
An invalid file name is specified (null).
- Description
-
The file path specified in the Message Queue adapter runtime-environment property file is invalid.
- (S)
-
The start processing of the Message Queue adapter continues.
- (O)
-
Correct the Message Queue adapter runtime-environment property file, and then restart the Message Queue adapter.
-
KDEH20900-E
The message log file was not found.
- Description
-
The message log file was not found.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
Contact maintenance personnel.
-
KDEH20901-E
Initialization of the message log file has failed. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Method name
cc....cc: Exception information
- Description
-
An attempt to initialize the message log failed.
- (S)
-
Complies with the message that is output next.
- (O)
-
Contact maintenance personnel.
-
KDEH20902-W
Initialization of the trace has failed. (adapter name = aa....aa, trace name = bb....bb, output file prefix string= cc....cc, number of output files = dd....dd, size of output files = ee....ee, error message = ff....ff)
aa....aa: Adapter name
bb....bb: Trace name
-
method trace: Method trace
-
data trace: Data trace
-
stack trace: Stack trace (Exception log)
cc....cc: Parameter used for initialization (<Output destination directory>\mtdtrace)
dd....dd: Parameter used for initialization (number of output files)
ee....ee: Parameter used for initialization (size of output file)
ff....ff: Error message
- Description
-
An attempt to initialize the trace failed.
- (S)
-
Complies with the message that is output next.
- (O)
-
If the cause of the error is an invalid parameter, correct the Message Queue adapter runtime-environment property file, and then restart the Message Queue adapter. If the cause of the error is not associated with operations, collect the log and trace information, and then contact maintenance personnel.
-
-
KDEH20903-W
The default value will be assumed for the trace output path. (adapter name = aa....aa, trace name = bb....bb, default value = cc....cc)
aa....aa: Adapter name
bb....bb: Trace name
-
method trace: Method trace
-
data trace: Data trace
-
stack trace: Stack trace (Exception log)
cc....cc: Default value
- Description
-
The default value is assumed for the trace output path.
- (S)
-
The trace is output to the default output destination and processing continues.
- (O)
-
See the messages displayed before this message, and eliminate the cause of the error.
-
-
KDEH20904-E
The trace cannot be output because the default trace output path could not be acquired. (adapter name = aa....aa, trace name = bb....bb)
aa....aa: Adapter name
bb....bb: Trace name
-
method trace: Method trace
-
data trace: Data trace
-
stack trace: Stack trace (Exception log)
- Description
-
The trace cannot be output because the default trace output destination cannot be obtained.
- (S)
-
The start processing for Message Queue adapter is cancelled.
- (O)
-
See the messages displayed before this message, and eliminate the cause of the error.
-
-
KDEH21000-I
Message Queue - Adapter has been terminated. (adapter name = aa....aa)
aa....aa: Adapter name
- Description
-
The Message Queue adapter is stopped.
-
KDEH21001-W
An internal error occurred during the processing to terminate Message Queue - Adapter. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Internal method name
cc....cc: Exception information
- Description
-
An internal error occurred during the stopping of the Message Queue adapter.
- (S)
-
The stop processing of the Message Queue adapter continues.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH21900-W
An attempt to end the trace has failed. (adapter name = aa....aa, trace name = bb....bb, method name = cc....cc, error message = dd....dd)
aa....aa: Adapter name
bb....bb: Trace name
-
method trace: Method trace
-
data trace: Data trace
-
stack trace: Stack trace (Exception log)
cc....cc: Name of the method where the error occurred
dd....dd: Error message
- Description
-
An attempt to end the trace failed.
- (S)
-
The end processing continues.
- (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.
-
-
KDEH30000-E
An unsupported operation was specified. (adapter name = aa....aa, operation name = bb....bb)
aa....aa: Adapter name
bb....bb: Operation name
- Description
-
An unsupported operation was specified.
- (S)
-
Processing is cancelled.
- (O)
-
Specify an operation that is supported by the Message Queue adapter, and then re-execute the invoke service request.
-
KDEH30001-E
An unsupported message format was specified. (adapter name = aa....aa, operation name = bb....bb, message type = cc....cc, message format = dd....dd)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Message type
-
REQUEST: Request message
-
RESPONSE: Response message
dd....dd: Message format
-
UNKNOWN: Unknown
- Description
-
An unsupported message format was specified.
- (S)
-
Processing is cancelled.
- (O)
-
Specify a message format that is supported by the Message Queue adapter (XML, binary), and then re-execute the invoke service request.
-
-
KDEH30002-E
An attempt to acquire a request message has failed. (adapter name = aa....aa, operation name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Exception information
- Description
-
An attempt to obtain a request message failed.
- (S)
-
Processing is cancelled.
- (O)
-
Make sure that the request message is correct. If there is no problem with the request message, save the exception information, and then contact maintenance personnel.
-
KDEH30003-E
An attempt to save a response message has failed. (adapter name = aa....aa, operation name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Exception information
- Description
-
An attempt to save a response message failed.
- (S)
-
Processing is cancelled.
- (O)
-
Save the exception information, and then contact maintenance personnel.
-
KDEH30004-E
An attempt to save a fault message has failed. (adapter name = aa....aa, operation name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Exception information
- Description
-
An attempt to save a fault message failed.
- (S)
-
Processing is cancelled.
- (O)
-
Save the exception information, and then contact maintenance personnel.
-
KDEH30005-E
An error occurred during Message Queue - Adapter processing. (adapter name = aa....aa, operation name = bb....bb)
aa....aa: Adapter name
bb....bb: Operation name
- Description
-
An error occurred during the processing of the Message Queue adapter.
- (S)
-
Processing is cancelled.
- (O)
-
See the messages displayed before this message, and eliminate the cause of the error.
-
KDEH30006-E
An internal error occurred during Message Queue - Adapter processing. (adapter name = aa....aa, operation name = bb....bb, method name = cc....cc, exception information = dd....dd)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Internal method name
dd....dd: Exception information
- Description
-
An internal error occurred during the processing of the Message Queue adapter.
- (S)
-
Processing is cancelled.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH30007-E
Asynchronous communication is not supported. (adapter name = aa....aa, operation name = bb....bb)
aa....aa: Adapter name
bb....bb: Operation name
- Description
-
Asynchronous communication is not supported.
- (S)
-
Processing is cancelled.
- (O)
-
Set the communication model for the operation information settings of the Message Queue adapter definitions in the development environment to synchronous, and then re-package the Message Queue adapter.
-
KDEH30100-E
An internal error occurred during Message Queue - Adapter communication processing. (adapter name = aa....aa, method name = bb....bb, error code = cc....cc)
aa....aa: Adapter name
bb....bb: Method name
cc....cc: Cause code
Cause code
Content
11
null was specified for an argument of the invoke method.
12
An unexpected type of operation was specified.
13
The value obtained from the Message Queue adapter communication-configuration definition file is null.
16
The value obtained for the request message information is null.
17
The value obtained for the request message write data is null.
19
The value obtained for the message format is not an XML or binary value.
20
The argument for generating ArrayList is a negative value.
21
An attempt to create the request message write data in the XML format failed.
22
An out-of-scope index was specified for obtaining the ArrayList element.
23
An error (array error) occurred in the byte operations of a request message in the binary format.
24
An error (type mismatch) occurred in the byte operations of a request message in the binary format.
25
An error (null) occurred in the byte operations of a request message in the binary format.
26
An attempt to create a default response message failed (DOM generation failed).
27
An attempt to create a default response message failed (element settings failed).
31
An attempt to obtain an element value for a request message in the XML format failed.
32
An error (encoding error) occurred in the byte operations of a request message in the binary format.
33
An error (encoding error) occurred in the byte operations of a text message.
99
An unexpected error other than that described above occurred.
- Description
-
An internal error occurred during the communication processing of the Message Queue adapter.
- (S)
-
Processing is cancelled.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH30101-E
A specified resource adapter name was not found. (adapter name = aa....aa, operation name = bb....bb, resource adapter name = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Lookup Name of a resource adapter
- Description
-
The specified resource adapter was not found.
- (S)
-
Processing is cancelled.
- (O)
-
Make sure that the Lookup Name for the resource adapter is correctly specified in the HITACHI Application Integrated Property File and Message Queue adapter communication-configuration definition file. If the lookup name is correct, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30102-E
A specified queue name was not found. (adapter name = aa....aa, operation name = bb....bb, queue name = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Lookup Name of a queue
- Description
-
The specified queue was not found.
- (S)
-
Processing is cancelled.
- (O)
-
Make sure that the Lookup Name for the queue is correctly specified in the HITACHI Application Integrated Property File and Message Queue adapter communication-configuration definition file. If the Lookup Name is correct, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30103-W
A specified queue has no messages. (adapter name = aa....aa, operation name = bb....bb, queue name = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Lookup Name of a queue
- Description
-
There are no messages in the specified queue.
- (S)
-
Processing continues.
- (O)
-
Check the following causes of the error, and if the causes are applicable, wait for some time and then re-execute the processing. If problem is not resolved even after eliminating the cause, collect the log and trace information, and then contact maintenance personnel.
-
The message response monitoring time in the Message Queue adapter communication-configuration definition file lapsed when the messages to be received did not exist in the queue.
-
A transaction timeout occurred when the messages to be received did not exist in the queue.
-
No messages exist in the queue for receiving messages during a request for browsing or message reception.
-
-
KDEH30105-E
An exception occurred during character code conversion. (adapter name = aa....aa, operation name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Exception information for FileNotFoundException, IOException (also containing sub-classes)
- Description
-
An exception occurred during character code conversion.
- (S)
-
Processing is cancelled.
- (O)
-
Check the storage path of the transformation table (user mapping file) for code conversion, specified in the Message Queue adapter runtime-environment property file. If the exception information is for exceptions other than FileNotFoundException or IOException, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30106-E
An error occurred during character code conversion. (adapter name = aa....aa, operation name = bb....bb, error code = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Cause code#
- Note#
-
This is the return code of the HJCConverters.getConvertState method. The following table lists and describes the return code causes:
No.
Value
(Decimal number)
Return code
Cause
1
(00)
HJCConvertState.CST_NORMAL
The method ended successfully.
2
(01)
HJCConvertState.CST_CONVSTOP
The method ended because an undefined code was detected.
3
(02)
HJCConvertState.CST_HALFCODE
The method ended halfway through the multi-byte characters.
4
(03)
HJCConvertState.CST_SHIFTEND
The method ended when the input value was the first byte of the shift code.
5
(04)
HJCConvertState.CST_UNREGISTED_USERPROC
The settings specified the invocation of a user program when an undefined code is detected, but the function is not registered, so the method ended.
6
(05)
HJCConvertState.CST_BAD_SHIFTMODE
The method ended because an invalid shift code is set up in the return value of the function.
7
(06)
HJCConvertState.CST_ESCEND
The method ended because the escape sequence code is invalid. Note that the return code is returned only when the transformation source code is the JIS Kanji code.
8
(07)
HJCConvertState.CST_BAD_ESCMODE
The method ended because an invalid escape sequence code is set up in the return value of the function. Note that the return code is returned only when the transformation destination code and transformation source code is the JIS Kanji code.
9
(08)
HJCConvertState.CST_BAD_ENDIAN
The method ended because BOM could not be identified correctly. If the COP_UTFBOM option is specified for BOM data transformation, the BOM status of the BOM data might not match the specification for the following options:
-
COP_BIGENDIAN_UTF16
-
COP_BIGENDIAN_UTF32
-
- Description
-
An error occurred during character code conversion.
- (S)
-
Processing is cancelled.
- (O)
-
Check whether the character code of the binary definition specified in the request message format of a service component matches the character code set up in the Message Queue adapter communication-configuration definition file. If character codes are matching, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30107-E
The XML request message is invalid. (adapter name = aa....aa, operation name = bb....bb, error cause = cc....cc)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Cause
Cause information
Cause
The number of child elements of the root element is invalid.
The number of child elements of the root element is invalid.
The root element name is invalid.
The root element name is invalid.
A value of the element is invalid.
An element value is invalid.
The first child element of the root element is invalid.
The first child element of the root element is invalid.
The number of child elements of the user data element is invalid.
The number of child elements of the user data element is invalid.
The root element does not correspond to the operation type.
The root element does not correspond to the operation type.
The element cannot be omitted is not specified in the child element of the root element.
A mandatory element is missing from the child element of the root element.
The number of child elements of the mqheader element is invalid.
The number of child elements of the mqheader element is invalid.
The child element of the mqheader element is invalid.
The child element of the mqheader element is invalid.
- Description
-
The value of the XML request message is invalid.
- (S)
-
Processing is cancelled.
- (O)
-
Make sure that the request message is correct. If there is no problem with the request message, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30108-E
A binary request message value is invalid. (adapter name = aa....aa, operation name = bb....bb, value = cc....cc, error cause = dd....dd)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Value
dd....dd: Cause
Cause information
Cause
The type of the queue name length element is invalid.
The type of the queue name length element is invalid.
A value of the queue name length element is invalid.
The value of the queue name length element is invalid.
The length of the request message is invalid.
The overall length of the message is invalid.
- Description
-
The value of the binary request message is invalid.
- (S)
-
Processing is cancelled.
- (O)
-
Make sure that the request message is correct. If there is no problem with the request message, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30109-E
The error occurred by the method of the JMS interface. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Internal method name
cc....cc: Exception information
- Description
-
An error occurred due to a method of the JMS interface.
- (S)
-
Processing is cancelled.
- (O)
-
See the exception information, and review and, if necessary, revise, the JMS interface-related settings. If there is no problem in the review, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30110-W
The error occurred by the method of the JMS interface. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Internal method name
cc....cc: Exception information
- Description
-
An error occurred due to a method of the JMS interface.
- (S)
-
Processing continues.
- (O)
-
See the exception information, and review and, if necessary, revise, the JMS interface-related settings. If there is no problem in the review, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30111-E
Processing for the message aa....aa has failed. (adapter name = bb....bb, resource adapter name = cc....cc, queue name = dd....dd)
aa....aa: Communication type
-
send: Send processing
-
receive: Receive processing
-
browse: Browse processing
bb....bb: Adapter name
cc....cc: Lookup name of a resource adapter
dd....dd: Lookup Name of a queue
- Description
-
The communication processing of the Message Queue adapter failed.
- (S)
-
Processing is cancelled.
- (O)
-
Eliminate the cause of the error based on the message displayed just before this message. If recovery is not possible even after eliminating the cause of failure, collect the log and trace information, and then contact maintenance personnel.
-
-
KDEH30112-E
An unsupported message was received. (adapter name = aa....aa)
aa....aa: Adapter name
- Description
-
A message with an invalid message type was received.
- (S)
-
Processing is cancelled.
- (O)
-
Check whether there is a problem with the message format.
If there is no problem with the message format, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30113-E
XML conversion of a message has failed. (adapter name = aa....aa)
aa....aa: Adapter name
- Description
-
The XML conversion of a message failed.
- (S)
-
Processing is cancelled.
- (O)
-
Check whether there is a problem with the message format.
If there is no problem with the message format, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30114-E
The specified operation was not found. (adapter name = aa....aa, operation name = bb....bb)
aa....aa: Adapter name
bb....bb: Operation name
- Description
-
The specified operation was not found in the Message Queue adapter communication-configuration definition file.
- (S)
-
Processing is cancelled.
- (O)
-
Check whether the operation name is specified in the Message Queue adapter communication-configuration definition file.
If there is no problem with the specified operation name, collect the log and trace information, and then contact maintenance personnel.
-
KDEH30117-E
The message format is invalid. (adapter name = aa....aa, operation name = bb....bb, message type = cc....cc, message format = dd....dd)
aa....aa: Adapter name
bb....bb: Operation name
cc....cc: Message type
-
REQUEST: Request message
-
RESPONSE: Response message
dd....dd: Message format
-
BINARY: Binary message
- Description
-
The message format is invalid.
- (S)
-
Processing is cancelled.
- (O)
-
Set up the schema for the correct format for the request message or response message in the development environment, and then perform re-packaging.
-
-
KDEH30900-W
An internal error occurred during output to the message log file. (adapter name = aa....aa, method name = bb....bb, exception information = cc....cc)
aa....aa: Adapter name
bb....bb: Name of the method where the error occurred
cc....cc: Exception information
- Description
-
An internal error occurred during the output of the message log.
- (S)
-
The collection of message log is cancelled and processing continues.
- (O)
-
Collect the log and trace information, and then contact maintenance personnel.
-
KDEH30901-W
An error occurred during output of the trace file. (adapter name = aa....aa, trace name = bb....bb, method name = cc....cc, error cause = dd....dd)
aa....aa: Adapter name
bb....bb: Trace name
-
method trace: Method trace
-
data trace: Data trace
cc....cc: Name of the method where the error occurred
dd....dd: Cause
- Description
-
An error occurred during the output of the trace file.
- (S)
-
The collection of trace is cancelled and processing continues.
- (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.
-