This file holds the names of security keys that are used to lock options. To lock an option, the name of the key is entered in the Lock field of the Option File. To permit a user to unlock the option, the user's name is entered in the Holder field of this file. It is cross-referenced by name and holder.
.01name(+)0;1FREE TEXTBEach entry in this File is the name of a key that defines some characteristic or capability for individual specified users. The capability might be access to some OPTION (file 19) which is permited with the authorization. Other functionalities (such as allowing scheduling overbook) might also be allowed only if the key is held. Keys are named with the standard package prefix formats; a 2-4 character package prefix for standard names or Z.
.02descriptive name0;2FREE TEXTThis is a more descriptive name for the KEY than allowed in the namespaced name field.
.03person lookup0;3SET OF CODESl:LOOKUP
This field when set to 'lookup' will build a X-ref on the NEW PERSON file of all holders of the key. This will be under a X-ref of 'AK.'_ so that a package can lookup members of a group. There is a standard SECURITY KEY that will be sent out of 'PROVIDER' with the lookup flag set. Then a package can do a lookup of PROVIDER's with the following code: S DIC="^VA(200,",D="AK.PROVIDER",DIC(0)="AEQ" D IX^DIC
.04keep at terminate0;4BOOLEANy:YES
If this field is set to YES (1) then this key will not be removed from a user in the New Person file when they are terminated. One example is the 'PROVIDER' key.
.05send to j2ee0;5BOOLEAN0:No
This field controls if this is a Security Key that should be sent to the J2EE application server for temporary role assignment. If this field is set to 'Yes' then this Security Key can be sent to the application server.
1description1;0WORD-PROCESSINGThis is a short description of the security key, indicating what the key locks out, and what class of users should be assigned the key.
3subordinate key3;0MULTIPLE19.13Subordinate authorization are "given" when the "master" authorization is given. This allows easier and more efficient delegation of authorizations.
4granting condition4;E1,245FREE TEXTThis is MUMPS code that set $T true if its OK for the person to be granted this key.
5mutually exclusive keys5;0MULTIPLE19.15

Referenced by 5 types

  1. ACCESSION (68) -- user access authorization
  2. LOAD/WORK LIST (68.2) -- user access authorization
  3. EXAMINATION STATUS (72) -- user key needed
  5. MH TESTS AND SURVEYS (601.71) -- a privilege