PCC-00091: TYPE statement requires format specification for this Oracle datatype

PCC-00091: TYPE statement requires format specification for this Oracle datatype

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

Action: Add the length, precision, and or or scale specification for the external datatype to the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-00090: Precision or scale specification must be given for DECIMAL datatype

PCC-00090: Precision or scale specification must be given for DECIMAL datatype

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

Action: Add the precision and or or scale specification to the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-00089: Invalid Oracle TYPE specification

PCC-00089: Invalid Oracle TYPE specification

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

Action: Check the spelling of the external datatype name. If necessary, supply the missing datatype name.

PCC-00087: EXEC SQL TYPE statement not allowed for this host language

PCC-00087: EXEC SQL TYPE statement not allowed for this host language

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.

Action: Remove the offending EXEC SQL TYPE statement.

PCC-00086: Source file string has zero length

PCC-00086: Source file string has zero length

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

Action: Specify a valid source file containing embedded SQL statements.

PCC-00085: Error writing to file string

PCC-00085: Error writing to file string

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.

Action: Check that sufficient privileges exist to access the file and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with system manager).

PCC-00083: Bind and define variables not allowed in CREATE statement

PCC-00083: Bind and define variables not allowed in CREATE statement

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.

Action: Correct or remove the erroneous CREATE statement.

PCC-00082: Length and scale specifications must be an integer

PCC-00082: Length and scale specifications must be an integer

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

Action: Correct or remove the length and or or scale specification.

PCC-00081: Scale specification not allowed for given datatype

PCC-00081: Scale specification not allowed for given datatype

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

Action: Check the precision specification and remove the scale specification.

PCC-00080: TYPE identifier already TYPEd

PCC-00080: TYPE identifier already TYPEd

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.

Action: Check the spelling of the identifiers. Use different identifiers in the EXEC SQL TYPE statements, or remove one of the EXEC SQL TYPE statements.

PCC-00079: ANSI requires colon on label in WHENEVER statement

PCC-00079: ANSI requires colon on label in WHENEVER statement

Cause: An Oracle extension to the ANSI or 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.

Action: No action required. However, for ANSI or ISO compliance, prefix alphanumeric (but not numeric) WHENEVER ... GOTO labels with a colon.

PCC-00078: FIPS warning: Invalid ANSI SQL Identifier

PCC-00078: FIPS warning: Invalid ANSI SQL Identifier

Cause: An Oracle extension to the ANSI or 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 or ISO compliant EXEC SQL END DECLARE SECTION; This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI or ISO compliance, change the host variable name so that it is lamp;lt;lamp;nbsp;= 18 characters long, begins with a letter, and does not contain consecutive or trailing underscores.

PCC-00077: Colon usage with numeric label in WHENEVER statement is not ANSI

PCC-00077: Colon usage with numeric label in WHENEVER statement is not ANSI

Cause: An Oracle extenstion to the ANSI or 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.

Action: No action required. However, for ANSI or ISO compliance, prefix alphanumeric (but not numeric) WHENEVER ... GOTO labels with a colon.

PCC-00076: DISPLAY type must be SIGN LEADING SEPARATE

PCC-00076: DISPLAY type must be SIGN LEADING SEPARATE

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

Action: Check the spelling of the variable declaration. If necessary, remove the reference to the unsupported DISPLAY type.

PCC-00075: : expected before indicator variable

PCC-00075: : expected before indicator variable

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

Action: Prefix a colon to the indicator variable in question.

PCC-00073: Cursor is declared but never OPENed at line number in file string.

PCC-00073: Cursor is declared but never OPENed at line number in file string.

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

Action: Remove the cursor declaration or code an OPEN statement for the cursor.

PCC-00072: Input file name length exceeds the maximum length

PCC-00072: Input file name length exceeds the maximum length

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

Action: Use a file name of length less than or equal to the maximum platform specific file name length.

PCC-00071: Unable to open message file.

PCC-00071: Unable to open message file.

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.

Action: Check that the limit for open files is high enough (check with the system manager). Otherwise, contact customer support.

PCC-00070: Illegal syntax, Exponential value in SQL statement: string

PCC-00070: Illegal syntax, Exponential value in SQL statement: string

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.

Action: Reformat the number correctly.

PCC-00069: Host variable string has unsupported datatype at line number in file string

PCC-00069: Host variable string has unsupported datatype at line number in file string

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.

Action: Redefine the host variable in the Declare Section, giving it a supported datatype.

PCC-00068: Host and indicator variables may not have the same name.

PCC-00068: Host and indicator variables may not have the same name.

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.

