Outputting the last dialog message by the sign-on service
If there is not a service restart pending and the sign-on service is terminated with MPUT PM and PEND FI, the last dialog message of the user‘s last session is output if the user is generated with RESTART=YES. The user can then continue working with the same screen that was being used when the last session was terminated, regardless of whether this occurred inside or outside of a service.
Messages
If a UTM application uses a sign-on service, then the following messages are not produced (and therefore not output to the SYSLOG and MSGTAC):
K001, K002, K004 through K008.
Message K033 (Successful sign-on) is also output when a sign-on service is used.
Unsuccessful attempts in the sign-on service
In the sign-on service, unsuccessful attempts of the user to sign on can be intercepted: if openUTM does not accept the authorization data entered by the user, the sign-on service can ask the user to repeat the input. The maximum number of input attempts can be programmed. If this number is exceeded, the sign-on service should terminate. UTM then shuts down the connection in the case of TS applications and terminals, whereas only the conversation is ended in the case of UPIC.
In addition, openUTM counts all of the unsuccessful attempts of a client or unsuccessful attempts under a user ID made in uninterrupted succession, also over a series of sign-on services. The maximum permitted number of failed sign-on attempts must be defined in the UTM generation. After this number of failed sign-on attempts has been made (see openUTM manual “Generating Applications”, KDCDEF statement SIGNON, operand SILENT-ALARM), openUTM reports this event to SYSLOG (silent alarm, UTM message K094). Sign-on attempts by unauthorized persons can be uncovered and averted with an MSGTAC routine.
Abnormalities in the sign-on service
openUTM checks whether the rules for the sign-on service are observed. This also provides protection against any manipulation of the program units of the sign-on service. If such errors occur, openUTM terminates the sign-on service with PEND ER and shuts down the connection to the terminal. The connection is then shut down in the case of TS applications and terminals, whereas only the conversation is ended in the case of UPIC.