Sign-on services, also known as SIGNON event services, are user-programmed services that can be used to define your own sign-on processes. Sign-on services can be used by terminals, UPIC clients, and TS applications, i.e. by clients generated with the PTERM or TPOOL statement (except HTTP clients).
Calling sign-on services
A sign-on service is linked to the application name. If a client signs on under a particular application name, the sign-on service associated with this application name is started and replaces the standard sign-on process described in the preceding sections. If several application names are generated with BCAMAPPL statements, several different sign-on services can exist in an application. This means that client-specific sign-on services can be created, e.g. one for terminals, one for UPIC clients, and one for TS applications. More details can be found in sections "Sign-on service for terminals" through "Sign-on service for UPIC clients".
If no sign-on service is generated for an application name, the client runs through the standard sign-on process.
Generating sign-on services
Sign-on services are generated as follows; see also the openUTM manual “Generating Applications”:
TAC KDCSGNTC is used to generate the sign-on service for the standard application name (defined in MAX APPLINAME).
BCAMAPPL appliname2...,SIGNON=signon-tac is used to generate the sign-on service for the application name appliname2. signon-tac must be defined in a TAC statement.
If you also want UPIC clients to be able to use sign-on services, SIGNON ...,UPIC=YES must be generated as well.
A PROGRAM statement is also needed for each of these TACs. The name of the first program unit run through in the sign-on service is specified here.
Programming sign-on services
The special KDCS calls SIGN ST, SIGN ON and PEND PS are used for programming a sign-on service. A detailed description of how to program a sign-on service and what rules to observe in the process can be found in the corresponding section of the openUTM manual „Programming Applications with KDCS”.