The Inter User Communication Vehicle (IUCV), Advanced Program‑to‑Program Communication/VM (APPC/VM), and the Virtual Machine Communication Facility (VMCF) define communication paths for the transfer of data between two processes (virtual machines and CP system services). These methods are types of Interprocess Communications (IPC).
You can establish a fine degree of audit and control over the IPC paths through CA ACF2 for VM resource rules. CA ACF2 for VM validates these resource rules to establish a one‑way IPC path connection and logs the establishment and termination of a one‑way IPC path connection. These functions make a user accountable for his actions during IUCV, APPC/VM, and VMCF interprocess communications.
The following terms describe CA ACF2 for VM support for IUCV, APPC/VM, and VMCF:
Invokes a request to perform a data or message transfer.
The recipient of a request to perform a data or message transfer. This recipient is not necessarily a virtual machine, but can be a CP system service or an application‑define resource ID.
These three communication paths are similar in function. They differ in the amount of data that you can transfer between the initiator and target virtual machines and in their path structures. In the case of APPC/VM, the initiator and target machines can be on physically separate VM systems through the Transparent Services Access Facility (TSAF).
To implement IUCV, APPC/VM, and VMCF validation, you must turn on the appropriate option in the OPTS VMO record (IUCVVLD for an IUCV or APPC/VM path connection, or VMCFVLD for a one‑way VMCF path connection). Then, modify the RESCLASS VMO record and, if necessary, the RESTYPE VMO record and the COMSEC operand. This operand is in the VMXAOPTS macro in HCPAC0. After you make these modifications,
CA ACF2 for VM validates them through resource rules.
|
Copyright © 2009 CA Technologies.
All rights reserved.
|
|