PCC-02108: UNSAFE_NULL=YES allowed if MODE=ORACLE and DBMS=V7 or V8

PCC-02108: UNSAFE_NULL=YES allowed if MODE=ORACLE and DBMS=V7 or V8

Cause: UNSAFE_NULL=YES was specified on the command line, but but either the MODE was not ORACLE or the DBMS was not V7 or V8.

Action: Specify MODE=ORACLE and DBMS=V7 or V8 when using UNSAFE_ NULL=YES.

PCC-02107: You may not specify PARSE = FULL when CODE = CPP

PCC-02107: You may not specify PARSE = FULL when CODE = CPP

Cause: The PARSE=FULL and CODE=CPP options were both specified on the command line. The PARSE=FULL option invokes the C parser which does not understand any C++ constructs generated by the precompiler with CODE=CPP option.

Action: Set the PARSE option to either NONE or PARTIAL if the CODE=CPP option is specified.

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

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

Cause: The USERID option was specified on the command line, but SQLCHECK was not equal to FULL or SEMANTICS. The USERID has no effect, unless SQLCHECK=FULL or SQLCHECK=SEMANTICS.

Action: This is a warning message only.

PCC-02105: Unable to open list file

PCC-02105: Unable to open list file

Cause: The precompiler could not open the listing file. This message can result from many causes. For example, o) A pathname for a specified listing file contains a non-existent directory. o) An operating-system error occured because the file system or disk is full. o) Write permission on the specified directory has not been granted.

Action: Track down the cause of the error, as suggested above, and correct it.

PCC-02104: Unable to connect to Oracle

PCC-02104: Unable to connect to Oracle

Cause: The precompiler could not connect to Oracle with the username, password, and, if applicable, database link that was supplied. Note that this is a precompiler message, not a runtime message. This means that the USERID option value, either on the command line or in a configuration file, was incorrect.

Action: Check that the username and password are current and correct. Run SQL*DBA or SQL*PLUS and verify that connection can be made using that username and password.

PCC-02103: Password:

PCC-02103: Password:

Cause: The username was specified on the command line without a password. For example, proc sqlcheck=full iname=sample1.pc userid=scott

Action: Re-enter the command line, and include the password or specify the password when prompted.

PCC-02102: Fatal error while doing C preprocessing

PCC-02102: Fatal error while doing C preprocessing

Cause: The precompiler issues this message after a more specific message.

Action: Correct the problem specified in the previous message or messages.

PCC-02101: Unable to open input file

PCC-02101: Unable to open input file

Cause: The precompiler could not open the input file. This is the .pc file specified in the INAME=option. This means that the file does not exist, that a directory was incorrectly specified in the pathname, or that the person running the precompiler does not have read permission for the file. This message could also result from operating-system errors. For example, an unmounted file system or disk I or O errors, could trigger this error.

Action: Check that permission to read the file exists and that the full pathname has been specified correctly. Check for operating- system problems. See also the operating system-specific Oracle documentation.

PCC-02100: Unable to initialize PL or SQL

PCC-02100: Unable to initialize PL or SQL

Cause: The precompiler connected to Oracle but could not invoke the PL or SQL engine. This error can result if an earlier release of Oracle7 is used without the Procedural Option.

Action: To use PL or SQL, upgrade to a more recent release of Oracle7.

PCC-02081: CMD-LINE: Unterminated option value list or value list was truncated.

PCC-02081: CMD-LINE: Unterminated option value list or value list was truncated.

Cause: An option that takes a list of values was entered. The value list did not have a closing parenthesis. This error may also occur if the list of values entered on a single line was too long and Pro*C truncated it.

Action: Ensure that all value lists are terminated with a closing parenthesis. Split long value lists into individual entries.

PCC-02066: CMD-LINE: Could not find or could not open system config file

PCC-02066: CMD-LINE: Could not find or could not open system config file

Cause: The system configuration file has a standard name (pmscfg.h) and a location that is operating system dependent. On UNIX systems, it is located in the ORACLE_HOME or proc directory. If a file named pmscfg.h is not found in the standard location, this warning message is issued.

