OpenESQL Preprocessor Error Messages

• COBES0002 token is badly defined.
  An error exists in the definition of the SQLCA area, SQLCODE field, or SQLSTATE field.
• COBES0003 Program contains more than one definition of token
  More than one definition exists of one or more of the following fields: SQLCA, SQLCODE, or SQLSTATE.
• COBES0004 Nested or multi-source programs not allowed.
  You are trying to compile a program that is nested or multi-source. This is not supported.
• COBES0005 An error occurred when processing the internal dictionary.
  A system error has occurred trying to read the internal dictionary that the preprocessor creates of all host variables used in the program.
• COBES0006 No DB engine could be found.
  The required OpenESQL system software was not installed.
• COBES0007 Source file name is invalid.
  A system error has occurred. The source file name passed to the preprocessor is not valid.
• COBES0010 OESQL rejected an unspecified option.
  OESQL precompiler services returned a -4905 sql error on initialization.
• COBES0022 The directive SQL(DBMAN=ODBC) is not supported under Personal Edition.
  You are using Studio Enterprise Edition Personal Edition. This Edition does not support ODBC.
• COBES0023 The SQL(DBMAN) directive option is not supported with native applications.
  You have specified the SQL(DBMAN) compiler directive option to compile a native application. This is not supported.
• COBES0100 SQL incompatible with MAINFRAME
  The preprocessor has encountered an embedded SQL statement that is not supported when the BEHAVIOR SQL compiler directive option is set to MAINFRAME.
• COBES0101 Statement is too long.
  The SQL statement passed to the preprocessor is more than 65536 characters long. The preprocessor gets passed a compressed version of the SQL statement rather than the original source, which might have comments included as well as leading and trailing blanks.
• COBES0102 Statement contains too many host variables.
  The SQL statement contains more than 8000 host and indicator variables.
• COBES0103 token does not have a suitable definition to be used as a host variable.
  The host variable displayed in error message is not recognized with a data definition suitable for SQL data types.
• COBES0104 Bad SQL data declaration.
  An unexpected SQL declaration was passed to the preprocessor.
• COBES0105 Syntax error.
  The SQL statement includes invalid syntax or does not include required information.
• COBES0106 Filename too long.
  A filename used in the program to specify a copybook or INCLUDE file is more than 260 characters long.
• COBES0107 File token not found.
  The copybook specified in token was not found.
• COBES0108 token is not unique and should be qualified.
  The host variable displayed in token is not unique.
• COBES0109 token is not a data item.
  The host variable displayed in token was not defined or was defined incorrectly.
• COBES0110 Statement contains more than one SQLDA.
  More than one SQLDA has been used in the SQL statement.
• COBES0111 token is not a table of null indicator variables.
  The preprocessor expects that the token displayed is either a null indicator or a null indicator table.
• COBES0112 token should not be defined with an OCCURS clause.
  A host variable is defined as part of an OCCURS clause.
• COBES0113 token should not be a subordinate to an item defined with an OCCURS clause.
  A host variable is defined as part of an OCCURS clause or as part of a structure that includes an OCCURS clause.
• COBES0114 Statement only allowed in the Procedure Division.
  An SQL statement such as EXEC SQL SELECT was coded in the Working-Storage Section.
• COBES0115 Statement not allowed in the Procedure Division.
  A SQL statement such as EXEC SQL DECLARE TABLE was coded in the Procedure Division
• COBES0116 An error occurred when processing the trace file.
  A file error occurred while trying to write information to the preprocessor trace file.
• COBES0118 Mismatched DECLARE.
  More than one DECLARE statement was found within an EXEC SQL statement.
• COBES0119 Host variable name is too long.
  The host variable name is too long. The maximum length of the host variable is 30 characters.
• COBES0120 Internal error - dictionary handle is too big.
  The preprocessor creates an internal dictionary of all host variables used in a program. When building the dictionary, a system error occurred.
• ES0121 Compiler directive SQL(token1=token2) is invalid or badly sequenced - all SQL statements ignored.
  The command line used to compile the application or program either contains an invalid value for a valid SQL compiler directive option (represented by token2), or the SQL compiler directive option appears in the wrong place.
• COBES0123 Invalid ILTARGET - cannot use ILTARGET(ANYCPU) - must specify ILTARGET(X86) or ILTARGET(X64).
  You have specified the ILTARGET(ANYCPU) compiler directive to compile an ODBC application as .NET managed code.
• COBES0201 BEHAVIOR directive not valid unless TARGETDB directive of DB2, ORACLE, or MSSQLSERVER set first.
  You have set the SQL(BEHAVIOR) compiler directive option, but neglected to also set the SQL(TARGETDB) directive to a value of DB2, ORACLE, or MSSQLSERVER. SQL(BEHAVIOR) is dependent on SQL(TARGETDB).
• COBES0202 BEHAVIOR directive not set.
  You have neglected to set the SQL(BEHAVIOR) compiler directive option, which is required to compile OpenESQL applications.
• COBES0203 PREFETCH and BEHAVIOR directives are mutually exclusive - cannot set both.
  You have set both the SQL(PREFETCH) and SQL(BEHAVIOR) compiler directive options to compile an application. These are mutually exclusive.
