Releases 9.2 and 1.8.77 for Windows
Part Number A96113-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Pro*COBOL Precompiler Getting Started Releases 9.2 and 1.8.77 for Windows Part Number A96113-01 |
|
This chapter provides an overview of building Oracle database applications with Pro*COBOL Releases 9.2 and 1.8.77 for Windows operating systems.
This chapter contains these topics:
This section describes the basics of precompiling a Pro*COBOL application.
| See Also:
Pro*COBOL Precompiler Programmer's Guide for more information about Pro*COBOL commands, precompiler options, and configuration files |
Use one of the following commands to precompile a file:
procob filename
procob18 filename
By default, if no extension is provided, Pro*COBOL tries to open filename.pco. If the ONAME option is not specified, Pro*COBOL generates a file named filename.cbl.
Many useful options are available at precompile time. Included are options that allow you to determine how:
To see a list of available options and their default values, enter the following at the command prompt:
C:\> procob
To see the option, defaults, and the restrictions (if any) on values, enter the following at the command prompt:
C:\> procob /?
Pro*COBOL reads the configuration file for options before processing options supplied at the command line.
pcbcfg.cfg. This file is located in the ORACLE_BASE\ORACLE_HOME \precomp\admin directory.pcccob.cfg. This file is located in the ORACLE_BASE\ORACLE_HOME\precomp\admin directory.The configuration file has the following two options:
Check the following to determine whether you should change the value of COMP-5:
If you are using MERANT Micro Focus COBOL, COMP-5 can be set to yes (COMP-5=yes) or no (COMP-5=no).
For a workaround during the compilation stage, use the MERANT Micro Focus COBOL compiler directive:
MAKESYN "COMP-5" = "COMP"
This statement directs the compiler to treat COMP items as if they are COMP-5 items.
The INCLUDE option enables the provided .cob files in the ORACLE_BASE\ORACLE_HOME\precomp\public directory to be included without an explicit INCLUDE= option at the command line.
If you are using embedded PL/SQL blocks, do the following:
SQLCHECK option and the USERID string to connect at the precompiling command line.SQLCHECK=FULL option to check the syntax or semantics of embedded SQL statements and PL/SQL blocks.
| See Also:
Pro*COBOL Precompiler Programmer's Guide for an example of a command line string or review the PL/SQL MAKE file |
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:
In each of these the COBSQL utility may be used with the following advantages:
.pco source file rather than the .cbl file produced by Pro*COBOL.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:
MAKESYN "COMP-5" = "COMP"
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).
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\orasql9.lib
The previous commands produce sample1.exe, which can be executed like any other Windows NT, Windows 2000, or Windows 98 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:
scott with password tiger.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:
For release 9.2.0, the batch files are located in ORACLE_BASE\ORACLE_HOME \precomp\demo\procob2. For release 1.8.77, the files are located in ORACLE_BASE\ORACLE_HOME \precomp\demo\procob.
To build the sample programs:
C:\ORACLE\ORA90\PRECOMP\DEMO\PROCOB2> makeit sample1
The commands to run the sample programs assume that the following are the current working directories:
ORACLE_BASE\ORACLE_HOME \precomp\demo\procob2 directory for release 9.2.0ORACLE_BASE\ORACLE_HOME \precomp\demo\procob directory for release 1.8.77You 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 for release 9.2.0 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\orasql9.lib
For release 1.8.77, this batch file contains the following:
procob18 iname=%1.pco ireclen=132
cobol %1 /anim /litlink makesyn "COMP-5" = "COMP";
cbllink %1 /M%1 ORACLE_BASE\ORACLE_HOME\precomp\lib\orasql9.lib
The Pro*COBOL sample files listed in Table 2-1, " Pro*COBOL Sample Programs" are located in the ORACLE_BASE\ORACLE_HOME\precomp\demo\procob2 (release 9.2.0) and/or ORACLE_BASE\ORACLE_HOME\precomp\demo\procob (release 1.8.77) directories. The SQL scripts are located in the ORACLE_BASE\ORACLE_HOME\precomp\demo\sql directory.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|