The SIGNON service

The SIGNON sign-on service is a dialog service that is started

• after the connection to a terminal or a transport system client has been established by means of a transport system application, provided a sign-on service has been generated for this access point, or

• before the start of every conversation initiated by a UPIC client, provided a sign-on service has been generated for this access point and

  • sign-on services were released for UPIC clients at generation,

  • the application is generated with OMIT-UPIC-SIGNOFF=NO,

  • and the user is not yet signed on.

A separate sign-on service can be generated for each transport system access point of a UTM application, see the SIGNON-TAC operand of the BCAMAPPL statement and the TAC statement with the KDCSGNTC transaction code in the openUTM manual “Generating Applications”.

Generation notes

• The sign-on service for a transport system access point defined with MAX APPLINAME is generated with TAC KDCSGNTC,PROGRAM=... This sign-on service thus becomes the default for all the transport system access points of the application.

• The SIGNON-TAC parameter of the BCAMAPPL statement can be used to generate another sign-on service for a transport system access point. If a sign-on service is not to be used for a transport system access point, the value *NONE must be specified for the SIGNON-TAC parameter.

• Sign-on services are enabled for UPIC clients as follows:
  SIGNON ...,UPIC=YES.

• In the SIGNON statement in the generation you can specify that a user can still temporarily sign on to the UTM application if the validity period of his or her password has run out (operand GRACE = YES). In this case, the password of the user must be changed if the sign-on service is to end successfully.

• The maximum number of failed sign-on attempts from a client can be monitored as follows:
  SIGNON ,SILENT-ALARM=number

  When this value is reached, message K094 is output to SYSLOG. This message can also be processed by an MSGTAC program (see "Asynchronous service MSGTAC").

You will find a detailed description in the openUTM manual “Generating Applications”.