What Is the Lawson Database Driver Configuration File?

Every product line and data area must have an associated IBM database driver configuration file, stored in the following location:

%LAWDIR%\ dataarea \IBM

This file contains information that specify how the Lawson database drivers interact with the IBM database. When a database driver starts, it reads the database driver configuration file. The parameters in the file are exported into the environment of each database driver.

A database driver configuration file is created for a product line by the Lawson installation program based on the responses entered for the installation questions. Data areas are not created by the installation program, so you must create a new IBM file for each new data area you create. How Do I Create a New Data Area?

Changes in the Lawson IBM database driver configuration file can take effect without stopping or starting the database. You need to idle the drivers using the dbadmin utility, however. Editing the Lawson Database Driver Configuration File

Each new connection to the database requires an ibmdb process. Using latm, however, can cause the same ibmdb process to be used if you use an application repeatedly within a specified amount of time.

Note: The database driver configuration file is in the application server and not in the database server.

The following shows a sample Lawson IBM database driver configuration file.

LAWGATENAME=ibmdb.exe
DBNAME=law3gl
DB2INSTANCE=db2v7
LOGINNAME=lawson
PASSWORD=lawsonpw

Setting Batch or Online Connect Parameters

There are two ways to create a Lawson IBM Configuration file. Specify one set of connect parameters for the entire system or specify two sets of parameters, one for batch programs and one for online programs.

Example 1: Single connection parameters for online and batch programs (AIX client shown)

LAWGATENAME=ibmdb.exe
DBNAME=law3gl
LOGINNAME=lawson
PASSWORD=lawsonpw
DB2INSTANCE=db2v7

Example 2: Separate connection parameters for online and batch programs (AIX client connecting to an IBM DB2 O/S 390 server shown)

LAWGATENAME=ibmdb.exe
DB390NAME=law3gl
LOGINNAME=lawson
PASSWORD=lawsonpw

DB2INSTANCE=db2v7
DBNAME=lawgl
LIBPATH=/opt/db2v7/sqllib/lib:/usr/lib:/lib

[BATCH]
DB2INSTANCE=db2v7b
DBNAME=lawglb
LIBPATH=/opt/db2v7b/sqllib/lib:/usr/lib:/lib