Building Applications for UNIX** Environments

IBM XL FORTRAN for AIX

The script file bldxlf, 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. 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 # bldxlf script file # Build sample FORTRAN program containing embedded SQL. # Usage: bldxlf <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. xlf -I/usr/lpp/db2_05_00/include -c util.f # Compile the program. xlf -I/usr/lpp/db2_05_00/include -c $1.f # Link the program. xlf -o $1 $1.o util.o -ldb2 -L/usr/lpp/db2_05_00/lib

Compile and Link Options for bldxlf

The script file contains the following compile options:

xlf
The FORTRAN compiler.
-Ipath
Specify the location of the DB2 include files. For example: -I/usr/lpp/db2_05_00/include.
-c
Perform compile only; no link. This book assumes that compile and link are separate steps.

The script file contains the following link options:

xlf
Use the compiler to link edit.
-o filename
Specify the name of the executable program.
util.o
Include the object file for error-checking.
-ldb2
Link with the database manager library.
-Lpath
Specify the location of the DB2 runtime shared libraries. For example: -L/usr/lpp/db2_05_00/lib. If you do not specify the -L option, the compiler assumes the following path: /usr/lib:/lib.

Refer to your compiler documentation for additional compiler options.

Compile and Link Options for bldxlf
The script file contains the following compile options: `xlf` The FORTRAN compiler. `-I`path Specify the location of the DB2 include files. For example: `-I/usr/lpp/db2_05_00/include`. `-c` Perform compile only; no link. This book assumes that compile and link are separate steps.
The script file contains the following link options: `xlf` Use the compiler to link edit. `-o` filename Specify the name of the executable program. `util.o` Include the object file for error-checking. `-ldb2` Link with the database manager library. `-L`path Specify the location of the DB2 runtime shared libraries. For example: `-L/usr/lpp/db2_05_00/lib`. If you do not specify the `-L` option, the compiler assumes the following path: `/usr/lib:/lib`. Refer to your compiler documentation for additional compiler options.

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

Go to the window in which you set your environment variables by running db2profile. Refer to "Setting Your Environment" if you need more information.
Start the database manager on the server, if it is not already running, by entering:
```
db2start
```
Build the sample program, connecting to the SAMPLE database, by entering:
bldxlf 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 :

Go to the window in which you set your environment variables by running db2profile.
Start the database manager on the server, if it is not already running, by entering:
```
db2start
```
Run the program. If you built the updat sample program, enter:
```
updat
```

Note: To build FORTRAN applications that do not contain embedded SQL, you can use the script file bldxlfapi. It contains the same compile and link options as bldxlf, 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.

Building FORTRAN Stored Procedures

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

The script file uses the source file name, $1, for the shared library name, and for the main entry point to the shared library.

#! /bin/ksh # bldxlfsrv script file # Builds a FORTRAN stored procedure. # Usage: bldxlfsrv <stor_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 # Compile the util.f error-checking utility. xlf -I/usr/lpp/db2_05_00/include -c util.f # Compile the program. xlf -I/usr/lpp/db2_05_00/include -c $1.f # Link the program using the export file $1.exp, # creating a shared library called $1 with the main # entry point $1. xlf -o $1 $1.o util.o -ldb2 -L/usr/lpp/db2_05_00/lib \ -H512 -T512 -bE:$1.exp -e $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 bldxlfsrv

The script file contains the following compile options:

xlf
The FORTRAN compiler.
-Ipath
Specify the location of the DB2 include files. For example: -I/usr/lpp/db2_05_00/include.
-c
Perform compile only; no link. This book assumes that compile and link are separate steps.

The script file contains the following link options:

xlf
Use the compiler to link edit.
-o filename
Specify the output as a shared library file.
util.o
Include the object file for error-checking.
-ldb2
Link with the database manager library.
-Lpath
Specify the location of the DB2 runtime shared libraries. For example: -L/usr/lpp/db2_05_00/lib. If you do not specify the -L option, the compiler assumes the following path: /usr/lib:/lib.
-H512
Specify output file alignment.
-T512
Specify output file text segment starting address.
-bE:filename.exp
Specify an export file. The export file contains a list of the stored procedures.
-e entry
Specify the default entry point to the shared library.

