Application Monitor agent configuration

The Application Monitor agent allows monitoring of:

• user applications

• DCAM applications

• BCAM applications

• subsystems

• job variables

• log files

In addition, groups of associated statements can be managed as a unit (object).

The type and extent of the application monitoring are controlled individually via a configuration file located on BS2000 file system. The configuration file must have the USER-ACC attribute set to ALL-USERS so that the Application Monitor agent has access to it at system startup. Note that the job variables should also have shared user access as well (USER-ACCESS=*ALL-USERS). The name of the configuration file is notified to the application monitor agent in the start command (in the rc file) via -c option. If there are errors in the configuration file, the start procedure is interrupted. If no configuration file is specified, monitoring is restricted to subsystems only.

The following table describes agent specific command line arguments:

Option	Defaults	Description
-c <BS2:config-file>	no-file; only subsystems are monitored	Apply given configuration file to start monitoring selected objects.
-t <sec>	5 sec.	Basic counter, which determines how often objects are checked: Subsystems checked (5 * counter) sec (default, each 25 sec) Files checked (1 * counter) sec (default, each 5 sec) DCAM apps checked each (60 * counter) sec (default, each 5 min)