The following sections describe the various ways in which a client can sign off from the UTM application or is signed off by UTM. In this case, terminals differ from all other clients because users can only sign off from the application explicitly from terminals.
Signing off in the event of a timeout
Maximum wait times can be defined at UTM generation using:
the TERMWAIT= (PEND KP timer) and PGWTTIME= (PGWT timer) operands in the KDCDEF control statement MAX
the IDLETIME= (transaction end timer) operand of the PTERM or TPOOL statement or the OSI-LPAP statement for OSI TP partners.
If a wait time set with these timers expires, the following message is output to terminals:
K021 No input within the specified period
openUTM then signs off the user ID and shuts down the connection to the client. The client can subsequently sign on to the application again and continue a possibly open service, see section "Service restarts".
Signing off with the KDCOFF command
A terminal user can sign off from the UTM application by entering the UTM command KDCOFF or KDCOFF BUT. See also the UTM user command KDCOFF on "KDCOFF - sign off from a UTM application".
KDCOFF from a program
openUTM offers the function calls SIGN OF and SIGN OB, which can be used to trigger the effect of the KDCOFF or KDCOFF BUT user command in a dialog program unit. SIGN OF/OB is possible for terminals, UPIC clients, and TS applications. These calls are not permitted in program units running for an OSI TP partner.
SIGN OF and SIGN OB work as follows:
SIGN call | Command | Effect |
SIGN OF | KDCOFF | openUTM shuts down the connection to the client |
SIGN OB | KDCOFF BUT | The connection remains open for terminals; the user is signed off. |
The call has different effects for terminals and UPIC clients/ TS applications:
In the case of terminals, openUTM first outputs the MPUT message and message K095 to the terminals. Only with the next (arbitrary) input from the terminal is the user signed off and the connection shut down (with SIGN OF).
In the case of UPIC clients and TS applications, the MPUT message is sent and the connection shutdown is then initiated immediately.
Some of the possible applications of the SIGN OF/OB function call are outlined below:
Applications with particular security requirements. After signing off, a user can only process a single service.
The control part of the screen also offers “Sign Off” or “Sign On” as possible follow-up actions. Depending on the input, the follow-up program unit then creates a SIGN OF or SIGN OB call. Following the dialog output of this program unit and the subsequent input, either the connection to the terminal is shut down or the sign-on service is started.
- Improved data protection: The screen can be overwritten by the last MPUT, no process-specific data remains on the screen.