55 PCB-00001 to PCB-00903

Cause: This is a generic error message from the command-line processor.

Cause: The command line processor encountered a severe error.

Cause: When MODE={ANSI14 | ANSI13}, DBMS=V7 or V8 was specified, or when MODE=ANSI, DBMS=v6 was specified. These option settings are incompatible. Note that the DBMS option was not available before release 1.5 of the Oracle Precompilers.

Cause: The option UNSAFE_NULL=YES has been used with DBMS=V6 or DBMS=NATIVE (the default) or has been used with MODE=ANSI/ANSI14/ANSI13.

Cause: The precompiler option NLS_LOCAL=YES was used without also specifying MODE=ANSI. The precompiler option MODE=ANSI must be specifiied if NLS_LOCAL=YES.

Cause: The USERID option was specified when SQLCHECK={SYNTAX | NONE}. This is unnecessary.

Cause: This is a generic error message from the command-line processor.

Cause: The precompiler tried to parse an embedded PL/SQL block when SQLCHECK={SYNTAX | NONE}. PL/SQL blocks can be parsed only when SQLCHECK=SEMANTICS is specified.

Cause: The MAXLITERAL option has been used in an inline EXEC ORACLE OPTION statement after and EXEC SQL, EXEC TOOLS, or EXEC IAF statement. This is not allowed.

Cause: The SQLCHECK option was entered inline and specified a level of checking higher than the level specified (or accepted by default) on the command line. This is not allowed. For example, if SQLCHECK={SYNTAX | LIMITED} is specified on the command line, SQLCHECK={SEMANTICS | FULL} cannot be specified inline. This informational message is; the precompiler ignores the inline value and continues processing.

Cause: V6 compatibility is no longer supported. The precompiler will precompile as though DBMS=NATIVE was specified.

Cause: The precompiler option TYPE_CODE=ANSI was used without also specifying DYNAMIC=ANSI. The precompiler option DYNAMIC=ANSI must be specifiied if TYPE_CODE=ANSI.

Cause: The precompiler was unable to reopen a temporary file. Some possible causes follow:

o File access privileges are insufficient.

o Another user has locked the file.

o There is not enough disk space.

o There are too many open files.

Cause: The precompiler was unable to open the system configuration file. The system configuration file does not exist or is not in the proper directory.

Cause: The file name length specified exceeded the maximum length. Some operating systems have a maximum file name length.

Cause: The precompiler was unable to open the input file specified by the INAME precompiler option. Some possible causes follow:

o The filename is misspelled.

o The file does not exist.

o The search path to the file is incorrect.

o File access privileges are insufficient.

o Another user has locked the file.

o There is not enough disk space.

o There are too many open files.

Cause: The file name length specified exceeded the maximum length. Some operating systems have a maximum file name length.

Cause: The precompiler was unable to open the input file specified in the INCLUDE statement. Some possible causes follow:

o The filename is misspelled.

o The file does not exist.

o The search path to the file is incorrect.

o File access privileges are insufficient.

o There is not enough disk space.

o There are too many open files.

Cause: The precompiler was unable to open the list file specified by the LNAME precompiler option. Some possible causes follow:

o The filename is misspelled.

o The file does not exist.

o The search path to the file is incorrect.

o File acces privileges are insufficient.

o Another user has locked the file.

o There is not enough disk space.

o There are too many open files.

Cause: The precompiler was unable to open the output file specified by the ONAME precompiler option. Some possible causes follow:

o The filename is misspelled.

o The file does not exist.

o The search path to the file is incorrect.

o File acces privileges are insufficient.

o Another user has locked the file.

o There is not enough disk space.

o There are too many open files.

Cause: The precompiler was unable to open a file for temporary use. Some possible causes follow:

o File acces privileges are insufficient.

o A file of the same name already exists and is locked.

o There is not enough disk space.

o There are too many open files.

Cause: A PIC N/G variable, an implicit VARCHAR group item with a PIC N/G elementary item, or a group item with a PIC N/G elementary item was used in an EXEC SQL VAR statement. This is not allowed.

