KSET - define a key set

The KSET control statement allows you to combine the key codes of an application, which were defined for data access control, to form a logical key set. You can specify several control statements for a single key set.

KDCDEF implicitly generates the KDCAPLKS key set, which by default contains all key codes.

KSET	keysetname    ,KEYS={ ( key1,key2,... key n ) | MASTER }

keysetname	Name of the defined key set up to eight characters in length. You can assign this key set to a user (in a USER statement in section "USER - define a user ID") to an LTERM partner (in a LTERM statement in section "LTERM - define an LTERM partner for a client or printer") to a partner application (in an LPAP or OSI-LPAP statement in section "LPAP - define an LPAP partner for distributed processing based on LU6.1" or "OSI-LPAP - define an OSI-LPAP partner for distributed processing based on OSI TP") to a TAC (in the TAC statement in section "TAC - define the properties of transaction codes and TAC queues") to an LTAC (in the LTAC statement in section "LTAC - define a transaction code for the partner application") to a TPOOL (in the TPOOL statement in section "TPOOL - define an LTERM pool" or "Format and uniqueness of object names") After the connection has been established, the key set of the LTERM or (OSI-)LPAP partner assigned to the connection is available to the client or partner application. After signing on to the application, the key set of the user ID is available to the client or partner application. The lock/key code and the access list concept are described in detail in the openUTM manual “Concepts und Functions”. An introduction to access control can be found in section "Lock/key code concept".
KEYS = (key1,..., keyn)
	Key or access codes of the key set keysetname List of numbers between 1 and the maximum value permitted by the application (MAX ...,KEYVALUE=number). These numbers correspond to the key codes contained in this key set. A key or access code grants access to a resource secured with a lock code or an access list, provided the key code and lock code match or the access code is contained in the access list. You can specify up to 60 key codes/access codes in each KSET statement. If a key set contains more than 60 key codes, you must issue another KSET statement with the same keysetname. If you only specify one key code, you can omit the parentheses. If you enter the value 0 for key, this is ignored by openUTM. No message is output.
MASTER	The MASTER key set contains all the key codes/access codes of the application.