Action: Create a system configuration file in the standard location. The file can be empty. See also the operating system specific Oracle documentation.

PCC-02047: CMD-LINE: Option is not allowed inline:

PCC-02047: CMD-LINE: Option is not allowed inline:

Cause: An option was entered inline that can only be entered on the command line or in a configuration file. For example, the offending code might look like EXEC ORACLE OPTION (NLS_CHAR=lamp;lt;lamp;nbsp;namelamp;gt;); The NLS_CHAR option can only be entered on the command line or in a configuration file.

Action: Remove the option from the source file, and specify it on the command line.

PCC-02046: CMD-LINE: Unable to open config file:

PCC-02046: CMD-LINE: Unable to open config file:

Cause: A non-existent user configuration file was specified on the command line with the config option.

Action: Provide a valid filename for the configuration file.

PCC-02045: CMD-LINE: Option is not unique:

PCC-02045: CMD-LINE: Option is not unique:

Cause: An option name was partially specified on the command line that made it non unique. For example, % proc in=t.pc the in option can imply either the INAME or INCLUDE option.

Action: Provide sufficient characters on the command line to make the option name unique.

PCC-02044: CMD-LINE: Illegal or out of range value for option:

PCC-02044: CMD-LINE: Illegal or out of range value for option:

Cause: A value specified for a command line option was not within the accepted range. For example,, the range for the MAXOPENCURSORS option is 5 to 256. If a value outside the range is specified, the message is triggered.

Action: See the Programmer s Guide to the Oracle Precompilers for the ranges that option values can take.

PCC-02043: CMD-LINE: Option syntax is incorrect

PCC-02043: CMD-LINE: Option syntax is incorrect

Cause: A value for a command line option was incorrectly specified.

Action: See the Programmer s Guide to the Oracle Precompilers, Release 2.2 for the correct syntax for specifying command line option values.

PCC-02041: CMD-LINE: Option does not exist:

PCC-02041: CMD-LINE: Option does not exist:

Cause: A non existent option on the command line was specified.

Action: See the Programmer s Guide to the Oracle Precompilers, Release 2.2 for a list of the valid command line options and their possible values.

PCC-02040: CMD-LINE: Option selected, but no value provided

PCC-02040: CMD-LINE: Option selected, but no value provided

Cause: An option on the command line was specified, but a value for it was not included. For example, the offending code might look like: proc iname=sample1.pc oname=

Action: Provide a value for the option.

PCC-02035: CMD-LINE: CONFIG= option is invalid in a config file

PCC-02035: CMD-LINE: CONFIG= option is invalid in a config file

Cause: A user configuration file inside a user configuration file cannot be specified. That is, nested configuration files cannot be nested.

Action: If there are nested configuration files, move the options from the nested files to the top levels.

PCC-02023: Found end of file while scanning a PL or SQL statement

PCC-02023: Found end of file while scanning a PL or SQL statement

Cause: The precompiler encountered an end of file while parsing a PL or SQL statement (EXEC SQL EXECUTE ...).

Action: Complete the PL or SQL statement.

PCC-02022: Found end of file while scanning a SQL statement

PCC-02022: Found end of file while scanning a SQL statement

Cause: The precompiler encountered an end of file while parsing an EXEC SQL statement.

Action: Add statement terminator(;) or complete the EXEC SQL statement.

PCC-02021: Found newline while scanning string literal

PCC-02021: Found newline while scanning string literal

Cause: A string constant contains a newline character, For example char x(( = Hello world;

Action: Remove the newline character.

PCC-02020: Preprocessor error at line number, column number, file string:

PCC-02020: Preprocessor error at line number, column number, file string:

Cause: This message indicates that an error condition occured as the precompiler was in the preprocessing phase. A more specific error message will follow this message.

Action: Correct the error according to the action specified for the message that follows.

PCC-02019: Preprocessor warning at line number, column number, file string:

PCC-02019: Preprocessor warning at line number, column number, file string:

Cause: This message indicates that a warning condition occured as the precompiler was doing the preprocessor pass. A more specific warning message will follow this message.

Action: Correct the condition according to the action specified for the message that follows.

PCC-02018: found end-of-file while scanning comment

PCC-02018: found end-of-file while scanning comment

Cause: A C comment either in C code or in an embedded SQL statement, was not terminated.

Action: Find the unterminated comment and terminate it with * or .

PCC-02017: unable to open output file

PCC-02017: unable to open output file

Cause: The precompiler could not open an output file. This could be a generated code output file(.c file) or a listing file. This message can result from many causes. For example: o) A pathname for a specified output file contains a non-exixtent directory. o) An operating-system error occured because the file system or disk is full. o) Write permission on the specified directory or directories in the path do not exist.

