Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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.

Without this policy, when a monitored resource in the administrative domain is deleted on any node in the administrative domain, the global status of the monitored resource changes to *FAILED. This indicates that the resource has been deleted on at least one node in the administrative domain, but still may need to be deleted from other nodes.

Adding a PowerHA policy for administrative domain resources

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.

When adding a PowerHA policy for the cluster administrative domain you need:

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

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

The PowerHA administrative domain resource policies qualifiers and values

PowerHA policies for administrative domain resources contain policy qualifiers designated as resource types (RSCTYPE). Supported resource types and the associated policy values are listed in the table below:

Policy Qualifier

Policy Value

RSCTYPE(*ALL)

LIB(*ALL)

LIB(NAME1 NAME2 …)

RSCTYPE(*ASPDEV)

*BLANK

RSCTYPE(*AUTL)

*BLANK

RSCTYPE(*CLS)

LIB(*ALL)

LIB(NAME1 NAME2 …)

RSCTYPE(*ENVVAR)

*BLANK

RSCTYPE(*ETHLIN)

*BLANK

RSCTYPE(*JOBD)

LIB(*ALL)

LIB(NAME1 NAME2 …)

RSCTYPE(*OPTDEV)

*BLANK

RSCTYPE(*PRTDEV)

*BLANK

RSCTYPE(*SBSD)

LIB(*ALL)

LIB(NAME1 NAME2 …)

RSCTYPE(*TAPDEV)

*BLANK

RSCTYPE(*USRPRF)

*BLANK

Policy value definitions

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.

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.

Examples

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:

ADDHAPCY PCY(QCST_AD_DELETE) PCYDMN(ADMDMN) QUAL('RSCTYPE(*ALL)') VALUE('LIB(*ALL)')

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: 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 resource type for an existing policy cannot be changed. Instead, the policy must be removed and a new policy added.

In this example, if you have an existing QCST_AD_DELETE policy that applies to *ALL resource types:

Policy Name

Policy Domain

Policy Qualifier

Policy Value

QCST_AD_DELETE

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:

ADDHAPCY PCY(QCST_AD_DELETE) PCYDMN(ADMDMN) QUAL('RSCTYPE(*USRPRF)') VALUE(*BLANK)
RMVHAPCY PCY(QCST_AD_DELETE) PCYDMN(ADMDMN) QUAL('RSCTYPE(*ALL)')

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

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.

  • No labels