You can use the KC_MODIFY_OBJECT call during an application run to modify the properties of objects and parameters of the application program and initiate actions (e.g. resetting of statistical values).
| KC_MODIFY_OBJECT in "KC_MODIFY_OBJECT - Modify object properties and application parameters" |
The following object types have properties that can be modified dynamically:
KC_CLUSTER_NODE, KC_DB_INFO, KC_KSET, KC_LOAD_MODULE, KC_LPAP, KC_LSES, KC_LTAC, KC_LTERM, KC_MUX, KC_OSI_CON, KC_OSI_LPAP, KC_PTERM, KC_TAC, KC_TACCLASS, KC_TPOOL, KC_USER.
The following sections describe how to modify certain object types in more detail (KC_PTERM, KC_LTERM, KC_TAC, KC_USER, KC_KSET and KC_LSES).
The following parameter types have properties that can be modified dynamically:
KC_CLUSTER_CURR_PAR, KC_CLUSTER_PAR, KC_CURR_PAR, KC_DIAG_AND_ACCOUNT_PAR, KC_MAX_PAR, KC_TASKS_PAR, KC_TIMER_PAR.
You can modify a single object with each KC_MODIFY_OBJECT call. However, it is possible in an administration program to call KC_MODIFY_OBJECT more than once in order to modify the properties of multiple objects. In the call you specify the type of the object, its name and the properties to be modified.
When modifying application parameters, in a single call you can modify all the parameters that belong to the same parameter type.
The section entitled "KC_MODIFY_OBJECT - Modify object properties and application parameters" explains which properties can be modified for which object type or application parameter and which actions are thus initiated.
The effectiveness and duration of a change depends on the object type or application parameter and on the property that is changed. Some changes apply only to the current application run, whereas others apply beyond it as well (durable). A change can take effect:
immediately
after transaction processing (PEND)
when the utilization of the application permits it
UTM cluster applications (Unix, Linux and Windows systems)
The following applies in a UTM cluster application:
Depending on the object, the call can initiate actions that apply either globally in the cluster or locally in the node. Actions with a global effect apply to all the node applications in the UTM cluster application irrespective of whether a node application is currently active or not. Actions with a local effect only apply to the node applications at which they are executed.