Versions Compared

Version Old Version 10 New Version 11
Changes made by

Brian Nordland

Brian Nordland

Saved on

Key

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

The QCST_AD_CREATE policy specifies which resources will be automatically added to the specified cluster administrative domain when the resource is created. Normally, resources must be manually added to the cluster administrative domain after they are created. If a QCST_AD_CREATE policy is specified for a resource type and a resource of that type is created, a monitored resource entry (MRE) will be automatically added for the resource. This MRE will monitor all of the attributes for the resource.

...

  • 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.

  • Objects restored to the system are not covered under the QCST_AD_CREATE PowerHA policy.

...

These policies specify to automatically add resources of *ASPDEV, *AUTL, *CLS, *JOBD, *SBSD, and *USRPRF to the administrative domain when they are created on any node in the administrative domain. If the cluster is inactive or partitioned at the time of the creation of the resource, the resource is added 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_DELETE, and QCST_AD_RESTORE.

Example 2 - Changing an existing policy to specify a list of Libraries

...

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.