Use the DIRECT record to identify the CP‑owned volume that contains the page‑formatted directory area for the CP object directory.
DIRECT vaddr volser [volser2 [volser3 [volser4]]]
DIRECT is defined in the PRODUCT CONFIG file.
Specifies the virtual address of the full-pack minidisk (or a read/write link that the CA VM:Secure virtual machine has to the full pack minidisk) containing the CP object directory. Be sure that CA VM:Secure has at least an MR link to the minidisk specified by this virtual address. If another user has a Read-Write LINK to this minidisk, and that user might logon before the product server is started), then it may be necessary to grant the CA VM:Secure product server an MW LINK to the Object Directory volume.
Specifies a list of up to four volume serial numbers of the real DASD that contains the CP object directory. Usually a single volume serial number is defined, but in a Single System Image complex, a unique volume serial is specified for each member in the complex.
The volume(s) specified by the DIRECT record are usually a system residence volume. The minidisk specified by the virtual address is normally a full‑pack minidisk; this minidisk must begin at real cylinder or block zero and extend through the entire directory area. The minidisk should cover the entire DASD.
Important! If other users are to share access to this minidisk, take extreme care to prevent multiple users from updating the CP object directory.
Do not use DIRECTXA, DIRMAINT, or other programs to modify the CP object directory while CA VM:Secure is running. Using these programs may cause the CP object directory to become corrupted. If CA VM:Secure detects that another program has modified the CP object directory, CA VM:Secure immediately ends.
|
Copyright © 2014 CA.
All rights reserved.
|
|