Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Defining the client sign-on procedure

This section describes the interface between generation and the sign-on procedure for clients if the application is generated with user IDs. The sign-on procedure is made up of the following two stages: establishing the connection and signing on.

The connection is established using the application names as specified in the operand BCAMAPPL= or, for OpenCPIC, specified in the operand LOCAL-ACCESS-POINT=.

Signing on to a UTM application

Signing on to a UTM application is carried out using a user ID. The following stages are required, regardless of whether the default sign-on service is used or another sign-on service:

  • When using terminals, the terminal user must prove their authorization once a connection has been established. To do this the user must enter at least one user ID. This user ID must be generated in a USER statement. This is also called the real user ID.

  • TS applications, UPIC clients and HTTP clients are signed on after connection using a so-called connection user ID. This is a user ID which is

    • either a user ID implicitly generated by openUTM using the LTERM name if no user ID is specified in the operand USER= of the LTERM statement,

    • or an explicit connection user ID, if a user ID is specified in the operand USER= which is generated with a USER statement, see "Automatic sign-on under a specific user ID". This user ID cannot be used as a real user ID.

  • OpenCPIC clients are signed on under their association names once the association has been established. The association names are formed using the names specified in the operand ASSOCIATION-NAMES= and a sequential number, for example, ASSOC03, see "OSI-LPAP - define an OSI-LPAP partner for distributed processing based on OSI TP"

UPIC clients, HTTP clients, TS applications and OpenCPIC clients which are signed on using a connection user ID or using their association name can then subsequently sign on using a real user ID.

The execution of the sign-on service can be defined by the generation, for example, using automatic connection establishment, automatic sign-on under a specific user ID, separate sign-on service or by permitting multiple sign-ons.

  • Detailed information about the sign-on service can be found in the relevant section of the openUTM manual “Using UTM Applications”. The individual steps required for a client to sign on to a UTM application are described there.