Configuration File Reference › SUBPOOL Record › Description

Description

Each subpool definition specifies a method for allocating from extents and the maximum amount of disk space allowed for each allocation request.

CA VM:Secure maintains a complete mapping of all controlled disk space within its virtual memory. Each time you define a minidisk, the subpool you specify governs where and how CA VM:Secure will allocate the disk space.

In the DASD CONFIG file, a SUBPOOL record must appear before any EXTENT record that references the named subpool. You cannot continue SUBPOOL records beyond the first line.

To allow directory managers to use any individual subpools, authorize them specifically by including the subpool name on the MANAGER record in the VMSECURE MANAGERS file.

Examples

• The following record defines a subpool, MAIN, that balances minidisk allocations across all volumes. The individual extents on each volume fill up from the low end, and there is no size limit:

  SUBPOOL MAIN ROTATING LOWEND *
  

• The following record defines a subpool, SALES, that allocates minidisks to the best fitting gap available. The best fitting gap is either an exactly matching gap or the smallest gap with at least 1200K of disk space in addition to the size of the requested minidisk. If two or more possible gaps exist in the same extent, CA VM:Secure uses the one nearer the high end of the extent. CA VM:Secure cannot allocate a minidisk from this subpool that is larger than 2400K:

  SUBPOOL SALES SMALLGAP 1200K HIGHEND 2400K