71 PCC-00001 to PCC-01515

Cause: The precompiler was unable to open a temporary file for internal use. There might be insufficient disk space, too many open files, or read-only protection on the output directory.

Cause: There is a syntax error in an EXEC statement or the statement is not properly terminated.

Cause: The symbol in a conditional precompilation statement (such as EXEC ORACLE IFDEF) is invalid, or the name of a SQL descriptor, statement, or cursor is invalid or was not properly declared.

Cause: There is an EXEC ORACLE ELSE or EXEC ORACLE ENDIF statement without a matching EXEC ORACLE IFDEF statement.

Cause: A host variable defined in the Declare Section has an unsupported datatype or has a scale or precision outside the supported range.

Cause: A condition other than SQLERROR, SQLWARNING, or NOT FOUND was specified in an EXEC SQL WHENEVER statement, or one of these was used, but spelled incorrectly.

Cause: At lease one of the following:

o An action other than CONTINUE, DO, GOTO, or STOP was specified in an EXEC SQL WHENEVER statement.

o One of the specified actions was spelled incorrectly.

o The host language does not allow the action (STOP is illegal in Pro*Pascal programs).

o A GOTO label is invalid.

Cause: A host variable used in an EXEC SQL statement was not declared in the Declare Section or has an unsupported datatype.

Cause: An EXEC statement was not placed properly in the host program. For example, there might be a data manipulation statement in the Declare Section. In a Pro*COBOL program, the Declare Section might be outside the WORKING-STORAGE or LINKAGE SECTION.

Cause: A BEGIN DECLARE SECTION statement was found inside a Declare Section.

Cause: An END DECLARE SECTION statement without a matching BEGIN DECLARE SECTION statement was found. Either the BEGIN DECLARE SECTION statement is missing or misspelled or the END DECLARE SECTION statement is an extra.

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 name of a descriptor, statement, or cursor was not declared or is misspelled.

Cause: The host language syntax used to define a host variable in the Declare Section is incorrect.

Cause: The syntax in a SQL statement is faulty. The precompiler was expecting a host variable, but found something else.

Cause: There is a syntax error in an array declaration. The precompiler was expecting a right bracket (]) but found something else.

Cause: The syntax in a SQL statement is faulty. The precompiler found an unexpected or illegal token.

Cause: The precompiler was unable to find information about an input host variable (bind variable) used in a SQL statement.

Cause: The precompiler was unable to find information about an output host variable (define variable) used in a SQL statement.

Cause: An Oracle error occurred.

Cause: The precompiler process ran out of memory.

Cause: An Oracle connection error occurred while the precompiler was trying to log off, probably because ORACLE has been shut down.

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 indicator variable used in a SQL statement was not declared in the Declare Section or its name is misspelled.

Cause: A host variable used in a SQL statement was not declared properly. Some possible causes follow:

o It was not declared in the Declare Section.

o Its datatype is not supported.

o Its name is misspelled.

o It is a COBOL group item; in Pro*COBOL, only elementary items are allowed in a SQL statement.

Cause: The name of a SQL descriptor, statement, or cursor was re-declared (that is, declared twice)

Cause: A precompiler option was specified inline in an EXEC ORACLE statement. Some options can be specified only on the command line. For example, INAME cannot be specified inline.

Cause: The name of a precompiler option was abbreviated ambiguously. For example, MAX= might refer to MAXLITERAL or MAXOPENCURSORS.

Cause: The value specified for a precompiler option is invalid, probably because the value is misspelled (as in LTYPE=HORT) or out of range (as in PAGELEN=-55).

Cause: The precompiler found an invalid precompiler option name. Some possible causes follow:

o The option name is misspelled.

o The specified option does not exist.

o The equal sign (=) between the option name and value is missing or has space around it.

Cause: No value was specified for a precompiler option. Either the value is missing or there is space around the equal sign (as in LTYPE =SHORT).

