|
|
|
Although you can dynamically change all values on all DASD CONFIG file records, there are certain restrictions and expectations that are established for each record type.
You can add, change, and delete DEVTYPE records without restrictions. Any new values are used in all subsequent references.
You can add EXTENT records without restrictions.
You can delete EXTENT records, but all minidisks defined within those extents will no longer be controlled by CA VM:Secure.
When changing the cylinder or block ranges, existing minidisks cannot cross the boundary between two extents and must be either completely within a single extent or completely outside all extents. If you do not follow these guidelines, the extent information will not be updated. Additionally, any minidisks that were previously contained within a defined extent and are not within any extent after the update will no longer be controlled by CA VM:Secure.
You can change the subpools listed on an EXTENT record as long as the subpools are still defined. If you change an allocatable extent with subpools to a fixed CP extent, you must use IGNORE records to make all minidisks in that extent ignored to avoid overlay conflicts that will prevent the update from completing.
You can add, change, and delete IGNORE records without restrictions, unless removing an IGNORE statement will cause an overlap.
You can add, change, and delete NOLINK records without restrictions. However, if you change or delete a NOLINK record so that fewer minidisks are removed from LINK mapping, then CA VM:Secure must scan the entire object directory to recreate the LINK mapping structure.
You can add VOLUME records without restrictions.
You can delete VOLUME records, but all minidisks defined on those volumes will no longer be controlled by CA VM:Secure.
You can change the device type name on a VOLUME record as long as the true underlying device type does not change. For example, assume you have a DEVTYPE record that defines a custom device type, 3390NMDC, based on a 3390 prototype, and a VOLUME record that specifies the 3390NMDC name. You can change the device type name to 3390 or any other name that also resolves to a true 3390 device type.
SUBPOOL records can be added without restrictions.
You can delete SUBPOOL records as long as the subpools being deleted are not referred to on any EXTENT records.
You can change SUBPOOL records without restrictions. The new values will be used for all subsequent allocations from that subpool.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |