Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The QCST_AD_DELETE policy automates and simplifies management of the removal of monitored resources and their respective MREs from a cluster. If an administrative domain uses the QCST_AD_DELETE policy with its monitored resources, then a resource deleted on one node of the cluster administrative domain can be deleted on all other active cluster nodes. Once the resource has been deleted on all cluster nodes, the MRE for the resource is also removed from the cluster administrative domain.

...

  • The name of the administrative domain the policy will apply to.

  • The names of the resource type or types that the policy will create resource entries for.

Info

Note: Depending on the resource type, a list of libraries may be required for the policy.

...

LIB(*ALL) indicates that the resource type can be created in any library. *BLANK indicating that the resource type does not require any library. LIB(NAME1 NAME2...) using only resources contained in the specified libraries.

Note

Important:

  • If LIB(*ALL) is specified with the RSCTYPE(*ALL) policy qualifier, the policy will cover all resource types, whether or not the resource type requires a library.

...

These policies specify that when any of the MRE types supported by this policy are deleted on any node in the administrative domain, the resource will be deleted from all other nodes in the administrative domain and removed from the administrative domain. If the cluster is inactive or partitioned at the time of the creation of the resource, the resource is deleted when clustering is started or the partition condition is resolved.

Tip

Tip: The CFGPCY(*YES) parameter on CRTCAD also adds policies of type QCST_AD_CREATE and QCST_AD_RESTORE.

Example 2 - Changing the resource type for an existing policy

...

The above commands add a new policy specific to user profiles and then remove the existing policy for all resource types.

Tip

Tip: In this example, the new policy for user profiles is added first, followed by the removal of the more general policy. This is done so that there is not a period of time where there is no policy that applies to user profiles. If the policy for all was removed first, then a user profile was deleted before the new policy was added, the behavior would be as if there was no policy defined.