Action: Track down the cause of the error, as suggested above, and correct it.

PCC-02016: include file pathname is too long

PCC-02016: include file pathname is too long

Cause: The pathname for include files exceeded the maximum length of 80 characters.

Action: Move the include file, or create an environment variable or logical to shorten the pathname.

PCC-02015: unable to open include file

PCC-02015: unable to open include file

Cause: The precompiler could not open a header file that was specified using the #include preprocessor directive or the EXEC SQL INCLUDE statement. This can happen if the file specification is inaccurate or if read permission or read access rights on the file or on one or more of the directories in the path were not granted.

Action: Recheck that the file specification is correct, that the file exists, and that read permission has been granted so that the file can be read.

PCC-02014: Syntax error at line number, column number, file string:

PCC-02014: Syntax error at line number, column number, file string:

Cause: The precompiler detected an errorin C or embedded SQL syntax. This message is followd by a more specific error message.

Action: Correct the syntax error.

PCC-02013: unknown escape sequence

PCC-02013: unknown escape sequence

Cause: The precompiler found an escape sequence that it could not process inside a string literal. This error can arise when multibyte character strings that can contain shift-in or shift-out escape sequences are used.

Action: Correct the string representation.

PCC-02012: did not find matching quote for char constant

PCC-02012: did not find matching quote for char constant

Cause: A character constant with a single quotation mark was not terminated.

Action: Terminate the character constant.

PCC-02011: found identifier greater than 128 characters (truncated)

PCC-02011: found identifier greater than 128 characters (truncated)

Cause: The precompiler found an identifier that was too long.

Action: Shorten the identifier. SQL identifiers should be limited to 18 characters.

PCC-02010: found end-of-file while scanning string literal

PCC-02010: found end-of-file while scanning string literal

Cause: A string in a SQL statement, which should be delimited by single quotation marks, was not terminated properly.

Action: Check that all strings are delimited.

PCC-01515: FIPS warning: Undeclared host variable string at line number in file string

PCC-01515: FIPS warning: Undeclared host variable string at line number in file string

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

Action: No action required. However, for ANSI or ISO compliance, declare the host variable within a Declare Section.

PCC-01513: FIPS warning: Unsupported datatype in line number of file string

PCC-01513: FIPS warning: Unsupported datatype in line number of file string

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

Action: No action required. However, for ANSI or ISO compliance, use only ANSI or ISO standard types.

PCC-01512: Invalid EXEC SQL INCLUDE of file string found at line number in file string

PCC-01512: Invalid EXEC SQL INCLUDE of file string found at line number in file string

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

Action: Embed required source text directly in the Pro*Ada file. Use the with context clause to include required packages.

PCC-01511: Identifier on line number in file string too long for code generated in file string

PCC-01511: Identifier on line number in file string too long for code generated in file string

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.

Action: Use a shorter identifier or use the ORECLEN option to increase the allowed line length.

PCC-01510: No Package, Procedure or Function statement seen in string

PCC-01510: No Package, Procedure or Function statement seen in string

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

Action: Add the appropriate statement(s) to the source file and rerun Pro*Ada.

PCC-01501: Your Pro*Ada authorization is about to expire

PCC-01501: Your Pro*Ada authorization is about to expire

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

Action: Call customer support for assistance.

PCC-01500: You are not authorized to run Pro*Ada

PCC-01500: You are not authorized to run Pro*Ada

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

Action: Call customer support for assistance.

PCC-01401: Your Pro*Pascal authorization is about to expire

