The dialog administration commands can be used by:
users on terminals
UPIC clients
TS applications
- HTTP clients
LU6.1 or OSI TP partner applications
other dialog program units in the application
The user IDs, LPAPs and OSI-LPAPs, which are calling the commands must have administrator authorization.
Input of administration commands
A user on the terminal must enter the commands in line mode. Formatted entries are not accepted (exception: commands which have no operands).
The advantage of entering commands in line mode is that command processing does not take much time and administration tasks can also be performed in conjunction with other services.
In the UTM application on a BS2000 system, entries for administration commands will be rejected if an edit profile was used the last time that output was issued.
Output of results
openUTM returns the result of command processing to the job-submitting service. Output to the terminal also occurs in line mode.
If output to a terminal does not fit on one page of the screen, openUTM offers a continuation prompt on the last line of each screen display which can be used to continue output from the current position.
The chapter "Administration commands - KDCADM" describes what the result message for each command looks like in the section describing the relevant commands.
Output after successful processing of an administration command does not necessarily mean that the action you requested has been completed successfully. With some commands, the message merely means that openUTM has initiated the action (e.g. to establish a connection, to exchange programs). The reason for this is that it takes an extended period for these actions to be carried out or that openUTM is not able to execute the action until a later time. You can find out whether the appropriate action was carried out successfully by submitting a KDCINF query at a later date. With some of these actions (e.g. program exchange), openUTM generates K messages after processing is complete which indicate to you whether or not the action was performed successfully. These messages are usually sent to the message destination SYSLOG; output takes place in standard form (SYSOUT/stderr).