Server environment variables

To override the driver resources for all tables in a database, or for specific tables and company numbers in the database, use the environment variables that affect the database driver. You can set the database driver server environment variables in the following three ways:

  • Use the LN Database Definitions (ttaad4510m000) and Tables by Database (ttaad4111m000) sessions.
  • Manually modify the LN tabledef6.2 file.
  • Use the standard operating system mechanism.
Note: Sessions that maintain the tabledef6.2 file will not preserve manually added changes.

To modify database driver behavior, Infor recommends that you use the LN Database Definitions session. If you must configure specific tables and companies for access with a specific database driver, ensure you use the Tables by Database session. These sessions cause environment variables for a particular database driver to override the defaults set in the resource file, and allow you to centrally maintain the environment variables.

The Database Definitions session maintains database driver configuration information in a file called tabledef6.2. This file is stored in the directory %BSE%\lib, which resides on the machine on which the database driver runs. Although Infor recommends that you use the Database Definitions session to maintain this file, advanced users can manually modify this file.

The format of the tabledef6.2 file is as follows: 

<Table Name>:<Company Number>:<Driver Type>(<Environment Variable>= <Value>):<audit Y/N>

If you must specify multiple environment variables for a single table and company number, the variables are listed in the parentheses, separated by commas.

If you must specify all tables or all companies, you must use the asterisk (*) in place of a table name or company number. For example, you can make the following entry in the tabledef6.2 file: 

tccom010:812:oracle8(ORAPROF=0.4):N

In this example, all the queries on table tccom010812 that require at least 0.4 seconds are logged in the ORAPROF file. Note that this table is considered to have a different database definition from other tables. If an Oracle driver is already running, but accesses a different table, a separate driver starts for this table. Environment variables that appear in the driver specifications of the tabledef6.2 file are placed in the driver’s environment before the variables are invoked, so the variables are available to the driver at startup.

If you must modify the default database driver resources for specific users, to set database driver environment variables for specific users, use the standard operating system. These environment variables override the settings created in the Database Definitions session for these users.