PCC-01401: Your Pro*Pascal authorization is about to expire

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

Action: Call customer support for assistance.

PCC-01400: You are not authorized to run Pro*Pascal

PCC-01400: You are not authorized to run Pro*Pascal

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

Action: Call customer support for assistance.

PCC-01301: Your Pro*PL or I authorization is about to expire

PCC-01301: Your Pro*PL or I authorization is about to expire

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

Action: Call customer support for assistance.

PCC-01300: You are not authorized to run Pro*PL or I

PCC-01300: You are not authorized to run Pro*PL or I

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

Action: Call customer support for assistance.

PCC-01202: Identifier string truncated to 31 characters

PCC-01202: Identifier string truncated to 31 characters

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

Action: No action required. This message is just informational.

PCC-01201: Your Pro*C authorization is about to expire

PCC-01201: Your Pro*C authorization is about to expire

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

Action: Call customer support for assistance.

PCC-01200: You are not authorized to run Pro*C

PCC-01200: You are not authorized to run Pro*C

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

Action: Call customer support for assistance.

PCC-01102: Invalid label at line number in file string

PCC-01102: Invalid label at line number in file string

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

Action: Correct or remove the statement label.

PCC-01101: Your Pro*FORTRAN authorization is about to expire

PCC-01101: Your Pro*FORTRAN authorization is about to expire

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

Action: Call customer support for assistance.

PCC-01100: You are not authorized to run Pro*FORTRAN

PCC-01100: You are not authorized to run Pro*FORTRAN

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

Action: Call customer support for assistance.

PCC-01019: Invalid conversion buffer size

PCC-01019: Invalid conversion buffer size

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.

Action: Specify an integer in the range 1-32765.

PCC-01018: Conversion buffer size can only be specified for character types

PCC-01018: Conversion buffer size can only be specified for character types

Cause: A CONVBUFSZ clause has been used in an EXEC SQL VAR statement where the variable is not of a character datatype.

Action: Remove the CONVBUFSZ clause from the EXEC SQL VAR statement.

PCC-01017: The SQLCA and a SQLCODE variable cannot both be used

PCC-01017: The SQLCA and a SQLCODE variable cannot both be used

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.

Action: Use either the SQLCA or the SQLCODE variable. Remove either the include of the SQLCA or the SQLCODE variable declaration.

PCC-01016: N character literals not supported in embedded PL or SQL

PCC-01016: N character literals not supported in embedded PL or SQL

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

Action: Remove the N character literal from the PL or SQL block.

PCC-01015: Cannot equivalence PIC N variable string

PCC-01015: Cannot equivalence PIC N variable string

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.

Action: Do not use the PIC N variable in an EXEC SQL VAR statement. If you want an equivalence to an Oracle type using an EXEC SQL VAR statement, use a PIC X variable, instead of a PIC N variable.

PCC-01014: VARYING not supported with PIC N PICTURE clause

PCC-01014: VARYING not supported with PIC N PICTURE clause

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

Action: Remove the keyword VARYING from the variable declaration. If you want to declare a PIC N VARCHAR variable, specify the precompiler option VARCHAR=YES and declare the variable as an implicit VARCHAR group item as illustrated by the following example: EXEC SQL BEGIN DECLARE SECTION

PCC-01013: Invalid use of PIC N array variable string at line number in file string

PCC-01013: Invalid use of PIC N array variable string at line number in file string

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

Action: Declare the PIC N variable without an OCCURS clause or, if the PIC N variable is not used in any SQL statements, declare it outside the Declare Section.

PCC-01012: DATA DIVISION not found

PCC-01012: DATA DIVISION not found

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.

Action: Add a DATA DIVISION to the input source file.

PCC-01011: USAGE IS BINARY clause must be terminated by . on same line

PCC-01011: USAGE IS BINARY clause must be terminated by . on same line

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.

Action: Check that the period terminating the USAGE IS BINARY clause is on the same line as the USAGE clause.

PCC-01010: Invalid use of NULL character in character literal

PCC-01010: Invalid use of NULL character in character literal

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

Action: Remove the null character from the string literal.