Refer to your compiler documentation for additional compiler options.

Compile and Link Options for bldxlfsrv
The script file contains the following compile options: `xlf` The FORTRAN compiler. `-I`path Specify the location of the DB2 include files. For example: `-I/usr/lpp/db2_05_00/include`. `-c` Perform compile only; no link. This book assumes that compile and link are separate steps.
The script file contains the following link options: `xlf` Use the compiler to link edit. `-o` filename Specify the output as a shared library file. `util.o` Include the object file for error-checking. `-ldb2` Link with the database manager library. `-L`path Specify the location of the DB2 runtime shared libraries. For example: `-L/usr/lpp/db2_05_00/lib`. If you do not specify the `-L` option, the compiler assumes the following path: `/usr/lib:/lib`. `-H512` Specify output file alignment. `-T512` Specify output file text segment starting address. `-bE:`filename.exp Specify an export file. The export file contains a list of the stored procedures. `-e` entry Specify the default entry point to the shared library. Refer to your compiler documentation for additional compiler options.

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

Go to the window in which you set your environment variables by running db2profile. Refer to "Setting Your Environment" if you need more information.
Start the database manager on the server, if it is not already running, by entering:
```
db2start
```

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

bldxlfsrv 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.

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 bldxlf script file. Refer to "IBM XL FORTRAN for AIX" for details.

To run the stored procedure, do the following:

Go to the window in which you set your environment variables by running db2profile.
Start the database manager on the server, if it is not already running, by entering:
```
db2start
```
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.

Using the IBM XL FORTRAN for AIX Compiler

If you develop applications that contain embedded SQL and DB2 API calls, and you are using the IBM XL Fortran for AIX compiler, keep the following points in mind:

The Fortran compiler (xlf) treats lines with a D or d in column 1 as conditional lines. You can either compile these lines for debugging or treat them as comments.
The precompiler always treats lines with a D or d in column one as comments.
The compiler is case insensitive by default. You can make it case sensitive by using a compiler option.
SQL keywords are always case insensitive. If you make the compiler case sensitive, you must enter all Fortran keywords in lowercase. Additionally, identifier references must match the case of declarations.
A single tab introduces source lines such that the following character is positioned at column 7. The compiler treats tabs in locations other than between columns 1-6, and in character constants, as blanks.
You cannot use the following data declaration keywords in host variable declarations: POINTER, BYTE, STATIC, and AUTOMATIC.
Pass by-value arguments using %VAL() and by-reference arguments using %REF(). The API Reference uses this syntax in the Fortran DB2 API examples.
You cannot use the XL FORTRAN for AIX free-format option in .sqf files.
The DB2 precompiler is case insensitive, but XL Fortran for AIX may not be, depending on compiler options. Therefore, do not use host variables with the same spelling and expect the case of the letters in the variable to make them unique. For example, the precompiler treats NAME, name, and Name as equal.
Similarly, the following keywords are recognized to different extents by the precompiler, and always in a case insensitive manner:
```
@PROCESS            END            IMPLICIT      SUBROUTINE
AUTOMATIC           ENDDO          INTEGER
BLOCKDATA           ENDFILE        LOGICAL
BYTE                ENDIF          PARAMETER
CHARACTER           ENTRY          POINTER
COMPLEX             FORMAT         PROGRAM
DOUBLECOMPLEX       FUNCTION       REAL
DOUPLEPRECISION     IF             STATIC
```
The precompiler allows only digits, blanks, and tab characters within columns 1-5 on continuation lines.
You cannot use the \ character to include string delimiters within strings. For example, use the strings 'the''character' or "the""character" instead of 'the\'character' or "the\"character".
FORTRAN .sqf source files do not support Hollerith constants.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]