Cause: The host variable is a group item containing tables. Indicator variables used with this type of host variable must be group items of tables of indicators corresponding the the tables in the group item host variable.

Cause: The host variable is a group item. Indicator variables used with this type of host variable must be a group item or table of indicator variables.

Cause: The variable used as a host variable was a group item which itself contained other group items.

Cause: A group item host variable was used outside of an INTO or VALUES clause. A group item host variable may be used only in an INTO or VALUES clause.

Cause: A PIC N or PIC G variable was used in an embedded PL/SQL block when the precompiler option NLS_LOCAL=YES was used. A PIC N or PIC G variable is not supported in this situation.

Cause: A "N" literal (a literal of the form N"...") was used within a PL/SQL block when the precompiler option NLS_LOCAL=YES was used. N literals are not supported in this situation.

Cause: A PIC N variable was declared using an OCCURS clause. Tables of PIC N variables are not supported when NLS_LOCAL=YES.

Cause: A variable of unsupported datatype was used in a SQL statement or embedded PL/SQL block.

Cause: A variable whose format does not support scaling was used in a SQL statement or embedded PL/SQL block. The following formats do not support scaling: PIC S9(n) COMP PIC S9(n) COMP-4 PIC S9(n) COMP-5 PIC S9(n) BINARY PIC 9(n) COMP

Cause: A variable declared with DISPLAY-1 in the usage clause without PIC G or PIC N in the picture clause was used in a SQL statement.

Cause: The keyword VARYING was used in a PIC N variable declaration.

Cause: A variable declared with a PIC clause and COMP-1 or COMP-2 was used in a SQL statement or embedded PL/SQL block.

Cause: A variable declared with a JUSTIFIED clause was used in a SQL statement or embedded PL/SQL block.

Cause: A variable declared with an OCCURS clause with the TO TIMES subclause was used in a SQL statement or embedded PL/SQL block.

Cause: A variable declared with an OCCURS clause with the ASCENDING or DESCENDING KEY IS subclause was used in a SQL statement or embedded PL/SQL block.

Cause: A variable declared with an OCCURS INDEXED clause was used in a SQL statement or embedded PL/SQL block.

Cause: A variable declared with a RENAMES clause was used in a SQL statement or embedded PL/SQL block.

Cause: A size which is specified which is not valid for the specified data type.

Cause: A scale which is specified which is not valid for the specified data type.

Cause: A variable declared with an OCCURS clause with the DEPENDING ON subclause was used in a SQL statement or embedded PL/SQL block.

Cause: A variable declared with PIC S9(n), with n greater than what is allowed on the given platform, was used in an embedded sql statement. On 32 bit machines n must not exceed 9, and on 64 bit machines, n must not exceed 18.

Cause: A variable used in a SQL statement was not declared or its name is misspelled or if option DECLARE_SECTION=YES the declaration was not in a DECLARE SECTION.

Cause: There is more than one variable of the same name and the qualification given was insufficient to determine which variable the reference was to.

Cause: The name of a descriptor, statement, or cursor was not declared or is misspelled, or was declared as a different kind of SQL identifier.

Cause: The SQL identifier (cursor name, statement name, etc.) has already been defined in another way.

Cause: An indicator variable used in a SQL statement was not declared in the Declare Section or its name is misspelled.

Cause: An unacceptable group item variable was used in a SQL statement. or its name is misspelled.

Cause: An indicator variable was not declared in the Declare Section as a 2-byte integer. Indicator variables must be defined as 2-byte integers.

Cause: An host variable table was used with an indicator table declared with a smaller dimension. For example: EXEC SQL BEGIN DECLARE SECTION END-EXEC. 01 EMP-NUM OCCURS 4 TIMES PIC S9(4) COMP. 01 EMP-NUM-IND OCCURS 2 TIMES PIC S9(4) COMP. EXEC SQL END DECLARE SECTION END-EXEC. ... SELECT ... INTO EMP-NUM:EMP-NUM-IND ...

