The basic administration functions are called by means of predefined transaction codes, which are allocated to the standard administration program (KDCADM) during generation. These predefined transaction codes are known as administration commands.
Each basic function has a dialog transaction code and an asynchronous transaction code. The basic functions can thus be executed in a dialog, or asynchronously via message queueing.
Administration in a dialog
Within the dialog, the basic administration functions are initiated synchronously either by the administrator at the terminal or by a client program. In both cases, the desired administration command is specified in the form of a dialog transaction code. openUTM immediately executes the requested administration function, and returns a corresponding response.
Several administrators or administration clients can access the administration functions simultaneously.
Administration via message queueing
Like administration in a dialog, this type of administration allows the basic administration functions to be initiated by the administrator at the terminal. In this case, however, the desired command is entered in the form of an asynchronous transaction code.
It is also possible to access the basic administration functions from UTM program units. For this purpose, the program unit issues an MQ call (FPUT or DPUT) for the corresponding asynchronous transaction code.
In both cases, openUTM places the administration job in the appropriate queue, executes it independently of the administrator or program unit, and outputs the result in the form of an asynchronous message to a defined destination. Possible destinations include the administrator’s terminal, another terminal, a printer, or an asynchronous program.
With administration via message queuing, several administrators or UTM program units can access the administration functions simultaneously.
If administration is initiated by means of MQ calls from UTM program units, the time control facility can be used.
Overview: Transaction codes of the standard administration program
Dialog TAC | Asynchronous | Administration function |
KDCAPPL | KDCAPPLA | Change the number of processes, timer settings, and maximum |
KDCBNDL | KDCBNDLA | Exchange the master LTERMs of two LTERM bundles. |
KDCDIAG | KDCDIAGA | Call diagnostic tools: enable/disable test mode, trace, and KDCMON |
KDCHELP | KDCHELPA | Request information on the syntax of TACs from KDCADM |
KDCINF | KDCINFA | Query the current settings of system parameters, load statistics for the application, and object properties |
KDCLOG | KDCLOGA | Switch the user log file to the next file generation |
KDCLPAP | KDCLPAPA | For administration of UTM applications for distributed processing: |
KDCLSES | KDCLSESA | For administration of UTM applications for distributed processing: |
KDCLTAC | KDCLTACA | For administration of UTM applications for distributed processing: |
KDCLTERM | KDCLTRMA | Lock/unlock an LTERM partner, establish / shut down connections, |
KDCPOOL | KDCPOOLA | Change the number of clients permitted for a terminal pool |
KDCPROG | KDCPROGA | Replace the load modules of the application program |
KDCPTERM | KDCPTRMA | Lock/unlock clients/printers, establish / shut down connections |
KDCSHUT | KDCSHUTA | Terminate the application |
KDCSLOG | KDCSLOGA | Switch the system log file (SYSLOG) of the application, enable/disable size monitoring, define a threshold value for size monitoring, query information on the SYSLOG |
KDCSWTCH | KDCSWCHA | Change the allocations between the client/printer and the LTERM Partner |
KDCTAC | KDCTACA | Lock/unlock transaction codes (local services) |
KDCTCL | KDCTCLA | Change the number of processes available to a TAC class |
KDCUSER | KDCUSERA | Lock/unlock user IDs, change passwords |
The following TACs are only available in openUTM on BS2000 systems: | ||
KDCMUX | KDCMUXA | Lock/unlock multiplex connections, establish / shut down connections |
KDCSEND | KDCSENDA | Send messages to terminal users |