Cause: The input file was not specified on the command line.

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: This is an internal error message not usually issued.

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 precompiler was unable to open the listing 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 listing 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: 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: The size of an array variable in an INTO/USING clause is too small for the number of rows processed.

Cause: There is a misplaced clause at the end of an EXEC SQL statement (an AT clause at the end of a SELECT statement, for example), or the

Cause: A string constant is missing an ending quotation mark, or a comment is missing an ending delimiter.

Cause: The precompiler was unable to generate a descriptor for the compilation unit. This can occur from either of the following:

o A non-existent or improperly implemented Declare Section

o Undetected syntax errors near the beginning of the source file or just before the END DECLARE SECTION statement

Cause: The declared size of a VARCHAR host variable exceeds the precompiler limit of 65533 bytes.

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 precompiler expected to find a statement terminator at the end of an EXEC statement but found something else. This can happen if tabs were embedded in the source code (because the precompiler has no way of knowing how many spaces a tab represents).

Cause: A host array was used as a bind (input) variable in the WHERE clause of a SELECT statement. This is not allowed.

Cause: A FOR clause was used with a SELECT statement. This is not allowed as data returned from the last loop in the execution of the SELECT overwrites data returned in a previous loop.

Cause: Two AT clauses, one in a DECLARE STATEMENT statement, the other in a DECLARE CURSOR statement, pertain to the same SQL statement. The AT clause may be specified with either DECLARE STATEMENT or DECLARE CURSOR, but not with both.

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

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 precompiler encountered an end-of-file while parsing a PL/SQL block.

Cause: Two or more occurrences of a host variable in an EXEC SQL statement were associated with different indicator variables. This is not allowed.

Cause: The SQLCHECK=SEMANTICS option was specified, but the USERID option on the command line was not specified.

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

Cause: While reading the input file, the precompiler found a line longer than IRECLEN.

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 variable had an unsupported datatype. For a list of supported datatypes, see the language-specific supplement to the Programmer's Guide to the Oracle Precompilers.

Cause: The precompiler found a syntax error while parsing a number coded in scientific notation. The precompiler expected to find a signed integer following the exponentiation indicator (E), but found something else.

Cause: The precompiler was unable to open the message file containing the messages that can be issued by the precompiler. This can happen if there are too many open files or if there were problems with installation of the precompiler.

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

Cause: A cursor was DECLAREd but was not referenced in an OPEN statement. This is only an informational message.

Cause: An indicator variable was not prefixed with a colon, as required.

Cause: This message is issued only by Pro*COBOL. DISPLAY SIGN LEADING SEPARATE is the only DISPLAY type supported by Pro*COBOL.

Cause: An Oracle extenstion to the ANSI/ISO SQL standard was used. Specifically, a numeric WHENEVER ... GOTO label was prefixed with a colon. For exammple the code might have looked like EXEC SQL WHENEVER SQLERROR GOTO :99; 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 name given to a host variable:

o is longer than 18 characters,

o does not begin with a letter, or

o contains consecutive or trailing underscores. In the following Pro*C example, the host variable name is 19 characters long and therefore non-compliant: EXEC SQL BEGIN DECLARE SECTION; int department_location: -- not ANSI/ISO compliant EXEC SQL END DECLARE SECTION; 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 alphanumeric WHENEVER ... GOTO label was not prefixed with a colon. For example the offending code might look like: EXEC SSQL WHENEVER NOT FOUND GOTO no_more; This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: The identifier being TYPEd in an EXEC SQLY TYPE statement appeared in a previous EXEC SQL TYPE statement. A given identifier can appear in only one EXEC SQL TYPE statement.

Cause: The Oracle external datatype referenced in an EXEC SQL VAR or EXEC SQL TYPE statement does no allow a scale specification.

Cause: A floating point number or a non-number to specify a length or scale was used. Only integers can be used.

