Previous Topic: Step 2: Find Enough Free Space on a CP–owned Volume for the Entire Directory

Next Topic: Step 4: Change the DASD CONFIG File So That It Lists the Correct Extents for the CP Object Directory

Step 3: Allocate a Placeholder Minidisk in This Space (Optional)

You may want to allocate a minidisk as a placeholder for the CP DRCT area. With this minidisk defined, the CP DRCT area will show up in the output when you use IBM’s DISKMAP command against the USER DIRECT file. In addition, if you change to another directory management product, this area will continue to be protected even though it is no longer protected by an entry in the CA VM:Secure DASD CONFIG file. (You will create the entry in the DASD CONFIG file in a later step.)

If you want to create a placeholder minidisk, allocate that minidisk now. The recommended owner of this minidisk is $DIRECT$ (your site may have a different naming convention). CA VM:Secure will ignore this minidisk in the CA VM:Secure DASD CONFIG file. To create a placeholder minidisk (for example, $DIRECT$ 124) to cover the new CP DRCT area, follow these steps:

  1. Enter VMSECURE CONFIG DASD and add the following record:
    IGNORE $DIRECT$ 124
    

    Save the change.

  2. Enter VMSECURE EDIT $DIRECT$ and add an MDISK statement from the beginning of the CP object directory to the end.

    For example, if the new directory is located on volume ESA240, a 3390 device, from cylinder 1 to cylinder 50, add:

    MDISK 124 3390 1 50 ESA240 RR
    

    File the change.