Action: Rename the host or indicator variable.

PCC-00067: Ireclen exceeded. Line number in file string truncated.

PCC-00067: Ireclen exceeded. Line number in file string truncated.

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

Action: Either shorten the input line or specify a larger IRECLEN value on the command line.

PCC-00066: Userid only used when SQLCHECK = FULL, userid ignored.

PCC-00066: Userid only used when SQLCHECK = FULL, userid ignored.

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

Action: Specify the USERID option only when SQLCHECK=SEMANTICS.

PCC-00065: Userid required, but not specified.

PCC-00065: Userid required, but not specified.

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

Action: Specify USERID=username or password or enter a username and password when prompted or specify SQLCHECK={SYNTAX | NONE}.

PCC-00064: All uses of a given host variable must use identical indicator variables.

PCC-00064: All uses of a given host variable must use identical indicator variables.

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

Action: Rename the indicator variables so that each occurrence of the host variable is associated with the same indicator variable.

PCC-00063: Reached end of file string before End-of-Statement at line number

PCC-00063: Reached end of file string before End-of-Statement at line number

Cause: The precompiler encountered an end-of-file while parsing a PL or SQL block.

Action: Add the appropriate statement terminator (;) or end-of-block statement (END;) to the PL or SQL block.

PCC-00062: Must use option SQLCHECK=SEMANTICS(FULL) when there is embedded PL or SQL

PCC-00062: Must use option SQLCHECK=SEMANTICS(FULL) when there is embedded PL or SQL

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

Action: Remove the PL or SQL block or specify SQLCHECK=SEMANTICS.

PCC-00061: Error at line number, column number. PLS-number: string

PCC-00061: Error at line number, column number. PLS-number: string

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

Action: Refer to the indicated PL or SQL error message to correct the SQL statement or embedded PL or SQL block.

PCC-00060: Both CURSOR and STATEMENT have AT clauses at line number of file string.

PCC-00060: Both CURSOR and STATEMENT have AT clauses at line number of file string.

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.

Action: Remove the AT clause from one of the statements.

PCC-00056: FOR clause not allowed on SELECT statement at line number in file string.

PCC-00056: FOR clause not allowed on SELECT statement at line number in file string.

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.

Action: Remove the FOR clause from the SELECT statement and use a host- language construct to iteratively execute the SELECT statement.

PCC-00055: Array string not allowed as bind variable at line number in file string

PCC-00055: Array string not allowed as bind variable at line number in file string

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

Action: Remove the host array or replace it with a simple host variable.

PCC-00054: Expected End-of-Statement at column number in line number of file string

PCC-00054: Expected End-of-Statement at column number in line number of file string

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).

Action: If tabs are embedded in the source ocde, replace them with spaces. Check the statement syntax and check that each EXEC statement has a terminator. For embedded CREATE {FUNCTION | PROCEDURE | PACKAGE} statements and for embedded PL or SQL blocks, check that the statement terminator is END-EXEC.

PCC-00053: FOR variable string is invalid type at line number in file string

PCC-00053: FOR variable string is invalid type at line number in file string

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).

Action: Check the declaration and check that the count variable has a datatype of NUMBER or LONG (or a compatible Oracle or host-language datatype).

PCC-00051: Size of VARCHAR string is larger than 65533 in line number in file string

PCC-00051: Size of VARCHAR string is larger than 65533 in line number in file string

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

Action: Check the Declare Section, making sure the size of each VARCHAR variable does not exceed the limit of 65533 bytes.

PCC-00050: Unable to generate descriptor in program unit ending line number in file string

PCC-00050: Unable to generate descriptor in program unit ending line number in file string

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

Action: Verify that the Declare Section is properly implemented. Then check for syntax errors at the beginning of the compilation unit and before any END DECLARE SECTION statement, and correct as appropriate.

PCC-00047: Unterminated comment or string constant beginning near line number in file string

PCC-00047: Unterminated comment or string constant beginning near line number in file string

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

Action: Check that all comments are delimited and all string constants are enclosed by quotation marks.

PCC-00045: %s clause inappropriate at line number in file string. Ignored.

PCC-00045: %s clause inappropriate at line number in file string. Ignored.

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

Action: Check the statement syntax, then relocate or correct the misplaced or invalid clause.

PCC-00044: Array size mismatch in INTO or USING. Minimum is: string(number:number)

PCC-00044: Array size mismatch in INTO or USING. Minimum is: string(number:number)

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

Action: Declare all array variables in the INTO or USING clause to have at least the minimum dimension given.