Cause: In an EXEC SQL statement, an indicator variable had the same name as a host variable. The names of a host variable and its associated indicator variable must be different. Also, an indicator variable cannot be used as a host variable.

Cause: A host table was used in the WHERE clause of a SELECT-INTO statement or in the SELECT list of a SELECT-INTO statement.

Cause: The size of an table variable in an INTO/USING clause is too small for the number of rows processed.

Cause: The count variable in a FOR clause has the wrong datatype. The datatype must be NUMBER or LONG (or be compatible with NUMBER or LONG).

Cause: The size of a table variable in an INTO/USING clause of a dynamic EXECUTE statement has been ARRAYLEN...EXECUTE"d while the other host variable has not and is not a table of dimension 1 or a plain non-table host variable. Example: 01 X PIC X(10) OCCURS 10. 01 Y PIC S9(4) COMP OCCURS 10. 01 Z PIC S9(4) COMP. ... EXEC SQL ARRAYLEN X (DIM) EXECUTE END-EXEC. ... EXEC SQL EXECUTE S1 USING :X, :Y END-EXEC. <-- error EXEC SQL EXECUTE S1 USING :X, :Z END-EXEC. <-- ok Please note that this error differs from 233 in that it is an ERROR not a WARNING.

Cause: To use PIC N or PIC G variables as host variables, both of the environment variables NLS_LANG and NLS_NCHAR must be set with correct values. One of the following problems has occurred which prevents Pro*COBOL from accepting PIC N and PIC G variables as host variables: 1) One or both of NLS_LANG and NLS_NCHAR are not set at all. 2) NLS_LANG is not set with a valid language, territory, or character set. 3) NLS_NCHAR is not set to a valid NCHAR character set. 4) The character set specified by NLS_NCHAR is not a fixed width character set. Pro*COBOL can only use fixed width character sets for PIC N or PIC G host variables.

Cause: A VARYING or SQL-CURSOR declaration has been encountered which has the level number greater than 48.

Cause: A group item that is a table and having an element that is a table was used in a SQL statement.

Cause: A group item that is a table and used as an indicator has an element that is a table or group item.

Cause: An elementary item belonging to a group item with an OCCURS clause has been referenced. This is not allowed.

Cause: The COUNT item in the dynamic SQL statement must be a host variable but is not.

Cause: The particular item in the dynamic SQL statement is required to be a host variable or exact numeric (integer) constant, but is not.

Cause: An Oracle extension to the ANSI/ISO standard was used. Specifically, aa pointer or nonconforming datatype such as VARCHAR was used. For example, the offending code might look like: EXEC SQL BEGIN DECLARE SECTION END-EXEC. 01 USERNAME PIC X(10) VARYING. EXEC SQL END DECLARE SECTION END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a non-ANSI function was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a nonconforming SQL statement such as PREPARE was used. For example, the offending code might look like: EXEC SQL PREPARE SQL-STMT FROM :HV END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, dynamic SQL or embedded PL/SQL was used. For example, the offending code might look like: EXEC SQL EXECUTE BEGIN SELECT ... END; END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a nonconforming keyword such as NOTFOUND, STOP, RAISE, or DO was used in the WHENEVER statement. (Note that NOT FOUND is ANSI-compliant.) For example, the offending code might look like: EXEC SQL WHENEVER SQLERROR STOP END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the parameter RELEASE, COMMENT, or FORCE were used in a COMMIT or ROLLBACK statement. For example, the offending code might look like: EXEC SQL ROLLBACK RELEASE END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, one of the following statements was used:

o CREATE FUNCTION

o CREATE PROCEDURE

o CREATE PACKAGE