Cause: Host variables cannot appear in a CREATE statement. If the makeup of a CREATE statement cannot be known until run time, a dynamic SQL statement must be used to execute it. That is, the program must accept or build the CREATE statement at run time, store it in a host string, then EXECUTE it.

Cause: The precompiler was unable to write to the named output file. Some possible causes follow:

o Sufficient file access privileges were not defined.

o Another user has locked the file.

o There is not enough disk space.

o There are too many open files.

Cause: The source file specified on the command line contains no code. Consequently, there is nothing for the precompiler to process.

Cause: An EXEC SQL TYPE statement was used with a host language that does not support user-defined datatype equivalencing. This feature is available only in Pro*C and Pro*Pascal.

Cause: The user-defined datatype name in an EXEC SQL TYPE statement is missing or misspelled, is a reserved word, is not a legal identifier in the host-language or conflicts with a base datatype in that language.

Cause: The Oracle external datatype name in an EXE SQL TYPE or EXEC SQL VAR statement is missing or misspelled.

Cause: A precision and/or scale specification for the Oracle external datatype DECIMAL in an EXEC SQL TYPE or EXEC SQL VAR statement was omitted.

Cause: A length, precision, and/or scale specification for an Oracle external datatype in an EXEC SQL TYPE or EXEC SQL VAR statement was omitted.

Cause: An invalid length or scale for an Oracle external datatype in an EXEC SQL TYPE or EXEC SQL VAR statement was specified.

Cause: The precompiler found an option available in a prior version or different host language but not in the current version or host language.

Cause: When MODE={ANSI | ANSI14}, a length of less than 2 characters for a char[n] host variable was specified or a simple char variable was specified. When MODE={ANSI | ANSI14}, the length must be at least 2 characters. This message is issued only by the Pro*C precompiler.

Cause: FORTRAN source files are expected to have at least one PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA statement, which the precompiler uses to detect the beginning of a routine or compilation unit.

Cause: When MODE=ANSI14, an array SELECT or FETCH was attempted. However, array operations are not allowed with MODE=ANSI14.

Cause: The DECIMAL and DISPLAY external datatype was used in an EXEC SQL VAR or EXEC SQL TYPE statement with an Oracle precompiler other than Pro*COBOL or PRO*PL/I. These external datatypes are available only in Pro*COBOL and PRO*PL/I.

Cause: In a Pro*C, Pro*FORTRAN, Pro*Pascal program, scale in an EXEC SQL TYPE or EXEC SQL VAR statement in the current context cannot be specified.

Cause: A length for the ROWID, DATE, or MLSLABEL external datatype was specified in an EXEC SQL TYPE or EXEC SQL VAR statement. This is unnecessary because those are fixed length types.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a non-integer WHENEVER ... GOTO label was in a Pro*Pascal program. For example, the offending code might look like: EXEC SQL WHENEVER NOT FOUND GOTO quit; This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: A Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a lowercase 'e' was used in scientific notation. For example, the offending code might look like: maxnum = 10e38; 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 UPDATE OF clause was used in a cursor declaration. For example, the offending code might look like: EXEC SQL DECLARE emp_cursor CURSOR FOR SELECT ENAME, SAL FROM EMP WHERE DEPTNO = :dept_number FOR UPDATE OF SAL; 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; 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 array-processing SQL statement. For example, the offending code might look like: EXEC SQL FOR :limit INSERT INTO EMP (EMPNO, JOB, DEPTNO) VALUES (:emp_number, :job_title, :dept_number); 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 keyword WORK was used in a COMMIT or ROLLBACK statement. For example, the offending code might look like: EXEC SQL COMMIT WORK RELEASE; 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 was used in a COMMIT or ROLLBACK statement. For example, the offending code might look like: EXEC SQL ROLLBACK RELEASE; 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 :password; 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_statement FROM :sql_string; 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; This informational message is issued by the FIPS Flagger when FIPS=YES.

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.

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 VARCHAR username[20]; EXEC SQL END DECLARE SECTION This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: When MODE={ANSI14 | ANSI13}, DBMS=V7 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: In an EXEC SQL VAR statement, a VARCHAR or VARRAW external datatype was specified without a length. Unlike other types, the maximum length of the data field must be specified for VARCHAR and VARRAW.

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

