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 created added for the resource. This MRE will monitor all of the attributes for the resource.
...
Each PowerHA administrative domain resource policy is defined by the cluster administrative domain name specified in the domain name field and the resource type specified in the RSCTYPE keyword in the policy qualifier field. The name of any defined cluster administrative domain resource type may be specified. In addition the special value *ALL can be specified for the resource type, indicating all resource types supported by that policy.
...
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 Depending on the resource type, you may require a list of libraries may be required for the policy. |
The PowerHA administrative domain resource policies qualifiers and values
...
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:
|
...
Example 1 - Default Policies Created by PowerHA
PowerHA now automatically creates default policies when CFGPCY(*YES) is specified on the Create Cluster Admin Domain (CRTCAD) command. The following lists the example commands to add the same policies in an administrative domain, ADMDMN:
...
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_RESTORE DELETE and QCST_AD_DELETERESTORE. |
Example 2 - Changing an existing policy to specify a list of Libraries
...
This policy indicated that any job description created in any library is automatically added in to the administrative domain. It is now desired to limit the scope of this policy to only resources created in libraries APP1 and DEVLIB. The policy can be changed with the following command:
...
The resource type for an existing policy cannot be changed. Instead, the policy must be removed and a new policy added. For
In this example, if a policy was added for *ALL resource types and the desire is to change the policy so that it is only for user profiles, the following commands would be required for administrative domain ADMDMN.
Existing Policy:
...
you have an existing QCST_AD_CREATE policy that applies to *ALL resource types:
Policy Name | Policy Domain | Policy Qualifier | Policy Value |
|---|---|---|---|
QCST_AD_CREATE |
...
ADMDMN | RSCTYPE(*ALL) |
...
LIB(*ALL) |
...
If you want to change it to apply to only user profiles, you need to remove the existing policy and add the new policy:
| Code Block |
|---|
RMVHAPCYADDHAPCY PCY(QCST_AD_CREATE) PCYDMN(ADMDMN) QUAL('RSCTYPE(*ALLUSRPRF)') VALUE(*BLANK) ADDHAPCYRMVHAPCY PCY(QCST_AD_CREATE) PCYDMN(ADMDMN) QUAL('RSCTYPE(*USRPRFALL)') VALUE(*BLANK) |
The above commands add a new policy specific to user profiles and then remove the existing policy for all resource types and add a new policy specific to user profiles.
| 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. |