|
HP OpenVMS System Manager's Manual, Volume 1:... |
Using OpenVMS System Management Utilities and... |
|
|
| |
Using OPCOM to Communicate with System Users
| Function | For More Information |
|---|---|
|
To broadcast
messages to users who are logged in
|
Sending Messages to Users
|
|
To control
the use of OPA0: as an operator terminal
|
Controlling the Use of OPA0: as an Operator Terminal
|
|
To designate
terminals as operator terminals, enabling them to display messages
broadcast by OPCOM
|
Designating Operator Terminals
|
|
To record messages
broadcast by OPCOM in a log file
|
HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems
|
|
To send requests
to an operator1
|
Sending Requests to an Operator
|
|
To reply to operator requests
|
Replying to Operator Requests
|
Understanding OPCOM
Operator Communication Manager (OPCOM) illustrates the function of OPCOM.
|
Figure 3 Operator Communication Manager (OPCOM) |
 |
OPCOM uses the following components:
| Component | Description | For More Information |
|---|---|---|
|
OPCOM process
|
The system
process that manages OPCOM operations. Unless you disable it, the
OPCOM process starts automatically at system startup time.
|
Starting OPCOM
|
|
Operator terminals
|
Terminals designated
to display messages broadcast by OPCOM. Usually, the console terminal
(with the device name OPA0:) is the operator terminal. However,
you can designate any user terminal as an operator terminal.
|
Designating Operator Terminals
|
|
Operator log
file
|
A file that
records messages broadcast by OPCOM. The file is named SYS$MANAGER:OPERATOR.LOG.
|
HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems
|
|
OPCOM messages
|
Messages broadcast
by OPCOM. These messages are displayed on operator terminals and
written to the operator log file. The messages might be general messages
sent by you, user requests, operator replies, or system events.
|
HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems
|
|
REPLY and REQUEST commands
|
DCL commands that allow
you to use and control OPCOM.
|
Sending Messages to Users,
Sending Requests to an Operator, and
Replying to Operator Requests
|
OPCOM uses the following defaults:
OPCOM has the following requirements:
Starting OPCOM
The OPCOM process starts
automatically during system startup, unless it is disabled. You
might need to start OPCOM interactively if a software problem causes
the process to fail and prevents OPCOM from restarting automatically.
To start OPCOM, enter the following command from the system manager's account (SYSTEM):
If a software problem causes OPCOM to fail, contact your HP support representative. Be sure to keep the process dump file named SYS$SYSTEM:OPCOM.DMP. (When OPCOM fails, it creates this file.)$@SYS$SYSTEM:STARTUP OPCOM
Sending Messages to Users
To broadcast
a message to users, enter the DCL command REPLY as follows:REPLY [/qualifier...] ["message-text"]
For example:
Use the following qualifiers to control OPCOM messages:$REPLY/ALL/BELL "Please log off"
| Qualifier | Description |
|---|---|
|
/ALL
|
Broadcasts a message to
all terminals that are attached to the system or cluster. These
terminals must be turned on and have broadcast-message reception
enabled.
|
|
/BELL
|
Rings a bell at the terminal
receiving a message when entered with the /ALL, /TERMINAL, or /USERNAME qualifier;
two bells when entered with the /URGENT qualifier; and three bells
when entered with the /SHUTDOWN qualifier.
|
|
/NODE[=(node-name[,...])
|
Broadcasts a message to
the local cluster node only, or to a node or nodes you specify.
|
|
/SHUTDOWN
|
Sends a message beginning "SHUTDOWN...";
if used with the /BELL qualifier, rings three bells at terminals receiving
the message.
|
|
/TERMINAL=(terminal-name[,..])
|
Broadcasts the message to
the specified terminals.
|
|
/URGENT
|
Broadcasts a message beginning "URGENT...";
if used with the /BELL qualifier, rings two bells at terminals receiving
the message.
|
|
/USERNAME=(username[,...])
|
Broadcasts a message to all terminals
at which users are logged in to the system (or cluster), or only
to the terminals of the specified users.
|
For more information, refer to the HP OpenVMS DCL Dictionary.
The REPLY command in the following example sends a message to all users logged in to node WLDWND. When the message is displayed, a bell rings at the terminal.
The REPLY command in the following example sends a message to the user logged in at terminal TTC1. When the message is displayed, a bell rings at that terminal.$REPLY/ALL/BELL/NODE=WLDWND "Please log off"
$REPLY/BELL/TERMINAL=TTC1: "Your file has completed printing"
Controlling the Use of OPA0: as an Operator
Terminal
By default, OPCOM enables OPA0: as an operator terminal except
on workstations in clusters (unless the workstation is the first
system into the cluster). OPCOM determines whether a system is a
workstation by testing the system for a graphics device. Specifically,
this test is:
F$DEVICE ("*", "WORKSTATION", "DECW_OUTPUT")You can control the use of OPA0: as an operator terminal,
whether or not the node is a workstation or part of an OpenVMS Cluster
system, by defining the following logicals in SYS$MANAGER:SYLOGICALS.COM:| Logical Name | Function |
|---|---|
|
OPC$OPA0_ENABLE
|
Defined as True or False;
if True, specifies that OPA0: is to be enabled as an operator terminal.
|
|
OPC$OPA0_CLASSES
|
Specifies the operator classes that are
enabled for OPA0. The logical name can be a search list of the allowed
classes, a comma-separated list, or a combination of the two. If
you specify an invalid class, all classes are enabled, and a message
similar to the following is displayed on the console at system startup
and logged to the OPERATOR.LOG file:
%%%%%%%%%%% OPCOM 18-MAY-2000 13:28:33.12 %%%%%%%%%%% "BADCLASS" is not a valid class name in OPC$OPA0_CLASSESSee Designating Operator Terminals for a description of the valid operator classes. |
The logicals take effect the next time you boot the system.
Designating Operator Terminals
Normally, the console terminal
(with the device name OPA0:) is automatically an operator terminal
except for workstations in an OpenVMS Cluster environment. However,
you can designate any terminal as an operator terminal. You can
also disable a previously designated operator terminal.
To designate a terminal as an operator terminal, enter the REPLY/ENABLE command at the terminal. For example:
To designate an operator's terminal in batch or in startup command procedures, SYS$COMMAND must be assigned to a valid terminal device.$REPLY/ENABLE$ %%%%%%%%%%% OPCOM 13-JUL-2000 11:30:30.56 %%%%%%%%%%% Operator _BHAK$FTA20: has been enabled, username SYSTEM
If your facility is large, there may be several operators, each of whom is assigned to specific tasks. If this is the case, you can specify the classes of messages the operator terminal receives and responds to when you enable the operator terminal, as follows:REPLY/ENABLE=(keyword[,...])
where keyword is an operator class described in the following table:
| Keyword (operator class) | Description |
|---|---|
|
CARDS
|
Displays messages sent to
the card readers.
|
|
CENTRAL
|
Displays messages sent to
the central system operator.
|
|
CLUSTER
|
Displays messages from the
connection manager pertaining to OpenVMS Cluster system state changes.
|
|
DEVICES
|
Displays messages pertaining
to mounting disks.
|
|
DISKS
|
Displays messages pertaining
to mounting and dismounting disk volumes.
|
|
LICENSE
|
Displays messages pertaining
to software licenses.
|
|
NETWORK
|
Displays messages pertaining
to networks; the keyword CENTRAL must also be specified to inhibit
network messages.
|
|
OPER1 to OPER12
|
Displays messages sent to
operators identified as OPER1 to OPER12.
|
|
PRINTER
|
Displays messages pertaining
to print requests.
|
|
SECURITY
|
Allows messages pertaining
to security events; requires SECURITY privilege.
|
|
TAPES
|
Allows messages pertaining to mounting
and dismounting tape volumes.
|
For example:
Disabling Operator Terminals$REPLY/ENABLE=(PRINTER,OPER3)
A terminal that you designate as an operator's terminal remains enabled even when the operator logs out. To return the terminal to normal (nonoperator) status, enter the REPLY/DISABLE command from the terminal.
The following example designates terminal TTA3 as an operator terminal, enabling it to receive messages concerning printers, magnetic tapes and disks, and messages intended for the central operator. Later, it relinquishes terminal TTA3's ability to receive messages concerning tapes. The terminal still receives and can respond to messages about disks and printers and messages directed to CENTRAL.
$REPLY/ENABLE=(PRINTER,DISKS,TAPES,CENTRAL)$ %%%%%%%%%%% OPCOM 13-JUL-2000 11:37:09.52 %%%%%%%%%%% Operator TTA3 has been enabled, username SYSTEM $ %%%%%%%%%%% OPCOM 13-JUL-2000 11:37:09.53 %%%%%%%%%%% Operator status for operator TTA3 CENTRAL, PRINTER, DISKS, TAPES$REPLY/DISABLE=TAPES%%%%%%%%%%% OPCOM 13-JUL-2000 11:37:09.53 %%%%%%%%%%% Operator status for operator TTA3 CENTRAL, PRINTER, DISKS$REPLY/DISABLE%%%%%%%%%%% OPCOM 13-JUL-2000 11:38:50.68 %%%%%%%%%%% Operator TTA3 has been disabled, username SYSTEM
Sending
Requests to an Operator
In sites where operators are assigned to assist users by mounting
volumes and changing printer forms, users can communicate with operators
by entering the DCL command REQUEST and the following qualifiers:
| Qualifier | Description |
|---|---|
|
/REPLY
|
Sends a request and requests
a reply to the message. Requests sent with this command are issued
a unique identification number to which the operator sends the response.
The user cannot enter any commands until the operator responds.
|
|
/TO=((operator)[,...])
|
If your facility is large, there may
be several operators, each of whom has specific tasks. The /TO qualifier
lets users send requests to a specific operator. Options are as
follows: CARDS, CENTRAL, CLUSTER, DEVICES, DISKS, NETWORK, OPER1
to OPER12, PRINTER, SECURITY, TAPES.
|
The DCL commands MOUNT/ASSIST and BACKUP/ASSIST also request operator assistance. For more information, see the following sections:
An operator is monitoring an operator terminal enabled for the PRINTER class. The following PRINT command submits an output job that requires a special print form (/FORM=LETTER). The REQUEST command sends a message to the operator. After completing the request, the operator would send a reply, as explained in Replying to Operator Requests.
$PRINT/COPIES=2/QUEUE=LQ_PRINT REPORT.OUT/FORM=LETTERJob REPORT (queue LQA1, entry 401) pending$REQUEST/REPLY/TO=PRINTER -_$"Have queued job 401 as FORM=LETTER; can you print it?"%OPCOM-S-OPRNOTIF, operator notified, waiting...10:42:16.10 %OPCOM-S-OPREPLY, AFTER 11:00 19-APR-2000 10:25:32.40, request 3 completed by operator OPA0
Replying to Operator Requests
In sites where
operators are assigned to assist users by mounting volumes and changing
printer stock, operators can reply to user requests using the DCL
command REPLY and the following qualifiers:
| Qualifier | Description |
|---|---|
|
/ABORT=identification-number
|
Replies to the request specified
by the identification number and cancels the request.
|
|
/PENDING=identification-number
|
Replies to the request specified
by the identification number and prevents the user from entering
other commands until the operator fulfills or aborts the request.
The current terminal must be enabled as an operator terminal.
|
|
/STATUS
|
Reports which classes are
enabled, and all outstanding user requests for the terminal from
which this command was entered. The current terminal must be enabled
as an operator terminal.
|
|
/TO=identification-number
|
Replies to the request specified by the
identification number and completes the request. The current terminal
must be enabled as an operator terminal.
Note that you can also use a variation of the REPLY/TO command in response to a MOUNT/ASSIST and BACKUP/ASSIST commands. For more information, see Assisting Users in Mounting Volumes and Requesting Operator Assistance. |
An operator working with magnetic tapes would also use additional REPLY qualifiers specific to magnetic tape operations. For more information, see Sending Messages Back to Users. For detailed information about the REPLY command and its qualifiers, refer to the HP OpenVMS DCL Dictionary.
In the following example, the REPLY/TO command replies to operator request number 5, issued by user ROBINSON. The MOUNT device is switched to DUA4, and the user is notified.
%%%%%%%%%% OPCOM, 19-APR-2000 10:20:50.39 %%%%%%%%%%% request 5 from user ROBINSON Please mount volume GRAPHIC_FILES in device _DUA11: Shelf 4 - slot B$REPLY/TO=5 "SUBSTITUTE DUA4"
1 These functions are used in sites where operators are assigned to help users mount disk or tape volumes and printer forms.
( Number takes you back )
|
|