[next] [previous] [contents]

  2.4 Using OPCOM to Communicate with System Users
  The operator communication manager (OPCOM) is a tool
  for communicating with users and operators on the system.
  OPCOM allows you to perform the following functions.

  Function

                                                                      For More
                                                                      Information


  To broadcast messages to users who are logged in Section 2.4.2
  To control the use of OPA0: as an operator terminal Section 2.4.3
  To designate terminals as operator terminals,
  enabling them to display messages broadcast by
  OPCOM

                                                                      Section 2.4.4
  To record messages broadcast by OPCOM in a log
  file

                                                                      Section 18.6.3
  To send requests to an operator

                                          1
                                                                      Section 2.4.5
  To reply to operator requests

                                      1
                                                                      Section 2.4.6


  1
    These functions are used in sites where operators are assigned to help users mount
  disk or tape volumes and printer forms

  Figure 2-2 illustrates the function of OPCOM.


  OPCOM Components
  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.

                                                                                  Section 2.4.1
  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.

                                                                                  Section 2.4.4
  Operator log file A file that records messages broad-
                                cast by OPCOM. The file is named
                                SYS$MANAGER:OPERATOR.LOG.

                                                                                  Section 18.6
  OPCOM messages Messages broadcast by OPCOM. These mes-
                                sages are displayed on operator terminals
                                and written to the operator log file. The mes-
                                sages might be general messages sent by
                                you, user requests, operator replies, or system
                                events.

                                                                                  Section 18.6.2
  REPLY and REQUEST
  commands

                                DCL commands that allow you to use and
                                control OPCOM.

                                                                                  Section 2.4.2,
                                                                                  Section 2.4.5,
                                                                                  and
                                                                                  Section 2.4.6


  OPCOM Defaults
  OPCOM uses the following defaults:

  .
        OPCOM is started by default on all systems.
  .
        Except for workstations in a VMScluster environ-
        ment, OPCOM logs messages to OPA0:, which is en-
        abled by default as an operator terminal. The log file
        SYS$MANAGER:OPERATOR.LOG is opened, and all
        OPCOM classes are enabled on both the operator termi-
        nal and the log file.

        Section 2.4.3 explains how to control the use of OPA0: as
        an operator terminal. Section 18.6.3.2 explains how to
        specify the default state of operator log files.

  OPCOM Requirements
  OPCOM has the following requirements:

  .
        To execute an OPCOM REPLY command, OPCOM
        must be running, and you must enter the REPLY com-
        mand from a terminal device designated as an operator
        terminal.
  .
        The OPCOM REPLY command requires at least OPER
        privilege. You must have SHARE privilege if another
        process is logged in to the designated operator terminal.
        To enable or disable the security class, you must have
        SECURITY privilege.
  .
        To designate an operator terminal in batch or SYSTARTUP,
        you must assign SYS$COMMAND to a valid terminal
        device.

  2.4.1 Starting OPCOM
  The OPCOM process must be running to execute the
  OPCOM REPLY command. The OPCOM process starts
  automatically during system startup, unless it is disabled. You
  might need to start OPCOM interactively if a software prob-
  lem 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):
  $ @SYS$SYSTEM:STARTUP OPCOM

  If a software problem causes OPCOM to fail, submit
  a software problem report (SPR) to report the prob-
  lem to Digital. Include the process dump file named
  SYS$SYSTEM:OPCOM.DMP. When OPCOM fails, it cre-
  ates this file to allow Digital representatives to determine the
  cause of the failure.

  2.4.2 Sending Messages to Users
  To broadcast a message to users, enter the REPLY command
  as follows:
  REPLY [/qualifier...] ["message-text"]

  For example:
  $ REPLY/ALL/BELL "Please log off"

  Use the following qualifiers to control OPCOM messages:


  Qualifier Description

  /ALL Broadcasts a message to all ter-
                                            minals that are attached to the
                                            system or VMScluster. These ter-
                                            minals must be turned on and
                                            have broadcast-message reception
                                            enabled.
  /BELL Rings a bell at the terminal receiv-
                                            ing a message when entered with
                                            the /ALL, the /TERMINAL, or the
                                            /USERNAME qualifier; two bells
                                            when entered with the /URGENT
                                            qualifier; and three bells when
                                            entered with the /SHUTDOWN quali-
                                            fier.
  /NODE[=( node-name [,...]) Broadcasts a message to the local
                                            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 speci-
                                            fied 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 termi-
                                            nals at which users are logged in
                                            to the system (or VMScluster), or
                                            only to the terminals of the specified
                                            users.


  For more information, see the OpenVMS DCL Dictionary .

  Examples
  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.
  $ REPLY/ALL/BELL/NODE=WLDWND "Please log off"

  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/BELL/TERMINAL=TTC1: "Your file has completed printing"

  2.4.3 Controlling the Use of OPA0: as an Operator
            Terminal
  You can control the use of OPA0: as an operator terminal,
  whether or not the node is part of a VMScluster 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.

  The logicals take effect the next time you boot the system.

  2.4.4 Designating Operator Terminals
  Normally, the console terminal (with the device name OPA0:)
  is automatically an operator terminal except for workstations
  in a VMScluster environment. However, you can designate
  any terminal as an operator terminal. You can also disable a
  previously designated operator terminal.

  Enabling Operator Terminals
  To designate a terminal as an operator terminal, enter the
  REPLY/ENABLE command at the terminal. For example:
  $ REPLY/ENABLE
  $
  %%%%%%%%%%% OPCOM 13-JUL-1995 11:30:30.56 %%%%%%%%%%%
  Operator _BHAK$FTA20: has been enabled, username SYSTEM

  The REPLY/ENABLE command requires OPER privilege.
To designate an operator's terminal in batch or in startup
  command procedures, SYS$COMMAND must be assigned to
  a valid terminal device.

  If your facility is very 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 termi-
  nal receives and responds to when you enable the operator
  terminal, as follows:
  REPLY/ENABLE=(class[,...])

  The following table describes each class of messages:


  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 VMScluster state changes.
  DEVICES Displays messages pertaining to mounting disks.
  LICENSE Displays messages pertaining to 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:
  $ REPLY/ENABLE=(PRINTER,OPER3)

  Disabling Operator Terminals
  A terminal that you designate as an operator's terminal
  remains enabled even when the operator logs out. To re-
  turn the terminal to normal (nonoperator) status, enter the
  REPLY/DISABLE command from the terminal.

  Example
  The following example designates terminal TTA3 as an op-
  erator 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-1995 11:37:09.52 %%%%%%%%%%%
  Operator TTA3 has been enabled, username SYSTEM
  $
  %%%%%%%%%%% OPCOM 13-JUL-1995 11:37:09.53 %%%%%%%%%%%
  Operator status for operator TTA3
  CENTRAL, PRINTER, DISKS, TAPES
  $ REPLY/DISABLE=TAPES
  %%%%%%%%%%% OPCOM 13-JUL-1995 11:37:09.53 %%%%%%%%%%%
  Operator status for operator TTA3
  CENTRAL, PRINTER, DISKS
  $ REPLY/DISABLE
  %%%%%%%%%%% OPCOM 13-JUL-1995 11:38:50.68 %%%%%%%%%%%
  Operator TTA3 has been disabled, username SYSTEM

  2.4.5 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 REQUEST com-
  mands 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 very large, there may be
                                several operators, each of whom has spe-
                                cific tasks. The /TO qualifier lets users send
                                requests to a specific operator. Options are
                                as follows: CARDS, CENTRAL, CLUSTER,
                                DEVICES, DISKS, LICENSE, 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:

  .
        For MOUNT requests, see Section 8.5.3.
  .
        For BACKUP requests, see Section 10.9.1.

  Example
  Assume an operator is monitoring an operator terminal
  enabled for the PRINTER class. The following PRINT com-
  mand 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 Section 2.4.6.
  $ PRINT/COPIES=2/QUEUE=LQ_PRINT REPORT.OUT/FORM=LETTER
  Job 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-1995 10:25:32.40, request 3 completed by operator OPA0

  2.4.6 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 REPLY commands. Operators
  can use the following qualifiers:

  Qualifier Description


  /ABORT= id-
  number

                              Replies to the request specified by the identifica-
                              tion number and cancels the request.
  /PENDING Replies to the request specified by the identifica-
                              tion 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 out-
                              standing user requests for the terminal from
                              which this command was entered. The cur-
                              rent terminal must be enabled as an operator
                              terminal.
  /TO= id-number Replies to the request specified by the identifi-
                              cation 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 Section 8.5 and
                              Section 10.9.1.


  An operator working with magnetic tapes would also use ad-
  ditional REPLY qualifiers specific to magnetic tape operations.
  For more information, see Section 8.8.2.4. For detailed infor-
  mation on the REPLY command and its qualifiers, see the
  OpenVMS DCL Dictionary .

  Example
  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-1995 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"