The Application Monitor agent allows monitoring of:
user applications
BCAM applications
DCAM applications
subsystems
job variables and
log files
Logically associated components of a process (applications, log files, subsystems and job variables) can be monitored together as a group.
The term applications are taken to mean programs and tasks here. The type and extent of application monitoring is controlled individually with the configuration file. Please see the corresponding section on section “Statements for the configuration file” for information on configuration file creation.
Log files
Monitoring via log files is provided for those applications that cannot send a trap to the management station themselves. Instead of this, these applications deposit messages in a log file that is monitored by the Application Monitor. The Application Monitor agent evaluates these messages and sends filtered messages to the management station as a trap.
BS2000 log files must be of type ISAM and must be shareable (SHAREUPD=YES). NFS or POSIX log files can be in ASCII or EBDIC format. The default format is EBDIC, ASCII format must be marked in the configuration file. The file name entry in the configuration file must contain the user ID for BS2000 or the absolute path name in the case of
NFS / POSIX. The agent cannot otherwise discriminate between BS2000 and
NFS / POSIX files.
By default, log files are checked every 5 seconds by the agent. This value can be changed in the start command using the -t option. If the agents detect changes to the files, a trap is sent to the management station for new messages, if they are matching the given pattern. When no pattern was specified, all message will trigger traps.