2.4 Messages from KDEC60000 to KDEC79999 : Messages

KDEC60000-E

Initialization of the DB adapter has failed. (adapter name = aa....aa, cause = bb....bb)

aa....aa: Service ID of the service adapter

When the cause code is 02: *
When the cause code is not 02: Adapter name

bb....bb: Cause code

Cause code	Content
`01`	An attempt to execute definition analysis process has failed
`02`	An attempt to acquire the service ID of database adapter has failed
`03`	An attempt to acquire the HCSC server name has failed
`90` to `99`	Other

Description: An attempt to initialize the database adapter failed.
(S): Cancels the processing.
(O): If the cause code is 01 or from 90 to 99, reference the message displayed before this message, and remove the cause of the error. For the other cause codes, collect the log and trace information, and then contact maintenance personnel.

KDEC60001-E

An attempt to parse the definition has failed. (adapter name = aa....aa, operation name = bb....bb, cause = cc....cc, information1 = dd....dd, information2 = ee....ee)

aa....aa: Service ID of the service adapter

bb....bb: Operation name

This information is not displayed, if the operation name cannot be identified.

cc....cc: Cause code

dd....dd: Information 1

ee....ee: Information 2

Cause code	Content	Information 1	Information 2
`01`	File read error	File name	This information is used by the database adapter for troubleshooting.
`02`	Invalid definition value	Parameter name	Defined value
`03`	Invalid name for self-defined file	Types of self-defined file SQL-Operation: SQL operation definition Application attributes: HITACHI Application Integrated Property File	None
`04`	Invalid definition item	Parameter name	`01`: There is no parameter `02`: There are multiple parameters `03`: Parameter value has been omitted
`05`	A value other than `XML` or `BINARY` is specified in the message type of the standard message.	Parameter name `input/ standard-message/ message-type`: Message type of the request message `output/ standard-message/ message-type`: Message type of the response message	Defined value
`06`	A value other than `XML` is specified in the message type of the database adapter message.	Parameter name `input/ service-message/ message-type`: Message type of the request message `output/ service-message/ message-type`: Message type of the response message	Defined value

Description

An attempt to parse the definition failed.

(S)

Cancels the processing.

(O)

Take one of the following actions according to the cause code. If action cannot be taken, contact the Cosminexus administrator.

When the cause code is 01

Check the existence of the corresponding file, access permissions, file contents, file size, and the usage of the file in other processes. Also, re-create the database adapter EAR file in the development environment. If the error cannot be corrected, collect the log and trace information, and then contact maintenance personnel.
When the cause code is 02 to 06

Check and, if necessary, revise the settings in the general-purpose custom adapter definitions, and then re-create the database adapter EAR file in the development environment.

KDEC60002-E

A service call was interrupted. (adapter name = aa....aa, HCSCCommonID = bb....bb, ServiceRequestID = cc....cc, ClientID = dd....dd, operation name = ee....ee, cause = ff....ff, RootApInfo = gg....gg)

aa....aa: Service ID of the database adapter

bb....bb: HCSC message common ID

cc....cc: Service request ID

dd....dd: Client correlation ID

ee....ee: Operation name

ff....ff: Cause code (maintenance information)

gg....gg: Root application information

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

Description: An attempt to process a service component failed.
(S): Cancels the processing.
(O): Check the messages displayed before this message, and eliminate the cause of the error.

KDEC60003-E

An exception occurred during finish processing for the DB adapter. (adapter name = aa....aa, cause = bb....bb)

aa....aa: Service ID of the service adapter

bb....bb: Cause code (maintenance information)

Description: An error occurred during the end processing of the database adapter.
(S): Cancels the processing.
(O): Check the message that was displayed before this message and eliminate the cause of the error.

KDEC62000-E

The specified telegram is invalid. (cause = aa....aa, information = bb....bb)

aa....aa: Cause code

bb....bb: Information

Cause code	Content	Information
`01`	Message type mismatch.	`input_telegram type =` `specified-requester-message-type` `defined_telegram type =` `defined-message-type` `message-type` is one of the following: `XML`: XML message `BINARY`: Binary message `ANY`: Any message `NONE`: No request message from the service requester
`02`	The operation name is not defined.	`operationName =` `specified-operation-name`
`03`	An internal error occurred.	`operationName =` `specified-operation-name`

Cause code

Content

Information

01

Message type mismatch.

input_telegram type = specified-requester-message-type

defined_telegram type = defined-message-type

message-type is one of the following:

XML: XML message
BINARY: Binary message
ANY: Any message
NONE: No request message from the service requester

02

The operation name is not defined.

operationName = specified-operation-name

