Parameter Change Confirmation 

Use

You confirm all changes to the parameters and transfer them to the parameter file. Before storing them the check status of all parameters is verified.

If you specify the NOCLOSE option, the parameter session remains open (Opening a Parameter Session) after the parameters have been stored. If you do not specify this option, the parameter session is closed after the parameters have been stored.

The changed values in the parameter file are effective when the database instance is restarted.

Prerequisites

You have changed parameter values in a parameter session.

You have the DBM operator authorization ParamCheckWrite.

Syntax

param_commitsession [NOCLOSE]

Successful Reply

The system outputs an OK message.

Error Message

Execution of the command is refused:

ERR
14,ERR_XPCHECK_CN00 : param check failure/request
<identifier> <checkstatus>
<user_value>
<computed_value>

Values for the individual fields of the reply

<checkstatus>

The following check status may occur:

Mandatory: An obligatory parameter has been assigned a blank value.

Constraint: a constraint could not be fulfilled.

Request: the user input deviates both from the value transferred to the system and confirmed by it earlier, as well as from the system default value.

<user_value>

Value that the user entered with param_put.

<computed_value>

Default value calculated by the system

Check status request is output only if the user entry varies from the value of the parameter in the parameter file.

Continuation of Procedure

If the check status is a request, you can correct the error as follows:

Specify the valid value with param_putconfirm (Correcting Parameters). Otherwise the system default <computed_value> is used this for parameter for all further calculations of other parameters.

In the following cases the new parameter is refused:

- The parameter has the value NOBODY for the CHANGE property

- - The parameter has the value NO for the property MODIFY and the parameter file was already checked by the kernel (parameter __PARAM_CHANGED___ exists)

- You are dealing with a devspace parameter (Devspace property = Yes) and there are changed kernel parameters in the parameter file (Devspace property= No), that have not yet been checked by the kernel
(Exception: You are creating a new database instance)

- The parameter is a kernel parameter and devspace parameters have already been changed, but not yet checked by the kernel.