MainView Alarm Management
MainView Alarm Management works in conjunction with the MainView for UNIX System Services product, as well as other MainView products, to provide alarms. These alarms display messages that can alert you when system resources are overutilized.
Products that use MainView Alarm Management are:
- CMF MONITOR
- MainView for CICS
- MainView for DB2
- MainView for IMS
- MainView for WebSphere MQ
- MainView for z/OS
- MainView for UNIX System Services
- MainView VistaPoint
MainView Alarm Management is capable of simultaneously monitoring multiple systems, which means that MainView Alarm Management installed on one system keeps track of your entire sysplex.
The MainView for UNIX System Services product is distributed with alarms that you can customize to meet your specific monitoring needs. The following table lists the available alarms:
Alarm | Triggered when |
|---|---|
BBUBPS01 | Current number of processes for any one user has exceeded a specified percentage of the maximum allowable concurrent processes for a user |
BBUBPS02 | Current number of open files for a process has exceeded a specified percentage of the maximum allowable open files for a process |
BBUBPX01 | Current number of processes has exceeded a specified percentage of the maximum allowable concurrent processes on the system |
BBUBPX02 | Current number of user IDs on the system has exceeded a specified percentage of the maximum allowable concurrent user IDs on the system |
BBUFIL01 | One or more files listed in the FSSTAT view have a Match Indicator of N, indicating that the desired file is mounted but is not on the required mount point |
BBUFIL02 | Percent of unprivileged free blocks for a file system falls below a specified value |
BBUFIL03 | One or more HFS files listed in the FSSTAT view have a status of Missing |
BBUFSM01 | Read/write mounted file system utilization has exceeded a specific threshold |
BBUFSM02 | Read/write mounted file system utilization delta has exceeded a specific threshold |
BBUHFS01 | Interval lookup cache hit ratio for an HFS file system falls below a specified value |
BBUHFS02 | Interval page one cache hit ratio for an HFS file system falls below a specified value |
BBUHFS03 | Interval index read cache hit ratio for an HFS file system falls below a specified value |
BBUHFS04 | Interval index write cache hit ratio for an HFS file system falls below a specified value |
BBUHFS05 | Interval index I/O cache hit ratio for an HFS file system falls below a specified value |
BBUHFS06 | Interval cache hit ratio for global HFS falls below a specified value |
BBUPRO01 | One or more processes listed in the PESTAT view have a status of Missing |
BBUPSO01 | Process job CPU has exceeded a specific threshold |
BBUSYS01 | Process zombie count has exceeded a specific threshold |
BBUWAI01 | z/OS Unix waiter latch contention where latch number > 0 |
BBUXET01 | z/OS UNIX Environment Test return code checking |
Use the ALRMDIST view to manage the distributed alarms. Use the EZALARMS menu to navigate to other Alarm Management views.
Alarm definitions
Alarm definitions consist of the following parameters:
- threshold and filter criteria
- view, product, and context for which the criteria are established
- message IDs and message text
- monitoring frequency and time intervals
- hyperlinks to views, extended Help, or MainView AutoOPERATOR commands
Alarm definitions are stored in a parameter library member that is read by MainView Alarm Management at MVALARM PAS initialization.
Threshold conditions are defined as one of five priority levels:
- Informational
- Warning
- Minor
- Major
- Critical
For more information about the MainView Alarm Management, see Using MainView Alarm Management.