This section describes only agent-specific options. All other agents could be started without specifying any additional options, by calling them as simple binary using its program name.
Application Monitor agent
appMonAgent [-c <inputfile>]
[-t <int>]
[-r <old-file> <new-file>]
-c <BS2:inputfile>
You may specify a configuration file when you start the Application Monitor agent (see section “Statements for the configuration file”). If no configuration file is specified, all the subsystems recognized by the BS2000 system when the Application Monitor agent was started are monitored. The configuration file, which is defined by <inputfile>, must be stored in the BS2000 file system.
-t <int>
Interval at which the agent checks for requests from the command program. The default interval is set to five seconds.
File monitoring is carried out when the interval has expired.
The monitoring interval for subsystems is calculated as five times the value set for the timer interval, i.e. 25 seconds in the standard case.
It may happen that changes of state in applications or job variables may not be not notified until the timer interval has expired.
The monitoring interval for DCAM applications is calculated as 60 times the value set for the time interval, i.e. 5 minutes in the standard case.
-r <BS2:old-file> <BS2:new-file>
Converts the "old" configuration file (existing in SDF format) to the configuration file <new-file> with the new format.
Console Monitor agent
consoleAgent -o <operid>
-y <op-role1> [,<op-role2>, ...., <op-role10>] | -a <auth-file>
[-k <password>]
[-c <BS2:msg-filter>]
[-n <BS2:negative-msg-filter>]
[-r <proc>]
directly via the options -o, -y and -k (optional)
or via the authentication file using option -a
The Console Monitor agent has further functions, see Additional functions of the ConsoleMonitor agent.
Description of the options:
-o <operid>
defines the operator ID
Mandatory operand if -a is not specified.
-y <op-role1> [,<op-role2>, ...., <op-role10>]
Name of the operator role containing the relevant routing code for console monitoring.
Mandatory operand if -a is not specified.
-a <auth-file>
Using -a <auth-file> you can alternatively specify the complete path name of the authentication file where the role(s) and the password are defined.
Example: /etc/snmp/.conMonAuth.
Mandatory operand if -y and -o are not specified.
-k <password>
Definition of the password which authorizes the agent to access $CONSOLE. No specification (default value) means that no password is required.
-k may not be specified together with -a.
-c <BS2:msg-filter>
Path name of the file containing the filter configuration of the agent. No
specification (default value) means that all messages will generate trap.
-n <BS2:negative-msg-filter>
Path name of the file containing the negative filter configuration of the agent. No specification (default value) means that no message will be filtered out.
Additional functions of the Console Monitor agent
consoleAgent -A <auth-file>Outputs a prompt with which an authentication file can be generated. This file remains encrypted with AES.
consoleAgent -s <auth-file>Outputs the operator IDs and role(s) defined in the authentication file. If a password has been defined, *SET is output, otherwise *NONE.
<auth-file> is the absolute path to the authentication file.
HSMS agent
Starting the HSMS agent in the POSIX shell:
hsmsAgent -l <HSMS-library>
Description of the option:
-l <HSMS-library>
Path name of HSMS-SYSLIB, mandatory option.
openUTM agent for monitoring UTM applications
openUTMAgent [-c <BS2:inputfile>]
Description of the option:
-c <BS2:inputfile>
When the agent is started, a configuration file can be specified (see section“Configuring the openUTM agent”).
Storage agent
Starting the storage agent in the POSIX shell:
storageAgent [-c <BS2:inputfile>]
Description of option:
-c <BS2:inputfile>
BS2000 configuration file describing the pubsets, disks or ROBAR applications are to be monitored.