Methods of overriding parameters
You can override parameters using any of the following methods:
External file overrides
This is the recommended method for managing parameter overrides. Overrides are stored in external files with the PATROL Agent. These files are easy to distribute and replace. For more information, see Using external override files to manage parameter overrides.
An operator override is stored in an external database. This method works best for small sites. For more information see the PATROL Console for UNIX User Guide or PATROL Console for Microsoft Windows User Guide — Customizing PATROL, Volume 3.
The PSL function set_alarm_ranges() changes the alarm ranges of a parameter. This method is useful for intelligent KMs that determine their own alarm ranges during run-time. However, this method is CPU intensive and can cause problems if parameters are changed, so it is not recommended for regular use. For more information see set_alarm_ranges().
A developer override is a change to a parameter for a specific application on a specific host. It is stored in a special section of the KM file and can be created by only a developer console. This method is not recommended for large enterprises. For more information see the PATROL Console for UNIX User Guide or PATROL Console for Microsoft Windows User Guide — Customizing PATROL, Volume 3.