AA FD10A TC RSX 11M & M Plus MCR Operations Manual
User Manual: AA-FD10A-TC RSX-11M & M-Plus MCR Operations Manual
Open the PDF directly: View PDF 
.
Page Count: 388
| Download | |
| Open PDF In Browser | View PDF |
RSX-11 M/M-PLUS
MeR Operations Manual
Order No . AA-FD1 OA- TC
RSX-11 M/M-PLUS
MeR Operations Manual
Order No. AA-FD10A-TC
c
c
c
RSX-11 M Version 4.2
RSX-11 M-PLUS Version 3.0
digital equipment corporation · maynard, massachusetts
First Printing, June
Revised, November
Updated, April
Revised, July
1979
1981
1983
1985
The informatio~ in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no resporisibility
," for any errors that may appear in this document.
The software described in this document is furnished under a license
and may be used or copied only in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by Digital Equipment Corporation or its
affiliated companies.
Copyright
GV
1979, 1981, 1983, 1985 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future
documentation.
c
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DEC US
DECwriter
DIBOL
EduSystem
lAS
MASSBUS
MICRO/PDP..,.l1
Micro/RSX
PDP
PDT
RSTS
RSX
UNIBUS
VAX
VMS
VT
(
ZK2640
HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call 800-258-1710
In New Hampshire, Alaska, and Hawaii ,call 603-884-6660
In Canada call 613-234-7726 (Ottawa-Hull)
800-267-6215 (all other Canadian)
DIRECT MAIL ORDERS (USA & PUERTO RICO)'
Digital Equipment Corporation
P,O. Box CS2008
Nashua, New Hampshire 03061
DIRECT MAIL ORDERS (CANADA)
Digital Equipment of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk
DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
PSG Business Manager
c/o Digital's local subsidiary or
approved distributor
'Any prepaid order from Puerto Rico must be placed
with the local Digital subsidiary (809-754-7575)
Internal orders shoUld be placed through the Software Distribution Center (SDC), Digital Equipment
Corporation, Northboro, Massachusetts 01532
.
CONTENTS
(
Page
Preface
v
Summary of Technical Changes
CHAPTER 1
1.1
1.1.1
1.1.2
1.1.3
1.2
1.3
CHAPTER 2
(
2.1
2.1.1
2.1.2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.5
2.5.1
2.5.1.1
2.5.1.2
2.5.2
2.5.3
2.5.4
2.5.5
2.5.5.1
2.6
CHAPTER 3
l
3.1
3.2
3.3
3.4
3.5
ix
INTRODUCTION TO MCR
•
MCR COMMAND LINES
The MCR Prompt • •
Keywords • • • • •
Comments • • • • •
THE MCR INTERFACE •
MCR COMMAND SUMMARY
• • • •
• • • •
· .
· .
• • • • •
••••
.
.
.
.
.
. 1-1
. .
• .
.
.
.
.
•
•
.
.
•
•
.
.
•
•
.
•
•
•
•
1-3
1-4
1-4
1-5
1-5
SYSTEM CONVENTIONS
FILES-il • • • • • • • • • • • • • • • • • • • • • 2-1
File Ownership and Directories
• • • • • 2-2
File Protection • • • • • • • •
• 2-3
FILE SPECIFICATIONS • • • • • •
• • • • • 2-4
User Identification Codes (UICs) • • • •
• 2-6
Wildcards
••••• • • • • • • • • • •
• 2-7
File Specification. Defaults
• • • • 2~7
Conventional and Default File Types
• • • • 2-8
Examples of File Specifications • • • • •
• 2-9
DEVICES • • • • • • • • • • • • • •
2-10
Logical Unit Numbers • • • • • •
2-10
Pseudo Devices • • •
•• • • •
2-10
The Null Device
• • • •
• • • • • 2-11
Logical Device Names and Logical Names
2-12
Public, Private, and Unowned Devices • •
2-13
TERMINALS • • • • • • •
••••
2-14
Input Prompts
• • • • • ••
• • • • 2-14
Special Character Keys and Control Characters
2-15
Terminal privilege • • • • • • • •
2-19
Attached and Unattached Terminals
2-19
Slave Terminals
• • • • • • • • • •
2-19
TASKS· • • • • • • •
•• • • •
2-19
Partitions • • • •
2-20
Parti tion Types
• • • • 2-20
Subpartitions
• • • • • • • • • 2-20
Mul tiprogramming •
• • • •
2-21
Creating a Task
• • • • •
2-21
Task-Naming Convention • • • • •
• • • • 2-21
Installing a Task
• • • • • • • • • • • 2-23
Install-Run-Remove Tasks
• • • • 2-23
NONPRIVILEGED USE OF ACNT • • • • • • • •
2-24
MCR COMMANDS
(NP,P)
•••••••••
ANCILLARY CONTROL DRIVER (P,NP)
ALLOCATE CHECKPOINT SPACE (P)
ACTIVE (NP)
• • • •
·
ALLOCATE (NP,P)
••••••
~aORT
iii
.
• • • • • • • 3-3
• • • 3-8
3-11
. . . . . .
3-14
3-16
(
CONTENTS
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
3.18
3.19
3.20
3.21
3.22
3.23
3.24
3.25
3.26
3.27
3.28
3.29
3.30
3.31
3.32
3.33
3.34
3.35
3.36
3.37
3.38
3.39
3.40
3.41
3.42
3.43
3.44
3.45
3.46
3.47
3.48
3.49
3.50
3.51
3.52
APPENDIX A
ALTER (P)
ASSIGN (NP,P)
ACTIVE TASK LIST (NP)
BLOCK (NP, P)
BOOT (P)
BREAKPOINT TO EXECUTIVE DEBUGGING TOOL (P)
BROADCAST (NP,P)
BYE (NP)
CANCEL (NP,P)
COMMON BLOCK DIRECTORY (NP)
COMMAND LINE INTERPRETER (P ,NP)
CLOCK QUEUE (NP)
DIGITAL COMMAND LANGUAGE (NP)
DEALLOCATE (NP,P)
DEBUG (NP, P)
DEVICES (NP ,P)
DEFINE LOGICALS
DISMOUNT (NP, P)
.
FIX-IN-MEMORY (P)
GROUP GLOBAL EVENT FLAGS (NP,P)
HELLO OR LOGIN (NP)
HELP (NP)
HOME (NP, P)
INITVOLUME (NP)
INSTALL (P)
LOAD (P)
LOGICAL UNIT NUMBERS (NP)
MOUNT (NP, P)
OPENREGISTER (P)
PARTITION DEFINITIONS (NP)
REASSIGN (P)
REDIRECT (P)
REMOVE (P)
RESUME (NP,P)
RUN (NP, P)
SAVE (P)
SET (NP, P)
SYSTEM SERVICE MESSAGE (P)
SWITCH REGISTER (P)
ATL FORMAT (NP)
TASKLIST
TASKLIST (NP)
TIME (NP,P)
USER FILE DIRECTORY (NP ,P)
UNBLOCK (NP, P)
UNFIX (P)
UNLOAD (P)
UNSTOP (NP,P)
3-19
3-20
3-31
3-34
3-35
3-38
3-39
3-43
3-45
3-46
3-48
3-55
3-56
3-57
· · · · · .' . · · · ·
·· · ····
·
·
···
············
· ·
·· ··
· · · · ·· ·· ·· ·· ·· · ·· · · · · · · ··
···············
····
····
····
·
·
·
·
·· ····· ······
3-60
· ·· · · · ·
· · · · 3-63
·
· · ·· ·· · · · · · ·· · · · · 3-70
3-75
· · · · · · 3-77
3-79
········
· · · · 3-87
3-93
····
3-99
· · · · · · ·· · · ··
3-116
· · ·· ·· · ·· ·· · · · · ·· ·· ·· 3-132
.. ·
3-140
·
3-141
· 3-164
· · ·· ·· ·· ·· ·· ··
·
· ·· ·· ·· · · · · ·· 3-169
·
·
3-172
··
·
·
·
·
·
·
3-173
· 3-17.5
···· ·
· ·· · · · · · · · ·· · ·.. ·. ·· •• 3-V77
· · · ·· · · · ·• / ti78
··
····
-187
· · · · · · · · · ··
····
3-197
···
· · · · · · ·· 3-273
·
·
·
·
3-274
·
·
·
·
·
·
·
·
·
·
·
3-275
· ·· ·· 3-276
·
·
·
·
·
·
·
·
·
·
· · 3-278
···········
3-280
·
·
·
·
·
·
·
·
3-283
··········
3-284
·
·
·
·
·
·
·
·
·
·
3-285
· ·· 3-287
· · ··
·····
3~58
/
C
C
.
MCR AND TKTN MESSAGES
TABLES
2-1
2-2
3-1
3-2
~.
· · · · · · · · · · · · · · · · · 2-10
2-15
3-35
·
3-199
··
···········
Pseudo Devices
Special Character Keys and Control Characters
Valid Bootable Devices
SET Keywords
iv
l
\
(
PREFACE
MANUAL OBJECTIVES
The RSX-llM/M-PLUS MCR Operations Manual provides you with the
information you need to operate and control RSX-IIM/M-PLUS systems.
The Monitor Console Routine (MCR) serves as a terminal interface
between you and your RSX-llM/M-PLUS operating system. This manual
describes the basic concepts ofMCR operation and shows you how to use
MCR commands.
This manual identifies two basic types of users:
privileged and
nonprivileged.,
MCR provides privileged users with functions that
control and modify system operation and permit program development and
system maintenance.
MCR provides nonprivileged users with functions
that permit program development and private device and terminal
maintenance.
(
c
INTENDED AUDIENCE
The RSX-lIM/M-PLUS MCR Operations Manual does not attempt to train
users.
The manua-I--assumes that the reader is familiar with both
real-time and batch computer operating procedures.
It also assumes
that the reader has experience working with computer terminals and
other hardware devices.
A user is broadly defined as anyone who interfaces directly with
RSX-IIM/M-PLUS to perform a task. This broad definition is assumed
because of the many and varied settings to which RSX-llM/M-PLUS
operating systems are applied.
RSX-llS is a compatible subset system of RSX-lIM/M-PLUS.
Thus,
manual can also be used as a reference document for RSX-IIS.
this
STRUCTURE OF THIS MANUAL
Chapter 1 describes MCR and provides a summary of MCR commands.
Chapter 2 discusses basic concepts of the RSX-IIM/M-PLUS file system
(Files-II file structure), and describes system conventions such as
device and task naming conventions.
Chapter 3 provides a detailed description of each MCR command.
The
command descriptions are alphabetized according to the abbreviated
forms of the command names.
Appendix A lists messages that are common to MCR commands, and
messages from the Task Termination Notification Program (TKTN). The
messages are listed in alphabetical order.
Messages that
are
command-specific are described in the individual command descriptions.
v
PREFACE
ASSOCIATED MANUALS
Although the RSX-llM/M-PLUS MCR Operations Manual is
primarily
self-contained, the reader should be familiar with system generation
options and features in order to fully understand this manual.
For
detailed descriptions of system generation, refer to the RSX-llM
System Generation and Installation Guide or the RSX-llM-PLUS System
Generation and Installation Guide.
c
CONVENTIONS USED IN THIS MANUAL
This manual observes the following conventions:
Convention
Meaning
A 1- to 3-character key symbol indicating that
press the corresponding key on the terminal.
example,
(BIT)
indicates the RETURN key and
indicates the ESCAPE key.
you
For
@
A symbol indicating that you are to perform a
control key sequence;
that is, you press the key
labeled
CTRL
while
you
press
another
key
simultaneously.
For example,
(CTRLlC)
means that you
hold down the CTRL key while you press the C key.
The system displays control key sequences in the
following manner:
AC or AZ. Therefore, examples of
terminal display in this manual show control key
sequences as they are displayed on the terminal
screen.
[
]
l
Square brackets usually indicate optional entries in
a command line or file specification. When you
enter an option, you do not include the brackets.
Square brackets are also
part
of
the
User
Identification Code and User File Directory syntax
(for example, [group,member] or [named]). When you
use a UIC or a UFD (in a file specification, for
example), you must include the brackets.
{ }
Braces indicate a choice of required entries for a
command line.
You can use any of the entries
enclosed in the braces, but you must specify one of
them.
SET
Uppercase letters and words indicate that you should
enter the letter or word exactly as shown.
file name
(base)
red ink
Lowercase letters and words indicate that you are to
substitute a word or value.
The base of a number
after the number.
255 (decimal) •
is indicated in parentheses
For example: 77777(octal), or
Red ink in examples indicates input that you type at
the terminal.
Shaded text indicates
that
the
documentation
pertains to one operating system only.
vi
(
PREFACE
Meaning
Convention
(
blt: ink
Pink shading indicates that the text
RSX-llM operating systems only.
pertains
to
Gray shading indicates that the text
RSX-llM-PLUS operating systems only.
pertains
to
Blue ink
pertains
systems.
that
in text indicates information
only
to RSX-llM-PLUS multiprocessor
(
(
l
vii
(
Summary of Technical Changes
This revision of the RSX-llM/M-PLUS MeR Operations Manual contains
changes and additions ~made in Version 4.2 of the RSX-llM operating
system, and Version 3.0 of the RSX-llM-PLUS operating system.
This summary has the following sections:
•
New operating system features
•
New or modified MeR commands
•
New or modified MeR command keywords
NEW OPERATING,SYSTEM FEATURES
c
ix
Summary of Technical Changes
Network Command Terminal (NCT)
If support for NCT was selected for your system during system
generation, you can establish a remote connection from your
terminal to other systems in a network.
c
Terminal characteristics
You can use the SET command with a variety of new keywords
control many of the characteristics of your terminal.
to
NEW OR MODIFIED MCR COMMANDS
(
(
NEW OR MODIFIED MCR COMMAND KEYWORDS
l
x
Summary of Technical Changes
(
MOU
(
SET
(
The MOUNT command has the following modified keywords:
/FPRO
Specifies default file protection codes for
files created on Files-II magnetic tapes or
disks. Formerly, this keyword applied only to
disks.
/PRO
Specifies the default volume protection for
Files-II
magnetic
tape or disk volumes.
Formerly, this keyword
applied
only
to
Files-II disk volumes.
The SET command has the following modified keyword:
/BUF
SET
Sets the default buffer size of a specified
device.
The minimum default buffer size for
devices
other
than
terminals
is
now
14(decimal) characters. Formerly, the minimum
size was one character.
The mlnlmum buffer
size
for
terminals
remains
16(decimal)
characters.
The SET command also has the following new keywords:
/[NO]ANSI
Informs the system whether a terminal supports
ANSI standardized escape sequences.
/[NO]AVO
Enables or disables the advanced video
for a terminal.
/[NO]BLKMOD
Enables or
disables
local
editing
block-mode transmission for a terminal.
l
xi
option
and
Summary of Technical Changes
/[NO]DEC
Indicates whether the specified
upwardly
compatible
with
terminals.
terminal is
VT100-series
/[NO]EDIT
Indicates whether a terminal can
perform
ANSI-defined advanced editing functions.
/HOST
Sets a specified node as a host system.
Executes only on systems that selected Network
Command
Terminal
support
during
system
generation.
/[NO]HSYNC
Enables or disables synchronization between a
host system and a terminal. Enabling host
synchronization prevents the typeahead buffer
from overflowing.
/INQUIRE
Inquires what type a terminal is and then sets
the standard terminal attributes for that
type.
(
( ....
~
(~
/[NO]PARITY
Enables or disables parity
checking for a terminal.
/[NO]PASTHRU
Enables or disables the passing through of
special
characters.
Enabling pass-through
causes the system to ignore the standard
functions of special characters. Instead, the
system passes special characters through to a
program in their binary form.
generation
/[NO]PRINTER_PORT
Informs the system whether a
printer port.
/[NO]REGIS
Indicates whether a terminal
ReGIS graphics character set.
/[NO]SOFT
Indicates
whether
a
terminal
software-defined character sets.
/[NO]TTSYNC
terminal
has
~upports
and
a
the
supports
Enables or disables terminal synchronization
.for
a
terminal.
Enabling
terminal
synchronization allows control characters to
stop and start output to your video screen.
xii
(
Summary of Technical Changes
(
(
(
xiii
CHAPTER 1
INTRODUCTION TO MCR
The Monitor Console Routine (MCR) serves as an interface between you
and the RSX-llM/M-PLUS system. This chapter introduces you to MCR and
provides a summary of the MCR commands.
Before trying to use MCR commands, be sure that your terminal is set
to MCR. You can verify this by pressing CTRL/C. If your terminal is
set to MCR, it will display the explicit MCR prompt (MCR»
when you
press CTRL/C.
Section 1.1.1 describes the explicit MCR prompt. If
you want MCR to be the default command line interpreter for your
terminal, have your system manager set this up for you in your account
file.
.
1.1
c
MCR COMMAND LINES
To issue an MCR command, type a command line in response to a default
prompt (» or the explicit MCR prompt (MCR». A command line consists
of three components: a command name, command parameters, and a line
terminator.
It is not necessary to type the entire command name when you issue a
command.
MCRuses only the first three letters of command names,
except for the HELP command, which must be entered in full.
You
follow the command name with command parameters and a line terminator
(the RETURN key).
(
For example, you can type the CANCEL command as follows:
>CAN taskname ®TIl
The variable taskname is a parameter for the CANCEL command.
®TIl
signifies the RETURN key, which is a line terminator. As in this
example, you often type only the first three letters of a command
name. However, some commands have 3-letter acronyms as command names.
For example, the names for the ASSIGN and USER FILE DIRECTORY commands
are ASN and UFD, respectively.
With most MCR commands, you can specify the full form of the command
name, but this is unnecessary because MCR only uses the required first
three letters. However, if you want to make the intent of the command
clear to someone else, you can type the full command name. For
example:
>CANCEL taskname®TIl
l
1-1
INTRODUCTION TO MCR
A space or a tab signals the end of the command namei therefore, no
spaces or tabs are allowed within the command name itself. For
example:
(
>OPENREGISTER address
is permissible, while
>OPEN REGISTER address
is not.
Typically, a command parameter is a task name, the name of a file, or
a device specification. A parameter can be modified by a keyword (see
Section 1.1. 2) .
You press the RETURN key, the ALT key, or the ESC key to terminate a
MCR returns the default prompt after processing a
command line.
command line that is terminated by the RETURN key. MCR suppresses the
default prompt after processing a command line terminated by the ESC
key, except when the ESC key has special significance as a terminator
(as with the RUN and OPENREGISTER commands, for example). MCR then
accepts subsequent unsolicited input even though the default prompt
does not appear.
[.~
When MCR parses a command line, it normally compresses any multiple
spaces and tabs, and treats character strings beginning with a
semicolon (i) or an exclamation mark (1) as comments (see Section
1.1.3) .
When you use quotation marks ("") in the command' line, however, MCR
parses the portion within the quotes exactly as you typed it. No
compression occurs. This allows you to use special nonalphanumeric
characters in your command line as well as American National Standard
(ANSI)X.327-l978 file specifications, which permit embedded spaces.
c
If you use only one quotation mark in the command line, MCR assumes an
ANSI file specification and does not compress the line past the
quotation mark.
(See Section 6.2 of the RSX-llM/M-PLUS and Micro/RSX
I/O Operations Reference Manual for more information on support for
quotation marks.)
c
1-2
INTRODUCTION TO MCR
1.1.1
The MeR Prompt
MCR uses three kinds of prompts to indicate that a terminal is waiting
for your input:
the default prompt, task prompts, and the explicit
MCR prompt. The default prompt and task prompts are described more
fully in Chapter 2.
A terminal sends MCR any input that you
explicit MCR prompt (MCR». For example:
type
in
response
to
the
MCR> command-input
You invoke the explicit MCR prompt by pressing the CTRL key and the
key simultaneously (this is written as CTRL/C).
C
However, in special cases, pressing CTRL/C will not invoke the MCR
prompt.
The secon~d item in the following list describes one such
Case. Also, the description of CTRL/C in Table 2-2 describes two
other situations in which CTRL/C does not invoke the explicit MCR
prompt.
The following list explains various
explicit MCR prompt:
c
ways
that
you
can
invoke
the
1.
When a terminal is displaying the default prompt (», there
is no guarantee that input typed in response to this prompt
will be directed to MCR because another task may have
attached to the terminal. To ensure that MCR does receive
the input, press CTRL/C to invoke the MCR prompt. After MCR
processes the command line, the terminal will again display
the default prompt.
2.
When a terminal is displaying a task prompt (tsk», you
invoke
MCR by pressing CTRL/C.
After (or while)
processes the command line, the terminal will display
original task prompt.
can
MCR
the
If you requested MCR to display information (with the TIME
command, for example) and it is not displayed before the task
prompt appears, press the RETURN key. This will display the
information and then the original task prompt. Also press
the RETURN key if you would like to know whether MCR
processed the command line or if it returned an error
message.
(
NOTE
If an attached task specifies an asynchronous
system trap (AST) upon receiving unsolicited
input, CTRL/C causes an AST to occur, and
therefore, pressing CTRL/C gains the task's
attention rather than MCR's.
Consequently,
the MCR prompt does not appear.
3.
When any terminal is receiving output from a task, you can
interrupt the output by pressing CTRL/C. At the completion
of the current I/O operation, the terminal displays the
explicit MCR prompt.
After MCR processes the command line
directed to it, the system resumes the interrupted output.
1-3
INTRODUCTION TO MCR
In all three cases, if the command line invokes a task, the task will
issue its own prompt.
You can resppnd to this prompt with another
CTRL/C, which invokes the MCR prompt. You can then request another
task that issues its own prompt and so on.
(Note that because CTRL/C
does not abort the task that was active when you typed the CTRL/C, it
is
possible
to
have
several tasks active at your terminal
concurrently.)
1.1.2
Keywords
Some of the MCR commands use keywords that affect a command parameter.
Keywords are similar in function to switches (see Section 2.2). A
keyword consists of a slash (/) followed by the keyword.
A keyword
may be followed by an optional equal sign (=) and value. For example:
/keyword[=value]
A keyword modifies the action of a command. You can apply a keyword
directly to the command or to a command parameter, depending on the
command. If the keyword follows the command name, it modifies the
action of the command.
If the keyword follows a parameter, it
modifies the action of the parameter.
For example, the INSTALL command requires a filename parameter that
specifies the task to be installed. You can append keywords to this
file name. One such keyword, /TASK, specifies the name under which
the task is to be installed. For example:
INS BOB.TSK/TASK=AMBER@]
This command installs the task image file BOB.TSK with the name AMBER.
When you want to use the task, you invoke it with the name AMBER.
(
If you want to specify multiple keywords with a command, you can enter
the
keywords
in
any
order.
Also,
because
keywords
are
command-specific, the keywords for each command are defined in each
command description (see Chapter 3).
1.1.3
Comments
MCR treats a line of text as a comment if the first character in the
line is a semicolon (i).
In addition, you can delimit comments within
a command line by using an exclamation point (!).
The first
exclamation point starts the comment and the second point or line
terminator ends the comment. MCR ignores all text between the two
exclamation points. For example:
>i
THIS LINE IS A COMMENT
>TAL !THIS IS A COMMENT STRING!
RMDEMO
Comments are especially useful to clarify commands in indirect command
files.
If a semicolon or exclamation point is part of a command line, you
must place these characters within quotation marks (see Section 1.1).
1-4
c
INTRODUCTION TO MCR
1.2
(
-
THE MCR INTERFACE
MCR parses your typed input to determine what the command line is
requesting and then responds accordingly. To service a request, MCR
either uses an MCR overlay or activates an independent task.
most
The required three letters of the command name are the
significant part of a command line. MCR uses the command name to
The following procedures
determine the necessary overlay or task.
detail how MCR activates the appropriate overlay or task to service
each command:
(~
~
1.
MCR searches a table containing names of commands that MCR
services.
If the table contains a command that matches the
one you have typed, MCR either loads the corresponding
overlay or starts the. secondary task ( .•• MCR), which invokes
the correct overlay. Then the overlay processes the command
line.
(On single-user RSX-IIM systems, all commands are
serviced by MCR .•. , which is the primary MCR task.There is no
secondary MCR task.)
2.
If the table does not contain a matching command, MCR
prefixes three dots ( ..• ) to the command name and searches.
the System Task Directory (STD) for a task by that name (that
is,
... tsk).
MCR returns an error if the STD does not
contain the specified task.
c
(
1.3
MCR COMMAND SUMMARY
The MCR commands described in Chapter 3 are listed here by category.
This command summary provides a compact overview of the facilities
available at your terminal. Commands followed by (NP) are available
to all users.
Commands followed by (p) are available only to
privileged users.
Commands followed by (NP,P) are nonprivileged
commands with privileged options.
Commands followed by (P,NP) are
privileged commands with nonprivileged options.
1-5
INTRODUCTION TO MCR
Initialization Commands
(
ACS (p)
Allocates or discontinues
checkpoint file on disk.
the
use
of
ASN (NP,P)
a
device
BOOT (p)
Bootstraps a new system
transfers control to it.
DMOUNT (NP,P)
Dismounts a volume by marking the volume for
dismount and releasing its control blocks
(complement of MOUNT).
FLAGS (NP,P)
Creates, displays, or eliminates group global
event flags.
HOME (NP,P)
Alters the values contained in various fields
of the home block of a Files-II disk volume.
INITVOLUME (NP)
Initializes a disk, DECtape, or magnetic tape
to produce a Files-II volume.
INSTALL (p)
Installs a task in the system.
LOAD(P)
Loads a
memory.
MOUNT (NP,P)
Mounts a volume by creating its control
blocks and making the volume accessible to
the file system.
REDIRECT (p)
Redirects_all I/O requests from one
device to another.
physical
SET (NP,P)
Alters or displays system,
characteristics.
or
TIME (NP,P)
Enters the time and date into the system.
Displays the time and date on your terminal.
UFD (NP,P)
Creates a User File Directory (UFD) in a
Master File Directory (MFD) on a Files":'ll
volume.
nonresident
1-6
into
device
memory
driver
device,
and
(
into
task
c
INTRODUCTION TO MCR
Informational Commands
(
ACT (NP)
Displays on your terminal the names of active
tasks that were requested from that terminal.
ATL (NP)
Displays on your terminal the names
status information for active tasks.
CLQUEUE (NP)
Displays on your terminal
tasks in the clock queue.
DEVICES (NP)
Displays on your terminal information about
peripheral devices recognized by the system.
LUNS (NP)
Displays on your terminal the list of static
logical unit number (LUN) assignments for a
specific task.
PARTITIONS (NP)
Displays on your terminal
each partition in memory.
TAL (NP)
Displays on your terminal the names and
status of all tasks in the system or the name
and status of a specific task.
TASKLIST (NP)
Displays on your terminal
each installed task.
information
a
and
about
description
a
of
description
of
Task Control Commands
ABORT (NP,P)
Terminates execution of a running task.
ALTER (p)
Alters the priority of a task.
BLOCK (NP,P)
Blocks a task.
CANCEL (NP,P)
Cancels time-based initiation requests for
task (no effect on current execution).
FIX (p)
Fixes a task in a partition in
task becomes memory-resident).
REASSIGN (p)
Changes logical unit number (LUN) assignments
for a task.
REMOVE (p)
Removes a task from the system (complement of
INSTALL) .
RESUME (NP,P)
Resumes execution
suspended itself.
RUN (NP,P)
Initiates the execution of a task. The task
may run immediately, after a time delay, or
in synchronization with the system clock.
Periodic rescheduling is optional.
a
(
1-7
of
a
task
memory
that
(the
had
INTRODUCTION TO MCR
UNBLK (NP,P)
Unblocks
a
previously
(complement of BLOCK).
UNFIX (p)
Makes a memory-resident
(complement of FIX).
UNLOAD (p)
Removes a loadable device driver from
(complement of LOAD).
UNSTOP (NP,P)
Resumes execution of a task that has
stopped internally by the Executive.
blocked
task
task
nonresident
c
memory
been
System Maintenance Commands
BRK (p)
Passes control . to the Executive Debugging
Tool (XDT). Valid only for systems that have
generatedXDT support.
OPEN (p)
Displays on the
entering
terminal
the
contents of a memory location for examination
or modification.
SAVE (p)
Copies the current system image into the
system image file from which the system was
booted.
SSM (p)
Inserts. text into the error log file.
SWR (p)
RSX-IIM-PLUS mUltiprocessing systems only.
Displays the current value of, or sets or
clears a bit in the switch register.
Multiuser Protection Commands
ALLOCATE (NP,P)
Allocates a device to a user (reserves
device as the user's private device).
BRO (NP,P)
Broadcasts
terminals.
BYE (NP)
Logs out of the system.
DEALLOCATE (NP,P)
Deallocates a private (allocated)
(complement of ALLOCATE).
HELLO or
LOGIN (NP)
Logs in on the system.
HELP (NP)
Displays the contents of a help file.
a
message
to
a
terminal
the
Allows usage of a command
(CLI) other than MCR.
DCL (NP)
Permits
command
MCR.
line
device
interpreter
a DIGITAL Command Language (DCL)
to be issued from a terminal set to
1-8
c
or
Command Line Interpreter Commands
CLI (P,NP)
~..
(
CHAPTER 2
SYSTEM CONVENTIONS
This chapter discusses system conventions including basic concepts of
the RSX-llM/M-PLUS Files-II file system and those aspects of file
handling that directly relate to user functions.
Additionally, this
chapter discusses devices, terminals, and tasks. The last section .of
this chapter briefly describes the Account File Maintenance Program
(ACNT) •
2.1
FILES-ll
RSX-llM/M-PLUS includes a volume-structure system called Files-II to
oversee the storage and handling of files.
In RSX-llM/M-PLUS, a file
is an owner-named area on a volume, and a volume is a medium such as a
disk, a DECtape, or a magnetic tape. Two RSX-llM/M-PLUS utilities and
three MCR commands help you to prepare volumes for use with Files-II:
c
(
•
•
•
•
•
Disk Volume Formatter Utility (FMT)
Bad Block Locator Utility (BAD)
INITIALIZE VOLUME (INI)
MOUNT (MOU)
USER FILE DIRECTORY (UFD)
The utilities are described in the RSX-llM/M-PLUS Utilities
The commands are described in Chapter 3 of this manual.
Manual.
Files-II supports three types of specially formatted volumes:
disks,
DECtapes, and magnetic tapes.
(Files-II magnetic tapes conform to the
American National Standard X3.27-l978.)
,For a volume to become a Files-II volume, you must initialize it with
the INI command. A volume that has not been initialized by INI is a
"foreign" volume. Foreign volumes are treated differently by RSX-llM
and RSX-llM-PLUS systems.
2-1
SYSTEM CONVENTIONS
A system utility, the File Transfer Utility Program (FLX), allows you
to access foreign volumes in DIGITAL's DOS-II or RT~ll format. FLX
translates files on such volumes into Files-II format. In most cases,
a DECtape will have a foreign format and, therefore, requires the use
of the FLX utility. See the RSX-IIMjM-PLUS Utilities Manual for a
full description of FLX.
(
Before Files-II can access a file, the volume tha.t contains the file
must be known to the system. You make a Files-II volume known to the
system by issuing the MOUNT command for the device on which the volume
is loaded.
2.1.1
File OWnership and Directories
When you create a file, the system places the file name in a User File
Directory (UFD). and stores your current User Identification Code (UIC;
see Section 2.2.1) in the file header to indicate that you are the
owner of the file. In most cases, the UFD corresponds to your UIC,
but a file can be listed in a UFD that is not related to your UIC.
It
is also possible for your file to be listed simultaneously in more
than one UFD.
(The files will have different file IDs.)
Each user has a default UFD corresponding to his or her UIC. The UFD
is on a default system device (SY:), which is specified by the system
manager when the user's account is created.
A UFD is itself a file, which you must explicitly create by means of
the MCR UFD command (see Chapter 3). You specify a UFD in the format
[g,m] where g and m are octal numbers between 1 and 377 (0 is
reserved).
These numbers represent the file owner's group and member
numbers, respectively. The actual name of the UFD is a concatenation
of the group and member numbers, terminated by .DIR. For example, the
name of the directory that corresponds to the UFD [203,65] is
203065.DIR.
(Note that leading zeros are added to the UFD so that g
and m are each three digits long.)
All UFDs on a volume are listed in the volume's Master File Directory
(MFD) ,
which corresponds to UFD [0,0] and is therefore named
OOOOOO.DIR. The directories (the UFDs and the MFD) list the names of
files and contain pointers to each file's header. The file header
contains information about the file's owner and the physical location
of the file segments; the header occupies one or more blocks of the
volume's index file ([O,O]INDEXF.SYS).
To delete a UFD, 'you can use the Peripheral Interchange progra~ (PIP)
to first delete all of the files contained in the UFD (thereby freeing
the space for future use) by typing:
PIP> [g, m]
* .*; * JDE (Bill
After you delete all the files, use PIP to delete the UFD by typing:
PIP> [O,O]gggmmm. DIR; * JDE (Bill
The variable gggmmm is the concatenation
number components of the appropriate UFD.
of
Refer to the RSX-IIMjM-PLUS
description of PIP.
Manual
Utilities
2-2
the
group
for
and
a
member
detailed
(
SYSTEM CONVENTIONS
2.1.2
(
File Protection
To access a file, you must know the UFD in which it is located.
However, knowing the location of a file does not guarantee access to
it. You must also satisfy the conditions that are specified in a
protection mask associated with the file you wish to access. The
volume that contains the file must be mounted before the file system
can access the file.
Every file has a protection mask that describes the types of access
allowed to each of four user classes. RSX-IIM/M-PLUS systems allow
the following four types of access:
.~.
Read
The user, or the user's task, may read, copy, print,
type the file, and, if it is a task, run it.
Write
The user, or the user's task, may add, delete, or modify
data in the file by writing to space already allocated
to the file.
Extend
The user, or the user's task, may change the
disk space allocated to the file.
Delete
The user, or the user's task, may delete the file.
amount
or
of
Users are categorized by UIC into the following four classes:
(
System
The operating system itself and privileged users
having group numbers of lO(octal) or less).
Owner
The user having· the same UIC as the
created under.
Group
All users having the same group number as
file was created under.
World
All Users.
one
the
the
(those
file
was
one
the
A file owner assigns access rights by one of the following means:
(
(
INI
Allows you to specify a default file protection code for
all
files subsequently created on the initialized
volume.
UFD
Establishes access rights to a UFD file only.
A user
often allows read access to a.UFD but denies write,
extend, or delete access to the files listed within it.
MOUNT
Allows you, while mounting a volume, to specify the
default file protection to be assigned to files created
on the volume. This protection overrides the protection
established with the INI command.
SET
Allows you, when you use the /DPRO keyword, to specify a
default
protection
code
for all files that you
subsequently create under your UIC.
PIP
Has an option that enables you to alter access rights to
your files.
To gain access to a file, a user must satisfy the protection mask of
both the file to be accessed and the UFD in which the file is listed.
For example, to write to an existing file, you need at least read
access to the UFD and write access to the file. To create a new file,
you need both write and extend access to the UFD.
2-3
SYSTEM CONVENTIONS
2.2
FILE SPECIFICATIONS
MCR uses a. standard format for specifying files in a command line.
The form~t is a string that consists of one or more input and output
file specifications, as follows:
c
File specification>output outfilel •.• ,outfilen=infilel .•• ,infilen
The variable outfile is an output file specification and infile is an
input file specification. The ellipsis mark ( ••. ) indicates that you
may include any number of file specifications in the string.
The
number o.f file specifications is determined by the receiving command
or task. The command line (the line of file specifications plus the
task or command name) cannot exceed 80 characters.
(On half-duplex
terminals, the command line cannot exceed the maximum buffer size set
for your terminal.)
Some commands and tasks may not require the outfile portion. When
is omitted, you might also be able to omit the equal sign (=).
The individual file specifications (whether input or output) have
following format:
it
the
ddnn: [g,m]filename.typeiversio'U/switchl •.• /switchn
(
ddnn:
Specifies the physical or logical device unit on which the volume
containing the file resides. The device unit is expressed as: a
2-character alphabetic device namei an optional 1-, 2-, or
3-digit octal unit numberi and a colon (for example, TT104: or
LP1:). If you do not specify a unit number, the default number
is O. The default device is your system device (SY:).
(
[g,m] (or [directory])
Specifies the directory in which the file is located.
The
variables g and m are octal numbers between 1 and 377 that
represent the
file
owner's
group
and
member
numbers,
respectively.
Square brackets area mandatory part of the
thus, they are required for all directories.
directory
syntaxi
filename
Specifies the name of the file, an alphanumeric string from 0 to
9 characters long (there are exceptions to this, depending on. the
2-4
(
SYSTEM CONVENTIONS
particular program on which you are working).
A period always
separates the file name from the file type. You must specify the
file name. No default is applied.
(
If you want to include special characters in the file name (for
example,
semicolons [~], or exclamation marks [1]), place
quotation marks ("") around the name. That way, MeR will parse
the name exactly as you typed it. ANSI file names for use with
files on ANSI magnetic tapes can contain special characters that
are unacceptable in normal Files-ll file names. Therefore, you
use quotation marks to enclose ANSI filenames that include
special characters.
If you use only one double quotation mark
("), MCR assumes that the rest of the line is an ANSI magnetic
tape file name and parses the name as such.
(See Section 1.1 for
more information on using quotation marks.)
type
Consists of an alphanumeric mnemonic from 1 to 3 characters long
that identifies the nature of the file's contents (the file type
can also be null). For example, .FTN indicates that the file
contains a FORTRAN source program and .OBJ indicates that the
contents are object (compiled) code. If you do not specify a
file type, MCR may assign a default file type. Some conventional
and default RSX-llM/M-PLUS file types are listed in Section
2.2.4.
A semicolon (~) always separates the file type from the
. version number.
version
(
(
The numbers -1 and 0 have special significance: -1 implies the
lowest existing version of a file and 0 implies the highest
existing version. I+ you omit the version number when you enter
a file specification, the default version is the version with the
highest version number.
/switch (or /keyword)
Consists of an ASCII name that identifies a task or command
option. Options generally modify the task's function in some way
or provide information that the task needs in order to respond
correctly to the command line.
l
2-5
SYSTEM CONVENTIONS
The switch can be in one of three forms:
jsw
Sets the switch action
j-sw
Negates the switch action
jNOsw
Negates the switch action
r
The number of values permitted and the interpretation of a switch
depend on the task to which the switch is directed.
You can also modify switches with arguments. These arguments may
be ASCII strings, octal numbers, or decimal numbers.
The
following rules apply:
2.2.1
•
Numbers terminated by a decimal point (.) are decimal.
•
Numbers preceded by a pound sign (#) are octal.
•
Whether the default for a numeric value is octal or decimal
depends on the command or task to which the switch is
directed and on the switch itself.
•
You can precede any numeric value by a plus
(-) sign~ plus is the default.
•
A plus or minus sign, if present, must precede the pound
sign (#) of an explicit octal number (for example, -#323).
(+)
or
minus
User Identification Codes (UICs)
(
On multiuser protection systems, a terminal has two UICs:
a
protection UIC and a default UIC. The system checks the protection
UIC against a file's protection mask to determine a user's access
rights to the file.
The default UIC determines the UFD of the file to
be accessed whenever you omit the UIC field in the file specification.
(See Section 2.1.1 for more information on UFDs.)
How the system sets these two UICs depends on the privilege status of
the user logged in at the terminal. When a nonprivileged user logs
in, the terminal assumes the user's 10ginUIC as its protection UIC.
The login UIC also becomes the initial default UIC for the terminal.
You can issue the SET JUIC command to alter the default UIC, but the
protection (login) UIC remains unchanged.
When a privileged user logs in, the terminal also assumes the login
UIC as the protection and default UICs. However, when you issue the
SET JUIC command, the system alters both of these UICs instead of just
the default UIC.
Because the protection UIC is also changed, the
system no longer knows your login UIC.
(This does not apply to
RSX-IIM-PLUS systems on which Resource Accounting is active because
the accounting system keeps a record of every user's login UIC.)
2-6
SYSTEM CONVENTIONS
2.2.2
(
Wildcards
A wildcard character is an asterisk (*) or a percent sign (%) that you
can use in the place of all or part of a file specification in a
command line. A wildcard causes the system to ignore the contents of
the wild field and to select all the files that satisfy the remaining
explicitly specified fields.
Asterisk wildcards
(*)
can be used in any part of the
file
specification except the device-unit field, which must be explicitly
supplied or defaulted to SY:
(see Section 2.2.3).
The following
examples illustrate the advantage of using the asterisk wildcard:
PIP>PROG.MAC:l,PROG.OBJ:l,PROG.TSK:l/DE@ID
This command line deletes the three individual files specified.
(The
/DE switch instructs PIP to delete the files.) Since the three files
the
have the same file name and version number, but different types,
following command line would delete the same files:
PIP> PROG. *: l/DE @ID
This command line also deletes any other files (on the default device
in the default UFO) named PROG with a version number of 1. You should
check existing files before using wildcards (for example, by issuing
the command line PIP>PROG.*:l/LI).
2.2.3
c
File Specification Defaults
You can omit any field in a command line file specification except the
file name
(the BOOT command, which is described in Chapter 3, is the
only exception to this rule). When you omit one or more fields in a
file specification, the system assumes the following defaults:
Field
ddnn:
[g,m]
Default
The pseudo device unit SY:.
to this default:
There are two exceptions
1.
The BOOT command defaults to device LB:.
2.
The specification of a dollar sign ($) in the
INSTALL and RUN command lines defaults to
device LB:
(see Chapter 3).
The default directory (see Section 2.2.1) specified
for each terminal in one of the following ways:
At system generation (see the RSX-IIM or
RSX-IIM-PLUS
System
Generation
and
Installation Guide)
filename
2.
By means of the SET command (see Chapter 3)
3.
By means of the HELLO command (see Chapter 3)
No default (except for the BOOT command).
A file
specification must include either a file name or a
wildcard in the filename field (see Section 2.2.2).
2-7
SYSTEM CONVENTIONS
Field
type
version
Default
A 1- to 3-character alphanumeric mnemonic; one of the
file types listed in Section 2.2.4; or null. Default
types depend on the task to which the specification
is directed and whether the specification refers to
an input or an output file. For example, the FORTRAN
compiler defaults the type of an input file to .FTN
and the type of an output file to .OBJ.
(
~
For input files, the highest existing version number.
For output files, the highest existing version number
plus 1.
/switch
2.2.4
Switch defaults are established by
and commands.
individual
tasks
Conventional and Default File Types
RSX-IIM/M-PLUS has a set of conventional and default file types used
to
reflect
the
contents of a file.
(The defaults used by
DIGITAL-supplied software are described in the manuals that pertain to
the
individual
programs.)
Although you can assign your own
3-character file types, it is convenient to use the following types:
Type
~I
File Contents
BAS
BASIC-II language source program (default)
BAT
Batch file (default)
B2S
BASIC-PLUS-2 source program (default)
CBL
COBOL language source program (default)
CLB
Indirect command file library (default)
CMD
MCR or task
default)
COR
SLP correction file (convention; must be specified)
DAT
Data (as opposed to a program;
specified)
DIR
Directory
default)
FTN
FORTRAN IV, FORTRAN IV-PLUS, and FORTRAN-77
source program (default)
LOG
Log of batch processing session (default)
LST
Listing file (default)
~C
MACRO-II source program (default)
MAP
Task Builder memory allocation map (default)
MLB
Macro library (default)
commands
(for
(an
example,
2-8
indirect
a
c
command
convention;
User
File
file;
must
be
Directory;
language
(
SYSTEM CONVENTIONS
Type
(
File Contents
OBJ
Object program (output from the MACRO-II Assembler or
a compiler; default)
ODL
Task Builder overlay description (default)
OLB
Object module library (default)
PAT
correction file used by assembler to create a patched
object module (convention; must be specified)
POB
Patched object module input file used
utility (convention; must be specified)
SML
System macro library (default)
STB
Symbol table (default)
SYS
Bootable system image (default)
TMP
Temporary file (convention; must be specified)
TSK
Task image (default)
TXT
Text file (convention; must be specified)
ULB
Universal library file (default)
2.2.5
by
the
PAT
Examples of File Specifications
In the following examples, the three letters that identify the task,
followed by a right-angle bracket, are the standard task prompts for
the respective system programs (for example, PIP».
•
Assemble the MACRO-II source file CRGPT.MAC and create the
object output file CRGPT.OBJ. UFD [200,200J on device DMO:
is specified for both files.
MAC>DMO:[200,200JCRGPT.OBJ=DMO:[200,200JCRGPT.MAC~
(
•
Delete the file SBG.OBJ;5. The output file specification is
not applicable and therefore is omitted. The input device
defaults to SY:.
PIP> [200, 200 JSBG. OBJ; 5 IDE
•
Task build the object file CRGPT.OBJ.
(.OBJ is the default
file type for object files.) The output file will be named
CRGPT.TSK because .TSK is the default file type for the Task
Builder's output file.
The device and UFD are also defaulted.
TKB>CRGPT=CRGPT
•
~.
~
Delete all files with the name TESTDAT, regardless of type or
version.
The system uses default values for the device and
UFD.
PIP>TESTDAT.*;*/DE~
2-9 '
SYSTEM CONVENTIONS
2.3
DEVICES
A primary function of the operating system is to manage all connected
peripheral devices and thereby maintain efficient system performance.
Peripheral devices are the actual hardware elements that make up the
computer
system.
During system generation, the system manager
explicitly describes all peripheral devices attached to the system.
Devices within multiuser protection systems are subject to a special
set of MCR functions (see Section 2.3.5).
Each device has a unique identifier. The identifier consists of two
alphabetic characters that form a logical device name (see Section
2.3.4) and an optional unit number of up to three octal digits
followed by a colon (:). If you omit the optional octal unit number,
the system defaults to unit number o.
See the RSX-IIM System Generation and Installation Guide or the
RSX-IIM-PLUS System Generation andInstallation Guide for a list of
the peripheral devices supported by the respective- operating system.
2.3.1
Logical Unit Numbers
A task performs I/O operations using logical units identified by
numbers, called logical unit numbers (LUNs), rather than using
specific device units. Yo~ assign a LUN to a specific device before
the task actively uses the LUN. You can make the LUN assignment at
one of three times:
1.
At task-build time
2.
From within the task at run time using
directive
3.
With the REASSIGN command after the task has
and while it is dormant
the
ALUN$
Executive
been
installed
c
Refer to the RSX-IIM/M-PLUS I/O Drivers Reference Manual or the
appropriate language user's guide for more information about logical
unit numbers.
2.3.2
(
Pseudo Devices
A pseudo device is a device unit name that usually corresponds to a
real physical device.
This association is declared through the
commands ASSIGN and REDIRECT.
Pseudo devices provide a shorthand
method for referencing the physical devices (for example, the pseudo
device name SY: refers to the user's system device). Table 2-1 lists
some of the RSX-IIM/M-PLUS pseudo devices.
Table 2-1
Pseudo Devices
Pseudo Device
Name
Console listing device
CL:
Console output device
CO:
(Continued on next page)
2-10
SYSTEM CONVENTIONS
Table 2-1 (Cont.)
Pseudo Devices
(
Pseudo Device
Name
System library device
LB:
Terminal input/output device
TI:
User's system device
SY:
Spooling device (RSX-IIM-PLUS only)
SP:
In a given task, LUN 1 may be assigned to CL:, the console listing
device.
When the task references LUN 1, the data is sent to whatever
to any
device CL: has been redirected to. You can redirect CL:
appropriate device (a line printer or a terminal, for example) without
affecting the task's execution.
A pseudo device redirected to a terminal assumes the privilege status
of the terminal to which it is redirected.
If the terminal is
privileged, CL: becomes privileged when it is redirected to that
terminal.
But if CL: is subsequently redirected to a nonprivileged
terminal, it will also become nonprivileged.
The normal procedure is to redirect the console output device (CO:) to
the main operator's terminal and CL: to the line printer. The system
automatically redirects TI:, the most commonly qsed pseudo device,
depending on how a task has been activated:
c
c
2.3.3
•
When you issue the RUN command to activate a task immediately,
the system redirects the TI: for that task to your terminal.
•
If, in a task, the Executive directives RQST$ or SPWN$
activate another task, that task's TI: defaults to the TI:
of the task that issued the directive. A privileged task can
specify an alternate TI: for the activated task.
•
If the Executive enters a task into 'the clock queue for
activation
after
a specified interval, the task's TI:
defaults to CO:.
(Both the RUN command and the Executive
directive RUN $ allow a task to be activated at a specified
interval from the time the command or directive was issued.)
The Null Device
Program testing often requires an available input or output device.
The null device (NL:) can be used for either of these purposes. NL:
is neither a pseudo nor a physical device, but, most of the time, it
is considered to be a pseudo device.
When a task reads from NL:, NL:
returns the code for end-of-file
(IE.EOF).
When a task writes to NL:, NL: returns the code for
success (IS.SUC) but discards the output. As an example, if you are
testing a program that normally generates large amounts of printout,
you can assign the appropriate LUN to NL: rather than wasting paper
or disk space.
(
2-11
SYSTEM CONVENTIONS
2.3.4
Logical Device Names and Logical Names
Logical device names provide another means by which tasks can maintain
device independence.
A logical device name has the same syntax as a
physical device unit. This syntax consists of a 2-letter ASCII name,
and an optional unit number of one or two octal digits followed by a
colon (:).
The name can either be equivalent to a
standard
RSX-IIM/M-PLUS device name (for example, DM:) or it can consist of two
letters picked at random (for example, ZZ:). Before you run a task
that refers to a logical device rather than a physical device, you
must issue the ASSIGN command to associate the logical device name the
task uses with a physical device unit (see Chapter 3).
NOTE
The names II:, and RD: are used by DIGITAL software.
Using these names as logical device names could
produce undesirable results.
In addition to logical device assignments, RSX-IIM-PLUS operating
systems that select extended logical name support during system
generation can create and delete logical name assignments.
You can
assign logical names to file specifications and to other logical
names. - You can have as many as ten levels of logical assignments.
The ASSIGN and DEFINE LOG ICALS command descriptions in Chapter 3
provide detailed explanations of logical name assignments.
The term "logical assignments" can apply to either logical device or
logical name assignments. There are five types of logical assignments
on RSX-IIM/M-PLUS operating systems:
task
assignments,
global
assignments,
group
assignments/
local
assignments, and login
assignments.
•
Task assignments apply to an individual task and
when the task has completed executing.
are
•
Local assignments apply only to tasks initiated from the
terminal used to make the assignments.
Any terminal can
define or delete its own set of local assignments.
•
Login assignments apply only to systems that support multiuser
protection.
When a user issues the HELLO (or LOGIN) command
to log in to the system, the system automatically establishes
one or more login logical device assignments. The login
assignments apply only to tasks initiated from the terminal
while the current user is logged in. Only privileged users
can define or delete login assignments.
•
Group assignments apply to tasks run by users who have a
common group number in their User Identification Code (UIC).
•
Global assignments apply to all tasks running in the system.
deleted
The system uses logical assignments in the following order:
task,
local, login, group, and global. If you make a iocal assignment using
a logical name that is already used in a login assignment, the system
uses the local assignment. When you delete the local assignment, the
system resumes using the login assignment.
'
2-12
c
c
c
SYSTEM CONVENTIONS
(
Also, the Executive sets up a logical device table that records all
logical device assignments and notes whether each assignment is local,
login, group, or global. The Executive then searches the logical
device table before the physical device table every time a task refers
to a device. Thus, a logical name found in the logical device table
receives precedence over a physical device unit that has the same
identifier.
2.3.5
Public, Private, and Unowned Devices
Systems
that
support
multiuser
protection
impose
special
characteristics on devices.
Devices can be public, private, or
unowned. These characteristics are defined as follows:
•
A public device is a device that anyone logged into the system
can use.
A privileged user can make a device public by
issuing the SET /PUB command. If a privileged user mounts a
volume on a public device, all system users can access files
on the volume without having to mount the volume themselves
(depending on the volume and file protection specified for the
volume). A public device cannot be allocated and can only be
dismounted by a privileged user with the DISMOUNT /DEV
command.
{See Chapter 3 for descriptions of the MOUNT,
DISMOUNT, and SET commands.}
•
A private device is a device that a user has allocated by
means of the ALLOCATE command. Only privileged users and the
owner of a private device can access the device for use within
the Files-II file system. If a nonprivileged user allocates a
device and mounts a volume on the device, other nonprivileged
users cannot access the volume; privileged users can access
the volume by issuing a MOUNT command.
•
An unowned device is a device that is neither public nor
private.
If a user, either privileged or nonprivileged,
mounts a volume on an unowned device, all other users can
issue subsequent MOUNT commands and thus access the volume.
(
Nonprivileged users can allocate and mount a volume on an unowned
device, and privileged users can also make an unowned device public.
c
A privileged user can designate any device in the system as a public
device. The devices most commonly made public are the system disk (by
default) and the system library device.
The ALLOCATE command (see Chapter 3) makes an unowned device private
to the user issuing the command. Allocating a device prevents any
other nonprivileged user from accessing the device.
(Privileged users
can override a nonprivileged allocation.) When a user accesses a
device without allocating it, other users can then access and/or
allocate that device.
The DEALLOCATE command (see Chapter 3) changes a private device back
to an unowned device, thereby allowing other users to gain access to
it. Privileged users can deallocate any private device regardless of
who owns it.
Nonprivileged users can deallocate on;ly their own
private devices. When a user logs out, the system ~automatically
dismounts and deal locates any private devices belonging to that user.
For efficient use of system resources, however,
users
should
deallocate devices as soon as the devices are no longer needed.
2-13
SYSTEM CONVENTIONS
c
2.4
TERMINALS
The terminal is the primary means of communication between the user
and the computer system.
Each terminal in a system has a number
associated with it, which is displayed when you log in. You can also
refer to any terminal that you use as TI:, and you can work from more
than one terminal at the same time.
In RSX-llM/M-PLUS, several terminals can operate concurrently.
Each
terminal operates independently of others in the system so that each
can run tasks at the same time. For example, the .PIP utility and the
MACRO-ll Assembler can .run concurrently from different terminals.
(The same task can also run concurrently from different terminals,
although each copy of the task running will have its own identifier.
See Section 2.5.4 for more information.)
2.4.1
Input Prompts
When you use MCR, there are three prompts that indicate a terminal
waiting for input from you:
•
The default prompt (»
•
The task prompt (tsk»
•
The MCR prompt (MCR»
is
The default prompt (» at the beginning of a new line indicates that
the
terminal is ready to accept unsolicited input.
The term
unsolicited implies that no specific task has requested input from the
terminal.
Whatever you type in response to the default prompt is
directed to MCR.
(An abnormal situation can occur, however, if a task
either solicits input or attaches to the terminal without displaying a
task prompt. A soliciting or attached task might receive input that
you intended for MCR. See Section 2.4.4 for information on attached
terminals.) When MCR receives unsolicited input, it identifies,
analyzes, and responds appropriately to the input.
When MCR activates a task to service
prompts as follows:
a
command,
the
task
normally
tsk>
The variable tsk is a 3-character task name.
tasks identify themselves by a 3-character
should do the same.)
(All DIGITAL system
prompt and user tasks
As long as a prompting task has ~ttached to a terminal, the task
receives all solicited input entered at the terminal until the task
detaches (see Section 2.4.4). The terminal discards all unsolicited
input.
An unattached task, however, may not receive solicited input
2-14
c
c
SYSTEM CONVENTIONS
(
because another task could solicit input from 'the terminal before you
can type a response to the prompt for the unattached task. The
intervening task would' then recei v.e the input intended for the
unattached task.
To avoid this situation, every task that solicits
input from a terminal should perform the following
sequential
procedure:
1.
Attach to the terminal
2.
Prompt with a properly formatted identifier (that is, tsk>)
3.
Solicit input (issue a read request)
The MCR prompt (MCR»
2.4.2
is described in Section 1.1.1.
Special Character Keys and Control Characters
You can request the system to control terminal operation by means of
special character keys and control characters. The relevant special
character keys are TAB, ESC (or ALT), RETURN, and DELETE (or RUBOUT).
A control character is produced when you press the CTRL key and
simultaneously press a letter key.
When you press CTRL/R, CTRL/U, or CTRL/Z, the Executive and the
terminal driver display AR,
AU,
or AZ at the issuing terminal and
perform the related function. When you press CTRL/C, the explicit MCR
prompt
(MCR»
is displayed.
(If the terminal is set to recognize
commands from DCL or a user-written command line interpreter, pressing
CTRL/C would display that prompt instead.) For the other control
characters, the Executive does not return a display.
(
Table 2-2 lists all the special character keys and control characters,
and describes the function of each.
Table 2-2
Special Character Keys and Control Characters
Character
Description
RETURN
The RETURN key terminates a line of input and advances
the cursor or print head to the beginning of the next
line.
ESC
The ESC (escape) key terminates a line of input
without moving the cursor or print head. When used to
terminate an MCR command, it suppresses the default
MCR prompt. See the descriptions of the OPEN and RUN
commands (in Chapter 3), which have special uses for
the ESC key.
(
If the appropriate optional facility was selected for
your system during system generation, the ESC key can
be the first character in an escape sequence.
For
more information about escape sequences, refer to the
RSX-llM/M-PLUS I/O Drivers Reference Manual or the
description of the SET jESCSEQ command in Chapter 3 of
this manual.
(Continued on next page)
2-15
SYSTEM CONVENTIONS
Table 2-2 (Cont.)
Special Character Keys and Control Characters
Character
DELETE
c
Description
The DELETE key deletes the last character typed at the
terminal as well as additional contiguous characters
if the key is pressed repeatedly.
On
non~CRT
terminals, the first DELETE deletes a character and
prints a backslash (\) and and the deleted character.
Subsequent deletions cause the system to print the
deleted characters. Then, when you enter the first
non-DELETE character, the system prints a terminating
backslash and follows it
with
that
non-DELETE
character.
For example:
----first DELETE
I ---second DELETE
I I----third DELETE
I I I ----first non-DELETE
I II I
MISTKAE\EAK\AKE
The result is MISTAKE.
On a CRT terminal that supports backspacing (a system
generation option in RSX-llM; always included in
RSX-llM-PLUS) and has been declared to be a CRT
terminal by the SET /CRT=ttnn: command, the DELETE
key moves the printing position one space to the left
and erases any character displayed in that position.
For example, to correct the word MISTKAE, press
DELETE key three times to erase E, A and K.
result is MIST. Then type AKE to get MISTAKE.
the
The
Note that when DELETE deletes a character in the last
character position on the right of the screen, the
last character appears to remain and the next-to-last
charac~er disappears.
However, the system has in fact
deleted the last character.
You can refresh the
screen and verify your correction by pressing CTRL/R.
CTRL/C
c
(
Pressing CTRL/C either as the first character in a
line or when the terminal is sending data causes MCR
to prompt for command input with the explicit prompt
MCR>.
If the terminal is set to a command line
interpreter (CLI) other than MCR, pressing CTRL/C
displays the explicit prompt for the CLI.
(Two
special effects of CTRL/C are described in
the
following text.)
If a task is prompting for· input when you press
CTRL/C, MCR displays its explicit pro~pt, then returns
control to the interrupted task after receiving a
single line of input.
(An exception occurs when an
attached task specifies an asynchronous system trap
(AST) for unrequested characters.
In this case,
CTRL/C causes an AST to occur, thereby gaining the
task's attention rather than MCR's.)
(Continued on next page)
2-16
(
SYSTEM CONVENTIONS
Table 2-2 (Cont.)
Special Character Keys and Control Characters
Character
Description
Special effects:
•
If the last character entered at the terminal
CTRL/S,
CTRL/C
resumes the output that
suspended by CTRL/S.
•
If a terminal has been set to "hold screen" mode
by the SET /HOLD command, CTRL/Chas the effect of
a SET /NOHOLD command; that is, CTRL/C disables
hold screen mode.
(The hold screen feature is, in
some cases, a system generation option in RSX-IIM
but is always included in RSX-IIM-PLUS.)
See Section
CTRL/C.
~
C
c
1.1.1
for
more
information
on
was
was
using
CTRL/I
(or
TAB)
Pressing CTRL/I (or TAB) moves the cursor or print
head to the next horizontal tab stop on the line. The
system establishes tab stops at every eighth character
position in the line (8, 16, 24,and soon).
CTRL/K
Pressing CTRL/K causes a vertical tab by directing the
system to output four line feeds (four blank lines).
CTRL/L
Pressing CTRL/L causes a form feed
(but the system
does not perform paging).
A form feed consists of
eight line fee,ds, so CTRL/L appears on the terminal as
eight blank lines.
CTRL/O
Pressing CTRL/O alternately suppresses and resumes the
display of output at your terminal.
It allows you to
skip over any unwanted output and then continue the
display at a later point.
When you press the first CTRL/O,the system discards
the output it is sending to your terminal rather than
displaying it.
(The system can send the output much
faster when it does not have to display it.) When you
press the secondCTRL/O, the system resumes displaying
the output at the point it has reached in sending it
(not from the point where you pressed the first
CTRL/O) •
If you do not press another CTRL/O, the
system continues displaying the output until
it
reaches the end of the file.
Pressing CTRL/O may cause different system actions
depending on the state of your terminal when you press
it.
If the terminal is attached to a task other than
MCR, pressing CTRL/O suppresses the display of the
task's output until you press another CTRL/O to resume
the display
(as described previously). However, if
the terminal is not attached to anoth~r task, CTRL/O
suppresses only the remainder of the line currently
being displayed.
Subsequent lines of output will
still be displayed.
c
(Continued on next page)
2-17
SYSTEM CONVENTIONS
Table 2-2 (Cont.)
Special Character Keys and Control Characters
Character
Description
CTRL/a
Pressing CTRL/a' after a
CTRL/S
resumes
output
suspended by CTRL/S.
(This feature is a system
generation option in RSX-llM but is always included in
RSX-llM-PLUS. )
CTRL/R
Pressing CTRL/R before pressing a line terminator
(RETURN, ALT or ESC) causes the system to retype the
current line on a' new line, omitting any deleted
characters.
You
can
then continue typing the
remainder of the line. '
For example:
MISTKAE\EAK\AKE AR
MISTAKE
If the current line is empty and you issue
the explicit MCR prompt (MCR», CTRL/R
system to perform a carriage return and
CTRL/R is echoed as AR .
(This feature
generation option in RSX-llM but is always
RSX-llM-PLUS. )
CTRL/S
CTRL/U
CTRL/R from
directs the
line feed.
is a system
included in
Pressing CTRL/S while the terminal is receiving output
suspends additional output until you press CTRL/a or
CTRL/C. The suspended output is merely delayed, not
discarded as with CTRL/O. The combined functions of
CTRL/a and CTRL/S are convenient when using a CRT
terminal.
(This feature is a system generation option
in RSX-llM but is always included in RSX-llM-PLUS.)
~
c
Pressing CTRL/U before typing a line
terminator
(RETURN, ALT or ESC) deletes the current line. The
system responds with a carriage return and line feed
and displays a new prompt so that the line can be
retyped.
The system also displays a CTRL/U when you begin to
type a command line but do not press the RETURN key
before the timeout count expires.
(The timeout count
is specified at systero generation time.) Again, a new
prompt is displayed.
CTRL/U is echoed as AU.
(This control character works
only with the full-duplex terminal driver.)
CTRL/X
Pressing CTRL/X clears the terminal typeahead buffer.
The
typeahead
buffer
temporarily
stores input
characters until the terminal driver can pass them to
the task.
When the typeahead buffer is full, input
characters are not accepted. Pressing CTRL/X clears
the buffer.
CTRL/X is echoed as AX.
(This control
character works only with the full-duplex terminal
driver.)
CTRL/Z
Pressing CTRL/Z indicates end-of-file. It is used to
indicate to system tasks such as MAC, PIP, and TKB
that you are finished and the task may exit.
CTRL/Z
is echoed as AZ.
2-18
c
SYSTEM CONVENTIONS
2.4.3
Terminal Privilege
You can issue privileged commands only from a privileged terminal. On
multiuser protection systems, individual users are either privileged
or nonprivileged.
When you log in, the terminal assumes your
privilege status~ On other systems, a terminal's privilege status is
determined initially at system generation. You can also use the SET
/[NO]PRIV command (see Chapter 3) at a privileged terminal to modify
the privilege status of your own and any other terminal connected to
the system.
CAUTION
You must take great care when
any
terminal
is
privileged.
Privileged
commands can disrupt or severely impair
system operation.
2.4.4
Attached and Unattached Terminals
A terminal is attached when all input and output are directed to or
from a task other than MCR. For example, when you invoke a task (such
as the text editor EDT), the task usually attaches to the terminal so
that no other task can use the terminal for I/O. When you wish to
exit (by pressing CTRL/Z, for example), the task is detached from the
terminal and subsequent input is usually directed to MCR.
c
Since an attached terminal directs all input to the dedicated task,
you must either exit from the task or press CTRL/C to gain MeR's
attention before attempting to communicate with MCR.
(See Section
1.1.1 for a description of CTRL/C as a means of temporarily gaining
MCR's attention.)
. .
See the RSX-llM/M-PLUS I/O Drivers Reference
information on terminals and terminal drivers.
2.4.5
c
Manual
for
more
Slave Terminals
You ca'n dedicate a terminal exclusively to one or more tasks by
issuing a SET command option that sets the terminal to slave status.
(A special I/O function issued by a task can also set a terminal to
slave status.) The difference between a slave terminal and an attached
terminal is that a slave terminal rejects all unsolicited input,
including CTRL/C (however, a slave terminal does accept CTRL/O,
CTRL/Q, and CTRL/S). Attached terminals do accept CTRL/C.
Until you issue another MCR command (or a task issues another special
I/O function) to delete the slave status, the terminal can only be
used to communicate with tasks soliciting input from Jthe terminal.
Slaved terminals are often dedicated to real-time applications.
See the RSX-llM/M-PLUS. I/O Drivers
terminals and terminal drivers.
2.5
Manual
for
more
information
on
TASKS
The basic executable unit of an RSX-llM/M-PLUS system is the task.
A
task is either privileged or nonprivileged. A privileged task has
special device and memory access rights that a nonprivileged task does
2-19
SYSTEM CONVENTIONS
not have. Because of their special access rights, privileged tasks
are potentially hazardous toa running system whereas nonprivi1eged
tasks are not.
The following sections give only
Consult the RSX-11M!M-PLUS and
complete description.
2.5.1
(
cursory information about tasks.
Micro/RSX Task Builder Manual for a
Partitions
A task runs in a predetermined contiguous area of memory
partition. A partition has the following characteristics:
•
A name
•
A defined size
•
A fixed starting address
•
A defined type
called
a
relationship between
nds
whether the
2.5.1.1 Partition Types - There are two types of partitions in
tasks can execute:
•
System-controlled
•
User-controlled
which
c
(
In a system-controlled partition, the Executive allocates available
space to accommodate as many tasks as possible at anyone time. This
allocation may involve shuffling resident tasks to arrange available
space into a contiguous -block large enough to contain a requested
task. Only mapped systems support system-controlled partitions.
In both types of partitions, the Executive can temporarily move
(checkpoint) a resident 'ta.k to a disk to make space available for
another task.
c
2-20
SYSTEM CONVENTIONS
2.5.2
Multiprogramming
Tasks compete for system resources (including memory) on the basis of
priority and resource availabiility_.
The priority of a task is
determined by a number assigned when the task is created by the Task
Builder, when it is installed, or when it is run. A priority number
is between 1 and 250(decimal), where 250 is the highest priority. The
highest priority task that has access to and can use all the resources
it needs has control of the cPq.
A task often becomes blocked when it requests system services.
For
example, it can block itself as it waits for an I/O transfer to
complete. While the task is blocked in this way, the Executive looks
for another task to use the CPU. The chosen task will be the one that
has the highest priority and whose needed resources are available.
c
2.5.3
Creating a Task
You perform four steps to create a task and prepare it for execution:
c
1.
Enter a program in a supported
editor.
source
language
through
an
2.
Submit the source code to the
appropriate
(assembler/compiler) to produce an object file.
3.
Submit the object file to the Task Builder to produce a
image file.
4.
Use the INSTALL command to install the task image file in the
system or use the install-run-remove option of the RUN
command (see Section 2.5.5.1).
translator
task
The output files that result from Steps I, 2, and 3 are each stored on
a Fl.les-Il volume.
2.5.4
Task-Naming Convention
c
2-21
SYSTEM CONVENTIONS
(
c'
\
c
'C
2-22
SYSTEM CONVENTIONS
(,
2.5.5
Installing a Task
When you install a task with the INSTALL command or a form of the RUN
command, the system records a number of task parameters in a
system-resident list called the System Task Directory (STD).
These
parameters include the name of the task and the address on the volume
that contains the task image. An installed task is defined as a task
that has an entry in the STD~ it need not be resident in memory nor
competing for system resources. The system considers a task dormant
(not active) until a request is made for it to run~
The concept of dormant and active tasks is important in a real-time
system.
A dormant task does not use any memory outside of the
Executive (it requires only an STD entry and need not be resident),
yet when the task is needed to service a real-time event, the
Executive quickly and efficiently
introduces
it
into
active
competition for ,system resources.
An installed task's STD entry
enables this quick response because the STD contains all
the
parameters the system needs to retrieve the requested task.
c
c
You can run an installed dormant task by issuing the RUN ~ommand, or
another task can request the task to run by issuing an Executive
directive, such as RQST$ (Request), RUN$ (Run), or SPWN$ (Spawn).
When the Executive receives a request to run a
series of actions:
task,
it
performs
a
1.
Places the task in active competition for system
(including memory) with other resident tasks.
resources
2.
Allocates the necessary resources as they become free.
3.
Brings the task into memory when there is space available in
its partition.
(The Executive will checkpoint a task with a
lower priority, if there is one, to make room for the
requested task.)
If another task fully occupies the partition in which the new task is
to be installed and no resident task can be checkpointed, the system
places the task in a queue of other requested tasks, each waiting for
space to become available in its partition. Note that the number of
installed dormant tasks can, and usually will, far exceed the number
of active tasks.
l
2-23
SYSTEM CONVENTIONS
(~-
c
c
2.6
NONPRIVILEGED USE OF ACNT
RSX-IIM/M-PLUS systems provide an Account File Maintenance Program
(ACNT) for creating and maintaining an account file for a multiuser
protection system. The account file contains entries for all the UICs
that have been authorized for use in the system. One UIC can be
shared by several users, each user having his or her own password.
2-24
SYSTEM CONVENTIONS
c
c
c
2-25
(
CHAPTER 3
MCR COMMANDS
This chapter provides a detailed description of each MCR command. The
commands are presented in alphabetical order, rather than by function
or privilege status.
Note that the commands are
alphabetized
according to the abbreviated forms of their names.
~
The descriptions of the commands and command messages in this
adhere to the following notational conventions:
chapter
..•
•
Lowercase text indicates a variable whose actual value is
determined when the command is entered or the message is
issued. For example, the value of the variable taskname
depends on the name of the task associated with the command or
message.
•
Square brackets ([]) indicate optional entries in a command
line or file specification.
Note that when an option is
entered, the brackets are not included.
(
Square brackets are also a part of the User File Directory
(UFO) and User Identification Code (UIC) syntax ([group,
member]). When you use a UFO or UIC (in a file specification,
for example), brackets are required syntax elements; that is,
they do not indicate optional entries.
•
c
unless specified otherwise, all numeric values required in a
command can be .entered as decimal or octal. Usually, decimal
values are indicated by a trailing period (.), and octal
values are indicated either by the absence of a period or by a
pound sign character (#) preceding the number.
For example,
the following three values are equal:
255.
377
#377
The command descriptions in this
consisting of the following parts:
chapter
•
The command name
•
The command line format
•
Command-related error messages
have
a
standard
format
The remainder of this introduction describes the parts of a command
description.
A part that does not apply to a particular command is
omitted from that command description.
3-1
MCR COMMANDS
COMMAND NAME
Each command description begins by showing the command name.
The
minimum acceptable abbreviation of the command name is shown in large
bold letters at the top of the page. The full command name appears in
capital letters underneath the abbreviation.
Immediately following
the command name, the status of the command is indicated
in
parentheses, using the following symbols:
•
(NP) indicates a nonprivileged command.
•
(p) indicates a privileged command.
•
(NP,P) indicates
options.
a
nonprivileged
•
(P,NP) indicates
options.
a
privileged
Finally, each command name description
command's function.
command
command
concludes
with
with
by
(
privileged
nonprivileged
describing
the
(i
Format
~
This part of the command description shows the command format,
describes any command line parameters, and for most commands, includes
examples of command line syntax.
Command-Related Error Messages
This part of the command descr1ption lists and explains the error
messages that are specific to the command. The command may also
produce the common error messages listed in Appendix A. These common
error messages are not listed with the individual commands.
(
(
(
3-2
MCR COMMANDS
ABO
(
3.1
ABORT (NP,P)
The ABORT command terminates execution of a specified task.
On
operating systems that have multiuser protection, nonprivileged users
can abort a nonprivileged task if the task was requested from the same
terminal that the ABORT command is issued from. On operating systems
that do not have multiuser protection, nonprivileged users can abort
any nonprivileged task. Nonprivileged users can also abort privileged
tasks requested from the issuing terminal if the tasks have requested
an exit AST service routine with the SREX$ form of the SPECIFY
REQUESTED EXIT AST Executive directive. Privileged users can abort
any task.
When a task that has specified an exit AST service routine is aborted,
it
enters
the
routine instead of being aborted immediately.
Privileged tasks enter the specified AST routine each time a valid
abort request is issued.
However, future exit ASTs are not queued
until the first exit AST has been effected. Nonprivileged tasks enter
the specified AST routine only once. After that, any valid attempt to
abort the task succeeds.
See the RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual for
more information on the SPECIFY REQUESTED EXIT AST directive. Note
that the issuing terminal receives no indication that the task being
aborted was actually aborted or that it received the abort AST
instead.
(
Aborting a task forces an orderly termination of the
To effect the termination, the system:
specified
task.
•
Performs I/O rundown. Cancels I/O for all non~file-structured
devices.
Allows I/O for file-structured devices to complete
and then deaccesses the files.
Detaches all attached devices.
(I/O rundown may take a considerable amount of time for tasks
connected to a network node.)
•
Requests the Task Termination Notification program (TKTN) to
display a message on the aborted task's issuing terminal
giving the reason for the termination.
(If the /PMD keyword
is specified and the task is not checkpointed, the task's
registers are also displayed.)
•
Releases the task's partition if the task is not fixed.
•
If the system supports the ALTER PRIORITY directive (a system
generation option), alters the task's running priority to
247 (decimal) (unless the exit AST service routine has been
specified).
A task must be memory-resident to be aborted:
this change in running priority usually causes a quick return
for a checkpointed task.
c
If the command includes the optional keyword /PMD,
it forces the
system to produce a Postmortem Dump of the aborted task. The dump is
generated even if the task was not built with the Task Builder /PM
switch or installed with the INSTALL /PMD=YES keyword.
Format:
ABO[RT] taskname[/PMD][/TERM=ttnnn:]
3-3
MCR COMMANDS
ABO (Cont.)
(
taskname
The name of the task to be aborted. If you omit the taskname,
the command attempts to abort task ttnn.
(The variable nn is the
octal unit number of the issuing terminal.)
Likewise, if you specify only the first three characters
taskname, ABORT defaults the taskname to tskTnn.
of
the
/PMD
A keyword that requests a Postmortem Dump of the aborted task.
Examples:
>ABO MAC @)
Task "MACT3
terminated
Aborted via directive or CLI
II
MCR (the command line interpreter for these examples)
aborted a task called MACT3, even though the command, issued
from TT3:, specified only the 3-letter task name.
The command >ABO MACT3
has the same effect.
issued from any privileged terminal
>ABO @)
Task "TT7
terminated
Aborted via directive or CLI
c
II
MCR aborted the task, TT7, from TT7:; the task name does not
have to be specified to abort task TTn.
Command Error Messages:
On receiving an ABORT command, MCR requests the Executive to
abort the task.
The Executive subsequently activates the Task
Termination Notification program (TKTN). TKTN then produces the
termination display shown in the preceding examples. Messages
following an ABORT command can therefore corne either from the
ABORT command itself or from TKTN.
Messages from ABORT command:
ABO
Task marked for abort
A previous request has already been made to abort the
specified task~ but the abort has not yet occurred. The
task marked for abort is probably not currently resident in
memory or it has outst?lnding I/O (for example, an MM:
tape-positioning operation must complete).
3-4
(
MCR COMMANDS
(
ABO (Cont.)
ABO -- Task not active
The specified task is not currently active.
Messages from Task Termination Notification program (TKTN):
TKTN displays information about task aborts,
the ABORT command or by some other means.
format:
whether caused by
The display has the
Task terminated
C_.,
~-
Following the displayed cause for the abort is a list of the
task's registers at the time of the abort (if the task was not
checkpointed). The possible causes of an abort are described in
the following messages:
Aborted via directive or CLI
Either an Executive directive or a CLI command
another task caused the task to be aborted.
issued
by
Aborted via CLI
Postmortem Dump will be generated
c
A CLI command aborted the task and
Dump.
requested
a
Postmortem
11/40 F.P. exception
The task encountered a floating point exception while
executing on a PDP-ll/40 and no SST routine was specified to
process the trap.
AST abort. Bad stack
c
An asynchronous system trap (AST) could not be effected
because the AST parameters could not be pushed onto the
task's stack.
Checkpoint failure. Read error
The task could not be read
checkpointed.
back
into
memory
after
being
lOT execution
c
The task executed an Input/Output Trap (lOT) instruction,
but no synchronous service trap (SST) routine was specified
to process the trap.
-
3-5
MCR COMMANDS
c
ABO (Cont.)
Load failure. Read error
The task could not be loaded because of a hardware error.
'Memory protect violation
The task encountered a memory-protect violation and
routine was specified to process the trap.
no
SST
Non-RSX EMT execution
The task executed an EMT instruction with an argument other
than 377(octal) or, in the case of a privileged task
switching to system state, 376(octal), and no SST routine
was specified to process the trap.
Odd address or other trap four
The task executed a word instruction with an odd address or
referenced a nonexistent memory location in an unmapped
system, and no SST routine was specified to process the
trap.
Parity error
A parity error occurred while the task was executing.
The
task was fixed in memory so that the memory could not be
reused by another task.
Required bus runs are offline or not present
(RSX-IIM-PLUS multiprocessor operating systems on~y.) The
task, or a common that the task is mapped to, was installed
with an affinity for a CPU or a bus run that'is off line.
Reserved inst execution
The task executed an illegal instruction and no SST
was specified to process the trap.
routine
SST abort. Bad stack
An SST could not be effected because the SST parameters
could not be pushed onto the task's stack, or a stack
overflow was detected in an unmapped system, as indicated by
a non-zero value in the header guard word.
Task exit with outstanding I/O
The task exited with one or more outstanding I/O requests.
Tasks should terminate all I/O operations before exiting.
The system does, however, process all outstanding I/O
requests.
3-6
(
MCR COMMANDS
ABO (Cont.)
(
Task installed in more than one system
The task image file has been installed in more than one
system.
When a task is installed, pointers to various
system data structures are stored in the task header in the
task image file.
If a task is installed in more than one
system, the header contains pointers for the last system in
which the task was installed. When the task is loaded for
execution, the loader verifies that the header contains
valid pointers for the current system. When a task has been
installed in more than one system, the loader check fails
and the task is aborted.
T-bit trap or BPT execution
[-~.'
~
c
The task either set the T-bit in the Processor Status Word
(PSW) or executed a Breakpoint Trap instruction, qnd no SST
routine was specified to process the trap.
Trap execution
The task executed a TRAP instruction and no SST routine
specified to process the trap.
c
3-7
was
MCR COMMANDS
(
(
(
3-8
MCR COMMANDS
(
c
(
(
3-9
MCR COMMANDS
c
(
3-10
MCR COMMANDS
ACS
(
3.3
ALLOCATE CHECKPOINT SPACE (p)
The ALLOCATE CHECKPOINT SPACE (ACS) command allocates or discontinues
a checkpoint file on disk for systems that support the dynamic
allocation of checkpoint space. The disk containing the checkpoint
file must be in Files-II format. Only one checkpoint file per disk is
allowed, but numerous disks can each contain a checkpoint file.
Generally, sufficient checkpoint space is twice the total amount of
memory that all of the running tasks will use.
When the system needs checkpoint space, it searches the checkpoint
files in the order in which they were created. If space is not
available in the first file created (the primary file), it searches
for space in the second file created (the secondary file), and so on.
An ACS command that discontinues a checkpoint file may not take effect
immediately.
If the specified file contains one or more checkpointed
tasks, the tasks must be returned to memory before the system can
discontinue the file.
However, once the request to discontinue the
file has been made, the system does not use the file for any more
checkpointed tasks.
Format:
ACS ddnn:/BLKS=n
ddnn:
(
A device unit that contains a mounted Files-II disk.
number (nn) is not specified, the default is zero.
If the unit
/keyword:
/BLKS=n
c
Specifies the number (n) of blocks on the disk to be
allocated for the checkpoint file.
(A block is 512 decimal
bytes.) For example, the following
command
allocates
250(decimal) blocks for a checkpoint file on the DB: disk:
>ACS DB:/BLKS=250.®m
When n is zero, the system discontinues the use of the
checkpoint file; the file is neither deleted nor truncated.
However, the use of the file is discontinued only after all
of the tasks that are checkpointed to it can be brought into
memory and checkpointed elsewhere.
For example, the following command
>ACSDB:/BLKS=O ®m
discontinues the checkpoint file on disk DBO:.
This does
not mean that the space allocated to the checkpoint file is
freed. The system checkpoint file [O,O]CORIMG.SYS retains
the space initially allocated by the ACS command so that the
c
3-11
MCR COMMANDS
c
ACS (Cont.)
space will be available the next time it is needed. If you
want to free the space allocated to the system checkpoint
file after its use has been discontinued, use the following
commands:
>ACS ddnn:/BLKS=O
~
ACS -- Checkpoint file now inactive
>PIP
[O,OJCORIMG.SYS/TR~
You must set the block size of the checkpoint file to zero,
to discontinue the file before you can truncate it. Do not
issue the PIP command line until the "Checkpoint file now
inactive" message has been displayed. PIP cannot determine
if the checkpoint file is still in use, so iss.uing the
command line might cause a volume corruption or a system
crash.
Examples:
>ACS OS: /BLKS=250. ~
>ACS DB:/BLKS=1024.~
This command sequence allocates a primary checkpoint file on
OS:
and a secondary checkpoint file on DB:. The primary
file is 250(decimal) blocks long and the secondary file is
l024(decimal) blocks long.
When tpe system searches for
checkpoint space, it will first look in the file on OS: and
then in the file on .DB:.
>ACS OS: /BLKS=O
c
~
Discontinues use of the checkpoint file on OS:.
Command Error Messages:
ACS
Checkpoint file already in use on device
A previous ACS command established a checkpoint file on the
volume mounted on the specified device.
A volume can
contain only one checkpoint file.
(
ACS -- Checkpoint file now inactive
This message appears after you issue an ACS command to
discontinue a checkpoint file and the file does not contain
any checkpointed tasks. The message indicates that use of
the file was discontinued immediately after the command was
issued. If the file is still in use, TKTN will issue a
message when the file is finally discontinued.
(
',--
3-12
MCR COMMANDS
ACS (Cont.)
(
ACS -- File I/O error nnn.
The ACS command detected an error when it tried to allocate
or open the checkpoint file.
The code nnn.
is an FCS error
code that defines the cause of the error.
See
the
RSX-llM/M-PLUS
and
Micro/RSX I/O Operations Reference
Manual.
(If the code is -24, the message may indicate that
the disk,
usually a fixed-head disk, does not have enough
contiguous sp~ce to allocate the
file.
The
normal
implication of the code -24 is "device full".)
ACS
File not in use
A checkpoint file was not in use on the device specified
the ACS command.
in
ACS -- Not Files-ll device
The command specified a device
Files-ll disk.
The specified
mounted Files-ll disk.
***
that did not contain a
device unit must contain a
-- Checkpoint file now inactive
This message, issued by TKTN, indicates that a request to
discontinue use of a checkpoint file on device ddnn: has
finally been satisfied. The need to return checkpointed
tasks from the discontinued file back into memory caused the
delay between the request and this message.
c
***
Checkpoint space allocation failure
The task could not be checkpointed because there was not
enough room in the system checkpoint file and .checkpoint
space was not allocated in the task image file. Either make
the system checkpoint file bigger or create a second one.
c
Note that tasks built with the /AL switch are checkpointed
to their task image file if the system checkpoint file is
full.
3-13
MCR COMMANDS
c
ACT
J
3.4
ACTIVE (NP)
The ACTIVE command displays the names of all active tasks that have
the terminal from which the command is entered as their TI:. On
RSX-llM-PLUS operating systems, the display includes the octal unit
number of the terminal that initiated each task.
Format:
ACT[IVE] [/keyword]
/keywords:
/ALL
Displays the names of all active tasks that are currently in
the system.
(;
/TERM=ttnn:
Displays the names of all of
terminal specified by ttnn:.
the
active
tasks
for
the
Examples:
RSX-llM operating systems
c
>ACT (BIT)
MCR .••
.• • MCR
>ACT / ALL (BIT)
RMDEMO
MCR .••
•• • MCR
FllACP
••• PIP
>ACT /TERM=TT7:(BIT)
••• PIP
>
(
RSX-11M-PLUS operating systems
>ACT (BIT)
(TT17 :)
MCR •••
(TT17:)
ACTT17
>
>ACT / ALL (BIT)
(COO: )
LDR •••
RMDEMO (TT62:)
(TT17:)
MCR •••
FllACP (COO: )
(COO: )
DSOOFI
(COO: )
DS01Fl
LSTACP (COO: )
(COO: )
DB03Fl
,/
'(
3-14
..
MCR COMMANDS
(~
ACT (Cont.)
AT.V6
QMG...
HRC. . •
PIPTA1
(VT6:)
(coo:)
(coo: )
(TT101:)
>
>ACT /TERM=TT107:~
LBRTA7 (TT107: )
>
{ ~
.....
c
(
3-15
MCR COMMANDS
ALL
3.5
(
ALLOCATE (NP,P)
The ALLOCATE command establishes a specified device as your private
device.
This command applies to all RSX-IIM-PLUS operating systems
but only to RSX-IIM operating systems that
support
multiuser
protection.
Device allocation prevents other nonprivileged users from
accessing a device (see Section 2.3.5). Only the device's owner or a
privileged user can access or deallocate a private device. Mounted
devices, public devices, or other users' private devices cannot be
allocated.
The system automatically deallocates your private devices when you log
out by issuing the BYE command.
You may also allocate a device to a specific terminal rather than
TI:.
This allows you to allocate a device to a virtual terminal.
to
Format:
C
ALL[OCATE] dd[nn:] [=llnn:] [/keyword]
dd
The device mnemonic of the device that you want to allocate.
nn:
The optional unit number of the device. If the number and the
colon are omitted,
the system allocates the first available
logical unit of the dd-type device and displays the allocated
device in the following format:
(
ALL -- now allocated
lInn:
The optional name of a logical device, which the system creates
and assigns to the physical device being allocated.
(This is a
local assignment as created by the ASSIGN command.) Specifying a
logical device name is helpful when using the /TYPE keyword in an
indirect command file.
/keywords:
/TERM=ttnn:
Specifies the terminal number (ttnn:) to which the device is
to be allocated.
/TYPE=dev
Specifies the type of device that you want when you specify
a generic allocation.
Instead of allocating a specific
device, the command allocates the first available device of
the specified type. The variable dev is the physical name
of the device (for example, RP06, RK07).
When you use the /TYPE keyword, you specify the device type
only.
You do not include a unit number or a colon in the
specification.
3-16
(
MCR COMMANDS
ALL (Cont.)
(
(;Examples:
>ALL OK2:
~
Allocates disk OK2:.
c
>ALL OK:
~
Allocates disk DKO:.
>ALL OKl:/TERM=VTl:~
Allocates disk OKl:
VTl: •
to
the
specified
virtual
terminal,
>ALL ok=xxo: ~
ALL -- OK3: now allocated
(
Allocates the first available logical unit of OK {in this
case, disk OK3:,
since units 0, 1, and 2 were ,allocated
previously or are public devices} and assigns it the logical
name XXO:.
>ALL OB/TYPE=RP06 ~
Allocates any available RP06 disk.
l
3-17
MCR COMMANDS
c
ALL (Cont.)
Command Error Messages:
ALL -- Device allocated to other user
The specified device has already been allocated
user.
'by
another
ALL -- Device attached
The specified device cannot
attached to a running task.
be
allocated
because
it
is
ALL -- Device not in system
The specified device driver does not exist in the system, or
the data base for the device driver is not in the system or
in the driver's task image.
ALL -- Invalid keyword
The specified keyword
command.
cannot
be
used
with
the
ALLOCATE
ALL -- Pseudo device error
device.
Pseudo
The command attempted to allocate a public
devices cannot be allocated.
device.
The specified device is a
cannot be allocated.
pseudo
devices
c
ALL -- Public device
Public
ALL -- User logged on terminal
The command attempted to allocate a terminal that has been
logged-in by another user. Logged-in terminals cannot be
allocated.
3-18
c
MCR COMMANDS
ALl
(
3.6
ALTER (p)
The ALTER command
installed task.
changes
the
static
or
running
priority
of
an
Format:
ALT[ER] taskname /keyword(s)
taskname
The name of the task whose priority is to be altered.
/keywords:
/PRI=n
Changes the task's static priority,
and,
if the system
supports the· ALTER PRIORITY directive, the task's running
priority.
(All RSX-IIM-PLUSoperating systems support the
directive.)
/RPRI=n
Changes the task's running priority only (valid only
systems that support the ALTER PRIORITY directive).
in
c
The priority can be from 1 to 250(decimal). The system assumes that
the priority value you specify is an octal number unless you include a
period (.) after the value.
Examples:
(
3-19
MCR COMMANDS
ASN
3.7
c
ASSIGN (NP,P)
The ASSIGN command assigns, deletes, or displays logical device
assignments.
A logical device assignment associates a user-chosen
name (a logical device name) with a physical device, a pseudo device,
or another logical device. When you assign a logical device .name to a
pseudo device or to another logical device, the system equates your
assignment to the equivalent physical device.
When you assign logical device names, you use the same syntax that you
use for physical device names.
That is, a logical device name
consists of a 2-character alphabetic ASCII name, an optional unit
number one or two digits· long, and a mandatory colon (:). The two
characters in the logical device name can be equivalent to a standard
RSX-IIM/M-PLUS physical device name (~or example, DK:), or they can be
two letters picked at random (for example, HI:).
.
When you install a task or the system processes an ASSIGN LUN
directive, the system searches for a specified device by scanning the
logical device name table first and then scanning the physical device
name table. As a result, you can assign logical device names that are
identical to physical device names even though the logical and
physical device names do not refer to the same physical device •. This
is because the system equates a specified device name to the first
matching table entry that it finds. Therefore; if a logical device
name is identical to a physical device name, the logical device name
has precedence.
c
or to a
On
RSX-IIM operating systems and
extended logical name
assignments: local ass
nts.
•
RSX-IIM-PLUS operating
there are three
c
Local assignments are assignments that you assign or delete
for
any
terminal on which you are logged in.
.Local
~ssignments apply only to tasks that are
initiated from the
terminal that is used to make the assignments. Also, local
assignments last only as long as the login session in which
they are made.
That is, the system automatically deletes a
session's local assignments when you log out. If you want to
c
3-20
MeR COMMANDS
(
ASN (Cont.)
make the same local assignment whenever you log in, you can
enter the assignment in your login command file.
Both
privileged and nonprivileged users can assign or delete local
assignments.
•
Login assignments may be made automatically by the system each
time you log in.
An example of a login assignment is the
logical name SY:, which the system assigns to your default
device each time you log in (if the device you log in to is
different than the default system device). The system keeps
track of login assignments by account, so you can use login
assignments regardless of which terminal you use to log in.
However,
the login assignments for an account apply only to
tasks that are initiated from that account.
Also,
only
privileged users can assign and delete login assignments.
•
Global assignments apply to all tasks running in the system.
Only privileged users can assign or delete global assignments.
(.-----
,~-
c
c
The order in which the system uses logical assignments is:
task,
local,
login, group,
and global. For example, if you make a local
assignment using a logical device name that is already used in a login
assignment, the system uses the the local assignment. When you delete'
the local assignment, the system reverts to using the login assignment
(you delete assignments by entering ASN = ).
3-21
MCR COMMANDS
c
ASN (Cont.)
c
(
3-22
MCR COMMANDS
(
ASN (Cont.)
c
c
3-23
MCR COMMANDS
(
ASN (Cont.)
c
c
3-24
MCR C.OMMANDS
(
ASN (Cont.)
Formats:
The ASSIGN command has three types of formats.. Following is a brief
list of these formats, and a description of the terms used in the
formats. Then each format is described in greater detail,
including
descriptions of optional keywords, and examples.
ASN eenn:=ll [nn] : [/keyword(s)]
!Makes logical assignments
ASN =[ll[nn]:] [/keyword]
!De1etes logical assignments
ASN [jkeyword]
!Disp1ays logical assignments
The terms
meanings:
shown
in
the
ASN
command
formats
have. the
following
ee
The equivalence name (the name or specification to which you
assigning a logical name)
c
are
11 :
The logical name
nn
The optional 1- or 2-digit unit number
ttnn:
The terminal device name and number
=gnn
A User Identification Code' (UIC) group number
Format descriptions:
ASN eenn:=ll [nn] : [/keyword(s)]
c
Makes a local logical assignment for the terminal from which it
is entered.
However, when entered with keywords, this command
can make login, group, or global assignments; or it can make
3-25
MCR COMMANDS
c
ASN (Cont.)
login assignments for other terminals.
Both nonprivileged and
privileged users can make local logical assignments, but only
privileged users can make other types of assignments.
If both the equivalence name and the logical name are terminated
by colons, the equivalence name will be translated iteratively
until it is resolved to its final equivalent physical device.
Keywords:
/TERM=ttnn:
Makes a logical assignment for
ttnn: •
the
terminal
specified
by
/LOGIN
(Privileged keyword). Makes a login logical assignment for
the terminal from which it is entered unless another
terminal is specified.
~-
(
/GBL or /SYSTEM
(Privileged keyword.) Makes a global
(system-wide)
logical
assignment.
A global assignment is entered into the
system-level ,translation table and it applies to all tasks
running in the system.
Examples:
)ASN DB2:=JK:ffi)
Assigns the logical device name JK:
to device DB2:.
This is a local assignment for the issuing terminal
during the current login session.
3-26
c
MCR COMMANDS
(
ASN (Cont.)
)ASN
DB3:=JS:/LbGIN/TERM=TT12:~
Assigns the logical device name J S : t o device DB3:.
This is a login assignment for terminal TT12:. Only
privileged users can make login asstgnments.
)ASN DB2: =JK: /GBL
c
~
Assigns the logical device name JK:
to device DB2:.
This is a global assignment for all system users and
all tasks running in the system. Only privileged users
can make global assignments.
)ASN DB=JK: ~
ASN -- Invalid logical name
If you specify a colon at the end of a logical name,
you must also include a colon in the equivalence
string.
ASN =[ll[nn]:] l/keyword]
Deletes all local logical assignments for the terminal from which
it is entered
(when entered without parameters). When entered
with a specific logical assignment, deletes that
specific
assignment.
When entered with keywords, deletes all of the
logical assignments of the specified type.
Nonprivileged users
can only delete local logical assignments for their own terminal,
but privileged users can delete other types of assignments, or
assignments for other terminals.
c
Note that when you delete logical assignments with the ASN
command, the command deletes assignments made by the DFL command
as well.
3-27,
MCR COMMANDS
c
ASN (Cont.)
Keywords:
/TERM=ttnn:
(Privileged keyword.) Deletes all of the local logical
assignments of the specified terminal or deletes a specific
logical assignment if one is specified.
/LOGIN
(Privileged keyword.) Deletes a specific login logical
assignment when one is specified. When /LOGIN is specified
without 11nn: or ttnn:
(ASN =/LOGIN), deletes all login
logical assignments for the terminal from which the command
is entered.
/GBL or /SYSTEM
(Privileged
. assignments,
specified.
keyword.)
Deletes
all
global
or a specific global assignment
logical
if one is
c
Examples:
>ASN = (!®
Deletes all local logical assignments for the
from which it i,s entered.
terminal
>ASN =JK:(!®
c
Deletes the local logical device name JK:.
>ASN =JS:/LOGIN/TERM=TT12:(!®
Deletes the login logical device name JS: for terminal
TT12:.
Only
privileged
users can delete login
assignments.
>ASN =JK: /GBL (!®
Deletes the global logical assignment JK:.
Only
privileged users can delete global logical assignments.
3-28
c
MCR COMMANDS
(
ASN (Cont.)
>ASN =/GBL 001
Deletes all global logical assignments.
ASN [/keyword]
Displays the local and login logical assignments for the terminal
from which it is entered (when entered without a keyword). When
entered with a keyword, displays other types
of
logical
assignments.
Nonprivileged
users can display the logical
assignments of their terminal, their group, and the system by
entering the /ALL keyword (ASN /ALL). Privileged users can also
display the logical assignments of other terminals (by using the
/TERM keyword) •. When there are no logical assignments of the
specified type, the system returns the CLI prompt instead of a
display.
Keywords:
/ALL
Displays all of the local, login, and group
logical
assignments of the terminal from which it is entered, and
"Ill system logical assignments.
/TERM=ttnn:
c
c
(Privileged keyword.) Displays all of the local
logical assignments of the specified terminal.
and
login
/GBL or /SYSTEM
(Privileged keyword.)
assignments.
Displays
all
system-level
logical
Examples:
>ASN 001 .
JK
DB2:
JS
DB3:
Local TI - TT12:
Login TI - TT12:
Displays all of the local and login logical assignments
for the terminal from which· it is entered. Note that
the assignments are displayed with the logical name
first and the equivalence name second, whereas when you
make logical assignments, you specify the equivalence
name first.
If the terminal does not have any local or
logical assignments, the command line prompt (»
is
returned without a display.
3-29
MCR COMMANDS
c
ASN (Cont.)
>ASN
SY
JK
JS
/ALL ffi)
DRS:
Global
DB2:
Local TI - TT12:
DB3:
Login TI - TT12:
Displays all of the global logical assignments in the
system,
and all of the group, local, and login
assignments for the terminal from which, it is entered.
Command Error Messages:
~
ASN -- Device not in system
You;specified a device in the command line that is not a
valid device, or that is not. presently on line. Check the
device name and then try entering your command again.
When
you enter your command, be sure to specify the device name
first and the logical name second.
ASN -- Device not terminal
You specified an invalid terminal
keyword.
Check the name of the
command again.
name with the /TERM
terminal and try your
(
ASN -- Privileged command
You tried to make a privileged logical assignment from
nonprivileged terminal. The assignment was not made.
a
ASN -- Syntax error
You entered a command with incorrect syntax.
syntax for your command and try it again.
Check
the
ASN -- Terminal not logged in
You specified a terminal that is not presently logged in
the system.
3-30
to
..
MCR COMMANDS
ATL
(
3.8
ACTIVE TASK LIST (NP)
The ACTIVE TASK LIST (ATL) command displays the name and status of all
active tasks in the system or the status of a particular task. The
display provides information useful for determining the exact status
of each active task. The display contains the following information
for each task:
c
•
Task name
•
Task control block physicaJ address (octal)
•
Partition name
•
Partition control block physical address (octal)
•
Partition base and limit physical addresses (octal)
•
Task's running priority and default priority
•
Task status flags
•
TI: terminal physical device-unit
•
Nonbuffered and buffered I/O counts (decimal)
•
Task local event flags
•
Task registers
tasks only)
and
Processor
Status
Word
(memory-resident
The displayed task status flags are from the Task Control Block
(TCB)
or the Partition Control Block (PCB). The ATL command displays the
name of the bit if the bit is set to 1 at the time of the display.
Bits set to 0 a~e not displayed. Flag names are three characters long
and correspond to the last three characters of the mnemonic defining
the status bits.
For example, AST represents the bit T2.AST and
indicates that ;the task is processing an Asynchronous System Trap.
Names prefixed by a minus sign (-) indicate that the bit represents
the complement of the condition. For example, -CHK indicates that the
task cannot be checkpointed.
If the task is not in memory (the OUT flag is displayed), the contents
of the PC (Program Counter), the PSW (Processor Status Word), and the
registers are not displayed.
c
3-31
MCR COMMANDS
ATL (Cont.)
(
The following list provides a brief description of
flag:
Status
ABO
ACP
AST
'ELK
CAF
each
task
status
Description
Task is being aborted.
Task is an Ancillary Control Processor (ACP).
Task is processing an AST.
Task is blocked by a command line interpreter
command.
Task cannot be checkpointed due to checkpoint
allocation failure.
Checkpoint space is allocated in task image.
Task cannot be check inted.
(CLI)
space
(
(
-PMD
OUT
(
3-32
MCR COMMANDS
ATL (Cont.)
Status
RDN
REM
REX
ROV
RST
RUN
SEF
Task I/O is being run down.
Task is to be removed on exit.
Task has abort AST effected or in progress.
Task has resident overlays.
Task is restricted (used by layered software).
(RSX-llM-PLUS multiprocessor systems only.) Task
executing on another processor.
Task is stopped for an event flag(s).
is
s reser
(SPM-ll) •
Task is being suspended.
Task was suspended prior to AST.
Task is stopped for terminal input.
Task was stopped prior to AST.
Task is iti a "wait-for" state.
Task was in a "wait-forfl state
(;-
c
Description
Format:
ATL [taskname]
Example:
c
>ATL mJ
LDR ••• 112050 LDRPAR 112404 00253100-00255600Pri - 248. Dpri - 248.
Status: -CHK FXD STP -PMD PRY NSD
TI - COO:
laC - O. BIO - O. Ef1g - 000001 000000 PS - 170000
PC - 120354 Regs 0-6 120212 010364 177777 107646 074714 107614 120166
RMDEMO 053550 GEN
046020 01036700-01065600 Pri - 225. Dpri - 225.
Status: -CHK WFR -PMD PRY MCR
TI - TTO:
laC - fro BIO - O. Ef1g - 000021 040000 PS - 170010
PC - 125234 Regs 0-6 000000 136257 132066 000000 136321 134560 121166
F11ACP 111550 GEN
067150 01164600-01230600 Pri - 149. Dpri - 149.
Status: STP ACP -PMD PRY NSD CAL
TI - COO:
laC - O. BIO - O. Ef1g - 000002 000001 PS - 170000
PC - 135244 Regs 0-6 000010 000066 000016 000000 067420 111550 120244
MCR ••• 110160 SYSPAR 114514 00202600-00212600 Pri - 160. Dpri - 160.
Status: STP -PMD PRY MCR CLI NSD CAL
TI - TT51:
laC - O. BIO - O. Eflg ~ 000001 040000 PS - 170000
PC - 122436 Regs 0-6 000000 120476 122032 120432010554 043552 120366
3-33
MCR COMMANDS
BlK
3.9
c
BLOCK (NP ,P)
The BLOCK command blocks an installed task.
It declares to the system
that the specified task is not eligible to execute or to compete for
memory. On multiuser protection .ystems, nonprivileged users can only
block active tasks requested from the issuing terminal.
Privileged
users can block any task.
On systems without multiuser protection,
any user can block any task.
However, the following tasks cannot be blocked:
ACP tasks, CLI tasks,
tasks that are being aborted, and tasks that are exiting.
Blocking a task sets the block bit in the Task Control Block
(TCB).
When a task's block bit is set, the task is ineligible to compete for
system resources.
To clear the block bit,
issue the MCR UNBLOCK
command or,
if the task is active, abort the task.
(Unblocking or
aborting a task are the only ways to cancel the BLOCK command.)
A blocked task has an effective priority of zero.
If the task can be
checkpointed, any task can checkpoint it. Once checkpointed, the
blocked task is no longer eligible to compete for space in memory.
A
blocked task that is subsequently aborted is automatically unblocked
by the system.
If the task had previously specified a requested exit
AST, the task is unblocked and the AST is declared for it.
Format:
BLK [taskname] [/TERM=ttnn:]
taskname
The name of the task to be blocked.
If taskname is not
specified,
the command attempts to block the task requested from
the issuing terminal (task TTnn).
(
Examples:
>BLK TST OOJ
Blocks task TSTT36, prohibiting it from further execution.
TT36:
is the terminal from which the task was initiated.
3-34
MCR COMMANDS
BOO
(
3.10
BOOT (P)
The BOOT command bootstraps a system that exists as a task image file
on a Files-ll volume.
It provides a convenient means of terminating
one system and initiating another, especially on mlnlmum hardware
configurations.
For example, BOOT can be used to terminate a
real-time system and initiate a program development system.
The BOOT command
operation.
immediately
terminates
the
system
currently
Bootable systems, such as RSX-IIM and RSX-llS, are special task
files that have no task headers.
in
image
Format:
BOO [T]
[filespec]
filespec
The standard RSX-IIM/M-PLUS file specification in the form:
dev:[ufd]filename.typeiver
This specifies the file from which a new system is to be loaded.
c
(
Defaults applied to the file specification are:
dev:
The system device LB:
[ufd]
The directory under which BOOT is running
filename
RSXllM
type
SYS
version
The latest version
Note that BOOT is the only command
specification to omit the file name.
that
Table 3-1 lists all of the valid bootable devices
operating systems.
allows
for
the
RSX-IIM/M-PLUS
Table 3-1
Valid Bootable Devices
RSX-llM
l
RL01/02
RK05
RK06/07
RM02/03/05/80
RA60
RA80/81
RC25
MLll
RSX-llM-PLUS
RP02/03
RP04/05/06
RS03/04
RX01/02
RX50
RD51
DEC tape
RL01/02
RK05
RK06/07
RM02/03/05/80
RA60
RA80/81
RD 52/53
3-35
file
RC25
RP02/03
RP04/05/06
RX50
MLll
MCR COMMANDS
BOO (Cont.)
Restrictions:
For an. unsaved system boot, the boot device physical unit number
(unit plug) must equal the logical unit number (LUN) in the
unsaved system. Otherwise, the initial SAVE command line will
not work.
It is not possible to correctly boot a
under the following circumstances:
large
unsaved
Executive
1.
When booting a mapped RSX-11M or RSX-11M-PLUS
system from an unmapped RSX-llM system.
operating
2.
When booting a 22-bit RSX-11M or RSX-11M-PLUS operating
system from an 18-bit RSX-11M operating system.
c
(
If the Executive Debugging Tool (XDT) has beeri generated into the
system, XDT displays the following when an RSX-llM/M-PLUS operating
system is booted for the first time:
XDT: baselevel
XDT>
where baselevel is the base level number for the system.
Pressing the G key in response to the prompt returns control to
and causes the system to come up normally. After the
system has been saved, XDT does not reappear unless a user sets a
breakpoint or issues the BRK command, or the system crashes.
(See the
RSX-11M/M-PLUS and Micro/RSX Debugging Reference Manual
for
a
description of XDT.)
RSX-11M/M~PLUS
3-36
c
MCR COMMANDS
(
BOO (Cont.)
Example:
)BOO TEST
OOJ
Bootstraps from the system device the
the file TEST.SYS.
system
contained
in
Command Error Messages:
BOO -- Device not in system
The booting system does not contain
needed for the device being booted.
the
data
structures
BOO -- Device offline
An attempt was made to boot a file on an off-line device.
BOO
DPB error
This
A bad Directive Parameter Block was created by BOOT.
If the
error indicates that the system itself has faulted.
error persists, submit a Software Performance Report (SPR)
to DIGITAL.
c
BOO -- File not contiguous
An attempt was made to load a system from
file. System images must be contiguous.
a
noncontiguous
BOO -- Invalid load device
BOOT detected a
residence device.
device
.that
was
invalid
as
a
system
the
system
BOO -- Label block read error
c
An attempt was made to read the label block
image file, but the attempt failed.
of
BOO -- Not a system image
BOOT did not consider the file to be a system image
probably because the file is formatted improperly.
file,
BOO -- No transfer address
BOOT did not consider the file to be a system imag~ file
because the specified transfer address in the label block
appears to be corrupted.
c
3-37
MeR COMMANDS
c
BRK
3.11
BREAKPOINT TO EXECUTIVE DEBUGGING TOOL (P)
The BREAKPOINT TO EXECUTIVE DEBUGGING TOOL
(BRK) command passes
control to the Executive Debugging Tool
(XDT)
if XDT has been
generated into the system. If XDT is not in the system, the command
has no effect.
(See the RSX-llM/M-PLUS and Micro/RSX Debugging
Reference Manual for a description of XDT.)
I-f--successful, the BRK
command halts all system activity.
Proceeding from a breakpoint
normally restores the system to the state that existed when the BRK
command was issued.
When XDT gains control, it prints the following message on the console
terminal:
BE: nnnnnn
XDT>
This message confirms that XDT has control.
All XDT commands are
available for use in debugging the Executive or user-written drivers.
To return control to MCR, enter the P command; MCR then prompts with a
right-angle bracket (».
c
Format:
BRK
Example:
>BRK OOJ
BE: 124560
XDT>P
(
>
Command Error Message:
3-38
MCR COMMANDS
BRO
(
3.12
BROADCAST (NP,P)
The BROADCAST command displays a specified
terminals, as follows:
message
at
one
or
more
•
A privileged user can display a message at all te/rminals
connected to the system or, in a multiuser protection system,
at all logged-in terminals.
•
Both privileged and nonprivileged users can display a
at anyone terminal.
message
You can also create an indirect command file to contain o~e or more
lines of input to the command.
Each line specifies the target
terminal and the message to be broadcast.
(Privileged users can
broadcast a message simultaneously to all terminals.)
To use the
command file, enter the command name followed by an at sign
(@)
and
the command file specification.
If the message cannot be broadcast within 20 seconds,
displays the following message at the issuing terminal:
the
system
BRO -- Message failed to reach ttnn:
If a privileged user specifies multiple terminals (ALL:
or LOG:), the
system returns one error message for each busy terminal.
(
If you have used SET /NOBROadcast so that you will not receive any
messages sent by the BRO command, the user .sending the message will
receive an error message.
Formats:
BRO[ADCAST]
ttnn: message
BRO[ADCAST] @filespec
c
BRO[ADCAST] ALL:message (Privileged format)
BRO[ADCAST] LOG:message (Privileged format)
NOTE
Each format can be entered on two successive lines by
pressing the RETURN key immediately after the command
name;
this invokes the direct task format.
For
example:
>BRO @'l
BRO>ttnn:message
To exit from the direct task format, press CTRL/Z.
3-39
MCR COMMANDS
(
BRO (Cont.)
ttnn:
The terminal to receive the broadcast message.
message
The message to be broadcast. This is an ASCII character string
that cannot exceed the length of one line (80 characters). Note
that an exclamation mark (I) cannot be broadcast.
Usually, BRO uses uppercase letters when it displays. the message.
When you use the direct task format, however, BRO displays the
message exactly as you typed it.
filespec
The specification of a file containing one or more message
in the format:
lines
ttnn: message
user-name message
or, for privileged users:
ALL:message
c
LOG:message
ALL:
Privileged option. Indicates that the message is to be sent to
all terminals connected to the system (this does not include
slave terminals, virtual terminals, or terminals that have the
broadcast option disabled) •
LOG:
Privileged option. Indicates that the message is to be sent to
all logged-in terminals (this does not include slave terminals,
virtual terminals, or terminals that have the broadcast option
disabled) •
In
a system that does not support multiuser
protection, LOG: defaults to ALL:.
c
c'
3-40
MCR COMMANDS
BRO (Cont.)
The BRO command displays the message in one of the following formats:
RSX-IIM systems and RSX-IlM ... PLUS systems without Resource Accounting
dd:month:yr hh:mm
message
to ttnn:
From node::ttnn:
The variable node is the name that was selected for your system during
system generation.
It is also your DECnet node name if your system is
on the network.
Examples:
RSX-IIM systems and RSX-IIM-PLUS systems without Resource Accounting
)BRO TT5l: PRIVILEGED TESTING.
PENDING CRASH. ~
displays
c
lO-AUG-85 13:35
From QUACK::TT52:
PRIVILEGED TESTING. PENDING CRASH.
>BRO ~
BRO)TT5l: More testing.
to TT5l:
Crash likely. (Bill
displays
lO-AUG-85 13:37
From QUACK::TT52:
More testing. Crash likely.
c
to TT5l:
)BRO LOG:System going down in 5 minutes for reboot. ~.
displays
lO-AUG-85 13:40
From.QUACK::TT52:
SYSTEM GOING DOWN IN 5 MINUTES FOR REBOOT.
c
3-41
to TT5l:
MCR COMMANDS
c
BRO (Cont.)
Note:
The BROADCAST command uses the write-breakthrough feature of the
terminal driver, a system generation option always generated with
an RSX-IIM multiuser protection system and all RSX-IIM-PLUS
operating systems.
If the system supports the feature, under
most circumstances the broadcast message will reach all targeted
terminals. I f the system does not support the wr i te-br,eakthrough
feature, the write defaults to a write logical block; the message
cannot break through any type of 1/0 at the terminal.
Command Error Messages:
BRO -- Command input error
The BROADCAST iask did not receive the
(Usually an indirect command file could
Reenter the command line.
command line.
not be found.)
BRO -- Command syntax error
c
The command line had an improper format.
BRO -- Illegal device specified
The specified device was not a terminal.
BRO -- Message failed to reach ttnn:
The message could not be displayed within 20 seconds at
terminal specified by ttnn:.
the
BRO -- Privileged command
(
A nonprivileged uSer entered a privileged option of the
command,
that is, attempted to broadcast one message to all
connected or logged-in terminals.
BRO -- User not receiving messages
The terminal to
SET INOBROadcast.
which
the
3-42
message
was
sent
has
been
MCR COMMANDS
BYE
(
3.l3
BYE (NP)
The BYE command logs you out of a multiuser protection system.
The
system writes a logout message on the console terminal (CO:), displays
a terminating message on the initiating terminal, aborts any active
nonprivileged and some privileged tasks that belong to you, dismounts
volumes mounted by you (unless you are a privileged user and you have
mounted a public device, because mounted public volumes remain
mounted), and deallocates any private devices you had previously
allocated.
When it logs a terminal out, the BYE command follows this procedure:
1.
Checks
to
see if the terminal's current command
line
(CLI) has requested a silent logout.
If it has,
BYE does not display any information and does not execute the
system logout command file.
interpr~~er
(-
=
c
2.
If silent logout is not requested, resets the default CLI for
the terminal to MCR,
resets the terminal so that it can
receive
broadcast
messages,
and
executes
LB: [1,2]SYSLOGOUT.CMD, the system logout command file.
3.
Informs the full-duplex terminal driver or DECnet that the
terminal is logging out.
BYE issues a Queue Input/Output
(QIO) directive that the terminal driver uses to hang up
remote lines or that DECnet uses to break the connection.
This action can be controlled by the /[NO]HOLD keyword.
If
you specify /HOLD~ BYE logs out the terminal but the line is
not hung up.
If you specify /NOHOLD, BYE logs out the
terminal and the line is hung up.
The default is /NOHOLD.
(
The way in which BYE aborts (or does not abort) a task active on the
terminal being logged out depends on the task and its privilege
status.
All tasks with abort ASTs and all nonprivileged tasks that are active
at your terminal when you issue the BYE command are aborted.
If a
nonprivileged task has requested an exit AST service routine by means
of a SPECIFY REQUESTED EXIT AST (SREA$ or SREX$) directive, BYE allows
the task to enter this service routine. BYE requests each of these
tasks to exit
(abort), causing the requested exit AST to be entered
for the task. For all of these nonprivileged tasks, BYE allows a
user-specified time interval during which the AST can be executed for
the task. This time interval is specified when the BYE task is built.
The default interval is zero, which means that BYE does not wait at
all if another value for the time interval has not been specified. At
the end of the time interval, if the task has not exited or if the AST
service routine has not been entered, BYE aborts the task normally
(a
second requested exit AST cannot be declared for a nonprivileged
task). BYE also aborts any other nonprivileged tasks that are still
active.
3-43
MCR COMMANDS
c
BYE (Cont.)
BYE aborts a privileged task that has requested an AST service routine
in the same way as a nonprivileged task. However, any privileged
tasks that have not exited by the end of the time interval are not
necessarily aborted.
The task itself must determine if it will be
aborted or not. Privileged tasks that did not request the AST service
routine remain active.
Format:
BYE [/[-] [NO]HOLD]
Example:
>BYE (Bg)
Have a Good Evening
13-May-85 18:47 TT13: is logged off QUACK
Depending on the time of day, the system displays "Have a Good
Morning," "Have a Good Afternoon," or "Have a Good Evening."
(
Note that some tasks, including BYE, spawn or request other tasks.
These other tasks ar.e also included in the task totaL For example,
when you issue a RUN-immediately command, the Resource Accounting
system records three tasks: the MCR task to execute the RUN command,
INSTALL to install the task, and the actual execution of the task.
Command Error Message:
BYE
-- Syntax error
A keyword other than a form of /HOLD
(/HO[LD] ,/NOHO[LD],
/-HO[LD]) was specified in the command line.
3-44
(
MCR COMMANDS
c
CAN
3.14
CANCEL (NP,P)
The CANCEL command cancels time-based initiation requests for a task.
These
requests
result
from a RUN$ directive or any of the
time-synchronized variations of the MCR RUN command and are placed in
the clock queue.
(Note that you must be privileged to use these forms
of the RUN command.)
Only a privileged user can issue a CANCEL
initiated from the entering terminal.
command
for
a
task
not
CANCEL does not affect execution of a currently active task.
CANCEL
removes only the time-based schedule requests still in the clock
queue.
e-
Format:
CAN [CEL] taskname
where taskname is the name of the taSk.
Example:
)CAN XKE
c
~
Cancels all periodic rescheduling and time-based
requests for task XKE.
c
3-45
initiation
MCR COMMANDS
c
(
3-46
MCR COMMANDS
(
c
c
3-47
MCR COMMANDS
ell
3.16
(I
COMMAND LINE INTERPRETER (P,NP)
The COMMAND LINE INTERPRETER (CLI) command allows the use of a command
line interpreter other than MCR, such as DCL or a user-written CLI. A
CLI task receives unsolicited input from a terminal and then att
inter ret the i
t as a command.
All of the eLI command keywords and subkeywords can
three characters.
be
truncated
to
Formats:
CLI /keyword[=cliname]
CLI/INI[T]=cliname[/subkeyword(s)]
cliname
The name of the alternate CLI.
six characters long.
This name can be between one
and
c
Keywords:
/DISABLE=cliname
Disables the specified CLI.
The CLI cannot accept any
commands.
This effectively stops system use by terminals
set to this CLI until the CLI is enabled again. The system
sends a message to the CLI informing it that it has been
disabled i f the CLI was initialized with the /MESSAGE
subkeyword specified.
(
/ELIM=cliname or /ELIM=*
Removes all of .the data structures for the specified CLI or,
if the wildcard (*) is used, for all of the alternate CLls.
After this command is executed, the CLI task can be removed
(see the description of the REMOVE command).
Individual CLls can be eliminated only if no terminals are
set to them.
When you use the wildcard option, all CLls
except MCR are eliminated. Any terminals set to a non-MCR
CLI are disabled.
The terminals can be enabled again by
setting them to any valid CLI
(after
it
has
been
initialized)
or
to MCR (which does not need to be
initialized). CLls that were initialized with the /MESSAGE
subkeyword receive a message from the system informing them
that they have been eliminated.
/ELIM=* is intended to be used during
procedure.
3-48
the
system
shutdown
MCR COMMANDS
Cli (Cont.)
(
/ENABLE=cliname
Enables a previously disabled CLI. The CLI can now accept
commands.
If the CLI was initialized with the /MESSAGE
subkeyword specified, the system sends a message to the CLI
informing it that it is now enabled.
While a CLI is disabled, the terminal remains set to it. To
set the terminal to an enabled CLI, issue the SET /CLI
command from another terminal (privileged users only).
/INIT=cliname[/subkeyword(s)]
Ini tializes. the data structures for the specified CLI so
that terminals can be set to it. The CLI task must have
been installed with the /CLI=YES option.
All CLls except
MCR must be initialized before they can be used.
If the /MESSAGE subkeyword is specified, the system sends a
message to the CLI, informing the CLI that it has been
initialized.
Subkeywords:
/CPR=l s tring"
c
Specifies the CTRL/C prompt string.
The string
inside the quotation marks has the same syntax as
the MACRO-II .ASCII directive (see the PDP-II
MACRO-II Language Reference Manual).
You must
supply characters such as RETURN «15»
and LINE
FEED
«12»
because
they are not supplied
automatically. For example:
/CPR=I<15><12>/MCR>/"
c
sets up the string for MCR's CTRL/C prompt.
This
means that when you press CTRL/C, the system
issues a RETURN/LINE FEED and then displays the
prompt MCR).
The string can be between 0 and 31 characters
long.
A null string, that is, a string with zero
characters (/CPR="II) , specifies th,at no prompt will
be issued.'
If you want to use double quotation marks or
slashes
within
the
string,
use
different
characters as the
string
delimiters.
(The
delimiters can be any character that is not used
in the string.)
The default is /CPR;:I<15><12>/cli>" where
the name of the CLI •.
cli
is
/CTRLC
Specifies that the CLI is requesting
CTRL/C
notification .packets. These packets are only sent
if the terminal has the CTRLC terminal attribute
.set.
3-49
MCR COMMANDS
Cli (Cont.)
(
/DISABLE
Initializes the CLI iri disabled modew The system
rejects any commands issued from the terminal
until the CLI is enabled.
By default, the CLI is enabled.
/DPR="string"
Specifies the default. prompt to be issued when an
empty command line is entered. As with /CPR, the
st~ing inside the double quotation marks
has the
same syntax as the MACRO~ll .ASCII directive. You
must supply characters such as RETURN «15»
and
LINE FEED «12»
because they are not supplied
automatically.
The string can be between 0 and 31 characters
long.
A null string (/DPR="") specifies that no
prompt should be issued.
If you want to use double quotation mar~s or
slashes
within
the
string,
use
different
characters as the
str ing
delitni ters.
(The
delimiters can be any character that is not used
in the string.)
The default is /DPR="<15><12>/>/".
c
/LGO
Specifies that the CLI will accept commands from
terminals that are not logged in. This allows the
CLI to execute the commands without the user
having
to log in.
An application can, for
example, use the terminal for data entry only and
not .allow it access to the system. The terminal
is under complete control of the CLI task.
You
can only do what the CLI allows.
c
It is up to the CLI to do any user validation or
security checks. Also, be careful when doing any
file I/O from tasks running on a terminal that is
riot logged in, because the UIC and privileges for
the terminal are undefined.
By default, commands from terminals that are not
logged in will be rejected by the system and will
not be passed to the CLI.
/MESSAGE
Specifies that the CLI wants to receive messages
from the system. The system messages inform the
CLI of events such as its being enabled or
(
3-50
MCR COMMANDS
(
Cli (Cont.)
disabled, or if a terminal is being set to the CLI
or if. it is being dissociated from the CLI.
(See
the RSX-IIM/M-PLUS System Management Guide for a
list of the messages and their format.)
By default, the CLI does not receive messages from
the system.
/NULL
Specifies that the CLI will accept empty command
buffers resulting from a user pressing the RETURN
key as the first character in a command line.
No
prompt is issued.
By default, the command is not passed to
and the default prompt is issued.
the
CLI
/PRIV
Specifies that a user must be privileged to set
the terminal to the CLI.
(See the description of
the SET command.)
By default, a nonprivileged user can
her own terminal to the CLI.
c
set
his
or
/PROMPT
Specifies that the CLI wants to receive prompt
requests if a task that was started in order to
execute a command exits.
By default, the dispatcher issues a prompt and the
request is not passed to the CLI.
/QUIET
c
Specifies that the MCR commands HELLO and BYE do
silent logins and logouts, respectively.
(See the
descriptions of these commands.) The keyword also
suppresses messages from the dispatcher.
/RESTRICT
Specifies that only the CLI can issue the SCLI$
directive to set a terminal to itself.
(See the
RSX-IIM/M-PLUS and Micro/RSX Executive Reference
Manual. )
Note that you cannot use /RESTRICT for
whose names are in the form ••• xxx.
.
3-51
CLI
tasks
MCR COMMANDS
c
Cli (Cont.)
/TASK=taskname
Specifies the name of the task that will act as
the CLI. Use this keyword if the name of the task
is different from the name of the CLI.
/MESSAGE=cliname:"message-text"
Sends an ASCII message to the CLI if it has the message
attribute set for it (by the /MESSAGE subkeyword).
If the
CLI does not have the attribute set, the command issues an
error message.
/SHOW
(Nonprivileged keyword.) Displays i~formation about all CLls
on the system.
The information includes the name of the
CLI, the task that implements the CLI, the number of
terminals set to the CLI, several status bits for the CLI,
and whether the CLI is active.
The following list gives the meaning of the status bits:
ACT
CLI is active (always shown for MCR).
DSB
CLI is currently disabled.
PRV
CLI was initialized with the /PRIV
You must be privileged to set
(including TI:) to this CLI.
RST
CLI was
initialized
with
the
/RESTRICT
subkeyword. Only the CLI can set a terminal to
itself •
subkeyword.
a terminal
(I
/UNOVR
Clears the override bit set for the terminal's CLI.
When
the
HELLO
command
enters
the
command
file
.LB: [1,2] SYSLOGIN .CMO, the terminal is set to a specific CLI.
However, an override bit is also set so that the command
file can execute from MCR.
Clearing the override bit
ensures that commands issued from the terminal will go to
the correct CLI.
/UNOVR is useful ohly with SYSLOGIN.CMD, immediately
ch~ining to a user's LOGIN~CMD, or exiting.
c
before
Examples:
>CLI /sHow.OOl
MCR
MCR •••
DCL
••• DCL
9
0
ACT
Displays information-about the CLls currently
the system.
installed
in
CI
3-52
MCR COMMANDS
c
Cli (Cont.)
>CLI /INI=TCP/LGO/MES/TASK=PROMPT ®ill
Initializes the task PROMPT as a CLI.
The command line
specifies that the CLI will be called TCP, it will accept
commands from unlogged-in terminals, and it will receive
messages from. the system.
(Note that PROMPT must first be
ibstalled with the /CLI=YES option before it can
be
initialized as a CLI.)
Command Error Messages:
CLI -- CLI already exists
You attempted to initialize a CLI that already exists in the
system.
E-
CLI
-~
CLI does not accept messages
The CLI was not initialized with the /MESSAGE keyword, so
its message attribute bit has not been set. The CLI is
unable to receive any messages.
CLI -- CLI in use
You attempted to eliminate a CLI that
set to it.
(
still
has
terminals
CLI -- Device attached
The CLI command cannot do a /SHOW
task has attached the terminal.
display
because
another
CLI -- Feature not supported
The system does not support alternate CLls.
CLI -- Illegal keyword value
c
You specified. an
subkeyword.
invalid
string
with
the
/CPR
or
/DPR
CLI -- Illegal use of restrict switch
A CLI cannot be initialized with /RESTRICT if
the CLI task is in the form ••• xxx.
the
name
of
CLI -- Invalid keyword
An incorrect keyword was specified in the command line.
CLI -- Max number of CLls already present
You attempted to initialize another CLI, but the maximum
number of CLls allowed in the system has already been
reached.
(,
3-53
MCR-COMMANDS
Cli (Cont.)
CLI -- No pool space
Not enough space in pool is present
specified in the command line.
to
do
the
operation
CLI -- Output error
An I/O error occurred while output was
terminal. .
being
sent
to
the
CLI -- Partition too small to buffer information
The /SHOW subkeyworddid not have enough space to buffer the
display information.
Try reinstalling the MCR task with a
larger increment, using the
/INC
keyword
(see
the
description of the INSTALL command).
If the error persists,
submit a Software Performance Report (SPR).
CLI -:.. Pr i v ileged command
Nonprivileged users can only use the /SHOW keyword.
CLI -- Syntax error
The command line was not entered correctly.
CLI -- Task not a CLI
You attempted to initialize a CLI
installed with the /CLI=YES keyword.
task
that
was
not
(
CLI -- Task not in system
The specified CLI task has not been installed, or you
attempted to eliminate a CLI whose name is unknown to the
system.
c
3-54
MCR COMMANDS
CLQ
3.17
CLOCK QUEUE (NP)
The CLOCK QUEUE
(CLQ)
command displays on the entering terminal
information about tasks curr.ently in the clock queue. The informat.ion
consists of the task names, the next time each task is to be. run, ,and
each task's reschedule interval,
if one was specified. The system
places. a task in the clock queue if the task was activated by the RUN
command,
which specified a time-based option, or by the RUN$
directive.
Format:
,CLQ [UEUEl
Example:
>CLQ ffi'J
TASKI Scheduled at 22-NOV-85 10:24:30:00
TASK2 Scheduled at 22-NOV-85 10:30:00:00 Reschedule interval 30M
>
The first task in the queu~ will run at 10:24:30:00
(hour:
minute:
second: clock tick); it has no~ been rescheduled.
The second task in the queue will next run at 10:3n:00:00
and is scheduled to run every 30 minutes. "
c
(
3-55
MCR COMMANDS
Del
3.18
c
DIGITAL COMMAND LANGUAGE (NP)
The DIGITAL COMMAND LANGUAGE (DCL) command allows you to issue
commands from a terminal that is set to MCR.
I.ns·tead of
processing the command line, DCL processes it. The DCL task must
installed before it can do command processing. See the RSX-IlM or
RSX-lIM-PLUS Command Language Manual for descriptions of the
commands.
DCL
MCR
be
the
DCL
Format:
DCL command-line
Examples:
>DCL SET DEF LB:
~
Issues the DCL command that sets the default device for
entering terminal to be LB:
(the system device) •
>DCL TYPE [303,24]USERS.TXT
the
~
Issues the DCL command that displays a file on the entering
terminal.
The file is USERS.TXT, which is in directory
[303,24] •
c
(
3-56
MCR COMMANDS
DEA
(
3.19
DEALLOCATE (NP,P)
The DEALLOCATE command releases a private (allocated) device,
thereby
allowing other users to access
it.
(This command applies only to
systems that support multiuser protection.)
Nonprivileged users can
only deallocate private devices that they themselves have allocated.
A privileged user can deallocate any device in the system.
Note that when an owner of a private device logs out (issues the BYE
command),
the system deal locates all of that user's private devices.
However, if the system detects an error while attempting to deallocate
a device,
it stops and does not deallocate that device or any
remaining devices.
The related error message does not state which
device caused the error.
If an allocated device has been mounted, it must be dismounted
you deallocate the device.
before
Format:
DEA[LLOCATE]
[ddnn:]
ddnn:
The device unit name and number of the private device to be
deallocated.
If the command line does not specify a.device unit,
the system deal locates all private devices owned by the user
logged in on the issuing terminal.
Example:
)DEA DM: ·lBfll
Deallocates disk DM:.
The deallocated
mounted or allocated by other users.
(
3-57
device
can
now
be
MCR COMMANDS
c
c
c
3-.58
MCR COMMANDS
c
L-
c
c
l
3-59
MCR COMMANDS
DEV
3.21
(
DEVICES (NP,P)
The DEVICES command displays the symbolic names of all devices or all
of a particular device type or the name of a specific device.
The
device names appear in one column; second and subsequent columns
contain additional information about each device.
Formats:
DEV [ICES]
DEV[ICES] dd:
DEV [ICES] ddnn:
DEV[ICES] /LOG
dd:
The type of devices for which you want the information to
displayed.
This parameter-must be a physical device name.
be
ddnn:
The specific device for which you want the information to be
displayed.
This parameter may be either .a physical or a logical
device name.
/LOG
Displays all logged-in terminals.
c
(
Examples:
3-60
MCR COMMANDS
DEV (Cont.)
(
c
(
3-61
MCR COMMANDS
DEV (Cont.)
.Notes:
The following notes describe the information that can
example displays.
appear
in
the
•
MOUNTED indicates that the device is mounted.
If a privileged
user issues the command, the display includes the volume
label.
•
PUBLIC indicates that the device has been set public.
•
NOWRITE indicates that the volume is software write-locked
(write operations are not allowed on the volume).
•
TYPE indicates the device type.
•
MARKED FOR DISMOUNT indicates that a mountable device has been
requested to be dismounted, but the dismount operation has not
yet been completed.
\
•
OFFLINE indicates that, although the system tables contain
entrie~
for this device,
the host configura~ion does not
contain the related device, or the device was powered down at
the time of the boot.
•
[uic] LOGGED ON indicates that the user identified
(the protection UIC) has logged in on the terminal.
by
•
LOADED indicates that a loadable device
loaded.
is
currently
•
UNLOADED indicates that a 16adable device driver is
not loaded.
currently
•
A device name in the second column is the device. to which the
corresponding device in the first column has been redirected.
•
A terminal name in the second column followed by the text
"- PRIVATE" indicates that the device named in the first
column has been allocated to the user logged in on the
terminal in the second column.
•
The lines in the display for a specific' terminal .list the
characteristics that have been set for the terminal.
The
description of the SET command gives all of the available
characteristics.
driver
(I
[uic]
c
(
3-62
MeR COMMANDS
c
(
3-63
MCR COMMANDS
c
c
c
3-64
MeR COMMANDS
(
cc
(-
c
3-65
MCR COMMANDS
c
c
c
3-66
MCR COMMANDS
c
E-
c
c
3-67
MCR COMMANDS
c
c
(
3-68·
MCR COMMANDS
(
(
(
3-69
MCR COMMANDS
DMO
3.23
DISMOUNT (NP ,P)
The DISMOUNT command requests the file system to mark a volume for
dismount and release its control bl.ocks.
Marking a volume for
dismount prevents programs from opening additional files on the
volume.
After all files open on the volume are closed, the Ancillary
Control Processor (ACP) releases the control blocks and dismounts the
volume.
Ifa single user has mounted a volume, the DISMOUNT command declares
the volume logically off line.
If multiple users have mounted a
volume, the volume remains accessible until all users have dismounted
it .•
When you dismount a volume, the DISMOUNT command prints on your
terminal a message about whether or not a final dismount has been
initiated. When the dismount operation completes, either through the
Files-ll
disk
system or the ANSI magnetic tape system (ANSI
X3.27-1978), the command prints the following message on the console
terminal (CO:):
***
dismount complete
NOTE
Do not remove the volume until after you have received
this message.
If you remove the volume before you
have received this message, the volume might be
corrupted and the next volume placed on the device
drive will probably become corrupted too.
c
There may be a considerable delay between the time you issue the
command and the printing of this message if a number of 1/0 requests
are pending or a number of files are open on the volume.
mounted.
c
The Files-II volume label may be up to 12 characters in length
for disk and DECtape, and up to 6 characters for magnetic tape.
It is used to verify that the proper volume is being dismounted.
A volume label is optional
(if the command omits a label, no
volume label check is performed).
c
Nonprivileged users can only dismount volumes that they have
A privileged user can dismount any mounted volume.
Formats:
DMO ddnn:
[["]label["]]
[lkeyword(s)]
DMO IUSER [/keyword(s)]
ddnn:
The device unit that holds the volume to be dismounted.
label
3-70
MCR COMMANDS
c
DMO (Cont.)
contains
If a volume label for a magnetic tape
characters, it must be enclosed in quotation marks.
description of the MOUNT command for the list of
characters.
special
See the
special
Keywords:
/DEV
(Privileged keyword.)
Dismounts all users from a
device.
This
keyword must be specified if
dismounting a public device.
specific
you are
/USER
Dismounts all volumes that a user has mounted.
/TERM=ttnn:
(Privileged keyword.)
Dismounts all volumes that a user
the specified terminal has mounted.
at
/LOCK=option
(
Allows logical I/O to a volume after it is dismounted.
If
the drive supports software spin-down, you can also specify
whether or not the disk should be left spinning after the
dismount. For magnetic tapes, /LOCK can be used to dismount
and remount a tape without having to reload the tape.
The options for the /LOCK keyword are:
/LOCK=Nounload
/LOCK=Unload
/LOCK=Virtual
When you specify the Nounload option (/LOCK=N), DISMOUNT
clears the volume valid bit and does not spin down the disk
or unload the tape. This option only inhibits access to the
volume.
This option is the default lock value for volumes
mounted as foreign and with no ACP specified.
(See the
description of the MOUNT command.)
When you specify the Unload option
(/LOCK=U)
for disks,
DISMOUNT clears the volume valid bit and, if the drive
supports the spin-down function, spins down the disk.
When
you specify /LOCK=U for tapes, DISMOUNT rewinds and unloads
the tape. Depending on the hardware, this may only place
the unit off line at load point or it may completely unload
the tape and close the autoload tape ring.
The /LOCK=U
option is the default lock value for all volumes mounted
with a standard ACP. The usual procedure after dismounting
a volume that uses a standard ACP is to remove the volume
from the drive.
3-71
MCR COMMANDS
c
DMO (Cont.)
The Virtual option is privileged. When you specify /LOCK=V,
DISMOUNT does not clear the volume valid bit and does not
spin down thedi~k or unload the tape. The Executive still
permits logical I/O to the volume. For example, the task
image of an insta1led task can re$ide on a disk that has
been dismounted with the /LOCK=V option. However, the file
system cannot access the volume. This option is the default
when dismounting the system disk pribr to saving the system.
Examples:
>DMO DMI:AMBER ®ill
Dismounts the volume labeled AMBER on device unit DMI:.
If
a single user has mounted the volume, the command dismounts
the volume. If more than one user has mounted the volume,
the. volume remains mounted for the other users.
>DMO DMl:/DEV ®ill
c
Places the volume on device unit DMl: logically off line and
releases all control blocks. Users. can no longer access the
device.
>DMO /USER/TERM=TT17: ®ill
Dismounts all volumes mounted by terminal TT17:.
>DMO DMO: mTIl
DMO -- TT60:
dismounted from DMO:
***
Final dismount initiated
***
Begins the dismounting process for DMO:. When the "dismount
complete" message is printed on the console terminal, the
volume can be removed from the drive.
Command Error Messages:
DMO -- Warning -- Tasks installed from
The disk being dismounted has tasks installed from it.
DMO
dismounts the disk, but you can still run the tasks until
the disk has spun down. Use the TAS command to find out
which tasks are installed.
3-72
c'
MCR COMMANDS
c
DMO (Cont.)
DMO -- Checkpoint file still active
The command attempted to dismount a volume that contained an
active checkpoint file.
The" volume cannot be dismounted
until the checkpoint file has been discontinued.
Issue an
ACS command to discontinue the file and reissue the DMO
command when the system issues a message to indicate that
the checkpoint file is inactive.
DMO -- Dismounting system disk
c
This message should only occur during a system generation or
during system shutdown. Since the system disk is a public
device, it can be dismounted only by a privileged user.
DMO -- Dismount is not necessary for cassettes
Self-explanatory.
This is an informational message only.
is attached by task
DMO attempted to dismount an attached device.
Because DMO
processes the mount list several times before exiting, a
device could be dismounted if the task to which it belongs
detaches before DMO exits.
If the device is dismounted, a
normal dismount message appears later.
DMO -- No volume list
The command specified a magnetic tape for
volume label list does not exist.
c
3-73
which
a
mounted
MCR COMMANDS
c
DMO (Cont.)
Too many devices attached, no further attach messages
DMO issues this message when eight
(or more) devices are
attached during a DMO IUSER operation.
The message is
issued only when the eighth device is attached;
it_ is not
subsequently issued again if more devices are attached.
DMO -- Volume not mounted
The specified device was not mounted.
DMO -- Volume not mounted by TI:
The command specified a dismount operation for a volume that
was not mounted from the issuing terminal or the command
specified the wrong device name for a tape set.
~-
DMO -- Wrong volume label
The volum~ label and the label specified in the command
not match.
did
c
c
3-74
MCR COMMANDS
FIX
c
3.24
FIX-IN-MEMORY (P)
The FIX command loads and locks a task into its partition. Subsequent
requests for running the task are serviced more quickly because the
task is resident in memory and does not have to be loaded from the
disk before it can run. The system can fix a task in memory only when
the partition in which it is to be fixed becomes available.
Fixed tasks remain physically in memory even after they exit.
Therefore, they do not have to be reloaded when a request is made to
run them.
(Note that reexecuting fixed tasks is not always practical;
to reexecute, the task must initialize all impure data and LUN
assignments at run time.) Only an UNFIX or REMOVE command can free the
occupied memory partition.
The following restrictions apply to the fixing of tasks:
c
•
Active tasks cannot be fixed.
•
A task must be instailed before it can be fixed.
Format:
FIX taskname[/keyword]
c
The variable taskname is the name of the task to be fixed in
memory.
c
3-75
MCR COMMANDS
c
FIX (Cont.)
Examples:
>FIX XKE
Fixes task XKE in its partition.
Command Error Messages:
~..
FIX -- Partition busy
The partition in which the task was to
occupied, so the task could not be fixed.
be
fixed
was
FIX -- Task active
The specified task is already active.
be fixed.
Active
tasks
cannot
c
FIX -- Task already fixed
The specified task was
al~eady
fixed in memory.
FIX -- Task being fixed
The specified task was already being
f~xed.
(
FIX -- Task has no read only segment
An attempt was made to fix the read-only segment of a
multiuser task, but the spcified task does not have a
read-only segment.
FIX -- Task not in system
The specified task has not been installed in the system.
uninstalled task cannot be fixed.
3-76
An
MeR COMMANDS
FLA
(
3.25
GROUP GLOBAL EVENT FLAGS (NP,P)
The GROUP GLOBAL EVENT FLAGS (FLA)
command creates, eliminates, or
displays group global event flags. Group global event flags provide
each Ule group with 32 event flags in addition to the 32 common and 32
local event flags. Group global event flags are similar in use to the
common event flags (see the RSX-llM/M-PLUS and Micro/RSX Executive
Reference Manual).
However, only those tasks running under the same
group Ule can use the group global event flags for that group.
Nonprivileged users can only create or eliminate group global event
flags for their login group Ule.
Privileged users can create or
eliminate group global event flags for any group.
Format:
>FLA[GS]
[[ggg]/keyword]
[ggg]
Represents the group for which the group global event flags
to be created. The default group is the login UIC group.
are
Keywords:
/CRE
Creates group global event flags for
group.
If the flags already exist
delete, the delete flag is cleared.
(i
the
but
specified UIC
are marked for
/ELIM
Eliminates group global event flags for the specified UIC
group.
Event flags are not eliminated until the access
count reaches zero. If the access courtt is greater than
zero, the flags are marked for delete.
(
When you omit the group number and keyword specification, the
displays all the group global event flags in the form:
ggg
access count
event flags
I
command
[DEL]
where [DEL] indicates group global event flags marked for delete.
Examples:
>FLA 303/CRE !Bill
Creates group global event flags for all tasks running under
the UIC group number 303. All flags are initialized to zero
when created.
>E'LA !Bill
303
1
000010 000000
Displays the access count (1) and event flags set (in this
case, flag 68) for the UIC group 303. The access count is
the number of tasks using the event flags.
3-77
MCR COMMANDS
c
FLA (Cont.)
The group global event flags are represented by two octal
words.
The first word contains event flags 65 through 80
(from right to left) and the second word contains event
flags 81 through 96 (from right to left).
>FLA 303/ELIM ®ill
Eliminates group global event flags for DIC group 303.
Command Error Message:
FLA --
Ill~gal
function
The /CRE keyword was specified, but the event flags already
existed
(even though they may have been marked for delete),
or the /ELIM keyword was specified, but the. event flags were
already eliminated or marked for delete.
(
(
3-78
MCR COMMANDS
(
HEULOG
3.26
HELLO OR LOGIN (NP)
The HELLO and LOGIN commands log you in on a terminal to gain access
to a multiuser protection system.
Before you log in, the system
rejects all-MCR commands except HELLO, LOGIN, and HELP.
Parameters to
the HELLO command are a last name or User Identification Code (UIC)
and a password.
The system validates these parameters according to
entries in an account file.
If the name or UIC and password match an entry in
the system performs the following procedure:
c
the
account
file,
1.
Checks to see if the terminal's current command
line
interpreter
(CLI)
has requested a silent login.
(Silent
logins are available only on
systems
with
multi-CLI
support.)
If so, HELLO does not display the login text file
or the user's login command file, does not execute the system
login command file, and does not set the default CLI for the
terminal.
2.
Assigns
system
already
the one
3.
Establishes the user's login directory, which is the
default directory.
4.
Records the current time and date and other information about
the terminal session in the system file.
the login logical device name SYO:
to the user's
disk unless the user's logical system device is
the same as physical device SY:.
(The system disk is
that contains the user's files.)
initial
5.
c
6.
Displays a system identification, the current date, and the
time the user logged in on the terminal.
However, if the CLI
requests silent login, the information is not displayed.
7.
If the system supports alternate CLls, sets the terminal's
default CLI to be the one specified in the user's account
file.
8.
Displays the contents of
the
file
LB: [1,2]LOGIN.TXT.
However, if the CLI requests a silent login, LOGIN.TXT is not
displayed.
9.
Executes the system command file LB: [1,2]SYSLOGIN.CMD (if it
exists)
unless the CLI requests a silent login. Before the
file is invoked, HELLO instructs the system to override the
user's default CLI and use MCR to process the file.
(This
allows SYSLOGIN.CMD to use MCR commands.)
SYSLOGIN.CMD is
invoked with the terminal privileged and slaved.
3-79
MCR COMMANDS
c
HEL/LOG (Cont.)
HELLO passes the following information to SYSLOGIN.CMD:
Default system device
Login UIC
Last name
First initial
If terminal is to be privileged
If terminal is to be slaved
(xxn: )
([g,m] )
(P or NP)'
(S or NS)
If SYSLOGIN.CMD exists, it must do the following:
•
Check the appropriate parameter to see if the
terminal should be privileged or nonprivileged and
set the terminal accordingly, then
check
the
appropriate parameter to see if the terminal should
be slaved or nonslaved and set
the
terminal
accordingly.
NOTE
It is important to
set
a
terminal's
privilege status before its slave status.
Otherwise, a nonprivileged user could become
privileged.
•
c
If your system has multi-CLI support, issue the CLI
/UNOVR command to instruct the system to use the
user's CLI.
The CLI would be MCR, DCL, or a
user-written CLI.
If a default CLI is not specified in the account
file,
the terminal is set to MCR.
If the specified
CLI is not present in the system, HELLO issues an
error message and the user cannot log in.
The following code is an example of a system
(using the Indirect Command Processor):
.SLAV:
.,
o;CLEAR
.,
.OVER:
c
comma~dfile
.ENABLE SUBSTITUTION
.ENABLE QUIET
.IF P5 = "P" .GOTO SLAV
SET /NOPRIV=TI:
.IF P6 = "s" .GOTO OVER
SET /NOSLAVE=TI:
OVERRIDE BIT
CLI /UNOVR
.DISABLE QUIET
.SETS FILE Pl+P2+"LOGIN.CMD"
.TESTFILE 'FILE'
.IF HEL
•
>HEL
Account Or name:
Password:
•
>HEL
Password:
that
the
user
Ipassword
uic
user name
password
uic
username
password
uic
c
Your User Identification Code (Ule).
following four Ule representations:
The
command
allows
the
g,m
[g ,m]
glm
[g/m]
To suppress part of the display of the file
slash form (that is, glm or [g/m]).
LOGIN.TXT,
The variables g and m are octal numbers from 1
represent group and member numbers,respectively.
to
use
377
the
that
username
Your last name, which can be entered in place of a Ule.
password
c
An alphanumeric password. If you type the password in response
to the prompt "Password:," the system does not display (echo) the
typed characters.
3-81
MCR COMMANDS
c
HEL/LOG (Cont.)
If the HELLO command was successful, the system displays the following
message:
system i.d.
dd-mm-yy hh:mm Logged on Terminal ttnn:
xxxnnnn
as
greeting
[login-text]
system i.d.
One of the following, depending on the system:
RSX-llM BLnn
[g,m] System
RSX-llM-PLUS V3.0 BLnn
nodename
[g,m] System
~!
nod-ename
dd-mm-yy
The current date.
hh:mm
The time the user logged in.
c
greeting
One of the following, depending on the time of day:
Good Morning
Good Afternoon
Good Evening
(
login-text
The contents of LOGIN.TXT (or BATCH. TXT) •
the contents of the file as follows:
The
system
displays
•
If you use the slash form when specifying the UIC the first
time you log in, the display concludes at the first percent
sign (%) in the file. Subsequent logins on any one day (using
the slash form) do not display the contents of the text file
unless the file has been edited.
(The percent sign is used to
separate new messages from old ones.)
•
If you do not use the slash form, the system displays the
entire file.
(Note that you can press CTRL/O to end the
display after the first percent sign.)
If the login text file does not exist, the following
displayed:
Message file error -26
3-82
message
is
MCR COMMANDS
(
HEL/LOG (Cont.)
Examples:
(
c
c
3-83
MCR COMMANDS
HEL/LOG (Cont.)
(
Command Error Messages:
c
Note that if you use the LOGIN command to log in instead of HELLO, the
error messages are preceded by LOG.
HEL -- Account file open failure
The account file was open for another user or the disk
containing the account file was not mounted. Reenter the
command l i ne •
HEL -- Assign failure
HELLO could not assign your system device.
3-84
MCR COMMANDS
c
HEL/LOG (Cont.)
HEL -- Cannot find physical LB:
HELLO could not open the file because LB: was not assigned.
HEL. -- Cannot set eLI
command
line
(Multi-eLI operating systems only.) The
interpreter
(eLI)
is installed in the system, but HELLO
failed to set the terminal to the eLI.
HEL -- eLI not in system
(Multi-eLI operating systems only.) You could not log in
because the default eLI specified for you in the account
file is not installed in the system.
HEL -- Invalid account
The name or Ule specified in the command is not stored in
the account file or the password specified does not match
the name or Ule given.
HEL -- Logins are disabled
c
The system was in the process of shutting down or the
command SET /NOLOGON has been issued. You cannot log in at
these times.
HEL -- Low pool - nonprivileged log ins disabled
To save space in pool, the
nonprivileged users to log in.
system
will
not
allow
HEL -- Message file error
c
The system could not open the file LOGIN.TXT for a reason
indicated by the Fes code nnn. See the RSX-IIM/M-PLUS and
Micro/RSX I/O Operations Reference Manual for a definition
of the Fes code.
HEL -- Other user logged on
Another user was currently logged in on the
issuing
terminal.
Only one user at a time can be logged. in on a
terminal.
3-85
MCR COMMANDS
HEL/LOG (Cont.)
HEL -- Spawn failure
The SPAWN Executive directive failed to assign your system
device or the RPOI Executive directive failed to chain to
Indirect to execute the login command file.
HEL -- Syntax error
The format of the command line for HELLO was incorrect.
HEL -- Terminal allocated to other user
The issuing terminal was already allocated to another user.
You cannot log in on a terminal allocated to someone else.
HEL -- Timeout on response
You did not respond to the HELLO prompt before the timeout
count elapsed.
(The timeout count is specified when the
HELLO task is built.)
HEL -- Warning
**
Default device not in system
Your default system device is not in the system, so HELLO
did not make the assignment. However, you are still logged
in.
c
3-86
MCR COMMANDS
HELP
(
3.27
HELP (NP)
The HELP command displays the contents of the general help file for
your system.
The default help file is LB: [1,2]MCR.HLP. HELP is the
only MCR command that you can issue without logging in.
The display
usually contains information on how to log in on the terminal, but
each installation can change the contents of its help file to suit
spec if i c needs.
Formats:
HELP % [jOUT:filespec]
HELP [jkeyword]
[qualifierl]
[qualifierl]
[qualifier2]
[qualifier2]
[ ••• qualifier9]
[ ••• qualifier9]
%
Displays the text contained in [current-uic]HELP.HLP.
be logged in to request HELP %.
You
must
qualifierl ••• qualifier9
The subject on which
displayed.
you
would
like
help
information
to
be
Keywords (all mutually exclusive):
c
/CLI :cliname
Directs HELP to the help file for a command line interpreter
(CLI) in LB: [1,2]cliname.HLPIo
If you are in your own CLI and omit the keyword, the default
help file is LB: [1,2]MCR.HLP.
/DCL
Specifies that the help
text
begins
in
the
file
LB:[1,2]DCL.HLP.
This is the default for terminals set to
DCL.
c
/FIL: [filespec]
Specifies any file where help text is located.
If you do
not give a complete file specification, the defaults are
LB: [1,2]filename.HLP.
If you only use /FIL:,
the default
help file is LB: [1,2]MCR.HLP.
/GRO
Instructs HELP to use
[group,l]HELP.HLP on the default
volume as the root help file.
Group help files allow users
with the same group number to share common help files for
that group.
/LOC
Displays the text contained in
directory on the default volume.
to the HELP % command.
3-87
HELP. HLP in the default
This keyword is equivalent
MCR COMMANDS
('
HELP (Cont.)
IMCR
Spec i f i es tha t
the help
text
begins
in
the
file
LB: [1,2]MCR.HLP.
This is the default for terminals set to
MCR.
IOUT:filespec
Saves the text of the help file (or files) in the specified
file.
If you do not use the lOUT keyword, HELP displays the
files on your terminal.
Ixxx
Specifies that the help
text
begins
in
the
file
LB:[1,2]xxx.HLP, where xxx is the name of a CLI. This
keyword produces the same results as specifying ICLI:xxx.
~I
The format of a HELP. HLP file is:
I
FIRST-QUALIFIER-I
Text
that
will
FIRST-QUALIFIER-I.
be
displayed
if
you
type
HELP
2
FIRST-QUALIFIER-2
Text that will be displayed if you type HELP FIRST-QUALIFIER-I
FIRST-QUALIFIER-2.
2
SECOND-QUALIFIER-2
Text that will be displayed if you type HELP FIRST-QUALIFIER-I
SECOND-QUALIFIER-2.
I
SECOND-QUALIFIER-I
Text
that
will
SECOND-QUALIFIER-I.
be
displayed
if
you
type
c
HELP
\\
The numerals are level numbers from I to 9. Level numbers must be the
first character of the line they are on, and the qualifiers that
follow must be uppercase. Arbitrary strings of blanks or tabs are
allowed between level numbers and qualifiers.
If a qualifier begins
with a dollar sign ($) or a slash (I), the $or I is ignored.
HELP interprets its command line in a strictly nested fashion.
When
seaiching for qualifiers in a help file, HELP begins by looking for a
line containing level number 1, followed by the first qualifier
specified in the comm.and line. If successful and no other qualifiers
were specified, the subsequent help text is displayed. Otheiwise, the
search continues for a line containing level number 2, followed by the
second qualifier specified in the command line. Again,
if no other
qualifiers were specified, the subsequent help text is displayed.
This correspondence of qualifier position in the HELP command line
with level numbers in the help file continues until the last qualifier
is found.
•
3-88
c
MCR COMMANDS
(
HELP (Cont.)
HELP permits references within the help file to other files that
contain large blocks of text or additional ,level numbers and their
qualifiers.
Indirect references to other files decreases search time
and also allows more flexible use of the help file. To reference
another file from within the help file, specify an at sign (@) as the
first nonblank character on a line followed by a file specification.
For example:
@filespec
The variable filespec is any legal RSX-llM/M-PLUS file specification.
The default file type is .HLP. However, if a file type other than
.HLP is specified, HELP uses the specified file type as the default in
succeeding
indirect
references.
For example, if you specify
@filename.TXT, HELP uses .TXT as the default file type in future
indirect references.
The file version number always defaults to the
highest existing version.
The file referenced in this manner has the same format as the help
file.
Note that if the indirect file contains level numbers, the
level numbers must be greater than the level number in the help file
that precedes the call to the indirect file. For example, if the help
file contains the following lines, HELPEXAMPLE.HLP can only contain
level numbers greater than 1:
1 EXAMPLE
c
@HELPEXAMPLE
HELP also allows you to share text between two or more similar or
synonymous qualifiers in the help file. To do this, specify a pound
sign (#) followed by the similar qualifier as the firstnonblank
character on a line. For example, to relate the qualifiers LOGIN and
HELLO, the help file would contain the following lines:
1 LOGIN
#HELLO
c
1 HELLO
See Ben Jones for an account and password.
Note that the qualifier that contains the displayed text must be of
the same level number as all the qualifiers that refer to it. Also,
since HELP searches the help file sequentially, the qualifier must
appear after all those that refer to it.
Along with one-word synonyms, you can also use string
example:
1 UTILITIES
2 RUNNING
= TASKS EXECUTING
1 TASKS
2 EXECUTING
Always begin the string synonym with qualifier 1.
c
3-89
synonyms.
For
MCR COMMANDS
(I
HELP (Cont.)
Example:
The following is an example of a help file:
The seneral form of the HELP command is:
HELP [Qualifier1] [Qualifier2J [ ••• rnuslifier9J
This
displa~s
text from the swstem help file.
The other seneral form of the HELP command is:
HELP % [Qualifier1] [Qualifiar2J [ ••• mualifier9J
This displa~s information from B user's own help file.
not lesal until ~ou are losSed in.
1 LOGIN
:tHELLO
1 SPELLING
Type HELP SPELLING DICTIONARY followed bw
want to spell.
the
word
~DU
2 DICTIONARY
The file DICTIONARY.HLP [not included in this example]
contains an abrid.ed listins of freouentlw misspelled
words.
@DICTIONARY
1 HELLO
c
See Ben Jones for an account and password.
1 CREATE
NOTE
When crestins a help filer the first line
be blank since it is not displayed •
should
c
. By convention, each line .hould b •• in with a blank or tab; the lines
cannot besin with the disits 1 to 9 since these wDuld be interpreted
as level nUmbel's, Also, dependinS Uf"lHI thf:~ t.~If'~~S elf d(:'~vices in !:I(JU1'
configuration, some practical restrictions should be imposed. For
example, to accom'ffiodiilte VT05BfH l:i.nes of te>:t should rl()'\'. eHc~~ed 72
characters IonS and a block of text should no~ exceed 20 lines.
If
there are level n+1 Qualifiers, the~ should be mentioned in the text
so that they are known to exist. Siffiilarl~? level 1 ~ualifiers should
be added to the text displayed when onl~ HELP is tw~ed.
(
3-90
MCR COMMANDS
HELP (Cont.)
I f a system contained this help file,
display in response to HELP L:
>HELP L
you
would
get
the
following
~
See Ben Jones for an account and password.
>
The qualifier HELLO is the synonym defined for LOGIN
(L), so HELP
(Note that a
displays the text following HELLO for both qualifiers.
qualifier may be specified by the fewest initial characters that
unambiguously define it.)
Command Error Messages:
HEL -- Ambiguous HELP qualifier
The qualifier does not specify a unique part of the help
file.
Further characters must be supplied. Examine the
command line that HELP displayed below the error message and
specify the last qualifier displayed more completely.
HEL -- Ambiguous HELP synonym
c
The qualifier referenced as a synonym was not unique.
HEL -- Cannot initialize file storage region correctly
The HELP text could not be buffered adequately.
command line.
Reenter the
HEL -- Cannot open output file
c
The output file specified with the /OUT:filespec keyword
cannot be created.
This message can occur for several
reasons. For example, the device may be write-locked or you
do
not have the necessary access privileges for the
specified directory.
HEL -- Excessively nested or recursive synonyms
A string synonym used in the help
defined recursively.
file
has
probably
been
HEL -- HELP file error
The help file could not be opened for the reason specified
by the FCS code nnn.
If the code number is -26, the help
file does not exist. See the RSX-llM/M-PLUS and Micro/RSX
I/O Operations Reference Manual for definitions of the error
codes.
HEL -- HELP synonym not found
The help file referenced a synonym, but
include it.
3-91
the
file
did
not
MCR COMMANDS
(,
HELP (Cont.)
HEL -- Illegal switch - not logged in
You attempted to reference a local or group help file or
output help text to another file without being logged in.
Log in on the system and then enter the HELP command line.
HEL -- Improper HELP file format
The help file is not in proper format and cannot be
Either edit the file or reenter it in proper format.
used.
HEL -- Indirect HELP file open error
HELP attempted to ref~rence another file from within
help file, but could not open the indirect file.
the
HEL -- Indirect HELP file syntax error
HELP encountered a syntax error either in a
another file or in the indirect file itself.
reference
to
HEL -- Switch syntax error
/
You specified a keyword incorreptly.
line.
/
Reenter
the
command
HEL -- Unknown HELP qualifier
The help file does not contain the last qualifier
in the command line below the error message.
displayed
c
c
3-92
MCR COMMANDS
HOM
(
3.28
HOME (NP,P)
The HOME command allows you to modify certain fields in the home block
of a Files-II disk volume. After you make the changes, HOME performs
extensive checks to ensure that a good home block is written back onto
the volume.
If any of these checks fail, HOME attempts to place an
alternate home block on the first free block on the home block search
path.
If this is completed successfully, HOME issues a warning
message about the new home block. However, you should copy the volume
as soon as possible, because the alternate home block could be
destroyed while the volume is mounted.
To use the HOME command, you must first install the INI task with
task name ••• HOM as follows:
the
>INS $INI/TASK= ••• HOM ®ill
The difference between INI and HOME is that INI writes the home block
of a volume whereas HOME changes the information in the home block
(without changing anything else). Because the HOME command and the
INI command are implemented within the same task, they share many of
the same error messages. See the description of the INI command for
explanations of these common messages.
c
Also, you should be aware that you cannot use the HOME command on
RSX-IIM Version 3.2 operating systems (or earlier versions), or on
RSX-IIM-PLUS Version 1.0 operating systems, and get the desired
results.
Format:
HOM[E] ddnn:volume-label/keyword(s)
ddnn:
The volume whose home block you want to modify.
c
volume-label
The current label for the volume.
/keyword(s)
The specifications for the fields you want to modify in the home
block.
Each keyword defaults to the value specified for the
particular field when the volume was initialized.
The keywords
do not change the files created by the INI command.
Keywords:
c
/DENS=density
Checks the density of a diskette. If specified, the drive
density
is
compared
against
the keyword value for
consistency. Acceptable values are: HIGH and LOW.
3-93
MCR COMMANDS
c-
HOM (Cont.)
/EXT=block-count
Specifies the default file-extend size.
A file must be
extended when it has used all of its allocated space. Legal
values for block-count range from l to 255 (decimal) •
Note that if you specify /EXT=O, no files
(including the
system files)
can be extended. Therefore, although there
may be free space on the disk volume, unless there are also
free file headers, new files cannot be created on the
volume.
(If there are no free headers and the index fi le
cannot be extended, no new files can be created.)
/FPRO=[system,owner,group,world]
Specifies the default protection for the files on the
volume.
The system recognizes four classes of users for
file protection purposes. The position of the user classes
in the protection code string is fixed in this order:
[SYSTEM, OWNER, GROUP, WORLD]. The location in the string
defines which user class you are specifying.
Also, the system recognizes four types of access
file protection purposes:
R
W
E
D
-
codes
for
Read access
Write access
Extend access
Delete access
C.·
In each instance, the absence of a code means that the
class is denied that type of access.
The square brackets around the protection code are
syntax.
user
required
If you want to specify the default protection for a user
class, enter an asterisk (*) instead of access codes in that
class's place in the string.
/LRU=directory-count
Specifies the approximate number of directories that will be
accessed simultaneously.
The Files-ll Ancillary Control
Processor (FllACP) maintains a list of the most recently
used directories. The value that you specify for /LRU sets
the number of entries in this list.
In general, directory
operations can be speeded up significantly by increasing the
number of entries.
If a directory appears in the list, no disk I/O is required
for finding the directory in the Master File Directory
(MFD).
In addition, directory operations do not require the
directory file header to be read.
If you do not use /LRU,
the default for directory-count is the value specified when
the volume was initialized.
3-94
(
MCR COMMANDS
HOM (Cont.)
Legal values for
directory-count
range
from
1
to
l27(decimal).
Note that increasing the value for /LRU
increases the number of File Control Blocks (FCBs) used, and
may increase the amount of system pool used. See the
appropriate system generation manual for more information.
Also note that if you specify /LRU=O, the FllACP will not
keep a list of directories. This is not recommended and
could have an adverse effect on system efficiency.
/MXF=file-count
Specifies the maximum number of files allowed on the volume.
This number corresponds to the number of file headers in the
volume's index file. The value for /MXF includes the five
system files and cannot be greater than the total number of
bits allocated to the index file bitmap. Use the following
algorithm to determine the maximum number of files allowed
on your volume:
maximum = (4096.)
c
* (current-number-of-index-file-bitmap-blocks)
The number of index file bitmap blocks depends on the
maximum number of files currently allowed on the volume.
Use the /VI keyword to obtain this number and read the
description of the /INF keyword for the INI command to
determine how many index file bitmap blocks are on the
volume.
Note that you also cannot reduce the maximum number of files
already specified for the volume.
/NAME=new-volume-label
Specifies a new label for the volume.
c
/OVR (P)
Instructs the HOME command to override label processing so
that a volume can be modified without specifying a volume
label.
/OWNER=[group,member]
Specifies the owner of the volume. Legal group and member
numbers range from 1 to 377(octal). The square brackets are
required syntax. This keyword is identical to the /UIe
keyword.
3-95
MCR COMMANDS
c
HOM (Cont.)
jPRO= [system,owner ,group,world]
Specifies the default protection for a volume. Access codes
consist of four groups of four codes in the access rights
word as follows:
R
W
C
D
-
Read access
write access
Create access
Delete access
In each instance, the absence of the code
user class is denied the access right.
means
that
the
The user classes
(system, owner,
group,
world)
are
positional. That is, the location of the word in the string
defines the user class to whom the code applies. The order
is:
[system,owner,group,world]
The square brackets are required syntax.
Substitute an asterisk (*) for the access codes to force the
default value for a specific class.
jUIC=[group,member]
Specifies the owner of the volume. Legal group and member
numbers range from 1 to 377(octal). The square brackets are
required syntax. This keyword is identical to the JOWNER
keyword. /VI
Lists the HOME keywords and their values for
volume.
3-96
the
c
specified
c
MCR COMMANDS
c
HOM (Cont.)
/WIN=retrieval-pointer-count
Specifies the number of mapping pointers to be allocated for
file windows. A file window consists of a number of mapping
pointers and is stored in memory when the file is opened.
(See
the
RSX-IIM/M-PLUS and Micro/RSX I/O Operations
Reference
Manual
for
a
description
of
mapping
pointers.)
The retrieval-pointer-count must be between 1
and 127 (decimal) •
Example:
>HOM DKO :TEST/MXF=2357 ./VI !Bill
** Volume information for DKO: **
~..
c
Label
/Cha
/Ext
/Fpro
/Lru
/Mxf
/Pro
/Uic
/Win
TEST
[]
100.
[RWED,RWED,RWED,R]
3.
2357.
[RWED,RWED,RWED,RWED]
[1,1]
= 7.
=
=
=
=
=
Maximum possible files = 4096.
The Homeblock revision count is 1, Last revised on ll-AUG-85
Volume created on ll-AUG-85 at 19:47:37
Command Error Messages:
NOTE
c
If you receive an error mes~age that is not listed
here, see the description of the INI command for an
explanation of the message.
*** ATTENTION ***
THIS VOLUME IS OPERATING WITH A REPLACEMENT HOME BLOCK
PLEASE TAKE THE ACTION OUTLINED IN THE DOCUMENTATION
HOME could not ensure that a good bome block would be written
back to the volume, so it has placed an alternate home block on
the first free block on the home block search path. The new home
block is not allocated to or mapped by any file. You should copy
the volume as soon as possible, because many operations on a
mounted volume could destroy the replacement home block.
HOM -- Failed to find home block
HOME could not locate the home block of the volume.
3-97
MCR COMMANDS
c
HOM (Cont.)
HOM -- Failed to place alternate home block
When HOME cannot ensure that a good home block will be written
back to the volume, it attempts to place an alternate home block
on the first free block of the home block search path.
This
message indicates that the attempt failed.
Note that your volume
may be cQrrupted and therefore unmountable.
HOM -- MXF less than or equal to the existing value
The value specified with /MXF was less than or equal to the
maximum number of files already specified for the volume. This
value must be .greater than the current number of files allowed.
HOM -- Switch is not legal in this mode
You attempted to use INITIALIZE
with the HOME command.
keywords
and/or
their
options
HOM -- Wrong volume label
The volume label specified in the'command line did not match
volume's current label.
the
c
3-98
MCR COMMANDS
INI
(
3.29
INITVOLUME (NP)
The INITIALIZE VOLUME command produces a Files-II volume (see Section
2.1). On disk and DECtape volumes, the command initializes the volume
(destroys all existing files), writes a dummy bootstrap and a home
block, and builds the directory structures. On magnetic tape volumes,
the command writes a volume label according to the ANSI X3.27-l978
standard and writes a dummy file that destroys all existing files.
Note that a magnetic tape volume produced by the INI command is
considered to be a null volume.
If you are going to transport a newly
initialized tape to a non-RSX-llM/llM-PLUS operating system, you might
first have to make the null volume comply fully with the ANSI
standard. To produce an ANSI-standard volume, you must write an
actual file or a null file on the tape. You can use the following
command line to do this:
PIP>ddnn:DUMMY=NL:
(Also note that the null device NL:
RSX-llM operating systems.)
c
is a system generation option
on
On multiuser protection systems, you can only initialize a volume on
allocated, private devices (that is, a device you have allocated). On
RSX-llM operating systems that do not support multiuser protection,
only privileged users can initialize a volume.
Selecting appropriate values for the command parameters requires an
in-depth knowledge of Files-II.
Refer to the RSX-llM/M-PLUS and
Micro/RSX I/O Operations Reference Manual for details' of the Files=rI
disk and ANSI magnetic tape structures.
Format:
INI [TVOLUME] ddnn: [II] volume-label [II] [jkeyword (s) ]
Note that you can use a hyphen (-) as the last character on a
line to extend the INI command line when selected keywords cause
it to exceed 80 characters (or whatever buffer size has been
specified
for the terminal).
You can use any number of
continuation lines, but the total command line cannot exceed
512 (decimal) characters.
On RSX-llM operating systems, you must first invoke INI and
begin using continuation lines when INI prompts you (INI».
then
On RSX-llM-PLUS operating systems,
you
can
begin
using
continuation lines on the same line in which you invoke INI.
ddnn:
The device unit name and number of the volume to be initialized.
l
3-99
MCR COMMANDS
(
INI (Cont.)
["] volume-label ["]
The volume label. This may be up to 12 characters in length
disk and DECtape, and up to 6 characters for magnetic tapes.
label identifies the volume and must be specified.
for
The
For magnetic tapes, the volume label is usually a reel number
that uniquely identifies the tape. The number is assigned by the
installation and, according to the ANSI standard, cannot be
duplicated within an installation.
When you specify a volume label for the magnetic tape, you can
use the uppercase letters A through Z, the digits 0 to 9, and the
following special characters:
! " % & '
(
)
* + , - • / : < = >
? ;
To use a label that contains a special character, enclose the
label in quotation marks ("label"). To use a quotation mark in a
label, you must use two quotation marks within the quoted string.
For example, the label T"l% has to be specified in the command
line as "T""l%". Any lowercase letters specified in a volume
label are converted to uppercase before any operations are
performed on the volume.
/keyword(s)
The specifications for various characteristics
volume to have upon initialization.
you
want
the
Keywords:
/ACCESS="character"
Allows the owner of a magnetic tape volume to specify the
access protection for the volume.
INI places "character" in
VOLl (the accessibility field), which is usually blank.
Legal values for "character" are the uppercase letters A
through Z, the digits 0 to 9, and the following special
characters:
! " % & '
(
)
* + , - .' / : < = >
?
The default value for "character" is a space.
Note that if any nonblank character is specified,
privileged user will be able to mount the volume.
only
a
/BAD=[option]
Indicates that bad block processing is to be included in the
volume initialization.
Consequently, bad blocks on the
volume will be marked as being currently in use and cannot
be allocated to files.
The brackets surrounding each option
The options are:
[MAN]
are
required
Accept a bad block list specified
terminal.
3-100
syntax.
from
the
(
MCR COMMANDS
INI (Cont.)
[AUTO]
Read the bad block descriptor file on the
last track of the volume created by the
manufacturer's diagnostic routines or the
Bad Block Locator Utility (BAD).
[NOAUTO]
Ignore the bad block descriptor
perform no bad block processing.
[AUTO,MAN]
Read the bad block file and, when done,
accept blocks specified from the terminal.
[OVR]
Include the last track in the BADBLK.SYS
file.
This option assumes that the bad
block file is located on the last good block
before the last track. The option is only
valid
for
devices
that
contain
manufacturer-recorded bad block data in the
last tracks (that is, DL:, DM:, and DR:
type devices) •
[OVR,MAN]
Override the
manufacturer's
bad
block
descriptor file and accept blocks specified
from the terminal.
If the command line specifies [MAN],
blocks as follows:
c
INI
file
prompts
for
and
bad
INDLBN (S) =
Bad blocks can then be entered in the format:
blocknum:number
where blocknum specifies the bad block number and number
'specifies the number of sequential bad blocks beginning at
blocknum.
c
INI requires the colon when you specify a sequence of bad
blocks.
Both blocknum and number default to decimal unless
preceded by a pound sign (#).
To specify a single block, simply enter the block number and
omit the colon.
To specify a sequence of bad blocks, separate each series of
blocks with a space, tab, or comma.
For example, the
command 1 i ne :
INI>LBN(S)=100:2,3,200:l00,45:1
enters blocks 100, 101, 3, 200 through 299, and
blocks.
c
45
as
bad
A null line (pressing the RETURN key in response to the
prompt) displays the bad blocks. The first number in the
display represents the beginning block of the sequence;
the
second number is the number of bad blocks in the sequence.
(Note that the numbers are decimal.)
To terminate bad block input, press CTRL/Z or the ESC key.
3-101
MCR COMMANDS
c
INI (Cont.)
The default option is /BAD=[AUTO].
INI obtains the bad
block information from the manufacturer-recorded bad block
descriptor file located on the last track of an RK06/07,
RLOl/02, or RM02/03/05/80 disk.
INI also searches the last
track for a bad block descriptor file created by the BAD
utility.
\
/DENS=density
Sets the bit density (bits per inch or bpi) of a magnetic
tape loaded on a TE16, TU16, TU45, TSll, TSV05, TU80, TU77,
or TU78 tape drive. Legal keyword values are as follows:
/DENS=800
/DENS=1600
/DENS=6250
/DENS=HIGH
/DENS=LOW
The default keyword values are as follows:
/DENS=6250 for TU78 volumes
/DENS=1600 for TSll/TSV05/TU80 volumes
/DENS=800 for all others.
The /DENS keyword checks the density of a diskette in an
RX02 drive or of a tape on a TSll/TSV05/TU80 drive.
If a
/DENS value is specified, the drive density is compared to
the keyword value for consistency. If a (jDENS value is not
specified, no consistency check is performed and the volume
is initialized at its current density.
c
/EXT=block-count
Specifies the number of blocks by which a file is to be
extended when the file has used all of its allotted space.
Legal values for block-count range from 1 to 255 (decimal) •
The default is /EXT=5. Note that if you specify /EXT=O~ no
files
(including
the system files)
can be extended.
Therefore, although there may be free space on the disk
volume, unless there are also free file headers, new files
cannot be created on the volume.
(If there are no free
headers and the index file cannot be extended, no new files
can be created.)
/FPRO=[system,owner,group,world]
Specifies the default protection for files created on the
volume being initialized.
Access codes consist of four
groups of four codes in the access rights word as follows:
R WE D -
Read access
Write access
Extend access
Delete access
3-102
c
MCR COMMANDS
(
INI (Cont.)
In each instance, the absence of the code
user class is denied the access right.
means
that
the
The user classes (system, owner,
group,
world)
are
positional; that is, the location of the word in the string
defines the user class to whom the code applies. The order
is as follows:
[system, owner, group, world]
The square brackets are required syntax.
\
.
~.
Substitute an asterisk (*) for the access codes to force the
default value for a specific class. '
The default file protection is /FPRO=[RWED,RWED,RWED,R] •
That is, all types of access are allowed for all user
classes except the world, which is allowed read access. only.
/INDX=index-file-position
Specifies the logical block number for the index file.
The
keyword can be used to force the index file, the Master File
Directory (MFD) , and the storage allocation file to a
specific volume location, usually to minimize access time.
Four possibilities are available:
c
BEG
- Place the index
volume.
MID
- Place the index file at the middle of the volume.
END
- Place the index file at the end of the volume.
BLK:nnn - Place the
number.
c·
index
file
file
at
the
at
The defaults are:
/INDX=MID (disk
(DECtape, DECtape II, and MLll) •
beginning
the
of
specified
devices),
the
block
/INDX=BEG
/INF=initial-index-file-size
Specifies the number of file headers to allocate initially
in the index file.
The five system files (INDEXF.SYS,
BITMAP.SYS, BADBLK.SYS, CORIMG.SYS, and OOOOOO.DIR) are not
included in the value for /INF.
The maximum number of file headers that can be allocated to
a volume is either determined by the value specified with
the /MXF keyword or is defaulted.
The default number is
based on the size of the volume (see the description of /MXF
for the calculation). The maximum number of file headers
determines if the volume will have a 1-, 2-, or 3-header
index file.
l.
3-103
MCR COMMANDS
INI (Cont.)
(
You need to determine the maximum number of file headers
allowed on the volume before you can calculate the number of
headers that will be preallocated initially. The number of
preallocated file headers is determined by either the value
you specify with /INF or a formula that uses the value you
specify with /MXF.
The following list gives the three
general formulas (one for each type of index file):
l-header index file
headers = maximum/2
headers
The initial number of preallocated
headers.
maximum
The maximum number of
with /MXF).
files
If headers is less than 100 (decimal) ,
INI
l6(decimal) file headers for your volume.
file
(specified
preallocates
,
2-header index file
headers = maximum/2 or 25593, whichever is larger
3-header index file
headers = maximum/2 or 51699, whichever is larger
See the description of the /MXF keyword for more information
on multiheader index files.
(
/LRU=directory-count
Specifies the approximate number of directories that will be
accessed simultaneously. The FllACP maintains a list of the
most recently used directories.
The value specified for
/LRU sets the number of entries in this list.
In general,
directory operations can be speeded up significantly by
increasing the number of entries.
(
If a directory appears in the list, no disk I/O is required
for finding the directory in the Master File Directory
(MFD). In addition, directory operations do not require the
directory file header to be read.
Legal values for
directory-count
range
from
0
to
l27(decimal).
Note that increasing the value for /LRU
increases the number of File Control Blocks (FCBs) used and
may increase the amount of system pool used. See the
appropriate system generation manual for more information.
Also note that if you specify /LRU=O, the F1IACP will not
keep a list of directories. This is not recommended and
could have an adverse effect on system efficiency.
The default is /LRU=3.
(
3-104
MCR COMMANDS
INI (Cont.)
/MXF=f ile-count
Specifies the maximum number of files allowed on the disk
volume.
This number corresponds to the number of file
headers in the vOlume's index file (see the description of
the /INF keyword).
The value for /MXF includes the five
system files.
In general, for a disk of size N blocks, the
theoretical
maximum number of files is calculated as
follows:
MXF = «N- « (N+4095 •. ) /4096.) +9.» *127.) /258.
If you initialize a disk with the /VI keyword, the value for
the maximum number of files is displayed along with the
other volume information (see the command examples).
If you
do not specify a maximum value, the default value is
calculated by INI using the following formula:
default MXF = (theoretical maximum MXF)/8
c
The maximum file-count value of a disk also decides if the
volume will be a Files-ll level 401 or 402 volume. Level
402 volumes will have a multiheaderindex file and allow up
to
65,500 (decimal)
files
on them.
INI creates the
multiheader index file and modifies the volume's home block
automatically if the value specified is greater 25,593.
(If
65K index file support is not specified for the INI task,
the largest value allowed for /MXF is 25,593. With 65K
support, the largest value is 65,500.)
Note that such
volumes are not backwards compatible from RSX-llM Version
4.0 or from RSX-llM-PLUS Version 2.0. INI issues a warning
message
about
the incompatibility when it creates a
structure level 402 volume.
NOTE
(
To create the Files-ll disk structure, a Files-ll
volume
requires
the
following
five
files:
INDEXF.SYS, BITMAP.SYS, BADBLK.SYS, CORIMG.SYS, and
OOOOOO.DIR (see the RSX-llM/M-PLUS and Micro/RSX I/O
Operations Reference Manual). Thus~he /MXF value
must be computed by adding the maximum number of
user UFDs and files plus the five files required for
the Files-ll structure.
/OWNER= [g ,m] (disks, DECtapes, and magnetic tapes)
/OWNER="owner" (magnetic tapes only)
Specifies the owner of the volume.
It is similar to /UIC,
but for magnetic tapes allows you to use a syntax other than
[g,m]. /OWNER="owner" allows you to change the entire
"owner identifier" field in the volume label block if this
is necessary for interchange with other systems.
l
3-105
MCR COMMANDS
c
INI (Cont.)
c
/PRO=[system,owner,group,world]
Specifies the default protection for a volume. Access codes
consist of four groups of four codes in the access rights
word, as follows:
R
W
C
D
-
Read access
Write access
Create access
Delete access
In each instance, the absence of the code
user class is denied the access right.
means
that
the
The user classes
(system, owner,
group,
world)
are
positional;
that is, the location of the word in the string
defines the user class to whom the code applies. The order
is:
[system, owner, group, world]
The square brackets are required syntax.
Substitute an asterisk (*) for the access codes to force the
default value for a specific class.
3-106
(
MCR COMMANDS
INI (Cont.)
The default volume protection is /PRO=[RWED,RWED,RWED,RWED].
That is, all types of access are allowed to all four user
class~s.
/UIC=[group,member]
Specifies the owner of the volume. Legal group
numbers
range from 1 through 377 (octal) •
brackets are required syntax.
and
The
member
square
The default is /UIC=[l,l].
/VI
Lists all of the INI
specified volume.
keywords
and
their
values
for
the
/WIN=retrieval-pointer-count
c
Specifies the number of mapping pointers to be allocated for
file windows. A file window consists of a number of mapping
pointers and is stored in memory when the file is opened.
(See
the
RSX-llM/MPLUS
and Micro/RSX I/O Operations
Reference
Manual
for
a ---description --Of
mapping
pointers.)
The retrieval-pointer-count must be in the range
of 1 to 127 (decimal) •
The default is /WIN=7.
Examples:
>INI DK1:ICTSVOL2/UIC=[[2,5]]/INDX=BEG/FPRO=[[RWED,RWE,RW,R]]®ill
The INITVOLUME parameters used in the example are:
DK1:
Device unit
ICTSVOL2
Volume label
/UIC
User Identification Code
owner: group=2, member=5
/INDX=BEG
Index file location, forced to beginning of
volume
/FPRO
Default file protection, specified by class
as:
system:
owner:
group:
world:
3-107
of
the
volume
Read,Write,Extend,Delete
Read,Write,Extend
Read,Write
Read-only
MCR COMMANDS
c
INI (Cont.)
>INI DKO:TEST/EXT=100./VI ffi)
**
**
Volume information for DKO:
Label
/Bad
/Cha
/Ext
/Fpro
/Indx
/Inf
/Lru
/Mxf
/Pro
/Uic
/Win
TEST
[Auto]
[]
= 100·.
=
[RWED,RWED,RWED,R]
Mid
147.
= 3.
294.
= [RWED,RWED,RWED,RWED]
= [1,1]
7.
Theoretical maximum files
2357.
Command Error Messages:
INI -- Allocation for SYS file exceeds volume limit
The system was unable to allocate a system
specified block because of intermediate
end-of-vo1ume.
file from the
bad blocks or
INI -- Bad block file corrupt - data ignored
Although automatic bad block recognition was selected,
the
bad block data on the disk was not in the correct format and
was therefore ignored.
c
INI -- Bad block file full
The disk had more than 102(decima1) bad regions on it.
INI -- Bad block header I/O error
An error was detected in writing the bad block file header.
c
INI -- B1ock(s) exceed volume limit
The specified block (or blocks) exceeded the
of the volume.
physical
size
INI -- Boot block write error
An error was detected in writing the volume boot block.
INI -- Checkpoint file
head~r
I/O error
An error was detected in writing the checkpoint file header.
INI -- Command I/O error
INI encountered an I/O error while reading the command line.
3-108
c
MCR COMMANDS
c
INI (Cont.)
INI -- Command too long
The command, including continuation lines,
maximum length of 512(decimal) characters.
exceeded
the
INI -- Data error
The command specified a bad
region that was too large.
block
number
or
contiguous
INI -- Device not allocated to this terminal -
The command line specified a private device that was
allocated to a terminal other than the one from which the
command was issued.
INI -- Device not in system
The command line specified
system configuration.
a
device
not
in
the
current
INI -- Device not mounted foreign
c
INI -- Device not ready -
The command line specified a device that was not ready
up to speed).
(not
INI -- Device offline
The specified device is in
on-line.
the
system
but
not
presently
INI -- Device write locked -
The command line specified a volume that was write-locked
and therefore could not be initialized as a Files-ll volume.
INI -- Disk is alignment cartridge
The last track on an RK06/RK07, RL01/RL02, RM02/RM03/RM05 or
RM80 disk identified the volume as an alignment cartridge,
which cannot be initialized a s a Files-ll volume.
An
alignment cartridge is specifically formatted for aligning
disk read/write heads.
INI -- Driver not loaded
c
The command line specified a device for which the driver has
not been loaded.
3-109
MCR COMMANDS
c
INI (CQnt.)
INI -- Duplicate block(s) found
INI attempted to define a block as bad that had already been
defined as such.
INI -- Failed to attach device -
INI could not attach the specified device.
INI -- Failed to read bad block file
The command was unable to read
from
the
last
track
of
RM02/RM03/RM05,' or RM80 disk.
the
an
bad block information
RK06/RK07, RLOI/RL02,
INI -- Failed to read manufacturer's bad sector file
A disk read (hardware) error occurred when INI attempted to
read the the manufacturer-recorded bad block data on a
last-track device. Reenter the command line and include the
/BAD=OVR option.
INI -- Failed to read software bad sector file
The software-detected bad sector file could not be read.
Reenter the command line and include the /BAD=OVR option.
INI -- Home block allocate write error
WhilelNI was overwriting a bad
error occurred.
home-block
area,
a
write
c
INI -- Home block I/O error
An error was detected in writing the Volume Home Block.
INI
~-
Illegal argument value
This message can occur for one
reasons:
INI
with
or
more
/EXT
of
was
the
following
greater
than
•
The value specified
200(decimal).
•
The value specified with /INF was less than 16(decimal).
•
The value specified with /INF or /MXF was too
the device type.
•
The value specified
127(decimal) •
with
/LRU
was
greater
than
•
The value specified
127(decimal) •
with
/WIN
was
greater
than
large
c
for
Illegal keyword value
The value you specified with the keyword is illegal.
the description of the keyword for the legal values.
3-110
Check
(
MCR COMMANDS
(
INI (Cont.)
INI -- Illegal Ule
The Ule you specified with the /Ule keyword is not a valid
one or is in an incorrect format.
Legal values for Ules are
1 to 377 (octal) and are in the format [g,m].
INI
Index file bit map I/O error
An error was detected in writing the index-file bitmap.
INI -- Index file I/O error
An error was detected in writing the index-file header.
INI
(
I/O error on device
A fatal hardware error occurred on the specified device.
INI
I/O error sizing device -
The system encountered an I/O error
disk.
while
sizing
an
RFll
INI -- Magtape label must be specified
(
The command attempted to initialize a magnetic tape
specifying the required volume label.
without
INI -- Magtape device error -
While positioning the magnetic tape, the system
an I/O error.
encountered
INI -- Magtape write error -
While writing to the magnetic tape, the
an I/O error.
system
encountered
INI -- Manufacturer's bad sector file corrupt
The manufacturer-recorded bad block data on a last-track
device is in. an inconsistent format. Reenter the command
line and include the /BAD=OVR option.
INI -- MFD file header I/O error
An errOr was detected in writing the Master
(MFD) file header.
File
Directory
INI -- MFD write error
An error was detected in writing a block in the Master
Directory (MFD).
3-111
File
MCR COMMANDS
(
INI (Cont.)
INI -- Mutually exclusive switches specified
This message can occur for the following reasons:
INI
•
The keywords /ACCESS, /OWNER, and
specified in the same command line.
•
The keyword /POS cannot
keyword except /VI.
be
specified
be
cannot
/UIC
with
any
other
No bad block data found
Although automatic bad block specification was selected, no
bad block file was found on the volume. This is only a
warning; INI continues and initializes the volume.
INI -- Not file structured device
The system
device.
does
not
support
Files-ll
on
the
specified
INI -- Null file header I/O error
An error was detected in writing null-file
index file.
headers
to
the
INI -- Preallocated too many headers for single header index files
The number you specified with the /INF
than 25598 (decimal);
therefore, the
have a multiheader index file.
keywo~d
was greater
volume would have to
c
INI -- Preallocationinsufficient to fill 1st index file header
The number you spe.cified with the /INF keyword was less than
25588 (decimal) •
INI
Preallocation insufficient to fill 1st and 2nd index file
headers
The number you specified with the /INF keyword was less than
51694 (decimal) •
C~
INI -- Privilege violation
This message can occur for the following reasons:
INI
•
Only privileged users can use the /OVR .keyword.
(This is an error message for the HOME command.)
•
Only privileged users can initialize
nonmultiuser protection system.
volumes
in
a
Public device -
The command line specified a public
devices can be initialized.
device.
Only
private
(
3-112
MCR COMMANDS
c
INI (Cont.)
INI -- Storage bitmap file header I/O error
A fatal hardware error occurred while
file header was being initialized.
the
storage
bitmap
INI -- Storage bitmap file I/O error
An error was detected in writing the storage allocation file
header.
INI
Switch is not legal for this device type
A keyword was specified that cannot be used with the
specified d~vice. Check the description of the keyword for
the valid devices.
INI -- Switch is not legal in this mode
You attempted to use HOME keywords and/or their options with
the INI command.
INI -- Syntax error
This message can occur for the following reasons:
c
(
•
The value specified with the
more than one character long.
/ACCESS
keyword
•
The volume label for an ANSI magnetic tape contained
an invalid character.
•
Illegal syntax was used during the manual
bad block numbers.
•
A keyword was specified immediately after
the
command name in the command line, instead of after
the volume name (for example, INI /UPO DO:).
input
was
of
INI -- This program must be invoked as an MCR function
The task must be installed with
••• INI •
the
task
name
••• HOM
or
INI -- Undefined density selection
The command line specified an illegal density value.
INI -- Unit does not support 800 bpi
The command line specified 800 bpi for a drive that does not
support 800 bpi.
INI -- Unit does not support 1600 bpi
The command line specified 1600 bpi for a
not support 1600 bpi.
l
3-113
drive
that
does
MCRCOMMANDS
(
INI (Cont.)
INI -- Unit does not support 6250 bpi
The command line specified 6250 bpi for a
not support 6250 bpi.
drive
that
does
INI -- Unit does not support HIGH/LOW density selection
The command line specified HIGH or LOW density for a device
for which the /DENS HIGH and LOW options are undefined.
INI -- Unit does not support density switch
The command line specified multiple densities for
that does not have multiple density capability.
a
device
INI -- Unit is not at LOW density
The command line specified that a diskette in an RX02 drive
be
initialized at low density, but the diskette was
formatted at high density.
INI -- Unit is not at HIGH density
The command line specified that a diskette in an RX02 drive
be initialized at high density, but the diskette was
formatted at low density.
INI -- Value of (I;NF + 5) exceeds /MXF
The value speci~ied with the /INF keyword plus 5
(for the
five system files)
is greater than the maximum number of
files specified with /MXF.
c
INI -- Volume mounted Files-II
An attempt was made to initialize a mounted Files-II volume.
Mounted Files-II volumes cannot be initialized.
INI -- Volume name too long -
c
(volume name)
The command line specified a volume label that
characters
for
magnetic
tape devices or
characters for disk or DECtape devices.
exceeded 6
12 (decimal)
l
3-114
MCR COMMANDS
(
INI (Cont.)
INI -- Warning -- Block 0 is bad
Block 0 of the specified volume, the boot block, was bad.
Therefore, a bootable image cannot be placed on this volume.
This is only a warning; INIcontinues and initia.lizes the
volume.
INI-- Warning -- This volume is not backwards compatible
INI has created a structure level 402 volume
value specified with the /MXF keyword was
25,593. Level 402 volumes cannot be used on
RSX-llM prior to Version 4.0 or on versions of
prior to Version 3.0.
(
c
3-115
because the
greater than
versions of
RSX-llM-PLUS
MCR COMMANDS
INS
3.30
(
INSTALL (P)
The INSTALL command makes a specified task executable by the sys~em.
An installed task is dormant (not active) until the Executive recelves
a request for the task to run. INSTALL accepts optional keywords that
provide parameters that were not specified when the task was built or
that override previously specified parameters.
When you install a task, the system creates a Task Control Block (TCB)
for the task in a memory-resident table called the System Task
Directory (STD). The task parameters contained in the TCB enable the
system to run the task when requested to do so by anMCR command or a
system directive. You cannot run a task until it has been installed
(see Section 2.5).
(Note that the RUN command has an option that
automatically installs and removes a task before and after running
it. )
A TCB contains both the address of the load-device Unit Control Block
(UCB) and the Logical block- number
(LBN) of the task image file.
Because task image files are contiguous, the Executive can load the
task image in one transfer when an MCR command or system directive
requests an installed task.
(However, if the task is greater than 32K
words, loading requires more than one transfer.)
When you install a task in a unsaved system, the system stores the
task image file's LBN in the task header. When the system is saved,
the SAVE task places the file identification, rather than the file's
LBN,
in the TCB. Then when the system is rebooted, it opens the task
file and stores the new current LBN of the task in the TCB. If a task
has been deleted, the system cannot open the task file when the system
is rebooted. The system then automatically removes the task's TCB
from the STD.
A saved system does not retain the physical addresses of installed
tasks.
The Disk Save and Compress (DSC) and Backup and Restore (BRU)
utilities can compress and copy a disk containing a saved system, thus
moving the task files to different physical locations. However,
because the TCB entries contain task file identifications rather than
LBNs, the system can function normally when it is rebooted.
(
Format:
INS [TALL]
[$] filespec l/keyword (s)]
filespec
The file specification in the form:
ddnn:[g,m]filename.type;version
The type defaults
remaining fields.
to
TSK;
standard
3-116
defaults
apply
to
the
(
MCR COMMANDS
(
INS (Cont.)
$
When' you specify $ in the command line, ddnn: defaults to LB:,
and [g,m] defaults to the current system UIC (usually, [1,50] for
an unmapped system and [1,54] for a mapped system).
On RSX-llM-PLUS operating systems, if you specify $ and the file
cannot be found under the system UIC, INSTALL searches the
By convention, LIBUIC is
library directory on device LB:.
[3,54].
Note that if LB: has been reassigned to another device and that
device's system UIC contains privile~ed tasks built for another
system, your system will crash.
Keywords:
/AFF=[CPx,UBy]
(RSX-llM-PLUS
multiprocessor
operating
systems
only.)
Allows
you
to specify the specific resources
(affinity) required for task execution. The square brackets
are
required syntax.
Legal values for the processor
specification (x) are A, B, C, and D.
Legal values for
UNIBUS run specifications (y) are E, F, H, J, K, L, M, N, P,
R, S, and T.
(
When you specify the /AFF keyword, the installed task runs
only on the processor to which the specified URMs are
connected.
/CKP=option
c
Specifies whether or not a task will be checkpointable. The
I f you
specify /CKP=YES (the
options are YES and NO.
default for tasks that can be checkpointed), checkpointing
is allowed.
If you specify /CKP=NO, checkpointing is
disabled for the task.
The /CKP keyword overrides the /CP switch specified at
build.
task
On systems that support the dynamic allocation of checkpoint
space, the task image file does not need to contain
allocated checkpoint space. The presence of the /CKP=YES
keyword instructs the system to allocate checkpoint space,
when required, for the task from a checkpoint file.
(See
the
ACS
command
for more information on allocating
checkpoint space.)
/CLI=option
(-
Specifies that the task being installed is a command line
interpreter
(CLI).
The options are YES and NO. You must
install a CLI with the YES option before you can set a
terminal to that CLI
(SET /CLI) or work with the CLI by
means of the CLI command. However, if the task was built
3-117
MCR COMMANDS
(
INS (Cant.)
with the /CL option, you do not need to install the task
with CLI=YES. For more information on the /CL option of the
Task Builder, refer to the RSX-llM-PLUS and Micro/RSX
Version 3.0 Release Notes.
/INc=size
(Mapped systems only.)
Increments
the
address
space
allocated to a task that runs in a system-controlled
partition. The variable size is the number of additional
words of address space to allocate.
The increment is
usually expressed in octal, but may also be expressed in
decimal by appending a period.
This keyword overrides the EXTTSK or PAR option used at
task-build time.
Tasks that specify the size of the
partition in which they are running use this keyword to
identify how much dynamic space they may allocate to symbol
tables or buffers. Tasks such as MAC, TKB, PIP, VFY, and
AT. use the space from the end of the task image to the end
of their address space as dynamic memory.
In effect, the
/INC keyword defines the number of words in this dynamic
region.
.
You cannot extend a task that uses memory-resident overlays.
(See the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual.)
Also, you cannot extend
task if you want it to be
checkpointed to its original task image file. Therefore,
you cannot specify the /INC keyword with the /WB=YES
keyword.
-a-
The default is either the
or zero.
~ize
specified at task-build time,
/IOP=option
Specifies that a privileged task can overmap the I/O page.
The options are YES and NO.
If you specify /IOP=YES,
INSTALL assumes that the task will overmap the I/O page (APR
7) and, if the task is larger than BK words, issues a
warning message. If you specify /IOP=NO, INSTALL assumes
that the task does not need to to use the I/O page, and it
does not issue a warning message.
.
Specifying
/IOP complements the Task Builder /IP switch.
/IP
informs
INSTALL
that the task is intentionally
overmapping the I/O page.
The default is /IOP=YES.
3-11B
(,
(
MCR COMMANDS
(
INS (Cont.)
/PAR=pname
Overrides the partition name specified at task-build time.
In an unmapped system, the specified partition must have the
same base address as the partition for which the task was
built.
If the keyword specifies a nonexistent partition, the system
issues a warning message and attempts to install the task in
the GEN partition.
By default, TKB uses the name GEN.
(See the RSX-llM or
RSX-llM-PLUS System Generation and Installation Guide for an
explanation of multiuser system defaults.)
/PMD=option
Requests a Postmortem Dump if the task aborts. The options
are YES and NO.
If you specify /PMD=YES, a Postmortem Dump
occurs if the task aborts because of an SST error condition.
If you specify /PMD=NO, no dump is requested at SST abort
time.
To generate a dump, the Postmortem Dump task PMD ••• must be
installed in the system.
This keyword overrides the /PM
switch specified at task-build time.
The default is specified at task-build time.
(
/PRI=number
Specifies the priority for the task. The value of number
can be between 1 and 250 (decimal) , where 250 is the highest
priority. The standard numbering conventions apply;
that
is, the default is octal, and the value is a decimal number
if it is followed by a period.
The default is /PRI=50.
3-119
MCR COMMANDS
(
INS (Cont.)
(
/SLV=option
Specifies slave status for the task. The options are ~ES
and NO.
If you specify /SLV=YES, data sent to the installed
task is marked with the terminal number (TI:)
of .the task
sending it. When the installed task receives the data, the
$ystem sets the task's TI:
to that associated with the
data.
This keyword overrides the /SL switch specified at
task build.
If you specify /SLV=NO, the TI:
when the task receives data.
3-120
of the task does not change
MCR COMMANDS
(
INS (Cont.)
The default is specified at task-build time.
/SYNC=option
(RSX-llM-PLUS
multiprocessor
operating
systems
only.)
Synchronizes task use of a common.
The options are
YES and NO.
This keyword permits several tasks to share a
If you
common and use the common for synchronization.
specify /SYNC=YES for two or more tasks, only one of the
tasks can execute at one time.
Note that if one of the
tasks becomes blocked, the others compete to execute.
The /SYNC keyword prevents inconsistent data that occurs as
the result of race conditions. For example, if two tasks
access a common, the /SYNC keyword ensures that only one
task executes at one time. This prevents the second task
from reading or writing the common while the first task is
executing.
The default is /SYNC=NO.
/TASK=taskname
(
Specifies the name by which the system refers to the task.
The default taskname is the name specified at task-build
time, or the first six characters of the file name.
(See
the RSX-llM
or
RSX-llM-PLUS
System
Generation
and
Installation Guide for an explanation of multiuser system
defaults.)
c
/UIC=[group,member]
Specifies the UIC for the task.
The square brackets are
required syntax. You can also override the UIC with the RUN
command.
3-121
MCR COMMANDS
(
INS (Cont.)
The task UIC determines the file-protection class
(system,
owner, group, world)
to which a task belongs and thus
directly influences file access. Note that file protection
may differ from file to file.
The default is specified at task-build time.
This default
applies only to tasks started by a RUN$ directive or a RUN
command that specifies a time delay before run time.
Tasks
started by typing the name as a command (for example, PIP
and TKB) run under the default UIC of the terminal from
which the command was issued.
c
c
3-122
MCR COMMANDS
INS (Coni.)
c
c
3-123
MCR COMMANDS
(
INS (Cont.)
(
EXqmp1es:
)INSTALL SCAN rBm
Installs task SCAN.
Priority and directory are defaulted.
)INSTALL DM1: [1,111]SCAN.TSK;4/PRI=103 rBm
InstallS task SCAN, file type TSK, version 4 on device DM1:,
group number 1, member number 111, with a priority of
103 (octal) ..
)INS MAC/INC=4096 ./PAR=SYSCTL rBm
Installs task MAC in the system-controlled partition
and increases the task size by 4096 words.
Notes:
1.
3-124
SYSCTL
c
MCR COMMANDS
(
INS (Cont.)
(
c
Command Error Messages:
INS -- Addressing extensions not supported
The command tried to install a task with a VSECT
(virtual
section) into a system that does not support the feature.
INS -- Base address must be on 4K boundary
The base virtual address of the task was not on a
boundary.
This message applies only to mapped systems.
4K
INS -- Base mismatch common block
The base address of the partition did not match that of
common block.
the
INS -- Cannot install privileged task from nonprivileged terminal
This message applies to multiuser protection systems only.
A nonprivleged user attempted to install a privileged task.
Only a privileged user can install a privileged task.
3-125
MCR COMMANDS
(
INS (Cont.)
INS -- Can't install directive common
An attempt was made to install a task in a directive common,
which the system does not support.
INS -- Can't install executive common
The executive commons (on systems that support executive
partitions)
cannot be installed at run time. The commons
must be installed with the VMR INSTALL command.
(See the
RSX-llM/M-PLUS System Management Guide) •
INS -- Checkpoint area too small
The area allocated for checkpointing the task was smaller
than the partition into which the task was being installed.
This message applies only to systems that do not support the
dynamic allocation of checkpoint space.
INS -- Checkpoint space too small, using checkpoint file
This is a warning message only.
The checkpoint space
allocated in the task image file is too small for the size
of the task (usually because of the IINC keyword).
The
system supports the dynamic allocation of checkpoint space
and will therefore use a checkpoint file to contain the
checkpointed task.
INS
(
Common block is task partition
A task's request for access to a common block was rejected
because the requested partition was a task partition.
(
INS -- Common block not loaded
The specified common block was linked to the task but had
not been installed in the system.
Install the common block,
then install the task.
INS -- Common block occupied
An attempt was made to load a task into a common block
was already occupied.
that
INS -- Common block parameter mismatch
Parameters of a common block did
task's label block.
not
match
those
in
the
INS -- Common block segment count error
The command installed a resident library with overlays, but
the number of overlay segments specified in the task header
was different from the number specified in the segment
descriptions.
3-126
MCR COMMANDS
(
INS (Cont.)
INS -- Fast map not supported
An attempt was made to install a task with the /FMAP=YES
.eyword, but during system generation support for fast
mapping was not selected for your system.
, INS -- File not contiguous
An attempt was made to install a noncontiguous task
file. Task images can only be contiguous files.
image
INS -- File not properly closed
An attempt was made to install a file that was not properly
closed (that is, locked). Since the file is locked, it is
probably corrupted. Install; a new copy of the file.
(
INS -- File not task image
Data in the label block was not correct, indicating that the
file was not,a task image.
INS -- File protection violation
An attempt was made to install a task to whose image file
you do not have proper access. You must have read access to
install a task image file.
c
INS -- Illegal device
The device specified at task build by the assign
(ASG)
option does not exist in the system. This is a warning
message only. The task is installed.
INS -- Illegal device/volume
The specified device was not a valid task-residence device.
INS -- Illegal first APR
(Mapped systems only.) A privileged task, built to run
using APR 4 or 5 as its base, was too large. Using APR 4,
the task was larger than 12K; using APR 5, the task was
,larger than 8K.
If the Executive has been built to support 20K of address
space, APR 5 is the only valid base APR for tasks mapping
into the Executive. A privileged task that does not map
into the Executive must use APR 0 as its base.
(See the
RSX-IIM/M-PLUS and Micro/RSX Task Builder Manual for a
description of the /PR switch.)
3-127
MCR COMMANDS
c
INS (Cont.)
INS -- Illegal priority
The value of the priority specified in the command
outside the valid range, which is 1 to 250 (decimal) •
was
INS -- Length mismatch common b1·ock
The length parameter for the common block, as described in
the label block for the task image, did not match the
corresponding length parameter defined in the system.
A
task's label block data must match system data for that task
before it can be installed.
INS -- Low pool, try later
(Systems with pool monitoring support only.)
During low
pool conditions, the Pool Monitor Task (PMT ••• ) temporarily
disables
insta11-run-remove
and
/CMD
requests
for
nonprivi1eged users.
c
INS -- No checkpoint space, assuming not checkpointab1e
This is a warning message only. The command attempted to
install the task as checkpointab1e, but the task was not
built as checkpointab1e and therefore had no checkpoint
space allocated in its task image file. Because the system
does not support the dynamic allocation of checkpoint space,
it considers the task unable to be checkpointed.
INS -- No checkpoint space or dynamic checkpoint file
An attempt was made to install a task with external headers
(/CKP=YES), but no
(/XHR=YES), or a checkpointab1e task
checkpoint space or dynamic checkpoint file was available
for it.
INS -- No room available in STD for new task
No dynamic memory was available to enter the Task Control
Block
(TCB)
in the System Task Directory (STD). The task
could not be installed.
INS -- Not enough APRs for task image
(Mapped systems only.)
The Task Builder allows the user to
specify the virtual base address of a task image as a
multiple of 4K.
Privileged tasks that access the Executive
3-128
c
MCR COMMANDS
(
INS (Cont.)
start at either virtual address 100000(octal)
for a 16K
Executive or at virtual address 120000 (octal) for a 20K
Executive.
If the virtual base address is set too high,
there are not enough APRs remaining to map the task image.
(See the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual
for information on privileged tasks.)
INS
Partition not common
A partition specified for a common area or
defined as a common partition.
library
is
not
INS -- Partition not in system, defaulting to GEN
This is a warning message only.
The specified partition
does not exist, so the system attempts to install the task
in the GEN partition.
INS
Privileged task larger than 12K
A privileged task was larger than 12K words.
Privileged
tasks on an unmapped system have a maximum size of 12K.
INS
(
c
Privileged task not mapped to I/O page
A privileged task was larger than 8K
and
therefore
overlapped the I/O page. This message occurs if the task is
installed with the /IOP=YES option.
INS -- Specified partition for common block
An attempt was made to install a task in a common block.
INS -- Specified partition too small
The task being installed was larger than the partition
which it was being installed.
into
INS -- Task image already installed
(-
The requested task image, which was checkpointable, had
already been installed. On systems that do not support the
dynamic allocation of checkpoint space, checkpointable tasks
that have checkpoint space allocated can be installed only
once; other tasks can be installed more than once
(under
different names).
3-129
MCR COMMANDS
c
INS (Cont.)
INS -- Task image I/O error
INSTALL could not read the task image
rewrite
the
task
image
header.
write-locked.)
file or could
device
(The
not
is
INS -- Task image virtual address overlaps common block
The virtual addresses reserved for the task image overlap
those reserved for the common block specified in the
message. A corruption of the task image file probably
caused the overlap.
INS -- Task may not be run
This message can be issued for the following reasons:
•
An attempt was made to run a CLI task.
CLI tasks
are
activated
by the system;
they cannot be
activated with the install-run-remove option of the
RUN command.
c
INS -- Task name already in use
An attempt was made to install a task with the same name
one already in the system.
as
INS -- Task not in system
An attempt was made to install a task that is not built into
the system, or the task name was specified incorrectly.
INS
Too many common block requests
A task made too. many requests for common blocks.
limited to seven requests.
INS
A task
is
Too many LUNs
A task requested more than 255(decimal) LUNs to be assigned.
3-130
c
MCR COMMANDS
INS (Cont.)
INS
Undefined common block
A task referenced a common block that had not been defined
in the system.
Usually,
this message indicates that the
task was built for another system.
INS -- Warning -- Privileged task overmaps the I/O page
A privileged task that is mapped into the Executive is
usually also mapped into the I/O page to access the
registers for the KTll and other devices. Many tasks do not
require this access and can use the additional 4K words of
virtual address space for the task image.
This message
warns that a task that may require access to the I/O page
might have grown too large.
(
3-131
MCR COMMANDS
LOA
3.31
(
LOAD (P)
The LOAD command reads a nonresident
(loadable) device driver into
memory and, if necessary, relocates the data base constructs and
interrupt-vector linkages required to allow access to the device.
On
RSX-IIM-PLUS
operating
systems,
the
task
CON
constructs
interrupt-vector linkages.
The LOAD command eliminates the need to link infrequently used device
drivers
permanently into the Executive.
. (Executive support of
loadable device drivers is a system generation option on RSX-IIM
operating systems but is always included on RSX-IIM-PLUS operating
systems.) The result is the potential for an increase in the amount of
system dynamic memory.
You can load driver~ that are up to 8K words in
however, that the loadable device driver itself
locations above 4K.
length.
Note,
must map to any
The driver for a device, for example ZY:, can indicate association
with a partition by allocating one word in the driver and labeling it
with the global symbol $ZYCOM. If $ZYCOM is defined in a driver, you
cannot load the driver until you create ZYCOM (LOA writes the PCB
address of ZYCOM into $ZYCOM).
Format:
c
LOA[D] dd: [/keyword(s)]
dd:
A 2-character ASCII loadable device driver name.
Keywords:
c
(
3-132
MCR COMMANDS
(
LOA (Cont.)
/EXP=expname
Specifies the name or file specification of
Executive partition to be loaded into memory.
an
extended
/HIGH
If the partition is system-controlled, /HIGH causes the
driver to be loaded as high in the partition as possible;
absence of /HIGH loads the driver as low in the partition as
possible.
If the partition is not system-controlled, the driver
occupies the entire partition whether or not you specify
/HIGH.
/PAR=parname
Specifies the partition (parname) into which the
to be loaded.
c
c
driver
is
All loadable drivers are usually placed in the
same
partition, by convention DRVPAR. This has the advantage of
preventing fragmentation of the GEN partition.
When the command line omits this keyword, the system loads
the driver into the partition specified when the driver was
buil t.
/SIZE=parsize
Specifies the minimum size (in words) of the partition into
which the driver is to be loaded. If the partition is
system-controlled, a subpartition will be created at this
size.
The value of parsize is rounded up to the next highest
of 100 (octal) words and must be less than 100000.
unit
/VEC
Specifies that the driver to be loaded is
vectored.
Vectoring avoids the normal comparison of the driver symbol
table file and the system symbol table file.
3-133
MCR COMMANDS
(
LOA (Cont.)
Examples:
>LOAD
MM: (BIT)
!LOAD TU16 DRIVER (MMDRV)
Loads the MMDRV driver into the partition that was specified
when the driver was built.
>LOA
LP:/PAR=DRVPAR(BIT)
!LOAD LPll DRIVER (LPDRV)
INTO DRVPAR
Loads the LPDRV driver into the DRVPAR partition.
>LOAD /EXP=LB: [1,54]DCMEXP/PAR=GEN(BIT)
Loads the data cache manager
partition into the GENpartition.
(DCM)
extended
Executive
Notes:
•
Rigid instructions for building loadable device-driver tasks
are defined in the RSX-llM or RSX-llM-PLUS Guide to Writing an
I/O Driver.
Note that the system generation- procedures
include provisions to simplify the task building of drivers.
•
It is not possible to make all device drivers loadable.
not all loadable drivers can have loadable data bases.
•
The LOAD command requires that a driver's TSK and STB files
reside under the system UIC on the system disk (LB: ). For
example, the following command requires that the
files
DTDRV.TSK and DTDRV.STB reside on LB: under the appropriate
system UIC:
LOA
Also,
(
DT:
The command SET /SYSUIC displays and defines the system UIC;
the usual values, however, are [1,50] for an unmapped system
and [1,54] for a mapped system.
•
The LOAD command does not initiate
space in a partition.
checkpointing
•
The LOAD command requires pool space as follows:
If the driver data base is being loaded,
the
needs contiguous pool space equal to its size.
to
free
data
a
base
In a mapped system, each interrupt entry in the driver
needs pool space for an Interrupt Control Block (ICB).
If the driver is being loaded into a system-controlled
parti tion, the Partition Control Block (PCB) needs pool
space.
Command Error Messages:
LOA -- Cannot LOAD/UNLOAD a pseudo device
The device you attempted to load is a pseudo device.
devices do not have drivers.
3-134
Pseudo
c
MCR COMMANDS
(
LOA (Cont.)
(
LOA -- Device not in system
The data base for the device driver was not in the system or
in the driver's task image.
LOA -- Device not mounted
The system device (LB:) was not mounted.
LOA -- Driver already resident
The specified device driver had already been
permanently resident.
loaded
or
is
load
or
LOA -- Driver being loaded or unloaded
The Executive was effecting
unload the driver.
another
request
to
LOA -- Driver built with wrong executive STB file
The STB file for the driver was not compatible with the
current Executive.
The task build probably specified an
RSXllM.STB file that was not for the current system.
(3-135
MCR COMMANDS
(
LOA (Cont.)
LOA -- File has illegal STB format
The driver's STB file contained an illegal
data record format.
object
code
or
LOA -- File not a valid driver task image
The driver's task image was either overlaid or
header.
had
a
task
LOA -- File ddDRV.TSK not contiguous
The file ddDRV.TSK was not contiguous. Device drivers (like
all task image files) must be contiguous.
LOA
I
Illegal driver task APR usage
A device driver must be built for APR 5 and must be
than
8K
(for example, PAR=DRVPAR:120000:40000).
message applies to mapped systems only.
c
less
This
(
LOA -- Illegal value for symbol in file
The symbol symname is defined to an illegal value in file
ddDRV.STB. This can occur for several reasons, some general
and some specific to individual symbols.
For example,
symbols cannot have odd values, most symbols cannot be
defined as as zero, $ddTBL must exist and have a value ,less
than $ddEND, and mapped loadable drivers cannot reference
$INTSV.
LOA -- Insufficient pool space
The required
available.
amount
of
system
dynamic
memory
was
not
c
3-136
MCR COMMANDS
(
LOA (Cont.)
LOA -- Invalid driver data base at offset in file
The driver had an invalid data base value at offset xxxx
relative to the symbol $ddDAT. This can occur for three
general reasons:
1.
An invalid value, for example, D.UCB was odd.
2.
The value for a word is not within the bounds of the
loadable data base.
LOAD produces an error message
citing the offending value.
3.
An element is missing from the loadable data base. LOAD
attempts to verify one kind of data structure as another
kind. For example, if a DCB is missing, LOAD tries to
verify the following UCB as the DCB. LOAD cites the DCB
as being incorrect.
LOA -- Loadable driver support not in system
The system generation option to support loadable device
drivers was not chosen or necessary routines are not in the
Executive.
3-137
MCR COMMANDS
(
LOA (Cont.)
LOA -- Open failure on file
LOAD encountered
specified file.
an
error
in
attempting
to
open
the
c
LOA -- Partition too small
The partition into which the driver was to be loaded was not
large enough to contain/it.
LOA -- Region/partition is a common
You have attempted to load a device driver into a common
partition or region. A device driver cannot be. loaded into
a common partition or region.
3-138
MCR COMMANDS
(
LOA (Cont.)
LOA -- Symbol is doubly defined by file
The symbol symname is defined twice in the specified file.
Duplicate symbols are illegal. The driver is not loaded.
LOA -- Symbol is undefined in file
The symbol symname was found in the specified file, but
symbol was not defined.
the
LOA -- Task image I/O error in file
The device is probably write-locked. LOAD could not read
the task image file or could not rewrite the task image
header.
(
LOA -- Warning -
Loadable driver larger than 4K
Loadable drivers can be up to 8K words in length.
The
driver must explicitly map to any location above 4K words.
3-139
MCR COMMANDS
LUN
3.32
c
LOGICAL UNIT NUMBERS (NP)
The LUN command displays the static logical unit number
(LUN)
assignments for a specified task.
(Static assignments are those
recorded in the task's disk image file.) The display consists of a
list of physical device units in one column and their corresponding
LUNs in an adjoining column.
When the specified task is running, the display does not necessarily
reflect the running task's assignments. For example, an Executive
directive issued from within the task (ASSIGN LUN) can alter the LUN
assignments.
If the specified task was initiated by the install-run-remove option
of the RUN command, the task has no static LUN assignments • . In this
case, LUN displays the message:
LUN -- Task not in system
Fo:i:mat:
LUN[S] taskname
Example:
>LUN XKE
TIO: 1.
SYO:
2.
SYO:
3.
SYO: 4.
LBO: 5.
ffi)
c
The display shows static assignments for LUNs 1, 2, 3, 4,
and 5, which are recorded in the task image file header; no
other LUNs are statically assigned to the task XKE.
Command Error Messages:
LUN -- No LUNs
The task that is the argument of the LUN command did not
have any logical assignments.
This is an informational
message.
LUN -- Task not in system
The specified task is not installed or the task
initiated by the install-run-remove option of the
command. This is an informational message.
was
RUN
LUN -- LUNs not available because task image is deleted
The LUN assignments for the specified task could not be
disp,layed because the task's image has been deleted from the
system.
3-140
c
MCR COMMANDS
(
MOU
3.33
MOUNT, (NP, P)
The MOUNT command allows the file system software access to physical
devices.
For all volumes on these devices, MOUNT creates the file
system control blocks that the Ancillary Control Processors (ACPs) use
to support data access on the device. MOUNT also declares, provided
an on-line access path exists, that the volume is logically on line
for access. The command then requests the ACP to mount the volume or
volume set. Mounting a volume also resets the QIO and Error counts to
zero. These counts are used by the .Error Logging faci,lity.
The kbuNT command supports the following three types of devices:
c
c
1.
File-structured devices.
file-structured devices.
Disks and DECtapes are examples
2.
Sequential devices.
sequential devices.
3.
Non-file-structured devices.
Devices
nonstandard
file
structures
non-file-structured devices.
Magnetic
tapes
are
with
are
an
example
unformatted
examples
of
of
or
of
File structured devices are usually controlled by the Files-II
Ancillary
Control
Processor
(FIIACP), which supports Files-II
Structure Levell. Magnetic tapes are usually controlled by the
Magnetic Tape Ancillary Control Processor (MTAACP), which supports
both
ANSI
(X3.27-1978)
and
unlabeled
tape
formats.
Non-file-structured devices do not have to be mounted on RSX-IIM
operating systems, but they must be mounted as foreign devices on
RSX-IIM-PLUS operating systems.
When you mount a Files-II or magnetic tape volume, there are several
default ACPs that MOUNT can use. MOUNT first defaults the ACP name to
ddnnFl. This allows you to tailor the ACP that controls a specific
volume and then name that ACP after the volume. For example, if you
tailor FIIACP for an RK06 disk and install it as DMOIFl, then when you
issue a MOUNT command for DMl:, MOUNT searches for the ACP DMOIFl.
For disks, if MOUNT cannot find an ACP whose name is in the form
ddnnFl, it searches for an ACP whose name is in the form ddAACP and
then FIIACP. For magnetic tapes, the default ACPs are ddnnFl, ddAACP,
and then MTAACP. Note that (for privileged users) these defaults can
be overridden by using the /ACP keyword.
It is recommended for slow disk devices such as DECtape' that a
separate ACP be used. Thus, you should install a copy of FIIACP as
DTAACP for DECtape and a copy as DDAACP for DECtape II.
3-141
MCR COMMANDS
MOU (Conf.)
When a device is dismounted, outstanding I/O is allowed to complete,
but no additional files can be accessed On that volume (see the
description of the DISMOUNT command).
MOUNT also classifies devices and volumes into three other types:
public, shared, and nonshared. A public volume is one that all system
users can access. Public volumes are the only type supported by
nonmultiuser systems.
A shared volume is one that can be mounted
multiple times by multiple users. A nonshared volume (p~ivate) is one
allocated to a single user. See Chapter 2 for more information on
device types.
~
A nonprivileged user can only mount a volume on:
•
The user's private device. No other user can access or mount
the volume until the volume is dismounted and deallocated.
•
Any other device that has not been allocated or set public.
If another user mounts the volume, that user can also access
it.
Only one user can mount a magnetic tape volume (or volume set) at
time.
one
Some file attributes and positioning information can be supplied after
the volume is mounted with the MAG utility. For more information, see
the RSX-llM/M-PLUSand Micro/RSX I/O Operations Reference Manual.
If the
waits
device
issues
device is not ready when you attempt to mount the volume, MOUNT
from 30 to 60 seconds for the device to become ready.
If the
is still not ready after the waiting period has elapsed, MOUNT
an error message.
The following descriptions of the MOUNT command formats illustrate the
parameters and keywords associated with Files-II volumes and with ANSI
magnetic tapes. All the keywords are collectively described following
the format descriptions.
You can use a hyphen (-) as a line terminator to extend the MOUNT
command line when selected keywords cause the command to exceed 80
characters (or whatever buffer size has been specified for the
entering terminal). You can use any number of continuation lines, but
the total command line cannot exceed 255(decimal) characters.
Note that since the override volume label keyword
(/OVR)
is a
privileged option of the MOUNT command in a multiuser protection
syste~, a nonprivileged user must always specify a volume label.
Formats:
Files-II Disk or DEC tape Format:
MOU[NT] ddnn:[label] [/keyword(s)]
ddnn:
Device unit on which the volume is to be mounted.
no default device unit; you must specify one.
3-142
There
is
c
c
MCR COMMANDS
MOU (Cont.)
label
Th~
Files-II volume label may be null or up to 12 characters
in length.
It is used to ensure that the correct volume is
being mounted.
In a multiuser protection system, the
command must include a volume label unless the privileged
/OVR keyword is present.
/keyword (s) :
MOUNT keywords for Files-II devices
values in the volume's home block.
override
corresponding
Note that in the syntax of the following keywords,
use either an equal sign (=), or a colon (:).
/ACP=option
you
can
/PRO=option
/CACHE=option
c
/DENS=density
/PUB
/EXT=block-count
/[NO]SHARE
/FOR
/UIC';'uic-spec
/FPRO=[system,owner,group,world]
/UNL
/LOCK=option
/VI
/LRU=directory-count
/[NO]WAIT
/OVR
/WIN=option
/PARM="user parameters"
/[NO]WRITE
ANSI Magnetic Tape Format:
c
Magnetic tapes, unlike disks and DECtapes, can be mounted by the
set as well as individually. In fact, when you mount a single
magnetic tape, you are mounting a set consisting of only one
tape.
A tape set consists of logically related records or files
written on one or more reels of tape. Only the first tape in the
set has to be loaded on a device at the time the MOUNT command is
issued, but all tapes in the set can be loaded on different
devices when the command is issued.
.
The tape set is identified by a File Set Identifier.
Each tape
in the file set is identified by a Volume Identifier. By
default, the File Set 10 is the same as the Volume 10 of the
first reel of tape in the set. If this is true for your tape
set, it is not necessary to specify the Volume IDs for the tapes
(although it is recommended).
Volume Identifiers should be assigned by the system
should be unique within the installation.
The
usually the reel number of the physical tape.
Identifier, however, is a name chosen by the user to
or her own tape.
3-143
manager and
Volume ID is
A File Set
refer to his
MCR COMMANDS
(
MOU (Cont.)
If your tape set processing uses more volumes than you specified
with the /VOL keyword, you can use any expired or newly
initialized tape for the output volume. For input, you can use
only the next volume in the tape set. To determine if the new
input tape is the correct one, the system checks the tape's File
Set ID, file sequence number, and file section .number. If
specified, the system also checks the Volume ID.
MOU[NT] device-list: [file-set-ID]
[/keyword(s)]
device-list
One or more device names on which the volume or volume set
is to be mounted.
More than one device name can be
specified only for multivolume ANSI magnetic tape set~.
If
the command specifies more than one device name, the names
must be separated by commas and enclosed in parentheses, as
follows:
(ddn:,ddn:,ddn: ••• ) •
Note that when you specify more than one device name, you
must always access the tapes through the first name given in
the device list.
(This also applies when you dismount the
tape set.)
If you attempt to access a tape through another
device name, you will get an error message.
file-set-ID
The File Set Identifier (or File Set ID) can be up to six
characters long. The File Set ID is the name you choo~e for
the tape set. By default, it is the same as the first
Volum~
Identifier (Volume ID) in the, volume set. To create
a tape set with a File Set ID that is different from the
Volume ID of the first tape in the set, specify both the
File Set ID and the first tape's Volume ID.
If you are mounting a newly' initialized tape, you can
specify your own File Set ID by using a form of the
following command line (note that the /VOL keyword is used
because the File Set ID and the Volume ID are not the same):
>MOU MM:MYSET/VOL=A234
See the description
Volume IDs.
of
c
c
~
/VOL
for
more
information
about
File Set IDs can use the digits 0 to 9, the uppercase
letters A through Z, and the following special characters:
!
"%
&
'
(
)
* + , -.
/:
< = > ?
To use a name that contains a special character, enclose the
name in quotation marks.
To use a quotation mark in the
name, you must use two quotation marks within the quoted
string.
For example, the label T"l% should be specified as
"T""l%".
3-144
(
MCR COMMANDS
(
MOU (Cont.)
Any lowercase letters specified in a File Set ID or Volume
ID are converted to uppercase before any operations are
performed on the tape.
Any other invalid character is
converted to a question mark (?). Also, you can use either
an equal sign (=) or a colon (:) wherever an equal sign is
indicated in the keyword syntax.
/keyword(s) :
c
/ACP=option
/OVRFSID
/BS=n
/PARM="user parameters"
/CC=option
/PRO=option
/DENS=density
/PUB
/FOR
/RS=n
/FPRO=protection-spec
/[NO]SHARE]
/[NO]HDR3
/TR=option
/[NO] LABEL
/UIC=[uic]
/LOCK=option
/VI
/OVR
/VOL= (list)
/OVRACC
/[NO]WAIT
/OVREXP
/[NO]WRITE
Keywords:
/ACP=option (P)
c
Specifies the name of the ACP to be used
processor for the volume being mounted. The
the name of a task that is installed as an ACP
UNIQUE, which specifies that a dedicated ACP
for the volume.
as the file
option can be
or it can be
is to be used
You only need to specify an ACP in special cases. If an ACP
has
beeri written for a customer application in your
installation, you will need to use that ACP for volumes used
by that application.
When you specify the UNIQUE option, MOUNT creates a copy of
the FllACP if the device is a disk or DECtape or of MTAACP
if the device is a magnetic tape. This unique ACP is given
a name in the form ddnnFl or ddnnAP. When the volume is
dismounted and the file processor exits, the ACP
is
automatically removed.
The default depends on the device type.
3-145
MCR COMMANDS
(
MOU (Cont.)
IBS=n
Specifies the block size for an unlabeled magnetic tape
volume or the block size for files on an ANSI labeled tape
that are Level 1 or 2 (do not have an HDR2 record).
The
value for n can be from 14 (for unlabeled tapes) or 18 (for
ANSI tapes) through 16000. IBS also specifies the default
block size for newly created files on an ANSI magnetic tape.
c
c
('
3-146
MCR COMMANDS
(
(
MOU (Cont.)
/CC=option
Specifies the record type for an unlabeled magnetic tape
volume, or the record type for files on ANSI labeled tapes
that are Level 1 or 2 (do not have an HDR2 record) or that
are/ Level 3 but do not have a system code (HDR CP 61)
beginning with DEC or OS. The options are:
FOR
LIST
NONE
These options correspond to the
OPEN statement.
FORTRAN
keywords
for
the
/DENS=density
The density (bits per inch or bpi) of the medium loaded on
the drive.
Acceptable density values depend on the device
type as indicated below:
3-147
MCR COMMANDS
(
MOU (Cont.)
The default density values are:
TE16
TSll
TSV05
TU45
TU77
TU78
TU80
/DENS=800
/DENS=1600
/DENS=1600
/DENS=800 (or LOW)
/DENS=800
/DENS=6250
/DENS=1600
If you specify more than one device type in the command line
but you do not specify a density, the default density is the
lowest density supported by all of the devices.
/EXT=block-count
Specifies the number of blocks by which a file can be
extended
when it exhausts its space allocation.
The
block-count must be between 1 and 255 (decimal) •
The default is the
ini tiali zed.
value
specified
when
the
volume
was
/FOR
Indicates a foreign (non-Files-ll) volume.
If you do not specify an ACP name (with /ACP=option), a file
system (an ACP) cannot access the volume. Absence of an ACP
name permits tasks (such as INI, DSC, BAD, or user tasks
executing
non-file-structured
device
QIOs)
access to
non-Files-ll volumes.
/FPRO=protection-spec
Specifies the default file protection for files created on a
Files-II disk or magnetic tape while the disk is mounted.
The protection specification has two formats:
(SYSTEM:RWED,OWNER: RWED,GROUP: RWED,WORLD: RWED)
or
[RWED,RWED,RWED,RWED]
The access codes consist of four groups of four codes in the
access rights word as follows:
R
W
E
D
-
Read access
write access
Extend access
Delete access
3-148
(
MCR COMMANDS
(
MOU (Cont.)
In each instance, the absence af the cade means
applicable user is denied the access right.
The defaults are the
Black.
values
taken
fram
the
that
Valume
the
Harne
/[NO]HDR3
Specifies whether an HDR3 label is to. be written when
creating new files.
The /NOHDR3 keyward is needed anly when
it is knawn that the target system cannat handle a tape with
an HDR3 label.
This keyward has no. ather effect ar
applicatian.
The default is /HDR3.
/[NO] LABEL
Specifies that a magnetic tape valume is in ANSI farmat
(/LABEL) ar unlabeled (/NOLABEL). The default is /LABEL.
/LOCK=aptian
Specifies the default value far the DISMOUNT /LOCKkeyward.
c
The aptians are:
Naunlaad
Unlaad
Virtual
c
When yau specify the Naunlaad aption (/LOCK=N), the valume
valid bit is cleared, but the disk is nat spun dawn ar the
tape unlaaded. This is the default aptian far valumes
maunted fareign and no. ACP specified. Far example, when yau
want to. initialize a valume as a Files-II valume, yau first
issue
a MOUNT command with the /FOR keyward.
After
initializing the valume, the usual pracedure is to. dismaunt
it and then issue anather MOUNT cammand, using a standard
ACP. Since the default lack value is N, the valume remains
spinning ar laaded and yau can immediately issue the MOUNT
cammand that specifies the ACP.
When yau specify the Unlaad aptian (/LOCK=U) far disks,
valume valid bit is cleared and, if the drive supparts
spin-dawn functian, the disk is pawered dawn.
When
specify this aptian far tapes, the tape is rewaund
unlaaded. This aptian is the default lack value far
valumes maunted with a standard ACP.
3-149
the
the
yau
and
all
MCR COMMANDS
(
MOU (Cont.)
The Virtual option is privileged. When you specify /LOCK=V,
the volume valid bit is not cleared and the disk is not spun
down or the tape unloaded.
See the
detalls.
description
of
the
DISMOUNT
command
for
more
/LRU=directory-count
Specifies the approximate number of directories that will be
accessed simultaneously while the volume is mounted. The
FllACP maintains a list of the
most
recently
used
directories.
The value specified for /LRU sets the number
of entries in this list.
In general, directory operations
can be speeded up significantly by increasing the number of
entries.
If a directory appears in the list, no device I/O is
required for finding the directory in the Master File
Directory (MFD).
In ad~ition, directory operations do not
require the directory f{le header to be read.
Legal values for
directory-count
range
from
0
to
127 (decimal) •
Note that increasing the value for /LRU
increases the number of File Control Blocks (FCBs) used and
may increase the amount of system pool used. See the
appropriate system generation manual for more information.
(
Also note that if you specify /LRU=O, the FllACP will not
keep a list of directories. This is not recommended and
could have an adverse effect on system efficiency.
If you do not use /LRU, the default for directory-count
the value specified when the volume was initialized.
is
/OVR (P)
For disks and DECtapes,
instructs the MOUNT command to
override label processing so that a volume can be mounted
without specifying a volume label.
For magnetic tapes, instructs the MOUNT command to override
File Set ID processing on the first tape of a tape set so
that a volume can be mounted without specifying a File Set
ID.
When you specify /OVR, the File Set ID is taken from the
first volume in the set.
However, MOUNT still checks the
IDs for the remaining volumes in the set.
This prevents
improper tape processing.
(Note that Volume IDs for the
tape volumes are overridden if they are not specified,
whether or not you use /OVR.)
3-150
c
MCR COMMANDS
(
MOU (Cont.)
/OVRACC (P)
Instructs the MOUNT command to override the
an ANSI magnetic tape volume.
protection
for
/OVREXP (P)
Instructs the MOUNT command to override the expiration
on the tape volume(s).
date
/OVRFSID (P)
Instructs the MOUNT command to ignore File Set Identifiers
on the second and subsequent magnetic tape volumes of a
multivolume set.
/OVRFSID
may
cause
improper
tape
processing.
This keyword should be used only if you know
the volume does not conform to the ANSI standard.
/PARM=luser-parameters"
Instructs the MOUNT command to pass nonstandard parameters
from the command line to a foreign ACP. The user-parameter
string can consist of up to a maximum of 40 (decimal)
characters enclosed in quotes ("). The quotation marks are
not included when the cha~acters are counted.
c
If the quoted parameter itself includes a quotation mark,
the quotation mark must be followed by another quotation
mark.
This keyword is valid only with foreign (/FOR) volumes.
/PRO=protection-spec
c
Specifies the def.aul t volume protection for a Files-II disk
or magnetic t~e.
The protection specification has two
formats:
(SYSTEM: RWCD,OWNER: RWCD,GROUP:RWCD,WORLD:RWCD)
or
[RWCD,RWCD,RWCD,RWCD]
The access codes consist of four groups of four codes in the
access rights word as follows:
R - Read access
W - Write access
C - Create access at volume level; extend access
at file level
D - Delete access
In each instance, the absence of the code means
applicable user is denied the access right.
The defaults are the values specified when
ini tialized.
3-151
the
that
the
volume
was
MCR COMMANDS
MOU(Cont.)
/PUB
Specifies that the volume is accessible by all users,
depending on the volume and file protection set for the
volume. The drive on which the volume is mounted is
deallocated and set public if necessary.
The defaults are:
/PUB if the volume is public
/SHARE if the volume is not allocated or set public
/NOSHARE if the volume is allocated to a user
See Chapter 2 for more information on public devices.
/RS=n
Specifies the number of characters in a record for unlabeled
magnetic tape volumes or the number of characters in a
record for files on ANSI labeled tapes that are Level I or 2
(do not have an HDR2 record). The value for n can be from 1
through the value specified with /BS.
/[N01SHARE
/SHARE specifies that a volume can be mounted multiple times
by one or more users.
Each user who mounts the volume gains
access to it based on the volume and file protection
established for the volume when it was first mounted. After
all users have issued a DISMOUNT command and all file
activity has ceased, the volume is released by the file
processor. The volume is deallocated and set nonpublic if
necessary.
/NOSHARE specifies that the volume is reserved for dedicated
use by the first user who mounted the volume. No other
users can access the volume. The drive on which the volume
is mounted is allocated to the user's terminal and set
nonpublic if necessary.
The defaults are:
/PUB if the volume is public
/SHARE if the volume is not allocated or set public
/NOSHARE if the volume is allocated to a user
/TR=option
Specifies the kind of character translation used in read and
write operations on an unlabeled magnetic tape volume. The
options are:
NONE
No translation takes place.
EBCDIC
Translation from EBCDIC to ASCII for read;
ASCII to EBCDIC for write.
(Note that
translations
are
not
completely
symmetrical.
Some characters in one set
do not have equivalent characters in the
other set.)
3-152
c
c
·MCR COMMANDS
(
MOU (Cont.)
UTI, UT2,
UT3
Translation
done
by
user-supplied
Translation
tables
that
have
been
previously linked into MTAACP.
Up to
three tables may be linked.
By default, no translation
takes
place.
(See
the
RSX-IIM/M-PLUS and Micro/RSX I/O Operations Reference Manual
for more information on character translation.)
/UIC=[uic]
Specifies the User Identification Code (UIC) for the volume
owner in the form [group,member]. The square brackets are
required syntax. The numbers for group and member range
from 1 to 377(octal). This UIC overrides the one specified
when the volume was initialized.
/UNL
Specifies that the volume index file should be unlocked for
write access by a system user. When locked, the index file
is read-only; when unlocked, it is read or write.
This
keyword is typically required when you are recovering lost
blocks or performing other maintenance with the VFY utility.
(See
the
RSX-IIM/M-PLUS
Utilities
Manual
for more
information.) Note that this keyword has nothing to do with
device write-locking.
c
The default is locked.
/VI
Displays the volume information on the entering terminal.
The information displayed is the characteristics with which
the volume was mounted.
For Files-II volumes, the volume information format is:
(
Volume Information
Class:
Files-II
Device:
ddnn
Volume label:label
Owner:
[uic]
Protection:
[system,owner,group,world]
Default:
[system,owner,group,world]
Processor:
ACP name
For last-track devices (for example, DL:, DM:, and DR:) and
for DU:-type devices, /VI also displays, in octal, the pack
serial number of the volume.
For foreign volumes, the volume information format is:
Volume Information
Class:
Foreigr
Device:
ddnn
Volume label:label
3-153
MCR COMMANDS
MOU (Cont.)
For magnetic tape volumes, the volume information format is:
Volume Information
Class:
ANSI labeled tape or Unlabeled tape
Device:
ddnn
Fileset ID:
id
Volume ID:
id
Owner:
[uic]
Processor:
ACP name
For magnetic tape, the volume information repeats the device
and label lines if multiple units were specified and omits
the volume protection and characteristics defaults
(volume
protection and characteristics do not apply to magnetic
tapes) •
/VOL= (list)
Specifies the Volume Identifier
(Volume ID)
for an ANSI
magnetic tape.
If you specify more than one Volume ID (for
a multivolume tape set), the Volume IDs must be separated by
commas.
Initially, the tape with Volume-IDI must be physically
loaded on the first device unit specified in the command
line. The remaining tapes mayor may not be loaded on other
units specified in the command line.
You must specify
Volume IDs in the order in which the volumes make up the
volume set because the system searches for or requests each
successive volume in the specified Volume ID order.
The second and succeeding volumes should be mounted on the
additional units in the order in which they were specified
in the command line or as requested by console messages from
MTAACP.
If more tapes are required than were specified at mount
time, MTAACP automatically adds additional volumes to the
set.
When the command line is issued, the system checks the tape
on the first drive to ensure that it is the first volume of
file-set-ID (see the format for MOUNT command lines for
magnetic tapes).
I f you do not specify the /VOL keyword,
the system does not check the Volume ID for the tape.
For compatibility with previous RSX-IIM/M-PLUS releases, the
command line
>MOU MM: (A,B,C)
is equivalent to the command line
>MOU MM:A /VOL=(A,B,C)
/[NO]WAIT
Specifies whether you require operator
assistance,
in
performing the mount.
The main use of this keyword is for
batch jobs, indirect command files, or terminals distant
from the machine room.
3-154
(
MCR COMMANDS
(
MOU (Cont.)
If you specify /WAIT in an interactive mount, a message
concerning the mount is sent to the operator's console and
the mount is not completed until the operator takes action.
If you specify /NOWAIT in a batch job or indirect command
file,
or if the mount is interactive, no message appears.
The volume must have been previously placed on the device
and readied for access (spun up/brought on-line).
The default is /NOWAIT.
/WIN=option
Specifies the number of mapping pointers to be allocated for
file windows. A file window consists of a number of mapping
pointers and is stored in memory when the file is opened.
(See
the
RSX-llM/M-PLUS and Micro/RSX I/O Opera~ions
Reference Manual for a description of retrieval pointers.)
The number of retrieval pointers must be less than 129.
/WIN accepts the following options:
(
n
All files are set up with this
default
unless
overridden
on
access;
legal values are 1
to
127 (decimal) or the FULL option.
USER:n
User default value for the volume.
INDEX:n
Number of pointers to
the index file window
(USER:n,INDEX:n)
If n is not the same for both of
these, defaults to the user default
value for the volume default and to
the number specified for the index
file
FULL
Windows are created that map as
much of the file as possible; FULL
can be used for n in all of these
options.
allocate
The default is the number of pointers specified in the
block with either the INI or HOME command.
to
home
/[NO]WRITE
/WRITE specifies that write operations are allowed on the
volume
(the volume is software write-enabled) within the
limits of volume and file protection.
/NOWRITE specifies that write operations are not allowed
the volume (the volume is software write-locked).
By default, write operations are allowed.
l
3-155
on
MCR COMMANDS
(
MOU (Cont.)
Examples:
>MOU OMI :AMBER 001
Mounts the volume on device unit DM1:.
(In this example,
the optional parameters have not been specified. Therefore,
MOUNT uses the parameter values in the volume's home block.)
No volume information is displayed.
>MOU (MTO:,MTI:,MT2:)MYSET /VOL=(VOL1,VOL2,VOL3) 001
Mounts the volume set MYSET on units MTO:, MTI:, and MT2:.
Initially, VOLl must be physically loaded on MTO:; the first
volume in a set must always be loaded on the first unit
specified in the command. VOL2 and VOL3 mayor may not be
loaded when the command line is issued.
If they are loaded,
they can reside on the remaining units in any order (for
example, VOL3 could be loaded on MT1:).
The system searches for the next volume in a set by Volume
10 rather than by unit number; the order in which volumes
are listed in the command line is the order in which the
system searches for and/or requests the volumes.
If VOL2
and and VOL3 are not loaded, the system requests each in
turn.
The volumes can be loaded on either MTO:, MT1:, or
MT2: •
>MOU OM1:SYS004/LRU=9/VI/WIN=20 001
Mounts the volume labeled SYS004 on DM1:. The command line
reserves space for nine directory File Control Blocks (FCBs)
to remain in the ACP's pool or system pool, displays the
volume information, and changes the default window block
size for files opened on this volume to 20 (decimal) •
(
(
Command Error Messages:
See the RSX-I1M/M-PLUS and Micro/RSX I/O Operations
Manual for definitions of the I/O error codes.
Reference
MOU -- Ambiguous keyword
The abbreviation used for a keyword in the command line was
too short for MOUNT to distinguish it from another keyword.
Reenter the command line, using a longer form of the
keyword.
3-156
MCR COMMANDS
(~
MOU (Cont.)
MOU -- Command input error
An error occurred while MOUNT was attempting to read
command line.
Correct the error condition listed
reenter the command line.
the
and
MOU -- Command syntax error
The command line is not in the proper format. The incorrect
part of the command line is enclosed in brackets. Reenter
the command line, using the correct syntax.
MOU -- Device driver not loaded
The device driver for the specified device is not loaded.
Load the device driver, using the LOAD command, and reenter
the command line.
MOU -- Device not mountable
The specified device cannot be mounted. Some devices do not
require mounting although the media are removable. Verify
that you are using the correct device and reenter the
command line if necessary.
c
MOU -- Device not ready
The specified device returned a device-not-ready status or
failed to respond within approximately 60 seconds. Verify
that you are using the correct device, ready the device, and
reenter the command line.
MOU -- Device status changed during mount
(
The device status for the specified device changed between
the initial device classification and the final setting up
of the data structures.
This is usually the result of
another
user
mounting
or
dismounting
the
volume
simultaneously with the command in error. Verify the device
status and reenter the command line.
MOU -- Failed to allocate sufficient dynamic storage
Mounting a volume may require a significant amount of
primary or secondary pool for data structures and the ACP.
Either MOUNT or the ACP was unable to allocate enough space
in pool. Wait until activity on the system has lessened and
then reenter the command line.
3-157
MCR COMMANDS
(
MOU (Cont.)
MOU -- Failed to start Ancillary Control Processor
The Executive was unable to start the ACP task.
The task
may be exiting or there may not be sufficient resources.
Reenter the command line at a later time.
MOU -- FllMSG not installed
The task FllMSG is not installed.
to install it.
Ask your
system
manager
MOU -- I/O error on device
on
Mount another volume on drive or place on-line to use
A new output volume is being opened and the expiration date
has not been reached. A new volume can be placed on line,
in which case its expiration date is also checked.
If the
same volume or another volume with the same Volume 10 is
placed on line, the volume is overwritten even though it is
not expired.
This message occurs only on volume switching. If a program
is creating a file and specifies the file position of a file
whose expiration date has not been reached, the create
operation terminates with IE.EXP.
xxxxxx -- Mount next volume on drive
The ACP does not know the name of the next volume in the
tape set.
The next volume must be placed on the drive
specified. When this message appears, the action to be
taken depends on whether a program is currently reading or
writing the set as follows:
•
When writing, the ACP accepts any tape that has been
properly initialized.
The expiration date of the
first file on the tape is checked to
verify
overwrite access.
If the write ring is missing when
the tape is placed on line, the program writing to
the tape will receive an error message •
•
When reading, the next volume of the current volume
set must be placed on the drive specified in the
message. The Volume 10 is not checked, but other
consistency checks are made, depending on the type
of read operation currently in progress.
3-162
c
(
MCR COMMANDS
MOU (Coni.)
xxxxxx -- Mount on drive
Place the volume specified in the mess~ge on the drive
indicated.
The ACP knows the name of the volume because
either multiple Volume IDs were specified in the command
line or the ACP has already processed
(and therefore
remembers) the Volume 10 while the tape 'set has been
mounted.
xxx xxx -- Place drive on-line
The next device drive requested in a multivolume,
operation is off line.
multiunit
xxxxxx -- Requested action for drive' not completed
This is a reminder message.
It indicates that a condition
reported in a previous message from xxxxxx has not yet been
taken care of.
xxx xxx -- Requested action for task on drive
not completed/Please complete or abort task
This is a reminder message.
delay.
c
It is displayed
after
a
long
xxx xxx -- Wrong volume mounted on drive
A subsequent volume of a multivolume tape set has been
placed on line, but the ACP does not think it is the correct
volume.
This condition can occur for the following reasons:
•
The, MOUNT command line specified explicit volume IDs
and the volume that should be mounted is not the one
on the drive.
•
The ACP has learned the volume sequence of the
current tape set because of previous processing
while the set has been mounted and the v,olume that
should be mounted is not the one on the drive.
•
The volume on the drive is not in ANSI format.
•
A hardware error prevented the ACP from reading any
of the labels in the label set at the beginning of
the volume.
•
Some other inconsistency in the volume label set has
been encountered.
(
3-163
MCR COMMANDS
c
OPE
3.34
OPENREGISTER (P)
The OPENREGISTER command allows examination and optional modification
of a word of memory.
To open a location within a task, the task must
be fixed in memory.
By default, OPEN displays a location and its contents in octal.
Special control characters allow you to also have the information
displayed in ASCII, Radix-50, double-byte, or decimal format.
To
specify a different format,
type the desired control character
followed by the ESC key. You can do multiple conversions for the same
location on one line. The display remains on the same line until you
open the next location.
You use the same control characters to insert new values into a.
location in ASCII, Radix-50, double-byte, or decimal format.
In this
case, type the desired control character followed by the new value and
then press the RETURN key to insert the new value and open the next
location.
Fo.rmat:
OPE[N] memory-address [+ or - n] [/keyword]
memory-address /contents [control-character] [value] line-terminator
The first line is the OPEN command line. The second line is the
general format in which OPEN displays the contents of the
location. After that, you can display and change the contents in
various formats.
c
memory-address
A 1- to 8-digit octal memory address (location).
+ or - n
One or more optional octal numbers to be added to
from the memory address.
or
subtracted
(
/keyword
One of the keywords defined later in
apply only to mapped systems.
this
text.
The
keywords
control-character
One or more optional special characters used to display values or
insert new values in octal, ASCII, single-character ASCII,
Radix-50, double-byte, or decimal format. The special characters
and their related formats are:
/ - octal (default format)
" - ASCII
- single-character ASCII
% - Radix-50
\ - double-byte
- decimal
3-164
(
MCR COMMANDS
(
OPE (Cont.)
line-terminator
The line terminator directs the subsequent action of OPEN.
Any
value that is entered replaces the contents of the word whose
address and current value are shown in the first part of the
display line. The slash(/) is part of .the display line.
@
ESC or ALTMODE: ESC (or ALTMODE) terminates acceptance
of further
input and is the only exit from the OPEN
command.
If used after a special control character, it
converts the contents of a location from octal to the
desired format.
RETURN:
the next sequential location is opened.
If
used after a special control character and new value
sequence, it inserts the new value in the specified
format into a location.
Circumflex (up-arrow on some
previous location is opened.
c
terminals)/RETURN:
the
*lBDl
or
@ lBDl
Asterisk/RETURN
pointed to by
opened.
or at sign/RETURN:
the
location
the contents of the opened location is
>lBDl
Right-angle bracket/RETURN:
the contents of the open
location is treated as a branch instruction. The
effective address of the branch is the next opened
location.
You cannot supply a value
(modify the
current open location) and close the location with a
right-angle bracket/RETURN.
cKeywords:
/AFF=[CPx,UBy]
(RSX-llM-PLUS
multiprocessor
operating
systems
only.)
Accesses
an address relative to the specified
processor's I/O page.
The square brackets are required
syntax.
/CPU=CPx
c
(RSX-llM-PLUS
only.)
Accesses
partition.
multiprocessor
operating
systems
an address relative to the specified CPU
3-165
MCR COMMANDS
(
OPE (Cont.)
/DRV=dd:
Accesses an address relative to the beginning of
partition
that
contains the loadable driver for
specified device.
the
the
/KNL
Accesses the first 32K of Executive memory.
c
c
/TASK=taskname
Accesses an address relative to the specified task (the task
partition). Note that the task must be fixed.
3-166
MCR COMMANDS
OPE (Cont.)
After accepting the first input line, OPEN finds the
to be accessed by using either:
•
The keyword (in a mapped system)
•
The specified address as the actual address
memory
location
When /DRV, /PAR, /REG, and /TASK are used, the supplied memory address
(a virtual address in the partition) is modified by + or - n. The
absolute address thus formed is used to display the second line shown
in the command format.
In particular, the virtual address (task,
partition, or kernel) and its contents are displayed.
You may then
enter an optional replacement value, followed by a line terminator.
c
c
Examples:
c
3-167
MCR COMMANDS
(
OPE (Cont.)
Command Error Messages:
OPE -- Byte address
The address specified as the argument to
was an odd address.
An even address
(for example, 3000)
is
address (for example, 3001) is illegal.
the
OPEN
legal.
command
An
odd
OPE -- Input I/O error
In attempting to read the next
error.
command,
OPEN
detected
an
OPE -- Invalid address
The address specified as an argument by the OPEN command
referenced a nonexistent memory location, an address outside
of the specified partition, an address outside of the task's
virtual address space, or an address in a task without
instruction and data space.
\
OPE -- Task not fixed
An attempt was made to open a virtual location in a task.
Since the task was not fixed, it mayor may not have been in
memory when you issued the OPEN command.
This message
indicates that the task was not in memory.
3-168
(
MCR COMMANDS
PAR
3.35
PARTITION DEFINITIONS (NP)
The PARTITION DEFINITIONS (PAR) command displays a description of each
memory partition in the system.
c
c
3-169
MCR COMMANDS
PAR (Cont.)
Format:
PAR[TITIONS]
Examples.:
c
c
c
3-170
MCR COMMANDS
(
c
PAR (Cont.) .
MCR COMMANDS
REA
3.36
REASSIGN (P)
The REASSIGN command reassigns a task's logical unit numbers
(LUNs)
from one physical device unit to anotlier. The reassignments affect
only the static assignments recorded in the task's image file on disk.
The command does not affect a memory-resident task.
Hence, REASSIGN
has no effect on the assignments of a currently executing task, or on
the assignments of a task that is fixed in memory.
Format:
REA[SSIGN] taskname lun ddnn:
taskname
The name of the task.
1un
The logical unit number of the task.
ddnn:
The new device unit, which can be a physical, logical, or
device.
pseudo
~ ,
Examples:
>REA TSK1 3 TTO:®ill
Reassigns LUN 3 of task TSK1 to device TTO:.
>REA GNRL 2 TTi:®ill
Reassigns LUN 2 of task GNRL to device TTl:.
>REA TEST 3 XX: ®ill
Reassigns LUN 3 of task TEST to logical device XX:.
Command Error Message:
REA -- LUN out of range
An attempt was made to reassign a LUN that was greater than
the maximum number of LUNs allocated to the task when it was
buil t.
3-172
MCR COMMANDS
(
RED
3.37
REDIRECT (P)
The REDIRECT command redirects all I/O requests previously directed to
one physical device unit to another physical device unit. The
REDIRECT command is especially useful if I/O units required for a task
are not working. The command does not affect any I/O requests already
in the I/O queue.
You cannot redirect the following device units:
•
The pseudo device TI:
(nor can a device be redirected to TI:)
•
An attached device
•
A device unit containing a mounted volume
In addition, you cannot redirect a pseudo device to
you redirect a terminal to the null device.
c
itself,
nor
can
You can redirect a logged-in terminal to a device other than a
terminal
(except for the null device), but it is not generally
advisable to do so because terminal I/O would be written to the device
and that could destroy the boot block.
If you do redirect a terminal
to another type of device, you should redirect the terminal to itself
before you log out.
Format:
RED [IRECT] nddnn:=oddnn:
nddnn:
The new device
directed.
(
unit
to
which
subsequent
requests
will
be
oddnn:
The old device unit from which requests have been redirected.
Example:
>RED TT3:=TT6:@]
Redirects all I/O requests for device TT6: to device
(RED TT6:=TT6:
restores I/O requests for TT6:.)
TT3:.
Command Error Messages:
RED -- Circular redirect error
The attempt to redirect a device would result in a
list of redirections.
circular
RED -- Device not redirectable
An attempt was made to redirect
redirected.
3-173
.a
device
that
cannot
be
MCR COMMANDS
c
RED (Cont.)
RED -- New device not known to system
The new device specified by the REDIRECT command was not
known to the system (did not exist in the device tables).
RED -- Old device attached
An attempt was made to redirect an attached device.
RED -- Old device mounted
An attempt was made to redirect a mounted device.
RED -- Old device not known to system
An attempt was made to redirect an unknown
device did not exist in the device tables).
device
(the
RED -- Pseudd device redirect error
An attempt was made to redirect one pseudo device to another
pseudo device.
RED -- TI redirect error
An attempt was made to redirect the pseudo device TI:.
device cannot be redirected.
RED
~-
This
TT redirect error
An attempt was made to redirect a terminal
device. This combination is not allowed.
to
the
null
c
3-174
MCR COMMANDS
(
REM
3.38
REMOVE (P)
The REMOVE command deletes an entry (a task
Directory
(STD)
and thereby removes the
removal of a task from the system makes the
system.
This action is the complement of
of the task in the system is the task image
name) from the System Task
task from the system.
The
task unrecognizable to the
INSTALL. All that remains
file.
If
REMOVE also checks to see if the task is an initialized CLio
REMOVE issues an error message.
so,
To remove a task that is currently executing, you must first abort the
task.
Format:
REM [OVE] taskname
taskname
The name of the task to be removed.
c
Example:
>REM
SCAN OOJ
Removes the task named SCAN from the system.
file is not deleted.
The task image
Notes:
c
1.
If a task that is the object of a REMOVE command
the command unfixes the task and then removes it.
2.
REMOVE cancels all
specified task.
3.
REMOVE unlinks a task from all ICS/ICR interrupts.
4.
REMOVE deallocates all receive-by-reference and receive-data
packets for the task and detaches all attached regions.
(See
the RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual
for more information:)
time-based
3-175
schedule
requests
is
fixed,
for
the
MCR COMMANDS
(
REM (Cont.)
Command Error Message:
REM -- CLI in use
An attempt was made to remove a CLI that was still active.
Before a CLI can be removed, its CPB must be eliminated with
the CLI command.
(
c
3-176
MCR COMMANDS
(
RES
3.39
RESUME (NP,P)
The RESUME command continues execution of a previously suspended task.
A nonprivileged user can issue the RESUME command only for tasks
initiated from the issuing terminal. A privileged user can direct the
RESUME command to any suspended task.
Format:
RES [UME] taskname [/TERM=ttnnn:]
taskname
The name of the task to be resumed.
If you omit the task name,
the command attemp.ts to resume task TTnn (where nn is the octal
unit number of the issuing terminal).
Example:
)RES RX7
(
~
Resumes task RX7.
Note:
A task cannot suspend any task other than itself.
command allows such a suspended task to proceed.
The
RESUME
Command Error Message:
RES -- Task not suspended
(
The task specified
suspended.
in
the
3-177
RESUME
command
line
was
not
MCR COMMANDS
RUN
3.40
(
RUN (NP,P)
The RUN command initiates the execution of a task.
cause a task to be:
•
•
•
•
•
The
command
can
Run immediately (NP)
Run at a time increment from now (P)
Run at a time increment from clock unit synchronization (P)
Run at an absolute time of day (P)
Installed, immediately run, and removed on exit (NP)
All of these options, except
with or without rescheduling.
install-run-and-remove,
are
available
Formats:
RUN has five format variations.
1.
Run immediately (nonprivileged option).
RUN taskname [/UIC=[g,m]]
c
taskname
A 1- to 6-character task name.
/EST=option
Specifies whether exit status is to be returned from the
RUN command or from the task being run with the RUN
command. The options are YES and NO.
If you specify
EST=YES, the exit status returned from the RUN command
is the status of the task being run. RUN waits for the
task to emit status and returns that status.
If you
specify EST=NO, the exit status returned from the RUN
command is the status of the command only. RUN does not
wait for the task to emit status.
It returns status
indicating
only
whether
the
task was initiated
successfully.
The default is /EST=NO.
/Ule
(Privileged option on multiuser systems only.)
The Ule
under which the task will be requested to run. This Ule
also determines which files the task can access.
3-178
(
MCR COMMANDS
(
RUN (Cont.)
The UIC has the format [g,m], where g and m represent
the group and member numbers, respectively. Legal group
and member numbers range from 1 to 377(octal).
The
square brackets are required syntax.
When you use JUIC, RUN locates the task image file in
the specified UIC (on device SY:) and runs the task from
that UIC. The specified UIC also becomes the default
and protection UICs for the task.
When you do not use JUIC, RUN looks for the task image
file in the System Task Directory (STD) to see if the
task is already installed.
If RUN finds the task,
it
proceeds to run it.
If RUN does not find the task, it
looks for the file in the UIC (on device SY:)
to which
the terminal requesting the task is set, .and then
installs and runs the task. The terminal's UIC becomes
the default and protection UICs for the task.
Note that on mapped systems, you can request a task to
run that is not in the STD. MCR invokes a catchall task
to install and run the uninstalled task.
See the
RSX-IIMjS Release Notes or the RSX-IIM-PLUS Release
Notes for information about the catchall task.
See the description of JUIC under Format 5 for
by nonprivileged users and tasks.
c
The default is the UIC of the terminal that
RUN command (jUIC is not specified).
2.
its
use
issued
the
Run at a time increment from now (privileged option).
RUN taskname dtime [jRSI=magu] [jUIC=[g,m]]
taskname
A 1- to 6-character task name.
(
dtime
The time at which the task will be initiated in time
units
from command issuance.
This time parameter
consists of two fields: a magnitude field and a units
field.
The parameter is in the form magu where mag is
the magnitude and u is one of the following time units:
T, S, M, or H.
The magnitude is the number of units to be clocked.
It
cannot exceed 24 hours in the specified unit and is
decimal by default.
The unit fields are T, S, M, and H:
T
Ticks. A tick is a clock interrupt.
The rate
at which interrupts occur depends on the type of
clock installed in the system.
For a line
frequency clock,. the tick rate is either 50 or
3-179
MCR COMMANDS
(
RUN (Cont.)
60 per second, depending on the line frequency.
For a programmable clock, a maximum of 1000
ticks per second is available. The frequency is
selected at system generation.
T can be any positive value from 0 to a
length of 15 bits.
maximum
S
Seconds. S can be any positive value from 0
a maximum length of 15 bits.
to
Minutes. M can be any positive value from 0
1440 (decimal) •
to
Hours. H can be any positive value. from
24(decimal).
to
M
H
0
/RSI
The reschedule interval. The format is the same as for
dtime.
The reschedule interval specifies how often the
task is to be rerun.
Thus, each time the specified
interval of time lapses, an initiation request is made
for the specified task.
If the magnitude is equal to
reschedule interval is set to 1.
the same as specifying /RSI=lH.
o (zero), then the
Specifying /RSI=OH is
Note that the CANCEL and
effect of this keyword.
commands
REMOVE
negate
the
c
The default is no rescheduling.
/UIC
See Format 1.
3.
Run at a time increment
(privileged option).
from . clock
unit .synchronization
The system determines the task start-time by waiting for the
first specified time unit
(hour, minute, second, tick) to
increment and then waiting for the specified time to elapse.
RUN taskname sync [dtime] [/RSI=magu] [UIC=[uic]]
taskname
A 1- to 6-character task name.
3-180
MCR COMMANDS
(
RUN (Cont.)
sync
H
M
S
T
-
Synchronize
Synchronize
Synchronize
Synchronize
on
on
on
on
the
the
the
the
next
next
next
next
hour
minute
second
tick
dtime
See Format· 2.
If present, dtime is added to the
synchronization unit to produce the actual run time for
running the task.
IRSI
See Format 2.
IUIC
See Format 1.
4.
Run at an absolute time of day (privileged option).
RUN taskname atime [/RSI=magu] [jUIC= [uic] ]
taskname
c
A 1- to 6-charactertask name.
atime
Absolute time of day at which
Input format is hh:mm:ss.
to
initiate
this
task.
hh - Hours (decimal assumed)
mm - Minutes (decimal assumed)
ss - Seconds (decimal assumed)
c
IRSI
See Format 2.
IUIC
See Format 1.
5.
Install, run immediately, and remove on exit.
RUN [ddnn:] [$] filename [jkeyword (s)
f
ddnn:
The device unit on which the task image file resides.
$
Specifies that the file can be found in the System Task
Directory on device LB: (if ddnn: is not specified).
3-181
MCR COMMANDS
(
RUN (Cont.)
The SgT jSYSUIC command defines the system directory.
By convention, the directory is [1,50] on an unmapped
system and [1,54] on a mapped system.
If you do not specify $, RUN searches for the task image
file in the UIC (on device SY:) to which the terminal
requesting the task is set.
(This is similar to Format
1 when JUIC is not specified.)
Note that if LB: has been reassigned to another device
and that device's system UIC contains privileged tasks
built for another system, your system will crash.
filename
The name of the task image file to be run.
Keywords:
jCKP=option
Specifies whether or
not
a
task
will
be
checkpointable.
The options are YES and NO.
If
you specify jCKP=YES
(default for checkpointable
tasks), checkpointing is allowed.
If you specify
jCKP=NO, checkpointing is disabled for the task.
(
The jCKP keyword overrides the jCP switch specified
at task build.
On systems that support the dynamic allocation of
checkpoint space, the task image file does not need
to contain allocated
checkpoint
space.
The
presence of the jCKP=YES keyword instructs the
system to allocate checkpoint space for the task
when required from a checkpoint file.
jCMD="command-line"
Passes the specified command line to the task for
processing.
The command line must begin with the
task's acronym and it must be valid for the task
(for example,
if the task being installed is MAC,
"command-line" must be a valid MACRO-ll command
line)
or a syntax error will occur. When the task
has finished executing the command line, the task
is removed.
/EST=option
Specifies whether exit status is to be returned
from the RUN command or from the task being run
with the RUN command. The options are YES and NO.
If you specify EST=YES, the exit status returned
from the RUN command is the status of the task
3-182
(
MCR COMMANDS
(
RUN (Cont.)
being run.
RUN waits for the task to emit status
and returns that status.
If you specify EST=NO,
the exit status returned from the RUN command is
the status of the command only. RUN does not wait
for the task to emit status.
It returns status
indicating only whether the task was initiated
successfully.
The default is /EST=YES.
/INC=size
Increments the address space allocated to a task
The
that runs in a system-controlled partition.
variable size is the number of additional words of
address
space to allocate.
The increment is
usually expressed in octal, but can also
be
expressed in decimal by appending a period.
This keyword overrides the EXTTSK or PAR option
used ai task-build time.
Tasks that specify the
size of the partition in which they are running use
this keyword to identify how much dynamic space
they may allocate to symbol tables or buffers.
Tasks such,as MAC,TKB, VFY, and AT. use the space
from the end of the task image to the end of their
address space as dynamic memory.
In effect, the
/INC keyword defines the number of words in this
dynamic region.
On RSX-llM/M-PLUS systems, you cannot extend a task
that
uses memory-resident overlays.
(See the
RSX-llM/M-PLUS and Micro/RSX Task Builder Manual.)
The default is the
time.
c
size
specified
at
task-build
/IOP=option
Specifies that a privileged task can overmap the
I/O page.
The options are YES and NO.
If you
specify /IOP=YES, RUN assumes that the task will
overmap the I/O page
(APR7) and, if the task is
larger than 8K words, issues a warning message.
If
you specify /IOP=NO, RUN assumes that the task does
not need to use the I/O page. No warning message
is issued.
/IOP complements the Task Builder /IP switch.
Specifying
/IP informs RUN that the task is
intentionally overmapping the I/O page.
The default is /IOP=YES.
/PAR=parname
Specifies the partition in which the task is to
installed.
The default is
task-build time.
3-183
the
partition
specified
be
at
MCR COMMANDS
(!
RUN (Cont.)
/PMD=option
Requests a Postmortem Dump when the task aborts.
The options are YES, and NO.
If you specify
/PMD=YES, a Postmortem Dump is requested for the
task
if
it aborts because of an SST error
condition. If you specify /PMD=NO, no dump is
requested at SST abort time.
To generate a dump, the Postmortem Dump task PMD •••
must be installed in the system. This keyword
overrides the /PM switch specified at task-build
time.
The default is specified at task-build time.
/PRI=number
(Privileged keyword.) Specifies the priority of the
task.
The value range is 1 to 250 (decimal) , where
250 is the highest priority.
Standard number
conventions apply:
octal by default, decimal if
followed by a period.
(This keyword is ignored i f
specified by a nonprivileged user.)
The default is /PRI=50.
c
/SLV=option
Specifies the slave status of the task.
The two
options are YES and NO.
If /SLV=YES, data sent to
the installed task is marked with the TI:
of the
sending task. When the installed task receives the
data, the system sets the task's TI:
to ,that
associated with the data. This keyword overrides
the /SL switch that was specified at task build.
I f /SLV=NO, the TI:of the task
when receiving data.
does
not
change
The default is specified at task-build time.
/TASK=taskname
Specifies the name the task will use while it is
running. This name is a temporary assignment only.
If taskname is not found in the STD, MCR names it
TTnn by default, where nn is the unit number of the
requesting terminal~
3-184
MCR COMMANDS
RUN (Cont.)
jurc= [g ,m]
Sp~cifies
the urc under which the task will be
requested to run. The square brackets are required
syntax.
rf you specify a urc, the urc becomes the default
urc for the task.
However, your protection urc
becomes the protection urc for the task.
rf you do
not specify a urc, your default and protection urcs
become the default and protection urcs for the
task.
(See the previous description of jUrC for
the effects for privileged users and tasks.)
(
The default is the urc of the terminal that
the RUN command.
issues
Examples:
)RUN .TR7 15M ffil
(
Runs task TR7 15 minutes
issued.
from
the
time
the
command
was
)RUN XKE 15MjRSr=90SjUrC=[3,1]ffil
Runs task XKE 15 minutes from the time the command was
issued, rescheduling it every 90 seconds, with a urc of
[3,1] •
)RUN DK2: $MAC ffil
Runs the task in file DK2:MAC.TSK from the system directory.
The task is automatically installed, run, and removed on
exit.
Notes:
•
rf the command requests the task to run immediately (Format
1), it establishes the terminal from which the task was
initiated as the pseudo device Tr:. For Formats 2, 3, and 4,
the system establishes the issuing terminal as the pseudo
device CO:.
3-185
MCR COMMANDS
c
RUN (Cont.)
•
A run-immediately command (Format 1), if terminated with an
ESC character instead of a RETURN, echoes the default prompt
when the requested task exits and not when MCR has finished
initiating the task. This facility enables you to determine
when a task that is not producing output on a terminal has
exited.
•
The install-run-remove format (Format 5) also establishes the
terminal from which the command was issued as the pseudo
device TI: and causes the default prompt to be displayed on
TI:
when the task exits.
This form of the command is
especially useful when the space available in the dynamic
storage region (pool) is low because the memory necessary for
a Task Control Block (TCB)
returns to pool when the task
exits.
Command Error Messages:
RUN
Invalid time parameter
A specified time field was incorrect.
RUN
Task being aborted
A request for the execution of a task was made, but the task
was being aborted either because of an unrecoverable error
or an abort command ,or directive issued by a user.
(
RUN -- Task may not be run
The task you have specified cannot be executed
the following reasons:
•
for
one
of
You specified a task with the ••• tsk form of the task
name.
The ••• tsk form of a task name identifies a task
that was installed with a prototype TCB. Thus, the task
cannot be run.
Instead, specify only the 3-character
task name (tsk); or install and run the task under a
different name (such as tskTnn).
•
You specified a task with the tsk$$$ form of the task
name.
The tsk$$$ form of a task name identifies a
special network task. Such tasks cannot be run.
•
You specified a task that is installed
tasks cannot be run.
•
The RUN command encountered a spawn failure when it tried
to spawn the specified task.
3-186
as
a
CLI.
CLI
(
MCR COMMANDS
(
SAY
3.41
SAVE (P)
The SAVE command copies the current RSX-llM/M-PLUS operating system
image
(the contents of main memory) into the system image file from
which the current image was booted.
(The system image file is a
special task image file named, by convention, RSXllM.SYS.)
The
command saves the image so that a hardware bootstrap or the BOOT
command can later be used to reload and restart it.
All RSX-llM/M-PLUS system images reside on a file-structured volume as
a specially formatted task image:
the image does not have a task
header. There may be more than one system image on a volume (for
example, a program development system and a production or test
system), and nonprivileged tasks can be installed in several system
images at the same time.
(
To determine the minimum size for a system image file, compute the
formula of four times the size plus two (4*SYSIZ+2). For example:
28K requires 114.
blocks
32K requires 130.
blocks
l24K requires 498.
blocks
256K requires 1026.
c
blocks
You can save system images on any of the following devices:
3-187
MCR COMMANDS
c
SAY (Cont.)
To successfully save a system, the SAVE command requires that:
•
Error logging is.not active.
•
All tasks must be installed from LB:.
•
No checkpoint files are active.
•
No volumes except the load device are mounted.
•
The load device can be successfully dismounted.
•
No tasks have outstanding I/O.
•
No tasks are connected to interrupts.
•
All drivers, active tasks, fixed tasks and, on RSX-llM-PLUS
operating systems, all loaded commons and secondary pool
reside within the amount of main memory that SAVE will write
to the system image file.
(
(
An error is reported if any of these requirements are not met.
SAVE is active when the memory-resident system image is copied to
disk. Because of this, VMR considers SAVE to be an active task in the
system image. This is correct because SAVE is the task that sta:rts
the system after a boot.
The Executive references the file images of installed tasks by
physical addresses
(logical block numbers, or LBNs). A saved system
does not always retain the physical disk addresses of installed tasks.
For example, the Disk Save and Compress Utility Program (DSC) can
3-188
MCR COMMANDS
(
SAY (Cont.)
compress and copy a disk containing a saved system,
thus movipg the
task files to different physical locations. Therefore, SAVE converts
the LBNs of all installed tasks into file identifications and stores
these
in the TCBs.
Since the TCB entries contain task file
identifications rather than LBNs after a system save, the system can
function normally when it is rebooted even if LBNs have changed in the
meantime.
Upon system rebooting, SAVE reopens the task file and stores the new
LBN of the task in the TCB.
If a task has been deleted, the system
cannot open the task file when the system is rebooted.
In this case,
the system automatically removes the task's TCB from the STD.
When the bootstrap block is written, the physical disk-block address
of the system image file is stored with it.
However, the file can be
deleted.
If there is file system activity, the blocks previously
allocated to the system image may be reallocated to another file.
A
subsequent bootstrap that uses the boot block could possibly cause
random data to be loaded.
Upon rebooting a saved system, SAVE:
•
Selects the system clock
•
If the last memory partition is system-controlled, sizes
memory and extends the partition so that it uses all available
memory
•
On multiuser protection systems, validates that
device is not allocated and then sets it public
•
Sets the context of the
privileged, and nons laved
•
Outputs a system identification message
•
Redirects all pseudo devices to the boot device
•
Mounts the system disk
•
Initiates the file [1,2]STARTUP.CMD on the booted device
(
console
Format:
SAV[E]
[/keyword(s)]
3-189
terminal
as
the
logged
boot
in,
MCR COMMANDS
c
SAY (Cont.)
Keywords :.
/WB
Indicates that a hardware boot block pointing to the system
image is to be written to the system device. The new boot
block points to the file that is saved with the SAVE
command.
Thus, on the next hardware bootstrap, this saved
file will be loaded. If the command line omits the /WB
keyword, the boot block still points to the prior system
image, which may have been overwritten.
/MOU="string"
Automatically issues a MOUNT command at
mount the sy.stem disk.
system
startup
to
The MOUNT command line ("string") that you specify must be
enclosed within quotes and must be in the proper format
(that is, including all necessary slashes (/) or equal signs
(=».
Note that SAVE does not check the syntax of the
string.
/SFILE="filespec"
Automatically
initiates
an
indirect
command
file
([l,2]STARTUP.CMD)
on the boot device at system startup.
This keyword allows you to specify another indirect command
file.
(
The command file you specify must be enclosed within quotes.
Note that SAVE does not check the syntax of filespec.
c
3-190
MCR COMMANDS
(
SAY (Cont.)
Example:
>SAV (BDJ
The current status of the system is saved on the system
disk.
System changes made by the REDIRECT command or other
MCR commands are also saved with the system image that is
resident in main memory.
Command Error Messages
(Error messages that apply only to RSX-11M-PLUS operating systems
are described last):
SAV -- Bad task file VBN, task removed -
SAVE removed the specified task because it contained ~ bad
virtual block number
(VBN)
in its file header. The task
image file has probably been corrupted.
SAV -- Booted device's driver not loaded
VMR has been used to unload the driver for the system
(booted) disk.
Using another system, use VMR to load the
driver and then reboot the system.
(
SAV -- Booted device not in system -
When the system was booted, SAVE could not find the booted
device
(device name dd, physical unit number nnn, CSR
mmmmmm) in the system data structures.
For example, the
system was booted from DB3:, but the system data structures
include only DBO: and DB1:.
On RSX-l1M-PLUS multiprocessor operating systems, the boot
device must be directly connected to the target processor;
it cannot be connected by a bus switch.
SAV -- Cannot find home block
SAV could not find the device's home block when searching
for it or, on RSX-llM-PLUS operating systems, an error
occurred while SAV was attempting to read the home block.
SAV -- Checkpoint file still in use on
The system cannot be saved because a checkpoint~,ile on the
specified device is still active. Deallocate the checkpoint
file (see the ACS command) and reenter the SAVE command
line.
3-191
MCR COMMANDS
(
SAV (Cont.)
SAV
Common, driver or task above system image file limit
A system cannot be saved if addresses for a memory-resident
structure are higher than the highest address of main memory
written to the system image file.
Use the PARTITION
DEFINITIONS command
(PAR)
to determine the cause of the
problem.
This iricludes the running task image of SAVE.
SAV -- Dismount complete for
This is an informational message.
The message indicates
that TKTN is not installed in the running system.
If the
load device is mounted when SAVE starts, SAVE attempts to
dismount it.
Since TKTN is not installed, the dismount
complete message from DMO is not displayed on the console
terminal.
As a substitute, SAVE writes this message to the
terminal.
SAV -- Error attempting to dismount
If the load device is mounted when SAVE is initiated, SAVE
issues a DISMOUNT command to MCR when the save operation is
complete.
This message indicates
that
the
dismount
operation was not successful.
The system may be usable, but
it is recommended that you reboot and issue a DISMOUNT
command.
SAV
Error logging still active
(
A system cannot be saved while error logging is active.
Disable error logging and reenter the SAVE command line.
SAV -- Index file header checksum error
(
While rebooting a saved system, SAVE detected a checksum
The error
error in the file header of the index file.
causes the system to halt.
The disk has probably been
corrupted.
SAV -- Index file header read error
While rebooting a saved system, SAVE detected an error in
the file header of the index file.
The error causes the
system to halt.
SAV -- Label block I/O error
In attempting to save the system image, SAVE wrote the
transfer address in the label block of the system image
file.
An error occurred during this write attempt.
The
disk could be corrupted.
3-192
(
MCR COMMANDS
(
SAY (Cont.)
SAV -- MeR is not installed
When a system is booted, SAVE uses MeR to mount
disk. Use VMR to install the MeR ••• task.
the
system
SAV -- No pool space
There is not enough space in pool to contain checkpoint
information when SAVE tries to force resident read/write
commons to their file images.
SAV -- Not a valid save device
An attempt was made to- save a system on a device that is not
part of the system I/O data structures (this generally
implies that $SYSIZ+2 and $SYSIZ+6 are corrupted)
or SAVE
does not support the device.
SAV -- Open file(s) on
c
There are open files
Manager is stopped.
ori
ddnn:.
Ensure
that
the
Queue
c
SAV -- System may not boot correctly
The file [system-uic]SAV.TSK was not found on the boot
device.
If SAVE must be checkpointed to redirect and mount
the booted device, the system disk will be overwritten,
causing unpredictable results.
SAV -- System may not work - Larger than main memory
This message indicates that the booted system has less main
memory than the saved system image file and that a structure
resident in the system image file is completely or partially
absent in the booted system. If the system can run without
the structure, the UNLOAD and UNFIX commands can be used to
remove the rio'nexistent structures.
3-193
MCR COMMANDS
(
SAY (Cont.)
SAV -- $SYSIZ does not point at system image file
SAVE determines the location of the system image file on the
system disk by examining the locations near the Executive
label $SYSIZ. SAVE then makes several validation checks on
that file.
If those checks fail, SAVE does not write to the
disk on the assumption that it could corrupt the disk by
writing to something that is not a system image file.
The
system image or the system image file has been corrupted.
Examine several locations after $SYSIZ and then reboot.
SAV -- Task active in another system, task removed -
The task is installed in another system as well as in the
booted system.
Since the task is active and mapped to
dynamic regions in the other system, it cannot be run in the
booted system.
SAV -- Task file deleted, task removed -
While rebooting a saved system, a file identification that
appears in the Task Control Block (TCB) could not be found
in the index file on the boot device.
This indicates that
the file has been deleted.
SAV -- Task file header error, task removed -
When SAVE read the task header to restore the LBN of the
task file,
the checksum was bad or there was a file number
mismatch. Therefore, the task was removed.
(
SAV -- Task file header read error, task removed -
SAVE removed the specified task because it
the task's file header.
could
not
read
SAV -- Task file header write error, task removed -
When SAVE attempted to reassign the LUNs of the task or to
rewrite
a
mapping window PCB address,
it could not
successfully rewrite the task header.
Therefore,
the task
was removed.
c
SAV -- Task header read error
SAVE detected an I/O error while reading in a task header to
write the file identification into the TCB. This error
causes the system to halt.
SAV -- Task header read error, task removed -
SAVE detected an I/O error while reading in a task header to
reassign LUNs or to remap the mapping windows.
Therefore,
the task was removed.
SAV -- Task label block read error, task removed -
When SAVE attempted to reassign the LUNs of the task to the
current system, the task's label block could not be read
(the label block contains the static LUN assignments).
Therefore, the task was removed.
3-194
(
MCR COMMANDS
SAV(Cont.)
SAV -- Task too big for partition, task removed -
The current CPU has less memory than the system image file.
This
message
indicates
that the last partition has
contracted such that the indicated task cannot fit into it,
even if everything else is removed from the partition.
SAV
Task has outstanding I/O
A system cannot be saved if a task is
complete.
waiting
for
I/O
to
SAV -- Task is active and checkpointed
You cannot save a system if it contains an active and
checkpointed task.
This restriction prevents a possible
system crash because, if the task was installed in another
system image file,
the task image could be corrupted when
the task was run in the second system.
SAV -- Task is connected to an interrupt vector
Disconnect the task from the interrupt vector or
and reenter the SAVE command line.
c
abort
it,
SAV -- Task not installed from an LB:
All tasks must be installed from an LB:.
Use the TAS
command to determine which tasks are not. Reenter the SAVE
command line after removing the tasks or installing them
from an LB:.
SAV -- Volume still mounted on
c
The volume on device ddnn: was still mounted when the SAVE
command line was issued.
A system cannot be saved with
volumes mounted. Dismount the volumes and reenter the SAVE
command line.
If necessary, use the DEVICES command to
determine which volumes are mounted.
SAV -- Volume structure not supported
While rebooting a saved system, SAVE determined from the
disk's home block that the disk's structure is not supported
by the current version of RSX-llM/M-PLUS. This error causes
the system to halt.
SAV -- (Warning) Nonexistent LUN assignment for task
The physical device to which SAVE was attempting to reassign
a LUN does not exist in the booted system. This condition
is resolved if the task p'erforms a run-time assignment to
the LUN; otherwise, the task will encounter an error
condition when it attempts to use the LUN.
Additional RSX-llM-PLUS Operating System Command Error Messages:
SAV -- Accounting is active
SAVE cannot save a system if Resource
active.
3-195
Accounting
is
still
MCR COMMANl>S
SAY (Cont.)
c
(
(3-196
MCR COMMANDS
(
SET
3.42
SET (NP,P)
The SET command dynamically changes characteristics
information about the system, tasks, and devices.
of
and
displays
Nonprivileged users can change the characteristics of their own
terminals
(pseudo device TI:)
and any privately allocated device.
Privileged users can change the characteristics of any device and also
of any task and of the system. All users can display information
about any device or task or about the system.
The following two lists describe most of
nonprivileged and privileged users.
the
available
options
for
(TI:)
and
Nonprivileged options:
•
Establish characteristics for the issuing terminal
for private devices
•
Set the default UIC for the issuing terminal
•
Display the status (determined by the
all terminals and other devices
•
Display statistics about system dynamic memory
keyword
specified)
of
(
Privileged options:
c
•
Establish characteristics for any device in the system
•
Establish the default UIC for any terminal in the system
•
Establish the default directory for DECnet-related tasks
•
Establish the system UIC
•
Set a device to public status so
access the device
•
Create partitions and subpartitions
•
Move the top boundary of a partition
•
Add space to the dynamic core pool
•
Modify the pool limit parameters used by the Pool Monitor Task
•
Enable write check on devices that support it
3-197
that
any
system
user
can
MCR COMMANDS
(
SET (Cont.)
•
Specify the maximum number of I/O packets to
to optimize I/O performance
•
Specify the maximum size to which a task can extend itself
•
Enable or disable the ability to log
multiuser protection system
in
on
be
preallocated
terminals
in
a
Improper use of the SET command from a privileged terminal can result
in a situation in which privileged user input will not be accepted.
Avoid the following two situations:
•
All privileged terminals in ~he system are slaved and cannot
enter unsolicited input to MCR, and logins are disabled.
Nonprivileged terminals cannot enter privileged commands and
therefore
cannot
reset the privileged terminals to be
nonslaved. See the description of the /SLAVE keyword in the
"Keywords" section.
•
The buffer length of all the nonslaved, privileged terminals
is shorter than 14 (decimal) bytes.
In this case, the terminal
buffer is then too small for a privileged user to enter many
important commands required to continue system operation or to
alter the status of other terminals. See the description of
the /BUF keyword in the "Keywords" section.
Also, some keywords
(for example, /ABAUD, /FDX, /HHT,
/LINES,
/TYPEAHEAD, and /WRAP)
are supported only with the full-duplex
terminal driver.
The full-duplex terminal driver is a
system
generation option on RSX-llM operating systems but is always included
on RSX-llM-PLUS systems. Note that if you select the full-duplex
driver on an RSX-llM system, you must also select the get/set multiple
characteristics option to display or set
any
terminal-related
characteristics.
(
(
Note: You can also use any DCL SET command from MCR.
Refer to the
RSX-llM or· the RSX-llM-PLUS Command Language Manual for information
about DCL commands.
Format:
SET /keyword=values
Only one keyword per command line is permitted. You can
keywords with NO to negate or disable the function of
(Exceptions are noted in Table 3-2. The system returns a
message whenever NO precedes one of these keywords.)
The
described in alphabetical order following Table 3-2.
prefix most
the keyword.
syntax error
keywords are
l
3-198
MCR COMMANDS
SET (Cont.)
Table 3-2
SET Keywords
Keywords
Type
Console
Output Task
/COLOG
Device
Characteristics
/[NO]ABAUD[=ttnn:]
/[NO]ANSI[=ttnn:]
/ [NO] AVO [=ttnn:]
/[NO]BLKMOD[=ttnn:]
/ [NO] BRO [=ttnn:]
/BUF=ddnn:[~ize]
c
/CLI=ttnn: [cli]
/[NO]CRT[=ttnn:]
/DCL [=ttnn:]
/ [NO]DEC [=ttnn:]
c
/ [NO] EBC [=ttnn:]
/[NO]ECHO[=ttnn:]
/[NO]EDIT[=ttnn:]
/[NO]ESCSEQ[=ttrin:]
/[NO]FDX[=ttnn:]
/[NO]FORMFEED[=ttnn:]
/HFILL=ttnn:[value]
/[NO]HHT[=ttnn:]
/[NO]HOLD[=ttnn:]
/[NO]HSYNC[=ttnn:]
. (Continued on next page)
3-199
MCR COMMANDS
(
SET (Cont.)
Table 3-2 (Cant.)
SET Keywords
Keywords
Type
/INQUIRE
/LINES=ttnn:[value]
/[NO]LOWER[=ddnn:]
/MCR[=ttnn:]
/[NO]PARITY[=ttnn: [option]]
/[NO]PASTHRU[=ttnn:]
/[NO] PRINTER_PORT [=ttnn:]
/[NO]PRIV[=ttnn:]
/[NO]PUB[=ddnn:]
/[NO]REGIS[=ttnn:]
/[NO] REMOTE [=ttnn: [speed]]
/[NO]RPA[=ttnn:]
/[NO]SLAVE[=ttnn:]
/[NO]SOFT[=ttnn:]
/SPEED=ttnn:[recv:xmit]
/TERM=ttnn:[value]
/[NO]TTSYNC[=ttnn:]
/ [NO] TYPEAHEAD [=ttnn: [sizell
/UIC[=[uic] [:ttnn:]]
/[NO]VFILL[=ttnn:]
/[NO]WCHK[=ddnn:]
(Continued on next page)
3-200
l
MCR COMMANDS
(
SET (Cont.)
Table 3-2 (Cont.)
SET Keywords
Type
Keywords
/[NO]WRAP[=ttnn:]
Enable/Disable
Login
(pri vileged
options)
/[NO]LOGON
I/O Packet
/MAXPKT [=n]
c-
/NETUIC[=[uic]]
/SYSUIC[=[uic]]
Memory
Allocation
(see notes
before error
messages)
c
/MAIN=pname[:base:size:type]
(RSX-llM systems; synonym for
/PAR on RSX-llM-PLUS systems)
/NOMAIN=pname
(RSX-llM systems; synonym for
/NOPAR on RSX-llM-PLUS systems)
/MAXEXT[=size]
/POOL[=top]
(Continued on next page)
3-201
MCR COMMANDS
(
SET (Cont.)
Table 3-2 (Cont.)
SET Keywords
Keywords
Type
/TOP=pname:value
Networking
/HOST[=node[::]]
Pool
Monitor Task
/PLCTL [= [high] [: [low] [: [frz] [: [basep]]]]
System
Tuning
/RNDC [=nn]
/RNDH [=nn]
/RNDL [=nn]
/SWPC [=nn]
/SWPR [=nn]
Keywords:
(
/ABAUD[=ttnn:]
(Full-duplex terminal
driver
only.)
Enables
autobaud
detection for the remote dial-up line for the specified
terminal. The terminal driver samples the line's first
input character, tries to determine the incoming baud rate,
and sets the interface speed accordingly.
A nonprivileged user can display all the terminals that have
autobaud detection enabled, but only a privileged user can
enable the option for a specific terminal.
When you omit =ttnn:,
the system displays all
terminals that have autobaud detection enabled.
of
the
Examples:
>SET
/ABAUD=TT10:~
Enables autobaud detection for TT10:.
>SET /ABAUD
ABAUD=TT4 :
. ABAUD=TT 5:
ABAUD=TT6:
ABAUD=TT10:
~
Displays all
terminals
detection enabled.
3-202
that
have
autobaud
(
MCR COMMANDS
c
SET (Cont.)
INOABAUD[=ttnn:]
(Full-duplex terminal driver
only.)
Disables
autobaud
detection for the specified terminal.
The terminal driver
does not attempt to determine the incoming baud rate for the
remote dial-up line.
A nonprivileged user can display all of the terminals that
have had autobaud detection disabled, but only a privileged
user can disable the option for a specific terminal.
When you omit =ttnn:, the system displays
terminals that do not have autobaud detection.
all
of
the
Examples:
>SET
INOABAUD=TT6:~
Disables autobaud detection for TT6:.
>SET INOABAUD
NOABAUD=COO:
NOABAUD=TT4:
NOABAUD=TT6:
NOABAUD=TT7:
~
Displays all terminals that do not
detection enabled.
(
have
autobaud
IANSI [=ttnn:]
(Full-duplex terminal driver only.) Informs the system that
the
specified
terminal supports ANSI standard escape
sequences.
When you omit =ttnn:,
the system displays all of the
terminals that support the ANSI standard escapest:quences.
(
Examples:
>SET
IANSI=TT10:~
Enables support of ANSI standard escape
for TT10:.
>SET IANSI
ANSI=TT6:
ANSI=TT10:
ANSI=RT7:
sequences
~
Displays all terminals that support ANSI
escape sequences.
standard
INOANSI [=ttnn:]
(Full-duplex terminal driver only.) Informs the system that
the specified terminal does not support ANSI standard escape
sequences.
3-203
MCR COMMANDS
(
SET (Cont.)
When you omit =ttnn:, the system displays all of the
terminals that do not support the ANSI standard escape
sequences .,
Examples:
>SET INOANSI=TTS:@ill
Disables support of ANSI standard escape sequences
for TTS:.
>SET INOANSI @ill
NOANSI=COO:
NOANSI=TTS:
NOANSI=HT8:
Displays all terminals that do
standard escape sequences.
not
support
ANSI
IAVO [=ttnn:]
(Full-duplex terminal driver only.)
Specifies
that
a
VT100-series terminal has the advanced video option. This
option enables the terminal to blink, bold, and flash parts
of the screen, and to set the screen at 132(decimal)
columns. If the word SET-UP blinks in set-up mode, the
terminal has the advanced video option. See your system
manager for more information.
When you omit =ttnn:, the system displays
terminals that have the advanced video option.
all
of
(
the
Examples:
>SET IAVO=TT7:@ill
Enables the advanced video option onTT7:.
c
>SET IAVO @ill
AVO=TT7:
AVO=TT13:
AVO=RT27:
Displays all of the
advanced video option.
terminals
that
have
the
INOAVO [=ttnn:]
(Full-duplex terminal driver only.) Disables
video option for the specified terminal.
the
advanced
When you omit =ttnn:, the system displays all of
terminals that do not have the advanced video option.
Examples:
>SET INOAVO=TTS:
Disables the advanced video option for TTS:.
3-204
the
MCR COMMANDS
(
SET (Cont.)
>SET /NOAVO 00l
NOAVO=TT5:
NOAVO=TT15:
NOAVO=TT25:
Displays all of the terminals without the advanced
video option.
/BLKMOD [=ttnn:]
(Full-duplex terminal driver only.)
Enables local editing
and block-mode transmission for the specified terminal.
When you omit =ttnn:,
the system displays all
terminals that have the block-mode option enabled.
of
the
have
the
Examples:
>SET /BLKMOD=TT3:00l
Enables the block-mode option for TT3:.
>SET /BLKMOD 00l
BLKMOD=TT3:
BLKMOD=TT17:
BLKMOD=RT23:
Displays all of the terminals
block-mode option enabled.
that
/NOBLKMOD[=ttnn:]
(Full-duplex terminal driver only.) Disables local editing
and block-mode transmission for the specified terminal.
When you omit =ttnn:,
the system' displays all
terminals that have the block-mode option disabled.
(
of
the
have
the
Examples:
>SET /NOBLKMOD=TT3:00l
Disables the block-mode option for TT3:.
>SET /NOBLKMOD 00l
NOBLKMOD=TT3:
NOBLKMOD=TT7:
NOBLKMOD=HT14 :
Displays all of the terminals
block-mode option disabled.
that
/BRO[=ttnn:]
Enables the broadcast option for the specified terminal.
The terminal can receive messages sent from other terminals
with the BROADCAST command.
3-205
MCR COMMANDS
(
SET (Cont.)
When you omit =ttnn:, the system
terminals that can receive messages.
displays
all
of
the
/BR0 is valid only on systems that have multi-CLI support.
Examples:
>SET
/BRO=TT7:~
Enables the broadcast option for TT7:.
>SET /BRO
BRO=C(}O:
BRO=TT4:
BRO=TT5:
BRO=TT6:
BRO=TT7:
~
Displays all of the terminals
broadcast option enabled.
that
have
the
L-'i
/NOBRO [=t tnn: ]
Disables the broadcast option for the specified terminal.
The
terminal cannot receive messages sent from other
terminals. The terminal also cannot receive messages from
the SHUTUP program until the last five minutes before system
shutdown. It is recommended that you not use the -/NOBRO
keyword unless you need to because you could miss important
messages.
When you
termina~s
omit =ttnn:, the system displays
that cannot receive messages.
all
of
c
the
/NOBRO is valid only on systems that have multi-CLI support.
Examples:
>SET
(
/NOBRO=TT4:~
Disables the broadcast option for TT4:.
>SET /NOBRO
NOBRO=TT4:
NOBRO=TTIO:
~
Displays all of the terminals
broadcast option disabled.
that
have
the
/BUF=ddnn: [size]
Sets or displays the default buffer size of the specified
device. A nonprivileged user can display the buffer size of
any device but can only set the buffer size of TI:.
A
privileged user can set the buffer size for any device.
3-206
MCR COMMANDS
(
SET (Cont.)
The specified size must be at least 14 (decimal)
and less
than or equal to 255 (decimal) • If ddnn: is a terminal, the
specified size must be greater than l5(decimal)
and less
than or equal to 255 (decimal) • /BUF is particularly useful
for defining line printer width (80 or 132 decimal columns)
and the maximum number of characters allowed in a command
line.
When you omit size, the system displays the buffer
the specified device.
Example:
>SET /BUF=LPO:~
BUF=LPO:132.
Displays the current buffer size of LPO:.
>SET
/BUF=TT1:40.~
Sets TTl: buffer size to 40 (decimal) •
(
l
3-207
size
of
MCR COMMANDS
c
SET (Cont.)
c
(
3-208
MCR COMMANDS
(
SET (Cont.)
/CLI=ttnn: [cli]
(
Defines the default command line interpreter (CLI)
for the
specified
terminal.
The CLI can be MCR, DCL,or a
user-written CLI.
(However, note that before a CLI can be
used, it must be installed with the INSTALL /CLI=YES
command .)
A nonprivileged user can display the default CLI for any
terminal but can only set the CLI for TI:. A privileged
user can set the default CLI for any terminal.
When you omit cli, the system displays the
CLI for the specified terminal.
current
default
/CLI is valid only on systems that have multi-CLI support.
Examples:
>SET /CLI=TI: tBffi
CLI=TI:MCR
Displays the current default CLI for TI:.
>SET /CLI=TI :ACLI tBffi
Sets the default CLI for TI:
to ACLI.
/COLOG
This keyword is documented with the Console Output
(COT) in the RSX-llM/M-PLUS System Management Guide.
c
3-209
Task
MCR COMMANDS
c
SET (Cont.)
/CRT[=ttnn:]
Defines the specified terminal as a Cathode Ray Tube (CRT)
terminal and enables the backwards deletion option. Typing
the RUBOUT or DELETE key moves the printing position one
space to the left and erases any character displayed in that
position.
A nonprivi1eged user can display all terminals defined as
CRTs but can only define TI: as a CRT. A privileged user
can define any terminal as a CRT.
When you omit =ttnn:, the system
terminals that are defined as CRTs.
displays
all
of
the
Examples:
>SET
/CRT=TT3:~
Enables the backwards deletion option for terminal
TT3: •
>SET /CRT
CRT=TT3:
CRT=TT4:
~
Displays all the terminals that have the backwards
deletion option enabled.
/NOCRT[=ttnn:]
Deletes the CRT status of the specified
disables the backwards deletion option.
terminal
and
A nonprivi1eged user can display all the terminals not
defined as CRTs but can only delete CRT status for TI:. A
privileged user can delete CRT status for any terminal.
When you omit =ttnn:, the system displays all terminals that
are not defined as CRTs.
Examples:
>SET
/NOCRT=TT4:~
Disables the backwards deletion option for TT4:
>SET /NOCRT
NOCRT=TTO:
NOCRT=TT1:
NOCRT=TT2:
NOCRT=TT4:
~
Displays all the terminals that have the backwards
deletion option disabled.
3-210
c
c
MCR COMMANDS
SET (Cont.)
JDCL [=ttnn: 1
Enables the recognition of DIGITAL Command Language
(DCL)
commands at the specified terminal. Commands entered in
response to the default prompt are submitted to DCL.
To return a terminal to MCR command
DCL command SET TERMINAL MCR.
recognition,
type
the
A nonprivileged user can display all of the terminals that
recognize DCL commands, but can only enable DCL recognition
for TI:. A privileged user can enable any DCL command
recognition for any terminal.
When you omit =ttnn:, the system displays all of
terminals that have DCL command recognition enabled.
the
JDCL is valid only on systems that have multi-CLI support.
Examples:
>SET jDCL=TT3:(@)
Enables DCL command recognition for TT3:.
c
>SET JDCL (@)
DCL=TT3:
DCL=TT7:
DCL=TTIO:
DCL=TT12:
Displays all of the terminals that
commands.
recognize
DCL
(Full-duplex terminal driver only.)
Indicates that
specified
terminal
is
upward-compatible
with
VT100-series of terminals.
the
the
When you omit =ttnn:, the system displays
terminals that are upward-compatible.
of
the
terminals
that
the
VT100-series
are
of
JDEC [=ttnn: 1
(
all
Examples:
>SET JDEC (@)
DEC=TT5:
DEC=TT1:
Displays
all
of
the
upward-compatible
with
terminals.
jNODEC [=ttnn: 1
(Full-duplex terminal driver
specified
terminal
is not
VT100-series of terminals.
3-211
only.)
Indicates
upward-compatible
that
with
the
the
MCR COMMANDS
c
SET (Cont.)
When you omit =ttnn:, the system displays
terminals that are not -upward-compatible.
all
of
the
Examples:
>SET /NODEC ffil
NODEC=TT4:
NODEC=RT23:
c
c
l
3-212
MCR COMMANDS
SET (Cont.)
c
3-2l3
MCR COMMANDS
c
SET (Cont.)
c
c-
3-214
MCR COMMANDS
(
SET (Cont.)
(
/NOEBC [=ttnn:]
(
(Full-duplex terminal driver only.)
Disables the eight-bit
character option.
Before passing the input characters to
the device, the terminal driver clears the eighth bit.
A nonprivileged user can display all terminals that have the
option disabled but can only disable the EBC option for TI:.
A privileged user can disable EBC for any terminal.
When you omit =ttnn:,
the system displays
terminals that have the EBC option disabled.
all
of
the
Examples:
>SET /NOEBC ffil
NOEBC=TTO:
NOEBC=TT1:
NOEBC=TT2:
NOEBC=TT4:
Displays all terminals that have
disabled.
the
EBC
>SET /NOEBC=TT3: ffil
Disables the EBC option for terminal TT3:.
3-215
option
MCR COMMANDS
(
SET (Cont.)
/ECHO[=ttnn:]
Instructs the terminal driver to
typed on the specified terminal.
display
each
character
A nonprivileged user can display all of the te~minals that
echo typed characters but can only enable the echo option
for TI:. A privileged user can enable the echo option for
any terminal.
When you omit =ttnn:, the system displays_ all
terminals -that have the echo option enabled.
of
the
Examples:
>SET /ECHO=TT3:®ill
Enables the echo option for terminal TT3:.
>SET /ECHO OOJ
ECHO=TTl:
ECHO=TT3:
Displays all of the terminals that have
option enabled.
the
echo
/NOECHO [=ttnn:]
Instructs the terminal driver to inhibit the display of
input characters typed on the specified terminal.
all
A nonprivileged user can display all terminals that do not
echo typed characters but can only disable the echo option
for TI:. A privileged user can disable the echo option for
any terminal.
When you omit =ttnn:, the system displays
terminals that have the echo option disabled.
all
of
the
Examples:
>SET /NOECHO ®ill
NOECHO=TTO:
NOECHO=TT2:
NOECHO=TT4:
Displays all of the terminals
typed characters.
that
do
not
>SET /NOECHO=TT3:®ill
Disables the echo option for terminal TT3:.
3-216
echo
(
MCR COMMANDS
SET (Cont.)
/EDIT[=ttnn:)
(Full-duplex terminal driver only.)
Indicates that the
specified terminal can perform ANSI-defined advanced editing
functions. The VTI02 is an example of such a.terminal.
Whe'n you omit =ttnn:, the system displays all of the
terminals that can perform the advanced editing functions.
Examples:
>SET /EDIT=TT22:®ill
Sets advanced editing functions for TT22:.
>SET /EDIT ®ill
EDIT=TT7:
EDIT=TT22:
EDIT=TT35:
Displays all of the terminals that
editing functions.
have
advanced
/NOEDIT [=ttnn: )
c
(Full-duplex terminal driver only.)
Indicates that the
specified terminal cannot perform ANSI-defined advanced
editing functions.
When you omit =ttnn:, the system
that
cannot
perform
terminals
functions.
displays all
the advanced
of the
edi ting
Examples:
>SET /NOEDIT=TT22:®ill
c
Diaables advanced editing functions for TT22:.
>SET /NOEDIT ®ill
NOEDIT=TT22:
NOEDIT=TT37:
NOEDIT=RT44:
Displays all of the terminals
advanced editing functions.
that
do
not
have
/ESCSEQ [=ttnn:)
Enables the recognition of escape sequences from
the
specified terminal.
The. terminal driver treats the ESC
character as the beginning of an escape sequence rather than
as a line terminator. See the RSX-IIM/M-PLUS I/O Drivers
Reference Manual for further information about
escape
sequences.
3-217
MCR COMMANDS
(
SET (Cont.)
A nonprivileged user can display all terminals that can send
and receive escape sequences but can only enable escape
sequence recognition for TI:. A privileged user can enable.
escape sequence recognition for any terminal.
When you omit ·=ttnn:, the system displays all of
terminals that can send and receive escape sequences.
the
Examples:
)SET /ESCSEQ=TT 3: OOJ
Establishes TT3: as a terminal that can send
receive escape sequences.
and
)SET /ESCSEQ OOJ
ESCSEQ=TT3:
ESCSEQ=TT5:
ESCSEQ=TTIO:
Displays all of the terminals that
receive escape sequences.
can
send
and
sequences
from
the
/NOESCSEQ[=ttnn:]
Disables the recognition
specified terminal.
of
escape
A nonprivileged user can display all terminals that do not
recognize escape sequences but can only disable the option
fo~ device
TI:.
A privileged user can disable escape
sequence recognition for any terminal.
c
When you omit =ttnn:, the system displays all of the
terminals that have escape-sequence recognition disabled.
Examples:
c
.)SET /NOESCSEQ=TT3: OOJ
Disables escape sequence recognition for TT3:.
)SET /NOESCSEQ OOJ
NOESCSEQ=TTO:
NOESCSEQ=TTl:
NOESCSEQ=TT2:
NOESCSEQ=TT3:
NOESCSEQ=TT4:
Displays all of the terminals that cannot send
receive escape sequences.
or
/FDX [=ttnn:]
(Full-duplex terminal driver only.)
Instructs the terminal
driver to accept input from the specified terminal while
simultaneously outputting to it.
3-218
c
MCR COMMANDS
(
SET (Cont.)
A nonprivileged user can display all the
full-duplex
terminals but can only enable the. option for TI:. A
privileged user can enable the full-duplex option for any
terminal.
When you omit =ttnn:, the system displays
full-duplex terminals (if there are any).
all
of
the
Examples:
>SET /FDX=TT3:®ill
Declares that TT3:
is a full-duplex terminal.
>SET /FDX @@
FDX=TTI:
FDX=TT3:
Displays all the full-duplex terminals.
/NOFDX [=ttnn:]
c
(Full-duplex
terminal
driver
only.)
Disables
the
the
terminal
driver
does
not
full-duplex
option;
simultaneously process input and output from the specified
terminal.
A nonprivileged user can display all terminals that have the
full-duplex option disabled but can only disable the option
forTI:. A privileged user can disable the full-duplex
option for any terminal.
When you omit =ttnn:, the system displays all of the
terminals that have the the full-duplex option disabled.
Examples:
c
>SET /NOFDX=TT3: @@
Disables the full-duplex option for terminal TT3:.
>SET /NOFDX @@
NOFDX=TTO:
NOFDX=TT2 :
NOFDX=TT3:
NOFDX=TT4:
Displays all of the terminals that do not
input and output simultaneously.
process
/FORMFEED~=ttnn:]
Indicates that the specified terminal ~as
feed.
a
hardware
form
A nonprivileged user can display all terminals that have
hardware form feed, but can only declare it for TI:.
privileged user can declare it for any terminal.
When you omit =ttnn:, the system displays
terminals that have a hardware form feed.
3-219
all
of
a
A
the
MeR COMMANDS
c
SET (Cont.)
Examples:
>SET /FORMFEED
FORMFEED=TTl:
~
Displays all of the terminals that have a hardware
form feed.
>SET /FORMFEED=TT3:®]
Declares that TT3:
has a hardware form feed.
/NOFORMFEED[=ttnn:]
Indicates that the
hardware form feed.
specified
terminal
will
not
have
a
A nonprivileged user can display all terminals that do not
have a hardware form feed, but can only specify the option
for TI:. A privileged user can specify the option for any
terminal.
When you omit =ttnn:, the system displays all
terminals that do not have a hardware form feed.
of
the
Examples:
>SET /NOFORMFEED
NOFORMFEED=TTO:
NOFORMFEED=TT2:
NOFORMFEED=TT4:
(
~
Displays all of the terminals that do not
hardware form feed.
>SET /NOFORMFEED=TT3:
have
a
~
Specifies that TT3:
feed.
will not have a hardware form
/HFILL=ttnn: [value]
(Full-duplex terminal driver only.)
Specifies the number of
fill characters
(value)
that the terminal driver places
after a carriage return when outputting to a terminal.
The
range for the value is 0 to 7.
A nonprivileged user can display the number of
fi 11
characters for any terminal but can only change the value
for TI:. A privileged user can specify the number of fill
characters for any terminal.
When you omit value, the system displays the fill
value for the specified terminal.
character
Examples:
>SET /HFILL=TT3:
HFILL=TT3:0
~
Displays the number of fill characters for TT3:.
3-220
(
MCR COMMANDS
(
SET (Cont.)
>SET /HFILL=TT3:3 ffi)
Specifies for TT3:
that
follow a carriage return .•
three
fill
characters
/HHT[=ttnn:]
(Full-duplex terminal driver only.)
Indicates
to
the
terminal driver that the specified terminal has a hardware
horizontal tab.
A nonpriyileged user can display all terminals that have
hardware horizontal tab but can only declare it for TI:.
privileged user can declare it for any terminal.
When you omit =ttnn:, the system displays
terminals that have a hardware horizontal tab.
all
of
a
A
the
Examples:
>SET /HHT ffi)
HHT=TT4:
HHT=TT6:
HHT=TT7:
c
Displays all of the terminals that have a hardware
horizontal tab.
>SET /HHT=TT3: ffi)
Declares that TT3:
has hardware horizontal tabs.
/NOHHT[=ttnn:]
(Full-duplex terminal driver only.)
Indicates that the
specified terminal does not have a hardware horizontal tab.
A nonprivileged user can display all terminals that do not
have a hardware horizontal tab but can only declare it for
TI:. A privileged user can declare it for any terminal.
When you omit =ttnn:, the system displays all of
terminals that do not have a hardware horizontal tab.
the
Examples:
> SET /NOHHT ffi)
NOHHT=TTO:
NOHHT=TTl:
NOHHT=TT2:
Displays all of the terminals that do not
hardware horizontal tab.
have
a
>SET /NOHHT='l'T3:ffi)
c
Declares that TT3:
horizontal tab.
3-221
does
not
have
a
hardware
COMMA.NDS
MCR
(
SET (Cont.)
/HOLD [=ttnn:]
Enables hold-screen mode at the specified CRT terminal.
When hold-screen mode is enabled, the terminal displays
output one screenful at a time.
The screenful of output
remains on the screen until you type the SCROLL key while
pressing the SHIFT key.
The terminal then refills the
screen.
You can also advance the screen contents one line
at a time by typing the SCROLL key.
Hold-screen mode is useful when copying files to terminals
that normally transmit output at high baud rates (9600, for
example). Note, however, that hold-screen mode may not be
appropriate for use with certain types of programs (editors
or terminals using different speeds for input and output,
for example).
A nonprivileged user can display all terminals currently in
hold-screen mode but .can only place TI: in hold-screen
mode.
A privileged user can place any
terminal
in
hold-screen mode.
When you omit =ttnn:, the system displays all
terminals that are currently in hold-screen mode.
of
the
Examples:
(
)SET/HOLD=TT3:®]
Enables hold-screen mode for CRT terminal TT3:.
The terminal erases its screen and positions the
cursor at the top left (home) of the screen.
)SET /HOLD ®]
HOLD=TT3:
HOLD=TT7:
HOLD=TT12:
Displays all
of
the
hold-screen mode enabled.
terminals
that
have
(
/NOHOLD [=ttnn:]
Disables hold-screen mode at the specified CRT terminal.
A nonprivileged user can display all terminals not in
hold-screen mode but can only disable the option for TI:. A
any
privileged user can disable hold-screen mode for
terminal.
When you omit =ttnn:, the system displays
terminals that have hold-screen mode disabled.
all
of
the
Examples:
)SET
/NOHOLD=TT3:~
Disables hold-screen mode for terminal TT3:.
3-222
(
MCR COMMANDS
(
SET (Cont.)
>SET /NOHOLD 001
NOHOLD=TTO:
NOHOLD=TT3:
Displays all
of
the . terminals
hold-screen mode disabled.
that
have
/HOST[=node[::]]
Establishes the specified node as the host
user.
system
for
the
When you use the /HOST keyword, the Network Command Terminal
(NCT ••• ) task is activated to establish a DECnet link.
If
NCT ••• is not installed in the system, MCR searches for the
task ••• RMT.
If ••• RMT is not installed in the system, an
error message is issued.
(For a complete description of
NCT ••• error messages, see the DECnet documentation.)
c
After issuing the /HOST keyword, you may enter terminal
management mode by typing CTRL\ (that is, the control
key, thebackslash key, and the RETURN key). Valid commands
for terminal management mode are CONTINUE and CLEAR HOST.
Typing CONTINUE and then pressing the RETURN key exits you
from terminal management mode and returns you to the remote
session. CLEAR HOST followed by RETURN terminates the
remote session.
When you omit =node[::], the system displays the host system
for the terminal.
The /HOST keyword executes only on systems that select
Network
Command
Terminal
(NCT) support during system
generation. On RSX-IIM-PLUS operating systems, if DECnet is
selected during system generation, support for NCT is
included.
On RSX-IIM operating systems, if DECnet is
selected during system generation, support for NCT may also
be selected.
Examples:
>SET /HOST=FRIEND::001
Sets node
terminal.
FRIEND
as
the
host
node
for
your
>SET /HOST 001
Host=FRIEND RSX-IIM~PLUS V3.0 BL24
Displays the name of the host node for you~
terminal.
The display line includes the name and
version number of the operating system that the
host node runs.
/HSYNC [=ttnn:]
(Full-duplex terminal driver only.) Enables synchronization
between
the
host system I and the specified terminal.
Synchronization between the host and terminal controls the
typeahead buffer to keep it from overflowing. When the
3-223
MCR COMMANDS
(
SET (Cont.)
typeahead buffer is nearly full,
the terminal temporarily
locks the keyboard, which prevents you from typing and
entering information that the system is not yet ready to
accept.
After the terminal driver transmits the characters
in the typeahead buffer to the system and there is again
available space in the buffer, the terminal driver unlocks
the keyboard. You can then resume typing. When you specify
/HSYNC, the system generates a CTRL/S to lock the keyboard
and a CTRL/Q to unlock it.
The /HSYNC keyword is recommended for users of terminals
that transmit information in blocks; for example, the
DIGITAL VT131 or VT132 terminals, or any other terminal that
emulates those two models.
If you do not have such a
terminal, it ia unlikely that you will fill the typeahead
buffer.
(If you would like the typeahead buffer of your
terminal to be a different size, you may be able to use the
/TYPEAHEAD keyword to change it.)
.
The default for the VT100-series of terminals is /HSYNC.
When you omit =ttnn:, the system displays all of the
terminals that have synchronization between the host and the
terminal.
Examples:
>SET
(
HSYNC=TT2:~
Enables synchronization between the host and TT2:.
>SET HSYNC
HSYNC=TT2:
HSYNC=TT4 :
HSYNC=RT7:
~
Displays all synchronized terminals.
/NOHSYNC [=ttnn:]
(Full-duplex terminal driver only.) Disables synchronization
between the host system and the terminal for the specified
terminal. The terminal does not lock the keyboard when the
typeahead buffer becomes full.
Therefore, any characters
that you subsequently enter (until the typeahead buffer is
cleared again) will be lost.
The default for VT52 terminals is /NOHSYNC.
When you omit =ttnn:, the system displays all of the
terminals that do not have host/terminal synchronization.
Examples:
>SET /NOHSYNC=TT20:
~
Disables synchronization for TT20:.
3-224
MCR COMMANDS
(
SET (Cont.)
>SET /NOHSYNC (BIT)
NOHSYNC=TT12:
NOHSYNC=TT20:
NOHSYNC=RT28:
Displays all
synchronized.
of
the
terminals
that
are
not
/INQUIRE[=ttnn: ]
Sets all appropriate attributes, including a buffer size of
80 for the specified terminal. The keyword sends a query to
the terminal to find out what model it is and then issues
the SET command for that terminal model. The following
DIGITAL terminals are set explicitly:
VT50; VT52; VT55;
VT6l;
the VT100-series (the VT100, VTlOl, and VTl05 are all
set as VT100s); VT125; VT13l; VT132; the VT200-series; LA34;
LA38; LA120; VKlOO
(which is treated as a VT100); the
DECmate II and Rainbow 100-series (all of which are treated
as VTl02s); and the PC300-series. All other terminals are
set to /NOCRT and /BUF:TI:80, and are considered to be
unknown models. Also, terminals that do not support escape
sequences (such as the LA36) , display the characters "Z[CC"
when queried.
If you include SET /INQUIRE in your login command file, you
may not need to set any attributes for the terminal because
SET /INQUIRE sets most of them for you.
Examples:
>SET /INQUIRE=TT3:(BIT)
Inquires as to the type of terminal that TT3:
is,
and then sets the appropriate attributes for that
terminal type.
c
c
3-225
MCR COMMANDS
(
SET (Cont.)
>SET /LIBUIC=[6,54) ®ill
Sets the library UIC to [6,54).
/LINES=ttnn:[value)
(Full-duplex terminal driver only.)
Establishes the number
of lines per page (value) for the terminal. The range for
value is 1 to 255 (decimal) • To specify a decimal value,
place a period (.) after the number.
A nonprivileged user can display the number of lines per
page for any terminal but can only specify the number for
TI:. A privileged user can specify the number of lines per
page for any terminal.
When you omit value, the system displays the number of lines
per page for the specified terminal.
Examples:
>SET /LINES=TT3:®ill
LINES=TT3:24.
Displays the number of lines per page for TT3:.
>\SET /LINES=TT3: 20 ®ill
Specifies in octal the number of
for TT3:.
lines
per
page
c
/LOGON
(Privileged keyword.)
Enables logging in on terminals in
multiuser protection system.
a
/NOLOGON
(Privileged keyword.)
Disables logging in on terminals in a
multiuser protection system.
/LOGON and /NOLOGON clear and set a flag checked by the
HELLO command when a user attempts to log in on a terminal.
/NOLOGON provides a means of preventing users from accessing
the system during such activities as system maintenance or
account file maintenance.
/LOWER [=ddnn: )
Specifies that lowercase characters on a terminal or line
printer are not to be converted to uppercase when they are
received from the device driver.
Note that this keyword
only affects input from a terminal, not output to a
terminal.
A nonprivileged user can display all devices that do not
convert lowercase characters to uppercase but can only
specify the option for TI:. A privileged user can specify
the option for any terminal or line printer.
3-226
c
MCR COMMANDS
(
SET (Cont.)
When you omit =ddtm:, the system displays all the devices
for
which
lowercase characters are not converted to
uppercase.
Examples:
>SET /LOWER=TT3:®ill
Inhibits conversion of lowercase characters
uppercase when they are received from TT3:.
to
>SET /LOWER ®ill
LOWER=LPO:
LOWER=TTI:
LOWER=TT3:
LOWER=TT7:
Displays all the devices for which lowercase
characters are not converted to uppercase.
/NOLOWER[=ddnn:]
c
Resets the characteristics for the terminal or line printer.
For terminals, lowercase characters received on input are
automatically - converted to
uppercase
and
echoed
as
uppercase.
The keyword has no effect on characters output
to the terminal. For line printers, lowercase characters
output to the device are printed as uppercase.
A nonprivileged user can display all the devices that
perform this conversion but can only specify the option for
TI:. A privileged user can specify the option for any
terminal or line printer.
When you omit =ddnn:, the system displays all the
for which conversion to uppercase is specified.
(
devices
Examples:
>SET /NOLOWER ®ill
NOLOWER=LPI:
NOLOWER=TTO:
NOLOWER=TT2:
NOLOWER=TT4:
Displays all the devices
that
automatically
convert lowercase characters to uppercase.
>SET /NOLOWER=TT3:®ill
Resets TT3:
so that lowercase characters
automatically converted to uppercase.
are
/MAIN=pname[:base:size:type]
(On RSX-IIM-PLUS operating systems, synonym for /PAR.)
Establishes the specified partition as a main partition. A
nonprivileged user can only display the base size, and type
of a main partition.
3-227
MCR COMMANDS
(
SET (Cont.)
pname
The 1- to 6-character alphanumeric partition name.
:base
The physical base address of the
as a number of 64-byte blocks.
partition,
specified
:size
The size of the partition, specified
64-byte blocks.
as
a
number
of
:type
~)
The partition type:
SYS
A system-controlled task partition
COM
A common partition
DEV
A common partition mapping into the
registers
device
User-controlled and
system-controlled
task
partitions
contain user tasks. Common partitions are used for resident
libraries and common blocks. Device partitions are used by
nonprivileged tasks to access device registers in the
external page, such as those for the UDC and ICS/ICR-ll.
Base and size can be entered in any of the following formats
(nnnn is a number in bytes to which the system applies a
multiplication factor to determine the value used):
Format
nnnn
nnnn.
nnnK
nnn.K
Calculated Value
Octal (nnnn*lOO)
Decimal (nnnn.*64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)
c
c
Valid ranges of calculated values ( in words) are:
Octal
Decimal
Octal K
Dec:;l'imal K
0<=base<177777
0.<=base<65535
OK<=base<3777K
0.K<=base<2047.K
0SET /MAIN=SYSPAR:420:140:TASK®ill
Defines a main partition named SYSPAR as
a
user-controlled partition whose base address is
42000 (octal)
and whose length is 14000 (octal)
bytes.
>SET /MAIN=SYSPAR ®ill
MAIN=SYSPAR:0420:0l40:TASK
Displays the parameters of the main partition
SYSPAR. Note that if the main partition is a task
partition
and
contains
subpartitions,
the
parameters of the subpartition are also displayed.
/NOMAIN=pname
(On RSX-llM-PLUS operating systems, synonym for /NOPARi
privileged keyword.)
Eliminates the specified partition
from the system.
Example:
>SET /NOMAIN=SYSPAR ®ill
Eliminates the
system.
main
partition
SYSPAR
from
the
/MAXEXT[=size]
(Privileged keyword.)
Establishes the maximum size to which
a task can extend itself beyond its mapped array area by
means of the EXTEND TASK directive (see the RSX-llM/M-PLUS
and Micro/RSX Task Builder Manual for information about
arrays and the--"RSX-llM/M-PLUS and Micro/RSX
Executive
Reference Manual for a description-oI the directive).
The keyword is only valid on mapped RSX-llM systems that
selected the EXTEND TASK directive option during system
generation and on all RSX-llM-PLUS systems.
Note that a
nonprivileged user can display the maximum size to which a
task can extend itself (but not change the size).
3-229
MCR COMMANDS
SET (Cont.)
The maximum size can be expressed in four formats:
n
nK
n.
n.K
See the description of the /MAIN
definition of these size values.
or
/PAR
keyword
for
a
When you omit =size, the system displays the current maximum
size in the format:
MAXEXT=m
where m is an octal number equal
64-byte blocks allowed for a
indicat~s 20K words) •
to the maximum size in
(for example, 1200
task
Examples:
>SET /MAXEXT=20. K ~
Establishes 20.K as the maximum size
task can extend itself.
to
which
a
C
>SET /MAXEXT ~
MAXEXT=12000
Displays the current maximum size to which a
can extend itself.
task
/MAXPKT [=n]
Specifies the maximum number of I/O packets to be retained
in a separate queue for use by the QIO directive. The
number of retained packets
(n)
is used to optimize the
servIcIng of QIO requests.
The range for n is 0 to
15 (decimal) •
A nonprivileged user can only display
current number of available I/O packets.
the. maximum
and
When you omit =n, the system displays the maximum number and
the current number of available I/O packets in the format:
MAXPKT=m. : c •
where m. is the maximum number of
number of available I/O packets.
and
c. is
the
current
Examples:
>SET /MAXPKT=12.
~
Sets the maximum number of I/O packets retained
for optimization of I/O servicing to 12(decimal).
3-230
c
MCR COMMANDS
(
SET (Cont.)
>SET /MAXPKT ®TIl
MAXPKT=12.:3.
Displays the maximum and current number of I/O
packets.
The maximum number of of I/O packets to
be retained explicitly for QIO pr.ocessing is
12 (decimal) •
Three
packets
are
currently
available.
/MCR[=ttnn:]
Enables MCR command recognition at the specified terminal.
Commands entered in response to the default prompt are
submitted to MCR.
A nonprivileged user can display all the terminals that
recognize MCR commands but can only specify the option for
TI:. A privileged user can enable MCR command recognition
for any terminal.
When you omit =ttnn:,the system displays
terminals that recognize MCR commands.
all
of
the
/MCR is valid only on systems that have multi-CLI support.
Examples:
c
>SET /MCR ®TIl
MCR=TTl:
MCR=TT2:
MCR=TT3:
Displays all of the terminals that
commands.
recognize
>SET /MCR=TT4: ®TIl
c-
Enables MCR command recognition for TT4:.
3-231
MCR
MCR COMMANDS
(
SET (Cont.)
c
c
3-232
MCR COMMANDS
(
SET (Cont.)
(
(
(
3-233
MCR COMMANDS
c
SET (Cont.)
/NETUIC[=[uic]]
Specifies the UIC in which all DECnet-related tasks are
stored.
The keyword applies only to systems that selected
the external communication products option during system
generation.
On RSX-IIM operating systems, if you did not select support
for DECnet at system generation, NETUIC defaults to SYSUIC.
A nonprivileged user can display the current network
but only a privileged user can set or change it.
When you omit
network UIC.
=[uic],
the
system
displays
the
c
UIC,
current
(
Examples:
>SET /NETUIC ~
NETUIC=[20,34]
Displays the current network UIC.
>SET /NETUIC=[110,3]
~
Sets the network UIC to [110,3].
3-234
MCR COMMANDS
(
SET (Cont.)
(
3-235
MCR COMMANDS
c
seT (Cont.)
c
c
l
. 3-236
MCR COMMANDS
SET (Cont.)
c
(
3-237
MCR COMMANDS
c
SET (Cont.)
c
c
3-238
MCR COMMANDS
(
SET (Cont.)
/PARITY[=ttnn:[option]]
(Full-duplex terminal driver only.) Enables and determines
the type of parity generation and checking for the specified
terminal. Parity generation and checking is used to verify
the transmission of data between the terminal and the
computer. Verification is done by sending an extra bit with
each character, which serves as a check that the transmitted
character was received properly.
When parity checking is enabled, an additional bit called a
parity bit is generated and sent with each character output
from the computer.
c
The options for /PARITY are EVEN and ODD. The state of the
parity bit, which is either 0 or 1, is determined by the
option
used
with
the
keyword.
If
you
specify
/PARITY=ttnn:EVEN, the state of the parity bit is selected
to force the total of "1" bits to be even. If you specify
/PARITY=ttnn:ODD, the total number of "1" bits is odd. The
terminal driver checks the state of the parity bit to see if
it is correct.
If it is not, a transmission error has
occurred. The terminal driver performs the same parity bit
generation when you enter a character and the system checks
for parity when it receives the character.
Note that the terminal hardware must be set to the same mode
of parity generation and parity checking for correct data
transmission to occur.
On
VT100and
VT200-series
terminals, this is done through the terminal's SET-UP mode.
The /PARITY keyword is not related to the /EBC
(Eight-Bit
Character)
keyword.
If parity is selected, an extra bit is
physically transmitted with each character, whereas the
eight-bit character option affects only whether the eighth
data bit should be cleared or left alone.
When you omit =ttnn:, the system displays all of the
terminals that have parity generation and checking enabled.
Examples:
>SET
/PARITY=TT27:0DD~
Enables odd parity checking for TT27:.
>SET /PARITY
PARITY=TT4:
PARITY=TT17:
PARITY=TT27:
l
~
Displays all of the
checking enabled.
3-239
terminals
that
have
parity
MCR COMMANDS
(
SET (Cont.)
/NOPARITY[=ttnn:]
(Full-duplex terminal
driver
only.)
Disables
parity
generation and checking for the specified terminal. Data
transmitted between the terminal and the system is not
verified.
When you omit =ttnn:,
the system displays all of the
terminals that do not have parity generation and checking
enabled.
Examples:
>SET /NOPARITY=TTIO:®W
Disables parity checking for TTlO:.
>SET /NOPARITY ®W
NOPARITY=TT7:
NOPARITY=TTIO:
NOPARITY=TTI2:
Displays all of the terminals
parity checking en~bled.
that
do
not
have
c
(
3-240
MCR COMMANDS
c
SET (Cont.)
/PASTHRU[=ttnn:]
(Full-duplex terminal driver only.) Requests that the system
ignore the standard functions of special characters that are
typed at the specified terminal. Insteaq, when /PASTHRU is
enabled, the terminal driver passes special characters to a
program in their binary form.
c
c
/PASTHRU allows you to suppress standard operating system
responses to special characters (for example, CTRL/C and
CTRL/O), thereby controlling output to the terminal screen.
When a terminal is set to /PASTHRU, it does not respond to
special characters in the usual ways. The terminal does not
recognize any control characters (except CTRL/S and CTRL/Q
if the terminal is set to /TTSYNC), and it does not respond
to carriage-return and line-feed characters.
Also, any
programs that are running from a terminal that has /PASTHRU
enabled will not process the standard special character
functions.
If your terntinal does not seem to be working
may be because it has been set to /PASTHRU.
When you omit =ttno:, the system
terminals that are set to /PASTHRU.
displays
properly,
all
of
it
the
Examples:
>SET
/PASTHRU=TT1:~
Enables the pass~through option for TTl:.
>SET /PASTHRU
PASTHRU=TT1:
PASTHRU=TT2:
PASTHRU=TT3:
~
Displays all of the
/PASTHRU.
3-241
terminals
that
are
set
to
MCR COMMANDS
c
SET (Cont.)
/NOPASTHRU[=ttnn:]
(Full-duplex terminal driver only.) Requests that the system
treats special characters typed at the specified terminal
according to their standard function.
The default terminal setting is /NOPASTHRU.
When you omit =ttnn:, the system displays
terminals that are not set to /PASTHRU.
all
of
the
,
Examples:
>SET /NOPASTHRU=TTI2: ®ill
Disables the pass-through option for TTI2:.
The
terminal driver will process special characters
entered from TTI2:
in the standard fashion.
>SET /NOPASTHRU ®ill
NOPASTHRU=TTIO:
NOPASTHRU=TTI2:
'I
Displays all of the terminals that
disabled.
have
/PASTHRU
/PRINTER_PORT[=ttnn:]
(Full-duplex terminal driver only.) Informs the system that
the specified terminal has a printer port. A terminal with
a printer port can be connected to a local printer so that
you can print a hard copy of the display on your terminal
screen. VT200-series terminals have printer ports.
When you omit =ttnn:, the system
terminals that have a printer port.
displays
all
of
the
Examples:
(
>SET /PRINTER_PORT=TTI5:®ill
Indicates that terminal TTI5:
has a printer port.
>SET /PRINTER PORT ®ill
PRINTER PORT=TTI5:
PRINTER-PORT=TTI6:
Displays all of the terminals
ports.
that
have
printer
/NOPRINTER_PORT
(Full-duplex terminal driver only.) Informs the system
the specified terminal does not have a 'printer port.
When you omit =ttnn:, the system displays
terminals that do not have a printer port.
3-242
c
all
of
that
the
MCR COMMANDS
(
SET (Cont.)
Examples:
>SET /NOPRINTER_PORT=TT6=®ill
Indicates that terminal
printer port.
TT6:
does
not
have
a
>SET /NOPRINTER PORT ®ill
NOPRINTER PORT=TT2:
NOPRINTER-PORT=TT6:
Displays all of the terminals
printer ports.
that
do
not
have
/PLCTL [= [high] [: [low] [: [frsiz] [:basep]]]]
I~
(
(Privileged keyword.) Sets the pool limit parameters used by
the Pool Monitor Task (PMT). The following list defines the
parameters:
high
The high pool limit in bytes.
low
The low pool limit in bytes.
frsiz
The minimum byte size of the largest free pool
block required for a~oiding low-pool action by
thePMT.
basep
The base task priority, which is the lowest
priority a nonprivileged task can have and
still be eligible for memory contention during
times of low pool. This priority remains in
effect until pool conditions improve.
Note
that only those tasks requested while the
system is in a low pool state are affected.
The following list defines the limits of the parameters:
84.
<=
84.
(=
O.
low <= high <= total size of system pool
frsiz <= high
<= basep <= 250.
The followjng list gives the defaults for the parameters:
high
1600. bytes
low
600. bytes
frsiz
200. bytes
basep
51.
See the RSX-1IM/M-PLUS
System
Management
Guide
for
information on determining the values for the parameters.
When you omit the parameters, the
current parameters for the system.
3-243
system
displays
the
MCR COMMANDS
(
SET (Cont.)
Example:
>SET /PLCTL IDJ
PLCTL=loOO.:600.:200.:51.
Displays the current settings for the
parameters.
pool
limit
/POOL[=top]
Increases the size of the dynamic storage region (pool).
The parameter top specifies the first location in memory to
be used for user partitions. You specify the location in
units of 64-byte blocks. The location can be given as an
octal or decimal number.
A nonprivileged user can
dynamic storage region.
only
display
the
size
of
the
When you omit =top, the system displays
dynamic storage region in the format:
the
size
of
the
POOL=top:max.:total.
top
The first location for user partitions
(displayed
bytes with two trailing zeros suppressed).
in
max.
The longest free block (displayed in words) •
total.
The total pool space (displayed in words) •
Examples:
(
>SET /POOL=1200 IDJ
Establishes
120000 (octal)
as
location for user partitions.
the
beginning
>SET /POOL IDJ
POOL=1200:03380.:06322.
Displays the first location for user partitions,
the longest free .block, and the total of all pool
space (the first free block is at 120000, the
longest free block is 3380 decimal words, and the
total pool space is 6322 decimal words).
/PRIV [=ttnn: ]
EstabliShes the specified terminal as a privileged terminal.
A nonprivileged user can only display the terminals that are
privileged.
A privileged user can set any terminal to be
privileged.
3-244
l,
MCR COMMANDS
SET (C9nt.)
When you omit =ttnn:,
privileged terminals.
the
system
displays
all
of
the
Examples:
>SET /PRIV=TTI: ®ill
Establishes TTl:
as a privileged terminal.
>SET /PRIV ®ill
PRIV=TTO:
PRIV=TTI:
Displays all the privileged terminals.
/NOPRIV [=ttnn:]
Establishes the specified terminal to be nonprivileged.
A nonprivileged user can only display the terminals that are
nonprivileged. A privileged user can set any terminal to be
nonprivileged.
When you omit =ttnn:, the
nonprivileged terminals.
(!
system
displays
all
of
the
Examples:
>SET /NOPRIV ®ill
NOPRIV=TT2 :
NOPRIV=TT3:
Displays all the nonprivileged terminals.
>SET /NOPRIV=TTI:®ill
Establishes TTl:
(
as a nonprivileged terminal.
/PUB [=ddnn : ]
(RSX-IIM multiuser protection and RSX-IIM-PLUS operating
systems only.)
Establishes the specified device as a
public device. A public device is one that can be accessed
by all system users.
Note that allocated and already
mounted devices cannot be set public.
(Devices can be set
public before they are mounted.)
A nonprivileged user can display all the public devices, but
only a privileged user can establish a device as public.
When you omit =ddnn:, the system
devices.
displays
all
Examp"ies:
>SET /PUB=LP: ®ill
C\
Establishes LPO:
3-245
as a public device.
the
public
MCR COMMANDS
(
SET (Cont.)
)SET /PUB 001
PUB=DBO:
PUB=DBl:
PUB=LPO:
Displays all the public devices.
/NOPUB=[ddnn:]
(RSX-llM multiuser protection and RSX-llM-PLUS operating
systems only.)
Establishes the specified device as a
nonpublic device. A nonprivileged user can display the
devices
that were previously set public but are now
nonpublic, but only a privileged user can make a public
device nonpublic.
Note that mounted devices cannot lose
their public status.
When you omit =ddnn:, the system displays all of the devices
that are in use and are nonpublic devices.
Examples:
)SET /NOPUB 001
NOPUB=DKO:
NOPUB=DKl:
Displays all the private and
devices.
unowned
(nonpublic)
)SET /NOPUB=LPO:OOl
Establishes LPO:
c
as a nonpublic device.
/REGIS [=ttnn:]
(Full-duplex terminal, driver only.)
Indicates that the
specified terminal supports the ReGIS graphics character
set. The VTl25 and the VT240 are two such terminals.
When you omit =ttnn:, the system displays all of the
terminals that support the ReGIS graphics character set.
c
Examples:
)SET /REGIS=TTl7:00l
Indicates that terminal TTl7:
graphics characte~ set.
supports the
ReGIS
)SET /REGIS 001
REGIS=TTl:
REGIS=TT17 :
Displays all of the terminals
ReGIS graphics character set.
that
support
the
(~
3-246
MCR COMMANDS
SET (Cont.)
/NOREGIS[=ttnn:]
(Full-duplex terminal driver
speGified terminal does not
character set.
only. )
Indicates that the
support the ReGIS graphics
When you omit =ttnn:, the system displays all of the
terminals that do not support the ReGIS graphics character
set.
Examples:
>SET
/NOREGIS=TT13:~
Indicates that terminal TT13:
does
the ReGIS graphics character set.
not
support
Displays all of the terminals that do not
the ReGIS graphics character set.
support
>SET /NOREGIS
NOREGIS=TTll:
NOREGIS=TT13 :
~
/REMOTE[=ttnn: [speed]]
(
Declares that the specified terminal is connected to a modem
and can be connected to the system by means of a dial-up
network. The terminal has a line to a DHll, DHUll, DHVll,
DLll, DLVll, DZll, DZQll, or DZVll multiplexer.
A nonprivileged user can display all remote lines, but only
a privileged user can declare a terminal as a remote line.
(
Specifying speed establishes the initial baud rate
(answer
speed)
of the remote dial-up line for the specified
terminal. You may specify an answer speed only for DHlls,
DHUlls,
DHVlls, DZlls, DZQlls, and DZVlls, which are
variable-speed multiplexers.
(You cannot specify an answer
speed for DLlls or DLVlls.)
Valid speeds for the DHll are 0, 50, 75, 110, 134.5,
200,
300,
600,
1200, 1800, 2400, 4800, 9600,
(user-specified baud rate A), and EXTB (user-specified
rate B) •
150,
EXTA
baud
Valid speeds for the DHUll and the DHVll are 75, 110, 134.5,
150, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600, and
19200.
Valid speeds for the DZll, DZQll, and DZVll are 50, 75, 110,
134.5, 150, 300, 600, 1200, 1800, 2000, 2400, 3600, 4800,
7200, and 9600.
When you omit =ttnn:, the system displays all of the remote
terminals. When you omit speed, the current setting for the
terminal remains in effect.
3-247
MCR COMMANDS
(
SET (Cont.)
Examples:
>SET /REMO'l'E ffil
REMOTE=TTl:1200
REMOTE=TT2:0
REMOTE=TT4:0
Displays all of the terminals that
set as remote dial-up lines.
are
currently
>SET /REMOTE=TT3: 1200 ffil
Sets the terminal line corresponding to '1''1'3:
remote
dial-up line.
The initial baud
(answer speed) for the line will be 1200.
as a
rate
6,
/NOREMOTE [= t tnn : ]
Declares that the terminal's
connected to a modem.
line
is
a
local
line
not
A nonprivileged user can display all local lines, but only a
privileged user can declare a terminal as local.
When you omit =ttnn:, the
lines.
system
displays
all
the
local
c
Examples:
>SET /NOREMOTE=TT3:ffil
Declares that the terminal line
local line.
for
'1''1'3:
is
a
>SET /NOREMOTE ffil
NOREMOTE=TTO:
NOREMOTE=TT3:
Displays all the local lines.
/RNDC [=nn]
Defines the length of the Executive round-robin scheduling
in ticks.
The nn can be an octal value, or decimal if
followed by a period (.). The minimum value for nn is zero.
See the RSX-IIM System Generation and Installation Guide or
the RSX-IIM-PLUS System Generation and Installation Guide
for more information.
A nonprivileged user can display the value for the interval,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the interval.
3-248 "
(
MCR COMMANDS
(
SET (Cont.)
Examples:
>SET /RNDC 00)
RNDC=6.
Displays the current
scheduling interval.
length
of
the
round-robin
to
10 (decimal)
>SET /RNDC=lO. 00)
Sets the length of
ticks.
the
interval
/RNDH [=nnl
Defines the highest priority (1 to 250 decimal) that will be
considered for Executive round-robin scheduling.
The class
must be higher than the one specified with /RNDL.
See the
RSX-llM System Generation and Installation Guide or the
RSX-1IM~PLUS System Generation and
Installation Guide for
more information.
--A nonprivileged user can display the value for the priority,
but only a privileged user can change the value.
(
When you omit =nri, the system displays the current value for
the priority.
Examples:
>SET /RNDH 00)
RNDH=150.
Displays the current highest priority class
is considered for round-robin scheduling.
that
>SET /RNDH=120.00)
(
Sets the highest priority class to 120 (decimal) •
/RNDL[=nnl
Defines the lowest priority
(in a range from 1 to 250
decimal)
that will be considered for Executive round-robin
scheduling. The class must be lower than the one specified
with
/RNDH.
See
the RSX-llM System Generation and
Installation Guide or the RSX-llM-PLUS System Generation and
Installation Guide for more information.
A nonprivileged user can ~isplay the value for the priority,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the priori ty.
(
3-249
MCR COMMANDS
(
SET (Coni.)
Examples:
>SET /RNDL lBTIl
RNDL=1
Displays the current lowest priority class that is
considered for round-robin scheduling.
>SET /RNDL=20. lBTIl
Sets the lowest priority class to 20 (decimal) •
/RPA[=ttnn:]
(Full-duplex
terminal
driver
only.)
Enables
the
read-pass-all option of the terminal driver. The terminal
driver passes all input characters (including
special
function characters such as CTRL/C)
to the driver input
buffer.
A nonprivileged user can display all terminals that have the
option enabled but can only enable the read-pass-all option
for TI:. A privileged user can enable the read-pass-all
option for any terminal.
When. you omit =ttnn:, the system displays all the
that have the read-pass-all option enabled.
terminals
Examples:
c
>SET /RPA lBTIl
RPA=TTO:
RPA=TTI:
Displays all of the
terminals
where
input
characters are passed directly to the input buffer
for the full-duplex terminal driver.
>SET /RPA=TT3: lBTIl .
Enables the read-pass-all option for TT3:.
c
/NORPA[=ttnn:]
(Full-duplex terminal driver only.) Disables the readpass-all option. The terminal driver does not pass special
function input characters (such as CTRL/C) from the terminal
to the driver input buffer.
A nonprivileged user can display all terminals that have the
option disabled but can only disable the read-pass-all
option for TI:.
A privileged user can
disable
the
read-pass-all option for any terminal.
When you omit =ttnn:, the system displays all of the
terminals that do not pass special function characters to
the terminal driver input buffer.
l
3-250
MCR COMMANDS
(
SET (Cont.)
Examples:
>SET /NORPA 00l
NORPA=TT2:
NORPA=TT4:
Displays all of the terminals
read-pass-all option disabled.
that
have
the
>SET /NORPA=TT3:00l
Specifies that TT3:
not pass special function
input characters to the input buffer for the
full-duplex terminal driver.
c
(
l
3-251
MCR COMMANDS
(
SET (Cont.)
c
(
/SLAVE[=ttnn:]
Establishes the specified terminal as one that can enter
data only if it is solicited from a task by a READ QIO$.
Thus, the specified terminal always rejects unsolicited
input (other than CTRL/O, CTRL/Q, and CTRL/S).
3-252
l
MCR COMMANDS
(
SET (Cont.)
A nonprivileged user can display all slave terminals but can
only establish TI: as a slave terminal. Privileged users
can establish any terminal as a slave terminal.
When you omit =ttnn:, the system displays all
terminals that are currently classified as slaved.
of
the
Examples:
>SET /SLAVE=TT3:®]
Establishes TT3: as a terminal
enter data solicited by a task.
that
can
only
>SET /SLAVE tB.0
SLAVE=TT3:
Displays all of the slave terminals
the system.
currently
in
/NOSLAVE [=ttnn:]
Removes slave status from a specified terminal.
A nonprivileged user can only
display
the
nonslave
terminals.
A privileged user can set any slave terminal to
be nonslave.
(
When you omit =ttnn:, the system displays all
terminals.
the
nons lave
Examples:
>SET /NOSLAVE tB.0
NOSLAVE=TTO:
NOSLAVE=TT1:
NOSLAVE=TT2:
NOSLAVE=TT4:
(
Displays all the nonslave terminals.
>SET /NOSLAVE=TT3:tB.0
Sets TT3:
to a nons lave terminal.
/SOFT [=ttnn:]
(Full-duplex terminal driver only.)
Indicates that the
specified terminal can accept software-defined character
sets.
The VT200-series of terminals can accept these
character sets.
When you omit =ttnn:, the system displays all of
terminals that accept software-defined character sets.
the
Examples:
>SET /SOFT=TT4: tB.0
Indicates that
terminal
TT4:
software-defined character sets.
3-253
can
display
MCR COMMANDS
(
SET (Cont.)
SET /SOFT ruJ
SOFT=TT2:
SOFT=TT3:
SOFT=TT4:
Displays all of the terminals that
software-defined character sets.
can
display
/NOSOFT[=ttnn:]
(Full-duplex terminal dtiver only.)
Indicates that the
specified terminal cannot accept software-defined character
sets.
When you omit =ttnn: , the system displays all of the
terminals that do not accept software-defined character
sets.
Examples:
>SET /NOSOFT=TT17:ruJ
Indicates that terminal TT17:
software-defined character sets.
cannot
display
>SET /NOSOFT ruJ
NOSOFT=TT1:
NOSOFT=TT16:
NOSOFT=TT17:
(
Displays all of the terminals that cannot
software-defined character sets.
display
/SPEED=ttnn: [recv:xmit]
Establishes the receive and transmit baud rate for terminals
attached to the system through a DHll, DHUll, DHVll, DZll,
DZQll, or DZVll variable-speed multiplexer.
The
recv
argument is the baud rate at which characters are input to
the computer from the terminal. The xmit argument is the
baud rate at which characters are output to the terminal
from the computer. You must specify both arguments when
setting the speed. If you do not specify either argument,
the system displays the current settings.
A nonprivileged user can display the speed settings for any
terminal, but can set the speed only for TI:. A privileged
user can set the sneed for any terminal.
Valid baud rates for the DHll are 0, 50, 75, 110, 134.5,
150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, EXTA
(user-specified baud rate A), and EXTB (user-specified baud
rate B).
Valid baud rates for the DHUll and the DHVll are 75, 110,
134.5, 150, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600,
and 19200.
3-254
(
MCR COMMANDS
(
SET (Cont.)
Valid baud rates for the DZll, DZQll, and DZVll are 50, 75,
110, 134.5, 150, 300, 600, 1200, 1800, 2000, 2400, 3600,
4800, 7200, and 9600.
If you have a DZll, DZQll, or DZVll, the receive and
transmit
baud
rates must be the same because these
multiplexers do not support split speeds.
Examples:
>SET /SPEED=TT3: ~
SPEED=TT3:2400:2400
Displays the current speed setting for TT3:.
>SET /SPEED=TT3: 9600: 9600
~
Sets the receive and transmit baud rates for
to 9600.
(
c
3-255
TT3:
MCR COMMANDS
SET (Cont.)
(
(
/SWPC [=nn]
Defines the number of clock ticks for a single Executive
swapping interval.
The parameter nn is in the range 0 to
45,568 (decimal) and can be an octal value, or decimal if
followed by a period (.). See the RSX-IIM System Generation
and Installation Guide or the RSX-IIM-PLUS System Generation
and Installation Guide for more information.
A nonprivileged user can display the value for the interval,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the interval.
Examples:
>SET /SWPC
SWPC=30.
tBm
Displays the current number of clock ticks for the
swapping interval.
3-256
MCR COMMANDS
(
SET (Cont.)
>SET /SWPC=60. OOJ
Sets the new swapping interval to 60 (decimal) •
/SWPR [=nn]
Defines a priority range for Executive swapping.
The
parameter nn can be between 0 and 127(decimal), and it can
be an octal value, or a decimal value if it is followed by a
period (.).
The value for /SWPR affects the installed priority of all
tasks.
Each task is initiated at its installed priority
plus the value for nn (priority + nn). While the task is
executing, its priority is decremented until it becomes the
installed priority minus the value for nn
(priority - nn).
When the priority reaches this lower limit, the task is
swapped out so that another task with a higher priority can
execute.
The priority for the new task changes in the same
way. See the RSX-IIM System Generation and Installation
Guide or the RSX-IIM-PLUS System Generation and Installation
Guide for more information.
A nonprivileged user can display the value for the priority,
but only a privileged user can change the value.
c
When you omit =nn, the system displays the current value for
the priority range.
Examples:
>SET /SWPR OOJ
SWPR=5.
Displays the current
priority range.
c
value
for
the
swapping
>SET /SWPR=lO.OOJ
Sets the new priority range to 10 (decimal) •
/SYSUICl=[uic]]
Establishes the UIC for the system and all system tasks. On
most unmapped systems, the system UIC is [1,50]; on most
mapped systems, the system Ule is [1,54]. These UIC values
are the initial defaults on unsaved systems. The UIC also
becomes the default Ule used by the LOAD command and the
install-run-remove option of the RUN command.
A nonprivileged user can display the system Ule, but only
privileged user can change it.
a
When you omit =[uic], the system displays the current system
Ule.
3-257
MCR COMMANDS
c
SET (Cont.)
Examples:
)SET /SYSUIC mJ
SYSUIC=[l,54]
Displays the current system UIC.
)SET /SYSUIC=[3,54]mJ
Sets the system UIC to [3,54].
/TERM=ttnn: [value]
(Full-duplex terminal driver only.) Establishes the terminal
type (value) for the specified terminal. Supported standard
terminal types are:
ASR33
ASR35
DTCOI
KSR33
LA12
LA30P
LA30S
LA34
LA36
LA38
LA50
LAIOO
LA120
LA180S
LA210
LQP02
LQP03
LN03
PC3xx
VT05B
VT50
VT52
VT55
VT61
VT100
VTIOI
VTI02
VTI05
VT125
VT131
VT132
VT2xx
A nonprivileged user can display the terminal type for any
terminal but can only establish the terminal type for Tl:.
A privileged user can establish the terminal type for any
terminal.
When you omit the value parameter, the system
terminal type for the specified terminal.
displays
the
MCR also accepts an alternate form of the command. You can
specify the terminal type and equate it to the desired
terminal.
This
automatically
associates
certain
characteristics of the particular terminal type with the
specified terminal.
(See the RSX-IIM/M-PLUS I/O Drivers
Reference Manual for a list of the implicit characteristics
for each terminal type.)
The command is in the format:
SET /term-type=ttnn:
where term-type is one of the standard terminal types.
that the terminal types are mutually exclusive.
Note
The half-duplex terminal driver also accepts the /term-type
form of the command. However, the only legal terminal types
for the half-duplex driver are /ASR33, /LA30S, and /VT05B.
The command associates implicit characteristics of the
terminal type with the specified terminal, but, unlike the
full-duplex terminal driver, the types are not mutually
exclusive.
The following list describes the effects of the keywords for
the half-duplex terminal driver:
/ASR33
Converts lowercase letters
to
uppercase
before they are output to the terminal.
3-258
c
c
MCR COMMANDS
(
SET (Cont.)
/LA30S
Indicates that fill characters necessary for
the LA30S terminal are used after a carriage
return. The number of fill characters used
depends on the current carriage position at
the time the carriage return occurs.
/VT05B
Sets a vertical fill of three nulls after a
line feed on 60 Hz systems and of four nulls
on 50 Hz systems.
Examples:
>SET /TERM=TT3:®ill
TERM=TT3:VT52
Displays the terminal type for TT3:.
>SET /TERM=TT1:LA36 ®ill
Establishes TTl:
as an LA36 terminal.
>SET /LA36=TT1: ®ill
Same effect as previous example; establishes
as an LA36 terminal.
(
TTl:
You can also use an alternate command form to display all of
the terminals that are not a specific type.
The format is
as follows:
SET /NOterm-type
Note that you cannot negate a terminal type for a terminal.
You can only display the terminals that are not a specific
type. Negating terminal type returns a syntax error since
the terminal would be an indeterminate type.
(
/TOP=pname:value
Directs MCR to move the top boundary of the specified
system-controlled partition up or down the amount indicated
by the value parameter, or sets the partition size to that
amount.
The keyword modifies the top boundary of a
partition even if the partition has tasks installed in it.
If you modify the partition so that it may be too small to
hold the tasks installed in it, MCR displays a warning
message but modifies the partition anyway.
pname
The 1- to 6-character alphanumeric
system-controlled partition.
name
for
the
value
The number of 64-byte blocks.
The value parameter can be supplied in
+value, -value, value, +* or *, and -*
3-259
five
formats:
MCR COMMANDS
c
SET (Cont.)
+value
Moves the top boundary up by the specified amount.
Moving the top boundary up makes the partition
larger.
NOTE
You can supply the value in the same units
as the base and size parameters in the
keywords
described
/MAIN
or
/PAR
previously.
-value
Moves the top boundary down by the specified
amount.
Moving the top boundary down makes the
partition smaller.
value
Establishes the total partition size equal to
specified value by moving the top boundary.
the
+* or *
Moves the top boundary up as far as possible.
This format causes the top boundary to move to the
bottom boundary of the partition above it or to
the top of memory if the partition is the top
partition in memory.
c
-*
Moves the top boundary down as far as possible.
This format causes the top boundary to move down
to the top of the first fixed task, common, or
driver in the partition at the time the /TOP
keyword is executed. If nothing is loaded into
the partition, the partition assumes a size of one
64-byte block.
(
Examples:
)SET /TOP=TSTPAR: +5 tBrn
Moves the top boundary
64-byte blocks.
of
TSTPAR
up
by
five
)SET /TOP=PAR23: -* tBrn
Moves the top boundary of PAR23
possible.
down
as
far
as
c
3-260
MCR COMMANDS
c
SET (Cont.)
/TTSYNC[=ttnn:]
(Full-duplex terminal driver only.)
Enables the terminal
synchronization option for the specified terminal. When
/TTSYNC is enabled, you can press CTRL/S to halt output to
the terminal screen, and CTRL/Q to resume output to the
terminal screen.
The default terminal setting is /TTSYNC.
When you omit =ttnn:, the system displays
terminals that have terminal synchronization.
all
of
the
Examples:
>SET
/TTSYNC=TT20:~
Enables terminal synchronization for TT20:.
>SET /TTSYNC
TTSYNC=TT7:
TTSYNC=TTll :
TTSYNC=TT20:
TTSYNC=RT5:
(
~
Displays all of the terminals that
synchronization enabled.
have
terminal
/NOTTSYNC[=ttnn:]
(Full-duplex terminal driver only.) Disables the terminal
If
synchronization option for the specified terminal.
terminal synchronization is disabled on your terminal, the
system does not respond when you press CTRL/S or CTRL/Q.
c
Note that, if you set your terminal to /NOTTSYNC, the NO
SCROLL key on VT100-series terminals and the HOLD SCREEN key
on VT200-se.ries terminals will no longer work.
When you omit =ttnn:, the system displays all of
terminals that do not have terminal synchronization.
the
Examples:
>SET
/NOTTSYNC=TT13:~
Disables terminal synchronization for TT13:.
>SET /NOTTSYNC
TTSYNC=TT13:
~
Displays all of the terminals that
synchronization disabled.
have
terminal
/TYPEAHEAD[=ttnn: [size]]
(
Instructs the terminal
(Full-duplex terminal driver only.)
driver to store input characters in a buffer before passing
the characters to a requesting task. Thus, characters input
between requests are not lost.
3-261
MCR COMMANDS
SET (Cont.)
(
A nonprivileged user can display all terminals that have
typeahead option enabled but can only enable the option
TI:.
A privileged user can enable typeahead for
terminal.
These rules also apply to the size of
typeahead buffer.
the
for
any
the
When you omit =ttnn:, the system displays
terminals that have typeahead enabled.
of
the
have
the
all
Examples:
>SET /TYPEAHEAD=TT3:®ill
Enables the typeahead option for TT3:.
>SET /TYPEAHEAD ®ill
TYPEAHEAD=TTl:
TYPEAHEAD=TT2:
TYPEAHEAD=TT7:
TYPEAHEAD=TT12:
Displays all of the terminals
typeahead oPtion enabled.
that
c
/NOTYPEAHEAD[=ttnn:]
(Full-duplex terminal driver only.) Disables the typeahead
option; the terminal driver does not store input characters
in a buffer to prevent their loss.
A nonprivileged user can display all te.rminals that have the
typeahead option disabled but can only disable the option
for TI:. A privileged user can disable typeahead for any
terminal.
When you omit =ttnn:, the system displays
terminals that have typeahead disabled.
all
of
the
Examples:
>SET /NOTYPEAHEAD=TT3:®ill
Disables the typeahead option for TT3:.
>SET /NOTYPEAHEAD ®ill
NOTYPEAHEAD=TTO:
NOTYPEAHEAD=TT4:
Displays all of the terminals that have
disabled.
3-262
typeahead
c
MCR COMMANDS
(
SET (Cont.)
jUIC[=[uic] [:ttnn:]]
Establishes the specified UIC as the default UIC for the
terminal. Unless ttnn: is specified, the default UIC is set
for TI:.
If the system supports multiuser protection
(some
RSX-IIM and all RSX-IIM-PLUS operating systems) and you are
a privileged user, the command also sets the terminal's
protection UIC (see Section 2.2.1).
b
In a single-user system, all tasks run from the terminal are
run with the UIC of the terminal.
In a multiuser protection
system, a privileged user can override the terminal UIC with
the JUIC keyword for the RUN command. External MCR function
tasks are also requested with the terminal's UIC.
These
tasks are:
the MCR MOUNT, INSTALL, DISMOUNT, and UFO
commands (which run as tasks), and all system-supplied
software.
A nonprivileged user can only display and change the default
UIC for TI:. A privileged user can display and change the
default UIC for any terminal.
When you omit =[uic], the system displays the current
default UIC for TI:.
When you omit =[uic] but specify
=ttnn:, the system displays the current default UIC for that
terminal.
(
Examples:
(
>SET JUIC ruJ
UIC=[lO,lO]
Displays the current default UIC for terminal TI:.
>SET jUIC=[303,3]ruJ
Sets the default UIC for terminal TI:
to [303,3].
>SET jUIC=TT12:ruJ
UIC=[12,20]
Displays the current default UIC for TT12:.
>SET jDEF ruJ
DRS: [1,1]
Named TT3 :
[1,1]
Protection UIC:
Displays the current
protection UIC.
3-263
default
directory
and
MCR COMMANDS
(
SET (Cont.)
>SET /UIC=[12,10] ®ill
>SET /DEF ®ill
DRS: [1,1]
Named TT3:
Protection UIC:
[12,10]
Sets the default UIC to [12,10], but the default
directory does not change when you change the
default UIC in named directory mode.
> SET /NONAMED ®ill
> SET /DEF ®ill
DRS: [12,10] Nonamed TT3:
Protection UIC:
[12,10]
In nonamed (numeric) directory mode, the default
directory changes to match the specified UIC.
>SET /UIC=[200,200]®ill
>SET /UIC ®ill
Default UFD:
[200,200]
Protection UIC:
[200,200]
Changes both the default User's File Directory
(UFD), and protection UIC. In npnamed directory
mode, this behavior is compatible with previous
versions of RSX. Remember that the default UFD is
used for the location of
files
while
the
protection UIC is used to determine privilege for
file protection purposes.
/VFILL[=ttnn:]
c
(Full-duplex terminal driver only.)
Enables the vertical
fill characters option for the specified terminal. The
option instructs the terminal driver to add four fill
characters following each line feed.
A nonprivileged user can display all terminals that have the
vertical fill characters option enabled but can only enable
it for TI:. A privileged user can enable the option for any
terminal.
When you omit =ttnn:, the system
terminals that have the vertical
enabled.
displays all of the
fill characters option
Examples:
>SET /VFILL ®ill
VFILL=TTO:
VFILL=TT1:
Displays all of the terminals with
fill characters option enabled.
the
vertical
>SET /VFILL=TT3:®ill
Instructs the full-duplex terminal driver to add
four fill characters following each line feed at
TT3:.
3-264
c
MCR COMMANDS
SET (Cont.)
/NOVFILL[=ttnn:]
(Full-duplex terminal driver only.) Disables the
fill characters option for the specified terminal.
vertical
A nonprivileged user can display all terminals that have the
vertical fill characters option disabled but can only
disable it for TI:.
A privileged user can disable the
option for any terminal.
When you omit =ttnn:, the system
terminals that have the vertical
disabled.
displays all of the
fill characters option
Examples:
>SET /NOVFILL
NOVFILL=TT2:
NOVFILL=TT4:
~
Displays all of the terminals that have
vertical fill characters option disabled.
>SET /NOVFILL=TT3:
the
~
Disables the option for TT3:.
(
/WCHK [=ddnn:]
Specifies that all write operations are to be followed by a
write check for all Files-ll disk devices except OX: and
DY:. The checks assure the reliability of data transfers to
the specified disk.
However, writing is slowed because
there are two I/O operations instead of just one.
(
A nonprivileged user can only display the devices that have
write checking enabled. A privileged user can enable write
checking for any device that supports it.
When you omit =ddnn:, the system displays all the
disk devices that have write checking enabled.
Files-ll
Examples:
>SET /WCHK
WCHK=DBO:
WCHK=DKO:
~
Displays all the Files-ll disk devices
write checking enabled.
(
>SET
/WCHK=DK1:~
Enables write checking for DK1:.
3-265
that
have
MCR COMMANDS
(
SET (Cont.)
/NOWCHK[=ddnn:]
Specifies that write checking is
specified device.
to
be
disabled
for
the
A nonprivileged user can only display the devices that have
write checking disabled.
A privileged user can disable
write checking for any device.
When you omit =ddnn:, the system displays all the Files-II
disk devices except OX: and DY: that have write checking
disabled.
Examples:
>SET /NOWCHK mJ
NOWCHK=DBI:
Displays all the devices that
checking but have it disabled.
>SE~
support
write
/NOWCHK=DKI:mJ
Disables write checking for"DKI:.
/WRAP [=ttnn:]
(Full-duplex terminal driver only.)
Enables the wrap-around
option.
The wrap-around option instructs the terminal
driver to generate a carriage return/line feed sequence when
the number of input characters exceeds the terminal's buffer
size. The carriage return/line feed sequence is transparent
and does not appear in the input buffer.
A nonprivileged user can display all terminals that have the
wrap-around option enabled but can only enable it for TI:.
A privileged user can enable wrap-around for any terminal.
When you omit =ttnn:, the system displays all
terminals that have the wrap-around option enabled.
of
the
have
the
c
c
Examples:
>SET /WRAP mJ
WRAP=TTI:
WRAP=TT2:
Displays all of the terminals
wrap-around option enabled.
that
>SET /WRAP=TT3:mJ
Enables the wrap-around option for TT3:.
/NOWRAP[=ttnn:]
Disables the wrap-around option; the terminal driver does
not accept input characters beyond the buffer size for the
terminal.
3-266
c
MCR COMMANDS
c
SET (Cont.)
A nonprivileged user can display all terminals that have the
wrap-around option disabled but can only disable it for TI:.
A privileged user can disable the option for any terminal.
When you omit =ttnn:, the system displays all of
terminals that have the wrap-around option disabled.
the
Examples:
>SET /NOWRAP mJ
NOWRAP=TTO:
NOWRAP=TT4 :
Displays all of the terminals
wrap-around option disabled.
that
have
the
>SET /NOWRAP=TT3:mJ
Disables the wrap-around option for TT3:.
Notes on Memory Allocation Keywords (see Table 3-2):
•
If a partition contains an installed task common or loaded
driver and a keyword (for example, /NOMAIN or /NOSUB) attempts
to eliminate the partition, the system rejects the command.
•
When defining a main partition or a subpartition, the name
must not already be defined as a partition.
In addition, a
main partition cannot overlap any other main partition, nor
can a subpartition of a main partition overlap any other
subpartition of the main partition. An exception is for DEV
partitions,
which can overlap.
Subpartitions cannot be
created on the I/O page.
•
Once you allocate space to the dynamic storage region
(pool),
the space ~an never be recovered for use in partitions.
•
System-controlled partitions cannot include
subpartitions
explicity defined by the SET command. An attempt to define
subpartitions in system-controlled partitions in this way will
be rejected. The Executive dynamically defines subpartitions
in a system-controlled partition as they are needed for tasks
installed in the partition.
(
(
3-267
MCR COMMANDS
(
SET (Cont.)
Command Error Messages:
SET --Alignment error
An attempt was made to create
address or size conflicted
physical memory size.
a partition, but the base
with existing partitions or
SET -- Cannot inquire remote terminal
You specified a remote terminal of the type HTn:
SET /INQUIRE keyword. This is not allowed.
with
the
SET -- Cannot remove driver common
On systems with a Q-bus, the driver common DYCOM cannot be
removed if the DY driver is loaded. Also, the driver common
PUCOM cannot be removed if either the DU driver or the MU
driver is loaded.
SET -- Cannot remove executive common
The executive commons (on systems that support executive
partitions)
cannot be removed from the running system. The
executive commons must be installed and removed with VMR
(see the RSX-llM/M-PLUS System Management Guide) •
(
SET -- Cannot use set host from remote terminal
You issued the SET /HOST command from a remote terminal.
The SET /HOST command can be issued only from physical,
local terminals.
SET -- CLI is restricted
An attempt was made to set a terminal to a CLI, but the CLI
was initialized with the /RESTRICT subkeyword. This means
that only the CLI itself can set a terminal to the CLI.
SET -- CLI requires the terminal to be logged in
An attempt was made to set a terminal to
terminal is not logged in.
The CLI
commands from logged-in terminals.
a CLI, but the
will only accept
SET -- Crash device has been successfully loaded
This is an informational message. It tells you that the
device specified with the SET /CRASH DEVICE keyword has been
successfully loaded as the crash devlce for the system.
SET -- Default directory operation failed
This error usually occurs because of low pool
Wait a few minutes and retry the operation.
conditions.
SET -- Device busy
An attempt was made to set a terminal characteristic
terminal that is busy (attached).
3-268
for
a
(
MCR COMMANDS
SET (Cont.)
SET -- Device is not in system
You specified a device with the SET /CRASH DEVICE keyword
that is not in the current system configuration but you did
not specify the address of the device's CSR.
SET -- Device not in system
You specified a device in the command line that
the current system configuration.
is
not
in
SET -- Device not terminal
An attempt was made to set terminal
device that is not a terminal.
characteristics
for
a
SET -- Device not variable speed multiplexer
An attempt was made to set the baud rate for a terminal that
was not attached to a DH11, DHVl1, DZ11, DZQ11, or DZV11
multiplexer.
SET -- Device offline [] or privileged diagnostic
c
The device specified in the command line, although generated
into the system, was not physically present in the host
configuration. If the off-line device is a magnetic tape,
the message includes the device unit.
SET -- ERROR, Task PSW is not installed
The task that changes passwords is not installed in the
system.
Ask your system manager to install PSW, or have
your password changed with the ACNT utility (see Chapter 2).
SET -- Feature not supported
The command keyword specified a feature or device
currently not incorporated into the system.
that
is
SET -- Illegal password syntax
You typed a password using incorrect syntax.
Type in a
password consisting of 39 or fewer Radix-50 characters. The
Radix-50 characters are the 26 uppercase letters A through
Z, the numerals 0 to 9, the period (.), and the dollar sign
($) •
3-269
MCR COMMANDS
(
SET (Cont.)
SET -- Invalid speed
The multiplexer line does not support the requested speed,
or the command specifJed unequal receive and transmit baud
rates for a DZll, DZQll, or DZVll.
These multiplexers do
not support split speeds.
SET -- IO.STC VV$CHE DC$SET OR DC$ACT FAILED
Data cach~ng attributes could not be set for
specified.
the
disk
you
was
not
SET -- Line not DZll
The command attempted to set to remote a line that
attached to a DZll multiplexer.
c
c
SET -- New password verification error
The password you typed in response to the "Verification"
prompt was not the same as the one you typed in response to
the "New password" prompt. The password remains unchanged.
Try again.
3-270
MCR COMMANDS
(
SET (Cont.)
SET -- Nonexistent memory
An attempt was made to define
memory.
a
partition
in
nonexistent
SET -- Old password validation error - password unchanged
You typed in your old password incorrectly.
correct password and retype it.
Check
for
the
a
name
SET -- Partition already exists
An attempt was made
already in use.
to
define
a
partition
with
SET -- Partition not system-controlled
(
An attempt was made to move the top boundary of a partition
with
the /TOP keyword.
This can be done only with
system-controlled partitions.
SET -- Space used
An attempt was made to create a partition or subpartition in
a storage area that is already occupied.
SET
(
System disk chosen as crash device
This is a warning message.
It warns you that you specified
the system device as the crash dump device with the SET
/CRASH DEVICE keyword. The system device will be loaded as
the crash dump device, but it is recommended that you do not
use the system device as the crash dump device.
SET -- Task installed in partition
An attempt was made to eliminate a partition or subpartition
that contains installed tasks.
SET -- Timeout on response
You issued the SET /PASSWORD command, but allowed a prompt
to wait 60 seconds without typing in a response. Your
password remains unchanged. Try again.
(
3-271
MCR COMMANDS
(~
SET (Cont.)
SET -- Write check not supported
An attempt was made to enable write checking on a device
that does not support it. See the oescription of the /WCHK
keyword for the valid devices.
(
(
3-272
MCRCOMMANOS
SSM
(
3.43
SYSTEM SERVICE MESSAGE (P)
The SYSTEM SERVICE MESSAGE (SSM) command inserts text into the error
log file.
The text appears in error log reports produced by the error
log report generator.
For information on the report generator, see the RSX-llM/M-PLUS
Logging Manual.
Error
Format:
SSM
messag~
message
Any text string up to a maximum of 79 characters.
Example:
>SSM TESTING VOLUME INTEGRITY ON OMl:, POSSIBLE FORMAT ERRORS. @]
Inserts the message into the error log file.
(
(
3-273
MCR COMMANDS
(
c
c
(
3-274
MCR COMMANDS
TAL
(~
3.45
TASKLIST - ATL FORMAT (NP)
The TAL command displays the na~es and status of all tasks or of a
specific task installed in the syste~.
The display for~at is the sa~e
as that of the ACTIVE TASK LIST (ATL) command. See the ATL command
for a description of the printout.
For~at:
TAL
[taskna~e]
taskna~e
The name of a specific task.
Examples:
c
c
3-275
MCR COMMANDS
TAS
3.46
(
TASKLIST (NP)
The TASKLIST command displays a description of each
The display contains the following information:
1.
Task name
2.
Task version identification
3.
Partition name
4.
Task priority
5.
installed
task.
'Size of task in bytes (octal)
6.
Load device identification
7.
Disk address logical block number (octal)
8.
Task memory state
~
..
Format:
TAS[KLIST]
[taskname] [/DEV=ddnn:]
c
taskname
The name of a specific task.
/DEV=ddnn:
Displays the names and status of all
specified device.
tasks
installed
If you specify both taskname and /DEV, the system
information about the task installed from that device.
from
the
displays
Examples:
>TAS mJ
LDR ••• 07.05
03.3
TKTN
RMDEMO X03.03
MTAACP 0006
F11MSG VOOIO
MCR ••• 3.2
TAST17 01
••• STO 000005
••• BYE 01.5
FllACP M0235
SECFCP M0235
DTAACP M0235
••• DMO 03.2
••• INI 03.1
••• MOU 03.01
••• UFD V0407
LDRPAR
SYSPAR
GEN
GEN
GEN
SYSPAR
GEN
SYSPAR
GEN
FCPPAR
GEN
GEN
GEN
GEN
GEN
GEN
248.
248.
225.
200.
200.
160.
160.
151.
150.
149.
149.
149.
140.
140.
140.
140.
00002200
00010000
00013700
00013000
00005400
00010000
00025000
00010000
00040000
00040000
00026200
00026200
00040000
00040000
00040000
00040000
3-276
LBO:-Ol035303 FIXED
LBO :-01126742
SYO:-00352100
DSO:-00000777
SYO:-Ol053030
LBO:-Ol05l626
LBO:-OI05l676
SYO:-01136540
LBO:-Ol051337
LBO:-Ol052445
SYO:-00055463
SYO:-Ol052554
LBO: -01051403.
LBO:-Ol05l56l
LBO:-Ol05l653
LBO:-OIO
(
MCR COMMANDS
(
lAS (Cont.)
(User typed CTRL/O to suppress further output.)
)TAS /DEV=DRO:®ID
DROOFI M0323 SYSPAR
Fl1ACP M0323 GEN
DBOIFl M0323 GEN
DB07Fl M0323 SYSPAR
ERRLOG Vl.01 GEN
PMD ••• 04.0
GEN
HRC ••• 02
GEN
SYSLOG 1.02
GEN
••• INS 06
GEN
149.
149.
149.
149.
148.
140.
140.
00055700
00044000
00044000
00044000
00042200
00015200
00055100
130. 00016300
100. 00035400
LBO:-00475656 FIXED
LBO:-00315566
LBO:-00315566
LBO:"':00315566 FIXED
LBO:-00335276
LBO:-00503535
LBO:-00505331
LBO :-0050.4250
LBO:-00502750
The displays contain from left to right:
task name, task
version,
task version identification, partition name, task
. priority, task size, load device identification, logical block
number on the load device, and task memory state. On a processor
with less than 124K words of memory, the size field
(fifth
column) contains 6-digit rather than 8-digit numbers.
FIXED indicates that the task is fixed in memory.
CHECKPOINTED indicates that the task has been swapped
memory to make room for a task with a higher priority.
c
out
of
If the task version identification field is blank (the rest of
the line is offset to the left) or contains meaningless output,
the task was installed from a disk that has since been replaced
or removed from the drive.
Command Error Message:
TAS -- Task not in system
The task specified in the
installed in the system.
c
3-277
command
line
is
not
currently
MCR COMMANDS
c
TIM
TIME (NP,P)
3.47
The TIME command allows you to:
•
Set the current time of day (privileged)
•
Set the current date (privileged)
•
Display the current time and date
Format:
TIM [E]
[hrs :mins [: secs]]
[ml/day/year]
or
TIM [E]
[hrs :mins [: secs] ] [day-m2-year]
hrs
The value for hours, which can be between 0 and 23.
mins
The value for minutes, which can be between 0 and 59.
secs
The value for seconds, which can be between 0 and 59.
for seconds is an optional parameter.)
(The value
c
ml
The value for the month, specified as a number between 1 and 12.
m2
c
The value for the month, specified as a 3-letter abbreviation.
day
The value for the day of the month, which can be
31.
between
1
and
year
The value for the year, which can be between 0 and 99.
is relative to 1900, so that 1985 is specified as 85.
The
year
Notes:
•
When the command specifies neither time nor date, the system
displays the current time and date on the entering terminal.
•
If a privileged user specifies the time and date, the command
sets the clock and calendar.
If, only the time is specified,
only the clock is set; if only the date is specified, only the
calendar is set.
3-278
MCR COMMANDS
c
TIM (Cont.)
•
A privileged user can specify the
order.
time
•
The form used to specify the date does not affect the display
format. The date is always displayed as day-month-year.
•
All numeric values are decimal.
necessary (or permitted).
No
and
date
terminating
in
period
Examples:
>TIM ffi)
10:23:31 26-SEP-85
Displays the current time and date.
>TIM 01:02 9/23/85
ffi)
Sets the time to 01:02:00 and the date to 23-Sep-85.
c
3-279
either
is
MCR COMMANDS
UFO
3.48
(
USER FILE DIRECTORY (NP,P)
The USER FILE DIRECTORY (UFO) command creates a User File Directory
(UFO)
on a Files-II volume and enters its name into the Master File
Directory (MFD).
(See Section 2.1.1 for further information about
UFOs.)
Before creating a UFO, you must first initialize and
MOU) the volume.
mount
(INI
and
On multiuser protection systems, a nonprivileged user can create
directory only on a volume mounted on a privately allocated device.
privileged user can create a directory on any mounted volume.
a
A
Format:
UFO ddnn:[volume-label] [g,m] [/keyword(s)]
ddnn:
Device unit containing the volume on which
created will reside.
the
directory
being
There is no default device unit; you must specify one.
volume-label
If specified, the label is compared with the label on the volume.
If the names match, a directory can be created.
If they do not
match, the command is rejected.
By default, the volume-label is null; no check is made if you
not specify a volume-label.
c
do
[g,m]
Specifies the directory that you want to create.
On RSX-IIM
operating systems, the directory must be a numeric directory of
the form [g,m]. The variables g and m represent the group and
member numbers, respectively, and their values can be between 1
and 377 (octal) • On RSX-IIM-PLUS operating systems, the directory
can be a named or a numeric directory. The square brackets are
required parts of the directory syntax.
There is no default for the directory, you must specify one.
,/ALLOC=number
The number of directory entries for which space in the UFO is to
be allocated.
The specified number is rounded up to the next
multiple of 32 (decimal) •
The default is 32 (decimal) •
(
3-280
MCR COMMANDS
UFO (Cont.)
/PRO=[system,owner,group,world]
Establishes access rights for the directory file.
Access codes
consist of four groups of four codes in the access rights word,
as follows:
R - Read access
W - Write access
E - Extend access
o - Delete access
In each instance, the absence of a code means that the user class
is denied that type of access.
The square brackets are required syntax.
The defaul ts are:
[RWED, RWED, RWED, R] •
Example:
>UFD DMl: [1,1]
c
~
Creates a directory for the UIC [1,1] on DMl:. The name and
file number of the number of the UFO file are entered into
the MFD. The name of the UFO is OOlOOl.DIRil, and its owner
is UIC [1,1].
Command Error Messages:
UFO -- Can't read MCR command buffer
The directory was initiated by a RUN command rather than
an MCR command.
as
UFO -- Directory already exists
The requested directory already exists on the volume.
c~
UFO -- Failed to create directory
No space existed on the volume or an I/O error occurred.
UFO -- Failed to enter in MFD
There was no room in the MFD or on the
error occurred on the volume.
volume,
or
an
I/O
UFO -- Home block I/O error
An error was detected while the Volume Home Block was
read.
being
UFO --Not Files-II device
The volume on which the directory was to be created was
a Files-II volume and therefore could not support UFOs.
3-281
not
MCR COMMANDS
c
UFO (Cont.)
UFO -- Volume not mounted
The volume on which a directory is to
mounted.
be
created
must
be
UFO -- Write attributes failure
An error was encountered while the attributes of either
MFD or the newly created UFO were being written.
the
UFO -- Wrong volume
The volume label and the label specified in the command line'
did not match.
c
c
3-282
MCR COMMANDS
(
UNB
3.49
UNBLOCK (NP,P)
The UNBLOCK command continues the execution of a previously blocked
active task or allows a previously blocked dormant task to execute if
it is requested to do so.
(See the description of the BLOCK command.)
On systems with multiuser protection, a nonprivileged user can unblock
any active task running from the issuing terminal. A privileged user
can unblock any task. On systems without multiuser protection, any
user can unblock any task.
The system automatically unblocks an active task when it is aborted.
Format:
UNB[LOCK]
[taskname] [/TERM=ttnn:]
taskname
The name of the task. If you omit taskname, the command unblocks
the task requested from the issuing terminal (task ttnn).
(
Examples:
>UNB TST ffi)
Unblocks task TSTT36 and allows it to continue executing.
(TT36:
is the number of the terminal from which the task is
running. )
c
3-283
MCR COMMANDS
UNF
3.50
(
UNFIX (P)
The UNFIX command frees a fixed task from memory. This allows tasks
that have been waiting for the partition in which the fixed task
resides to compete for the partition. However, if a fixed task exits
or aborts, it still occupies the physical memory in the partition.
UNFIX is the complement of the FIX command.
Format:
UNF[IX] taskname
tasknanie
The name of the task.
~)
c
Examples:
>UNFIX }(KE (8§Il
Unfixes task XKE, freeing the partition in which it
for task competition.
resides
Command, Error Message:
UNF -- Task not fixed
An attempt was made to unfix a task that was not fixed.
3-284
MeR COMMANDS
UNL
(
3.51
UNLOAD (P)
The UNLOAD command removes a loadable device driver from memory.
If a
device is mounted, attached, or has outstanding I/O, its driver cannot
be unloaded. Also, the UNLOAD command cannot remove a data base from
memory, even if the data base was loaded by means of the LOAD command.
To unload a device driver from memory, the driver's symbol table (STB)
file must reside on the system device (LB:) in the system directory.
The SET /SYSUIC command displays and defines the system directory, but
usual values are
[1,50]
for unmapped systems and [1,54] for mapped
systems.
Format:
UNL[OAD] dd:[/keyword]
dd:
A 2-character ASCII device name.
Keyword:
c
Example:
>UNL LP:
~
Unloads the loadable device driver for device LP:.
Command Error Messages:
UNL -- Device not in system
No such device exists in the system.
UNL -- Device not mounted
c
The system device (LB:) was not mounted.
3-285
MCR COMMANDS
c
UNL (Cont.)
UNL -- Driver built with wrong Executive STB file
The STB file for the
current Executive.
driver
is
not
compatible
with
the
UNL -- Driver cannot be unloaded
The UNLOAD command attempted to remove a
permanently
resident device driver (that is, a driver built as part of
the Executive).
UNL -- Driver not 10aded
The device driver specified in the UNLOAD command
not resident in memory.
line
was
UNL -- File has illegal STB format
The driver's STB file contained illegal object code or data.
UNL -- Illegal value for symbol in file
The symbol symname is defined to an illegal value by the
file ddDRV.STB.
Since ddDRV •. STB had to pass a previous
in~pection by the LOA command, there
probably has been a
procedural error or ddDRV.STB has been corrupted.
c
c
UNL -- Symbol is doubly defined by file
The symbol symname is defined twice in the specified file.
Duplicate systems are illegal. The driver remains loaded.
UNL -- Symbol is undefined by file
The symbol symname was found in the specified file, but
symbol is not defined.
3-286
the
MCR COMMANDS
UNS
(
3.52
UNSTOP (NP,P)
The UNSTOP command continues execution of a task that has been stopped
internally by the Executive.
Examples of stopped tasks a.re tasks that
have issued a STOP$S or RCST$ (RECEIVE DATA OR STOP) directive.
A nonprivileged user can only unstop tasks being run from the
terminal. A privileged user can unstop any stopped t'ask.
issuing
Format:
UNS [TOP]
[taskname] [/TERM=ttnnn:]
taskname
The name of the task.
If you omit taskname, the command unstops
the task being run from the issuing terminal (task ttnnn) •
Examples:
RSX-llM/M-PLUS operating systems:
c
>UNS
TST ®TIl
Clears the stop bit for
task TSTTl7 and allows it to
continue executing.
(TTl7:
is the number of the terminal
from which the task is running.)
3-287
(
APPENDIX A
MCR AND TKTN MESSAGES
Messages from MCR and TKTN appear in this appendix in alphabetical
order. Some messages include remedial action to be taken by the user.
This is not included with messages for which the required action is
obvious or contained in the description of the message.
The XXX in the messages indicates the
that detected the error.
3-character
component
of
MCR
11/40 F.P. exception
Explanation: This is a TKTN message.
The task encountered a
floating point exception while executing on a PDP-ll/40 and no
SST routine was specified to process the trap.
Aborted via directive or CLI
(
Explanation: This is a TKTN message.
Either an Executive
directive or a CLI command issued by another task caused the task
to be aborted.
Aborted via CLI
Explanation:
task.
This is a TKTN message.
A CLI command aborted
the
XXX -- Account file open failure
(
Explanation: The account file was open for another user
disk containing the account file was not mounted.
User Action:
or
the
Reenter the command line.
XXX -- Addressing extensions not supported
Explanation: The command tried to install a task with a VSECT
(virtual section)
into a system that does not support the
feature.
A-I
MeR AND TKTN MESSAGES
xxx --
Alignment error
Explanation: An attempt was made to create a partition, but the
base address or size conflicted with existing partitions or
physical memory size.
xxx --
(
Allocation for SYS file exceeds volume limit
Explanation: The system was unable to allocate the system file
from the specified block because intermediate bad blocks or
end~of-volume was encountered.
xxx --
Ambiguous help qualifier
Explanation:
help file.
The qualifier does not specify a unique part of the
User Action: Reenter the command line, specifying the
more completely.
xxx --
Ambiguous help synonym
Explanation:
unique.
xxx --
qualifier
The qualifier
referenced
as
a
synonym
was
not
Assign failure
Explanation:
assignments.
The HELLO command could not complete login
logical
AST abort. Bad stack
Explanation:
because the
stack.
xxx --
An AST cannot be effected
be pushed onto the task's
Bad block file corrupt - data ignored
Explanation:
xxx --
This is a TKTN message.
AST parameters cannot
Ba~
The bad block file contained bad data.
block file full
Explanation:
The disk had more than 102(10) bad regions on it.
XXX -- Bad block header I/O error
Explanation:
file header.
xxx --
A write error was detected in writing the bad-block
Bad task file VBN, task removed -
Explanation: The system removed the specified task because it
contained a bad Virtual Block Number (VBN) in its file header.
The task image file has probably been corrupted.
xxx --
Base address must be on 4K boundary
Explanation: The base virtual address of the task is not on a 4K
boundary. This message applies only to mapped systems.
A-2
c
MCR AND TKTN MESSAGES
xxx --
(
Base mismatch common block
Explanation: The base address of the partition, as recorded in
the task image, did not match the base address of the common
block.
xxx --
Block(s) exceed volume limit
Explanation: The specified
physical size of the volume.
block
(or
blocks)
exceeded
the
volume
boot
XXX -- Boot block write error
Explanation:
block.
xxx --
An error was detected in writing
Booted device's driver not loaded
Explanation: VMR has been used to
system (booted) disk.
xxx --
c
the
unload
the
driver
for
the
Booted device not in system --
Explanation: When the system was booted, SAVE could not find the
booted device
(device name dd, physical unit number nnn, CSR
mmmmmm) in the system data structures. For example, the system
was booted from DB3:, but the system data structures include only
DBO: and OBI:.
xxx --
Byte address
Explanation: The address specified as the argument to the OPEN
command was an odd address. For example, the address 3000 is a
.legal address, but the address 3001 is not.
c
xxx --
Cannot install privileged task from non-privileged terminal
Explanation: This message applies to
multiuser
protection
systems only.
A nonprivileged user attempted to install a
privileged task. Only a privileged user can install a privileged
task.
xxx --
Cannot LOAD/UNLOAD a pseudo device
Explanation: The device you attempted to load is a
device. You must specify the name of a physical device.
xxx --
Can't read MCR command buffer
Explanation: The UFD was initiated by a RUN command rather
as an MCR command.
xxx --
c
pseudo
than
Checkpoint area too small
Explanation: The area allocated for checkpointing the task was
smaller than the partition into which the task was being
installed. This message applies only to systems that do not
support the dynamic allocation of checkpoint space.
A-3
MCR AND TKTN MESSAGES
Checkpoint failure. Read error
Explanation: This is a TKTN message. The task could not be read
back into memory after being checkpointed.
xxx --
(
Checkpoint file already in use on device
Explanation: A previous ACS command established a checkpoint
file on the volume mounted on the specified device unit. A
volUme can contain only one checkpoint file.
xxx --
Checkpoint file header I/O error
Explanation:
file header.
xxx --
An error was detected
in
writing
the
checkpoint
Checkpoint file now inactive
Explanation: This message appears after an ACS command has been
issued to discontinue a checkpoint file and the file does not
contain any checkpointed tasks. The message indicates that use
of the file was discontinued immediately after the command was
issued. If the file is still in use, TKTN will issue a message
when the fi,le is finally discontinued.
***
-- Checkpoint file now inactive
Explanation: This is a TKTN message. A request to discontinue
use of a checkpoint file on device ddnn: has been satisfied.
The need to return checkpointed tasks from the discontinued file
back into memory caused the delay between the request and this
message.
xxx --
Checkpodnt file still active
c
Explanation: The command attempted to dismount a volume that
contained an active checkpoint file.
The volume cannot be
dismounted until the checkpoint file has been discontinued.
User Action:
Issue an ACS command to discontinue the file and
reissue the DMO command when the system issues a message to
indicate that the checkpoint file is inactive.
xxx --
Checkpoint file still in use on
Explanation: The system cannot be saved because
file on the specified device is still active.
User Action: Deallocate the checkpoint file
command) and reenter the SAVE command line.
***
a
(see
checkpoint
the
c
ACS
Checkpoint space allocation failure
Explanation: This is a TKTN message. The checkpoint file did
enough
space for the specified task to be
not
contain
checkpointed.
XXX -- Checkpoint space too small, using checkpoint file
Explanation: This is a warning message only.
The checkpoint
space allocated in the task image file is too small for the size
of the task (usually because of the /INC keyword).
The system
supports the dynamic allocation of checkpoint space and will
therefore use a checkpoint file to contain the checkpointed task.
A-4
(
MCR AND TKTN MESSAGES
***
-- Checkpoint write error
Explanation: This is a TKTN message. A write failure occurred
while the system was attempting to checkpoint the specified task.
xxx --
Circular redirect error
Explanation: The attempt to redirect a device would result in
circular list of redirections.
xxx --
a
Command input error
Explanation: Circumstances prevented the BROADCAST task from
receIvIng the command line
(usually an indirect command file
could not be found); or, a system directive or the RUN command,
rather than the HELLO command, has initiated the HELLO task; or
an error occurred while MOUNT was attempting to read the command
line~
User Action:
xxx --
(
Command I/O error
Explanation: An I/O error was encountered while the command line
was being read.
xxx --
Command syntax error
Explanation:
xxx --
c
In the case of BROADCAST, reenter the command line.
The command line had an improper format.
Command too long
Explanation: An INI or MOUNT command, including continuation
lines, exceeded the maximum length of 512(10) characters.
xxx --
Common block is task
p~rtition
Explanation: A task's request for access to a common block was
rejected because the requested partition was a task partition.
xxx --
Common block not loaded
Explanation: The specified common block was linked to
but had not been installed in the system.
User Action:
xxx --
task
Install the common block, then install the task.
Common block occupied
Explanation: An attempt was made to load a task
block that was already occupied.
xxx --
the
into
a
common
Common block parameter mismatch
Explanation: Parameters of a common block did not match those in
the task's label block.
A-5
MCR AND TKTN MESSAGES
xxx --
Common block segment count error
Explanation: The command installed a resident library with
overlays, but the number of overlay segments specified in the
task header is different from the number specified in the segment
descriptors.
xxx --
Common, driver or task above system image file limit
Explanation: A system cannot be saved if addresses for a
memory-resident structure are higher than the highest address of
main memory written to the system image file.
User Action:
problem.
Use the PAR command to determine the cause
of
the
c
(i
A-6
MCR AND TKTN MESSAGES
xxx --
(
Data error
Explanation: The specified bad-block
contiguous region size is too large.
User Action:
xxx --
number
or
the
specified
Reenter a valid number or size.
Device attached
Explanation: The specified device cannot be allocated because it
is attached to a running task or the CLI command cannot do a
/SHOW display because the terminal is attached to another task.
xxx --
Device
no~
allocated to this terminal
Explanation: The command line specified a private device that
was allocated to a terminal other than the one from which the
command was issued.
xxx --
Device not in system
Explanation: The device specified in the command line is not
the current system configuration.
c
xxx --
in
Device not in system
Explanation: The specified device driver does not exist in the
system, or the data base for the device driver is not in the
system or in the driver's task image.
xxx --
Device not mounted
Explanation: The device specified in the file specification was
not mounted.
In response to a LOAD or UNLOAD command, the system
device (LB:) was not mounted.
(
xxx --
Device not redirectable
Explanation:
xxx --
The specified device cannot be redirected.
Device not ready -
Explanation: The command line specified a volume
ready (not up to speed).
xxx --
that
was
not
Device not terminal
Explanation: An attempt was made to set terminal characteristics
for or the /TERM keyword was specified for a device that is not a
terminal.
xxx --
Device not variable speed multiplexer
Explanation: An attempt was made to set the baud rate for
terminal that was not attached to a DHll or DZll multiplexer.
c
A-7
a
MeR AND TKTN MESSAGES
xxx --
Device offline[-ddnn:]
Explanation: The device specified in the command line, although
generated into the system, was not physically present in the host
configuration. If the off-line device is a magnetic tape drive,
the message includes the device unit.
xxx --
Device write locked -
Explanation: The
write-locked.
xxx --
command
line
specified
a
volume
that
was
Directory already exists
Explanation:
xxx --
The requested UFD already exists on the volume.
Disk is alignment cartridge
Explanation: The last track on an
RK06/07,
RLOI/02,
or
RM02/03/05/80/RP07 disk identified the volume as an alignment
cartridge, which cannot be initialized as a Files-II volume.
An
alignment cartridge is specifically formatted for aligning disk
read/write heads.
***
(
~\
-- Dismount complete
Explanation: This is a TKTN message.
This message indicates
that
the
device requested for dismount is now logically
disconnected from the system (that is, all files are deaccessed
and the VCB is deallocated).
xxx --
DPB error
Explanation: A bad Directive Parameter Block was created by MCR.
This error indicates that the system itself has faulted.
User Action: If the error
persists,
Performance Report (SPR) to DIGITAL.
xxx --
submit
a
Software
Driver already resident
Explanation: The specified device driver had already been loaded
or is permanently resident.
xxx --
Driver being loaded or unloaded
Explanation: The Executive was effecting another request to load
or unload the driver.
xxx --
Driver built with wrong Executive STB file
Explanation: The STB file for the driver was not compatible with
the current Executive.
xxx --
Driver cannot be unloaded
Explanation: The UNLOAD
command
attempted
to
remove
a
permanently resident device driver (that is, a driver built as
part of the Executive).
A-8
c
MCR AND TKTN MESSAGES
xxx --
(
Driver load/unload calls not supported
Explanation: The requested driver included the symbols $ddLOA or
$ddUNL in its source. These symbols are reserved for future use
by the LOAD and UNLOAD commands.
xxx --
Driver not loaded
Explanation:, The device driver specified in the UNLOAD command
was not resident in memory, or the INI or MOUNT command specified
a device for which a driver was not loaded.
xxx
-~
Duplicate block(s) found
Explanation: A block that had been specified as
defined as bad a second time.
xxx --
bad
was
being
Error logging still active
Explanation: A system cannot be saved while error logging is
active. Disable error logging and reenter the SAVE command line.
xxx --
Failed to attach device -
Explanation:
The specified device could not be attached.
XXX -- Failed to create directory
Explanation:
occurred.
xxx --
No space existed on the
volume
or
an
I/O
error
Failed to enter in MFD
Explanation: No space existed in the Master File Directory (MFD)
or on the volume, or an I/O error occurred on the volume.
xxx --
Failed to read bad block file
Explanation: The INI command was unable to rea'd the bad block
information from the last track of an RK06/07, RL01/02, or
RM02/03/05/80/RP07 disk.
xxx --
Feature not supported
Explanation: The command keyword specified a feature or device
that was not incorporated into the system at system generation,
or the command itself cannot be used.
xxx --
File has illegal STB format
Explanation:
or data.
xxx --
The driver's STB file contained illegal object code
File I/O error nnn.
Explanation: The ACS command detected an error when it tried to
allocate or open the checkpoint file. The code nnn. is an FCS
error code that defines the cause of the error.
See the
RSX-llM/M-PLUS I/O Operations Reference Manual.
A-9
MCR AND TKTN MESSAGES
xxx --
File not a valid driver task image
Explanation: The driver's task image was either overlaid or
a task header.
XXX
had
(
File not contiguous
Explanation: An attempt was made to boot a system or install a
task from a noncontiguous file.
System images and task images
must be contiguous.
XXX --File not contiguous
Explanation: Th~ file specified was not
must be contiguous.
xxx --
contiguous.
The
file
File not found
Explanation: The requested file was not in the directory on
specified volume.
xxx --
File not in use
Explanation: A checkpoint file was not
specified in the ACS command.
xxx --
the
in
use
on
the
device
File ,not properly closed
Explanation: An attempt was made to install a file that was not
properly closed (that is, locked). Since the file is locked, it
is probably corrupted.
Install a new copy of the file.
XXX -- File not task image
Explanation: Data in the label block was not correct, indicating
that the file was not a valid task image.
xxx --
Home block allocate write error
Explanation: A write error occurred
overwriting a bad home-block area.
while
the
system
was
reading
or
writing
the
XXX -- Home block I/O error
Explanation: An error was detected in
volume home block.
xxx --
Illegal device
Explanation: The device specified at task-build time by the
assign
(ASG)
option does not exist in the system. This is a
warning message only.
xxx --
c
Illegal device specified
Explanation:
The specified device was not a terminal.
A-lO
C
MeR AND TKTN MESSAGES
xxx --
(
Illegal device/volume
Explanation:
device.
xxx --
The specified device was not a valid task-residence
Illegal driver task APR usage
Explanation: A device driver must be built for APR 5 and must be
less
than 8K (for example, PAR=DRVPAR:120000:40000).
This
message applies to mapped systems only.
xxx --
Illegal first APR
Explanation: A privileged task, built to run using APR 4 or 5 as
its base, was too large. Using APR 4, the task was larger than
12K; using APR 5, the task was larger than 8K.
If the Executive has been built to support 20K of address space,
APR 5 is the only valid base APR for tasks mapping into the
Executive.
A privileged task that does not map into the
Executive must use APR 0 as its base.
(See the RSX-llM/M-PLUS
and Micro/RSX Task Builder Manual for a description of the IPR
keyword .)
-This message applies only to mapped systems.
xxx --
Illegal function
Explanation: A command was entered that MeR could not
or an inappropriate keyword was specified.
(
xxx --
Illegal keyword value
ExpLanation:
invalid.
A
User Action:
Enter a legal string or value.
xxx --
recognize
string
or
value
entered
for
a
keyword
was
Illegal priority
Explanation: The value of the priority in the command was out of
range (that is, not 1 through 250 decimal).
(
xxx --
Illegal Ule
Explanation:
xxx --
The command line specified an illegal Ule.
Illegal value for symbol in file
Explanation: The symbol symname is defined to an illegal value
in the file ddDRV.STB. This can occur for several reasons, some
general and some specific to individual symbols.
For example,
symbols cannot have odd values, most symbols cannot be defined as
zero, $ddTBL must exist and have a value less than $ddEND, and
mapped loadable drivers cannot reference $INTSV.
xxx --
Improper help file format
Explanation: The help file is not in proper format and cannot be
used.
Either edit the file or reenter it in the proper format.
xxx --
Index file bit map I/O error
Explanation:
bitmap.
An error was detected
A-ll
in
writing
the
index-file
MCR AND TKTN MESSAGES
xxx --
Index file header checksum error
Explanation: While rebooting a saved system, the system detected
a checksum error in the file header of the index file.
The error
causes the system to halt. The disk has probably been corrupted.
xxx --
(
Index file header read error
Explanation: While rebooting a saved system, the system detected
an error in the file header of the index file.
The error causes
the system to halt.
XXX -- Index file I/O error
Explanation:
header.
xxx --
An error was detected
the
index-file
to
read
the
next
command,
OPEN
Insufficient pool space
Explanation:
available.
xxx --
writing
Input I/O error
Explanation: In attempting
detected an error.
xxx --
in
The
required,
amount
of
pool
space
not
was
c
Invalid account
Explanation: The name or UIC specified in the command line is
not stored in the account file or the password specified does not
match the name or UIC given.
xxx --
Invalid address
Explanation: The address specified as an argument by the OPEN
command referenced a nonexistent memory location, an address
outside of the specified partition, or an address outside of the
task's virtual address space.
xxx --
Invalid driver data base at offset in file
Explanation: The driver had an invalid data base value at offset
xxxx relative to the symbol $ddDAT.
xxx --
Invalid keyword
Explanation: A keyword was specified in the
cannot be used with the command.
A-l2
command
line
that
(
MCR AND TKTN MESSAGES
xxx --
(,
Invalid load device
Explanation: The BOOT or INSTALL command detected a device
was invalid as a system- or task-residence device.
xxx --
that
Invalid speed
Explanation: The multiplexer line does not support the requested
speed, or the command line specified unequal receive and transmit
baud rates for a DZII or DZVII.
The DZII and DZVII do not
support split speeds.
xxx --
Invalid time parameter
Explanation:
xxx --
Invalid
A specified time field was incorrect.
utc
Explanation: A value of zero was detected for either
number or the member number.
the
group
lOT execution
Explanation: This is a TKTN message. The task executed an lOT
instruction and no SST routine was specified to process the trap.
xxx --
I/O error sizing device -
Explanation:
RFll disk.
The system encountered an I/O error while sizing an
c
xxx --
Label block I/O error
Explanation: In saving the system image, the SAVE command writes
the transfer address in the label block of the system image file.
An error occurred during this write attempt. The disk could be
corrupted.
l'
xxx --
Label block read error
Explanation: The BOOT command could not read the label block
the system image.
A-l3
of
MeR AND TKTN MESSAGES
xxx --
Length mismatch common block
Explanation: The length parameter for the common block, as
described in the label block for the task image, did not match
the corresponding length parameter defined in the system.
A
task's label block data must match system data for that task
before it can be installed.
xxx --
Line not DZII
Explanation: The command attempted to set to remote a line
was not attached to a DZII multiplexer.
xxx --
that
Listing device not available
Explanation: The device unit on which MeR was attempting
display information was attached and unavailable for use.
xxx --
(
to
Load device not LB:, task removed -
Explanation: The system removed the specified task while saving
a system because the task had not been installed from LB:.
Load failure. Read error
Explanation: This is a TKTN message.
loaded because of a hardware error.
xxx --
The
task
could
not
be
Loadable driver support not in system
Explanation: The system generation option to support loadable
device drivers was not chosen or necessary routines are not in
the Executive.
xxx --
Logical device not in system
Explanation: The specified logical device name was
in the logical device tables.
xxx --
not
defined
Logins are disabled
Explanation: The system was in the process of shutting down or
the command SET /NOLOGON has been issued. A user cannot log in
at these times.
xxx --
LUN out of range
Explanation: An attempt was made to reassign a LUN that was
greater than the maximum number of LUNs allocated to the task
when it was built.
xxx --
Magtape label must be specified
Explanation: An INI command attempted to initialize
tape without specifying the required volume label.
a
magnetic
Explanation: While
positioning
a
magnetic
tape
initializing it, the system encountered an I/O error.
before
XXX -- Magtape device error - '
xxx --
Magtape write error -
Explanation: While writing to
the
magnetic
tape
initialization, the system encountered an I/O error.
A-14
during
c
MCR AND TKTN MESSAGES
xxx --
(
MCR is not installed
Explanation:
system disk.
***
When a system is booted, SAVE uses MCR to mount the
Use VMR to install the MCR ••• task.
Memory parity error in partition ' -- Not ready
Explanation:
not ready.
xxx --
This is a TKTN message.
The specified
device
was
Null file header I/O error
Explanation: An error was detected in writing null file
to the index file.
headers
Odd address or other trap four
Explanation: This is a TKTN message. The task executed a word
instruction with an odd address or referenced a nonexistent
memory location in an unmapped system, and no SST routine was
specified to process the trap.
xxx --
Old device attached
Explanation:
xxx --
Old device mounted
Explanation:
(
xxx --
An attempt was made to redirect an attached device.
An attempt was made to redirect a mounted device.
Old device not known to system
Explanation: An attempt was made to redirect an unknown
(the device does not exist in the device tables).
xxx --
Open filets) on
Explanation: There are open files on
Queue Manager is stopped.
xxx --
(
Ensure
that
the
is
at
user
user
currently logged in
on
the
a time can be logged in on a
Output error
Explanation:
xxx --
ddnn:.
Other user logged on
Explanation: Another
terminal.
Only one
terminal.
xxx --
device
An MCR terminal-write operation failed.
Overlap seeks not supported
Explanation: The command attempted to enable overlapped-seek
support for other than a DM or an RH device controller.
xxx --
Parameter conflict with already mounted volume
Explanation: The volume was already mounted foreign and Files-ll
access was requested or the volume was mounted Files-ll and
foreign access was requested.
(
A-17
MeR AND TKTN MESSAGES
Parity error
Explanation: This is aTKTN message. A parity eiror occurred
while the task was executing. The task was fixed in memory so
that the memory cannot be reused for another task.
XXX -- Partition already exists
Explanation: An attempt was made to define a
name already in use.
xxx --
partition
with
a
Partition busy
Explanation: The partition in which the task was to be fixed was
occupied, so the task could not be fixed.
xxx --
Partition not common
Explanation: A partition specified for a common area or
was not defined as a common partition.
xxx --
library
Partition -- Read failure. Check hardware status
Explanation: This is a TKTN message.
detected a hardware error.
xxx --
The
card
reader
driver
Region/partition is a common
Explanation: An attempt was made to load a device driver into a
A device driver cannot be loaded
common partition or region.
into a common partition or region.
A-19
MCR AND TKTN MESSAGES
(
***
-- Replacement control task not installed
Explanation;
This is a TKTN message.
While bringing
the
specified device on line or detecting a bad block on the device,
the driver could not call the replacement control task
(RCT)
because it is not installed.
Install RCT.
Required bus runs are offline or not present
Explanation:
{task, or a common that it is mapped to, was
installed with an affinity for a CPU or a bus run that is off
line.
Reserved inst execution
Explanation: This is a TKTN message.
The task executed an
illegal instruction and no SST routine was specified to process
the trap.
***
(
-- Select error
Explanation: This is a TKTN message. The selected device
not ready or more than one drive had the same unit number.
was
(
xxx --
Space used
Explanation: An attempt was made to create a partition
subpartition in a storage area already occupied.
xxx --
a
Specified partition for common block
Explanation:
block.
xxx --
or
An attempt was made to install a task in
a
common
Specified partition too small
Explanation: The task being installed was
partition into which it was being installed.
A-20
larger
than
the
(
MeR AND TKTN MESSAGES
SST abort. Bad stack
Explanation: This is a TKTN message. An SST cannot be effected
because the SST parameters cannot be pushed onto the task's
stack, or a stack overflow was detected in an unmapped system, as
indicated by a nonzero value in the header guard word.
xxx --
Storage bitmap file I/O error
Explanation: An error was detected in writing
allocation file header.
xxx --
the
storage
Symbol is doubly defined by file
Explanation: The symbol symname is defined
specified file. Duplicate symbols are illegal.
xxx --
out
twice
in
the
Symbol is undefined in file
Explanation: The symbol symname was found in the specified file,
but the symbol was not defined.
xxx --
(
Syntax error
Explanation: This message generally indicates that the
information was entered incorrectly.
required
User Action: You can usually correct this condition by
the arguments according to the command specifications.
retyping
xxx --
System may not boot correctly
Explanation: The file [system-uic]SAV.TSK was not found on the
boot device.
If SAVE must be checkpointed to redirect and mount
the booted device, the system disk will be overwritten, causing
unpredictable results.
c
xxx --
Task active
Explanation:
active.
xxx --
The task used as the argument of
the
command
was
Task active in another system, task removed -
Explanation:
The task is installed in another system as well as
in the booted system.
Since taskname is active and mapped to
dynamic regions in the other system, it cannot be run in the
booted system.
A-21
MeR AND TKTN MESSAGES
XXX -- Task already fixed
Explanation: The task used as the argument of the FIX command is
already fixed in memory.
c
XXX -- Task and partition bases mismatch
Explanation: The base of the partition did not match the base of
the task being installed. This message applies only to unmapped
systems.
XXX -- Task being aborted
Explanation: A request for the execution of a task was made, but
the task was being aborted either because of an unrecoverable
error or an abort command or directive issued by a user.
XXX -- Task being fixed
Explanation: An attempt was made either to fix or to
priority of a task that was already being fixed.
alter
the
XXX -- Task checkpointable
Explanation: An attempt was made to fix a checkpointable task in
memory. A checkpointable task cannot be fixed in memory.
Task exit with outstanding I/O
c
Explanation: This is a TKTN message. The task exited with one
or more outstanding I/O requests.
Tasks should terminate all I/O
operations before exiting. The system does, however, process all
outstanding I/O.
XXX -- Task file deleted, task removed -
Explanation: While
rebooting
a
saved
system,
a
file
identification that appears in the Task Control Block (TCB) could
not be found in the index file on the boot device.
This
indicates that the file has been deleted.
XXX -- Task file header error, task removed -
Explanation: When SAVE read the task header to restore the LBN
of the task file, the checksum was bad or there was a file number
mismatch. Therefore, the task was removed.
XXX -- Task file header read error, task removed -
Explanation: The system removed the specified task because
encountered a failure while reading the task's file header.
it
XXX -- Task header read error
Explanation: The system detected an I/O error while reading in a
task header to write the file identification into the TCB.
This
error causes the system to halt.
A-22
c
MCR AND TKTN MESSAGES
xxx --
Task image already installed
Explanation: The requested task image, which was checkpointable,
had already been installed.
On systems that do not support the
dynamic allocation of checkpoint space, checkpointable tasks that
do not have checkpoint space allocated can be installed only
once; other tasks can be installed more than once
(under
different names).
xxx --
Task image I/O error
Explanation:
INSTALL could not read the task image file or
could not rewrite the task image header.
(The device
write-locked.)
xxx --
it
is
Task image I/O error in file
Explanation: The device is probably write-locked. MCR could not
read the task image file or could not rewrite the task image
header.
xxx --
Task image virtual address overlaps common block
Explanation:
The virtual addresses reserved for the task image
overlap those reserved for the common block specified in the
message. A corruption of the task image file probably caused the
overlap.
Task installed in more than one system
Explanation: This is a TKTN message. The task image file has
been installed in more than one system.
The task's header
contains pointers for the last system in which the task was
installed.
The pointers are not valid for the current system.
Remove the task and reinstall it in the current system.
(
xxx ------
Task installed in partition
E-x-pl-ana-t-i-(m-:-AIl-a-t-tempt-w~s-made-to-----€Liminate_a_par_t_Lt_Lon
or
subpartition that contains installed tasks.
(
xxx --
Task marked for abort
Explanation: A previous request has already been made to abort
the specified task, but the abort has not yet occurred.
The task
marked for abort is probably not currently resident in memory or
it has outstanding I/O.
xxx --
Task name already in use
Explanation: An attempt was made to install a task with the same
name as one already in the system.
xxx --
Task not active
Explanation:
The specified task is not currently active.
A-23
MeR AND TKTN MESSAGES
xxx --
Task not fixed
Explanation: An attempt was made to unfix a task that was not
fixed or to open a virtual location of a task that was not fixed.
xxx --
(!
Task not in system
Explanation: The specified task has not been installed or the
task was initiated by the install-run-remove option of the RUN
command.
xxx --
Task not suspended
Explanation: The task specified in the RESUME command
not suspended.
xxx --
was
waiting
for
Task has outstanding I/O
Explanation: A system cannot be saved if a task is
I/O to complete.
xxx --
line
Task is active and checkpointed
Explanation: You cannot save a system if it contains an active
and checkpointed task.
This restriction prevents a possible
system crash because, if the task was installed in another system
image file,
the task image could be corrupted when the task was
run in the second system.
xxx --
Task is connected to an interrupt vector
Explanation: Disconnect the task from the interrupt
abort it, and reenter the SAVE command line.
xxx --
vector
or
Task not installed from an LB:
Explanation: All tasks must be installed from the system device
(LB:).
Use the TAS command to determine which tasks are not
installed. Reenter the SAVE command line after removing the
tasks or installing them from LB:.
T-bit trap or BPT execution
Explanation: This is a TKTN message. The task has either set
the T-bit in the Processor Status Word or executed a Breakpoint
Trap instruction, and no SST routine was specified to process the
trap.
xxx --
Terminal allocated to other user
to
Explanation: The issuing terminal is already allocated
A user cannot log in on a terminal allocated to
another user.
someone else.
xxx --
TI redirect error
Explanation: An attempt was made to redirect the
TI:. This device cannot be redirected.
A-24
pseudo
device
(\
MeR AND TKTN MESSAGES
(
xxx --
Too many common block requests
Explanation:
xxx --
Too many LUNs
Explanation:
xxx --
A task is limited to seven common block requests.
A task attempted to assign more than 255(10) LUNs.
Too many subpartitions
Explanation: An attempt was made to assign more than seven
subpartitions.
A partition is limited to a maximum of seven
subpartitions.
(
TRAP execution
Explanation: This is a TKTN message. The task executed a TRAP
instruction and no SST routine was specified to process the trap.
xxx --
Undefined common block
Explanation: A task referenced a common block that had not been
defined in the system. Usually, this message indicates that the
task was built for another system.
(
xxx --
Undefined density selection
Explanation:
value.
xxx --
The
command
line
specified
an
illegal
density
unit does not support 800 bpi
Explanation: The command line specified 800 bpi for a drive that
does not support 800 bpi.
XXX -- Unit does not support 1600 bpi
Explanation: The command line specified 1600
that does not support 1600 bpi.
xxx --
xxx --
for
a
drive
bpi
for
a
drive
Unit does not support 6250 bpi
Explanation: The command line specified 6250
that does not support 6250 bpi.
(
bpi
Unit does not support density switch
Explanation: The command line specified multiple densities for a
device that does have multiple-density capability.
A-25
MCR AND TKTN MESSAGES
xxx --
Unit does not support HIGH/LOW density selection
Explanation: The command line specified HIGH or LOW density
a device for which the HIGH and LOW options are undefined.
XXX
for
(
Unit is not at LOW density
Explanation: The command line specified that a floppy disk in an
RX02 drive be initialized at LOW density, but the floppy was
formatted at HIGH density.
XXX -- Unit is not at HIGH density
Explanation: The command line specified that a floppy disk in an
RX02 drive be initialized at HIGH density, but the floppy was
formatted at LOW density.
xxx --
Unknown main partition
Explanation: An attempt was made to define a subpartition
nonexistent main partition.
xxx --
a
Unknown help qualifier
Explanation: The help file does not contain the last
displayed in the command line below the error message.
***
in
qualifier
-- Unrecoverable hardware device error
Explanation: This is a TKTN message.
unrecoverable hardware error.
xxx --
Error Logging recorded
an
(
User logged on terminal
Explanation: The command attempted to allocate a terminal that
has been logged in by another user. Logged-in terminals cannot
be allocated.
(
xxx --
Volume mounted Files-II
Explanation: An
Files-II volume.
xxx --
attempt was made to initialize a
mounted
Mounted Files-II volumes cannot be initialized.
Volume name too long -
(volume name)
Explanation~
The command line specified a volume label that
exceeded SIX characters for magnetic tape devices or 12(10)
characters for disk or DECtape devices.
A-26
MCR AND TKTN MESSAGES
xxx --
(
Volume not mounted
Explanation: An attempt was made to dismount or to create a UFO
on a volume that is not mounted. A volume on which a UFD is to
be created must be mounted.
xxx --
Volume not mounted by TI:
Explanation: The command line specified a dismount operation for
a volume that was not mounted from the issuing terminal or the
command line specified the wrong device name for a magnetic tape
set.
xxx --
Volume(s) still mounted on
Explanation:
A system with mounted volumes cannot be saved.
User Action: To correct the problem, dismount the volumes and
retry the command.
The DEVICES command can be used to display
the mounted volumes.
~)
xxx --
Volume structure not supported
Explanation: Your operating system does not support the Files-ll
structure level of the volume being mounted.
In response to a SAVE command, while rebooting a saved system,
the system determined from the disk's home block that the disk's
structure is not supported by the current version of your
operating system.
This error causes the system to halt.
(
xxx --
Block 0 is bad
Explanation: Block 0 of the specified volume, the boot block,
was bad. A bootable image cannot be placed on this volume.
This
is a warning message only.
xxx --
l
Warning
Warning - Loadable driver larger than 4K
Explanation: Loadable drivers can be up to 8K words in length.
The driver must explicitly map to any locations above 4K words.
A-27
MCR AND TKTN MESSAGES
xxx --
(Warning) Nonexistent LUN assignment for task
Explanation: The physical device to which SAVE was attempting to
reassign a LUN does not exist in the booted system. This
condition is resolved if the task performs a run-time assignment
to the LUN; otherwise, the task will encounter an error condition
when it attempts to use the LUN.
xxx --
(
Warning - privileged task overmaps the I/O page
Explanation: A privileged task that is mapped into the Executive
is usually also mapped into the I/O page to access the registers
for the KTll and other devices. Many tasks do not require this
access and can use the additional 4K words of virtual address
space for the task image. This message warns that a task that
may require access to the I/O page might have grown too large.
XXX -- Write attributes failure
Explanation: An error was encountered while the attributes
either the MFD or the newly created UFD were being written.
***
of
-- Write back caching data lost. Unit write locked
Explanation: This is a TKTN message. When the specified device
was brought on line, RCT detected that its cache contained
corrupted data, so the device was write-locked for protection.
After
correcting
the
cache
data,
mount the device as
write-enabled (MOUNT /WRITE) •
Note that every time the device is brought
display this message.
xxx --
on
line,
TKTN
will
c'
Write check not supported
Explanation: An attempt was made to support write checking on
device that does not support it.
xxx --
a
Wrong volume label
Explanation: The volume's current label and the label
in the command line did not match.
A-28
specified
c
INDEX
(
c
c
/ABAUD keyword
SET command, 3-202
ABO command
See ABORT command
ABORT command, 1-6, 3-3
error messages, 3-4
examples, 3-4
format, 3-3
keywords
/PMD, 3-4
/TERM, 3-4
parameters, 3-4
/ACCESS keyword
INITVOLUME command, 3-100
Access types, 2-3, 3-94, 3-148,
3-149, 3-213
Account
and UFO, 2-2
and UIC, 2-2
creating, 2-24
protection, 3-241
Account File Maintenance Program
See ACNT
ACD command
See ANCILLARY CONTROL DRIVER
command
ACNT, 2-24, 3-240, 3-241
ACP
See Ancillary Control Processor
/ACP keyword
MOUNT command, 3-145
ACS command
See ALLOCATE CHECKPOINT SPACE
command
ACT command
See ACTIVE command
ACTIVE command, 1-7, 3-14
examples, 3-14
format, 3-14
keywords
/ALL, 3-14
/TERM, 3-14
ACTIVE TASK LIST command, 1-7,
3-31
example, 3-33
format, 3-33
/AFF keyword
INSTALL command, 3-117
OPENREGISTER command, 3-165
ALL command
See ALLOCATE command
/ALL keyword
ACTIVE command, 3-14
ASSIGN command, 3-29
DEFINE LOGICALS command, 3-68
/ALLOC keyword
USER FILE DIRECTORY command,
3-280
ALLOCATE CHECKPOINT SPACE command,
1-6, 3-11
error messages, 3-12
examples, 3-12
format, 3-11
keyword
/BLKS, 3-11
ALLOCATE command, 1-8, 3-16
allocating private device, 2-13
error messages, 3-17
examples, 3-17
format, 3-16
keywords
/TERM, 3-16
/TYPE, 3-16
parameters, 3-16
ALT command
See ALTER command
ALTER command, 1-7, 3-19
examples, 3-20
format, 3-19
keywords
/PRI, 3-19
/RPRI, 3-19
/TERM, 3-19
parameters, 3-19
American National Standards
Institute
See ANSI
ANCILLARY CONTROL DRIVER command,
1-6, 3-8
examples, 3-9
format, 3-8
functions, 3-8
Ancillary Control Processor, 3-70,
3-141
Files-II, 3-94, 3-141, 3-146,
3-150, 3-208
for foreign files, 3-151
Magnetic Tape, 3-141
ANSI
file name, 2-5
magnetic tape, 2-5
/ANSI keyword
SET command, 3-203
ASCII
character set, 3-153
command option, 2-6
task name, 2-6
ASN command
See ASSIGN command
ASSIGN command, 1-6, 3-20
and logical devices, 2-12
and pseudo devices, 2-10
error messages, 3-30
examples, 3-26, 3-28, 3-29
formats, 3-25, 3-27, 3-29
keywords
/ALL, 3-29
/FINAL, 3-26
Index-l
INDEX
ASSIGN command
keywords (Cont.)
/GBL, 3-26, 3-28, 3-29
/GR, 3-26, 3-28, 3-29
/LOGIN, 3-26, 3-28
/SYSTEM, 3-26, 3-28
/TERM, 3-28, 3-29
Assignments
See also Logical assignment
logical device, 2-12, 3-20
logical name, 3-21, 3-63
global, 3-21, 3-64
group, 3-21, 3-64
local, 3-21, 3-64
login, 3-21, 3-64
task, 2-12
AST
See Asynchronous system trap
Asterisk (*) wildcard, 2-7
Asynchronous system trap, 1-3,
2-16
service routine, 3-3
ATL command, 3-31
See ACTIVE TASK LIST command
Autobaud detection, 3-202
/AVO keyword
SET command, 3-204
Backup and Restore utility
See BRU
Bad block
descriptor file, 3-102
initializing, 3-~00, 3-102
processing, 3-100
/BAD keyword
INITVOLUME command, 3-100
options, 3-100
AUTO, 3-101
MAN, 3-101
NOAUTO, 3-101
OVR, 3-101
Baud rate
automatic detection of, 3-202
receive, 3'-254
remote terminal
setting, 3-247
setting, 3-254
transmit, 3-254
valid, 3-254
Bit density, 3-147
diskette, 3-102
magnetic tape, 3-102
ar.K command
See BLOCK command
/BLKMOD keyword
SET command, 3-205
/BLKS keyword
ALLOCATE CHECKPOINT SPACE
command, 3-11
BLOCK command, 1-7, 3-34
examples, 3-34
format, 3-34
keyword
/TERM, 3-34
BLOCK command (Cont.)
parameters, 3-34
BOO command
See BOOT command
BOOT command, 1-6, 2-8, 3-35
error messages, 3-37
example, 3-37
format, 3-35
parameters, 3-35
Bootstrapping
system, 3-35
mapped, 3-36
unmapped, 3-36
unsaved, 3-36
BPI
See Bit density
BREAKPOINT TO EXECUTIVE DEBUGGING
TOOL command, 1-8, 3-38
error message, 3-38
example, 3-38
format, 3-38
BRK command
See BREAKPOINT TO EXECUTIVE
DEBUGGING TOOL command
BRO command
See BROADCAST command
/BRO keyword
SET command, 3-205
BROADCAST command, 1-8, 3-39
and indirect command file, 3-39
error messages, 3-42
examples, 3-41
formats, 3-39
message formats, 3-41
option, 3-40
BRU, 3-116, 3-188
/BS keyword
MOUNT command, 3-146
/BUF keyword
SET command, 3-206
BYE command, 1-8, 3-43
error message, 3-44
example, 3-44
format, 3-44
keywords, 3-43
Cache data
See Data caching
/CACHE keyword
MOUNT command, 3-146
SET command, 3-207
CAN command
See CANCEL command
CANCEL command, 1-7, 3-45, 3-180
example, 3-46
format, 3-45
parameters, 3-45
CBD
See Common Block Directory
CBD command
See COMMON BLOCK DIRECTORY
command
ICC keyword
MOUNT command, 3-147
Index-2
(
c
(
INDEX
(
(
Character
pass-through, 3-241, 3-250
translation, 3-8 to 3-10, 3-152
wildcard, 2-7
Checkpoint
file, 3-11
primary, 3-12
size, 3-12
space
allocating, 3-11, 3-117,
3-119, 3-182
task, 2-20, 3-11, 3-31, 3-182
/CKP keyword
INSTALL command, 3-117
RUN command, 3-182
CL:, 2-10, 2-11
/CLE keyword SWITCH REGISTER,
3-274
CLI
commands, 1-8
data structures, 3-48
DCL, 3-56
default, 3-79
disabling, 3-49
eliminating, 3-48
login, 3-79
prompt string, 3-49
task, 3-49
CLI command
See COMMAND LINE INTERPRETER
command
/CLI keyword
HELP command, 3-87
INSTALL command, 3-117
SET command, 3-209
Clock
interrupt, 3-180
queue, 2-11
displaying, 3-55
CLOCK QUEUE command, 1-7, 3-55
example, 3-55
format, 3-55
CLQ command
See CLOCK QUEUE command
/CMD keyword
RUN command, 3-182
CO:, 2-11, 3-188
Command line, 1-1 to 1-2
comments, 1-4
compressing, 1-2
continuing, 1-2, 2-4
format, 3-2
length, 2-4
parameters, 1-1, 1-2
parsing, 1-2
processing, 1-5
quotation marks, 1-2
special characters, 1-2
terminating, 1-2
Command line interpreter
See CLI
COMMAND LINE INTERPRETER command,
1-8, 3-48
error messages, 3-53 to 3-54
COMMAND LINE INTERPRETER command
(Cont. )
examples, 3-52
formats, 3-48
keywords
/DISABLE, 3-48
/ELIM, 3-48
/ENABLE, 3-49
/INIT, 3-49
/MESSAGE, 3-52
/UNOVR, 3-52
parameters, 3-48
subkeywords
/CPR, 3-50
/CTRLC, 3-49
/DISABLE, 3-50
/DPR, 3-50
/LGO, 3-50
/MESSAGE, 3-51
/NULL, 3-51
/PRIV, 3-51
/PROMPT, 3-51
/QUIET, 3-51
/RESTRICT, 3-51
/SNGL, 3-51
/TASK, 3-52
Commands
command line interpreter, 1-8
description
format, 3-1
name, 3-2
informational, 1-7
initialization, 1-6
multiuser protection, 1-8
privilege status, 3-2
privileged, 2-19
summary of MCR, 1-5 to 1-8
system maintenance, 1-8
task control, 1-7
Common
checkpointing, 3-122
device, 3-125, 3-238
installing, 3-122
memory image, 3-125
name, 3-170
partition, 3-169
read-only, 3-169
read/write, 3-169
read-only
installing, 3-122
read/write
checkpointing, 3-122
region, 3-75
accessing, 3-120
displaying, 3-46
installed, 3-119
protecting, 3-119
removing, 3-175
status, 3-46
status bits, 3-46
synchronizing, 3-121
tasks, 3-47
unfixing, 3-284
reinstalling, 3-125
Index-3
INDEX
Common Block Directory, 3-116
displaying, 3-46
removing regions, 3-175
COMMON BLOCK DIRECTORY command,
1-7, 3-46
examples, 3-47
format, 3-46
keyword
/TASKS, 3-46
parameters, 3-46
Continuation line, 1-2
Control
character, 2-15 to 2-18
key, 2-15
Control Status Register
See CSR
Controller Table Block, 3-132
/CPU keyword
OPENREGISTER command, 3-165
/CRASHDEV keyword
SET command, 3-209
/CRE keyword
FLA command, 3-77
Create access
volume, 3-96, 3-106, 3-151
/CRT keyword
SET command, 3-210
CSR
address
boot device, 3-190
saving, 3-190
/CSR keyword
SAVE command, 3-190
CTB
See Controller Table Block
/CTB keyword
LOAD command, 3-132
CTRL/C, 1-3, 2-17
invoking CLI prompt, 3-49
CTRL/I, 2-17
CTRL/K, 2-17
CTRL/L, 2-17
CTRL/O, 2-17
CTRL/Q, 2-18
CTRL/R, 2-18
CTRL/S, 2-18
CTRL/U, 2-18
CTRL/X, 2-18
CTRL/Z, 2-18
Data
transfer
checking, 3-265
Data caching, 3-146 to 3-147,
3-207 to 3-209
options, 3-146, 3-207
region, 3-146, 3-207
specifying partition, 3-146,
3-207
DCL, 3-56
DCL command
See DIGITAL COMMAND LANGUAGE
command
/DCL keyword
HELP command, 3-87
SET command, 3-211
DEA command
See DEALLOCATE command
DEALLOCATE command, 1-8, 3-57
example, 3-57
format, 3-57
parameters, 3-57
DEB command
See DEBUG command
DEBUG command, 1-7, 3-58
error messages, 3-59
examples, 3-58
format, 3-58
parameter, 3-58
Debugging
aid, 3-58
task, 3-58
/DEC keyword
SET command, 3-211
/DEF keyword
SET command, 3-212
DEFINE LOGICALS 'command, 1-6,
3-63
error messages, 3-69
examples, 3-66, 3-67, 3-68
format, 3-67, 3-68
formats, 3-65
keywords
/ALL, 3-68
/FINAL, 3-66
/GBL, 3-66, 3-67, 3-68
/GR, 3-66, 3-67, 3-68
/SYSTEM, 3-67, 3-68
/TERM, 3-67, 3-68
Delete access, 2-3
common region, 3-120
file, 3-149, 3-213
UFD, 3-281
volume, 3-94, 3-96, 3-106,
3-151
DELETE key, 2-16
/DENS keyword
HOME command, 3-93
INITVOLUMEcommand, 3-102
MOUNT command, 3-147
Density
See Bit density
DEV command
See DEVICES command
/DEV keyword
DISMOUNT command, 3-71
Device, 2-10 to 2-14
accessing, 3-141
allocating, 2-13, 3-16
attached, 3-173
bootab1e, 3-35
characteristics
setting, 3-197
common, 3-238
controller
overlapped-seek support,
3-236
Index-4
c
C\
INDEX
c
c
Device (Cont.)
deallocating, 2-13, 3-16, 3-57
. default, 3-212
displaying, 3-60
driver
building, 3-134
loadable, 3-166
loading, 3-132
mapping, 3-132
nonresident, 3-132
vectoring, 3-132, 3-134
fairness-count, 3-235
file-structured, 3-141
Files-ll, 2-1
I/O requests
redirecting, 3-173
identifier, 2-10
list, 3-144
mounted, 3-62
name, 2-4
assigning logical, 2-12
displaying, 3-60
non-file-structured, 3-141
nonshared, 3-142
null, 2-11
off-line, 3-62
on-line, 3-62
peripheral, 2-10
private, 2-13, 3-246
deallocating, 3-16, 3-57
displaying, 3-246
privileged status, 2-13
pseudo, 2-10 to 2-11, 3-173
public, 2-13, 3-62, 3-142
dismounting, 2-13
displaying, 3-245, 3-246
setting, 3-245
saving system image, 3-187
sequential, 3-141
shadow, 3':' 7 0
shared, 3-142
spooled, 3-173
unowned, 2-13
user's default, 2-11
DEVICES command, 1-7, 3-60
examples, 3-60
formats, 3-60
keyword
/LOG, 3-60
parameters, 3-60
DFL command
See DEFINE LOGICALS command
DIGITAL COMMAND LANGUAGE command,
1-8, 3-56
examples, 3-56
format, 3-56
DIGITAL Multinational Character
Set, 3-8
Directory
See also UFD
count
legal values, 3-95
maximum, 3-104
specifying, 3-104, 3-150
Directory (Cont.)
creating files, 2-2
data caching, 3-146, 3-207
default, 3-212
deleting, 2-2
format, 2-4
library, 3-182
login, 3-79
named, 2-4
nonamed, 2-4
numbered, 2-4
group number, 2-4
member number, 2-4
specification, 2-4
syntax, 2-4
system, 3-182
terminal
default, 2-7
/DIS keyword
SWITCH REGISTER command, 3-274
/DISABLE keyword
COMMAND LINE INTERPRETER
command, 3-48
/DISABLE subkeyword, 3-50
Disk
characteristics
displaying, 3-60
dismounting, 3-70
home block, 3-93
initializing, 3-99
spinning down, 3-71
DISMOUNT command, 1-6, 3-70
error messages, 3-72
examples, 3-72
formats, 3-70
keywords
/DEV, 2-13, 3-71
/LOCK, 3-71
/TERM; 3-71
/USER, 3-71
parameters, 3-70
shadow device, 3-70
DMO command
See DISMOUNT command
Dollar sign ($)
in file specification, 2-7
specifying directory, 3-182
/DPRO keyword
SET command, 3-213
/DRV keyword
OPENREGISTER command, 3-166
Dynamic storage region
See Pool
/EBC keyword
SET command, 3-215
EBCDIC
character set, 3-153
/ECHO keyword
SET command, 3-216
/EDIT keyword
SET command, 3-217
/ELIM keyword
CLI command, 3-48
Index-5
INDEX
/ELIM keyword (Cont.)
FLA command, 3-77
/ENABLE keyword, 3-49
Error
log file, 3-273
messages
See individual commands,
Appendix A
Error log report generator, 3-273
ESC key, 2-15
/ESCSEQ keyword
SET command, 3-217
/EST keyword
RUN command, 3-178, 3-182
Event flag, 3-58
creating, 3-77
eliminating, 3-77
group global, 3-77
local, 3-77
UIC, 3-77
Executive
directive, 3-140
aborting tasks, 3-5
fast-mapping, 3-118
loadable device driver, 3-132
partition
extended, 3-133
priority range, 3-257
round-robin scheduling, 3-248
swapping interval, 3-256
tables
logical device, 2-13
physical device, 2-13
task
aborting, 3-3
active, 2-23
allocating space, 2-20
checkpointing, 2-20
dormant, 2-23
header, 3-122
loading, 3-116
priority, 2-21
running, 1-5, 2-23, 3-116
Executive Debugging Tool, 3-36
invoking, 3-38
/EXP keyword
LOAD command, 3-133
/EXT keyword
HOME command, 3-94
INITVOLUME command, 3-102
Extend access, 2-3
common region, 3-120
file, 3-149, 3-213
UFD, 3-281
volume, 3-94
Extent
data caching, 3-146, 3-208
FCB '
See File Control Block
/FDX keyword
SET command, 3-218
/FIL keyword
HELP command, 3-87
File
accessing, 2-3, 2-6, 3-122
and directory, 2-2
content, 2-5
count
calculating maximum, 3-105
deleting with wildcard, 2-7
extending, 3-102
header
allocating, 3-103
calculating preallocated,
3-104
contents, 2-2
initializinq, 3-103
maximum per volume, 3-103
location, 2-3
maximum per volume
calculating, 3-104
name
specifying, 2-4
ownership, 2-2, 2-3
protection, 2-3, 2-6, 3-122,
3-148, 3-152, 3-214, 3-241
default, 3-103
specifying, 3-102
system image, 3-187
type, 2-5, 2-8
conventional, 2-8
default, 2-8
version number, 2-.5
window
mapping, 3-155
File Control Block, 3-104, 3-156
File Set Identifier, 3-143, 3-144,
3-150, 3-151, 3-154
File specification, 2-4
default, 3-35
defaults, 2-7
examples, 2-9
Files-ll
assigning logical name, 3-21
format, 2-4
input, 2-4
UIC, 2-6
File Transfer Utility Program
See FLX
Files-II, 2-1
file name, 2-5
volume
dismounting, 3-70
home block, 3-93
initializing, 3-99
label, 3-70
mounting, 3-142
protecting, 3-148, 3-151
types, 2-1
/FINAL keyword
ASSIGN command, 3-26
DEFINE LOGICALS command, 3-66
FIX command
See FIX-IN-MEMORY command
FIX-IN-MEMORY command, 1-7, 3-75
error messages, 3-76
examples, 3-76
Index-6
c
c
(
INDEX
c-
(
(
(
FIX-IN-MEMORY command (Cont.)
format, 3-75
keywords
/REG, 3-75
/RON, 3-75
FLA command
See GROUP GLOBAL EVENT FLAGS
command
Flag
See also Event flag
group global event, 3-77
FLX utility, 2-2
/FMAP keyword
INSTALL command, 3-118
/FOR keyword
MOUNT command, 3-148
Foreign volume
See Volume
/FORMFEED keyword
SET command, 3-219
/FPRO keyword
HOME command, 3-94
INITVOLUME command, 3-102
MOUNT command, 3-148
/GBL keyword
ASSIGN command, 3-26, 3-28,
3-29
DEFINE LOGICALS command, 3-66,
3-67, 3-68
Global logical assignment, 3-20
/GR keyword
ASSIGN command, 3-26, 3-28,
3-29
DEFINE LOGICALS command, 3-66,
3-67, 3-68
/GRO keyword
HELP command, 3-87
GROUP GLOBAL EVENT FLAGS command,
1-6, 3-77
error messages, 3-78
examples, 3-77
format, 3-77
keywords
/CRE, 3-77
/ELIM, 3-77
Group logical assignment, 3-20
/HDR3 keyword
MOUNT command, 3-149
HEL command
See HELLO command
HELLO command, 1-8, 3-79
error messages, 3-84
examples, 3-83
formats, 3-81
HELP command, 1-8, 3-87
error messages, 3-91
examples, 3-90
formats, 3-87, 3-88
keywords
/CLI, 3-87
/DCL, 3-87
/FIL, 3-87
HELP command
keywords (Cont.)
/GRO, 3-87
/LOC, 3-87
/MCR, 3-88
lOUT, 3-88
qualifiers, 3-87, 3-88
HELP file, 3-87 to 3-93
format, 3-88
qualifiers, 3-88
/HFILL keyword
SET command, 3-220
/HHT keyword
SET command, 3-221
/HIGH keyword
LOAD command, 3-133
/HOLD keyword
BYE command, 3-43
SET command, 3-222
HOM command
See HOME command
Home block
access types, 3-94
changing, 3-93
initializing, 3-93
task
installing, 3-93
HOME command, 1-6, 3-93
error messages, 3-97
example, 3-97
format, 3-93
keywords
/DENS, 3-93
/EXT, 3-94
/FPRO, 3-94
/LRU, 3-94
/MXF, 3-95
/NAME, 3-95
/OVR, 3-95
/OWNER, 3-95
/POS, 3-95
/PRO, 3-96
/UIC, 3-96
/VI, 3-96
/WIN, 3-97
/HOST keyword
SET command, 3-223
/HSYNC keyword
SET command, 3-223
I/O page
accessing, 3-238
overmapping, 3-183
specifying, 3-238
subpartition, 3-267
/INC keyword
INSTALL command, 3-118
RUN command, 3-183
Index file, 3-103
header
allocating, 3-103
/INDX keyword
INITVOLUME command, 3-103
Index-7
INDEX
/INF keyword
INITVOLUME command, 3-103
Informational commands, 1-7
INI command
See INITVOLUME command
/INIT keyword, 3-49
subkeywords, 3-49 to 3-52
Initialization commands, 1-6
INITVOLUME command, 1-6, 3-99
default file protection, 2-3
error messages, 3-108 to 3-116
examples, 3-107
format, 3-99
keywords
/ACCESS, 3-100
/BAD, 3-100
/DENS, 3-102
/EXT, 3-102
/FPRO, 3-102
/INDX, 3-103
/INF, 3-103
/LRU, 3-104
/MXF, 3-105
/OWNER, 3-105
/POS, 3-106
/PRO, 3-106
/UIC, 3-107
/WIN, 3-107
parameters, 3-99
/INQUIRE keyword
SET command, 3-225
INS command
See INSTALL command
INS'TALL command, 1-6, 3-116
format, 3-116
installing task, 2-21, 2-23
keywords
/AFF, 3-117
/CKP, 3-117
/CLI, 3-117
/FMAP, 3-118
/INC, 3-118
/IOP, 3-118
/PAR, 3-119
/PMD, 3-119
/PRI, 3-119
/ROPAR, 3-120
/SEC, 3-120
/SLV, 3-120
/SYNC, 3-121
/TASK, 3-121
/TIME, 3-121
/UIC, 3-121
/WB, 3-122
/XHR, 3-122
parameters, 3-116
Instruction
data space, 3-167
Interrupt
clock, 3-180
vector, 3-132
Interval
reschedule, 3-180
/IOP keyword
INSTALL command, 3-118
RUN command, 3-183
c
Keyword
function, 1-4
position, 1-4
syntax, 1-4
/KNL keyword
OPENREGISTER command, 3-166
/KNLD keyword
OPENREGISTER command, 3-166
/LABEL keyword
MOUNT command, 3-149
LB:, 2-7, 2-11, 3-35, 3-188
LBN
See Logical block number
Library
directory, 3-117, 3-182
resident
installing, 3-116
LIBUIC
See Library directory
/LIBUIC keyword
SET command, 3-225
Line
dial-up, 3-247
local, 3-248
displaying, 3-248
remote, 3-202, 3-247
terminal
parallel processing, 3-252
serial processing, 3-251
/LINES keyword
SET command, 3-226
LOA command
See LOAD command
LOAD command, 1-6, 3-132
format, 3-132
keywords
/CTB, 3-l32
/EXP, 3-l33
/H I GH, 3 -l3 3
/PAR, 3-l33
/SIZE, 3-l33
/VEC, 3-l33 '
parameters, 3-132
/LOC keyword
HELP command, 3-87
Local logical assignment, 3-20
/LOCK keyword
DISMOUNT command, 3-71
MOUNT command, 3-149
options
/Noun1oad, 3-71
/Un1oad, 3-71
/Virtua1, 3-71
LOG command
See LOGIN command
/LOG keyword
DEVICES command, 3-60
Index-8
c
(
INDEX
(
(
(
Logical assignment, 3-20 to 3-30,
3-63 to 3-69
assigning, 3-25, 3-26
deleting, 3-21, 3-25, 3-27,
3-28
displaying, 3-29
global, 2-12, 3-20, 3-64
group, 2-12, 3-20, 3-64
local, 2-12, 3-20, 3-64
login, 2-12, 3-20, 3-64
system, 3-20
tables, 3-64
task, 2-12, 3-20
Logical block number, 3-103,
3-116, 3-189
Logical device assignment, 2-12,
3-20 to 3-30
assigning, 3-20
device name tables, 3-20
Logical device name, 2-12
assigning, 3-20
syntax, 2-12, 3-20
Logical name assignment, 3-20,
3-21, 3-63 to 3-69
assigning, 3-63, 3-65
deleting, 3-65, 3-67
displaying, 3-65, 3-68
global, 3-21, 3-63, 3-64
group, 3-21, 3-63, 3-64
local, 3-63, 3~64
login, 3-21
tables, 3-22, 3-63 to 3-64
task, 3-20
translation, 3-64
Logical unit numbers, 2-10, 3-36,
3-172
See also LOGICAL UNIT NUMBERS
command
assigning, 2-10
reassigning, 3-172
LOGICAL UNIT NUMBERS command, 1-7,
3-140
error messages, 3-140
example, 3-140
format, 3-140
Login
default logical device, 3-79
default logical directory, 3-79
logical assignment, 3-20
UIC, 2-6
LOGIN command, 1-8, 3-79
error messages, 3-84
examples, 3-83
/LOGIN keyword
ASSIGN command, 3-26, 3-28
/LOGON keyword
SET command, 3-226
/LOWER keyword
SET command, 3-226
/LRU keyword
HOME command, 3-94
INITVOLUME command, 3-104
MOUNT command, 3-150
LUN
See Logical unit numbers
LUN command
See LOGICAL UNIT NUMBERS
command
Magnetic tape
dismounting, 3-71
initializing, 3-99
label, 3-71, 3-100
mounting, 3-143
record, 3-152
/MAIN keyword
SET command, 3-227
Master File Directory, 2-2, 3-94,
3-103, 3-104, 3-150, 3-280
/MAXEXT keyword
SET command, 3-229
/MAXPKT keyword
SET command, 3-230
MCR
interface, 1-5
keywords, 1-4
prompt, 1-3, 2-17
See also Prompt
summary of commands, 1-5 to 1-8
/MCR keyword
HELP command, 3-88
SET command, 3-231
Memory
address, 3-164
dynamic, 3-118, 3-132, 3-183
fixing tasks in, 3-75
location
closing, 3-165
displaying, 3-164
inserting values in, 3-164
opening, 3-164
mapping, 2-20
partition, 2-20
/MESSAGE
keyword
CLI command, 3-52
subkeyword
CLI command, 3-52
Message
error
See individual commands,
Appendix A
system service, 3-273
MFD
See Master File Directory
MOU command
See MOUNT command
/MOU keyword
SAVE command, 3-190
MOUNT command, 1-6, 3-141
formats, 3-142, 3-144
keywords
/ACP, 3-145
/BS, 3-146
/CACHE, 3-146
ICC, 3-147
/DENS, 3-147
Index-9
INDEX
MOUNT command
keywords (Cont.)
/FOR, 2-14, 3-148
/FPRO, 3-148
/LOCK, 3-149
/LRU, 3-150
/[NO]HDR3, 3-149
/[NO]LABEL, 3-149
/[NO]SHARE, 3-152
/[NOIWAIT, 3-154
/[NO]WRITE, 3-155
/OVR, 3-150
/OVRACC, 3-151
/OVREXP, 3-151
/OVRFSID, 3-151
/PARM, 3-151
/PRO, 3-151
/J:lUB, 3-152
/RS, 3-152
/TR, 3-152
/UIC, 3-153
/UNL, 3-153
/VI, 3-153
/VOL, 3-154
/WIN, 3-155
parameters, 3-142
volume
accessing, 2-13
mounting, 2-3
Multiplexer, 3-247, 3-254
Multiprogramming, 2-21
Multiuser protection
and devices, 2-13
commands, 1-8
system, 2-6
/MXF keyword
HOME command, 3-95
INITVOLUME command, 3-105
OPENREGISTER command
keywords (Cont.)
/KNL, 3-166
/KNLD, 3-166
parameters, 3-164
Operating system
See System
/OPT keyword
SET command, 3-235
Overlay, 1-5
data caching, 3-146, 3-208
memory-resident, 3-183
/OVLP keyword
SET command, 3-236
/OVR keyword
HOME command, 3-95
MOUNT command, 3-150
/OVRACC keyword
MOUNT command, 3-151
/OVREXP keyword
MOUNT command, 3-151
/OVRFSID keyword
MOUNT command, 3-151
/OWNER keyword
HOME command, 3-95
INITVOLUME command, 3-105
/NAME keyword
HOME command, 3-95
/NAMED keyword
SET command, 3-231
/NETUIC keyword
SET command, 3-234
Network
connecting to, 3-247
dial-up, 3-247
/NOCEX keyword
SET command, 3-234
Null device, 2-11
ODT, 3-58
On-line Debugging Tool
See ODT
OPE command
See OPENREGISTER command
lOPE keyword
OPENREGISTER command, 3-166
OPENREGISTER command, 1-8, 3-164
format, 3-164
keywords
/AFF, 3-165
/CPU, 3-165
PAR command
See PARTITION DEFINITIONS
command
/PAR keyword
INSTALL command, 3-119
LOAD command, 3-133
RUN command, 3-183
SET command, 3-237
Parameters·
command line, 1-2
Parity checking, 3-239
/PARITY keyword
SET command, 3-239
/PARM keyword
MOUNT command, 3-151
Partition
See also Subpartition
address, 2-20
accessing, ~-166
cache
specifying, 3-146, 3-207
common, 3-116, 3-169
creating, 3-237
defining, 3-267
definition, 2-20
displaying, 3-169, 3-237
eliminating, 3-267
GEN, 3-119, 3-133
loading device driver, 3-133
mapped system, 2-20
name, 2-20, 3-169
naming, 3-119
size, 2-20, 3-169, 3-237
setting, 3-259
system, 3-183, 3-267
system-controlled, 2-20, 3-118,
3-169
Index-l0
()
(
INDEX
c
(
l
Partition (Cont.)
task
allocating, 2-20
fixing, 3-76
installing, 3-183
relationship between, 2-20
type, 2-20, 3-169
DEV, 3-237
DIAG, 3-238
SYS, 3-237
unmapped system, 2-20
user, 3-267
user-controlled, 2-20, 3-169
Partition Control Block, 3-31,
3-134
address, 3-46, 3-169
PARTITION DEFINITIONS command,
1-7, 3-169
display, 3-169
format, 3-170
Password
account, 3-240
changing, 2-24, 3-240
encryption, 3-240
maximum length, 3-240
task, 3-240
/PASSWORD keyword
SET command, 3-240
/PASTHRU keyword
SET command, 3-241
PCB
See Partition Control Block
Peripheral device
See Device
Peripheral Interchange Program
See PIP
PIP, 2-2
deleting directory, 2-2
files
accessing, 2-3
deleting, 2-2
/PLCTL keyword
SET command, 3-243
PMD
See Postmortem Dump
/PMD keyword
ABORT command, 3-4
INSTALL command, 3-119
RUN command, 3-184
PMT
See Pool Monitor Task
Pool
installing headers in, 3-122
limit
displaying, 3-244
setting, 3-243
primary
installing tasks, 3-31
secondary
displaying, 3-251
installing tasks, 3-31, 3-120
percent in use, 3-251
saving, 3-187
size
Pool
size (Cont.)
displaying, 3-244
setting, 3-244
space
allocating, 3-267
/POOL keyword
SET command, 3-244
Pool Monitor Task, 3-243
/POS keyword
HOME command, 3-95
INITVOLUME command, 3-106
Postmortem Dump, 3-3
generating, 3-119
requesting, 3-184
task, 3-184
/PRI keyword
ALTER command, 3-19
INSTALL command, 3-119
RUN command, 3-184
/PRINTER PORT keyword
SET command, 3-242
/PRIV keyword
SET command, 3-244
Privilege status, 2-6, 3-2
/PRO keyword
HOME command, 3-96
INITVOLUME command, 3-106
MOUNT command, 3-151
USER FILE DIRECTORY command,
3-281
Processor Status Word, 3-31, 3-58
Program Counter, 3-31
Prompt
CLI string, 3-49
default, 2-14
MCR, 1-3, 2-14, 2-16
task, 2-14
Protection
account, 2-24, 3-241
code
UIC, 2-3
common region, 3-119
fi1e, 3-148, 3-152, 3-214
specifying default, 3-102
magnetic tape, 3-151
multiuser, 2-6, 2-12, 2-24,
3-79
multiuser commands, 1-8
UIC, 3-185
volume, 3-148, 3-151
Pseudo device, 2-10 to 2-11
See also Device
names, 2-10
/PUB keyword
MOUNT command, 3-152
SET command, 3-245·
Queue optimization, 3-235
algorithms, 3-235
fairness-count, 3-235
REA command
See REASSIGN command
Index-11
INDEX
Read access, 2-3
common region, 3-119
file, 3-148, 3-213
UFD, 3-281
volume, 3-94, 3-96, 3-106,
3-151
REASSIGN command, 1-7, 3-172
error messages, 3-172
examples, 3-172
format, 3-172
parameters, 3-172
RED command
See REDIRECT command
REDIRECT command, 1-6, 3-173
and pseudo devices, 2-10
error messages, 3-173
examples, 3-173
format, 3-173
parameters, 3-173
/REG keyword
FIX-IN-MEMORY command, 3-75
UNFIX command, 3-284
Region
address
accessing, 3-166
common, 3-75
accessing, 3-120
installed, 3-119
protecting, 3-119
status, 3-46
synchronizing, 3-121
tasks, 3-47
unfixing, 3-284
data caching, 3-146, 3-207
removing, 3-175
ReGIS character set, 3-246
/REGIS keyword
SET command, 3-246
REM command
See REMOVE command
/REMOTE keyword
SET command, 3-247
REMOVE command, 1-7, 3-175, 3-180
error messages, 3-176
example, 3-175
format, 3-175
parameter, 3-175
RES command
See RESUME command
Resource Accounting, 2-6, 3-121
RESUME command, 1-7, 3-177
error messages, 3-177
example, 3-177
format, 3-177
keyword
/TERM, 3-177
parameter, 3-177
RETURN key, 2-15
/RNDC keyword
SET command, 3-248
/RNDH keyword
SET command, 3-249
/RNDL keyword
SET command, 3-249
/RON keyword
FIX-IN-MEMORY command, 3-75
UNFIX command, 3-284
/ROPAR keyword
INSTALL command, 3-120
RUN command, 3-184
/RPA keyword
SET command, 3-250
/RPRI keyword
ALTER command, 3-19
/RS keyword
MOUNT command, 3-152
/RSI keyword
RUN command, 3-180, 3-181
RUN command, 1-8, 3-178
error messages, 3-186
examples, 3-185
formats, 3-178
installing task, 2-23
keywords
/CKP, 3-182
/CMD, 3-182
/EST, 3-178, 3-182
/INC, 3-183
/IOP, 3-183
/PAR, 3-183
/PMD, 3-184
/PRI, 3-184
/ROPAR, 3-184
/RSI, 3-180, 3-181
/SLV, 3-184
/TASK, 3-184
/TIME, 3-185
/UIC, 3-179, 3-180, 3-185
options
absolute time, 3-178
immediate, 3-178
install-run-remove, 2-21,
2-23, 3-140, 3-178
synchronized, 3-178
time increment, 3-178
prototype task, 3-178
SAV command
See SAVE command
SAVE command, 1-8, 3-187
error messages, 3-191
examples, 3-191
format, 3-189
keywords
/CSR, 3-190
/MOU, 3-190
/SFILE, 3-190
/WB, 3-190
/SEC keyword
INSTALL command, 3-120
/SECPOL keyword
SET command, 3-251
/SERIAL keyword
SET command, 3-251
SET command, 1-6, 3-197
error messages, 3-268 to 3-272
format, 3-198
keyword
Index-12
(
c
(
INDEX
(
(
SET command
keyword (Cont.)
list, 3-199T to 3-202T
keywords
/BUF, 3-206
/CLI, 3-118, 3-209
/CRASHDEV, 3-209
/DCL, 3-211
/DEF, 3-212
/HFILL, 3-220
/HOST, 3-223
/INQUIRE, 3-225
/LIBUIC, 3-225
/LINES, 3-226
/MAXEXT, 3-229
/MAXPKT, 3-230
/MCR, 3-231
/NETUIC, 3-234
/[NO]ABAUD, 3-202
/[NO]ANSI, 3-203
/[NO]AVO, 3-204
/[NO]BLKMOD, 3-205
/[NO]BRO, 3-205
/[NO]CACHE, 3-207
/[NO]CRT, 3-210
/[NO]DEC, 3-211
/[NO]DPRO, 2-3, 3-213
/[NO]EBC, 3-215
/[NO]ECHO, 3-216
/[NO]EDIT, 3-217
/[NO]ESCSEQ, 3-217
/[NO]FDX, 3-218
/[NO]FORMFEED, 3-219
/ [NO] HHT, 3-2·21
/[NO]HOLD, 2-17, 3-222
/[NO]HSYNC, 3-223
/[NO]LOGON, 3-226
/[NO]LOWER, 3-226
/[NO]MAIN, 3-227
/[NO]NAMED, 3-231
/[NO]OPT, 3-235
/[NO]OVLP, 3-236
/[NO]PAR, 3-237
/[NO]PARITY, 3-239
/[NO]PASTHRU, 3-241
/[NO]PRINTER PORT,3-242
/[NO]PRIV, 2=19, 3-244
/[NO]PUB, 2-13, 3-245
/[NO]REGIS, 3-246
/[NO]REMOTE, 3-247
/[NO]RPA, 3-250
/[NO]SERIAL, 3-251
I[NO]SLAVE, 2-19, 3-252
/[NO]SOFT, 3-253
/[NO]SUB, 3-255
/[NO]TTSYNC, 3-261
/[NO]TYPEAHEAD, 3-261
/[NO]VFILL, 3-264
/[NO]WCHK, 3-265
/[NO]WRAP, 3-266
/NOCEX, 3-234
/PASSWORD, 3-240
/PLCTL, 3-243
/POOL, 3-244
SET command
keywords (Cont.)
/RNDC, 3-248
/RNDH, 3-249
/RNDL, 3-249
/SECPOL, 3-251
/SPEED, 3-254
/SWPC, 3-256
/SYSUIC, 3-182, 3-257
/TERM, 3-258
/TOP, 3-259
/UIC, 2-6, 3-263
nonprivileged options, 3-197
privileged options, 3-197
/SET keyword
SWITCH REGISTER command, 3-274
/SFILE keyword
SAVE command, 3-190
/SHARE keyword
MOUNT command, 3-152
/SIZE keyword
LOAD command, 3-133
/SLAVE keyword
SET command, 3-252
/SLV keyword
INSTALL command, 3-120
RUN command, 3-184
/SOFT keyword
SET command, 3-253
Special character key, 2-15 to
2-18
/SPEED keyword
SET command, 3-254
SSM command
See SYSTEM SERVICE MESSAGE
command
STD
See System Task Directory
/SUB keyword
SET command, 3-255
Subpartition
See also Partition
base address, 3-255
defining, 3-267
definition, 2-20
displaying, 3-256
eliminating, 3-256, 3-267
setting, 3-255
size, 3-255
task, 2-21
Swi tch, 2-5
See also Keyword
argument, 2-6
SWITCH REGISTER command, 1-8,
3-274
examples, 3-274
formats, 3-274
keywords
/CLE, 3-274
/DIS, 3-274
/SET, 3-274
parameters, 3-274
/SWPC keyword
SET command, 3-256
Index-13
INDEX
SWR command
See SWITCH REGISTER command
SY:, 2-4, 2-7, 2-11, 3-79, 3-212
user device logical, 3-21
/SYNC keyword
INSTALL command, 3-121
SYS$LOGIN
user directory logical, 3-21
System
bootstrapping, 3-35
restrictions, 3-36
unsaved
wi th XDT, 3-36
unsaved system, 3-36
valid device, 3-35
checkpoint file, 3-11
device
default, 3-79
directory, 3-182
identification, 3-79
image file, 3-187
location, 3-187
saving, 3-187
devices, 3-187
size, 3-187
transporting, 3-36, 3-190
maintenance commands, 1-8
mapped, 2-20, 3-164
UIC, 3-257
saved
installing task, 3-116
saving, 3-188
UIC, 2-3
unmapped, 2-20, 2-21
UIC, 3-257
unsaved
installing task, 3-116
System logical assignment, 3-20
SYSTEM SERVICE MESSAGE command,
1-8, 3-273
example, 3-273
format, 3-273
System Task Directory, 1-5, 3-116,
3-182, 3-189
installing task, 2-23, 3-179
removing task, 3-175
/SYSUIC keyword
SET command, 3-257
TAL cominand
See TASKLIST-ATL command
TAS command
See TASKLIST command
Task
aborted, 3-283
aborting, 2-24, 3-3
access rights, 2-20
accessing, 3-122
active, 1-5, 2-23, 3-14, 3-76
displaying, 3-31
list, 3-31
address
accessing, 3-166
space
Task
address
space (Cont.)
allocating, 3-183
attached, 1-3, 2-15, 2-19
blocked, 2-21, 3-283
priority, 3-34
building, 3-123
default partition, 3-119
device driver, 3-134
header, 3-123
name, 3-121
cancelling, 3-45
catchall, 3-179
checkpointing, 2-20, 3-33, 3-75,
3-117, 3-118, 3-182
CLI
removing, 3-175
common
fixing, 3-75
installing, 3-120, 3-184
unfixing, 3-284
common region
mapping count, 3-46
synchronizing, 3-121
control commands, 1-7
creating, 2-21
debugging, 3-58
definition, 2-19
device independence, 2~12
displaying, 3-275
dormant, 2-23, 3-116
dynamic memory, 3-183
event flags, 3-77
executing, 3-116
resources, 3-117
exiting, 1-5
extending, 3-118
fixing in memory, 3-75
restrictions, 3-75
header
external, 3-122
installing, 3-122
options, 3-123
image file, 3-35, 3-116, 3-175,
3-179, 3-182, 3-187
creating, 2-21
install ing, 2-21
STD entry, 1-5
installed, 1-5
blocking, 3-34
displaying, 3-276
installing, 1-5, 2-23, 3-116,
3-120
time limit, 3-121
loading, 3-75
partition, 3-133
logical assignment, 3-20
mapping, 3-118, 3-183
naming, 1-5, 2-14, 2-21, 2-22,
2-24, 3-121, 3-185
nonprivileged, 2-20
object file, 2~21
overlay, 3-118
Index-14
c
c
(
INDEX
(
(
(
)
Task (Cont.)
partition, 2-20
installing, 3-183, 3-267
specifying size, 3-118, 3-183
system-controlled, 3-118
priority, 2-21, 3-257
altering, 3-3, 3-19
base, 3-243
running, 3-3, 3-19
specifying, 3-119, 3-184
static, 3-19
privileged, 2-20, 3-183
Processor Status Word, 3-58
prompt, 1-3, 2-14
protecting, 3-122, 3-185
prototype, 3-186
installing, 3-121
reassigning, 3-172
removing, 3-175
resident, 3-75
resuming, 3-177
running, 1-5, 2-11, 2-20, 2-24,
3-178 to 3-186
options
immediate, 3-186
install-run-remove, 3-186
reschedule interval, 3-180
UIC, 3-185
uninstalled, 3-179
size, 3-118
slave, 3-120, 3-184
spawning, 2-23, 3-183, 3-186
status flags
displaying, 3-31
list of, 3-32 to 3-33
subpartition, 2-21
system, 3-257
terminal
attached, 2-19
slave, 2-19
time limit
specifying, 3-185
UIC, 3-263
specifying, 3-122
unblocked, 3-283
unfixing, 3-284
unloading, 3-75
Task Builder, 2-20, 3-3, 3-122,
3-183
switch
/CP, 3-117
/DA, 3-59
/IP, 3-118, 3-183
/XH, 3-123
task
object file, 2-9, 2-21
priority, 2-21
Task Control Block, 3-31, 3-34
creating, 3-116
installing, 3-120
removing, 3-116
saving, 3-189
Task control commands, 1-7
/TASK keyword
INSTALL command, 3-121
RUN command, 3-184
/TASK subkeyword, 3-52
Task Termination Notification
program
See TKTN
TASKLIST command, 1-7, 3-276
error messages, 3-277
examples, 3-276
format, 3-276
parameters, 3-276
TASKLIST-ATL command, 1-7, 3-275
examples, 3-275
format, 3-275
parameters, 3-275
/TASKS keyword
COMMON BLOCK DIRECTORY command,
3-46
TCB
See Task Control Block
/TERM keyword
ABORT command, 3-4
ACTIVE command, 3-14
ALLOCATE command, 3-16
ALTER command, 3-19
ASSIGN command, 3-28, 3-29
BLOCK command, 3-34
DEFINE LOGICALS command, 3-67,
3-68
DISMOUNT command, 3-71
RESUME command, 3-177
SET command, 3-258
UNBLOCK command, 3-283
UNSTOP command, 3-287
Terminal
attached, 2-19
baud rate
setting, 3-254
buffer, 3-261
characteristics
setting, 3-197, 3-202 to
3-267
eLI
default, 3-79
definition of, 2-14
directory
default, 2-7
displaying, 3-60
driver
full-duplex, 3-219
half-duplex, 3-258
nonprivileged, 2-19
nonslave, 3-253
numbers, 2-22
privilege status, 2-19, 3-80
prompt, 1-3
read-pass-all, 3-250
remote, 3-202
displaying, 3-247
setting, 3-247
session
accounting, 3-79
slave, 2-19, 3-80
Index-15
INDEX
Terminal
slave (Cont.)
displaying, 3-253
setting, 3-252
speed
setting, 3-254
synchronization
disabling, 3-261
setting, 3-261
task
attaching, 2-15, 2-19
displaying, 3-60
name, 2-21, 2-22
running, 1-5, 2-14
type
setting, 3-258
UIC, 2-6
unattached, 2-19
TI:, 2-11
. T 1M command
See TIME command
TIME command, 1-6, 3-278
examples, 3-279
format, 3-278
parameters, 3-278
/TIME keyword
INSTALL command, 3-121
RUN command, 3-185
TKB
See Task Builder
TKTN, 3-3
messages, 3-5 to 3-8
See also Appendix A
format, 3-5
/TOP keyword
SET command, 3-259
/TR keyword
MOUNT command, 3-152
!TTSYNC keyword
SET command, 3-261
/TYPE keyword
ALLOCATE command, 3-16
/TYPEAHEAD keyword
SET command, 3-261
UCB
See Unit Control Block
UFD, 2-2, 3-1
and UIC, 2-2
command, 2-2
contents, 2-2
creating, 2-2
default, 2-2
deleting, 2-2
format, 2-2
group number, 2-2
member number, 2-2
UFD command
See USER FILE DIRECTORY command
UIC, 2-2, 2-6, 3-1, 3-81
and UFD, 2-2, 3-212, 3-280
default, 2-6
event flags, 3-77
group
UIC
group (Cont.)
access count, 3-77
login, 2-6
password, 3-79
privilege status, 2-6
protection, 2-6
running tasks, 3-178
system task, 3-257
task
specifying, 3-122
terminal, 2-6
setting, 3-263
user categories
group, 2-3
owner, 2-3system, 2-3
world, 2-3
volume
specifying, 3-153
/UIC keyword
HOME command, 3-96
INITVOLUME command, 3-107
INSTALL command, 3-121
MOUNT command, 3-153
RUN command, 3-178, 3-180,
3-185
SET command, 3-263
UNB command
See UNBLOCK command
UNBLOCK command, 1-8, 3-283
examples, 3-283
format, 3-283
keywords
/TERM, 3-283
parameters, 3-283
UNF command
See UNFIX command
UNFIX command, 1-8, 3-284
error messages, 3-284
examples, 3-284
formats, 3-284
keywords
/REG, 3-284
/RON, 3-284
parameters, 3-284
UNIBUS
run specifications, 3-111
Unit Control Block, 3-116
UNL command
See UNLOAD command
/UNL keyword
MOUNT command, 3-153
UNLOAD command, 1-8, 3-285
error messages, 3-285
example, 3-285
format, 3-285
keyword
/VEC, 3-285
parameter, 3-285
UNS command
See UNSTOP command
UNSTOP command, 1-8, 3-287
examples, 3-287
Index-16
(
c
c-
INDEX
(
c
(
UNSTOP command (Cont.)
format, 3-287'
keywords
/TERM, 3-287
parameter, 3-287
User File Directory
See UFD
USER FILE DIRECTORY command, 1-7,
3-280
creating UFO, 2-3
error messages, 3-281
example, 3-281
format, 3-280
keywords
/ALLOC, 3-280
/PRO, 3-281
parameters, 3-280
User Identification Code
See UIC
/USER keyword
DISMOUNT command, 3-71
/VEC keyword
LOAD command, 3-133
UNLOAD command, 3-285
/VFILL keyword
SET command, 3-264
/VI keyword
HOME command, 3-96
MOUNT command, 3-153
/VOL keyword
MOUNT command, 3-154
Volume
accessing
dismounted, 3-142
allocating, 3-152
bit density, 3-147
DECtape
initializing, 3-99
directories, 3-150
dismounting, 3-70
displaying information, 3-153
Files-II, 2-1, 3-35
home block, 3-93
initializing, 3-99 to 3-116
foreign, 2-1
accessing, 2-2
displaying information, 3-153
mounting, 2-2, 3-148, 3-151
home block, 3-149
identifier, 3-144, 3-154
index file
unlocking, 3-153
initializing, 2-1
label, 3-70, 3-100, 3-150
Volume (Cont.)
locking, 3-149
magnetic tape
labelling, 3-147, 3-149
protecting, 3-151
record, 3-152
mounting, 2-3, 3-141
Files-II, 3-142
foreign, 3..,..148
magnetic tape, 3-142, 3-1~3
nonprivileged, 3-142
shared, 3-152
mounting with ACP, 3-148, 3-149
nonshared, 3-142
private
mounting, 3-148
protecting, 3-102, 3-151
public, 3-142, 3-152
dismounting, 3-71
mounting, 3-152
setting, 3-152
record type, 3-147
shared, 3-142
UIC
specifying, 3-153
unloading, 3-149
virtual, 3-149
/WAIT keyword
MOUNT command, 3-154
/WE keyword
INSTALL command, 3-118, 3-122
SAVE command, 3-190
/WCHK keyword
SET command, 3-265
Wildcard character, 2-7
/WIN keyword
HOME command, 3-97
INITVOLUME command, 3-107
MOUNT command, 3-155
/WRAP keyword
SET command, 3-266
Write access, 2-3
common region, 3-119
file, 3-148, 3-213
UFD, 3-281
volume, 3-94, 3-96, 3-106,
3-151
/WRITE keyword
MOUNT command, 3-155
XDT
See Executive Debugging Tool
/XHR keyword
INSTALL command, 3-122
Index-17
C/,
RSX-llM/M-PLUS
MCR Operations Manual
. AA-FDlOA-TC
READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a wntten reply and are eligible to receive one under Software
. Performance Report (SPR) service, submit your comments on an SPR form.
Did you find this manual understandable, usable, and well organized? Please make suggestions for improvement.
Did you find errors in this manual? If so, specify the error and the page number.
Please indicate the type of user/reader that you most nearly represent.
o
o
o
o
o
o
Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify)
Name _____________________________________________ Date ______________________________
Organization
Street
City ___________________________________________ State __________ Zip Code ___________
or Country
(
-
-
DoNotTear-FoldHereandTape -
-
-
-
-
-
-
-
-
-
~DmDDmD
IIIIII
No Postage
Necessary
if Mai led ir the
United States
BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE
SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698
- -
-..:.. -
Do Not Tear - Fold Here
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
_
-
_
-
_
_
Printed in U.S.A.
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : Yes XMP Toolkit : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19 Create Date : 2006:06:21 13:22:27Z Modify Date : 2017:08:05 22:31:18-07:00 Metadata Date : 2017:08:05 22:31:18-07:00 Format : application/pdf Document ID : uuid:68acca48-a0f0-44d1-8e01-2aeed72fa67f Instance ID : uuid:8446aad3-7e95-db4b-99b2-740290fc3a7c Producer : Adobe Acrobat 9.0 Paper Capture Plug-in Page Layout : SinglePage Page Count : 388EXIF Metadata provided by EXIF.tools