User`s guide

Pro*COBOL
Programmatic Interfaces 5-7
Before precompiling, the statement PERFORM COB-LABEL1 runs the code in paragraph
COB-LABEL1 until the COB-LABEL2 heading is reached. However, the precompiler
generates a paragraph heading,
SQL-LABEL1 , for the code generated from the EXEC SQL
statement.
As a result, after precompiling, PERFORM COB-LABEL1 runs the code in the paragraph,
COB-LABEL1 , until SQL-LABEL1 is reached. The workaround for this problem is to use
SECTIONS or to run PERFORM COB-LABEL1 THRU COB-LABEL2 .
A COPY statement as first statement in WORKING STORAGE SECTION may result in wrong
code generation if copied structures are to be continued by non-copied code because
the precompiler generates its data definitions before the first data definition of the
source program. To avoid this action, insert one
FILLER definition as first line in
WORKING-STORAGE SECTION as follows:
01 FILLER PIC X
■ The default data type for PIC X variables has changed in version 8.1.7 from
VARCHAR2 to CHARF . A precompiler option provides backward compatibility:
PICX={VARCHAR2 | CHARF (default)} .
This option is allowed only on the command line or in a configuration file. The new
default action is consistent with the usual COBOL move action.
For more details, refer to the chapter "Precompiler Options", in Pro*COBOL
Programmer's Guide.
5.4.1 Starting Pro*COBOL
To start the Pro*COBOL precompiler, enter the following command:
/START-PROGRAM $ORAC1120.PROCOB
* INAME=myprog.PCO ONAME=myprog.COB [options]
where:
myprog specifies the COBOL program to compile and link
options is one of the PROCOB options described in the Pro*COBOL Programmer's
Guide.
Before
precompiling
After precompiling
COB-LABEL1. COB-LABEL1
. .
. .
EXEC SQL.... SQL-LABEL1.
. .
. .
COB-LABEL2. COB-LABEL2.
Note: Using the default PICX=CHARF while precompiling existing
applications may result in run-time error
ORA-1403: no data found .