Policy limitations for monitoring an object

The policy actions are driven mainly by data supplied by the discovery of objects. Under the conditions listed below, objects might not be discovered. 

• An extension's discovery feature is disengaged, for example, when QPMON is running on z/OS which by default has discovery turned off.
• The agent or extension where the information originates is running an older version of the product, for example, you have upgraded the server to version 8.0, but have not finished upgrading all the agents and extensions on all monitored machines.
• The extension does not support discovery.

Under these circumstances, the following restrictions might apply:

• Policies can match objects that were registered for monitoring via a mechanism other than a policy action. The act of registering an object for monitoring causes the object to exist, attributes to be published, and be recognized for policy evaluation. In this case, all the normal policy expressions are valid.
• Policies can match objects that are not monitored but are known to exist in the Object Repository tab synchronize functionality. Policy expressions for these objects are limited to expressions that match the object instance path. Policies using such expressions can use the register for monitoring action. Expressions that use attribute values do not work as no attributes are published for objects that are not registered for monitoring.