03

An internal error occurred.

operationName = specified-operation-name

Description: The request message is invalid.
(S): Cancels the processing.
(O): Remove the cause of the error on the basis of the cause code. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC62001-E

An attempt to convert a telegram has failed. (cause = aa....aa, information = bb....bb)

aa....aa: Cause code

bb....bb: Information

Cause code	Content	Information
`01`	An attempt to execute data transformation processing has failed.	`beforeFormatId =` `format-ID-before-transformation` `afterFormatId =` `format-ID-after-transformation`
`60`	An error occurred while a request message was being processed. The request message might have a syntax error.	The error message might be output if the HCSC server is set up by specifying `advanced` for the `xmlanalyze-mode` property in the HCSC server setup definition file. In other cases, no information is output.
`61`	A non-null value was specified for a request format ID or a response format ID by the service requester, and no data transformation definition file or format definition file has been registered for the specified format ID.	`beforeFormatId =` `format-ID-before-transformation` `afterFormatId =` `format-ID-after-transformation`
`70` to `79`	The EAR file is invalid.	This information is used by the database adapter for troubleshooting.
`80` to `99`	An internal error occurred.	This information is used by the database adapter for troubleshooting.

Description: An attempt to transform a message failed.
(S): Cancels the processing.
(O): Remove the cause of the error on the basis of the cause code and the message that was displayed before this message. If the cause code is from 70 to 99, re-generate the EAR file. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC63000-E

An unsupported telegram was specified. (message type = aa....aa, telegram type = bb....bb)

aa....aa: Message type

REQUEST: Request message

bb....bb: Message format

BINARY: Binary message
UNKNOWN: Unknown

Description: An unsupported message format was specified.
(S): Cancels the processing.
(O): Specify the message format (XML message) that is supported by the database adapter, and then re-execute the service component invocation request.

KDEC63001-E

The specified telegram is invalid. (cause = aa....aa, information = bb....bb)

aa....aa: Cause code

bb....bb: Information

