This section provides an overview of building Oracle database applications with Pro*COBOL for Windows operating systems.
This section contains these topics:
Pro*COBOL supports the MERANT Micro Focus NetExpress version 5.0 for 32-bit Windows. This section describes how to compile and link Pro*COBOL applications using the MERANT Micro Focus compiler.
You can build and execute a MERANT Micro Focus COBOL application in two ways:
How to Use the IDE (using NetExpress only)
How to Use the Animator Products (products other than NetExpress)
The COBOL and CBLLINK Commands (all products)
In each of these the COBSQL utility may be used with the following advantages:
Pro*COBOL is run by the MERANT Micro Focus compiler and does not need to be run as a separate step.
Animation is done using the .pco source file rather than the .cbl file produced by Pro*COBOL.
The MAKEYSYN directive is provided automatically and need not be specified manually.
A program generated by Pro*COBOL can be compiled and executed from within the MERANT Micro Focus NetExpress IDE. Simply add the .cbl
file generated by Pro*COBOL to a Net Express project. To avoid potential inconsistencies when calling routines in the Oracle libraries the program should be compiled using the directive:
MAKESYN "COMP-5" = "COMP"
This directive can be specified in the build setting for the source file, the project settings or through a $SET
line at the start of the source file. When you select Rebuild or Rebuild All the IDE generates an executable ready to Run or Animate.
Programs can be compiled and executed from within the MERANT Micro Focus COBOL debugger, Animator V2.
To avoid potential inconsistencies when calling routines in the Oracle libraries, select the menu option Compiler Directives, and enter:
This step is required because MERANT Micro Focus COBOL stores binary numbers in Big Endian format. Oracle libraries expect binary numbers to be stored in Little Endian format (machine format).
MAKESYN "COMP-5" = "COMP"
COBOL
and CBLLINK
can be used to build programs in two ways, depending on whether the Pro*COBOL runtime is to be statically linked or accessed through a DLL at runtime.
For dynamic linking, the commands are:
COBOL sample1 /MAKESYN"COMP-5"="COMP"; CBLLINK sample1
For static linking, the commands are:
COBOL sample1 /LITLINK /MAKESYN"COMP-5"="COMP";
CBLLINK sample1 ORACLE_BASE\ORACLE_HOME\precomp\lib\orasql12.lib
The previous commands produce sample1.exe
, which can be executed like any other Windows program.
Note:
MERANT Micro Focus COBOL must be installed on the same system as Pro*COBOL to successfully execute the file.COBSQL
can be used to simplify preprocessing and debugging. To use COBSQL
, specify the following directive to the COBOL compiler:
PREPROCESS(COBSQL) COBSQLTYPE=ORACLE8 ENDP
or the short form:
P(COBSQL) CSQLT=ORA8 ENDP
COBSQLTYPE
should be set to ORACLE
or ORA
for versions of Pro*COBOL prior to release 8.0. The directive may be set with a $SET
line at the start of the source file, on the COBOL command line, in program build settings or project settings for NetExpress, or with SQL compiler directives settings for Animator. At compile time, COBSQL runs Pro*COBOL as a background task and passes its output to the COBOL compiler together with additional information required to enable Animator to track execution using the .pco
file rather than .cbl
file.
When using COBSQL
there is no need to deal directly with the .cbl
file. Instead, add the .pco
file to a NetExpress project, or open it with Animator.
Oracle provides sample programs to demonstrate the use of Pro*COBOL with Oracle database features. See "Sample Files" for a listing of these programs.
This section describes how to use the basic precompiling, compiling, and linking commands to build the sample programs. This section also describes the preparations required for running the Pro*COBOL sample programs.
To run the Pro*COBOL sample programs, you must have a database account with the username scott
and the password tiger
. If this account does not exist on your database, create one before running the sample programs.
The scott account must contain the emp and dept tables. If the account does not contain these tables, use the demobld.sql script to create them.
To run the demobld.sql script:
Start SQL*Plus.
Connect to the database as username scott with password tiger
.
Run the demobld.sql script. For example:
SQL> @ORACLE_BASE\ORACLE_HOME\sqlplus\demo\demobld.sql
Pro*COBOL supplies the makeit.bat file which is listed in the next section, for building a MERANT Micro Focus COBOL sample file:
The batch files are located in ORACLE_BASE\ORACLE_HOME \precomp\demo\procob2
.
To build the sample programs:
Run the batch files with any sample file. Do not include the file extension. For example:
C:\ORACLE\ORA90\PRECOMP\DEMO\PROCOB2> makeit sample1
Ensure that all paths and file names reflect the configuration of your system, if you encounter errors when building a sample program.
The commands to run the sample programs assume that the following is the current working directory:
ORACLE_BASE\ORACLE_HOME \precomp\demo\procob2
You may need to modify the sample link script to reflect the configuration of your system. See "Compiling and Linking Pro*COBOL Applications" for more information.
The makeit.bat contains the following:
procob iname=%1.pco ireclen=132 cobol %1 /anim /litlink makesyn "COMP-5" = "COMP"; cbllink %1 /M%1 ORACLE_BASE\ORACLE_HOME\precomp\lib\orasql12.lib
The Pro*COBOL sample files listed in Table F-1 are located in the ORACLE_BASE\ORACLE_HOME\precomp\demo\procob2
directory. The SQL scripts are located in the ORACLE_BASE\ORACLE_HOME\precomp\demo\sql
directory.
Table F-1 Pro*COBOL Sample Programs
Sample Program | Description |
---|---|
|
Simple query |
|
Cursor operations |
|
Host tables |
|
Datatype equivalence |
|
Dynamic SQL Method 1 |
|
Dynamic SQL Method 2 |
|
Dynamic SQL Method 3 |
|
Stored procedure call |
|
Stored procedure call |
|
Dynamic SQL Method 4 |
|
Cursor variable operations |
|
Cursor variable operations |
|
|
|
Nested program |
|
Simple query and insert |
|
Host table x |
|
LOB datatypes |
|
LOB datatypes |