|
|
|
The following table shows the sequence requirements of the records that appear in the DASD CONFIG file. For a sample DASD CONFIG file, see Sample DASD CONFIG.
|
Record |
Sequence Requirements |
Quantity Allowed |
|---|---|---|
|
SUBPOOL |
Must appear before the specified subpool is referenced by an EXTENT record |
Multiple |
|
DEVTYPE |
Must appear before the specified device is referenced by a VOLUME record |
Multiple |
|
VOLUME |
Does not require that an EXTENT record follow it. When one does not, all space on the entire volume is treated as not controlled by CA VM:Secure; the volume itself is controlled |
Multiple |
|
EXTENT |
Must appear immediately following the VOLUME record to which it applies, or following other EXTENT records for the same volume |
Multiple |
|
IGNORE |
Can appear anywhere in the file |
Multiple |
|
NOLINK |
Can appear anywhere in the file |
Multiple |
You can manage DASD through CA VM:Secure if you identify the DASD to CA VM:Secure in its DASD CONFIG file.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |