To install CA ACF2 for z/VM properly, the operating system configuration and service level, the CA ACF2 for z/VM and installation virtual machines, the user diagnose codes, and the VMDBK control block must meet certain requirements.
There are no required IBM APARs at this time.
One of the components of CA ACF2 for z/VM is a disconnected service machine. It internally autologs this virtual machine when the first user logs on after VM IPL is complete. This service machine runs continuously as long as VM is up. This service machine performs all that need CA ACF2 for z/VM database activity or logging. The user ID of the CA ACF2 for z/VM service machine defaults to ACF2VM, but you can change it through the SRVMID operand of the VMXAOPTS macro.
If you use VSAM shared databases, the CA ACF2 for z/VM service machine must have at least 8Mb of virtual storage, defined in the CP directory. If you do not use VSAM databases, 5Mb of storage is sufficient. For each additional user beyond 512, add 1 Kb of storage.
The CA ACF2 for z/VM service machine runs in an ESA mode virtual machine and will exploit storage above the 16 Mb line.
The CAIMAINT ID requires a virtual machine size of 6 Mb to install CA ACF2 for z/VM. You can define this size in the CP directory or by CP commands before starting the installation procedure.
This section describes the storage requirements for CA ACF2 for z/VM for VM r12. These figures are a guideline. The actual storage requirements vary based on the application of maintenance.
CA ACF2 for z/VM dynamically acquires CP free storage for all validations.
It frees the acquired storage when it completes validation. The following is the requirements for CP free storage acquired at initialization:
|
Type of Storage |
Bytes |
|---|---|
|
CA ACF2 for z/VM free storage |
1,440 |
|
CA ACF2 for z/VM options free storage (HCPAC0) |
750 |
|
Total free storage |
2,190 |
Options free storage requirements vary from site to site. To estimate the length of your assembly, examine the length of your HCPAC0 assembly. The amount of options free storage you must allocate is approximately the length of HCPAC0. As distributed, HCPAC0 is 750 bytes. (CA ACF2 for z/VM rounds up all storage units because CP only allocates free storage in units of double words.)
CMS file level security, the requirements per logged‑on user for CP free storage are:
|
Storage |
Bytes |
|---|---|
|
Base free storage |
328 |
|
Free storage for every eight linked disks |
112 |
|
Total free storage (for user with no more than eight disks) |
440 |
Free storage for linked disks is allocated in units of 112 bytes.
CP free storage requirements per logged‑on user without CMS file level security are:
|
Storage |
Bytes |
|---|---|
|
Base free storage |
328 |
|
Total free storage |
328 |
The storage requirement for the CP resident nucleus is:
|
Type of Module |
Kb |
|---|---|
|
Required resident modules |
80 |
|
Total resident modules |
80 |
CA ACF2 for z/VM dynamically implants two user diagnose codes: ACF2 and 0ACF. Inserting these diagnose codes is transparent to the operating system and non‑CA ACF2 for z/VM code.
CA ACF2 for z/VM requires a single fullword in the VMDBK. The VMUSRFD operand of the VMXAOPTS macro specifies the name of this field, normally one of the VMDUSERn fields. The default is VMDUSER8.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|