Document revision date: 19 July 1999

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):

$ @SYS$SYSTEM:STARTUP OPCOM

If a software problem causes OPCOM to fail, contact your Compaq support representative. Be sure to keep the process dump file named SYS$SYSTEM:OPCOM.DMP. (When OPCOM fails, it creates this file.)

2.4.3 Sending Messages to Users

To broadcast a message to users, enter the DCL command REPLY 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 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 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.4 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 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.

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

2.4.5 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.

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-1998 11:30:30.56 %%%%%%%%%%% Operator _BHAK$FTA20: has been enabled, username SYSTEM

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 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[,...])

The following table describes each keyword:

Keyword	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:

$ 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 return the terminal to normal (nonoperator) status, enter the REPLY/DISABLE command from the terminal.

Example

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-1998 11:37:09.52 %%%%%%%%%%% Operator TTA3 has been enabled, username SYSTEM $ %%%%%%%%%%% OPCOM 13-JUL-1998 11:37:09.53 %%%%%%%%%%% Operator status for operator TTA3 CENTRAL, PRINTER, DISKS, TAPES $ REPLY/DISABLE=TAPES %%%%%%%%%%% OPCOM 13-JUL-1998 11:37:09.53 %%%%%%%%%%% Operator status for operator TTA3 CENTRAL, PRINTER, DISKS $ REPLY/DISABLE %%%%%%%%%%% OPCOM 13-JUL-1998 11:38:50.68 %%%%%%%%%%% Operator TTA3 has been disabled, username SYSTEM

2.4.6 Sending Requests to an Operator

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

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

$ 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-1998 10:25:32.40, request 3 completed by operator OPA0

2.4.7 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 Section 8.5.3 and Section 10.9.1.

An operator working with magnetic tapes would also use additional REPLY qualifiers specific to magnetic tape operations. For more information, see Section 8.8.2.4. For detailed information about the REPLY command and its qualifiers, refer to 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-1998 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"

2.5 Using VMSKITBLD.COM to Modify a System Disk

On VAX systems, the command procedure SYS$UPDATE:VMSKITBLD.COM allows you to duplicate system files from an existing system disk on another disk.

On Alpha systems, procedures similar to those in the VMSKITBLD.COM procedure are performed by the AXPVMS$PCSI_INSTALL.COM procedure. refer to the OpenVMS Alpha Version 7.2 Upgrade and Installation Manual.

The SYS$UPDATE:VMSKITBLD.COM procedure offers the following options:

Option	Description	For More Information
BUILD	Builds a new common system disk after destroying all existing files on the disk.	Section 2.5.1
COPY	Copies the operating system files to an existing disk without destroying nonsystem files that are currently on the disk.	Section 2.5.2
ADD	Adds a new system root directory to an existing system disk.	Section 2.5.3

VMSKITBLD uses two disks:

Disk	Description
Source disk	The disk from which you copy system files. The source disk must be an existing system disk.
Target disk	The disk to which you move the system files.

At some point, you might want to create a new system disk. For example, suppose that your existing system disk is an RA81 disk. If you purchase a larger RA90 disk and want to use it as your system disk, you could use the VMSKITBLD BUILD option to build a new system disk on the RA90 disk.

The existing system disk is the source disk. The new disk is the target disk.

If you want to build your operating system on another disk and you are not concerned about losing the current contents of the target disk, use the BUILD option as described in the following procedure.

How to Perform This Task

1. If the source disk is not the current booted system disk, boot the operating system from the source disk.
2. Log in to the SYSTEM account.
3. Make sure the disk is spun up and on line. If you are using a removable disk, you must also place the disk into the appropriate drive.
4. Enter the following command to invoke VMSKITBLD:

   $ @SYS$UPDATE:VMSKITBLD

   VMSKITBLD prompts you to choose one of the following options:

   * Operation [BUILD,ADD,COPY]?

