| Cause | The file does not exist. |
| Action | Check if the file exists or use another file. |
| Cause | An input file was not specified. |
| Action | Specify an input file. |
| Cause | Two or more input files were specified. |
| Action | Specify only one input file. |
| Cause | Cannot open the output file. |
| Action | Verify that the file name is correct. |
| Cause | The configuration file could not be found. |
| Action | Verify that the path to the configuration file is correct. |
| Cause | Invalid file extension. |
| Action | The input file name must have an extension. |
| Cause | The input file name is over 256 bytes long. |
| Action | Reduce the length of the file name. |
| Cause | Undefined cursor name. |
| Action | Verify that the cursor name is correct. |
| Cause | Undefined DB name. |
| Action | Verify that the DB name is correct. |
| Cause | The DML statement syntax is incorrect. |
| Action | Verify that the syntax of the DML statement is correct. |
| Cause | The dynamic SQL statement is invalid for the ANSI mode. |
| Action | Use a dynamic SQL statement that is valid for the ANSI mode. |
| Cause | A CONTEXT USE statement was not used to specify context application. |
| Action | Use a CONTEXT USE statement. |
| Cause | To use a thread-related command, the THREADS option needs to be set to YES. |
| Action | Set the THREADS option to YES. |
| Cause | The context is not allocated. |
| Action | Allocate the context. |
| Cause | The parameter expression is invalid. |
| Action | Check the expression syntax. |
| Cause | The host variable is not declared in the declare section. |
| Action | In ANSI or ISO mode, only variables declared between the EXEC be used as a host variable. |
| Cause | The array size of the host variable is invalid. |
| Action | Modify the array size of the host variable so that it is an integer greater than 1. |
| Cause | The identifier is not defined. |
| Action | Define the identifier. |
| Cause | The structure is not defined. |
| Action | Define the structure. |
| Cause | The type is not defined. |
| Action | Define the type. |
| Cause | Only objects defined as structures may be used in that manner. |
| Action | Use an object that is defined as a structure. |
| Cause | Accessed a pointer with a period (.), or accessed non-pointer with an arrow (->). |
| Action | Review the item and use the correct access method. |
| Cause | Undefined member of a structure. |
| Action | Define the object as a member of the structure. |
| Cause | An attempt was made to bind a multi-dimensional array type. |
| Action | Modify the bind parameter. |
| Cause | No name is defined for the host structure declared as array. |
| Action | Specify a name for the structure. |
| Cause | A structure cannot be bound in another structure. |
| Action | Delete the nested structure definition. |
| Cause | An array cannot be a member of the structure. |
| Action | Remove the array from the members of the structure. |
| Cause | The format of VARCHAR is invalid. |
| Action | If VARCHAR is an invalid array, modify it and re-declare it. |
| Cause | The cursor name is already defined. |
| Action | Use another cursor name. |
| Cause | The DB name is already defined. |
| Action | Use another DB name. |
| Cause | No SQL statement is prepared yet. |
| Action | Prepare an SQL statement. |
| Cause | The indicator variable is not a SHORT type. |
| Action | Declare the indicator variable as a SHORT type. |
| Cause | The indicator variable cannot be a structure because the host variable is not a structure. |
| Action | Match the type of host variable to the type of indicator variable. |
| Cause | The indicator variable must be a structure because the host variable is a structure. |
| Action | The indicator variable must be defined as a structure. |
| Cause | The host variable has different dimensions as the indicator variable. |
| Action | The indicator variable must have the same dimensions as the host variable. |
| Cause | Invalid signed or unsigned operator has been used to defined variables. |
| Action | Delete signed or unsigned operator. |
| Cause | Invalid type declared. |
| Action | Check if a structure or typedef definition is used with a primitive type. |
| Cause | Invalid type declaration. |
| Action | Check if the declaration of structure or typedef is duplicated. |
| Cause | More than one signed or unsigned operator. |
| Action | Correctly mark signed or unsigned. |
| Cause | Array variables cannot be used in WHERE clauses of a SELECT statement. |
| Action | Change array variables in WHERE clauses of the SELECT statement into general variables. |
| Cause | When updating, if at least one of host variables is an array type, all host variables should be array type, and vice versa. |
| Action | Declare all host variables as array. |
| Cause | The table does not exist or is not declared in any clause. |
| Action | Declare the table. |
| Cause | The column(s) could not be found. |
| Action | Check the name of the column(s). |
| Cause | Invalid DML syntax. |
| Action | Verify that the DML syntax is correct. |
| Cause | Invalid ESQL syntax . |
| Action | Verify that the ESQL syntax is correct. |
| Cause | Invalid C syntax. |
| Action | Verify that the C syntax is correct. |
| Cause | Failed to preprocess C programming language. |
| Action | Locate the cause of the error and modify it. |
| Cause | The SQL statement starts with a string that is not an ESQL directive. |
| Action | Verify that the ESQL syntax is correct. |
| Cause | The syntax should not contain an AT clause. |
| Action | Delete the AT clause. |
| Cause | The host variable type is not compatible with the column type of the table. |
| Action | Check the type of host variable. |
| Cause | The number of parameters is different from the number of columns. |
| Action | Check the number of parameters. |
| Cause | Failed to check semantics using server. |
| Action | Verify that the semantics are correct. |
| Cause | Unsupported option. |
| Action | Delete the option. |
| Cause | The option cannot be used here. |
| Action | Check the location (config file, command line, etc.) where location. |
| Cause | Invalid type of option value. |
| Action | Check the type of the option value. |
| Cause | Invalid option value. |
| Action | Check the option value. |
| Cause | Undefined option. |
| Action | Verify that the option exists. |
| Cause | Invalid format of the option value. |
| Action | Check the format of the option value. |
| Cause | If SQLCHECK=SEMANTICS (or FULL), USERID should be also specified. |
| Action | Specify the USERID option. |
| Cause | User ID must be less than 128 bytes. |
| Action | Reduce the size of the user ID. |
| Cause | Password must be less than 63 bytes. |
| Action | Reduce the size of the password. |
| Cause | Embedded PSM block was used without the SQLCHECK=SEMANTICS option. |
| Action | Specify the SQLCHECK=SEMANTICS option. |
| Cause | Failed to access the server for semantics check. |
| Action | Check the connection information and server status. |
| Cause | A C comment beginning with '/*' was not terminated. |
| Action | Terminate the comment properly. |
| Cause | UNION is not properly terminated. |
| Action | Check the syntax. |
| Cause | Failure while preprocessing C programming language. |
| Action | Correct the error as shown in the additional messages. |
| Cause | Not properly connected to the server. |
| Action | Connect to the server and retry. |
| Cause | The address of the host variable is NULL. |
| Action | Specify a valid host variable. |
| Cause | The cursor to be used is not declared. |
| Action | Declare the cursor first. |
| Cause | Closed cursors cannot be closed again in ANSI mode. |
| Action | Make sure that the specified cursor isn't already closed. |
| Cause | Opened cursors cannot be opened again in ANSI mode. |
| Action | Make sure that the specified cursor isn't already open. |
| Cause | Invalid parameter type. |
| Action | Verify that the parameter type is correct. |
| Cause | Invalid connection string. |
| Action | Verify that the connection string is correct. |
| Cause | Invalid use of output parameter. |
| Action | Check the output parameter. |
| Cause | Invalid use of input parameter. |
| Action | Check the input parameter. |
| Cause | A cursor name was not specified. |
| Action | Specify the cursor name. |
| Cause | The prepared statement name is unspecified. |
| Action | Specify the name of the prepared statement. |
| Cause | The database name is unspecified. |
| Action | Specify the name of the database. |
| Cause | The length of database name is 0. |
| Action | Specify a DB name. |
| Cause | The prepared statement that was used is not defined.. |
| Action | Verify that the name of the prepared statement is correct. |
| Cause | Describe input for descriptor has not been performed. |
| Action | Perform describe input first. |
| Cause | The SQLDA variable that was used is not defined. |
| Action | Define the SQLDA variable first. |
| Cause | The connection opened with the database name does not exist. |
| Action | Make a connection first. |
| Cause | The specified database connection is closed. |
| Action | Try to reconnect. |
| Cause | This cursor is not defined for the specified database. |
| Action | Specify the correct database name. |
| Cause | The number of output parameters does not match the number of output columns. |
| Action | Ensure that the quantities match. |
| Cause | The number of bind variables does not match the number of parameters. |
| Action | Ensure that the quantities match. |
| Cause | The indicator variable was not specified in the INTO clause. |
| Action | Specify the indicator variable for the INTO clause. |
| Cause | Too many rows were returned by a select statement. |
| Action | Ensure that the expected number of rows does not violate any constraints. |
| Cause | The result does not match the given charmap. |
| Action | Make sure the result value is not null or an invalid value. |
| Cause | The statement has been executed in wrong sequence. |
| Action | Execute ESQL statements according to the fetch execution sequence. |
| Cause | The descriptor name already exists. |
| Action | Use another name for the descriptor. |
| Cause | The descriptor has not been assigned. |
| Action | Assign the descriptor first. |
| Cause | An attempt was made to use an undefined descriptor. |
| Action | Verify that the name of the descriptor is correct. |
| Cause | An attempt was made to use a host structure for embedded PSM or dynamic SQL. |
| Action | Use a general variable type, not a structure. |
| Cause | The file to be included does not exist. |
| Action | Specify a valid file path with the INCLUDE option. |
| Cause | This option cannot be used for this host language. |
| Action | Check the locations where this option can be used (config file, command line, etc.). |
| Cause | Invalid COBOL syntax. |
| Action | Verify that the COBOL syntax is correct. |
| Cause | Preprocessing of COBOL language failed. |
| Action | Locate the cause of the failure and fix it. |
| Cause | Invalid argument. |
| Action | Check the help file for the Precompile utility. |
| Cause | An invalid header file has been included. |
| Action | Verify that the header file is correct. |
| Cause | An attempt was made to use \'defined\' as a macro name. |
| Action | Change the macro name. |
| Cause | A macro name was not specified in #%1$s directive. |
| Action | Modify the macro. |
| Cause | The macro name is inappropriate. |
| Action | Modify the macro to follow the syntax of C programming language. |
| Cause | #%1$s syntax is invalid. |
| Action | Use #%1$s "file name" or #%1$s <file name>. |
| Cause | The #include file is recursive. |
| Action | Check the #include files and fix the recursion problem. |
| Cause | The #%1$s directive is invalid. |
| Action | Modify the #%1$s directive. |
| Cause | The #pragma GCC poison directive is invalid. |
| Action | Modify the #pragma GCC poison directive. |
| Cause | The pragma is invalid. |
| Action | Modify the pragma syntax. |
| Cause | The syntax of the conditional clause (IF-ELSE-ENDIF) is invalid. |
| Action | Correct the clause syntax. |
| Cause | The #%1$s directive is non-terminated. |
| Action | Fix the directive syntax. |
| Cause | Predicate syntax used in #assert and #unassert is invalid. |
| Action | Modify the syntax. |
| Cause | Cannot paste the two specified tokens together. |
| Action | Modify the setting syntax. |
| Cause | The \'%1$s\' macro accepts %2$u arguments, but %3$u arguments were specified. |
| Action | Modify the clause with the \'%1$s\' macro. |
| Cause | One or more arguments of the \'%1$s\' macro are not terminated. |
| Action | Modify the setting syntax. |
| Cause | The \'%1$s\' parameter of the macro is specified twice. |
| Action | Delete one of the duplicate parameters. |
| Cause | \'%1$s\' is not in the macro parameter list. |
| Action | Verify that the parameter name is correct. |
| Cause | Macro parameter syntax is invalid. |
| Action | Correct the macro parameter syntax. |
| Cause | # token is not in the macro parameter list. |
| Action | Modify the setting syntax. |
| Cause | The syntax of the part using the \'##\' operator is bad. |
| Action | Modify the setting to meet the syntax. |
| Cause | The conditional expression contains division by 0 error. |
| Action | Modify the conditional expression. |
| Cause | The \'defined\' operator uses invalid syntax. |
| Action | Modify the syntax used with the operator. |
| Cause | Unable to open the \'%1$s\' file. |
| Action | Specify a valid file path. |
| Cause | The length of the given VARCHAR is invalid. |
| Action | Change the length of the VARCHAR. |
| Cause | A REF clause may not be used here. |
| Action | Delete the invalid REF clause. |
| Cause | No file to copy or include. |
| Action | Specify a valid file to copy or include with the INCLUDE option. |
| Cause | The continued line does not follow COBOL programming language syntax. |
| Action | Locate out the cause of the error and fix it. |
| Cause | This type of host variable is not supported. |
| Action | Find out the cause of the failure, and modify the part having the problem in the message. |
| Cause | Indicator variable must be int type because IND_TYPE is 32bit. |
| Action | Declare indicator variable as int type. |
| Cause | Invalid character. |
| Action | Check that the character is placed in the correct location. |
| Cause | Invalid host variable. |
| Action | Check that the variable is placed in the correct location. |
| Cause | A host variable of external data type 5 was not terminated with a NULL character. |
| Action | Add NULL to the end of the character string. |
| Cause | Invalid iteration count. |
| Action | Iteration count must contain an integer value of 1 or greater. |
| Cause | Invalid parameter data length (dynamic method 4) |
| Action | Set the variable length to a correct value. |
| Cause | Failed to check semantics with the server due to communication problems. |
| Action | Check the communication status with server. |
| Cause | ESQL configuration has not yet been performed. |
| Action | Execute the 'gen_esql_cfg.sh' file from the 'client/config' directory under the database home directory. |
| Cause | Invalid EXEC SQL INCLUDE statement. |
| Action | Modify the syntax of the EXEC SQL INCLUDE statement. |
| Cause | Invalid parameter data type (dynamic method 4) |
| Action | Check whether the variable type is valid. |
| Cause | Invalid type of bind variable (ANSI type dynamic SQL method 4). |
| Action | Verify that the bind variable type is valid. |
| Cause | The expression used in PREPARE was previously declared to use a particular database connection. |
| Action | Do not use an AT clause, or modify the DECLARE clause. |
| Cause | An ESQL statement is used in an included header file. |
| Action | To use an ESQL statement, use an EXEC SQL INCLUDE statement. |
| Cause | Not authorized to access this directory. |
| Action | Receive authorization to open the directory. |
| Cause | The path after #include does not specify a valid directory. |
| Action | Specify a valid directory. |
| Cause | The precision or scale of the declared type is out of range. |
| Action | Check the precision or scale, and enter a value that is within range. |
| Cause | The SQL is not DML. |
| Action | Check the SQL. |
| Cause | The SQL is DDL. |
| Action | Check the SQL. |
| Cause | The SQL is PSM. |
| Action | Check the SQL. |
| Cause | The size of log file is too large or too small. |
| Action | Check the esql config file, enter a value that is within the range(>= 1M and <= 1G). |
| Cause | The lengths in the host variable and in the length field do not match. |
| Action | Check the code and fix the length field of SQLDA or the length in the host variable(VARCHAR or other type). |
| Cause | The number of bind variables does not match the number of attributes. |
| Action | Check the numbers of bind variables and attributes. |
| Cause | Output file name is same with Input file name. |
| Action | Verify that the output file name is different from input file name. |
| Cause | Two or more output files were specified. |
| Action | Specify only one output file. |
| Cause | Ambiguous variable \'%1$s\' is referenced. |
| Action | Check the host variable. |
| Cause | Database name must be less than 128 bytes. |
| Action | Reduce the size of the database name. |
| Cause | The dynamic SQL statement must not be a query (SELECT statement). |
| Action | Use a dynamic SQL method 3, 4 or modify the dynamic SQL. |
| Cause | The number of struct indicator members is different from the number of struct host variable members. |
| Action | Check the number of struct indicator members. |
| Cause | Invalid PL/1 syntax. |
| Action | Verify that the PL/1 syntax is correct. |
| Cause | Database was not installed successfully. |
| Action | Execute the install batch file in the bin directory of the Database Home. |