This section includes the following topics:
The script file bldf77api, in sqllib/samples/fortran, contains the commands to build a DB2 API program. The parameter, $1, specifies the name of your source file.
#! /bin/ksh # bldf77api script file # Builds a Fortran DB2 API program # Usage: bldf77api <prog_name> # Set DB2PATH to where DB2 will be accessed. # The default is the standard instance path. DB2PATH=$HOME/sqllib # Compile the util.f error-checking utility. f77 -I$DB2PATH/include -c util.f # Compile the program. f77 -I$DB2PATH/include -c $1.f # Link the program. f77 -o $1 $1.o util.o -L$DB2PATH/lib -R$DB2PATH/lib -ldb2 |
| Compile and Link Options for bldf77api |
|---|
|
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 client from the source file client.f, enter:
bldf77api client
The result is an executable file, client. You can run the executable file against the sample database by entering the executable name:
client
The script file bldf77, in sqllib/samples/fortran, contains the commands to build an embedded SQL 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> ]] # Set DB2PATH to where DB2 will be accessed. # The default is the standard instance path. DB2PATH=$HOME/sqllib # 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 -I$DB2PATH/include -c util.f # Compile the program. f77 -I$DB2PATH/include -c $1.f # Link the program. f77 -o $1 $1.o util.o -L$DB2PATH/lib -R$DB2PATH/lib -ldb2
| 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 from the source file updat.sqf, enter:
bldf77 updat
The result is an executable file, updat. You can run the executable file against the sample database by entering the executable name:
updat
The script file bldf77sp, in sqllib/samples/fortran, contains the commands to build an embedded SQL 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> ]] # Set DB2PATH to where DB2 will be accessed. # The default is the standard instance path. DB2PATH=$HOME/sqllib # 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 -G $1.f -o $1 -I$DB2PATH/include # Copy the shared library to the sqllib/function subdirectory of the DB2 instance. # This assumes the user has write permission to this directory. rm -f $DB2PATH/function/$1 cp $1 $DB2PATH/function
| Compile Options for bldf77sp |
|---|
|
The script file contains the following compile options:
Refer to your compiler documentation for additional compiler
options.
|
To build the sample program outsrv from the source file outsrv.sqf, enter:
bldf77sp outsrv
The script file copies the stored procedure to the server in the path sqllib/function. For DB2DARI parameter style stored procedures where the invoked procedure matches the shared library name, this location indicates that the stored procedure is fenced. If you want this type of stored procedure to be unfenced, you must move it to the sqllib/function/unfenced directory. For all other types of DB2 stored procedures, you indicate whether it is fenced or not fenced with the CREATE FUNCTION statement in the calling program. For a full discussion on creating and using the different types of DB2 stored procedures, please see the "Stored Procedures" chapter in the Application Development Guide.
| Note: | An unfenced stored procedure runs in the same address space as the database manager and results in increased performance when compared to a fenced stored procedure, which runs in an address space isolated from the database manager. With unfenced stored procedures there is a danger that user code could accidentally or maliciously damage the database control structures. Therefore, you should only run unfenced stored procedures when you need to maximize the performance benefits. Ensure these programs are thoroughly tested before running them as unfenced. Refer to the Application Development Guide for more information. |
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 outcli that calls the stored procedure. You can build outcli using the script file bldf77. Refer to "Embedded SQL Applications" for details.
To call the stored procedure, 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.