KLKINNAM Examples

Example 1: Using KLKINNAM to Specify More than One Control Point

In this example, the CL/SuperSession operator facility and GATEWAY1 are under the control of NAM; all other gateways are under the control of RACF®. You might want to use this kind of setup to create two levels of security: one for data center personnel (under NAM), and one for all other users (under RACF, with dynamic application lists).

In addition, a field validation exit routine has been specified. This routine will get control to validate all data fields before they are passed to the control point exit and/or the z/OS® security system.

Define three control points in TLVPARM(KLKINNAM):

FIELDEXIT=KLKNAMPX
DEFAULT  RACF  CLASSES=external
KLKLV000 NORACF DB DSNAME=prefix.KLK.NAM
KLSGW001 NORACF DB DSNAME=prefix.KLK.NAM

Example 2: Using a Dialog to Specify More than One Control Point

In TLVPNENU, create a dialog containing this prologue:

)prologue
  CNTRLPT(cntrlptname)
    SET majorkey (VGET('&VSSUSER' var))
    VPUT('&VSSUSER' var 'str')
  CNTRLPT(DEFAULT)

where cntrlptname is the name of a control point defined in TLVPARM(KLKINNAM).

In this example, the first VGET and VPUT use cntrlptname, and subsequent VGETs and VPUTs use the DEFAULT control point. For more information on CNTRLPT, VGET, and VPUT, see the CL/SuperSession SSPL Reference Manual.

Example 3: Specifying More Than One NAM Database

You can set up more than one NAM database by specifying a different dataset name in each control point definition.

Define two control points in TLVPARM(KLKINNAM):

DEFAULT DSNAME(dsname1)
KLSGW002  DSNAME(dsname2)

where dsname1 and dsname2 are the names of two VSAM datasets to be used for two NAM databases.

If a user logs onto GATEWAY1, the gateway will use dsname1 as the NAM database. If a user logs onto GATEWAY2 (ACB name KLSGW002), the gateway will use dsname2 as the NAM database.