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

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.

Required.

The database name.

The default is the data area name. If you want to use another name, enter it with this parameter.

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.

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.

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.

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.

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.

Deprecated.

Do not use this parameter in the db.cfg file. This value is configured in the dataarea.xml file.

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.

For Oracle, replaces the parameters clause of a CREATE INDEX statement for text indexes with the appropriate DDL string entered following this parameter.

Use this parameter instead of TEXT_COMMIT, TEXT_NO_COMMIT, or TEXT_SYNC if you need control over DDL generation.

For Oracle, TRUE means that the text index is updated when the database commitment occurs.

If you need control over DDL generation, use the CTXPARMS parameter.

For Oracle, TRUE means that the text index will never be updated. In this case, the database administrator must perform the text index update.

If you need control over DDL generation, use the CTXPARMS parameter.

For Oracle, specifies an interval upon which the text search index will be created. A recurring job will automatically be created.

For example, this setting of could be added to specify a 30-minute interval for a recurring job that commits any text index changes:

TEXT_SYNC=every "SYSTIMESTAMP + INTERVAL ''30'' MINUTE"

If you need control over DDL generation, use the CTXPARMS parameter.

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.

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:

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:

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

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.

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).

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.

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.

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.

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.

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.

This parameter must be set to a value greater than 1 to enable array inserts. Lawson recommends a setting of 10 for normal use.

When you perform a dbcopy or database reorganization, particularly when a large amount of data has been inserted into the database, you may want to increase the size of this parameter. Lawson recommends increasing it to 50 in these cases. Return the parameter to your normal setting when the dbcopy or the database reorganization completes.

Optional.

Allows values of TRUE (on) or FALSE (off).

Specifies whether the database suspends when a table space runs out of space, to wait for DBA intervention. This feature applies only to Landmark programs (such as the database reorganization utility) execution.

Optional. Requires RESUMABLE set to TRUE.

Specify how long, in seconds, the database waits for DBA intervention.

Optional.

Invoke the database SQL explain plan.