Protecting Special Resources › IUCV, APPC/VM, and VMCF Validation and Logging › Information for Shared Databases

Information for Shared Databases

In a shared database environment, the implementation procedure for IUCV, APPC/VM, and VMCF security is the same. However, there are special considerations that give you increased flexibility when designing IUCV, APPC/VM, and VMCF security for shared databases. This flexibility translates into increased control of resources through the resource type codes. By modifying these codes, you can separate operating system resources for each CPU to meet your unique security requirements.

If you run two VM systems, you can establish separate rule sets for individual systems to implement more control. For example, you can separate the rule sets for IUCV, APPC/VM, and VMCF through the type code specified in the CONTROL(VMO) record and resource rules.

First, modify the resource type code in the RESCLASS VMO record:

SET CONTROL(VMO)

For SYSTEMA:

CHANGE RESCLASS IUCV(ISA) VMCF(VSA)

Next, modify the RESTYPE VMO record.

CHANGE RESTYPE TYPES(ISA,VSA)

After you modify the resource type codes, write resource rules to use the new type codes.

$KEY(VMSYSU) TYPE(ISA)
UID(TLCAMS) ALLOW

For more information about shared databases, see the Systems Programmer Guide.