This section describes how to enlarge the CP object directory without moving it to a different DASD volume. For instructions on enlarging the CP object directory by moving it to another DASD volume, see Enlarging the CP Object Directory (Moving It to a Different DASD Volume).
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:Director 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 recommended size and then to change it to at least that size. (The next several pages provide details for completing each of these steps.)
To enlarge the CP object directory
IBM CP planning guides give space requirements for the CP object directory area. For more information about your space requirement, see the appropriate IBM planning and administration documentation, and then use the following information in the IBM formulas for calculating the total control block space (tcbs).
Note: Some versions of CP call the TCBS number of records NR, the number of USERs NU, and the number of DEVs ND.
The TCBS calculation with these numbers gives the approximate number of pages that CA VM:Director needs to initialize the online directory. It is only approximate because CA VM:Director interactively updates the online directory. Therefore, we recommend that you add about 25 percent to the TCBS that you calculated above for work space.
After you change the directory allocation size, you can determine how close your estimate was by tracking the number of times you see message 065I on the CA VM:Director console while CA VM:Director is running. While this message is generated at CA VM:Director startup to tell you the number of online directory pages currently in use, it is also generated when CA VM:Director runs out of work space and then reclaims it. The reclaiming of work space is called dynamic rebuild.
If you see many occurrences of this message during the day, consider increasing the size of the online directory allocation.
As a rule, enough space is about double the amount of space you have just calculated in Step 1. This free space must be on one volume, but it can contain multiple extents and does not need to be contiguous. However, you can improve performance by allocating one contiguous area.
vmdirect map esa240 free
The command response in the following example displays the availability on 3390–type volume ESA240:
*VOLUME: ESA240 TYPE: 3390 UTILIZATION: 83%
ALLOCATION SIZE STARTING ENDING USAGE INFORMATION *FREE* 75 1 75 *FREE* *FREE* 54 190 243 *FREE* *FREE* 23 650 672 *FREE*
Check how much free space is available after you move a minidisk. Use the MAP command to do so. If there is still not enough space, move as many minidisks as necessary to free up the space you need.
To calculate the starting page number, use this formula:
To calculate the ending page number, use this formula:
If your site uses a minidisk as a placeholder for the CP areas such as the CP DRCT area, you need to update this user ID’s MDISK statement to represent the new location of the CP DRCT area. The benefit of this minidisk is that, when you use the IBM DIRMAP utility against the USER DIRECT file, the location of the CP DRCT area shows up in the output. In addition, if you change to another directory management product, this area will continue to be protected even though the area is no longer protected by an entry in the CA VM:Director DASD CONFIG file. (You will update this entry in the DASD CONFIG file in a later step.)
If you have a placeholder minidisk that represents the current CP object directory, you can update that minidisk now to reflect the new CP DRCT area. For example, if $DIRECT$ 123 is a placeholder for the old CP object directory and the new directory will be located on volume ESA240, a 3390 device, from cylinder 1 to cylinder 50, use the VMDIRECT EDIT $DIRECT$ command to change the location of $DIRECT$’s 123 minidisk to the following:
MDISK 123 3390 1 50 ESA240 RR
You must change the DASD CONFIG file to reflect the new location of the CP object directory so that you or other directory managers do not inadvertently allocate a new minidisk over the area you just allocated. Simply covering the area with a placeholder minidisk is not sufficient because subsequently scratching or moving that minidisk can cause CP system failures.
vmdirect config dasd
If the area you just created is in the middle of one extent, split the extent into three to isolate the CP area. For example:
EXTENT beg end EXTENT beg * <=== new CP area EXTENT beg end
If the newly allocated area begins or ends the current extent, split the extent in two so that the new CP area is isolated. For example:
EXTENT beg end EXTENT beg * <=== new CP area
As a precaution, back up your current object directory before continuing. Use the VMXBKP01 utility to make a backup. VMXBKP01 writes a USER DIRECT file to disk. Send a copy of the USER DIRECT file to OPERATOR’s reader. We also recommend that you write a copy of this file to tape.
As an extra precaution, you may also want to take a full DDR dump of the volume containing your object directory.
Log on to the user ID of your CA VM:Director service virtual machine and enter the END command to shut down CA VM:Director. If you do not shut down CA VM:Director, unpredictable results may occur in CA VM:Director or in the outcome of CPFMTXA. Do not log off.
Link to the minidisk that covers cylinder 0 through the end of the new CP DRCT area in read/write mode. Format the new extent and allocate it, using the CPFMTXA command. The command responds with a series of prompts to first format and then allocate the directory space.
When you finish with the format/allocate program, press Enter to return to CMS.
For example, the volume that will contain the new object directory is a 3390, linked at virtual address 100. It has a label of ESA240. The new object directory will be located on cylinders 1 through 50.
Important! Do not re-IPL until you complete Step 10: Change the allocation bit map on the old extent and re–IPL z/VM, in Enlarging the CP Object Directory (Moving It to a Different DASD Volume) in this chapter.
The series of command prompts and entries required to format this volume looks like the following, where the command prompts are in light type and the user entries are in bold type:
ENTER FORMAT OR ALLOCATE: format FORMAT FUNCTION SELECTED: ENTER DEVICE ADDRESS (CUU): 0100 ENTER DEVICE TYPE: 3390 ENTER START CYLINDER (xxx) OR LABEL: 0001 ENTER END CYLINDER (xxx): 0050 ENTER DEVICE LABEL: esa240 FORMAT STARTED FORMAT DONE 000 NO. PAGE RECORDS WITH READ-CHECK ERRORS ENTER FORMAT OR ALLOCATE:
The series of command prompts and user entries to allocate the new directory space looks like the following:
ENTER FORMAT OR ALLOCATE: allocate ALLOCATE FUNCTION ENTER DEVICE ADDRESS (CUU): 100 ENTER DEVICE TYPE: 3390 ENTER DEVICE LABEL: esa240 ENTER ALLOCATION DATA FOR VOLUME ESA240 TYPE CYL CYL drct 1 50 end ALLOCATION RESULTS PERM 0000 0000 DRCT 0001 0050 PERM 0052 3339 DEVICE 100 VOLUME ESA240 ALLOCATION ENDED ENTER FORMAT OR ALLOCATE:
Start CA VM:Director with the VMXSYS SOURCE command and add any options that you normally use. Log on to VMANAGER and issue VMSERVER VMDIRECT and check the Server Startup Command tag.. CA VM:Director writes the CP object directory to the new directory area.
|
Copyright © 2014 CA.
All rights reserved.
|
|