Digital PDFs

DEC-11-OMOGA-B-D

November 1975

158 pages

Original

5.0MB

Document:	RSX-11M Operator’s Procedures Manual
Order Number:	DEC-11-OMOGA-B-D
Revision:	0
Pages:	158
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V2/DEC-11-OMOGA-B-D_Oper_1975.pdf

OCR Text

RSX-11M
Operator's Procedures
Manual
Order No. DEC-11-0MOGA-B-D

RSX-llM Version 2

digital equipment corporation · maynard. massachusetts

First Printing, November 1974
Revised, September 1975
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no 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 to the terms of such
license.
Digital Equipment Corporation assumes no responsibility for the use
or reliability of its software on equipment that is not supplied by
Digital.

@ 1974, 1975 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
DECUS
UNIBUS
COMPUTER LABS
COM TEX
DDT
DECCOMM

DECsystem-lo
DECtape
DIBOL
EDU SYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8

MASS BUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11

LIMITED RIGHTS LEGEND
Contract No.
Contractor or Subcontractor:

Digital Equipment Corporation

All the material contained herein is considered limited rights data
under such contract.

1/76-15

CONTENTS
Page
vii

PREFACE

CHAPTER

0.1
0.2
0.3

MANUAL OBJECTIVES AND READER ASSUMPTIONS
STRUCTURE OF THE DOCUMENT
ASSOCIATED DOCUMENTS

vii
vii
viii

INTRODUCTION

1-1

1.1

SUMMARY

1-5

PROCEDURES AND CONVENTIONS

2-1

2.1

2-1
2-2

2.7.1
2.7.2

TERMINAL OPERATIONS
Special and Control Characters
TERMINAL CHARACTERISTICS
TERMINAL INPUT CONVENTIONS
START-UP PROCEDURES
Start-Up Using BM792-YB Bootstrap ROM
Start-Up Using MRll-DB Bootstrap ROM
Start-Up Using BM873-YA Bootstrap ROM
Start-Up Using BM873-YB Bootstrap ROM
Start-Up Using M9301-YA or M9301-YB
Bootstrap ROM
Start-Up Display Sequence
ERROR DETECTION AND HANDLING
COMMAND STRINGS
PERIPHER.~L DEVICE N~-~ING ~.ND ASSIGNMENT
Device Reassignment
Device Redirection

2.7.3
2.7.4

Pseudo Devices

2-17

Logical Devices

2-18

FILES AND FILE SPECIFIERS

3-1

3.1
3.2
3.2.1
3.2.2
3.2.3

3-1
3-1
3-2
3-3
3-5
3-6

3.2.5
3.2.6
3.2.7

INTRODUCTION
FILE FUNDAMENTALS
File Protection
File Specifiers
Volumes and Files
Defaults in File Specifiers
Use of File Types
Asterisk Convention (Wildcards)
Example of Filename Command Strings

MCR COMMANDS

4-1

4.1
4.2
4.2.1
4.2.2

COMM.AND SUMMARY
MONITOR CONSOLE INTERFACE
Command Syntax
Keywords
Comments

4-1
4-4

2 .1.1
2.2
2.3
2.4
2.4.1

2.4.2
2.4.3

2.4.4
2.4.5
2.4.6
2.5
2.6
2.7

CHAPTER

3.2.4

CHAPTER

4.2.3

iii

2-5
2-6
2-8
2-8
2-9
2-9
2-10

2-11
2-11
2-12
2-13

2-14
2-16
2-16

3-6
3-7
3-8

4-4
4-5
4-5

CONTENTS (Cont.)
Page
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.4

OPERATOR COMMANDS
Command Description Format
Initialization Commands
Informational Commands
Task Control Commands
System Maintenance Commands
TASK NAMING CONVENTIONS

4-6
4-6
4-8
4-47
4-51
4-68
4-78

INDIRECT COMMAND FILES

5-1

5.1
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
5.2.6.l
5.2.6.2
5.2.6.3

5-1
5-1
5-2
5-3
5-3
5-3
5-4
5-4
5-4
5-4

5.2.6.4
5.2.6.5
5.2.6.5.l
5.2.6.5.2
5.2.6.5.3
5.2.6.5.4
5.2.6.5.5
5.2.6.6
5.2.6.7
5.2.6.8
5.2.6.9
5.2.6.10
5.2.6.11
5.2.7
5.2.8
5.2.9

INDIRECT COMMAND FILES
MCR INDIRECT FILE PROCESSOR
Symbols
Commands to MCR
Switches
Multi-Level Indirect Files
Syntax
Directives
Define a Label
Ask a Question and Wait for a Reply
Delay Execution for a Specified Period of
Time
Branch to a Label
Logical Test (IF)
Test if Symbol Is True or False
Test if Symbol Is Defined or Not Defined
Test if Task Is Installed or Not Installed
Test if Task Is Active or Not Active
Compound Tests
Branch to Label on Detecting an Error
Pause for Operator Action
Set Symbol to True or False
Wait for a Task to Finish Execution
Initiate Parallel Task Execution
Comments
Task Name References
Example of Command File and Its Execution
Error Messages

MCR ERROR MESSAGES

6-1

6.1
6.2

INTRODUCTION
MESSAGES

6-1
6-1

APPENDIX A

MCR COMMAND SUMMARY

A-1

APPENDIX B

BASIC MCR SYNTAX AND ERROR MESSAGES

B-1

CHAPTER

5-5
5-6
5-6
5-6
5-7
5-7
5-7
5-8
5-8
5-9
5-9
5-10
5-10
5-11
5-11
5-11
5-12

FIGURES
FIGURE

1-1

Sample System Memory Layout

1-3

TABLES
TABLE

2-1
2-2

Characters Used in Terminal Operations
RSX-llM Peripheral Devices
iv

2-3
2-15

PREFACE

0.1

MANUAL OBJECTIVES AND READER ASSUMPTIONS

The intent of this manual is to enable its user to successfully
operate an RSX-llM system.
It is designed to be self-contained.
However, if the operator wishes to have deeper insight into system
construction and the precise meaning of terminology used throughout
this manual, a reading of the RSX-llM System Generation Manual is
strongly recommended.
Although the introduction to this manual has a tutorial slant, it does
not claim to train operators. The reader is assumed to be familiar
with computer operating procedures, both realtime and batch, to have a
basic vocabulary of computer-related terms, and to have had experience
operating both the computer console and the terminal devices supported
by RSX-llM for use as operator consoles.
Finally, the term "operator" includes not only the conventional
understanding of that term, but also anyone who chooses to interface
directly with RSX-llM to accomplish some task.
The
expanded
definition of an operator is necessitated by the varied settings in
which an RSX-llM system will operate; some of those settings will not
have an operator in the conventional sense.
This manual is intended mainlv for RSX-llM users:
however:
it can
also be used as a referen~e document for RSX~llS operation; since
RSX-llS is subset-compatible with RSX-llM.

0.2

STRUCTURE OF THE DOCUMENT

Chapter 1 is a capsule overview of the RSX-llM system, focusing on
those aspects of the system related to the operator interface. It
also contains the system-unique terminology used throughout the
manual.
Chapter 2 discusses conventions for
names.

terminal

operations

and

device

Indirect

File

Chapter 3 discusses the file system and file specifiers.
Chapter 4 describes the operator commands.
Chapter 5 describes the use of indirect files and
Processor.

the

Chapter 6 contains the error messages produced by the Monitor
Routines (MCR).

Console

Appendix A contains all RSX-llM MCR commands in summary form.
Appendix B contains a summary of MCR commands and error messages for
RSX-llS.
RSX-llS MCR is a proper subset of RSX-llM MCR; thus,
RSX-llS MCR differs only in the subset commands it will accept.

0.3

ASSOCIATED DOCUMENTS

Other manuals closely allied to the purposes of this document are
described briefly in the RSX-llM/RSX-llS Documentation Directory,
Order No. DEC-11-0MUGA-B-D. The Documentation Directory defines the
intended readership of each manual in the RSX-llM/RSX-llS set and
provides a brief synopsis of each manual's contents.

CHAPTER 1
INTRODUCTION

RSX::lJM ___ is a .m.ultiprogramming, t"e2ltJme op~.rating sy~_tem_~-Its
f un.d.a.rrlan..t.al____ _fy_n._c_UJltL .. _L§__ _t_q _ 12.t.QVJ.o.~
tne con t.r::ol fq r snaring sys tern
r_e_s_uur.ce.s_ among __a_ny .nYmbe_r _of __ u_s~_r__'.':PJ..~_p~red tasks~ ___ These
tasks are
writ ten in a supported source languag_e _: ____ -- i ~-e·:-·;··-MACRO:_ll, FORTRAN IV,
or FORTRAN IV-PLUS.
The sour_G~ J.angu,_gge hi s1,11Js.E!quently translated,
U.nk~_Q.____ t_Q_ J_gJ::.rn _a ___ tg._!:?k imcige, cin_d stored_ on a f ile-s tr uc tu red volume in
a named £ilsL.tha._t ___i__s ___acc:;_ess j,J::>i~ PY th.~ __f q_~ __ s_y.~t--~~.

· 1'.C1_SJ<s__ s_t_9_,rgd___ on _a __nle-:-~t_ructurecj volume may pe _installed
into an
Rsx_-i.!M______s__:y._s_tem_ and_ subsequently run by _issu_ing a command to the
Monitor Console Rout~I'le (MCR}. The terms "install" and
Hrun"
have
pr-ec_i_se -- mea_'ning-s whicr; will be. discussed shortly. MCR provides the
language interface between the operator and the system.
b_t9sk r_l!11_s__ ~I'l a 29rtition. A partition is
memo_ry __ ~ay_i~g_ the following a-ttr ibufes: -

a ____c_?_~-~~2-~~~~-------~-!~_<:k

name;

A defined size;
A fixed starting address, and
A defined type.

. 'J:.l:!~f.g are tw.Q_____Y.~r:_s i_.Q}1_~-- o_f_ R~X~lJr:t:_

m_apped __and
Urtf0a._pped.
From
the
operator's point of view, differences exist between ~h~-~wo versions
only with respect to installing tasks into a partition.

:rn

_u_11m9__pp~cLsys.tem_s_, a
task is linked,
installed, and run
in a
_.2§.r tU_i..QJ1_ - J1_a_yJr.i__g___ Cl spec if"ic b_ase a.ddress. ~ Such
tas"k cann"o t ~e r"tiri
in any partition whose base is not identical
mapp"ed" "sysl:ems-; ·· ·a.·
task may be installed into any partition large enough to contain it,
b_ut__ Jt _ccin_ only run in the partidon into which it was installed.
In
both systems, if the task is checkpointable (i.e., may be temporarily
suspended to make the CPU available to higher priority tasks,
its
checkpoint area must be large enough to contain the partition into
which it was installed.

:··--·--rri ·

RSX-.llM. supports two typ_es of task par tUJ9n._s; . sy~te~-c:on~r~_l}ed and
u~~~~--:-9()I_1_trqJJ_~~-· ___ ?p_a~e
in_ a _sys tern-con trolled _ pa_r__t~ ~is>.~ ~_(mapped
sys.terns only} is dynamically allocated by the system to as many tasks
as will fit simultaneously in the partition.
~ user-controlled
parJ:iUon (bot:h mapped and u11mapped systems} is allocated to only one
task at a time.

1.n__addition, a user-:controlled partition, which is a

m(!_in PC.Htition,
can_ J'.~ J~.u.b.d,Jyide_d in to as many as seven non-over lapping subpar .ti tions.
The subpartitions occupy the identical physical memory as the main

1-1

INTRODUCTION
Q.9!"~.iJion.

However, tasks may not be resic]ent in a ma_in partition and
Us subpartiti~rns simultaneously. I f a main partition is occupfea~
the subpartitions cannot also be occupied. All subpartition~ G~.!l ..J1ave
tasks residing_ tn Jtiemt . ~D.~~~to_re, up to seven _ potentially parallel
tas_k_ e~_ equtJ.911_~ ~an exist within a· pre-empted "·main· partition. - ----·-~-------

T~~-~Q~l

9f _subpaf titioning is to reclaim large storage areas in
unmapp_eq _ -~ystems.
For example, when a large task requiring ·a--ma.-tn
partition is either no longer active or can be
checkpointed,
subpartitioning can be employed to make room for a number of smaller
real time tasks.
Tasks running_jn partitions compete for system resources based on
their -prior f ty and resource avaTia5IITty~ - :rr11e· highest pr ioJ:i E£ Ea_~TC
which has all the resources it need~ to iun, and which can_rnake use of
the resQ_.ur:_q_~-~.- it. needs, will be in control of the CPU.
As _ta_ske __ r_eq':!_e~-~- _sys tern servJc_es ,_ they_ be~9me _blocked, usually w~ i_U_11g
for ~n I/O transfer to complete. Our ing this blockage, RSX-llM.lo.oks
fgr an9the_r task to run. Running a task in the blocked inter.vals ___ of
other tasks is termed multiprogramming.
Task.sin all _partitions compet~ QD_._th~ ba_s.is ....of priority for the ___ __c.Ell.
Thus, the greater the number of user-controlled partitions {including
main partition and subpartitions), and the larger the size of the
dynamically allocted, system-controlled partitions, the greater the
possibilities are for competition.
In addition to competition between memory resident tasks, aDQther
level of competition is in trod u~ce~ by the chec kpo int ing facility_~--· A
task currently running may, if declared chec~pointable_, be pre=e~~~~d
from memory, moved to mass storage, and replaced by a higher pri9Jity
task installed to run in the same partition. Later, when the bigher
priority ~ask has finished, the previously swapped-out task is
returned to memory and continues operation from the point
of
interruption. This roll-in, roll-out process is termed checkpointlng.
These fundamental concepts are illustrated in Figure 1-1.

1-2

INTRODUCTION

JOE
2K

JIM
TOM
3K

JACK
8K

SY SPAR
6K

RSX-llM
--- ---- -

.t:XECU'l'.l VE

QL----.

Figure 1-1
Sample System Memory Layout

Suppose a 16K unmapped system exists with the memory layout shown in
Figure 1-1.
The______ E~_e_qµtiyt:;! _.r~_g_i,qn_,_ req_uj,._J:.'i.ng -~K, c9nsi!?ts of the
Executive and the user-controlled main partition SYSPAR.
Thi~
partft"ioii- --c-onta.l.ns the -file system, MCR,. and the Task Termination
Notification routine
(TKTN).
Furthermore, . the
file sys_~ern _ _:i,s
checkpointable and of lower priorit-y-·tiian MCR
TKTN ._ _'!'.h.1:1_§_, if t_0:e
file sys__t:.e_m is runnJrig and an operator requests MCR, the File System
w_q_l _b~ _c;:_h~ckpointed, and MCR wil_l be loaded and initiat~d.

-or

Th~ user area is composed of a user-controlled
main partition named
TOM,
6Kin length, and three subpartitions, riamed JOE, JIM; and JACK.
The BK partition is used tor program preparation task~ su~h as the
!~rigµ~g~ ~r6cessors and the Task Builder.
These programs will usually
hav:e. a Low priority and may be checkpoinlable.

Th~_~h~ee ~ubpartttions are for realtime tasks.
Any time one of these
tfiJ?.X.s _needs the processor and it has a higher priority than the task
occupying the main partition, the contents of the main partition will
be __ ~heckpointed (if the occupant task is checkpointable).
Sl)p_po_s_~_

the partitions JOE, JIM, JACK, and SYSPAR are occ;:_upied and the
tgsks in thero are ready to run. To which task does the Executive give
the processor? As stated earlier,
the task selection process is

1-3

INTRODUCTION
entirely dependent on task priority; this holds true for SYSPAR as
well. Hencf;?,__th:e_highest priority task will run next, regardless of
where it resides in memory.
Earlier, the two terms
install, and
run
were said to have precise meanings. These meanings will be defined
while sketching the creation of a task. Assume that an operational
RSX-llM system exists.
A.n RSX~.l.lM... tas.k.. comes .in to ex is te.nce through four basic steps.:..
l?,t:"_Q_g_r?m_ is writ ten in a supported
source
language
{MAC:R0-1t,· .. FORTRAt·f '"tv~· or -FORTRAN-··rv=I>Eusr··and sEO!"'eff.. orr·a
f iie=sfrli~'tur'ed voi"ume vi~_- a source language processor •... --...._

The source code is submitted to the applicable transla~or,
an.g a.n.opjecJ: f.il_e is buPt. 011 a file-structJ1r~d .volume.
-.

Th~L.Qbj.ect _file. is submitted to the . Task
Builder, and the
output, kno~n a!;L the task-image fil.e, is .. also... stor.ed o.n....a
file-structured volume.

Finally, via an MCR comma.nd_,_ the task i..s installed
operational system.

into

tJ:1e

Installation involves recording a number of .task parameters __irL___ a
tab.le ·called the system task directoq· {STD) .• .. ____'!'_he
record~d ta?!< parameters include its _nc:tme, length, and volume addrg§s.
An installed task is one which has an entry in the STD. Such a task
is not in memory, nor is it in competition for CPU resources.
It is
simply known to the system and is considered dormant until activated.
syiitem-~re.sfdent

A dormant tas~may_be activated via the MCR Run command, or it may . be
activated i~~~rnally by another. active task which issues a RQ~1$
(Request:)" or RUN$- (RUN.) ·Executive directive._ ~l'l~~ such a reque~t Js
received, a seq~en~e- of events is initiated that allocates resources~
brings the task .in.to_ memory, and places it in active competition with.
other tasks. ... Thus, an installed task is one that is known to the
system, w~i~h is dormant, sigce it is not eligible to compete for
resources.
On the other hand, an active task is also known to the
system, _but it is eligjJ::>le to compete for_.system resources~
Note that the number of installed tasks can,
exceed the number of active tasks.

and

usually

will,

far

The concept of dormant versus active is much more important in a
realtime system than in a batch-oriented system. ~dormant task uses
very little memoryi yet, when the task is needed to service a
realtime event, it can quickly and efficiently be introduced into
active competition for system resources, since most of the parameters
de~cribing
the task, including its volume address, are already
r~sident in main memory.

1-4

INTRODUCTION
1.1

SUMMARY

su_c_cessful ___ Qp~r:at_ion of
opera tor_'~ un9er_~_t_apd__i __i1g_
it~_ facJJ. i __ti_~s_:

The

stru~ture

the
an RSX~t1!'1 __ ~ystem is enhanced by
_of one of RSX-llM's st·r-ucture-s arid- tl:"i"ree - oT

is:

Partitions (both user-controlled and system-controlled), and
the facilities are:
~ultiprogramm~I'lg;

---~J1_ec._kp9 int ing,

_and

'rask cJ:~g tJon, ins t?l i~ t ~on_, _ _?_I}(j ·o-~~-~- ~Y.-~_t ion.

By understanding these terms, the operator can comprehend the dynamic
behavior exhibited by RSX-llM, especially in larger configurations
which exploit its potential.

1-5

CHAPTER 2
PROCEDURES AND CONVENTIONS

2.1

TERMINAL OPERATIONS

. in teqtc t,l.oQ . wJJ:J1 ... RSX-<LlM .... ~.E:!gµJre~ . q.
understand_i1:1g_ of . t:he. following:

Ef~.~~:~.Jj_y~----·-t~sm.ina)

Peripheral device_ nam.i_ng ...aJlCL assJgQJnen t._;

.3.

File na.ming and file specifiers, .and

.4.

Indirect file construction 1see_Chapter 5).

gqmpl~ te

The.RSX:-llM operator p.erJorms a role in two. major areas:
1.

The control of on-line processes, and

Emergency on-line system alteration.

Operator functions fall into four classes:
1.

Initialization Commands
.IJ:LUl;aJJ ?:aU.9!1. includes:
Entering date and/or
I!"!.~_t._?..U in.g

tim~;

tas~s;

Pr~paring mass storag~ media
M.~m1_Q__,r_y_~r.:e::2~rtit. ion. ing, and

