The User/Application Relationship table

The security exit will then access the User/Application Relationship table, TBOLUSAP, to verify that the user who is signed on is allowed to access the specified application. The user-application pairs defined in this table allow you to control access to user applications. Table 28 lists the type of entries that will be contained in the User/Application Relationship table:

Table 28. User/Application Relationship entries

Signon user ID

Signon appl ID

Target appl ID

Description

TBOL

The default application if no user/application pair is found.

U00001

ADMN

The default application for user U00001.

U00001

TBOL

TBOL

The default application is optionally available to user U00001 if TBOLTBOL is entered.

U00002

PAYR

PAYR is the only application available to user U00002.

At installation, the User/Application Relationship table is set up to allow the administrator to perform the initial user setup for tablesONLINE/CICS. After installation TBOLUSAP contains the entry listed in Table 29.

Table 29. Installation entry

Signon user ID

Signon appl ID

Target appl ID

Description

ADMN

The Administration Application (Intended only for initial administrative access).

To restrict access to the administrative functions of tablesONLINE/CICS, change the entries in the TBOLUSAP after installation to the entries listed in Table 30.

Table 30. Post-installation entries

Signon user ID

Signon appl ID

Target appl ID

Description

TBOL

The default application (generally for instructional use)

XXX1

ADMN

ADMN

The Administrators application for USER XXX1

XXX2

ADMN

ADMN

The Administrators application for USER XXX2

The first entry is set up to allow first-time users to access and become familiar with tablesONLINE. The additional two users XXX1 and XXX2 are intended to be used as user IDs by the tableBASE administrator(s). In order to sign on to the Administrator menu, you must enter TBOLADMN.