Cause: The same host array was specified in two different ARRAYLEN statements. A given host array cannot be specified in more than one ARRAYLEN statement.

Cause: A valid array dimension was not specified in an ARRAYLEN statement. The array 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 ename_array (25); -- illegal dimension

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a host variable was initialized in its declaration, as shown in the following Pro*C example: EXEC SQL BEGIN DECLARE SECTION; int dept_number = 20; -- not ANSI/ISO-compliant EXEC SQL END DECLARE SECTION; This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: A variable declared with the type specifier "const" was used in an INTO clause. Such variables should not be modified and should not be used in an INTO clause.

Cause: d by insufficient disk space.

Cause: An array of pointers was declared, which is not allowed. However, pointers to scalar types are allowed. With Pro*C, declare pointers to char[n] and varchar[n] variables as pointers to CHAR or VARCHAR (with no length specification).

Cause: On the command line, the same pathname for INAME and ONAME was specified, which designates the precompiler input and output files, respectively.

Cause: In a Pro*C program, a VARCHAR declaration spans more than one line, which is not allowed.

Cause: In a FORTRAN program, subroutine, or function, the precompiler option COMMON_NAME was mistakenly specified after the PROGRAM, SUBROUTINE, or FUNCTION statement. If COMMON_NAME is specified inline, its EXEC ORACLE OPTION statement must precede the PROGRAM SUBROUTINE, or FUNCTION statement.

Cause: The precompiler was unable to find or open the system configuration file (a text file containing preset command-line options, which the precompiler uses by default). Some possible causes follow:

o The file does not exist.

o The search path to the file is incorrect.

o File access privileges are insufficient.

o There are too many open files. However, this message is just a warning. Processing continues even if the system configuration file does not exist.

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

Cause: The command line processor encountered a severe error.

Cause: A required command-line option is missing. For example, the INAME option, which specifies the name of the input file, might be missing.

Cause: An host variable array was used with an indicator array declared with a smaller dimension. For example: EXEC SQL BEGIN DECLARE SECTION; int dept_no[20]; short dept_no_ind[10]; EXEC SQL END DECLARE SECTION; ... SELECT ... INTO dept_no:dept_no_ind ...

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: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, an Oracle Result Set Cursor has been used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: An array of SQL_CURSOR host variables was declared or, if Pro*COBOL, a PICTURE clause was specified in the SQL-CURSOR declaration. In Pro*FORTRAN, a length specification (i.e. "*n") on the SQL_CURSOR declaration could have been specified. These usages are not supported.

Cause: A SQL_CURSOR variable was used in an INTO or WHERE clause. SQL_CURSOR variables can be used only where ordinary cursor identifiers would be used or, in a PL/SQL block, where a cursor would normally be used.

Cause: There was an attempt to reference a host variable as a cursor reference. Cursor variables are not implemented in PRO*Pascal or Pro*PL/I.

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: 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 These statements are Oracle extensions to the ANSI/ISO SQL standards. This informational message is issued by the FIPS Flagger when FIPS=YES.

Cause: There has been an attempt to use CONTEXT sql statements. The thread safety feature is not implemented in PRO*Pascal, Pro*PL/I, or Pro*C 1.x.

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

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

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: EXEC SQL ENABLE THREADS or one of the EXEC SQL CONTEXT statements has been used, even though option THREADS is set to NO.

Cause: An invalid host language was specified using the command-line host option. The host option valid values are pro* language specific. For example, for profor, the only valid value is FORTRAN. For procob, the only valid values are COBOL and COB74.

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

Cause: The authorization or license to run the Pro*COBOL Precompiler has expired.