S_etting term{nal:
.types;
puffer sizes;
slave status, and
privilege.

for file processing;

·-

Informational Commands
These functions provide the operator with
the structure of the running system.
r_~q_l:J~~t:

'I'Jme and cla te ;
Task names;
~a.rtiil6ri detinitiona;
Symbolic device names and status, and
Logical device assignments.

2-1

a description of
_The _operator can

PROCEDURES AND CONVENTIONS
3.

Control Commands
Control functions include:
Tc:ts_k execution;
Task resumption;
Task abort;
~iii arid -Unfix tasks in memo~y, and
Log icaL device assignments.

During on-line operationi:;, an operator 9-r softwa_i;-e diagnostic
engineer can save the current state of the system foi
subsequent restoration (via the Save command);
also, any
word_ in the system ~an be examined or altered, using the Ogen
Eegister command~ If the Executive Debugging Tool (XDT) has
been generated into the system, control can be passed to it
by use of the Breakpoint command.

2.1.1

Special and Control Characters

Spec iaL cl:lar~<;:_t~_r;_§_ _ c3.re u_~_~d ___ t() c()ri__t:rol __ an opera tor terminal.
Control
are typ_ed while the control key (CTRL) and one .othe:-r~~k'e'y
ar~ simultaneously depressed.
The two control characters CTRL/Z _and
CTRL/U are echoed as AZ and Au. Other CTRL characters, alth6ugh
ech9ed, are non-printing characters ~nd~ therefore, do not appear on
the disp~ay ~edium.

charac:t~rs

The characters used in terminal operations are described in Table 2-1.

2-2

PROCEDURES AND CONVENTIONS
Table 2-1
Characters Used in Terminal Operations
SYMBOL

EXPLANATION

CTRL/C

TY.Eir.!9_. __ ~'!'._~J;.L_<;:___ ···C:::~~-~~~ _. ·-·~-~~ ···"'"~~~.. recognition sequence
d.iscussed bel~w to be initia~e<?: . · "'cTs n·oi: e·choed.

CTRL/I

HQf.J.:zont.al ta,b causes spacing to the next tab ~-~<?l?·
These stops are set by the sof~~are tollowirig every
eighth character position. AI is not echoed.

CTRL/K

Typi..ng <:.'I'RL/;K cau.ses a ve.rtical tab (appears on
__ termina,l as fqu~ line f~eds). AK is not echoed.

CTRL/L

Typing CTRL/L causes a form feed.

·-e·:~fa.t!I' 11-r:i_~_~Je.icfa a~~. :P.tac:.ed. 'on ~he

the

Paging is not done;
AL

g ispl,ay medium..

is not echoed.
CTRL/O

CTR~/O is Uf3.~d .. to.. SlJ.JW.[eS.s__ the.. _ display
of unwanted
output on a terminal.
The subsequent effect of
I enteiing CTRt/b-~epends on the state of the terminal
I when the character is entered. AO is not echoed.

is controlled internally by a single bit called
I CTRL/O
t,
cne
01c. wnen cn1s 01c is sec, oucpuc
I

u1sao~e-oucpuc

......

to the terminal is disabled;
proceed.

when cleared, output can

Initially, the bit is cleared.
When CTRL/O
is
entered, the bit is complemented. Thus, a typical
response of entering successive CTRL/O characters is
to stop and start output to the terminal. Characters
that would have normally been displayed during the
stopped interval are discarded.
If more than one task is sending output to a terminal,
it is essential that CTRL/O affect only the task
delivering output at the time CTRL/O is entered;
control is implemented as follows:

'.!1_h~

i.s~ua_nce

of an At_tac:h. Q_IO directive;

The .is.sua.nce of a. De.tach QIO directive;
The solicitation of inputr and
The ar;_rjv_aJ ..of

un~glic_i~ed

input.

For unattached terminals, the bit is also cleared each
time an output request directed to the terminal is
initiated.

2-3

PROCEDURES AND CONVENTIONS
Table 2-1 (Cont.)
Characters Used in Terminal Operations
SYMBOL

EXPLANATION

CTRL/O
(Cont.)

Given these conditions for clearing the disable bit,
and the fact that entering CTRL/O always complements
the
bit, the following applies at the entering
terminal:
For an attached terminal, output can be stopped by
entering CTRL/O.
The interrupted output stream
will be discarded until the next:
Detach;
Solicited input;
Unsolicited input, or
Another CTRL/O.
For unattached terminals, entering CTRL/O stops
output, but remains in effect for only the current
buffer of output, since, at
the
next
I/O
initiation,
the
system
always
clears
the
Disable-Output bit for unattached terminals.

CTRL/Q

Typing_ CTRL/Q after typing CTRL/S will resume outp~t
sus_p~n_Q.~_C:Lby _t_tie pr:evious CTRL/S.
"Q is not echoed.

CTRL/S

Typing CTRL/S during output suspends additional output
until CTRL/Q is typed. The functions of CTRL/S and
CTRL/Q are convenient when using a display terminal
which transmits at rates above 600 baud. "s is not
echoed.

CTRL/U

Typing_CTRL/U prior to typing a line terminator caus~§_
the previously typed characters to be deleted back to
the default prompting symbol">". The system responds
with a carriage return and line-feed so that the line
can be retyped. Echoed as "u.

CTRL/Z

A break _c_haracter indicating___ e_nq-:-()f-_file. I t is used
as a signal to system tasks, such. as MACR0-11, PIP,
and TKB, indicating that the user is finished and the
subject task may exit. Echoed as "z.

ESC

The ESC_c_haracter represents_ the ESCape or ALTMODE
key.
Entering
this line terminator leaves the
carriage (or cursor) of the terminal intact. It-has a
specialized meaning to MCR when terminating a command.
It will suppress the default prompt from MCR commands
when they complete.
However, an ESCAPE character
terminating a Run command produces special results
(see the description of the Run command for a detailed
explanation). ESC is not echoed.

2-4

PROCEDURES AND CONVENTIONS
Table 2-1 (Cont.)
Characters Used in Terminal Oper4tions
SYMBOL

2.2

EXPLANATION

Typing the RETURN key will end line input and cause
the
carriage (or cursor)
to return to carriage
position 1.

The back slash symbol is used to delimit characters
deleted by typing the RUBOUT key. Typing a RUBOUT
deletes the last character typed. Several contiguous
characters
can
be deleted by typing successive
RUBOUTs.

TERMINAL CHARACTERISTICS

Th~re are tY/O_types qf_MCR commands:
privileged and non-privileged.
Non-privileged c9mmands may be invoked at any terminal, where~s
privileged commands may be invoked only at privileged terminals..
The
privileged characteristic is associated with a given terminal at
system generation; subsequently, any privileged terminal can, via the
MCR Set command, establish any other terminal as privileged or
non-privileged.

CAUTION
Privileged commands can destructively
interfere with system operation and with
themselves. Caution is urged when more
than one privileged terminal is present
on the system.
Non-privileged commands are available to any unattached* terminal in
the system.
More than one terminal may be in use at a time, and all
MCR non-privileged commands are available to e~ch terminal.
A
terminal may be attached to a task other than MCR, in which case, all
input or output is directed to or from that task.
Thus, one person
can run PIP at one terminal, while another runs MACR0-11 at another
terminal; still a third may be controlling the system using MCR
commands.
This capability is restricted only by memory availability
for the various tasks.
Commands are serviced by either:
1.

Independent tasks (such as Mou_nt and Install), or

The MCR D.ispatch~r an(l

~~-t

of._ o-vecbys.

* Attached terminals are those dedicated to a single task.

Only
task to which it is dedicated can perform I/O to such a terminal.

2-5

the

PROCEDURES AND CONVENTIONS
Whenever a 1 ine is __e_n t_ered _ _ from an unattached terminal, the__ MCR
Dispatcher reads the command line.
I t then takes the first thr-ee
characters of the ijn~ (these are unique and form a part o{ --the
command) and searc:ties a table of commands processed by overlay_~_!_ If
the MCR Dispatcher -flrids the command in this table, it loads -the
overlay to process the command.
If it does not find the naro~--' it
prefixes
(three periods)
to the command and searches the system task directory (STD) for a task
by__ J;h~t name (e.g., ••. MAC), as described in the following paragrapns.
I f __the MCR Dispatcher finds
the task and it is not active, the
Dispatcher will request the Executive to run the task. If the task is
active or not in the system, the Dispatcher will search for the task,
as follows:

<command-name>n
where n is the terminal unit number from which the command was issued
(e.g., MACl). If the Dispatcher finds the task and it is not already
active, the Dispatcher will request that the task be run.
If the
Dispatcher
does
not
find
task
<command-name>n,
but
task
... <command-name> is installed in a system-controlled partition and is
not checkpointable, the Dispatcher will create a task by the name of
<command-name>n and request it to be run. This task will be identical
(uses the same J:a.sk:-:_image file) to the parent task ••• <command:-name:>-.
This feature is extremely useful in multi-terminal systems used for
program development.
At the time the Dispatcher makes the request, it also sends the
complete command to the task it just requested. This scheme makes it
possible for users to add (or delete) operator services to meet their
application needs.
For example, an installation could write a routine which displays the
day of the year using the internally stored current date. If the task
is called DAY, the user would build and install it as:
... DAY
Then the user-issued command:
>DAY
will result in task initiation.

2.3

TERMINAL INPUT CONVENTIONS

An unattached operator terminal waiting for input is in one
states:

three

Ready to accept unsolicited input;

Ready to accept solicited input to MCR;

Ready to accept solicited input to a task other than MCR.

2-6

PROCEDURES AND CONVENTIONS
A terminal ready to accept unsolicited input displays the character:

>
on the terminai. This single-character display on a terminal is
referred to as the default prompt. Irt_EU~--~nter~___f_ol].o~!.D.9 __ ?___ Q_~Jc3.1JJ~-p,;pmpt _i_~ .?.i_wP.:Y~.--i~_pJJ.~-g~Lcl:~_;:ec::~ed to MCR, _a11d . . the. MCR Dispatcher
ide_QJjJ_!_~-~J _?!}ajy_z~-~-L ...'!Q_~---~~-~-po_n~ S. t§:- S~bscju~n t inp~l ~
Whenever CTRL/C is entered as the first character on a
a\o.i~_t:::~n.<i in_P,u_t",_ -r.iC:R _i_s_ ·e-xplic i t"ly in i tfa ted, --and -fhe -p-rompt:

terminal

MCR>
app~ars

on_the dis~lay medium.

Any input entered following the

MCR>
prompt is explicitly directed to MCR. In the case of the default
-b6wever,-another task could internally solicit input; if the
soliciting task did not itself issue a prompt, then input (though
thought to be directed to MCR} would in fact be sent to the task most
recently soliciting input. The default prompt merely indicates that
MCR will field unsolicited input.

~rompt,

To avoid erroneous input, any task intending to solicit input should:
1.

Attach to the terminal;

Prompt with a p~ope~ly formatted identifier (i.e., tsk>), and
then

Solicit input.

Once a task is initiated _by MCR, it will generally prompt with:
tsk>
n~m~~
All DEC system tasks are
-~a~k
it is advisable that user
identified with a 3-character prompt;
programs follow this convention. Wh~.n ?_ _t(i~~---Ef'C?.rn.P~-- h_9_s_ .. bee11 _ issued
and is then immediately followed by a read, the next line of input is
directed tq t~e soliciting task.

w_l}_~J~__ J:_§_is___ j,_i::;. ~--1-=9DE._r:~c ter

When a task is sending characters to a terminal without attaching to
it, the output can be interrupted by entering any character. At the
completion of the current I/O operation, the character will be echoed,
and the operator can issue ·a corrimarid -t6 MCR.
For attached terminals sending data, a similar interruption can be
by entering CTRL/C. Then, as with unattached terminals, at
~he completion of the current I/O operation:
~chieved

will be_ -~-!-~J~_layed.
These conventions enable tasks delivering
conveniently.

2-7

output

interrupted

PROCEDURES AND CONVENTIONS
MCR commands are usually initiated as unsolicited input and are
terminated by typing a carriage return;
the Open command is an
exception, because it is terminated by typing the ESCape key. If any
other command to MCR is terminated with an ESCape character, MCR will
not respond with the default prompt.
Typing CTRL/C as the first
character in a line, or anytime when a terminal is sending data, will
always obtain MCR's attention,
even
for
attached
terminals.
Unsolicited input, except CTRL/C, will be rejected if the terminal is
attached. All examples in this manual use the default prompt.
If a task prompt is awaiting input, the sequence:
CTRL/C

(Carriage Return)

will obtain MCR's attention. Following a single input line to MCR,
the original task whose prompt was overridden is again given control
of the terminal.

2.4

START-UP PROCEDURES

After performing the applicable start-up procedure (see following
sections), the RSX-llM system message is then displayed at the
computer console terminal. At this point, the operator should enter
the time and the date, and establish his user identification code
(UIC) via the MCR Set command. The step-by-step start-up procedure is
carried out as described in the following sections.

2.4.1

Start-Up Using BM792-YB Bootstrap ROM

The following
bootstrap ROM:

procedures

are

used

starting

the

BM792-YB

Depress HALT.

Set the console switches to 173100.

Depress LOAD ADDRESS.

Enter the address of the load device in the console switches:
RKll Disk

177406

RFll Disk

177462

RPll Disk

176716

TCll DECtape

177344

Lift up the HALT key.

Press START.

The start-up sequence in
console terminal.

section

2.4.6

2-8

then

displayed

the

PROCEDURES AND CONVENTIONS
2.4.2

Start-Up Using MRll-DB Bootstrap ROM

procedures in starting up the MRll-DB bootstrap ROM:

Use the
1.

Depress HALT.

Enter the address of the load device in the console switches:
RFll Disk

173100

RKll Disk

173110

TCll DECtape

173120

TMll Mag tape

173136

RPll Disk

173154

Depress LOAD ADDRESS.

Lift up the HALT key.

Press START.

The start-up sequence in
console terminal.

2.4.3

section

2.4.6

then

displayed

the

Start-Up Using BM873-YA Bootstrap ROM

The following
bootstrap ROM:

procedures

are

used

starting

the

BM873~YA

Depress HALT.

Enter the address of the load device in the console switches:
RF ll/RH70 Disk

, ..., """I'\ I'\"

.1/.JUUU

RKll/RH70 Disk 173010
TCll DECtape

173030

TMll Magtape

173050

RPll Disk

173100

RCll Disk

173144

KLll/DLll

173210

TAll Cassette

173230

PCll Papertape 173312
3.

Depress LOAD ADDRESS.

Lift up the HALT key.

Press START.

2-9

PROCEDURES AND CONVENTIONS
The start-up seqence in section 2.4.6 is then displayed on the console
terminal.

2.4.4

Start-Up Using BM873-YB Bootstrap ROM

To start up the BM873-YB bootstrap ROM, use the following procedures:
1.

Depress HALT.

Enter the address of the load device in the console switches:

---· ·-·-------····-·· ·---

RH11/RS03/RS04 Disk (unit 0)

173000

RH11/RS03/RS04 Disk (unit in switch
register)

173002

RKll Disk
(unit 0)
..

173030

RKll Disk (unit in switch register)

173032

TCll DECtape (unit 0)

173070

TMll Mag tape (unit 0)

173110

RFll Disk

173136

RH11/RH70/TM02/TU16 Magtape (unit 0)

173150

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

~Cll

Disk

173212

RH11/RH7u Device Combination (unit zero)

173230

RH11/RH70 Device Combination (unit in switch
register)

173232

RH11/RH70/RP04 Disk (unit 0)

173320

RH11/RH70/RP04 Disk (unit in switch register)

173322

RP11/RP02/RP03 Disk (unit 0)

173350

RP11/RP02/RP03 Disk (unit in switch
register)

173352

KLll/DLll Console Terminal Reader

173510

TAll Cassette (unit zero)

173524

TAll Cassette (unit in switch register)

173526

PCll Papertape Reader

173620

)_._____ I_)~J?:C"_e~.f>

LQ~D

Al)DRESS.

3a. For units other
register.

than

zero,

2-10

enter

unit

number

switch

PROCEDURES AND CONVENTIONS
4.

Li f_t -- ~p_ __ the HALT key.

Press START.

The start-up sequence in
console terminal.

2.4.5

section

2.4.6

then

displayed

the

using

the

Start-Up Using M9301-YA or M9301-YB Bootstrap ROM

The M9301-YA or M9301-YB
following procedures:

bootstrap

ROM

started

Press the BOOT Switch.

In response to the "$" prompt on the console terminal,
one of the following:
DB DK DP DS DT DX CT MC MM MT PR TT -

enter

RJP04 Disk
M9301-YB only
RKll Disk
RPll (RP02/03) Disk
RS03/04 Disk
M9301-YB only
TCll Dectape
RXll Floppy Disk
TAll Cassette Tape
Mixed Massbus Device
M9301-YB only
TM02/TU16 Magtape
M9301-YB only
TMll/TUlO Magtape
PCll/PRll Paper Tape Reader
KLll/DLll Console Terminal Reader

The two alphabetic characters may be followed by an optional
single octal digit for bootstrapping from units other than
zero and terminated by a carriage return.
The start-up sequence in
console terminal.

2.4.6

section

2.4.6

then

displayed

the

Start-Up Display Sequence

If the system being bootstrapped was built with a different device
configuration than the current host, a series of display lines appears
on the console in the form:
DEVICE ddnn:

NOT IN CONFIGURATION*

where:
dd
nn

device name.
unit number.

* Devices not in the configuration are declared off-line and the
display OFFLINE is appended to these devices as part of the output of
the Devices command.

2-11

PROCEDURES AND CONVENTIONS
Then the system displays:
RSX-llM <version-number> <base level> <memory size> [MAPPED]
>RED ddnn:•SYO:
>MOU ddnn:
>@ [ 1, 2_] STARTUP
where:
<version number>

- the release
version
number,_ e.g.,
Release 2 of RSX-llM is V02. --- .. - - -----

-_ T_h_e software
development
group
at
Digital periodically brings together new
versions
of
the
softw.are
under
development.
Internal groups may use
this
software
to
ensure
correct
operation and to build new software.
These development milestong5_9_re called
base levels.
Release ?~f RSX-llM is
hase level BL12.

size>

- the memory size (in the form of nn_nK} of
the machine on which the system_was
bootstrapped.

<m~_mory

[MAPPED]

- MAPPED is displayed for sys tE;Jns _buU t to
use the memory management unit.

- Device name.

- Unit number.

[l,2]STARTUP

- The file specifier for the indirect
command
file
which
is
invoked
automatically at bootstrap time
and
which
contains
user
commands _for
initializing the bootstrapped system.

The system is now ready for operation. The RED and MOU display are
internally-generated
Redirect and Mount commands.
The Redirect
command establishes the load device as the system device SY:, and the
Mount command Mounts the load device as a Files-11 volume.

2.5

ERROR DETECTION AND HANDLING

E(.£9-f_ de tee ti on and reporting are provided for
the various MCR
commands. When an error is detected, an appropriate message (prefixed
by the name of the command) is displayed at the entering terminal.
Messages which are uniqu~ t6 a given command are listed with the
discussion of t~e command in Chapter 4. All error messages are listed
in Chapter 6 in alphabetical order.

2-12

PROCEDURES AND CONVENTIONS
2.6

COMMAND STRINGS

When

~yping

MCR command strings, the following conventions apply:

l . ____CQ_mmc:iJld strings _axe _Jeri:ninq.t:ed eUher by

a carriage return
(<G_R>}
or _ESCap~_ (~ES_9>L ke.Y depression. ___ J_L _ _t.h~__ command is_
terminated by a <CR>, a default prompt will be displayeq_ on
.c.ompl_etion of the command. _If the command is t_ei:-!f!inat_~_d by
an <ESC>, the default prompt will not be displayed ___when __ Jh~
co~rn_and
completes.
_O_e_faul t prompt _ suppr_es_sio_n __ i_s__ used in _
c__g_njunction with a special feat_ure of the Run comrnp_nd. ThtJ_s,
if the following_ ~~guence is ~n~ered:
>RUN TEST <ESC>

no_ default prompt wiil be displayed_ when the Run command
c9_mpl_e,_tes ______ ~h-~- re,qq~e~ __to i11itiate the -task TEST!__ ____B.A.t.h_E?..f.t __?_§
a feature of the Run command terminated by an ESCape aQt,ion,
the default prompt will be displayed when the ta~k TEST
g_x~ts~
T:tlL_s J~_~J_P.!'."~ e.na_bles t.he operator _t.od_istinguish when
a
task, wh_ich p_roc]uces no output on th_e_ - te-rmii1al, has
__(:_OJl!P_le ted.
2_.__A_ __cQm.rn_and

mµsJ:_be _se_parated from its parameter_s by
+ o_n_e__ tab_._ .

least

g11_~-~g_c_~-- o

I f an err~n is _discoy~_:r.-e.~_ whi_l_e
entering a command string
prior to typing a terminator, the line may be delete~ back to
the prompting character
(>}
by typing CTRL/U
(formed by
-~J_II}_ u_ l_taneou_sly _ pressing the CTRL and u characters) .
RUBOUT,
Which is echoeda~_ i3._ __ b_?Cksl.a._~h (\)..1 may be U-sed to delete the
last character or contiguous characters typed. The first
RUJI6U·r·--fyped will cause \ and the character delete<r·-10 -·-he__ _
e9.ltQ.~_9.
Further RlJBOUTs cause only the deleted character to
b_g___~GD9~_Q_'!_ _ The next non...:RUBOUT character entered will cause
___<=! __ .. ___ \_to
be echoed, along with the character entered.
StJ.QJ:>_~_quex1 _ t; ___ n9n.-Rt]BOUT
characters
(with
no
intervening
RUBOUTs} are echoed. Thus:

First RUBOUT
Second RUBOUT
Third RUBOUT

~~First non-RUBOUT

MISTKAE\EAK\KE
l-~
-f

Produces:
MISTAKE
4.
to

An~

number of alphanumeric characters may be concatenated
first
three letters of the command and before its
a~guments or command string terminator
(carriage return or
ESCape}.
Oog _Q( __ more spaces or _taps must separate the
command name from its operands. Spaces or tabs are useful in
improving the readability of printed copy. For example, the
the

2-13

PROCEDURES AND CONVENTIONS
Install command could be invoked to install the task FAULT by
typing:
~NS

FAULT
or

INSTALL FAULT

2.7

PERIPHERAL DEVICE NAMING AND ASSIGNMENT

During system generation, all peripheral devices attached to the
system~ are
explicitly described.
To simplify the naming of ~~h~se
devices, :each device is given a unique name which is used in all
commands referring to the device.
Al)_ peripheral dey ices are referenced by using a 2-charac ter ASCII
device name __ and an optional 1- or 2-digit octal unit number (for
example, DKO: and MTl:). The combination of device name and unit
identifier is referred to as the device-unit pair or simply the
device-unit. If the unit number is omitt~d, the system uses unit 0 by
default;
thus, LP:
indicates line printer O. Table 2-2 lists the
device names supported by
RSX-llM.
The
hardware
controller
designations appear in parentheses.

2-14

PROCEDURES AND CONVENTIONS
Table 2-2
RSX-llM Peripheral Devices
PERIPHERAL DEVICES

DEVICE-UNIT

Analog-to-Digital Converter {ADOl-D)

ADnn:

{AFCll)

AFnn:

Card Reader (CRll)

CRnn:

Cassette (TAll)

CTnn:

DECtape (TCll)

DTnn:

DISK (RH11/RH70/RP04}

DBnn:

(RFll}

DFnn:

__ (R!51~)_

PKnn:

(RPll}

DPnn:

(RH11/RH70/RS03/RS04)

DSnn:

(RXll)

DXnn:

~_r1_(j__~_~_t_!:" ial

~_nd

Control _sy~_tem Local

ICnn:

Remote __(__;r_~~lJC.R'.:"_UJ

Laboratory Peripheral System (ARll)

ARnn:

(LPSll)

LSnn:

Line Printer (LSll/LPll/LVll)

LPnn:

Magtape {RH11/RH70/TM02)

MMnn:

(TMll/TMAll)

MTnn:

Paper Tape Punch (PCll}

PPnn:

Paper Tape Reader {PCll/PRll}

PRnn:

Parallel Line Interface {DAll-B)

XBnn:

Synchronous Line Interface

{DLll-E}

XLnn:

(DPll}

XPnn:

( DQll)

XQnn:

( DUll)

XUnn:

Terminal (DLll/DHll/DJll)

TTnn:

Universal Digital Controller (UDCll)

UDnn:

2-15

PROCEDURES AND CONVENTIONS
Table 2-2 (Cont.)
RSX-llM Peripheral Devices
DEVICE-UNIT

PSEUDO DEVICES
Console Listing

CL:

Console Output

CO:

Network

NT:

Pseudo Input Terminal

TI:

System Default Device

SY:

Programs_ co_mmunicate with peripheral devices through logica~ unit
(LUNs).
By relating a LUN to a device-unit, input/out~ut
issued to that LUN will be directed to the device represented by the
device-unit designation. LUNs.. are as_soc_ia ted with device-units at one
of three stages in the t~sk creation process:
numbe~s

2.7.1

l.~

During task build;

Via an MCR Reassign
installed, and

At task run time via the Assign LUN Executive directive.

command

after

the

task

been

has

Device Reassignment

The device assignment process effects a name connection. It relates a
program name (LUN)
to a physical device-unit;
nothing more is
implied. If the device-unit has been generated into the system, -the
name connection will succeed. Success, however, does not necessarily
mean the device can be immediately accessed.
The device may, for
example, be attached to another task, or it may be physically
inoperable;
neither of these conditions will prevent a
valid
assignment from occurring.
Successfull access can subsequently be
made when the device-unit becomes unattached or the malfunction is
corrected.

2.7.2

Device Redirection

The operator, in practice, does not often reassign devices.
more common operator function is that of device redirection.

A much

Redirection causes I/O directed to one device-unit to bypass the
original name connection and instead be directed to a different
physical device-unit. Physical device redirection is a system wide
phenomenon. Thus, any task referring to a redirected device will have
its I/0 redirected to the target device.

2-16

PROCEDURES AND CONVENTIONS
Suppose, for example, that a task has LUN 1 assigned Lv TT:.
Assume
during the task's execution that TT: becomes inoperable, making it
impo_§§.:ible for the task to continue. The operator can redirec_t _I/O
destined for TT: to TTl:. This redirection remains in effect until
another Redirect command changes it. Redirection can occur to any
l~~~l.
Thus, if TTl: in th~ above example becomes inoperable, I/O
can be redirected to TTS: or any other appropriate device.
Note

that

redirection

does

not in any way alter the original
assignment.
If the task is removed from
memory and then subsequently
re-activated,
and
the
internal
redirection is still in effect, the redirect path will automatically
hold for the task.
LUN~to-physical-device-unit

2.7.3

Pseudo Devices

The redirect prpcess usually inyolves _five pseudo devices:
CO:

_____u~_ed _for_ c_onsole output

CL:

Used for console listing

NT:

Used for network communications

TI:

Used for terminal input

SY:

Us.ed

,3_S

t_ti_e. _sys~em device

Virtually every task in the system, including system tasks, has a need
to communicate with one or more of these pseudo devices. Unlike the
real devices in the system (e.g., DKO:, TT3:, and LPl:), pseMdQ
devices are so named because they do not correspond to real devices
UI!_~iJ tl1ey .. a.Ee _r~~J_rected.
In... a. gbz_e_n____ tazk, LUN 1 _may be assigned to CL: .
This
task;
in
del.iv.e.Li.n.g output to LUN 1, wants the data sent to the console listing
d~yjce;
the task itself is not concerned with th~ particul~~ device
in the system actually serving as the console listing device.
The. __operator can change the device to be used as the console 1 is ting
device by redirecting ~L: to another device-unit (e.g., from a line
pr:_inter to a terminal)_. ____The effect of th_is___r_e.qire9tion _is to cause
all I/O di~ected to CL: to go to the terminal, rather than to the
line p~inte.~. Note that the tasks directing I/O to CL:
are unaware
of this change and are not altered in any way.
When a pseudo device-to-real device redi~~~t connection is made, the
pseudo device assumes the privileged/non-privileged attribute of the
real device.
Thus, if CO:
is redirected to TTO:
(which is
privileged}# and then subse.quentl~ redirected to TTl:
(which is not
privUeqeq}, __ CO: _lose§ its privileged status.
Normally, CO: is redirected to the main operator's terminal, and CL:
is normally redirected to the line printer. The psuedo device TI:
(terminal input/output) is the pseudo device most frequently used.
When a task is initiated via an MCR Run command, the terminal from
which it is started is established as the task's TI:
terminal.
The
initiated task can communicate with the user via the TI: pseudo
device. If a task is initiated internally via a Run Executive
directive, TI: is defaulted to CO:.

2-17

PROCEDURES AND CONVENTIONS
2.7.4

Logical Devices

~99 ical

device names may be assigned to physical dev ic_es__b_y. me.~m§ of
tl1e MCR Assign command.
A log ica1 device name c.on_ais.t.~--- _9.f" a
2-character ASCII name and an optional . _1-:- QJ.: . ... i""." .. dig_t~ ....Qct;_~_L __ unit
nuniP.~.r-~ ..
Any reference to a logical device will be mapped by-tbe
system into the physical device to which it is assigned.
There____ ~g_e
t.w.o types of logical. device assignments: . lo.c.a.l .and ..g.l_o_bal. __ _bg_~al
logical device assignments are in ef feet Of1lY .for tasks. in it ia t.ed from
the entering term inai." . That is~ iocaI Togical d"ev ice. assTgnmen t-s. are
associate.cl with a particular terminal.
Global
logical
device
assignmer"i"ts ·affect a1T tasks running in the sys tern.
The logical .Q.~yi_ce table is always searc.hed by_ the systeun .P.eJQ_f~- the
physical
device
ta.ble.
This precedence allows logical d.evJ_ce
assignments to over~ide physical device
names.
Local
device
assignments override any global ass{gnments, and global assignments
override physical device names. Similarly, identical local logical
device names may be used at different terminals ~ithout interference.
This feature, which is a system generation option, allows a programmer
to write a program without concern for the device ac~ually used at run
time. He may reference a logical device name and assign it to the
desired device prior to run time. For examples of logical device
assignment, see the description of the Assign command in Chapter 4.

2-18

CHAPTER 3
FILES AND FILE SPECIFIERS

3.1

INTRODUCTION

This chapter is not mandatory reading for operators. It is included
to add depth to the operator's understanding of files, file naming
conventions, and file,protection.

3.2

FILE FUNDAMENTALS

Files a.re__ o..wn_e_e::-nam.ed _ar_eas on direct _ CiCcess _vol Ullles.
Volumes are
c;}a ta-:~-~r ~y_ir.ig __ . . I1l~~J9_--~h~~-~--~~--a~~ -be- ifie --Th~_s--~Fr~-cfure--a-nd
the... ___so_ftw_are which suppqrts it is call~d flles-11., _ In R~X:-llM; disK·s
and DECta_pes.. __ 9o~pf-is_e- - _-_th-~ ---s-uppor ted --v-o"fume--'ty"f,es-_. -DECtape - riiay---beei ther file structured or contain a data format supported by the File
Transfer Program
(FLX).
Cassettes
and
magtapes
are
not
file-structured volumes; the structure on these devices is supported
by the File Transfer Program (FLX} or user I/O.

str-uc-tu-rea·:--

F.Jles benaye m_uc_l'l ljkg devices in that t_ask I/O may be directed to
them. _fl9W~Ye~,- _sine~ a file is just a portion of a r_andom access
v9_.L1Jme; _files can be created as long as space for .them . exists __o_n _____ the
volume.
_Thus, they are much more dynamic and flexible than. physic.al
_d.~J_c;e_...§_,
Due to the fact that more than one programmer's files may
exist on the same volume, conventions are required for naming the
areas and techniques for protecting files belonging ~u different
owners from being altered, except by the owner or an other user with
the owner's permission.
Filenames are made unique by use of a ~ser identification code (UIC).
A file cannot he accessed unless the- 'uit un~er ~hich it is st6t~d-Ts
known. Knowing the UIC does not guarantee access, howe~er, sin~e e~~h
file __ex.is ting under _.a g_iven UIC c.an be ind ividual.l_y pro tee ted.
Individual file protection is discussed in Section 3.2.1.
Associated with each UIC is a user filedirectory (UFD). The UFD is a
-fiie --w-hiCh contains the riames' of all files currently existing under" a
given UI_C. 'A _Uf'._D_ is itself a file belonging- to a- specl.fic user - and
has all the characteristics Qf ~ fil~, including the manner in which
access to it is granted.
UICs are specified in the format [nnn,nnn]; nnn is a 3-digit number,
usually represented in octal, having a range of 0 th~u 377{8). -The
first number in the pair is referred to ~s _the group numberT--the
second, the member nurol::>~i;: ~ _ 'T6-eTimTna~t·e· r-epe-t it i ve entry of UICs in
command strings, a default UIC can be established for each terminal in

3-1

FILES AND FILE SPECIFIERS
the system, either at system generation or dynamically from any
terminal with the Set command. When a command requiring a UIC is
entered from the terminal, and the UIC is not explicitly specified,
the default is used.

3.2.1

File Protection*

Four lypes of file actions exist:
~ead_;

Write;
Extend.!

~nd

Delete
.
- -•
-~""'····"··'

The users that are
f o u_~__ ~~G!-~-~-g or i es :

allowe~

to perform these actions are

divided

System -- All system software (all tasks with a group
10(8) or less),

number

into
of

Owner

The user under whose UIC the file is stored,

Group

Any user whose UIC has the first three digits in common
with the owner,

World

Any user not included in the three categories described
above.

When protection is specified, any combination of the four actions
(read, write, extend, delete) can be assigned to each of the f_g_1,1r
groups~
For example, the system and the owner can have read, write,
extend, and delete privileges, the group can have read privileges, and
the world can be denied access to the file.
In RSX-llM, the basic protectable entity is the file.
The UIC is
required to obtain the opportunity for accessing a given set of files.
But each file stored under a given UIC is individually protected.
A~cess to a specific file, given the UIC, is established by the owner.
The owner can prevent access to each of his files, and he can exfend
different access rights to the four classes of users described above.
The owner of a file establishes access privileges to these
classes in one of five ways:
1.

four

user

At volume initialization time.
The Initvolume command allows the user to specify
~ile protection for all files created on the volume.

default

* Volumes are protected from illegal access by non-privileged tasks if
they have been mounted with the MCR Mount command.
command for additional details (Section 4.3.2).

3-2

See the Mount

FILES AND FILE SPECIFIERS
~----·-T-~~---~~R

User __ f.i}e Directory command.

ThJ.~L c:=q:rnma,nd ___~i:; t;a,blJshe s a~ces::l r_ig_b.t~ to the_ .U_fD f Ue _ only._
Often, a user will permit access to his nFn. but will
restrict access to the files catalogued in the UFD.

3_.__ ____ p_p:~_.. fH_e ___ l1 t. PJ_~y_.
PJP_ has _ _c;in __9p_t,_ i_911 wl)_iQh. enables~ t,h_e
E!" i_~_(~_ e~~?_. o-~-- h ~-s f i 1 es •
4.

ow_l'ler

alter

access

Within a user task.
Using the WRITE ATTRIBUTES Files-11 I/O function, a user
w.rl,t;:g __ Q_~w- ?C:..~.~e-~. _p_rqtection attributes ··10 Tne··5 -·he ·oviri."s.

can

At mount time.
In the Mount com_m_apd, t;:.h~__ us~r __ !l)_a_y .. ~p_e_ci~y the default file
protect.Jon
t_o _be given files created after the- mount
operation;
this . specff'fcafion .... o\fef[i"aes·--·-nnn· ... ~_pe~:i!=·ie-a·
duri?g volume initialization.
-·

3.2.2

File Specifiers

Any com29n~~t, 9f RSX-llM which has a requirement to refer to files
does so via a standard command string with the following general
format:
outflespcl,
••• outflespcn
......__...
. '"~

= inflespcl, ••• inflespcn

Outfle!?PC::_ t~ __ 9:n output file
~pee-~~ i~ r _.__ _

~ee_cif~er ~and

inflespc is an

input

file

Any number of specifiers are possible, the actual number being
determined by the task which will use the command string. In no case,
however, may the total length of the command string exceed the maximum
line length (80 bytes).
Each file specif~~r
format: - ·
·

(w~ether

ipput

output)

has

the

following

_<l~v.: .[g,mJf_il~11ame ~ t;:.ype ;ver sion/swi tchl ••• /swi tchn

where:
dev:

(g_,m]

The physical device-unit on which the volume
contc;i.i.IJ.JQg .. _th_e_ desire(l ~ile is mounted, for
example, DKO: or DTl:. The designation consists
of a 2-character ASCII name followed by an
optional 1- or 2-digit octal unit number and a
colon.
The user identification code {UIC) associated
the user file directory containing the
desired file. The UIC consists of a group number

~ith

~nd a member-~u~ber.

3-3

FILES AND FILE SPECIFIERS
filename

~De name of the file.
In RSX-llM, a filename can
be up to nine alphifri'llineric characters in length.
The filename and type are always separated by a
period (.) .

type

A_ means of disting~ishing ~mong various forms of
.one.____ file. For example, a source FORTRAN--p-rogram

might be named COMP.FTN, while the object code
associated with that program might be called
COMP.OBJ. The use of file types is discussed in
section 3.2.5.
The file type and version are
always separated by a semicolon (;).
version . .

An octal number used to differenJJq_~e among
v.a.t.i.ou.s versions of a file. For example, when ·a
file is first created, it is assigned a v~rsion
number of 1. If the file is subsequently opened
for editing, the original file is retained for
backup, and a new file is created with the same
filename and type, but with a version number of
2.
The version number is in the range 0 thru
77777.

/switch

A 2-character ASCII name identifying a_ switch
option.
The switch itself may have three -'forms.
If the switch designator, for example, is SW,
then:
/SW
/-SW,
/NOSW

Sets the switch action;
Negates the switch action, and
Also negates the switch action.

In addition, the switch identifier
may
be
followed by any number of values. The permitted
values are ASCII strings, octal numbers, or
decimal numbers. The default for a value may be
octal or decimal. Values which are terminated by
a decimal point are explicitly decimal. Values
preceded by a pound sign (#) are explicit octal.
Finally, any numeric value may be preceded by a +
or - sign; plus is the default notation.
If
explicit octal ( #) is used, the sign (if one is
used) must precede the # {pound) sign.
The
following are valid switch specifications:
/SW:27:MAP:29.
/-SW
/NOSW:-#SO:SWITCH
The number of permissible values and the switch
interpretations themselves depend entirely on the
particular task to which they are directed.

3-4

FILES AND FILE SPECIFIERS
3.2.3

Volumes and Files

The following discussion of volumes and files is intended as a
structural sketch of the procedures needed to create, name, and access
files. Details appear under the discussion of the associated MCR
commands.
In the previous section, filename strings were discussed. A filename,
however, refers to a file on a file-structured volume, and several
steps are required before such a file can actually be created and
subsequently referred to by name.
Volumes are data carrying media which can be file structured.
In
RSX-llM, disks and DECtapes comprise the supported file-structured
volumes.
B.e.£c.r.a ..th.e RSX"'.'"llM __ file system cna access or

create a file from a
U§er_:-_s_µppJied _ fUen~me, the voJ.JJrn~ rnus_t be initialized, it must be
mo.unt.ed, a.nd a user file di.re.ctory __must be created._ T.he_se.thr_ee_s.teps
a.r..e.. ac.c_om_plis.h.ed_ by_ the MCR Initvolurne, Mount, and User _F_i.Je ___pir_e~_tory
C._2~mands;
all three commands are discussed in Section 4.3.2.
A _fila-::st.cu.c.tured .vo.1-ume is organized such that files contained on the
volu_m.__g_____~_g_I}____Q_~---I~-~J_.t~_yg_fl_J?Y_ ~l)~jf ___ ri_a.~~~~ _ Directories are used to map
n__aJl)_es_ t;o _ _tl}e ___ pJ1y_sic_?t. J,9c_a,tions_ ory_ the volume where the referenced
fil_e
is _s_t.o.red.
The Initvolume_ command establishes the basic
st~uctural framework for these file directories.
A volume which has
not been processed by the Initvolume command is defined as a foreign
volume; such a volume cannot be processed by the RSX-llM file system.

Each .owne_r having a_ unj.que UIC should have a directory file of all the
f ilea_ cr.eat.ed __unde.r.,_hi.s....UI.C. ___No other user of the system can access
these files unless they know the UIC and have access privileges to the
file. The User File Directory command establishes this directory file
for a UIC. Once the directory file is established, the owner can
create, reference, or delete files specific to his UIC.
Fina):Jy,._ a!}__y __ yolJJ_m~--~p __q_~_ (3._cc:.e_EL§e_c;l_ l:;>_y _the _file

system must be made
kno_w.n_ tq_ _ the 5ys_te_m via the Mount command. Note that unmounted
volumes can be accessed directly by user tasks, which is often a
requirement in time~critical applications.
Th_1,1_s, J::>eJ_o_z::_ e ___ a f:ilename can be used to access a file, the volume_ which
is to contain the file must be initialized, the volume must be
iden£THe:d t-0:-.ihe :s.y.ste:m~~~via~ -the Mount c-ommand,. and. a user file
directory \VhJ_c:::_h wJ_U _c_Qntain th.e name of _the file_ must be_ created.
Volume in_i Ual.izatio.n ..and .us.er-. file directory creation need only be
per formed once _ fo__r __ a vol.ume; mounting, however, must be d_one after
each boo ts tr.ap of the syste-m.

3-5

FILES AND FILE SPECIFIERS
3.2.4

Defaults in File Specifiers

Any of the elements of the file specifier canbe default~_QJ __ ~xcept the
f_p~~§~_~*.
The. system uses defaults as specified below:
--STRING ELEMENT

3.2.5

SYSTEM DEFAULT
which

the

dev:

SY:. -- The device-unit on
system volume is mounted.

[g ,m]

The default UIC
specified
for
each
terminal during system generation. The
UIC default may be changed dynamically
with an option of the MCR Set command.

filename

No default. Must be specified explicitly
or
implicitly (using an asterisk) as
described in Section 3.2.6.

type

A user-meaningful file type. For example,
if a list file is created, the system
assigns it a file type of LST in the
absence of a user-specified type. See
Section 3.2.5 for a list of default file
types.

version

For input files, the most recent version
number. For output files, the next higher
version number. An exception is the PIP
file delete function, which require~ an
explicit version number;
this feature
prevents
the
user from inadvertently
deleting the latest version of a file.

/switch

Switch defaults are established
individual
system tasks which
them.

by the
require

Use of File Types

RSX-llM has a standard set of file types which are used when the type
is omitted from a file specifier. While the user can assign his own
file types, system operations are facilitated if use is made of the
file types presented in the following table. These mnemonic types are
used by all DEC-supplied software to reflect actual file contents.
FILE TYPE

':I,
F

MEANING

CMD

A file containing a list
commands (indirect file).

DAT

A data file, as opposed to a program file.

task

* The MCR Boot command is the one filename-requirement exception.
Boot command in Section 4.3.2 for the default.

3-6

MCR

See

FILES AND FILE SPECIFIERS
DIR

A directory file,
directory.

FTN

A FORTRAN language source program.

LST

A listing file.

MAC

A MACR0-11 source program.

MAP

A Task Builder memory allocation file.

MLB

A user macro library.

OBJ

An object
FORTRAN) .

OLB

An object module library.

SML

The system macro library.

TSK

A task image.

program

The defaults used by DEC-supplied software
describing individual software components.

3.2.6

for

example,

{output

appear

from

user

file

MACR0-11

the

manual{s)

Asterisk Convention (Wildcards)

In addition to relying on defaults in the file specifier, the user
also can place .an asterisk (*) in the specifier to indicate that the
content of _tJ1at el_e_men__~--- of the ~tr ing will _ be satisfied by all
existing values.
By permitting- -ari. "any value" indicator within a
specifier, the user can affect more than one file at a time.
To illustrate this capability, the Peripheral Interchange Program
(PIP) supplied by DEC with RSX-llM will be used. PIP performs a
number of functions, one of which is deleting files.
To del~~e ___ t_l-1~
file PRO~~MAC;l, supply the following_command string to PIP:
~IP>PROG.MAC~~/DE

The string:
PIP>
Is PIP's console prompting string;
-switch.

the notation /DE is

PIP's

delete

Assume that the programmer has a requirement to delete the files
PROG.MAC;l, PROG.OBJ;l, and PROG.TSK;l, and that these fil~s ftre tbe
only existing PROG version 1 files.
Deletion can be accomplished
using the asterisk convention as follows:
PIP>PROG.*;l/DE
The effect of the asterisk is to cause PIP to delete all PROG version
l files, regardless of type. Thus, the asterisk can represent any
value; this characteristic is the source of the terminology "wildcard
specifier."

3-7

FILES AND FILE SPECIFIERS
An asterisk can be placed in any portion of the file specifier except
the device indicator.
The device indicator must be specified or
defaulted to SY:.

3.2.7

Examples of Filename Command Strings

) ///1

1f .,111<

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

are

Example 1:
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>DKO: [200,200]CRGPT.OBJ=DKO: [200,200]CRGPT.MAC
Example 2:
Delete the file SBG.OBJ;5. The output filename string is omitted
because it is not applicable. The input device is SY:, and the
[200,200) UIC is defaulted.
PIP>SBG.OBJ;5/DE
The UIC [200,200) in this example will be selected if,
if:
1.

A /UIC switch has been specified via PIP, or

PIP is running under UIC [200,200).

and

only

Example 3:
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; device and UIC are also defaulted.
TKB>CRGPT=CRGPT.OBJ
TKB>//
The default UIC [200,200) in this example will be
and only if, TKBi is running under ore [200,200).

selected

if,

type

selected

if,

Example 4:
Qelete all files with the name CRGPT, regardless
version: SY: and (200,200) are defaulted.
PIP>CRGPT *;*/DE
The default UIC [200,200) in this example will
and only if;
1.

A /UIC switch has been given in PIP, or

PIP is running under UIC [200,200].

3-8

CHAPTER 4
MCR COMMANDS

4.1

COMMAND SUMMARY

This chapter begins with a list, by category, of all MCR commands.
The list is identical to the order in which the commands are discussed
in detail. The page number for the command is in square brackets
immediately preceding the functional description of the -command. This
command summary provides a compact overview of the
facilities
available from an operator console.
Initialization Commands
ASN**

[4-8]

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

BOOT*

[4-10]

Bootstrap a new system
transfer control to it.

DMOUNT*

[4-12]

Delete the volume control
declare volume off-line.

INITVOLUME*

[4-14]

Initialize
volume.

INSTALL**

[4-22]

Install a task in the system.

MOUNT*

[4-28]

Create the volume control block (VCB)
and
declare volume on-line for access by the file
system.

SET**

[4-33]

Set system and
terminal
characteristics;
redefine partitions;
display terminal and
partition
characteristics
on
entering
terminal.

TIME**

[4-43]

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

UFD

[4-44]

Create a user file directory (UFD)
file and
enter its filename into the volume's master
file directory (MFD) file.

RSX-llM

* Commands with a single asterisk are privileged;
part of the syntax.
** Certain options are privileged on commands
4-1

w~th

into

memory

and

(VCB)

and

block

Files-11-structured

system;
entering

the asterisk is not

double asterisks.

MCR COMMANDS
Informational Commands
DEVICES*

(4-47)

Display the list
recognized by the
terminal.

LUNS*

(4-48)

Display the list of LUN assignments for
indicated task on the entering terminal.

PARTITIONS*

(4-49]

Display the list of partition
the entering terminal.

TASKLIST*

[4-5~]

Display the System Task List on CL:.

of
peripheral
system on the

devices
entering

definitions

Task Control Commands
ABORT***

[4-51]

Terminate execution of a running task.

ALTER*

[4-54]

Alter the priority of a task.

CANCEL***

[4-55]

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

for

FIX*

[4-56]

Fix a task
resident).

becomes

memory

REASSIGN*

[4-57]

Change LUN assignment.

REDIRECT*

[4-58]

Redirect all I/O requests
device to another.

one

physical

REMOVE*

[4-6~]

Remove a task from the system.

RESUME***

[4-61]

Resume execution of a suspended task.

RUN

[ 4-6 2 ]

~ch e du 1 e

UNFIX*

[4-67]

Unfix a task from memory.

memory

(task

from

a task ' s a c t iv a t ion .
The task may
run
immediately,
after
a delay, or in
synchronization
with
the
system
clock.
Periodic rescheduling is optional.

* Commands with a single asterisk are privileged;
part of the syntax.

the asterisk is not

*** Commands with triple asterisks are privileged if the subject tasks
were not started from the terminal from which the command was issued.

4-2

MCR COMMANDS
System Maintenance Commands
ACT*

[4-68]

Display names of active tasks on the
terminal.

ATL*

[4-69]

Display name and status information for active
tasks on the entering terminal.

BRK

[4- 71]

Pass control to the Executive Debugging Tool
(XDT).
Valid for systems which have XDT
generated into them.

OPEN*

[4-72]

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

SAVE*

[4-75]

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

TAL*

[4-77]

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

* Commands with a single asterisk are privileged;
part of the syntax.

4-3

the

entering

file
in

from
the

the asterisk is not

MCR COMMANDS
4.2

MONITOR CONSOLE INTERFACE

The operator communicates with the
following terminals:

RSX-llM

system

via

one

the

Teletype* Models ASR/KSR-33 or ASR/KSR-35;
LA30 or LA36 DECwriter, or
VT05 or VT50 Display.
MCR (Monitor Console Routines) is the interface between the terminal
and
the
RSX-llM system.
MCR input is initiated by entering
unsolicited input on an unattached terminal which has displayed the
default prompt, or by typing CTRL/C. If CTRL/C is entered, the system
responds by displaying
MCR>
on the terminal, indicating that it will now accept an MCR command.
When MCR is ready for another command, it displays the default prompt:

>
Ali examples show the default prompt.

4.2.1

Command Syntax

It is not necessary to type the entire command name when submitting a
command.
MCR ___ r.egu.i.r.:.e~ ..... QnJ,y_ ...J;,be ____..fJ.r..§.t ... th.r~e_.Jg_t;t~_(.~LQJ_a ___ <.:;Ql!lm~pd,
followed by _t_he commang param~_t:g_ r_s_. ___:I;.f .Q~tt:amtlex.s .e.xis.t4_.the¥.-.IDJHLt__J::ie
preceded . h¥.at.lea.st..one blan.k or tab.......
The following example shows how the Time command may be specified.
Note that brackets are used in the example solely to indicate that the
"E" is optional; the square brackets are not actually entered as part
of the command name.
__>_T IM1El. <CR>**
14:00:04 22-AUG-75
Thus, either
>TIM<CR>
or
>TIME<CR>
is acceptable.

* Teletype is a registered trademark of the Teletype Corporation.

** The angle brackets are used to denote that the enclosed values are
not taken literally as part of the command syntax. For example, <CR>
indicates that a carriage return terminates the input line.

4-4

MCR COMMANDS
4.2.2

Keywords

Some

commands use keywords which generally apply to a command
A keywo"rd is similar in function to the swifche~s" aesctibed.
in Section 3.2.2. A keyword consists of a slash (/), followed by an
A.SP I ige11_ q_f ~~a tJq~, ~nq___<?E.~_A9naf ly fci~ !owe_d _~y_ an e9~~~ ....sign· ..(;;·r- ana
t~~-- val_1:1-~- _o.r_ ~-h-~- ke_yword, as follows:
ari~ll!~!!I.-

/Keyword=value
Keywords can be entered in any order. As an example of keyword usage,
the Install command requires a filename argument specifying the task
to be installed. Keywords can be appended to the filename. One such
keyword, _L'l:'A$K, _<::a.D.. _$.P~~-:Lfy___ the name und.e.r...wh.ich ___ th~~-..t~.~-!<:.!.~ __te> ... t:?~
ins tall_~_q ~-- __Th_us,
>INS_ J"_Ir~_. TSK/TASK=_SUPER.. _

will cause the task contained
"in'stalied' -with a name of ···sup"t'.R.
defined with each command.

in the file named JIM.TSK to be
Keywor-ds are cOmm-and" specific -aria -are·-

An example of a keyword without a value is the UNLOCK
Mount command

switch

the

!'.!h_ich speci~Jes _th?J.._9.~-~~-.l1_".1:_it 0 is to be mounted unlocked.

4.2.3

Comments

MCR will treat a line of text as a comment if the first character in
the ___ Ifn'e·--Ts- - - a -s-emfco-,lon (;) • - In add ft ion, the -exciam:a ti oh maXK'"\!l
may be u_~E?_d _to delimit comments in a command. The first exclamation
mark starts t~e t6mment and the next exclam~tion mark or end of line
terminates the comment. All text between the two exclamation marks is
ignored. For example:

THIS LINE IS A COMMENT

>TAS !THIS IS A COMMENT STRING!
This feature is especially useful to comment commands in MCR
files which are described in Section 5.1.

4-5

indirect

MCR COMMANDS
4.3

OPERATOR COMMANDS

MCR accepts
Command names are at least three characters in length.
the first three characters of a command and then searches for a blank,
tab, carriage return, or ESCape character. Therefore, embedded blanks
If a command is entered
are not allowed in a command name.
incorrectly, an error message will be displayed at the entering
terminal.
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 (e.g., [dt]) may or may not be included
in the command, at the user's option. The one exception to
this rule is the syntax for the specification of a DIC. The
format for a DIC is [g,m], where the square brackets are
required syntactical elements.

Unless explicitly qualified, all numeric values required in a
command may 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
is base 10;

the value

Each command is described using the following subheadings;
do not apply are omitted.

those that

have the same value.
377 is base 8.)

4.3.1

(The value 255.

Command Description Format

COMMAND NAME
This section is headed by the command name in capital letters. On the
right margin, the minimal MCR command mnemonic is shown. If the
command can be executed only from a privileged terminal, the word
"privileged" appears in parentheses following the command name.
Following the heading, the
described.

command's

intent

within

the

system

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

4-6

MCR COMMANDS
Examples:
Example uses are shown.
Command Related Error Messages:
Error messages specific to the command appear in this section.
The command may also produce messages listed in Chapter 6 {common
error messages), but these are not listed here.
Notes:
A list of special considerations that may prove helpful
assisting the programmer in the proper use of the command.

4-7

MCR COMMANDS
4.3.2

Initialization Commands

ASSIGN (some privileged options)
ASN is used to define, d~le.te, or display: ...lo_gicaLde.v.ice assignments.
Logical device as~ignments ~re a convenient ~ay to asso~iate logical
names with physical dev i_ce~ •. l'h.ere ·a·r~· .. two ·typ~s·. · Q.c-·:I9g]~§J_ ~ __ g_ev ice
a$signments: ... Io.cal .. ·and . . glob.al.
.LQC_9J .. __qssignme.11~~ ....~EElY only to
commands and tasks initiated from the terminal t":rom ··whTCtl"".the
as.signfll.t;!I'l~ ___ .~9§.... m.a.d~.. ~.~-·-··-~-Ci-9..~L.... t~r;m)n~_f. ro.~Y h.a.v.e its. own s.~.. ·of
as~~--~r;:t.!lle~.t~-~- ... G1gpaJ.. 3~.!?sJgD.I1J5!11J.§L... appJy ...~o . all .. comm(indf:>___ .9~___5asRs
un.J:,~~s
a l()g ical. n?t.rn.e... j.s g_g_~Jne_q bo.th .as global ..a..ng __ local, i~1ch ·
cas_e_,_ the local 9ss i_g_n1nen.t QV:E;r ~.ide.s . the global assignment_.
Log i(fal
device names may be the same as physical device names, or they may be
purely random as long as they follow the syntax for devic.e ... nfil!les!...
This syr1!;ax'" ... requir.es a 2-character ASCII device name followed_b¥:-~1.1
op~Jq_nal l"":" or 2-::_dJgJ t o~.t~l unit number.
When referring to a logical
device, the name must be terminated by a colon.

Format:
ASN. ppnn: =llnn :J/GJ.3-.LJ....

Assign lo.g.ical name l.lmL ~Q pp_ysi~al dE!Y ic,e. .PP.nD:.· _....... I f /GBL
is . .SP~~JJJ~Qi-~1h~-~Ei.§Jgnme..nJ:. j_5__ gl9Q.9J_ ..._. A terminal must 'Ee
privileged to define or delete global assignments.

Display local logical assignments.
ASN /GBL
fo .r

all

Delete the local device assignment of logical name llnn.
/GBL is specified, the global assignment is deleted.

Di~plc;iy

all local and global
terminals in the system.

logical

assignments .

ASN =llnn: [/GBL]

ASN = [/GBL]
Delete all local logical assignments.
all global assignments ar~ deleted.

If /GBL is specified,

where:
pp

- Phy~ical device name

rm.

- Unit number

- Logical device name

Example:
>ASN
>ASN
>ASN

DP:=USl:
!Define USl:
DT:=US2:
!Define US2:
DK:=GBO:/GBL !Define global logical device name GBO:

4-8

MCR COMMANDS
>ASN
US2:
USl:
>ASN
US2:
USl:
GBO:
>ASN
>ASN
>ASN

DTO:
DPO:
/GBL
DTO:
DPO:
DKO:
=US2:
=/GBL
=USl:

!List local assignments
LOCAL TI - TTO:
LOCAL TI - TTO:
!List all assignments
LOCAL TI - TTO:
LOCAL TI - TTO:
GLOBAL
!Eliminate local logical device name US2:
!Eliminate all global assignments
!Eliminate local logical device name USl:

Command Error Messages:
ASN -- LOGICAL DEVICE NOT IN SYSTEM
The ~pecif ie~ logical. devj~~ name has not been defined
previously and there.fore cannot __b~ found in the
19_9 ical device_ assignment ~able for the terrn'.fr1al ~
ASN. ~- PSEUDO DEVICE ASSIGNMENT ERROR
A .logical device name may no~ qe
_q_~v i.ce ..

4-9

as~.ign.~.d __ to

pseud.o

MCR COMMANDS
BOOT {privileged)
Boot is used to bootstrap a system which exists as a task image file
on a fjle-structured volume.
lL_ provi4es ~convenient means f6r
terminating one system and initiating another, especially on minimum
hardware
configurations.
For
example, Boot can be used for
terminating a real-time system and initiating a program development
system.
Format:
BOO[T]

[filespec]

where:
f ilespec - The standard RSX-llM file specifier of the form
dev: [group,member]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 SY:

[group ,member]

- The UIC under which BOO is
running

type

- RSXllM
- SYS

version

- Latest version

filename

Example:
>BOO TEST
Bootstrap from the system device the system contained in the
file TEST.SYS.
Command Error Messages:
BOO -- DPB ERROR
A bad DPB was created by MCR.
This error indicates
that the system itself has faulted. If the error
persists, consult your local DEC software specialist.
BOO -- FILE NOT CONTIGUOUS
An attempt is being made
non-contiguous
file.
contiguous.

4-10

to load
System

a system from a
images
must
be

MCR COMMANDS
BOO -- INVALID LOAD DEVICE
Boot has detected a device
system residence device.

which

invalid

BOO -- LABEL BLOCK READ ERROR
Boot cannot read the label block of the system image.
BOO -- NO TRANSFER ADDRESS
Boot could not find a transfer address
system image (result of a task build).

virgin

not

system

BOO -- NOT SYSTEM IMAGE
Boot has determined that the
image.

file

Notes:
1.

The system in operation at the time of Boot command execution
is immediately terminated.

The Boot command is the
filename specification.

Bootable systems are special task image files
that have no
task headers.
Examples of such systems are RSX-llM, RSX-llS,
PRESRV.

only

4-11

command

with

optional

MCR COMMANDS
DMOUNT (privileged)
Dismoun_t declares that the volume or commun ica Uons c:hannel is
logically off-line. After a dismount operation, the device cannot be
accessed by the assocla~ed Ancillary Control Processox .(ACP).
For a
Files-11 volume, a request is placed in the file system queue to
delete the volume control block (VCB), and the volume is marked for
dismount so that no further files can be accessed on the volume. The
VCB is a main memory resident control block that controls volume
access.
The command is completed when the VCB is actually deleted.
The VCB deletion does not occur until all accessed files on the volume
have been de-accessed. When the de-accessing process is complete, a
message is issued, indicating that the dismount operation is complete.
For a network device, the communication volume control block is
immediately deleted, and all further processing on the channel is
terminated.
Format:

where:
-

dey :_

Q~y~ce~~~it

Default:

of the volume to be dismounted.

none;

must be specified.

volume-label - The Files-11 volume label may be up to twelve
characters in length. It is used to \1_arraa~e
th.at the proper volume is being di$IJLQ_g_I)_~~Q·
A volume label may not be specified for a
communications channel.
Default:

Twelve nulls (null volume label).

Examples:
>DMO DKl:RVOLUME
This command causes the VCB for DKl:

to be del~tea.

>DMO XU:
This command causes
the
network
ACP
to
terminate
communication over the channel connected to device Xtf: --- -Command Error Messages:
DMO -- ALREADY MARKED FOR DISMOUNT
The device-unit has already been requested to be
dismounted and is in the process of waiting for all
accesses to the volume to complete.

4-12

MCR COMMANDS
DMO -- HOME BLOCK CHECKSUM ERROR
The checksum in the home
checksum do not agree.
caused by an I/O error.

block
This

and the calculated
message is probably

DMO -- HOME BLOCK I/O ERROR
An error was detected in updating the volume
sequence number in the volume home block.

file

DMO -- NOT MOUNTABLE DEVICE
The device specified is not a mountable
therefore cannot be dismounted.

device

and

DMO -- NOT MOUNTED
The device specified is not currently mounted.
DMO -- WRONG VOLUME
The volume label and
command do not match.

the

label

specified

the

Notes:
1.

The message

*** ddnn:

DISMOUNT COMPLETE

is issued to CO: when the dismount has been completed either
by the file system or the network ACP. There may be a
considerable delay between the issuance of the command and
the printing of this message if there are a number of I/O
requests pending and/or files accessed on the volume.

4-13

MCR COMMANDS
INITVOLUME (privileged}
The function of the Initialize Volume command is to produce a
Files-11-structured volume. In particular, it initializes the volume
(all existing files are destroyeqJ_, writes a dummy p_ootstrap and . a
home block, and builds th~ directory structures. The details of the
Files-11 structure are discussed in the RSX-11 I/O
Operations
Reference Manual.
Format:
INI [TVOLUME] _dev: [volume-label] [/keyw_ord] [/keyword_].~.

/BAD
/CHA
/EXT
/FPRO
/INDX
/INF
/MXF
/PRO
/UIC
/WIN

[option]
[characteristics]*
block-count
[system,owner,group,world]
index-file-position
initial-index-file-size
file-count
[system,owner,group,world]*
[group,member]*
retrieval-pointer-count

where:
dev:

- Device-unit of the volume to be initialized.
Default:

none;

must be specified.

volume-label - The volume label may be up
to
twelve
characters in length. It is used to identify
the volume.
Default:
BAD

twelve nulls.

- This keyword indicates
that
bad
blQ~k
processing is to be included in the yplume
initiAlizGtion. The result of this will be
th~t
bad blocks on the volume will be marked
~s in-use and will not be allocated to files.
The options are:
· · --· -- .
- Accept block specified from
terminal.
[AUTO]
- Read bad block file
on
volume
created
by
diagnostic routine (BAD}.
[AUTO,MAN] - Read bad block file and,
when done, accept blocks
specified from terminal.
[MAN]

* The asterisked keywords are included for RSX-llD compatibility.
Thus, volumes built on RSX-llM can be mounted on an RSX-llD system.

4-14

MCR COMMANDS
The brackets are required syntax. If MAN is
specified, the program will prompt for bad
blocks with:
IN I> BAD=

Bad blocks may be entered in two formats.
nnnnn

- A single block

nnnnn,mmmm - A contiguous series of mmmm
blocks beginning at nnnn.
A
null
line
(carriage
return)
terminates
bad
block input.
CHA

The characteristics words are optional ASCII
strings separated by commas.
The square
brackets are required syntax.
For
the
Initvolume command, two characteristics are
defined:
ATCH - ATTACH/DETACH (device can be used
by
one
task
or
group
exclusively);
included
for
RSX-llD compatibility. Unused by
RSX-llM.

Default:
DCF

- Device Control
Functions
are
permitted;
included for RSX-llD
compatibility.
Unused
by
RSX-llM.
Default:

EXT

no DCF.

The default number of blocks by which a
file
exhausting its space ·allotment is to be
ex tended.

Default:
f_PRO

no Attach/Detach.

five blocks.

- Keyword for default file protection.
Access
codes consist of four, 4-code groups in the
Access Rights word, as follows:
R

w
E
b

Read
-Write
Ex fend
Delete

In each instance, th~ absence of the code
means that the access right is denied the
user.
The square brackets are
required
syntax.
Default:

[RWED,~WED,~WED,R].

4-15

MCR COMMANDS
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
The
order
of
appearance
of
characters R, W, E, and D is fixed.

the

R, if desired, must be first.

w, if desired, is next.

E, if desired, is next.
D, if desired, is last.
Thus, RWE and RE are
WR and DEWR are not.

acceptable,

while

- Index file logical block number. This can be
us.ed to .f.Pr.~_e_ t_he index file, master file directory
(MFD), and storage allocation file to a specific ~61um~
lo~~ttqn,
usually for minimizing access time. Four
possibilities are available:

INDX

.BEG

Place index file at
9f the volume.

MID

- Place index file at the
t_he volume.

middle

END

- Place index file at the end of
volume.

the

BLK:nnn - Place
numb~r

Default:
INF

file

beginning

the

block

specifi~d~

middle of volume.

Initial index file size. This is the number
of "iiie h-e-aders. -to ... aifow space for in the
first index file allocation.
Default:

MXF

index

the

16 files.

'I'h_e rnC'lX imum number of files (file headers in
the volume's index file)
per:mJ_tted.. QD the
volume; this number must be less than or
equai
the number specified for the device
in the table below:

Maximum
DECtape
RK Disk
RF Disk
RS03 Disk

4-16

144
1200

256
256

MCR COMMANDS
RS04
RP02
RP03
RP04

Disk
Disk
Disk
Disk

512
10000
20000
42949
Defaults

DECtape
RK Disk
RF Disk
RS03 Disk
RS04 Disk
RP02 Disk
RP03 Disk
RP04 Disk

600
128
128
256
5000
10000
21474
NOTE

A Files-11 volume requires five files
to create the on-disk structure (See
Appendix E
of
the
RSX-11
I/0
Operations Reference Manual). '.!'hus,
MXF must be computed by the maximum
·n:umEe~--.
u·s·er-····uFiS Is and "fiTe~i 'pTus
the __5 ·_)eCi~fie~-- f'or____ The· ·- ··F'nes~n
structure.

PRO*

- Keyword for volume access rights parameter.
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 access right is denied the
user.
The square brackets are
required
syntax.
Default:

[RWED,RWED,RWED,RWED].
NOTE

Protection

code

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

system,owner,group,world
The order of appearance
of
the
characters R, W, E, and D is fixed.

4-17

MCR COMMANDS
R, if desired, must be first.

w, if desired, is next.

E, if desired, is next.
D, if desired, is last.
Thus, RWE and RE are acceptable,
while WR and DEWR are not.

UIC*

- Keyword for 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.
Def a ul t :

WIN

[1 , 1 ]

T~e_

number_ oL lll_apping _ pointers
to
be
allocated for file windows. A file windo-·wTs
m~de - up of a number of mapping
poTn-f~f s-. ana
is stored in memory when the f_ile is_ g_pened.
(See Appendix F in the RSX-11 I/O Opera~ici~~
Reference Manual for a description of a
mapping pointer.)
Default:

Example:
>IN! DKl:ICTSVOL2/UIC=[2,5]/INDX=BEG/FPRO=[RWED,RWE,RW,R]<CR>

The Initvolume parameters in the example above are:
DKl:

- Device-unit

ICTSVOL2

- Volume-label

/INDX=BEG - Index file location, forced to beginning of volume
/FPRO

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

/UIC

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

- User identification code:

group=2, member=S

* RSX-llM does not protect a volume at the UIC level.
It does,
however, prevent direct access to MOUnted volumes by non-privileged
tasks. This parameter is included to permit volume interchangeability
with RSX-llD.

4-18

MCR COMMANDS
Command Error Messages:
INI

ALLOCATION FOR SYS FILE EXCEEDS VOLUME LIMIT
Unable to allocate system file from specified block due
intermediate bad blocks or end of volume.

INI -- BAD BLOCK FILE FULL - TASK ABORTED
The disk has more than 102 bad regions on it.
INI -- BAD BLOCK HEADER I/O ERROR
An error was detected in writing out
header.

the

bad

block

file

INI -- BLOCK(S) EXCEED VOLUME LIMIT
Specified block {or
volume.

blocks)

exceed(s)

physical

size

INI -- BOOT BLOCK WRITE ERROR
An error was detected in writing out the volume boot block.
INI

CHECKING DDnn
Automatic bad block specification is proceeding using the
bad block file provided by the Bad Block Locator utility
program.

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

the

checkpoint

file

INI -- DATA ERROR
Too large a bad
specified.

block

number

contiguous

region

was

A block which has been defined as bad is being
bad a second time.

defined

INI -- DUPLICATE BLOCK(S) FOUND

INI -- DEVICE NOT INIT-ABLE
The device is not a supported Files-11 device.
INI -- DEVICE NOT READY
The specified device is not ready.
INI -- DEVICE WRITE LOCKED
The specified device is hardware write-locked.
INI -- FILE CORRUPT - DATA IGNORED
Bad block file contains bad data.

4-19

MCR COMMANDS
!NI -- HOME BLOCK ALLOCATE WRITE ERROR
In overwriting
occurred.

bad

home

block

area,

write

error

!NI -- HOME BLOCK WRITE ERROR
An error was detected in writing out the volume home block.
!NI -- ILLEGAL KEYWORD VALUE
A value entered for a keyword exceeds its limits.
!NI -- INDEX FILE BIT MAP I/O ERROR
An error was detected in writing out
map.

the

index

file

bit

!NI -- INDEX FILE HEADER I/O ERROR
An error was detected in writing out the index file header.
!NI -- MFD FILE HEADER I/O ERROR
An error was detected
directory file header.

writing

out

the

master

file

!NI -- MFD WRITE ERROR
An error was detected in writing out a block in the MFD.
!NI -- NO BAD BLOCK DATA FOUND
Although automatic bad block specification was selected, no
bad block file was found on the volume.
!NI -- NOT FILES-11 DEVICE
The system does
device.

not

support

Files-11

the

specified

!NI -- NULL FILE HEADER I/0 ERROR
An error was detected in writing out null file
the index file.

headers

!NI -- STORAGE BITMAP FILE HEADER I/O ERROR
An error was detected in writing out the storage allocation
file header.
!NI -- VOLUME MOUNTED
Mounted volumes may not be initialized.

4-20

MCR COMMANDS
Notes:
1.

The Initvolume command is closely related to the file system.
The
parameters
are listed and their explanations are
necessarily sketchy. Selecting values for the parameters
requires an in-depth knowledge of the file system. Refer to
both the RSX-11 I/O Operations Reference Manual and the
RSX-llM System Generation Manual.

4-21

MCR COMMANDS
INSTALL (privileged)
TP,e Install command is used to make tasks known to the system a_nd !:_()
load resident libraries in common partitions. The filespec parame~~r
is the Qnly reguired_~rgument. The keywords are optional argumen~~
for parameters ~h~~ w~r~ either not specified at task-build time, or
are to be overridden during the execution of the Install command. The
process of task installation results in a main memory resident task
control block (TCB) being constructed. Once installed, a task may be
acted upon by specifying its name in an appropriate command directive.
Format:
INS[TALL] filespec[/keyword] [/keyword] ...
Keywords:
/CKP
/INC

/PAR
/PMD
/PRI
/TASK
/UIC

option
size
pname
option
number
taskname
[group,rnernber]

where:
filespec - The file specifier in the form:
dev: [group,member]filename.type;version
The standard defaults for file specifiers apply.
Default:

TSK

CKP

- Checkpoint option.
If CKP=YES (default
for
checkpointable
tasks),
checkpointing
of
a
checkpointable task will be allowed. If CKP=&o;·
checkpointing will be disabled for the task~-------

INC

- The number of additional words of address space
to be allocated to a task which is to run in a SY? t~lll~C:9[1troUed par ti ti on.
The ex tens ion size
is usually expressed in octal hut may also be
expressed in decimal by appending a period. This
keyword will override the EXTTSK parameter used
at task-build time and is used for tasks which
determine the size of the partition in which they
are running in order to decide how much dynamic
space they may allocate to symbol tables or
buffers. Tasks such as MACR0-11, TKB, PIP, VFY,
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.
Default:
zero.

size specified at task-build

4-22

time,

MCR COMMANDS
PAR

- A partition name which overrides the partition
specified at ~ask-bµild ttme. In the unmapp~d
system, the partition specified must have the
same base address as the partition for which the
task was built.
Default:
TKB uses the name GEN.
(See the
RSX-llM System Generation Manual for explanation
of multiuser system defaults.}

:PMD

_-: __ J?9_5-kt1ortem
I?ump_
option.
If
PMD=YES,
a
pQ$_t-mor tern dump will- be -.reg)1estea for __ the task
i_J_____ it__ ~~l::>_<2_~ts due to an SST error condition.
If
PMD=NO (the default from a task~buila}, no dump
will be requested at SST abort time. '.!_'.Q_ _qel)era~-~
a dump, the posJ: mor tern c:;lump t9_s_)S_ f.>_~p.! •.!. __ll!us_t____ }:)~
installed in the system.
This keyword will
override the /PM switch specified at-task-build
time.

Default:
PRI _______ _

- fl.I ioi;J_ty_ number__ ~
The value range is
250 (10).
Number co_nyeri_t.i,()1}5- __ a_pply.

De fa u 1 t :
TASK

specified at task-build time.

- Taskname.
referre_d.

50 •

through

( de c i ma 1 ) •

The name by which the task

Default: first six characters of the filename or
the name specified at task-build time.
(See the
RSX-llM System Generation Manual for explanation
of multiuser system defaults.)
UIC

- ..L9.~91:1E,m~mb~r]_. 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 to tasks started by a Run directive or
command. Tasks started by typing the name as a
command, e.g., PIP, TKB, etc., run under the
default UIC of the terminal from which the
command was issued. This UIC is defined by the
Set command.

Examples:
>INSTALL SCAN
Install task SCAN.

Priority and UIC defaulted.

4-23

MCR COMMANDS
>INSTALL DKl: [l,lll]SCAN.TSK;4/PRI=l03
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=4096./PAR=SYSCTL
Install task MAC in the system-controlled partition
and increase the task size by 4096 decimal words.

SYSCTL

Command Error Messages:
INS -- BASE ADDRESS MUST BE ON 4K BOUNDARY
The base virtual address of the task is not on
boundary. Applicable only to mapped systems.

INS -- BASE MISMATCH COMMON BLOCK <common-name>
The base address of the partition does not match that
of the common block.
Applicable only to unmapped
systems.
INS -- CHECKPOINT AREA TOO SMALL
The area allocated for checkpointing the task is
smaller than the partition into which it is being
installed.
INS -- COMMON BLOCK IS TASK PARTITION <common-name>
A task's request for access to a common block is
rejected because the partition requested is a task
partition.
INS -- COMMON BLOCK NOT LOADED <common-name>
The specified common block is liriked to the task but
has not been installed into the system. Install the
common block, then install the task.
INS -- COMMON BLOCK OCCUPIED
An attempt has been made to load a common block
is already occupied.

which

INS -- COMMON BLOCK PARAMETER MISMATCH <common-name>
Parameters of a common block do not match those in the
task's label block.
INS

-- FILE NOT CONTIGUOUS
An attempt is being made to inst.all a task from a
non-contiguous file.
Task images may exist only in
contiguous files.

4-24

MCR COMMANDS
INS -- FILE NOT TASK IMAGE
Data in the label block is not correct,
that the file is not a task image.

indicating

INS -- ILLEGAL DEVICE ddnn:
Device specified at task build by the assign keyword
options does not exist in the system. This is a
warning message; the task will be installed.
INS -- ILLEGAL DEVICE/VOLUME
The device specified is not
device.

valid

task

residence

INS -- ILLEGAL FIRST APR
A privileged task, built to run using APR 4, 5, or 6
as its base, is too large. Using APR4, the task is
larger than 12K; using APRS, the task is larger than
SK; using APR6, the task is larger than 4K.
Applies only to mapped systems.
INS -- ILLEGAL PRIORITY
The value of the priority specified in the command
out of range (i.e., not 1 to 250(10), inclusive).

INS -- LENGTH MISMATCH COMMON BLOCK <blockname>
The length parameter for the common
block,
as
described in the label block for the task image, does
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 -- 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 10000Q(8) to be
able to map the first 16K 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
wit9
the
remaining
mapping
registers.
Applicable to mapped systems only.
INS -- NO ROOM AVAILABLE IN STD FOR NEW TASK
This message means that there is no dynamic memory
available to build the system task directory {STD)
entry {task control block); therefore, no task can be
installed.
INS -- PARTITION NOT COMMON
A partition specified for a common
defined as a common partition.

4-25

library

not

MCR COMMANDS
INS -- PRIVILEGED TASK LARGER THAN 12K
Privileged tasks have a maximum size of 12K.
INS -- SPECIFIED PARTITION FOR COMMON BLOCK
A task is being installed into a common block.
INS -- SPECIFIED PARTITION TOO SMALL
The task being installed is larger than the
into which it is being installed.

partition

INS -- TASK AND PARTITION BASES MISMATCH
The base of the partition does not match that of the
task
being installed.
Applies only to unmapped
systems.
INS -- TASK IMAGE I/O ERROR
or it is
(Device is

Install cannot read the task image file
unable to rewrite the task image header.
write locked.)
INS -- TASK IMAGE CURRENTLY INSTALLED

The requested task image, which is checkpointable, is
already installed. Checkpointable tasks may be singly
installed; other tasks may be multiply installed.
INS -- TASK NAME ALREADY IN USE
An attempt has been made to install a task
same name as one already in the system.

with

the

INS -- TOO MANY COMMON BLOCK REQUESTS
A task is limited to three common block references.
INS -- TOO MANY LONS
A task has requested more
assigned.

than

255(10)

LUNs

INS -- UNDEFINED COMMON BLOCK <blockname>
A task references a common block that is not defined
in the system. Usually, this indicates that the task
was built for another system.

4-26

MCR COMMANDS
Notes:
1.

Once a task is installed, its physical location is known to
the Executive by virtue of the fact that its TCB contains the
address of the load device unit control block and the logical
block number of the image.
Thus, to load the task, no
searching is needed, and the task can be read in one
transfer.
However, the user is not prevented from deleting
the disk file that the task resides in.
If the file is
deleted, subsequent file system activity could reallocate the
disk blocks to another file.
In this case, the task will
probably abort on task load.

4-27

MCR COMMANDS
MOUNT {privileged)
The Mount command logically connects devices to ancillary control
processors (ACPs).
For Files-11 volumes, the Mount command creates
the Volume Control Block (VCB) and declares that the volume is
logically on-line for access by the file system. The VCB is allocated
in dynamic memory and controls access to the volume.
Details are
specified in the RSX-11 I/O Operations Reference Manual. For network
channels, the Mount command informs the network ACP that the device is
available for use in the network. It allocates a communication Volume
Control Block and issues a Mount request to the ACP.
Format:
MOU[NT] dev: [volume-label] [/keyword] [/keyword] ...
Keywords:
/ACP
/EXT
/FPRO
/LRU
/PRTCL
/RCK
/TEL
/UIC
/UNL
/VI
/WIN

taskname
block-count*
[system,owner,group,world]*
least recently used directory count*
network protocol name**
redundancy check algorithm name**
telephone number for dial up link**
user id code*
(no value is associated with UNL)*
(no value associated with VI)*
retrieval-pointer-count*

Mount keywords for Files-11 devices
values in the volume's home block.

override

corresponding

where:
dev:

- Device-unit on which
mounted.
Default:

none;

the

volume

must be specified.

volume-label - The Files-11 volume label may be up to twelve
characters in length. It is used to ensure
that the correct volume is being mounted.
A
volume label may not be specified for network
channels.
Default:
ACP

twelve nulls;
performed.

label

check

- The task name of an
Ancillary
Control
Processor designed to process this volume.

* Keyword valid for Files-11 devices only.

** Keyword valid for network devices only.

4-28

MCR COMMANDS
Default;
depends
indicated below:

For Files-il voiumes: the
FllACP
For network channels, the
NT •••.
EXT

ACP

name

ACP

name

- The number of blocks by which a file which
exhausts
its space allocation is to be
extended.
Default:

FPRO

type,

device

taken from the home block.

- 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

In each instance, the absence of the code
means that the access right is denied the
user.
The square brackets are
required
syntax.
Default: values taken from volume home block.
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:

The order of appearance
of
the
characters R, W, E, and D is fixed.
R,
W,
E,
D,

if desired,
if desired,
if desired,
if desired,

must be first.
is next.
is next.
is last.

Thus, RWE and RE are acceptable,
while WR and DEWR are not.

4-29

MCR COMMANDS
LRU

- The number of directory File Control Blocks
(FCB)
kept in memory by the ACP per volume.
The more FCB's kept 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 and thus the file is found more
quickly.
Default:

PRTCL

- The name of the network line protocol.
Default:

RCK

DDCMP

- The name of the redundancy checking routine.
Default:

TEL

CRC16

- The telephone number of a line to a remote
node. Up to 12 digits may be specified.
Default: null (Note:
in DECNET Release 1)

dial-out not supported

UIC

- User identification code -

UNL

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

locked.

- Display the volume
information
on
the
entering terminal. The information displayed
is that under which the volume was mounted.
The volume information format is:
DEVICE
TYPE
LABEL
UIC
ACCESS
CHA RAC

WIN

[group,member].

ddnn:
type
volume label
[nnn,nnn]
[system,owner,group,world]
[

]

The number of mapping
pointers
allocated for file windows.
Default:

taken from home block.

Examples:
>MOU DKl:
Mount the volume on device-unit DKl:.
(In th is example, the
optional parameters have not been specified; therefore, the
parameter values in the volume's home block are used.) No
label checking is performed.
No volume information is
displayed.

4-30

MCR COMMANDS
>MOU DKl:SYS004
Mount the volume labeled SYS004 on DKl:
>MOU XP:/TEL=l6176468600
Mount the DPll link and dial the remote node whose telephone
number is 16176468600.
Command Error Messages:
MOU -- ACP NOT IN SYSTEM
Task specified as ACP or default ACP is
the system.

not

installed

MOU -- ALREADY MOUNTED
The network device-unit specified has already been mounted.
MOU -- DEVICE ATTACHED
The specified device-unit is currently attached by
and may not be mounted.
MOU

task

DEVICE NOT DEFINED IN NETWORK
The specified device-unit has not been defined in the
current network topology and therefore may not be mounted.

MOU -- DEVICE OFFLINE
The specified device, although generated into the system,
is not physically present in the host configuration.
MOU -- FILE HEADER READ ERROR
Mount cannot read either
storage allocation file.

the

index

file

header

the

MOU -- HOME BLOCK READ ERROR
An I/O error was detected in trying to read the home block.
This usually indicates that the volume is not ready. Wait
until it is ready and reissue the command.
MOU -- NT DEVICE NOT MOUNTED
The device NT: must always be
device in a network.

mounted

before

any

other

The device specified is not supported as a Files-11
or a network device.

device

MOU -- NOT MOUNTABLE DEVICE

4-31

MCR COMMANDS
MOU -- OTHER VOLUME MOUNTED
An attempt has been made to mount a
which aiready has a mounted volume.

volume

device

MOU -- RETRIEVAL POINTERS WRONG FORMAT
The index file retrieval pointers are not in correct format
for RSX-llM.
MOU -- STORAGE BIT MAP FILE READ ERROR
An I/0 error was
allocation file.

encountered

while

reading

the

storage

MOU -- TASK NOT ACP
The task specified as an
characteristics of an ACP.

ACP

does

not

have

the

MOU -- WRONG VOLUME
The volume label and the label specified in the command
not match.

MOU -- VOLUME STRUCTURE NOT SUPPORTED
RSX-llM does not support the Files-11
the volume being mounted.

4-32

structure

level

MCR COMMANDS
SET (some privileged options)
The Set command makes it possible to dynamically alter a number
system-wide parameters.
Some of the options are privileged.
particular, SET enables the user to:

of
In

Establish the default buffer size for a device;*

Establish terminal device characteristics;

Establish a terminal as privileged;*

Characterize a terminal as a slave terminal (a terminal
which the system will not accept unsolicited input);

Establish a default UIC for a terminal;**

Create partitions or subpartitions;*

Add space to the dynamic core pool, and*

Cause all writes to an RKOS disk to be automatically followed
by a write check to ensure that the data was written
correctly.

from

Format:
SET /Keyword=values
Only one keyword per command is permitted. All of the keywords
except BUF, POOL, and UIC may be prefixed by NO to negate the
effect of the keyword.
Specifying NO on BUF, POOL, or UIC
produces a syntax error.
Keywords for setting device characteristics are:
/BUF

= dev: [size]

/LA30S [= dev:]
/LOWER [= dev:]
/PRIV

[= dev:]

/SLAVE [= dev:]
/SPEED = dev: [recv:xmit]
/UIC

[= [group ,member] [:] dev:]]

/UIC

[=dev:]

/VTOSB [= dev:]

* Privileged terminal status required.
** Privileged terminal status required to change default UIC for other
terminal.

4-33

MCR COMMANDS
The effects of these keywords are as follows:
BUF

- Set or display the default buffer size of the
the size is not entered,
specified device.
If
this keyword results in the current size being
BUF
particularly useful for
displayed.
is
defining line printer width (80 or 132 columns).

LA30S

- Establishes the specified terminal device as an
LA30S.
If dev: is omitted, all terminals which
are defined as LA30S are displayed.

NOLA30S - Resets the terminal to other than an LA30S.
If
dev:
is omitted, all non-LA30S terminals will be
displayed.
LOWER

- Specifies that lower-case characters are not to be
converted to upper case when received from the
If dev:
is omitted, all
specified terminal.
terminals for which lower-case characters are not
converted are displayed.

NOLOWER - Resets the terminal characteristics
so
that
lower-case characters received on input will be
automatically converted to upper case and echoed
as upper case.
Absence of dev: results in the
display of all terminals for which conversion to
upper case is specified.
PRIV

- Sets the specified terminal to privileged status.
If
dev:
is omitted, MCR will display all
privileged terminals.

NOPRIV

- Sets the identified terminal to non-privileged
status.
Absence of dev: results in a display of
all non-privileged terminals.

SLAVE

- Establishes the specified terminal as one which
can only enter data if it is solicited from a
task; thus, unsolicited input is always rejected.
Absence of dev: will result in the display of all
terminals currently classified as slaves.

NOSLAVE - Resets slave status. Absence of dev: results
the displays of all non-slave terminals.

SPEED

- Establishes the receive and transmit baud rate for
terminals attached to the system through a DHll
multiplexer. The argument "recv" is the receive
baud rate for the DHll, and "xmit" is the transmit
baud rate for the DHll. Both must be specified in
setting the speed. If neither is specified, the
current settings will be displayed.
Valid baud
rates are:
0, 110, 150, 200, 300, 600, 1200,
1800, 2400, 4800, 9600, A (user-specified baud
rate A), and B (user-specified baud rate B).

VTOSB

- Sets the specified terminal as a VTOSB (a 2400
baud VTOS).
If dev: is omitted, all terminals
classified as VTOSB will be displayed.

4-34

MCR COMMANDS
NOVTOSB - Resets the terminal to other than a VTOSB.
If
dev:
is omitted, all terminals classified as
non-VTOSB terminals will be displayed.
OIC

- The specified OIC is established as the default,
which is used implicitly for the entering terminal
unless dev: is specified, in which case, the
default OIC is set for that terminal. Setting the
ore explicitly is a privileged command. All tasks
run from the terminal are run with the OIC of the
terminal, unless explicitly overridden with the
OIC switch in the Run command. Further, external*
MCR function tasks are requested with this OIC.
If a OIC is not specified, the current OIC will be
displayed. If only dev: is specified, the UIC
for the specified terminal will be displayed,
command
provided that the terminal
was issued is privileged.

Notes:
1.

The status of all terminals may be displayed at any terminal.

Privileged status may
terminal.

LA30S, SLAVE, and VTOSB status may be altered from a
privileged terminal, or the requesting terminal may alter its
own status.

Buffer size may be altered only from a privileged terminal.

The UIC of a terminal may be altered from the same terminal.
The UIC of any terminal may be altered from a privileged
terminal.

Improper usage of the Set command from a privileged terminal
can result in a situation in which privileged operator input
will not be accepted. There are two situations which must be
avoided, arising when one of the following conditions is in
ef feet:

only

altered

from

privileged

There are no non-slave, privileged terminals in the
system. Non-privileged terminals cannot enter privileged
commands.
Slaved terminals cannot enter unsolicited
input to MCR.

The buffer length of all non-slave, privileged terminals
is shorter than 14 bytes. The terminal buffer is too
short to enter many important commands required to
continue system operation or to alter the status of other
terminals.

* These are the MCR Mount, Install, Dismount, and UFD commands
run as tasks) and all system-supplied software.

4-35

(which

MCR COMMANDS
Keywords for altering memory allocation are:
/MAIN

pname[:base:size:type]

/NOMA IN

pname

/SUB

mname:pname[:base:size]

/NOSUB

mname:pname

/POOL

[=top]

These keywords are used as follows:
MAIN

- This keyword is used to establ1sh a main partition.
pname

The 1- to 6-character
partition name.

:base

Physical base
address
of
the
partition specified as a number of
64-byte blocks.

:size

Size of the partition specified
a number of 64-byte blocks.

:type

TASK

for

alphanumeric

user-controlled task
SYS
for
a
system-controlled task partition,
COM for a common partition, or DEV
for a common partition mapping into
the
device
registers.
User-controlled
and
system-controlled task partitions
are allocated for
user
tasks.
Common
partitions are used for
resident
libraries
and
common
blocks. Device partitions are used
by non-privileged tasks to access
device registers in the external
page, such as those for the UDC and
ICS/ICR-11.
parti~ion:

Base and size may be entered in any of the
following formats;
nnnn is a number 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 are:
Octal
Decimal
Octal K
Decimal K

4-36

O<=base<l 77777
0.<=base<65535
OK <=base< 3 77 7K
O.K<=base<2047.K

O<size<2000
O.<size<l024.
OK<size<40K
O.K<size<32.K

MCR COMMANDS
For system-controlled partitions, size may
range
from
O<size<l024.K
or any valid
representation of these limits.
Example:
Any of the following inputs for
allocate a 2048. byte partition.

size

will

40
32.

lK
l.K
If base, size, and type are not specified,
MCR displays the values of these parameters
for the named partition.
If tne
named
partition is a main partition, the parameters
of all its subpartitions will
also
be
displayed.
NOMAIN

- The NOMAIN keyword eliminates the named
from the system.

partition

SUB

- This keyword is used to establish a subpartition.
Subpartitions
may
only
be
established
in
user-controlled main partitions.
mname

The
1to
6-character
main
partition name.
The subpartition
being
defined
will
become
a
subpartition
in the named main
partition.

:pname

The 1- to 6-character subpartition
name.
The
subpartition
being
defined is 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 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.)

4-37

MCR COMMANDS
Valid ranges of values are:
O<=base<lOOOO
O.<=base<4096.
OK<=base<200K
O.K<=base<l28.K

Octal
Decimal
Octal K
Decimal K

O<size<2000
O.<size<l024.
OK<size<40K
0. K<si ze<32. K

Example:
Any of the following inputs for
allocate a 2048. byte partition.

size

will

40
32.
lK
l.K

If base and size are omitted, the current values
will be displayed for the named subpartition.
NOSUB

- Eliminates the named subpartition from the system.

POOL

- This keyword is used to increase the size
dynamic storage region.
top

the

- First location in memory to be used for
user
partitions.
This is given in
number of 64-byte blocks.
It can be
given in octal or decimal. If top is
not given, the system will print out the
current top of memory, the size of the
longest block of pool space in words,
and the total number of words in the
pool.
The format is:
POOL = top:max:total
where top is given in units of 64-byte
blocks.
Max and total are in decimal
words.

Keyword for specifying write check on writes to RKOS disks:
/WCHK[=dev:]
/NOWCHK [=DEV:]
to have all
This feature
transfers to
all RKOS disk
be displayed.

WCHK

Specifies the RKOS disk which is
writes followed by a write check.
provides high reliability for data
the RKOS disk. I f dev: is omitted,
drives with write check enabled will

NOWCHK -

Specifies that write check is to be disabled for
the spec i f ied device. If dev: is not specified,
the RKOS disks which have write check disabled
will be displayed.

4-38

MCR COMMANDS
Command Error Messages:
SET -- ALIGNMENT ERROR
An attempt has been made to create a partition but the
base
address
or
size
conflicts with existing
partitions or physical memory size.
SET -- DEVICE NOT DHll
An attempt has been made to set the baud rate for a
terminal which is not attached to a DHll multiplexer.
SET -- DEVICE NOT TERMINAL
set
An
been
made
to
attempt
has
characteristics for a non-terminal device.

terminal

SET -- NON EXISTENT MEMORY
An attempt has been made
non-existent memory.

define

partition

An attempt has been made to define a partition with
name that is already in use.

SET -- PARTITION ALREADY EXISTS

SET -- SPACE USED
An attempt has been made to create a partition
subpartition in a storage area already occupied.

SET -- TASK INSTALLED IN PARTITION
An attempt has been made to eliminate a main partition
or subpartition containing installed tasks.
SET -- TOO MANY SUBPARTITIONS
A main partition
subpartitions.

limited

maximum

seven

SET -- UNKNOWN MAIN PARTITION
An attempt has been made to define a subpartition of a
non-existent main partition.
SET -- WRITE CHECK NOT SUPPORTED
An attempt has been made to enable write check on a
device which is not an RK05. Write check is currently
supported for RK05 disks only.
Notes:

~~-

If a task is currently installed in a partition and an
attempt is made to eliminate the partition (/NOMAIN, /NOSUB),
the command will be rejected.

4-39

MCR COMMANDS
2.

If a main partition is eliminated, all its subpartitions
al so el im ina ted.

If a subpartition is being eliminated, only the specified
subpartition will be eliminated. A main partition that has
subpartitions with tasks installed will not be allowed to· be
eliminated until those tasks are removed.

When defining a partition (main or sub)
the name must not
already be defined as a partition.
In addition, main
partitions may not overlap any other main partition, nor may
subpartitions
of
a
main partition overlap any other
subpartitions of the main partition.

The numeric value convention applies to all the
numeric values.

All partitions, except LDR, are considered user partitions by
the POOL command.
Thus, SYSPAR is included as a user
partition.

Once space has been allocated to the dynamic storage
it can never be recovered for use in partitions.

System-controlled partitions may not have
subpartitions
explicitly defined by the Set command. An attempt to do so
will be rejected. The Executive defines subpartitions of the
system-controlled partition dynamically as needed for tasks
installed in the system-controlled partition.

Examples:
>SET /BUF=LPO:
BUF=LPO: 132.
Display the current buffer size of LPO:
>SET /BUF=TT1:40.
Set TTl:

buffer size to 40(10).

>SET /LA30S=TT2:
>SET /LA30S
LA30S=TTO:
LA30S=TT2:
Set TT2: as an LA30S.
Display all LA30S terminals.
>SET /NOLA30S=TTO:
Set TTO: to other than an LA30S terminal.
>SET /PRIV=T'rO:
Set TTO: to a privileged terminal.

4-40

Set

are

command

region,

MCR COMMANDS
>SET /PRIV
PRIV=TTO:
PRIV=TTl:
Display ~11 privileged terminals.
>SET /SLAVE=TT 3:
Set TT3:

to a slave terminal.

>SET /VTOSB
VTOSB=TT4:
VTOSB=TTS:
VTOSB=TT6:
Display all VTOSB terminals.
>SET /MAIN=SYSPAR:420:140:TASK
Define a main partition called SYSPAR as a user-controlled
partition whose base address is 42000(8) and whose length is
14000 (8) bytes.
>SET /SUB=SYSPAR:MCRPAR:445:56
Define a subpartition called MCRPAR of main partition SYSPAR
whose base address is 44500(8) and whose length is 5600(8)
bytes.
>SET /MAIN=SYSPAR
MAIN=SYSPAR:0420:0140:TASK
SUB=SYSPAR:MCRPAR:0445:0056
Display the parameters of the main partition SYSPAR and
of its subpartitions.

all

>SET /NOSUB=SYSPAR:MCRPAR
Eliminate subpartition MCRPAR.
>SET /NOMAIN=SYSPAR
Eliminate main partition SYSPAR.
SET /MAIN=GEN:l000:6000:SYS
Define a main partition called GEN as a system-controlled
partition whose base address is 100000(8) and whose length
is 600000 (8) bytes.
>SET /POOL=420
Set the beginning of user partitions to 42000(10).
>SET /POOL
POOL=0420:150:420.
The first location for user partitions is 42000;
the
longest free block is 150. words, and the total of all pool
space is 420. words.

4-41

MCR COMMANDS
SET /WCHK=DKl:
Enable write check on DKl:.

4-42

MCR COMMANDS
TIME (some privileged options)
The Time command makes it possible to:
Set the current time of day (privileged);
Set the current date (privileged), or
Display the current time and date.
Format:
TIM[E]

[hrs:mins[:secs]]

[mnth/day/year]

where:
hrs

Hours (range 0-23)

mins

Minutes (range 0-59)

secs

Seconds (range 0-59)

mnth

Month (range 1-12)

day

Day (range 1-31)

year

Year (range 0-99). Year is relative to 1900;
1975 is entered as 75.

(optional)

thus,

Examples:
>TIM
10:23:31 03-May-75
Display the current time and date.
>TIM 1:30 4/7/75
Set the time to 01:30:00 and the date to 07-Apr-75
Notes:
1.

If neither time nor date is specified, the current
date will be displayed on the entering terminal.

If the time and date are specified, the clock and calendar
will be set; if only the time is specified, the clock will
be set; if only the date is specified, the calendar will be
set.

The order of time and date in the command is not significant.
Either order will be accepted.

All numeric values are decimal.
necessary (or permitted).

4-43

terminating

time

period

and

MCR COMMANDS
USER FILE DIRECTORY
This MCR command creates a user file directory file (UFD) on a
Files-11 volume and enters its name into the master file directory
file (MFD). Each user or group of users desiring private protection
and file access by name requires a UFD. The volume must have been
subjected to Initvolume and Mount commands before UFOs may be defined.
Once a volume has been initialized and mounted, UFOs may be added at
any time.
Format:
UFD dev: [volume-label] [group,member] [/Keyword] [/Keyword]
Keywords:
/ALLOC

number-of-entries

/PRO

[system,owner,group,world]

where:
dev:

- Device-unit containing the volume on
the UFD 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 UFD 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: 32(10)

PRO

- Establishes access rights for the directory
file. Access codes consist of four, 4-code
groups in the Access Rights word,
as
follows:
R
Read
W Write
E = Extend
D = Delete
In each instance, the absence of the code
means that the access right is denied the
user class.

4-44

MCR COMMANDS
Defaults: [RWED,RWED,RWED,RWED]
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
The order of appearance of the
characters R, W, E, and D is fixed.
R, if desired, must be first.

w, if desired, is next.

E, if desired, is next.
D, if des ired, is last.
Thus, RWE and RE are acceptable,
while WR and DEWR are not.
Example:
>UFD DKl: [1,1]
Create a user file directory 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:
UFO -- CAN;T READ MCR COMMAND BUFFER
UFD was initiated by a Run command rather than
MCR command.

error

has

UFD -- DIRECTORY ALREADY EXISTS
The requested UFD already exists on the volume.
UFD -- FAILED TO CREATE DIRECTORY
No space exists on the volume
occurred.

I/O

UFD -- FAILED TO ENTER IN MFD
No room in the MFD, or no room on the
I/O error has occurred on the volume.

volume,

UFD·-- HOME BLOCK I/O ERROR
An error was
block.

detected

4-45

reading

the

volume

home

MCR COMMANDS
UFO -- NOT FILES-11 DEVICE
The device on which the UFO is to be created is not
Files-11 device and therefore cannot support UFOs.

UFO -- WRITE ATTRIBUTES FAILURE
An error was encountered while writing the attributes
of either the MFD or the newly created UFO.
UFO -- WRONG VOLUME
The volume label and
command do not match.

the

label

specified

the

UFO -- VOLUME NOT MOUNTED
Volume on which a UFO is to be created must be mounted
before accessing the Files-11 structure.
Notes:
1.

UFO is valid only for mounted volumes.

4-46

MCR COMMANDS
4.3.3

Informational Commands

DEVICES {privileged)
The Devices command displays the symbolic names
known to the system on the entering terminal.

all

device-units

Format:
DEV [ICES]
Example:
>DEV
DKO:
DK!:
DFO:
DTl:
DT2:
DT3:
LPO:
TTO:

MOUNTED
MOUNTED
MARKED FOR DISMOUNT
OFF LINE

TTl:
TIO:

COO:
CLO:
SYO:

TTO:
LPO:
DKO:

Notes:

MOUNTED is an optional message to indicate that the device is
mounted.

MARKED FOR DISMOUNT is an optional message to indicate that a
mountable device has been requested to be dismounted, but the
dismount operation has not yet been completed.

OFFLINE is an optional message which indicates that, although
the system tables contain entries for this device, the host
configuration does not contain the related device.

A device name in the second column is the device to which the
corresponding device in the first column has been redirected.

4-47

MCR COMMANDS
LOGICAL UNIT NUMBERS {privileged}
The Logical Unit Numbers command is used when the operator needs to
determine which physical devices a task has statically assigned. A
list of physical device units and corresponding logical unit numbers
is displayed on the entering terminal. It indicates which devices
were assigned to the specified task.
Format:
LUN[S] taskname
Example:
>LON XKE
TIO:
TIO:

1
2

CLO:

TT3:
TT3:

DKO:

TT3:

The
display
shows
static
assignments
for
3, 4, 5, 6, and 7, as recorded in the task image
header; no other LUNs are statically assigned to the
XKE.

LUNs
file
task

Command Error Messages:
LUN -- NO LONS
The task which is the argument of the LUNs command
does not have any logical units. This is not an error
message, but rather, an indication that there are no
assignments to display.
Notes:
1.

After a task is in operation, the LUNs command display does
not necessarily reflect the actual assignments in effect.
Assign LUN Exucutive directives issued by the task may have
changed the static assignments.

4-48

MCR COMMANDS
PARTITION DEFINITIONS (privileged)
The Partition Definitions command displays on the entering terminal
description of each memory partition in the system.

The following is displayed:
1.
2.
3.

4.
5.

Partition name;
Partition base address (octal);
Partition size (octal);
Partition kind, main partition or subpartition, and
Partition type, TASK (user-controlled), COM (common),
(device registers), or SYS (system-controlled).

DEV

Format:
PAR [TIT IONS]
Example:
>PAR
LDR
SYS PAR
TKNPAR
GEN
COMP AR
DE VP AR

023544
030100
030100
040000
140000
160000

001000
007700
000400
100000
020000
020000

MAIN
MAIN
SUB
MAIN
MAIN
MAIN

TASK
TASK
TASK
SYS
COM
DEV

Notes:
1.

The display contains the name, base, size, kind, and type
partition in columns 1 through 5, respectively.

Partitions of type TASK are user-controlled task partitions.
COM partitions are used for re-entrant 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. SYS partitions
are system-controlled task partitions.

4-49

MCR COrv!MANDS
TASKLIST (privileged)
The Task List command displays a description
pseudo device CL:. The display contains:
1.
2.
3.
4.
5.
6.
7.
8.

each

task

the

Task name;
Task version identification;
Partition name;
Task priority;
Size of task in bytes (octal);
Load device identification;
Disk address logical block number (octal), and
Task memory state.

Format:
TAS[KLIST]
Example:
>TAS
. LDR.
.TKTN.
... MCR
.•• MOU

OOOlM LDR
OOOlM GEN
OOOlM MCR
OOOlM PAR3K

248.
249.
221.
221.

010600
002200
002200
001400

DKO: -00000010572
DKO: -00000011112
DKO: -00000010511
DKO: -00000011255

FIXED

CHECKPOINTED

Notes:
1.

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.

FIXED indicates that the task is fixed in memory.

CHECKPOINTED indicates that the task has been swapped out
memory to make room for a higher priority task.

4-50

MCR COMMANDS
Task Control Commands

4.3.4

ABORT (some options privileged)
The Abort command allows a console operator to terminate the execution
of an indicated task.
In the example below, the task, SCAN, is
terminated immediately.
Format:
ABO[RT] taskname
Example:
>ABORT SCAN
TASK "SCAN " TERMINATED
ABORTED VIA DIRECTED or MCR
PC=076400
PS=000030
RO=OOOOOO
Rl=004230
R2=074350
R3=000020
R4=000000
R5=076000
SP=076114

Command Error Messages:
When Abort is issued, MCR will cause the Task Termination
Notification routine (TKTN) to run. It is TKTN that produces the
termination display shown in the above example.
Thus, messages
following an Abort command may come from the command itself or
from TKTN. These two possible message origins are presented
separately below.
Message From Abort command:
ABO -- TASK NOT ACTIVE
The specified task is not currently active.
Messages from Task Termination Notification Routine (TKTN):
The Task Termination Notification routine is used to display all
task aborts, whether from the MCR Abort command or some other
source. The display consists of:
TASK "<taskname>" TERMINATED
<abort cause>
The display of the abort cause is followed
task's registers at the time of the abort.
abort causes.

4-51

by a list of the
Listed below are the

MCR COMMANDS
Abort Cause Messages:
ABORTED BY DIRECTIVE or MCR
Either MCR or an Executive directive issued by another
has caused the task to be aborted.
11 40 F.P.

task

EXCEPTION

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

BAD STACK

AN AST cannot be effected because the AST parameters
be pushed onto the task's stack.
CHECKPOINT FAILURE.
Task could not
checkpointed.

cannot

READ ERROR.
be

read

back

into

memory

after

being

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

was

READ ERROR

Task could not be loaded.
MEMORY PROTECT VIOLATION
The task encountered a memory protect violation and
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) and no SST routine was specified to process the
trap.
ODD ADDRESS OR OTHER TRAP FOUR
The task executed a word instruction with an odd address or
referenced a non-existent memory location in an unmapped
system and no SST routine was specified to process the trap.
PARITY ERROR
A parity error occurred while executing the task. The task
is fixed in memory so that the memory will not be re-used by
another task.
RESERVED INST EXECUTION
The task has executed an illegal instruction
routine was specified to process the trap.

4-52

and

SST

MCR COMMANDS
SST ABORT.

BAD STACK

An SST cannot be effected because the SST parameters cannot
be pushed onto the task's stack, or a stack overflow has
been detected in an unmapped system, as indicated by a
nonzero value in the header guard word.
TASK EXIT WITH OUTSTANDING IO
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 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.
TRAP EXECUTION
The task has executed a Trap instruction and no SST
was specified to process the trap.

routine

Notes:
1.

Aborting a task causes an orderly, but forced, termination of
the specified task.
It:
a.

Performs I/O rundown; I/O for all non-file-structured
devices is cancelled. I/O for file-stuctured devices is
allowed to complete and then the files are deaccessed.
All attached devices are detached. 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
the task's registers at termination.
If the task is
checkpointed at the time TKTN is called to process the
abort,
the registers will not be printed. For tasks
whose names begin with" ••. " and which were aborted via
the ABO command, the registers will not be displayed.

Releases the task's partition if the task is not fixed.

An Abort command directed to a task not initiated from the
entering
terminal
may only be issued from privileged
terminals.

4-53

MCR COMMANDS
ALTER (privileged)
This command allows
installed task.

the

operator

change

the

priority

Format:
ALT[ER] taskname /keyword=value
Keyword:
/PRI

priority

where:
taskname - Name of task whose priority is to be altered.
priority - New priority to
task.

assigned

the

specified

Example:
>ALT TEST /PRI=250
Alter the priority of task TEST to 250(8).

Command Error Messages:
ALT -- TASK BEING FIXED
An attempt was made to change the priority of
which is in the process of being fixed.

task

Notes:
1.

A task that is active (not dormant) or being fixed in
cannot have its priority altered.

memory

Priority must be less than or equal to 250(10)
than 0. The numeric conventions apply.

greater

4-54

and

MCR COMMANDS
CANCEL (some privileged options)
The Cancel command allows the operator to cancel 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.

Format:
CAN[CEL] taskname
Example:
>CAN XKE
Cancel all periodic rescheduling and
requests for task XKE.

time-based

initiation

Notes:
1.

A Cancel command directed to a task not initiated from the
entering
terminal
may only be issued from privileged
terminals.

Cancel does not affect the current execution of the task if
it is active. Only the time-based schedule requests still in
the queue are removed.

4-55

MCR COMMANDS
FIX-IN-MEMORY (privileged)
The Fix-in-Memory command allows the operator to force a task to be
loaded and locked into its partition. Subsequent requests for ~he
task to be run will be serviced more quickly, since the task will be
memory resident and will not have to wait for loading from the disk.
Format:
FIX taskname
Example:
>FIX XKE
FIX task XKE in its partition.
Command Error Messages:
FIX -- PARTITION BUSY
Partition in which task is to be fixed
occupied, so task cannot be fixed.

currently

FIX -- TASK BEING FIXED
The subject task is already in the
fixed.

process

being

FIX -- TASK ALREADY FIXED
The specified task is already fixed in memory.
FIX -- TASK CHECKPOINTABLE
A checkpointable task cannot be fixed in memory.
Notes:
1.

Fixed tasks remain physically in memory even after they exit,
and, thus, they need not be reloaded when requested to run.
Their ability to respond to realtime demands is, therefore,
increased.
Only an Unfix command can place the task in a
state which will permit subsequent freeing of the occupied
memory.

A task is fixed upon availability of the partition in which
it is to be fixed. Thus, the task may not be fixed until the
partition is available.

Checkpointable tasks are not fixable.

Active tasks may not be fixed.

A task must be installed before it can be fixed.

4-56

MCR COMMANDS
REASSIGN (privileged)
The Reassign command allows the operator to reassign a task's Logical
Unit Numbers (LUNs)
from one physical device-unit to another. The
reassignments are made in the disk image only.
Format:
REA[SSIGN] taskname lun nud:
where:
lun
nud

Logical unit number
New device-unit.

Examples:
>REA JOE 3 TTO:
Reassign LUN 3 of task JOE to device TTO:.
>REA BILL 2 TTl:
Reassign LUN 2 of task BILL to device TTl:.
Command Error Messages:
REA -- LUN OUT OF RANGE
An attempt has been made to reassign a LUN which is
greater
than the maximum number of LUNs allocated
during task build.
Notes:
1.

Reassign performs re-assignments in the indicated task's disk
image; only the static device assignments are altered.

Reassign does not affect a memory-resident task.
Hence,
Reassign has no effect on the assignments of a currently
executing task, nor on a task that is fixed in memory.
The
Redirect command (see next page) is used for dynamic device
reconfiguration.

4-57

MCR COMMANDS
REDIRECT (privileged)
The Redirect command allows the operator to redirect all I/O requests
directed to a physical device-unit to another physical device-unit.
The Redirect command is especially useful if I/O units required for a
task are inoperable.
Format:
RED[IRECT] nud:=old:
where:
nud:

New device-unit;

this is the redirected-to device;

Equal sign notation for the redirect action;
old:

Old device-unit;
device.

this

the

and,

redirected-from

Examples:
>RED TT3:=TT6:
Redirect all I/O requests for device TT6:

to device TT3:.

>RED TT:=LP:
Redirect all I/O requests for device LPO:

to device TTO:.

Command Error Messages:
RED -- CIRCULAR REDIRECT ERROR
An attempt has been made to redirect a device
that a circular list of redirects would result.

such

RED -- DEVICE NOT REDIRECTABLE
The specified old device may not be redirected.
RED -- NEW DEVICE NOT KNOWN TO SYSTEM
The new device in the Redirect command is not known to
the system (does not exist in the device tables).
RED -- OLD DEVICE ATTACHED
An attempt has
device.

been

made

redirect

attached

RED -- OLD DEVICE MOUNTED
An attempt has been made to redirect a mounted device.

4-58

MCR COMMANDS
RED -- OLD DEVICE NOT KNOWN TO SYSTEM
An attempt has been made to redirect an unknown device
(the device does not exist in the device tables).
RED -- PSEUDO DEVICE REDIRECT ERROR
An attempt has been made to redirect a
to another pseudo device.

pseudo

device

RED -- TI REDIRECT ERROR
The pseudo device TI:

may not be redirected.

Notes:
1.

Redirect does not affect any I/O requests already in the
queue.

The device TI:

A pseudo device may
device.

A mounted volume may not be redirected.

An attached device may not be redirected.

I/O

may not be redirected.
not

4-59

redirected

another

pseudo

MCR COMMANDS
REMOVE (privileged)
The Remove command allows the operator to delete a task name from the
System Task Directory (STD), actually removing the task from the
system. All that remains in the system is the task image file.
Format:
REM[OVE] taskname
Example:
>REM SCAN
Remove task named SCAN from the system.
remains.

The task image file

Notes:
1.

The process of removing a task from the system makes a task
unknown to the system. It is the complement of Install.

To remove a task that is in execution, first abort the
then remove it.

If a task that is the object of a Remove command is fixed, it
is automatically unfixed and then removed.

Remove automatically cancels all time-based schedule requests
for the specified task.

Remove automatically
interrupts.

unlinks

4-60

task

from

all

task,

ICS/ICR

MCR COMMANDS
RESUME (some privileged options)
The Resume command allows the operator to continue the execution of
previously suspended task.

Format:
RES[UME] taskname
Example:
>RES XKE
Resume task XKE.
Command Error Messages:
RES -- TASK NOT SUSPENDED
The task used as the argument of the Resume command is
not currently suspended.
Notes:
1.

A task can only be suspended as a result of a Suspend
directive issued by the running task to suspend itself; a
task cannot suspend any task other than itself.
The Resume
command allows such a suspended task to proceed.

A Resume command directed to a task not initiated from the
entering
terminal
may only be issued from privileged
terminals.

4-61

MCR COMMANDS
RUN
Run is the command which initiates the execution of a task.
a task may be:

With

Run

Started immediately;
Started a time increment from now;
Started a time increment from clock unit synchronization;
Started at an absolute time of day, or
Installed, immediately run, and removed on exit.
All of these options, except install-run-and-remove,
with or without optional rescheduling.

are

available

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

Run Immediate.
RUN taskname [/Keyword] [/Keyword]
Keywords:
/RSI

nnnnu

/UIC = [group,member]
where:
taskname

A 1- to 6-character taskname.

RSI

The reschedule interval. The format is the
same as for dtime 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

Keyword for the UIC parameter.
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
the value established for
from which the Run command is

Run a time increment from now.
RUN taskname dtime [/Keyword] [/Keyword]

4-62

MCR COMMANDS
Keywords:
/RSI

nnnnu

/UIC

[group,member]

where:
taskname

A 1- to 6-character taskname.

dtime

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

A magnitude field, and

A units field.

where:
nnnn
u

The magnitude
Units, with:
T for
s for
M for
H for

ticks;
seconds;

minutes, and
hours.

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 on 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.
(Frequency is selectable
at system generation.)
S

Seconds.

Minutes.

Hours.

The magnitude is the number of units to be
clocked,
but the magnitude value cannot
exceed 24 hours in the specified units.
Units = T. Any positive value is
(maximum of 15 bits).

4-63

valid

MCR COMMANDS
Units = S. Any positive value is
(maximum of 15 bits).
Units

The

valid

maximum

magnitude

maximum

magnitude

1440(10).

Units

H.
The
24(10).

RSI

See Format 1, above.

uic

See Format 1, above.

Run a time increment from clock unit synchronization.
The task start time is determined by first waiting for the
next time unit's occurrence (hour, minute, second, tick) and
then waiting for the specified time increment to elapse.
Run taskname sync [dtime] [/Keyword] [/Keyword]
Keywords:
/RSI

nnnnu

/UIC

[group,member]

where:
taskname

A 1- to 6-character taskname.

sync

H
M

s
T

synchronize on
synchronize on
synchronize on
synchronize on

the
the
the
the

next hour;
next minute;
next second, and
next tick.

dtime

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 1, above.

UIC

See Format 1, above.

Run at an absolute time of day.
RUN taskname a time [/Keyword] [/Keyword]
Keywords:
/RSI

nnnnu

/UIC

[group,member]

where:
taskname

A 1- to 6-character taskname.

a time

Absolute time of day when this task will
initiated. Input format is hh:mm:ss.

4-64

MCR COMMANDS
where:
hh
mm

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

RSI

See Format 1, above.

UIC

See Format 1, above.

Install, run immediately, and remove on exit.
When Run tries to start a task as a type 1 request, it
searches the system task directory (STD) for the task;
if it
finds the entry, it proceeds to run it. However, if the task
is not found, it will attempt to install a task whose
filename is that given as the task name. The directory under
which it looks for this file is determined by the presence or
absence of a leading "$". If no "$" is found, it looks under
the UIC of the terminal requesting the RUN.
If "$" is
present, it looks under
the system directory ([1,50]
for
unmapped systems, and under [1,54] for mapped systems).
RUN

[$]filename [/keyword] [/keyword] ...

Keywords:
/UIC

[group,member]

/PRI

Priority number.

The value range is

through

250 (10).
Default:

/PAR

c: (\

JVo

Partition into
installed.
Default:

(dee imal) .

which

the

task

from task build.

/TASK

Task name. Name which is to be temporarily
assigned to the task while it is running.

/INC

Number of words by which the task is to be
increased.
For system-controlled partitions
only.
(See description of Install command for
more complete explanation.)

where:
$

Optional - specifies that file is
under sys tern UIC ( [ 1, 50] or [ 1, 54]) •

found

filename

Is the name of the task image
run.

Examples:
>RUN XKE lSM
RUN task XKE 15 minutes from command issuance.

4-65

file

MCR COMMANDS
>RUN XKE 15M/RSI=90S/UIC=[3,l]
RUN task XKE 15 minutes from command issuance, rescheduling
it every 90 seconds, with a user identification code of
[3,1].
>RUN $MAC
Run task in file MAC.TSK from the system directory.
automatically installed, run, and removed on exit.

Task is

Command Error Messages:
RUN -- INVALID TIME PARAMETER
A time field is incorrect.
RUN -- TASK BEING ABORTED
A request for the execution of a task has been made,
but the subject task is currently being aborted either
due to an unrecoverable error or as the result of an
operator Abort directive.
Notes:
1.

Formats 1 and 5, i.e., Run Immediate, will establish TI:
as
the terminal from which the task was initiated, if no /RSI is
specified. Otherwise, the TI: terminal will be set to CO:.

A Run immediate, if specified without the /RSI option and
terminated with an ESCape character instead of a carriage
return, will echo the default prompt when the requested task
exits and not when MCR has finished initiating the task.
This provides a facility whereby an operator can determine
that a task which produces no output on a terminal has
exited.

The install, run, and remove form will establish the terminal
from which the command was initiated to be the TI: terminal
and will cause the default prompt to be displayed on TI:
when the task exits. This form of the command is especially
useful when the space available in the dynamic storage region
is small.

4-66

MCR COMMANDS
UNFIX (privileged)
The Unfix command allows the operator to free a fixed task from
memory.
The effect is to allow tasks waiting Lvr. the partition in
Unfix is the
which the task resides to compete for the partition.
complement of the Fix command.
Format:
UNF[IX] taskname
Example:
>UNFIX XKE
Unfix task XKE, freeing the partition in
for task competition.

which

resides

Command Error Messages:
UNF -- TASK NOT FIXED
An attempt has been made to unfix a task which is
fixed.

not

Notes:
1.

If a task exits or aborts, but is fixed, it will still remain
in control of the physical memory in which it resides.

4-67

MCR COMMANDS
4.3.5

System Maintenance Commands

ACTIVE (privileged)
This command will display the names of all active tasks on the
requesting terminal. It is a quick way to determine the status of the
system.

Format:
ACT[IVE]

Example:
>ACT
... MCR
FllACP
... PIP

4-68

MCR COMMANDS
ACTIVE TASK LIST (privileged)
This command will display the name and status of all active tasks in
the system on the entering terminal. It provides information useful
for determining the exact status of each active task.
The following
information is displayed for each task:
1.
2.
3.
4.
5.
6.
7.
8.
9.

Task name;
Task control block physical address (octal);
Partition name;
Partition base and limit physical addresses (octal);
Task status flags;
TI terminal physical device-unit;
I/O count (decimal);
Task local event flags, and
Task registers and Processor Status Word
(memory resident
tasks only) •

The task status flags displayed are those from the task control block
(TCB).
This command will display 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
System Generation Manual for a description of the TCB.) For example,
FXD represents the bit TS.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.
STATUS

TCB FLAG

ABO

TS.ABO
TS.ACF
TS.AST
TS.BFX
TS.CHK
TS.CKD
TS.CKP
TS.CKR
TS.DST
TS.EXE
TS.FXD
TS.HLT
TS.MCR
TS.MSG
TS.PMD
TS.OUT
TS.PRV
TS.RON
TS.REM
TS.SPN

ACP

AST
BFX
-CHK
CKD
CKP
CKR
DST
-EXE
FXD
HLT
MCR
MSG
-PMD
OUT
PRV
RON
REM
SPN
SPNA
STP
WFR
WFRA

TS.STP
TS.WFR

DESCRIPTION
Task is being aborted.
Task is an Ancillary Control Processor.
Task is processing an AST.
Task is being fixed in memory.
Task is not checkpointable.
Task checkpointing is disabled.
Task is checkpointed.
Task checkpoint request pending.
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.
Task Post Mortem Dump disabled.
Task is out of memory.
Task is privileged.
Task I/O is being run down.
Task is to be removed on exit.
Task is being suspended.
Task was suspended prior to AST.
Task stopped for terminal input.
Task is in a "wait-for" state.
Task was in a "wait-for" state prior to AST.

Format:
ATL

4-69

MCR COMMANDS
Example:
>ATL
.•• MCR 061300 SYSPAR 100000-107777 -PMD PRV
TI - TT5:
roe - o. EFLG - 000001 040000 PS - 170000 PC - 103520
REGS 0-6 000106 000001 000004 050372 057066 061300 100372
FllACP 062430 FCPPAR 110000-131777 -PMD ACP PRV WFR
TI - COO:
roe - o. EFLG - 000002 040004 PS - 170000 PC - 100470
REGS 0-6 062442 000000 000001 054054 053054 046212 100264

Notes:
1.

If the task is not in memory (OUT flag
is displayed),
the
contents of the PS, PC and registers will not be displayed.

4-70

MCR COMMANDS
BREAKPOINT TO EXECUTIVE DEBUGGING TOOL (privileged)

(XDT)
This command will pass control to the Executive Debugging Tool
if it has been generated into the system. If XDT is not in the
system, this command is a no-op.

Format:
BRK

Example:

>BRK

Notes:
1.

When XDT gains control, it will print the message
BE: nnnnnn
XDT>
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 and
MCR will prompt with ">".

4-71

MCR COMMANDS
OPEN REGISTER {privileged)
The Open command allows examination and optional modification of a
word of memory. If a location within a task is opened, 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 6-digit octal memory address.

+ or -n

One or more optional octal numbers to be
added to or subtracted from the memory
address.

Keywords:
/TASK

Taskname

/PAR

Partition name

/KNL

(No value is associated with KNL)

TASK, PAR,
systems.

and

KNL

are

applicable

After accepting the first input line, Open
location to be accessed by either using:
1.

The keyword in a mapped system;

Using the specified address
unmapped system.

the

only

mapped

finds

the

memory

actual

address

TASK results in the task partition being located; PAR results in
the named partition being located; and KNL results in Executive
memory (the first 32K of memory) being accessed. If no keyword
is specified, the absolute address is opened.
When TASK and PAR 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 the contents are displayed. The
operator may then enter an optional replacement'value followed by
a line terminator.
The line terminator directs the subsequent action of Open. If a
value is entered, it replaces the contents of the word whose
address and current value are shown by the first part of the
line-2 display. The slash (/) is part of the line-2 display.

4-72

MCR COMMANDS
Line Terminator Options:
ESC

ESCape or ALTMODE:
ESC
(ALTMODE)
terminates
acceptance of further input and is the only means of
exit from the MCR Open function.

Carriage return:
opened.

~CR

Up-arrow (circumflex on some terminals)
return: the previous location is opened.

*CR or @CR

Asterisk carriage return, or
at-sign
carriage
return:
the location pointed to by the contents of
the opened location is opened.

the next

sequential

location

carriage

Example:
>OPE 4+10/TASK=CYCLE
000014 060014/350<ESC>
In this example, the value of the virtual address of 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 is an odd address.

argument

the

Open

The address 3000 is a legal
address 3001 is illegal.

address;

however,

the

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 references 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 is being made to open a task virtual
location.
Since the task is not fixed, it may or may
not be in memory at the time the command is issued.

4-73

MCR COMMANDS
Notes:
1.

In a mapped system, specifying an illegal location or
accessing beyond the limits of the partition will result in
an error. The user is limited to the memory region specified
(TASK or PAR) •

In an unmapped system, any location in physical memory can be
accessed.

In a mapped system, any address of physical
accessed by not specifying a keyword.

4-74

memory

may

MCR COMMANDS
SAVE (privileged)
The Save command is used to write the main-memory resident image of an
RSX-llM system into a task image file such that a hardware bootstrap
or the Boot command may later be used to reload and restart it.
The
saved system is written into the file from which it was originally
booted. This command is intended to provide the user with a facility
for building development systems that have tasks already installed,
thus, eliminating the need for repetitive task installation following
every system bootstrap.
Format:
SA V [ E ] [ /WB]

/WB

Indicates that a boot block pointing to the system
image is to be written out to the system device.
The new boot block will point to the file saved
with the issuance of the command. Thus, on the
next hardware bootstrap, it will be this file that
is loaded.
Without the /WB switch, the file
previously pointed to by the boot block remains in
effect, that is, it is not overwritten.

Example:
>SAV
The current status of the system is saved on the system
disk.
System changes made by the Redirect or other MCR
commands are also saved with the system main-memory resident
image.
Command Error Messages:
SAV -- I/O OUTSTANDING

Tasks remain in the system with I/O requests waiting
to complete.
A system cannot be saved with I/O
outstanding.
SAV -- LABEL BLOCK I/O ERROR
In saving the system image, Save writes the transfer
address in the label block of the system image file.
An error occurred during this write attempt.
SAV -- NOT VALID SAVE DEVICE
A system may only be saved on a directory device.
SAV -- VOLUME(S) STILL MOUNTED
A system may not 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.

4-75

MCR COMMANDS
Notes:
1.

The Save command verifies that
making the following checks:

the

system

No tasks have outstanding I/O;

No mountable devices are mounted.

inactive

and

An error is reported if either of these checks fails.
2.

All RSX-llM system images reside on a file-structured volume
as a special form of a 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) •

This command writes out the system image
which it was booted.

A system may be booted via the hardware bootstrap, in which
case, a specified file is booted (see /WB), or it may be
booted by the Boot command.

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 which were allocated to the system image may
subsequently be reallocated to another file.
A subsequent
bootstrap using the boot block will result in the loading of
possibly random data.

4-76

the

file

from

MCR COMMANDS
TASK LIST - ATL FORMAT (privileged)
This command will display, on the entering
terminal,
the names and
status of all tasks installed in the system in the format of the ATL
command. See the ATL command for a description of the printout.

Format:
TAL

Example:

>TAL
. LDR. 052644 LDR
-000777 -EXE -CHK FXD PRV
TI - COO:
IOC - 0. EFLG - 000001 000000 PS - 170340 PC
REGS 0-6 044632 000010 052364 061332 062660 061300 000534
TKTN
061040 SYSPAR 100000-107777 -EXE -PMD -CHK OUT PRV
TI - COO:
IOC - 0.
EFLG - 000001 000000
RMDEMO 053600 GEN
152000-162477 -PMD -CHK PRV WFR
TI - TTO:
IOC - 0.
EFLG - 000001 000000 PS - 170000 PC
REGS 0-6 105772 104114 000000 10577 001601 105772 101204
... MCR 061300 SYSPAR 100000-107777 -PMD PRV
TI - TT5:
IOC - 0.
EFLG - 000001 040000 PS - 170000 PC
REGS 0-6 000106 000001 000004 050372 077762 061300 100372
FllACP 062430 FCPPAR 110000-131777 -PMD ACP PRV WFR
TI - COO:
roe - 0. EFLG - 000002 040004 PS - 170000 PC
REGS 0-6 062442 000005 000001 056770 053054 046212 100264

4-77

- 045170

- 106566
- 103520
- 100470

MCR COMMANDS
4.4

TASK NAMING CONVENTIONS

RSX-llM may be configured into a single-user system or a multiuser
system.
In order to run many copies of the same task image with as
little impact on the user as possible, a set of naming conventions and
an algorithm have been used.
These conventions are such that the
entire naming algorithm is transparent to the casual user of the
system. This naming convention applies to all tasks which are invoked
as external MCR functions
(e.g., PIP, MOU, MAC, etc.).
On a
single-user system, these tasks are prefixed with
(three
periods) to create the task name (e.g., PIP's task name is " ... PIP").
For multiuser systems, another naming convention applies. The task
name is suffixed with the unit number of the terminal from which it
was invoked (e.g., PIP invoked from Terminal 2 {TT2:) is named
"PIP2"). The user does not need to know this, however, since he may
refer
to the task by the three character command name in all commands
that require a task name. Thus, to abort an external MCR function,
the user types ABO xxx, where xxx is the command name.
For tasks invoked using the install, run, and remove option of the Run
command, the naming is straightforward. It is always named "TTn",
where n is the unit number of the terminal from which it was started.
Again, the user is not required to know this, since the naming
algorithm will automatically find the right task.
However, by not
specifying a task name, the system will automatically search for task
"TTn".
The algorithm which follows applies to all MCR commands which
a task name as an argument.
if found,

require

Search for the explicitly named task;
it.

operate

I f the named task is not found, insure
that the task name
given is three characters long.
If
it is not, the task
cannot be found. I f it is, search for "xxxn", where xxx is
the 3-character name specified on the command, and n is the
unit number of the terminal from which the command was
issued. I f xxxn is found, operate on it.

If xxxn is not found, search for task " ... xxx".
If it is
found, operate on it;
if not found, the task cannot be
found. The TI terminal for •.• xxx must be the same as the
terminal from which the command was issued or the task will
not be found.

If no task name was specified, search for task "TTn", where n
is the unit number of the terminal from which the command was
issued. If TTn is found, operate on it;
if TTn is not
found, the task cannot be found.

This algorithm, as can be seen, proceeds in an orderly way and will
always find the correct task.
In addition, task names used by
single-user systems default correctly, since tasks of the name "xxxn"
will not be in the system, and the search will go to step 3 of the
algorithm.
For
tasks
on
multiuser
systems
running
in
system-controlled partitions, this algorithm also works, since it
always searches for task "xxxn" before " .•• xxx".
(See the RSX-llM
System Generation Manual for a more detailed description of multiuser
sys terns.)

4-78

MCR COMMANDS
Examples:
1.

On terminal TT2:, the sequence of commands
>RUN $PIP
PIP>"C<CR>
MCR>ABO<CR>
will abort task TT2 (in reality PIP), which was caused to
run by the Install-Run-and-Remove command.

On terminal
sequence

TTO:,

single-user

system,

the

command

>PIP
PIP>"C<CR>
MCR>ABO PIP

will abort task " •.. PIP".
3.

On terminal TTl:, where task PIPl has been installed or has
been dynamically created in a system-controlled partition,
the sequence,
>PIP
PIP>"C<CR>
MCR>ABO PIP
will abort task "PIPl".

On terminal TTl:, where task ... PIP is running, the sequence
>PIP
PIP>"C<CR>
MCR>ABO PIP
will abort task " ... PIP", since PIPl is not in the system.
NOTE
In this case, a check is made
to
determine if the TI terminal for task
... PIP is the same as TTl:. If not, the
task would not be found.

4-79

CHAPTER 5
INDIRECT COMMAND FILES

5.1

INDIRECT COMMAND FILES

An indirect command file is a text file containing a list of commands
exclusive
to, and interpretable by, a single task, usually a
system-supplied component of RSX-llM, such as MACR0-11 or the Task
Builder.
In addition to task components, MCR has an indirect file
processor ( ... AT.) which interprets commands and either acts on them
or passes them on to MCR for processing.
Indirect files are initiated by replacing the command string
by a task with a file specifier preceded by an at sign (@}.
For example, to initiate a file of MACR0-11 commands, the
input:

required

user

would

>MAC @INPT.CMD
After MACR0-11 is initiated, it accesses the
commands.

file

INPT.CMD

To initiate a file of MCR commands, the user would simply
file specifier preceded by an at (@) sign, as shown below,

for

its

enter

the

>@f ilespec
anytime MCR will accept input.
The default file type for indirect command files is .CMD. An indirect
file may contain any command interpretable by the task to which it is
directed, but no others.
Indirect files for tasks other than MCR may not contain indirect
references.

file

MCR indirect files may reference other MCR indirect files, but the
maximum nesting depth is limited to four levels of files. MCR will
display on the requesting terminal every command retrieved from an MCR
indirect command file.

5.2

MCR INDIRECT FILE PROCESSOR

The MCR indirect file processor task (AT.) is capable of reading a
command input file and interpreting each line as either a command to
be passed directly to MCR or a reguest for action by the task itself.

5-1

INDIRECT COMMAND FILES
Commands for MCR are simply entered on a line, requiring no special
prefix characters, whereas commands to the indirect command file
processor always begin with a period (.). Comments are indicated by a
leading exclamation point or semicolon and are printed on the entering
terminal.
Commands interpreted by
following capabilites:

the

indirect

file

processor

provide

the

Define a label (.label:);
Ask a question and wait for reply (.ASK);
Delay execution for a specified period of time (.DELAY);
Branch to a label {.GOTO);
Determine whether a task is active or not {.IFACT/.IFNACT);
Determine whether a symbol is defined or not {.IFDF/.IFNDF);
Determine whether a task is installed in the system or not
{.IFINS/.IFNINS);
Determine whether a symbol is true or false (.IFT/.IFF);
Branch to a label on detecting an error (.ONERR);
Pause for operator action {.PAUSE);
Set the value of a symbol to true or false (.SETT AND .SETF);
Wait for a task to finish execution (.WAIT);
Start a task, pass a command line to it and continue (.XQT), and
provide commentary ("!text" OR ";text").

5.2.1

Symbols

It is possible to define symbols which represent true or false values
and which may be tested to control flow through the indirect command
file. Symbols are one to six ASCII characters in length.
Numb~rs,
upper and lower case letters, and special characters are all valid.
Symbols are defined by the .ASK directive or by the .SETT and .SETF
directives.
The first appearance of the symbol in one of these
directives defines the symbol and sets it to true or
false;
subsequent directives may test the value or redefine it.
There is one special symbol which is always defined and is used to
determine whether the system on which the user is running is mapped or
unmapped. This symbol is
<MAPPED>
The brackets are required syntax. If the system is unmapped, <MAPPED>
has a value of false;
if the system is mapped, it has a value of
true.
Example:
.IFT <MAPPED> SET /UIC=[l,54]
If the system is mapped, the Set command is passed to MCR.

5-2

INDIRECT COMMAND FILES
5.2.2

Commands to MCR

A command is normally passed directly to MCR for processing, and the
indirect file processor waits until MCR has processed it before going
on to the next command in the file. However, if the first character
in the line is a period (.), this signals that the command is to be
interpreted by the indirect file processor and appropriate action is
to be taken. The command is scanned and processed from left to right.
When the final command on the line is processed and the conditions are
true, the rest of the line will be passed to MCR.
If the conditions
are false, the rest of the line will be ignored and the next line will
be processed.
Example:
.IFNINS ... PIP INS [l,50JPIP

If task ... PIP is not installed, the command INS [l,SO]PIP will be
passed
to
MCR
for execution.
If ... PIP was installed, the
INS [l,50]PIP command would not be passed to MCR. Each command passed
to MCR is also displayed on the entering terminal as a log of executed
commands.

5.2.3

Switches

The indirect file processor accepts two switches:

/TR and /DE.

/TR

Indicates that a trace of each line processed is to be
provided 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 mark (comment) and displayed. If
the command causes some action to occur, the next line
printed
will indicate the action:
usually, this line
consists of the MCR commands issued as a result of the
previous directive.

/DE

Indicates that the indirect command file
when processing is complete.

deleted

These switches may be prefixed with a minus sign (-) or "NO" to negate
the action of the switch, e.g., /NOTR will not generate a trace. The
defaults are /NOTR and /NODE.

5.2.4

Multi-Level Indirect Files

Up to four levels of indirect command files may be specified.
Each
time a new level is entered, all symbols previously defined are masked
out of the symbol table, and only symbols defined in the current level
are avaliable;
symbols are local to the level of command file in
which they are defined. When control returns to a previous level, the
symbols defined in that level are available again.

5-3

INDIRECT COMMAND FILES
5.2.5

Syntax

All directives are separated from their arguments by at least one
space.
MCR commands are separated from directives by at least one
space.

5.2.6

Directives

5.2.6.1

Define a Label

.label:

Labels are always at the beginning of the line; they may be on a line
with additional directives and/or an MCR command, or on a line by
themselves. When control is passed to a line with a label, the line
is processed as if the label was not there. Commands do not have to
be separated from the label by a space. Only one label is permitted
per line. Labels are 1 to 6 characters long and must be preceded by a
period and terminated by a colon.
Any valid ASCII character is
allowed in a label.
Examples:
.100:

.HERE:
.10$:

5.2.6.2

Ask a Question and Wait for a Reply

The .ASK directive will ask a question, wait for a reply, and set a
specified symbol to the value of true or false, depending on the
reply. If the symbol is not defined, an entry will be made in the
symbol table. If the symbol is already defined, its value will be set
by the answer to the question.
Format:
.ASK ssssss txt-strng
where:
ssssss

1- to 6-character symbol which is assigned a
true/false value.

txt-strng

any ASCII string of characters which must be
preceded by at least one blank.

The text-string will be prefixed with an asterisk and suffixed with
"? [Y/N] :"
when it is displayed. Three answers are recognized by the
indirect file processor:
1. Y<CR> - set symbol ssssss to true.
2. N<CR> - set symbol ssssss to false.
3. <CR> - set symbol to false.
<CR> indicates carriage return.

5-4

INDIRECT COMMAND FILES
Example:
.ASK A DO YOU WANT TO INSTALL PIP
will display

>* DO YOU WANT TO INSTALL PIP? [Y/N]:
on the entering terminal.

5.2.6.3

Symbol A will be set to true or false.

Delay Execution for a Specified Period of Time

The .DELAY directive is used to delay further
indirect file for a specified period of time.

.DELAY

processing

the

Format:
.DELAY nnu
where:
nn
Number of time units to delay
u = T - ticks;
S - seconds;
M - minutes, and
H - hours.
The parameter nn is octal,
example:

unless

terminated

with

period.

lOS is 10(8) seconds
10.S is 10(10) seconds
When the DELAY directive is executed, the message
AT.

DELAYING

is issued.
When the time period expires and the task resumes, the message
AT.

CONTINUING

is issued.
Example:
The directive
.DELAY 20M
will delay processing for 20 (8), or 16 {10) minutes.

5-5

For

INDIRECT COMMAND FILES
5.2.6.4

Branch to a Label

Branches from one line in an indirect file to another are accomplished
with the .GOTO directive. All commands between the .GOTO directive
and the specified label are ignored.
Branches may go forward or
backward in the file.
Format:
.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
will transfer control to the line containing the label .100:.

5.2.6.5

Logical Test {IF)

There are a number of directives which make tests;
if the test is
true, the rest of the command is processed. Logical tests may be
combined into a compound logical test with the .AND and
.OR
directives.

5.2.6.5.1

Test if Symbol Is True or False

The value of a symbol may be tested for true or false;
true, the rest of the command is processed.

.IFT/.IFF
if the test is

Format:
• IFT
. IFF

ssssss
ssssss

If symbol ssssss is true .
If symbol ssssss is false .

The symbol must be preceded and followed by at least one blank, except
at the end of a line, in which case, it need not be followed by a
blank.
Example:
.IFT
.IFF

A
B

.GOTO
.GOTO

100
200

5-6

INDIRECT COMMAND FILES
5.2.6.5.2

Test if Symbol Is Defined or Not Defined

.IFDF/.IFNDF

A test can be made to determine whether a symbol has been defined or
not defined;
if the rPRr is true, the rest of the command is
processed. This directive does not test the value of the symbol.
Format:
. IFDF ssssss
. IFNDF ssssss

If symbol ssssss is defined •
If symbol ssssss is not defined .

The symbol ssssss must be preceded and followed by at least one blank,
except at the end of a line, in which case, it need not be followed by
a blank.
Example:
.IFDF A .GOTO 100
.IFNDF A .ASK A DO YOU WANT TO SET TIME

5.2.6.5.3

Test if Task Is Installed or Not Installed

.IFINS/.IFNINS

A test can be made to determine whether a r~Rk is installed in rhP
system; if the test is true, the rest of the command is processed.
Format:
. IFINS tttttt
. IFNINS tttttt

If task tttttt is installed .
If task tttttt is not installed .

The task name tttttt must be preceded and followed by at least one
blank, except at the end of a line, in which case, the trailing blank
is not required.
Example:

.IFINS ••. PIP .GOTO 250
.IFNINS ••. PIP INS [l,50]PIP

5.2.6.5.4

Test if Task Is Active or Not Active

.IFACT/.IFNACT

A test can be made to determine whether a task is active;
is true, the rest of the command is processed.

if the test

Format:
. IFACT tttttt
. IFNACT tttttt

If task tttttt is in execution .
If task tttttt is not in execution .

The task name tttttt must be preceded and followed by . at least one
blank, except at the end of a line, in which case, it need not be
followed by a blank.

5-7

INDIRECT COMMAND FILES
Example:
.IFACT
.IFNACT

5.2.6.5.5

REPORT
REPORT

.GOTO 350
RUN REPORT

Compound Tests

"If" tests may be combined via the .AND and .OR directives.
In
addition, an implied .AND is effected when multiple IFs appear on the
same line without being separated by an .AND directive. In this case,
the command is executed only if all tests are true. The compound
operators .AND and .OR must be preceded and followed by at least one
blank.
Examples:
.IFT A .AND .IFF B .GOTO C
.IFT A .IFF B .GOTO C
.IFT A .OR .IFF B RUN PIP

5.2.6.6

Same effect as first line

Branch to Label on Detecting an Error

.ONERR

If one of the following errors is detected:
1.

Undefined symbol referenced,

Symbol table overflow,

Undefined label, or

Syntax error,

control will be passed to the line containing the specified label.
This feature provides the user with a means of gaining control to
terminate command file processing in an orderly manner.
Format:
.ONERR

label

Control is passed to the line starting with ".label:" upon detecting
an error.
The .ONERR directive may be issued at any place in the
command file. If the directive is executed, error processing will be
passed to that 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, the task will exit.
Example:
.ONERR

100

5-8

INDIRECT COMMAND ¥ILES
5.2.6.7

Pause for Operator Action

.PAUSE

It is possible to interrupt the processing of an indirect file and
for operator action. This is done using cne .~Au~~ directive.
Issuing a .PAUSE directive will cause the indirect file processor task
to supend itself. The operator may perform some specified operations
and then cause the task to resume.

wait

Format:
.PAUSE
When the indirect file processor task suspends itself, it displays the
following message on the entering terminal:
AT. -- PAUSING.

TO CONTINUE TYPE "RES tttttt"

where:
tttttt

is the name of the task.

When the operator is ready to resume, he types:
>RES

tttttt

The task then prints out:
AT.

-- CONTINUING

and it continues processing where i t left off.

5.2.6.8

Set Symbol to True or False

.SETT/.SETF

A symbol may be defined or its value may be changed by use of the
.SETT/.SETF a1recc1ves. If the symbol is not defined, a symbol table
entry is built and set to the appropriate value;
if the symbol
exists, the value is set appropriately.
Format:
.SETT
• SE'I'F

ssssss
ssssss

Set symbol ssssss to true .
Set symbol ssssss to false.

The symbol ssssss must be preceded by at leest one blank.
Example:
.SETT
.SETF

X
ABCDE

5-9

INDIRECT COMMAND FILES
5.2.6.9

Wait for a Task to Finish Execution

Processing of the indirect command file may be suspended until
particular task has terminated by issuing the .WAIT directive.

Format:
.WAIT

tttttt

The task name tttttt must be preceded by at least one blank.
Example:
.WAIT

5.2.6.10

PIP

Initiate Parallel Task Execution

Normally, a command is passed to MCR and the indirect file processor
waits until the command is completely executed.
However, it is
possible 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 will continue as soon
as the Run command is processed. But the user is not able to pass a
command string to the target task via the Run command. Using the .XQT
directive, it is possible to start a task, pass a command string to
it, and continue processing command lines in parallel with the
initiated task.
Format:
.XQT

cmd command-string

where:
cmd

is the name of the task
DMO).

(e.g.,

command-string

is the command to the task.

MAC,

PIP,

Using the .XQT command provides a facility to initiate parallel
processing of tasks. To synchronize the execution of parallel tasks,
the .WAIT directive can be used to suspend command file processing
until the specified task has completed.
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-10

parallel

INDIRECT COMMAND FILES
5.2.6.ll

Comments

Comments are indicated by a leading semicolon (;).
Comments may also
appear within paired exclamation marks.
Comments are displayed on the
entering terminal to provide an explanation or instructions regarding
an indirect command file.
Example:
THIS IS A COMMENT!
THIS IS A COMMENT ALSO

5.2.7

Task Name References

Task name references in an indirect command file follow the same rules
as for
MCR.
If the task was started as an external MCR task (e.g.,
MAC, PIP, DMO), it may be referenced by its 3-character name.
Thus,
the .WAIT, .IFINS, .IFACT directives need only specify the 3-character
command name and the indirect file processor will
find
the correct
task.
Of course, a specific task may be referenced using its full
6-character name.

5.2.8

Example of Command File and Its Execution
Command File

EXAMPLE OF INDIRECT COMMAND FILE PROCESSOR COMMANDS
.SETF PIPINS
.ASK CONT DO YOU WANT TO CONTINUE
.IFF CONT .GOTO 100
.10:.IFINS PIP .SETT PIPINS
.IFNINS PIP INS [l,54]PIP
.!FINS PIP
PIP IS INSTALLED
.!FACT AT.
INDIRECT FILE PROCESSOR IS ACTIVE
.IFNDF X ; X IS NOT DEFINED
.SETF X
.IFDF X ; X IS NOW DEFINED
.ONERR 50
.!FT Y .GOTO 60
.50:; Y IS NOT DEFINED - ONERR EXAMPLE
.60:.PAUSE
.DELAY SS
.IFDF PIPINS .AND .IFDF X ; TEST OF AND
.IFDF PIPINS .OR .IFDF Z ; TEST OF OR
.ASK LOOP DO YOU WANT TO LOOP
.IFT LOOP .GOTO 10
.100:.ASK X DO YOU WANT TO GO TO SECOND LEVEL FILE
.IFT X @LEVEL2
;RETURN TO LEVEL 1 FILE
.XQT PIP
.WAIT PIP

5-11

INDIRECT COMMAND FILES
Execution of Command File
>@ATEXMPL

>; EXAMPLE OF INDIRECT COMMAND FILE PROCESSOR COMMANDS

>;
>*
>;
>;
>;
>;

DO YOU WANT TO CONTINUE? [Y/N] :Y
PIP IS INSTALLED
INDIRECT FILE PROCESSOR IS ACTIVE
X IS NOT DEFINED
X IS NOW DEFINED

AT. -- UNDEFINED SYMBOL Y
>; Y IS NOT DEFINED - ONERR EXAMPLE

AT. -- PAUSING. TO CONTINUE TYPE "RES AT.O
>RES AT.
AT. -- CONTINUING

>
>

AT.

DELAYING

AT.
CONTINUING
>; TEST OF AND
>; TEST OF OR
>* DO YOU WANT TO LOOP? [Y/N] :N
>*DO YOU WANT TO GO TO SECOND LEVEL FILE? [Y/N]:Y

>;
>; LEVEL 2 FILE
>; RETURN TO LEVEL 1 FILE
>PIP
PIP>

>"'z

@ <EOF>
)

5.2.9

Error Messages

AT. -- BAD COMMAND OR SYNTAX
A directive is unknown or the syntax of
incorrect.

the

directive

AT. -- BINARY OPERATOR ERROR
Incorrect use of the .AND or .OR directives.
AT. -- CONTINUING
Not an error message. Indicates that the indirect file
processor is resuming execution after a .PAUSE or .DELAY
directive.
AT. -- DELAYING
Not an error message.
was just executed.

Indicates that

5-12

.DELAY

directive

INDIRECT COMMAND FILES
AT. -- FILE READ ERROR
An error was detected in reading the indirect file.
Usually due to records which are more that 80. bytes long.
AT. -- INVALID ANSWER
In response to a question from .ASK, the operator entered
something other than Y, N, or null, followed by carriage
return. The question will be repeated.
AT. -- MAXIMUM INDIRECT FILES EXCEEDED
An attempt has been made to reference an indirect file at a
nested depth greater than four.
AT.

PAUSING.

TO CONTINUE TYPE "RES tttttt"

Not an error message. The indirect
executed a .PAUSE directive.
AT. -- RECORD LARGER THAN 80.

file

processor

just

BYTES

A record larger than 80.
Maximum record size is 80.

bytes
bytes.

has

been

encountered.

AT. -- REDEFINING SPECIAL SYMBOL
An attempt has been made to change the value of a special
symbol (i.e., those bracketed with"<" ">"). They may not
be redefined.
AT. -- SYMBOL TABLE OVERFLOW ssssss
The symbol table is full and there is no space
ssssss.

for

symbol

AT. -- QNDEFINED LABEL 1111111
The label 111111 specified in a .GOTO or
cannot be found.

.ONERR

directive

not

AT. -- UNDEFINED SYMBOL ssssss
The symbol ssssss is being tested,
defined.

but

has

been

Notes:
1.

The default file type for indirect command files is .CMD.

When the indirect file processor reaches the
the top level file, it will display:
>@ <EOF>
and exit.

5-13

end-of-file

CHAPTER 6
MCR ERROR MESSAGES

6.1

INTRODUCTION

All messages from MCR and TKTN appear in this section in alphabetical
order.
Some messages include an action subheading that suggests
remedial action to be taken by the operator. In messages where the
required action is obvious or contained in the description of the
message, the action subheading is omitted.

6.2

MESSAGES

11 40 FP.

EXCEPTION
This is a TKTN message.
The task has encountered a
floating point exception while executing on a PDPll/40 and
no SST routine was specified to handie the trap.

XXX -- ACP NOT IN SYSTEM
The specified Ancilliary Control Processor is not installed
in the system.
XXX -- ALIGNMENT ERROR
An attempt has been made to create a partition but the base
address or size conflicts with existing partitions or
physical memory size.
XXX -- ALLOCATION FOR SYS FILE EXCEEDS VOLUME LIMIT
Unable to allocate system file from specified block due
intermediate bad blocks or end-of-volume.

XXX -- ALREADY MARKED FOR DISMOUNT
The device-unit has already been requested to be dismounted
and the associated ACP is in the process of waiting for all
accesses to the volume to complete.
XXX -- ALREADY MOUNTED
The network device specified has already been mounted.

6-1

MCR ERROR MESSAGES
AST ABORT.

BAD STACK
This is a TKTN message. An AST cannot be effected because
the AST parameters cannot be pushed onto the task's stack.

XXX - BAD COMMAND OR SYNTAX
A directive is unknown or the syntax of
incorrect.

the

directive

block

file

XXX -- BAD BLOCK FILE FULL - TASK ABORTED
The disk has more than 102 bad regions on it.
XXX -- BAD BLOCK HEADER I/0 ERROR
A write error was detected in writing the
header.

bad

XXX -- BASE ADDRESS MUST BE ON 4K BOUNDARY
The base address of the task is not
Applicable only to mapped systems.

boundary.

XXX -- BASE MISMATCH COMMON BLOCK <common-name>
The base address of the common block, as recorded in the
task image, does not match the base address of the resident
common block.
XXX -- BINARY OPERATOR ERROR
Incorrect use of the .AND or .OR
directives.

indirect

file

processor

XXX -- BLOCK(S) EXCEED VOLUME LIMIT
Specified block (or
volume.

blocks)

exceed(s)

physical

size

XXX -- BOOT BLOCK WRITE ERROR
An error was detected in writing the volume boot block.
XXX -- BYTE ADDRESS
The address specified as the argument to the Open command
is an odd address.
For example, the address 3000 is a
legal address; however, the address 3001 is not.
XXX -- CAN'T READ MCR COMMAND BUFFER
UFD was started by a Run command rather than by
command; therefore, the command cannot be parsed.

MCR

XXX -- CHECKING ddnn:
Automatic pad block specification is proceeding, using the
bad block file produced by the Bad Block Locator utility
program.

6-2

MCR ERROR MESSAGES
XXX -- CHECKPOINT AREA TOO SMALL
The area allocated for checkpointing the task is smaller
than the partition into which it is being installed.
CHECKPOINT FAILURE.

READ ERROR

This is a TKTN message. The task could not
into memory after being checkpointed.

*** ddnn:

read

back

occurred

while

CHECKPOINT WRITE ERROR
This is a TKTN message. Write failure has
attempting to checkpoint a task.

XXX -- CIRCULAR REDIRECT ERROR
An attempt has been made to redirect a device such
circular list of redirects would result.

that

XXX -- COMMAND I/O ERROR
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

COMMON BLOCK IS TASK PARTITION <common-name>
A task's request for access to a common block is rejected
because the partition requested is a task partition.

XXX -- COMMON BLOCK NOT LOADED <common-name>
The specified common block is linked to the task but has
not been loaded into the system. Install the specified
common block, then install the task.
XXX -- COMMON BLOCK OCCUPIED
An attempt has been made to load a common

block

which

already occupied.

XXX -- COMMON BLOCK PARAMETER MISMATCH <common-name>
Parameters (partition name and PIC attributes) of a
block do not match those in the task's label block.

common

XXX -- CONTINUING
Not an error message. Indicates that the indirect file
processor is resuming execution after a .PAUSE or .DELAY
directive.
XXX -- DATA ERROR
Bad block number or contiguous region
specified. Reenter properly.

6-3

size

too

large

MCR ERROR MESSAGES
XXX -- DELAYING
Not an error message. A .DELAY directive was just executed
by the indirect file processor.
XXX -- DEVICE ATTACHED
The specified device is currently attached by
may not be mounted.

task

and

XXX -- DEVICE NOT DEFINED IN NETWORK
The specified device has not been defined in
topology and therefore may not be mounted.

the

network

XXX -- DEVJCE NOT IN SYSTEM
The device specified in the command was not generated into
the system. Devices that are to be used in the system must
be specified during system generation.
XXX -- DEVICE NOT MOUNTED
The device specified
mounted.

the

file

specification

not

XXX -- DEVICE NOT READY
Specified device is not ready.
XXX -- DEVICE NOT REDIRECTABLE
The specified device may not be redirected.
XXX -- DEVICE NOT TERMINAL
An attempt has been made to
for a non-terminal device.

set

terminal

characteristics

XXX -- DEVICE OFFLINE
The specified device, although generated into the system,
is not physically present in the host configuration.
XXX -- DEVICE WRITE-LOCKED
Specified device is hardware write-locked.
XXX -- DIRECTORY ALREADY EXISTS
The requested user file directory file
the volume.

***

ddnn:

already

exists

DISMOUNT COMPLETE

This is a TKTN message. This indicates that the device
requested to be dismounted is now logically disconnected
from the system, i.e., all files are deaccessed and the VCB
is deallocated.

6-4

MCR ERROR MESSAGES
XXX -- DPB ERROR
A bad DPB was created by MCR.
cne

system

itself

has

This

faulted.

error

indicates

that

If the error persists,

consult your local DEC software specialist.
XXX -- DUPLICATE BLOCK(S) FOUND
A block which has been specified as bad is being defined as
bad a second time.
XXX -- FAILED TO CREATED A DIRECTORY
No space exists
occurred.

the

volume,

I/O

error

has

XXX -- FAILED TO ENTER IN MFD
No space exists in the master file directory, or no space
exists on the volume, or an I/O error has occurred on the
volume.
XXX -- FATAL I/O ERROR
An input or output operation cannot be completed due to the
unavailability of a device or dynamic memory, or a device
error has occurred.
XXX -- filename FILE HEADER I/0 ERROR
An error was detected in trying to write
header for the specified system file.

out

the

file

XXX -- FILE HEADER READ ERROR
Mount cannot read either the
allocation file.
Action:

Determine the problem;
contact Field Service.

index

file

the

storage

if it is a hardware error,

XXX -- FILE NOT CONTIGUOUS
An attempt is being made to boot a system or install a task
from a non-contiguous file. System images and task images
must be contiguous.
XXX -- FILE NOT FOUND
The requested file is not in the directory on the specified
volume.
XXX -- FILE NOT TASK IMAGE
Data in the label block is not correct, indicating the file
is not a valid task image.

6-5

MCR ERROR MESSAGES
XXX -- FILE READ ERROR
An error was detected in reading an indirect file.
This
error is usually due to records which are more than 80.
bytes long.
XXX -- HOME BLOCK ALLOCATE WRITE ERROR
In overwriting
occurred.

bad

home

block

area,

write

error

XXX -- HOME BLOCK CHECKSUM ERROR
The checksum in the home block and the calculated checksum
do not agree. This condition is probably caused by an I/O
error.
XXX -- HOME BLOCK I/0 ERROR
An error was detected in reading or writing the volume home
block.
XXX -- HOME BLOCK READ ERROR
An error as 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
A write error was
block.

detected

writing

the

volume

home

XXX -- ILLEGAL DEVICE ddnn:
The device specified at
command keyword option
system.

task-build time by the Assign
(Devices) does not exist in the

XXX -- ILLEGAL DEVICE/VOLUME
The device specified is not a valid task residence device.
XXX -- ILLEGAL FIRST APR
A pri~ileged task built to run using APR 4, 5, or 6 as its
base, is too large. Using APR4, the task is larger than
12K; using APRS, the task is larger than SK; using APR6,
the task is larger than 4K.
Applies only to mapped
systems.
XXX -- ILLEGAL FUNCTION
A command has been entered which

MCR

cannot recognize.

XXX -- ILLEGAL KEYWORD VALUE
A value entered for a keyword exceeds its limits.
legal value.

6-6

Enter

MCR ERROR MESSAGES
XXX -- ILLEGAL PRIORITY
The value of the priority in the command is
(i.e., not l

out

range

index

file

bit

to 250 (10), inclusive).

XXX -- INDEX FILE BIT MAP I/O ERROR
An error was detected in writing out
map.

the

XXX -- INPUT I/0 ERROR
In attempting to read the next command,
detected an error.

the

Open

command

XXX -- INVALID ADDRESS
The address specified as an argument in the Open command
references a nonexistent memory location or an address
outside the boundaries of the specified partition.
XXX -- INVALID ANSWER
In response to a question from the indirect file processor
directive .ASK, the operator entered something other than
Y, N, or null, followed by carriage return.
The question
will be repeated.

XXX -- INVALID KEYWORD
A keyword has been encountered which is not recognizable by
the specific command processor.
XXX -- INVALID LOAD DEVICE
The Boot or Install command has detected a device which
invalid as a system or task residence device.

XXX -- INVALID TIME PARAMETER
A time field is incorrect.
XXX -- INVALID UIC
A value of zero for either the group number or
number was detected.

the

member

!OT EXECUTION
This is a TKTN message. The subject task has executed an
!OT instruction and no SST routine was specified to process
the trap.
XXX -- I/O OUTSTANDING
Tasks remain in the system with I/O requests waiting to
complete. A system cannot be saved with I/O outstanding.
Action:

Wait for I/O to complete and re-enter the command.

6-7

MCR ERROR MESSAGES
XXX -- LABEL BLOCK I/0 ERROR
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
The Boot command cannot read the label block of the
image.

system

xxx -- LENGTH MISMATCH COMMON BLOCK <common-name>
The length parameter for the common block, as described in
the label block for the task image, does 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 -- LISTING DEVICE NOT AVAILABLE
The device-unit to which MCR is attempting to display
information (PAR, DEV, etc.) is attached and is unavailable
for use.
·
LOAD FAILURE.

READ ERROR

This is a TKTN message.
loaded.

The requested task

could

not

XXX -- LOGICAL DEVICE NOT IN SYSTEM
The specified logical device is not defined in the
device tables.

logical

XXX -- LUN OUT OF Rf,NGE
An attempt has been made to re-assign a LUN which is
greater than the maximum number of LUNs allocated during
task build.
XXX -- MAXIMUM INDIRECT FILES EXCEEDED
An attempt has been made to access an indirect file at a
depth greater than four levels. MCR indirect files may
nest to a maximum of four levels in depth.
MEMORY PROTECT VIOLATION
This is a TKTN message.
protect violation and
process the trap.

The task encountered a memory
no SST routine was specified to

XXX -- MFD WRITE ERROR
An error was
directory.

detected

6-8

writing

out

the

master

file

MCR ERROR MESSAGES
XXX -- NEW DEVICE NOT KNOWN TO SYSTEM
New device in Redirect command is not known to
(does not exist in the device tables).

the

system

XXX -- NO BAD BLOCK DATA FOUND
Although automatic bad block specification was selected, no
bad block file could be found on the volume. This is a
warning message.
XXX -- NO LUNS
The task which is the argument of the LUNs command does not
have any logical units. This is not an error message, but
rather an indication that there are no assignments to
display.
XXX -- NO POOL SPACE
Request for dynamic memory
satisfied by the Executive.

MCR

cannot

currently

XXX -- NO ROOM AVAILABLE IN STD FOR NEW TASK
This message means that there is no dynamic storage
available to make an entry in the System Task Directory
(STD); therefore, no task can be installed.
XXX -- NO TRANSFER ADDRESS
The Boot command could not find a transfer address
virgin system image (result of a task build).

XXX -- NON EXISTENT MEMORY
An attempt has been
non-existent memory.

made

define

partition

NON RSX EMT EXECUTION
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
Because of the virtual base address of the task, there
not enough APRs left to map the entire task image.

are

XXX -- NOT MOUNTABLE DEVICE
The specified device-unit is not
therefore cannot be mounted.

mountable

XXX -- NOT MOUNTED
The device specified is not currently mounted.

6-9

device

and

MCR ERROR MESSAGES

***

dnn:

NOT READY
This is a TKTN message.

Specified device is not ready.

XXX -- NOT SYSTEM IMAGE
The Boot command has determined that
system image.

the

file

not

XXX -- NOT VALID SAVE DEVICE
The Save command may be issued only to directory devices.
ODD ADDRESS OR OTHER TRAP FOUR
This is a TKTN message.
The task executed a
word
instruction
with
an
odd
address
or referenced a
non-existent memory location in an unmapped system and no
SST routine was specified to process the trap.
XXX -- NT DEVICE NOT MOUNTED
The device NT:
devices.

must be mounted before

any

other

network

attached

XXX -- OLD DEVICE ATTACHED
An attempt has
device-unit.

been

made

redirect

XXX -- OLD DEVICE MOUNTED
An attempt has been made to redirect a mounted device-unit.
XXX -- OLD DEVICE NOT KNOWN TO SYSTEM
An attempt has
device-unit.

been

made

redirect

unknown

XXX -- OTHER VOLUME MOUNTED
An attempt has been made to mount a volume on a device-unit
which already has a volume mounted.
XXX -- OUTPUT ERROR
An MCR terminal-write operation has failed.
PARITY ERROR
This is a TKTN message. A parity error occurred during
task execution.
The task is fixed in memory so that the
memory will not be reused for another task.
XXX -- PARTITION BUSY
The partition in which a task is to be fixed is currently
occupied by a running task:
thus, the task may not be
fixed.

6-10

MCR ERROR MESSAGES
XXX -- PARTITION ALREADY EXISTS
An attempt has been made to define a partition with a
that is already in use.

name

XXX -- PARTITION NOT COMMON
A partition specified for a common or resident
not defined as a common partition.

library

XXX -- PARTITION NOT IN SYSTEM
The partition name specified as an argument in a command,
or during task build, cannot be found in the system.
XXX -- PAUSING.

TO CONTINUE TYPE "RES tttttt"

Not an error message. The indirect
executed a .PAUSE directive.

file

processor

just

XXX -- PRIVILEGED COMMAND
A command was issued from a non-privileged terminal that is
available only to privileged terminals.
XXX -- PRIVILEGED TASK LARGER THAN 12K
Privileged tasks have a maximum size of 12K.
XXX -- PSEUDO DEVICE ASSIGNMENT ERROR
A logical device name may
device.

not

assigned

pseudo

XXX -- PSEUDO DEVICE REDIRECT ERROR
An attempt has been made to redirect
another pseudo device.

device

An indirect file for MCR contains a record whose length
greater than 80. bytes.

XXX -- RECORD LARGER THAN 80.

pseudo

BYTES

XXX -- REDEFINING SPECIAL SYMBOL
An attempt has been made to change the value of an indirect
file
processor
special symbol (those bracketed with
"<" ">"). Special symbols may not be redefined.
RESERVED INST EXECUTION
This is a TKTN message. The task has executed an illegal
instruction and no SST routine was specified to process the
trap.

6-11

MCR ERROR MESSAGES
XXX -- RETRIEVAL POINTERS WRONG FORMAT
The index file retrieval pointers are not in the correct
format for RSX-llM.
Refer to the RSX-11 I/O Operations
Reference Manual for details.

***

ddnn:

SELECT ERROR

This is a TKTN message. The selected device is not ready,
or there are multiple drives with the same unit number.
XXX -- SPACE USED
An attempt has been made to create a partition or
subpartition in a main storage area already occupied.

XXX -- SPECIFIED PARTITION FOR COMMON BLOCK
An attempt is being made to install
block.

task

common

XXX -- SPECIFIED PARTITION TOO SMALL
The task being installed is larger than the partition
which it is being installed.
SST ABORT.

into

BAD STACK
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 has been detected in an unmapped
system, as indicated by a nonzero value in the header guard
word.

XXX -- STORAGE BIT MAP FILE READ ERROR
An error was encountered
storage allocation.

while

attempting

read

the

XXX -- SYMBOL TABLE OVERFLOW ssssss
The indirect file processor symbol table is full;
no space for symbol ssssss.

there is

XXX -- SYNTAX ERROR
This message generally indicates
that
the
required
information has been entered incorrectly. The user can
usually correct this condition by retyping the arguments
according to the command specifications.
XXX -- TASK ACTIVE
The task used as the argument of the command is active.
XXX -- TASK ALREADY FIXED
The task used as the argument of the Fix command is already
fixed in memory.

6-12

MCR ERROR MESSAGES
XXX -- TASK AND PARTITION BASES MISMATCH
The base of the partition does not match that of the task
being installed. Applicable only to unmapped systems.
XXX -- TASK BEING ABORTED
A request for the execution of a task is being made, but
the task is currently being aborted due to an error or as
the result of an MCR Abort command.
XXX -- TASK BEING FIXED
An attempt was made to either fix or alter the priority
a task that is in the process of being fixed.

XXX -- TASK CHECKPOINTABLE
A checkpointable task cannot be fixed in memory.
TASK EXIT WITH OUTSTANDING I/0
This is a TKTN message. Tasks should terminate
operations before exiting.
The system does,
perform all outstanding I/O.

all I/0
however,

XXX -- TASK IMAGE I/O ERROR
The Install command cannot read the task image file.
XXX -- TASK IMAGE CURRENTLY INSTALLED
The requested task image is already installed.
only to checkpointable tasks.

Applicable

XXX -- TASK INSTALLED IN PARTITION
An attempt has been made
containing installed tasks.
XXX

partition

eliminate

An attempt has been made to install a task
name as one already in the system.

with

the

same

not

have

the

TASK NAME ALREADY IN USE

XXX3-- TASK NOT ACP
The task specified as an
characteristics of an ACP.

ACP

does

XXX -- TASK NOT ACTIVE
The specified task is not currently active.
XXX -- TASK NOT FIXED
An attempt has been made to unfix a task which is not
fixed, or to open a memory location of a task which is not
fixed.

6-13

MCR ERROR MESSAGES
XXX -- TASK NOT IN SYSTEM
The referenced task has not been installed.
XXX -- TASK NOT SUSPENDED
The task used as the argument of the Resume command is
currently suspended.

not

TBIT TRAP OR BPT EXECUTION
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.
TRAP EXECUTION
This is a TKTN message.
The task has executed a TRAP
instruction and no SST routine was specified to process the
trap.
XXX -- TI REDIRECT ERROR
The psuedo device TI:

may not be redirected.

XXX -- TOO MANY COMMON BLOCK REQUESTS
A task is limited to three common block references.
XXX -- TOO MANY LUNS
A task has requested more than 255(10) LUNs to be assigned.
XXX -- TOO MANY SUBPARTITIONS
A main user-controlled partition is limited to a maximum of
seven subpartitions.
XXX -- UNDEFINED COMMON BLOCK <common-name>
A task references a common block that is not defined in the
system.
Usually, this message indicates that the task was
built to run in another system.
XXX -- UNDEFINED LABEL 111111
The label 111111 specified in a .GOTO or
cannot be found.

.ONERR

directive

not

been

An attempt to define a subpartition of a non-existent
partition has been made.

main

XXX -- UNDEFINED SYMBOL ssssss
The symbol ssssss is being tested, but
defined by the indirect command file.

has

XXX -- UNKNOWN MAIN PARTITION

6-14

MCR ERROR MESSAGES
XXX -- VOLUME MOUNTED

Mounted volumes may not be initialized.
XXX -- VOLUME NOT MOUNTED
Volume on which a UFD is to be created
before accessing the Files-11 structure.

must

mounted

XXX -- VOLUME(S) STILL MOUNTED
A system may not be saved with volumes mounted. To correct
the problem, dismount the volumes and retry the command.
The MCR Devices command may be used to display the mounted
volumes.
XXX -- VOLUME STRUCTURE NOT SUPPORTED
RSX-llM does not support the Files-11
the volume being mounted.

structure

level

attributes

The volume label and the label specified in the command
not match.

XXX -- WRITE ATTRIBUTE FAILURE
An error was encountered while writing the
either the MFD or the newly created UFD.
XXX -- WRITE CHECK NOT SUPPORTEn
Write check is only supported for RKOS disks.
XXX -- WRONG VOLUME

6-15

APPENDIX A
MCR COMMAND SUMMARY

Initialization Commands
ASN [ [ppnn:]=[llnn:]] [/GBL]
BOO [T]

[filespec]

DMO[UNT] dev: [volume-label] [/Keyword]
Keyword:
/UIC

= [group,member]

INI [TVOL] dev: [volume-label] [/keyword] [/keyword] •••
Keywords:
/BAD
/CHA
/EXT
/FPRO
/INDX
/INF
/MXF
/PRO
/UIC
/WIN

[options]
[characteristics words]
block-count
[system,owner,group,world]
logical-block-number
initial-index-file-size
file-count
[system,owner,group,world]
[group,member]
retrieval-pointer-count

INS[TALL] filespec[/keyword] [/keyword] •••
Keywords:
/CKP
/INC
/PMD
/PAR
/PR!
/TASK
/UIC

option
size
option
pname
number
taskname
[group,member]

A-1

MCR COMMAND SUMMARY
MOU[NT] dev: [volume-label] [/keyword] [/keyword]
Keywords:
/ACP
/EXT
/FPRO
/LRU
/PRTCL
/RCHK
/TEL
/UIC
/UNL
/VI
/WIN

taskname
block-count
[system,owner,group,world]
count
line protocol name
redundancy check routine name
telephone number
[group ,owner]
(no value is associated with UNL)
(no value associated with VI)
retrieval-pointer-count

SET /keyword
Only one keyword per command is permitted.
Keywords for setting device characteristics:
/BUF
/LA30S
/LOWER
/PRIV
/SLAVE
/SPEED
/UIC
/UIC
/VT05B
/WCHK

= dev: [size]
[= dev:]
[= dev:]
[ = dev:]
[= dev:]
=dev: [rev :xmit]
[=[group,member] [dev:]]
[ =dev:]
[= dev:]
[= dev:]

Keywords for partitions:

TIM[E]

/MAIN

= pname[:base:size:type]

/SUB
/POOL

= mname:pname[:base:size]
[=top]

[hrs:mins[:secs]]

[mnth/day/year]

UFD dev: [volume-label] [/Keyword]
Keywords:
/ALLOC = number-of-entries
/PRO= [system,owner,group,world]

A-2

MCR COMMAND SUMMARY
Informational Commands
DEV [ICES]
LUN(S] taskname
PAR (TIT IONS]
TAS (KLIST]
Task Control Commands
ABO[RT] taskname
ALT(ER] taskname /keyword
Keyword:
/PRI = priority
CAN[CEL] taskname
FIX taskname
REA[SSIGN] taskname lun nud:
RED[IRECT] nud:=old:
REM[OVE] taskname
RES[UME] taskname
RUN taskname [/Keyword] [/Keyword]
Keywords:
/RSI
/UIC

nnnnu
[group ,member]

RUN taskname dtime [/Keyword] [/Keyword]
Keywords:
/RSI
/UIC

nnnnu
[group,member]

A-3

MCR COMMAND SUMMARY
RUN taskname sync [dtime] [/Keyword] [/Keyword]
Keywords:
/RSI
/UIC

nnnnu
[group ,member]

RUN taskname atime [/Keyword] [/Keyword]
Keywords:
/RSI
/UIC

nnnnu
[group ,member]

RUN [$]filename [/Keyword] •..
Keywords:
/UIC
/PRI
/PAR
/TASK
/INC

[group ,owner]
priority
partition name
taskname
size

UNF[IX] taskname
System Maintenance Commands
BRK
OPE[N] memory address [+or -n] [/Keyword]
(memory address)

(contents of address)/[value]line-terminator

Line Terminator Options:
ESC

ESCape or ALTMODE: if
entered,
the
last
location opened is set to the new value.
Further, if ESC or ALTMODE is entered with no
associated value, no related location is opened
and the Open command is terminated.
The ESC
(or ALTMODE) key is the only means of exit from
the MCR Open function.

Carriage return:
is opened.

the next sequential

location

Up-arrow (circumflex on some terminals) return:
The previous location is opened.
*CR
or
@CR

Asterisk carriage return or at-sign carriage
return: the location pointed to by the final
contents of the opened location is opened.

A-4

MCR COMMAND SUMMARY
SAV [E] [/Keyword]
Keyword:
/WB

A-5

APPENDIX B
BASIC MCR SYNTAX AND ERROR MESSAGES

taskname
CAN[CEL]
taskname
RES[UME]
taskname
ATL
TAL
OPE[N] x
ABO[RTj

*
*
*

(unmapped)

X(+/-n) [/PAR=partition] (mapped)
<ESC> exit from OPE
~CR>
open next.
<CR> open previous
* or @ <CR> open indirect
-<CR> open location at PC offset
RED[IRECT] nud=old
REM[OVE] taskname
RUN taskname [/RSI=nnu] [/UIC=[group,member]]
RUN taskname dtime [/RSI=nnu] [/UIC=[group,member]]
RUN taskname stime dtime [/RSI=nnu] [/UIC=[group,member]]
RUN taskname atime [dtime] [/RSI=nnu] [/UIC=[group,member]]
TIM[E] [[hh:mm:ss] [mm/dd/yy]]
prints date as dd-mmm-yy
terminators <CR> or <ESC>
Error messages are of the form
XXX -- nn [-message]*
where:
XXX
- is the name of the MCR command issuing the error.
NN
- is the message code number.
[-message] - is the optional error message text.

* Selectable during RSX-llS system generation.

B-1

BASIC MCR SYNTAX AND ERROR MESSAGES
BASIC MCR ERROR MESSAGE CODES AND TEXT
CODE
1
2
3
4
5
6
7
8
9
10

11
12
13

14
15

16
17
18

19
20

22
23
24
26
27

TEXT
ILLEGAL FUNCTION
SYNTAX ERROR
NO POOL SPACE
INVALID KEYWORD
DEVICE NOT IN SYSTEM
PRIVILEGED COMMAND
PARTITION NOT IN SYSTEM
IO ERROR
BYTE ADDRESS
INVALID TIME PARAMETER
TASK NOT IN SYSTEM
INVALID ADDRESS
TASK NOT ACTIVE
TASK BEING ABORTED
TASK NOT SUSPENDED
TASK ACTIVE
CIRCULAR REDIRECT ERROR
OLD DEVICE NOT KNOWN TO SYSTEM
NEW DEVICE NOT KNOWN TO SYSTEM
PSUEDO DEVICE REDIRECT ERROR
OLD DEVICE ATTACHED
TI REDIRECT ERROR
INVALID UIC
ILLEGAL KEYWORD VALUE
LISTING DEVICE NOT AVAILABLE
DEVICE NOT REDIRECTABLE

B-2

INDEX
°"' 'T"'"'~

fiDV I

A
C:: 1
'"l-..J.J..

Compound tests; 5-8
Control characters, 2-2
CR, 2-5
CTRL/C, 2-3
CTRL/I, 2-3
CTRL/K, 2-3
CTRL/L, 2-3
CTRL/O, 2-3
CTRL/Q, 2-4
CTRL/S, 2-4
CTRL/U, 2-4
CTRL/Z, 2-4

ABORT, 4-51
ACTIVE, 4-68
ACTIVE TASK LIST, 4-69
ALT, 4-54
ALTER, 4-54
.ASK, 5-4
Ask a question and wait for a
reply, 5-4
ASN, 4-8
ASSIGN I 4-8
Asterisk convention (wildcards),
3-7
ATL, 4-69

Defaults in file specifiers, 3-6
Define a label, 5-4
.DELAY, 5-5
Delay execution for a specified
period of time, 5-5
DEV, 4-4 7
Device assignment, peripheral, 2-14
Device naming, peripheral, 2-14
Device reassignment, 2-16
Device redirection, 2-16
Devices, logical, 2-18
Devices, peripheral, 2-15
Devices, pseudo, 2-17
Directives, 5-4
DISMOUNT, 4-12
Display sequence, Start-up, 2-11
DMO, 4-12

Back slash, 2-5
BM792-YB Bootstrap ROM, Start-up
using, 2-8
BM873-YA Bootstrap ROM, Start-up
using, 2-9
BM873-YB Bootstrap ROM, Start-up
using, 2-10
BOOTSTRAP, 4-10.
Bootstrap ROM, Start-up using
BM792-YB, 2-8
Bootstrap ROM, Start-up using
BM873-YA, 2-9
Bootstrap ROM, Start-up using
BM873-YB, 2-10
Bootstrap ROM, Start-up using
M9 301-YA, 2-11
Bootstrap ROM, Start-up using
M9301-YB, 2-11

Bootstrap ROM, Start-up using
MRll-DB I 2-9
Branch to label on detecting an
error, 5-8
Branch to a label, 5-6
BREAKPOINT TO EXECUTIVE DEBUGGING
TOOL, 4-71
BRK, 4-71

CAN, 4-55
CANCEL, 4-55
Characters,
Control, 2-2
Special, 2-2
Command description format, 4-6
Command files, Indirect, 5-1
Command name, 4-6
Command related error messages,
4-7
Command strings, 2-13
Command summary, 4-1
Command syntax, 4-4
Commands to MCR, 5-3
Comments, 4-5, 5-11

Error detection and handling, 2-14
Error messages, 5-12, 6-1
ESC, 2-4

File fundamentals, 3-1
File processor, MCR Indirect, 5-1
File protection, 3-2
File specifiers, 3-3
File specifiers, Defaults in, 3-6
File-structured volume, 1-1
File types, use of, 3-6
Filenames, 3-1
Files and file specifi~rs, 3-3
Files and volumes, 3-5
Files, Indirect command, 5-1
Files, Multi-level indirect, 5-3
FIX-IN-MEMORY, 4-56

.GOTO, 5-6

Index-1

INDEX (Cont.)
.IFACT, 5-7
.IFDF, 5-7
. IFF, 5-6
.IFINS, 5-7
.IFNACT, 5-7
.IFNDF, 5-7
.IFNINS, 5-7
. IFT, 5-6
Indirect corn.rrland files, 5-1
Indirect file processor, MCR, 5-1
Indirect files, Multi-level, 5-3
Informational commands, 4-47
INI, 4-14
Initialization commands, 4-8
INITIALIZE VOLUME, 4-14
Initiate parallel task execution,
5-10
INS, 4-22
INSTALL, 4-22

MCR Commands (Cont.)
REDIRECT, 4-58
REMOVE, 4-60
RESUME I 4-61
RUN, 4-62
SAVE, 4-75
SET, 4-33
TAL, 4-77
TASKLIST, 4-50
TIME, 4-43
UFD, 4-44
UNFIX, 4-67
MCR, Commands to, 5-3
MCR error messages, 6-1
MCR Indirect file processor, 5-1
Monitor console interface, 4-4
MOU, 4-28
MOUNT, 4-28
MRll-DB Bootstrap ROM, Start-up
using, 2-9
Multi-level Indirect files, 5-3

Keywords, 4-5
Naming conventions, Task, 4-78
Non-privileged MCR commands, 2-5
.LABEL, 5-4
Logical devices, 2-18
Logical test, 5-6
Logical unit number, 2-16
LUN, 2-16, 4-48

M9301-YA Bootstrap ROM, Start-up
using, 2-11
M9301-YB Bootstrap ROM, Start-up
using, 2-11
Mapped system, 1-1
MCR commands ,
ABORT, 4-51
ACTIVE, 4-68
ALTER, 4-54
ASSIGN, 4-8
ATL, 4-69
BOOT, 4-10
BREAKPOINT, 4-71
CANCEL, 4-55
DEVICES, 4-47
DISMOUNT, 4-12
FIX, 4-56
INITIALIZE VOLUME, 4-14
INSTALL, 4-22
LUNS, 4-4 8
MOUNT, 4-28
Non-privileged, 2-5
OPEN, 4-72
PARTITIONS, 4-49
Privileged, 2-5
REASSIGN, 4-57

.ONERR, 5-8
OPE, 4-72
OPEN REGISTER, 4-72
Operator commands, 4-6

PAR, 4-49
Partition, 1-1
.PAUSE, 5-9
Pause for operator action, 5-9
Peripheral device assignment, 2-14
Peripheral device naming, 2-14
Peripheral devices, 2-15
Privileged MCR commands, 2-5
Pseudo devices, 2-17

REA, 4-57
REASSIGN, 4-57
RED, 4-58
REDIRECT, 4-58
REM, 4-60
REMOVE, 4-60
RES, 4-61
RESUME, 4-61
RUN, 4-62

Index-2

INDEX (Cont.)
SAV, 4-75
SAVE, 4-75
SET, 4-33
Set symbol to true or false, 5-9
.SETF, 5-9
.SETT, 5-9
Special characters, 2-2
Start-up display sequence, 2-11
Start-up procedures, 2-8
Start-up using BM792~YB Bootstrap
ROM, 2-8
Start-up using BM873-YA Bootstrap
ROM, 2-9
Start-up using BM873~YB Bootstrap
ROM, 2-10
Start-up using MRll-DB Bootstrap
ROM, 2-9
Start-up using M9301-YA Bootstrap
ROM, 2-11
Start-up using M9301-YB Bootstrap
ROM, 2-11
Subpartitions, 1-3
Switches, 5-3
C::umhn 1 c:

...,.1 ..... ~----,

Volume, file-structured, 1-1
Volumes and files, 3-5

.WAIT, 5-9
Wait for a task to finish execution, 5-9
Wildcards (asterisk convention) ,
3-7

• XQT; 5-10

i::.-?

4-44
UIC, 3-1
UNF I 4-67
UNFIX, 4-67
Unmapped systems, 1-1
User Identification Code, 3-1
User-controlled partition, 1-1
UFD,

Syntax, 5-4
System-controlled partition, 1-1
System maintenance commands, 4-68

TAL, 4-77
TAS, 4-50
Task, 1-4
Task control commands, 4-51
TASK LIST - ATL FOR.1-L~T, 4-77
Task name references, 5-11
Task naming conventions, 4-78
Tasks, 1-2
Terminal characteristics, 2-5
Terminal input conventions, 2-6
Terminal operations, 2-1
Test if symbol is defined or not
defined, 5-7
Test if symbol is true or false,
5-6
Test if task is active or not
active, 5-7
Test if task is installed or not
installed, 5-7
TIM, 4-43
TIME, 4-43

Index-3

READER'S
NOTE:

CO~u~ENTS

RSX-llM Operator's
Procedures Manual
DEC-11-0MOGA-B-D

This form is for document corrments only.
Problems
with software should be reported on a Software
Problem Repcrt (SPR) form

Did you find errors in this manual?

If so, specify by page.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.

Is there sufficient documentation on associated system programs
required for use of the software described in this manual?
If not,
what material is missing and where should it be placed?

Please indicate the type of user/reader that you most nearly represent.
[] Assembly language programmer
[]

Higher-level language programmer

[] Occasional programmer (experienced)
[]

User with little programming experience

[]

Student programmer

[]

Non-programmer interested in computer concepts and capabilities

CitY~~~~~~~~~~~~~~State~~~~~~-Zip Code~~~~~~~

or
Country
If you require a written reply,

please check here.

[]

·-------------------------------------------------------Fold llere------------------------------------------------------------

------------------------------------------- Do Not Tear · Fold llere and Staple -----------------------------------------------

FIRST CLASS
PERMIT 'NO. 33
MAYNARD, MASS.
JSINESS REPLY MAIL
) POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES

stage will be paid by:

Software Communications
P. O. Box F
Maynard, Massachusetts 01754

digital equipment corporation

Printed in U.S.A.