You can use the storage management agent to monitor disks and pubsets. For this pass the configuration file via the command line on the startup (configure it in the rc-script file): "-c <BS2:config-file>".
It is possible to modify the configuration file during operation by setting the storMgmtGlobalDataInputFile.0 object. If the configuration file contains syntax errors, processing continues with the previous message filter file.
The configuration is performed using an input file:
For monitoring the saturation level of individual public volumes (pubsets), the relevant PVS must be specified in the input file of the agent. This is done using the ADD-PUBSET-RECORD statement.
To monitor the state of the selected ROBAR application, use the statement ADD-ROBAR-RECORD.
To monitor the reconfiguration state of the individual disks, the relevant disks must be specified in the input file of the agent. This is done using the ADD-DISK-RECORD statement.
The REMARK statement can be used to store comments in the configuration file.
The last statement in the configuration file should be the END statement. Any statements that appear after the END statement are ignored.
A maximum of 128 pubsets and/or disks can be monitored.
ADD-PUBSET-RECORD - adding a pubset to be monitored
//ADD-PUBSET-RECORD |
PUBSET= <cat_id 1..4> , CHECK=SATURATION-LEVEL , TRAP-COMMUNITY= *STORAGE / *PUBSET-NAME / <c-string 1..64> |
PUBSET=<cat_id 1..4>
CAT-ID of the pubset to be monitored.
CHECK=SATURATION-LEVEL
Object to be monitored; currently only possible to specify the SATURATION-LEVEL (Default value).
TRAP-COMMUNITY=*STORAGE / *PUBSET-NAME / <c-string 1..64>
Community string with which the trap is sent.
If *PUBSET is defined, the <cat-id> is used as the Community Name.
If <c-string 1..64> is specified, this string is sent as the Community Name.Default value: *STORAGE
ADD-DISK-RECORD - adding a disk to be monitored
//ADD-DISK-RECORD |
DISK-MN =<alphanum-name 1..4> , CHECK=RECONFIGURATION-STATE , TRAP-COMMUNITY= *STORAGE / *DISK-MN / <c-string 1..64> |
DISK-MN=<alphanum-name 1 ..4>
Mnemonic name for the device to be monitored
CHECK=RECONFIGURATION-STATE
Object to be monitored; currently on possible to specify the RECONFIGURATION-STATE (Default value).
TRAP-COMMUNITY=*STORAGE / *DISK-MN / <c-string 1..64>
Community string with which the trap is sent.
If *DISK-MN is defined, the name defined for DISK-MN is used as the Community Name.If <c-string 1..64> is specified, this string is sent as the Community Name.
Default value: *STORAGE
ADD-ROBAR-RECORD - adding a ROBAR-CL application to be monitored
//ADD-ROBAR-RECORD |
LOCATION =< composed-name_1..8_with-underscore> , VERSION=*NONE / <product-version mandatory-man-corr> / <product-version without-man-corr> , JV-NAME= <filename_1..54 without-gen-vers> , TRAP-CONDITION = A / list-poss (6) : <name_1 .. 1> |
LOCATION=< composed-name_1..8_with-underscore>
Each storage location is identified by its name <alphanum-name 1..8>.
VERSION=*NONE / <product-version mandatory-man-corr> /
<product-version without-man-corr>
Version of the ROBAR-CL application to be monitored.
JV-NAME= <filename_1..54>
Job variable (MONJV), which is used to monitor this application.
TRAP-CONDITION = A / list-poss (6) : <name_1 .. 1>
States of a MONJV for which a trap is sent. The value A means all states.