Variables in the database driver configuration file

msfdb2000

The name of the database driver executable, used between the Lawson applications and the Microsoft SQL Server database.

Required.

The database name.

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

Required.

Required.

Enter this parameter when using the USE_CFG_FILE login procedure―. Do not use the LOGINNAME parameter for any other login procedure.

This is the user name used when the database driver connects to the Microsoft SQL Server database. The default is lawson.

Required.

Enter this parameter when using the USE_CFG_FILE login procedure―. Do not use the PASSWORD parameter for any other login procedure.

This is the password for LOGINNAME, which the database driver uses when it connects to Microsoft SQL Server. The default is lawson.

This parameter is required when Lawson Security and Resource Management are implemented to manage users and secure data.

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 USE_CFG_FILE. You can either specify a LOGINNAME and PASSWORD in the MICROSOFT file, or configure the system so that each individual user accesses the database with a unique user name.

Required.

This parameter is the database owner. If the tables were not created by the user named in LOGINNAME, set SCHEMA to the name of the user who created the tables.

If SCHEMA is not specified in the MICROSOFT file, the database driver (msfdb2000) uses these methods to determine a value for the table owner:

• If defined in the MICROSOFT file, the LOGINNAME value from the MICROSOFT database driver configuration file defaults for the SCHEMA value.

• If the LOGINNAME parameter is not defined, the database login name specified for the database service defaults to the SCHEMA value when using the USE_PRIVILEGED_ID database authentication option.

• If the USE_USER_ID database authentication option for Lawson Security is used in your system or if Lawson Security is not implemented in your system, the lawson user defaults for the SCHEMA value.

If SCHEMA is not specified in the MICROSOFT file, the database utilities (bldmsf2000ddl, bldmsf2000sec, verifymsf2000, or msf2000du) use these methods to determine a value for the table owner:

• If defined in the MICROSOFT file, the LOGINNAME value from the MICROSOFT database driver configuration file defaults for the SCHEMA value.

• If the LOGINNAME and SCHEMA parameters are not defined, the database login name must be specified on the command line when running one of these utilities.

Optional.

The default is FALSE, but it is commented out as shown below:

#FILEGROUPS=FALSE

TRUE places 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.

Optional.

Indicates the maximum number of rows to be fetched at a time from the database server. The default is 10 rows.

The setting for this variable in the database driver configuration file applies to all files in the data area or data ID unless a variable specific to a program has been created. When a variable specific to a program has been created, it overrides the setting in the database driver configuration file.

Optional. Only applies to specific utilities (dbreorg, dbcopy, importdb -b, impcsv -b) and batch tokens.

Indicates the maximum number of rows to be buffered in the database driver before an array insert flushes data out to the database. This parameter must be set to a value greater than 1 to enable array inserts. Lawson recommends a setting of no larger than 10 for normal use.

This parameter should not be included in the MICROSOFT file for normal Lawson applications data processing through the database driver (msfdb2000).

However, when you perform a dbcopy or dbreorg, particularly when a large amount of data has been inserted into the database, 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 dbreorg completes.

See Editing the Lawson Database Driver Configuration File

Applications commit records to the database at different intervals. When a commit occurs, the insert buffer is flushed. Batch tokens typically commit every 50 records, importdb commits every 100, and dbcopy commits every 3000 records. Setting INSERTBUFSIZE higher than the commit interval results in buffered inserts of the commit interval size.

As with ARRAYBUFSIZE, you can set this variable to control a specific program. The program-specific setting overrides the setting in the database driver configuration file.