Assigning pools to a policy
Policies control MainView SRM collection and automation activities on pools, storage groups, and volumes.
Definitions in the SMPOOLxx member are used to assign these resources to a policy. The POLICY parameter can be specified to assign a pool, storage group, or volume to a policy. This topic discusses assigning a pool to a policy; for more information about assigning a storage group or a volume to a policy, see Assigning-storage-groups-and-volumes-to-a-policy.
For pools, the POLICY parameter on the pool definitions SET statement causes the pool to be managed by that policy. Pool definitions that do not specify the POLICY parameter can be assigned to a default pool policy established by the SMMSYSxx POL_POOL parameter.
If a default pool policy is not specified in the SMMSYSxx POL_POOL parameter and the pool is not specifically assigned to a policy, the pool will not be assigned to any policy. If a pool is not assigned to any policy, no MainView SRM collection or automation activities will be initiated against that pool. Configuration views within the product still report on the pool, and activity can still be initiated against the pool by using console commands or the MainView interface, but MainView SRM will not automatically initiate the activity if the pool is not assigned to a policy.
Only DASD type pools can be assigned to a policy. The POLICY parameter is ignored when used on a tape pool.
As distributed, all pools are assigned to a default pool policy. For users migrating from an earlier version of MainView SRM, the distributed environment is based on settings in the previous versions of the PARMLIB member.
Assigning a pool or group to a policy causes all of the volumes in the pool or group to be assigned to the policy. MainView SRM supports assigning a volume to up to eight policies. The first eight definitions in the SMPOOLxx member (reading from top to bottom) that cause the volume to be assigned to a policy are honored. Subsequent definitions in the SMPOOLxx member are ignored.
Examples of assigning pools to a policy
The following table shows examples of how to define and use pool policies.
Pool policy examples
Defining a pool policy | Result |
|---|---|
SET POOLNAME=WORKPOOL POLICY=POLWRK01 INC VOL=WRK/ | The pool is defined as WORKPOOL and includes all volumes that begin with WRK. The volumes in this pool will be managed according to the POLWRK01 policy that is defined in the SMPOLIxx PARMLIB member. |
SET POOLNAME=TESTPOOL POLICY=POLWRK01 INC VOL=TST/ | The pool is defined as TESTPOOL and includes all volumes that begin with TST. The volumes in the pool will be managed by the POLWRK01 policy that is defined in the SMPOLIxx PARMLIB member. |
SET POOL=STRGPOOL INC VOL=STG/ INC VOL=WRK/ | The pool is defined as STRGPOOL and includes all volumes that begin with either WRK or STG. The volumes in this pool are not specifically assigned to a policy, because the POLICY parameter is not specified. If the SMMSYSxx POL_POOL parameter is used to specify a default policy for pools, the STRGPOOL will be assigned to that policy. If the SMMSYSxx POL_POOL parameter is not specified, the pool will not be managed by any policy. |
The following information applies to the example:
- WRK volumes are assigned to both WORKPOOL and STRGPOOL. Because the WORKPOOL is assigned to the POLWRK01 policy, the WRK volumes will be managed by that policy. If a default pool policy is being used, the WRK volumes will be managed also by the default policy through the STRGPOOL definition.
- The STG volumes are included only in the STRGPOOL pool in this example. Either they will be managed by the default pool policy if one is being used, or they will not be managed by any policy.