Use policy scope to restrict the scope of a policy that defines task rules further to a
specific operation of an application. You can define one or more policy scopes by using the CICS® bundle manifest editor. Policy scope can be defined for any
policy that defines task rules that are deployed either into a stand-alone CICS region or with a CICS application.
Policy scope cannot be defined for policies that define any system rules or any policy deployed
with a CICS platform.
Before you begin
You must have a CICS bundle
project in the Project Explorer view.
About this task
A policy scope is used to restrict the task rules defined by a policy to a specific application operation
that is defined in an application entry point definition.
Each policy scope names a policy resource and an application operation. The policy resource is not required to be
declared in the same CICS bundle project.
For more information about application entry points, see
Defining application entry points.
For more information about policy scopes, see
Policy scopes.
Procedure
- Expand the CICS bundle project and
META-INF folder.
- Open the cics.xml file with the CICS Bundle Manifest Editor to
view the bundle manifest.
- Click the Policy Scopes tab to open
the list of policy scopes for the bundle.
- Click Add to define a scope for
the policy:
- Enter the name of the application operation.
- Enter the name of the policy resource.
The policy must be defined in a CICS bundle project that is
deployed with the CICS bundle but does not need to be in the same
CICS bundle project.
- Click OK to add the policy scope to the bundle manifest.
- Click or press Ctrl+S (cmd+S for OS X) to save the changes to the bundle
manifest.
Results
A policy scope for an application operation is created. When
the policy is deployed, the operation name is used to restrict the
user tasks to which the policies task rules apply.