Server environment variables

Environment variables that affect the database driver can be used to override the driver resources for all tables in a database or for specific tables and company numbers within the database. To set the database driver server environment variables, you can use:

  • The LN Database Definitions (ttaad4510m000) session and Tables by Database (ttaad4111m000) session.
  • The Infor Management console to modify environment variables for each LN instance.
  • The standard operating system mechanism for setting environment variables.

The LN Database Definitions session is the recommended method to modify database driver behavior. When specific tables and companies are to be configured for access with a specific database driver, the Tables by Database session must be used. These sessions allow environment variables for a particular database driver to be written to the following table definitions files:

  • %BSE%\lib\tabledef6.1 for Infor Baan IVc
  • %BSE%\lib\tabledef6.2 for Infor Baan 5.0/LN

Environment variables present in the driver specifications in the table definitions file are passed to the driver and added to its environment after startup. Environment variables that correspond to resources override the defaults set in the resource file. This method allows the environment variables to be maintained centrally.

The Database Definitions session maintains database driver mapping and configuration information in the table definition file. This file is stored in the directory %BSE%\lib residing on the application server machine where the database driver runs. The format of entries in the table definition file is: 

<table name>:<company number>:<driver type>(<environment variable>=<value>)

The “<driver type>” and optional “(<environment variable>=<value>)” portions are collectively known as the driver specification. If multiple environment variables are to be specified for a single table and company number, they are listed within the parentheses and separated by commas. If all tables or all companies are to be specified, the asterisk (*) is used as a wildcard in place of table name or company number. For example, the following entry can be made in the table definition file: 

tccom010:812:msql7(MSQL_LOCK_TIMEOUT=60,MSQL_DSN=SQLSRV)

In this example all the queries on table tccom010812 are sent to an LN SQL Server driver. The MSQL_LOCK_TIMEOUT and MSQL_DSN settings specified are added into the driver’s environment after it is started.

Note: Tabledef entries with different driver specifications are considered to have a different database definition from entries. If an MSQL driver is already running, but has a different driver specification, a separate driver is started for this entry. Environment variables that appear in the driver specifications of the table definition file are placed in the driver’s environment after it is invoked. The variables are available to the driver at startup.

If the default database driver resources must be modified for specific users, the standard operating system method can be used to set database driver environment variables on a per-user basis. These environment variables override the resource settings for these users.