Parameter Properties 

Property

Explanation

Possible values

CASESENSITIVE

Upper/lower case distinctions are relevant (for example, file names under UNIX)

YES | NO

CHANGE

Parameter can be changed

YES | NO

CLEAR

In a new installation, the parameter must not be copied from another database instance (examples: database instance name, devspaces)

YES | NO

DEVSPACE

Type of parameter (Yes: devspace parameter, NO: kernel parameter)

YES | NO

DISPLAYNAME

Character string (may include spaces) displayed in place of the parameter name in the DBMGUI

 

DYNAMIC

Parameter has a position indicator in the description file (for example: DATADEV_?)
In the parameter file such parameters become, for example, DATADEV_00, DATADEV_01, and so on)

YES | NO

GROUP

Assignment to a group for display in the Database Manager GUI
GENERAL: General database parameter, visible
EXTENDED: Special database parameter, visible
SUPPORT: Parameter list specified only for support, visible
NO: The parameter is not accessible using the Database Manager GUI
INFO: The parameter contains special information for users

GENERAL
| EXTENDED
| SUPPORT
| NO
| INFO

INSTANCES

Instance type for which the parameter is relevant

No entry: Parameter is generally valid

LVC | OLTP | BW | CS

INTERN

The value is only in the description file, not in the parameter file (Configuring Database Instances)

YES | NO

LASTKNOWNGOOD

Valid value of the parameter with which the database instance was last started

 

MANDATORY

Mandatory parameter

YES | NO

MAX

Maximum parameter value

 

MIN

Minimum parameter value

 

MODIFY

You can still change the parameter after the database instance has been generated (for example: RUNDIRECTORY: NO)

YES | NO

OVERRIDE

You can overwrite the DBM Server’s proposed value

YES | NO | HIGHER

VALUESET

Permitted value set for a parameter
The individual values must be separated by spaces or tabs. Permitted string constants in character string parameters must be set off in quotation marks.