| Note: | Before using the SPARCompiler FORTRAN compiler, make sure db2ln was run when DB2 was installed. This command links the DB2 header files into /usr/include. If this has not been done, SPARCompiler FORTRAN may not be able to find the header files because it does not have an environment variable or a switch such as -l to locate them. |
The script file bldf77, in sqllib/samples/fortran, contains the commands to build a sample FORTRAN 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
# bldf77 script file
# Builds a FORTRAN program that contains embedded SQL
# Usage: bldf77 <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.sqf bindfile
# Bind the program to the database.
db2 bind $1.bnd
# Disconnect from the database.
db2 connect reset
# Compile the util.f error-checking utility.
f77 -w -c util.f
# Compile the program.
f77 -w -c $1.f
# Link the program.
f77 $1.o util.o -L/opt/IBMdb2/v5.0/lib -R/opt/IBMdb2/v5.0/lib \
-R/opt/SUNWspro/lib -ldb2 -o $1
|
| Compile and Link Options for bldf77 |
|---|
|
The script file contains the following compile options:
|
|
The script file contains the following link options:
Refer to your compiler documentation for additional compiler options.
|
To build the sample program updat.sqf, do the following:
db2start
bldf77 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 :
db2start
updat
| Note: | To build FORTRAN applications that do not contain embedded SQL, you can use the script file bldf77api. It contains the same compile and link options as bldf77, but does not connect, prep, bind, or disconnect from the SAMPLE database. It is used to compile and link the DB2 API sample programs written in FORTRAN. |
The script file bldf77sp, in sqllib/samples/fortran, 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 the 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 # bldf77sp script file # Builds a FORTRAN stored procedure # Usage: bldf77 <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.sqf bindfile # Bind the program to the database. db2 bind $1.bnd # Disconnect from the database. db2 connect reset # Build the stored procedure. f77 -w -G $1.f -o $1 # 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 bldf77sp |
|---|
|
The script file contains the following compile options:
Refer to your compiler documentation for additional compiler options.
|
To build the stored procedure outsrv.sqf do the following:
db2start
bldf77sp 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. |
Once you build the stored procedure outsrv, you can build outcli that calls the stored procedure. You can build outcli using the bldf77 script file. Refer to "SPARCompiler FORTRAN" for details.
To run the stored procedure, do the following :
db2start
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.