Administering Facility Security › VM as a Facility

VM as a Facility

As supplied, virtual machines running CA Top Secret are doing so under the VM facility. CA Top Secret controls access to the VM facility by requiring that the user be authorized to use the virtual machine. By default, only the MSCA is authorized to use VM when CA Top Secret is first installed. Everyone else must be explicitly authorized to use the VM facility through a TSS CREATE or ADDTO function. If you want to segregate your VM CPUs into different facilities use the FACILITY control option to rename one of the dummy USERnn entries in the Facility Matrix Table. For example:

FACILITY(USER1=NAME=VMTEST)

designates the USER1 entry as VMTEST, and

FACILITY(VMTEST=MODE=WARN)

sets the mode to WARN.

Next, use the VMFAC control option to associate your CA Top Secret facility to the HCPSYSID of the CPU by entering:

VMFAC(SYSTEMC=VMTEST)

In this example, SYSTEMC identifies the SYSID for HCPSYSID.

As you can see, CA Top Secret is flexible enough to be worked into a production VM environment. Just as you can set up a test CPU, you can also set up other test and production CPUs.