Generating sign-on services for clients

It is possible to program special sign-on services for terminals, UPIC clients and TS applications. A sign-on service is linked to an application name. This means that you can assign a sign-on service to any application name. Application names are defined using MAX APPLINAME= or in a BCAMAPPL statement.

If a client signs on using a specific application name, then the sign-on service assigned to this application name is started. The application name under which the client has to sign on is specified in PTERM/TPOOL in the operand BCAMAPPL.

Sign-on services are generated as follows:

• The sign-on service for the default application name (as defined in
  MAX ... APPLINAME) is generated using:

  TAC KDCSGNTC, PROGRAM=signon-prog1
  PROGRAM signon-prog1 ...

  signon-prog1 is the name of the program unit that is initially run in the sign-on service.

  If a default application name is generated for a sign-on service, this is then taken as the default value for all application names generated using BCAMAPPL.

• The sign-on service for an application name defined using BCAMAPPL is generated using:

  BCAMAPPL appliname2...,SIGNON=signon-tac
  TAC signon-tac, PROGRAM=signon-prog2
  PROGRAM signon-prog2

  signon-prog2 is the name of the program unit that is initially run in the sign-on service.

• If sign-on services are also to be run for UPIC clients, you must specify the following in the SIGNON statement:

  SIGNON ... UPIC=YES

  If this setting is not made, no sign-on service is started for UPIC clients, not even if an appropriate sign-on service has been generated for the application name.

More information about the programming can be found in the openUTM manual „Programming Applications with KDCS”.