o CREATE TRIGGER This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the DROP TABLE statement was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the FOR clause was used in an table-processing SQL statement. For example, the offending code might look like: EXEC SQL FOR :LIMIT INSERT INTO EMP (EMPNO, JOB, DEPTNO) VALUES (:EMPNUM, :JOB, :DEPTNO) END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the CONNECT statement was used to log on to ORACLE. For example, the offending code might look like: EXEC SQL CONNECT :USERNAME IDENTIFIED BY :PSSWORD END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the AT <db_name> clause was used in a SQL statement. For example, the offending code might look like: EXEC SQL AT oracle3 COMMIT RELEASE END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the EXEC SQL VAR statement was used.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the keyword WORK was used in a COMMIT or ROLLBACK statement. For example, the offending code might look like: EXEC SQL COMMIT WORK RELEASE END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the TO SAVEPOINT <save_id> clause was used in a ROLLBACK statement.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the DECLARE DATABASE statement was used.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the DECLARE TABLE statement was used.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the one of the following statements was used:

o EXEC IAF GET

o EXEC IAF PUT

o EXEC TOOLS GET

o EXEC TOOLS SET This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a group item variable was used as a host variable. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the ARRAYLEN statement was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, an EXEC ORACLE statement was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a variable declared of VARYING type was used in a SQL statement. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, an iimplicit varchar variable was used in a SQL statement. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, an EXEC SQL LOB statement was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: A syntax error was found.

Cause: The character string was not terminated with a quote or apostrophe as appropriate or line continuation was not correct.

Cause: A block of pseudo-text has not been properly terminated with "==".

Cause: An EXEC statement began in Area A (before column 12).

Cause: A syntax error was found.

Cause: No EXEC SQL CONTEXT USE statement was encountered and the option threads=yes was requested.

Cause: The runtime context variable referenced in an EXEC SQL CONTEXT USE statement is not of type sql_context.

Cause: EXEC SQL ENABLE THREADS has been used, even though option THREADS is set to NO.

Cause: An explicit AT clause was used with an ALLOCATE statement or a FETCH/CLOSE statement also using a sql-cursor declaration.

Cause: The precompiler was unable to log on to ORACLE with the specified username and password. An ORACLE error with given number occurred when the logon was attempted.

Cause: The precompiler has encountered an include SQLCA statement after SQLCA has already been included. The SQLCA can only be included once.

Cause: The SQLCA has been included and a SQLCODE variable has been declared. This is not allowed as references to the SQLCODE variable are ambiguous and will result in COBOL compiler errors.

Cause: A FOR clause was used with a SELECT, LOB, or DEALLOCATE DESCRIPTOR statement. A FOR clause cannot be used with these statements. In the case of a SELECT statement, data returned from the last loop in the execution of the SELECT would overwrite data returned in a previous loop.

Cause: When MODE={ANSI | ANSI14}, an attempt was made to use the WHENEVER SQLWARNING statement without declaring the SQLCA. When MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the WHENEVER SQLWARNING statement, the SQLCA must be declared.

Cause: if mode=ORACLE, then a cursor defined with a WHERE CURRENT OF clause must also have a FOR UPDATE clause.

Cause: A fatal parsing error or token stack overflow error has been encountered.

Cause: A severe semantics error occurred because the USING clause was used with the OPEN cursor statement and the cursor declaration is not for a PREPAREd statement. The correct sequence of statements should be like: EXEC SQL prepare sv from :sel_stmt END-EXEC. EXEC SQL declare csv cursor for sv END-EXEC. EXEC SQL open csv USING :hv1, :hv2 END-EXEC.

Cause: An invalid external datatype was specified in the EXEC SQL VAR statement.

Cause: Refer to the indicated PL/SQL error message for the indicated condition.

Cause: The precompiler found an error in an embedded SQL statement or PL/SQL block.

Cause: ARRAYLEN is only valid with PL/SQL.

Cause: In an ARRAYLEN statement, the name of a previously declared host table was not specified. The first host variable in an ARRAYLEN statement must be a table. The second host variable, which specifies an array dimension, must be a 4-byte integer. The correct syntax follows: EXEC SQL ARRAYLEN HTABLE (DIM) END-EXEC. The ARRAYLEN statement must appear along with, but somewhere after, the declarations of host_table and dimension.

