In this section you will find an overview of the parameters you need to pass to UTM depending on the operation you wish to execute. The descriptions are organized according to the operation codes passed in the opcode field of the parameter area and are listed in alphabetical order.
Description format
The description of an operation code consists of four parts:
The first part offers a general outline of the actions that can be executed, a list of the requirements that must be fulfilled so that UTM can execute the relevant action, and notes and special cases to consider when executing the actions.
If changes are made to the configuration and the properties then information is provided concerning the period during which the performed modifications will remain effective and whether these changes have a global or local effect for UTM cluster applications.
If the administration function or a portion of the function described can also be executed by means of an administration command (KDCADM transaction code), then the following symbol is used to indicate this command:
The second part is a table containing a short description of which areas (parameter, identification, selection or data area) require data for each action, and of the data that must be specified in these areas.
The third part consists of a schematic representation of the call, containing all optional and mandatory entries and the information that is returned by UTM. Fields requiring data before the call is made are shaded gray in the graphics. All fields in the parameter area that are not listed in the tables must be set to binary zero before you call KDCADMI.
The symbol "—" in a table means that no data needs to be passed to UTM in this area.
The fourth part contains comments and notes on the graphic, i.e. regarding the entries that need to be made and the information that is returned by UTM.