Previous Topic: Changing the Size of the CA VM:Secure DRCT and AUDT Minidisks

Next Topic: Step 1: Calculate the Number of Pages That CA VM:Secure Needs to Initialize the Directory

Enlarging the CP Object Directory (Moving It to a Different DASD Volume)

This section describes how to enlarge the CP object directory by moving it to a different DASD volume. For instructions on enlarging the CP object directory without moving it to a different DASD volume, see Enlarging the CP Object Directory (Keeping It on the Same DASD Volume).

Note: Although this section describes enlarging the CP object directory, you can use the instructions to move the directory without enlarging it. For example, you can move the directory because of hardware failures on the DASD volume on which the directory resides. To simply move the directory, start with Step 2.

Monitor the CP object directory so that you can enlarge its directory extents when it runs out of control block space. This happens during normal directory use.

To check your CP object directory, look for the following messages at CA VM:Secure startup time. The first message indicates how many objects (users, profiles, and pool members) you have in the directory and how many pages of space the directory needs to hold the control blocks:

065I DIRECTORY CONTAINS number USERS number PROFILES AND
     number POOL MEMBERS ON number PAGES

The second message indicates the total directory size and how much is available:

294I THE DIRECTORY CONTAINS number TOTAL PAGES. number PAGES
     ARE AVAILABLE FOR USE

When the messages indicate that you need to enlarge the CP object directory allocation (there are few pages available compared to the total directory size), take the following steps to calculate the required size, and then to change it to at least that size.

  1. Calculate the number of pages that CA VM:Secure needs to initialize the directory.
  2. Find enough free space on a CP–owned volume for the entire directory.
  3. Optionally, allocate a placeholder minidisk in this space.
  4. Change the appropriate EXTENT record in the DASD CONFIG file so that it accurately reflects the new location of the CP object directory.
  5. Create an ignored minidisk for CA VM:Secure to link to, if necessary.
  6. Back up the current CP directory.
  7. Format and allocate the new extent.
  8. Stop CA VM:Secure and update the configuration.
  9. Restart CA VM:Secure.
  10. Change the allocation bit map on the OLD DRCT area and re–IPL z/VM.
  11. Update links to the CP object directory.