Configuring the Console Monitor agent

The Console Monitor has access to the console commands of UCON via $CONSOLE. The following preparation is required to enable the Console Monitor to access the BS2000 console:

• Create the operator ID <operator-id>

• Granting the access rights for the operator ID

Create the operator ID <operator-id>

/ADD-USER USER-ID=<operator-id>, -
/PROTECTION-ATTRIBUTE=*PAR(LOGON-PASSWORD=<pass>), -
/ACCOUNT-ATTRIBUTES=*PAR(ACCOUNT=<account-no>)

The logon attributes defined here must be specified in the rc file when starting the Console Monitor (see Console Monitor agent (Agents-specific options for starting agents manually)).

Granting the access rights for the operator user ID

For operating with SECOS, access rights must additionally be granted for the operator ID to $CONSOLE:

/MOD-LOGON-PROTECTION USER-IDENTIFICATION=<operator-id>,

                        OPERATOR-ACCESS-PROG=*YES(PASSWORD-CHECK=*YES)

The class 2 system parameter NBBAPRIV must be set to the default value N.

The following tables describe agent specific command line arguments:

Mandatory Options	Description
-o <operid> -y <op-role1> [,<op-role2>, ...., <op-role10>]	Specify Operator's ID Specify Operator's role(-s); up to 10
or
-a <auth-file>	Load credentials specified in file

Optional arguments	Description
-k <password>	Specify password to access $CONSOLE
-c <msg-filter>	Load message filter
-n <negative-msg-filter>	Load negative message filter
-A <auth-file>	Outputs a prompt with which an authentication file can be generated. This file remains encrypted with AES.
-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.

Defining message filters

The Console Monitor agent uses two filter options for selecting messages:

• positive message filter
  selects messages to be sent to the management station

• negative message filter
  selects messages not to be sent to the management station