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.