Cause: The authorization or license to run the Pro*COBOL Precompiler is about to expire.

Cause: In a Pro*COBOL Precompiler program, only a blank, hyphen (-), asterisk (*), slash (/), or letter "D" is allowed in the indicator area, but the precompiler found another character.

Cause: In a PRO*COBOL program, a continuation line was completely blank, except for the continuation character.

Cause: In a Pro*COBOL input file, the last EXEC statement was not terminated properly.

Cause: The precompiler could not find the PROCEDURE DIVISION header in a Pro*COBOL program. Some possible causes follow:

o A keyword in the header is missing or misspelled.

o There is an apostrophe in the REMARKS section (the precompiler mistook the apostrophe for the beginning of a string literal).

o There is an unterminated literal in the WORKING-STORAGE SECTION.

o The wrong value for the FORMAT option was specified.

Cause: In a Pro*COBOL program, EXEC statements must begin in Area B, but the precompiler found a statement beginning in Area A.

Cause: The precompiler could not find the WORKING-STORAGE SECTION header in a Pro*COBOL program, probably because a keyword is missing or misspelled, or the wrong value for the FORMAT option might have been specified.

Cause: A few COBOL compilers do not allow group items to be passed as parameters in a CALL statement. (Check the COBOL compiler user's guide.) If the compiler is one of these, group items within the Declare Section can contain only one elementary item.

Cause: In a Pro*COBOL program, an EXEC SQL statement is followed by another statement in the same sentence. An EXEC SQL statement must be the last statement in a COBOL-74 sentence and so must be terminated by the keyword ELSE or a period.

Cause: A null character (binary zero) was found in a string literal. This is not allowed by Pro*COBOL.

Cause: The period terminating the USAGE IS BINARY clause must be on the same line as the USAGE clause. This message only occurs on systems that support the COMP5=YES command line option of Pro*COBOL, where where COMP-5 is substituted for BINARY.

Cause: The Pro*COBOL precompiler did not find a DATA DIVISION in the input source file. Pro*COBOL applications are required to have a DATA DIVISION.

Cause: A PIC N variable was declared using an OCCURS clause. Tables of PIC N variables are not supported by the Pro*COBOL precompiler.

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

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

Cause: An "N" character literal was used within a PL/SQL block

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 CONVBUFSZ clause has been used in an EXEC SQL VAR statement where the variable is not of a character datatype.

Cause: The size specified in a CONVBUFSZ clause must be an integer in the range 1-32765. Either the size given is not an integer or is outside the required range.

Cause: The authorization or license to run the Pro*FORTRAN Precompiler has expired.

Cause: The authorization or license to run the Pro*FORTRAN Precompiler is about to expire.

Cause: The Pro*FORTRAN Precompiler found an invalid FORTRAN statement label in columns 1 through 6.

Cause: The authorization or license to run the Pro*C Precompiler has expired.

Cause: The authorization or license to run the Pro*C Precompiler is about to expire.

Cause: A host identifier (the name of a host variable, for example) was truncated to the maximum length (31 characters) allowed by the precompiler.

Cause: The authorization or license to run the Pro*PL/I Precompiler has expired.

Cause: The authorization or license to run the Pro*PL/I Precompiler is about to expire.

Cause: The authorization or license to run the Pro*Pascal Precompiler has expired.

Cause: The authorization or license to run the Pro*Pascal Precompiler is about to expire.

Cause: The authorization or license to run the Pro*Ada Precompiler has expired.

Cause: The authorization or license to run the Pro*Ada Precompiler is about to expire.

Cause: Every Ada source file must have a package, procedure, or function statement. The precompiler did not find one.

Cause: An identifier used in the host program is of a length that causes precompiler-generated code to exceed the length limitation on source lines.

Cause: The EXEC SQL INCLUDE statement is not allowed in Pro*Ada.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a host variable was declared with a non-ANSI/ISO standard type.

Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, a host variable was declared outside of a Declare Section.