HP OpenVMS DCL Dictionary
HP OpenVMS DCL Dictionary
For complete information on specifying time values, refer to the
OpenVMS User's Manual or the online help topic DCL_Tips (subtopic Date_Time).
/STYLE=keyword
Specifies the file name format for display purposes.
The valid keywords for this qualifier are CONDENSED and EXPANDED.
Descriptions are as follows:
| Keyword |
Explanation |
|
CONDENSED (default)
|
Displays the file name representation of what is generated to fit into
a 255-length character string. This file name may contain a DID or FID
abbreviation in the file specification.
|
|
EXPANDED
|
Displays the file name representation of what is stored on disk. This
file name does not contain any DID or FID abbreviations.
|
The keywords CONDENSED and EXPANDED are mutually exclusive. This
qualifier specifies which file name format is displayed in the output
message, along with the confirmation if requested.
File errors are displayed with the CONDENSED file specification unless
the EXPANDED keyword is specified.
Refer to the OpenVMS User's Manual for more information.
Examples
| #1 |
$ RENAME AVERAGE.OBJ OLDAVERAGE
|
The RENAME command in this example renames the highest existing version
of the file AVERAGE.OBJ to OLDAVERAGE.OBJ. If no file named
OLDAVERAGE.OBJ currently exists, the new file is assigned a version
number 1.
| #2 |
$ RENAME/NONEW_VERSION SCANLINE.OBJ;2 BACKUP.OBJ
|
The RENAME command in this example renames the file SCANLINE.OBJ;2 to
BACKUP.OBJ;2. The /NONEW_VERSION qualifier ensures that, if
BACKUP.OBJ;2 already exists, the RENAME command does not rename the
file, but instead reports the error.
| #3 |
$ RENAME *.TXT;* *.OLD;*
|
The RENAME command in this example renames all versions of all files
with the file type TXT to have the file type OLD. The file names and
version numbers are not changed.
| #4 |
$ RENAME WATER.TXT [.MEMOS]
|
The RENAME command in this example changes the directory name of
WATER.TXT from your default directory to the MEMOS subdirectory. (The
RENAME command moves the file to another directory.)
| #5 |
$ RENAME [BORDERS.TESTFILES]SAVE.DAT []TEST
|
The RENAME command in this example renames the file SAVE.DAT in the
directory BORDERS.TESTFILES to TEST.DAT. The new file is moved to the
current default directory.
| #6 |
$ RENAME COEISABLAST.TXT COEIsABlast.txt
|
The RENAME command in this example changes the case of COEISABLAST.TXT
to COEIsABlast.txt. You must be on an ODS-5 disk and previously have
used the SET PROCESS/CASE_LOOKUP=SENSITIVE command for this RENAME
command to work properly.
| #7 |
$ RENAME/LOG
$_From: DATA.*,INFO.*
$_To: NEW
%RENAME-I-RENAMED, _DISK0:[SYSTEM]DATA.AAA;1 renamed to _DISK0:[SYSTEM]NEW.AAA;1
%RENAME-I-RENAMED, _DISK0:[SYSTEM]DATA.BBB;1 renamed to _DISK0:[SYSTEM]NEW.BBB;1
%RENAME-I-RENAMED, _DISK0:[SYSTEM]DATA.CCC;1 renamed to _DISK0:[SYSTEM]NEW.CCC;1
%RENAME-I-RENAMED, _DISK0:[SYSTEM]INFO.001;1 renamed to _DISK0:[SYSTEM]NEW.001;1
%RENAME-I-RENAMED, _DISK0:[SYSTEM]INFO.002;1 renamed to _DISK0:[SYSTEM]NEW.002;1
%RENAME-I-RENAMED, _DISK0:[SYSTEM]INFO.003;1 renamed to _DISK0:[SYSTEM]NEW.003;1
$
|
In this example, three files exist with the file name of DATA, and
three files have the file name of INFO. This RENAME command illustrates
the asterisk (*) wildcard character in the input file names and the use
of temporary default file types and version numbers on the output
files. The result is the renaming of all six files as displayed by the
/LOG qualifier.
| #8 |
$ RENAME NODE1::DISK2:[SMITH]ASSEMSHT.EXE NODE1::DISK3:[JONES]ASSEMBLYSHEET.EXE
|
The RENAME command in this example renames the file ASSEMSHT.EXE in the
SMITH directory on remote node NODE1 and disk DISK3 to
ASSEMBLYSHEET.EXE in the JONES directory on the same remote node and
disk. You can rename a file on another node and disk only if the new
file resides on that same node and disk.
REPLY
Broadcasts a message to a terminal or terminals.
See the qualifier descriptions for restrictions.
Format
REPLY [message-text]
Parameter
message-text
Specifies the text of the message. The text must be 1 to 511
characters. Enclose the text in quotation marks (" ") if it
contains spaces, special characters, or lowercase characters.
Description
All users with OPER (operator) privilege can use the REPLY command to
communicate with system users. The REPLY command does the following:
- Displays messages at users' terminals
- Responds to user requests
- Responds to magnetic tape file system requests
- Enables and disables operator status on a terminal (if the operator
communication process [OPCOM] is running)
- Closes the operator's log file and opens a new one (if OPCOM is
running)
You must always use one or more qualifiers with the REPLY command in
order for it to be meaningful. If you use the REPLY command without
using any qualifiers, an error message is returned. When you use the
REPLY command for any purpose other than displaying messages at users'
terminals, you must also use the /ENABLE=keyword qualifier. See the
description of the /ENABLE qualifier to determine the appropriate
keyword (or keywords) for your purpose.
Displaying Messages at Users' Terminals
To contact one or more system users, the operator enters one of the
following REPLY commands:
- REPLY/ALL message-text
- REPLY/TERMINAL=(terminal-name[,...]) message-text
- REPLY/USERNAME[=(username[,...])] message-text
The /ALL qualifier sends a message to all terminals that are on line
and are connected to the OpenVMS system or OpenVMS Cluster. Generally,
when an important message is to be broadcast, such as information about
a system shutdown, you should use the /ALL qualifier.
The /TERMINAL qualifier sends a message to one or more specific
terminals on the system or cluster.
The /USERNAME qualifier sends a message to terminals at which one or
more system or cluster users are logged in.
Note that the /TO qualifier is not used under these three
circumstances, because the operator is not replying to a specific
request from either the file system or a user.
To broadcast to a terminal other than your own, you must have OPER
privilege. The REPLY command is not complete until all terminals you
are broadcasting to have received the message.
Responding to User Requests
When a user enters the REQUEST/REPLY command, the process associated
with the requesting user's terminal is put
in a wait state until the operator responds by using one of the
following REPLY commands:
- REPLY/ABORT=identification-number message-text
- REPLY/PENDING=identification-number message-text
- REPLY/TO=identification-number message-text
The /ABORT qualifier indicates that the user's request has been
canceled.
The /PENDING qualifier sends a message to the user and keeps the user's
process in a wait state until the request can be fulfilled or aborted.
The /TO qualifier indicates that the user's request has been fulfilled.
When a user enters the REQUEST/REPLY command, the message is displayed
at the system console terminal. For example:
%OPCOM, 24-DEC-2001 09:49:24.47, request 3, from user SYSTEM
_TTB6:, This is a sample request
|
The user cannot enter any further commands until the operator responds
using the /ABORT or the /TO qualifier, or until the user aborts the
request. If the operator does not respond and the user does not abort
the request, the request is repeated at 5-minute intervals on the
operator's terminal until the operator replies.
The REPLY command is an essential part of the procedures that operators
must use in order for users to gain access to tape and disk volumes.
Responding to File System Requests
When a multivolume tape volume reaches the end-of-tape (EOT) mark, the
magnetic tape file system suspends processing
and sends a message to the operator to mount the next tape. The
operator responds using one of the following REPLY commands:
- REPLY/TO=identification-number label
- REPLY/INITIALIZE_TAPE=identification-number label
- REPLY/BLANK_TAPE=identification-number label
- REPLY/ABORT=identification-number
The /TO qualifier indicates that the file system request has been
fulfilled. When the request from the magnetic tape file system
specifies a volume label, the operator mounts the specified tape and
enters the REPLY/TO command; however, if the file system requests a new
volume, the operator can reuse a scratch volume by mounting it and by
entering the REPLY/INITIALIZE_TAPE command. The operator also can mount
a blank volume and then enter the REPLY/BLANK_TAPE command. In any
case, the operator may add the message "label" to the REPLY
command to specify the volume's label. The quotation marks ("
") are required syntax.
If the request is "REMOUNT" or "MOUNT NEW", the
label is required in the message text. If the request is
"MOUNT", no label is needed.
The /ABORT qualifier indicates that the file system request has been
canceled.
Enabling and Disabling Operator Status on a Terminal
Any terminal connected to the operating system can be established as an
operator's terminal if OPCOM is running.
When an operator who is logged in to an account with OPER (operator)
privilege enters the REPLY/ENABLE command at the designated terminal,
that terminal can be used to respond to user requests and to monitor
device status. Such a terminal retains operator status until it is
specifically disabled, or until the end of the current interactive
session, if it was established as a temporary operator's terminal (see
the description of the /TEMPORARY qualifier).
Operator messages are printed on the system console terminal unless
that terminal is explicitly disabled as an operator's terminal.
When the operator enters the REPLY/ENABLE command, OPCOM confirms that
the terminal has been enabled. For example:
%OPCOM, 24-DEC-2001 10:22:19.75, operator status for operator OPA0
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE,
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
|
When the operator enters the REPLY/DISABLE command, OPCOM uses the
following message to confirm that the terminal is no longer an operator
terminal:
%OPCOM, 24-DEC-2001 10:03:23.48, operator disabled, operator OPA0
|
To grant specific operator status on a particular terminal, the
operator includes one or more keywords after the /ENABLE qualifier. For
example, to establish a terminal as an operator terminal that can
receive messages pertaining to mounting and dismounting tapes and
disks, the operator enters the following:
$ REPLY/ENABLE=(DISKS,TAPES)
|
%OPCOM, 24-DEC-2001 10:04:00.18, operator enabled, operator OPA0
$
%OPCOM, 24-DEC-2001 10:04:00.47, operator status for operator OPA0
TAPES, DISKS
|
OPCOM confirms that the terminal has operator status for tape and disk
messages.
To discontinue specific operator status, the operator includes one or
more keywords after the /DISABLE qualifier. For example, to inhibit an
operator terminal from receiving messages pertaining to mounting and
dismounting disks, the operator enters the following command:
%OPCOM, 24-DEC-2001 10:04:30.83, operator status for operator OPA0
TAPES
|
Note that OPCOM lists the specific operator status still assigned to
the terminal.
When an operator disables operator status on all terminals, including
the system console terminal, OPCOM records all subsequent messages in
the operator log file, except user requests and messages requiring an
operator reply.
%OPCOM-S-OPRNOTIF, operator notified, waiting. 10:06:03.25
%OPCOM-S-OPREPLY, %OPCOM 24-DEC-2001 10:06:03:25, no operator coverage
|
To determine the operator status and to obtain a list of pending
requests for a particular terminal, the operator enters the following
command:
This command also shows all outstanding requests for this operator.
Closing the Operator's Log File and Opening a New One
To close the current
operator's log file and open a new one, the operator enters the
REPLY/LOG command. If OPCOM is running, all subsequent messages are
recorded in the new log file. To close the current log file without
opening a new one, the operator enters the REPLY/NOLOG command. All
subsequent messages are not recorded until the operator enters the
REPLY/LOG command.
Qualifiers
/ABORT=identification-number
Sends a message to the user or magnetic tape file system corresponding
to the unique identification number and cancels the request.
/ALL
Requires OPER (operator) privilege.
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. The /ALL qualifier is incompatible
with the /USERNAME and /TERMINAL qualifiers.
/BELL
Rings a bell at the terminal receiving 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 qualifier.
/BLANK_TAPE=identification-number
Requires VOLPRO (volume protection) privilege.
Sends a message to the magnetic tape file system indicated by the
identification number to override the checking of volume label
information. The volume label must be specified in the
message-text parameter. The current terminal must be enabled
as an operator terminal for TAPES.
/DISABLE[=(keyword[,...])]
Requires OPER (operator) privilege. Requires
OPER and SECURITY privileges for security messages.
If the operator communication manager (OPCOM) is running, restores to
normal (that is, nonoperator) status the terminal at which the command
is entered. The /DISABLE qualifier cannot be entered from a batch job.
To restrict the types of messages displayed on an operator's terminal,
specify one of the following keywords:
|
CARDS
|
Inhibits messages sent to the card readers.
|
|
CENTRAL
|
Inhibits messages sent to the central system operator.
|
|
CLUSTER
|
Inhibits messages from the connection manager pertaining to cluster
state changes.
|
|
DEVICES
|
Inhibits messages pertaining to mounting disks.
|
|
DISKS
|
Inhibits messages pertaining to mounting and dismounting disk volumes.
|
|
LICENSE
|
Inhibits messages pertaining to software licenses.
|
|
NETWORK
|
Inhibits messages pertaining to networks; the keyword CENTRAL must also
be specified to inhibit network messages.
|
|
OPER1 to OPER12
|
Inhibits messages sent to operators identified as OPER1 to OPER12.
|
|
PRINTER
|
Inhibits messages pertaining to print requests.
|
|
SECURITY
|
Inhibits messages pertaining to security events; requires SECURITY
privilege.
|
|
TAPES
|
Inhibits messages pertaining to mounting and dismounting tape volumes.
|
When an operator logs out from a remote or a dial-in terminal, the
operator terminal is automatically disabled.
/ENABLE[=(keyword[,...])]
Requires OPER (operator) privilege. Requires
OPER and SECURITY privileges for security messages.
Designates as an operator's terminal the terminal at which the REPLY
command is entered, if OPCOM is running. The /ENABLE qualifier cannot
be entered from a batch job. To enable the following types of messages
displayed on an operator's terminal, specify one of the following
keywords:
|
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 cluster
state changes.
|
|
DEVICES
|
Displays messages pertaining to mounting disks.
|
|
DISKS
|
Displays messages pertaining to mounting and dismounting disk volumes.
|
|
LICENSE
|
Diplays 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.
|
/INITIALIZE_TAPE=identification-number
Sends a message to the magnetic tape file system indicated by the
identification number to initialize a magnetic tape volume. This
qualifier can be used whenever the file system requests the mounting of
a new volume. The system performs normal protection and expiration
checks before initializing the volume. The current terminal must be
enabled as an operator terminal for TAPES.
If the tape drive cannot read the volume, the mount fails and an error
message is returned. Use the /BLANK_TAPE qualifier to override the
checking of information on a volume label.
/LOG
/NOLOG
Requires OPER (operator) privilege.
Closes the current operator's log file and opens a new one if OPCOM is
running. The /NOLOG qualifier closes the current log file, but does not
open a new log file. The current terminal must be enabled as an
operator terminal. The operator can then examine the contents of the
previous log file.
/NODE[=(node-name[,...])]
Sends a message to the local cluster node only. The optional parameter
list allows you to specify which nodes will receive the message.
Default sends messages to all cluster nodes.
/NOTIFY (default)
/NONOTIFY
Sends a message describing success back to the originating terminal.
/PENDING=identification-number
Requires OPER privilege.
Sends a message to the user 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.
/SHUTDOWN
Sends a message beginning "SHUTDOWN..."; if used with the
/BELL qualifier, rings three bells at terminals receiving the message.
/STATUS
Requires OPER (operator) privilege.
Reports the current operator status and all outstanding user requests
for the terminal from which this command was entered. The current
terminal must be enabled as an operator terminal.
/TEMPORARY
Designates the terminal at which the command is entered to be an
operator's terminal for the current interactive session only. This
qualifier is meaningful only when used with the /ENABLE qualifier.
/TERMINAL=(terminal-name[,...])
Requires OPER (operator) privilege.
Broadcasts the message to specified terminals, where the
terminal-name parameter is the device name of the terminal.
Incompatible with the /ALL and /USERNAME qualifiers.
/TO=identification-number
Requires OPER (operator) privilege.
Sends a message to the user or file system 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 command where you redirect the mount
operation to another device. Whenever you must substitute a device,
load the user's volume on the alternate device and prepare the device
for connection before entering the REPLY command. Use the following
syntax:
REPLY/TO=identification-number "SUBSTITUTE device-name"
|
You can abbreviate the word SUBSTITUTE to S and can use uppercase or
lowercase characters. After a space, use the remainder of the
message-text space to name the substituted device.
/URGENT
Sends a message beginning "URGENT..."; if used with the /BELL
qualifier, rings two bells at terminals receiving the message.
/USERNAME[=(username[,...])]
Requires OPER (operator) privilege.
Broadcasts a message to all terminals at which users are logged in to
the system (or OpenVMS Cluster), or only to the terminals of the
specified users. Incompatible with the /ALL and /TERMINAL qualifiers.
/WAIT
Sends a message synchronously and then waits. The default is to send a
message to OPCOM, which does the actual I/O. On a cluster, the message
is sent to the local node.
Examples
| #1 |
$ REPLY/ALL/BELL "SYSTEM GOING DOWN FOR BACK-UP. PLEASE LOG OFF."
|
The REPLY command in this example broadcasts a message to all terminals
on the system. When the message appears at the user's terminal, it is
prefixed with the terminal name, the user name of the sender, and (when
DECnet-Plus or DECnet for OpenVMS is installed) the node name. The bell
sounds at the terminal as the message is displayed.
| #2 |
$ REPLY/ENABLE=DISKS
%OPCOM, 24-DEC-2001, 10:17:09.02, operator enabled, operator OPA0
$
%OPCOM, 24-DEC-2001 10:17:10.30, operator status for operator OPA0
DISKS
|
The REPLY/ENABLE command in this example designates the terminal OPA0
as an operator terminal that can receive messages pertaining to
mounting and dismounting disks. The OPCOM message confirms that
terminal OPA0 is established as an operator's terminal.
| #3 |
%OPCOM, 24-DEC-2001 10:19:33.21, request 5, from user SYSTEM
OPA0, Please mount OPGUIDE on DKA3:
$ REPLY/PENDING=5 "YOU'LL HAVE TO WAIT... -
_$ THERE ARE SEVERAL REQUESTS BEFORE YOURS"
.
.
.
$ REPLY/TO=5
24-DEC-2001 10:20:25.50, request 5 completed by operator OPA0
|
In this example the OPCOM message indicates that a user wants the
operator to place the disk volume labeled OPGUIDE on the disk drive
DKA3 and prepare the device for connection. The REPLY/PENDING command
indicates that the operator can perform the task but not immediately;
the /PENDING qualifier prevents the user from entering other commands
until the operator fulfills or aborts the request. After mounting the
disk on the drive the operator sends a message indicating that the
request has been fulfilled. When no message is specified, OPCOM sends a
standard message indicating that the task has been performed.
| #4 |
%%%%%%%%%% OPCOM, 24-DEC-2001 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"
|
The REPLY/TO command with the SUBSTITUTE syntax in this example is used
in response to a MOUNT/ASSIST command entered by user ROBINSON. The
MOUNT device is switched to DUA4, and the logical name specified by the
user in the MOUNT command is defined with an equivalence name of DUA4
rather than the drive originally specified.
| #5 |
$ REPLY/STATUS
%OPCOM, 24-DEC-2001 10:20:50.39, operator status for operator OPA0
DISKS
|
|
