User`s guide

ManualsBrandsSiemens ManualsComputer equipmentBS2000/OSD

The Oracle Call Interface

5-8 Oracle Database User's Guide

5.4.2 Pro*COBOL Include, System Configuration, and Demo Files

The Pro*COBOL include files, demo files, and system configuration file are shipped

under:

$ORAC1120.PRO.INCLUDE.LIB

$ORAC1120.COBOL.DEMO.*.PCO

$ORAC1120.UTM.DEMO.*.PCO

$ORAC1120.CONFIG.PCBCFG.CFG

An example of a compilation and precompilation procedure is included in your Oracle

Database Software under the name

$ORAC1120.P.PROCOB2000

5.4.3 SQLLIB Calls

If you want to code explicit COBOL calls to

SQLLIB

functions, then call

SQ0XXX

instead

SQLXXX

. For example, call

SQ0ADR

instead of

SQLADR

5.4.4 Linking Pro*COBOL

To link a Pro*COBOL 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.

■ Unicode is only supported with COBOL2000. This might generate calls to the

BS2000-Macro

NLSCNV

. To resolve the

GNLCNV

entry, use the system XHCS library.

Refer to Fujitsu User's Guide XHCS for BS2000 for more information about the

GNLCNV

entry.

To link your program, you should create your own user-specific link procedure. An

example of such a link procedure is included on your Oracle Database Software under

the name,

$ORAC1120.P.PROLNK

5.4.5 openUTM Applications

You can use Pro*COBOL to write openUTM program units. Refer to Oracle Database

Installation and Administration Guide for Fujitsu BS2000/OSD for openUTM

programming rules. Program units written in Pro*C and Pro*COBOL can be

combined.

5.5 The Oracle Call Interface

Under BS2000/OSD, the Oracle Call Interface supports the C and COBOL languages.

When you use the set of host language calls that make up the Oracle Call Interface,

you can access the data in an Oracle Database by programs written in the C and

Note: The PROCOB option MAXLITERAL defaults to 180, not 256,

as shown in the Pro*COBOL Programmer's Guide. The option

FORMAT=TERMINAL is not supported.

Note: You must use

BINDER

instead of

TSOSLNK