Digital PDFs

AA-H263A-TC

June 1979

324 pages

Original

17MB

Document:	RSX-11M/M-PLUS MCR Operations Manual
Order Number:	AA-H263A-TC
Revision:	0
Pages:	324
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V3.2_Jun79/2_Operation/AA-H263A-TC_RSX-11M_V3.2_MCR_Operations_197906.pdf

OCR Text

RSX-11 M/M-PLUS
MCR Operations Manual
Order No. AA-H263A-TC

RSX-11 M Version 3.2
RSX-11 M-PLUS Version 1.0

To order additional copies of this document, contact the Software Distribution
Center, Digital Equipment Corporation, Maynard, Massachusetts 01754

digital equipment corporation · maynard, massachusetts

First Printing, June 1979
The information in this document is subject to change without notice
and should not be construed as a conunitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may only be used or copied 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 or its affiliated companies.

1979 by Digital Equipment Corporation

The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DEC US
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM
ASSIST-11
VAX
DECnet
DATATRIEVE

DECsystem-lo
DECtape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20
RTS-8
VMS
IAS
TRAX

MASS BUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11
TMS-11
ITPS-10
SBI
PDT

CONTENTS
Page
SUMMARY OF TECHNICAL CHANGES

vii

PREFACE

CHAPTER

INTRODUCTION

1-1

1..1
1.. 2
1.. 2 .1
1.. 2. 2
1.. 3
1.. 4

1-1
1-1
1-1

1. 4 .1

TASKS
PARTITIONS
Partition Types
Subpartitions
MULTIPROGRAMMING
TASK OPERATION
Installing A Task

PROCEDURES AND CONVENTIONS

2-1

2.1
TERMINALS
2 .1.1
Special and Control Characters
2 .1. 2
Terminal Characteristics
2.1.2.1
Terminal Privilege
2.1.2.2
Attached and Unattached Terminals
2.1.2.3
Slave Terminals
2 .1. 3
Input Prompts
2.1.3.l
The Default Prompt
2.1.3.2
The Task Prompt
2.1.3.3
The MCR Prompt
2.2
DEVICES
2.2.1
Pseudo Devices
The Null Device
2.2.2
2.2.3
Logical Devices
2.3
MULTIUSER PROTECTION FUNCTIONS
Logging On and Off a Terminal
2.3.1
2.3.1.1
The Hello Command
2.3.1.2
The Bye Command
2.3.2
Public, Private, and Unowned Devices
The Account File Maintenance Program (ACNT)
2.3.3
2.3.3.l
Creating the Account File
2.3.3.2
Adding Account Entries
Examining Account Entries
2.3.3.3
2.3.3.4
Modifying Account Entries
Listing All Account Entries
2.3.3.5
Sorting the Account File
2.3.3.6
Deleting Account Entries
2.3.3.7
Nonprivileged Account Modifications
2.3.3.8
2.3.3.9
ACNT Error Messages
THE SHUTUP PROGRAM
2.4
CHAPTER

1-2
1-2
1-2
1-3

2-1
2-1
2-5
2-6
2-6
2-6
2-7
2-7
2-7
2-7
2-8
2-11
2-12
2-12
2-13
2-13
2-14
2-15
2-16
2-17
2-18
2-18
2-19

2-20
2-21
2-21
2-21
2-22
2-22
2-23

FILES AND VOLUMES

3-1

3.1
3 .1.1
3 .1. 2

FILES-11
File Ownership and Directories
File Protection

3-1
3-1
3-2

iii

CONTENTS

Page

CHAPTER

3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5

FILE SPECIFIERS
User Identification Codes (UICs)
File Specifier Defaults
Standard File Types
The Asterisk Convention (Wildcards)
Examples of File Name Command Strings

3-3
3-5
3-6
3-6
3-8
3-8

MCR COMMANDS

4-1

INTRODUCTION
4.1
THE MCR INTERFACE
4.2
Keywords
4.2.1
Comments
4.2.2
Command References to Active Tasks
4.2.3
Task-Naming Convention
4.2.3.l
Install-Run-Remove Tasks
4.2.3.2
COMMAND SUMMARY
4.3
COMMAND DESCRIPTION FORMAT AND SYNTAX
4.4
NONPRIVILEGED MCR COMMAND DESCRIPTIONS
4.5
ABO (Abort)
ACT (Active)
ALL (Allocate)
ASN (Assign)
ATL (Active Task List)
BRO (Broadcast)
BYE (Bye)
CAN (Cancel)
CBD (Common Block Directory)
DEA (Deallocate)
DEV (Devices)
DMO (Dismount)
FLA (Group Global Event Flags)
HEL (Hello)
HELP (Help)
INI (Initvolume)
LUN (Logical Unit Numbers)
MOU (Mount)
PAR (Partition Definitions)
RES (Resume)
RUN (Run)
SET (Set)
STP (Stop)
TAL (Task List - ATL Format)
TAS (Task List)
TIM (Time)
UFD (User File Directory)
UNS (Unstop)
PRIVILEGED MCR COMMAND DESCRIPTIONS
4.6
ACS (Allocate Checkpoint Space)
ALT (Alter)
BOO (Boot)
BRK (Breakpoint to Executive Debugging Tool)
CLQ (CLQUEUE)
FIX (Fix-in-Memory)
INS (Install)
LOA (Load)
OPE (Open Register)
REA (Reassign)

4-1
4-2
4-3
4-3
4-3
4-3
4-5
4-6
4-8
4-10
4-10
4-14
4-16
4-18
4-21
4-24
4-27
4-28
4-29
4-31
4-32
4-36
4-40
4-41
4-46
4-51
4-64
4-65
4-76
4-79
4-80
4-87
4-126
4-127
4-128
4-130
4-131
4-134
4-135
4-135
4-138
4-139
4-142
4-143
4-144
4-146
4-157
4-165
4-168

~·-'81\

at.,,.

CONTENTS
Page
RED
REM
SAV
SSM
SWR
UNF
UNL
CHAPTER

(Redirect)
(Remove)
(Save)
(System Service Message)
(Switch Register)
(Unfix)
(Unload)

INDIRECT COMMAND FILES

!5. 1
INTRODUCTION
5. 2
MCR INDIRECT FILE PROCESSOR
SYMBOLS
5. 3
5.3.1
Special Symbols
5.3.1.1
Special Logical Symbols
5.3.1.2
Special Numeric Symbols
5.3.1.3
Special String Symbols
5.3.2
Symbol Value Substitution
5.3.3
Numeric and String Symbols
5.3.3.l
Numeric Symbols and Expressions
5.3.3.2
String Symbols, Substrings, and Expressions
5.4
SWITCHES
5.5
MULTI-LEVEL INDIRECT FILES
5.6
DIRECTIVES
5.6.1
Define a Label
5.6.2
Ask a Question and Wait for a Reply
Ask for Definition of a Numeric Symbol
5.6.3
5.6.4
Ask for Definition of a String Symbol
Begin Block
5.6.5
Continue Processing Using Another File
5.6.6
5.6.7
Close Secondary File
Output Data to Secondary File
5.6.8
5.6.9
Decrement Numeric Symbol
5.6.10
Delay Execution for a Specified Period of
Time
5.6.11
Disable Option
5.6.12
Enable Option
5.6.13
End Block
5.6.14
Delete Symbols
5.6.15
Exit Current Command File
Call a Subroutine
5.6.16
Branch to a Label
5.6.17
Logical Test
5.6.18
5.6.18.1 Test if Symbol Meets Specified Condition
5.6.18.2 Test if Task is Active or Dormant
5.6.18.3 Test if Symbol is Defined or Not Defined
5.6.18.4 Test if Task is Installed or Not Installed
5.6.18.5 Test if Driver is Loaded or Not Loaded
5.6.18.6 Test if Symbol is True or False
5.6.18.7 Compound Tests
Increment Numeric Symbol
5.6.19
5.6.20
Define Logical End of File
5.6.21
Branch to Label on Detecting an Error
5.6.22
Open Secondary File
Open Secondary File for Append
5.6.23
Pause for Operator Action
5.6.24
Return from a Subroutine
5.6.25
5.6.26
Set Symbol to True or False

4-169
4-171
4-172
4-182
4-183
4-184
4-185
5-1
5-1
5-2
5-5
5-6
5-6
5-7
5-7
5-8
5-9
5-9
5-10
5-10
5-11
5-11
5-12
5-13
5-14
5-16
5-17
5-18
5-18
5-18
5-19
5-19
5-20
5-20
5-23
5-23
5-24
5-25
5-25
5-26
5-26
5-27
5-27
5-27
5-28
5-28
5-29
5-29
5-30
5-30
5-31
5-31
5-32
5-33
5-33

CONTENTS
Page
5.6.27
5.6.28
5.6.29
5.6.30
5.6.31
5.6.32
5.7
5.8
APPENDIX A

Set Symbol to Numeric Value
Set Symbol to String Value
Terminate Command File Processing
Test String Symbol
Wait for a Task to Finish Execution
Initiate Parallel Task Execution
TASK NAME REFERENCES
EXAMPLE COMMAND FILE AND ITS EXECUTION

5-33
5-34
5-35
5-36
5-36
5-37
5-37
5-38

MCR AND TKTN MESSAGES

A-1
Index-!

INDEX
TABLES
~rABLE

2-1
2-2
2-3

Special Character Keys and Control Characters
RSX-llM/M-PLUS Peripheral Devices
Permanent Pseudo Devices

2-2
2-9
2-11

SUMMARY OF TECHNICAL CHANGES

This revision of the RSX-llM/M-PLUS MCR Operations Manual contains
changes and additions that document RSX-llM V3.2 and RSX-llM-PLUS
Vl .O ..

TECHNICAL CHANGES COMMON TO RSX-llM AND RSX-llM-PLUS SYSTEMS

The following list contains a brief summary of technical
both operat:ing systems (RSX-llM/M-PLUS) :

changes

for

Revisions to ACNT and SHUTUP

Multiple mounts to insure device access in event of
operation

Support for group global event flags;

Stop-bit task synchronization;

Support for system service messages into error logging files;
MCH SSM command

New Dismount command keywords:

dismount

MCR Flags command

MCR Stop and Unstop commands

/DEV
/USER
/TERM
7.

New features
in the Help command that permit indirect
references to other files and provide the ability to share
text using a synonym feature

New Initialize volume command procedures

Full duplex terminal driver support in Set command

10. New Load command keywords:
/SIZE
/HIGH
11. New Save command keywords:
/MOU
/SFILE
12. New special symbols for the indirect command file processor:
~·

vii

13. New directives to the indirect command file processor:
.BEGIN
• DISABLE QUIET
.ENABLE QUIET,
.ERASE
.END
.EXIT
.OP ENA
.STOP

TECHNICAL CHANGES FOR RSX-llM-PLUS SYSTEMS
The following list contains a brief summary of additional enhancements
to RSX-UM-PLUS:
1.

To perform virtual I/O, the volume must be mounted. The /FOR
keyword for the Mount command permits access to non-Files-11
yolumes

Support to set,
clear,
or display bits in the
register;
SWR command (multiprocessing systems only)

New Allocate command keyword:

switch

/TERM
4.

Additional Dismount command keyword to specify volume
rights following a dismount:

access

/LOCK
5.

New keywords to support regions
multiuser tasks

and

read-only

segments

New task naming convention to support more
terminals, and /TERM switch to avoid conversions

New keyword (/AFF) to support CPU affinity in
systems

multiprocessor

New keyword (/SYNC) for the Install command to
synchronization in multiprocessor systems

support

than

77(8)

task

Note that RSX-llM-PLUS is a new operating system. The preceding list
summarizes only the major extensions of RSX-llM. RSX-llM-PLUS users
should read the complete manual to gain operating system insight.
For
example,
the RSX-llM-PLUS summary of technical changes omits the fact
that the system supports multiple processors;
it is assumed in the
summary that the reader realizes RSX-llM-PLUS provides extensions to
RSX-llM.

viii

PREFAC.E

MANUAL OBJECTIVES

The RSX-llM/M-PLUS MCR Operations Manual provides
information needed
to operate and control an RSX-llM/M-PLUS system.
It supplies an
introduction to the basic concepts of MCR and describes the use of MCR
as the terminal interface with the RSX-llM/M-PLUS operating system.
The manual
identifies two
types
of
users:
privileged
and
nonprivileged.
MCR provides privileged users functions that control
and modify system operation as well as functions that permit program
development and system maintenance.
MCR provides nonprivileged users
only those functions
required for
program development and
local
maintenance.

INTE:RDED AUDIENCE

The RSX-llM/M-PLUS MCR Operations Manual does not attempt to train
operators.
The manual assumes that the
reader
is familiar with
computer operating procedures, both real-time and batch, and that
the
reader has experience operating terminal devices.
An "operator" is broadly defined as anyone who
interfaces directly
with RSX-llM/M-PLUS to perform a task.
This broad definition is used
because of the many and varied settings
in which RSX-llM/M-PLUS
operates;
some
settings
do not
require an operator
in the
conventional sense of the term.
RSX-·118 is a compatible subset system of RSX-llM/M-PLUS.
Thus,
manual can also be used as a reference document for RSX-llS.

this

STRUCTURE OF THE DOCUMENT

Chapter 1 introduces basic RSX-llM/M-PLUS
system interface.

concepts

that

pertain

Chapter 2 describes procedures that you can use to control
the
operation of your terminal,
the execution of your tasks, and (if
privileged) the operation and resources of the system.
The chapter
also describes many system conventions, such as device and task naming
conventions.
Chapter 3 discusses basic concepts of the RSX-llM/M-PLUS
(Files-11).

file

system

Chapter 4 supplies detailed definitions of a 11 the MCR commands.
The
command definitions are in alphabetical order, by privilege category.

Chapter 5 defines
indirect command files and describes the MCR
indirect command file processor.
Directives to the indirect command
file processor appear in alphabetical order.
Appendix A lists, in alphabetical order, the MCR and Task Termination
Notification routine
(TKTN)
messages that can be returned by the
system.
Appendix B lists the subset of MCR commands that makes up
the subset supported by RSX-llS.

Basic

MCR,

ASSOCIATED DOCUMENTS
Other documents related to RSX-llM/M-PLUS are briefly described in the
respective documentation directories.
Although
the RSX-llM/M-PLUS MCR Operations Manual
is
primarily
self-contained,
the
reader should be familiar with system generation
options and features to understand the function of this manual in the
context of RSX-llM/M-PLUS as a whole
(see either the RSX-llM or
RSX-llM-PLUS System Generation and Management Guide).

CONVENTIONS USED IN THIS DOCUMENT
User

(operator)

input appears in red.

Shading distinguishes RSX-llM-PLUS specific concepts and commands.
Shading appears at the page or paragraph level only;
where explicit
distinctions are described in the text, material is not shaded.
Also,
distinct examples
(one from an RSX-llM system and one
from an
RSX-llM-PLUS system) are labeled, but not shaded.
A symbol with a one- to three-character abbreviation indicates that
you press the corresponding key on the terminal, for example, ~ or
@).
The symbol
~TRL/N)
indicates that you must press the key labeled CTRL
while you simultaneously press a no the r key:
for example,
(crRLtz)
@:@~ ,
~TRLt0 •
In examples, these three control key sequences
are shown as AZ, AR, Au, respectively, because that is how the system
echoes them.

CHAPTER 1

INTRODUCTION

This chapter introduces basic RSX-llM/M-PLUS concepts that you should
be familiar with before you attempt to interact with the operating
system.

1.1

TASKS

The fundamental executable unit of an RSX-llM/M-PLUS system is the
task.
Each task is either privileged or nonprivileged.
A privileged
task has special device and memory access rights that a nonprivileged
task
does not have.
Because of their special access
rights,
privileged tasks are potentially hazardous to a running system whereas
nonprivileged tasks are not.
Consult the RSX-llM/M-PLUS Task Builder
Manual for a complete description of the distinctions between and uses
of privileged and nonprivileged tasks.

1.2

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

The relationship between a task and the partition
in which
it runs
depends
on whether the system is mapped or unmapped.
RSX-llM-PLUS
systems are always mapped.
In an unmapped RSX-llM system, a task can
run only
in a
partition that has the same starting address as the
partition for which the task image was created by the Task Builder.
In mapped systems,
however, a task can run in any partition that is
large enough to contain it.
(See
the RSX-llM/M-PLUS Task Builder
Manual for more information about mapped and unmapped systems.)

Partition Types

1.2.1

RSX-llM supports two types of partition in which tasks can execute:
1.

System-controlled

User-controlled

1-1

INTRODUCTION

In a system-controlled partition, the Executive allocates available
space to accommodate as many tasks as possible at any one 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.
A user-controlled partition, however, is exclusively allocated to one
task at a time.
This type of partition is supported by both mapped
!and unmapped systems under RSX-llM.
In both types of partitions, the
resident task out to a disk
available for another task.

Executive can temporarily move a
(checkpoint)
in order to make space

Subpartitions

1.2.2

RSX-llM users can subdivide a user-controlled partition into as many
as
seven
non-overlapping subpartitions.
Like its parent main
partition, a subpartition can contain only one task at a time.
Since
the subpartitions occupy the same physical memory as the main
partition, tasks cannot be simultaneously resident in both the main
partition and one or more subpartitions.
But since each subpartition
can contain a task, up to seven tasks can potentially run in parallel
within a pre-empted main partition.
RSX-llM uses subpartitions to reclaim large storage areas in unmapped
systems.
For example,
when a
large task that requires a main
partition is either no longer active
or
can
be
pre-empted
(checkpointed),
subpartitioning allows the partition space to be used
for a number of smaller tasks.

1.3

MULTIPROGRAMMING

Tasks compete for system resources (including memory) on the basis of
priority and resource availability.
The priority of a task is
determined by a number assigned either when the task is created by the
Task Builder, when it is installed, or when it is run. The number is
in the range 1 to 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 CPU.
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 has access to all the resources it needs.

1.4

TASK OPERATION

You perform four steps to create a task and prepare it for execution:
1.

Enter a program in a supported
editor.

Submit the source code to the
appropriate
(compiler), which produces an object file.

1-2

source

language

through

translator

INTRODUCTION
3.

Submit the object file to the Task Builder, which produces
task-image file.

Finally, issue an MCR command to install the task image
in the system.

file

The output files that result from Steps 1, 2, and 3 are each stored on
a F iles-11 volume (see Sect ion 3 .1).

Installing A Task

1.4.1

When you install a task (by issuing the MCR 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 are the name and length 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 until a request is made for it to be activated.
The concept of dormant and active tasks is important
in a real-time
system.
A dormant task uses very little memory (it requires only an
STD entry and need not be resident);
and 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;
the STD
contains all the parameters the system needs to retrieve the requested
task.
You can activate an installed, dormant task by
issuing the MCR Run
command;
or,
another task can activate the task by issuing an
Executive directive, either RQST$
(Request),
RUN$
(Run),
or SPWN$
(Spawn).
When the Executive receives a request to activate a
a series of ac~ions:
1.

Allocates the necessary resources

Places the task in active competition
with other resident tasks

Brings the task into memory
its partitionl)

for

tas~,

performs

system

resources

(when there is space available in

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

1 The Executive can checkpoint a lower priority, checkpointable
if there is one, to make room for the requested task.
1-3

task,

""·

CHAPTER 2
PROCEDURES AND CONVENTIONS

This chapter describes the procedures that permit you to control the
system from a terminal and discusses operating system conventions.
The topics are:

• How to operate a terminal (Section 2. 1)
• How to manage peripheral devices (Sect ion 2.2)
• How to operate in a multiuser protection system (Sect ion 2. 3)
• How to shut down an RSX-llM/M-PLUS system (Section 2.4)

2.1

2.1.1

TERMINALS

Special and Control Characters

You 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), CR (or RETURN) and RUBOUT (or
DELETE).
In this manual,
the symbols ~, ~, ~), and~'
respectively, denote these keys. A control character is produced when
you type a letter key while pressing CTRL (control). In this manual,
a control character is written (crnL/N) where N is the variable letter
key.
WhE!n you type (crnL;R) ,
(crnL;u) , or
@JE) , the Executive performs the
related function and displays ftR, ftu, or AZ at the issuing terminal.
WhE!n you type (cm;c) , the explicit MCR prompt
(MCR>)
is displayed.
(In an RSX-llM-PLUS system,
(crnL/c)
could, if the terminal is set to
DCL command recognition, display the DCL prompt
(DCL>).) For other
control characters, however, the Executive does not return a display.
Table 2-1 lists all the special character keys and control characters,
and describes the function of each.

2--1

PROCEDURES AND CONVENTIONS

Table 2-1
Special Character Keys and Control Characters
Character

Description
The ~ (Carriage Return) key terminates a
line of
input and advances the carriage or cursor to position
1 on the next line.

The ~key terminates a line of input without moving
the carriage or cursor.
When used to terminate an MCR
command, it suppresses the default MCR prompt.
See
the descriptions of the Open and Run commands (in
Chapter 4), which have special uses for the~ key.
In systems that have generated
the
appropriate
optional facility,
the ~ key can be the first
character
in
an
escape
sequence
(see
the
RSX-llM/M-PLUS I/O Drivers Reference Manual and the
description of the SET /ESCSEQ command).
The~

key deletes the last character typed at the
terminal, and further contiguous characters if the key
is pressed repeatedly.
The first~ typed deletes a
character and prints a backslash (\) followed by a
display of
the
deleted
character.
Subsequent
deletions cause the system to display the deleted
character.
Then, when the operator enters the first
non-~ character,
the system prints a terminating
backslash followed by the character typed.
For example:

--..

----First~
! ---Second~
! !----Third ~

! !! ----First
!

non-~

!1 1

MISTKAE\EAK\AKE
The result is MISTAKE.
On a CRT terminal that supports backspace
(a system
generation option)
and has been declared to be a CRT
by the SET /CRT=t tn:
command, the ~ 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, first press
times to erase E, A and K respectively.
The
result is MIST. Then type AKE to get MISTAKE.

~three

(Note that when~ 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
character disappears.
However, the system has in fact
deleted the last character;
you can type
«TRw~
for
verification.)
(continued on next page)

""''
2-2

PROCEDURES AND CONVENTIONS

Table 2-1 (Cont.)
Special Character Keys and Control Characters
~i

Character

Description
(cTRLtc)
typed either as the first character in the line
or when the terminal is sending data causes MCR to
prompt for command
input with the explicit prompt
MCR>.
(Two special effects of .(cTRLf<c~
are described
below.)

If a task is prompting for
input when the operator
types
(cTRL/c~
followed by a carriage
return,
MCR
displays its explicit prompt, then returns control to
the
interrupted task after receiving a single line of
input.
(An exception arises when an attached task
specifies
an Asynchronous System Trap
(AST)
for
unrequested characters.
In this case,
(crnLtc)
causes
an AST to occur thereby gaining the task's attention
rather than MCR's.)
See Section 2.1.3 for a more
the use of (crnL1'c)
•

detailed

discussion

Special effects:
• If the last character entered at the terminal was
(CTRLts)
,
(crnLt.c)
additionally performs thE~ function
0 f a (cTRL/Q) •
• If a terminal has been set to "hold screen" mode
by the /HOLD option of
the MCR SET command,
~TRLrc)
has the effect of a SET /NOHOLD command;
that is,
(cTRLtiC)
disables hold screen mode.
(This
feature is a system generation option in RSX-llM,
but
is
always
included in an RSX-llM-PLUS
system.)
@~

(or ~)moves the current print position to
the next horizontal tab stop on the line.
The system
establishes tab stops at every eighth
character
position in the line.
(cTRL/1)

(cTRL/K)

causes a vertical tab by performing

four

line

feeds.
causes a
form feed
(but does not: perform
paging).
The action appears on the terminal as eight
line feeds.

(cTRL/L)

(cTRLto)
alternately suppresses and resumes thE~ display
of output at the terminal.
The effect of
«rnLt0
depends on the state of the terminal when you type the
character.

(continued on next page)

2-3

PROCEDURES AND CONVENTIONS

Table 2-1 (Cont.)
Special Character Keys and Control Characters
Character
~~

(Cont.)

Description
The system controls the function of «rRL/0 internally
by means of a single bit associated with the terminal
called the disable output bit. When the bit is set,
the system disables output to the terminal. When the
bit is cleared, the system resumes the output display.
Initially, the bit is clear; the first
(cm10)
typed
causes the bit to be set. The next «rnL10 typed then
clears it again. Thus the net effect of successive
(crnL10)
characters is to alternately stop and start the
display of output at the terminal.
The
system
discards characters directed to a terminal that has
disabled the display of its output.
If more than one task is sending output to a terminal,
it is essential that
«rnL10
affect only the task
delivering output at the time you type
(cm10).
The
system handles this problem as follows:
The disable bit is unconditionally
attached terminals at:

cleared

for

• The issuance of an Attach QIO directive
• The issuance of a Detach QIO directive
• The issuance of a Write QIO directive
the "clear CTRL/O" subfunction bit set

that

has

• A request for input
• The arrival of unsolicited input
For unattached terminals, the bit is also cleared each
time a task initiates a request to output to the
te rmi na 1.
Given these conditions for clearing the disable bit,
and the fact that entering &rnL10 always complements
the bit,
·(nRL/o)
affects the entering terminal as
fol lows:
At an attached terminal, you can stop output by typing
•
The
interrupted output stream will be
discarded until the next:

(crRL/o)

• Detach
• Solicited input
• Unsolicited input
•

(crRL/O)

At unattached terminals,
(crnL10)
stops output only for
the current buffer, since, at the next I/O initiation,
the system always clears the disable output bit for
unattached terminals.
(continued on next page)
2-4

PROCEDURES AND CONVENTIONS

Table 2-1 (Cont.)
Special Character Keys and Control Characters
Character

Description
typed after a ~rnL!s) resumes output suspended
by the previous
€rnL~ •
(This feature is a system
generation option in RSX-llM systems,
but is always
included in RSX-llM-PLUS systems.)
~TRLl0

Typing «TRL/~ before typing a line terminator 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. If the
current line is empty,
«rnL/~
performs a carriage
return and line feed.
For example:
MISTKAE\EAK\AKE AR
MISTAKE
(This feature is a system generation option in RSX-llM
systems,
but is always included in RSX-llM-PLUS
systems.)
Typing (CTRL!s) while the terminal is receiving output
suspends additional output until you type ~TRLt0 or
(cTRLtc)

•

The suspended output is merely

delayed,

not

lost
(see the description of
(cTRLto) ) •
Thi~ combined
functions of (cTRL/Q) and
(cTRL/s)
are convenient when
using a CRT terminal.
(This feature is a system
generation option.)
Typing ~TRLt0 before typing a line terminator deletes
the current line. The system responds with a carriage
return and line-feed so that the line can be retyped.
«rnLt0
is echoed as "U.
Typing (cTRLtx) clears the terminal type-ahead buffer.
The
type-ahead
buffer
temporarily stores input
characters until the terminal driver can pass them to
the task.
When the type-ahead buffer is full, input
characters are not accepted; type «rnLt~ to clear the
buffer.
@:~

2.1.2

Typing «rnL/~
indicates end-of-file. It is used to
indicate to system tasks such as MAC, PIP, and TKB
that the user is finished and the task may exit.
(cTRLtz)
is echoed as "z .

Terminal Characteristics

In HSX-llM/M-PLUS, a number of terminals can operate concurrently;
each terminal operates independently of others in the system so that
each can run one or more different tasks. Thus the PIP utility and
the MACR0-11 Assembler, for example, can run from different terminals
at the same time, as long as the required memory is available.

2-5

PROCEDURES AND CONVENTIONS
If an RSX-llM/M-PLUS system supports multiuser protection
(a system
generation option), each user must log onto a terminal before issuing
further MCR or task commands (other than the Help command).
Section
2.3.l describes how to log on and off a terminal in a multiuser
protection system.

2.1.2.l Terminal Privilege - Privileged commands can only be
issued
at a privileged terminal.
In RSX-llM/M-PLUS systems that support
multiuser protection,
individual users are either privileged or
nonprivileged.
When a user logs on
(see Section 2.3.1.1), the
terminal assumes the privilege status of the user logging on.
In
other
RSX-llM/M-PLUS systems,
a terminal's privilege status
is
determined initially at system generation. Subsequently, you can use
the MCR Set command
(see Section 4.5) at a privileged terminal to
modify the privilege status of any other terminal connected to the
system.
CAUTION
Users must take great care when more
than
one
terminal
is
privileged.
Privileged commands can destructively
interfere with system operation and with
each other.

2.1.2.2 Attached and Unattached Terminals - A terminal is attached
when all its input and its output are directed to or from a task other
than MCR.
For example, when you invoke a task
(such as the text
editor EDI),
the task usually attaches to the terminal so that no
other task can use the terminal for I/O. When you wish to exit
(for
example,
by
typing
(crRL19), the task is detached from the terminal,
which normally directs subsequent input to MCR.
Since an attached terminal directs all input to the dedicated task,
you must either exit from the task or gain MCR's attention before
attempting to communicate with MCR.
(See Section 2.1.3
for
a
description
of
«mLtc)
as a means of
temporarily gaining MCRs
attention.)

~!
2.1.2.3 Slave Terminals - You can dedicate a terminal exclusively to
one or more tasks by issuing an MCR 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 ~TRL/c) , but excepting
~TRLl0,
(CTRi:1~,
and
~TRL/s).
Attached terminals accept certain forms
of
unsolicited input.
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 the terminal.
Slave terminals are often dedicated to real-time applications.

""'i
2-6

PROCEDURES AND CONVENTIONS

2.1.3

Input Prompts

There are three prompts indicating that
input:
1.

The default prompt (>)

The task prompt (TSK>)

The MCR prompt (MCR>)

terminal

waiting

for

2.1.3.1 The Default Prompt - A default prompt
(the character > in
position 1 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 normally 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.1.3.2 below.) When MCR receives unsolicited input,
it identifies, analyzes, and responds appropriately to the input.
Section 4.2 explains how MCR responds to commands.

2.1.3.2 The Task Prompt - When MCR activates
command, the task normally prompts:

task

service

tsk>
where tsk is a 3-character task name.
(All DIGITAL system tasks
identify themselves by a 3-character prompt, and user tasks should do
the same.)
As long as a prompting task has attached to a terminal,
the task
receives all solicited input entered at the terminal until the task
detaches.
(The terminal discards all
unsolicited
input.)
An
unattached task, however, encounters the possibility that another task
could solicit input from the terminal before the operator types a
response to the prompt. The intervening task would then receive the
input intended for the task that displayed the prompt. To avoid this
situation, every task intending to solicit input from a terminal
should perform the following sequence:
1.

Attach to the terminal

Prompt with a properly formatted identifier (that is, tsk>)

3•

So 1 i c i t

input ( i s sue a read request )

2.1.3.3 The MCR Prompt - A terminal always sends
typed in response to the explicit prompt:
MCR>
You can invoke the explicit MCR prompt by typing:

or (as shown in the second case described below):

2-7

MCR

any

input

PROCEDURES AND CONVENTIONS
( @Ohl©
does not invoke the MCR prompt in a special case described in
the second note below.
In addition, the description of (cTRuc) in
Table 2-1 describes two further situations in which
(cTRu0
does not
obtain the MCR> prompt.)

The following notes explain various uses of the explicit MCR prompt:
•

When a terminal is displaying the default prompt (see Section
2.1.3.1),
there is no guarantee that input typed in response
will be directed to MCR. To ensure that MCR does receive the
input,
press
(crRu9
to invoke the MCR prompt. After MCR
processes the single line of input,l the terminal resumes
display of the default prompt.

•

When a terminal is displaying a task prompt (tsk>),
can invoke MCR by typing

the

user

After MCR processes the single line of inputl received,
terminal again displays the original task prompt.

the

NOTE
If an attached task specifies an AST on receiving
unsolicited input,
(crRLtc)
causes an AST to occur,
thereby gaining the task's attention rather than
MCR's. Consequently, the MCR prompt does not appear.
•

2.2

When any terminal is receiving output from a task, you can
interrupt the output by typing (crRL/~ • At the completion of
the current I/O operation, the terminal displays the explicit
MCR prompt.
After MCR processes the single line of inputl
directed to it, the system resumes the interrupted output.

DEVICES

A primary function of the operating system is to manage all connected
peripheral devices and thus maintain efficient system performance.
This section provides basic information needed to manage peripheral
devices.
(Devices within multiuser protection systems are subject to
a special set of MCR functions, described in Section 2.3.2.)
During system generation,
the operator explicitly describes all
peripheral devices attached to the system (see the RSX-llM or
RSX-llM-PLUS System Generation and Management Guide).
The single line of input received by MCR may in fact invoke a task
that proceeds to issue its own prompt. The prompt of the invoked task
can, however, also be answered by a (crRL/c) to invoke the MCR prompt.
You can then request another task that issues its own prompt, and so
on ..
1

2-8

PROCEDURES AND CONVENTIONS
Each device has a unique identifier.
The identifier consists of two
ASCII characters, which form a logical device name, and an optional 1or 2-digit octal unit number, followed by a colon (:).
If you omit
the optional octal unit number, the system defaults to unit O.
Peripheral devices are the actual hardware elements which make up the
computer
system.
Table 2-2 lists the supported RSX-llM/M-PLUS
peripheral devices and their physical device
names.
Hardware
controllers
appear in parentheses.
An asterisk (*) precedes a device
that is supported in RSX-llM systems but not in RSX-llM-PLUS systems.
Pseudo devices must always refer to a
real physical device.
They
declare
this association through the MCR commands Assign or Redirect.
Pseudo devices provide a
shorthand method for
referencing real
physical devices
(for example, the pseudo device name SY::
refers to
the system disk) and thus simplify the default structure.
Table
2-3
lists the HSX-llM/M-PLUS pseudo devices.
Table 2-2
RSX-llM/M-PLUS Peripheral Devices
Device-unit

Peripheral Devices
(ADOl-D)

ADnn:

(AFCll)

AFnn:

*Laboratory Peripheral System (ARll)

ARnn:

Card Reader

CRnn:

*Analog-to-Digital Converter

(CRll)

Cassette

(TAll)

CTnn:

DECtape

(TCll)

DTnn:

DEC tape I I

DDnn:

(TU 5 8 )

Disks
RP04/05/06 disk packs
RF disks

(RH11/RH70/RP04/RP05/RP06)

DBnn:
DFnn:

(RFll)

RK05 cartridge disks

DKnn:

(RKll)

RK06/07 cartridge disks

(RK611)

DMnn:

(RLll)

DLnn:

RM02/03 disks

(RH11/RM02, RH70/RM03)

DRnn:

RP02/03 disks

(RPll)

DPnn:

RS03/04 disks

(RH11/RH70/RS03/RS04)

DSnn:

RLOl cartridge disks

RXO.l floppy disk

(RXll)

DXnn:

RX02 floppy disk

(RX211)

DYnn:
(continued on next page)

2-9

PROCEDURES AND CONVENTIONS
Table 2-2 (Cont.)
RSX-llM/M-PLUS Peripheral Devices
Device-unit

Peripheral Devices
*Graphics Display Processor and Scope (VT11/VS60)

GRnn:

*Industrial Control System Local

ICnn:

and Remote

(ICS/ICR-11)

*Industrial Control Subsystem (DSSll/DRSll)

ISnn:

Laboratory Peripheral Accelerator

LAnn:

(LPAll-K)

*Laboratory Peripheral System (LPSll)

LSnn:

Line Printer (LAll/LSll/LPll/LVll)

LPnn:

Ma gt apes
TU45/TU16/TE16/TU77 (RH11/RH70/TM02/TM03)

MMnn:

TS03/TU10/TE10 (TMll/TMAll/TMBll)

MTnn:

TS04 (TSll)

MSnn:

Paper Tape Punch

(PCll)

PPnn:

Paper Tape Reader

(PCll/PRll)

PRnn:

Terminal (DLll/DHll/DJll/DZll)

TTnn:

Parallel Interprocessor Link
[RSX-llM-PLUS systems]

(PCL-118)

TXnn:/RXnn:
*Parallel Line Interface (DAll-B)

XBnn:

*Asynchronous Line Interface

XLnn:

Interprocessor Link

(DLll-E)

(DMC)

XMnn:

*Synchronous Line Interface (DPll)

XPnn:

(DQl 1)

XQnn:

(DUPll)

XWnn:

(DUll)

XUnn:

*Universal Digital Controller (UDCll)

2-10

UDnn:

PROCEDURES AND CONVENTIONS
Table 2-3
Permanent Pseudo Devices

~·

Pseudo Device

Name

Console Listing

CL:

Console Output

CO:

System Default Device

LB:

Pseudo Input Terminal

TI:

User Default Device

SY:

Null Device

NL:

Virtual Terminal

(RSX-llM-PLUS systems)

VT:

A task performs I/O on_ logical units
identified by numbers,
called
Logical Unit Numbers
(LUNs),
rather than on specific device units.
Either the programmer or a user assigns each LUN to a specific device
before the task actively uses the LUN.
A LUN assignment can occur at
one of the three points:
1.

At task build

From within the task at run time via an Executive directive

Via an MCR command
(Reassign)
after
installed and while it is dormant

the

task

has

been

Ref er to the RSX-llM/M-PLUS I/O Drivers Reference Manual or the
appropriate language User's Guide for more information about logical
units.

2.2.1

Pseudo Devices

A pseudo device is a device unit name that does not correspond to a
real device until the pseudo device has been redirected.
Every task
in the system, including a system task, needs to communicate with one
or more of the following pseudo devices:
CO:

Console output device

CL:

Console listing device

LB:

System library device

TI:

Terminal input/output device

SY:

User's system device

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
device CL:
has been redirected to.
You can redirect CL:
to any
appropriate device (a line printer or a terminal, for example) without
affecting the task's execution.

2-11

PROCEDURES AND CONVENTIONS

A pseudo device redirected to a terminal assumes the privilege status
of the terminal to which it is redirected. If TT:
is a privileged
terminal, 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 CO:
to the main operator's
terminal, and CL:
to the line printer. The system automatically
redirects TI:, the most commonly used pseudo device, depending on how
a task has been activated:
you issue the MCR
• When
immediately, the system

Run command to activate a task
redirects the TI: for that task to

your terminal.
•

If,
in a task, the Executive directive RQST$ or SPWN$
activates another task, that task's TI: defaults to the TI:
of the task that issued the directive.

If the Executive enters a task into a clock queue
• activation
a specified interval,
after
the task's

for
TI:
defaults to co:.
(Both the MCR Run command and the Executive
directive RUN$ allow task activation at a· specified interval
after the command or directive has been issued.)

2.2.2

The Null Device

Program testing often requires a data source and a data sink. A data
source is a device that you can use as a source of unlimited data;
and a data sink is a device to which you can send unlimited amounts of
data.
These devices are testing mechanisms only, and are not real
devices. You can use the null device to serve as both data source and
sink when you test programs. For example, while testing a program
that normally generates large amounts of printout, you can redirect or
assign the appropriate LUN to NL:.
The system then discards the
output directed to NL:. When a task reads from NL:, the null device
returns the code for end of file (IE.EOF); when a task writes to NL:,
the null device returns the code indicating success (IS.SUC).

2.2.3

Logical Devices

Logical device names provide another means by which tasks can maintain
device independence.
(This feature is a system generation option in
RSX-llM systems, but is always included in RSX-llM-PLUS systems.) A
logical device name has the same syntax as a real device unit;
it
consists of a 2-character ASCII name (alphabetic) and an optional 1or
2-digit octal unit number,
followed by a colon
(:).
The
2-character name can either be equivalent to a standard RSX-llM/M-PLUS
device name
(for example, DK:), or it can consist of two letters
picked at random (for example, XY:).
Before you run a task that
refers to a logical device rather than a real device unit, you must
issue the MCR Assign command to associate the task's logical device
name with a real device unit (see Section 4.5).

2-12

PROCEDURES AND CONVENTIONS
Thn~e

types of logical device assignments
systems:
global, local, and login.

exist

RSX-llM/M-PLUS

•

Global apply to all tasks running in the system.

•

Local apply only to tasks initiated from the terminal used to
make
the assignments.
Local assignments override conflicting
global and login assignments;
and the same logical device
name may be locally assigned to different devices by different
terminals.

•

Login apply to systems
that support multiuser protection.
When a user
issues
the MCR Hello command to log into the
system, the system automatically establishes one or more login
logical device assignments.
Login assignments override global
assignments, but local assignments made from the
terminal
override both login and global assignments.
If a local assignment overrides an assignment established at
login,
the system reinstates
the login assignment when the
user deassigns the local logical device name.

·'-""

The login logical device assignments remain
in effect
until
the user logs
off or until a privileged terminal deassigns
them.
The Executive sets up a logical device table that records all
logical
device assignments and notes whether each assignment is local, login
or global.
The Executive then searches this table every time a
task
refers
to a
device.
A logical name found in the table receives
precedence over a physical device-unit having the same identifier.

2.3

MULTIUSER PROTECTION FUNCTIONS

Multiuser protection,
a
system
generation
option,
allows
an
RSX-llM/M-PLUS installation to monitor and control individual users of
the system.

2.3.1

Logging On And Off A Terminal

Each user must log onto a terminal before the system accepts
further
MCR or task commands, other than the MCR Help commands.
Depending on
the user's User Identification Code (UIC), the terminal
logged onto
becomes privileged or nonprivileged.
After completing a session, log off the terminal.
The process of
logging on and off a terminal enables the system to keep accounting
information about each user.
The following information is printed on the console terminal following
each log on/off in the format
time
time

[g' m]
TTnn:

TTnn:

The MCR commands that log a user on and off a terminal are
Bye~.

2-13

Hello

and

PROCEDURES AND CONVENTIONS

2.3.1.l The Hello Command - The parameters to the Hello command are
the user's UIC (or last name) and a password. The standard format for
a UIC specifier is [g,m], where g and mare octal numbers from l
to
377 that represent group and member numbers, respectively.
The Hello
command allows several UIC formats (see Section 4.5).
A privileged
user has a group number less than or equal to 10 octal.
Each UIC has
an associated 1- to 6-character alphanumeric string or password that
guards against unauthorized access to the system.
No one can
successfully log onto a terminal without supplying the correct
password for the specified UIC (or last name).
For example:
HELLO ~
ACCOUNT OR NAME:

[30113G5J t8.fil)

PASSWORD:

Note that the Hello command prompts for its parameters when you press
~ after each element of the command string.
Alternatively, you can
type the entire command string on one line, as follows:
HELLO

[30113G5J

/BOB t8.U)

where BOB (preceded by a mandatory slash)
is the password for
the
specified UIC.
(The slash is required only when the password is on
the same line as the UIC or last name.) When the user types a password
in response to the prompt PASSWORD:, the system does not display the
typed characters.
You can also type the command in a mixed format, supplying one element
of the string on one line and prompting for the other. The procedure
shown in the following example ensures that the system suppresses the
password:
HELLO AMBER t8.ITJ
PASSWORD: 00)

Note that this example of the Hello command specifies the
from which the system determines the UIC.

last

name,

After you log onto a terminal, the system automatically assigns the
logical name SY:
to the user's system disk (a login logical device
assignment) and then searches the corresponding UFD for a file
LOGIN.CMD.
If found, the file is sent to the indirect processor (see
Chapter 5).
This is especially useful when you issue the same
commands after each log on.
For example,
if the user-created
LOGIN.CMD file contained
SET /LOWER=TI:
SET /BUF=TI:80.
SET /CRT=TI:
the following would be displayed each time the user logged
RSX-llM system:

2-14

PROCEDURES AND CONVENTIONS
>HEL AMBER
PASSWORD:
RSX-11M BL2G MULTI-USER SYSTEM
GOOD AFTERNOON
19-FEB-79 14:08 LOGGED ON TERMINAL TT20:
>@LOGIN,CMD
>SET /LOWER=TI:
>SET /BUF=TI:BO,
>SET /CRT=TI:
>@ <EDF>

If the group number is less than 11, the terminal becomes privileged;
if
the
group number is 11 or greater,
the terminal assumes
nonprivileged status (see Section 2.1.2.1).

2.3.1.2 The Bye Command - When you complete a session at the terminal
issue the Bye command to log off. This command has no parameters;
it
simply instructs the system to terminate the session.
The system
deletes all local and login logical device assignments, dismounts all
mounted private devices (see Section 2.3.2), deallocates all private
devices,
aborts all active nonprivileged tasks requested from the
terminal, displays a termination message, and prevents further use of
the terminal until another user logs on.
Example:
>BYE

>
HAVE A GOOD AFTERNOON
19-FEB-79 2:15 TT5: LOGGED OFF

2-15

PROCEDURES AND CONVENTIONS

Public, Private, and Unowned Devices

2.3.2

Systems
that
support
multiuser
protection
impose
special
characteristics on devices. Devices are 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 an MCR Set command keyword.
If a privileged user
mounts a volume on a public device, all system users can
access files on the volume.
However, since a subsequent
Dismount command inhibits further file access, each user that
accesses the volume should issue a Mount command.
A public
device cannot be allocated.

•

A private device is a device that a user has allocated
(by
means of the MCR command Allocate). Only privileged users and
the owner 0£ a private device can access the device for use
within the Files-11 file system (see Section 3.1). 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 system users can
issue subsequent Mount commands and thus access the volume.
Note that other users cannot access the volume until they
issue a Mount command.
Nonprivileged users can only allocate or mount a volume on an
unowned device. Privileged users can allocate, set public, or
mount a volume on an unowned device.

A privileged user can designate any device in the system as a public
device.
The devices most commonly made public are the line printer
and the system disk. See Section 4.5 for a description of the Set
command /PUB keyword that makes a device public.
The MCR Allocate command makes an unowned device the private property
of the user issuing the command. Device allocation 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 Section 4.5) 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 no matter who
owns it.
Nonprivileged users can deallocate only their own private
devices. When a user logs off, the system automatically dismounts and
deallocates any private devices belonging to that user. To encourage
efficient use of system resources, however, users should deallocate
devices as soon as the devices are no longer needed.
·'.:"·.:.:··::·'.

Mf~~q§ ...~xs£~Jii, does not p~rJTIJt: ahY:
e'il9tHIJ1~9.~ ..........!.??.· c::lcc;es"§· a . . '79.JPIJl~ ...9!1. ~·

J.J§ .. ~yst~rn,.10u mus~ (frst: }'!3~'-:1~ .~r1. ·~GB

~ .• JJB~ £oriri(l~~~9. ,Qr .As. . . .ot:h~r . t:t1~n r.~~·~.~fa .•. . . . .
.~>yg..lH.Iq~ ·.·~·~ fq,r:~.Jgn · · · .. (ll"ld ....·····•e.i.the r ..·. ~.lfi:t:.ia~J~.g···
· ~ ·Sl,l~t:9rni . . ~. C:·~ 1:9.·.•. s~.EV,. i.C:.~. apcgss . . ·.·r~qµ~5:t!3• .·.·.· •.· .JJAi

.Ift9 .t~Cil.l:ftf:!lT!~BE~ of. the Mount or Dismount commands.~·
RSX-:-llM-PtUSpermit$ i()§~p~J. t/q.J
., .•..
2-16

PROCEDURES AND CONVENTIONS
RSX-llM grants specific tasks, such as INI, DSC, BAD, and FLX, access
to unmounted volumes. See the Mount and Dismount command descriptions
in Chapter 4.

2.3.3

The Account File Maintenance Program (ACNT)

RSX-·llM/M-PLUS provides an Account File Maintenance Program (ACNT) for
the creation and maintenance of a multiuser account file. Whenever a
user tries to log onto a terminal, the system checks the Hello command
parameters against the account file to determine whether or not the
user should be allowed access to the system (see Section 2.3.1).
The
account file describes all the UICs that have been authorized for use
within the multiuser protection system.
One UIC can have several
users, each user having his or her own password.
ACNT is an interactive program that allows a privileged user to:
•

Create the account file

•

Add new accounts to the file

•

Examine individual account entries

•

Modify individual account entries

•

List all the account entries in the file

•

Delete an account from the file

•

Sort the account file

When activated, ACNT lists the options and requests you to select one.
Then enter the first letter of the verb that identifies the desired
option (C for Create, A for Add, and so on). The program responds by
requesting further input or by displaying information according to the
option selected.
Each account
entry
includes
the
following
inf c::>rmation:
•

UIC, which serves as an account number

•

Password

•

User's system devicel

•

First name

•

Last name

•

Date and time of the user's most recent login

•

The number of times that the user has logged into the system

1 When a user logs in successfully,
logical name SY:
to this device.

2-17

the

system

assigns

the

PROCEDURES AND CONVENTIONS

A nonprivileged user
entry description of

(see

The legal characters for user names are A-Z, 0-9, "$", ""',
",", and
"!".
Lower-case characters are converted to upper-case equivalents.
Any ASCII character greater than 40 {octal) is valid for a password.

2.3.3.1 Creating the Account File - A multiuser system cannot have
more than one account file at a
time.
Create the initial file
immediately after system generation to allow normal use of the system.
You should run ACNT under a privileged UIC (uic [1,2] is used by
convention) to prevent nonprivileged users from accessing the account
file.
The
program's create function allocates a
file
called
[O,O]RSXll.SYS and sets the file's protection to [RWED,RWED,,].
This
protection allows file access to privileged users and privileged tasks
only.
A privileged user may copy and optionally extend the account
file
(RSXll.SYS)
using PIP. The new copy will receive the RSX-llM/M-PLUS
default file protection, which includes read access for the world.
The system manager should, therefore, immediately run ACNT.
ACNT will
detect the incorrect protection codes, mark as free any extended area,
resort the file,
and
restore proper protection.
This prevents
unauthorized access to ACNT.
The following example shows how to create the account file:
>RUN $ACNT
* ACCOUNT FILE MAINTENANCE PROGRAM *
OPTIONS ARE: A - ADO, C - CREATE FILE, D - DELETE, E - EXAMINE,
L - LIST, M - MODIFY, S - SORT, CTRL/Z - EXIT
ENTER OPTION: C ~
ENTER MM( I MUM NUMBER OF ACCOUNTS: n, ~
Enter a decimal number (n.) to specify the maximum number of account
entries to be listed in the file.
The system then creates an account
file large enough to contain that number of entries.
If the account
file
proves
to be insufficient, additional account file space can be
obtained by copying the file using PIP and specifying the /BL switch.
Note that the protection precautions listed above apply in this case.

2.3.3.2 Adding Account Entries - After you enter the
of accounts, ACNT prompts

maximum

number

ENTER ACCOUNT DR <ESC> FOR OPTIONS ( N,N ):
In this way, ACNT allows you to start adding accounts to the file
immediately after
its creation.
To respond, enter either the octal
group and member numbers of a UIC, separated by a comma (that is g,m),
or the ~key to request a list of all the available options.
Each
new account is entered and the file
is automatically maintained in
sorted order by UIC.

2-18

""' •-.

PROCEDURES AND CONVENTIONS

The following example starts up ACNT and then shows how to add account
entries to the file.
>RUN $ACNT
* ACCOUNT FILE MAINTENANCE PROGRAM *
0 P T I 0 f\I S ARE : A - ADD , C - CREAT E F I LE , D - DE LET E , E - E}-(~IM I NE ,
L - LIST, M - MODIFY, S - SORT, CTRL/Z - EXIT
ENTER OPTION: A 00)
ENTER ACCOUNT OR <ESC> FOR OPTIONS < N,N >: 200,202 00)
PASSWORD < < =G CHARS, >: BB 00)
DEFAULT SYSTEM DEl,! I CE < DDU >: SY 00)
FIRST NAME < < = 12 CHARS, ) : BOB 00)
LAST NAME < < =14 CHARS, ) : AMBER ~Il
UFO SY00:[200t202J

>
ENTER ACCOUNT OR <ESC> FOR OPTIONS

N,N ): 2001203

00)

ACNT prompts for each required item of information after you enter the
UIC group and member numbers.
The prompts include the number of
characters permitted in the password, the first name,
and the last
name.
The default system device prompt requests a device name and
unit number (optional if 0).
After receiving the last name, ACNT
issues an MCR UFD command to
create a directory for
the new account on the default system disk.
ACNT then repeats the prompt:
ENTER ACCOUNT OR <ESC> FOR OPTIONS

N1N >:

You can either continue to add account entries, choose another option,
or terminate ACNT.

2.3.3.3 Examining Account Entries - The Examine option
displays
details about
individual account entries. After ACNT displays the
options and the prompt
ENTER OPTION:

enter E, and ACNT responds by displaying
ENTER ACCOUNT OR <ESC> FOR OPTIONS

NtN ):

Then type the UIC numbers of the account to be examined.

For example:

OPTIONS ARE: A - ADD1 C - CREATE FILE1 D - DELETE1 E - EXAMINE1
L - LIST1 M - MODIFY1 S - SORT1 CTRL/Z - EXIT
ENTER OPTION: E 00)
ENTER ACCOUNT OR <ESC> FOR OPTIONS
N 1N ) : 200 1202 00)
[ 200 1202 J
BB
BOB
AMBER
SYOO:
2/1/79 19:44:48 00001
ENTER ACCOUNT OR <ESC> FOR OPTIONS

NtN ):

ACNT displays two lines of information about each entry corresponding
to the specified account.
The first line shows, from left to right,
the account UIC, password, first name, last name, and default system
device.
The second line consists of the date and time of the
account's last login, followed by the number of times a user has
logged into the system with this account since the account file was
created. After displaying all the entries for the specified UIC,
the
program prompts for another account or ~ for a list of ·options.
2-19

PROCEDURES AND CONVENTIONS
If ACNT receives another account number,
it displays entry details
about the specified UIC;
ACNT remains in Examine mode until you type
~to request a list of options.

2.3.3.4 Modifying Account Entries - The Modify option allows
a
privileged user to change the password, default system device, first
name and/or last name of an account~
In an RSX-llM-PLUS system,
the
Modify option also allows you to change the session 1dentifier and the
account number.
(A nonprivileged user can run the ACNT program to
change the password of his or her own account;
see Section 2.3.3.8.)
For example:
OPTIONS ARE: A - ADD1 C - CREATE FILE, D - DELETE, E - EXAMINE,
L - LIST, M - MODIFY, S - SORT, CTRL/Z - EXIT
ENTER OPTION: M ID
ENTER ACCOUNT OR < ESC > FOR OPTIONS ( N 'N ) : 200, 202 ID
[2001202] BB BOB AMBER LBOO:
2/1/78 18:44:46
00001
THIS ENTRY? [Y/NJ: YID
TYPE <ESC> TO LEAVE ENTRY UNCHANGED
PASSWORD ( <=G CHARS, ) : ZUK ID
DEFAULT SYSTEM DEl,J I CE ( DDU ) : DB 1 ID
UFD DB01:[2001202J

FIRST NAME ( <=12 CHARS. ) :
®:Q
L.AST NAME ( < = 14 CHARS
~
ENTER ACCOUNT OR <ESC> FOR OPTIONS ( N1N ):
I

)

After you specify the account to be modified, the program displays the
account entry and asks for verification. Type either Y (Yes) or N
(No) to indicate that the correct account was or was not specified.
If ACNT receives a negative reply, it searches the file for another
entry with the same UIC.
For example:
ENTER OPTION: M ID
ENTER ACCOUNT OR <ESC> FOR OPTIONS
[2001202J BOB AMBER LBOO:
02/12/78 10:36:25 00037
THIS ENTRY? CY/NJ: N ID
C2001202J BOB REBMA LBOO:
02/12/78 8~23:25 00145
THIS ENTRY ? [Y/NJ Y

N1N ): 2001202 ID

WHEN ACNT receives a positive reply, it prompts for the entry details,
requests ~ in response to an
item not to be changed, and then
prompts for each changeable account item.
In the first Modify example
above,
the user changes the account's password to ZUK and the default
system device to DB!:. The program issues an MCR UFD command to
create a directory
for the account on the new system disk, and then
prompts for the remaining items (first and last names).
An examination of the
[2001202]

[200,202] account might now read:

BOB
ZUK
2/1/78 18:44:46

AMBER

DBO 1 ::

00001

You can either continue in Modify mode by entering another account, or
type ~to obtain a list of opt ions.

2-20

PROCEDURES AND CONVENTIONS

2.3.3.5 Listing All Account Entries - The List option either displays
on the user's terminal or spools to the line printer all the accounts
described in the account file.
For example:
OPTIONS ARE: A - ADD1 C - CREATE FILE, D - DELETE, E - EXAMINE,
L - LIST, M - MODIFY, S - SORT, CTRL/Z - EXIT
ENTER OPTION: L IBm
PRINT PASSWORDS? [Y/NJ: N IBm
ALL ACCOUNTS? [Y/NJ: N IBm
ENTER GROUP NUMBER <N>: 7 IBm
ENTER T - TERMINAL OR L - SPOOLED LINEPRINTER: T IBm
[0071001]
BOB
AMBER
SYOO:
1/30/79
9:52:21
01985
[0071002]
BOB
MB ERA
LBOO:
1 /29/79
11: 54: G
01391
BOB
BERM A
LBOO:
[0071003]3
1/30/79
13: 8:51
00195
SYOO~
BOB
Ef~BMA
[007 1004J
2/1179
9:42: 3
008El9
[0071005]
BOB
r~EBMA
f3YOO:
01469
211179
9:48:44

In this example, ACNT lists the entries of a specific group in the
file
(without displaying the passwords) at the terminal. The program
then displays all its options and requests a choice.

2.3.3.6 Sorting the Account File - The Sort option sorts the
file in ascending order by UIC.
For example:

account

DELETE, E - EXAMINE,
OPTIONS ARE: A - ADD1 C - CREATE FILE, D
E)< IT
L - LISTt M - MODIFY, S - SORTt CTRL/Z
ENTER OPTION: S IBm

When the sort is complete, ACNT displays
OPTIONS ARE: A - ADD1 C - CREATE FILE, D
DELETE, E - EXAMINE,
L - LISTt M - MODIFY, S - SORT, CTRL/Z
EXIT
ENTER OPTION:

and prompts for another option.

2.3.3.7 Deleting Account Entries - The Delete
individual accounts from the file.
For example:

option

eliminates

OPTIONS ARE: A - ADD1 C - CREATE FILE1 D - DELETE, E - EXAMINE,
L - LIST, M - MODIFY, S - SORT, CTRL/Z - EXIT
ENTER ()PT ION: D IBm
ENTER ?~CCOUNT DR <ESC> FOR OPTIONS ( N tN ) : 200 1202 IBm
[2001202] BOB AMBER LBOO:
02/12/79 10:38:25 00037
THIS ENTRY? CY/NJ: N IBm
[2001202] BOB REBMA LBOO:
02/12/79 G:23:25 00145
THIS ENTRY ? [Y/NJ Y IBm
DELETE UFO AND FILES? CY/NJ: YID
PIP DB01:[2001202J*•*;*/DE
>PIP DB01:[010J200202.DIR;*/DE

>
ENTER ACCOUNT OR <ESC> FOR OPTIONS ( N1N ) :

2-21

PROCEDURES AND CONVENTIONS
After you specify the account to be deleted, ACNT displays the account
entry and requests a Y (yes) or N (no) reply for verification. A
negative reply causes ACNT to search for another entry with the same
UIC.
If the
reply
is Y for Yes, the program asks if you want to
delete the account's UFD and other files.
Another positive
reply
produces Peripheral Interchange Program (PIP) commands to delete these
files.
If you enter N in response to the deletion query,
the
account's files and UFD are left intact.
Remain in Delete mode by
entering another account, or type ~for the option list.

2~3.3.8
Nonprivileged Account Modifications - A nonprivileged user
can run the ACNT program to change his or her password;
all other
ACNT options are privileged.
For example:

>RUN ACNT

* ACCOUNT FILE MAINTENANCE PROGRAM *
PASSWORD ( < =G CHARS, ) : BOB (flITl
TYPE <ESC> TO LEAVE ENTRY UNCHANGED
PASSWORD ( <=G CHARS, ) : PSWRD (flITl
OPERATION COMPLETE
When a nonprivileged user runs the ACNT program, it identifies
itself
and immediately prompts for the password of the user currently logged
onto the terminal.
It then searches the account file for
the entry
that matches the UIC and password.
When ACNT locates the correct
entry, it instructs the user to type ~to leave an entry unchanged.
ACNT then prompts for
the new password and changes it whenever the
user types characters other than~ in response to the prompt.
The
prompt shows the maximum character length allowed for a password.
ACNT displays OPERATION COMPLETE and automatically exits after the
user terminates the wrong password in response to the initial query.
To enable this nonprivileged option, the ACNT task must already be
installed in the system. A nonprivileged user cannot request ACNT by
the install-run-remove option of the Run command because ACNT
is a
privileged task.

2.3.3.9 ACNT Error Messages - The ACNT program returns the
error messages:

following

ACNT -- ACCOUNT ALREADY EXISTS

Explanation:
UIC and
file.

The user attempted to add an account with a
password that are already contained in the account

ACNT -- ACCOUNT FILE ALREADY EXISTS

Explanation:

The user attempted to create the account file,
but the account file already existed.

ACNT -- ACCOUNT FILE ERROR - x.

Explanation:

The program detected an I/O error
while
processing
the account file.
See the IAS/RSX-11
I/O
Operations Reference Manual, Appendix I, for a definition of
the error code.

2-22

PROCEDURES AND CONVENTIONS
ACNT -- ACCOUNT FILE FULL
Explanation: The account file is full;
the user cannot add
further accounts.
See the description of the Create command
for details on how to enlarge the account file.
ACNT -·- CANNOT FIND ACCOUNT
Explanation: The user attempted to delete,
modify an account that does not exist.

examine,

ACNT -- INVALID DEFAULT DEVICE NAME
Explanation:
The default system device specified is
not in the system or not a Files-11 device.

either

ACNT -- INVALID OPTION
Explanation:
In response to the prompt ENTER
user did not specify A, C, D, E, L, M, S, or
represent valid ACNT options.

OP~rION:,

the
, which

(£~

ACNT -- LISTING FILE ERROR
Explanation: When you use the List option, ACNT opens the
file SY:[current uic]
ACCNT.DMP.
This messagH indicates
that ACNT could not open the file;
for example, the device
was full or it didn't contain a UFD for the current UIC.
ACNT

-~-

SYNTAX OR COMMAND INPUT ERROR

Explanation:
The user typed an invalid character"
the. correct data.
ACNT -- WORKFILE - DYN.

MEM.

Re-enter

EXHAUSTED

Explanation:
There is insufficient dynamic memory.
Either
install the task in a larger partition, or install it with a
larger increment.
ACNT -- WORKFILE - VIRTUAL STORAGE EXCEEDED
Explanation:

2.4

The workf ile exceeds virtual memory.

THE SHUTUP PROGRAM

SHUTUP is a system task that permits orderly shut down of an
RSX-llM/M-PLUS system.
It issues warning messages to all terminals
connected or logged into the system, aborts all nonprivileged tasks,
and dismounts all devices.
It then halts the system.
Run SHUTUP from
any privileged terminal or from TTO:.
To successfully shut down a system using SHUTUP, the
must be installed:

following

tasks

AT., the MCR indirect command file processor

ACS, only if dynamic checkpoint space has been established

BYE, if multiuser protection support is included

2-23

PROCEDURES AND CONVENTIONS
4.

DMO, if there are any mounted volumes

ERF, if error logging is active.

""·
'

{lxi r{~~~rr~--~~us•··.···~ystern

s:in<t l)CL must: also . be

When activated, SHUTUP identifies itself and then prompts for
the
number of minutes before the system is to be shut down, the interval
in minutes between message broadcasts, and the number of minutes
to
wait before logins are disabled.
For example:
>RUN $SHUTUP
RSX11M SHUT DOWN PROGRAM
ENTER MINUTES TO WAIT BEFORE SHUTDOWN: 15
ENTER MINUTES BETWEEN MESSAGES: 3
ENTER MINUTES TO WAIT BEFORE DISABLING LOGINS: 5

After receiving this input
confirmation as follows:

(the numbers 15, 3, and 5), SHUTUP asks for

OK TO SHUTDOWN? CY/NJ:

If the response is negative, SHUTUP terminates.
If the
response
is
affirmative,
SHUTUP broadcasts the following message to all connected
or logged-in (multiuser protection systems only) terminals:
PLEASE FINISH UP1 15 MINUTES BEFORE SHUTDOWN
~'

Then 3 minutes later, the terminals receive another message:

PLEASE FINISH UP1 12 MINUTES BEFORE SHUTDOWN

SHUTUP continues to decrement the first number entered and to
issue
the warning messages at the specified interval until the waiting time
has elapsed.
If the system supports multiuser protection, after the specified delay
before disabling logins has expired (measured from the time SHUTUP is
started), SHUTUP displays the following message on the
invoking
terminal:
ALL FURTHER LOGINS ARE DISABLED

When the delay before
system, SHUTUP:

system

shutdown

has

expired

RSX-llM

Logs off all logged-in terminals

(multiuser systems only)

Stops the console driver

Redirects the console terminal to the TI:

If the file LB:[l,2]SHUTUP.CMD is present, submits it to
for execution

Stops the queue manager

Stops the error logging task,

(if present

in the system)

(QUE ••• )

2-24

if active

of SHUTUP
AT.

PROCEDURES AND CONVENTIONS

Deallocates all checkpoint space and
volumes

Halts the system

dismounts

all

mounted

At this point, you can either boot another system or resume the
current system by depressing the Continue switch on the CPU console.
To continue the current system operation, you must Mount the volumes
and follow normal system startup procedures.
The following is an example from an RSX-llM system:
RUN $SHUTUP
RSX11M SHUT DOWN PROGRAM
ENTER
ENTER
ENTER
OK TO

MINUTES TO Wf..\I T fJEFORE SHUTDOWN: 15
MINUTES BETWEEN MESS(-\GES: 3
MINUTES TO WAIT BEFDRE DI ~){.)BL. I NG LOGINS::
SHUTDOWN? CY/NJ: y

PL.EA!3E FINISH UP,

MINUTES

up '

MI NUTE!3 BETDRE !3HUTDDWN

PLF.:ASE FINISH

BEFDF~E

SHUTDOWN

ALL FURTHER LOGINS ARE DISABLED
PLEASE FINISH UP1 8 MINUTES BEFORE SHUTDOWN
PLEASE FINISH UP1 8 MINUTES BEFORE SHUTDOWN

2-25

~.)

PROCEDURES AND CONVENTIONS
PLEASE FINISH up, 3 MINUTES BEFORE SHUTDOWN
PLEASE FINISH UP, 2 MINUTES BEFORE SHUTDOWN
PLEASE FINISH UP,

MINUTES BEFORE SHUTDOWN

PLEASE FINISH UP1 0 MINUTES BEFORE SHUTDOWN
@LB: [ 112JSHUTUP
ERF
ERF
ERL

REQUESTED ERRLOG TO STD p LOGGING
LOGGING ENDED AFTER 0 ERRORS
II

ACS DBO:/BLKS=O,
ACS -- CHECKPOINT FILE NOW INACTIVE

DMD DBO: /DEl,I

*** DBO: -- DISMOUNT COMPLETE
DMD DB 1: I DEl,I

>
***DBi: -- DISMOUNT COMPLETE
ACS DSO:/BLKS=O,
ACS -- CHECKPOINT FILE NOW INACTIVE
DMD DSO: /DEl,I
*** DSO: -- DISMOUNT COMPLETE

>
DMD MMO:PAYRDL
MTAACP -- MMO: ** DISMOUNT COMPLETE **

>
To shut down the system in this example, SHUTUP:
•

Invokes the indirect command file
turn aborts the task ATTTl

which

•

Runs the task ERF to terminate the error logging task ERL
the RSX-llM/M-PLUS Error Logging Reference Manual)

(see

•

Deallocates checkpoint files on DBO:
ACS DBO: /BLKS= 0)

•

Dismounts the disks on DBO:, DBl:, and DSO:
DBO:)

•

Dismounts a
MMO: PAYROL)

magnetic

tape

[l,2]SHUTUP.CMD,

labeled

and DSO:

PAYROL

(for

example,

(for example, DMO
on

MMO:

(DMO

SHUTUP also issues Bye commands for all
logged-in terminals,
except
the terminal that issued RUN $SHUTUP.
Bye then displays a termination
message like the following:

>
HAVE A GOOD AFTERNOON
24-AUG-78 3:48 TT2: LOGGED OFF

Notes:
•

If the time to wait before shutdown is specified as less than
four minutes,
the
remaining two questions are not asked;
minutes between messages
is set to 1 and minutes before
disabling logins to 0.

2-26

PROCEDURES AND CONVENTIONS

•

"'-"''

Minutes between messages must be non-zero and not greater than
the minutes before shutdown.
Minutes before disabling logins
must not be greater than minutes before shutdown minus 3.
If
either value is incorrectly specified, SHUTUP rejects the
answer and re-prompts.

3 minutes remain before
system
shutdown,
SHUTUP
• When
interval between messages to 1
automatically changes the
minute.

2-27

·~.

·""'

CHAPTER 3
FILES AND VOLUMES

This chapter discusses basic concepts of
the RSX-llM/M-PLUS
file
system and highlights aspects of file handling which directly relate
to u:ser functions.
In RSX-llM/M-PLUSu a file is an owner-named area
on a volume, where volumes are magnetic media such as disks, DECtapes,
and magnetic tapes.

3.1

FILES-11

RSX-llM/M-PLUS includes a software system called Files-11
to oversee
the :storage and handling of files.
Five MCR functions prepare volumes
for use with Files-11:
volume Format Utility (FMT), Bad block utility
(BAD),
Initialize Volume
(INITVOL)"
Mount
(MOU),
and User File
Directory (UFD).
File:s-11 supports three types of specially formatted volumes:
disks,
DECtapes, and magnetic tapes.
(Files-11 magnetic tapes conform to the
American National Standard Magnetic Tape Labels and File Structure for
Information Interchange X3.27-1969.)
Before one of these
initialize it by
Section 4.5).
A
Initialize Volume
RSX-llM/M-PLUS file

volumes can be used on RSX-llM, you must properly
issuing the MCR Initialize Volume command (see
volume that has not been initialized by
the
command is a
"foreign" volume.
Files-11, the
system, cannot process foreign volumes.

A system utility called the File Exchange Program (FLX) allows you to
access foreign (not FILES-11) volumes in DIGITAL's DOS or RT-11 format
(cassettes, for example).
FLX translates files on such volumes
into
Files-11
format.
In most cases, DECtape will have a foreign format
and therefore require the use of the FLX utility.
See the RSX-11
Utilities Manual for a full description of FLX.
Before Files-11 can access a file, the volume that contains the file
must be known to the system.
You make a volume known to the system by
issuing a Mount command for the device on which the volume is loaded.

3.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 the user's current User Identification
Code (UIC) in the file header to indicate the owner of the file.
In

3-1

FILES AND VOLUMES

most cases,
the UFD corresponds to the owner UIC;
but a file can be
listed in a UFO that is not related to the owner code.
It is also
possible for a file to be listed simultaneously in more than one UFD.
A UFO is itself a file, which you must explicitly create by means
of
the MCR UFO command (see Section 4.5).
Specify a UFO in the format of
a UIC:
[g,m] where g and mare octal numbers in the range of 1-377
that represent the user's group and member number 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 UIC
[203,65]
is 203065.DIR.
(Note that
leading zeroes are added to the UFO to make g and m three places
each.)
All UFOs are listed in each volume's Master File Directory
(MFD),
which corresponds to UIC [0,0] and is therefore named 000000.DIR. The
directories (both the UFOs 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
i n de x f i 1 e ( [ 0 , 0 ] IND EX F • SYS ) •
To delete a UFD, first delete all of the files contained
(thereby freeing the space for future use) by typing:

After you delete all the files, delete the UFO by typing:
PIP> C010Jsssmmm+DIR;•/DE

where gggmmm is the concatenation of
components of the appropriate UIC.

the

group

and

member

number

Refer to the RSX-11 Utilities Manual for a detailed description of the
Peripheral Interchange Program (PIP).

File Protection

3.1.2

To access a file, you must know the UFO in which it is listed.
This
knowledge,
however,
is not sufficient to guarantee access.
You must
also satisfy conditions specified in a protection mask associated with
the file you wish to access.
In an RSX-llM-PLUS system, the volume
that contains the file must be mounted.
Evary file has a protection mask that describes the types of access
allowed to each one of four defined use.r groups.
RSX-llM/M-PLUS
defines four types of access:
•

Read

•

Write

•

Extend

•

Delete

3-2

FILES AND VOLUMES
The four user groups are defined according to UIC:
•

System - All system tasks, which are those that run under a
UIC having a group number less than or equal to 10{8)

•

Owner

- Tasks that run under the same UIC as the file's owner

•

Group

- Any task that runs under the same UIC group number
(the first octal number within the brackets) as the
f i 1 e ' s owner

•

World

- Any task or user that does not
above categories

fit

one

the

A file owner assigns access rights by one of the following means:
•

The MCR Initialize Volume
(INITVOL)
command.
This command
allows you to specify default file protection for all files
subsequently created on the initialized volume (when formatted
for use within Files-11).

MCR User File Directory
(UFD)
command.
This command
• The
establishes access
rights
to a UFD file only.
A user often
allows read access to a UFD, but denies access
listed within it.

the

files

•

The Peripheral Interchange Program (PIP).
PIP has an option
that enables
the owner to alter access rights to files.
See
the RSX-11 Utilities Manual.

•

The MCR Mount command.
This command allows you,
while
mounting a
volume, to specify the default file protection to
be given to files created on the volume.
This specification
overrides that established by means of the Initialize Volume
command.

To gain access to a file, a task 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.

3.2

FILE SPECIFIERS

MCR uses a standard format for referring to files in a command
line.
The format
is a string consisting of one or more input and/or output
file specifiers, as follows:
outfilel, ••• outfilex=infilel, ••• infilen
where outfile is an output file specifier and infile is an input
file
specifier.
The dots ( ••• ) indicate that you may include any number of
file specifiers in the string, the number being determined by
the
receiving task.
The command string (the string of specifiers plus the
task call or command) cannot exceed 80 characters,
the maximum line
lenigth.
For RSX-llM users,
the MCR Initialize Volume and Mount
commands (see Section 4.5) are exceptions to this rule.
RSX-llM-PLUS
users may extend any command line by appending a hyphen to the end of
the command line (see Section 4.1).
Some tasks may not require the outfile portion.
you can omit the equal sign (=) in some cases.

3-3

When it

omitted,

FILES AND VOLUMES
The individual file specifiers
following format:

(whether

input

output)

have

the

dev: [g,m]filename.type;version/switchl ••• /switchn
where:
dev:

specifies the physical or logical device unit on
which the volume containing the file is mounted.
The
device unit is expressed as a 2-character alphabetic
ASCII device name (see Section 2.2) and an optional
1- or 2-digit octal unit number, followed by a colon
(DKO:, DTl:
or LP:, for example).

[g Im]

stands for the User Identification Code
(UIC)
that
specifies the User File Directory (UFD) in which the
file is listed.
g and m are octal numbers from 0 to
377 that
represent the owner's group and member
number, respectively.
The brackets are a mandatory
part of the UIC syntax.

filename

specifies the name of
the
file,
an alphanumeric
string from 1 to 9 characters in length.
A period
always separates the file name from the file type.

type

consists of a 3-letter mnemonic that
identifies
the
nature of the file's
contents
(file type can be
null).
The standard RSX-llM/M-PLUS file
types are
listed in Section 3.2.2.
For example, .FTN indicates
that the file contains a FORTRAN source program,
and
.OBJ
indicates
that
the
contents are object
(compiled) code.
A semicolon
(;)
always separates
the file type from the version number.

version

stands for an octal number from 0 to
77777 that
differentiates various versions of a
file.
For
example, when a file is created, the system assigns
it a version number of 1. When you open the file for
editing, the system retains
the original file
for
backup and creates a new file.
The new file has the
same file name and type, but the version number is 2.
The numbers -1 and 0 have special significance:
-1
implies the lowest existing version of a file, and 0
implies the highest existing version.

/switch

consists of an ASCII
switch name
(usually
two
characters
long)
that
identifies a switch option.
You can optionally modify the switch as described
below.
Individual tasks
specify relevant switch
options, which generally modify the task's
function
in some way or provide
information that the task
needs to respond correctly to the command line.
The switch itself has one of three forms:
/SW

sets the switch action

/-SW
or
/NOSW

negates the switch action

3-4

FILES AND VOLUMES
The
number
of
permissible
values
and
the
interpretation of a
switch depend on the task to
which the switch
is directed
(switches are
task
specific).
The switch name may be modified by any number of
values;
these values may be ASCII strings, octal
numbers, or decimal numbers.
The following
rules
apply:
•Numbers terminated by a decimal point
decimal.

(.)

are

• Numbers preceded
octal.

(#)

are

pound

sign

• Whether the default for a numeric value
is
octal or decimal depends on the task to which
the switch is directed.
• You may precede any numeric value by a
plus
( +) o r mi nus ( - ) s i g n ;
p 1 us i s th 1:? def au l t .
• A plus or minus sign, if present, must precede
the pound sign (#) of an explicit octal number
(for example, -#323).

3.2.1

User Identification Codes (UICs)

In an RSX-llM/M-PLUS system that does
not
support
multiuser
protection,
each
terminal
has,
at
any one time,
one User
Identification Code (UIC).
A terminal's associated UIC is determined
by
the last Set /UIC command issued for the terminal, or is [200,200]
if the terminal's UIC has not been altered since system generation.
The system uses the current UIC of the issuing terminal whenever you
omit the UIC field of a file specifier.
The system also checks
this
UIC against the protection mask of any file that you want to access;
the check determines access rights to the file (see Section 3.1.2).
In a multiuser protection system,
a terminal has
protection UIC and a default UIC.
The system checks
UIC against a file's protection mask to determine the
rights to the file.
The default UIC determines the UFO
whenever you omit the UIC field in a file specifier.

two UICs:
a
the protection
user's access
to be accessed

How the system sets these two UICs depends on the privilege status of
the user logged onto the terminal.
When a nonprivileged user logs
onto a terminal, the terminal assumes the user's
logon UIC
as
its
protection UIC.
The logon UIC also becomes the initial default UIC;
but the nonprivileged user can issue a Set /UIC command to alter the
default UIC.
The protection UIC remains unchanged.
When a privileged
user logs onto a terminal, the terminal also assumes the logon UIC
as
both the protection and the default UIC.
However, when a privileged
user issues a Set /UIC command, the system alters both the default and
the protection UIC.
After logging into a multiuser protection system, a nonprivileged user
cannot alter the terminal's protection UIC;
whereas a privileged user
always alters both UICs when issuing a Set /UIC command.
Therefore, a
nonprivileged user can have a
default UIC
that differs from the
protection UIC;
but the protection and default UICs of cl privileged
user are always identical.

3-5

FILES AND VOLUMES
File Specifier Defaults

3.2.2

You may omit any field in a command line file specifier except the
file name.I When you omit one or more fields in a file specifier, the
system assumes the following defaults:
Field

Default

dev:

The pseudo device unit SY:,
usually
which the system volume is mounted. 2

the

device

[g' m]

The default UIC (see Section
each terminal, either:

specified

for

3.2.1)

•

(see
the
RSX-llM
or
at system generation
RSX-llM-PLUS
System Generation and Management
Guide)

•

by means of the MCR Set command

•

by means of the MCR
2.3.1.1)

Hello

(see Section 4.5)

command

(see

Section

filename

No default.I A specifier must include an explicit
file name or an asterisk (wildcard) within the file
name field (see Section 3.2.4).

type

One of the standard 3-letter mnemonics listed in
Section 3.2.3. The type defaulted to depends on the
task to which the specifier is directed, and whether
the specifier 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.

version

For input files,

the highest existing version number.

For output files, the highest existing version number
plus 1.
Note that you must include the version number when
using
PIP to delete a file.
This requirement
prevents inadvertent deletion of the highest version
of a file.
See the RSX-11 Utilities Manual.
/switch

3.2.3

Switch defaults are established by individual tasks.

Standard File Types

RSX-llM/M-PLUS has a standard set of file types used by
all
DIGITAL-supplied software to reflect actual file contents. Although
you can assign arbitrary 3-letter file types, it is convenient to use
the standard types described below.

1 The MCR Boot command is
Section 4.6.

the

only

exception

this

rule.

See

2 The MCR Boot command and specification of $ in the MCR commands
Install and Run default to device LB:.
See Sections 4.5 and 4.6.

3-6

""'·

FILES AND VOLUMES

Type

File Contents

BAS

A BASIC language source program

B2S

A BASIC-PLUS-2 source program

CBL

A COBOL language source program

CMD

MCR or task commands

COR

A SLP correction file

DAT

Data

DIR

A directory

FTN

(an indirect command file)

(as opposed to a program)
(for example, a User File Directory)

A FORTRAN language source program

F'1 f'

LST

A listing

'111/..,.,_s "

.•

MAC

A MACR0-11 source program

MAP

A Task Builder memory allocation map

MLB

A macro library

OBJ

An object program (output from the MACR0-11 Assembler
or a compiler)

ODL

A Task Builder overlay description

OLB

An object module library

SML

The system macro library

STB

A symbol table

SYS

A bootable system image

TMP

A temporary file

TSK

A task image

TX'I'

A text file

ULB

A universal library file

The defaults used by DIGITAL-supplied software are
manuals that pertain to the individual tasks.

3-7

described

the

FILES AND VOLUMES
3.2.4

The Asterisk Convention (Wildcards)

The asterisk convention allows you to specify more than one file in a
single specifier by placing an asterisk (*) or "wildcard" in one or
more fields of the specifier.
The wildcard causes the system to
ignore_the contents of the wild field and to select all the files that
satisfy the remaining explicitly described fields.
An asterisk can be placed in any part of the file specifier except the
device-unit field,
which must be explicitly supplied or defaulted to
SY:
(see Section 3.2.2). The following example, using the Peripheral
Interchange Program
(PIP),
illustrates the use of wildcards.
The
command line
PIP>PROG.MACil tPROG+OBJil tPROG,TSKil/DE

deletes the three individual files specified. Since the three files
have
the same file name and version number, but different types, the
following command line deletes the same files:
PIP>PROG.*il/DE

(The switch /DE instructs PIP to delete the files.) The command also
deletes any other files
(on the default device) named PROG with a
version number of l. You should check existing files
before using
wildcards (for example, by issuing the command line PIP> PROG.*;l/LI).

3.2.5

Examples Of File Name Command Strings

In the following examples,
the three letters
followed
standard prompts for the respective system programs.

are

• Assemble the MACR0-11 source file CRGPT.MAC and create the
object output file CRGPT.OBJ.
Both files are on DKO:
under
UIC [200,200].
MAC>DK0:[200t200JCRGPT+OBJ=DK0:[200t200JCRGPT.MAC

• Delete the file SBG.OBJ;5. The output file specifier
is not
applicable and tharefore is omitted.
The input device defaults
to SY: •
PIP>C200t200JSBG,OBJ;5/DE

•Task build the object file CRGPT.OBJ. The output will be named
CRGPT.TSK because TSK
is the default file type for the Task
Builder's output file;
the device and UIC are also defaulted.
TKB>CRGPT=CRGPT.OBJ
TKB>ll

• Delete all files with the name BOBSDAT, regardless of
type or
version.
The system uses default values for the device and
UIC.

3-8

CHAPTER 4
MCR COMMANDS

4.1

INTRODUCTION

You communicate with an RSX-llM/M-PLUS system from a
terminal.
The
Monitor Console Routine
(MCR)
serves as an interface between the
terminal and the RSX-llM/M-PLUS system.
To issue an MCR command, type a command string in response to a
default
(>) or explicit MCR (MCR>) prompt.
A command string consists
of three components:
a command name, any required parameters,
and a
linE~ terminator.
It is not necessary to type the entire command name when submitting a
command.
MCR requires only the first three letters of a command name
(the exception is Help, which must be entered in full),
followed by
command parameters.
For example, you can type the Cancel command as follows:
>CAN taskname ~
where taskname is the command parameter and ~ stands
for
carriage
return, the line terminator.
As in this example, the 3-letter command
namE~ often consists of the first three letters of the
command title.
Some commands, however, have 3-letter acronyms as command names.
For
instance, the names for the Assign and User File Directory commands
are ASN and UFD, respectively.
Although MCR recognizes only the first
three letters of a
typed
command name, you can concatenate any number (up to the maximum buffer
length of ths terminal) of alphanumeric characters to those
three
initial letters.
To make the intent of the command clear to someone
reading a printed copy of command input, you can typ~:
>CANCEL taskname

A space or a tab signals the end of the command name;
therefore,
spaces or tabs are allowed within the name itself.
For example,

>OPENREGISTER address
is permissible, while
>OPEN REGISTER address
is not.
Typically, a parameter is a task name, the name of a file, or a device
specification.
A parameter may be modified by either a switch or a
keyword (defined in Sections 3.2 and 4.2.1 respectively).

4-1

MCR COMMANDS

Press carriage return ~ or the AL.Tmode or ESCape key
~
to
terminate a command string.
When MCR completes command processing
following a~, it returns the default prompt.
MCR suppresses the
default prompt after processing a command string terminated by~
except when ~has special significance as a terminator (with the Run
and Open Register commands,
for example). MCR accepts subsequent
unsolicited input even though the default prompt does not appear.
This chapter describes in detail all of the MCR commands.
Each
description includes the full command title, the 3-letter command name
recognized by MCR, any required parameters, and whether or not the
parameters need to be modified •

.,,,jj~l~i~tt~~~[~tft~it'
t.ne··

4.2

THE MCR INTERFACE

MCR reads or parses the input you type and then responds appropriately
to the input. To service a request, MCR either loads an MCR overlay
or activates an independent task.
By following the procedures outlined below, MCR
appropriate overlay or task to service each command.

activates

the

The first three letters of the command name are the most significant
part of a command line. MCR uses the name to determine the required
overlay or task. First, it searches a table containing names of
commands serviced by MCR itself. If the table contains a matching
command, MCR loads the corresponding overlay, which proceeds to
process the command line.
If the table does not contain a match, MCR prefixes three dots
( ••• )
to the command name and then 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.
In an RSX-llM system, MCR displays a TASK ACTIVE message if ••• tsk is
already active at the terminal. If the STD does contain ••• tsk, and
it is not running at the issuing terminal, MCR in RSX-llM responds
conditionally in one of two ways:
•

If ••• tsk is not active, MCR requests the Executive to run the
task at the issuing terminal.

•

If ••• tsk
temporary

is active at another terminal, MCR creates a
STD entry that points to the already active task's

4-2

MCR COMMANDS
disk image.
MCR names the temporary task tskTnn, where nn is
the unit number of the terminal that issued the command, and
requests the Executive to run the task.
When tskTnn exits,
the Executive automatically deletes its STD entry.

Keywords

4.2.l

Some commands use keywords that generally apply to a command argument.
A keyword is similar in function to the switches described in Section
3.2. A keyword consists of a slash
(/),
followed by an ASCII
identification,
and optionally followed by an equal sign (=) and the
value of the keyword, as follows:
/keyword=value
As an example of using keywords, the Install command requires a
file
name parameter specifying the task to be installed.
You can append
keywords to the file name.
One such keyword,
/TASK,
specifies the
name under which the task is to be installed. Thus,
)INS BOB+TSK/TASK=AMBER

installs the task in the file BOB.TSK with a name of AMBER.
Enter keywords in any order.
defined with each command.

They

are

command-specific

and

are

Comments

4.2.2

MCR treats a line of text as a comment if the first character
in the
line is a semicolon
(;).
In addition, you can use the exclamation
point (1) to delimit comments in a command.
The first exclamation
point starts the comment and the next exclamation point or end of line
terminates the comment.
MCR ignores all text between the two
exclamation points.
For example:
THIS LINE IS A COMME~T

>i
~AL

!THIS IS A COMMENT STRING!

RMDEMO

Comments are especially useful to clarify commands
command files, which are described in Chapter 5.

4.2.3

MCR

indirect

Command References To Active Tasks

4.2.3.l Task-Naming Convention - In an RSX-llM multiuser protection
system,
more than one copy of a task can be active simultaneously.
When you request a task that
is already active,
MCR automatically
creates a name for a copy of the requested task:
tskTnn where tsk is
the 3-character task name and Tnn is the unit number of the requesting
terminal.
However,
to
refer to that task from the
requesting
terminal, you only need specify the 3-character task name (tsk).
4-3

MCR COMMANDS
For example, if you request PIP from TT2:, when PIP is already active
at another terminal,
MCR runs a task called PIPT2. To abort PIPT2
from TT2:, enter the command
>ABO PIP

and MCR aborts the correct version of PIP. However, to abort TT2:'s
version of PIP from another terminal, a privileged user must type
>ABO PIPT2

(The user at TT2:
can also specify PIPT2, but the full
necessary in most cases.)

name

not

Note that the naming convention does not apply to tasks
the MCR Run command.

requested

nn
nn

nn
nn
nn

is
is
is

nn
nn
nn

is
is
is
is

.is

AO
Al
A7

BO.

C7
DO

XO
X7

convention

4-4

MCR COMMANDS

4.2.3.2 Install-Run-Remove Tasks - Whenever a user activates a
task
by means of the
install-run-remove option of the Run command in an
RSX-llM system, MCR names the task TTnn, where nn is the unit number
of
the terminal that requested the task.
You can refer to task TTnn
in a command issued from terminal TTnn:
and can omit the
task name
altogether.
For example, if you issue the command >RUN $CALC from TTl:, MCR runs
the
task contained in a
file called CALC.TSK listed in the system
directory (for example, [1,54] in a mapped system), and names it TTL
To abort this task
from TTl:,
issue the Abort command without
specifying a parameter;
that is,
>ABO IBTil

The command
>ABO TT 1 illru

issued either from TTl:
or any privileged terminal also aborts the
task originally referred to as $CALC in a Run command issued from
termi na 1 'I'Tl: •

4-5

MCR COMMANDS
4.3

COMMAND SUMMARY

The MCR commands described
in this chapter are listed below by
category.
This command summary provides a compact overview of the
facilities available at a user terminal.
Commands available to both
privileged and nonprivileged users are described in alphabetical order
in Section 4.5. The commands followed by a P in parentheses are
available
only
to
privileged users.
These are described
in
alphabetical order in Section 4.6.

Initialization Commands
ACS

( P)

the

use

Define or delete a logical device assignment.
List current assignments on user's terminal.

ASN
BOOT

Allocate or discontinue
checkpoint file on disk.

( P)

Bootstrap a new system
transfer control to it.

into

and

memory

DMOUNT

Dismount a volume by running down file system
activity and deleting the Volume Control
Block (VCB).

FLAGS

Create, display, or
event flags.

INITVOLUME

Initialize an RSX-llM/M-PLUS Files-11 volume.

INSTALL (P)

Install a task in the system.

LOAD (P)

Read a nonresident device driver into memory.

MOUNT

Create a Volume Control Block
(VCB)
and
declare the volume online for access by the
file system.

SET

Alter or display
characteristics.

TIME

Enter the time and/or date into the system;
display the time and date on the entering
terminal.

UFD

Create a
specific
(MFD) •

UNLOAD (P)

Remove a loadable device driver from memory.

User File
volume's

eliminate

system-wide

group

global

terminal

Directory
(UFD)
in a
Master File Directory

Informational Commands
ACT

Display on the entering terminal the names of
active tasks.

ATL

Display on the entering terminal names
status information for active tasks.

4-6

and

"""·

MCR COMMANDS
Informational Commands (Cont.)
CLQUEUE ( P)

Display information about tasks in the
queue.

DEVICES

Display on the entering terminal the list of
peripheral devices recognized by the system.

LUNS

Display on the entering terminal the list of
static LUN assignments for a specific task.

PARTITIONS

Display on the entering terminal
the partition definitions.

TAL

Display on the entering terminal the
and status of all tasks in the system.

names

TASK LIST

Display on the entering terminal
Task List.

System

clock

list

the

Task Control Commands
ABORT

Terminate execution of a running task.

ALT EH (P)

Alter the priority of a task.

CANCEL

Cancel time-based initiation requests
for
task (no effect on current execution).

FIX (P)

Fix a task in
resident).

REASSIGN ( p)

Change LUN assignments.

RED I HECT ( p)

Redirect all I/O requests from
device to another.

REMOVE ( p)

Remove a task from the
of Install.)

RESUME

Resume execution of a suspended task.

RUN

Schedule a task's activation.
The task may
run
immediately,
after a time delay, or in
synchronization with
the
system
clock.
Periodic rescheduling is optional.

STP

Halt
(stop)
a task and
competition for memory.

UNFIX (P)

Makes a memory-resident task non-resident.

UNSTOP

Resume
execution
of
(Complement of Stop.)

memory

(task

becomes

memory

one

physical

(Complement

system.

remove

from

stopped

task.

System Maintenance Commands
BRK ( P)

Pass control to the Executive Debugging Tool
(XDT).
Valid only for systems that have
generated XDT support.

BRO

Broadcast a
terminals.

4-7

message

one

set

MCR COMMANDS
System Maintenance Commands (Cont.)
OPEN (P)

Display on the entering terminal the contents
of a memory location for examination or
modification.

SAVE ( P)

Save the image of memory
in
which the system was booted.

SSM (P)

Insert text into error log reports.
;·

the

file

from

··'

RSX-llM~PLUS . ·.· ·.• .mul~iprocel~iA<J' L

•

sysb~fos~·

Pi splay the current yalue, inset~ ~· y~·lq~i. or•

set/clear a bit in the sw.itch . .re<Ji~t~r:• :·

Multiuser Protection Commands

4.4

ALLOCATE

Allocate a device to a user (es ta bl i shes
device as the user's private device).

BYE

Log off the system.

DEALLOCATE

Deallocate a private device.

HELLO

Log into the system.

HELP

Display the contents of a Help file.

the

COMMAND DESCRIPTION FORMAT AND SYNTAX

Syntactical descriptions of commands and messages described
chapter observe the following notational conventions:

this

Lower case
indicates a
variable whose actual value is
determined when the command is entered or the message is
issued.
For example, the value of taskname depends on the
name of the task associated with the command or message.

Brackets [] enclose optional items.
A syntactical element
enclosed in brackets (for example, [dt]) is optional;
it may
or may not be included in the command.
One common exception
to this
rule
is the syntax for the specification of a UIC.
The format for a UIC is [ggg,mmm], where the square brackets
are required syntactical elements.

Unless explicitly qualified, all numeric values required in a
command can be entered as decimal or octal.
Decimal values
are
indicated by a trailing period;
octal values are
indicated by the absence of a trailing period. Thus,
255.
and
377
have the same value.
3 7 7 is base 8 • )

(The value 255.

4-8

is base 10;

the value

MCR COMMANDS
The following subheadings appear in the detailed command descriptions
of Sections 4.5 and
4.6.
Subheadings that do not apply
to a
particular command are simply omitted from the command description.

Command Name
Thi$ subheading identifies the command name in capital
letters.
The
minimal MCR command acronym is shown on the upper right or left
margin.
The text following this subheading describes
the command's
function.

Format
The command format is given, and all parameters are described.

Command Related Error Messages
Error messages specific to the command appear under this subheading.
The command may also produce the common error messages listed in
Appendix A.
These common error messages are not listed with
the
individual commands presented in this chapter.

4-9

MCR COMMANDS

4.5

NONPRIVILEGED MCR COMMAND DESCRIPTIONS

ABO
ABORT
The Abort command terminates execution of an
indicated
task.
Nonprivileged users can only abort a nonprivileged task requested from
the issuing terminal.
A privileged user can abort any task.
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 routine (TKTN)
to
display a message on the aborted task's TI:
terminal.
The
display describes the reason for the termination and, if the
task was built with the /PM Task Builder switch or installed
with the /PMD=YES keyword,
the
task's
·registers
at
termination.
However,
if the
task is checkpointed at the
time TKTN is called to process the abort,
TKTN does not
display the task's registers.

•

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. A task must be memory-resident to be aborted;
this
change
in running priority usually causes a quick return for
a checkpointed task.

If the command includes the optional keyword /PMD,
it forces
the
system to produce a post-mortem dump of the aborted task.
The system
therefore produces the dump whether or not the task was built with the
/PM Task Builder switch or installed with the /PMD=YES keyword.
Likewise, /-PMD suppresses a post-mortem dump.
Format:
ABO[RT] taskname[/PMD] [/TERM=TTnn:]
where:
taskname - The name of the task to be aborted.
If you omit the taskname, the command attempts to
abort task TTnn.
In an RSX-llM system nn is the octal unit number
of the issuing terminal (see Section 4.2.3).

4-10

MCR COMMANDS

AIBO (Cont.)

Likewise, if you specify only
characters,
abort
defaults
tskTnn.
See Section 4.2.3.
/PMD

the
the

first
three
taskname to

- A keyword that requests a post-mortem dump of the
aborted task.

Examples:

''-"'

>ABORT SCAN
TASK SCAN TERM I NAT ED
ABORTED VIA DIRECTIVE OR MCR
II

PC=07G400
PS=000030

RO=OOOOOO
R1=004230
R2=074350
R3=000020
R4=000000
R5:::07GOOO
SP=07G114

>ABO MAC
TASK MACT3 TERMINATED
ABORTED VIA DIRECTIVE OR MCR
11

MCR aborted a task called MACT3,
even though the command,
issued from TT3:, specified the 3-letter task name only (see
Sect ion 4. 2. 3 .1) •
In an RSX-llM system,
the c:ommand >ABO
MACT3,
issued from any privileged terminal, would have the
same effect.
In an RSX-llM-PLUS system, the command >ABO MAC
/TERM=TT3:,
issued from any privileged termina1, would have
the same ef feet.
>ABO ID
TASK TT7 TERMINATED
ABORTED VIA DIRECTIVE OR MCR
11

MCR aborted the task, TT7, from TT7:;
be specified to abort task TTn.

the taskname

need

not

Command Error Messages:
On receiving an Abort command,
MCR requests the Executive to
abort the task.
The Executive subsequently activates the Task
Termination Notification routine (TKTN).
TKTN then produces the
termination display shown in the above examples.
Messages
following an Abort command can therefore come either from the
command itself or from TKTN.

4-11

MCR COMMANDS

ABO {Cont.)
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.
ABO -- TASK NOT ACTIVE
The specified task is not currently active.
Messages from Task Termination Notification Routine
TKTN displays information about task aborts,
the MCR Abort command or some other means.
format:

(TKTN):

whether caused by
The display has the

TASK "taskname" TERMINATED
abort cause
Following the displayed cause for the abort
task's
registers at the time of the abort.
of the abort are described below.

is a list of
the
The possible causes

Abort Cause Messages:
ABORTED BY DIRECTIVE OR MCR
Either MCR or an Executive directive issued by another
caused the task to be aborted.

task

ABORTED VIA MCR
MCR aborted the task and requested a post-mortem dump.
11/40 F.P.

EXCEPTION

The task encountered a
floating point exception while
executing on a PDP-11/40, and no SST routine was specified
to process the trap.
AST ABORT.

BAD STACK

An AST could not be effected because the
could not be pushed onto the task's stack.
CHECKPOINT FAILURE.

AST

parameters

READ ERROR.

The task could not be read
check pointed.

back

into

memory

after

being

!OT EXECUTION
The task executed an !OT instruction, and no SST routine was
specified to process the trap.

4-12

MCR COMMANDS

Al3~0

LOAD FAILURE.

(Cont.)

READ ERROR

The task could not be loaded because of a hardware error.
MEMORY PROTECT VIOLATION
The task encountered a memory-protect violation, and no
routine was specified to process the trap.

SST

NON RSX EMT EXECUTION
The task executed an EMT instruction with an argument other
than 377(8)
or, in the case of a privileged task switching
to system state, 376(8) 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
it referenced a nonexistent memory
location, 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.
RESERVED INST EXECUTION
The task executed an illegal instruction, and no SST routine
was specified to process the trap.
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 nonzero value in the header guard word.
TASK EXIT WITH OUTSTANDING IO
The task exited with one or more outstanding I/O
requests.
Tasks should terminate all I/O operations before exiting.
The system does, however, clean up all outstanding I/O.
T BIT TRAP OR BPT EXECUTION
The task 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.
TRAP EXECUTION
The task executed a Trap instruction, and no SST routine was
specified to process the trap.

4-13

MCR COMMANDS

ACT
ACTIVE
The Active command displays at the issuing terminal the names of only
terminal-initiated
tasks.
In RSX-llM-PLUS systems,
the display
includes the octal unit numbers of the terminals that initiated each
task.
When issued in conjunction with /ALL (ACT /ALL),
the
active tasks are displayed at the entering terminal.

names

all

The Active command can also be issued in conjunction with /TERM
(ACT
/TERM=TTn:) to display on TI:
the names of all the active tasks for a
specific terminal.
Format:
ACT [IVE]

[/keyword]

Keywords:
/ALL
/TERM=TTn:
Examples:
RSX-llM systems
>ACT
MCR.,.
, • , SYS
>ACT /ALL
• LDR.
RMDEMO
MCR •••
, •.•SYS
F11ACP
• • • p Ip

>ACT /TERM=TT7:
•••PI p

>
RSX-llM-PLUS systems
>ACT
MCR.,.
ACTT17

<TT17:)
<TT17:)

>ACT /ALL
<COO:)
• •, LDR
(TTG2: )
RMDEMO
MCR,.,
(TT17:)
F11ACP (coo:)
(coo:)
DSOOF1
(COO:)
DS01F1
<COO:)
LSTACP
(coo:)
DB03F1

4-14

MCR COMMANDS

AT, t,JG

( l.JTG: )

QMG,,,

(COO:)
(COO:)

HRC,,,
PIPTA1

(TT101:)

>
>ACT /TERM=TT107:
LBRTA7
(TT107:)

4-15

MCR COMMANDS

ALL
ALLOCATE
The Allocate command establishes a specified device as the user's
private device.
(This command applies only to systems that support
multiuser protection.) Device allocation prevents other nonprivileged
users
from accessing a device (see Section 2.2).
Only the device's
owner or a privileged user can access or deallocate a private device.
Mounted devices, public
cannot be allocated.

devices,

other

users'

private

devices

The system automatically deallocates a user's private devices when the
user logs off (issues the Bye command).

·;~·sxj'.11~-~e&s ~~~fs may, opfiohally '··· allo~ate. ~
t~~mip~l.

r(;ltber

•ttian

to . TL:.

This

.;. ~~'.Vl9~·.••.to. ct.·vt{t:..9aJ· te rmina 1.

allows

Format:

where:
dd

The device
allocated.

nn:

mnemonic

the

device-unit

- The optional device-unit number to be allocated.
If
the command omits nn:,
the system allocates the
first available logical unit of the dd type device
and displays the allocated device in the following
format:
ALL -- ddnn:

llnn:

NOW ALLOCATED

- The optional name of a
logical device,
which the
system creates and assigns to the allocated physical
device.
(This is a local assignment as created by
the ASN command.)

Examples:
>ALL DK2:

Allocates disk DK2:.
>ALL DK:

Allocates disk DKO:.

4-16

MCR COMMANDS

ALL (Cont.)
>,ALL DK=)·O(O:
ALL -- DK3: NOW ALLOCATED
Allocates the first available logical unit of DK
(in this
case,
disk DK3:,
since units 0,1,
and 2 were allocated
previously or public) and assigns it the logical name XXO:.
Command Error Messages:
ALL -- DEVICE ALLOCATED TO OTHER USER
The specified device has
another user.

already

been

allocated

ALL -- DEVICE ATTACHED
The specified device cannot be allocated because it is
attached to a running task.
ALL -- PSEUDO DEVICE ERROR
pseudo

device.

Pseudo

The command attempted to allocate a
Public devices cannot be allocated.

public

device.

The specified device is a
devices cannot be allocated.
ALL -- PUBLIC DEVICE

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.

4-17

MCR COMMANDS

ASN
ASSIGN
The Assign command defines,
deletes,
or displays
logical-device
assignments.
Logical-device assignments associate logical names with
physical devices, pseudo devices, or other logical devices.
When a
user assigns a logical name to a pseudo or logi~al device, the system
resolves the assignment to the associated physical device.
There are
three types of logical-device assignment:
global, local, and login.
•

Global assignments apply to all tasks running in the system.
Only privileged users can
issue ASN commands to define or
delete global assignments.

•

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 occur only in systems that support multiuser
protection.
When a
user issues a Hello command to log into
the system, the system automatically assigns the logical name
SY: to the user's system device,
which is the device that
contains the user's files.
The login assignments apply only
to tasks initiated from the terminal while the current user is
logged in.
Only a privileged user can define. or delete
login
assignments.

Local assignments have precedence over both login
and
global
assignments;
and
login assignments have
precedence over global
assignments.
When a user deassigns a local logical-device name,
the
system defaults to any conflicting login assignments.
A logical-device name has the same syntax as a real device unit;
it
consists of
a 2-character ASCII name (alphabetic) and an optional 1or 2-digit octal unit number, followed by a colon(:).
The 2-character
name can either be equivalent to a standard RSX-llM/M-PLUS device name
(for exampla, DK:) or it can be two letters picked at
random
(for
example, ZY:).
When a user installs a task or the
system processes an Assign LUN
directive,
the system scans
the
logical device table before the
physical device table when searching for a
specified device.
As a
result,
a
user can define 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.
The system resolves a
specified device name
to
the first
matching table entry fqund.
Therefore,
if a logical device name is identical to a physical device
name, the logical name has precedence.
Nonprivileged formats:
ASN ppnn:=llnn:
Assign the logical name llnn: to device ppnn:. The command
establishes a local assignment for the issuing terminal.
ASN
Display at
the
issuing terminal
logical-device assignments.

4-18

all

local

and

MCR COMMANDS

ASN (Cont.)
ASN = [llnn:]
c

Delete the local assignment of the specified logical-device
name;
or delete all local logical-device assignments for
the issuing terminal if the command omits llnn:.
Privileged formats:
ASN ppnn:=llnn:/GBL
Define a global assignment that associates the logical
llnn: with device ppnn:.

name

ASN /GBL
Display all global, local, and
terminals in the system.

assignments

for

all

ASN = [ llnn: ] /GBL
Delete the specified global logical-device assignment;
or
delete all global assignments if the command omits llnn:.
ASN ppnn:=llnn:/LOGIN[/TERM=ttnn:]
Establish a login logical-device assignment for a specified
terminal,
or for the issuing terminal if the command omits
/TERM=ttnn:.
ASN /TERM=ttnn:
Display at the entering terminal all
local and login
logical-device assignments for the specified terminal.
ASN =llnn:/LOGIN[/TERM=ttnn:]
Delete the login logical-device assignment indicated by the
name llnn:
for a specified terminal, or for the issuing
terminal if the command omits /TERM=ttnn:.
ASN =/LOGIN[/TERM=ttnn:]
Delete all
login logical-device
specified terminal,
or for
the
command omits /TERM=ttnn:.

assignments
for
the
issuing terminal if the

ASN =[llnn:]/TERM=ttnn:
Delete the local logical-device assignment indicated by the
name llnn:
for the specified terminal;
or delete all local
logical-device assignments for the specified terminal if the
command omits llnn:.
where:
pp - Physical, logical, or pseudo device name
nn - Unit number
11 - Logical device name
tt - Terminal device name

4-19

MCR COMMANDS

ASN (Cont.)
E.xample:
>ASN
>ASN
>ASN
>ASN
US2:
us 1:
SY:
>ASN
US2:
us 1:
SY:
GBO:
>ASN
>ASN
>ASN
>ASN
>ASN
>ASN
ZZO:
}{YO:

DP:=US1:
DT:=US2:
DK:=GBO:/GBL
DTO:
LOCAL
DPO:
LOCAL
DPO:
LOGIN
/GBL
DTO:
LOCAL
DPO:
LOCAL
DPO:
LOGIN
DKO:
GLOBAL
=US2:
=/GBL
=US1:
DK:=XY:
}-{Y: =ZZ:

DKO:
DKO:

LOCAL
LOCAL

!Define US1:
!Define US2:
!Define slobal losical device name GBO:
!List local and losin assisnments
TI - TTC>:
TI - TTC>:
TI - TTO:
!List all assisnments
TI - TTO:
TI - TTO:
TI - TH>:
!Eliminate local losical device name US2:
!Eliminate all Slobal assisnments
!Eliminate local losical device name US1:
!Assisn ~Y: to DK:
!Assisn ZZ: to XY:
!DisPlaY assisnments
TI-TTO:
TI-TTO:

Command Error Messages:
ASN -- DEVICE NOT TERMINAL
The /TERM keyword value in
specify a terminal.

ASN

command

did

not

ASN -- LOGICAL DEVICE NOT IN SYSTEM
The specified logical device name was not included in
the system at system generation and therefore could
not be found in the logical device assignment table
for the terminal.

4-20

MCR COMMANDS

ATL
ACTIVE TASK LIST
This command displays on the entering terminal the name and status of
all active tasks
in the system or the status of a particular task
(task name).
The display provides information useful for determining
the exact status of each active task.
The display contains the
following information for each task:

:'-"

•
•
•
•
•
•
•
•
•
•
•
•

Task name
Task control block physical 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
I/O count, (dee i ma 1)
Task local event flags
Task registers and Processor Status Word
(memory-resident
tasks only)
RSX-llM-PLUS also displays the name of the parent task
(if
one exists) as well as the task blocking count.

The displayed task status flags are from the Task Control Block (TCB).
This command displays the name of the bit if the bit is set to one at
the time of the display.
Zero bits are not displayed.
Flag names are
three characters long and correspond to the last three characters of
the mnemonic defining the status bits.
(See the
RSX-llM
or
RSX-llM-PLUS Syste~ Generation and Management Guide for a description
of the TCB.) For example, FXD represents the bit T2.FXD and
indicates
that the task is fixed in memory.
Names prefixed by a minus (-) sign
indicate that the bit represents the complement of the condition.
For
example, -CHK indicates that the task is not checkpointable.
If the task is not in memory (the OUT flag is displayed), the contents
of the PC, the PS, and the registers are not displayed.

·~

Status

TCB Flag

ABO
ACP
AST
CAL
-CHK
CIP
CKP
CKR
CL!
DST
-EXE
FXD
HLT
MCR
MSG

T2.ABO
T3.ACP
T2 .AST
T3.CAL
TS.CHK
TS.CIP
TS.CKP
TS.CKR
T3 .CLI
T2.DST
TS.EXE
T2.F'XD
T2.HLT
T3.MCR
TS.MSG

Description
Task is being aborted.
Task is an Ancillary Control Processor.
Task is processing an AST.
Checkpoint space is allocated in task image.
Task is not checkpointable.
Task is blocked for checkpoint in progress.
Task is checkpointed.
Task checkpoint request pending.
Task is a command line interpreter.
Task ASTs are disabled.
Task is not in execution.
Task is fixed in memory.
Task is being terminated.
Task was activated by MCR.
Task aborted, waiting for TKTN message.
(continued on next page)

4-21

MCR COMMANDS

ATL (Cont.)
Status

TCB Flag

NET
NSD
-PMD
OUT
PRV
RDN
REM
ROV
RST
RUN

T3.NET
T3.NSD
T3.PMD
TS.OUT
T3.PRV
TS.RON
T3.REM
T3.ROV
T3.RST
TS.RUN

SEF
SLV
SPN
SPNA
STP
STPA
TIO
WFR
WFRA

T2.SEF
T3.SLV
T2.SPN

Description
Network protocol level.
Task cannot receive data (no send data allowed).
Suppress task Post-Mortem Dump on SST abort
Task is out of memory.
Task is privileged.
Task I/O is being run down.
Task is to be removed on exit.
Task has resident overlays (RSX-llM-PLUS systems).
Task is restricted.
Task
is
executing on
another
processor
(RSX-llM-PLUS
multiprocessing systems only).
Task is stopped for an event flag(s).
Task is slave.
Task is being suspended.
Task was suspended prior to AST.
Task stopped.
Task stopped prior to AST.
Task is waiting for terminal input.
Task is in a "wait-for" state.
Task was in a "wait-for" state before AST.

TS.STP
T2 .TIO
T2.WFR

Format:
ATL [taskname]
Examples:
RSX-llM systems
>ATL
,,,LOR 053828 LOR
053572 00000000-00000000 PRI - 248,
DPRI
248.
STATUS:
-CHK FXD STP PRV
TI - COO:
IOC - O,
EFLG - 000001 000000
PS
170000
PC
042518
REGS 0-8 000182 005800 177777 105312 084240 105280 053540
RMDEMO 054222 GEN
058800 00204000-00217800
PRI - 225.
DPRI
225.
STATUS:
WFR PRV CAL
TI - TTO:
IOC - O+
EFLG - 000001 000000
PS - 170010
PC
125072
REGS 0-8
123354 000081 000000 125032 001801 131530 120352
MCR,,, 105530 SYSPAR 107734 00110000-00120000
PRI - 180.
DPRI
1GO,
STATUS:
STP -PMD PRV NSD CAL
TI - TT20:
roe - o. EFLG - 000001 040000 PS - 170000 PC
REGS 0-8 000000 120470 121788 120424 122314 000000 120382
, ,,SYS 105280 GEN
084240

(operator typed

«TRw0

to suppress further output)

>ATL RMDEMO
RMDEMO 054222 GEN
058800 00204000-00217800
PRI - 225.
DPRI
225,
STATUS:
WFR PRV CAL
TI - TTO:
IOC - O,
EFLG - 000001 000000
PS - 170010
PC - 125072
REGS 0-8
123354 000081 000000 125032 001801 131530 120352

4-22

MCR COMMANDS

ATL (Cont.)
RSX-llM-PLUS systems
>ATL
••• LOR 118340 LDRPAR 118124 00408000-00410400
PRI - 248,
DPRI - 248,
STATUS:
STP -PMD PRV FXD
TI - COO:
IOC -0.
EFLG - 000001 000000
PS - 170000
PC - 120444
REGS 0-8 000182 020885 177777 087300 087250 084110 120188
RMDEMO 044724 GEN
043084 01825700-01841700
PRI - 225,
DPRI - 225.
STATUS:
WFR -PMD PRV MCR CAL
TI - TTO:
IOC - O.
EFLG - 000001 000000
PS - 170010
PC - 125100
REGS 0-8
123353 000082 000110 125040 001801 131774 120352
MCR,,, 115210 SYSPAR 038840 00184000-00174000
PRI - 180.
DPRI - 180.
STATUS:
STP -PMD PRV CLI NBD CAL
TI - TTO:
IOC - O.
EFLG - 000001 040000
PS - 170000
PC - 124104
REGS 0-8 000000 120474 000400 120430 000115 120510 120380
DCL,,, 058370 SYSPAR 043580 00184000-00174000
PRI - 180.
DPRI - 180.
STATUS:
STP -PMD PRV CLI NBD CAL OUT CKP BLK: 1
TI - TT10:
IOC - O.
EFLG - 000001 040000
OEVT88 082040 GEN
082314 01841700-01887500
PRI - 180.
DPRI - 180.

(operator typed

(cTRLto)

to suppress further output)

>ATL RMDEMO
RMDEMO 044724 GEN
043084 01825700-01841700
PRI - 225.
DPRI - 225.
STATUS:
TIO STP -PMD PRV MCR CAL
TI - TTO:
IOC - O,
EFLG - 000000 000000
PS - 170010
PC - 130352
REGS 0-8 000050 000040 000110 125040 001801 131774 120350

4-23

MCR COMMANDS

BRO
BROADCAST
The Broadcast command displays a specified
terminals, as follows:

message

one

•

A privileged user can display a message at all
terminals
connected to the system, or, in a multiuser protection system,
at all logged-in terminals.

•

Both privileged and nonprivileged users can display a
at any one terminal.

message

You can also create an indirect command file to contain one 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 after the command name the file specification
preceded by an at sign (@).
If the message cannot be broadcast within 10 seconds,
displays the following message at the issuing terminal:

the

system

BRO -- TERMINAL IS BUSY -- ttn:
If a privileged user specifies multiple terminals (ALL:
or LOG:), the
system returns one error message for each busy terminal.
~
c:;

F'ormats:
BRO[ADCAST] ttn:message
BRO[ADCAST] @filespec
BRO[ADCAST] ALL:message

(Privileged format)

BRO[ADCAST]

(Privileged format)

LOG:message

NOTE
Each format
can be entered on
two
successive
lines
by
pressing
~
immediately after the command
name;
this
invokes the direct task format.
For example:
>BRO[ADCAST]
~
BRO> ttn:message
To exit

the

direct

task

format

type

(CTRL/Z) •

where:
ttn:
message

Terminal to receive broadcast message.
- Message to be broadcast, an ASCII character
string that cannot exceed the length of one
1 ine (80 characters).

4-24

MCR COMMANDS

BRO (Cont.)
f ilespec

- Specification of a
file containing
more message lines in the format:

one

ttn:message
or, for privileged users:
ALL:message or
LOG:message
ALL:

- Privileged option.
Indicates that specified
message
is to be sent to all terminals
connected to the system
(this does
not
include slaved terminals, such as the RMDEMO
terminal or virtual terminals).

LOG:

- Privileged option.
Indicates
that
the
specified message is to be sent to all
logged-in terminals (this does not
include
slaved terminals or virtual terminals).
In a
system that does not
support
multiuser
protection, LOG:
defaults to ALL:.

The Broadcast command displays the message at the
as follows:
dd:month:yr

FROM:ttnn:

specified

terminal

To:TTnn:

message
Examples:
>BRO ALL:SYSTEM WILL SHUT DOWN 4PM TD GPM
)f.3RO

BRO> TT3:PLEASE LOAD DISK1 ON DK3:
>BRO @MESSAGE.CMD

Note:
The Broadcast command uses the write-breakthrough feature of the
terminal driver, a system generation option always generated with
a multiuser protection system.
If the system supports the
feature, the broadcast message, under most circumstances, reaches
all target terminals.
If the system does not support the
write-breakthrough feature, the write defaults to a write virtual
block;
the message cannot break through any type of I/O at the
terminal.

4-25

MCR COMMANDS

BRO (Cont.)
Command Error Messages:
BRO -- COMMAND INPUT ERROR
The BROADCAST task did not receive the command line.
(Usually an indirect file could not be found.) Retry
command.
BRO -- COMMAND SYNTAX
The command line had an improper format.
BRO -- ILLEGAL DEVICE SPECIFIED
The specified device was not a terminal.
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 -- TERMINAL IS BUSY -- ttn:
The message could not be displayed within
at the terminal specified by ttn:.

seconds

4-26

MCR COMMANDS

BYE
BYE:

The Bye command logs the user off a multiuser protection system.
The
system writes a log off message on CO:, displays a terminating message
on the initiating terminal,
aborts any active nonprivileged tasks
belonging to the user,
dismounts volume~ mounted by the user (an
exception is when a privileged user logs off; mounted public volumes
remain mounted), and deallocates the user's private devices (if any).
Format:
BYE

Example:
>BYE

HAVE A GOOD MORNING
25-JAN-78 1o~oa TT15~ LOGGED OFF

Depending on the time of day, the system displays HAVE
MORNING, HAVE A GOOD AFTERNOON, or HAVE A GOOD EVENING.

4-27

GOOD

MCR COMMANDS

CAN
CANCEL
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.
Only a privileged user may issue a Cancel
initiated from the entering terminal.

command

for

task

not

Cancel does not affect execution of a currently active task.
Cancel
removes only the time-based schedule requests still in the queue.
Format:
CAN[CEL] taskname
where taskname is the name of the task.
Example:
>CAN >(KE

Cancel all periodic rescheduling and
requests for task XKE.

4-28

time-based

initiation

MCR COMMANDS

4-29

MCR COMMANDS

4-30

MCR COMMANDS

DEA
DEALLOCATE
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
deallocate only 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 off (issues the
command), the system deallocates all that user's private devices.
If an allocated device has been mounted,
you deallocate the device.

it must be dismounted

Bye

before

Format:
DEA [ LLOCATE]

[ddn:]

where:
ddn:

- The device unit name and number of the
private device
to be deallocated.
If the command does not specify a
device-unit, the system deallocates all private devices
owned by the user logged onto the requesting terminal.

Ex,ample:
>DEALL DK:

Deallocate disk DK:.
The deallocated device can now
or allocated by other users.

4-31

mounted

MCR COMM~DS

DEV
DEVICES
The Devices command displays on the entering terminal the symbolic
names of all device~ or, optionally, all of a particular device type
known to the system. The device names appear in one column;
second
and subsequent columns contain additional information (when necessary)
about each device.
Format:
DEV [ICES]
DEV [ICES]

[dd:]
[/LOG]

where:
dd:

The device unit name to be displayed.

/LOG

Displays all logged on terminals.

whe:f) yot.1. ~pepf~y /LOG. in an RSX-llM-PLUS
£~e< .•.·.· . . ].09:i,p . . and· default. ·UICs.
Alsq,. if
.¢i.f.$f>~17X ,ipc;lµdes the .... ~a~e .. a11d t i111e ... of

·9':1FX"f!l1t:Iy · act

and the first initial

,in q9.er ..

Examples:
RSX-llM systems
>DEl,J
DBO:
DB1:
DB2:
DB3:
DB4:
DKO:
DK1:
DK2:
DK3:
OMO:
OM 1:
ORO:
DR 1:
DSO:
051:
OTO:
DT1:
DT2:
DT3:
D)-(0:
DX1:
LPO:
MMO:
MM1:
TTO:
TT1:
TT2:
TT3:

PUBLIC MOUNTED LOADED TYPE=RPOG
PUBLIC MOUNTED LOADED TYPE=RPOG
PUBLIC MOUNTED LOADED TYPE=RP04
TTGO: - PRIVATE LOADED TYPE=RP04
OFFLINE LOADED TYPE=RP04
TT14: - PRIVATE MOUNTED LOADED
TT22: - PRIVATE MOUNTED LOADED
TT51: - PRIVATE MOUNTED LOADED
TT52: - PRIVATE MOUNTED LOADED
LOADED TYPE=RKOG
TTGO: - PRIVATE LOADED TYPE=RKOG
OFFLINE LOADED TYPE=RM03
LOADED TYPE=RM03
PUBLIC MOUNTED LOADED TYPE=RS04
PUBLIC MOUNTED LOADED TYPE=RS04
LOADED
LOADED
LOADED
LOADED
LOADED
TT14: - PRIVATE MOUNTED LOADED
PUBLIC LOADED
TTGO: - PRIVATE LOADED
TT10: - PRIVATE LOADED
LOADED
LOADED
[31211] - LOGGED ON LOADED
LOADED

4-32

MCR COMMANDS

DEV (Cont.)

TT ll:
TT5:
TTG:
TT7:
TT10:
TT11:
TT12:
TT13:
TT1l!:
TT15:
TT1G:
TT17:
TT20:
TT21:
TT22:
TT23:
TT2l!:
TT25:
TT2G:
TT27:
TT30:
TT31:
TT32:
TT33:
TT3ll:
TT35:
TT3G:
TT37:
TTl!O:
TTl!1:
TTl!2:
TTl!3:
TT Lill:
TTl!5:
TTl!G:
TTl!7:
TT50:
TT51:
TT52:
TT53:
TT5l!:
TT55:
TT5G:
TT57:
TT80:
COO:

[302t310J - LOGGED ON LOADED

LOADED
[30G11l!J - LOGGED ON LOADED
[50125] - LOGGED ON LOADED
[30G150J - LOGGED ON LOADED

LOADED
[71387] - LOGGED ON LOADED
[ 301 t 350 J - LOGGED ON LOADED
E712J - LOGGED ON LOADED

LOADED
LOADED
C7t3G1J - LOGGED ON LOADED

LOADED
[30l!t303J - LOGGED ON LOADED
[30l!tl!J - LOGGED ON LOADED
[301137l!J - LOGGED ON LOADED

LOADED
LOADED
[301 t350J - LOGGED ON LOADED

LOADED
LOADED
[7t71J - LOGGED ON LOADED

LOADED
[30Gt3l!J - LOGGED ON LOADED
[3041307] - LOGGED ON LOADED
[ 301 t 380 J - LOGGED ON LOADED

LOADED
LOADED
LOADED
LOADED
[30l!t8J - LOGGED ON LOADED

LOADED
LOADED
LOADED
LOADED
[7t337J - LOGGED ON LOADED
[ 301 I :n5 J - LOGGED ON LOADED
[30l!115J - LOGGED ON LOADED
[21300J - LOGGED ON LOADED
C7t373J - LOGGED ON LOADED
[308t33J - LOGGED ON LOADED
[70tl!OJ - LOGGED ON LOADED
[3011350] - LOGGED ON LOADED
[303t1J - LOGGED ON LOADED
[30G117J - LOGGED ON LOADED

LOADED

NLO:
TIO:
CLO:
l._BO:
SYO:

LPO:
DBO:
DBO:

>DEt,J

I LOG

TT2:
TTll:
TT8:
TT7:

[312t1J
[302t310J
[308t1l!J
[50t25J

4-33

MCR COMMANDS

DEV (Cont.)
TT10:
TT12:
TT13:
TT14:
TT17:
TT21:
TT22:
TT23:
TT2G:
TT31:
TT33:
TT34:
TT35:
TT42:
TT47:
TT50:
TT51:
TT52:
TT53 :
TT54:
TT55:
TT5G:
TT57 :
TTGO:

[308150]
[71387]
[3011350]
[ 7 I 2]
[71381]
[304 1303]
[304 14]
[3011374]
[3011350]
[7 171]
[30G 134]
[304 1307]
[3011380]
[304 18]
C71337J
[3011335]
[304 '15]
[21300]
[71373]
[308133]
[70 140]
[3011350]
[30311]
[308117]

RSX-llM-PLUS systems
>DEt,J DB:
DBO:
PUBLIC MOUNTED LOADED LABEL=11MDEV TYPE=RP08
DB1:
PUBLIC MOUNTED LOADED LABEL=LISTING TYPE=RPOG
DB2:
TT57: - PRIVATE MOUNTED LOADED FOREIGN TYPE=RPOLI
DB3:
PUBLIC MOUNTED LOADED LABEL=RSX11MPBL4 TYPE=RP04

>
>DEt,J /LOG
TT17:
[30313]
[7 124]
TT20:
TT23 :
[7130]

[303 13] 14-FEB-78
[7 124]
14-FEB-78
[7130]
14-FEB-79

18:30
18:35
18:28

G
0
2

A,
G,
F,

ROBERTS
MATT
MICHEALS

The following notes describe the messages that can appear in the
subsequent columns.
More than one message can appear on the same
line.
•

MOUNTED indicates that the device is mounted.
If a privileged
user issues the command,
the display includes the mounted
volume's label.

•

PUBLIC indicates that the device has been set public.

•

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.

4-34

MCR COMMANDS

DEV (Cont.)
indicates that, although
• OFFLINE
entries for this device,
the

the system tables contain
host configuration does not

contain the related device.
•

[uic] LOGGED ON indicates that the user
identified
(the protection UIC) has logged onto the terminal.

•

LOADED indicates that a loadable device
loaded.

currently

•

UNLOADED indicates that a loadable 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.

driver

[uic]

name in the second column followed by the text
• A"- terminal
PRIVATE" indicates that the device named in the first
column has been allocated to
terminal in the second column.

4-35

the

user

logged

the

MCR COMMANDS

OMO
DISMOUNT
The Dismount command requests the file system to mark the volume
volume
dismount and release the control blocks.
Marking a
After
dismount denies additional files access to the volume.
files accessed on the volume are deaccessed, the ACP releases
control blocks and thus completes the dismount operation.

for
for
all
the

If a single user has mounted a volume, the Dismount command declares
the volume
logically offline.
In an RSX-llM-PLUS system, the volume
cannot be accessed until it is mounted.
In an RSX-llM system,
since
there is no Ancillary Control Processor (ACP) associated with the
unmounted volume, only specific tasks (such as INI, DSC, and BAD)
are
granted private access.
If multiple users have mounted a volume, the
volume remains accessible until all users have dismounted it.
When the dismount operation completes,
either through the Files-11
disk system or the ANSI magnetic tape system, the command prints the
message

*** dev:

DISMOUNT COMPLETE

on the console terminal (CO:).
There may be a considerable delay
between the
issuance of the command and the printing of this message
if a number of I/O requests are pending and/or a number of files are
accessed on the volume.
When Dismount completes its processing, it
immediately prints on the issuing terminal the device from which the
user has dismounted without waiting for I/O run down or file
deaccessing.
Nonprivileged users can only dismount volumes that they themselves
have mounted.
A privileged user can dismount any mounted volume.
In
RSX-llM-PLUS systems, you cannot dismount a volume on a shadow device;
you must first stop shadow recording.
Format:
>OMO ddn:

[label]

[/keyword (s)]

or
>OMO /USER [keywords]
Keywords:
/DEV
/USER
/TERM=ttnn:
/LOCK
where:
ddn:

Device-unit
dismounted.

volume-label -

The Files-11 volume label may be up to twelve
characters in length for disk and DECtape, and up
to six characters for magnetic tape.

that

4-36

holds

the

volume

MCR COMMANDS

OMO (Cont.)
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).
Keyword Definitions:
DEV

/DEV.
Privileged keyword.
This keyword dismounts all
users
from a
specific device.
In RSX-llM-PLUS, the
volume cannot be accessed;
in RSX-llM, the volume cannot
be accessed by an ACP.

USER

- /USER. This keyword dismounts all volumes
has mounted.

TERM

- /TERM=ttnn:.
all volumes
mounted.

that

user

Privileged keyword.
This keyword dismounts
that a user at a specified terminal has

4-37

MCR COMMANDS

OMO (Cont.)
~:

.. ;, .: . . .,,

p:i.¥

specify /LOCK=H. J9.r. d~sJ($ 1 :
·'?p·~~ID~<,.· y~Jl4 ..... J~nd,
if.. tl1e.4.rJv.~ . .• J?~p~pr:t~. t~Et
,~HPS.~Jpn,. >P()\tl~r:s.·· .dpV/[lJ:h~.... dl9K ..... W:h~n .r9µ:.§p~p~;y·(~·~.·

\A]h~·!l Y2':1

·E·B:~j·•• ,~.~R~.~r'···. ·.· · .Pi smount. ·r:~.\tl in<I~ . . .·.Cln<i . .•. . JJJtlc>a~s ··.t.h~.,. p·~ . ·.<< . .·. . .
>6t~>tlgn ~n~Jbit.s acces;s . .· t2·.~.J;l).~ .4\~§K..... !.b~ .1f.p('.;.. :'ij··· <:qP:t~
· · · ·g~fciµ+~. · loc~ . . Y~.:L.!J.~.... tc>J ~;LJ. Y()lJJJU~t?·.. ~.m9,µ.p~~~}~·~t..·
... ,.
. ~·i·····~.<;.r... 'rhe .•.9~.~@. :L.,...Pr:e>s.!slY.r~ ... :.~lt.~.r:.:.· ...g. i.~.1Jl9. ~:Q.~. :~.:~:g.· .v~·2 . ·
. :;:·;~9
.that .u.se.s a .B.~~9d~J.? ~CJ?. J§~:J;Q . ::$·:20·t2·t~%i~i~f'r;;;;;i~:~:
Examples:
>DMD DK1:AMBER

Dismounts disk DKl:. 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.

.Al\,

>DMD DK 1: /DEt,J

Places the volume
in Drive
releases all control blocks.

DKl:

logically

offline

and

>DMD /USER/TERM=TT17:

Dismounts all volumes mounted by terminal TT17:.
Command Error Messages:
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 -- NO VOLUME LIST
The command specified a magnetic tape drive for
a mounted volume label list does not exist.

which

DMO -- SHADOW RECORDING IS ACTIVE ON ddnn:
In an RSX-llM-PLUS system,
the command specified a
shadow device.
Shadow devices cannot be dismounted;
first stop shadow recording and then reenter the
command.
DMO -- VOLUME NOT MOUNTED

,/ \v I

The specified device was not mounted.

4-38

MCR COMMANDS

OMO (Cont.)
DMO -- VOLUME NOT MOUNTED BY TI:

The command specified a dismount operation for a
volume that was not mounted from the issuing terminal.
DMO -- WRONG VOLUME LABEL

The volume label and
command did not match.

4-39

the

label

specified

the

MCR COMMANDS

FLA
GROUP GLOBAL EVENT FLAGS
The Flags command creates, eliminates, or displays group global event
flags.
Group global event flags provide each UIC 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 Executive Reference Manual).
However,
0nly those
tasks
running under the same group UIC can modify group global event
flags.
Nonprivileged users can only create or eliminate
flags for their login group UIC.

gro~p

global

event
for

Privileged users can create or eliminate group global event flags
any group.
Format:
>FLA [GS]

[ggg/keyword]

where:
ggg

- Represents the group for which the group
flags are to be created

global

event

keyword - Specifies whether the group global event flag is to
created or eliminated

Keywords:
CRE

- /CRE. This keyword creates group
for the specified UIC group.

global

event

flags

ELIM

- /ELIM. This keyword eliminates group
flags for the specified UIC group.

global

event

the

command

If you omit the group number and keyword specification,
displays all the group global event flags in the form:
access count

ggg
where

[DEL]

event flags

[DEL]

indicates group global event flags marked for delete.

Examples:
>FLA 303/CRE

Creates group global event flags for all tasks running under
group number 303.

the

UIC

the

UIC

>FLA
303 1 000010 000000

Displays the access count and event flags set
group 303.

for

>FLA 303/ELIM

Eliminates group global event flags for UIC group 303.

4-40

MCR COMMANDS

HEL
HELLO
The Hello command logs a user onto a terminal to gain access to a
multiuser protection system.
Before a user logs in, the system
rejects all MCR commands except Hello 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 accounting file.
If the password matches the name or UIC
supplied, the system:
the
• Sets
according

terminal to privileged or nonprivileged status
to the user's UIC (a privileged user has a group
number less than or equal to 10(8))

the login logical-device name SYO:
to the
• Assigns
system disk (the disk that contains the user's files)

user's

the user's login UIC, which is the initial default
• Establishes
UIC
•

Records the current time and date and other information
the terminal session in the system file

about

Displays a system identification, the current
time the user logged onto the terminal
•

Optionally displays the contents of the file LB:[l,2]LOGIN.TXT
(you can suppress part of the display by typing CTRL/O)

•

Submits SY:[login uic]LOGIN.CMD to MCR if it is present

•

Displays the default prompt

Formats:
In the following command formats, the braces indicate
enters one of the two parameters.
•

>HEL[LO]

{uic
} /password
username

>HEL[LO]
~
• ACCOUNT
OR NAME:
PASSWORD:

•

>HEL[LO]
PASSWORD:

password

uic
}
{ username
~

{~!~rname} ~
password

4-41

that

the

user

MCR COMMANDS

HEL (Cont.)
where:
uic

The user's User Identification Code
command
allows
the
following
representations:

(UIC).
four

The
UIC

g,m
[g, m]

g/m
[g/m]
To suppress part of the display of the file
LB:[l,2]LOGIN.TXT,
use the slash form (that is,
g/m or [g/m]).
The variables g and m are octal numbers from 1 to
377 that
represent group and member numbers,
respectively.
username
password

The user's last name,
place of a UIC.

which

can

entered

- An alphanumeric password.
If you
type
the
password in response to the prompt PASSWORD:, the
system does not display the typed characters.

If the HELLO command was successful, the system displays the following
message:
system i.d.
greeting
dd-mm-yy hh:mm LOGGED ON TERMINAL ttnn:

xxxnnnn

[login-text]
where:
i. d.

is one of the following, depending on the system:
RSX-llM-PLUS VOl BL6 MULTI-USER SYSTEM
RSX-llM BL26 MULTI-USER SYSTEM

greeting

- One of the following greetings, depending
time of day:
GOOD MORN ING
GOOD AFTERNOON
GOOD EVEN ING
GOOD NIGHT

dd-mm-yy

- The current date.

4-42

the

MCR COMMANDS

HEL (Cont.)
logi n·-text

- The contents of the .file LB:[l,2]LOGIN.TXT.
The
system displays the contents of this file as
follows.
If you use the
slash
form
when
specifying the UIC, the display concludes at the
first percent sign (%) in the file at the
initial
login for that user.
Subsequent logins by that
user (using the slash form)
do not display the
contents unless LOGIN.TXT has been edited.
If you
do not use the slash form, the system displays the
entire file.
(Note that you can type CTRL/O to
discard all text after the first percent sign in
LOGIN.TXT.)
If this file does not exist, the
message MESSAGE FILE ERROR -26 is displayed.

Examples:
The following examples are from an RSX-llM system.
>HEL
ACCOUNT OR NAME:
PASSWORD:

AMBER

RS)<-11M BL2G

MULTI-USER SYSTEM

GOOD MORNING
2-FEB-79 10~03 LOGGED ON TERMINAL TT20:
2··-FEB--nl

*** NEW DISK CONFIGURATION ***
DBO: SYstem and User disk

(User typed

~rnw0

to stop output.)

>HEL [301/3G5J /BOB
f·<S>(--11M BL2G

MULTI-USER SYSTEM

GODO MClF?N I NG
2-FEB-79 10:08 LOGGED ON TERMINAL TT20:
>HEL. 301/385
PA!3Sl,,j0f?D:
RS>(-. 11M f:H . 28

MULTI-USER SYSTEM

GDOD MORNING
3-FEB-79 09:45 LOGGED ON TERMINAL TT17:

>
>HEI... 301 ,395 /BOB
RS>< ·-11 M BL2G

MULTI-USER SYSTEM

4-43

MCR COMMANDS

HEL (Cont.)
GOOD MORNING
3-FEB-78 08:45 LOGGED ON TERMINAL TT17:
2-FEB-78

*** NEW DISK CONFIGURATION ***
>
(User typed

(cTRL/o) )

Command Error Messages:
HEL -- ACCOUNT FILE OPEN FAILURE
or the
The account file was open for another user;
disk containing the account file was not mounted.
Retry the command.
HEL -- ACCOUNT FILE RECORD(S) LOCKED
An
RSX-llM-PLUS
error
message.
The
resource
accounting system or the ACNT program could not access
an account record. Retry the command.
HEL -- CANNOT ALLOCATE UAB
An
RSX-llM-PLUS
error
message.
The
resource
accounting system requires space in secondary pool to
allocate a User Account Block
(UAB).
If sufficient
space
is
not
available
in
secondary
pool,
nonprivileged
users
cannot
login.
(Resource
accounting accepts a switch,
/POOL RESERVE,
that
permits the system manager to alter the secondary pool
limit.
See the RSX-llM-PLUS System Generation and
Management Guide for complete details.)
HEL -- COMMAND INPUT ERROR
A system directive or the RUN command, rather than the
HELLO command, has initiated the HELLO task.
HEL -- INVALID ACCOUNT
The name or UIC specified in the command is not stored
in the account file;
or the password specified does
not match the name or UIC given.
HEL -- LOGINS ARE DISABLED
The system was in the process of shutting down;
or
the command SET /NOLOGON has been issued. A user
cannot log onto a terminal at these times.

4-44

MCR COMMANDS

HEL (Cont.)
HEL -- MESSAGE FILE ERROR nnn.
The system could not open the file LOGIN.TXT for a
reason
indicated by the FCS code nnn. See Appendix I
of the IAS/RSX-11 I/O Operations Reference Manual for
a definition of the FCS code.
HEL -- OTHER USER LOGGED ON
Another user was currently logged onto the
issuing
terminal.
Only one user at a time can be logged onto
a terminal.

HEL -- TERMINAL ALLOCATED TO OTHER USER
The issuing terminal was allocated to another user. A
user cannot log onto a terminal allocated to someone
else.

4-45

MCR COMMANDS

HELP
HELP
In an RSX-llM system, the Help command displays the contents of
the
file
[l,2]HELP.HLP at the
issuing terminal.
In an RSX-llM-PLUS
system,
the Help command displays
the contents
of
the
file
[l,2]MCR.HLP or
[l,2]DCL.HLP at the issuing terminal.
Help is the
only MCR command that you can issue without logging on.
The display
usually contains
information on how to log onto the terminal;
but
each installation can change the contents of its Help file
to suit
specific needs.
Note that you must type all four letters to distinguish Help from
Hello command.

the

The general format for the Help command is:
HELP [/CLI]

[qualifier]

[qualifier2]

[...

qualifier9]

··\~·r::~e~i.~·~ai·:•·i<·•~.~·~·~·r~ ···:·t:·6~~+····~1i~·6·~·.~·· a•·.~·1
2

.fUef . .•. . . .'l'.h~ ·. ·~~Xvie>:r.ais . va.lf<:] in RS~'""lJM~J;">r..p:s; <~

. 9E9 v·'!:1.l1e~. ··~C>( . /C,LI .... ~.re l'M¢~, w~tch:·~tlf~
~¥~9~Rt·. . J~.~ . . .·. 9~fau·lt .is /MCR • I.·;·. · .•.¥~()\'. :·~ieLiJt :0

' •......)r . ~~.!~.~..•. 9.~r~c~.~ . Hell'. . . ~() o9~~~~~"· . . . . . :~J.i·¥?~ .

't:he ·idefault is /DCL.

· ··

Another form of the HELP command displays the text
HELP file of the user.

contained

the

displays

the

Format:
HELP % [qualifierl]

[qualifier2]

The user must be logged on to request
contents of [current UIC] HELP .HLP.

[ ••• qualifier9]
HELP %.

HELP %

The form of the HELP.HLP file is:
1

UPPER-CASE-QUAL
Text displayed if you type HELP UPPER-CASE-QUAL.

UPPER-CASE-QUALl
Text
displayed
UPPER-CASE-QUALl.

you

type

HELP

UPPER-CASE-QUAL

UPPER-CASE-QUAL2
Text
displayed
UPPER-CASE-QUAL2.

you

type

HELP

UPPER-CASE-QUAL

ANOTHER-UPPER-CASE-QUAL
Text displayed if you type HELP ANDTHER-UPPER-CASE-QUAL.

The numerals are
level numbers and
range from one through nine
inclusive.
Level numbers must be the first character of their line
and the qualifiers that follow must be upper case.
Arbitrary strings
of blanks or tabs are allowed between level numbers and qualifiers.
If a qualifier begins with a dollar sign ($) or a slash (/), the $ or
I is ignored.

4-46

MCR COMMANDS

HELP (Cont.)
HELP interprets its command line in a strictly nested fashion.
When
interpreting parameters (qualifiers), Help searches the HELP file for
a line containing a
level number one followed by the specified
qualifier.
If such a line exists, Help displays the subsequent text
until it reaches another level number.
If you specify more
than one
qualifier,
Help searches for
a
line containing a level number one
followed by the first qualifier and then continues the search
for
a
level number two followed by the second qualifier.
(Note that the
search for level number two and the second qualifier stops
if Help
encounters a level number less than two.) If such a line exists, Help
displays the subsequent text until it encounters another level number.
The correspondence of qualifier position in the Help command line with
level numbers in the HELP file continues until the last qualifier
is
found.
Help permits references within the HELP file
to other files
that
contain large blocks of text and/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 non-blank character on a line followed by a file specifier.
For
example:
@f ilespec
where filespec is any legal RSX file specifier.
The default
filetype
is .HLP. However, if you specify a filetype other than HLP, Help uses
the specified filetype as the default
in
succeeding
indirect
references.
For example, if you specify @filename.
.TXT, Help uses
TXT as the default
filetype
in future
indirect
references;
the
default filetype corresponds to the last specified filetype.
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:
1 EXAMPLE
@HELPEXAMPLE
then HELPEXAMPLE.HLP can only contain level numbers greater
(the numerals 2-9 inclusive).

than

one

Help also allows you to share text between two or more similar or
synonomous qualifiers
in the HELP file.
To do this, specify a pound
sign (#) followed by the similar qualifier as the
first
non-blank
character on a
line.
For example, to relate the qualifiers LOG and
HELLO, the HELP file would contain the following lines:
1 LOG

#HELLO
1 HELLO
See Benn Still for an account and password.

4-47

MCR COMMANDS

HELP (Cont.)
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.
The following is an example of a HELP file.
The general form of the HELP command is:
HELP [qualifierl]

[qualifier2]

[ ••• qualifier9]

This displays text from the system help file.
The other general form of the HELP command is:
HELP % [qualifierl]

[qualifier2]

[ ••• qualifier9]

This displays information from a local (private) help file.
syntax is not legal until you are logged in.

This

1 LOG
#HELLO
1 SPELLING
Type HELP SPELLING DICTIONARY followed by
want to spell.

the

word

you

2 DICTIONARY
The file DICTIONARY.TXT (which is NOT included in this
example)
contains an abridged listing of
frequently
misspelled words.
@DICTIONARY
1 HELLO
See Benn Still for an account and password.
1 CREATE
NOTE
When creating a HELP file,
the first
line should be blank since it is not
displayed.
By convention, each line should begin with a blank or
tab;
the lines cannot begin with the digits l through 9
since these would be interpreted as level numbers.
Also,
depending
upon
the
types
of
devices
in
your
configuration,
some practical restrictions should be
imposed.
For example,
to accommodate VTOSBs, lines of
text should not be more than 72 decimal characters long,

4-48

MCR COMMANDS

HELP (Cont.)
and a block of text should not be more than 20 decimal
lines.
If there are level n+l qualifiers
(like 2
UPPER-CASE-QUAL above), they should be mentioned
in
the
text so that they are known to exist.
Similarly, level
one qualifiers should be added to the text displayed when
only HELP is typed.
If the system contains the above HELP file,
the following
is the
display
in
response to HELP L.
(Note that a qualifier may be
specified by the fewest initial characters that unambiguously define
it. )
>HELP L
See Benn Still for

an account and Password.

Command Error Messages:
HEL -- AMBIGUOUS QUALIFIER
The qualifier does not specify a unique part of the Help
file.
Further
information must be supplied.
Examine the command line
that Help displayed below the error message and specify the
last
qualifier displayed more completely.
HEL -- AMBIGUOUS SYNONYM
The HELP
file
attempted to share text
between
synonomous
qualifiers,
but the qualifier
referenced as a synonym was not
distinct.
HEL -- IMPROPER HELP FILE FORMAT
The Help file is not in proper format and cannot be used.
edit the file or re-enter it in proper format.

Either

HEL -- INDIBECT FILE OPEN ERROR
Help attempted to reference another file from within
file, but Help could not open the indirect file.

the

HELP

HEL -- INDIRECT FILE SYNTAX ERROR
Help encountered a syntax error either in a reference to
file or in the indirect file itself.

another

HEL -- MESSAGE FILE ERROR nnn
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.
HEL -- SYNONYM NOT FOUND
The Help file referenced a synonym, but the file did not
it.

4-49

include

MCR COMMANDS

HELP (Cont.)
HEL -- SYNTAX ERROR
An error in the command format occurred.
HEL -- UNKNOWN QUALIFIER
The Help file does not contain the last qualifier printed in
display of the command line below the error message.

the

4-50

MCR COMMANDS

INI
INITVOLUME
The Initialize Volume command produces a Files-11 volume (see Section
3.1)~
On disk and DECtape,
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, the
command writes a volume label according to the ANSI standard and a
dummy file that destroys all existing files.
In multiuser protection systems, a user can initialize a volume only
on allocated,
private devices
(that is,
a device the user has
allocated).
In RSX-llM systems that do not support
multiuser
protection, a user must be privileged to initialize a volume.
Selecting appropriate values for the command parameters
requires an
in-depth
knowledge
of Files-11.
Refer to the IAS/RSX-11 I/O
Operations Reference Manual for details of the Files-11 disk and ANSI
magnetic tape structure.
Format:
INI[TVOLUME] ddn:volume-label[/keyword(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
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 512.
characters.
Keywords:
/BAD=[option]
/CHA=[characteristics]l
/DENS=density selection
/gXT=block-count
/FPRO=[system,owner,group,world]
/INDX=index-file-position
/INF=initial-index-file-size
/LRU=directory-preaccess-count
/MXF=f ile-count
/PRO=[system,owner,group,world]l
/UIC=[group,member]l
/WIN=retrieval-pointer-count
/VI
1 This keyword is included for RSX-llD compatibility.
built on RSX-llM can be mounted on an RSX-llD system.

4-51

Thus,

volumes

MCR COMMANDS

INI (Cont.)
(/DENS is the only keyword valid for initializing a magnetic tape
volume.)
where:
ddn:

- Device-unit name and number of the
initialized.

volume

volume-label - The volume label.
This may be
up to twelve
characters
in length for disk and DECtape, and up
to six characters in length for magnetic tapes.
The label
identifies the volume and must be
specified.
BAD

- /BAD=[option]. The keyword /BAD
indicates that
bad-block processing is to be
included in the
volume initialization.
Consequently,
bad blocks
on the volume will be marked as in-use and cannot
be allocated to files.
The brackets surrounding each option are
syntax.
The options are:

required

[MAN]

- Accept
a
bad
block
list
specified from the terminal.

[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
lo cat o r u t i l i t y (BAD ) •

[NOAUTO]

- Ignores
the
bad-block
descriptor file and performs 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
(DL:,
DM:, and DR:).

4-52

-·--~.

MCR COMMANDS

INI (Cont.)
[OVR,MAN]

- Override the manufacturers bad
block
descriptor
file
and
accept blocks specified from
the terminal.

If the command specifies
[MAN],
prompts for bad blocks as follows:

the

program

INI>LBN (S) =
Bad blocks may then be entered in the format:
blocknum:number
where:
blocknum specifies the bad block number
number specifies the number of sequential bad
blocks beginning at blocknum
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
number and omit the colon.

block

You can also specify a sequence of bad blocks as
well as a
single bad block on the same command
line.
For example, the command line:
INI>LBN(S)=l00:2,3,200:100,45:1
enters blocks 100, 101, 3, 200 through 299, and 45
as bad blocks.
You can separate bad block series
with a space, tab, or comma.
A null line (a carriage return 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, type

(cTRLJz)

or~.

The default is BAD=[AUTO].
INI
obtains
the bad
block
information from a
factory-recorded bad
block descriptor file, located on the
last track
of an RK06, RLOl,
or RM03 disk.
Note that INI
also searches the
last track
for a
bad block
descriptor file created by the BAD utility.

4-53

MCR COMMANDS

INI (Cont.)
CHA

- /CHA=[characteristics]. The characteristics words
are ASCII strings separated by commas. The square
brackets are required syntax.
For the Initvolume
command, two characteristics are defined:
- ATTACH/DETACH
(device can be
used
by one task or group
for
exclusively);
included
This
RSX-llD
compatibility.
characteristic is not used by
RSX-llM/M-PLUS.

[ATCH]

Default:
[DCF]

- Device Control Functions are
permitted;
included
for
RSX-llD compatibility.
This
characteristic is not used by
RSX-llM/M-PLUS.
Default:

[ATCH,DCF]

DENS

no Attach/Detach.

no DCF.

the
above
Select both
of
options;
included for RSX-llD
This
compatibility.
characteristic is not used by
RSX-llM/M-PLUS.

- /DENS=bit-density.
The /DENS keyword sets the bit
density
(Bits Per Inch or BPI) of a magnetic tape
loaded on either a TU16 or TU45 tape drive.
The
drive must be capable of writing in either single
density (800 BPI) or double density
(1600 BPI).
Acceptable keyword values are:

/DENS=l600
/DENS=HIGH
/DENS= LOW
Default:

/DENS=800.

The /DENS keyword also functions
to check
the
density of a floppy disk in an RX02 drive, or of a
tape on a TS04 drive.
If /DENS is specified,
the
drive density
is compared against the keyword
value for consistency.
If /DENS is not specified,
no consistency check is performed and the media is
initialized at its current density.
EXT

- /EXT=block-count.
The /EXT keyword specifies the
number of blocks by which a file is to be extended
when the file has exhausted its allotted space.
Default:

/EXT=S

4-54

MCR COMMANDS

INI (Cont.)
FPRO

- /FPRO=[system,owner,gtoup,world].
The
/FPRO
keyword specifies the default protection for all
files created on the volume being initialized.
Access codes consist of four 4-code groups in the
Access Rights word as follows:
R
W
E
D

Read
Write
Extend
Delete

In each instance, the absence of
the code means
that the user
is denied the access right.
The
square brackets are required syntax.
Specify an asterisk (*) in the access rights word
to force the default value for a specific group.
Default:

/FPRO=[RWED,RWED,RWED,R].
NOTE
Protection
code
subparameters
(system,
owner,
group,
world)
are
positional.
That is, the location of
the word
in the parameter string
defines the user to whom the code
applies.
The order is:
system, owner, group, world

INDX

- /INDX=index-file-position.
The
/INDX
keyword
specifies the
index file
logical block number.
This 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
in order to minimize access time.
Four
possibilities are available:
BEG

- Place the index file at the beginning of
the volume.

MID

- Place the index file at

the

middle

the volume.
END

- Place the index file at the end

the

volume.
BLK:nnn - Place the index file
block number.

the

specified

Default:
/INDX=MID (disk devices), /INDX=BEG
(DECtape , TU 5 8 )

4-55

MCR COMMANDS

INI (Cont.)
INF

- /INF=initial-index-file-size.
The /INF keyword
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 000000.DIR, are not
included in
the value for /INF.
Defaults
DECtape
RK05
RK06
RK07
RF
RLOl
RL02
RM02/03
RS03/04
RP02
RP03
RP04/05
RP06
RXOl
RX02

LRU

- /LRU=FCB-count.
The number of directory File
Control Blocks
(FCBs)
kept in memory by the ACP
per volume.
These FCBs control access to User
File Directories (UFOs).
The more FCBs in memory,
the faster a UFO file can be found.
If the file
is in a directory for which the FCB is resident,
much of the overhead required to
open
the
directory is bypassed. Thus, the time required to
perform directory operations and
open
files
decreases as the number of FCBs increases.
Default:

MXF

16
147
834
1654
16
314
629
4049
16
1230
2460
5283
10478
16
16

/LRU=3

- /MXF=f ile-count. The /MXF keyword specifies the
maximum number of files
(file headers
in the
volume's index file) permitted on the volume. The
value for /MXF includes the five system files and
must be less than or equal to the number specified
for the device in the table below:
Theoretical Maximums
DECtape
RK05 Disk
RK06 Disk
RF Disk
RLOl Disk
RM03 Disk
RS03 Disk
RS04 Disk
RP02 Disk
RP03 Disk
RP04/05 Disk
-RP06 Disk
RXOl
RX02
4-56

278
2357
13344
499
5034
25600
499
1003
19680
25600
25600
25600
238
481

·~.

MCR COMMANDS

INI (Cont.)
Defaults
DECtape
RK05 Disk
RK06 Disk
RF Disk
RLOl Disk
RM03 Disk
RS03 Disk
RS04 Disk
RP02 Disk
RP03 Disk
RP04/05 Disk
- RP06 Disk
RXOl
RX02

34
294
1668
62
629
8099
62
125
2460
4920
10567
20596
29
60

NOTE
A Files-11 volume requires
five
files
INDEXF.SYS, BITMAP.SYS,
BADBLK .SYS,
CORIMG .SYS,
and
000000.DIR -- to create the on-disk
structure (See Appendix E of the
IAS/RSX-11 I/O Operations Reference
Manual).
Thus, MXF value must be
computed by the maximum number of
user UFD's and files plus the five
files
required for the Files-11
structure.
- /PRO=[system,owner,group,world]. The /PRO keyword
specifies volume access rights.
Access codes
consist of four 4-code groups in the access rights
word, as follows:
R
W
E
D

Read
Write
Extend
Delete

In each instance, the absence of the code means
that the user is denied the access right.
The
square brackets are required syntax.
Specify an asterisk (*) in the access rights word
to force the default value for a specific group.
Default:

[RWED,RWED,RWED,RWED].

1 RSX-llM/M-PLUS does not protect a volume at the UIC level.
It does,
however,
prevent direct access to mounted volumes by nonprivileged
tasks.
This feature permits volume interchangeability with RSX-llD.

4-57

MCR COMMANDS

INI (Cont.)
NOTE
Protection
code
subparameters
(system,
owner,
group,
world) are
positional. That is,
the location
of ,the word in the parameter string
defines the user to whom the code
applies.
The order is:
system, owner, group, world
UIC

- /UIC=[group,member].
Keyword
for
the
UIC
parameter specifying the owner of the volume.
Legal group and member numbers
range from 1 to
377(8). The square brackets are required syntax.
Default:

WIN

- /WIN=retrieval-pointer-count.
The /WIN keyword
specifies the number of mapping pointers to be
allocated for file windows.
A
file
window
consists of a number of mapping pointers;
it is
stored in memory when the file
is opened.
(See
Appendix
F in the IAS/RSX-11 I/O Operations
Reference Manual for a description of a mapping
pointer.)
Default:

/UIC=[l,l]

/WIN=7.

/VI. The /VI keyword lists all INI
keywords
their values on the issuing terminal.

and

Example:
>INI DK1: ICTSl,IOL2/UIC=[215J/IND>(=BEG/FPRO=CRWED 1RWE 1RW 1RJ illIT)

The Initvolume parameters in the example above are:
DKl:

- Device-unit

ICTSVOL2

- Volume-label

/UIC

- User
identification code
owner:
group=2, member=5

/INDX=BEG /FPRO

the

volume

Index file location, forced to beginning of
volume

- Default file protection, specified by group
as:
system:
owner:
group:
world:

Read,Write,Extend,Delete
Read,Write,Extend
Read, Write
Read-only

4-58

MCR COMMANDS

INI (Cont.)
Command Error Messages:
INI -- ALLOCATION FOR SYS FILE EXCEEDS VOLUME LIMIT
The system was unable to allocate a system file
from
the specified block because of intermediate bad blocks
or end of volume.
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.
INI -- BAD BLOCK FILE FULL
The disk had more than 102 bad regions on it.

"-"'

INI -- BAD BLOCK HEADER I/O ERROR
An error was detected in
file header.
INI -- BLOCK(S)

writing

out

the

bad-block

(or blocks) exceeded the

physical

EXCEED VOLUME LIMIT

The specified block
size of the volume.
INI -- BOOT BLOCK WRITE ERROR

An error was detected in writing out the
block.

volume

boot

INI -- CHECKPOINT FILE HEADER I/O ERROR
An error was detected in writing
file header.

out

the

checkpoint

INI -- COMMAND I/O ERROR
This message indicates that INI encountered
error while reading the command line.

I/O

INI -- COMMAND TOO LONG
The command, including continuation lines,
the maximum length of 512.
characters.

exceeded

INI -- DATA ERROR
The command specified a bad-block number or contiguous
region that was too large.
INI -- DEVICE NOT ALLOCATED TO THIS TERMINAL - ddnn
The command line specified a private device that
allocated to other than the issuing terminal.

'--''
4-59

was

MCR COMMANDS

INI {Cont.)
!NI -- DEVICE NOT IN SYSTEM - ddnn
The command line specified a device not in the current
system configuration.
IN! -- DEVICE NOT READY - ddnn
The command specified a volume that was not ready
up to speed).

(not

IN! -- DEVICE WRITE LOCKED - ddnn
The command specified a volume that was write-locked
and therefore could not be initialized as a Files-11
device.
IN! -- DISK IS ALIGNMENT CARTRIDGE

·~.!

The last track on an RK06, RLOl,
or RM03
identified
the volume as an alignment cartridge, which cannot be
initialized as a Files-11 volume.
An
alignment
cartridge is specifically formatted for aligning disk
read/write heads.
!NI -- DRIVER NOT LOADED
The command line specified a
driver has not been loaded.

device

for

which

the

!NI -- DUPLICATE BLOCK(S) FOUND
A block that had already been defined as bad was being
defined as bad a second time.
IN! -- FAILED TO ATTACH DEVICE - ddnn
!NI could not attach the specified device.
IN! -- FAILED TO READ BAD BLOCK FILE
The command was
information from
RM03 disk.

unable to read the
bad
block
the last track of an RK06, RLOl, or

IN! -- FAILED TO READ MANUFACTURER'S BAD SECTOR FILE
A disk read hardware error occurred while attempting
to
read the factory-recorded bad block data on a
last-track device.
Reenter the command and
include
the OVR option.
!NI -- FAILED TO READ SOFTWARE BAD SECTOR FILE
The software-detected bad sector file could not be
read.
Reenter the command and include the OVR option.

4-60

~--------------------------------------------------------------------------------------------

MCR COMMANDS

INI (Cont.)
INI -- HOME BLOCK ALLOCATE WRITE ERROR
In overwriting a bad-home-block area,
occurred.

write

error

An error was detected in writing out the
block.

volume

home

INI -- HOME BLOCK I/O ERROR

INI -- ILLEGAL KEYWORD VALUE
A value entered for a keyword exceeded its limits.
INI -- ILLEGAL UIC
The command line specified an illegal UIC.
INI -- INDEX FILE BIT MAP I/O ERROR
An error was detected in writing
bit map.

out

the

index-file

out

the

index-file

INI -- INDEX FILE I/O ERROR
An error was detected in writing
header.
INI -- I/O ERROR SIZING DEVICE - ddnn
The system encountered an I/O error
RFll disk.

while

sizing

INI -- MAGTAPE LABEL MUST BE SPECIFIED
The command attempted to initialize a magnetic
without specifying the required volume label.

tape

INI -- MAGTAPE DEVICE ERROR - ddnn
While positioning the magnetic
encountered an I/O error.

tape,

the

system

tape,

the

system

INI -- MAGTAPE WRITE ERROR - ddnn
While writing to the magnetic
encountered an I/O error.
INI -- MANUFACTURER'S BAD SECTOR FILE CORRUPT
The factory-recorded bad block data on a
device
is in an inconsistent format.
command and include the OVR option.

last track
Reenter the

INI -- MFD FILE HEADER I/O ERROR
An error was detected in writing out the
Directory (MFD) file header.

4-61

Master

File

MCR COMMANDS

INI (Cont.)
!NI -- MFD WRITE ERROR
An error was detected in writing out a
Master File Directory (MFD).

block

the

IN! -- 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.
!NI -- NOT FILE STRUCTURED DEVICE
The system does not support Files-11 on the
device.

specified

!NI -- NULL FILE HEADER I/O ERROR
An error was detected in writing out null-file headers
to the index file.
IN! -- PUBLIC DEVICE - ddnn
The command line specified a public
private devices can be initialized.

Only

device.

!NI -- STORAGE BITMAP FILE I/O ERROR
An error was detected in
allocation file header.

writing

out

the

storage

IN! -- UNDEFINED DENSITY SELECTION
The command specified an illegal density value.
!NI -- UNIT DOES NOT SUPPORT 800 BPI
The command specified a drive that
800 BPI.

does

not

support

!NI -- UNIT DOES NOT SUPPORT 1600 BPI
The command specified
support 1600 BPI.

tape

drive

that

does

not

The command specified a device for which the High
Low keywords are undefined.

and

!NI -- UNIT DOES NOT SUPPORT HIGH/LOW DENSITY SELECTION

4-62

MCR COMMANDS

INI (Cont.)
IN! -- UNIT DOES NOT SUPPORT DENSITY SWITCH
The command specified a device
multiple density capability.

which

does

not

have

IN! -- UNIT IS NOT AT LOW DENSITY
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.
IN! -- UNIT IS NOT AT HIGH DENSITY
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.
IN! -- VOLUME MOUNTED FILES-11
An attempt was made to initialize a mounted Files-11
volume.
Mounted
Files-11
volumes
cannot
be
initialized.
IN! -- VOLUME MOUNTED FOREIGN WITH ACP
The command line specified a device that was mounted
foreign,
but with an ACP. To initialize a volume in
RSX-llM-PLUS, you cannot include an ACP name when the
volume is mounted as foreign.
IN! -- VOLUME NAME TOO LONG -

(volume name)

The command line specified a volume label
that
exceeded six characters for magnetic tape devices or
twelve characters for disk devices.
!NI -- 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;
IN! continues
and initializes the volume.

4-63

MCR COMMANDS

LUN
LOGICAL UNIT NUMBERS
The LUN command displays at the entering terminal the static 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, with the 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, and remove on
exit option of
the MCR Run command the task has no static LUN
assignments.
In this case, the message
LUN -- TASK NOT IN SYSTEM
is displayed.
Format:
LUN[S] taskname
Example:
>LUN HKE
CLO: 3
TT3:
TT3:

LI
5

DKO: G
TT3:

The
display
shows
static
assignments
for
LUNs
3, 4, 5, 6, and 7,
recorded in the task-image file header;
no other LUNs are statically assigned to the task XKE.
Command Error Message:
LUN -- NO LUNS
The task that is the argument of the LUNs command did
not have any logical units.
This is not precisely an
error message, but rather an indication that there
were no assignments to display.
LUN -- TASK NOT IN SYSTEM
The specified task is not installed;
or, the task was
initiated by the
install,
run,
and remove on exit
option of the MCR Run command. This is not precisely
an error message, but rather an indication that there
were no assignments to display.

4-64

MCR COMMANDS

MOU
MOUNT
The Mount command permits 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 online access path exists, that the volume is logically online for
accE~ss.

The command then requests the ACP to mount the volume set.
Mount
defaults
the ACP name to ddnnFl for disks and DECtapes. This permits
you to tailor the ACP that controls a specific volume and then name
that ACP after the volume.
For example, if you tailor FllACP for an
RKOS disk and install it as DKOlFl,
then when you
issue a Mount
command for DKl:, Mount searches for the ACP DKOlFl. If an ACP does
not exist by this name, it defaults to FllACP for disks.
The default
ACP for DECtapes is DTAACP and then FllACP if DTAACP does not exist.
The default ACP for magnetic tapes is always MTAACP.

RSX·-llM systems permit specific tasks, such as INI and DSC, access to
unmounted volumes.
It is only necessary to Mount a magnetic tape if
it is an ANSI standard tape.
FCS treats unmounted magnetic tapes as
unit record devices.
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). To ensure that a mounted volume
remains accessible,
each user of the device should issue a Mount
command.
Thus, each user that mounts a volume declares the volume
logically online, regardless of subsequent Dismount commands issued by
othier users.
A nonprivileged user can mount a volume on:
•

The user's private device (that is, a device that the user has
allocated).
No other nonprivileged user can access or mount
the volume until the volume is dismounted and deallocated.

•

A mounted public device.
All system users can access the
device.
To insure that the device remains accessible, each
user of the device should issue a Mount command. Note that a
privileged user must first mount a public device before
nonprivileged users can issue subsequent Mount commands.

•

Any other device that has not been allocated or set public.
If another user mounts the volume, that user can also access
it.

A privileged user can mount a volume on any random access device.
Only a single user can mount magnetic tape volumes.

4-65

MCR COMMANDS

MOU (Cont.)
To mount DECtapes as Files-11 volumes, the command defaults the ACP to
(Note
DTAACP, or to FllACP if DTAACP is not present in the system.
that the keyword /ACP always overrides the default.) The use of DTAACP
has the advantage that it avoids tying up the disk ACP (FllACP) during
the relatively long searches inherent in DECtape processing.
If powerfail recovery support was selected during system generation,
there is a delay when Mount is specified for a volume that is
off-line.
The description of the Mount command format consists of two parts
which separately
illustrate the parameters and keywords associated
with Files-11 volumes other than magnetic tape and Files-11 ANSI
magnetic tapes
respectively.
All the keywords are collectively
described following the format descriptions.
Files-11 Disk or DECtape Format:
MOU[NT] ddn: [volume-label] [keyword(s)]
Note that since the override volume label keyword
(/OVR)
is a
privileged option of the Mount command, in a multiuser protection
system, a nonprivileged user must always specify the volume-label.
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 512(10) characters.
Keywords:
/ACP=taskname
/DENS=density
/EXT=block-count
/FOR
/FPRO=[system,owner,group,world]
/LRU=FCB-count
/OVR
/PARM="user parameters"
/UIC=[uic]
/UNL
/VI
/WIN=retrieval-pointer-count
Mount keywords for Files-11 devices override corresponding
values
in the volume's home block.
(Mount also passes
keyword values to foreign ACPs.)

4-66

MCR COMMANDS

MOU (Cont.)
wh~~ re:

ddn:

Device-unit
mounted.
Default:

volume-label

Files-11

none;

which

the

volume

must be specified

- The F iles-11 volume label may- be 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.

(ANSI) Magnetic Tape Format:

MOU [NT] ddn: [label]

[keyword (s) ]

Keywords:
/ACP=taskname
/DENS=density
/FOR
/FPRO=[system,owner,group,world]
/OVR
/OVRFSID
/OVREXP
/PARM="user parameters"
/UIC=[uic]
/VI

- A unit number.
If the command specifies more than one
unit number,
the numbers must be separated by commas
and enclosed in parentheses, for example, (0,1,2).

label

2-character device name

(for example, MT)

The tape label may be up to six characters
in length.
If the command specifies moe than one label, the labels
must be separated
by
commas
and
enclosed
in
parentheses.
The number of labels should be equal to
or less than the number of units.
Initially, label-1 must be physically loaded on unit
ddl:.
The
remaining labeled tapes may or may not be
loaded on other units specified in the command.
You
must specify volume labels in the order in which the
volumes make up the volume set because the system

4-67

MCR COMMANDS

MOU (Cont.)
searches for and/or requests each successive volume
in
the specified label order. Since the system searches
according to label, the second volume onward can reside
on any of the specified units.
Keyword Definitions:
ACP

- /ACP=taskname.
The task name of an Ancillary
Control Processor
(ACP) designed to support
file activity on this volume.
Default:
depends
indicated below:

device

type,

For disks and DECtapes, the default ACP
is ddnnFl~
If ddnnFl is not included in
the system, the default ACP for disks in
FllACP (/ACP=FllACP) and the default ACP
for DECtapes is DTAACP
(/ACP=DTAACP).
If DTAACP
is not
in the system, the
default is FllACP.
For F iles-11
/ACP=MTAACP
DENS

(ANSI)

magnetic

tape,

- /DENS=density.
The density (Bits Per Inch or
BPI)
of the media loaded on the device.
Acceptable density values depend on
the
device type as indicated below:
TE16
TS04
TU45
TU77
RX02

800 (or LOW) or 1600 (or HIGH)
1600
800 (or LOW) or 1600 (or HIGH)
800 (or LOW) or 1600 (or HIGH)
LOW or HIGH

Defaults:
TE16
TS04
TU45
TU77
RX02
EXT

- /EXT=block-count.
This keyword specifies the
number of blocks a file that exhausts its
space allocation can extend.
Default:

FOR

/DENS=800
/DENS=l600
/DENS=800 (or LOW)
/DENS=800
/DENS=HIGH

taken from the home block.

- /FOR.
This keyword indicates a
foreign
volume;
the format of the volume and/or the
ACP that controls the volume
is not DEC
standard.
If you specify this keyword, Mount
performs a syntax check on the entire command
line, allocates a Volume Control Block (VCB),
indicates in the Unit Control Block
(UCB)
that
a
foreign volume
is mounted,
and
notifies the appropriate ACP.

4-68

MCR COMMANDS

MOU (Cont.)
When mounting a foreign
volume
on
an
RSX-llM-PLUS system,
an ACP name
is not
required.
However, if you do not specify an
ACP name,
a file system
(an ACP) cannot
access the volume.
Absence of an ACP name
permits tasks such as INI,
DSC,
and BAD
access to non-FILES-11 volumes.
When mounting a foreign volume on an RSX-llM
system,
you
must
specify an ACP name
(/ACP=taskname).
FPRO

'-'

/FPRO=[system,owner,group,world].
Keyword
for default file protection. Access codes
consist of four 4-code groups in the Access
Rights word, as follows:
R

w
E
D

Read
Write
Extend
Delete
Default

In each instance, the absence of
the code
means that the applicable user is denied the
access right.
The square
brackets
are
required syntax.
Specify an asterisk (*) in the access
word
to force the default value
specific group.

rights
for
a

Default:
for disk, values taken from volume
home block;
for
tape, standard protection
(RWED, RWED, RWE, R).
LRU

- /LRU=FCB-count.
The number of directory File
Control Blocks
(FCBs) kept in memory by the
ACP per volume.
These FCBs control access to
User File Directories (UFOs).
The more FCBs
in memory, the faster a file can be found.
If the file is in a directory for which the
FCB is resident,
the overhead required to
open the directory
is bypassed. Thus, the
time required to perform directory operations
and open files decreases as the number of
FCBs increases.
Default:

taken from the volume home block.

OVR

- Privileged option.
/OVR. The /OVR keyword
instructs the Mount command to override label
processing so that a volume can be mounted
without specifying a volume label.

OVRFSID

- /OVRFSID. The /OVRFSID keyword instructs the
Mount command to override the existing file
sequence identifiers on tape volumes.

4-69

MCR COMMANDS

MOU (Cont.)
OVREXP

- /OVREXP. The /OVREXP keyword instructs the
Mount command to override the expiration date
on the tape volume(s).

PARM

- /PARM="user parameters". The /PARM keyword
instructs
the
Mount
command
to
pass
non-standard parameters from the command line
to a foreign ACP. The user parameter string
can consist of up to a maximum of
40
characters enclosed in quotes (").
This keyword is valid only
with foreign (/FOR) volumes.

conjunction

UIC

- UIC=[uic].
User
[group, member].
syntax.

UNL

- /UNL.
Specify the volume index file as
unlocked.
When locked,
the index file is
read-only; when unlocked, it is read/write.
Default:

identification
Brackets
are

code
requried

locked.

- /VI. Display the volume information on the
entering terminal. The information displayed
is that under which the volume was mounted.
For random access
devices,
information format is:

the

volume

MOUNT ** VOLUME INFORMATION **
CLASS
FILES-11 or FOREIGN
DEVICE
ddnn:
LABEL
volume label
UIC
[group, me mb e r ]
VOL PRO
[system, owner, group, world]
FILE PRO
[system, owner, group, world]
CHARAC
[ATCH, DCF]
ACP NAME
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).
WIN

- /WIN=number. The number of mapping
to be allocated for file windows.

pointers

Default: If space is available and the I/O
optimization option was selected at system
generation, the entire index file is mapped
in the window block; otherwise, the number
of pointers specified in the home block.

4-70

MCR COMMANDS

MOU (Cont.)

Examples:
>MOU DK 1: AMBER

Mount the volume on device-unit DKl:.
(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.
>M 0 U MT < 0 t 1 , 2 ) : ( t,J 0 L 1 , t,J 0 L 2 , t,J 0 L 3 >

Mount the volume set on units MTO:, MTl:,
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 may or may not
be loaded when the command is issued.
If they are loaded,
they can
reside on the remaining units in any order (for
example, VOL3 could be loaded on MTl:).
The system searches
for the next volume in a set by volume label rather than by
unit number;
the order in which volumes are listed in the
command is the order in which the system searches for and/or
requests the volumes.
If VOL2 and VOL3 are not loaded,
the
system requests each in turn.
The volumes can be loaded on
either MTO:, MTl:, or MT2:.
>MOU DK1:SYS004/LRU=8/VI/WIN=20

Mount the volume labeled SYS004 on DKl:.
The command
reserves space for nine directory file control blocks to
remain in the ACPs pool or system pool, displays the volume
information,
and changes the default window block size for
files opened on this volume to twenty.
In RSX-llM systems, you can mount a network channel as a
native device.
For network channels,
the Mount command
informs the network ACP that the device is available for use
in the network.
Mount allocates a communication VCB and
issues a Mount request to the ACP.
RSX-llM Network Format:
MOU[NT] ddn: [/keyword(s)]
Network keywords:
/PRTCL=network-protocol
/RCK=name of a redundancy check algorithm
/TEL=telephone number of a dial-up link

ddn: - is the network device-unit to be made available for use in
the network.
The default ACP is /ACP=NT ••••
Network Keyword Definitions:
I

PRTCL - /PRTCL=network-protocol.
line protocol.
Default:

/PRTCL=DDCMP.

4-71

The name

the

network

MCR COMMANDS

MOU (Cont.)
RCK -/RCK=algorithm-name.
checking algorithm routine.
Default:

The

name

redundancy

the

/RCK=CRC16.

TEL -/TEL=number. The telephone number of a
remote mode.
Up to 12 digits may be specified.
Default:

line

Null.
NOTE

In future releases of RSX-llM,
native
network channels will not be supported;
future
releases
will
require
that
network channels be mounted as foreign.
Command Error Messages:
MOU -- ACP NOT IN SYSTEM
The task specified as ACP
installed in th~ system.

default

ACP

was

not

MOU -- ALREADY MOUNTED
The specified network device unit was already mounted.
MOU -- DEVICE NOT DEFINED IN NETWORK
in the
The specified device unit was not defined
current network
topology and therefore could not be
mounted.
MOU -- DEVICE NOT IN SYSTEM -dev:
The Mount command specified a device that had not
generated into the system.

been

MOU -- DEVICE NOT READY -dev:

""'

The device specified in the command, although generated
into the system, was not physically present in the host
configuration.
MOU -- DEVICE SPECIFIED TWICE
The Mount command specified the same
twice.

tape

device-unit

MOU -- DISMOUNT IN PROCESS
The ACP of the device to be mounted is in the
of deallocating control blocks for the device.
the command.

4-72

process
Reissue

MCR COMMANDS

MOU (Cont.)

''-".
MOU -- DRIVER NOT LOADED
The driver of the device to be mounted has not been
loaded.
Load the appropriate driver and reissue the
Mount command.
(See the description of the Load
command.)
MOU -- FAILED TO ATTACH DEVICE -dev:
The device-unit specified in the command was
by another task and could not be mounted.

attached

MOU -- HOME BLOCK I/O ERROR
An I/O error was detected in trying to read the home
block.
This message usually indicates that the volume
is not ready. Wait until it is ready and reissue the
command.
MOU -- ILLEGAL KEYWORD COMBINATION
The Mount command specified conflicting keywords.
MOU -- INDEX FILE I/O ERROR
Mount could not read either the index
the storage allocation file.

"-""'

file

header

MOU -- MOUNT ERROR FROM ACP xxx.
The magnetic tape ACP (MTAACP) detected an error while
trying to mount the volume set. The following is a
list of the MTAACP error code numbers and their
respective meanings.
Meaning

Decimal Value
6
7
8
11

12
13

17
18

Get command line error
Syntax error
Bad device
Wrong volume (incorrect label)
All units must be TU16s
Not ANSI format
Privilege violation
Units
have
different
track
specifications
(cannot mix 7- and 9track units)
Message task (FllMSG) not installed

(See the IAS/RSX-11 I/O Operations Reference Manual for
a further discussion of MTAACP error codes.)

4-73

MCR COMMANDS

MOU (Cont.)
MOU -- MULTI-UNIT DEVICE NOT TAPE
The command specified multiple units that are not
drives.

tape

MOU -- NT DEVICE NOT MOUNTED
The device NT:
was not mounted.
This device must
always be mounted before any other device in a network.
MOU -- NOT FILE STRUCTURED DEVICE
The specified device was not supported
device (including ANSI magnetic tape).

Files-11

MOU -- NOT MOUNTABLE DEVICE
The specified device was not
device.

supported

network

MOU -- OTHER VOLUME MOUNTED -dev:
An attempt was made to mount a volume on a device that
already had a mounted volume.
In multiuser protection
systems, only random a~cess devices can be mounted by
multiple users.
MOU -- PARAMETER CONFLICTS WITH MOUNTED VOLUME
An attempt was made to mount a mounted volume with
keyword parameters
that conflict with those values
specified when the volume was initially mounted.
MOU -- STORAGE BIT MAP FILE I/O ERROR
storage

An I/O error was encountered while reading the
allocation file.
MOU -- TASK NOT ACP
The task specified as an
characteristics of an ACP.

ACP

did

not

have

the

MOU -- UNDEFINED DENSITY SELECTION
The command specified an illegal density value.
MOU -- UNIT DOES NOT SUPPORT DENSITY SWITCH
The command specified a
device
multiple density capability.

which

does

not

have

High

and

MOU -- UNIT DOES NOT SUPPORT HIGH/LOW DENSITY SELECTION
The command specified a device for which the
Low keywords are undefined.

4-74

MCR COMMANDS

MOU (Cont.)
MOU -- UNIT DOES NOT SUPPORT 800 BPI
The command specified
support 800 BPI.

tape

drive

that

does

not

tape

drive

that

does

not

MOU -- UNIT DOES NOT SUPPORT 1600 BPI
The command specified
support 1600 BPI.

MOU -- UNSUPPORTED FILE HEADER FORMAT
The volume home block does not conform to FILES-11
format.
This may indicate a corrupted volume.
MOU -- WRONG VOLUME LABEL
The volume label and the label specified in the command
did not match.

4-75

MCR COMMANDS

PAR
PARTITION DEFINITIONS
This command displays on the entering terminal a description
memory partition in the system.
In an RSX-llM system,
specify:

the

display

Partition name

Partition base address

Partition size (octal)

Partition kind:

Partition type:
TASK
COM
DEV
SYS
taskname
DYNAMIC
DRIVER

for
for
for
for
for
for
for

consists

each

columns

that

or subpartition

(SUB)

five

(octal)

main partition (MAIN) I

user-controlled
common
device registers
system-controlled
task region
dynamically created region
region occupied by a loadable driver

COM partitions are used for resident libraries and common data areas.
DEV partitions are used to allow tasks to communicate with specific
device registers, such as the UDC and ICS/ICR-11
industrial control
subsystems.
See
Chapter
l
for a description of system and
user-controlled partitions, as well as subpartitions.
Dynamic and
task regions are defined in the RSX-llM/M-PLUS Executive Reference
Manual.
See the description of the Load command for information about
loadable drivers.
syst6m, the

displ~y

partition_

type:
indicates
indicates
indicates
driver

indicates that
common
indicates

common

indicates

mapped fo

4-76

MCR COMMANDS

PAR {Cont.)

Form,3 t:

PAR [TIT IONS]
Examples:
RSX-llM systems
Name
~·

"""'

>PAR
LOR
SYS PAR
FCPPAR
PMDPAR
SPLPAR
DRl.JPAR

Base

Size

000000
120000
130000
158000
158000
178000
178000
177800
200300
201300
202400

000000
010000
028000
020000
010000
014000
001800
000500
001000
001100
001000
003100
548000
013400
045700
034200
117100
045700
010000
117100

~~03400

GEN

212000
212000
225400
302100
:338300
1.155400
523300
c;o 1500

Kind Type
MAIN
MAIN
MAIN
MAIN
SUB
MAIN
SUB
SUB
SUB
SUB
SUB
SUB
MAIN
SUB
SUB
SUB
SUB
SUB
SUB
SUB

TASK
TASK
TASK
TASK
TASK
SYS
DR I t,JER DRil.JER DR I t,JER DR I t,JER DR I l,JER DR I t,JER SYS
(RMDEMO)
( + .. EDI>
( + + , AT,)
( , , , TKB)

DB:
os~

DK:
OT:
LP:
MM:

(EDIT13)
( • +
( + +

.SYS>
.MAC>

RSX-llM-PLUS systems
>PAR
SYS PAR 11 7734 00174400 00010000 MAIN
085230 00174400 00010000 TASK
<TKTN
SPLPAR 11 7787 00204400 00012000 MAIN
DRt,JPAR 117824 00218400 00140000 MAIN
1.17340 00218400 00003100 DR I l.JER (DB:)

4-77

MCR COMMANDS

....__.

PAR (Cont.)
11 7274
117184
117120
038314
118744
118700
118834
118550
118504
118440
118374
038044
038504
LDRPAR 117580
118054
TSTPAR 117514
SEC POL 117450
GEN
117404
115454
073400
052274
080774
037210
045104
040240
043300
044474
082254
081340
081874
081774
083050
070100
071114
037474
072244
042100
037540
084534
037724
070574

00221500
00228100
00227400
00233400
00238400
00237500
00243300
00300800
00318400
00317700
00321200
00321300
00322800
00358400
00358400
00381200
00421200
00443200
00443200
00534000
00542800
00571400
00820100
00858200
00718200
01007000
01077800
01170400
01230400
01242500
01254800
01313700
01401400
01437000
01474400
01571100
01831100
01715800
02050500
02143000
02340500

00001300
00001300
00004000
00001800
00001100
00003800
00035300
00015800
00001300
00001300
00000100
00001300
00003200
00002800
00002800
00040000
00022000
04734800
00070800
00008000
00003500
00020100
00038100
00028400
00070800
00070800
00070800
00040000
00012100
00012100
00037100
00037100
00035400
00035400
00074500
00028500
00084500
00102700
00033500
00134300
OOOll 1 700

DR I t.JER (DK:)
DR I t.JER ( DS: >
DRil.lER ( DM: >
DR Il.IER (D){:)
DR I t)ER (LP:)
DR I t.JER (MM: l
RW COM ! TT COM
DR I t.JER (TT:>
DR I l.JER (RD: )
DR Il.lER ( t.JT:)
DR I t.JER (NL: )
DR I t.JER ( DT: >
DRil.lER (DR:)
MAIN
TASK
<. t .LDR>
MAIN
SEC POOL
MAIN
<F11ACP>
TASK
<TT38
TASK
RO COM + •• .EDI+
< QMG,, • >
TASK
<HRC • • t >
TASK
TASK
<RMDEMO>
<DSOOF1
TASK
<DS01F1
TASK
<LSTACP
TASK
<SYSLOG
TASK
TASK
<LPPO
TASK
<LPP1
TASK
<BAP2
TASK
<BAP1
<AT, T38 ...
TASK
<AT, 1.13 >
TASK
TASK
<EDTT3 >
<PARt.13 >
TASK
<TT47
TASK
>
TASK
<EDIT25>
TASK
<TTF8
>
RW COM !RMSRES!
TASK
<LOGT17>

4-78

MCR COMMANDS

RES
RESUME
The Resume command continues execution of a previously suspended task.
A nonprivileged user can issue the Resume command only for
tasks
initiated from the entering terminal.
A privileged user can direct
the Resume command to any suspended task.
Format:
RES[UME]

taskname

[/TERM=TTnnn:]

where:

Exa1mple:
>RES )-(KE

Resume task XKE.
Note:
A task cannot suspend any task other than itself.
command allows such a suspended task to proceed.

The

Resume

command

Command Error Message:
RES -- TASK NOT SUSPENDED
The task used as the argument of
was not suspended.

4-79

the

MCR COMMANDS

RUN
RUN
The Run command initiates the execution of a task.
cause a task to be:

The

command

can

• Started immediately
• Started at a time increment from now
• Started at a time increment from clock unit synchronization
• Started at an absolute time of day

• Installed, immediately run, and removed on exit
All these options, except install-run-and-remove, are
or without rescheduling.

available

with

Run has five format variations, as described below.
Formats:
1.

Run immediately.
RUN task name [/RS I =magu] [/U IC= [ u i c] ]
where:
taskname - A 1- to 6-character task name.
RSI

- The reschedule interval -- The format is the
same as for dtime, which is detailed below
under format 2.
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.
Default:

UIC

(Privileged option in multiuser protection
systems only.) 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 through 377(8).
The
square brackets are required syntax. This is
the UIC under which the task
will
be
requested.
The UIC determines which files
the task may access.
Default:
terminal
entered.

no rescheduling.

the value established for
the
from which the Run command is

Run at a time increment from now.
RUN taskname dtime [/RSI=magu] [/UIC=[uic]]
where:
task name

A 1- to 6-character task name.
4-80

MCR COMMANDS

RUN (Cont.)
dtime

The time at which the task will be
initiated
in time units
from command issuance.
It
foliows the form magu.
A time parameter consists of two fields:
a.

A magnitude field

A units field

where:
mag

The magnitude
Units, one of the following letters:

M
H

The legal value of the magnitude
is
related
to the value of the units field, which is
encoded as:
T = Ticks
A
tick
is
a
clock
interrupt,
and 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 60 per second,
corresponding to the line frequency.
For a programmable clock, a maximum
of
1000
ticks
per
second
is
available.
(The
frequency
is
selected at system generation.)
S

Seconds

Minutes

Hou rs

The magnitude is the number of units to be
clocked,
but the magnitude value cannot
exceed 24 hours in the specified units.
If
the magnitude is equal to O, then the RSI is
set to 1.
For example,
/RSI
OH
is
equivalent to /RSI = lH.

Units

T
Any positive value is valid
(maximum of 15 bi ts) •

Units

s -- Any positive value is valid
(maximum of 15 bi ts) •

Units
~-

4-81

M -- The maximum
1440 ( 10) •

magnitude

MCR COMMANDS

RUN (Cont.)
Units

H -- The
24(10).

RSI

See Format l, above.

UIC

See Format l, above.

maximum

magnitude

Run at a time increment 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]]

where:
taskname
sync

A 1- to 6-character task name.
H

T
dtime

synchronize
synchronize
synchronize
synchronize

on
on
on
on

the
the
the
the

next
next
next
next

hour
minute
second
tick

As defined in Format 2,
above;
dtime,
if
present, is added to the synchronization unit
to produce the actual run time for
running
the task.

RSI

See Format l, above.

UIC

See Format l, above.

Run at an absolute time of day.
RUN taskname atime

[/RSI=magu] [/UIC=[uic]]

where:
taskname

A 1- to 6-character task name.

atime

Absolute time of day at which to
initiate
this task.
Input format is hh:mm:ss.
hh
mm
ss

hours (decimal assumed);
minutes (decimal assumed), and
seconds (decimal assumed).

RSI

See Format l, above.

UIC

See Format l, above.

Install, run immediately, and remove on exit.
When Run tries to start a task as a
type l
request,
it
searches the system task directory (STD) for the task;
if it
finds the entry, it proceeds to run it.
However, if Run does
not
locate the task,
it attempts to install a task whose
filename
is given as the task name.
Run determines which

4-82

,1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..

MCR COMMANDS

RUN (Cont.)
directory to look in for this file by the presence or absence
of
·a
leading
$
immediately
before
the task name
specification.
If you do not specify $, Run searches the UIC
of the terminal requesting the task on device SY:. If you
specify$, Run searches the system directory on device LB:.
The
SET /SYSUIC
command defines the system directory;
however, conventional values are
(1,50]
for an unmapped
system and
(1,54]
for a mapped system.
In an RSX-llM-PLUS
system, if you specify $ and the file cannot be found
under
SYSUIC, Run searches the library directory on device LB:. By
convention, LIBUIC is (3,54].
RUN

[ddn: J [$] filespec

[/keyword (s) J

Keywords:
/CKP=option
/PAR=pname
/PMD=option
/PRI=number

(Privileged)

/ROPAR=pname

(RSX-llM-PLUS systems)

/SLV=option
/TASK=taskname
/UIC=[group,member]
where:
ddn:

- Device-unit on which task
resides.

image

- Specifies that the file can be found
under the system UIC on device LB:
(if ddn:
is not specified).

filename

- The name of the task-image file to
run.

CKP

- /CKP=option.
Checkpoint option.
The
two
options are YES and NO.
If
/CKP=YES (default for checkpointable
tasks),
checkpointing is allowed.
If
/CKP=NO, checkpointing is disabled for
the task.
The /CKP keyword overrides the
switch specified at task build.

4-83

file

/CP

MCR COMMANDS

RUN (Cont.)
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 for the task when
required from a checkpoint file.
PAR

- /PAR=parname.
partition in
installed.
Default:
build.

PMD

task

specified

task-build

- /PRI=number.
Privileged
keyword.
Priority number. The value range is 1
through 250(10).
Standard
number
conventions apply;
octal by default,
decimal if followed by a period.
Default:

SLV

Partition specified at

- /PMD=option.
Post-Mortem Dump option.
The two options are YES and NO.
If
PMD=YES,
a
post-mortem
dump
is
requested for the task if it aborts
because of an SST error condition.
If
PMD=NO
(the
default
from
a
task-build), no dump is requested at
SST abort time. To generate a dump,
the post-mortem dump task PMD ••• must
be installed in the system.
This
keyword overrides the
/PM
switch
specified at task~build time.
Default:
time.

PR!

Parname specifies the
which the task is to be

/PRI=SO.

- /SLV=option.
Slave task option.
The
two options are YES and NO.
If the
command specifies /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
specified at task build.

4-84

MCR COMMANDS

RUN (Cont.)
If the command specifies /SLV=NO the
TI:
of the task does not change when
receiving data.
Default:

Specified at task build.

TASK

- /TASK=taskname.
The specified task
name is to be assigned temporarily to
the task while
it is running.
If
taskname
is not found in the STD, MCR
names it TTnn by default, where nn is
the unit number of the requesting
terminal.

UIC

- /UIC=[uic]. The square brackets
required syntax.
This is the
under
which
the
task
will
requested.
Default:
The value
the
terminal that
command.

established
issues the

are
UIC
be
for
RUN

Examples:
>RUN HKE 15M

Run task XKE 15 minutes from command issuance.
>RUN HKE 15M/RSI=80S/UIC=[311J

Run task XKE 15 minutes from command issuance,
it every 90 seconds, with a UIC code of [3,1].

rescheduling

>iRUN Dl\2: $MAC

Run task in file DK2:MAC.TSK from the system directory.
The
task is automatically installed, run, and removed on exit.
Note:s:
•

If the command is a Run Immediately, it establishes TI:
as
the terminal from which the task was initiated. Otherwise,
the system sets the TI:
terminal to CO:.

•

A Run Immediately, if specified without the /RSI option and
terminated with an ESCape character instead of a carriage
return, ·echos the default prompt when the requested task exits
and not when MCR has finished
initiating the task.
This
facility enables the operator to determine when a task that is
not producing output on a terminal has exited.

•

The install, run, and remove form establishes the terminal
from which
the command was initiated to be the TI:
terminal
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 Strorage Region
(DSR)
is small, since the memory necessary for a Task Control Block
(TCB) returns to the DSR when the task exits.

4-85

MCR COMMANDS

RUN (Cont.)
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 subject
task was being aborted either because of
an unrecoverable error or an Abort directive issued by
the operator.

4-86

MCR COMMANDS

SET
SET
The Set command dynamically alters device
displays system-wide status and statistics.

characteristics

and/or

A nonprivileged user can only alter local
terminal
(device TI:)
or
private device characteristics.
Privileged users can alter device
characteristics for any terminal in the system as well as system
statistics.
Both privileged and nonprivileged users
can display
status or statistics.
The following two lists describe all the available options
appropriate privilege heading.

under

the

Nonprivileged options:

•

Establish certain terminal characteristics
terminal only

•

Set the default UIC for the issuing terminal

•

Display the status (determined by the keyword
all terminals

•

Display statistics about system dynamic memory

for

the

issuing

specified)

Privileged options:

•

Establish device characteristics
system

•

Establish the default UIC for any terminal in the system

•

Establish the system UIC and, in an RSX-llM-PLUS system,
library
UIC
used
by
the
Load
command
and
install-run-remove option of the Run command

•
•

Set the privilege status of any terminal in the system

•

Set any device to public status so that any system
access the device

•
•
•
•

Create partitions and subpartitions

for

any

terminal

the

the
the

Set any terminal to slave status
user

can

Add space to the dynamic core pool
Enable write check on devices that support it
Specify the maximum number of I/O packets to be
in order to optimize I/O performance

preallocated

•

Specify the maximum size to which a task can extend itself by
means of the Extend Task system directive

•

Enable or disable the ability to
multiuser protection system

.'--1

4-87

log

onto

terminals

MCR COMMANDS

SET (Cont.)
Improper use of the Set command from a privileged terminal can
in a situation in which privileged operator input will
accepted.
Avoid the following two situations:

result
not be

•

All privileged terminals in the system are set to slave and
cannot
enter
unsolicited input to MCR.
Nonprivileged
terminals cannot enter privileged commands and therefore
cannot reset the privileged terminals to nonslave.
See the
description of the /SLAVE keyword below.

•

The buffer length of all the nonslaved, privileged terminals
is shorter than 14 bytes. The terminal buffer is then too
short 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 below.

A number of Set command keywords
(/CRT,
/ESCSEQ,
/HOLD,
/LOGON,
/LOWER,
/MAXEXT,
/MAXPKT,
/OVLP, /PUB, and /WCHK) are features that
you must include at system generation.
If you did not include support
at system generation, the the specified keyword has no effect. Also,
some keywords (/EBC, /ECHO, /FDX,
/FORMFEED,
/HFILL,
/HHT,
/LINES,
/RPA, /TYPEAHEAD, /VFILL, and /WRAP) are only supported with the full
duplex terminal driver.
The full duplex terminal driver is a SYSGEN
option in RSX-llM systems, but is always included in an RSX-llM-PLUS
system.
Format:
SET /keyword=values
Only one keyword per command is permitted. You can prefix most
keywords with NO to negate or disable the function of the
keyword.
Exceptions are /BUF, /MAXEXT, /MAXPKT,
/POOL,
/SPEED,
the system returns a syntax error whenever NO
/SYSUIC, and /UIC;
precedes one of these keywords.
Device Characteristics Keywords:
/BUF=dev: [size]

/CRT [ =TTnn:]
/DCL[=TTn:]

(RSX-llM-PLUS systems only)

/EBC [ =TTnn:]
/ESCSEQ [ =TTnn:]
/ECHO [ =TTnn:]
/FDX[=TTnn:]
/FORMFEED[=TTnn:]
/HFILL=TTnn: [value]
/HHT [ =TTnn:]
/HOLD[=TTnn:]

4-88

MCR COMMANDS

SET (Cont.)
/LINES=TTnn: [value]
/LOWER[=TTnn:]
/MCR[=TTn:]

(RSX-llM-PLUS systems only)

/OVLP[=ccn:]

(RSX-llM-PLUS systems only)

/PRIV [=TTnn:]
/PUB [ =dev:]
/REMOTE [ =TTnn:]
/RPA [ =TTnn:]
/SLAVE [ =TTnn:]
/SPEED=TTnn: [recv:xmit]
/TERM=TTnn: [value]
/TYPEAHEAD[=TTnn:]
/UIC[=uic[:TTnn:]]
/UIC[=TTnn:]
/VFILL[=TTnn:]
/WCHK [ =dev:]
/WRAP [ =TTnn:]
Keyword Definitions:
BUF

- /BUF=dev: [size]. Set or display the default buffer
size of the specified device.
A nonprivileged user can
display the buffer size of any device,
but can alter
only the buffer size of device TI:. A privileged user
can set the buffer size for any device.
The specified
size must be greater than 0 and less than or equal to
255(10).
If dev:
is a terminal, size must be greater
than 2 and less than or equal to 255(10).
/BUF is
particularly useful for defining line printer width
( 8 0 • o r 1 3 2 • co 1 u mn s ) •
When size is omitted,
the system
issuing terminal the buffer size
device.

displays at the
of the specified

Example:
>SET /BLJF:::L..PO :
BUF=LP0:132.

Display the current buffer size of LPO:.
>SET /BLJF=TTl:ao.

Sets TTl:

buffer size to 40(10).
4-89

MCR COMMANDS

SET (Cont.)
CRT

/CRT[=TTn:] where TTn:
is a Cathode Ray Tube
(CRT)
terminal.
The /CRT keyword defines the terminal as a
CRT and enables the backspace 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 nonprivileged 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 the keyword omits =TTn:, the system displays
the issuing terminal all terminals defined as CRTs.

Examples:
>SET /CRT=TT3:

Enables the backspace deletion option
terminal TT3:.

the

display

>SET /CRT
CRT=TT3:
CRT=TTll:

Displays all terminals that have the backspace deletion
option enabled.
NO CRT

/NOCRT[=TTn:] where TTn:
is a Cathode Ray Tube
(CRT)
terminal.
The /NOCRT keyword deletes the CRT status of
the specified device and disables
the
backspace
deletion option.
A nonprivileged user can display all terminals not
defined as CRTs,
but can only delete CRT status for
device TI:. A privileged user can define any terminal
as other than a CRT.
When the keyword omits =TTn:, the system displays at
the
issuing terminal all the terminals that are not
defined as CRTs.
Examples:
>SET /NOCRT=TTll:

Disables the backspace deletion option at TT4:
>SET /NOCRT
NDCRT=TTO:
NDCRT=TT1:
NOCRT=TT2:
NOCRT=TTll:

Displays all terminals that have the backspace deletion
option disabled.

4-90

MCR COMMANDS

SET (Cont.)

EBC

/EBC[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only.
The /EBC keyword enables the
8-bit character option.
The full duplex terminal
driver passes all eight bits of the input characters to
the specified terminal.
A nonprivileged user can display all terminals
that
have
the option enabled, but can only enable EBC for
TI:. A privileged user can enable the EBC option for
any terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all the terminals that have the
EBC option enabled.
Examples:
>SET /EBC=TT3:

Enables the EBC option for terminal TT3:.
>SET /EBC
EBC=TT3:

Displays
enabled.

all

terminals

4-91

that

have

the

EBC

option

MCR COMMANDS

SET {Cont.)
NOE BC

- /NOEBC[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only.
The /NOEBC keyword disables the
8-bit character option.
Before passing the
input
characters to the device,
the full duplex terminal
driver removes the parity bits.
A nonprivileged user can display all terminals that
have the option disabled, but can only disable EBC for
TI:.
A privileged user can disable EBC for any
terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all the terminals that have the
EBC option disabled.
Examples:
>SET /NOEBC
NOEBC=TTO:
NDEBC=TT1:
NOEBC=TT2:
NOEBC=TT4:

Displays all
disabled.
>SET

terminals

that

have

the

EBC

option

/NOEBC=TT3~

Disables the EBC option for terminal TT3:
ESCSEQ

- /ESCSEQ[=TTn:] where TTn:
is a terminal.
The /ESCSEQ
keyword 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-llM/M-PLUS I/O Drivers Reference Manual for further
information about escape sequences.
A nonprivileged user can display all terminals that can
send and receive escape sequences, but can only declare
TI:
able to send and receive escape sequences.
A
privileged user can establish escape recognition for
any terminal.
When the keyword omits =TTn:, the system displays at
the entering terminal all the terminals that can send
and receive escape sequences.
Examples:
>SET /ESCSEQ=TT3:

Establishes TT3:
sequences.

as a terminal that

can

send

escape

>SET /ESCSEQ
ESCSEQ=TT3:

Displays all terminals that can send and receive escape
sequences.

4-92

MCR COMMANDS

SET (Cont.)
NOESCSEQ - /NOESCSEQ[=TTn:] where TTn:
is a terminal.
The /NOESCSEQ keyword disables the recognition of
escape sequences at the specified terminal.
A nonprivileged user can display all terminals that do
not recognize escape sequences, but can only disable
the function for device TI:.
A privileged user can
disable escape recognition for any terminal.
When the keyword omits =TTn:, the system displays at
the issuing terminal all the terminals with escape
recognition disablede
Examples:
>SET /NOESCSEQ
NOESCSEQ=TTO:
NOESCSEQ =TT 1:
NOESCSEQ=TT2:
NOESCSEQ=TTll:

Displays all terminals
escape sequences.

that

cannot

send

receive

>SET /NOESCSEQ=TT3:

Disables escape sequence support at TT3:.
ECHO

- /ECHO[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only. The /ECHO keyword instructs the
full duplex terminal driver to display each character
typed on the entering terminal.
A nonprivileged user can display all terminals 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 the keyword omits =TTnn:, the system displays at
the entering terminal all the terminals that have the
echo option enabled.
Examples:
>SET /ECHO=TT3:

Enables the echo option for terminal TT3:
>SET /ECHO
ECHO=TT1:
ECHO=TT3:
Displays
enabled.

all

terminals

4-93

that

have

the

echo

option

MCR COMMANDS

SET (Cont.)
NOECHO

/NOECHO[=TTnn:] where TTnn:
is a terminal.
Full
duplex terminal driver only.
The /NOECHO keyword
instructs the terminal driver to inhibit the display of
all input characters typed on the specified terminal.
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 the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have the echo
option disabled.
Examples:
>SET /NOECHO
NOECHO=TTO:
NOECHO=TT2:
NOECHO=TT4:

Displays all
characters.

terminals

that

not

echo

typed

>SET /NOECHO=TT3:

Disables the echo option for terminal TT3:.
FOX

/FDX[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only. The /FDX keyword instructs the
full duplex terminal driver to accept input from the
specified terminal while simultaneously outputting to
it.

A nonprivileged user can display all full duplex
terminals, but can only enable the option for TI:. A
privileged user can enable the full duplex option for
any terminal.
When the keyword omits =TTnn:, the system displays
the entering terminal all full duplex terminals.

Examples:
>SET /FDH=TT3:

Declares that TT3:

is a full duplex terminal.

>SET /FD)<
FD)<=TT1:
FD)<=TT3:

Displays all full duplex terminals.
NOFDX

- /NOFDX[=TTnn:] where TTnn:
is a terminal. The /NOFDX
keyword disables the full duplex option; the terminal
driver does not simultaneously process input and output
from the specified terminal.

4-94

MCR COMMANDS

SET (Cont.)
A nonprivileged user can display all terminals that
have the option disabled,
but can only disable full
duplex operation for TI:.
A privileged user can
disable full duplex operation for any terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all the terminals that have the
full duplex option disabled.
Examples:
>SET /NOFD).(
NOFDH=TTO:
NOFD>(=TT2:
NOFO)<=TTll:

Displays all terminals that do not
output simultaneously.
>SET

process

input

and

/NOFD>(=TT3:

Disables the full duplex option for terminal TT3:.
FORMFEED - /FORMFEED[=TTnn:] where TTnn:
is a terminal.
Full
duplex terminal driver only. This keyword indicates
that the specified terminal has a hardware formfeed.
A nonprivileged user can display all terminals that
have a hardware formfeed, but can only declare it for
TI:. A privileged user can specify any terminal.
When the keyword omits =TTnn:, the system displays at
the
entering terminal all terminals that have a
hardware formfeed.
Examples:
>SET /FORMFEED
F'ORMFEED =TT 1:

Displays all terminals that have a hardware f ormfeed.
>SET

/FORMFEED=TT3:

Declares that TT3:

has a hardware formfeed.

NOFORMFEED - /NOFORMFEED[=TTnn:] where TTnn:
is a terminal.
Full
duplex terminal driver only. This keyword indicates
that the specified terminal does not have a hardware
formf eed.
A nonprivileged user can display all terminals that do
not have hardware formfeeds, but can only declare this
for TI:. A privileged user can specify any terminal.
When the keyword omits =TTnn:, the system displays
terminals that do not have a hardware f ormfeed.

4-95

all

MCR COMMANDS

SET (Cont.)
Examples:
>SET I NOFORMFEED
NOFORMFEED=TTO:
NOFORMFEED=TT2:
NOFORMFEED=TTLI:

Displays all
formfeeds.

terminals

that

not

have

hardware

>SET /NOFORMFEED=TT3:

Declares that TT3:
HFILL

does not have a hardware formfeed.

/HFILL=TTnn: [value] where TTnn:
is a terminal and
value is a number in the range of 0-7 inclusive. Full
duplex terminal driver only.
This keyword specifies
the number of fill characters that the full duplex
terminal driver places after a carriage return when
outputting to a terminal.
A nonprivileged user can display the number of fill
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 the keyword omits the value parameter, the system
displays at the entering terminal the fill character
value for the specified terminal.
Examples:
>SET I HF ILL= TT 3 :
HFILL=TT3:=0

Displays the number of fill characters for TT3:.
>SET /HFILL=TT3:3

Specifies that three fill characters follow a
return at terminal TT3:.
HHT

carriage

/HHT[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only.
This keyword indicates to the
full duplex terminal driver that the specified terminal
has a hardware horizontal tab.
A nonprivileged user can display all terminals that
have a hardware horizontal tab, but can only declare it
for TI:. A privileged user can specify any terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have hardware
horizontal tabs.

4-96

MCR COMMANDS

SET (Cont.)
Examples:
>SET /HHT
HHT=TTll:

Displays all terminals that
tabs.

have

hardware

horizontal

>SET /HHT=TT3:

Declares that TT3:
NOHH~r

has hardware horizontal tabs.

/NOHHT[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only.
The /NOHHT keyword indicates
that the specified terminal does not have hardware
horizontal tabs.
A nonprivileged user can display all terminals that do
not have hardware horizontal tabs, but can only declare
this for TI:.
A privileged user can specify any
terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that do not have
hardware horizontal tabs.
Examples:
>SET /NOHHT
NOHHT=TTO:
NOHHT=TT1:
NOHHT=TT2:

Displays all terminals
horizontal tabs.

that

not

have

hardware

>SET /NOHHT=TT3:

Declares that TT3:
tabs.
HOLD

does not have

hardware

horizontal

/HOLD[=TTn:] where TTn:
is a CRT display terminal.
The /HOLD keyword enables hold-screen mode at the
specified 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 the
user types SHIFT/SCROLL
(types the SCROLL key while
pressing the SHIFT key).
The terminal then refills the
screen.
The user 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 very high
baud rates.
Note, however, that hold-screen mode may
not be appropriate for use with certain types of
programs (editors or terminals using different speed
for input and output, for example).

4-97

MCR COMMANDS

SET (Cont.)
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.
If the keyword omits =TTn:, the system displays at the
issuing
terminal
all the terminals currently in
hold-screen mode.
Examples:
>SET /HOLD=TT3:

Enables hold-screen mode on CRT terminal TT3:.
The
terminal erases its screen and positions the cursor at
the top left (home) of the screen.
>SET /HOLD
HDLD=TT3:

Displays
enabled.
NOHOLD

all

terminals

that

have

hold-screen

mode

/NOHOLD[=TTn:] where TTn:
is a CRT display terminal.
The /NOHOLD keyword disables hold-screen mode at the
specified terminal.
A nonprivileged user can display all terminals not
in
hold-screen mode, but can only disable the function at
TI:. A privileged user can disable hold-screen mode
for any terminal.
If the keyword omits =TTn:, the system displays at the
issuing terminal all CRT terminals that have disabled
hold-screen mode.
Examples:
>SET /NOHOLD=TT3:

Disables hold-screen mode at terminal TT3:.
>SET /NOHDLD
NOHOLD=TTO:
NOHOLD=TT3:

Displays all
disabled.
LINES

terminals

that

have

hold-screen

mode

/LINES=TTnn: [value] where TTnn:
is a terminal and
value is a decimal number in the range 1-255 inclusive
that establishes the number of lines per page.
This
option requires the full duplex terminal driver.

4-98

MCR COMMANDS

SET (Cont.)
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 the keyword omits the value parameter, the system
displays at the entering terminal the number of lines
per page for the entering terminal.
Examples:
>SET /LINES=TT3:
LINES=TT3:24

Displays the number of lines per page for TT3:.
>SET /LINES=TT3:20

Specifies the number of lines per page for TT3:.
LOWER

- /LOWER[=dev:] where dev:
is either a terminal or line
printer.
Specifies that lower-case characters are not
to be converted to upper case when they are received
from the specified terminal or line printer driver.
A nonprivileged user can display all devices that do
not convert lower-case characters to upper case, but
can only define this function for TI:.
A privileged
user can enable this function for any terminal or line
printer.
If the keyword omits =dev:,
all devices for which
lower-case characters are not converted are displayed.
Examples:
>SET /LDWER=TT3:

Inhibits conversion of lower-case characters
case when they are received from TT3:.

upper

>SET /LOWER
LOWER=TT1:
LDWER=TT3:

Displays all devices for which lower-case
are not converted to upper case.

characters

NOLOWER - /NOLOWER[=dev:] where dev is either a terminal or a
line printer.
Resets the device characteristics so
that
lower-case characters
received on input
are
automatically converted to upper case and echoed or
printed as upper case.
A nonprivileged user can display all the devices that
perform this conversion,
but can only specify this
function for TI:. A privileged user can specify any
terminal or line printer.

4-99

MCR COMMANDS

SET (Cont.)
If the keyword omits =dev:,
the system displays all
devices
for
which
conversion to upper case
is
specified.
Examples:
>SET /NOLOWER
NOLOWER=TTO:
NOLOWER=TT2:
NOLOWER=TTll:
NOLOWER=LP1:

Displays all devices that automatically
case characters to upper case.

convert

lower

characters

are

>SET /NOLOWER=TT3:

Resets TT3:
so that
converted to upper case.

4-100

lower-case

MCR COMMANDS

SET (Cont)

,._,,

- /PRIV[=TTn:].
Sets
privileged status.
A nonprivileged user can only display the terminals
that have privileged status.
A privileged user can set
any terminal to privileged status.
If the keyword omits =TTnn:, the
privileged terminals.

system

Examples:
>SET

/ PR I t,J =T T l :

Sets the status of TTl:

to privileged.

>SET I PR I t,J
PRil.J::TTO:
PR I t,l::TT 1:

Displays all privileged terminals.

4-101

displays

all

MCR COMMANDS

SET (Cont.)
NOPRIV

/NOPRIV[=TTn:].
Sets
nonprivileged status.

the

identified

terminal

A nonprivileged user can only display the terminals
that have nonprivileged status.
A privileged user can
set any terminal to nonprivileged status.
The keyword omits =TTn:,
nonprivileged terminals.

the

system

displays

all

Examples:
>SET /NOPR!l.l
NDPRil,l=TT2:
NDPRil,l=TT3:

Displays all nonprivileged terminals.
>SET /NOPRIV=TT1:

Sets the status of TTl:
PUB

to nonprivileged.

/PUB[=dev:].
(Multiuser protection systems only).
The
keyword establishes the specified device as a public
device.
When the keyword does not specify a
device
name,
the command displays all the current public
devices at the issuing terminal.
SET /PUB
is not a
privileged form of the command.
When the keyword specifies a device name,
the command
is privileged.
In all cases, a user must be privileged
to issue the SET /PUB=dev:
form of the command.
If the keyword omits =dev:,
public devices.

the

system

displays

all

Examples:
>SET /PUB=LP:

Establishes LPO:

as a public device.

>SET /PUB
PUB=DBO:
PUB=DB1:
PUB=LPO:

Displays all public devices.
NOPUB

- /NOPUB=[dev:].
(Multiuser protection systems only).
Causes the specified device to lose its public status.
Nonprivileged users can only display the devices
that
previously were made public.
Only privileged users can
issue the SET /NOPUB=dev:
command.
When the keyword omits =dev:, the system displays at
the issuing terminal all private and unowned devices.

4-102

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOPUB
NOPUB=DKO:
NOPUB=DK1:

Displays all private and unowned devices.
>SET /NOPUB=LPO:

Removes the public status for LPO:.
REMOTE

/REMOTE[=TTn:] where TTn:
is a terminal with a line to
a
DHll, DLll,
or DZll multiplexer.
The keyword
declares that the specified terminal is connected to a
modem and can be connected by means of a dial-up
network.
A nonprivileged user can display all remote lines,
but
can only establish device TI:
as a remote terminal.
Privileged users can define any terminal as a
remote
line.
When the keyword omits =TTn:, the system displays at
the
issuing terminal all remote lines (including DHll
lines).
Examples:
>SET /REMOTE
REMOTE=TT1:
REMOTE=TT2:
REMOTE=TT4:

Displays all terminals that are currently set as remote
dial-in lines.
>SET /REMOTE=TT3:

Sets the ~errninal line
remote dial-in line.

corresponding

TT3:

line to
a DZll
NOREMOTE- /NOREMOTE[=TTn:] where TTn:
is a
multiplexer.
The NOREMOTE keyword establishes the
to a
terminal's line as a local line not connected
modern.
A nonprivileged user can display all local lines,
but
can only establish device TI:
as a local terminal.
Privileged users can define any terminal as local.
When the keyword omits =TTn:, the system displays at
the
issuing terminal all local lines (including DLll,
DHll, DJll, and DZll multiplexers).

4-103

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOREMOTE=TT3:

Establishes the terminal line
line.

for

TT3:

local

DHll,

DJll,

>SET /NOREMOTE
NOREMOTE=TTO:
NOREMOTE=TT3:

Displays all local lines
and DZll multiplexers).
RPA

(including DLll,

/RPA[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only.
The /RPA keyword enables the
read-pass-all option of the full duplex
terminal
driver.
The
terminal
driver
passes all
input
characters to the driver input buffer.
A nonprivileged user can display all terminals that
have
the option enabled, but can only enable the RPA
option for TI:. A privileged user can enable RPA for
any terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have the RPA
option enabled.
Examples:
>SET /RPA
RPA=TTO:
RPA=TT1:

Displays all terminals where
passed directly to the full
input buffer.

input characters are
duplex terminal driver

>SET /RPA=TT3:

Enables the RPA option for TT3:.
NORPA

/NORPA[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only. The /NORPA keyword disables the
read-pass-all option. The full duplex terminal driver
does not pass special function input characters (such
as
~TRLt0)
from the terminal to the driver
input
buffer.
A nonprivileged user can display all terminals
that
have
the option disabled, but can only disable RPA for
TI:.
A privileged user can disable RPA for
any
terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that do not pass
special function characters to the terminal driver
input buffer.

4-104

...............................................------------------·----------------------------------------~

MCR COMMANDS

SET (Cont.)
Examples:
>SET I NOR PA
NORPA=TT2:
NORPA=TTll:

Displays all
disabled.

terminals

that

have

the

option

RPA

>SE T I N 0 R P A =T T 3 :

Specifies that TT3:
characters to the
buffer.
SLAVE

not pass special function
input
full duplex terminal driver input

/SLAVE[=TTn:] where TTnn:
is a terminal.
Establishes
the specified terminal as one that can enter data only
if it is solicited from a task;
thus,
the specified
terminal always rejects unsolicited input (other than
(CTRL/O)

(CTRL/Q) I

and (CTRL/S) ) •

A nonprivileged user can display all slave terminals,
but can only establish TI:
as a slave terminai.
Privileged users can establish any terminal as a
slave
terminal.
of

all

only

enter

Absence of TTn:
results
in the display
terminals currently classified as slaves.
Examples:
>S E T I S LA l,J E = T T 3 :

Establishes TT3:
as a terminal
data solicited by a task.

that

can

>SET /SLAl,JE
SLAl,JE=TT3:

Displays all slave terminals.
NOSLAVE - /NOSLAVE[=TTn:].
te rmi na 1.

Removes slave status from a specified

A nonprivileged user can only display the non-slave
terminals.
A privileged user can set any slaved
terminal to non-slave.
Absence of =TTn:
non-slave terminals.

results

4-105

the

display

all

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOSLAl.IE
NOSLAl.IE=TTO:
NOSLAt,IE=TT 1:
NOSLAt.JE=TT2:
NOSLAl,IE=TTll:

Displays all non-slaved terminals.
>SET /NOSLAVE=TT3:

Sets TT3:
SPEED

to non-slave status.

- /SPEED=dev: [recv:xmit]. Establishes the receive and
transmit baud rate for terminals attached to the system
through a DHll or DZll multiplexer.
The argument
"recv" is the baud rate at which characters are input
to the computer from the terminal;
and "x~it"
is the
baud rate at which the computer outputs characters to
the terminal.
Both must be specified in setting the
speed.
If neither is specified, the current settings
are displayed.
A nonprivileged user can display the speed settings for
any device,
but can only set the speed of device TI:.
A privileged user can set the speed of any terminal.
Valid baud rates for the DHll are:
O, 110,
300, 600, 1200, 1800, 2400, 4800, 9600,

150,

200,

Valid baud rates for the DZll are:
0, 110, 150, 300,
600, 1200, 1800, 2000,
2400,
3600, 4800, 7200, and
9600. The receive and transmit baud rates for the DZll
must be the same;
the DZll does not support split
speeds.
Examples:
-~

>SET /SPEED=TT3:
SPEED=TT3:300:300

Displays the current speed setting for TT3:.
>SET /SPEED=TT3:2ll00:2l!OO

Sets the receive and transmit baud rates for
2400.
TERM

TT3:

/TERM=TTnn: [value] where TTnn:
is a terminal and value
is a supported terminal type.
The /TERM keyword
establishes terminal type for a specified terminal.
Supported standard terminal types are:
ASR33
LA30S
VT05B
VT61

ASR35
LA36
VT50
VTlOO

KSR33
LA120
VT52

4-106

LA30P
LA180S
VT55

MCR COMMANDS

SET (Cont.)
A nonprivileged user can display the terminal type for
any
terminal, but can only establish terminal type for
TI:. A privileged user can establish terminal type for
any terminal.
When the keyword omits the value parameter
(terminal
type), the system displays at the entering terminal the
terminal type for the indicated terminal.
MCR accepts an alternate form of the command;
you
specify the terminal type and equate it to the desired
terminal.
For example:
SET /term-type=TTnn:
where term-type is one of the above
types.

standard

terminal

Examples:
>SET /TERM=TT3:
TERM=TT3: l.JT52

Displays the terminal type for TT3:
>SET /TERM=TT1:LA3G

Establishes TTl:

as an LA36 terminal.

>SET /LA3G==TT1:

Same effect as above example;
LA36 terminal.

establishes TTl:

You can also use the alternate command forms to display
all terminals that are not of a specific type.
The
format is as follows:
SET /NOterm-type
Note that you cannot negate a terminal type,
you can
only display the terminals not of a specific type;
negating terminal type returns a syntax error,
since
the terminal would be of indeterminate type.
is a terminal.
Full
TYPEAHEAD - /TYPEAHEAD[=TTnn:] where TTnn:
duplex terminal driver only.
This keyword instructs
the full duplex terminal driver to buffer
input
characters
before
passing
the
characters
to a
requesting task.
Thus,
characters
input
between
requests are not lost.
A nonprivileged user can display all terminals
that
have
the typeahead option enabled, but can only enable
the option for TI:.
A privileged user can enable
typeahead for any terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have typeahead
enabled.

4-107

MCR COMMANDS

SET (Cont.)
Examples:
>SET /TYPEAHEAD
TYPEAHEAD=TT1:
TYPEAHEAD=TTZ:

Displays all terminals for which the terminal driver
buffers input characters before passing them to a task.
>SET /TYPEAHEAD=TT3:

Enables the typeahead option for TT3:.
NOTYPEAHEAD - /NOTYPEAHEAD[=TTnn:] where TTnn:
is a terminal.
Full
duplex terminal driver only. This keyword disables the
typeahead option;
the full duplex terminal driver does
not buffer input characters to prevent their loss.
A nonprivileged user can display
have
the option disabled,
but
option for TI:.
A privileged
typeahead for any terminal.

all terminals that
can only disable the
user
can
disable

When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have typeahead
disabled.
Examples:
>SET /NDTYPEAHEAD
NOTYPEAHEAD=TTO:
NDTYPEAHEAD=TTLI:

Displays all terminals that have typeahead disabled.
>SET /NDTYPEAHEAD=TT3:

Disables the typeahead option for TT3:.
UIC

- /UIC[=uic[:dev:]]. The specified UIC is established as
the default UIC for the entering terminal unless dev:
is specified, in which case the default UIC is set for
that
terminal.
If the system supports multiuser
protection, and the user
is privileged,
the command
also sets the terminal's protection UIC.
(See Section
3.2.1.) All tasks run from the terminal are run with
the
UIC of the terminal,
except in a multiuser
protection system.
In such a system, a privileged user
can override the terminal UIC with the UIC switch in
the Run command.
Further, external MCR function tasksl
are requested with this UIC.
If a UIC
is not specified,
the current U~~
is
displayed.
If only dev:
is specified, the UIC for the
specified terminal
is displayed,
provided that the
terminal issuing the command is privileged.

l
These tasks are the MCR Mount, Install, Dismount, and UFO
(which run as tasks) and all system-supplied software.

4-108

commands

MCR COMMANDS

SET (Cont.)
Examples:
>SET /UIC
UIC=C 10 t10J

Displays the current default UIC for terminal TI:.
>SET /UIC=C30313J

Sets the default UIC for terminal TI:
VFILL

[303 ,3].

- /VFILL[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal
driver
only.
This keyword enables the
vertical fill characters option for
the specified
terminal.
The
option instructs the full duplex
terminal driver to add four fill
characters
following
each linefeed.
A nonprivileged user can display all terminals that
have
the option enabled,
but can only enable it for
TI:. A privileged user can enable VFILL for any
terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have VFILL
enabled.
Examples:
>SET /l,JFILL
t,JFILL=TTO:
t,JFILL=TT1:

Displays all
enabled.

terminals

that

have

the

VFILL

option

>SET /l,JFIL.L=TT3:

Instructs the full duplex terminal driver to add
fill characters following each linefeed at TT3:.

four

NOVFILL - /NOVFILL[=TTnn:] where TTnn:
is a terminal.
Full
duplex terminal driver only. This keyword disables the
vertical fill option.
A nonprivileged user can display all terminals
that
have the option disabled, but can only disable it for
TI:. A privileged user can disable the VFILL option
for any terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have the VFILL
option disabled.

4-109

MCR COMMANDS

SET (Cont.)
Examples:
:>SET /NOl,JFILL
l\IOl,JF I LL= TT2:
l\IOl,JFILL=TTLI:

Displays all
disabled.

terminals

that

have

the

VFILL

option

:>SET /NOVFILL=TT3:

Disables the VFILL option for TT3:.
WCHK

- /WCHK [=dev:].
Specifies for
all Files-11
devices
except DX:, DL:
and magnetic tape (MT:, MM:, MS:) that
all writes are to be followed by a write check.
This
feature provides high reliability for data transfers to
the specified disk.
A nonprivileged user can only display the Files-11 disk
drives with write check enabled.
A privileged user can
enable write checking for any device that supports it.
If the keyword omits =dev:, all Files-11
with write check enabled are displayed.

disk

drives

Examples:
:>SET /WCHK
WCHK::: DBO:
WCHK==DKO:

Displays all Files-11 disk drives that have write check
enabled.
:>SET /WCHK=DK1:

Enables write check on DKl:.
NOWCHK

/NOWCHK[=dev:]. Specifies that write check
disabled for the specified device.

A nonprivileged user can only display the Files-11 disk
drives
that have write check disabled.
A p~ivileged
user can disable write check on any device.
If the keyword omits =dev:, all Files-11 devices except
DX:
and DL:
and magnetic tape (MT:, MM:, MS:) that
have write check disabled are displayed.
Examples:
:>SET /NOWCHK
NOWCHK=DB1:

Displays all the devices that support write check,
have it disabled.

4-110

but

MCR COMMANDS

SET (Cont.)
>SET /NOWCHK=DKl:
Disables write check for DKl:.
WRAP

/WRAP[=TTnn:] where TTnn:
is a terminal.
Full duplex
terminal driver only.
This keyword enables the wrap
around option.
The wrap around option
instructs
the
full
duplex terminal driver to generate a carriage
return/linefeed sequence when the number of
input
characters exceeds
the
terminal's
buffer size.
The
carriage return/linefeed sequence is transparent and
does not appear in the input buffer.
A nonprivileged user can display all terminals
that
have
the option enabled,
but can only enable it for
TI:.
A privileged user can enable wrap around for
any
terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all terminals that have the wrap
around option enabled.
Examples:

>SET /WRAP
WRAP=TTl:
WRAP=TT2:
Displays
all
terminals
for
which
a
carriage
return/linefeed sequence is generated following
an
input string that exceeds the terminal's buffer size.

>SET /WRAP=TT3:
Enables the wrap around option for TT3:.
NOWRAP

- /NOWRAP[=TTnn:]
where TTnn:
is a
terminal.
Full
duplex terminal driver only.
This keyword disables the
wrap around option;
the full
duplex terminal driver
does not accept input characters beyond the buffer size
for the terminal.
A nonprivileged user can display all terminals
that
have
the option disabled, but can only disable it for
TI:.
A privileged user can disable the option for
any
terminal.
When the keyword omits =TTnn:, the system displays at
the entering terminal all
terminals
that have the
option disabled.

4-111

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOWRAP
NOWRAP=TTO:
NOWRAP=TTll:

Displays all terminals that have the option disabled.
>SET /NOWRAP=TT3:

Disables the wrap around option for TT3:.
(Privileged option)

Enable or Disable Logon Keywords:
LOG ON

- /LOGON.
Enables logging onto terminals in a multiuser
protection system.
The keyword is privileged.

NOLOGON - /NOLOGON.
Disables logging onto terminals
in
a
multiuser
protection
system.
The
keyword
is
privileged.
/LOGON and /NOLOGON clear and set a
flag
checked by
the Hello command when a user attempts to
log onto a terminal. This Set option provides a means
of preventing users
from accessing the system during
system maintenance
or
account
file
maintenance
activity, for example.
I/O Packet Keyword:
MAX PKT

/MAXPKT[=n]. The /MAXPKT keyword 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.
A nonprivileged user can only display the
current number of available I/O packets.

maximum

and

If the keyword omits n,
the system displays at the
issuing terminal 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 and
current number of available I/O packets.

the

retained

for

Examples:
>SET IM A}-{ PKT= 1 2 ,

Sets the maximum number of
I/O packets
optimization of I/O servicing to 12(10).
>SET /MA}<PKT
MAHPKT=12. :3.

The maximum number of
I/O packets to be retained
explicitly for QIO processing is 12(10). Three packets
are currently available.

4-112

MCR COMMANDS

SET (Cont.)
System or Library UIC Keywords:
SY SU IC

/SYSUIC[=uic] where uic has the format [g,m]; g and m
are octal numbers that represent a group and member
number respectively. The /SYSUIC keyword establishes
the UIC for the system and all system tasks.
On most
unmapped systems, the system UIC is
[l,50];
on most
mapped systems,
the system UIC is [1,54]. These UIC
values are the initial defaults on virgin systems.
This UIC becomes the default UIC used by the Load
command and the install-run-remove option of the Run
command.
A nonprivileged user can only display the system UIC.
When the keyword omits =uic, the system displays at the
issuing terminal the current system UIC.
Examples:
>SET /SYSUIC
SYSUIC=C 1 t5l!J

Displays the current system UIC.
>SET /SYSUIC=[315llJ

Sets the system UIC to [3,54].

4-113

MCR COMMANDS

SET (Cont.)
Memory Allocation Keywords:
/MAIN=pname[:base:size:type]
/NOMAIN=pname

(Privileged RSX-llM keyword)

/SUB=mname:pname [:base:size]
/NOSUB=mname:pname

(RSX-UM keyword)

(RSX-llM keyword)

/PAR=pname [:base: size [:type]]
/NOPAR=pname

(Privileged RSX-llM keyword)

(RSX-UM-PLUS keyword)

(RSX-llM-PLUS keyword)

/POOL[=top]
/MAXEXT[=size]
Keyword Definitions:
MAIN

- /MAIN=pname[:base:size:type].
An
RSX-llM
keyword.
Establishes a main partition. A nonprivileged user can
only display the base,
size,
and type of a main
partition.
pname

- The 1- to 6-character alphanumeric
name.

:base

- Physical base address of
the
partition
specified as a number of 64-byte blocks.

:size
:type

Size of the partition specified as
of 64-byte blocks.

partition

number

- TASK for a user-controlled task partition
SYS for a system-controlled task partition
COM for a common partition
DEV for a common partition mapping
device registers

into

the

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

4-U4

MCR COMMANDS

SET {Cont.)
Base and size may be entered in any of the following
formats;
nnnn is a number
(in bytes)
to which a
multiplication factor is applied to determine the value
used.
Format

Calculated Value

nnnn
nnnn.
nnnK
nnn.K

Octal (nnnn*lOO)
Decimal (nnnn.*64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

Valid ranges of calculated values
Octal
Decimal
Octal K
Decimal K

(in words) are:

O<=base<l 77777
O.<=base<65535
OK<=base<3777K
O.K<=base<2047.K

O<size<2000
O.<size<l024.
OK<size<40K
O.K<size<32.K

For system-controlled partitions, size may range
from 0 to 1920.K or any valid representation of
these limits.
For example, any of the following inputs for
will allocate a 1920. - byte partition.

size

40
32.
lK
l.K

If the command does not specify base, size,
and type,
MCR displays the values of these parameters for the
named,partition.
If the named partition is a
task
partition,
MCR also displays the parameters of all its
subpartitions.
Examples:
>sET /MAIN=SYSPAR:420:140:TASK

Defines a
main
partition
named
SYSPAR
as
user-controlled
partition
whose
base address
42000(8) and whose length is 14000(8) bytes.

a
is

>sET /MAIN=SYSPAR
MAIN=SYSPAR:0420:0140: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

- /NOMAIN=pname.
Eliminates the
system.

A
privileged,
named partition

4-115

RSX-llM
keyword.
or library from the

MCR COMMANDS

SET (Cont.)
Example:
>SET /NOMAIN=SYSPAR

Eliminates the main partition SYSPAR from the system.
SUB

- /SUB=mname[:sname:base:size].
An
RSX-llM
keyword.
Establishes a subpartition. Subpartitions may only be
established in user-controlled main partitions.
mname

- The 1- to 6-character main partition
name.
The subpartition being defined
becomes a subpartition in the named main
partition.

:sname

- The 1- to 6-character subpartition name.
The subpartition being defined becomes a
subpartition of
the
main
partition
specified in mname.

:base

- Physical
base
address
of
the
subpartition,
specified as a number of
64-byte blocks.

:size

Size of the subpartition, specified as a
number of 64-byte blocks.

Base and size may be entered in any of the following
formats;
nnnn is a number
(in bytes)
to which a
multiplication factor is applied to determine the value
used.
Format

Calculated Value

nnnn
nnnn.
nnnK
nnn.K

Octal (nnnn*lOO)
Dec ima 1 (nnnn. *64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

Valid ranges of values
Octal
Decimal
Octal K
Decimal K

(in words) are:

O<=base<lOOOO
O.<=base<4096.
OK<=base<200K
O.K<=base<2047.K

O<size<2000
O.<size<l024.
OK<size<40K
O.K<size<32.K

For example, any of the following inputs for
size will allocate a 2048. - byte partition.
40
32.
lK
l.K

If base and size are omitted, the current
be displayed for the named subpartition.

4-116

values

will

MCR COMMANDS

SET (Cont.)
Examples:
>SET

/SUB=SYSPAR:MCRPAR:445:5~

Defines a
subpartition named MCRPAR in the
main
partition SYSPAR whose base address is 44500(8) and
whose length is 5600(8) bytes.
NOSUB

- /NOSUB=mname:sname.
A privileged, RSX-llM
Eliminates the named subpartition
{sname)
specified main partition {mname).
Example:
>SET

keyword.
from the

/NOSUB=SYSPAR:MCRP~R

Eliminates the subpartition
partition SYSPAR.

4-117

MCRPAR

from

the

main

MCR COMMANDS

SET (Cont.)
Base and size can be entered in
formats
where
nnnn
is
a
multiplication factor is appli~d
us·ea:
Format
nnnn
nnnn.
nnnK
nnn.K

of calculated
Octal
Decimal
Octal K
Decimal K

o.
0
0

For SYS partitions, size
any valid representation
Any 0£ the following inputs
19 2 0 • .;.. by t e part it ion :
40

32.

--,

lK
l.K

When the keyword omits base1
displays .. at the entering te
pa~ametefs for the speciJied
c~eate

RSX-11W·PLUS
or ~dd de~ice

pa~e

of the desired

/AFF=[CPx]

c, or o.
.···NQPAR

/NOPAR=pname.

An RSX-llM-PLUS

named partition (pname)
cannot eliminate a partition
are install~d or attached

the

ro.essa9e.
POOL

/POOL[=top].
region.
top

Increases the size of the dynamic storage

- Specifies the first location in memory to be
used
for
user partitions.
Specify the
location in units of 64-byte blocks.
It can
be given in octal or decimal.

4-118

MCR COMMANDS

SET (Cont.)
The format is:
POOL= top:max:total
where top is given in units of 64-byte blocks.
total are in decimal words.

max and

A nonprivileged user can only display the size
dynamic storage region~

the

If the keyword omits =top, the system displays the size
of the dynamic storage region in the format:
POOL=floc:lfb:tps
where:
floe
is the first
user
partitions
location for
(displayed in octal bytes with two trailing zeroes
suppressed).
lfb is the longest free
words).

block

(displayed

decimal

tps is the
words).

space

(displayed

decimal

the

beginning

for

total

pool

Examples:
>SET /POOL=ll20

Establishes
partitions.

42000(8)

user

>SET /POOL
POOL=Oll20:150,:ll30+

Displays the first location for user partitions,
the
longest free block,
and the total of all pool space
(the first free block is at 42000,
the longest free
block
is 150. words, and the total of all pool space
is 430. words.
MAX EXT

- /MAXEXT[=size]. Establishes the maximum size to which
a
task can extend itself by means of the Extend Task
directive (see the RSX-llM/M-PLUS Executive Reference
Manual).
The keyword is privileged and is only valid
on mapped systems that choose to support the Extend
Task directive at system generation. The maximum size
can be expressed in four formats:
n

nK
n.
n.K
See the description of /MAIN or /SUB for
of these size values.

4-119

definition

MCR COMMANDS

SET (Cont.)
If the keyword omits =size, the system displays at
issuing terminal the current maximum size in
format:

the
the

MAXEXT=m
where m is an octal number equal to the maximum size
allowed for a task,
in 64-byte blocks (for example,
1200 indicates 20K words).
A nonprivileged user can
only display the maximum size to which a task can
extend itself.
Examples:
>SET

/MA><D:T=20K

Establishes 20K as the maximum size to which a task can
extend itself.
>SET /MA><D:T
MAHE>:T= 1200

Displays the current
extend itself.

maximum

size

that

task

can

Notes:
If a partition currently contains a task, and a
keyword
(for
• example,
/NOMAIN
or /NOSUB)
attempts to eliminate the
partition, the system rejects the command.
•

A keyword that eliminates a main partition also eliminates all
its subpartitions.
A keyword that eliminates a specified
subpartition eliminates only that specified subpartition.

•

If a keyword attempts to eliminate a main partition that has
subpartitions in which tasks are installed, the system rejects
the keyword until those tasks
are
removed
from
the
subpartitions.

•

When defining a partition (main or sub)
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
Device .partitions, which can overlap.

•

The numeric value convention applies to all
numeric values.

•

All partitions except the resident loader partition,
• LDR.,
are considered user partitions by the POOL command. Thus, for
example, SYSPAR is considered a user partition.

•

Once you allocate space to the dynamic storage region,
space can never be recovered for use in partitions.

4-120

the

Set

command

the

MCR COMMANDS

SET (Cont.)
•

System-controlled partitions cannot include
subpartitions
explicitly defined by the Set command.
An attempt to define
subpartitions of system-controlled partitions in this way will
be rejected. The Executive dynamically defines subpartitions
of a system-controlled partition as needed for tasks installed
in the system-controlled partition.

Console Output Task Keywords:
/COLOG =

TTnn:
}
dev: [uic]filename.typ
{ TTnn:dev: [uic]filename.typ

/NOCOLOG
/CO TERM [ =TTnn:]
/LOGFILE[=dev: [uic]filename.typ]
See the RSX-llM or RSX-llM-PLUS SYSTEM Generation and Management Guide
for
a description of the Console Output Task (COT). All of the COT
keywords are privileged.
If COT is not active, the keywords
initiate
console logging using default or user-supplied console terminal and
listing file specifications. The /COLOG keywords provide a means to
change both the console terminal and the listing file specifications.
The /COTERM and /LOGFILE keywords change a single specification.
Keyword Definitions:
CO LOG

/COLOG.
If the console output task
is active,
the
keyword displays the name of the listing file and the
terminal number for the console terminal.
If COT is
not active,
the keyword initiates console logging
using TTO:
as the default console terminal and the
file SY: [1,4] CONSOLE.LOG as the default listing file.
Example:
>SET /COLOG
CONSOLE
TTO:
LOGFILE = SYO:[ltl!JCONSOLE.LOGi1G

Displays the default console terminal and the name
the listing file.

/COLOG=TTnn:. If COT is active,
the keyword closes
the current listing file, opens the next version as
the new listing file, and uses the specified terminal
as the console terminal.
If COT is not active, the
keyword initiates console logging using the specified
terminal
as
the console terminal and the file
SY:[l,4]CONSOLE.LOG as the default listing file.
Example:
>SET

/COl....OG:::TT3 ~

Creates a new version of the listing
TT3:
as the console terminal.

4-121

file

and

uses

MCR COMM.ANDS

SET (Cont.)
- /COLOG=dev: [UIC]filename.typ.
If COT is active,
the
keyword
closes
the listing file and opens the
specified file for use as the listing file.
Note that
TTO:
becomes the default console terminal;
if you
wish to change only the listing file, use the /LOGFILE
keyword.
If COT is not active, the keyword initiates
console logging using the specified file as the
listing file and TTO:
as the console terminal.
Example:
>SET /COLOG=DB1:[11llJTEMP+LOG

Closes the current listing file
and opens the
file
DBl:[l,4]TEMP.LOG. The console terminal becomes TTO:.
- /COLOG=TTnn:dev: [UIC]filename.typ.
If COT is active,
the
keyword closes the listing file,
opens the
specified file for use as the listing file,
and uses
the specified terminal as the console terminal.
If
COT is not active,
the keyword
initiates console
logging using the specified terminal and listing file.
Example:
)SET /COLOG=TT2:DB:[3,GJNEW.LOG

Closes the current listing file and uses TT2:
as the
console terminal and the file DB:[3,6]NEW.LOG as the
listing file.
NOCOLOG

- /NOCOLOG. This keyword instructs COT to close the
current listing file, redirect CO:
to TTO:, and exit.

CO TERM

/COTERM[=TTnn:].
If COT is active,
the
keyword
redirects console terminal messages to either TTO:
(the default console terminal)
or to the specified
terminal.
Note that the keyword does not close or
increment the version number of the current listing
file.
If COT is not active, the keyword initiates
console logging using TTO:
or the specified terminal
as the console terminal.
Note that the keyword
initiates COT without a listing file.
When the keyword omits =TTnn:,
messages are printed on TTO:.

console

terminal

Example:
>SET /COTERM=TTG:

Redirects console terminal messages to TT6:.
If COT
was not active when the command was issued, console
terminal messages are not written to a listing file.

4-122

MCR COMMANDS

SET (Cont.)
NOCOTERM - /NOCOTERM. This keyword
inhibits the printing of
messages on the console (or the redirected console)
terminal.
Console terminal messages are recorded
in
the listing file.
The keyword is valid only if COT is
active.
Example:
>SET /NOCOTERM

Inhibits printing of messages on the console terminal.
NOTE
If the first character of a console
terminal message
is a (cm~~
and there
is no assigned console terminal,
the
message is printed on TTO:.
If there is
an assigned
console
terminal,
the
message
is printed on the appropriate
console terminal.
LOG FI LE:

/LOGFILE[=dev: [uic]filename.typ.
If COT is active,
this keyword closes the current listing file and
either increments the version of the current file
(if
you omit the
file specification)
or creates a new
listing file using the specified file.
If COT is not
active,
the keyword
initiates console logging using
SY:[l,4]CONSOLE.LOG or the specified file as the
listing file.
Note that the keyword initiates COT
without a console terminal; console terminal messages
are written in the listing file only.
When the keyword omits a fjle
specification,
console
terminal messages are written in SY:[l,4]CONSOLE.LOG.
Example:
>SET /LOGFILE

Closes the current listing file and then uses the next
highest version of SY:[l,4]CONSOLE.LOG as the listing
file.
If COT was not active when the command was
issued,
console terminal messages are not printed on
the console terminal.
Command Error Messages:
SET -- ALIGNMENT ERROR
An attempt was made to create a partition,
base
address
or
size conflicted with
partitions or physical memory size.

4-123

but the
existing

MCR COMMANDS

SET (Cont.)
SET -- DEVICE NOT VARIABLE SPEED MULTIPLEXER
An attempt was
terminal that
multiplexer.

made to
was not

set the
attached

baud rate for a
to a DHll or DZll

SET -- DEVICE NOT TERMINAL
An attempt was made to set
for a nonterminal device.

terminal

characteristics

SET -- FEATURE NOT SUPPORTED
The command keyword specifies an optional feature that
was
not
incorporated into the system at system
generation.
SET -- INVALID SPEED
The multiplexer line specified does not support the
requested speed;
or the command specified unequal
receive and transmit speeds for a DZLl. The DZll does
not support split speeds.
SET -- LINE NOT DZll
The command attempted to set to remote a line that was
not attached to a DZll multiplexer.
SET -- NON EXISTENT MEMORY
An attempt was made
nonexistent memory.

define

partition

SET -- OVERLAP SEEKS NOT SUPPORTED
The command
support for
controller.

attempted to enable overlapped
seek
other than a DM,
DP, or RH device

SET -- PARTITION ALREADY EXISTS
An attempt was made to define a partition with a
already in use.

name

SET -- PSEUDO DEVICE ERROR
The command attempted to make a pseudo device
Pseudo devices cannot be public devices.

public.

SET -- SPACE USED
An attempt was made to create a
partition
subpartition in a storage area already occupied.

SET -- TASK INSTALLED IN PARTITION
An attempt was made to eliminate a main partition
subpartition containing installed tasks.

4-124

MCR COMMANDS

SET (Cont.)
SET --· TOO MANY SUBPARTITIONS
An attempt was made to define more than
seven
subpartitions.
A main partition is limited to a
maximum of seven subpartitions.
SET --· UNKNOWN MAIN PARTITION
An attempt was made to define
nonexistent main partition.

subpartition

SET -- USER PARTITION >32K NOT PERMITTED
The command attempted to create a partition greater
than 32K. User-controlled partitions greater than 32K
cannot be created in systems that do not support
extended logical address space, a system generation
option.
SET --· WRITE CHECK NOT SUPPORTED
An attempt was made to enable write check on a device
that was not a DB:, DF:, DK:, DM:, DP:, DR:, or DS:.

4-125

MCR COMMANDS

STP
STOP
The Stop command declares that a specified task is no longer eligible
to execute or compete for memory.
Nonprivileged users can only stop a
task requested from the issuing terminal.
A privileged user can stop
any task.
Stopping a task sets the stop bit in the Task Control Block
(TCB).
When a task's stop bit is set, the system considers the task blocked
as well as ineligible to compete for system resources.
To clear the
stop bit, issue the Unstop command.
Format:
STP

[taskname] [/TERM=TTnnn:]
~

where:

taskname

is the name of the task to be stopped.
If you
omit
taskname,
the
command stops the task
requested from the issuing terminal (TTnn).

-.: ....' :.·. ·· . .:·.:·· ............... -.:":·>

is. ·a.privileged. RSX--llM-·P~US k~y~~r~ ~tj~~ ~~~k~ ~·:h
task not
initiated from tn~ en~E(r~Q9 ;e.f(Ufp~}.• ·
See Section 4.2.3~
·
·
Examples:
RSX-llM systems
>STP BOBT17

Stops task
memory.

BOBT17

and

removes

from

competition

for

and

removes

from

competition

for

RSX-llM-PLUS system:
~TP

BOB/TERM=TT100:

Stops task
memory.

BOBTAO

Al\.

4-126

MCR COMMANDS

TAL
TASK LIST - ATL FORMAT
This command displays on the entering terminal the names and status of
all tasks or of a specific task installed in the system.
The display
format is the same as that of the Active Task List (ATL) command.
See
the ATL command for a description of the printout.
Format:
TAL [taskname]
where taskname is the name of a specific task.
Example:
>TAL
, LOR, 052220 LOR
052184 00000000-00000000 PRI - 248.
DPRI - 248.
STATUS:
-CHK FXD STP PRV
TI - COO:
IOC - O,
EFLG - 000001 000 000 PS - 170000
PC - 041350
REGS 0-8 000182 004030 177777 105312 084254 105280 052132
TKTN
105010 SYSPAR 107734 00110000-00120000 PRI - 248,
OPRI
248.
STATUS:
-EXE OUT -CHK -PMD PRV
TI - COO:
IOC - O,
EFLG - 000001 000000
RMDEMO 058214 GEN
053740 00217500-00233300
PRI - 225.
DPRI
225,
STATUS: WFR PRV CAL
TI - TTO:
IOC - O,
EFLG - 000001 000000 PS - 170010
PC
125072
REGS 0-8
123353 000070 000000 125032 001801 131530 12035i

PIPT2 081454 GEN
071524 00274300-00335300
STATUS:
OUT CKP TIO STP WFR -PMD REM MCR
TI
TT2:
IOC - O,
EFLG - 000003 040000

PRI - 50,

DPRI - 50.

>TAL. RMDEMO
RMDEMO 058214 GEN
053740 00217500-00233300 PRI - 225,
DPRI - 225+
STATUS:
WFR PRV CAL
TI - TTO:
IOC - 1,
EFLG - 000000 000000 PS - 170010
PC - 130224
REGS 0-8
000050 000132 000000 125032 001801 131530 120350

4-127

MCR COMMANDS

TAS
TASK LIST
The Task List command displays on the entering terminal a
of each installed task.
The display contains:
1.

Task name

Task version identification

Partition name

Task priority

Size of task in bytes

Load device identification

Disk address logical block number

Task memory state

description

(octal)

Format:
TAS[KLIST]
Example:
>TAS
, , , LOR
TKTN
RMDEMO
MTAACP
F11MSG
MCR,,,
DCL,,,
, , , DCL
TAST17
, , , STD
, , , BYE
F11ACP
SECFCP
DTAACP
,,,OMO
.. , INI
••• MOU
, ,,UFO

07.05
03.3
}{03.03
0008
l,J0010
3.2
0113A
0113A
01
000005
01. 5
M0235
M0235
M0235
03+2
03. 1
03.01
l,10407

LDRPAR
SY SPAR
GEN
GEN
GEN
SY SPAR
SY SPAR
GEN
GEN
SYS PAR
GEN
FCPPAR
GEN
GEN
GEN
GEN
GEN
GEN

(operator typed

248. 00002200 LB0:-01035303 FI )<ED
248. 00010000 LB0:-01128742
225+ 00013700 SY0:-00352100
zoo. 00013000 DS0:-00000777
200+ 00005400 SY0:-01053030
180+ 00010000 LB0:-01051828
180. 00010000 LB0:-00587017 CHECK POINTED
180. 00040000 LB0:-01221102
180+ 00025000 LB0:-01051878
151 • 00010000 SY0:-01138540
150. 00040000 LB0:-01051337
148 + 00040000 LB0:-01052445
14 9. 00028200 SY0:-00055483
149. 00028200 SY0:-01052554
1 40 + 000400!)0 LB0:-01051403
140. 00040000 LB0:-01051581
140. 00040000 LB0:-01051853
1 40 + 00040000 LB0:-010

(cTRw~

to suppress further output)

The display contains, in columnar form, from left to right:
task
name, 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
memory to make room for a higher priority task.

4-128

swapped

out

MCR COMMANDS

TAS (Cont.)
If the task version identification is missing (the rest of the
line is offset to the left) or garbage, the task was installed
from a disk that has since been removed from the drive or
replaced by another cartridge.

4-129

MCR COMMANDS

TIM
TIME
The Time command makes it possible to:
•

Set the current time of day

(privileged}

•

Set the current date

•

Display the current time and date

(privileged}

Format:
TIM[E]

[hrs:mins[:secs]]

[ml/day/year]

or
TIM[E]

[hrs:mins [:secs]] [day-m2-year]

where:
hrs

- Hours

(range 0-23}

mins - Minutes

(range 0-59}

secs - Seconds

(range 0-59}

(optional}

- Numeric representation of month

day

- Day

(range 1-12}

3-letter abbreviation for month
(range 1-31)

year - Year (range 0-99).
Year is relative to 1900;
1979 is entered as 79.

thus,

Notes:
•

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

•

A privileged user can specify the time
order.

•

All numeric values are decimal.
necessary (or permitted}.

and

date

terminating

period

Examples:
>TIM
10~23~31

03-NDV-78

Displays the current time and date.
>TIM 1:30 11/7/78

Sets the time to 01:30:00 and the date to 07-NOV-78
4-130

either
is

MCR COMMANDS

UFO
USER FILE DIRECTORY
This command creates a User File Directory (UFO) on a Files-11 volume
and enters its name into the Master File Directory (MFD).
See Section
3.1.l for further information about UFOs.
Before defining a UFO in an
RSX-llM system, you must first initialize and mount (IN! and MOU) the
volume.
You can add UFOs at any time after initializing and mounting
a
volume.
Before defining a ,UFO in an RSX-llM-PLUS system, you must
first mount the volume (if the volume has not been initialized,
mount
the· volume as foreign) and, if necessary, initialize it.
You can add
UFOs at any time after mounting a volume.
In multiuser protection systems, a nonprivileged user can create a UFO
only on a volume mounted on the user's private device (that is, a
device that the user has allocated).
Otherwise the user must
issue
the command from a privileged terminal.
Form.at:
UFO ddn: [volume-label] [group,member] [/keyword] [/keyword]
Keywords:
/ALLOC=number-of-entries
/PRO=[system,owner,group,world]
where:
ddn:

- Device-unit containing the volume on
the UFO being created will reside.
Default: none;

volume-label

which

must be specified.

- If specified, the label
is compared with
the label on the volume.
If the names
match, a UFO can be allocated.
If they do
not match, the command is rejected.
Default: nulls;

no check is made.

[group,member] - The UIC for the UFD. The UIC establishes
the owner of the UFD. The square brackets
are required syntax.
Default: none;
ALLOC

must be specified.

- Number of directory entries for which space
is to be allocated. The number provided is
rounded up to the next multiple of 32(10).
Default : 3 2 ( 10)

4-131

MCR COMMANDS

UFO (Cont.)
-

PRO

Establishes access rights for the directory
file.
Access codes consist of four 4-code
groups
in the Access Rights word,
as
follows:
R WE D -

Read
Write
Extend
Delete

In each instance, the absence of
the code
means that the user class is denied the
access right.
Defaults:

[RWED,RWED,RWED,R]

Example:
>UFO DK1:[111J

Create a user file directory (UFD)
for
the UIC
[1,1]
on
DKl:.
The name and file number of the UFD file are entered
into the MFD. The name of the UFD is 001001.DIR;l, and
its
owner is UIC [1,1].
Command Error Messages:
UFD -- CAN'T READ MCR COMMAND BUFFER
The UFD was initiated by a Run command rather than
an MCR command.

UFD -- DIRECTORY ALREADY EXISTS
The requested UFD already existed on the volume.
UFD -- FAILED TO CREATE DIRECTORY
No space existed
occurred.

the

volume,

I/O

error

UFD -- FAILED TO ENTER IN MFD
There was no room in the MFD or on the volume,
I/O error occurred on the volume.

UFD -- HOME BLOCK I/O ERROR
An error was
block.

detected

reading

the

volume

home

UFD -- NOT FILES-11 DEVICE
The device on which the UFD was to be created was not
a Files-11 device,
and therefore could not support
UFDs.

4-132

MCR COMMANDS

UFO (Cont.)
UFD -- VOLUME NOT MOUNTED
The volume on which a UFD is to be created must
mounted before accessing the Files-11 structure.

UFD -·- WRITE ATTRIBUTES FAILURE
An error was encountered while writing the attributes
of either the MFD or the newly created UFD.
UFD -- WRONG VOLUME
The volume label and
command did not match.

4-133

the

label

specified

the

MCR COMMANDS

UNS
UNSTOP
The Unstop command continues execution of a previously stopped task.
A nonprivileged user can issue the Unstop command only for tasks
initiated from the entering terminal. A privileged user can direct
the Unstop command to any stopped task.
Format:
UNS [TOP]

[taskname] [/TERM=TTnnn:]

where:
taskname

is the name of the task.
If you omit taskname,
the command allows the task requested from the
issuing terminal (task TTnn) to continue.

is a privileged RSX-llM;..PLUS keywC>rd

/'I'ERM:Z:'I'Tnnn:

that .•· .61.e~.r;~\.·

stop bit for a task not r~q1.1ested f.rom· tl:le.< ·
entering terminal. See Section 4~2.3,

the

Examples:
RSX-llM system:
>UNS

BOBT17

Clears the stop
executing.

bit

for

task

BOBT17

and

allows

continue

task

BOBTDl

and

allows

continue

RSX-llM-PLUS systems
>UNS

BOB/TERM=TT131:

Clears the stop
executing.

bit

for

4-134

MCR COMMANDS
4.6

PRIVILEGED MCR COMMAND DESCRIPTIONS

ACS
ALLOCATE CHECKPOINT SPACE
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-11 format.
Only one checkpoint file per disk is
allowed;
but numerous disks can each contain a checkpoint file.
In
general,
sufficient checkpoint space is twice the total amount of
memory that all of the running tasks are using.
When looking for file space to checkpoint a task, the system initially
searches the first
checkpoint file to be created.
If space is not
available in the primary file, it searches the second file
to be
created,
and so on.
The order in which checkpoint files were created
determines the order
in which the system scans
the files when
searching for available checkpoint space.
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 ~as been made, the system does not use the file
for
any more
checkpointed tasks.
Format:
ACS ddn:/BLKS=n
where::
ddn:

- A device-unit that contains a mounted Files-11
di sk•
I f the uni t numb e r ( n ) i s not spec i f i e d , i t
defaults to 0.

/BLKS

- /BLKS=n.
A keyword that specifies the number
(n)
of blocks on the disk
to be allocated for the
checkpoint file.
(A block is 512(10) bytes long.)
For example, the command
>ACS DB:/BLKS=250,

allocates 250(10) blocks for a checkpoint file
DB:.

When n is O, the system discontinues the use of
the checkpoint file;
the file is neither deleted
nor truncated.
For example, the command
>ACS DB:/BLKS=O

discontinues the checkpoint file on disk DB:.

4-135

MCR COMMANDS

ACS (Cont.)
When n is 1, the system deallocates the space used
for the checkpoint file.
Examples:
>ACS DS:/BLKS=250.
>ACS DB:/BLKS=1024.

Allocate a primary and a secondary checkpoint file.
The
primary file on DS:
(a fixed-head disk) is 250(10) blocks
iong.
The secondary file on DB:
is 1024(10) blocks long.
>ACS DS:/BLKS=O

Discontinue use of the checkpoint file on DS:.
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-unit.
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 were still
in use,
TKTN would issue a message when the file was
finally discontinued.
ACS -- DYNAMIC ALLOCATION OF CHECKPOINT SPACE NOT SUPPORTED
The ACS command was issued on a system that did not
include support of dynamic allocation of checkpoint
space at system generation.
ACS -- FILE I/O ERROR nnn.
The ACS command detected an error when it tried to
allocate or op~n the checkpoint file. The code nnn.
is an FCS error code that defines the cause of the
error.
See
Appendix
I
of the IAS/RSX-11
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 space
to allocate 'the file.
The normal implication of the
code -24 is device full.)
ACS -- FILE NOT IN USE
A checkpoint file was not
specified in the ACS command.

4-136

use

the

device

MCR COMMANDS

ACS (Cont.)
ACS -- NOT FILES-11 DEVICE
The command specified a device that did not contain a
Files-11 disk.
The specified device-unit must contain
a mounted Files-11 disk.

*** ddnn:

-- CHECKPOINT FILE NOW INACTIVE
The 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.

4-137

MCR COMMANDS

ALT
ALTER
The Alter command
installed task.

changes

the

static

running

priority

task name

- The name of the task whose priority is to
altered.

/PRI

- Changes the task's static priority,
and,
if
the
system
supports the Alter Priority
directive, the task's running priority.

/RPRI

- Changes the task's
running priority only
(valid only in systems that support the Alter
Priority directive).

Format:
ALT[ER]

taskname /keyword

Keywords:
/PRI=running and static priority
/RPRI=running priority only
/TERM=TTnnn:

(RSX-llM-PLUS systems)

where:

A pr iviJ~9ed
th~ ... J)rie>.r:J~y
.issuin9tertni

The priority is in the range 1 to 250 decimal.
The system assumes
that the priority you specify is octal unless you include a period
(

..
)

Examples:
RSX-llM systems
>ALT TEST /PRI=248,

Alter the static
248(10).

and

running

priority

task

TEST

>ALT CMFRUN /RPRI=70,

Alter the running priority of task CMFRUN to 70

(10).

RSX-llM-PLUS systems
>ALT ABC/PRI=202./TERM=TTG:

Alter the static and
202(10).

running

priority

task

ABCT6

to
~..

4-138

MCR COMMANDS

BOO
BOO'l'
The Boot command bootstraps a system that exists as a task-image file
on a Files-11 volume.
It provides a convenient means of terminating
one system and initiating another,
especially on minimum 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 are special task
image files
that have no
task
headers.
Examples of such systems are RSX-llM, RSX-llS, and PRESRV.
Form.at:
BOO [ T]

[file spec]

where:
filespec - The standard RSX-llM/M-PLUS file specifier of the
form
dev: [g,m]filename.type;ver
that specifies the file from which a
is to be loaded.

new

system

Defaults applied to the file specifier are:
dev:

- The system device LB:

[g Im]

- The UIC under which Boot is
running

type

- RSXllM
- SYS

version

- Latest version

filename

'"'-'

Note that Boot is the only command that allows the file
omit the file name field.

specifier

Restrictions:
- Virgin system Boot -- The boot device physical unit number
(unit
plug)
must equal the logical unit number in the virgin system.
Otherwise, the initial Save will not work.
Under certain circumstances, it is not possible to boot a
large,
mapped,
virgin Executive from an unmapped system.
If the new
Executive has loadable drivers above
27.SK words,
the drivers
will not be read into memory, thus causing problems when you try
to
run the system.
This can happen because Boot moves the

4-139

MCR COMMANDS

BOO (Cont.)
bootstrap code in an unmapped system to the top of memory less
.SK. To an unmapped Boot, this location appears to be 28K. Boot
then reads the virgin system image
into memory starting at
address zero up until the beginning of the bootstrap.
On saved
systems, Boot only reads the first block (Sl2 bytes) of the saved
system image and then passes control to the bootstrap code to
read in the rest of the system.
When a mapped system is used to boot a new system, Boot reads
in
the entire target system (minus .SK for the bootstrap}, because
the KTll is enabled, allowing Boot to
recognize more than 28K
words of memory.
has been generated into the
If the Executive Debugging Tool (XDT)
system,
XDT displays the following prompt when an RSX-llM/M-PLUS
system is booted for the first time:
XDT> baselevel
XDT>
Where baselevel
is
RSX-llM-PLUS system.

BL26

for

RSX-llM

system

BL6

for

Typing the G key
in response to the prompt returns control to
RSX-llM/M-PLUS,
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.
(See the RSX-llM or
RSX-llM-PLUS Guide to Writing an I/O Driver for a description of XDT.)
Example:
>BOO TEST

Bootstraps from the system device the
the file TEST.SYS.

system

contained

Command Error Messages:
BOO -- DPB ERROR
A bad DPB was created by Boot.
this error
indicates
that the system itself has faulted.
If the error
persists, submit a Software Performance Report
(SPR)
to DIGITAL.
BOO -- FILE NOT CONTIGUOUS
An attempt was made to
load a system
from
a
noncontiguous file.
System images must be contiguous.
BOO -- INVALID LOAD DEVICE
Boot detected a device that was invalid
residence device.

4-140

system

MCR COMMANDS

BOO (Cont.)

4-141

MCR COMMANDS

BRK
BREAKPOINT TO EXECUTIVE DEBUGGING TOOL
The BRK command passes control to the Executive Debugging Tool
(XDT)
if
it has been generated
into the system.
If XDT is not in the
system, the command has no effect.
See the RSX-llM or RSX-llM-PLUS
Guide
to Writing an I/O Driver for a description of XDT. Note that,
if successful, the 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 message

BE:
nnnnnn
XDT>
on TTO:
to indicate that XDT now 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

>.
!?< c:ltj RS.X-llM.;.;PLUS system, . you must issue. th~

conso1e t.ermifia1.

Format:
BRK
Example:
>BRK
BE: 124580
>WT> P

4-142

MCR COMMANDS

CLQ
CLQUEU E
The CLQUEUE command displays on the entering terminal
information
about tasks currently in the clock queue. The information 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 a Run command or a
RUN$ directive that specified a time-based option.
Format:
CLQ [ UEU E]
E~rnmple:

:>CLQ
TASK1 SCHEDULED AT 18-DEC-18 10:24:30:00
TASK2 SCHEDULED AT 18-DEC-78 10:30:00:00 RESCHEDULE INTERVAL 30 MINS

>
The first task in the queue will be run at 10:24:30:00
(hour:
minute:
second:
clock tick);
it has not been rescheduled.
The
second task in the queue will next be run at 10:30:00:00 and
is
scheduled to run every 30 minutes.

4-143

MCR COMMANDS

FIX
FIX- IN-MEMORY
The Fix-in-Memory command loads and locks a task into
its partition.
Subsequent requests for
running the task are serviced more quickly
because the task is memory-resident 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 be serially reusable.) Only an Unfix or
Remove command can free the occupied memory partition.
The following restrictions apply to the fixing of tasks:
In RSX-llM systems, checkpointable tasks cannot be fixed.
• RSX-llM-PLUS
systems,
checkpointable tasks should not
fixed;
fixing a
checkpointable
non-checkpointable.

task

makes

•

Active tasks cannot be fixed.

•

A task must be installed before it can be fixed.

the

In
be
task

Format:
FIX taskname
where taskname is the name of the task to be fixed in memory.

Examples:
>FI}-( ){KE

Fix task XKE in its partition.
>F I ){ F CS RE S I R E G

Fix the resident library for FCS in its partition.

4-144

,...,

MCR COMMANDS

FIX (Cont.)
>Fm

, , .MAC/RON

Fix the read-only segment of the MACR0-11 assembler
partition.

its

fixed

was

Command Error Messages:
FIX -- PARTITION BUSY
The partition in which the task was to be
occupied, so the task could not be fixed.
FIX -- TASK ALREADY FIXED
The specified task was already fixed in memory.
FIX -- TASK BEING FIXED
The subject task was already being fixed.
FIX -·- TASK CHECKPOINTABLE
An RSX-llM error message.
The subject task was
checkpointable.
A checkpointable task cannot be fixed
in memory.
Remove the task and install it
as
non-checkpointable
(/CKP=NO).
You can then fix the
task in memory.

4-145

MCR COMMANDS

INS
~'
INSTALL
The Install command makes a specified task known to the system.
An
installed task
is dormant until the Executive receives a request for
it to run.
Install accepts optional keywords which provide parameters
that were not specified at task build or override previously specified
parameters.
When you install a resident library
loads it into a common partition.

RSX-llM

system,

Install

When you install a resident library in an RSX-llM-PLUS system, Install
makes an entry for the resident library in the Common Block Directory
(CBD).
Install loads the resident library when a task
that uses
it
runs and removes the resident library when no task is attached to it.
When a task is installed, 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 an MCR command or a
system directive.
A task cannot be run until it has been installed.
(See Section 1.3.1.)
(Note that the Run command has an option that
automatically installs and removes a task before and after
running
it .. )
A task's TCB contains the address of the
load-device Unit Control
Block (UCB) and the Logical Block Number (LBN) of the task image file.
The Executive can therefore load the task image in one transfer when
an MCR command or system directive
requests an installed task.
(Loading requires more than one transfer if the task is greater than
321< words.)
When you install a task, the system stores the task image file's LBN
in the task header.
When a 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 reopens 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.
NOTE
If an installed task's file
image
is
deleted and other data is written into
that area,
the system probably will
crash if you attempt to activate the
deleted task.
A crash also occurs
if
the
disk
from which the task was
installed is removed and replaced with a
different disk.
This is because an
Executive table in the task
image
(the
task header) will contain random data.

4-146

MCR COMMANDS

INS (Cont.)
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.
But since the
TCB E~ntries contain task file identifications, rather than LBNs, after
a system save, the system can function normally when it is rebooted.
Formci t:
INS[TALL]

[$]filespec[/keyword(s)]

Keywords:
/AFF=[CPx,UBy]

(RSX-llM-PLUS multiprocessor systems)

/CKP=option
/EST=option
/INC=size
/PAR=pname
/PMD=option
/PRI=number
/PRO=[system,owner,group,world]

(RSX-llM-PLUS systems)

/HON=option

(RSX-llM-PLUS systems)

/HOPAR=parname

(RSX-llM-PLUS systems)

/SLV=option
/SYNC=option

(RSX-llM-PLUS multiprocessor systems)

/TASK=taskname
/UIC=[group,member]
where:
filespec - The file specifier in the form:
dev: [group,member]filename.type;version
The type defaults to TSK;
apply to the remaining fields.

standard

defaults

If $ is specified in the command line, then dev:
defaults to LB:, and [group,member] defaults to
system UIC
(usually,
[1,50]
in an
s stem and [l 54] in a

4-147

MCR COMMANDS

INS (Cont.)
..

Affinlty .... option
·v~iiil:'.
multiprocessor
~ys~~Jl\S.<. qnl'Yf<
uirea····syntax •...... l.e9al< vi!tlt,.le~·· ..• f(jr· ·
ication .. (x) are A, St,c.,, .~.l)d ·n,.
UNIBUS n1n specifiers ar;e E)
F·F·
N, P, R, ·S, and ';r ~
:
'.,:.::·:\:.::/:=\:· . . -

:;fB./"

•.the

you to . . speciff
for task execu.tion..

i.s; .. · ·. installed . wlth

....

:::

s:~~¢iff~;.·

af£ftif~Y . . . ~~h~¥e;'.

a specified resource ·.is not .available·";"··
CKP

/CKP=option.
Checkpoint option. The two options
are
YES and NO.
If /CKP=YES
(default for
checkpointable tasks), checkpointing is allowed.
If /CKP=NO,
checkpointing is disabled for the
task.
The /CKP keyword overrides
specified at task build.

the

/CP

switch

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

/EST=option.
Exit status option.
The
two
options are YES and NO.
If /EST=YES, the install
task waits for any task it spawns to complete and
emit exit status before continuing.
If /EST=NO,
the install task does not wait for exit status
from its offspring;
as soon as the install for
the spawned task completes,
the parent task
executes.
Default:
/EST=YES;
parent tasks do not exit
until their offspring task emits exit status.

INC

/INC=size. The number of additional words of
address space to allocate a task that runs in a
system-controlled partition. The extension size
is usually expressed in octal, but may also be
expressed in decimal by appending a period. This
keyword overrides the EXTTSK or PAR parameter
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
spac~
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.

4-148

MCR COMMANDS

INS {Cont.)
In an RSX-llM/M-PLUS system, you cannot extend a
task that uses memory-resident overlays.
See the
RSX-llM/M-PLUS Task Builder Manual.
Default:
either the size specified at task-build
time, or zero.
PAR

/PAR=pname.
A partition name that overrides the
partition 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.
Default:
TKB uses the name GEN.
(See the
RSX-llM or RSX-llM-PLUS System Generation and
Management Guide for an explanation of multiuser
system defaults.)

PMD

/PMD=option.
Post-Mortem Dump option.
The two
options
are
YES
and NO.
If /PMD=YES,
a
post-mortem dump occurs
if the task
aborts
because of an SST error condition.
If /PMD=NO
(the default
from a task-build),
no dump is
requested at SST abort time.
To generate a dump,
the post-mortem dump task PMD...
must
be
installed in the system.
This keyword overrides
the /PM switch specified at task-build time.
Default:

PR!

/PRI=number.
Priority number. The value range
is
1
through
250(10).
Standard numbering
conventions apply;
octal by default, decimal if
followed by a period.
Default:

PRO

specified at task-build time.

/PRI=SO.

/PRO=[system,owner,group,world]. An RSX-llM-PLUS
keyword.
Installed common region protection
option. Access codes consist of four
4-code
groups
in the access rights word of the common
region as follows:
R
W

E
D

Read
Write
Extend
Delete
Default

In each instance, the absence of the code means
that the applicable user
is denied the access
right.
The square brackets are required syntax.

4-149

MCR COMMANDS

INS (Cont.)
Specify an asterisk (*) in the access rights word
to force the default value for a specific group.
Defaults:

[RWED, RWED, RWED, RWED].

Note that you cannot specify protection options
for a read-only common region or the read-only
portion of a multiuser task.

/~O~(;'Ptio.n .•. An RSX-llM-PLUS keyW()Fq·.· .......•
•Q9rom()n . . . . re9iqn.
The two options are· YE§· iaq<:i.~9•
If /RON=YES, the common re9ion i.:S }.nstalle'd as··
tead.-.0n1y~
If /RON=NO,
the . common feg}cif'l. ..fs
installed with read-write access~
··· ·

Reaa!C>.rti¥• ·.

~.:

:/i·(·ll*i ,i.•.

•n~~~R· -

Default: /RON=NO; common regit:ms are
with read-write access.

inst::aifea::·

/R OP AR=p a rname • An RSX-11 M-PLUS keywo rel. : >T'h'is.
keyv;ord installs . the read-or)ly pott:.Jorl ()·~ :\Cl
multiuser task into a
specified
partlt;i•qn.;
parname.
.· .; •.•.• i•(.y.·
The partition you sped fy overrides .•the f>~r£:i£l;()l'l/
n.ame ·. suppUed .. at .. · task .·.• ~uild. l f no. par;~tt:J?t1·
O(!I\1e.\.fas ·specified .at . task .builc:!. and :t:o~•·.· . . clp .... I)()t. ....
specify .·
a. . . paftition ... ·.·.·•·•· ~tl.~ll . · · . ·. . ·.· • ip~t~l+Jn9·;.
(/ROPAR=!)arname),
the·. read-6f11Y <po~t;fon ·. q~ .•.. c:i·>,
multiuser·. task. is .. installed •. in . th.~ Sq.me P~rt/f-t;~<>.11
~s the ·.task •....·..•. Also,. if parname .··does . . not· .• ·e~+~·;(~··
th.e . read-only . portion is installed th. the same:
partJtion as the task.

SLV

/SLV=option. Slave task option. The two options
are
YES and NO.
If the command specifies
/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
specified at task build.
If the command specifies /SLV=NO the TI: of
task does not change when receiving data.
Default:

the

Specified at task build •

. /SnJc;=opt ion. synchronization option. 'ya.~Jai.< in
. ~SX--llM-PLUS . mul tlpiocessor sf$,~elll~>···• (:)plx'.t ·>.·The: . .:
~~9 ()Pti9ns are YES and NO.
Tl)~s. ~~¥.\V()~<l. RE7.~l)lt.t~-'· ·
sseveral tasks to shar.e a ·.90ft'\W.()t;l . .>41 .?~ ·.\497·.·~ll.7·
common for synchroriization •.···. Jf SX1'.ld'7)!~p>for · two
C)r ·. · more tasks, only one of·.· ~9e. t;a9kf; p~n ~·~egt1tE:)
a_t·.. a .tlme •.. Note .. that.· if. one of tp~. ~a~ks< becomes
bl9ckeq, the others compete to e~ec~t~j··
~.
..
~···

...

:··.~·.·~~~

.. ··~

4-150

MCR COMMANDS

INS (Cont.)

TASK

/TASK=taskname.
The name
refers to the task.

which

the

system

Default:
first 6 characters of the filename
or
the name specified at task-build time.
(See the
RSX-llM or RSX-llM-PLUS System Generation and
Management Guide for an explanation of multiuser
system defaults.)
UIC

/UIC=[group,member].
The square brackets are
required syntax.
This UIC is the default for the
task.
It can be overridden in the Run command.
The task UIC determines into what file-protection
class
(system,
owner,
group,
world)
a
task
belongs,
and
thus directly
influences
file
access.
Note that file protection may differ
from file to file.
Default:
default from task build.
This default
applies only to tasks started by a RUN$ directive
or an MCR Run command that specifies a time delay
before runtime.
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.
This UIC is defined by the
Set command or at login.

Examples:
>INSTALL SCAN

Install task SCAN.

Priority and UIC defaulted.

>INSTALL DK1:[1 t111JSCAN.TSK;4/PRI=103

Install task SCAN, file type TSK, version 4 on device DKl:,
group number 1, member number 111, with a priority of
103(8).
>INS MAC/INC=409G,/PAR=SYSCTL

Install task MAC in the system-controlled partition
and increase the task size by 4096 (10) words.

4-151

SYSCTL

MCR COMMANDS

INS (Cont.)
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 4K
boundary.
This message is applicable only to mapped
systems.
INS -- BASE MISMATCH COMMON BLOCK <common-name>
The base address of the partition did not match that
of the common block.
This message is applicable only
to unmapped systems.
INS -- CANNOT INSTALL PRIVILEGED TASK FROM NON-PRIVILEGED 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
privleged task.
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
A warning message. 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.
INS -- COMMON BLOCK IS TASK PARTITION <common-name>
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 <common-name>
The specified common block was linked to the task but
had not been installed into the system.
Install the
common block, then install the task.

4-152

MCR COMMANDS

INS (Cont.)
INS -- COMMON BLOCK OCCUPIED
An attempt was made to load a common
occupied.

block

that

was

those

INS -- COMMON BLOCK PARAMETER MISMATCH <common-name>
Parameters of a common block did not
the task's label block.

match

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.
INS -- FILE NOT CONTIGUOUS
An attempt was made
non-contiguous file.
contiguous files.

to
install a task from
a
Task
images may exist only in

INS -- FILE NOT TASK IMAGE
Data in the label block was not correct,
that the file was not a task image.

indicating

INS -- ILLEGAL DEVICE ddnn:
The device specified at task build by the assign (ASG)
options did not exist in the system.
This is a
warning message;
the task will be installed.
INS -- ILLEGAL DEVICE/VOLUME
The specified device was not
device.

valid

task-residence

INS -- ILLEGAL FIRST APR
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 Task Builder
Manual for a description of the /PR keyword.)
This
message applies only to mapped systems.
INS -- ILLEGAL PRIORITY
The value of the priority specified in the command was
out of range (that is, not 1 to 250(10), inclusive).

4-153

NCR COMMANDS

INS (Cont.)
INS -- LENGTH MISMATCH COMMON BLOCK <blockname>
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 -- NO CHECKPOINT SPACE, ASSUMING NOT CHECKPOINTABLE
This is a warning message. The command attempted to
install the task as checkpointable;
but the task was
not built as checkpointable 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
not to be checkpointable.
INS -- NO ROOM AVAILABLE IN STD FOR NEW TASK
No dynamic memory was available to build the System
Task Directory (STD) entry (Task Control Block [TCB]);
therefore, no task could be installed.
INS -- NOT ENOUGH APRS FOR TASK IMAGE
The Task Builder allows the user to specify the
virtual base address of a task image as a multiple of
4K. Privileged tasks start at virtual 100000(8)
to
map the first 16K of the Executive,
or virtual
120000(8) to map the first 20K of the Executive,
at
the same time as the user task.
If the virtual base
address is set too high, the task
image may not be
able
to
be
mapped with the rema1n1ng mapping
registers.
This message is applicable to mapped
systems only.
INS -- PARTITION NOT COMMON
A partition specified for a common area or library
not defined as a common partition.

INS -- PARTITION par NOT IN SYSTEM, DEFAULTING TO GEN

"'·

This is a warning message.
The specified partition
does not exist;
the system therefore attempts to
install the task in the GEN partition.
INS -- PRIVILEGED TASK LARGER THAN 12K
A privileged task was larger than 12K.
Privileged
tasks on an unmapped system have a maximum size of
12K.
INS -- SPECIFIED PARTITION FOR COMMON BLOCK
A task was being installed into a common block.

4-154

,,,

_____________________________________________________

MCR COMMANDS

INS (Cont.)

"-''
INS -- SPECIFIED PARTITION TOO SMALL
The task being installed was larger than the partition
into which it was being installed.
INS -- TASK AND PARTITION BASES MISMATCH
The base of the partition did not match the base of
the task being installed. This message applies only
to unmapped systems.
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).
INS -- TASK IMAGE I/O ERROR
Install could not read the task-image file, or Install
could not rewrite the task-image header.
(The device
is write-locked.)
INS -- TASK

IMAGE VIRTUAL
<block-name>

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 NAME ALREADY IN USE
An attempt was made to install a task
name as one already in the system.

with

the

same

INS -- TOO MANY COMMON BLOCK REQUESTS
A task made too many common-block requests.
limited to seven common-block references.

A task is

INS -- TOO MANY LUNS
A task
requested
assigned.

than

255(10)

LUN's

INS -- UNDEFINED COMMON BLOCK <blockname>
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.

4-155

MCR COMMANDS

INS (Cont.)
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 in order to
access the KTll registers 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.

4-156

................................................................................................................

·~

MCR COMMANDS

LOA
LOAD
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.
(Note
that
under
RSX-llM-PLUS,
the
task
CON
constructs
interrupt-vector linkages.) This 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.)
The result is the potential for an increase in the amount of
system dynamic memory.
You can load drivers 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 common partition for RSX-llM or a region for RSX-llM-PLUS 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:
LOA[D] dd: [/keyword (s)]
where:
dd:

- a 2-character ASCII loadable device driver name

Keywords:
/PAR=parname
/C'fB=cca [,.b ••• ]
/SIZE=parsize

(RSX-HM-PLUS systems only)

/HIGH

Keyword Definitions:
PAR

- /PAR=parname.
Specifies the partition
which the driver is to be loaded.

(parname}

into

In an RSX-llM system, the specified partition cannot be
a
common
partition,
but
all
other types are
permissible.

All loadable drivers are usually placed in the same
This has the
partition,
by
convention
DRVPAR.
the
GEN
advantage of preventing fragmentation of
loadable
partition
and normally ensures that all
drivers remain below 124K in memory (the maximum core
image size for the Save task}.

4-157

MCR COMMANDS

LOA (Cont.)
If the command omits this keyword, the system loads the
driver into the partition specified when the driver was
built.
'l'.Ht=l"''r";:a [ ,

b ••• ] •

An RSX-llM-PLUS

keywor,Ci-:'

""·

'!3pe~1ifi1i~~:r:i.

controller Controller Table BlpJ~K·i (~'f~)
base . t.o modify tathet.:J;haJ)·. ·.·µ$ln·9
in ·the ·loadapJ.e.· .d.at~t . . ba~er •. •. ••· .·. . ··~9.~~·\t.ha:t:
is necessary only ... if··· tbed,t;i\re;r <;C>p,t.a.ins. .. ·a... ·
base;
to. load most driyer::;,:·t:}1i,s•tce7(.W<)~d~.
ired.
(See the RSX .... llM:"""Pt;us Gi.iicfe · ·T;o
for oetails .)
·.. ' >·> ' .....

'W~~~i~}~~(f/;

is the muiuarilie'r
s lot.s in ,the·Crj,'s~s . .C?ntroJ.J.·~r .:-

Block. (KRB) table pointing to . the ISREtlf).•:Jn. it.h~<
data base. The slots are named· At 13·,· (;}" Pl>·~i< ·
L, M, N, p, R,

s, and T~

'•

' ' '

,.· ..... · ··· .. ······.· .. '···- ......... :·:·... ····· .. :··,

if .a.system c9nt.ainp a •. •. DJ3·:
the following command

a loadable data base for RHB:

qe'.~. ic~~p:\~~~·,.:.·
to· load:a<·DR:

DR: /CTB=RHB
SIZE

/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,
the created
subpartition will be this size.
parsize is rounded up to the next highest unit
{octal) and must be less than 100000.

HIGH

100

- /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 npt you
specify /HIGH.

Examples:
>LOAD

MM:

!LOAD TU1G DRIVER <MMDRV>

>LOA

LP:/PAR=DRVPAR

!LOAD LP11 DRIVER <LPDRV> INTO DRVPAR

Notes:
•

Guidelines for building loadable device-driver tasks
are
rigidly defined.
These guidelines are described 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.

Also,

4-158

'•------------------------------------------------------------------------------------~-----

MCR COMMANDS

LOA (Cont.)
o

The Load command requires that a driver's TSK and
reside under the system UIC on the system disk
example, the command
LOA

STB files
(LB:).
For

DT:

requires that the files DTDRV.TSK and DTDRV.STB reside on LB:
under the appropriate system UIC.
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.
e

The Load command does not
space in a partition.

initiate

checkpointing

The Load command requires pool space as follows:

free

If the driver data base is being loaded,
the command
needs contiguous pool space equal in size to the size
of the data base.

In a mapped system, the command needs pool space for
an Interrupt Control Block (!CB) for each interrupt
entry in the driver.

If the driver is being loaded into a system-controlled
partition,
the
command needs pool space for a
Partition Control Block (PCB).

Command Error Messages:
LOA -- CANNOT LOAD/UNLOAD A PSEUDO DEVICE
The device you attempted to load is a
Pseudo devices do not have drivers.

4-159

pseudo

device.

MCR COMMANDS

LOA (Cont.)

LOA -- DEVICE dd:

NOT IN SYSTEM

The data base for the device driver was neither in the
system nor 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 loaded or
is permanently resident.
LOA -- DRIVER BEING LOADED OR UNLOADED
The Executive was effecting another
the driver.

request

load

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 RSX-llM.STB that was not for the current
system.

LOA -- DRIVER LOAD/UNLOAD CALLS NOT SUPPORTED
An RSX-llM message.
The requested driver included the
global symbols $ddLOA or $ddUNL in its source.
These
symbols are reserved for future use by the Load and
Unload commands.
LOA -- FILE filename HAS ILLEGAL STB FORMAT
The driver's STB file contained an illegal object code
or data record format.
LOA -- FILE filename NOT A VALID DRIVER TASK IMAGE
The driver's task image was either overlaid or
task header.

4-160

had

MCR COMMANDS

LOA (Cont.)
LOA -- FILE ddDRV.TSK NOT CONTIGUOUS
The file ddDRV.TSK was not contiguous.
Device drivers
(like all "task" images), must be contiguous.
LOA -- ILLEGAL DRIVER TASK APR USAGE
A device driver must be built for APR 5 and must be
less than SK (for example, PAR=DRVPAR:l20000:40000).
This message applies to mapped systems only.

LOA -- ILLEGAL VALUE FOR SYMBOL symname IN FILE filename
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 zero;
$ddTBL must exist
and have a value less than $ddEND;
mapped loadable
drivers cannot reference $INTSV.
LOA -- INSUFFICIENT POOL SPACE
The required amount of system dynamic memory
available.

was

not

LOA -- INTERRUPT VECTOR ALREADY IN USE
An RSX-llM message.
not point to one
points.

interrupt vector does
A driver
of the nonsense interrupt entry

LOA -- INVALID DRIVER DATA BASE AT OFFSET xxxx IN FILE filename
The driver had an invalid data base value at offset
xxxx relative to the symbol $ddDAT. This can occur
for three general reasons.
There is something very
specific wrong with the word in question;
such as
D.UCB being odd, a conclusion Load made starting from
the word in error.

4-161

MCR COMMANDS

LOA (Cont.)
For example,
D.UCB,
D.UCBL, D.UNIT,
and D.UNIT+l
define the address of the last word of the last UCB.
If that word is not within the bounds of the loadable
database,
Load produces an error message citing
D.UNIT.
Load is off the track and
is attempting to
verify one kind of data structure as a different type.
For example,
in an RSX-llM-PLUS system,
if
the
loadable database starts with a CTB and the global
symbol $ddDCB is not in the database,
Load assumes
that the DCB is the first structure in the database.
Therefore, Load cites a word in the CTB as bad.
LOA -- INVALID INTERRUPT VECTOR
An RSX-llM message.
The interrupt vector address
specified in the driver data base was too high for the
current system.

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.
LOA -- OPEN FAILURE ON FILE filename
Load encounted an error
specified file.

attempting

open

the

LOA -- PARTITION parname BUSY
In an RSX-llM system, the user-controlled partition or
subpartition into which the driver was to be loaded
was already occupied.

4-162

MCR COMMANDS

LOA (Cont.)
LOA-- PARTITION parname IS A COMMON
An RSX-llM error message.
You have attempted to load
a device driver
into a common partition.
A device
driver cannot be loaded into a common partition.

LOA -- PARTITION parname IS NOT A COMMON
An RSX-llM error message.
The symbol $ddCOM is
globally defined in the driver.
The partition ddCOM
exists, but it is not a common partition.

LOA -- PARTITION parname NOT IN SYSTEM
An RSX-llM error message.
The partition specified
either in the Load command or at task build was not in
the system.

LOA -- PARTITION parname TOO SMALL
The partition into which the driver was to
was not large enough to contain it.

loaded

LOA -- REGION/PARTITION name IS A COMMON
You have attempted to load a device driver
into a
common partition.
A device driver cannot be loaded
into a common partition.
LOA -- SYMBOL symname IS DOUBLY DEFINED BY FILE filename
The symbol
ddDRV.STB

symname

4-163

defined

twice

the

file

MCR COMMANDS

LOA (Cont.)
LOA -- SYMBOL symname IS UNDEFINED IN FILE filename
The symbol symname was found in the
but it was not a symbol definition.

file

ddDRV.STB,

LOA -- TASK AND PARTITION parname BASES MISMATCH
An RSX-llM message.
The base address of the partition
into which the driver was to be loaded did not match
the base address of the partition address for which
the
task was built.
This message applies to unmapped
systems only.
·
LOA -- TASK IMAGE I/O ERROR IN FILE filename
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 SK words in length.
The
driver must explicitly map to any location above 4K
words.

4-164

MCR COMMANDS

OPE
OP EN REG !STER
The Open Register 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.
Format:
OPE[N] memory address [+ or -n] [/keyword]
(memory-address)

(contents-of-address)/[value]<line-terminator>

The Open command, as shown above, is a 2-line command. The first
line initiates the command.
Its parameters are as follows:
memory-address

- A 1- to 8-digit octal memory address.

+ or -n

- One or more optional octal numbers to be
added to or subtracted from the memory
addresse

Keywords:
/AFF=[CPx, UBy]
(RSX-llM-PLUS multiprocessor systems)
/CPU=CPx (RSX-llM-PLUS multiprocessor systems)
/TASK=taskname
/PAR=partition name (RSX-llM systems)
/REG=region name (RSX-llM-PLUS systems)
/KNL
/KNLD
(RSX-llM-PLUS systems)
/KNLI
(RSX-llM-PLUS systems)
/DRV=dd:
The keywords apply only to mapped systems.
Keyword Definitions:

TASK

- /TASK=taskname.
Accesses an address relative to the
specified task
(the task partition). Note that the
task must be fixed.

PAR

- /PAR=partition name.
An RSX-llM keyword.
Accesses an
address relative to the beginning of the specified
partition.

n
rst
Data
an
system supporting
(I and D) space, the keyword accesses and prints the
contents of addresses in the Executive data space.

4-165

MCR COMMANDS

OPE (Cont.)
An RSX- HM-PLUS. keyword. . . Thi$ ke~\¥6~q ~~cc~$~~~·
and pririts the contents of address7s in 7&r'~i~r?Y~lye
data space.
Valid only in RSX ..... llM-PLUS sy5ctE!rn$··:tha.t<
support I and o space.
. .· :
. ·· /Y
.

KNLO

- /I<NLO.

KNLI

ORV

- /DRV=dd:.
Accesses an address
relative
to
the
beginning of the partition that contains the loadable
driver for the specified device.

/KNLI.

An RSX-HM-PLUS keyworO.

1'hfJ; &7~~~~~~!{~~~~~~

and prints . the contents of addres;ses ,in t.l'.le:·ex7p~~i.~7 .
instruction space.
Valid only Jn RSX-llM--P.LUS' sy~t:.7ms·
that support I and 0 space.
·

~fter

accepting the first input line, Open finds the
to be accessed by using either:
•

The keyword

•

The specified address as the actual address

memory

location

(in a mapped system)

When /TASK, /PAR, /REG, and /ORV 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.
In a mapped RSX-llM system, an attempt to specify an illegal location
or access beyond the
limits of the partition causes an error.
The
user is limited to the specified memory region (TASK,
PAR,
or DRV).
However,
if the command omits a keyword, it can access any address of
physical memory.
In an unmapped RSX-llM system,
any
location
in
physical memory can be accessed.

Irt a11 RSX-llM-PLUS system, an attempt . to specify an. ill~g~l ,'}£bat.J.bn .·
or. q<;:cess. beyond tbe limits of. the partition c:aqses ·ary: ~·f'Pi~#~:: ;'Rtie: ··
us;erJs lirnitedto the specified memory region (TASK,,!lF;ff~: $r:<:~A~t~
fi<>\\f:7ve r, .• if the command omits a keyword, it can acc~i:;s. ~n¥:~
· of·
phy~ipal<Illernory •. In a multiprocessing system, to <a9cess> cU'} ~
>tn-a
a7.yi.s~ P~CJ~ . (the processor. s I/O page) I you niusttreat :~1}7 :.+~~·~t~.<;h'
as ap~otµte and .. append the /AFF keyword.
Likewise,
t9 ~S~~~.~ ,··~.l'l
address ·.in a CPU pa~tition, you must treat the locatign· ~$: abs.9.tL(te
and append the /CJ?U keyword.
.
.
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 line-2 display.
The
slash (/) is part of the line-2 display.
Line Terminator Options:
- ESCape or ALTMODE:
~
(ALTMOOE)
terminates
acceptance of further input and is the only means of
exit from the MCR Open function.
Carriage return:
opened.

the next

4-166

sequential

location

MCR COMMANDS

OPE (Cont.)
-

Up-arrow (circumflex on some terminals)
return:
the previous location is opened.

carriage

*~or @~- Asterisk

carriage
return,
or at-sign carriage
return:
the location pointed to by the contents of
the opened location is opened.

Right angle bracket carriage return;
the contents
of
the open location
is treated as a
branch
instruction.
The effective address of the branch is
the next opened location.
It is not permissible to
supply a value (modify the current open location)
and close the location with a >.

Example:
>OPE 4+10/TASK=CYCLE
000014 OG0014/350ESC

In this example, the specified virtual address in the task CYCLE
is 4, while n equals 10, yielding the effective task-relative
address of 000014. The system responds by printing the virtual
address
(000014),
and the contents of the address (060014),
followed by the slash.
The operator responds by entering the new
value 350 and the ESCape character.
The value 350 replaces the
previous contents of task virtual location 000014.
Command Error Messages:
OPE -- BYTE ADDRESS
The address specified as the
command was an odd address.

argument

An even address (for example, 3000) is legal;
address (for example, 3001) is illegal.

the

Open

odd

OPE -- INPUT I/O ERROR
In attempting to read the next command, Open
an error.

detected

OPE -- INVALID ADDRESS
The address specified as an argument
in 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.
OPE -- TASK NOT FIXED
An attempt was made to open a task virtual location.
Since the task was not fixed, it may or may not have
been in memory at the time the command was
issued.
This message indicates that the specified task was not
in memory when the command was issued.

4-167

MCR COMMANDS

REA
REASSIGN
This command reassigns a task's Logical Unit Numbers (LUNs)
from one
physical device-unit to another.
The reassignments affect only the
static assignments recorded in the task's disk image file.
The command does not affect a memory-resident task.
Hence,
Reassign
has no effect on the assignments of a currently executing task, nor on
those of a task that is fixed in memory.
Use the Redirect command for
dynamic device reassignments.
Format:
REA[SSIGN]

taskname lun ddn:

where:
taskname - is the name of the task
lun
- Logical unit number
ddn:
- New device-unit, which can be a physical,
or pseudo device.

logical,

Examples:
>•REA JOE 3 TTO:

Reassign LUN 3 of task JOE to device TTO:.
>REA BILL 2 TT1:

Reassign LUN 2 of task BILL to device TTl:.
>REA TEST 3 }0(:

Reassign 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 during task
build.

4-168

~--------------------------------------------------------------------------------------------------------------

MCR COMMANDS

RED
REDIHECT

This 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
inoperable.
The command does not affect any I/O requests aleady in
the I/O queue.
You cannot redirect the following device-units:
•

The device TI:

•

An attached device

•

A device-unit containing a mounted volume

In addition, you cannot redirect one pseudo device to another pseudo
device nor can you
redirect a logged in terminal to a device other
than a terminal.
Format:
RED[IRECT] nddn:=oddn:
where:
nddn:

- New device-unit to which subsequent requests will be
redirected.

oddn:

- Old device-unit
directed.

have

been

Redirect all I/O requests for device TT6:
to device
(RED TT6:=TT6:
restores I/O requests for TT6:.)

TT3:.

from

which

requests

Example:
>RED TT3:=TTG:

Command Error Messages:
RED -- CIRCULAR REDIRECT ERROR
The attempt to redirect a device
circular list of redirections.

would

result

An attempt was made to redirect a device
be redirected.

that

cannot

RED -- DEVICE NOT REDIRECTABLE

RED -- NEW DEVICE NOT KNOWN TO SYSTEM
The new device in the Redirect command was not known
to the system (did not exist in the device tables).

4-169

MCR COMMANDS

RED (Cont.)

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
device did not exist in the device tables).

(the

RED -- PSEUDO DEVICE REDIRECT ERROR
An attempt was made to redirect one pseudo
another pseudo device.

device

RED -- TI REDIRECT ERROR
An attempt was made to redirect the pseudo device TI:.
This device may not be redirected.

4-170

MCR COMMANDS

REM
REMOVE
The Hemove command deletes an entry (a task name) from the System Task
Directory
(STD),
and thereby removes the task from the system.
The
removal of a task from the system makes the task unknown to the
system.
This action is the complement of Install.
All that remains
of the task in the system is the task-image file.
To remove a task that is in execution, you must first abort the task.
Format:
REM[OVE] taskname
where taskname is the name of the task to remove.

Example:
>REM SCAN

Remove the task named SCAN from the system.
file is not deleted.

The

task-image

Notes:
•

If a task that is the object of a Remove command is fixed,
command unfixes the task and then removes it.

the

•

Remove cancels
specified task.

the

•

Remove unlinks a task from all ICS/ICR interrupts.

•

Remove deallocates all receive-by-reference and receive-data
packets for the task, and detaches all attached regions.
(See
the RSX-llM/M-PLUS Executive Reference Manual.)

all

time-based

4-171

schedule

requests

for

MCR COMMANDS

SAV
SAVE
The Save command copies the current system image (the contents of main
memory up to 124K) of an RSX-llM/M-PLUS system 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 special format task image.
This special format is a task image
without 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,
formula of four times the size plus two. For example:
28K requires 114.

blocks

32K requires 130.

blocks

124K requires 498.

blocks

compute

the

To successfully save a system, the Save command requires that:
On an RSX-llM system, Save must run from
does not require this)

Error logging is not active

All tasks be installed from an LB:

No checkpoint files are active

No volumes are mounted, except the load device

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,
in RSX-llM-PLUS
systems, all loaded commons reside within the amount of main
memory that Save will write to the system image file

,·

••

,In llsx....:11M~Pi.US syqtems, save also
;·....;,·.:,

.. r.

~9 ~~ace

· ·2.

All dh~c:kpoiritable

~.h1J'tt;Jng down

4-172

CO:

(RSX-llM-PLUS

MCR COMMANDS

SAV (Cont.)

An error is reported if any of the above requirements is not met.
Save is active when the memory-resident system image
is copied to
disk,
and thus Save appears in this image as an active task to VMR.
This appearance is correct because Save is the task that starts the
system after a boot.
The Executive
references the file
images of
installed tasks
by
physical addresses (LBNs).
A saved system does not always retain the
physical disk addresses of installed tasks;
for
example,
the Disk
Save and Compress utility can compress and copy a disk containing a
saved system,
thus moving the
task files
to different physical
locations.
Therefore,
Save converts the LBNs of all installed tasks
into :Eile 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 reboot, 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.
In RSX-llM-PLUS systems, since
installed common regions and read-only segments of multiuser tasks
face a similiar problem, Save also converts the absolute pointers for
these into relative pointers and restores the pointers when the system
is booted.
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 reboot of 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.

•

In multiuser protection systems,
validates that
device is not allocated and then sets it public

•

Sets the context of the
privileged, and non-slaved

console

4-173

terminal

the

boot

logged

in,

MCR COMMANDS

SAV (Cont.)
•

Sizes the boot device

(RSX-llM-PLUS systems)

•

Outputs system identification message

•

Redirects all pseudo devices to the boot device

•

Mounts the system disk

•

Initiates the file

[l,2]STARTUP.CMD on the booted device

Format:
SAV[E]

[/keyword(s)]

Keywords:

/WB
/MOU
/SFILE
/NOCON
/CSR

(RSX-llM-PLUS systems)
(RSX-llM-PLUS systems)

Keyword Definitions:
W.B

- /WB.
Indicates that a hardware
boot
block
pointing to the system image is to be written out
to the system device.
The new boot block points
to the file that is saved with the issuance of the
command. Thus, on the next hardware bootstrap,
this saved file will be loaded.
If the command
omits the /WB keyword, the boot block still points
to the prior system image, which may have been
overwritten.

MOU

- /MOU- 11 string 11 •
The Save task automatically issues
an MCR Mount command at system startup to mount
the system disk.
This keyword allows you to
specify options to be appended to that Mount
command.
The Mount command options you specify must be
enclosed within quotes and must be in the proper
format for Mount options (that is,
including all
necessary slashes
(/) or equal signs (=)).
Note
that Save performs no syntax checking of the
string.

Sli'ILE

- /SFILE= 11 filespec 11 •
The Save task 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 performs no syntax
checking of filespec.

4-174

MCR COMMANDS

SAV (Cont.)

Example:
>SAt.1

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:
SAV -- BAD TASK FILE VBN, TASK REMOVED - taskname
Save 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.
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 - dd nnn mmmmmm
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 DBl:.

4-175

MCR

COMMANDS

SAV (Cont.)
SAV -- CHECKPOINT FILE STILL IN USE ON ddnn:
The
on
the
the
SAV -- CO:

system cannot be saved because a checkpoint file
the specified device is still active.
Deallocate
checkpoint file (see the ACS command) and reissue
Save command.

REDIRECTED TO CO:
If it
is not
The console output driver is active.
You can use the
active,
the system may be corrupted.
Open command to redirect CO:
to the terminal from
which you are running Save.

SAV -- COMMON, DRIVER OR TASK ABOVE SYSTEM IMAGE FILE LIMIT
A system cannot be saved if
a
memory-resident
structure
is higher than the amount of main memory
that is written to the system image file.
Use the
Partitions command to determine the cause of the
problem.
This includes the
running task
image of
Save.
SAV -- DISMOUNT COMPLETE FOR ddnn:
This is not an error 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 ddnn:
If the load device is mounted when Save is initiated,
Save
issues a Dismount command to MCR. 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.
Run the task ERF to disable error logging and
reissue the Save command.
SAV -- HOME BLOCK READ ERROR
The home block of the booted device could not be read.
Try another drive.
If unsuccessful, the disk has been
corrupted or the area of the home block is bad.
This
error halts the system.

4-176

MCR COMMANDS

SAV (Cont.)
~'

SAV -- INDEX FILE HEADER CHECKSUM ERROR
While
rebooting a
saved system, Save 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.
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 volume could be corrupted.
SAV -- MCR IS NOT INSTALLED
When a system is booted, Save uses MCR to mount the
system disk.
MCR ••• must be installed using VMR.
SAV -- MUST BE RUN FROM TERMINAL CO:
SAV is not being run from the terminal
pseudo device CO:
is· redirected.
requirement on an RSX-llM-PLUS system;
message does not apply.

to which the
This is not a
therefore, the

SAV -- NOT 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 system
device.
SAV -- OPEN FILE(S) ON ddnn:
There are open files on ddnn:.
manager is stopped.

Insure that the

queue

SAV -- PARTITION parname NOT IN SYSTEM, TASK REMOVED - taskname
This is an RSX-llM error message.
If a
task
is
installed in more than one system,
the partition
control block addresses in its header mapping windows
may not be for the booted system. The task's label
block indicates that the task maps to parname,
but
parname is not in the current system. The label block
has probably been corrupted.

4-177

MCR COMMANDS

SAV (Cont.)
SAV -- SYSTEM MAY NOT BOOT CORRECTLY
The file [system uic]SAV.TSK was not found on the boot
device.
If SAV must be checkpointed in order 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,
Unload
and
Unfix
commands can be used to remove the
nonexistent structures.
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 - taskname
The task is installed in another system as well a~
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.
SAV -- TASK FILE DELETED, TASK REMOVED - taskname
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 - taskname
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 - taskname
Save removed the specified task because it encountered
a failure while reading the task's file header.

4-178

MCR COMMANDS

SAV (Cont.)
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.
The error causes the system to halt.
SAV -- TASK HEADER READ ERROR, TASK REMOVED - taskname
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 HEADER WRITE ERROR, TASK REMOVED - taskname
When Save attempted to rebind the LUNs of the task or
to
rewrite a mapping window PCB address, Save could
not successfully rewrite the task header.
Therefore,
the task was removed.
SAV -- TASK LABEL BLOCK READ ERROR, TASK REMOVED -

taskname

When Save attempted to rebind the LUNs of a
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.
SAV -- TASK TOO BIG FOR PARTITION, TASK REMOVED - taskname

'"'-"

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 taskname HAS OUTSTANDING I/O
A system cannot be saved if a task is waiting for
to complete.

I/O

SAV -- TASK taskname IS ACTIVE AND CHECKPOINTED
You cannot save a system if it contains an active and
checkpointed
task.
This
restriction prevents a
possible system crash;
if the task was
installed in
another system image fjle,
the task image could be
corrupted when the task was run in the second system.
SAV -- TASK taskname IS CONNECTED TO AN INTERRUPT VECTOR
Disconnect the task from the interrupt vector or abort
it and retry the Save command.
SAV -- TASK taskname NOT INSTALLED FROM AN LB:
All tasks must be installed from an LB:.
Use the TAS
command and determine which tasks are not.
Retry the
Save command after removing the tasks or
installing
them from an LB:.

4-179

MCR COMMANDS

SAV (Cont.)
SAV -- VOLUME STILL MOUNTED ON ddnn:
The volume on device ddnn:
was still mounted when the
Save command was
issued.
A system cannot be saved
with volumes mounted.
Dismount the volumes and
retry
the Save command.
If necessary, use the MCR 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 taskname
The physical device to which Save was attempting to
rebind 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.
Additional RSX-llM-PLUS Command Error Messages:
SAV -- BOOTED DEVICE CANNOT BE BROUGHT ONLINE
There was an error when Save attempted to bring either
the unit or controller of the booted device online.
The Executive is corrupted, the device driver does not
work,
or the device does not work.
There is no
recovery procedure.
SAV -- COMMON comname NOT INSTALLED FROM AN LB:
All checkpointable commons must be installed from an
LB:.
Remove the common and retry the Save command.
SAV -- DIRECTIVE PARTITION UNFIXED OR NONEXISTENT
VMR has been used to make
directive partition disappear.

4-180

the contents of the
Use VMR to restore it.

MCR COMMANDS

SAV (Cont.)
SAV -- PROPER CONTROLLERS AND/OR UNITS ARE NOT OFFLINE
When a system is saved, all device units and device
controllers except the TI:
of Save and the load
device must be offline.
Use the CON Display command
to determine which devices are online, and then issue
a CON OFFLINE ALL command.
SAV -- SECONDARY POOL HAS DISAPPEARED
Save attempts to initialize secondary pool during the
boot process. This message indicates that Save could
not find the PCB for the secondary pool partition.
SAV -- SECONDARY POOL IN USE
Save cannot save- a system if necessary pool is in use.
(Make certain that you have stopped CPU accounting.)
SAV -- SYSTEM MAY NOT WORK - CORRUPTED FILE FOR COMMON comname
When Save attempted to convert the file ID for the
common,
Save found that the task
image of the
checkpointable common was corrupted or had
been
deleted.
Save altered the system data structures to
prevent checkpointing of the common into what may now
be another task image.
SAV --(WARNING) COULD NOT SIZE BOOTED DEVICE
Save recognized the device name as a device that
it
should size, but it could not size it. The UCB words
U.CW2 and U.CW3 for the booted device may
incorrectly
indicate device size.
I/O errors may result. The
system will work properly if the UCB
correctly
indicates the size of the device.

4-181

MCR COMMANDS

SSM
SYSTEM SERVICE MESSAGE
The SSM command inserts text into the error log reports.
The command
places text
into an Error Message Buffer (EMB) which the task ERRLOG
eventually writes to the file ERR.TMP (see the RSX-llM/M-PLUS Error
Logging Reference Manual).
Following initial processing by PSE, SYE
includes the message in a full error report.
Each system service message is assigned a sequence number and a banner
heading as follows:

************************ENTRY nnn.*****************************~*
SYSTEM SERVICE MESSAGE
LOGGED date and time

ON CPx -- CONFIGURATION ENTRY #n.

*****************************************************************
TASK INITIATING MESSAGE:
THE MESSAGE IS BELOW:

••• MCR

Format:
>SSM message
where message is any text string up to a maximum of 79 characters.
Example:
>SSM TEST I NG 1,JOLUME

INTEGRITY ON DK 1: ,

Inserts the message into the error
appear in a full error log report.

log

4-182

POSSIBLE

report.

FORMAT ERRORS.

The

message

will

MCR COMMANDS

4-183

MCR COMMANDS

UNF
UNFIX
The Unfix command frees a fixed task from memory.
The effect
is to
allow tasks that have been waiting for the partition in which the task
resides to compete for the partition.
Unfix is the complement of the
Fix command.
If a fixed task exits or aborts,
of the partition.

it still occupies the physical memory

Format:
UNF[IX] taskname
where taskname is the name of the task.
~!

Examples:
>UNFIH ><KE
Unfixes task XKE, freeing the partition in which it
for task competition.

resides

>UNF FCSRES/REG
Frees the resident library for FCS from its partition.
>UNFIH , ,,MAC/RON
Unfixes the read-only segment of the MACR0-11 assembler from
its partition.
Command Error Message:
UNF -- TASK NOT FIXED
An attempt was made to
fixed.

4-184

unfix

task

that

was

not

MCR COMMANDS

UNL
UNLOAD
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 STB file must
reside on the system device
(LB:)
under the system UIC.
The SET
/SYSUIC command displays and defines the system UIC;
but usual values
are [1,50] for unmapped systems and [l ,54] for mapped systems.
Format:
UNL[OAD] dd:
where:
dd: - A 2-character ASCII device name
Example:
>UNL LP:

Unloads the loadable device driver for device LP:.
Command Error Messages:
UNL -- DEVICE ddn:

HAS UNITS ATTACHED, BUSY, AND/OR MOUNTED

An RSX-llM message.
Device ddn:
is the first or only
unit that is attached, mounted, and/or has outstanding
I/O. Therefore, the driver cannot be unloaded.
UNL -- DEVICE ddn:

NOT IN SYSTEM

No such device existed in the system.
UNL -- DEVICE NOT MOUNTED
The system device

(LB~)

was not mounted.

UNL -- DRIVER BUILT WITH WRONG EXECUTIVE STB FILE
The STB file for the driver was
the current Executive&

not

compatible

with

UNL -- DRIVER CANNOT BE UNLOADED
The Unload command attempted to remove a permanently
resident device driver
(that is, a driver linked to
the Executive).
UNL -- DRIVER NOT LOADED
The device driver specified in the Unload command
not resident in memory.

4-185

was

MCR COMMANDS

UNL (Cont.)
UNL -- FILE filename HAS ILLEGAL STB FORMAT
The driver's STB file contained illegal object code or
data.
UNL -- ILLEGAL VALUE FOR SYMBOL symname IN FILE filename
The symbol symname is defined to an illegal value by
the file ddDRV.STB.
Since ddDRV.STB had to pass
inspection by LOA,
there probably
has
been
a
procedural error or ddDRV.STB has been corrupted.
UNL -- LOADABLE DRIVER SUPPORT NOT IN SYSTEM
An RSX-llM message.
The system generation option
support loadable device drivers was not chosen.

UNL -- SYMBOL symname IS DOUBLY DEFINED BY FILE filename
The symbol symname was found in the file ddDRV.STB,
but
it was not a symbol definition. Since ddDRV.STB
had to pass inspection by LOA, there probably has been
a procedural error or ddDRV.STB has been corrupted.
UNL -- SYMBOL symname IS UNDEFINED BY FILE filename
The symbol symname was found in the file ddDRV.STB,
but
it was not a symbol definition. Since ddDRV.STB
had to pass inspection by LOA, there probably has been
a procedural error or ddDRV.STB has been corrupted.
Additional RSX-llM-PLUS Error Messages
UNL -- DEVICE ddn:

IS ATTACHED, BUSY, ONLINE AND/OR MOUNTED

Device ddn:
is the first or only unit that
is
attached, online, mounted, and/or has outstanding I/O.
Therefore, the driver cannot be unloaded.

4-186

CHAPTER 5

INDIRECT COMMAND FILES

This chapter describes indirect command files and how to use
them.
The sections that
follow describe the MCR indirect command file
processor and
its components and then define all the processor
directives that control the execution of an MCR indirect command file.

5.1

INTRODUCTION

An indirect command file
is a text file containing a
series of
commands exclusive to,
and
interpretable by,
a single task.
The
interpreting task
is usually
a
system-supplied
component
of
RSX-llM/M-PLUS, such as MCR, MACR0-11, or the Task Builder.
There are two types of indirect command files:
files and indirect MCR command files.

indirect task

command

An indirect task command file is a sequential file containing a
list
of task specific commands.
Rather than typing commonly used sequences
of commands, you can type the sequence once and store it
in a file.
The
indirect task command file is specified in place of the command
line(s} normally submitted to the task.
To initiate indirect task command files, replace the command string
for
a task with a file specifier, preceded by an at sign (@).
The
task requesting input then accesses the specified file and starts to
read and respond to the commands contained within it.
For example, to
initiate a file of MACR0-11 commands, input the following:
>MAC @INPT.CMD

The MACR0-11 Assembler accesses the file
commands contained within the file INPT.CMD.

and

then

executes

the

An indirect MCR command file contains a
list of MCR commands.
In
addition,
an indirect MCR command file can contain special commands
that allow you to control command file processing (see Section 5.2).
To initiate an indirect MCR command file, enter the file
specifier,
preceded by an at sign
(@),
whenever MCR can accept input.
For
example:
>@MCRIPT.CMD

The default file type for indirect command files is
above command line could also be input as follows:
>@MCRIPT

5-1

.CMD.

Thus

the

INDIRECT COMMAND FILES

An indirect file can contain any command that can
the task to which it is directed.

interpreted

Some tasks, including MCR, allow nested command files
(one command
file invokes another). See the appropriate task documentation for the
maximum nesting depth allowed.
When the processor reaches the end
displays the message

the

highest

level

file,

>@ <EDF>

and then exits.
To exit the indirect command file processor
(AT.) prematurely, type
@ii?Z)
in response to any request for input from the indirect file
processor. The message
>@ <EDF>

is then displayed.

5.2

MCR INDIRECT FILE PROCESSOR

Most tasks read and respond to commands contained in an indirect file
as if the commands were entered directly from a terminal. MCR,
however, has an indirect file processor for interpreting commands from
a file.
An MCR indirect command file can contain both normal MCR
commands and special commands (known as directives) to be interpreted
by the indirect file processor itself.
When processing an indirect command file, AT. first reads the command
file and interprets each command line either as a command to be passed
directly to MCR or as a request for action by the indirect command
file processor itself. The directives to AT. are distinguished by a
period (.) as the first character in the line. MCR commands have no
special pref ix characters.
The directives to AT.
to:

form a procedural language,

which

allows

you
=~

Define labels

Define and assign values to symbols of three types:
numeric, and string

Create and access data files

Control the logical flow within a command file

Perform logical tests

Enable or disable any of six operating modes

Increment or decrement a numeric symbol

Control time-based and parallel task execution

logical,

Two directives (.BEGIN and .END) permit you to block structure the
command file and create Begin-End blocks. Modular, block structured
command files are easier to debug and maintain.
More importantly,
Begin-End blocks isolate local symbol definitions as well as labels

5-2

INDIRECT COMMAND FILES

and thus conserve symbol table space. When you define a symbol,
the
indirect command file processor creates an entry in an internal symbol
table.
These symbol table entries retain their definitions throughout
the command file
execution if defined locally, or throughout all
levels of command files if defined globally.
Local symbols defined
within a block, however, are defined only within that block;
they are
erased from the symbol table when AT.
encounters an .END directive.
MCR displays on the requesting terminal every MCR command executed.
However,
if AT.
is activated by @filename/-MCR, MCR commands in the
indirect file are converted to comments with a
leading exclamation
point (1);
the MCR commands are displayed, but not executed.
An MCR indirect file can also include comments,
which the processor
prints at the
requesting terminal.
Comments that begin a line
interpreted by MCR have a leading semicolon (;).
(The semicolon can
be preceded on the same line by a directive to the
indirect
processor.) Comments that appear after the start of an MCR command
have a
leading exclamation point
(!).
All lines in an indirect
command file that begin with a period followed by a semicolon (.;) are
treated as comments, but are not displayed when the file is processed.
The indirect command file processor attaches the terminal while
processing contiguous comment lines (only comments beginning with ;,
not ! ) • This permits you to type
(cTRLto)
and suppress a
len9thy
comment.
Output is resumed by typing another
(CTRLto)
or is resumed at
the next MCR command in the command file.
The AT.
directives described in this chapter are listed below by
category.
A detailed description of each directive is presented in
alphabetical order in Section 5.6.

Label Definition
.label:

Assigns a name to a line in the command
so that the line may be referenced.

file

Symbol Def lnition
.ASK

Defines or redefines a
logical symbol and
assigns the symbol a logical (true or false)
value.

.ASKN

Defines or redefines a numeric symbol
assigns the symbol a variable value.

.ASKS

Defines or redefines a string symbol and
assigns the string symbol a variable ASCII
value.

• ERASE

Deletes local or global symbol definitions •

.SETT/.SETF

Defines or redefines a
logical symbol
assigns the symbol a true/false value.

and

.SETN

Defines or redefines a numeric symbol
assigns the symbol a numeric value.

and

.SETS

Defines or
redefines a string symbol and
assigns the symbol a character string value.

5-3

and

INDIRECT COMMAND FILES
File Access
.DATA

Specifies a single line of data to output
an output data file.

.CHAIN

Closes the current indirect
commands from another file.

• CLOSE

Closes an output data file •

.OPEN

Creates and opens an output data file (if the
file
exists, creates a new version and opens
it).

.OP ENA

Opens an existing file and appends subsequent
data (does not create a new version).

file

and

to
uses

Logical Control
• BEGIN

Marks the beginning of a Begin-End block •

• END

Marks the end of a Begin-End block •

.EXIT

Terminates processing of either a Begin-End
block or the current command file, returns
control to the previous level, and optionally
sets special symbol <EXSTAT> value.

.GOSUB

Branches to a label identifying a
within the command file.

• GOTO

Branches to a label within the command file •

.ONERR

Branches to a label upon detecting a specific
AT.
error condition.

.RETURN

Effects an exit from a subroutine and returns
to
the
line
immediately following the
subroutine call.

.STOP

Terminates indirect command file processing
and optionally sets AT.
exit status.

subroutine

Logical Tests
.IF

Determines whether or not a symbol satisfies
one of several possible conditions.

• I FACT/. IFNACT

Determines whether or not a task is active •

• IFDF /.I FN DF

Determines
defined.

• !FINS/. IFNINS

Determines whether or not a task is installed
in the system.

• IFLOA/. I FNLOA

Determines whether or not a device driver
loaded •

• IFT /.I FF

Determines whether a logical symbol
or false.

• TEST

Tests the length of a string symbol •

5-4

whether

not

symbol

is
true

INDIRECT COMMAND FILES
Enable/Disable An Operating Mode
.DISABLE

Disables substitution, data, global symbols,
lower-case option,
escape recognition,
or
echo control.

.ENABLE

Enables substitution, data,
lower-case option,
escape
echo control.

global symbols,
recognition,
or

Increment/Decrement Numeric Symbols
.DEC

Decrements the value of a numeric
one.

symbol

• INC

Increments the value of a numeric
one.

symbol

Execution Control
.DELAY

Delays the execution of an
indirect
file for a specified period of time.

.PAUSE

Stops the indirect command file processor and
allow user action.

.WAIT

Waits for
execution.

.XQT

Initiates a task, pass a command line to
it,
and continue indirect command file processing
without waiting for the task to complete

specified

task

command

complete

-"-"'
5.3

SYMBOLS

The MCR indirect file processor enables you to define symbols.
These
symbols can then be tested or compared in order to control flow
through the indirect command file.
They may also be substituted for
MCR commands, data records for data files, or comments to be displayed
on the terminal.
Symbol names are ASCII strings from l to 6 characters in length. They
must start with a letter (A-Z) or a dollar sign ($). The remaining
characters must be alphanumeric or $e
There are three symbol types:
•
•
•

Logical
String
Numeric

A logical symbol has either a true or false value.
A string symbol has as its value a string of ASCII characters, with
length between 0 and 80(10) characters inclusive.

A numeric symbol can have a numeric value in the range of 0-65535(10)
inclusive.
The symbol can be defined to have either a decimal or
octal symbol value.
The value (decimal or octal)
is
relevant only
when the symbol is substituted (see Section 5.3.2).

5-5

INDIRECT COMMAND FILES

A symbol's type (logical, numeric, or string) is defined by the first
assignment directive that assigns a value to the symbol. Subsequent
assignments may assign a different value, but cannot redefine the
symbol type. Assignment directives can assign:

5.3.1

•

A true or false value to define a logical symbol
(Defined by .ASK, .SETT or .SETF.)

•

An octal or decimal number to define a numeric symbol
(Defined by .ASKN or .SETN.)

•

A character string to define a string symbol
(Defined by .ASKS or .SETS.)

Special Symbols

The MCR indirect command file processor automatically defines special
symbols dependent upon specific system characteristics and the replies
to queries presented during command file execution. As with symbols,
special symbols can be compared, tested, or substituted and have three
types:
logical, numeric, and string.
All special symbols have a
common format;
angle brackets (<>) enclose the special symbol name.

5.3.1.1 Special Logical Symbols - The special logical symbols
assigned a true or false value under the following circumstances.
Symbol

are

Value

Set to true if last query was answered with a
escape character.
Otherwise,
<ESCAPE> is
false.

Set to true if answer to last numeric query
(.ASKN)
was defaulted (a single carriage return was entered).

Set to true if last string entered in response to an
.ASKS directive or tested with a .TEST directive
contains only alphanumeric characters.
An empty
string
also
sets <ALPHAN> true.
Note that a
lowercase response to a query when lowercase is
disabled sets <ALPHAN> false.

<RAD50>

Set to true if last string entered in response to an
.ASKS directive or tested with a .TEST directive
contains
only
Radix-50
characters.
Radix-50
characters
are the alphanumeric characters plus
period (.) and dollar ($). A blank is not a Radix-50
character in this context. An empty string also sets
<RAD50> true.

Set to true if the system on which AT.
is running is
mapped, false if the system is unmapped. Always true
in an RSX-llM-PLUS system.

Always false in an RSX-llM/M-PLUS system.

single
set to

5-6

,~,...4
....lllllJ~ZtiM•·•··~"''•iP"llliif~e~·......~--~an1111.-:>-;1m...--~··········•wc•~iii..-CS:...iznelillllll•r?trn~··. .llllililiiiiiliilllll.......__..._..~-.rc. .r........................................

INDIRECT COMMAND FILES

5.3.1.2 Special Numeric Symbols - The following values
to the. special numeric symbols.

are

assigned

Value
<ME:MS I Z>

Assigned the value of the current system memory
in K words.

Assigned the unit number of the user's default device
(SY : ) •

Assigned the value of O, 1, 2, or 4 depending on the
exit status from the last MCR command executed or
from the last .WAIT tskname directive where tskname
was activated by the .XQT directive.

size

This special numeric symbol
is modified at the
completion of a synchronous MCR command or at the
completion of a .WAIT directive.
The .EXIT directive
c~n also modify <EXSTAT>.
The value is returned from
the task that has completed if the task exits with
status.
Otherwise,
the value is returned from MCR.
The values O, 1, 2, and 4 indicate:

O
1

2
4

Warning
Success
Error
Severe error

Assigned the length of the string entered in response
to the last .ASKS directive or the string tested by
the last .TEST directive.

<SPACE>

Assigned the number, in octal, of free bytes
internal symbol table of AT ••

Assigned an octal number to r~present the operating
system on which AT.
is running.
The value 1 is for
an RSX-llM system, the value 6 is for an RSX-llM-PLUS
system.

·'-"···

5.3 .. 1.3 Special String Symbols - The
assigned the following string values.

special

string

the

symbols

are

Value
<CLI>

Assigned the acronym (three letters) of
the current
Command Language Interpreter (DCL or MCR);
format is
MCR.

<DATE>

Assigned the current date;

Assigned the UIC of the current
library;
format is [ggg,mmm]

Assigned the device mnemonic
user's default device (SY:);

5-7

format is dd-mon-yr.
nonprivileged

task

the

(two letters)
format is DK.

INDIRECT COMMAND FILES

Value
<SYSUIC>

Assigned the system UIC;

<TIME>

Assigned the current time;

format is hr:min:sec.

<UIC>

Assigned the current UIC;

format is [ggg,mmm]

5.3.2

format is [ggg,mmm].

Symbol Value Substitution

Substitution can occur in any line of a command file.
Indirect MCR
commands can use the values assigned to logical, numeric, string, or
special symbols by replacing a normal parameter
(for example, a
device-unit) with the symbol name enclosed in apostrophes
(for
example, 'DEV'). When a previous directive has enabled substitution
mode (.ENABLE SUBSTITUTION), AT.
replaces the symbol name enclosed in
apostrophes with the value assigned to the symbol.
When AT. encounters an apostrophe, it treats the subsequent text,
up
until a second apostrophe, as a symbol name. AT. then searches the
table of symbols for the corresponding symbol, and substitutes the
value of the symbol in the indirect command line in place of the
symbol name and surrounding apostrophes.
For example, the first three lines below appear in an indirect command
file.
When the processor executes these lines, it displays the last
two lines at the entering terminal •
• ASKS DEV MOUNT ON DEVICE?
.ENABLE SUBSTITUTION
MOUNT 'DEV'
>*MOUNT ON DEVICE? [SJ: DK2:
>MOUNT DK2:

DK2: was entere~ in response to the displayed question.
This reply
assigned the string value DK2: to string symbol DEV. Then when the
indirect file processor read:
MOUNT 'DEV'
it substituted for 'DEV' the value assigned to DEV, that is, DK2:. If
substitution mode was not enabled, the processor would simply have
passed the line to MCR as it appeared in the command file
(that is,
MOUNT I DEV').
If substitution mode is enabled, an apostrophe signals the beginning
of a string symbol. Thus, to include a single quote as text within a
command line, rather than as the start of a symbol, you must replace
the single quote with two contiguous apostrophes ('').
If substitution mode is enabled, the processor
file line
DON I IT SHOOT
as
DON'T SHOOT

5-8

displays

the

command

INDIRECT COMMAND FILES

5.3.3

Numeric And String Symbols

The MCR indirect command file processor assigns a value,
either
numeric or string, to symbols. This assignment defines the symbol as
either a numeric symbol or a string symbol.

5.3.3.1 Numeric Symbols And Expressions - A numeric symbol
is a
string of digits representing a value in the range of 0-177777 octal
(0-65535 decimal if
immediately followed by a period).
If an
arithmetic operation yields
a result outside of this range, a fatal
error occurs and the message
AT.--NUMERIC UNDER - OR OVERFLOW

is displayed.
When a numeric symbol is substituted into a string, the type (octal or
decimal)
is determined by the value assigned via an .ASKN or .SETN
dire~ctive ..
A numeric symbol or constant may be combined with another numeric
symbol or constant by a
logical or arithmetic operator to form a
numeric expression.
Arithmetic operators are used to add
(+),
subtract (·-), multiply (*), and divide (/).
Logical operators are the
inclusive OR (!) and logical AND (&).
No embedded blanks or tabs are
permitted between operators.
Numeric expressions are evaluated from left
to
right
unless
parentheses are used to form subexpressions that are evaluated first.
For example, the directive lines:
.SETN Nl 2
.SETN N2 3
.SETN N3 Nl+N2*4
assigns numeric symbol N3 the value 24

octal

whereas

the

directive

1 i neis

.SETN Nl 2
.SETN N2 3
.SETN N3 Nl+(N2*4)
assigns numeric symbol N3 the value 16 octal.
The type of an expression is octal if
otherwise the type is decimal.

all

the

For example, the directive lines:
.SETN Nl 2
.SETN N2 3
.SETN N3 Nl+N2*4.
assigns numeric symbol N3 the decimal value 20.

5-9

operands

are

octal;

INDIRECT COMMAND FILES
Numeric expressions are permitted as second operands
in numeric
.IF
and
.SETN directives.
They are also permitted as range and default
arguments in .ASKN and .ASKS directives.
The directives .EXIT and
.STOP permit numeric expressions to represent exit status.

5.3.3.2 String Symbols, Substrings, And
Expressions - A
string
constant is a string of any printable characters enclosed by quotes
(").
Empty strings are also permitted.
The number of characters
cannot exceed 80.
Examples:
"ABCDEF 11
1111

String symbols may have a value of any string coristant. The value is
assigned by a
.SETS or .ASKS directive.
For example, the directive
lines
.SETS
.SETS

Sl
S2

"ABCDEF"
Sl

assigns string symbol S2 the value
ABCDEF).

string

symbol

(that

is,

A substring facilitates the extraction of a segment from the value of
a string symbol.
You can use substrings only as second operands in
.SETS and .IF directives.
For example, the directive lines
.SETS
.SETS

Sl
S2

"ABCDEF"
Sl[l:3]

assign string symbol S2 the value of string symbol Sl beginning
character one and ending at character three (that is, ABC).

You can combine a string constant, symbol, or substring with another
string constant,
symbol,
or substring by the string concatenation
operator (+) to form a string expression.
String expressions are permitted as second operands in .SETS and
.IF
directives where the first operand is a string symbol.
For example,
the directive lines
.SETS
.SETS
.SETS

Sl
S2
S3

llA"

"CDEF"
Sl+ 11 B"+S2[1:3]

assign string symbol S3 the value of the concatenation of
string
11
symbol Sl, string constant
8", and the first three characters of
string symbol S2 (that is, ABCDE).

5.4

SWITCHES

The indirect file processor accepts three
/MC.

5-10

switches:

/TR,

/DE,

and

INDIRECT COMMAND FILES

Switch

Function

--/TR

Displays a trace of each p~ocessed line on the entering
terminal.
This function
is useful for debugging an
indirect command file.
Each command line,
including
those
that
begin with a
period
(directive),
is
displayed.
The period on the first directive
in the
line
is changed to an exclamation point (comment) and
displayed.
If the command causes some action to occur,
the next printed line indicates the action;
usually,
this line consists of the MCR commands
issued as a
result of the previous directive.

/DE

Indicates that the
indirect command
deleted when processing is complete.

file

/MC

Indicates that commands are to be passed to MCR.

Use any combination of the switches in the command
@filename /switches
or directive
.CHAIN filename /switches
To negate the action of the switch, prefix it with a minus sign (-) or
"NO"'
(for example,
/NOMC suppresses sending of commands).
The
defaults are /NOTR, /NODE, and /MC.
The switches you specify in the terminal command that
initiates
indirect processing are used as defaults when executing the commands
filename[/switches] or
.CHAIN filename[/switches].
This does not
apply, however, for the /DE switch;
the default is always /NODE.

5.5

MULTI-LEVEL INDIRECT FILES

You can specify up to four levels of MCR indirect command files.
A
processor directive
(.ENABLE GLOBAL)
allows the definition of some
symbols as global to all indirect file levels
(see Section 5.6.12).
Otherwise, each time the processor enters a deeper level, it masks all
symbols defined by the previous level out of the symbol table, so that
only symbols defined in the current level are available.
These
symbols are local only to the level of command file in which they are
defined.
When control
returns to a previous level, the symbols
defined in that level become available once again and the ones from
the lower level are lost.

5.6

DIRECTIVES

Directives must be separated from
commands by at least one space.

'-''·
5-11

their

arguments

and

from

MCR

INDIRECT COMMAND FILES
You can insert any number of
places of a command line:

blanks

and

•

At the start of the command line

•

Immediately following the colon

•

At the end of the command line

horizontal

tabs

three

(:) of a label

This allows you to format the command files
for
readability.
The
recommended procedure is to begin labels in column one and everything
else in column nine (after one horizontal tab).
lines processed between .ENABLE and
An important exception is the
.DISABLE DATA directives;
no blanks or tabs are removed from these
lines.
For example:
• I FT Z • GOTO l 0
MAC @ASM
•l 0:
TK B @BL D
.OPEN DATFIL
.DATA XXXXX
.ENABLE DATA
THIS IS DATA
THAT GOES INTO
THE DATA FILE
• DISABLE DATA
.GOTO 20

5.6.l

Define A Label

.label:

Labels always appear at the beginning of the line;
they may be on a
line with additional directives and/or an MCR command, on a line with
a comment, or on a line by themselves.
When control passes to a
line
with a label, the line is processed from the first character after the
colon.
Commands do
one
label
and must be
may contain

not have to be separated from the label by a space.
Only
is permitted per line.
Labels are l to 6 characters long,
preceded by a period and terminated by a colon.
A label
only alphanumeric characters and/or dollar sign ($).

It is also possible to define a label as a direct access label;
once
the
label
is found, its position in the command file is saved.
This
allows subsequent jumps to frequently called labels or subroutines to
be effected very quickly.
The first statement processed after a jump
to a direct access label is the one on the next line.
You can define
up to 20(10) direct access labels within an indirect command file.
If
you define more than 20, the subsequent direct access labels
replace
the earliest and so on.

5-12

. ..-.....................-.__.__................................-.----------llllilllll----iimliilmllli..............liliiililililli. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ._ _l_I

INDIRECT COMMAND FILES
To declare a label as direct access,
colon blank.

leave

the

line

following

the

Examples:
.100:

.ASK A DO YOU WANT TO CONTINUE?

• !FT

.GOSUB

200

.200:
;THIS IS THE START OF A SUBROUTINE

.RETURN

Ask A Question And Wait For A Reply

5.6.2

.ASK

The .ASK directive prints a question on the terminal,
waits for a
reply,
and sets a
specified logical symbol to the value of true or
false, depending on the reply.
If the symbol has not already been
defined,
the processor makes an entry in the symbol table.
If the
symbol has been defined, the processor resets
its value
(true or
false) in accordance with the reply.
The processor exits with a fatal
error if the symbol was previously defined as a string or numeric
symbol.
Forrna t:
.ASK ssssss txt-strng
where:

ssssss

1- to 6-character
true/false value.

symbol

assigned

txt-strng

any ASCII string of characters, preceded by
least
one
blank.
The maximum length
txt-strng is 70.

at
of

When executing an .ASK directive,
the processor displays txt-strng
prefixed by an asterisk and suffixed with "? [Y/N] :". The processor
recognizes four answers:
1. Y(~ - set symbol ssssss to true.
2 • N(~ - set s ymbo 1 s s s s s s to fa 1 s e •
3. ~
- set symbol to false.
<CR> indicates carriage return.
4. ~·~)
- set symbol ssssss to true and set the special logical
symbol
<ESCAPE> to true only if escape recognition has been
enabled.
~· indicates escape or altmode.

5-13

INDIRECT COMMAND FILES
Example:
The directive line
.ASK INSPIP DO YOU WANT TO INSTALL PIP
displays
>*DO YOU WANT TO INSTALL PIP? [Y/NJ:

on the terminal.
user types Y, N,

Symbol INSPIP will be set to true or false after the
or ~ (if escape recognition is enabled).

.ASKN

Ask For Definition Of A Numeric Symbol

5.6.3

The .ASKN directive prints on the terminal a
request
for
a numeric
value,
waits for it to be entered, optionally tests the range of the
numeric
response and/or applies a default value,
and sets the
specified symbol accordingly.
If the symbol has not previously been
defined, the processor makes an entry in the symbol table.
If the
symbol has already been defined, the processor resets its value in
accordance with the reply.
The processor exits with a fatal error
if
the symbol was previously defined as a logical or string symbol.
Format:
.ASKN ssssss txt-strng
.ASKN[low:high] ssssss txt-strng
.ASKN[::def] ssssss txt-strng
.ASKN[low:high:def] ssssss txt-strn~
(Brackets are required syntax)
where:
ssssss

1- to 6-character
numeric value.

symbol

assigned

txt-strng

any ASCII string of characters, preceded by at
least
one
blank.
txt-strng is the text
displayed by the indirect file processor.
The
maximum length of txt-strng is 70.

low: high

the inclusive limits for the response.

def

the default value.

The range and default arguments permit you to combine numeric symbols
or constants with another numeric symbol or constant to form a numeric
expression (see Section 5.3.3.1).
The command line cannot exceed 80 characters
in length.
When
executing
an .ASKN directive,
the processor displays txt-strng
prefixed by an asterisk and suffixed with [O]:
to indicate that the
response is considered as octal or [D]:
to indicate that the response
is considered as decimal.
The reply must be a number either within
the specified range or in the range 0-177777 octal by default, 0-65535
decima 1.
If the response is outside the specified range, the message
AT, -- VALUE NOT IN RANGE

is displayed and the query repeated.
5-14

INDIRECT COMMAND FILES

If an arithmetic operation yields a result greater than 177777(8) when
computing the actual value of any of the arguments low, high, or
default, a fatal error occurs and the message
AT. -- NUMERIC UNDER- DR OVER-FLOW

is displayed.
If the response is an empty.line (null) and a default value (def)
was
not specified,
the processor applies a default of 0. Note that in
this case, the range, if specified, must include 0.
The response may be either octal or decimal;
a leading pound sign (#)
forces octal, a trailing period (.) forces decimal.
In the absence of
both, the processor applies a
default
type.
The default
type
is
decimal
if either the range or default values are decimal expressions
(followed by a period).
Otherwise, the default type
is octal.
AT.
displays the default type as either [O] or [D].
To force a decimal default type without specifying a
use the following construction:

range

argument,

.ASKN [::O.] A ENTER VALUE
determines
When a numeric symbol is substituted into a string, AT.
the
type
(octal or decimal) by the assigned value. The type of the
source value is then copied to the destination symbol.
Examples:
The directive line
.ASKN

SYM

DEFINE NUMERIC SYMBOL A

displays
>*DEFINE NUMERIC SYMBOL A COJ:

on the entering terminal where:
[O]

= the default type

(octal).

The processor then defines symbol SYM according to the reply entered.
The directive line
.ASKN [2:35:16] NUMSYM DEFINE NUMERIC SYMBOL A
displays
>*DEFINE NUMERIC SYMBOL A CO R:2-35 D:1GJ:

in the format

[x R:low-high D:def]

where:

O if the default radix is octal,
dee ima 1.

R: low-high

the specified range.

D:def

the specified default.

5-15

INDIRECT COMMAND FILES
The processor then checks that
specified inclusive range.

the

response

string

within

the

The directive line
.ASKN [NUMSYM+l0:45:NUMSYM+l0] SYM DEFINE NUMERIC SYMBOL B
displays

(assuming the default value of 16 for NUMSYM)

>*DEFINE NUMERIC SYMBOL B CO R:2G-45 D:2GJ:

5.6.4

Ask For Definition Of A String Symbol

.ASKS

THE .ASKS directive prints on the terminal a
request for
a string
value to define a specified symbol, and optionally tests that the
number of characters in the response string falls within the specified
inclusive
range.
If the symbol has not previously been defined, the
processor makes an entry in the symbol table.
If the symbol has
already been defined,
the processor resets its value in accordance
with the reply.
The processor exits with a fatal error if the symbol
was defined previously as a logical or numeric symbol.
If the number
of characters is out of the specified range, the message
AT. -- STRING LENGTH NOT IN RANGE

is displayed and the query repeated.
Formats:
.ASKS ssssss txt-strng
.ASKS [low:high] ssssss txt-strng
(Brackets are required syntax)
where:
ssssss

1- to 6-character symbol to be assigned a string
value.

txt-strng

any ASCII string of characters, preceded by at
least
one
blank.
txt-strng is the text
displayed by the indirect file processor.
The
maximum length of txt-strng is 70.

low: high

the
inclusive limits
for
the
number
characters permitted in the response string.

The command line cannot exceed 80 characters in length.
When specifying range arguments, you may combine numeric symbols or
constants with another numeric symbol or constant to form a numeric
e xp res s i on ( s e e S e ct i on 5 • 3 • 3 • l ) •
When executing an .ASKS directive, the processor displays txt-strng
prefixed by an asterisk (*) and suffixes it with [S]:. The reply must
be an ASCII character string.

5-16

INDIRECT COMMAND FILES

Examples:
The directive line
.ASKS NAM PLEASE ENTER YOUR NAME
displays
>*PLEASE ENTER YOUR NAME ESJ:

on the entering terminal.
The processor
according to the string reply entered.

then

defines

symbol

NAM

The directive line
.ASKS [1:15] MIDNAM PLEASE ENTER YOUR MIDDLE NAME
displays
>* PLEASE ENTER YOUR MIDDLE NAME ES R:1-15J:

in the format

[S R:low-high]

the symbol type

R:low-high

the specified range for number of characters.

(string).

Begin Block

5.6.5

.BEGIN

The .BEGIN directive marks the beginning of a Begin-End block.
All
local symbols
following the directive are local to the block instead
of the entire command file.
An .ERASE LOCAL directive· (see Section
5.6.14) erases all local symbols within the block.
Begin-End blocks can be nested up to a maximum depth of 127.
AT.
usually exhausts stack space before this limit can be reached;
you
may wish to rebuild AT.
and specify more task stack space
if an
application requires the maximum nesting level.
Format:
• BEGIN
.BEGIN must be the only directive on a
line.
The
.BEGIN directive
cannot appear, for example, on the same line as an .IF directive.
Begin-End blocks isolate local symbol definitions and labels.
All
local symbols defined
inside a block
lose definition outside the
block.
However, all symbols defined outside a block retain definition
throughout
the command file.
Note that symbols defined outside a
block and then modified within a block assume and
retain the value
assigned in the block.
The block must be terminated by an .END directive.

5-17

INDIRECT COMMAND FILES
.CHAIN

Continue Processing Using Another File

5.6.6

The .CHAIN directive closes the current indirect file, masks all local
symbols,
and continues processing using commands fetched from anoth~r
file.
However, the .CHAIN directive does not close data files or
change the file indirection level.
Format:
.CHAIN filename

[/switches]

where filename is the name of the file that contains the new commands
and /switches are any of the optional switches described in Section
5 .. 4.
Example:
The directive
.CHAIN OUTPUT
transfers control to the file OUTPUT.CMD.

.CLOSE

Close Secondary File

5.6.7

The .CLOSE directive closes the secondary
directive.

file

opened

.OPEN

Format:
.CLOSE [#n]
(Brackets not part of syntax.)
where:
#n

optional file number in the range 0-3
inclusive.
Default
is #~.
You can substitute a numeric
symbol for the value n by enclosing the symbol in
apostrophes.

Output Data To Secondary File

5.6.8

.DATA

The .DATA directive specifies text that is to be output to a secondary
file previously opened by an .OPEN directive.
Format:
.DATA [#N] text-string
(Brackets not part of syntax.)
where:
text-string

text to be output to the secondary file.

optional file
number
in
the
range
0-3
inclusive.
Default is O.
You can substitute
a numeric symbol for the value N by
including
single quotes ..

5-18

INDIRECT COMMAND FILES
The command line cannot exceed 80 characters.
(The specified text
cannot continue onto the next line.) If a secondary file is not open,
an error condition exists;
the
indirect file
processor
issues an
error message and begins error processing.
Example:
.SETS SEND "THIS IS DATA"
.OPEN TEMP
.DATA 'SEND'
.CLOSE
These directives output THIS IS DATA to the secondary file TEMP.DAT.

Decrement Numeric Symbol

5.6.9

.DEC

The ~DEC directive decrements a numeric symbol by 1.
The processor
exits with a
fatal error if the symbol was defined previously as a
logical or string symbol.
Format:
.DEC ssssss
where:
1- to 6-character numeric symbol.

SS SS SS

Example:
.DEC N
This directive decrements by 1
symbol N.

5.6.10

the

value

assigned

the

numeric

Delay Execution For A Specified Period Of Time

The oDELAY directive delays further processing of
for a specified period of time.

the

.DELAY
indirect

file

Format:
.DELAY nnu
where:
nn
u

Number of time units to delay.

= T - ticks
S
M
H

seconds
minutes
hours

The parameter nn is octal by default, or decimal if terminated with
period.
For example:

lOS is 10(8) seconds
10.S is 10(10) seconds
When the DELAY directive is executed, the processor issues the message
AT.

-- DELAYING

5-19

INDIRECT COMMAND FILES
When the time period expires
issues the message

and

the

task

resumes,

the

processor

AT, -- CONTINUING

Example:
The directive
.DELAY 20M
delays processing for 20(8), or 16(10) minutes.

5.6.11

.DISABLE

Disable Option

The .DISABLE directive
disables
a
specified
operating
mode
(substitution, data, global symbol, lower-case, escape recognition, or
echo control) previously activated by an .ENABLE directive.
See
Enable Option (Section 5.6.12) for operating mode information.
Formats:
.DISABLE SUBSTITUTION
.DISABLE DATA [#n]
(Brackets not part of syntax.)
where:
#n

optional file number in the range 0-3.
Default
is O.
You can substitute a numeric symbol for the value n by
enclosing the symbol in apostrophes •

• DISABLE GLOBAL
.DISABLE LOWERCASE
.DISABLE ESCAPE
• DISABLE QUIET

5.6.12

.ENABLE

Enable Option

The .ENABLE directive is used to invoke one of six operating modes:
lower to upper-case character conversion;
data mode;
global symbol
mode;
substitution mode;
recognition of an escape character;
or
echo control.
Each mode is independent of the others;
all six can be
active simultaneously. When the indirect
file processor starts to
process a command file, the initial settings are:
Lower case
Data
Global
Substitution
Escape
Quiet

enabled
disabled
disabled
disabled
disabled
disabled

In lower-case mode, characters read from the terminal in response to
.ASKS directives are stored in the string symbol without lower- to
upper-case conversion.
The
representation
of
characters
is
significant when comparing strings (see Section 5.6.18) since the .IF
5-20

INDIRECT COMMAND FILES
directive treats lower-case and upper-case characters as distinct.
Also,
note that if lower-case mode is disabled and the response to a
query is in lower-case, the special logical symbol <ALPHAN> is set to
false.
In data mode, the processor outptlltS lirl'es that follow the directive
line
.ENABLE DATA to a secondafy file.
{The .DATA directive sends a
single line of text to a secondaty file;
see Section 5.6.8.)
In global symbol mode, symbol na$es that begin with a dollar sign
($)
are defined as global to all levels of indirect files;
once such a
symbol has been defined, all levels recognize it.
Symbols that do not
begin with a dollar sign are always recognized only by the level that
defines them.
In substitution mode, the processor substitutes a string in place of a
symbol.
The symbol must begin and end in apostrophes ('SYMBOL').
For
example, if the symbol A has been assigned the string value THIS IS A
TEST,
then every A will be
replaced by THIS IS A TEST. When
substitution mode is active, the processor performs substitutions on
each line before scanning the line for directives and MCR commands.
(While obeying a .GOTO label directive, however, the processor ignores
any undefined symbols encountered before the target line, that is, the
line containing the specified label.)
Escape recognition permits the response to an .ASK,
.ASKN, or
.ASKS
directive to be an escape character.
A question answered with a
single escape character sets the special logical symbol
<ESCAPE> to
true.
The escape character must be used only as an immediate
terminator to the question;
if one or more characters precede the
escape, an error condition exists.
In this case, the message
AT.--INVALID ANSWER OR TERMINATOR

is printed and the query repeated.
Note that if you type
response to an .ASK directive, the specified logical symbol
.ASK ssssss txt-strng) is also set to true.

~:
in
(ssssss of

Quiet mode is valid only in systems that support parent-offspring
tasking;
the directive performs no function in systems that do not
support parent-offspring tasking.
In quiet mode, the processor does
not echo Command Line Interpreter (CL!) command lines. The command
lines are executed normally and, if they return a message or display,
the message or display is printed on the terminal.
Formats:
.ENABLE LOWERCASE
.ENABLE SUBSTITUTION
.ENABLE DATA [#n]
(Brackets not part of syntax.)
where:
#n

optional file number in the range 0-3~ Default
is O.
You can substitute a numeric symbol for the value n by
enclosing the symbol in apostrophes •

• ENABLE GLOBAL
.ENABLE ESCAPE
• ENABLE QUIET
5-21

INDIRECT COMMAND FILES

Examples:
•

Substitution mode .ENABLE SUBSTITUTION
.ASKS FIL SPECIFY SOURCE FILE
MAC
'FIL'='FIL'
When the indirect file is executing, the
displayed at the terminal are:

corresponding

lines

*SPECIFY SOURCE FILE [SJ:soURCE
>MAC SOURCE=SDURCE

•

Lower-case mode .ENABLE SUBSTITUTION
.ENABLE LOWERCASE
.ASKS A DEFINE STRING SYMBOL A
;

When the file is executing, the corresponding lines
at the terminal are:

displayed

>*DEFINE STRING SYMBOL A [SJ:RsX is in caps
:>;RSX is in caps

•

Global symbol mode The following two lines appear in
BOBl:

indirect

command

file

.ENABLE GLOBAL
.SETS $X "TEST"
A file called BOB2.CMD contains the following lines:
.ENABLE SUBSTITUTION
@BO Bl
MAC '$X', '$X'='$X'
Therefore, MCR displays the following when the
is run:

file

BOB2.CMD

>@5051

>MAC TEST1TEST=TEST
>@ <EDF>

•

Data mode
.OPEN SECFILE.DAT
.ENABLE DATA

.DISABLE DATA
The lines that fall between the .ENABLE
and
.DISABLE
directives are written to the secondary file SECFILE.DAT.

5-22

INDIRECT COMMAND FILES
•

Escape recognition mode ;IF YOU WANT A LIST OF OPTIONS, TYPE <ESC>
.ENABLE ESCAPE
.ASKS A ENTER OPTION
.IFT <ESCAPE> .GOTO LIST

.LIST: ;OPTIONS ARE: A (ADD), S (SUBTRACT), M (MULTIPLY)
If the user types the escape key (which is not displayed)
in
response to ENTER OPTION, the corresponding lines displayed at
the terminal are:
>;IF YOU WANT A LIST OF OPTIONSt TYPE <Esc~
>* ENTER OPTION [SJ: ®Q
> iOPTIONS ARE: A <ADD> t S <SUBTRACT> t M <MULTIPLY)

•
~

Quiet mode .ASK QUIET DO YOU WANT COMMANr LINES SUPPRESSED
.IFT QUIET .ENABLE QUIET
.IFF QUIET .DISABLE QUIET
ACT
If the response is affirmative,
the processor displays
active tasks, but not the Active command.
For example:

the

>DO YOU WANT COMMAND LINES SUPPRESSED? [Y/NJ:y
MCR, ••
ACTT 1 7
AT. T 1 7

5.6.13

End Block

.END

The ~END directive marks the end of the Begin-End block.
If AT.
encounters more .END directives than .BEGIN directives, command file
processing terminates and displays the following message:
AT+ -- ILLEGAL NESTING

Format:
.END
as the only directive on a line.

5 • 6 .14

Del ete Symbols

.ERASE

The oERASE directive deletes all local or global symbol definitions.
When you define a symbol, either locally (by defining a symbol value)
or globally (by enabling global symbol mode and preceding the symbol
name with a dollar sign ($)),AT.
creates an entry in a symbol table.
The oERASE directive erases either all local or all global entries
in
the table.
Following an .ERASE directive, you can redefine symbol values as
as symbol type.

5-23

well

INDIRECT COMMAND FILES
Formats:
.ERASE LOCAL
.ERASE GLOBAL
An .ERASE LOCAL directive outside of a Begin-End block erases all
local symbols.
An .ERASE LOCAL directive within a Begin-End block
erases only those local symbols defined in the block.
An .ERASE
GLOBAL, either outside of or within a Begin-End block, erases all
global symbols.
Example:
.ERASE LOCAL
This directive erases all local symbol definitions
command file.

5o6.15

for

the

indirect

.EXIT

Exit Current Command File

The .EXIT directive terminates processing of the current command file
or Begin-End block and returns control to the previous level command
file or, if the directive is executed within a block,
to the line
following an .END directive.
If the directive is encountered at the
uppermost indirect nesting level, AT.
exits and passes control to MCR
{see the .STOP directive, Section 5.6.29).
The directive also allows you to optionally specify a
into the special symbol <EXSTAT>.

value

copy

copied

the

Format:
.EXIT [value]
(Brackets not part of syntax.)
where value is an optional numeric expression
special symbol <EXSTAT>.

Examples:
The following line appears in an indirect command file 8081:
@8082
The file 8082.CMD contains the following line:
.EXIT
When AT.
encounters the .EXIT directive in 80B2, control
80Bl.CMD.

returns

If the .EXIT directive in 80B2.CMD includes a numeric expression,
example:

to
for

.EXIT N+2
AT.

evaluates the expression and copies the value into <EXSTAT>.

5-24

INDIRECT COMMAND FILES

.'-'.

5.6.16

Call A Subroutine

.GOSUB

The .GOSUB directive saves the current position in an
indirect
file
and then branches to a label. The label identifies an entry point to
a subroutine which is terminated by a .RETURN directive.
When you issue a .GOSUB directive from within a Begin-End block, AT.
saves the current block context and then scans down the file searching
for the first occurrence of the subroutine label.
Note that during
the scan, AT.
ignores any intervening .BEGIN or .END directives.
The
.RETURN directive
restores previous block context.
Thus,
the
subroutine can be contained within a Begin-End block.
The maximum nesting depth for subroutine calls is eight.
Form.at:
.GOSUB label
where label
is the
label that designates the first
line of a
subroutine,
but without
the l~ading period and trailing colon.
The
label must be preceded by at least one space.
Example:
The directive
.GOSUB EVAL
transfers control to the subroutine labeled .EVAL:.

5.6.17

Branch To A Label

.GOTO

file
The .GOTO directive causes a branch from one line in an indirect
to another.
All commands between the .GOTO directive and the
in
specified label are ignored.
Branches can go forward or backward
the file.
When executing a .GOTO directive, AT.
ignores all lines within a
nested Begin-End block.
Thus, the target label of a .GOTO directive
cannot be contained within a block
(unlike the target label of a
.GOSUB directive).
Likewise, the target of a .GOTO branch from within
a Begin-End block must be contained in that block;
the
.GOTO
directive cannot branch into or out of a block.
Note, however, that
AT.
permits branches across nested blocks.
When AT.
encounters
a
.GOTO directive within a Begin-End block,
it scans for the label
within that
block.
Since the
label scan starts at the
.BEGIN
directive and continues to the .END directive, multiply defined labels
are permitted within a block.
Fonna t:
.GOTO label
where label is the name of the label, but without the leading period
and trailing colon.
The label must be preceded by at least one space.
Example:
The directive
.GOTO 100
transfers control to the line containing the label .100:.
5-25

INDIRECT COMMAND FILES
5.6.18

Logical Test

A number of directives make tests;
if the test is true, AT.
processes the
remainder of the command line.
Logical tests can be
.AND and .OR
combined into a compound logical test by using the
directives.
5.6.18.1 Test If Symbol Meets Specified Condition .IF - The .IF
directive compares a numeric or string symbol with another expression
of the same type to determine if one of several possible conditions is
true.
If the condition is satisfied,
the processor executes the
remainder of the command line. When comparing a string symbol with a
string expression, the indirect processor compares the ASCII values of
each operand's characters (from left to right) one by one.
An operand
is considered greater if the first non-equal character has a greater
value than the corresponding character in the other operand.
Numeric
symbols are compared strictly on the basis of magnitude.
Format:

• IF symbol relop expr
where:
symbol

1- to 6-character
symbol.

re lop

one of the following relational operators:
EQ or
NE or
GE or
LE or
GT or
LT or

expr

<>
>=
<=
>
<

name

numeric

string

- equal to

- not equal to
- greater than or equal to
less than or equal to
- greater than
less than

expression of same type as symbol.

Examples:
.SETS x "A II
.SETS Y "a"
.IF X LT Y .GOTO 200

The ASCII value of string symbol X is less than the ASCII value of
string symbol Y, which satisfies the less than condition. Thus,
control passes to the line containing the label .200: •
• SETN Nl 2
.SETN N2 7
.IF Nl <= N2 PIP /LI
With the condition satisfied (numeric symbol Nl less than or equal
numeric symbol N2), the PIP command is processed •
• SETS Sl "AAb"
.SETS S2 "AA"
.SETS S3 11 8888 11
.IF Sl >= S2+S3[1:1]

.INC N

Since the condition where string symbol Sl is greater than or equal to
string symbol S2 concatenated with the first character of string
symbol S3 (AAb >= AAB) is satisfied, the processor increments numeric
symbol N.
5-26

INDIRECT COMMAND FILES

"-"'

5.6.18.2 Test If Task Is Active Or Dormant .IFACT/.IFNACT - The
.IF.A.CT or .IFNACT directive tests whether a task is active (.!FACT) or
dormant (.IFNACT).
If the test is true, the rest of the command is
processed.
If the specified task is not installed, the processor
assumes the dormant condition.
Formats:
.!FACT

tttttt

• IFNACT

tttttt

where:
tttttt

= a task name.

The task name tttttt must be preceded and followed
blank.

least

one

Examples:
.!FACT

REPORT

.GOTO 350

• IFNACT

REPORT

RUN REPORT

5.6.18.3 Test If Symbol Is Defined Or Not Defined .IFDF/IFNDF - The
.IFDF or .IFNDF directive tests whether a logical, numeric or string
symbol has been defined (.IFDF) or not defined (.IFNDF).
If the test
is true,
the rest of the command line is processed. This directive
does not test the value of the symbol.
Formats:
.IFDF

ssssss

.IFNDF

ssssss

where::
ssssss

1- to 6-character symbol being tested.

At least one blank must precede and follow the symbol.
Examples:
.IFDF

.GOTO 100

.IFNDF

.ASK A DO YOU WANT TO SET TIME

5.6.18.4 Test
If
Task
Is
Installed
Or
Not
Installed
• I FINS/. I FN INS - The • I FINS or • I FN INS directive tests whether a task
is installed (.!FINS) or not installed (.IFNINS) in the system.
If
the test is true, the rest of the command line is processed.

5-27

INDIRECT COMMAND FILES
Formats:
.IFINS

tttttt

• IFNINS

tttttt

where:
tttttt = a task name.
The task name tttttt must be preceded and followed
blank.

least

one

Examples:
.IFINS

PIP

.GOTO 250

.IFNINS

PIP

INS [l,50]PIP

Test If Driver Is Loaded Or Not Loaded .IFLOA/.IFNLOA - The
.IFLOA or .IFNLOA directive tests whether a driver is loaded {.IFLOA)
or not loaded {.IFNLOA) in the system.
If the test is true, the
rest
of
the command line
is processed.
Note that for purposes of this
directive, resident drivers are assumed to be loaded.
5~6.18.5

Formats:
.IFLOA dd:
• IFNLOA dd:
where:
dd:

a device driver.

Examples:
.IFLOA DK:

.GOTO 250

.IFNLOA DK:

LOA DK:

5~6.18.6

Test If Symbol Is True Or False .IFT/.IFF - The .IFT or .!FF
directive
tests whether a
logicai symbol is true or false.
If the
test is true, AT.
processes the remainder of the directive line.

The processor exits with a fatal error if the symbol being tested
previously defined as a numeric or string symbol.
Formats:
.IFT

ssssss

.IFF

ssssss

where:
ssssss

1- to 6-character logical symbol being tested.

At least one blank must precede and follow the logical symbol.

5-28

was

INDIRECT COMMAND FILES
Examples:
.IFT

.GOTO

100

.IFF

.GOTO

200

5.6.18.7 Compound Tests - You can combine "If" tests by using the
.AND and
.OR directives.
In addition, an implied .AND is effected
when more than one IF appears on the same line without being separated
by an .AND directive.
The compound operators .AND and .OR must be
preceded and followed by at least one blank.
The .AND directive takes precedence over the .OR directive as shown in
the following example:
.IFT A .OR .!FT B .AND .IFT C .GOTO D
That is, the processor reads the line as:
• I FT A • 0 R ( • I FT B • AND • I FT C ) .. GOTO D
Examples:
.IFT A .AND .IFF B

.GOTO HELP

If the logical symbol A is true and the logical symbol
control passes to the line containing the label .HELP: •

false,

If the logical symbol A is true or if the logical symbol B
the MCR Run command is issued.

false,

• IFT A .!FF B

.GOTO HELP

Same effect as the previous directive
• IFT A .OR

5.6.19

(.AND implied) •

.IFF B RUN PIP

Increment Numeric Symbol

• INC

The .INC directive increments a numeric symbol by 1.
The processor
exits with a
fatal
error if the symbol was previously defined as a
logical or string symbol.
Format:
.INC ssssss
where:
ssssss

1- to 6-character numeric symbol.

Example:
• INC N

Increment by 1 the value assigned to the numeric symbol N.

5-29

INDIRECT COMMAND FILES
5.6.20

Define Logical End Of File

The logical end of file directive
exits.
The message

I
(/) terminates file

processing

and

>@<EDF>

is then displayed.
li'orma t:

I
as the first non-blank character on a line.
You can use this directive at any location in the command file
to
quickly terminate file Frocessing, but care should be taken to avoid
an inadvertent exit.
Example:
.ASK CONT DO YOU WISH TO CONTINUE
.IFT CONT .GOTO 100
.100:

5.6.21

Branch To Label On Detecting An Error

.ONERR

If the processor detects one of the following errors:
•

Task not installed in system (.XQT, .WAIT, .!FACT, .IFNACT)

•

Undefined symbol

•

Bad syntax (.XQT, .WAIT, .DELAY)

•

Unrecognized command

•

String substitution error

•

Symbol type error

•

Redefinition of a symbol to a different
.ASKS, .SETT, .SETF, .SETN, .SETS)

•

Data file error
(.OPEN,
.OPENA,
.ENABLE DATA and .DISABLE DATA)

(any command)

(.IF, .!FT, .IFF, .INC, .DEC)
type

.DATA,

(.ASK,

.ASKN,

.CLOSE,

between

control passes to the line containing the specified label.
This
feature provides you with a means of gaining control in order to
terminate command file processing in an orderly manner.
Note that the .ONERR directive applies only to the error conditions
listed above;
errors
returned from a
task external to AT.
(for
example, an MCR syntax error) are not processed by the
.ONERR
directive.
Format:
.ONERR

label

5-30

INDIRECT COMMAND FILES
Upon detecting an error, the processor passes control to the
line
starting with .label:. The .ONERR directive must be issued before AT.
encounters the error condition.
If the directive is executed (one of
the above errors
is encountered),
error processing passes to the
specified label.
Subsequent errors pass control to the same label
until a
new .ONERR directive is executed.
If the label specified by
the .ONERR directive does not exist and an error condition has
occurred, indirect command file processing terminates.
Example:
.ONERR

100

Upon detecting one of the above error conditions, the indirect command
file processor passes control to the line labeled .100:.

5.6.22

Open Secondary File

.OPEN

The .OPEN directive opens a specified
file ..

secondary

file

output

Formc;1 t:
.OPEN [#n] filename
(Brackets not part of syntax.)
where:
file.

Def a ult

filename

a file to be opened as an output
file type is .DAT.

optional file number in the range 0-3
inclusive,
allowing up to
four data
files
to be open
simultaneously.
Default
is
#0.
You
can
substitute a numeric symbol for the value n by
enclosing the symbol in apostrophes.

Example:
.OPEN SECOUT
This directive opens the file SECOUT.DAT as an output file.

5.6.23

Open Secondary File For Append

.OP ENA

The .OPENA directive opens a secondary file and appends all subsequent
data to the file.

5-31

INDIRECT COMMAND FILES

Format:
.OPENA [#n] filename
(Brackets not part of syntax)
where:
filename

A secondary file to be opened with subsequent
data appended to it.
Default file type is .DAT.

optional file number in the range 0-3 inclusive,
allowing up to four data files to be open for
append simultaneously.
Default is #0. You can
substitute a numeric symbol for the value n by
enclosing the symbol in apostrophes.

Example:
.OPENA SECOUT
This directive opens the file SECOUT.DAT as an output file and appends
subsequent data to it.

5.6.24

Pause ~or Operator Action

.PAUSE

The .PAUSE directive interrupts processing of an indirect file to wait
for user action.
A .PAUSE directive causes the
indirect
file
processor task to stop itself.
The user may then perform some
operations and subsequently cause the task to resume.
Format:
.PAUSE
When the indirect file processor task stops itself,
following message on the entering terminal:
AT. -- PAUSING.

displays

TO CONTINUE TYPE "UNS tttttt"

where:
tttttt

= the name of the

indirect file processor task.

The operator then types the following command to resume the task:
>UNS

tttttt

The indirect file processor then displays the message:
AT, -- CONTINUING

and it continues processing where it left off.

5-32

the

INDIRECT COMMAND FILES
Return From A Subroutine

5.6.25

.RETURN

The oRETURN directive signifies the end of a
subroutine and
returns
control to the most recently saved position in the indirect file (the
line immediately following the .GOSUB directive that
initiated the
subroutine).
Formc:~ t:

.RETURN

Set Symbol To True Or False

5.6.26

.SETT/.SETF

The oSETT/.SETF directives define or change the value of a specified
logical symbol.
If the symbol has not been defined, the process6r
makes an entry in the symbol table and sets the logical symbol to the
value specified.
If the symbol has already been defined,
the
processor resets the symbol accordingly.
The processor exits with a
fatal error if the logical symbol was defined previously as a numeric
or string symbol.
Formats:
.SETT

ssssss

.SETF

ssssss

where:
ssssss

= 1- to 6-character logical symbol to be

assigned

true

false value.
The 1ogical symbol ssssss must be preceded by at least one blank.
Examples:
.SETT

This directive sets the logical symbol X to true •
• SETF

ABCDE

This directive sets the logical symbol ABCDE to false.

5.6.27

Set Symbol To Numeric Value

.SETN

The .SETN directive defines or changes the numeric value of a
specified symbol.
If the symbol has not been defined, the processor
makes an entry in the symbol table and sets the symbol to the numeric
value specified.
If the symbol has already been defined,
the
processor resets the symbol accordingly.
The processor exits with a
fatal
error if the numeric symbol was previously defined as a logical
or string symbol.

5-33

INDIRECT COMMAND FILES

Format:
.SETN ssssss numexp
where:
ssssss

1- to 6-character numeric symbol.

numexp

a numeric expression.

(See Section 5.3.3.1.)

When specifying a numeric value to assign to a symbol, you may combine
a numeric symbol or constant with another numeric symbol or constant
to form a numeric expression.
If numeric expressions are used,
no
embedded blanks or tabs are permitted.
Evaluation is done from left
to right unless parentheses are used to form subexpressions that are
evaluated first.
The type of an expression is octal if all the
operands are octal;
otherwise the type is decimal.
Examples:
.SETN NUMBER 27
This directive assigns to the
(octal) •

numeric

symbol

NUMBER

the

value

This directive assigns the numeric symbol Al the value
minus 5 multiplied by 3.

symbol

• SETN Al 3*(A2-5)

5.6.28

.SETS

Set Symbol To String Value

The .SETS directive defines or changes the string value of a specified
string symbol.
If the symbol has not been defined, the processor
makes an entry in the symbol table and sets the symbol to the
specified string value.
If the symbol has been defined, the processor
resets the symbol accordingly.
The processor exits with a fatal error
if the symbol was defined previously as a logical or numeric symbol.
Format:
.SETS ssssss strexp
where:
ssssss

1- to 6-character string symbol.

strexp

any string expression.

(See Section 5.3.3.2.)

The processor assigns to the specified symbol the string value
represented by the string expression strexp.
If a string constant is
used in strexp, the constant must be enclosed by quotes ("strexp").
You can combine a string symbol, constant, or substring with another
string symbol or substring by the string concatenation operator (+) to
form a string expression.

5-34

INDIRECT COMMAND FILES
Examples:
.SETS A "ABCDEF"
This directive assigns to the string symbol A the string value ABCDEF •
• SETS STR2 "ZZZ"
This directive assigns string symbol STR2 the value ZZZ •
• SETS X STR2+"ABC"
This directive assigns string symbol X the value of symbol
ABC (that is ZZZABC) •

STR2

plus

• SETS X STR2+A[l:3]
This directive is equivalent to the previous directive;
it assigns
the string symbol X the string value of STR2 plus the first three
characters of string A (that is ZZZABC) •
• SETS MYFILE <UIC>+"MYFILE.TXT"
This directive assigns the string symbol MYFILE the string value of
the current UIC plus the string MYFILE.TXT
(for example, if the
current UIC is [303,3], string symbol MYFILE is assigned the string
valu e [303,3]MYFILE.TXT).
1

5.6.29

Terminate Command File Processing

.STOP

The .STOP directive immediately terminates command file processing and
exits.
The message
>@ <EDF>

is then displayed.
The .STOP directive allows you to optionally set the exit
AT.
execution.

status

for

Format:
.STOP [value]
where value is an optional numeric expression to serve as the exit
status for the indirect command file processor.
If you do not specify
an exit status value, the .STOP directive is identical to the logical
end of file directive (/).
Example:
.STOP 0
This directive terminates command file processing and sets
status to zero.

5-35

AT.

exit

INDIRECT COMMAND FILES
5.6.30

Test String Symbol

.TEST

The .TEST directive moves the length of a
string symbol
into the
special numeric symbol <STRLEN>.
It also tests the characters of the
string and sets the special logical symbols
<ALPHAN> and
<RAD50>
accordingly (see Section 5.3 .1).
Format:
.TEST strsym
where strsym is the string symbol to be tested.
Example:
The directive
.TEST A
moves the number of characters in string A into
<STRLEN> and sets
<ALPHAN> and <RAD50> accordingly.
The special numeric symbol <STRLEN>
is then available to compare the length of string symbol A to some
numeric constant or expression.

5.6.31

Wait For A Task To Finish Execution

The .WAIT directive suspends processing of the indirect
until a particular task has terminated.

.WAIT
command

file

Format:
.WAIT

tttttt

The task name tttttt must be preceded by at least one blank.
If the taskname
is omitted,
the
indirect process-0r assumes
the
taskname applied by
the last previous "RUN filename" MCR command.
This name is specified as
TTnn
where:
TT

the invoking terminal.

the terminal number.

If the specified (or default) task
is not
installed,
the
indirect
processor
ignores
the .WAIT directive.
The .WAIT directive performs
no function if the /NOMCR switch is in effect.
Example:
.WAIT

PIP

This directive discontinues processing of the command file
terminal-initiated task PIP exits.

5-36

until

the

INDIRECT COMMAND FILES
5.6~32

Initiate Parallel Task Execution

.XQT

The indirect file processor usually passes a command to MCR and waits
until the command's execution has completed. However, it is possible
for the processor to initiate a task and not wait for it to complete
before executing the next indirect file command. The MCR Run command
initiates tasks, and the indirect file processor can continue as soon
as the Run command is processed.
However, you cannot use the Run
command to pass a command string to the target task.
The
.XQT
directive allows you to start a task, to pass a command string to it,
and to continue processing command lines in parallel with the
initiated task.
AT.
permits up to 10(10) successive .XQT directives.
Format:
.XQT

tsk-name command-string

where:
tsk-name

the name of the
PIP, DMO).

task

(for

example,

MAC,

command-string = the command to the task.
The .XQT command provides a facility to initiate parallel processing
of
tasks.
Use the
.WAIT directive to synchronize the execution of
parallel tasks;
command file processing is suspended until the
specified task completes.
Example:
.XQT MAC TEST,TEST=TEST
.XQT TKB BLD,BLD=BLD
.WAIT MAC
.WAIT TKB
The example starts an assembly and a task build executing in
and then waits for the two tasks to complete.

5.7

parallel

TASK NAME REFERENCES

References to task names in an indirect command file follow the same
rules as for MCR.
If the task was started as an external MCR task
(for example, MAC, PIP, DMO), it may be referenced by its 3-character
name.
Thus,
the .WAIT,
.IFINS,
and .IFACT directives need only
specify the 3-character task name;
the
indirect command
file
processor can then find the correct task.
Of course, you can always
refer to a specific task by using its full 6-character name.

5-37

INDIRECT COMMAND FILES
5.8

EXAMPLE COMMAND FILE AND ITS EXECUTION
EXAMP.CMD
.ENABLE SUBSTITUTION
.ENABLE GLOBAL

·------------------------------------------------------------

• I
•

.; This procedure calculates the day of the week from the
.; date obtained from the system.
•

•

·---------------------------------------~------~------------~

• I

.; DAYS OF THE WEEK.
•

.SETS DAYS "SUN MON TUESWED THURFRI SAT SUN"
•

.; MONTHS OF THE YEAR.
• I

• SETS MONTHS "JANFEBMARAPRMAYJUNJULAUGSEPOCTNOVDEC"
•

.; NUMBERS FOR DAYS OF THE MONTH.
• I

.SETS DAYMON "01020304050607080910111213141516171819202122232425262728293031"
•

.; NUMBERS FOR THE YEARS.
• I

.SETS YEARNM "798081828384858687888990919293949596979899"
.SETS DAT "'DATE>'"
! GET TODAYS DATE •
• SETS TIM "'TIME>'"
!GET THE TIME •
• SETS DAY DAT[l:2]
EXTRACT THE DAY
.SETS MONTH DAT[4:6]
EXTRACT THE MONTH
.SETS YEAR DAT8.:9.]
EXTRACT THE YEAR
.SETN DAYN 1.
DAY OF MONTH COUNTER •
• SETN NDX 1.
DAY OF MONTH INDEX •
• DLOOP:

.10:

.SETS TEMP DAYMON[NDX:NDX+l]
.IF TEMP = DAY .GOTO 10
.INC DAYN
• SETN NDX NDX+2.
.GOTO DLOOP
.SETN MONCNT 1.
.SETN NDX 1.

SET TO DAY OF MONTH
BRANCH IF CORRECT DAY
BUMP COUNTER
POINT TO NEXT DAY
TRY NEXT DAY
INIT MONTH COUNTER
INIT MONTH INDEX

.SETS TEMP MONTHS[NDX:NDX+2.]
.IF TEMP = MONTH .GOTO 20
• INC MONCNT
• SETN NDX NDX+3.
.GOTO MLOOP
.SETN YEARN 79 •
• SETN NDX 1.

SET TEMP TO MONTH
BR IF CORRECT MONTH
BUMP MONTH COUNTER
POINT AT NEXT MONTH
TRY NEXT MONTH
INIT YEAR COUNTER •
INITIALIZE YEAR INDEX •

.SETS TEMP YEARNM[NDX:NDX+l]
.IF TEMP = YEAR .GOTO 30
• INC YEARN
• SETN NDX NDX+2.
.GOTO YLOOP

SET TEMP TO MONTH
BRANCH IF CORRECT YEAR
BUMP YEAR COUNTER
POINT AT NEXT YEAR
TRY NEXT YEAR

• MLOOP:

• 20:
• YLOOP:

• I
• I
• I

.30:
•

• SETN Tl MONCNT+lO •
.SETN T2 Tl/13.
• SETN T3 (13*(Tl-(T2*12.}}-l.}/5 •

5-38

INDIRECT COMMAND FILES

•

.SETN T3 (Tl-(T2*12.))
.SETN T3 ( (13.*T3)-l)/5 •
• SETN T3 T3+DAYN+77 •
• SETN T4 YEARN+((MONCNT-14.)/12.)
.SETN T4 YEARN
.IF MONCNT < 3 .DEC T4
.SETN TS T4/100 •
• SETN T6 T4/400 •
• SETN T7 (5.*(T4-(T5*100.)))/4.
.SETN T7 (T4-(T5*100.))
.SETN T7 (5.*T7)/4 •
• SETN T8 T3+T7+T6-T5-T5+1 •
• SETN DAYNDX T8-((T8/7.)*7.)
.SETN DAYNDX (DAYNDX*4.)+l.
.SETS $DAY DAYS[DAYNDX:DAYNDX+3.]

• I

The date is - 'DAT',
The time is - 'TIM', and
Today is '$DAY'DAY.
See you tomorrow.
COMMAND FILE EXECUTION

> @E>(AMP
>;
>;

EXAMP.CMD

>;
>;

>; The date is - 17-APR-781
); The time is - 13:25:371 and
>; Today is TUESDAY.

); See You tomorrow.

>;
>@

<EDF>

5-39

DAY INDEX (SUNDAY = 0)
INDEX INTO DAYS LIST
GET DAY OF THE WEEK

APPENDIX A
MCR AND TKTN MESSAGES

Messages from MCR and TKTN appear
in this chapter in alphabetical
order.
Some messages
include
remedial action to be taken by the
operator. This is not included with messages for which the required
action is obvious or contained in the description of the message.
11 40 F.P. EXCEPTION

Explanation:

This is a TKTN message.
The task encountered a
floating point exception while executing on a PDP-11/40, and no
SST routine was specified to handle the trap.
ABORTED BY DIRECTIVE OR MCR

Explanation:

Either MCR or an Executive directive
another task caused the task to be aborted.

issued

ABORTED VIA MCR

Explanation:

MCR aborted the task and

requested

post-mortem

dump.
XXX -- ACCESS TO COMMON BLOCK DENIED

Explanation:

Common block protection requirements were not met.

XXX -- ACCOUNT FILE OPEN FAILURE

Explanation:

The account file was open for another user;
disk containing the account file was not mounted.

Uset Action:

or the

Retry command.

XXX -- ACCOUNT FILE RECORD(S)

LOCKED

Explanation: The account file or a specific record
Retry the command.

was

locked.

XXX -- ACP NOT IN SYSTEM

Explanation:

The specified Ancillary Control Processor
installed in the system.

was

not

XXX -- ADDRESSING EXTENSIONS NOT SUPPORTED

Explanation:
(virtual
feature.

The command tried to install a task with a VSECT
section)
into a system that does not support the

A-1

MCR 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 -- ALREADY MARKED FOR DISMOUNT

Explanation:

The device-unit has already been requested for
dismount and the associated ACP was waiting for all accesses to
the volume to complete.

XXX -- ALREADY MOUNTED

Explanation:

The specified network device was already mounted.

XXX -- AMBIGUOUS QUALIFIER

Explanation:

The qualifier does not specify a unique part of the

Help file.

User Action:

Further information must be supplied.

XXX -- AMBIGUOUS SYNONYM

Explanation: A qualifier
ambiguous shared entry.

the

Help

file

references

XXX -- ASSIGN FAILURE
Explanation:
assignments.
AST ABORT.

BAD STACK

Explanation:
because
stack.

The Hello command could not complete login logical
For example, the MCR dispatcher is not installed.

the

This is a TKTN message.
AST parameters cannot

An AST cannot be effected
be pushed onto the task's

XXX -- BAD BLOCK FILE CORRUPT - DATA IGNORED

Explanation:

The bad block file contained bad data.

XXX -- BAD BLOCK FILE FULL

Explanation:

The disk had more then 102 bad regions on it.

XXX -- BAD BLOCK HEADER I/O ERROR

Explanation:

A write error was detected in writing the bad-block

file header.
XXX -- BAD COMMAND OR SYNTAX

Explanation:

The directive was unknown
directive was incorrect.

A-2

the

syntax

the

MCR AND TKTN MESSAGES

xxx -·- BAD ~rASK FI LE VBN, TASK REMOVED - task name
Explanation:
The system removed the specified task because
contained a bad Virtual Block Number (VBN) in its file header.

XXX -- BASE ADDRESS MUST BE ON 4K BOUNDARY
Explanation:
The base address of the task
is not on a
boundary.
This message is applicable only to mapped systems.

XXX -- BASE MISMATCH COMMON BLOCK <common-name>
Explanation: The base address of the common block,
as recorded
in the task image, did not match the base address of the resident
common block.

XXX --- BINARY OPERATOR ERROR
Explanation:
The .AND or .OR
was not used correctly.

indirect-file-processor

directive

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.

An error was detected in writing

the

XXX -- BOOTED DEVICE'S DRIVER NOT LOADED
Explanation: VMR has been used to
system (booted) disk.

unload

the

driver

for

the

XXX -- BOOTED DEVICE NOT IN SYSTEM -- dd nnn mmmmmm
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 DBl: •

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;
however, the address 3001 is not.

XXX -- CANNOT INSTALL PRIVILEGED TASK FROM NONPRIVILEGED 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.

A-3

MCR AND TKTN MESSAGES
XXX -- CANNOT LOAD/UNLOAD A PSEUDO DEVICE

Explanation:

The device

you

attempted

load

pseudo

device.
XXX -- CAN'T READ MCR COMMAND BUFFER

Explanation:
MCR command;

UFD was started by a Run command rather than by
therefore, the command could not be parsed.

XXX -- CHECKING ddnn:

Explanation:

Automatic bad-block specification is proceeding,
using the bad-block file produced by the Bad Block Locator
utility program.

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

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:

""
j

An error was detected in writing out the checkpoint

file header.
XXX -- CHECKPOINT FILE NOW INACTIVE

Explanation:

This message appears after an ACS command has been
issued 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 were still
in use, TKTN would issue a message when the file was finally
discontinued.

*** ddnn:

-- CHECKPOINT FILE NOW INACTIVE

Explanation:

The 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
tasks
checkpointed to the discontinued file back into memory caused the
delay between the request and this message.

XXX -- CHECKPOINT FILE STILL ACTIVE

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.

A-4

!·----------------------------------------------------------------------------------------------------------

MCR AND TKTN MESSAGES
XXX -- CHECKPOINT FILE STILL IN USE ON dev:

Explanation:

The system cannot be saved because
file on the specified device is still active.

User

Action: Deallocate the checkpoint
command) and reissue the Save command.

file

a
(see

checkpoint
the

ACS

XXX -- CHECKPOINT SPACE TOO SMALL, USING CHECKPOINT FILE

Explanation:

A warning message. 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 rolled-out task.

*** ddnn:

CHECKPOINT WRITE ERROR

Explanation:

This is a TKTN message.
A write failure
while the system was attempting to checkpoint a task.

occurred

XXX -- CIRCULAR REDIRECT ERROR

Explanation: An attempt was made to redirect a device,
would have caused a circular list of redirects to result.
XXX -- CO:

which

REDIRECTED TO CO:

Explanation:

The console output driver is active.

User Action:

If it is not active,
use the Open command
to the terminal from which you are running.

redirect CO:

XXX -- COMMAND INPUT ERROR

Explanation:

Circumstances prevented the BROADCAST task
from
receiving the command line (usually an indirect file could not be
found);
or, a system directive or the Run command,
rather
than
the Hello command, has initiated the HELLO task.

User Action:

In the case of BROADCAST, retry the command.

XXX -- COMMAND I/O ERROR

Explanation:

An I/O error was generated during a
read to an
indirect
file, or an attempt by another task to obtain a command
from MCR failed.

XXX -- COMMAND SYNTAX ERROR

Explanation:

The command line had an improper format.

XXX -- COMMAND TOO LONG

Explanation:

An INITVOL or Mount command, including continuation
lines, exceeded the maximum length of 512.
characters.

XXX -- COMMON BLOCK IS TASK PARTITION common-name

Explanation:

A task's request for access to a common block was
rejected because the requested partition was a task partition.

A-5

MCR AND TKTN MESSAGES

xxx -- COMMON BLOCK NOT LOADED common-name
Explanation:
The specified common block was linked to
but had not been loaded into the system.
User Action:
the task.

Install the specified common

block,

the

then

task

install

XXX -- COMMON BLOCK OCCUPIED
Explanation:
An attempt was made to load a common block that was
already occupied.
XXX -- COMMON BLOCK PARAMETER MISMATCH common-name
Explanation: Parameters (partition name and PIC attributes) of a
common block did not match those in the task's label block.
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 common-name NOT INSTALLED FROM AN LB:
Explanation:
An RSX-llM-PLUS
message.
commons must be installed from an LB:.
User Action:

All

checkpointable

Remove the common and retry the Save command.

XXX -- COMMON, DRIVER OR TASK ABOVE SYSTEM IMAGE FILE LIMIT
Explanation:
A system cannot be saved
structure
is higher than the amount
written to the system image file.

if
of

a memory
resident
ma in memory that is

User Action:
Use the Partitions command to determine
of the problem.

the

cause

XXX -- COMMON NOT IN SYSTEM
Explanation:
The specified or required common does not exist
the current system.

XXX -- CONTINUING
Explanation:
This is not an error message.
This
message
indicates that the indirect file processor is resuming execution
after a .PAUSE or .DELAY directive.
XXX -- CTB name DOES NOT EXIST
Explanation:
The controller table name specified with
keyword does not exist in the resident database.

the

/CTB

XXX -- CTB NAME name IS A DUPLICATE
Explanation: The loadable database contains a Controller Table
(CTB) with a name that is the same as a CTB name in the resident
database.
CTB names must be unique.

A-6

MCR AND TKTN MESSAGES

xxx -- CTB name IS NOT SUPPORTED BY DRIVER-NOT LOADED
Explanation: The device driver's dispatch table does not have
all the Controller Table mnemonics that the rest of the database
(the DCBs and CTBs) implies it to have or the CTB is defective.
A defective CTB may contain a wrong name, or its linkage to the
DCB may be wrong.
XXX -- DCB TABLE FOR CTB name IS FULL

Explanation: Load attempted to write the address of your Device
Control Block (DCB) for the loadable database into the DCB table
of the Controller Table. There were no null entries in the DCB
table.
(Refer to the RSX-llM or RSX-llM-PLUS Guide to Writing an
I /0 Driver. )
XXX -- DATA ERROR

Explanation:

The specified bad-block
contiguous region size is too large.

User Action:

number

the

specified

Reenter properly.

XXX -- DATA FILE ERROR x.

Explanation:

The MCR indirect command file processor encountered
an error while processing an .OPEN, .CLOSE, .DATA directive or a
data mode access to the secondary file.
See Appendix I
in the
IAS/RSX-11 I/O Operations Reference Manual for a definition of
the numeric code x.

XXX -- DELAY ING

Explanation:

This is not an error message;
it indicates that a
.DELAY directive has
just been executed by the indirect file
processor.

XXX -- DEVICE ATTACHED

Explanation:

The specified device was currently attached by a
task and could not be mounted;
or the specified device cannot be
allocated because it is attached to a running task.

XXX -- DEVICE ATTACHED[-dev:]

Explanation:

The device-unit specified in the command
was
attached by a
task and could not be mounted.
For attempts to
mount one or more magnetic tapes, the message includes a specific
device-unit.

XXX -- DEVICE ddn:

HAS UNITS ATTACHED, BUSY, AND/OR MOUNTED

Explanation:

Device ddn:
is the first or only
attached,
mounted,
and/or has outstanding I/O.
driver cannot be unloaded.

unit that
is
Therefore, the

XXX -- DEVICE NOT ALLOCATED TO THIS TERMINAL

Explanation: The command line specified a private
was allocated to other than the issuing terminal.

device

that

XXX -- DEVICE NOT DEFINED IN NETWORK

Explanation:

The specified device had not been defined
network topology and therefore could not be mounted.
A-7

the

MCR AND TKTN MESSAGES
XXX -- DEVICE NOT IN SYSTEM

Explanation:

The device specified
in the command was
not
generated into the system.
Devices to be used in the system must
be specified during system generation.

XXX -- DEVICE NOT IN SYSTEM -dev:

Explanation:

The Mount command specified a tape drive
not been generated into the system.

XXX -- DEVICE ddn:

that

has

NOT IN SYSTEM

Explanation:

The data base for the device driver was neither
in
the system nor in the driver's task image;
or specified device
driver does not exist in the system.

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 (SY:) was not mounted.

XXX -- DEVICE NOT REDIRECTABLE

Explanation:

The specified device may not be redirected.

XXX -- DEVICE NOT READY - ddnn:

Explanation:

The command specified a volume that was
(not up to speed).

not

ready

XXX -- DEVICE NOT TERMINAL

Explanation:

An attempt was made to set terminal characteristics
for a non-terminal device.

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.

XXX -- DEVICE OFFLINE[-dev:]

Explanation:

The device specified in the command,
although
generated into the system, was not physically present in the host
configuration.
If the offline device is a magnetic tape drive,
the message includes the device-unit.

XXX -- DEVICE SPECIFIED TWICE -- dev:

Explanation:

The Mount command specified

the

same

device-unit

twice.

xxx -- DEVICE WRITE LOCKED - ddnn:
Explanation:

The

command

specified

volume

that

was

write-locked.
XXX -- DIRECTIVE PARTITION UNFIXED OR NONEXISTENT

Explanation:

VMR has been used to make the contents
directive partition disappear.
Use VMR to restore it.

A-8

the

MCR AND TKTN MESSAGES
XXX -- DIRECTORY ALREADY EXISTS

Explanation:

The requested UFD already exists on the volume.

XXX -- DISK IS ALIGNMENT CARTRIDGE

Explanation:

The last track on an RK06 disk
identified the
volume as an alignment cartridge, which cannot be initialized as
a Files-11 volume.
An alignment cartridge is specifically
formatted for aligning disk read/write heads.

***

ddnn:

DISMOUNT COMPLETE

Explanation:

indicates
This is a TKTN message.
This message
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 DPB was created by MCR.
that the system itself has faulted.

This error indicates

User Action: If the error
persists,
Performance Report (SPR) to DIGITAL.

submit

Software

XXX -- DRIVE 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 ALREADY RESIDENT

Explanation:

The

specified

device

driver

had

already

been

loaded.
XXX -- DRIVER BEING LOADED OR UNLOADED

Explanation:

The Executive was effecting another request to load

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
permanently resident device driver
the Executive).

attempted
to
remove
a
(that is, a driver linked to

XXX -- DRIVER DISPATCH TABLE IS INCONSISTENT

Explanation:
formatted.

The device driver's dispatch table is illegally
Refer to the RSX-llM-PLUS Guide to Writing an I/O

Drive~.

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.

A-9

MCR AND TKTN MESSAGES
XXX -- DRIVER NOT LOADED

Explanation: The device driver specified in the Unload command
was not resident in memory;
or the 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.

bad

was

being

XXX -- DYNAMIC ALLOCATION OF CHECKPOINT SPACE NOT SUPPORTED

Explanation:

The ACS command was issued on a system that did not
include support of dynamic allocation of checkpoint space at
system generation.

XXX -- ERROR LOGGING STILL ACTIVE

Explanation:
active.

A system cannot be saved while error
Run the task ERF to disable error logging.

logging

XXX -- FAILED TO ATTACH DEVICE - ddnn:

Explanation:

The specified device could not be attached.

XXX -- FAILED TO CREATE A DIRECTORY

Explanation:

No space existed on the volume,

I/O

error

No space existed in the Master File Directory
or on the vblume, or an I/O error occurred on the volume.

(MFD)

occurred.
XXX -- FAILED TO ENTER IN MFD

Explanation:

XXX -- FAILED TO READ BAD BLOCK FILE

Explanation:

The INITVOL command was unable to read
block information from the last track of an RK06 disk.

the

bad

XXX -- FATAL I/O ERROR

Explanation:

An input or output operation could not be completed
because of the unavailability of a device or dynamic memory, or a
device error occurred.

XXX -- FEATURE NOT SUPPORTED

Explanation:

The command keywor.d specifies an optional feature
that was not incorporated into the system at system generation.

XXX -- FILE name CONTAINS INVALID DRIVER DATA BASE

Explanation:

The driver had an invalid data base.

XXX -- FILE name HAS ILLEGAL STB FORMAT

Explanation:

The driver's STB file contained illegal object code

or data.

A-10

MCR AND TKTN MESSAGES

xxx -- filename FILE HEADER I/O ERROR
Explanation:

An error was detected
header for the specified system file.

writing

out

the

file

Explanation:

Mount could not read either the index file
storage allocation file.

the

User Action:

error,

XXX -- FILE HEADER READ ERROR

Determine the problem;
if it is a hardware
contact the local Field Service office.

XXX -- 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 Appendix I
of the IAS/RSX-11 I/O Operations Reference Manual.

XXX -- FILE filename HAS INCONSISTENT DRIVER LOAD INFORMATION

Explanation:

The partition for
loadable
beyond the end of the system image file.

drivers

logically

XXX -- FILE name NOT A VALID DRIVER TASK IMAGE

Explanation:

The driver's task image was either overlaid or

had

a task header.
XXX

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 name NOT CONTIGUOUS

Explanation: The file specified was not
must be contiguous.

The

file

The requested file was not in the directory on
specified volume.

the

contiguous.

XXX -- FILE NOT FOUND

Explanation:

XXX -- FILE NOT IN USE

Explanation:

A checkpoint file was not
specified in the ACS command.

use

the

device

XXX -- FIL.E NOT TASK IMAGE

Explanation:

Data in the label block was not correct,
that the file was not a valid task image.

indicating

XXX -- FILE READ ERROR

Explanation:
This error
bytes long.

An error was detected in reading an indirect
file.
is usually caused by records that are more then 80.

A-11

MCR AND TKTN MESSAGES
XXX -- HOME BLOCK ALLOCATE WRITE ERROR

Explanation:

A write error occurred
overwriting a bad home block area.

while

the

was

system

XXX -- HOME BLOCK CHECKSUM ERROR

Explanation:

The checksum in the home block and the calculated
checksum did not agree.
This condition was probably caused by an
I/O error.

XXX -- HOME BLOCK I/O ERROR

Explanation:

An error was detected in
volume home block.

reading

writing

the

XXX -- HOME BLOCK READ ERROR

Explanation: An error was detected in reading the home block.
This error usually indicates that the volume is not ready in the
drive.
Wait until it is ready and reissue the command.
XXX -- HOME BLOCK WRITE ERROR

Explanation:

A write error was detected in

writing

the

volume

home block.

There was an
r online ..
or the IIST
XXX

ILLEGAL DEVICE ddnn:

Explanation: The device specified at task-build time by the
Assign command keyword option
(Devices)
did not exist in the
system.
XXX -- ILLEGAL DEVICE SPECIFIED

Explanation:

Specified device was not a terminal.

XXX -- ILLEGAL DEVICE/VOLUME

Explanation:

The specified device was not a valid task-residence

device.
XXX -- ILLEGAL DRIVER TASK APR USAGE

Explanation:

A device driver must be built for APR 5 and must be
less than 4K
(e.g., PAR=DRVPAR:l20000:20000).
This message
applies to mapped systems only.

A-12

MCR AND TKTN MESSAGES
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 SK.
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 Task Builder Manual for a
description of the /PR keyword.) This message applies only to
mapped systems.

XXX -- ILLEGAL FUNCTION

Explanation:

A command was entered that MCR could not recognize.

XXX -- ILLEGAL KEYWORD COMBINATION

Explanation:

The command specified conflicting keywords.

XXX -- ILLEGAL KEYWORD VALUE
'~

Explanation:

A value entered for a keyword exceeded its limits.

User Action:

Enter a legal value.

XXX -- ILLEGAL PRIORITY

Explanation:
range

The value of the priority in the command was out of
(that is, not 1 to 250(10), inclusive).

XXX -- ILLEGAL UIC

Explanation:

The command line specified an illegal UIC.

XXX -- ILLEGAL VALUE FOR SYMBOL symname IN FILE name

Explanation:

The symbol symname is defined to an illegal value
by 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 then $ddEND;
mapped loadable drivers cannot reference $INTSV.
XXX -- IMPROPER HELP FILE FORMAT

Explanation:
used.

The Help file is not in proper format and cannot be
Either edit the file or re-enter it in proper format.

XXX -- INDEX FILE BIT MAP I/O ERROR

Explanation:

An error was detected in writing out the index file

bit map.
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.

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.
A-13

MCR AND TKTN MESSAGES
XXX -- INDEX FILE I/O ERROR

Explanation:

An I/O
index-file header.

error

was

detected

writing

out

the

Open

XXX -- INPUT I/O ERROR

Explanation:

In attempting to read the next
command detected an error.

command,

XXX -- INSUFFICIENT ICB POOL SPACE FOR CPU CPx

Explanation:

There is not enough pool
space to allocate an
Interrupt Control Block
for
the CPU designated in the error
message.
This message applies only to Multiprocessor,
I
and D
space systems.

XXX -- INSUFFICIENT POOL SPACE

Explanation:

The

required

amount

pool

space

was

not

available.
XXX -- INTERRUPT VECTOR ALREADY IN USE
A loadable device driv~r interrupt does not point
to one of the nonsense
interrupt entries.
This message can
appear when a user issues the Load command.

Explanation:

XXX -- INVALID ACCOUNT

Explanation:

The name or UIC specified in the command
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
in the Open
command referenced a
nonexistent memory location or an address
outside the boundaries of the specified partition.

XXX -- INVALID ANSWER

Explanation:

In response to a question from the
indirect file
processor directive
.ASK, the operator entered a response other
than Y, N, or null, followed by carriage return.
The processor
will repeat the question.

XXX -- INVALID DRIVER DATA BASE AT OFFSET xxxx IN FILE name

Explanation:

The driver had an invalid data base value at offset
xxxx relative to the symbol $ddDAT.

XXX -- INVALID KEYWORD

Explanation:

A keyword was encountered that was
by the specific command processor.

not

recognized

XXX -- INVALID INTERRUPT VECTOR

Explanation:

The
interrupt vector
driver data base was too high.

A-14

address

specified

the

___________________________________________________

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.

that

XXX -- INVALID SPEED
Explanation:
The multiplexer line specified does not support the
requested speed;
or the command specified unequal receive and
transmit speeds for a DZll. The DZll does not support split
speeds.

XXX -- INVALID TIME PARAMETER
Explanation:

A time field was incorrect.

XXX -- INVALID UIC
Explanation: A value of zero was detected for either
number or the member number.

the

group

IOT EXECUTION
Explanation:
This is a TKTN message. The subject task executed
an IOT instruction, and no SST routine was specified to process
the trap.

xxx -- I/O ERROR SIZING DEVICE - ddnn:
Explanation:
RFll disk.

The system encountered an I/O error while sizing an

XXX -- I/O OUTSTANDING
Explanation:
Tasks that have I/O requests waiting to complete
remain in the system.
A system cannot be saved with I/O requests
outstanding.
User Action:
the command.

Wait for the I/O requests to complete

and

reenter

xxx -- KRB name NOT IN LOADABLE DATA BASE
Explanation:
You are attempting to load the driver for a MASSBUS
device with a loadable data base. The special symbol (KRBname)
which defines the location of the KRB
is not defined in the
loadable data base.
Refer to RSX-llM-PLUS Guide to Writing an
I/O Driver •

'-"'

A-15

MCR AND TKTN MESSAGES
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.

XXX -- LABEL BLOCK READ ERROR

Explanation:

The Boot command could not read the label block
the system image.

XXX -- LENGTH MISMATCH COMMON BLOCK <common-name>

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 DZll

Explanation: The command attempted to set to remote a line
was not attached to a DZll multiplexer.

that

XXX -- LISTING DEVICE NOT AVAILABLE

Explanation: The device-unit on which MCR was attempting
display information was attached and unavailable for use.

XXX -- LOAD DEVICE NOT LB:, TASK REMOVED - taskname

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.
The requested
not be loaded because of a hardware error.

task

could

XXX -- LOADABLE DRIVER SUPPORT NOT IN SYSTEM

Explanation: The system generation option
device drivers was not chosen.

support

loadable

XXX -- LOGICAL DEVICE NOT IN SYSTEM

Explanation:

The specified logical device was not defined in the
logical device tables.

XXX -- 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 onto
a terminal at that time.

XXX

LUN OUT OF RANGE

Explanation:

An attempt was made to reassign a LUN that had a
value greater than the maximum number of LUNs allocated for the
task at task build.

A-16

MCR AND TKTN MESSAGES
XXX --

MAG~rAPE

LABEL MUST BE SPECIFIED

Explanation:

An INITVOL command attempted to
initialize
magnetic tape without specifying the required volume label.

xxx -- MAG~rAPE DEVICE ERROR - ddnn:
Explanation:

While
positioning
a
magnetic
tape
initializing it, the system encountered an I/O error.

before

xxx -- MAG~rAPE WRITE ERROR - ddnn:
Explanation:

While writing to
the
magnetic
tape
initialization, the system encountered an I/O error.

during

XXX -- MAXIMUM INDIRECT FILES EXCEEDED

Explanation: An attempt was made to access an indirect file at a
depth greater than four levels.
MCR indirect files may nest to a
maximum depth of four levels.
XXX -- MCR IS NOT INSTALLED

Explanation:
system disk.

When a system is booted, Save uses MCR to mount the
MCR •••
must be installed using VMR.

MEMORY PARITY ERROR IN PARTITION pname

Explanation:

This
is a TKTN message.
The error
logging
subsystem detected a memory parity error
in the specified
partition.
TKTN prints this message as notification of such.

MEMORY PROTECT VIOLATION

Explanation:

This is a TKTN message.
The
task encountered a
memory protect violation,
and no SST routine was specified to
process the trap.

XXX -- MESSAGE FILE ERROR nnn.

Explanation:

The system could not open the file LOGIN.TXT for
a
reason
indicated by
the FCS code nnn.
See Appendix I of the
IAS/RSX-11 I/O Operations Reference Manual for
a definition of
the FCS code.

XXX -- MFD FILE HEADER I/O ERROR

Explanation:
File Directory

An error was detected in
(MFD).

writing

out

the

Master

writing

out

the

master

XXX -- MFD WRITE ERROR

Explanation:

An error was detected in
file directory.

MICRO CODE LOADER NOT INSTALLED

Explanation:

For systems that include the KMCll line printer
driver
(LKDRV),
this message indicates that the task LPINIT is
not installed in the system.

A-17

MCR AND TKTN MESSAGES
XXX -- MOUNT ERROR FROM ACP - xxx.

Explanation:

The ACP detected an error while trying to mount the
volume set.
See the IAS/RSX-11 I/O Operations Reference Manual
for a definition of standard FCS error codes.

XXX -- MULTI-UNIT DEVICE NOT TAPE

Explanation:

The command specified multiple units that

are

not

tape drives.
XXX -- MUST BE RUN FROM TERMINAL CO:

Explanation:

Save is not being run from the terminal to which
the pseudo device CO:
is directed.
This is not a requirement on
an RSX-llM-PLUS system, therefore, the message does not apply.

XXX -- NEW DEVICE NOT KNOWN TO SYSTEM

Explanation:
known to
tables).

the

The new device in the Redirect command was not
system
(that is, it does not exist in the device

XXX -- NO BAD BLOCK DATA FOUND

Explanation:

Although automatic bad-block specification
selected,
no bad-block file could be found on the volume.
is a warning message.

was
This

XXX -- NO CHECKPOINT SPACE, ASSUMING NOT CHECKPOINTABLE

Explanation:

This is a warning message.
The command installed a
task that was designated checkpointable at task build, but that
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 not to be c6eckpointable.

XXX -- NO LUNS

Explanation:

A LUN command specified a task that had no
LUN assignments.

current

XXX -- NO POOL SPACE

Explanation:

The Executive could
request for dynamic memory.

not

currently

satisfy

MCR's

XXX -- NO ROOM AVAILABLE IN STD FOR NEW TASK

Explanation: No dynamic storage was available
entry
in the System Task Directory
(STD);
specified task could not be installed.

for making an
the ref ore,
the

XXX -- NO TRANSFER ADDRESS

Explanation:

The Boot command could not find a transfer
in a virgin system image (result of task build).

address

XXX -- NO VOLUME LIST

Explanation: The command specified a magnetic
which a mounted volume list does not exist.

A-18

tape

drive

for
.~.

MCR AND TKTN MESSAGES
XXX -- NON EXISTENT MEMORY

Explanation:

An attempt
nonexistent memory.

was

made

define

partition

NON HSX EMT EXECUTION

Explanation:

This is a TKTN message. The task executed an EMT
instruction having an argument other than 377(8), and no SST
routine was specified to process the trap.

XXX ·-- NOT ENOUGH APRS FOR TASK IMAGE

Explanation:

The Task Builder allows the user to specify the
virtual base address of a
task
image as a multiple of 4K.
Privileged tasks start at virtual 100000(8) to map the first 16K
of the Executive,
or virtual 120000(8) to map the first 20K of
the Executive, at the same time as the user task.
If the virtual
base address
is set too high, the task image may not be able to
be mapped with the remaining mapping registers. This message
is
applicable to mapped systems only.

XXX -- NOT FILE STRUCTURED DEVICE

Explanation:

The
specified device.

system

does

not

support

Files-11

the

XXX -- NOT FILES-11 DEVICES

Explanation:

The command specified a device that did not contain
a Files-11 disk.
The specified device-unit must contain a
mounted Files-11 disk.

XXX -- NOT MOUNTABLE DEVICE

Explanation:

The
device

Files-11
device.

specified
(including

a
device was not supported as
or a network
ANSI magnetic tape)

XXX -- NOT MOUNTED

Explanation:

***

dnn:

The specified device was not mounted.

NOT READY

Explanation:

This is a TKTN message.

The specified

device

was

not ready.
XXX -- NOT SYSTEM IMAGE

Explanation:

The Boot command determined that the file was not a

system image.
XXX -- NOT VALID SAVE DEVICE

Explanation:

The device specified in the Save command was not
valid.
The Save command can specify only random access devices
in Files-11 format.

XXX -- NT DEVICE NOT MOUNTED

Explanation:

The device NT:
was not mounted.
be mounted before any other network devices.

A-19

This device

must

MCR AND TKTN MESSAGES
XXX -- NULL FILE HEADER I/O ERROR

Explanation:

An error was
headers to the index file.

detected

writing

out

null-file

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:

attempt

attached

was

made

redirect

was

made

redirect

mounted

made

redirect

unknown

device-unit.

xxx -- OLD DEVICE MOUNTED
Explanation:

attempt

device-unit.

xxx -- OLD DEVICE NOT KNOWN TO SYSTEM
Explanation:

attempt

was

device-unit.
XXX -- OPEN FILE(S) ON ddnn:

Explanation: There are open files on
queue manager is stopped.

ddnn:.

Insure

that

the

XXX -- OTHER USER LOGGED ON

Explanation:
another user.
terminal.

The

issuing
Only one

terminal
user at

was currently logged
by
a time can be logged onto a

XXX -- OTHER VOLUME MOUNTED[-dev:]

Explanation:

An attempt was made to mount a volume on a
device
that already had a mounted volume.
The message specifies the
device-unit if it is a tape drive.
XXX -- OUTPUT ERROR

Explanation:

An MCR terminal-write operation failed.

XXX -- OVERLAP SEEKS NOT SUPPORTED

Explanation:

The command attempted to enable overlapped
support for other than a DM, DP, or RH device controller.

seek

XXX -- PARAMETER CONFLICTS WITH MOUNTED VOLUME

Explanation:

An attempt was made to mount a mounted volume with
keyword parameters that conflict with those values specified when
the volume was initially mounted.

PARITY ERROR

Explanation:

This is a TKTN message.
A parity error occurred
during task execution.
The task is fixed in memory so that the
memory cannot be reused for another task.

A-20

MCR AND TKTN MESSAGES
XXX -- PARTITION ALREADY EXISTS

Explanation:

An attempt was made to define a
name already in use.

partition

with

XXX -- PARTITION BUSY

Explanation:

The partition in which a task was to be fixed was
occupied by a running task;
thus, the requesting task could not
be fixed in that partition.

XXX -- PARTITION parname BUSY

:Explanation: The user-controlled partition or subpartition into
which
the driver was to be loaded was already occupied, or there
was not enough room in a system-controlled partition.
(The Load
command does not initiate checkpointing.)
XXX -- PARTITION parname IS A COMMON

Explanation:

An attempt was made to load a device driver into a
common partition.
A device driver cannot be loaded into a common
partition.

XXX -- PARTITION parname IS NOT A COMMON

Explanation:

A partition specified for
a common
library was not defined as a common partition.

resident

XXX -- PARTITION NOT IN SYSTEM

Explanation:

The partition name specified as an argument
in a
command, or during task build, could not be found in the system.

xxx -- PARTITION OR REGION name NOT IN SYSTEM
Explanation:

An attempt was made
to
load a
driver
into a
partition that does not exist
in the system, or Load found a
symbol $xxCOM in the driver and partition xxCOM does not exist in
the system.
XXX -- PARTITION parname NOT IN SYSTEM

Explanation:

The partition specified either in the Load
or at task build was not in the system.

command

XXX -- PARTITION par NOT IN SYSTEM, DEFAULTING TO GEN

Explanation:

This is a warning message.
The specified partition
does not exist;
the system therefore attempts to install the
task in the GEN partition.

xxx -- PARTITION parname NOT IN SYSTEM, TASK REMOVED - taskname
Explanation~

This is an RSX-llM error message.
If a
task
is
installed in more than one system, the partition control block
addresses in its header mapping windows may not be for the booted
system.
The task's label block indicates that the task maps to
parname, but parname is not in the current system.
The
label
block has probably been corrupted.

A-21

MCR AND TKTN MESSAGES
XXX -- PARTITION parname TOO SMALL

Explanation:

The partition into which the
loaded was not large enough to contain it.

driver

was

XXX -- PARTITION TOO SMALL TO BUFFER INFORMATION

Explanation:

The specified listing command resulted in excessive
output to the buffer.
The information in excess of the buffer
size is not displayed.

XXX -- PAUSING.

TO CONTINUE TYPE "RES tttttt"

Explanation:

This is not an error message.
processor just executed a .PAUSE directive.

The

indirect

file

PMD NOT POSSIBLE

Explanation:

This is a TKTN message.
A post-mortem dump was
requested
(or the task was built specifying a PMD), but the dump
could not be generated.
For example,
the PMD task was not
installed,
the PMD task and the aborted task were in the same
partition and not checkpointable, or there was not enough memory
available.

PMD WILL BE GENERATED

Explanation:

This is a TKTN message that
indicates
post-mortem dump was requested and will be generated.

that

XXX -- PRIVILEGED COMMAND

Explanation:

A command that was available only to
terminals was issued from a nonprivileged terminal.

privileged

XXX -- PRIVILEGED TASK LARGER THAN 12K

Explanation:

A privileged task was larger than 12K.
Privileged
tasks on an unmapped system have a maximum size of 12K.
~PROCESSOR

x rs ONLINE

.:.: _:. i .:" .: .:·. _:. ::·:.: : ::·:: . . :· .': ::·: ·~

RSX-llM-PLUS multiproces~qr· sysE~Jl\,
all
C>ne must be off line before yoµ can. boot a new·
-~

PROCESSOR

x IS NOT STOPPED

A multiprocessor system caG be saved :Only· ·if on~
proc.essor is active.
CPU x is ac1;ive
in additfoI'l. to. the
· pr0ces$or on which Save is running,.
Use CON to pl~¢e: piocesS,ot x

Explanation:

.~ :.f ::~:: Ra~:N:::::E::e~ :~:Rc:::::d:RE NOT 0FFL IN&..
EltplanaH on:

When a system i s sa vad , a 11

.• ;

ii;'1 j; .

d~vi C!a ,infts '1 Xd;a:~1·@W l

controllers except the TI: of Save and the load device must .. be·
offline.
Use the MC.R Devices or the CON Display .co1Ttrnarid t:o
deterrniJ'le .• which devices a re on line and theri issue .a CON• qfflJ.rif ·
ALL command.

A-22

MCR AND TKTN MESSAGES
XXX -- PSEUDO DEVICE ASSIGNMENT ERROR

Explanation:

An attempt was made to assign a logical device name
to a pseudo device.

XXX -- PSEUDO DEVICE ERROR

Explanation:

The specified device is a pseudo
devices cannot be allocated or made public.

device.

Pseudo

XXX -- PSEUDO DEVICE REDIRECT ERROR

Explanation: An attempt was made to redirect a pseudo device
another pseudo device.

XXX -- PUBLIC DEVICE

Explanation: The command attempted to allocate a public
Public devices cannot be allocated.

***

ddnn: READ FAILURE.

CHECK HARDWARE STATUS

Explanation:

This is a TKTN message.
detected a hardware error.

reader

driver

An indirect file for MCR contained a record
a length greater than 80.
bytesD

having

XXX ·-- RECORD LARGER THAN 8 0.

The

card

BYTES

Explanation:

xxx

device.

REDEFINING SPECIAL SYMBOL

Explanation:

An attempt was made to change the value of an
indirect file processor special symbol (a symbol bracketed with <
and >).
Special symbols may not be redefined.
XXX -- REDEFINING SYMBOL TO DIFFERENT TYPE ssssss

Explanation:

An .ASK or
the specified,
already
first definition of a
numeric,
or string);
the original type.

a .SET type directive attempted to set
defined symbol to a different type.
The
symbol determines
its type
(logical,
subsequent redefinitions must conform to

XXX -- REGION/PARTITION name IS A COMMON

Explanation:

An attempt was made to load a device driver into a
common partition. A device driver cannot be loaded into a common
partition.

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.

XXX -- RETRIEVAL POINTERS WRONG FORMAT

Explanation:

The index-file retrieval pointers were not
in
correct
format
for RSX-llM.
Refer to the IAS/RSX-11
Operations Reference Manual for details.

A-23

the
I/O

MCR AND TKTN MESSAGES
XXX -- RUNNING ABOVE SYSTEM IMAGE FILE LIMIT

Explanation: The system image file created to contain the saved
system is RSXllM.SYS. This error message appears when RSXllM.SYS
is not large enough to hold the memory in which both the system
and the Save task
run.
The Save task must be included in the
saved system image because Save is used to reboot the system.
Either run the Save task
in a partition lower in memory or
rebuild the system with a larger system image file.

***

ddnn:

SELECT ERROR

Explanation:

This is a TKTN message. The selected device
not ready, or more than one drive had the same unit number.

XXX -~·>SHADOW RECORDING IS ACTIVE ON ddnn:

~x'.~l~ria~lon:

St?tPi<fi ~d

r~pordin9.

'. •

RSX~llM-PLUs:

was

ii( ; i~/i'.'./'.

Th~:::t~r;'.~~~, <}~yifci.~)

This is an
rness(lge•
in a Dismount comma rid w~s beltig u~e<} '.
Shadow recording requires ·rnounted:,devtces~

sha~·9o/

fn"

XXX -- SPACE USED

Explanation:

An attempt was made to create a partition
subpartition in a main storage area already occupied.

XXX -- SPECIFIED PARTITION FOR COMMON BLOCK

Explanation:

An attempt was made to install a task in

common

block.
XXX -- SPECIFIED PARTITION TOO SMALL

Explanation:

The task being installed was
partition into which it was being installed.

SST ABORT.

larger

than

the

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 BIT MAP FILE I/O ERROR

Explanation:

An error was detected in writing
allocation file header.

out

the

storage

XXX -- STORAGE BIT MAP FILE READ ERROR

Explanation:

An error was encountered while attempting
the storage allocation.

read

XXX -- STRING SUBSTITUTION ERROR

Explanation:

The MCR indirect command file processor encountered
an error while performing a.substitution. A probable cause for
the error is either the omission of a second single quote or the
fact that the symbol name did not correspond to a string symbol.

XXX -- SYMBOL symname IS DOUBLY DEFINED BY FILE name

Explanation:

The symbol symname is defined

ddDRV.STB.

A-24

twice

the

file

MCR AND TKTN MESSAGES
XXX -- SYMBOL symname IS UNDEFINED BY FILE name

Explanation:

The symbol symname was found in the file ddDRV.STB,
but it was not a symbol definition.

XXX -- SYMBOL TABLE OVERFLOW ssssss

Explanation:
full;

The symbol table of the indirect file processor was
there was no space for symbol ssssss.

XXX -- SYMBOL TYPE ERROR ssssss

Explanation:

An .IF directive attempted to compare two types of
symbol;
ssssss is one of the compared symbols. Only symbols of
the same type can be compared.

XXX -- SYNTAX ERROR

Explanation:

This message generally indicates that the
information was entered incorrectly.

required

User Action:

The user can usually correct this condition by
retyping the arguments according to the command specifications.

XXX -- SYSTEM MAY NOT BOOT CORRECTLY

Explan,ation:

[system uic]SAV.TSK was not found on the boot
device.
If SAV must be checkpointed in order to redirect and
mount the booted device, the system disk will be overwritten,
causing unpredictable results.

XXX -- SYSTEM MAY NOT WORK - CORRUPTED FILE FOR COMMON comname

Explanation:

When Save attempted to convert to file ID for the
common,
Save found that the task image of the checkpointable
common was corrupted or had been deleted.
Save altered the
system data structures to prevent checkpointing of the common
into what may now be another task image.

XXX -- TASK ACTIVE

Explanation:

The task used as the argument of

the

command

was

active.
XXX -·- TASK ACTIVE IN ANOTHER SYSTEM, TASK REMOVED - taskname

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.

XXX -- TASK ALREADY FIXED

Explanation: The task used as the argument of
was fixed in memory.

the

Fix

command

XXX -- TASK AND PARTITION BASES MISMATCH

Explanation:

The base of the partition did not match that of the
task being installed.
This message is applicable only to
unmapped systems.

A-25

MCR AND TKTN MESSAGES
XXX -- TASK AND PARTITION parname BASES MISMATCH

Explanation: The base address of the partition into which the
driver was to be loaded did not match the base address of the
partition address for which the task was built.
This message
applies to unmapped systems only.
XXX -- TASK BE ING ABORTED

Explanation:

A request for the execution of a task was made, but
the task was being aborted either because of an error or because
of an MCR Abort command.

XXX -- TASK BEING FIXED

Explanation:

An attempt was made either to fix or to
priority of a task that was being fixed.

alter

the

XXX -- TASK CHECKPOINTABLE

Explanation:
memory.

An attempt was made to fix a checkpointable task in
A checkpointable task cannot be fixed in memory.

TASK EXIT WITH OUTSTANDING I/O

Explanation:

This is a TKTN message.
Tasks should terminate all
I/O operations before exiting, even though the system performs
all outstanding I/O when necessary.

XXX -- TASK FILE DELETED, TASK REMOVED - taskname

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 booted device.
This
indicates that the file has been deleted; deleted files do not
contain valid task images.

xxx -- TASK FILE HEADER ERROR, TASK REMOVED -

taskname

Explanation:

While rebooting a
saved system,
a task's
file
header could not be found and the task was therefore removed.

XXX -- TASK FILE HEADER READ ERROR, TASK REMOVED - taskname

Explanation:

The system removed the specified task because
encountered a failure while reading the task's file header.

XXX -- TASK HEADER READ ERROR

Explanation:

The system detected an I/O error while
reading in
all
task headers to store file identifications in the TCB. The
error causes the system to loop.

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.

A-26

-"'·

MCR AND TKTN MESSAGES
XXX -- TASK IMAGE I/O ERROR

Explanation:

Install could not read the task-image file,
or
Install could not rewrite the task-image header.
(The device is
write-locked.)
XXX -- TASK IMAGE I/O ERROR IN FILE filename

Explanation:
read the
header.

The device is probably write-locked. MCR could not
task-image file or could not rewrite the task image

XXX -- TASK IMAGE CURRENTLY INSTALLED

Explanation: The requested task image was already installed.
This message is applicable only to checkpointable tasks.
XXX -- TASK IMAGE VIRTUAL ADDRESS OVERLAPS COMMON BLOCK blockname

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.
and mapped to dynamic regions
in
installed in another.

Since the task
is active
one system,
it cannot be

XXX -- TASK INSTALLED IN PARTITION

Explanation:

An attempt was
containing installed tasks.

made

eliminate

partition

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.

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 ACP

Explanation:

The task specified as
characteristics of an ACP.

ACP

did

not

have

the

XXX -- TASK NOT ACTIVE

Explanation:

The specified task was not currently active.

XXX -- TASK NOT FIXED

Explanation:

An attempt was made to unfix a task that was not
fixed, or to open a memory location of a task that was not fixed.

XXX -- TASK NOT IN SYSTEM

Explanation:

The specified task had not been installed.

A-27

MCR AND TKTN MESSAGES
XXX -- TASK NOT IN SYSTEM tttttt

Explanation:

An .IFACT, .IFNACT, or .WAIT directive referred to
a task
that was not installed. These three directives can only
specify an installed task.

XXX -- TASK NOT SUSPENDED

Explanation: The task used as the argument of the Resume command
was not suspended.
XXX -- TASK taskname HAS OUTSTANDING I/O

Explanation:

A system cannot be saved if a task is
I/O to complete.

waiting

for

XXX -- TASK taskname 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;
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 taskname IS CONNECTED TO AN INTERRUPT VECTOR

Explanation:

Disconnect the task from the
abort it and retry the Save command.

interrupt

vector

XXX -- TASK taskname NOT INSTALLED FROM AN LB:

Explanation: All tasks must be installed from an LB:.
Use the
TAS command and determine which tasks are not.
Retry the Save
command after removing the tasks or installing them from an LB:.
TBIT 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

Explanation:
user.
else.

The issuing terminal has been allocated to another
user cannot log onto a terminal allocated to someone

XXX -- TERMINAL IS BUSY -- ttn:

Explanation:

The broadcast message could not be displayed within
10 seconds at the terminal specified by ttn:.

TRAP EXECUTION

Explanation:
instruction,
trap.

This is a TKTN message. The task executed a TRAP
and no SST routine was specified to process the

XXX -- TI REDIRECT ERROR

Explanation:
TI:.

An attempt was made to redirect the
This device cannot be redirected.

A-28

pseudo

device

MCR AND TKTN MESSAGES

XXX -- TOO MANY COMMON BLOCK REQUESTS

Explanation:

A task is limited to seven common block references.

XXX -- TOO MANY LUNS

Explanation:

A task attempted to assign more than 255(10)

LUNs.

XXX -- TOO MANY SUBPARTITIONS

Explanation:
~

An attempt was made to assign more than seven
subpartitions
in a user-controlled main partition.
A main
user-controlled partition
is limited to a maximum of
seven
subpartitions.

XXX -- TOO MANY SYMBOLS OF THE FORM $xxTMO IN FILE filename

Explanation:

Load is attempting to extract symbols of
the form
$xxTMO
from the drivers symbol definition file.
There are more
symbols of this form than LOAD can process.

XXX -- UNDEFINED COMMON BLOCK commonname

Explanation:

A task referenced a common block
that was not
defined
in the system.
Usually, this message indicates that the
task was built to run in another system.

XXX -- UNDEFINED DENSITY SELECTION

Explanation:

The command specified an illegal density value.

XXX -- UNDEFINED LABEL 111111

Explanation:

The label 111111 specified in
directive could not be found.

.GOTO

.ONERR

XXX -- UNDEFINED SYMBOL ssssss

Explanation:

The symbol ssssss was being tested, but it had
been defined by the indirect command file.

not

XXX -- UNIT DOES NOT SUPPORT 800 BPI

Explanation:

The command specified a drive that does not support

800 BPI.
XXX -- UNIT DOES NOT SUPPORT 1600 BPI

Explanation:

the INITVOL command specified
does not support 1600 bpi.

tape

drive

that

the

High

XXX -- UNIT DOES NOT SUPPORT HIGH/LOW DENSITY SELECTION

Explanation:

The command specified a device for which
and Low keywords are undefined.

A-29

MCR AND TKTN MESSAGES
XXX -- UNIT DOES NOT SUPPORT DENSITY SWITCH

Explanation:

The command specified
multiple density capability.

device

which

does

have

XXX -- 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 -- UNITS ATTACHED, BUSY, AND/OR MOUNTED

Explanation:

One or more device units handled by the driver are
attached,
mounted,
and/or have outstanding I/O. Therefore, the
driver cannot be unloaded.

XXX -- UNKNOWN MAIN PARTITION

Explanation:

An attempt was made to define a subpartition
nonexistent main partition.

XXX -- UNKNOWN QUALIFIER

Explanation:
printed
message.

***

ddn:

The Help file does not contain the
last qualifier
the display of the command line below the error

UNRECOVERABLE HARDWARE DEVICE ERROR

Explanation:

This
is a TKTN message.
The error
logging
subsystem recorded an unrecoverable hardware error. TKTN prints
this message as notification of such.

XXX -- USER LOGGED ON TERMINAL

Explanation:

The command attempted to allocate a terminal that
has been logged by another user.
Logged terminals cannot be
allocated.

XXX -- USER PARTITION >32K NOT PERMITTED

Explanation:

The command attempted to create a partition greater
than 32K.
Partitions greater than 32K cannot be created in
systems that do not support dynamic memory allocation,
a system
generation option.

XXX -- VOLUME MOUNTED FILES-11

Explanation:

An attempt was
Files-11
volume.
Mounted
initialized.

made
to
Files-11

initialize a
volumes
can

mounted
not be

A-30

...........................................................................................................................................................

MCR AND TKTN MESSAGES
XXX -- VOLUME MOUNTED FOREIGN WITH ACP

Explanation:

The command line specified a device that was
mounted foreign,
but with an ACP. To initialize a volume in
RSX-llM-PLUS, you cannot include an ACP name when the volume
is
mounted as foreign.

XXX -- VOLUME NAME TOO LONG -

(volume name)

Explanation:

The command line
exceeded six characters for
characters for disk devices.

specified a
volume label that
magnetic tape devices or twelve

XXX -- VOLUME NOT MOUNTED

Explanation:

An attempt was made to create a UFO on a
volume
that was not mounted.
A volume on which a UFO is to be created
must be mounted.

XXX -- VOLUME NOT MOUNTED BY TI:

Explanation:

The command specified a dismount operation
volume that was not mounted from the issuing terminal.

for

XXX -- VOLUME NOT READY

Explanation:

The command specified a volume that was
(not up to speed).

not

ready

XXX -- VOLUME(S) STILL MOUNTED

Explanation:

A system with mounted volumes cannot be saved.

User Action:

To correct the problem, dismount the volumes and
retry
the command.
The MCR Devices command can be used to
display the mounted volumes.

XXX -- VOLUME STRUCTURE NOT SUPPORTED

Explanation:

RSX-llM/M-PLUS does not support
structure level of the volume being mounted.

the

Fi les-11

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
RSX-llM/M-PLUS. This error causes the system to halt.
XXX -- VOLUME WRITE LOCKED

Explanation:

The
command
specified
a
volume
that
was
write-locked and therefore could not be initialized as a Files-11
device.
XXX -- WARNING BLOCK 0 IS BAD

Explanation:
was bad.

Block 0 of the specified volume,
the boot block,
A bootable image cannot be placed on this volume.

XXX -- (WARNING) COULD NOT SIZE BOOTED DEVICE

Explanation:

Save recognized the device name as a device that it
should size,
but it could not size it.
The UCB words U.CW2 and
U.CW3 for the booted device may incorrectly indicate device size.
I/O errors may result.

A-31

MCR AND TKTN MESSAGES
XXX -- WARNING - KRB name INTERRUPT VECTOR nnn IN USE

Explanation:

An attempt was made to load a driver that specifies
an interrupt vector which is not pointing to a nonsense interrupt
entry point address.
This is usually caused by a previously
loaded driver which has used this vector.

When you get this message, Load has loaded the driver
but it has not overwritten the interrupt vector.

correctly,

XXX -- WARNING - KRB name INTERRUPT VECTOR nnn TOO HIGH

Explanation:

An attempt was made to l~ad a driver that specifies
an
interrupt vector address that
is higher than the highest
permissible vector address in your system.

When you get this message, Load has loaded the driver
but it has not overwritten the interrupt vector.

correctly,

XXX -- 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.
XXX -- (WARNING) NONEXISTENT LUN ASSIGNMENT FOR TASK taskname

Explanation:

The physical device to which Save was attempting to
rebind 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 KT!!
registers 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 ATTRIBUTE FAILURE

Explanation:

An error was encountered in writing the
of either the MFD or the newly created UFD.

attributes

XXX -- WRITE CHECK NOT SUPPORTED

Explanation:

An attempt was made to support write check
for a
device other than a RK05 or RK06 disk.
Write check is supported
only for RK05 and RK06 disks.

XXX -- WRONG VOLUME LABEL

Explanation:

The volume label and the
command did not match.

A-32

label

specified

the

'-"'

INDEX

A
@ si9n, 5-1
ABO, 4-10
Abort. conuna:nd, 4-10
Aborting a task, 4-10
Access,
types of, 3-2
Access rights,
assigning, 3-3
Accessing a file, 3-2, 3-3
Account entries,
adding, 2-18
deleting, 2-21
examining, 2-19
listing, 2-21
modifying, 2-20, 2-22
sorting, 2-21
Account file,
creating multiuser, 2-17, 2-18
Account file entry, 2-18
Account file maintenance
program, 2-17
ACNT 2-17
functions of, 2-17
ACNT error messages, 2-22
ACP, 4-36, 4-65
/ACP keyword, 4-68
ACS, 4-135
ACT, 4-14
Active conunand, 4-14
Actiire task, 1-3
Active Task List conunand,
4-21
Actii1e tasks,
displaying, 4-14
displaying status of, 4-21
Adding account entries, 2-18
/AFF keyword, 4-148, 4-165
ALL, 4-16
/ALL keyword, 4-14
/ALLOC keyword, 4-131
Allocate Checkpoint Space
conunand, 4-135
Allocate command, 2-16, 4-16
Allocating a device, 2-16, 4-16
Allocating checkpoint file,
·4-135
Allocating dynamic checkpoint
:space, 4-135
ALT, 2-2, 4-138
Alteir conunand, 4-138
Altering running priority of
task, 4-138
Altering static priority of task,
·4-138
Ancillary Control Processor
(ACP), 4-36, 4-65
1,

ANSI magnetic tape, 3-1
mounting, 4-65
.ASK directive, 5-13
.ASKN directive, 5-14
.ASKS directive, 5-16
ASN, 4-18
Assign conunand, 4-18
Assigning access rights, 3-3
Assigning logical name, 4-18
Assigning temporary taskname,
4-85
Assignment,
defining logical, 4-18
deleting logical, 4-18
displaying logical, 4-18
global, 4-18
local, 4-18
logical device, 2-13, 2-14,
4-18
login, 4-18
Assignments,
displaying LUN, 4-64
Asterisk convention, 3-8
At (@) sign, 5-1
AT., 5-2
ATL, 4-21
Attached terminal, 2-6

B
Backspace option, 2-2
/BAD keyword, 4-52
Basic MCR error messages, B-1
Basic MCR syntax, B-1
Baud rates,
DHll, 4-106
DZll, 4-106
.BEGIN directive, 5-17
Bit,
disable output, 2-4
Block,
Task Control (TCB), 4-21,
4-146, 4-173
Unit Control (UCB), 4-146
Volume Control (VCB), 4-36,
4-65
Volume Set Control (VSCB) ,
4-65
Block Directory, Conunon, 4-146
Block Number,
Logical (LBN), 4-173
BOO, 4-139
Boot conunand, 4-139
Booting system image, 4-139
Branching to a label, 5-25
Branching to label on error, 5-30
Breakpoint conunand, 4-142

Index-!

INDEX

BRK, 4-142
BRO, 4-24
Broadcast command, 4-24
/BUF keyword, 4-88
Bye command, 2-15, 4-27

Command (Cont.)
Hello, 2-14, 4-41
Help, 4-46
Initialize Volume, 4-51
Install, 4-146
Install-run-remove, 4-80
Load, 4-157
Logical Unit Numbers, 4-64
Mount, 2-16, 4-65
Open Register, 4-165
Partition Definitions, 4-76
Reassign, 4-168
Redirect, 4-169
Remove, 4-171
Resume, 4-79
Run, 4-80
Save, 4-172
Set, 4-87
Stop, 4-126
Switch Register, 4-183
System Service Message, 4-182
Task List, 4-128
Task List-ATL Format, 4-127
Time, 4-130
Unfix, 4-184
Unload, 4-185
Unstop, 4-134
User File Directory, 3-2, 4-131
Command file,
indirect, 5-1
nested indirect, 5-2, 5-11
specifying an indirect, 5-1
Command file label, 5-12
Command file syntax,
MCR, 5-11
Command name, 4-9
Command parameter, 4-1
Command string termination, 4-2
Command summary,
MCR, 4-6
Command syntax, 4-1, 4-4
Commands,
informational, 4-6
initialization, 4-6
MCR, 4-1
multiuser protection, 4-8
RSX-llS MCR, B-1
system maintenance, 4-7, 4-8
task control, 4-7
Comments, 4-3, 5-3
Common Block Directory, 4-146
Console interface,
monitor, 4-1
Control Block,
Task (TCB), 4-21, 4-146, 4-173
Unit (UCB), 4-146
Volume (VCB), 4-36, 4-65
Volume Set (VSCB) , 4-65
Control characters, 2-1

c
CAN I 4-28
Cancel command, 4-28
Carriage return, 2-2
CBD, 4-29
/CHA keyword, 4-54
.CHAIN directive, 5-18
Changing account entries, 2-18,
2-19, 2-20, 2-21, 2-22
Characteristics,
alters device, 4-87
terminal, 2-5
Characters,
control, 2-1
CTRL, 2-1, 2-3, 2-4, 2-5
erasing, 2-2
special, 2-1
Checkpoint file, 4-135
allocating, 4-135
discontinuing, 4-135
Checkpoint space,
allocating dynamic, 4-135
/CKP keyword, 4-148
Clock queue entries,
displaying, 4-143
.CLOSE directive, 5-18
CLQ, 4-143
CLQUEUE command, 4-143
Code,
User Identification (UIC),
2-14 I 3-1, 3-5
/COLOG keyword, 4-21
Command,
Abort, 4-10
Active, 4-14
Active Task List, 4-21
Allocate, 2-16, 4-16
Allocate Checkpoint Space,
4-135
Alter, 4-138
Assign, 4-18
Boot, 4-139
Breakpoint, 4-142
Broadcast, 4-24
Bye, 2-1, 4-27
Cancel, 4-28
Common Block Directory, 4-29
CLQUEUE, 4-143
Deallocate, 2-16, 4-32
Devices, 4-32
Dismount, 4-36
Fix-in-memory, 4-144

Index-2

INDEX
Control commands,
task, 4-7
Control Processor,
Ancillary (ACP), 4-36, 4-65
ConvEmtion,
asterisk, 3-8
task-naming, 4-3
/COTERM keyword, 4-122
/CPU keyword, 4-165
/CRE keyword, 4-40
Creating HELP file, 4-46
Creating multiuser account
file, 2-17, 2-18
Creating User File Directory
(UFD) I 4-131
/CRT keyword, 4-90
/CTB keyword, 4-158
CTRL characters, 2-1
CTRL/C, 2-1, 2-3, 2-7, 2-8
CTRL/I, 2-3
CTRL/K, 2-3
CTRL/L, 2-3
CTRL/O, 2-3, 2-4
CTRL/Q, 2-5
CTRL/R, 2-5
CTRL/S, 2-5
CTRL/U, 2-1, 2-5
CTRL/Z, 2-5
Current UIC, 3-5

D
.DATA directive, 5-18
Data mode, 5-21
Date,
setting current, 4-130
/DCL keyword, 4-91
/DE, 5-11
DEA, 4-31
Deallocate command, 2-16, 4-31
Deallocating a device, 2-16, 4-31
Debugging Tool,
Executive, 4-140, 4-142
.DEC directive, 5-19
Default device-unit, 3-6
Default file protection, 3-3
Default file version, 3-6
Default prompt, 2-7, 4-2
Default switch, 3-6
Default UIC, 3-6
setting, 4-87, 4-108
Default UIC in multiuser
system, 3-5
Defaults,
file specifier, 3-6
Defining logical assignment,
4-18
.DEl~AY directive, 5-19
DELETE key, 2-2
Delete option, 2-21

Deleting a line, 2-5
Deleting account entries, 2-21
Deleting characters, 2-2
Deleting logical assignment, 4-18
/DENS keyword, 4-54, 4-68
/DEV keyword, 4-37
DEV, 4-32
Device,
allocating a, 2-16, 4-16
deallocating a, 2-16, 4-31
dismounting, 4-36
logical, 2-12, 2-13
null, 2-12
peripheral, 2-9, 2-10, 2-11
private, 2-16
pseudo, 2-11
public, 2-16
reassigning, 2-11, 2-12
redirecting, 2-11, 2-12
redirecting pseudo, 2-11, 2-12
unowned, 2-16
Device assignment,
logical, 2-13
Device command, 4-32
Device driver,
loadable, 4-157, 4-185
loading nonresident, 4-157
unloading, 4-185
Device table,
logical, 2-13
Device-unit,
default, 3-6
Device-unit name, 2-9, 2-10, 3-4
Devices,
display status of known, 4-32
peripheral, 2-9
pseudo, 2-9, 2-11
DHll baud rates, 4-106
Directive,
.ASK, 5-13
.ASKN, 5-14
.ASKS, 5-16
.BEGIN, 5-17
.CHAIN, 5-18
.CLOSE, 5-18
.DATA, 5-18
.DEC, 5-19
.DELAY, 5-19
.DISABLE, 5-20
.ENABLE, 5-20
.END, 5-23
.ERASE, 5-23
.EXIT, 5...;.24
.GOSUB, 5-25
.GOTO, 5-25
.IF, 5-26
.!FACT, 5-27
. IFDF, 5-27
• IFF, 5-28
.!FINS, 5-27

Index-3

INDEX

Directive (Cont.)
.IFNACT, 5-27
.IFNDF, 5-27
.IFNINS, 5-27
.IFT, 5-28
.INC, 5-29
.ONERR, 5-30
.OPEN, 5-31
.OPENA, 5-31
.PAUSE, 5-32
. RETURN I 5-33
.SETF, 5-33
.SETN, 5-33
.SETS, 5-34
.SETT, 5-33
.STOP, 5-35
.TEST, 5-36
.WAIT, 5-36
.XQT, 5-37
Directives,
processor, 5-2
Directory,
Master File (MFD) , 3-2
Common Block (CBD), 4-29
System Task (STD), 1-3, 4-146
User File (UFD), 3-1, 3-2
.DISABLE directive, 5-20
Disable output bit, 2-4
Disabling logons, 4-112
Disabling terminal display, 2-4
Discontinuing checkpoint file,
4-135
Disk Save and Compress utility,
4-147, 4-173
Dismount command, 4-36
Dismounting device, 4-36
Display,
disabling terminal, 2-3, 2-4,
2-5
resuming terminal, 2-3, 2-4,
2-5
Displaying,
active tasks, 4-21
clock queue entries, 4-143
current time and date, 4-130
HELP file, 4-46
logical assignments, 4-18
LUN assignments, 4-64
message at terminal(s), 4-24
partition definitions, 4-76
status of active tasks, 4-21
status of installed tasks,
4-127
status of known devices, 4-32
DMO, 4-36
Dormant task, 1-3
DOS format, 3-1
Driver,
loadable device, 4-157, 4-185

Driver (Cont.)
loading nonresident device,
4-157
unloading device, 4-173, 4~185
/DRV keyword, 4-166
DSC, 4-147
Dump,
postmortem, 4-10
Dynamic checkpoint space,
allocating, 4-135
Dynamic storage region,
setting size of, 4-118
DZll baud rates, 4-106

E
/EBC keyword, 4-91
/ECHO keyword, 4-93
/ELIM keyword, 4-40
.ENABLE directive, 5-20
Enabling logons, 4-112
.END directive, 5-23
Entries,
displaying clock queue,
4-143
.ERASE directive, 5-22
Erasing a line, 2-5
Erasing characters, 2-2
Error messages,
ACNT, 2-22, 2-23
Basic MCR, B-1
Command related, 4-9
MCR, A-1
TKTN, A-1
ESC key, 2-2
Escape sequence, 2-2, 4-92
/ESCSEQ keyword, 4-92
/EST keyword, 4-148
Examine option, 2-19
Examining account entries, 2-19
Examining word of memory, 4-165
Exchange program,
File (FLX), 3-1
Executive Debugging Tool, 4-140,
4-142
.EXIT directive, 5-24
/EXT keyword, 4-54, 4-68
Extensions,
task, 4-119

F
/FDX keyword, 4-94
File, 3-1
accessing a, 3-2, 3-3
allocating checkpoint, 4-135
checkpoint, 4-135
discontinuing checkpoint, 4-135
input, 3-3

Index-4

.....__________________________________________________________

......................................_.

INDEX

•"-'.

File (Cont.)
output, 3·-3
spe~cif iers, 3-3
specifier defaults, 3-6
File Directory,
Master (MFD), 3-2
UFO, deleting, 3-2
Use~r (UFD) , 3-1
File Exchange program (FLX),
3-1
File format, 3-1
File ownership, 3-1
File processor switches,
indirect, 5-10
File protection, 3-1, 3-2
default, 3-2
File specifier, 3-3
format, 3-4, 3-5
File specifier defaults, 3-6
File system, 3-1
File type, 3-4
standard, 3-6
File version, 3-6
de:Eault, 3-6
Filename, 3-4, 3-6
FILES-11 volume, 3-1
initializing, 4-51
FIX, 4-144
Fix-in-memory command, 4-144
Fixed task,
freeing a, 4-184
Fixing task in memory, 4-144
Flags,
task status, 4-21
FLX, 3-1
/FOR keyword, 4-68
Foreign volume, 3-1
Form feed, 2-3
/FORMFEED keyword, 4-95
Format, 4-9
DOS, 3-1
file, 3-1
RT-11, 3-1
/FPRO keyword, 4-55, 4-69
Freeing a fixed task, 4-144

G
Global assignment, 4-18
Global logical name, 2-13
Global symbol mode, 5-20
.GOSUB directive, 5-25
.GOTO directive, 5-25

H
HEL, 4-41
Hello command, 2-14, 4-41
HELP command, 4-46

HELP file, creating, 4-46
/HFILL keyword, 4-96
/HHT keyword, 4-96
/HIGH keyword, 4-158
/HOLD keyword, 4-97
Hold-screen mode, 4-97
Horizontal tab, 2-3

I/O processing,
optimizing, 4-112
I/O requests,
redirecting, 4-169
I/O rundown, 4-10
Identification Code
User (UIC), 2-14, 3-1, 3-5
.IF directive, 5-26
.IFACT directive, 5-27
.IFDF directive, 5-27
.IFF directive, 5-28
.IFINS directive, 5-27
.IFLOA directive, 5-28
.IFNACT directive, 5-27
.IFNDF directive, 5-27
.IFNINS directive, 5-27
.IFNLOA directive, 5-28
.IFT directive, 5-28
Image,
booting system, 4-139
saving system, 4-172
.INC directive, 5-29
/INC keyword, 4-148
Indirect command file, 5-1
nested, 5-11
specifying an, 5-1
Indirect file processing,
suspending, 5-36
Indirect File Processor,
directives, 5-2
MCR, 5-2
switches, 5-10
symbols, 5-5
variables (see symbols)
/INDX keyword, 4-55
/INF keyword, 4-55
Informational commands, 4-6
ACT, 4-6, 4-14
ATL, 4-6, 4-21
CBD, 4-6, 4-29
CLQUEUE, 4-7, 4-143
DEVICES, 4-7, 4-32
LUNS, 4-7, 4-64
PARTITIONS, 4-7, 4-76
TAL, 4-7, 4-127
TASKLIST, 4-7, 4-128
INI, 4-51
Initialization commands, 4-6
ACS, 4-6, 4-135

Index-5

INDEX

Initialization commands (Cont.)
ASN I 4-6 I 4-18
BOOT, 4-6, 4-139
DMOUNT, 4-6, 4-36
PLAGS, 4-6, 4-40
INITVOLUME, 4-6, 4-51
INSTALL, 4-6, 4-146
LOAD I 4-6 I 4-157
MOUNT, 4-6, 4-65
SET I 4-6 I 4-87
TIME, 4-6, 4-130
UFD, 4-6, 4-131
UNLOAD, 4-6, 4-185
Initialize Volume command,
3-1, 4-51
Initializing FILES-11 volume,
4-51
Input,
solicited, 2-7
unsolicited, 2-7
Input file, 3-3
Input prompt, 2-7, 4-1, 4-2
INS, 4-146
Install command, 4-146
Install-run-remove command, 4-80
Installed tasks,
displaying status of, 4-127
removing, 4-171
Installing a task, 1-3, 4-146
Interchange Program, Peripheral,
(PIP) I 3-2
Interface,
monitor console, 4-2
Interval.,
time, 4-80

K
Keyword, 4-3
/ACP, 4-68
/AFF, 4-148, 4-165
/ALL, 4-14
/ALLOC I 4-131
/BAD, 4-52
/BLKS, 4-135
/BUF, 4-89
/CHA, 4-54
/CKP, 4-83, 4-148
/COLOG, 4-121
/COTERM, 4-122
/CPU, 4-165
/CRE I 4-90
/CRT I 4-90
/CTB, 4-158
/DCL, 4-91
/DENS, 4-54, 4-68
/DEV, 4-37
/DRV I 4-166
/EBC, 4-91

Keyword (Cont. )
/ECHO, 4-93
/ELIM, 4-40
/ESCSEQ, 4-92
/EST, 4-148
/EXT, 4-54, 4-68
/FDX, 4-94
/FOR, 4-68
/FORMFEED, 4-95
/FPRO, 4-55, 4-69
/HFILL, 4-96
/HHT, 4-96
/HIGH, 4-158
/HOLD, 4-97
/KNL, 4-165
/KNLD, 4-166
/KNLI, 4-166
/LIBUIC I 4-113
/LINES, 4-97
/LOCK, 4-37
/LOG, 4-32
/LOGFILE, 4-123
/LOGON, 4-112
/LOWER, 4-99
/LRU, 4-56, 4-69
/MAIN I 4-114
/MAXEXT, 4-119
/MAPKT, 4-112
/MCR, 4-100
/MOU, 4-174
/MXF, 4-56
/NOCOLOG, 4-122
/NOCON, 4-175
/NOCOTERM, 4-123
/NOCRT, 4-90
/NOEBC, 4-92
/NOECHO, 4-93
/NOESCSEQ, 4-93
/NOFORMFEED, 4-95
/NOFDX, 4-94
/NOHHT, 4-97
/NOHOLD, 4-98
/NOLOGON, 4-112
/NOLOWER, 4-99
/NOMAIN I 4-115
/NOOVLP, 4-101
/NOPAR, 4-118
/NOPRIV, 4-102
/NOPUB, 4-102
/NOREMOTE, 4-103
/NORPA, 4-104
/NOSLAVE, 4-105
/NOSUB, 4-117
/NOTYPEAHEAD, 4-108
/NOVFILL, 4-109
/NOWCHK, 4-110
/NOWRAP, 4-111
/OVLP, 4-100
/OVR, 4-69

Index-6

...............................................................................____________________________

INDEX

Keyword (Cont.)
/OVREXP, 4-70
/OVRFSID, 4-69
/P A.R, 4 - 8 4 , 4-11 7 , 4 -14 9 , 4 -15 7 ,
4-165
/PA.RM, 4-70
/PM.D, 4-11, 4-84, 4-149
/POOL, 4-118
/PRI, 4-84, 4-138, 4-149
/PRIV, 4-101
/PRO, 4-57, 4-132, 4-149
/PRTCL, 4--71
/PUB, 4-102
/RCK, 4-72
/REG, 4-144, 4-165, 4-184
/REMOTE, 4-103
/RON, 4-144, 4-150, 4-184
/ROPAR, 4-84, 4-150
/RPA, 4-104
/RPRI, 4-138
/RSI, 4-80
/SE' ILE, 4·-17 4
/SIZE, 4-158
/SI~AVE, 4·-105
/SIN, 4-84, 4-150
/SPEED, 4·-106
/SUB, 4-116
/SYNC, 4-150
/SYSUIC, 4-113
/TASK, 4-85, 4-151, 4-165
/TE:L, 4-72
/TE:RM, 4-4, 4-5, 4-14, 4-37,
4-138
/TYPEAHEAD, 4-107
/U IC , 4- 5 8 , 4 - 7 0 , 4 - 8 0 , 4 -8 5 ,
4-108, 4-151
/UNL, 4-70
/USER, 4-37
/VE'ILL, 4-109
/VI, 4-58, 4-7 0
/WB, 4-174
/WCHK, 4-110
/WIN, 4-58, 4-7 0
/WRAP, 4-·111
Keyword value, 4-3
/KNL keyword, 4-165
/KNLD keyword, 4-166
/KNLI keyword, 4-166

L
Labe:l,
branching to a, 5-25
command file, 5-12
Labe:l on error,
branching to, 5-30
LBN, 4-146, 4-173
/LIBUIC keyword, 4-113
/LINES keyword, 4-97

Line,
deleting a, 2-5
erasing a, 2-5
retyping current, 2-5
Line terminator, 2-2, 2-5, 4-1
Line terminator options, 4-166
List option, 2-21
Listing account entries, 2-21
LOA, 4-157
Load command, 4-157
Loadable device driver, 4-157,
4-185
Loading nonresident device
driver, 4-157
Local assignment, 4-18
Local logical name, 2-12
/LOCK keyword, 4-37
/LOG keyword, 5-33
/LOGFILE keyword, 4-123
Logging off terminal, 2-13, 2-15,
4-27
Logging onto terminal, 2-13,
2-15, 4-41
Logical assignment,
defining, 4-18
deleting, 4-18
displaying, 4-18
Logical Block Number (LBN),
4-146, 4-173
Logical device, 2-12, 2-13
Logical device assignment,
2-13, 4-18
Logical device table, 2-13
Logical name, 2-12
assigning, 4-18
global, 2-13
local, 2-13
login, 2-13
Logical symbols, 5-5, 5-6
Logical test of symbols, 5-26
Logical Unit Number (LUN) ,
2-11
Logical Unit Numbers command,
4-64
Logical-device assignment, 2-13,
2-14, 4-18
Login assignment, 4-18
Login logical name, 2-13
/LOGON keyword, 4-112
Logon UIC, 3-5
Logons,
disabling, 4-112
enabling, 4-112
/LOWER keyword, 4-99
/LRU keyword, 4-56, 4-69
LUN, 4-64
LUN assignments,
displaying, 4-64
LUNs, 2-11
reassigning, 4-168

Index-7

INDEX

M
Magnetic tape,
ANSI, 3-1
mounting ANSI, 4-65
Magnitude value, 4-81
/MAIN keyword, 4-114
Mapped system, 1-1
Mask,
protection, 3-2
Master File Directory (MFD), 3-2
/MAXEXT keyword, 4-119
/MAXPKT keyword, 4-112
/MC, 5-11
MCR,
command file syntax, 5-11
command summary, 4-6
commands for RSX-llS, B-1
indirect file processor, 5-2
interface, 4-2
messages, A-1
messages for Basic MCR, B-1
prompt, 2-3, 2-7, 2-8
syntax for Basic MCR, B-1
/MCR keyword, 4-100
Memory,
examining word of, 4-165
modifying word of, 4-165
Message at terminal,
displaying, 4-24
Messages,
ACNT error, 2-22, 2-23
Basic MCR error, B-1
MCR, A-1
TKTN, A-1
MFD, 3-2
Mode,
data, 5-21
escape recognition, 5-20
global symbol, 5-20
lower-case, 5-20
substitution, 5-20
Modify option, 2-20
Modifying account entries,
2-20' 2-22
Modifying word of memory, 4-165
Monitor console interface, 4-2
MOU, 4-65
MOU keyword, 4-174
Mount command, 2-16, 3-1, 4-65
Mounting ANSI magnetic tape,
4-66
Mounting network channels, 4-71
Mounting volume, 4-65
Multiprogramming, 1-2
Multiuser account file, 2-17
creating, 2-18
Multiuser protection commands,
4-8
ALLOCATE, 4-8, 4-16

Multiuser protection commands
(Cont.)
BYE' 4-8 I 4-27
DEALLOCATE, 4-8, 4-31
HELLO, 4-8, 4-41
HELP, 4-8, 4-46
Multiuser protection system,
2-13
commands, 4-8
default UIC in, 3-5
functions of, 2-13
/MXF keyword, 4-56

N
Name,
command, 4-9
device-unit, 2-9, 3-3
global logical, 2-13
logical, 2-12
login logical, 2-13
task, 5-36
Nested indirect command
files, 5-2, 5-11
Network channels,
mounting, 4-71
/NOCOLOG keyword, 4-122
/NOCON keyword, 4-175
/NOCOTERM keyword, 4-123
/NOCRT keyword, 4-90
/NOEBC keyword, 4-92
/NOECHO keyword, 4-93
/NOESCSEQ keyword, 4-93
/NOFORMFEED keyword, 4-95
/NOFDX keyword, 4-94
/NOHHT keyword, 4-97
/NOHOLD keyword, 4-98
/NOLOGON keyword, 4-112
/NOLOWER keyword, 4-99
/NOMAIN keyword, 4-115
Nonprivileged,
status, 2-15
user, 2-6, 3-~5
/NOOVLP keyword, 4-101
/NOPAR keyword, 4-118
/NOPRIV keyword, 4-102
/NOPUB keyword, 4-102
/NOREMOTE keyword, 4-103
/NORPA keyword, 4-104
/NOSLAVE keyword, 4-105
/NOSUB keyword, 4-117
/NOTYPEAHEAD keyword, 4-108
/NOVFILL keyword, 4-109
/NOWCHK keyword, 4-110
/NOWRAP keyword, 4-111
Null device, 2-12
Number,
Logical Block (LBN), 4-146,
4-173

~
'
l

Index-8

.............................................____________________________,_.__

----------~~~~~~~~~~

INDEX

Number
(Cont. )
Logical Unit (LUN) , 2-11
NumE~ric constants, 5-9
Numeric expressions, 5-9
NumE~ric symbols, 5-5, 5-9, 5-19,
5-29, 5-33, 5-34, 5-36

0
.ONERR directive, 5-30
OPE 5-76
.OPEN directive, 5-31
.OPENA directive, 5-31
Open Register command, 4-165
Operation,
tc::tsk, 1-2
tE~rminal, 2-1
Optimizing I/O processing,
4-112
Option,
backspace, 2-2
delete, 2-21
examine, 2-19
list, 2-21
modify, 2-20
sort, 2-21
switch, 3-4
Output,
resuming suspended, 2-3
suspending terminal, 2-3, 2-5
Output file, 3-3
/OVLP keyword, 4-100
/OVR keyword, 4-69
/OVREXP keyword, 4-70
/OVRFSID keyword, 4-69
1,

Owrn~rship,

file, 3-1

p
PAR, 5-72
Par.ameter command, 4-1
/PAR keyword, 4-84, 4-117, 4-149,
4-157, 4-165
/PARM keyword, 4-70
Partition, 1-1
setting up, 4-114
system-controlled, 1-1
user-controlled, 1-1
Partition definitions,
displaying, 4-76
Partition Definitions command,
4-76
Password, 2-14
.PAUSE directive, 5-32
Peripheral devices, 2-9, 2-10
Peripheral Interchange Program
(PIP) I 3-2

Index-9

/PMD keyword, 4-10, 4-11, 4-84,
4-149
Pool,
setting size of dynamic,
4-118
/POOL keyword, 4-118
Postmortem dump, 4-10
/PRI keyword, 4-84, 4-138,
4-149
Priority, 1-2
Priority directive, alter, 4-10
Priority of task,
altering running, 4-10
altering static, 4-138
/PRIV keyword, 4-101
Private device, 2-16
allocating, 4-16
deallocating, 4-31
Privilege,
terminal, 2-6
Privileged,
user, 2-6, 2-15, 3-5
status, 2-15
/PRO keyword, 4-57, 4-132, 4-149
Processor,
Ancillary Control (ACP), 4-36,
4-65
MCR Indirect File (AT.), 5-2
Processor directives, 5-2
Processor switches,
indirect file, 5-10
Program,
account file maintenance
(ACNT), 2-17
File Exchange (FLX), 3-1
Peripheral Interchange
(PIP) , 3-2
SHUTUP, 2-23
Prompt,
default,
2-7, 4-2
input, 2-7, 4-1, 4-2
MCR, 2-3, 2-7, 2-8
task, 2-7
Protection,
default file, 3-3
file I 3-2
multiuser, 2-13
Protection mask, 3-2
Protection UIC, 3-5
/PRTCL keyword, 4-71
Pseudo devices, 2-9, 2-11
redirecting, 2-11, 2-12
/PUB keyword, 4-102
Public device, 2-16

Q
Queue entries,
displaying clock, 4-143

INDEX

Rates,
DHll baud, 4-106
DZll baud, 4-106
/RCK keyword, 4-72
RE.A, 4-168
Reassign conunand, 4-168
Reassigning device, 2-12
Reassigning LUNs, 4-168
RED, 4-169
Redirect conunand, 4-169
Redirecting,
device, 2-12
I/O requests, 4-169
pseudo device, 2-11, 2-12
/REG keyword, 4-144, 4-165,
4-184
REM, 4-171
/REMOTE keyword, 4-103
Remove conunand, 4-171
Removing installed task, 4-171
Requests,
cancelling time-based
initiation, 4-28
RES, 4-79
Rescheduling a task, 4-80
Resume conunand, 4-79
Resuming suspended output, 2-3
Resuming suspended task, 4-79
Resuming terminal display, 2-3
RETURN, 2-2
Return,
carriage, 2-2
.RETURN directive, 5-33
Retyping current line, 2-5
RK05/RK06 disk,
write check for, 4-110
/RON keyword, 4-144, 4-150, 4-184
/ROPAR keyword, 4-84, 4-150
/RPA keyword, 4-104
/RPRI keyword, 4-138
/RSI keyword, 4-80
RSX-llM/M-PLUS,
shutting down, 2-23
RSX-llS MCR conunands, B-1
RT-11 format, 3-1
RUN I 4-80
Run conunand, 4-80
Running a task, 4-80
Running priority, 4-10

s
SAVI 4-172
Save conunand, 4-172
Saving system image, 4-172
Secondary file, 5-31
SET I 4-87
Set conunand, 4-87

.SETF directive, 5-33
.SETN directive, 5-33
.SETS directive, 5-34
.SETT directive, 5-33
Setting,
current date, 4-130
current time, 4-130
default UIC, 4-108
size of dynamic storage
region, 4-118
system-wide characteristics,
4-87
terminal characteristics,
4-87
terminal UIC, 3-5, 4-108
Setting up partition, 4-114
Setting up subpartition, M-PLUS,
4-116
/SFILE keyword, 4-174
Shutting down RSX-llM/M-PLUS,
2-23
SHUTUP program, 2-23
/SLAVE keyword, 4-105
Slave terminal, 2-6, 4-105
/SLV keyword, 4-84, 4--150
Solicited input, 2-7
Sort option, 2-21
Sorting the account file, 2-21
Special characters, 2-1
Specifier,
file, 3-3, 3-4, 5-1
UIC, 2-14 I 3-4
Specifier defaults,
file, 3-6
Specifying a UFO, 3-3
Specifying an indirect
conunand f ilE3, 5-1
/SPEED keyword, 4-106
Standard file type, 3-6
Status,
nonprivileged, 2-15
privileged, 2·-15
Status flags,
task, 4-21
Status of active tasks,
displaying, 4·-21
Status of installed tasks,
displaying, 4-127
Status of known devices,
displaying 4-32
STD I 1-3 I 4-14 6
STD entry, temporary, 4-3
Stop conunand, 4-126
.STOP directive, 5-35
Storage region (pool) ,
setting size of dynamic, 4-118
STP, 4-126
String constants, 5-10
String expressions, 5-10

Index-10

INDEX

String symbol value,
substituting, 5-5
String symbols, 5-9, 5-10
String termination, command, 4-2
/SUB keyword, 4-116
Subpartition, 1-2
setting up, 4-11
Substituting string symbol
value, 5-8
Substitution mode, 5-20
Substrings, 5-10
Summary,
Basic MCR command, B-1
MCR command, 4-6
Suspended task,
re~suming, 4-79
Suspending indirect file
processing, 5-36
Suspending terminal output,
2-3' 2--5
Switch,
default, 3-6
Switch option, 3-4
Switch Register command, 4-183
Switch value, 3-5
Switches,
indirect file processor,
5-10
SWR,. 4-183
Symbol mode,
global, .5-20
Symbol value substitution, 5-8
Symbols, 5·-5
logical, 5-5, 5-6
logical test of, 5-26
numeric, 5-5, 5-7, 5-9
special, 5-6
string, 5-5, 5-7, 5-9
/SYNC keyword, 4-150
Syntax,
Basic MCR, B-1
command, 4-4
MCR command file, 5-11
System,
file, 3-1
mapped, 1-1
multiuser protection, 2-13
unmapped, 1-1
System image,
booting, 4-139
saving, 4-172
System maintenance commands, 4-7
BRK, 4-7, 4-142
BRO, 4-7, 4-24
OPEN, 4-8, 4-165
SAVE, 4-·8, 4-172
SSM, 4-8, 4-182
SWR, 4-8, 4-183
System Service Message command,
4-182

SSM, 4-182
System Task Directory (STD), 1-3,
4-146
System UIC, 4-113
System-controlled partition, 1-1
/SYSUIC keyword, 4-113

T
Tab,
horizontal, 2-3
vertical, 2-3
TAB key, 2-3
Table,
logical device, 2-13
TAL, 5-112
Tape,
ANSI magnetic, 3-1
mounting ANSI magnetic, 4-66
TAS, 4-128
/TASK, 5-57
Task, 1-1
aborting a, 4-10
active, 1-3
altering running priority
of, 4-138
altering static priority
of, 4-138
AT. I 5-2
dormant, 1-3
freeing a fixed, 4-144
installing a, 1-3, 4-146
preparing a, 1-2, 1-3
removing installed, 4-171
rescheduling a, 4-80
resuming suspended, 4-79
running a, 4-80
Task Control Block (TCB),
Task control commands, 4-7
ABORT, 4-7, 4-10
ALTER, 4-7, 4-138
CANCEL, 4-7, 4-28
FIX I 4-7' 4-144
REASSIGN, 4-7, 4-168
REDIRECT, 4-7, 4-169
REMOVE, 4-7, 4-171
RESUME, 4-7, 4-79
RUN' 4-7 I 4-80
STP, 4-7, 4-126
UNFIX, 4-7, 4-184
UNSTOP, 4-7, 4-134
Task Directory,
System (STD), 1-3, 4-146
Task execution,
terminating, 4-10
Task extensions, 4-119
Task in memory,
fixing, 4-144
/TASK keyword, 4-85, 4-151, 4-165

Index-11

INDEX

Task List command, 4-128
Task List-ATL Format command,
4-127
Task names, 5-36
Task-naming convention, 4-3
Task operation, 1-2
Task prompt, 2-7
Task status flags, 4-21
Task termination notification
routine (TKTN), 4-10
Taskname,
assigning temporary, 4-85
Tasks,
displaying active, 4-14, 4-21
displaying status of active,
4-21
displaying status of
installed, 4-127
TCB, 4-21, 4-146, 4-173
/TEL keyword, 4-72
Temporary STD entry, 4-3
/TERM keyword, 4-5, 4-14, 4-106
Terminal,
attached, 2-6
displaying message at, 4-24
logging off, 2-13, 4-27
logging onto, 2-13, 4-41
slave, 2-6, 4-105
types of operator, 4-8
unattached, 2-6
Terminal characteristics, 2-5
setting, 4-87
Terminal display,
disabling, 2-3
resuming, 2-3
Terminal operation, 2-1
Terminal output,
suspending, 2-3, 2-5
Terminal privilege, 2-6
Terminal UIC,
setting, 3-5, 4-108
Terminating command strings, 4-2
Terminating task execution, 4-10
Terminator,
line, 2-2, 2-5~ 4-1
.TEST directive, 5-36
Test of symbols,
logical, 5-26
TIM, 4-130
Time,
setting current, 4-130
Time command, 4-130
Time interval, 4-80
Time unit value, 4-80
Time-based requests,
cancelling initiation, 4-28
TKTN, 4-10
messages, A-1

Tool,
Executive Debugging, 4-140,
4-142
/TR, 5-11
Type,
file, 3-4
standard file, 3-6
/TYPEAHEAD keyword, 4-107

u
UCB, 4-146
UFO, 3-1
creating, 4-131
specifying a, 3-3
UFO command, 3-2, 4-131
UIC, 2-14, 3-1, 3-5
current, 3-5
default, 3-5
logon, 3-5
owner, 3-2
protection, 3-5
setting default, 4-108
setting terminal, 3-5, 4-108
system, 4-113
UIC in multiuser system,
default, 3-5
/UIC keyword, 4-58, 4-70, 4-80,
4-85, 4-108, 4-151
UIC specifier, 2-14, 3-5
Unattached terminal, 2-6
UNF I 4-184
Unfix command, 4-184
Unit Control Block (UCB), 4-146
Unit Number,
Logical (LUN), 2-11
Unit value,
time, 4-80
UNL, 4-185
/UNL keyword, 4·-70
Unload command, 4-185
Unmapped system, 1-1
Unowned device, 2-16
Unsolicited input, 2-7
Unstop command, 4-134
UNS, 4-134
/USER keyword, 4-37
User,
nonprivileged, 2-6, 2-15, 3-5
privileged, 2-14, 3-5
User File Directory, 3-1, 4-131
command, 4-131
creating, 4-131
User groups, 3-3
User Identification Code
(UIC), 2-14, 3-1, 3-5
Us~r-controlled partition, 1-1
Utility,
Bad block, 3-1.
Format, 3-1

Index-12
'Ri. . . . . . . . . . . . . . . . . . . . . . . . . . . .. _ . _ . __ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

~~~-

INDEX

v
Valu~=,

keyword, 4-3
maqnitude, 4-81
substituting string symbol,

.WAIT directive, 5-36
Wildcards, use of, 3-8

!5-8

switch, 3-4
time unit, 4-80
VCB, 4-36, 4-65
Version,
default file, 3-6

x
XDT, 4-140, 4-142
.XQT directive, 5-37

Index-13

RSX-llM/M-PLUS
MCR Operations Manual
AA-H263A-TC

READER'S COMMENTS

NOTE:

Th.is form is for document comments only. DIGITAL will
use comments submitted on this form at the company's
discretion.
If you require a written 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.

'-'1

Cll)

c:
.~

..c
.....
O>

0
0

.....

:::>
0

"-'1

Did you find errors in this manual?
page number.

If so, specify the error and the

G.>
ell

Please indicate the type of reader that you most nearly represent.
[] Assembly language programmer
[] Higher-level language programmer
[] Occasional programmer {experienced)
[] User with little programming experience
[] Student programmer
[] Other (please specify>~~~~~~~~~-~---~~---

Organization ________________________________
Street
City._________,_ _ _ _ _ _ state _______ zip Code _ _ _ _ _ __
or
Country

I
-

Do Not Tear - Fold Here and Tape

-,~

I III I

No Postage
Necessary
if Mailed in the
United States

I
I
I

POSTAGE WILL BE PAID BY ADDRESSEE

(~
RT/C SOFTWARE PUBLICATIONS TW/A14
DIGITAL EQUIPMENT CORPORATION
1925 ANDOVER STREET
TEWKSBURY, MASSACHUSETTS

Do Not Tear - Fold Here

01876

I
I

·~