PCC-00042: Must EXEC SQL INCLUDE SQLCA when mode=ANSI and WHENEVER SQLWARNING used

PCC-00042: Must EXEC SQL INCLUDE SQLCA when mode=ANSI and WHENEVER SQLWARNING used

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.

Action: Remove all WHENEVER SQLWARNING statements from the program or declare the SQLCA by hardcoding it or copying it into the program with the INCLUDE statement.

PCC-00041: Unable to open output file string

PCC-00041: Unable to open output file string

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.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).

PCC-00040: Unable to open listing file string

PCC-00040: Unable to open listing file string

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.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager). If a listing file is not needed, specify LTYPE=NONE on the command line.

PCC-00039: Unable to open input file string

PCC-00039: Unable to open input file string

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.

Action: Check that the file exists, that the search path to the file is correct, that sufficient privileges have been granted to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with the system manager).

PCC-00038: Unable to open a cursor

PCC-00038: Unable to open a cursor

Cause: This is an internal error message not usually issued.

Action: Call customer support for assistance. If the application does not require syntactic or semantic checking of SQL statements and does not use PL or SQL, specify SQLCHECK=NONE on the command line.

PCC-00037: Unable to log on to ORACLE with string . ORACLE error number: number

PCC-00037: Unable to log on to ORACLE with string . ORACLE error number: number

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.

Action: Refer to the indicated message in the ORA message chapters of this manual.

PCC-00036: No input file name specified

PCC-00036: No input file name specified

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

Action: Use the INAME command-line option to specify the input file.

PCC-00033: Missing operand for option string

PCC-00033: Missing operand for option string

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).

Action: Check that a value for each option has been specified and there is no space around the equal sign.

PCC-00032: Invalid option string

PCC-00032: Invalid option string

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.

Action: Check that the option exists and that its name is spelled correctly. To see an online display of the precompiler options, enter the precompiler command (with no options) at the operating- system prompt. Also check that there is an equal sign between the option name and value.

PCC-00031: Invalid value given for option string

PCC-00031: Invalid value given for option string

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).

Action: Check the value, making sure it is spelled correctly and within the legal range.

PCC-00029: Ambiguous option string

PCC-00029: Ambiguous option string

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

Action: Respecify the full option name or an unambiguous abbreviation. To see an online display of the precompiler options, enter the precompiler command (with no options) at the operating-system prompt.

PCC-00028: Option string not legal as EXEC ORACLE OPTION

PCC-00028: Option string not legal as EXEC ORACLE OPTION

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.

Action: Respecify the precompiler option on the command line, instead of in an EXEC ORACLE statement. To see an online display of the precompiler options, enter the precompiler command (with no options) at the operating-system prompt.

PCC-00027: Redeclared SQL Identifier string at line number in file string

PCC-00027: Redeclared SQL Identifier string at line number in file string

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

Action: Check the spelling of the identifier, then, if necessary, remove the extra declaration.

PCC-00026: Invalid host variable string at line number in file string

PCC-00026: Invalid host variable string at line number in file string

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.

Action: Add or correct the host variable declaration.

PCC-00025: Undeclared indicator variable string at line number in file string

PCC-00025: Undeclared indicator variable string at line number in file string

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

Action: Add or correct the indicator variable declaration.

PCC-00024: Indicator variable string has wrong type or length at line number in file string

PCC-00024: Indicator variable string has wrong type or length at line number in file string

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.

Action: Redefine the indicator variable as a 2-byte integer.

PCC-00023: Unable to log off from ORACLE

PCC-00023: Unable to log off from ORACLE

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

Action: Check that ORACLE is available, then retry.

PCC-00022: Out of space - unable to allocate number bytes

PCC-00022: Out of space - unable to allocate number bytes

Cause: The precompiler process ran out of memory.

Action: Allocate more memory to the process, then retry.

PCC-00021: Oracle Error: string

PCC-00021: Oracle Error: string

Cause: An Oracle error occurred.

Action: Refer to the indicated message in the ORA message chapters of this manual.

PCC-00020: Unable to obtain define variables at line number in file string

PCC-00020: Unable to obtain define variables at line number in file string

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

Action: Check that the output host variable is declared in the Declare Section and used properly in the SQL statement.

PCC-00019: Unable to obtain bind variables at line number in file string

PCC-00019: Unable to obtain bind variables at line number in file string

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

Action: Check that the input host variable is declared in the Declare Section and used properly in the SQL statement.

PCC-00018: Expected string , but found string at line number in file string

PCC-00018: Expected string , but found string at line number in file string

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

Action: Check the syntax and the spelling, then correct the SQL statement.