Sample programs for the sign-on service

Using the sample programs for the sign-on service, you can implement a simple sign-on service with FHS format output.

Both compiled objects and source programs (COBOL) are supplied. The new functions can thus be tried out quickly without programming. The source programs represent a programming template that can be used if you want to implement a sign-on service adapted to your own requirements.

Functions

The programs are suitable for all generation variants.

If required, the terminal user is requested to input sign-on data after the connection has been established. For this purpose, the sign-on service outputs a “welcome format” containing two input fields for the user ID and password. The password must be specified in printable form. Please remember when specifying the user ID and password that small letters are converted to capital letters.

If openUTM rejects the sign-on data, the sign-on service repeats the request for input. It then outputs the same format, though it now contains information on the rejection. After three failed attempts, the sign-on service is terminated.

If openUTM accepts the sign-on data, the sign-on service proceeds as follows:

• No service restart: A start format is output if one is generated; otherwise, a request is issued for input in line mode.

• Service restart: The screen restart of the open service is initiated.

English text is output on the terminal. The comments in the source program are also in English.

Components

The sample programs for the sign-on service are located in the library SYSLIB.UTM.070.EXAMPLE.

Element	LMS type	Meaning
SIGN1	S	COBOL source                      --> 1st program unit
SIGN2	S	COBOL source                      --> 2nd program unit
KDCSIGN1	R	Object module                       --> 1st program unit
KDCSIGN2	R	Object module                       --> 2nd program unit
FORSIGN	R	Screen format (' *' format)
FORSIGN	S	Addressing tool
FORSIGN	F	IFG source

Integration in a UTM application

To integrate the sample sign-on service in a UTM application, the KDCDEF generation statements must be extended as follows:

PROGRAM KDCSIGN1,COMP=ILCS
PROGRAM KDCSIGN2,COMP=ILCS
TAC     KDCSGNTC,PROGRAM=KDCSIGN1
TAC     TACSIGN2,PROGRAM=KDCSIGN2,CALL=NEXT

The TAC name TACSIGN2 is programmed. It is defined as a constant at the start of both program units and can thus be changed easily if required.

The standard primary working area must be at least 600 bytes, the communication area at least 2 bytes long (see MAX statement in the openUTM manual “Generating Applications”).

The linkage editor statement must be extended as follows:

INCLUDE-MODULES LIBRARY=$userid.SYSLIB.UTM.070.EXAMPLE ,ELEMENT=(KDCSIGN1, KDCSIGN2)

The screen format FORSIGN must be incorporated in the format library of the application. The format is suitable for terminals of types 8160, 9750, 9755 and 9763.

The program unit SIGN1 uses the COBOL85-specific statement EVALUATE.