5. Enter BUILD and press Return. VMSKITBLD displays messages that either prompt you for information needed to complete the operation or inform you of the procedure's status.
   1. In response to the following prompt, enter the name of the source disk:

      * Enter mounted SOURCE disk name (ddcu:):

   2. In response to the following prompt, enter the top-level system directory for the source disk:

      * Enter SOURCE disk top-level system directory [default = SYS0]:

      
      In most cases, you can choose the default value [SYS0].

   3. In response to the following prompt, enter the name of the target disk:

      * Enter TARGET disk name (ddcu:):

   4. In response to the following prompt, enter the volume label of the target disk:

      * Enter the TARGET disk's label [default = VAXVMSRL5]:

   5. In response to the following prompt, enter the top-level system directory:

      * Enter TARGET disk top-level system directory [default = SYS0]:

      
      In most cases, you can choose the default value [SYS0].

   6. The procedure displays the following message to warn you that the target disk will be initialized and to allow you to stop the procedure:

      The target disk will be initialized. * Target disk, _DUA0:, ready to be initialized? (Y/N): Y

      
      Make sure it is safe to destroy the contents of the target disk, and enter Y to continue.

   
   When the system displays the dollar sign ($) prompt, the system disk is built. VMSKITBLD automatically dismounts the target disk. At this point, the target disk contains all the operating system files required for a complete system.
6. Complete the system disk by creating a rights database and network proxy database and configuring the system with appropriate system parameters. For instructions, see Section 2.5.1.1.
7. To use the new system disk, reboot the system with the new system disk.

Example

The following example runs VMSKITBLD.COM to build a new system disk. It copies the files on the current system disk to create a new system disk on the DUA0: disk.

* Enter mounted SOURCE disk name (ddcu:): SYS$SYSDEVICE: * Enter SOURCE disk top level system directory [default = SYS0]: [Return] * Enter TARGET disk name (ddcu:): DUA0: [Return] * Enter the TARGET disk's label [default = VAXVMSRL5]: [Return] * Enter TARGET disk top level system directory [default = SYS0]: [Return] The target disk will be initialized. * Target disk, _DUA0:, ready to be initialized? (Y/N): Y Target disk, _DUA0:, has been initialized. %MOUNT-I-MOUNTED, VAXVMSRL5 mounted on _DUA0: Creating system specific directories ... Creating cluster common directories ... Creating SYSGEN files ... %SYSGEN-I-CREATED, _DUA0:<SYS0.SYSEXE>SWAPFILE.SYS;1 created %SYSGEN-I-CREATED, _DUA0:<SYS0.SYSEXE>PAGEFILE.SYS;1 created %SYSGEN-I-CREATED, _DUA0:<SYS0.SYSEXE>SYSDUMP.DMP;1 created Copying files from source disk ... Copying DECwindows file from source disk ... Writing a boot block ... System disk complete. $

2.5.1.1 Completing a System Disk Built with VMSKITBLD.COM

After you create a new system disk using the VMSKITBLD BUILD option, use the following procedure to complete the new system disk:

1. Boot the new system disk using a conversational boot. For instructions, refer to the upgrade and installation supplement for your computer.
2. When the SYSBOOT> prompt appears, enter the USE DEFAULT command to boot with default values for all system parameters.
3. To avoid starting all layered products on a system that is not tuned for them, possibly causing the system to hang, enter SET STARTUP_P1 "MIN" after the SYSBOOT> prompt.
4. Enter the CONTINUE command to continue booting.
5. After the system boots, log in to the SYSTEM account. The password for the system account will be the default password, MANAGER. Make sure you change this password.
6. Use the Authorize utility to create a rights database and a network proxy database. For more information, refer to the OpenVMS Guide to System Security.
7. Run AUTOGEN from the SAVPARAMS phase to set appropriate values for system parameters. Be sure to specify the CHECK_FEEDBACK option. See Section 14.5 and the AUTOGEN section of the OpenVMS System Management Utilities Reference Manual for detailed information about running AUTOGEN.
   To reboot from the former system disk, specify REBOOT as the end phase when invoking AUTOGEN.
   To reboot the system from the new system disk, specify SHUTDOWN as the end phase and reboot manually, specifying the new system disk.

Example

SYSBOOT> USE DEFAULT SYSBOOT> SET STARTUP_P1 "MIN" SYSBOOT> CONTINUE . . . $ SET DEFAULT SYS$COMMON:[SYSEXE] $ RUN AUTHORIZE UAF> CREATE/RIGHTS UAF> CREATE/PROXY UAF> EXIT $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT CHECK_FEEDBACK . . .

	privacy and legal statement
6017PRO_003.HTML