dupterm(8)dupterm(8)Namedupterm - DUP virtual terminal program
Syntax
/usr/etc/dupterm
Description
The DUP virtual terminal program provides access to the diagnostic and
utility features of DSA (DIGITAL Storage Architecture) intelligent disk
and tape controllers.
Depending upon the particular controller, operations may include the
execution of controller resident diagnostics and utilities or those
downloaded from the host system.
Further information regarding the operation of the utility and diagnos‐
tic capabilities associated with a particular controller may be
obtained from the appropriate documentation set for that controller.
Once invoked, prompts the user with "DUP>> ", and waits for a command.
can be in one of three states at any time. When it is started, it is in
state. When it has established a connection to the on the remote con‐
troller, it is in the state. When it starts execution of a diagnostic
or utility on the remote controller, it enters the state. In this
state, user typein is normally transmitted to the remote program. To
force to interpret a command locally instead, enter a '.' character as
the first character of the command line. To transmit a '.' as the
first character of a command line to the remote program, enter two
periods as the first two characters of the command.
The program recognizes the following commands. Commands are case
insensitive. The minimum acceptable abbreviation for each command is
shown in uppercase.
Help Displays a brief description of all commands.
ABort Valid only in state. Aborts the execution of the remote pro‐
gram. Enters the state.
Connect scs-node-name
Valid only in state. Attempts to establish a connection to the
SCS node named If successful, enters the state. Use the command
to get a list of available SCS nodes.
^ char Valid in state. Sends a control character to the remote pro‐
gram. The space between the "^" and is ignored.
DIsconnect
Valid only in states or Breaks the connection. If a remote
program was executing, terminates it as well.
Dust Valid in states or Issues a GET DUP STATUS command to the con‐
nected controller, and displays the results.
INFO Valid in all states. Displays SCS related information, such as
the node names and their SCS id's.
LOG [log-file-name]
Valid in all states. If a file name is given, all interaction
is logged in the file. If no file is given, terminates logging.
Quit Quits the session.
Runl task-name
Valid only in state. Loads the program from the local media
on the controller, and starts its execution. If successful,
enters the state. Whether is case-sensitive or not depends on
the controller.
RUNS task-or-file-name
Valid only in state. Attempts to load the program first from
the file on the local host, and if not found, from the file and
starts its execution. is the program name extension as
returned by the controller. If successful, enters the state.
SEt HSCmode {ON|OFf}
Valid in any state. When is set to does some special processing
needed by the HSC-nn controllers.
SEt SERver {-d|scs_sysap_name}
Valid in any state. Sets the name of the SYSAP name to use to
establish the connection. If -d option is given, tells it to
use the default servers "DUP", "MSCP$DUP", and "DUP$SERVER" in
order.
SHOw NODe
Valid only in the states or Displays the name of the node is
connected to currently.
SHOw SERver
Valid in any state. Displays the current server setting.
SHOw STATus
Valid in any state. Displays the current status of including
which controller it is connected to, and which program it is
executing, if any.
SHOw TASk
Valid only in state. Shows the name of the remote diagnostic
or utility currently executing.
SHOw VERsion
Displays version information about dupterm and the dup driver.
Useful for reporting problems.
SYNChronize
Valid in all states. Forces to change its state to confirm to
the actual state of the remote controller. This is useful if
the remote program does not confirm to the DUP Standard Dia‐
logue. In this case, there is no way for to know that the
remote program has terminated. This command can change the
state appropriately.
Restrictions
Execution of some diagnostic and utility programs may interfere with
normal activities of the controller. Refer to the appropriate con‐
troller documentation set for further specifics.
To use with a HSC-nn controller, first execute the command before con‐
necting. When the connection is established, the "HSC-nn>> " prompt is
displayed. At this point, HSC commands may be entered. When an HSC
command completes, one must type
.^Y
to get the "HSC-nn>> " prompt again. To quit, type the command
.abort
to abort the program on the HSC, or
.disconnect
to abort and disconnect. Note that these commands must be preceded by
a "." in order to force them to be interpreted by locally, rather than
being passed on to the controller.
The program cannot be run with its input redirected. This has to do
with the fact that it has to wait on both the controller, and the user
input, and there is no reliable way to determine when the next line of
input from the user should be read and sent to the controller. This is
a limitation of the protocol.
Diagnostics
The utility generates messages when the user does not have the appro‐
priate privileges and when operational errors occur.
Files
Device special files to connect to the driver.
dupterm(8)