What Are the Parameters in the Lawson Database Interface Configuration File?

The following topics describe the parameters in the Lawson db.cfg database interface configuration file:

Parameters that Specify Your Database Implementation

The parameters in the following table configure the database.


Parameter	Description
`[SECTION]`	A section name to group parameters. At least one entry is required; if your product line configuration includes multiple databases, you can have more than one entry. If you specify a value for dbname in %LASRCDIR%\dict\dataarea.xml, the section name should match the dbname. If you do not specify a value for dbname in dataarea.xml, the section name should be one of the following, depending on your database type. `COMMON` Any parameters placed in this section will apply to all database instances defined in the db.cfg file. `MSFDB` Indicates the database in this section is a Microsoft SQL Server database. `ORADB` Indicates the database in this section is an Oracle database. `UPGDB` (Deprecated) This parameter allows one additional database connection. You must specify the database type within this section using the DBTYPE parameter.
`DBNAME`	Required. The database name. The default is the data area name. If you want to use another name, enter it with this parameter.
`DBSERVER`	`DBSERVER` is the name of the server where your database is installed (or the alias). Enter a value for the server you need access to.
`DBTYPE`	Deprecated. Formerly used to indicate the type of database for this set of data. Normally this parameter was only used when the database section is designated `[UPGDB]`. This value would match the value of the dbtype parameter in the `dataarea.xml` file. You can change that value using the `changeda` command.
`PORT`	The port number for the database server.
`LOGINNAME`	This is the user name used when the database driver connects to the database. The default is `lawson`. The parameter is not required if SERVICENAME is specified.
`PASSWORD`	This is the password for `LOGINNAME`, which the database driver uses when it connects to the database. The default is `lawson`. The parameter is not required if SERVICENAME is specified.
`SERVICENAME`	This parameter specifies the name of the database service for this data area. If you do not enter a database service, the login procedure defaults to using the LOGINNAME and PASSWORD specified in this file.
`SCHEMA`	Deprecated. Do not use this parameter in the `db.cfg` file. This value is configured in the `dataarea.xml` file.
`FILEGROUPS`	Optional. The default is `FALSE`, but it is commented out as shown below: `#FILEGROUPS=FALSE` `TRUE` places Lawson tables and indexes in database file groups. `FALSE` does not use database file groups but instead places all tables and indexes into the `PRIMARY` file groups.

Parameters that Support Text Search

The parameters in the following table configure the Lawson database driver to use text indexing and search features provided by the database.

Parameter Description

TEXT_SERVER For SQL Server, the name of the server where the database with the text search feature was installed.

CHANGE_TRACKING

For SQL Server, specifies whether or not SQL Server maintains a list of all changes to the indexed data. The default is AUTO. The following values are supported:

MANUAL - Specifies that the change-tracking log will be propagated either on a schedule using SQL Server Agent, or manually by the user.
AUTO - Specifies that SQL Server automatically updates the full-text index as the data is modified in the associated tables. If AUTO has a significant performance impact, consider using textindexjob to drop and create jobs that populate text indexes.
OFF [ , NO POPULATION] - OFF specifies that Microsoft SQL Server does not keep a list of changes to the indexed data. When NO POPULATION is also specified, Microsoft SQL Server does not populate an index after it is created.

The NO POPULATION option can be used only when CHANGE_TRACKING is OFF.

Note:

See the Microsoft SQL Server documentation for more complete information on these parameters.

FREQ_TYPE=nnn

For SQL Server, an integer value (nnn) that indicates the type of schedule, or how often the job is to be executed.

The default value is 0 (zero). Valid values are shown in the following table:


1	Once
4	Daily
8	Weekly
16	Monthly
32	Monthly, relative to the value specified for FREQ_INTERVAL.
64	Run when the SQL Server Agent service starts.
128	Run when the computer is idle.

FREQ_INTERVAL=nn

For SQL Server, an integer value that indicates the day the job is executed. The default value is 0 (zero). The value specified for FREQ_INTERVAL is related to the FREQ_TYPE. The interpretation of the FREQ_INTERVAL value (nnn) is shown in the following table:

When FREQ_TYPE=1 (once)

The frequency interval is unused.

When FREQ_TYPE=4 (daily)

The job is scheduled to run every nn days.

When FREQ_TYPE=8 (weekly)

The job is scheduled to run on one or more of the following days. Combine days with an OR logical operator.


1	Sunday
2	Monday
4	Tuesday
8	Wednesday
16	Thursday
32	Friday
64	Saturday

When FREQ_TYPE=16 (monthly)

The job is scheduled to run on the nnth day of each month.

For example, when FREQ_INTERVAL= 14 and FREQ_TYPE=16, the job will be scheduled to run on the 14th day of each month.

When FREQ_TYPE=32 (monthly relative)

The job is scheduled to run on one of the following days:


1	Sunday
2	Monday
3	Tuesday
4	Wednesday
5	Thursday
6	Friday
7	Saturday
8	Day
9	Weekday
10	Weekend day

When FREQ_TYPE=64 (when the SQL Server Agent service starts)

The frequency interval is unused.

When FREQ_TYPE=128 (when the computer is idle)

The frequency interval is unused.

FREQ_SUBDAY_INTERVAL=nn For SQL Server, an integer value that specified the number of periods (FREQ_SUBDAY_TYPE) between each execution of the job. The default is zero (0).

FREQ_SUBDAY_TYPE=type

For SQL Server, an integer value that specifies the units for FREQ_SUBDAY_INTERVAL. Use one of the following values:


0x1	Run at a specified time.
0x4	The value of FREQ_SUBDAY_INTERVAL is measured in minutes.
0x8	The value of FREQ_SUBDAY_INTERVAL is measured in hours.

FREQ_RELATIVE_INTERVAL= nnn

For SQL Server, an integer value that indicates the occurrence of the interval, when the FREQ_TYPE specification is 32 (monthly relative).

For example, if FREQ_RELATIVE_INTERVAL is set to 2, FREQ_TYPE is set to 32, and FREQ_INTERVAL is set to 3, the scheduled job would occur on the second Tuesday of each month.


1	First
2	Second
4	Third
8	Fourth
16	Last

FREQ_RECURRENCE_FACTOR= nnn

For SQL Server, an integer value that specifies the number of weeks or months between the scheduled execution of the job.

FREQ_RECURRENCE_FACTOR can be used only when FREQ_TYPE is set to 8, 16, or 32.

The default is 0 (zero).

ACTIVE_START_DATE= yyyymmdd

For SQL Server, the date job execution will begin.

If ACTIVE_START_DATE is set, the date must be greater than or equal to 19900101.

ACTIVE_END_DATE= yyyymmdd For SQL Server, the date job execution will stop.

ACTIVE_START_TIME= hhmmss

For SQL Server, the time of day that job execution will begin. This value is used only on valid days between the ACTIVE_START_DATE and ACTIVE_END_DATE.

Times are formatted based on a 24-hour clock.

ACTIVE_END_TIME=hhmmss

For SQL Server, the time of day that job execution will end. This value is used only on valid days between the ACTIVE_START_DATE and ACTIVE_END_DATE.

Times are formatted based on a 24-hour clock.

Parameters that Configure Record Caching

Use the following parameters to enable record caching.


Parameter	Description
`ARRAYBUFSIZE`	Indicates the maximum number of rows to be fetched at a time from the database. The default is 10 rows. The setting for this variable in the database driver configuration file applies to all files in the data area.
`INSERTBUFSIZE`	Indicates the maximum number of rows to be buffered in the database driver before an array insert flushes data out to the database. Lawson recommends a setting of 1 (one) for Microsoft SQL Server.