Introduction
This document describes how you can use Robot Monitor to monitor various aspects of BRMS.
BRMS Overview
Backup, Recovery, and Media Services (BRMS) helps you implement a disciplined approach to managing your backups, and provides you with an orderly way to retrieve lost or damaged data.
BRMS Monitoring Components
Monitoring Commands
Two BRMS monitoring commands are supplied:
MONCHKBML allows you to monitor the total number of a nominated messages currently present in the BRMS log. The command runs the DSPLOGBRM command and checks the resulting spooled file to obtain the number of messages. The command uses the current date as the from date unless date area MONCHKBML is present, in which case the value stored in that data area is used.
MONCHKBMS allows you to monitor the total number of tapes in a specified status, by location, container, media class, and system. The command runs the WRKMEDBRM command and checks the resulting spooled file to obtain the number of tapes that satisfy the criteria entered. There are three different types of values that can be returned: the total active tapes, the total expired tapes, and the total volumes.
User Defined Monitors (User Supplied Integer)
When adding the definitions, set them up as monitor type User Supplied Integer and type CL (not: SQL). See the Robot Monitor documentation for an explanation of how to add data definitions.
In order for the command to run, you need to create a job description that contains the Robot Monitor installed library (usually MSM) together with the BRMS installed library (usually QBRM).
To create a job description, execute these commands on each system where BRMS monitoring will be set up:
- CRTDUPOBJ OBJ(MONBCK) FROMLIB(MSM) OBJTYPE(*JOBD) NEWOBJ(MONBRMS)
- CHGJOBD JOBD(MSM/MONBRMS) INLLIBL(QTEMP MSM QGPL QBRM)
Note: The commands will need to be adapted if Robot Monitor was installed into a library other than the default "MSM".
MONCHKBML: Check BRMS Message Log
MSGID Message ID Type (Integer)
It is advisable to use the message ID, such as BRM1993, in the short description as this can then be used in thresholds later.
Some examples of the message IDs that should be monitored are as follows:
- BRM412F - Cartridge not available.
- CPF67A1 - Cartridge not found.
- BRM401A - Volume ID does not match cartridge ID.
- BRM1993 - Volume is write protected.
The command must be qualified with the Robot Monitor product library, for example, MSM/MONCHKBML MSGID(BRM1993).
A default global threshold needs to be created, with entries added showing all possible values that can be returned for the parameters supplied:
| Value |
Long Description |
Short Desc. |
Severity |
| 0 |
|
|
0 |
| 1 |
There have been &v &n : "&N" msgs on &S today. |
|
50 |
MONCHKBMS: Check BRMS Media Status Type (Integer)
| LOC |
Location |
Type (Name) |
| CNR |
Container |
Type (Name) |
| MEDCLS |
Media Class |
Type (Name) |
| SYSNAME |
System Name |
Type (Text) |
| TYPE |
Type of Value |
Type (Name) |
It is advisable to use the type of value, such as *TOTEXP, in the short description as this information will then be contained in threshold messages.
The types of values that can be monitored are as follows:
- *TOTACT - Returns the total number of active volumes.
- *TOTEXP - Returns the total number of expired volumes.
- *TOTVOL - Returns the total number of volumes.
The command must be qualified, for example, MSM/MONCHKBMS TYPE(*TOTVOL).
A default global threshold needs to be created, with entries added showing all possible values that can be returned for the parameters supplied:
| Value |
Long Description |
Short Desc. |
Severity |
| 0 |
There are insufficient expired tapes for tonight’s backup on &S. Required 25, Actual &v. |
|
50 |
| 25 |
There are sufficient tapes, &v, for tonight's backups on &S. |
OK |
50 |
Other BRMS Monitoring
Monitoring of your BRMS is not limited to the use of BRMS-specific monitoring commands. You can also use generic checks to provide information about your BRMS environment.
Subsystem/Job Monitoring: BRMS jobs run in subsystem QIABRMNET so this can be monitored using a Subsystem Status check.
Job Queue Monitoring: BRMS jobs are submitted using job queue QBRM/Q1ABRMNET. This job queue can be monitored with job queue checks such as Job Queue Number of Entries, and Job Queue Max Wait Time, and Job Queue Status.
Library/Object Monitoring: BRMS data reside in library QUSRBRM. This library can be monitored for size using an Object Size check. Individual physical files within that library can also be monitored. For example, the file QA1ALG, the BRMS history log, can be monitored for size.
