Use this information to help you identify the source of
errors that can affect policies.
Subtopics
Policy rules not triggering
There can be a number of reasons why your policy rule is
not triggering. The problem might be in the policy configuration,
deployment, or at run time. There are a number of simple checks you
can perform to help you to debug the problem.
Policy rules unexpectedly triggering
There can be a number of reasons why your policy rule is
triggering unexpectedly. The problem might be in the policy configuration,
deployment, or at run time. Always use statistical data when you set
thresholds; do not rely on static analysis of code.
Policy search gives unexpected results
If you have policies that are deployed on platforms or
applications, you can use the search facility in the CICS Cloud perspective in the IBM® CICS Explorer® to search for rules that are defined for a specific scope.
Sometimes, your policy search might not give the results that you
expect.
Storage problems after abend policy processing
You might experience a leak of shared storage after a task
is abended by policy processing. The leak is caused by the abended
program not releasing shared storage when it abnormally terminates.
Last updated: Thursday, 27 June 2019