Cause: A valid table dimension was not specified in an ARRAYLEN statement. The table dimension must be specified using a previously declared 4-byte integer host variable, not a literal or expression. For example, the offending code might look like: EXEC SQL ARRAYLEN ETABLE (25) END-EXEC. -- illegal dimension

Cause: Within a PL/SQL statement, a host variable was used with two different indicator variables or was used with an indicator variable in one instance and without an indicator in another instance.

Cause: Within a PL/SQL statement, the variable was used as both a host variable and an indicator variable.

Cause: Indicator variables associated with host variables cannot be used in EXEC IAF statements such as GET and PUT in a user exit.

Cause: If a host variable is used to specify the message in an EXEC TOOLS MESSAGE statement, that host variable must be of a character type.

Cause: In a LOB DESCRIBE, an indicator variable was used with a host variable when retrieving a LOB attribute that does not require one.

Cause: A LOB operation was attempted between LOBs whose types were not compatible. For example, When ASSIGNing one LOB to another, both LOBs must be of the same type. If they are not, this error results.

Cause: The given host variable was not declared to be of the required character type. In this case, one of several possible character types would have been accepted. However, the host variable type did not match any of them.

Cause: This error can occur in either of the following situations

1. An attempt to READ from a LOB into a buffer whose type was not compatible with the LOB type.

2. An attempt to WRITE a buffer into a LOB whose type was not compatible with the buffer type.

Cause: The given host variable was not declared to be an internal LOB. BLOB, CLOB or NCLOB are internal lob types.

Cause: The given host variable was not declared to be any type of LOB, Internal or External. BLOB, CLOB or NCLOB are internal lob types. BFILE is an external type.

Cause: The given host variable was not declared to be an External LOB. BFILE is an external type.

Cause: An attempt was made to OPEN a BFILE in READ WRITE mode. Writable BFILEs are currently not supported so this operation is considered erroneous.

Cause: The host variable and attribute pairing in a LOB DESCRIBE was invalid. Most likely, this was due to some problem with the host variable. For example, this error could occur if the host variable was not declared.

Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given LOB was not of some Internal LOB type.

Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given LOB was not an External LOB type (BFILE).

Cause: A host variable was given that was not declared to be of some acceptable exact binary integer type. Generally, when this error occurs, a signed or unsigned integer type was expected. Floating point or otherwise imprecise numeric types are considered erroneous.

Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given source was not an internal or external LOB type.

Cause: A destination offset was specified in a LOB WRITE APPEND statement. The destination offset is assumed to be the end of the LOB so specifying an explicit destination offset is erroneous.

Cause: One of the following statements was used without specifying DYNAMIC=ANSI:

o EXEC SQL ALLOCATE/DEALLOCATE/GET/SET DESCRIPTOR

o EXEC SQL DESCRIBE OUTPUT/INPUT ... USING ... <descriptor name>

o EXEC SQL EXECUTE ... INTO ...

o EXEC SQL EXECUTE ... USING... <descriptor name>

o EXEC SQL OPEN ... INTO ...

o EXEC SQL OPEN ... USING... <descriptor name>

o SCROLL in DECLARE CURSOR

o EXEC SQL FETCH <orientation> ... where <orientation> is NEXT, PRIOR, FIRST, LAST, ABSOLUTE, or RELATIVE

Cause: The value specified in the WITH MAX clause of an EXEC SQL ALLOCATE DESCRIPTOR statement was less than 1 or greater than 65535

Cause: The value specified in the VALUES clause of an EXEC SQL GET/SET DESCRIPTOR statement was less than one or greater than 65535.

Cause: Pro*COBOL had detected an abnormal condition in its internal data structures. This error message should not normally ever be produced. Customer service should be contacted to report the error.

Cause: Pro*COBOL was unable to access the message file containing message text. The file is possibly corrupt.

Cause: Pro*COBOL was unable to access the message file containing message text. The file is possibly corrupt.