UNIX Installation Steps

The Acu4GL for DB2 product on UNIX is an add-on module that must be linked with the ACUCOBOL-GT runtime system. For this reason, you'll need a C compiler to install the Acu4GL product. To interface, you must use the ACUCOBOL-GT compiler and runtime, and the version of the runtime must match the version of Acu4GL.

The Acu4GL product is shipped using either TAR or CPIO format, depending on the type of machine you have. The label on the medium shipped to you tells you which format has been used.

From your Acucorp directory, choose where you want to install the Acu4GL product (or create a new directory for it) and then enter one of the following commands:

tar xfv device

Or:

cpio -icvBd < device

This will copy the files from the distribution medium to your ACUCOBOL-GT directory structure. device is the appropriate hardware device name (for example, /dev/rdiskette or /dev/rmt0). Sites using Texas Instruments System 1500 should add an uppercase "T" to the cpio options (-icvBdT).

Licenses

Each Acu4GL product has its own license file, which must be located in the same directory as the ACUCOBOL-GT runtime. For DB2, the license file is distributed with the name "runcbl.klc".

Installation Steps

Install DB2. The DB2 RDBMS, version 6.01 must be installed and configured prior to the installation of Acu4GL for DB2.
Create a new runtime system by performing the following steps.
Note: In the following directions, the term "runtime system" refers to the runtime shared object on systems where the ACUCOBOL-GT runtime is a shared object and to runcbl on other systems, where the runtime is static. The runtime is a shared object on the following systems: AIX 5.1 and later, HP-UX 11 and later, and Solaris 7 and later. To check, look at the contents of the "lib" subdirectory of your ACUCOBOL-GT installation. If the files "libruncbl.so" or "libruncbl.sl" reside in that directory, the runtime is a shared object on your system.
1. Link the runtime system. Edit the Makefile in the "lib" subdirectory. Change the CFLAGS file to read as follows:
```
CFLAGS = $(ACUSERVER_FLAGS) $(ACUCONNECT_FLAGS) 
   $(ACUSQL_FLAGS) -DACU4GL -DUSE_DB2 
```
2. Edit the FSI_SUBS line to read as follows:
```
FSI_SUBS = a4db2.o 
```
3. Edit the FSI_LIBS line to read as follows:
```
FSI_LIBS = $(ACU_LIBDIR)/libexpat.a <ibm DB2
  directory>/lib/libdb2.so 
```
4. Make sure you are in the directory containing the ACUCOBOL-GT runtime system. Then, at the UNIX prompt, enter the following command:
```
make
```
  This compiles "sub.c" and "filetbl.c", and then links the runtime system.
  
  Note: Make sure you have set all of the flags specific to your platform correctly before you relink your library and object files. If the make fails because of an out-of-date symbol table, execute the following command: ranlib *.a and then execute the make again. If the make fails for any other reason, call Technical Services.
Veryify the link. Enter the following command:
```
./runcbl -vv
```
This returns version information on all of the products linked into your runtime system. Make sure it reports the version of Acu4GL for DB2.

Shared Libraries

If you have relinked the ACUCOBOL-GT runtime and receive an error message of this type when you try to execute it:

"Could not load library; no such file or directory" "Can't open shared library . . . "

Tthis may mean that your operating system is using shared libraries and cannot find them. This can occur even if the shared libraries reside in the same directory in which you are currently located.

Set the environment variable LD_LIBRARY_PATH to find these shared libraries.