CA VM:Director automatically adds MINIOPT records when it updates an object directory. Each time a directory update is made, CA VM:Director checks each MDISK record in the directory entry against the caching attributes (CACHE|NOCACHE or MDC|NOMDC) on the DEVTYPE record. If no MINIOPT record is present and the specified attributes for the device type are not the CP default, CA VM:Director adds a MINIOPT record with the caching attributes specified on the DEVTYPE record.
For example, suppose you have a DEVTYPE record similar to this:
DEVTYPE 3390 3390 (NOCACHE NOMDC
The CP default for z/VM systems is CACHE MDC. If you issue the CA VM:Director EDIT command for a directory entry, CA VM:Director updates the directory. If there is currently a MINIOPT record following an MDISK record in the directory entry, no changes are made to this MINIOPT record. However, if there is no MINIOPT record following an MDISK that defines a minidisk on a 3390, CA VM:Director inserts the following MINIOPT record after the MDISK record:
MINIOPT NOCACHE NOMDC
It also updates the object directory and saves the source directory entry on the CA VM:Director DRCT (1B0) minidisk.
For CA VM:Director initialization, the scenario may be different. If a SOURCE start is invoked, CA VM:Director opens each directory entry. If a MINIOPT record is needed for caching, CA VM:Director sets the correct caching attributes in the object directory. However, the source directory entry is not normally changed and saved on the CA VM:Director DRCT (1B0) minidisk. The source directory does not contain the MINIOPT record even though the object directory entry is set with the correct caching attributes. You can use the SAVEDIR startup option to change the normal procedure and make CA VM:Director update all of the source directory entries on the CA VM:Director DRCT minidisk. For more information about SAVEDIR startup option, see Changing Startup Options in the chapter "Introduction" in the Administration Guide.
A directory update is not invoked during a quick start. Therefore, if the caching attributes on the DEVTYPE record are changed while CA VM:Director is down and a quick start is invoked at initialization, CA VM:Director does not make any changes to the online directory to reflect the new caching attributes of the device type. However, subsequent directory updates will recognize the new DEVTYPE record.
The following table lists all device types that CAVM:Secure support:
|
Name |
Default Block Size |
Units (Cylinders or Blocks) |
Tracks per unit |
Blocks per unit |
CMS 512 byte units |
Per 1K units |
Unit 2K units |
4K units |
ATTR |
|
|---|---|---|---|---|---|---|---|---|---|---|
|
|
||||||||||
|
3390 |
4096 |
65520 |
15 |
57326 |
735 |
495 |
315 |
180 |
C |
|
|
9336 |
1024 |
2147483640 |
1 |
512 |
1 |
0 |
0 |
0 |
F |
|
|
FB‑512 |
1024 |
2147483640 |
1 |
512 |
1 |
0 |
0 |
0 |
F |
|
Copyright © 2014 CA.
All rights reserved.
|
|