Cause code	Content	Information
Cause code	Content	When executing a single SQL statement	When executing multiple SQL statements^{#1 #2}
`01`	Root element name is invalid	Specified root element name
`02`	There is no element with the SQL identifier name or there are multiple elements with the SQL identifier name	Number of specified SQL identifier names	Number of specified SQL identifier names (Position)
`03`	The specified SQL identifier has not been defined in the SQL operation definition	Specified SQL identifier name	Specified SQL identifier names (Position)
`04`	`DBA_IN_DATA` element is missing	None	SQL identifier name (Position)
`05`	The `DBA_MULTI_SQL` element does not exist, or the number exceeds the upper-limit value	--	Number of `DBA_MULTI_SQL` elements specified
`06`	Elements other than the `DBA_MULTI_SQL` element exist below the `DBadapter` element	--	Specified element name
`11`	Argument element is missing	Element name	SQL identifier name.element name (Position)
`12`	Nodes other than `Text`, `CDATASection`, or `Comment` nodes exist under the argument element	Element name	SQL identifier name.element name (Position)
`13`	The argument element name is repeated	Element name	SQL identifier name.element name (Position)
`14`	An element that is neither a parameter element nor `IN` parameter element is specified under the SQL identifier element	Element name	SQL identifier name.element name (Position)
`21`	Attribute value is invalid	element-name.attribute-name = attribute-value	SQL identifier name.element name.attribute name = attribute value (Position)
`22`	Data not conforming to the `hexBinary` type of the XML Schema is detected. The request message must be revised.	`type` `=` `classification-of-non-conforming-data` `length` `=` `string-length` `char` `=` `non-conforming-characters` The following shows the values that can be displayed for `classification-of-non-conforming-data`, and the meaning. `LENGTH`: A character string contains an odd number of characters. `CHAR`: Characters other than 0 to 9, a to f, or A to F Either of the following values is displayed for `non-conforming-characters` depending on the content of `classification-of-non-conforming-data`: For `type` `=` `LENGTH`: `NONE` For `type` `=` `CHAR`: Characters not conforming to the `hexBinary` type
`23`	Data not conforming to the `base64Binary` type of the XML Schema is detected. The request message must be revised.	`length` `=` `string-length` `char` `=` `non-conforming-characters` `position` `=` `position-of-characters-with-error` Characters not conforming to the `base64Binary` type are displayed for `non-conforming-data-type`. The value displayed for `position-of-characters-with-error` might be the number of characters displayed for `string-length` or more if, for example, the number of characters is a multiple of 4 plus a single character. In such cases, `null` is displayed for `non-conforming-characters`.

Legend:: --: Not applicable.
#1: If the contents of multiple elements are invalid, the information related to the element in which the invalid contents were first detected is output.
#2: Out of the DBA_MULTI_SQL elements in the request message, the position of the corresponding DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

Description: The contents of the request message are invalid.
(S): Cancels the processing.
(O): Check, and if necessary, revise the service component invocation processing on the basis of the cause code, and then re-execute the service component invocation request.

KDEC63002-E

The telegram operation failed. (cause = aa....aa, information = bb....bb)

aa....aa: Cause code

bb....bb: Information

Cause code	Content	Information
`01`	Message acquisition failed	This information is used by the database adapter for troubleshooting.
`02`	An attempt to specify message settings failed	This information is used by the database adapter for troubleshooting.
`11`	DOM error occurred during message operations	This information is used by the database adapter for troubleshooting.

Description: The message operations failed.
(S): Cancels the processing.
(O): Reference the message that was displayed before this message and remove the cause of the error. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC63003-E

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

aa....aa: Service ID of the service adapter

bb....bb: Cause code

Cause code	Content
01	The connection information is not specified in the header message.
02	The optionalName element does not exist in the connection information of the header message.
03	No value is set for the optionalName element in the connection information of the header message.
04	There are multiple connection information items in the header message.

Description: The connection information specified when the service request was made, is invalid.
(S): Processing is cancelled.
(O): Eliminate the cause of the error on the basis of the cause code. If the error cannot be corrected, collect the log and trace information, and then contact maintenance personnel.

KDEC64000-E

An I/O error occurred. (file name = aa....aa, reason = bb....bb)

aa....aa: Name of the file with error

bb....bb: Cause of error

Description: An I/O error occurred.
(S): Cancels the processing.
(O): Check the existence of the corresponding file, the access permissions, and the usage of the file in other processes. If action cannot be taken, collect the log and trace information, and then contact maintenance personnel.

KDEC64001-E

The SQL operation definition file is not a well-formed XML document.

Description: The SQL operation definition file is not a well-formed XML document.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64002-E

SQL operation definition file error: The name of the root element is invalid.

Description: The format of the SQL operation definition file is invalid. The name of the root element is not <DBadapter_SQL_OPERATION>.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64003-E

SQL operation definition file error: The element has an invalid node. (element = aa....aa, error type = bb....bb)

aa....aa: Name of the element in which an invalid format was detected

bb....bb: Error type

01: There is an invalid attribute.
02: There is an invalid node under the corresponding element.

Description: The format of the SQL operation definition file is invalid. An invalid node exists.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64004-E

SQL operation definition file error: The format of an element name is incorrect. (element = aa....aa, error type = bb....bb)

aa....aa: Name of the element in which an invalid format was detected

When the element name can be acquired: name-of-the-element-in-which-an-invalid-format-was-detected
When the element name cannot be acquired: *

bb....bb: Name format type for the invalid element

01: SQL identifier name format (when the number of characters is greater than 256)
02: Argument element name format (when the number of characters is greater than 256)
03: SQL identifier name format (when DBadapter or DBA_MULTI_SQL is specified in the name)

Description: The format of the SQL operation definition file is invalid. There is an element with an incorrect name format. This message is output when the number of characters in the specified name is greater than 256 and when DBadapter or DBA_MULTI_SQL is specified in the SQL identifier name.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64005-E

SQL operation definition file error: An element was duplicated. (element = aa....aa, duplicated element = bb....bb)

aa....aa: Name of the element in which an invalid format was detected

When the element name can be acquired: name-of-the-element-in-which-an-invalid-format-was-detected
When the element name cannot be acquired: *

bb....bb: Duplicated element name

Description: The format of the SQL operation definition file is invalid.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64006-E

SQL operation definition file error: A required element could not be found. (element = aa....aa, required element = bb....bb)

aa....aa: Name of the element in which an invalid format was detected

bb....bb: Required element name

For SQL identifier: SQL_ID

Description: The format of the SQL operation definition file is invalid. A required element was not found.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64007-E

SQL operation definition file error: An invalid value for an element or attribute was detected. (element = aa....aa, attribute = bb....bb, cause = cc....cc)

aa....aa: Name of the element in which an invalid format was detected

When the element name can be acquired: name-of-the-element-in-which-an-invalid-format-was-detected
When the attribute value is invalid or the element name cannot be acquired: *

bb....bb: Name of the attribute in which an invalid format was detected

When the value set up for the element is normal: name-of-the-attribute-in-which-an-invalid-format-was-detected
When the value set up for the element is invalid: *

cc....cc: Cause of error

01: Not a database type.
02: Not in the format of Y and N.
03: Not an SQL command.
04: Non-numeric character or a number outside the range of int type.
05: Numeric character outside the specifiable range.
06: Null element.
07: The value is not hexBinary or base64Binary.

Description: The format of the SQL operation definition file is invalid. An invalid value was detected for an element or an attribute.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64008-E

SQL operation definition file error: A required attribute for a parameter element was not found. (SQL ID = aa....aa, parameter element = bb....bb, required attribute = cc....cc)

aa....aa: Name of the SQL identifier in which an error was detected

When the SQL identifier name can be acquired: name-of-the-SQL-identifier-in-which-an-error-was-detected
When the SQL identifier name cannot be acquired: *

bb....bb: Name of the argument element in which an error was detected

When the argument element name can be acquired: name-of-the-argument-element-in-which-an-error-was-detected
When the argument element name cannot be acquired: *

cc....cc: Required attribute name

Description: The format of the SQL operation definition file is invalid. The argument element does not have the required attribute.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64009-E

SQL operation definition file error: An invalid value for a parameter element or attribute was detected. (SQL ID = aa....aa, parameter element = bb....bb, attribute = cc....cc, cause = dd....dd)

aa....aa: Name of the SQL identifier in which an error was detected

When the SQL identifier name can be acquired: name-of-the-SQL-identifier-in-which-an-error-was-detected
When the SQL identifier name cannot be acquired: *

bb....bb: Name of the argument element in which an error was detected

When the argument element name can be acquired: name-of-the-argument-element-in-which-an-error-was-detected
When the argument element name cannot be acquired: *

cc....cc: Name of the attribute in which an invalid format was detected

When the value of cause 03, 04, or 05: *
For other cases: name-of-the-attribute-in-which-an-invalid-format-was-detected

dd....dd: Cause of error

01: The string cannot be specified for dba_inf.
02: The string cannot be specified for data_type.
03: There is an invalid attribute.
04: There is an invalid node.
05: The attribute values of duplicate argument elements do not match.

Description: The format of the SQL operation definition file is invalid. An error was detected in the value specified for an element or an attribute of an argument element.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64010-E

A DOM error occurred during an attempt to acquire SQL operation definition file information. (class = aa....aa, method = bb....bb, element = cc....cc, attribute = dd....dd, error code = ee....ee)

aa....aa: Class name

bb....bb: Method name

cc....cc: Name of the element that caused the error

When the element name can be acquired: name-of-the-element-that-caused-the-error
When an error occurs in the attribute or the element name cannot be acquired: *

dd....dd: Name of the attribute that caused the error

When no error has occurred in the element: attribute-that-caused-the-error
When an error has occurred in the element: *

ee....ee: Error code

Description: A DOM error occurred while the SQL operation definition file information was being obtained.
(S): Cancels the processing.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC64011-E

An invalid value is specified for an encoding declaration in the SQL operation definition file.

Description: An invalid value is specified for an encoding declaration in the SQL operation definition file.
(S): Cancels the processing.
(O): Check and, if necessary, revise the contents of the SQL operation definition file, and then re-create the database adapter EAR file in the development environment.

KDEC64012-E

The message file was not found.

Description: The message file was not found.
(S): Cancels the processing.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC66000-E

An attempt to connect to the database has failed. (DataSource name = aa....aa, error information = bb....bb, SQL state = cc....cc, error code = dd....dd)

aa....aa: Database reference name

bb....bb: DBMS-specific error message

cc....cc: SQL status

In HiRDB: SQLSTATE
In Oracle: Code indicating the SQL status
When the SQL status cannot be acquired: *

dd....dd: SQL code

In HiRDB: SQLCODE
In Oracle: ORA number

Description: An attempt to connect to the database failed.
(S): Cancels the processing.
(O): Remove the cause of the error on the basis of this message and the DBMS error information. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC66001-E

An attempt to close a connection to the database has failed. (DataSource name = aa....aa, error information = bb....bb, SQL state = cc....cc, error code = dd....dd)

aa....aa: Database reference name

bb....bb: DBMS-specific error message

cc....cc: SQL status

In HiRDB: SQLSTATE
In Oracle: Code indicating the SQL status
When the SQL status cannot be acquired: *

dd....dd: SQL code

In HiRDB: SQLCODE
In Oracle: ORA number

Description: An attempt to close a connection to the database failed.
(S): Cancels the processing.
(O): Remove the cause of the error on the basis of this message and the DBMS error information. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC66002-E

An attempt to acquire a data source has failed. (DataSource name = aa....aa)

aa....aa: Database reference name

Description: An attempt to obtain a database resource failed.
(S): Cancels the processing.
(O): Make sure that the value of the <res-ref-name> element in HITACHI Application Integrated Property File matches the value of the <DB_NAME> element in the SQL operation definition file. If the error cannot be corrected, collect the log and trace information, and then contact maintenance personnel.

KDEC66003-E

An SQL statement has a syntax error. (DataSource name = aa....aa, SQL ID = bb....bb, error information = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Database reference name

Optional name of the resource specified in the header variable if the destination is changed dynamically

bb....bb: SQL identifier name

When a single SQL statement is executed: SQL identifier name
When multiple SQL statements are executed^#: SQL identifier name (Position)

Note#

From among the DBA_MULTI_SQL elements in the request message, the position of the relevant DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

cc....cc: DBMS-specific error message

dd....dd: SQL status

In HiRDB: SQLSTATE
In Oracle: Code indicating the SQL status
If the status cannot be obtained: *

ee....ee: SQL code

In HiRDB: SQLCODE
In Oracle: ORA number

Description

An attempt to execute the SQL statement failed because of a syntax error in the SQL statement. This message is also output when you specify an SQL statement containing a data type that is not supported by the JDBC driver used by DB Connector for the search results, or when the database cannot be accessed.

When multiple SQL statements are executed, the information about the error that is detected first will be output.

(S)

Processing is cancelled.

(O)

When the cause of the error is a syntax error in the SQL statement

Eliminate the cause of the error on the basis of this message and the DBMS error information.
When the cause of the error is not a syntax error in the SQL statement

Eliminate the cause of the error on the basis of this message and the DBMS error information. If the error cannot be corrected, collect the log and trace information, and then contact maintenance personnel.

KDEC66004-E

An attempt to access the database has failed. (DataSource name = aa....aa, SQL ID = bb....bb, error information = cc....cc, SQL state = dd....dd, error code = ee....ee)

aa....aa: Database reference name

bb....bb: SQL identifier name

When executing a single SQL statement	When executing multiple SQL statements^#
SQL identifier name	SQL identifier name (Position)

#: Out of the DBA_MULTI_SQL elements in the request message, the position of the corresponding DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

cc....cc: DBMS-specific error message

dd....dd: SQL status

In HiRDB: SQLSTATE
In Oracle: Code indicating the SQL status
When the SQL status cannot be acquired: *

ee....ee: SQL code

In HiRDB: SQLCODE
In Oracle: ORA number

Description

An attempt to access the database failed.

When multiple SQL statements are executed, the information about the error that is detected first will be output.

(S)

Cancels the processing.

(O)

Remove the cause of the error on the basis of this message and the DBMS error information. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC66005-E

At least one unsupported data type is present in the search results. (DataSource name = aa....aa, SQL ID = bb....bb, table name = cc....cc, column name = dd....dd (ee....ee), data type = ff....ff)

aa....aa: Database reference name

Optional name of the resource specified in the header variable if the destination is changed dynamically

bb....bb: SQL identifier name

When executing a single SQL statement	When executing multiple SQL statements^#
SQL identifier name	SQL identifier name (Position)

#: Out of the DBA_MULTI_SQL elements in the request message, the position of the corresponding DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

cc....cc: table name

When the table name can be acquired: table-name
When the table name cannot be acquired: *

dd....dd: column name

When the column name can be acquired: column-name
When the column name cannot be acquired: *

ee....ee: Column number

ff....ff: Database-specific type

When the database-specific type can be acquired: database-specific-type acquired using getColumnTypeName of the ResultSetMetaData class
When the database-specific type cannot be acquired: *

Description

A data type unsupported by the database adapter is present in the search results. If the search results contain multiple data types that are not supported by the database adapter, the information about the unsupported data type that is detected first will be output.

When multiple SQL statements are executed, the information about the error that is detected first will be output.

(S)

Cancels the processing.

(O)

Check and, if necessary, revise the SQL statement to be executed so that the value of the type indicated by the data type is not included in the search results.

Alternatively, make sure that the correct value is specified for DB_TYPE (database type) in the SQL operation definition file.

KDEC66006-E

The format of the parameter element value is invalid. (SQL ID = aa....aa, parameter element = bb....bb, data type = cc....cc)

aa....aa: SQL identifier name

When executing a single SQL statement	When executing multiple SQL statements^#
SQL identifier name	SQL identifier name (Position)

#: Out of the DBA_MULTI_SQL elements in the request message, the position of the corresponding DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

bb....bb: Argument element name

cc....cc: Value of the attribute data_type in the SQL operation definition file

Description

The format of the argument element value is invalid.

When multiple SQL statements are executed, the information about the error that is detected first will be output.

(S)

Cancels the processing.

(O)

Make sure that the format of the argument element value matches the type specified in the data_type attribute in the SQL operation definition file.

KDEC66007-E

An attempt to set the IN parameter has failed. (DataSource name = aa....aa, SQL ID = bb....bb, parameter element = cc....cc, data type = dd....dd, error information = ee....ee, SQL state = ff....ff, error code = gg....gg)

aa....aa: Database reference name

Optional name of the resource specified in the header variable if the destination is changed dynamically

bb....bb: SQL identifier name

When executing a single SQL statement	When executing multiple SQL statements^#
SQL identifier name	SQL identifier name (Position)

#: Out of the DBA_MULTI_SQL elements in the request message, the position of the corresponding DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

cc....cc: Argument element name

dd....dd: Value of the attribute data_type in the SQL operation definition file

ee....ee: DBMS-specific error message

ff....ff: SQL status

In HiRDB: SQLSTATE
In Oracle: Code indicating the SQL status
When the SQL status cannot be acquired: *

gg....gg: SQL code

In HiRDB: SQLCODE
In Oracle: ORA number

Description

An attempt to set the IN parameter failed.

When multiple SQL statements are executed, the information about the error that is detected first will be output.

(S)

Cancels the processing.

(O)

Check whether the value of the data_type attribute in the SQL operation definition file matches the value corresponding to the data type in the database. If the values match, remove the cause of the error on the basis of this message and the DBMS error information. If the error cannot be removed, collect the log and trace information, and then contact maintenance personnel.

KDEC68000-I

The XML schema file was created successfully. (command = aa....aa, file name = bb....bb)

aa....aa: Command name

bb....bb: XML schema file name

Description: The creation of the XML schema file is complete.
(S): Terminates the command.

KDEC68001-E

Usage: csamkxmls -o <SQL operation definition file> -x <XML schema file> [-f]

Description: This message is output when the specified option or option argument is invalid. See this message and then re-execute the command.

KDEC68002-E

The specified option parameter is invalid. (command = aa....aa, option = bb....bb)

aa....aa: Command name

bb....bb: Invalid argument name

Description: The specified option argument is incorrect.
(S): Cancels the processing.
(O): Check the help message that is displayed after this message, and then re-execute the command.

KDEC68003-E

A required option was not specified. (command = aa....aa)

aa....aa: Command name

Description: A required option was not found. This message is output when the -o or -x options do not exist.
(S): Cancels the processing.
(O): Check the help message that is displayed after this message, and then re-execute the command.

KDEC68004-E

The specified file was not found. (command = aa....aa, file name = bb....bb)

aa....aa: Command name

bb....bb: Specified file name

Description: The specified file was not found. This message is output when the specified SQL operation definition file is not found.
(S): Cancels the processing.
(O): Check the SQL operation definition file name and path name, and then re-execute the command.

KDEC68005-E

The specified file already exists. (command = aa....aa, file name = bb....bb)

aa....aa: Command name

bb....bb: Specified file name

Description: The specified file already exists. This message is output when the specified XML schema file already exists and the -f option is not specified.
(S): Cancels the processing.
(O): Specify another XML schedule file or specify the -f option, and then re-execute the command.

KDEC68006-E

The user does not have permission to access the specified file. (command = aa....aa, file name = bb....bb, permission = cc....cc)

aa....aa: Command name

bb....bb: Specified file name

cc....cc: Required access permission

Description: The user does not have permissions to access the specified file. This message is output when the user does not have the write permissions (the -f option is specified) for the specified XML file, or the read permissions for the specified SQL operation definition file.
(S): Cancels the processing.
(O): Add the required permissions to the file, and then re-execute the command.

KDEC68007-E

An invalid file was specified. (command = aa....aa, file name = bb....bb)

aa....aa: Command name

bb....bb: Specified file name

Description: An invalid file was specified. This message is output when a file with an extension other than .xml or .xsd is specified or when a hidden file is specified.
(S): Cancels the processing.
(O): Check the file name and path name, and then re-execute the command.

KDEC68008-E

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

aa....aa: Command name

bb....bb: Specified file name

Description

The specified file name is invalid.

This message is output for one of the following conditions:

The name of the SQL operation definition file does not begin with csa_sql_.
The length of the XML schema file name (absolute path) exceeds 200 bytes.
The XML schema file name contains characters that cannot be used in the file name.

(S)

Cancels the processing.

(O)

Check the file name, and then re-execute the command.

KDEC68009-E

The message file was not found.

Description: The message file was not found.
(S): Cancels the processing.
(O): Contact the Cosminexus administrator.

KDEC68010-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 the processing.
(O): Re-execute the command on a command prompt that you have executed as an administrator.

KDEC68011-E

An error occurred while the permissions were being checked.

Description

An error occurred while the permissions were being checked.

processing.

(S)

Cancels the 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.

KDEC68020-E

The SQL operation definition file is not a well-formed XML document. (command = aa....aa)

aa....aa: Command name

Description: The SQL operation definition file is not a well-formed XML document.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68021-E

SQL operation definition file error: The name of the root element is invalid.

Description: The format of the SQL operation definition file is invalid. The name of the root element is not <DBadapter_SQL_OPERATION>.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68022-E

SQL operation definition file error: The element has an invalid node. (element = aa....aa, error type = bb....bb)

aa....aa: Name of the element in which the invalid format was detected

bb....bb: Error type

01: There is an invalid attribute.
02: There is an invalid node under the corresponding element.

Description: The format of the SQL operation definition file is invalid. An invalid node exists.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68023-E

SQL operation definition file error: The format of an element name is incorrect. (element = aa....aa, error type = bb....bb)

aa....aa: Name of the element in which the invalid format was detected

When the element name can be acquired: name-of-the-element-in-which-an-invalid-format-was-detected
When the element name cannot be acquired: *

bb....bb: Name format type for the invalid element

01: SQL identifier name format (when the number of characters is greater than 256)
02: Argument element name format (when the number of characters is greater than 256)
03: SQL identifier name format (when DBadapter or DBA_MULTI_SQL is specified in the name)

Description: The format of the SQL operation definition file is invalid. There is an element with an incorrect name format. This message is output when the number of characters in the specified name is greater than 256 and when DBadapter or DBA_MULTI_SQL is specified in the SQL identifier name.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68024-E

SQL operation definition file error: An element was duplicated. (element = aa....aa, duplicated element = bb....bb)

aa....aa: Name of the element in which the invalid format was detected

When the element name can be acquired: name-of-the-element-in-which-an-invalid-format-was-detected
When the element name cannot be acquired: *

bb....bb: Duplicated element name

Description: The format of the SQL operation definition file is invalid. An element was duplicated.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68025-E

SQL operation definition file error: A required element could not be found. (element = aa....aa, required element = bb....bb)

aa....aa: Name of the element in which an invalid format was detected

bb....bb: Required element name

For SQL identifier: SQL_ID

Description: The format of the SQL operation definition file is invalid. A required element was not found.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68026-E

SQL operation definition file error: An invalid value for an element or attribute was detected. (element = aa....aa, attribute = bb....bb, cause = cc....cc)

aa....aa: Name of the element in which the invalid format was detected

When the element name can be acquired: name-of-the-element-in-which-an-invalid-format-was-detected
When the attribute value is invalid or the element name cannot be acquired: *

bb....bb: Name of the attribute in which the invalid format was detected

When the value set up for the element is normal: name-of-the-attribute-in-which-an-invalid-format-was-detected
When the value set up for the element is invalid: *

cc....cc: Cause of error

01: Not a database type.
02: Not in the format of Y or N.
03: Not an SQL command.
04: Non-numeric character or a number outside the range of int type.
05: Numeric character outside the specifiable range.
06: Null element.
07: The value is not hexBinary or base64Binary.

Description: The format of the SQL operation definition file is invalid. An invalid value was detected for an element or attribute.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68027-E

SQL operation definition file error: A required attribute for a parameter element was not found. (SQL ID = aa....aa, parameter element = bb....bb, required attribute = cc....cc)

aa....aa: Name of the SQL identifier in which the error was detected

When the SQL identifier name can be acquired: name-of-the-SQL-identifier-in-which-an-error-was-detected
When the SQL identifier name cannot be acquired: *

bb....bb: Name of the argument element in which the error was detected

When the argument element name can be acquired: name-of-the-argument-element-in-which-an-error-was-detected
When the argument element name cannot be acquired: *

cc....cc: Required attribute name

Description: The format of the SQL operation definition file is invalid. An attribute required for an argument element was not found.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68028-E

SQL operation definition file error: An invalid value for a parameter element or attribute was detected. (SQL ID = aa....aa, parameter element = bb....bb, attribute = cc....cc, cause = dd....dd)

aa....aa: Name of the SQL identifier in which the error was detected

When the SQL identifier name can be acquired: name-of-the-SQL-identifier-in-which-an-error-was-detected
When the SQL identifier name cannot be acquired: *

bb....bb: Name of the argument element in which the error was detected

When the argument element name cannot be acquired: name-of-the-argument-element-in-which-an-error-was-detected
When the argument element name cannot be acquired: *

cc....cc: Name of the attribute in which an invalid format was detected

When the cause value is 03, 04, or 05: *
For other cases: name-of-the-attribute-in-which-an-invalid-format-was-detected

dd....dd: Cause of error

01: The string cannot be specified for dba_inf.
02: The string cannot be specified for data_type.
03: There is an invalid attribute.
04: There is an invalid node.
05: The attribute values of duplicate argument elements do not match.

Description: The format of the SQL operation definition file is invalid. An error was detected in the value specified for an element or attribute of an argument element.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68029-E

A DOM error occurred during an attempt to acquire SQL operation definition file information. (class = aa....aa, method = bb....bb, element = cc....cc, attribute = dd....dd, error code = ee....ee)

aa....aa: Class name

bb....bb: Method name

cc....cc: Name of the element that caused the error

When the element name can be acquired: name-of-the-element-that-caused-the-error
When an error occurs in the attribute or the element name cannot be acquired: *

dd....dd: Name of the attribute that caused the error

When no error has occurred in the element: name-of-the-attribute-that-caused-the-error
When an error has occurred in the element: *

ee....ee: Error code

Description: A DOM error occurred while the SQL operation definition file information was being obtained.
(S): Cancels the processing.
(O): Collect the exception information that is output after this message, and then contact maintenance personnel.

KDEC68030-E

An I/O error occurred. (command = aa....aa, file name = bb....bb, cause = cc....cc)

aa....aa: Command name

bb....bb: Name of the file with error

cc....cc: Error cause

Description: An I/O error occurred.
(S): Cancels the processing.
(O): Check the existence of this file, its access permissions, and whether or not the file is used in another process.

KDEC68031-E

An internal error occurred in during XML analysis. (class = aa....aa, method = bb....bb, information = cc....cc, error code = dd....dd)

aa....aa: Class name

bb....bb: Method name

cc....cc: Details

dd....dd: Error code

Description: An internal error occurred during XML parsing.
(S): Cancels the processing.
(O): Collect the exception information that is output after this message, and then contact maintenance personnel.

KDEC68032-E

An invalid value is specified for an encoding declaration in the SQL operation definition file. (command = aa....aa)

aa....aa: Command name

Description: An invalid value is specified for an encoding declaration in the SQL operation definition file.
(S): Cancels the processing.
(O): Check, and if necessary, revise the contents of the SQL operation definition file.

KDEC68099-E

An internal error occurred during command execution. (class = aa....aa, method = bb....bb, information = cc....cc, exception = dd....dd)

aa....aa: Class name

When the class name can be acquired: class-name
When the class name cannot be acquired: *

bb....bb: Method name

When the method name can be acquired: method-name
When the method name cannot be acquired: *

cc....cc: Detailed information

When the details can be acquired: details
When the details cannot be acquired: *

dd....dd: Name of the exception

When there is a corresponding exception name: exception-name
When there is no corresponding exception name: *

Description: An internal error occurred during command execution. If the XML schema file was created during the execution of the csamkxmls command, destroy the file.
(S): Cancels the processing.
(O): Collect the exception information that is output after this message, and then contact maintenance personnel.

KDEC70002-E

The message file was not found.

Description: The message file was not found.
(S): Cancels the processing.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC70003-W

Initialization of the method trace writer failed. (cause = aa....aa, error location = bb....bb)

aa....aa: Error cause

bb....bb: location of error

Description: An attempt to initialize the method trace failed.
(S): Resumes processing without outputting the method trace.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC70004-W

An attempt to close the method trace writer failed. (cause = aa....aa, error location = bb....bb)

aa....aa: Error cause

bb....bb: location of error

Description: An attempt to end the method trace failed.
(S): Resumes the method trace termination processing.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC70005-W

Initialization of the stack trace writer failed. (cause = aa....aa, error location = bb....bb)

aa....aa: Cause of the error

bb....bb: Location of the error

Description: An attempt to initialize the exception log failed.
(S): Processing continues without the output of the exception log.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC70006-W

An attempt to close the stack trace writer failed. (cause = aa....aa, error location = bb....bb)

aa....aa: Cause of the error

bb....bb: Location of the error

Description: An attempt to end the exception log failed.
(S): The exception log end processing continues.
(O): Collect the log and trace information, and then contact maintenance personnel.

KDEC79000-E

An internal error occurred. (class = aa....aa, method = bb....bb, maintenance information = cc....cc)

aa....aa: Class name

bb....bb: Method name

cc....cc: Maintenance information

Description: An internal error occurred.
(S): Terminates processing.
(O): Collect the log and trace information, and then contact maintenance personnel.