Building Applications for UNIX** Environments

Micro Focus COBOL

The script file bldmfcc, in sqllib/samples/cobol_mf, contains the commands to build a sample COBOL program.

The first parameter, $1, specifies the name of your source file. The second parameter, $2, specifies the name of the database to which you want to connect. The third parameter, $3, specifies the user ID for the database, and $4, specifies the password. Only the first parameter, the source file name, is required. Database name, user ID, and password are optional. If no database name is supplied, the program uses the default sample database.

#! /bin/ksh # bldmfcc script file # Builds a COBOL program containing embedded SQL # Usage: bldmfcc <prog_name> [ <db_name> [ <userid> <password> ]] # Connect to a database. if (($# < 2)) then db2 connect to sample elif (($# < 3)) then db2 connect to $2 else db2 connect to $2 user $3 using $4 fi # Precompile the program. db2 prep $1.sqb bindfile # Bind the program to the database. db2 bind $1.bnd # Disconnect from the database. db2 connect reset # Set COBCPY to include the DB2 COPY files directory. export COBCPY=$COBCPY:/opt/IBMdb2/v5.0/include/cobol_mf # Compile the checkerr.cbl error checking utility. cob -cx checkerr.cbl # Compile the program. cob -cx $1.cbl # Link the program. cob -x $1.o checkerr.o -L/opt/IBMdb2/v5.0/lib -ldb2 -lhppa -ldb2gmf

Compile and Link Options for bldmfcc
The script file contains the following compile options: cob The Micro Focus COBOL compiler. -cx Compile to object module.
The script file contains the following link options: cob Use the compiler to link edit. -x Specify an executable program. checkerr.o Include the object file for error checking. -Lpath Specify the location of the DB2 runtime shared libraries. For example: -L/opt/IBMdb2/v5.0/lib. -ldb2 Link with the DB2 library. -lhppa Specify the HP PA-RISC library (required). -ldb2gmf Link to the DB2 library. Refer to your compiler documentation for additional compiler options.

To build the sample program updat.sqb, do the following:

1. Go to the window in which you set your environment variables by running db2profile. Refer to "Setting Your Environment" if you need more information.

2. Start the database manager on the server, if it is not already running, by entering:

   db2start

3. Build the sample program, connecting to the SAMPLE database, by entering:

   bldmfcc updat

The result is an executable file updat. You can run the executable file against the SAMPLE database to see how it works by doing the following:

1. Go to the window in which you set your environment variables by running db2profile. Refer to "Setting Your Environment" if you need more information.

2. Start the database manager on the server, if it is not already running, by entering:

   db2start

3. Run the program. If you built the updat sample program, enter:

   updat

Building Micro Focus COBOL Stored Procedures

The script file bldmfsp, in sqllib/samples/cobol_mf, contains the commands to build a stored procedure. The script file compiles the stored procedure into a shared library on the server that can be called by a client application.

The first parameter, $1, specifies the name of your source file. The second parameter, $2, specifies the name of the database to which you want to connect. The third parameter, $3, specifies the user ID for the database, and $4 specifies the password. Only the first parameter, the source file name, is required. Database name, user ID, and password are optional. If no database name is supplied, the program uses the default sample database.

The script file uses the source file name, $1, for the shared library name.

#! /bin/ksh # bldmfsp script file # Builds a COBOL stored procedure. # Usage: bldmfsp <stored_proc_name> [ <db_name> [ <userid> <password> ]] # Connect to a database. if (($# < 2)) then db2 connect to sample elif (($# < 3)) then db2 connect to $2 else db2 connect to $2 user $3 using $4 fi # Precompile the program. db2 prep $1.sqb bindfile # Bind the program to the database. db2 bind $1.bnd # Disconnect from the database. db2 connect reset # Set COBCPY to include the DB2 COPY files directory. export COBCPY=$COBCPY:/opt/IBMdb2/v5.0/include/cobol_mf # Compile the checkerr.cbl error checking utility. cob +Z -cx checkerr.cbl # Compile the program. cob +Z -cx $1.cbl # Link the program. ld -b -o $1 $1.o -L/opt/IBMdb2/v5.0/lib -ldb2 -lhppa -ldb2gmf \ -L$COBDIR/coblib -lcobol -lcrtn # Copy the shared library to the sqllib/function subdirectory of the DB2 instance. # Note: this assumes the user has write permission to this directory. eval "H=~$DB2INSTANCE" cp $1 $H/sqllib/function

Compile and Link Options for bldmfsp
The script file contains the following compile options: cob The COBOL compiler. +Z Generate position-independent code. -cx Compile to object module.
The script file contains the following link options: ld Use the linker to link edit. -b Create a shared library rather than a normal executable file. -o Produce an output object file. -Lpath Specify the location of the DB2 runtime shared libraries. For example: -L/opt/IBMdb2/v5.0/lib. -ldb2 Link with the DB2 shared library. -lhppa Specify the HP PA-RISC library (required). -ldb2gmf Link to the DB2 library. -Lpath Specify the location of the COBOL runtime libraries. For example: -L$COBDIR/coblib. Refer to your compiler documentation for additional compiler options.

To build the outsrv.sqb stored procedure, do the following:

1. Go to the window in which you set your environment variables by running db2profile. Refer to "Setting Your Environment" if you need more information.

2. Start the database manager on the server, if it is not already running, by entering:

   db2start

3. Build the stored procedure, connecting to the SAMPLE database, by entering:

   bldmfsp outsrv
   

   The script file copies the stored procedure to the server in the path sqllib/function to indicate that the stored procedure is fenced. If you want the stored procedure to be unfenced, you must move it to the sqllib/function/unfenced directory. These paths are in the home directory of the DB2 instance.

   Note:

   An unfenced stored procedure or UDF runs in the same address space as the database manager and results in increased performance when compared to a fenced stored procedure or UDF, which runs in an address space isolated from the database manager. With unfenced stored procedures or UDFs there is a danger that user code could accidentally or maliciously damage the database control structures. Therefore, you should only run unfenced stored procedures or UDFs when you need to maximize the performance benefits. Ensure these programs are thoroughly tested before running them as unfenced. Refer to the Embedded SQL Programming Guide for more information about fenced and not fenced stored procedures.

4. If necessary, set the file mode for the stored procedure so the DB2 instance can run it.

Once you build the stored procedure outsrv, you can build the client application that calls the stored procedure. You can build outcli using the bldmfcc file. Refer to "Micro Focus COBOL" for details.

To run the stored procedure, do the following :

1. Go to the window in which you set your environment variables by running db2profile.

2. Start the database manager on the server, if it is not already running, by entering:

   db2start

3. Run the sample client application by entering:

   outcli

   The client application passes a variable to the server program outsrv, which gives it a value and then returns the variable to the client application.

Exiting the Stored Procedure

When you develop your stored procedures, exit your stored procedure using the following statement:

move SQLZ-HOLD-PROC to return-code.

With this statement, the stored procedure returns correctly to the client application.

[ DB2 List of Books | Search the DB2 Books ]