OPCOM
OPCOM, or the Operator Communication Manager, is a tool for communicating with users and operators on an OpenVMS system. It displays messages and events on terminals designated as operator terminals and writes them to a log file.
Event Classes
The following event classes can be enabled for OPCOM:
- CENTRAL
- PRINTER
- TAPES
- DISKS
- CARDS
- NETWORK
- SECURITY
- LICENSE
- OPER1 through OPER12
Related Logicals
- OPC$OPA0_ENABLE enables or disables OPA0: as the operator terminal by default
- OPC$OPA0_CLASSES specifies the classes enabled for OPCOM on OPA0:
- OPC$LOGFILE_NAME specifies the location of the log file
- OPC$LOGFILE_ENABLE enables the creation of OPERATOR.LOG
- OPC$ALLOW_INBOUND enables the inbound traffic from a node
- OPC$ALLOW_OUTBOUND enables the outbound traffic to a node
Commands
REPLY/LOG enables a terminal as an operator and opens a new version of OPERATOR.LOG REPLY/ENABLE enables a terminal as an operator for the classes specified as keywords REPLY/DISABLE disables a terminal as an operator for the classes specified as keywords
Privileges
Using OPCOM requires the following privileges:
- OPER to enable or disable the operator terminal (for all classes of events)
- SHARE to log into the designated operator's terminal as another process
- SECURITY to enable or disable sercurity events in the terminal
- none to send messages to an operator
Operator Log
By default, the operator log is stored in SYS$MANAGER:OPERATOR.LOG. The logfile is created if OPC$LOGFILE_ENABLE is defined as "TRUE" every time the system is rebooted. The classes are taken from OPC$LOGFILE_CLASSES or, if a log file is already open, from the current log file. If the logical does not exist, all classes are enabled. If OPC$LOGFILE_CLASSES contains an invalid class, all classes are enabled. In a clustered environment, this file is node specific. Messages that get into the log file can be controlled with REPLY/LOG/ENABLE and REPLY/LOG/DISABLE. Generally, messages that are logged to OPA0: also go to the operator log except the following:
- System SECURITY alarms and audits enabled using SET AUDIT command. These SECURITY messages are either logged to operator terminal and/or to SYS$COMMON:[SYSMGR]SECURITY.AUDIT$JOURNAL.
- Messages generated by the LANACP LAN Server process when a device status changes. These messages are displayed on the operator terminal and included in the log file written by LANACP, SYS$MANAGER:LAN$ACP.LOG.
