Configuring DBEngine Parameters

There are three types of DBEngine parameter files that you can configure, depending on your needs:

The common parameter file (DATA/ENGINE/CONTROL)

Use to specify availability, checkpoint frequency, etc., for all databases that do not set the parameter value in a database-specific parameter file or a logical–database-specific parameter file. The DATABridge license KEY should be specified in the common parameter file.

A database-specific parameter file (DATA/ENGINE/databasename/CONTROL)

Use to specify availability, checkpoint frequency, etc., at the database level. Options in the database-specific parameter file override the options in the common parameter file.

A logical–database-specific parameter file (DATA/ENGINE/databasename/logicaldatabasename/CONTROL

Use this type of DBEngine parameter file to specify availability, checkpoint frequency, etc., at the logical database level. Options in the logical–database-specific parameter file override the options in the database-specific parameter file and the options in the common parameter file.

DBEngine reads the database-specific parameter file and the logical–database-specific parameter file, if they exist, in addition to the common parameter file (DATA/ENGINE/CONTROL). The database-specific parameter file and the logical–database-specific parameter file can have the same options as the common parameter file. Options in the database-specific parameter file and the logical–database-specific parameter file override the options in the common parameter file. This allows you to configure different options for different databases (for example, to have different checkpoint frequencies).

Parameter files must be visible to DBEngine and in one of the following locations:

  • Under the current usercode (that is, the accessory’s usercode)
  • Under the DBEngine codefile’s usercode and pack name
  • Under the usercode of the DESCRIPTION file.