• COBES0204 Cannot use PREFETCH directive with TARGETDB=ORACLEOCI directive.
  You have specified the SQL(PREFETCH) compiler directive option and also set the SQL(TARGETDB) compiler directive option to ORACLEOCI. We do not support this combination.
• COBES0205 Cannot set directive PF_RO_CURSOR > 1 if RO_CURSOR directive is set to IC_FH.
  When compiling an application, you have set the PF_RO_CURSOR primitive directive to a value greater than 1 and also set the RO_CURSOR primitive directive to IC_FH. This combination is not supported.
• COBES0206 Cannot set directive PF_RO_CURSOR > 1 if RO_CURSOR directive is set to FORWARD and TARGETDB is MSSQLSERVER.
  When compiling an application, you have set the PF_RO_CURSOR primitive directive to a value greater than 1, set the RO_CURSOR primitive directive to FORWARD, and set the TARGETDB SQL compiler directive option to MSSQLSERVER. This combination is not supported.
• COBES0207 Cannot set directive PF_UPD_CURSOR > 1 if UPD_CURSOR directive is set to FORWARD.
  When compiling an application, you have set the PF_UPD_CURSOR primitive directive to a value greater than 1 and also set the UPD_CURSOR primitive directive to FORWARD. This combination is not supported.
• COBES0208 Cannot set UPD_CURSOR directive to DYNAMIC if TARGETDB directive is set to ORACLE.
  When compiling an application, you have set the UPD_CURSOR primitive directive to DYNAMIC, and also set the TARGETDB SQL compiler directive option to ORACLE. This combination is not supported.
• COBES0209 Cannot set UPD_CURSOR directive to STATIC if TARGETDB directive is set to MSSQLSERVER.
  When compiling an application, you have set the UPD_CURSOR primitive directive to STATIC, and also set the TARGETDB SQL compiler directive option to MSSQLSERVER. This combination is not supported.
• COBES0211 DBRMLIB name is too long, max 44 characters.
  The value specified for the DBRMLIB HCOSS compiler directive option exceeds the maximum length of 44.
• COBES0212 Simple name in DBRMLIB name is too long, max 8 characters.
  The value specified for the DBRMLIB HCOSS compiler directive option includes a simple name that exceeds the maximum length of eight.
• COBES0213 Simple name in DBRMLIB name starts with invalid character.
  The value specified for the DBRMLIB HCOSS compiler directive option includes a simple name that begins with an illegal character.
• COBES0214 Invalid character in DBRMLIB name.
  The value specified for the DBRMLIB HCOSS compiler directive option includes an illegal character.
• COBES0215 MEMBER name is too long, max 8 characters.
  The value specified for the MEMBER HCOSS compiler directive option exceeds the maximum length of eight.
• COBES0216 MEMBER name cannot begin with a numeric digit.
  The value specified for the MEMBER HCOSS compiler directive option begins with a numeric digit, which is not legal.
• COBES0217 Invalid character in MEMBER name.
  The value specified for the MEMBER HCOSS compiler directive option contains an illegal character.
• COBES0218 MEMBER directive not valid unless DBRMLIB directive set.
  You have set the MEMBER HCOSS compiler directive but neglected to also set the DBRMLIB HCOSS compiler directive. MEMBER is dependent on DBRMLIB.
• COBES0219 VERSION directive not valid unless DBRMLIB directive set.
  When compiling an application, you have set the VERSION HCOSS directive without also explicitly setting the DBRMLIB HCOSS directive. The VERSION directive is dependent on the DBRMLIB directive.
• COBES0220 VERSION is too long, max 64 characters.
  The value specified for the VERSION HCOSS compiler directive has exceeded its maximum allowable length of 64 characters.
• COBES0221 Invalid character in VERSION.
  The value specified for the VERSION HCOSS compiler directive contains an invalid character.
• COBES0222 Invalid Framework target - SQL applications must be built to target the 4.0 .NET Framework.
  When compiling an SQL application, you have specified the ILCLR compiler directive value as 2. SQL applications require that the SQL(ILCLR) compiler directive option be set to 4 to target .NET Framework version 4.0.
• COBES0223 TARGETDB directive not set.
  When compiling an SQL application, you have either neglected to set the SQL(TARGETDB) compiler directive option, or you have set it after the BEHAVIOR, ACCESS, BIND, or MARS compiler directive options.
• COBES0900 An internal error occurred.
  An unexpected error occurred in the preprocessor.
• COBES0901 This error prevents SQL processing from continuing - further EXEC SQL statements will be ignored.
  A severe SQL error has occurred. Additional EXEC SQL statements will not be processed by the preprocessor.
• COBES1000W Use of EXEC SQL INCLUDE SQLCA END-EXEC
  FIPS certification (reference X/OPEN CAE SQL 8.1.1) requires that this warning be generated.
• COBES1002 Statement is not in area B.
  An EXEC SQL statement starts before column 12.
• COBES1004 token directive is not supported and has been ignored.
  The compiler directive token is not supported when compiling SQL applications.

Parent topic: OpenESQL Messages

---

---