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: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 required size, and then to change it to at least that size.
IBM CP planning guides give space requirements for the CP object directory area. See the appropriate IBM planning and administration documentation for your space requirement, and then use the information below in the IBM formulas for calculating the total control block space (TCBS):
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 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 * free
This command shows free space on all DASD volumes controlled by CA VM:Director.
To find where you have directory space allocated, enter the CP QUERY ALLOC DRCT command. Only one directory area will be listed as active. If more than one DRCT area is allocated, we recommend you delete the inactive areas before continuing. To delete the space, mark it as PERM, using the procedure in Step 10.
The following example shows a portion of the VMDIRECT MAP command response. It displays the availability on 3390–type DASD 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:
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:Director 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:Director will ignore this minidisk in the CA VM:Director DASD CONFIG file. To create a placeholder minidisk (for example, $DIRECT$ 124) to cover the new CP DRCT area, follow these steps:
IGNORE $DIRECT$ 124
Save the change.
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.
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
Save the changes and close the DASD CONFIG file.
CA VM:Director requires a read/write minidisk from cylinder 0 to the end of the DRCT area that you intend to allocate in Step 7. This IGNORED minidisk normally belongs to $DASD$ and is usually a full–pack minidisk. If you do not have a full–pack minidisk for the DASD volume that will contain the new CP object directory, do the following:
IGNORE $DASD$ vaddr
vaddr
The address of the full–pack minidisk you will create in the next step.
Save this change.
MDISK 124 3390 0 END ESA240 RR
Save this change.
As a precaution, back up your current 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 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.
Link to the minidisk described in Step 5 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.
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:
Carefully XEDIT the CA VM:Director source directory entry. The file name of the correct file will be VMDIRECT. Change the definition of the 1A0 minidisk to be a multiple write link to the ignored minidisk described in Step 5. For example:
LINK $DASD$ 124 1A0 MW
Save this change.
Start CA VM:Director with the VMXSYS SOURCE ALTVOL 1A0 volser command and add any other options that you normally use. To check for these options, log on to VMANAGER and issue VMSERVER VMDIRECT. Check the Server Startup Command tag.. CA VM:Director writes the CP object directory to the new directory volume and shuts down with return code 4.
When your z/VM system is IPLed, CP searches for the DRCT area on all online SYSTEM volumes, in slot order, as defined in the CP SYSTEM CONFIG file. CP uses the first DRCT area it finds.
If the pack on which the old DRCT area resides is earlier in the search order than the pack on which the new DRCT area resides, CP uses the old DRCT area when a system IPL is performed. To force CP to use the new DRCT area, change the allocation bit map on the old DRCT area. Do this by executing CPFMTXA. Use the ALLOCATE function and change the allocation to PERM.
For backout purposes, we do not recommend that you reformat the old space at this time.
Bring down your z/VM system normally by using the SHUTDOWN command. Then, IPL your system and verify that CP and CA VM:Director are using the new DRCT area by entering:
cp query alloc drct
When you are sure that CP and CA VM:Director are using the new DRCT area, you can reformat the old directory space.
|
Copyright © 2014 CA.
All rights reserved.
|
|