User`s guide

Pro*COBOL
5-6 Oracle Database User's Guide
$ORAC1120.C.DEMO.*.PC
$ORAC1120.UTM.DEMO.*.PC
$ORAC1120.CONFIG.PCSCFG.CFG
An example of a compilation and precompilation procedure is included in the Oracle
Database Software under the name
$ORAC1120.P.PROC .
5.3.3 SQLLIB Calls
If you want to code explicit C calls to SQLLIB functions, then you must call SQ2XXX
instead of
SQLXXX . For example, call SQ2CEX instead of SQLCEX .
5.3.4 Linking Pro*C
To link a Pro*C program, you need:
■ The Common Run-Time Environment, CRTE .
■ The Pro* library ( $ORAC1120.PRO.LIB ), which contains the stub module, PROSTUB.
At run time, this module loads the pre-linked module,
ORAPRO , which contains the
actual
SQLLIB code.
To link your program, you should create your user-specific link procedure. An
example of such a link procedure is included in the Oracle Database Software under
the name,
$ORAC1120.P.PROLNK .
5.3.5 The Pro*C SQLCPR.H Header File
If you are making calls to Pro*C functions, such as sq2cls() or sq2glm() , then you can
include the
SQLCPR.H file in the C programs to verify that you have called the functions
correctly.
In the Pro*C programs add the following line:
EXEC SQL INCLUDE SQLCPR
as you would for SQLCA or SQLDA .
5.3.6 UTM Applications
You can use Pro*C to write UTM program units. Refer to Oracle Database Installation
and Administration Guide for Fujitsu BS2000/OSD for UTM programming rules.
5.4 Pro*COBOL
This section discusses the procedure for using Pro*COBOL. You must follow these
special considerations, when using Pro*COBOL:
■ Host variables of the type PIC S9(n) with n =8 and n >10 are not supported.
■ When using Pro*COBOL be careful about the following constructions with
paragraphs and
EXEC statements, because the precompiler generates a paragraph
heading for the code generated from these
EXEC statements.
Note: You must use BINDER instead of TSOSLNK .