PCC-01009: For hostlan = COB74, a SQL statement must be followed by ELSE or .

PCC-01009: For hostlan = COB74, a SQL statement must be followed by ELSE or .

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.

Action: Change the program logic, making the EXEC SQL statement the last statement in the sentence.

PCC-01008: Multiple element records not allowed in DECLARE section

PCC-01008: Multiple element records not allowed in DECLARE section

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.

Action: Assign each host variable its own group item.

PCC-01007: WORKING-STORAGE SECTION not found

PCC-01007: WORKING-STORAGE SECTION not found

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.

Action: Check that the WORKING-STORAGE SECTION header is in place and spelled correctly and that the right value for the FORMAT option is specified.

PCC-01006: EXEC statement cannot begin in Area A at line number in file string

PCC-01006: EXEC statement cannot begin in Area A at line number in file string

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

Action: Move the statement rightward so that it begins in Area B.

PCC-01005: PROCEDURE DIVISION not found

PCC-01005: PROCEDURE DIVISION not found

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.

Action: Check that the PROCEDURE DIVISION header is in place and spelled correctly, that there is no apostrophe in the REMARKS section, that all literals in the WORKING-STORAGE SECTION are terminated, and that the right value for the FORMAT option is specified.

PCC-01004: In an EXEC statement at end-of-file

PCC-01004: In an EXEC statement at end-of-file

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

Action: Terminate the last EXEC statement with an END-EXEC.

PCC-01003: Invalid continuation at line number in file string

PCC-01003: Invalid continuation at line number in file string

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

Action: Remove or replace the empty continuation line.

PCC-01002: Invalid character character in indicator area at line number in file string

PCC-01002: Invalid character character in indicator area at line number in file string

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

Action: Remove or replace the invalid character. If the FORMAT=ANSI option is specified, check for an end-of-line in column 7.

PCC-01001: Your Pro*COBOL authorization is about to expire

PCC-01001: Your Pro*COBOL authorization is about to expire

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

Action: Call customer support for assistance.

PCC-01000: You are not authorized to run Pro*COBOL

PCC-01000: You are not authorized to run Pro*COBOL

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

Action: Call customer support for assistance.

PCC-00147: DBMS=V6 no longer supported; using DBMS=NATIVE

PCC-00147: DBMS=V6 no longer supported; using DBMS=NATIVE

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

Action: Revise the specified DBMS option value from v6 to another value as desired.

PCC-00146: Illegal value for host option, ignored

PCC-00146: Illegal value for host option, ignored

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.

Action: Specify a valid host language with the host option.

PCC-00145: This statement can only be used with THREADS=YES

PCC-00145: This statement can only be used with THREADS=YES

Cause: EXEC SQL ENABLE THREADS or one of the EXEC SQL CONTEXT statements has been used, even though option THREADS is set to NO.

Action: Specify option THREADS=YES or remove the EXEC ENABLE THREADS or EXEC SQL CONTEXT statement from the source code.

PCC-00144: UNSAFE_NULL=YES must be used with DBMS=V7 and MODE=ORACLE

PCC-00144: UNSAFE_NULL=YES must be used with DBMS=V7 and MODE=ORACLE

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

Action: Either specify DBMS=V7 and MODE=ORACLE (the default) when using UNSAFE_NULL=YES or do not use UNSAFE_NULL=YES.

PCC-00143: Runtime context variable not of correct type

PCC-00143: Runtime context variable not of correct type

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

Action: Declare your runtime context variable of type sql_context.

PCC-00142: No EXEC SQL CONTEXT USE statement encountered

PCC-00142: No EXEC SQL CONTEXT USE statement encountered

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

Action: Ensure that the necessary context variable (of type sql_context) has been declared, ALLOCATEd, and USEd prior to any executable SQL statements.

PCC-00141: Thread Safety is not implemented in this precompiler

PCC-00141: Thread Safety is not implemented in this precompiler

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

Action: Rewrite your host-language code to not use contexts.

PCC-00140: CREATE FUNCTION or PROCEDURE or PACKAGE or TRIGGER are Oracle extensions

PCC-00140: CREATE FUNCTION or PROCEDURE or PACKAGE or TRIGGER are Oracle extensions

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

Action: No action is required. However, for ANSI or ISO compliance, do not use any of these statements.

PCC-00139: Cannot change MAXLITERAL after an EXEC SQL statement

PCC-00139: Cannot change MAXLITERAL after an EXEC SQL statement

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.

Action: Use the MAXLITERAL option only on the command line or in an EXEC ORACLE OPTION statement placed at the beginning of the input source file.

PCC-00138: Result Set Cursors are not implemented in this precompiler

PCC-00138: Result Set Cursors are not implemented in this precompiler

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 or I.

Action: Rewrite your host-language code to use standard SQL cursors.