OVNM 5.3 - Operations Agent for NonStop Object Reference Guide

Threshold Policies 37
2-8 FILESYS
The FILESYS subsystem deals with the monitoring and management of files on a NSK system. Files can be
monitored in various ways and predefined actions can be taken if and when the criterion is met. The
counters/modifiers that have been predefined for this system greatly facilitate the management of files on the
NSK node.
When adding FILESYS thresholds, the system bypasses SQL Views except for File Exists and File Not Exists
thresholds. It is recommended that the object name is fully qualified (Volume.subvolume.file name). If you do not
supply the volume or subvolume, it will be taken from the location where OVNM is installed.
2-8-1 OBJECT CLASS: DYNAMIC
Policy
Description
Operators Allowed
ALLOC EXTENTS
ALLOC EXTENTS allows the user to check on the number of
extents allocated to a file. The units for Value 1 (Low-Value)
and Value 2 (High-Value) should always be number of
extents allocated for the file.
• Equal to <value1>
• Not equal to <value1>
• Less than <value1>
• Less than or equal to <value1>
• Greater than <value1>
• Greater than or equal to <value1>
•
Greater than <value1> and less than
<value2>
• Less than <value1> or greater than
<value2>
AUDITED
This threshold type allows the user to check the AUDITED bit.
The EQUAL TO operator is used for ON, and the NOT
EQUAL TO operator is used for OFF.
•
EQUAL TO
• NOT EQUAL TO
CLEAR ON PURGE
This threshold type allows the user to test the CLEAR ON
PURGE bit. The EQUAL TO operator is used for ON, and
the NOT EQUAL TO operator is used for OFF.
• EQUAL TO
• NOT EQUAL TO
EOF This threshold type allows the user to set thresholds against
the EOF of a file. If you enter -1 for <value-1>, then the EOF
will be captured the first time the file is detected and that
value will be used in the evaluation of the threshold for each
succeeding poll.
•
Equal to <value1>
• Not equal to <value1>
• Less than <value1>
• Less than or equal to <value1>
• Greater than <value1>
• Greater than or equal to <value1>
•
Greater than <value1> and less than
<value2>
• Less than <value1> or greater than
<value2>
FILE EXISTS
FILE EXISTS allows the user to check for the existence of the
specified file. If it exists, then it will be treated as a violation
state.
No operator.
FILE XFER This threshold type allows the user to configure the
application to execute a job when a file has been
transmitted to the NonStop. For the threshold to be invoked,
the file must exist, must have data and must not be open.
The first step the user-defined command should perform is to
rename the file so the action is not invoked a second time.
At a minimum, it should open the file which would also
prevent the action from being invoked a second time. But
the user-defined command must rename or purge the file by
the time it completes.
•
No operator