The configuration file contains information as to which applications, tasks, subsystems, job variables and log files are to be monitored. Up to 256 user applications, BCAM applications, job variables and log files can be monitored, as well as 128 DCAM applications. The user and BCAM applications and tasks to be monitored must be started with job variables. There is no limit to the number of subsystems that can be monitored.
The entries in the configuration file are generated using SDF statements. The //REMARK can be used to store comments in the configuration file. The last statement in the file must always be //END. Statements that come after the END statement are ignored.
Monitoring | Statement |
Application | |
DCAM application | |
Subsystem | |
Job variable | |
Group of associated applications | |
Monitoring intervals |
ADD-APPLICATION-RECORD
The ADD-APPLICATION-RECORD statement states the BCAM and user applications to be monitored.
//ADD-APPLICATION-RECORD |
APPLICATION-NAME = <composed-name_1 .. 54_with-underscore> , VERSION = *NONE / <product-version> , TYPE = *BCAM / *USER , JV-NAME = <filename_1 .. 54> , TRAP-CONDITION = A / list-poss (6) : <name_1 .. 1> , WEIGHT= 0 / <integer 0 .. 999> |
APPLICATION-NAME=<composed-name_1..54_with-underscore>
Defines the application which the agent is to monitor.
VERSION=*NONE / <product-version>
Version number of the application
Default value: *NONE
TYPE=*BCAM / *USER
Type of application.
JV-NAME = <filename_1 .. 54>
Job variable (MONJV), which is used to monitor the application or task.
TRAP-CONDITION=A / list-poss (6) : <name_1 .. 1>
States for which a trap is to be generated.
WEIGHT= 0 / <integer 0 .. 999>
Weight of the traps specific to the Application Monitor agents. When sending a (generic) trap, the Application Monitor agent supplies the specified value for the trap object
appMonWeight and the trap number (see section “Notification Processing”). If various
weights are to be used in an application for various events, the associated ADD-APPLICATION-RECORD statement must be specified several times in the configuration file.Default value: 0
ADD-DCAM-APPLICATION-RECORD
The ADD-DCAM-APPLICATION-RECORD statement states the DCAM and user applications to be monitored cyclically. The monitoring interval for DCAM applications is 60 times the timer setting, i.e. 5 minutes by default. With the //SET-TIMER-OPTIONS (Statements for the configuration file) statement, you can set the monitoring interval to any multiple of the timer setting.
A maximum of 128 DCAM applications can be monitored.
//ADD-DCAM-APPLICATION-RECORD |
APPLICATION-NAME = <name_1 .. 8> , HOST= *OWN / <name_1 .. 8>> , KEEP-CONNECTION = *YES / *NO , MSG= *NONE / <c-string> / <x-string> , TRAP-CONDITION = list-poss (2) : *NOT-AVAILABLE / *AVAILABLE , WEIGHT= 0 / <integer 0 .. 999> |
APPLICATION-NAME=<name_1..8>
Defines the DCAM application which the agent is to monitor.
HOST=*OWN / <name_1..8>
Host on which the DCAM application is running
Default value: *OWN
KEEP-CONNECTION=*YES / *NO
Defines whether the connection is to be cleared down
Default value: *YES
MSG= *NONE / <c-string> / <x-string>
Connection message
TRAP-CONDITION=*NOT-AVAILABLE / *AVAILABLE
Conditions under which a trap is generated.
Default value: *NOT-AVAILABLE
WEIGHT= 0 / <integer 0 .. 999>
Weight of the traps specific to the Application Monitor agents. When sending a (generic) trap, the Application Monitor agent supplies the specified value for the trap object -appMon-Weight and the trap number (see section “Notification Processing”).
Default value: 0
ADD-SUBSYSTEM-RECORD
The ADD-SUBSYSTEM-RECORD statement defines the subsystems to be monitored. The monitoring interval for subsystems is 5 times the timer setting, i.e. 25 seconds by default. With the //SET-TIMER-OPTIONS (Statements for the configuration file) statement, you can set the monitoring interval to any multiple of the timer setting.
//ADD-SUBSYSTEM-RECORD |
NAME = <structured-name 1 .. 8> / *ALL , VERSION = *NONE / <product-version> , TRAP-CONDITION = *NONE / list-poss (8) : *CREATED / *NOT-CREATED / *IN-DELETE / *IN-CREATE / *IN-RESUME / *IN-HOLD / *NOT-RESUMED / *LOCKED , WEIGHT= 0 / <integer 0 .. 999> |
NAME=<structured-name 1..8> / *ALL
Defines the subsystem which the agent is to monitor.
VERSION=*NONE / <product-version>
Version number of the subsystem
Default value: *NONE
TRAP-CONDITION=*NONE / list-poss (8) : *CREATED / *NOT-CREATED / *IN-DELETE / *IN-CREATE / *IN-RESUME / *IN-HOLD / *NOT-RESUMED / *LOCKED
States for which a trap is to be generated.
Default value: *NONE
Note:
If NAME=*ALL is specified, you should use TRAP-CONDITION=*NONE as otherwise performance problems may arise.
WEIGHT= 0 / <integer 0 .. 999>
Weight of the traps specific to the Application Monitor agents. When sending a (generic) trap, the Application Monitor agent supplies the specified value for the trap object
appMonWeight and the trap number (see section “Notification Processing”). If various
weights are to be used in an application for various events, the associated ADD-SUBSYSTEM-RECORD statement must be specified several times in the configuration file.Default value: 0
ADD-JV-RECORD
The ADD-JV-RECORD statement defines the job variables to be monitored. By default, the Application Monitor agent sends each job variable modification as a trap. However, it is possible to filter the traps.
//ADD-JV-RECORD |
JV-NAME = <filename_1 .. 54> , APPLICATION-NAME = *NONE / <composed-name_1 .. 54_with-underscore> , PASSWORD = *NONE / <c-string_1 .. 4 > / < x-string_1 .. 8> , PATTERN = *NONE / list-poss (8) : <c-string_1 .. 256_with-lower-case> , WEIGHT= 0 / <integer 0 .. 999> |
JV-NAME = <filename_1 .. 54>
Defines the job variable which the agent is to monitor.
APPLICATION-NAME = *NONE / <composed-name_1 .. 54_with-underscore>Name of the application.
Default value: *NONE
PASSWORD = *NONE / <c-string_1 .. 4 > / <x-string_1 .. 8>
Read password of the job variables.
Default value: *NONE
PATTERN = *NONE / list-poss (8) : <c-string_1 .. 256_with-lower-case>
Defines one or more search patterns. If no PATTERN is specified, all JV changes are notified per trap.
The following wildcards are permissible:
? | replaces any character |
* | replaces any number of characters |
[s] | replaces exactly one character in a string s |
[c1 - c2] | replaces any character in the range c1 to c2 |
The backslash character "\" must be specified for special characters. A distinction is made between uppercase and lowercase.
Default value: *NONE
WEIGHT= 0 / <integer 0 .. 999>
Weight of the traps specific to the Application Monitor agents. When sending a (generic) trap, the Application Monitor agent supplies the specified value for the trap object
appMonWeight and the trap number (see section “Notification Processing”).
Default value: 0
DEFINE-OBJECT
Logically associated components in a process (applications, logfiles, subsystems and job variables) can be grouped together using the statement DEFINE-OBJECT. All elements stated in the DEFINE-OBJECT statement must also be defined in the configuration file with the corresponding ADD... statement.
//DEFINE-OBJECT | ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
OBJECT-NAME = <composed-name_1 .. 8_with-underscore>
Name of the object
BCAM-APPLICATION = *NONE / list-poss(5): <composed_name_1 .. 54_with-underscore>
BCAM applications that belong to this object
Default value: *NONE
USER-APPLICATION = *NONE / list-poss(5): <composed_name_1 .. 54_with-underscore>
User applications that belong to this object
Default value: *NONE
DCAM-APPLICATION = *NONE / list-poss(5): <name_1 .. 8>
DCAM applications that belong to this object
Default value: *NONE
LOG-FILE = *NONE / list-poss(5): <filename_1 .. 54> / <posix-pathname>
Log files that belong to this object
Default value: NONE
SUBSYSTEM = *NONE / list-poss(5): <structured-name_1 .. 8>
Subsystems that belong to this object
Default value: *NONE
JV = *NONE / list-poss(10): <filename_1 .. 54>
Job variables that belong to this object
MONITORING-TIME = *ALWAYS / *INTERVAL (...)
Specifies the monitoring time
Default value: *ALWAYS
*INTERVAL ( ...)
Defines the monitoring interval. If STOP-TIME is smaller than START-TIME, the hours after midnight are counted to the previous day when checking the EXCEPT-DAYS.
Example:
The monitoring time ranges from 20:00 to 3.00 hours, except from Saturday and Sunday. Monitoring therefore stops on Saturday at 3:00 in the morning and starts again on Monday at 20:00 in the evening.
START-TIME = HH:MM
Time when the object should be monitored
STOP-TIME = HH:MM
Time up to which the object should be monitored
EXCEPT-DAYS = *NONE / list-poss(6): MON / TUE / WED / THU / FRI / SAT / SUN
Weekdays on which the object is not to be monitored
Default value: *NONE
Example: Monitoring a MAREN system
A MAREN system consists of the following components:
Subsystem MAREN
Control program MARENCP
Automatic assignment of free tape MARENUCP
In addition, each VSN reserved by the automatic tape assignment function is automatically stored in the job variable TAPE.FILE.MAREN.
The following definition of a "MAREN" object combines these components:
//DEFINE-OBJECT OBJECT-NAME = MAREN //, USER-APPLICATION = (MARENCP, MARENUCP) //, SUBSYSTEM = MAREN //, JV = TAPE.FILE.MAREN
SET-TIMER-OPTIONS
The Application Monitor agent uses a timer. You specify the value for the timer when starting the Application Monitor agent. The statement SET-TIMER-OPTIONS defines the monitoring interval (polling factor). The monitoring interval defines the number of timer cycles which are to elapse before the next check is to be carried out.
//SET-TIMER-OPTIONS |
FILES = 1 / <integer> , SUBSYSTEMS = 5 / <integer> , DCAM-APPLICATIONS = 60 / <integer> |
FILES = 1 / <integer>
Defines the polling factor for files.
Default value: 1
SUBSYSTEMS = 5 / <integer>
Defines the polling factor for subsystems.
Default value: 5
DCAM-APPLICATIONS = 60 / <integer>
Defines the polling factor for DCAM applications.
Default value: 60