Additional System Profile Parameters
The most important system profile parameters for updates are described in the section entitled
Main System Profile Parameters for Updates. The system also supports additional parameters, which can be useful for correcting errors and optimizing update performance. These parameters are described below.You can access further detailed information if you call up transaction RZ11, search for the parameters and then display the documentation.
Parameter |
Description |
rdisp/vb_context |
You can use this parameter to specify how V1 update dispatching takes place. The parameter is interpreted as a bit mask:Bit 0: the DB group is to be retained during dispatching (see also Configuring Update Groups)Bit 1: an update server on which the current language is installed must be selected for dispatching. The default value 3 (both bits set) specifies, for example, that an update server is selected for update dispatching, which is in the same DB group, and on which the current language is installed. Changes should only be made in order to correct errors. Value range: 0 - 3 |
rdisp/vb2_context |
This parameter controls update dispatching for V2 updates (see rdisp/vb_context). |
rdisp/vb_factor |
Update request dispatching takes place in accordance with a simple procedure, which is described in Update Dispatching with Load Balancing.The parameter rdisp/vb_factor can be used to influence the number of update work processes relevant for dispatching in order to assign a greater number of update requests to servers that are particularly fast. The number of requests relevant for dispatching is the product of the current number of update processes and the value of rdisp/vb_factor. After the V1 part of an update request has been processed the V2 part is dispatched in the same way. The parameter value must have the following syntax: rdisp/vb_factor = S=<instance_name>,F=<factor>; … S=<instance_name>,F=<factor>;
rdisp/vb_factor = S=host1_C11_00,F=2.0; S=host2_C11_00, F=2.5; |
rdisp/vb_key_comp |
You can use the parameter rdisp/vb_key_comp to change the structure of the update key (see Displaying the Update Header). The key usually comprises the date, time, microseconds, host name, system number and work process number.In order to structure the index more favorably, you can move variable components to the start of the key by setting the parameter accordingly. |
rdisp/vb_refresh_info |
This parameter defines the time interval after which the context of an update server is redetermined. The context includes the number of server update work processes as well as the code page and DB node of the server. The context of an update server can change, for example, as a result of a new operation mode being set. This is why the context is reread every hour. |
rdisp/vb_v2_start |
This parameter specifies whether the V2 phase of an update request is started automatically at the end of the V1 phase or by a background job after a delay. Value range: 1: The V2 phase is started immediately after the V1 phase 2: The V2 phase is not started automatically |
