Digital PDFs

AA-L678A-TC

April 1983

407 pages

Original

25MB

Document:	RSX-11M/M-PLUS MCR Operations Manual
Order Number:	AA-L678A-TC
Revision:	0
Pages:	407
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V4.1_Apr83/2_Operation/AA-L678A-TC_mcr_198304.pdf

OCR Text

RSX-11 M/M-PLUS
MCR Operations Manual
Order No. AA-L678A-TC
Update Notice No. 1 (AD-L678A-T1)

RSX-11 M Version 4.1
RSX-11 M-PLUS Version 2.1

digital equipment corporation . maynard, massachusetts

First Printing, June 1979
Revised, November 1981
Updated, April 1983
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 be used or copied only in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by Digital Equipment Corporation or its
affiliated companies.
Copyright

@ 1979, 1981, 1983 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.

The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future
documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
IAS
MAS SB US
PDP
PDT
RSTS

RSX
UNIBUS
VAX
VMS

mamaoma
ZK2236

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call

800-258-1710

In New Hampshire, Alaska, and Hawaii call
In Canada call

603-884-6660

613-234-7726 (Ottawa-Hull)
800-267-6146 (all other Canadian)

DIRECT MAIL ORDERS (USA & PUERTO RICO)*
Digitai Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (CANADA)
Digital Equipment of Canada Ltd.
940 Belfast Road
Ottawa, Ontario K1 G 4C2
Attn: A&SG Business Manager

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
A&SG Business Manager
clo Digital's local subsidiary or
approved distributor

*Any prepaid order from Puerto Rico must be placed
with the local Digital subsidiary (809-754-7575)
Internal orders should be placed through the Software Distribution Center (SOC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

CONTENTS

Page
CHAPTER l
1.1
1.1.1
1.1. 2
1.1.3
1. 2
1.3
CHAPTER 2
2.1
2 .1.1
2 .1. 2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.5
2.5.1
2.5.1.l
2.5.1.2
2.5.2
2.5.3
2.5.4
2.5.5
2.5.5.1
2.6
CHAPTER 3

INTRODUCTION TO MCR
MCR COMMAND LINES
The MCR Prompt • •
Keywords • • • • • • • • • •
Comments • • • • •
• •
THE MCR INTERFACE
• • • • • • • • • • . . . . .
MCR COMMAND SUMMARY
• • • • •

•
•
•
.
•

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

SYSTEM CONVENTIONS
FILES-11 • • • • • •
• • • •
File Ownership and Directories • •
File Protection
•••••••
FILE SPECIFICATIONS
• • • • • • •
User Identification Codes (UICs)
•
Wildcards
••••••••••••
File Specification Defaults
Conventional and Default File Types
. . • . .
Examples of File Specifications
DEVICES
• • • • • • • • • • • • • • • • • • • •
Logical Unit Numbers
Pseudo Devices • • •
The Null Device
Logical Device Names • • •
Public, Private, and Unowned Devices
TERMINALS
• • • • • • • • • •
Input Prompts
• • • •
• • • •
Special Character Keys and Control Characters
Terminal Privilege • •
• ••••
Attached and Unattached Terminals
• • • •
Slaved Terminals • • • • •
TASKS
• • • • • • • • • • • • • •
• • • •
Partitions • • • • •
• •••• • • • • •
Partition Types
•••••
Subpartitions
••••••••••
Multiprogramming • •
• ••••
Creating a Task
•••••••••••••••
Task-Naming Convention • • • • • • • • • •
Installing a Task
Install-Run-Remove Tasks •
. • • •
NONPRIVILEGED USE OF ACNT
• • • •

• 2-1
2-2
• 2-2
• 2-3
• 2-5

2-6
. 2-7
• 2- 7
2-9
• 2-9
2-10
2-10
2-11
2-11
2-12
2-13
2-13
2-14
2-18
2-18
2-19
2-19
2-19
2-20
2-20
2-20
2-21
2-21
2-22
2-23
2-24

MCR COMMANDS
ABORT (ABO)
• • • • • • • • • • • •
• • • • • 3-3
ALLOCATE CHECKPOINT SPACE (ACS)
• • . • • • • 3-8
ACTIVE (ACT)
3-11
ALLOCATE (ALL)
3-12
ALTER (ALT)
3-15
iii

CONTENTS
Page
ASSIGN (ASN) • •
3-16
ACTIVE TASK LIST (ATL)
3-19
BLOCK (BLK)
3-22
BOOT (BOO) • • • • • • •
3-23
BREAKPOINT TO EXECUTIVE DEBUGGING TOOL (BRK)
3-26
BROADCAST (BRO)
. • • •
3-27
BYE (BYE)
• • • • • •
3-31
CANCEL (CAN) • • • • •
• • • • 3-33
COMMON BLOCK DIRECTORY (CBD)
3-34
COMMAND LINE INTERPRETER (CLI)
3-36
CLOCK QUEUE (CLQ)
3-43
DIGITAL COMMAND LANGUAGE (DCL)
3-44
DEALLOCATE (DEA) • • • • • • • • • •
3-45
DEBUG (DEB)
• • • • •
3-46
DEVICES (DEV)
• • • • 3-48
DISMOUNT (DMO) • • •
3-51
FIX-IN-MEMORY (FIX)
3-55
GROUP GLOBAL EVENT FLAGS (FLA)
3-57
HELLO (HEL} OR LOGIN (LOG)
3-59
HELP (HELP)
3-67
HOME (HOM) • • • • • • • • • • • •
3-73
INITVOLUME (INI) • • • •
• • • • 3-7 8
INSTALL (INS)
3-95
LOAD (LOA) • • • • • • • • • •
• • • • • • • 3-108
LOGICAL UNIT NUMBERS (LUN)
• • 3-116
MOUNT (MOU)
• • • • • • • •
• • • • • • • 3-117
OPENREGISTER (OPE) • • • • •
• 3-138
PARTITION DEFINITIONS (PAR)
• • • • • • • 3-143
REASSIGN (REA)
• • • •
• • • • • • • 3-146
REDIRECT (RED)
• • • •
• 3-147
REMOVE (REM) • • • • • • • •
• • 3-149
RESUME (RES) • • • •
• • 3-150
RUN (RUN)
• • • •
• • 3-151
SAVE (SAV} • •
• • 3-160
SET (SET)
.•••
• • 3-170
SYSTEM SERVICE MESSAGE (SSM)
• • • • • • 3-221
SWITCH REGISTER (SWR}
• • • 3-222
TASKLIST - ATL FORMAT (TAL}
• • 3-223
TASKLIST (TAS) • • • • • • •
• • • 3-224
TIME (TIM) • • • • • • • • • • • • •
. • • 3-226
USER FILE DIRECTORY (UFD)
• 3-228
UNBLOCK (UNB)
• • 3-230
UNFIX (UNF)
• 3-231
UNLOAD (UNL)
• 3-232
UNSTOP (UNS}
• 3-234
CHAPTER 4
4.1
4.1.l
4 .1. 2
4.2
4.3
4.4
4.4.1
4.4.1.1
4.4.1.2
4.4.1.3
4.4.2
4.4.3
4.4.4
4.4.5
4.5

THE INDIRECT COMMAND PROCESSOR
INDIRECT COMMAND FILES • • • • • •
• 4-1
Indirect Task Command Files
• 4-1
Indirect CLI Command Files •
• 4-2
INDIRECT COMMAND PROCESSOR • • • •
• • • 4-2
SUMMARY OF INDIRECT DIRECTIVES •
• • • 4-4
SYMBOLS
• . • • • • • • • • • • • •
• 4-7
Special Symbols
• • • • • •
• 4-8
Special Logical Symbols
••••
4-8
Special Numeric Symbols
4-10
Special String Symbols • •
4-12
Numeric Symbols and Expressions
••••
4-14
String Symbols, Substrings, and Expressions
4-16
Reserved Symbols • • • • • • •
4-17
Symbol Value Substitution
4-17
Substitution Format Control
4-18
SWITCHES • . • . . • • • . . • .
4-19
iv

CONTENTS
Page
DESCRIPTION OF INDIRECT DIRECTIVES • • • • •
Define a Label (.label:) • • • • • • • • •
ab~ a Question and Wait for a Reply (.ASK)
Ask for Definition of a Numeric Symbol (.ASKN)
Ask for Definition of a String Symbol (.ASKS)
Begin Block (.BEGIN) • • • • • • • • • • • • •
Continue Processing Using Another File (.CHAIN)
Close Secondary File (.CLOSE)
••••
Output Data to Secondary File (.DATA)
• • • •
Decrement Numeric Symbol (.DEC)
••••
Delay Execution for a Specified Period of Time
(.DELAY) • • • • • • • • • •
• •••
Disable Option (.DISABLE)
4.6.11
4.6.12
Enable Option (.ENABLE)
••••
4.6.13
End Block (.END) • • • • • •
• •••
4.6.14
Delete Symbols (.ERASE)
••••••
Exit Current Command File (.EXIT)
4.6.15
4.6.16
Call a Subroutine (.GOSUB) • • • • • • • •
Branch to a Label (.GOTO)
• • • •
4.6.17
4.6.18
Logical Test (.IF) • • • • • • • • • • • •
Test If Symbol Meets Specified Condition
4.6.18.l
(.IF)
• • • • • • • • • •
• •••
Test If Task Is Active or Dormant
4.6.18.2
(.IFACT/.IFNACT)
•••••
Test If Symbol Is Defined or Not Defined
4.6.18.3
(.IFDF/IFNDF)
•••••••
Test If Task Is Installed Or Not Installed
4.6.18.4
(.IFINS/.IFNINS) • • • • • •
Test If Mode Is Enabled Or Disabled
4.6.18.5
(.IFENABLED/.IFDISABLED) • • • • • •
Test If Driver Is Loaded Or Not Loaded
4.6.18.6
(.IFLOA/.IFNLOA) • • • • • • • • • • •
Test If Symbol Is True Or False (.IFT/.IFF)
4.6.18.7
4.6.18.8
Compound Tests • • • • • • • • • • • • • • •
Increment Numeric Symbol (.INC)
• • • • • • •
4.6.19
4.6.20
Define Logical End-of-File (/) • • • • • • • •
Branch to Label on Detecting an Error (.ONERR)
4.6.21
4.6.22
Open Secondary File (.OPEN)
•••••••
Open Secondary File for Append (.OPENA)
4.6.23
4.6.24
Open File for Reading (.OPENR) • • • • •
Parse Strings into Substrings (.PARSE)
4.6.25
4.6.26
Pause for Operator Action (.PAUSE) • •
4.6.27
Read Next Record (.READ) • • • • • • • •
4.6.28
Return from a Subroutine (.RETURN) • • •
Set Symbol to True or False (.SETT/.SETF/.SETL)
4.6.29
4.6.30
Set Symbol to Numeric Value (.SETN)
•••••
Set Symbol to Octal or Decimal (.SETO/.SETD) •
4.6.31
4.6.32
Set Symbol to String Value (.SETS) • • • •
Terminate Command File Processing (.STOP)
4.6.33
4.6.34
Test Symbol (.TEST)
• • • •
• ••••
Test Device (.TESTDEVICE)
••••••••••
4.6.35
4.6.36
Test a File (.TESTFILE)
••••••
Test a Partition (. TESTPARTITION)
• • • •
4.6.37
4.6.38
Wait for a Task to Finish Execution (.WAIT)
Initiate Parallel Task Execution (.XQT)
4.6.39
EXAMPLES • . • . • • • • • •
4.7
INDIRECT MESSAGES • • • • •
4.8
4.8.1
Information-only Messages
• • • • . • • •
Error Messages • • • • . • • • • • •
4.8.2
4.6
4.6.1
4.6.2
4.6.3
4.6.4
4.6.5
4.6.6
4.6.7
4.6.8
4.6.9
4.6.10

APPENDIX A

MCR AND TKTN MESSAGES

4-21
4-22
4-24
4-26
4-28
4-28
4-29
4-29
4-30
4-30
4-31
4-32
4-35
4-35
4-36
4-37
4-37
4-38
4-38
4-39
4-39
4-40
4-40
4-41
4-41
4-42
4-42
4-42
4-43
4-44
4-44
4-45
4-46
4-46
4-47
4-48
4-48
4-49
4-49
4-50
4-51
4-51
4-52
4-53
4-54
4-55
4-55
4-56
4-57
4-57
4-58

CONTENTS
Page
TABLES
TABLE

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

Pseudo Devices • • • •
• • • • • • • 2-10
Special Character Keys and Control Characters
2-15
Valid Bootable Devices
3-23
Number of Files Allowed on Volumes •
3-85
SET Keywords • • • • • • • • • • •
• 3-172

PREFACE

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

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

this

STRUCTURE OF THE DOCUMENT
Chapter 1 describes MCR and gives a summary of the commands.
Chapter 2 discusse.s basic concepts of the RSX-llM/M-PLUS file system
(Files-11) and also describes many system conventions, such as device
and task naming conventions.
Chapter 3 supplies detailed descriptions of all the MCR commands.
commands are in alphabetical order.

The

Chapter 4 discusses the indirect command processor (Indirect) and
explains the use of indirect command files.
Directives to the
indirect command processor appear in alphabetical order.
Appendix A lists, in alphabetical order, the MCR and Task Termination
Notification program (TKTN) messages that can be returned by the
system.

vii

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

CONVENTIONS USED IN THIS DOCUMENT
A symbol with a 1- to 3-character abbreviation indicates that you
00)
or
press the corresponding key on the terminal, for example,

®9.
~
indicates that you must ·press the key labeled CTRL
simultaneously press another key:
for example,
PRLgJ
,
ftRURl
,
~
In examples, these three control keys are shown
as AZ,
AR,
AU,
respectively, because that is how the system echoes
them.

The symbol
while you

Uppercase letters and words indicate that you should enter the letter
or word exactly as shown.
Lowercase letters and words indicate that
you are to substitute a word or value.
Square brackets ([]) indicate optional entries in a command line or
file specification.
When you enter an option, the brackets are not
included.
Square brackets are also a part of the User Identification Code and
User File Directory syntax ([group,member]). When you use a UIC or
UFD (in a file specification, for example), the brackets must be
included.
Braces ({}) indicate a choice of required entries for a command line.
You can use any of the entries enclosed in the braces, but you must
specify one of them.
Red ink in examples indicates input that you type on the terminal.
Shaded portions of text describe only one operating system.
Pink
shading indicates that the text pertains only to RSX-llM systems.
Gray shading indicates that the text pertains only to RSX-llM-PLUS
systems.

viii

SUMMARY OF TECHNICAL CHANGES

This revision of the RSX-llM/M-PLUS MCR Operations Manual contai~s
changes and additions included in the RSX-llM V4.0 and RSX-llM-PLUS
V2.0 operating systems.
Note that not all of the
single-user MCR.

new

technical

features

are

available

The following are new or revised MCR commands:
ALL

New keyword: /TYPE=RXnn.
Allocates
device of the specified type.

the

first

available

BLK

New command. Blocks an installed task and declares it
ineligible to execute or compete for memory. Blocked tasks
must be unblocked (with the new UNBLOCK command) or aborted.
The BLOCK command replaces the STOP command.

BOOT

Now allows booting of an RSX-llM-PLUS system from an RSX-llM
host and vice versa.

BRO

Now includes system and DECnet node names in the system
identification, and will not broadcast messages to terminals
that have disabled the broadcast option with SET /NOBRO.

69:~§}{F:!~~7~~l1§. ~y:s~e~~ >V/i~~ii··.~~~?l.i·~c~ . i\c¢ounti11g, . the BRO
commandJias·.·.·•·a ne:w·····f.ormat.•: .. · B~Ol.ADPA$,.J user+naijle m~*S.:ctg/e~:.

BYE

Now supports silent logouts.
New keyword: /[NO]HOLD, which specifies whether BYE
leave a terminal connected after it is logged out.

should

CLI

New command. Sets up for use a command line interpreter
(CLI) other than MCR, such as DCL or a user-written CLI.

CLQ

Now nonprivileged instead of privileged.

DCL

New command. Allows you to issue DIGITAL Command
(DCL) commands from a terminal that is set to MCR.

DEBUG

fRSX ... llffl-l?LUS syst:E!n1s only.} fprCes a task to trap to a
debugging aid (such as · t)DT) so that the task can be
debugged.

DEV

New format: DEV /ddnn:, which displays information about
specific device.

DMO

Now checks for installed tasks on a device.
If any such
tasks are present, displays a message and dismounts the
device.
The /LOCK keyword can now be used on RSX-llM.
for the keyword are Unload and Nounload.

New

Language

SUMMARY OF TECHNICAL CHANGES
HELLO

LOGIN can now be used as a synonym for HELLO.
The command now supports silent logins on systems with
multi-CL! support, and the system or DECnet node name is
included in the system identification.
There is also a
timeout count for responding to the default prompt.

HELP

Now displays, because of extended CLI capability, the
general help file for the command line interpreter to which
the terminal is set.
New keywords are:

HOME

/CL!

Directs HELP to the help file for
specified
command
line
interpreter
LB: [1,2] cliname.HLP.

the
in

/DCL

Specifies that the
LB: [ 1, 2] DC L. HLP.

help

text

begins

/FIL

Specifies
located.

where

help

text

/GRO

Instructs HELP to use
[group,l]HELP.HLP
the default volume as the root help file.

/LOC

Displays the text contained in HELP.HLP in
the default directory on the default volume
(synonymous with HELP%).

/MCR

Specifies that the
LB: [l,2]MCR.HLP.

/OUT

Saves the text of the help file (or files)
a specified file.

/xxx

in
Specifies that the help text begins
LB: [ 1, 2] xxx. HLP, where xxx is the name of the
command line interpreter.

any

file

help

text

begins

in
in

New command. Modifies certain fields in the home block of a
Files-11 disk volume.
Note that if you install an old version of the INI task
(RSX-llM V3.2/RSX-11M-PLUS Vl.O or earlier) using the name
HOM, the volumes will be initialized when you use the HOME
command.

INI

Now supports 65K files on volumes. These volumes are not
backwards compatible from RSX-llM V4.0 or from RSX-llM-PLUS
V2.0.
New or revised keywords are:
/ACCESS

Specifies the access
magnetic tape volume.

protection

for

/DEN

Now accepts 6250 bpi as
TU78 magnetic tape.

the

for

/OWNER

Specifies the owner of a magnetic tape volume
in a format other than as a UIC.

density

SUMMARY OF TECHNICAL CHANGES
INS

New keywords are:
/CL!

Installs
task
as
a
command
line
a
interpreter.
A CLI task must be installed
before the CL! can be used.

/IOP

Specifies that a privileged task can
the I/O page.

LOA

Now correctly loads
multiple controllers.

the

MOU

Now allows names with
magnetic tape volumes.

KMC
special

line

printer

characters

overmap

driver
in

with

them

for

New or revised keywords are:
/BS

Specifies
volumes.

block

size

for

magnetic

tape

/CC

Specifies
volumes.

record

type

for

magnetic

tape

/DENS

Now accepts 6250 bpi as a density for a
magnetic tape.

TU78

/HDR3

Specifies whether an HDR3 label
written when creating new files.

/LABEL

Specifies whether a magnetic tape volume is
in
ANSI
format
(/LABEL)
or unlabeled
(/NOLABEL) •

/LOCK

Specifies the default value for the
/LOCK keyword.

/OVRACC

Instructs the MOUNT command to override the
protection for an ANSI magnetic tape volume.

/PRO

Specifies the volume protection for
disks.

/PUB

Makes the volume accessible to all users,
depending on the volume and file protection
set for the volume.

/RS

Specifies number of characters
for magnetic tape volumes.

DISMOUNT

Files-11

record

SUMMARY OF TECHNICAL CHANGES
SET

New or revised keywords are:
/AB AUD

Enables autobaud detection for
remote dial-up line.

/BRO

Specifies whether a
terminal will receive
messages sent by the BROADCAST command.

/CLI

Displays or sets the default command line
interpreter for a terminal (or terminals) •

xii a

terminal's

SUMMARY OF TECHNICAL CHANGES
MOU
(Cont.)

OPE

/SHARE

Specifies whether more than one user can
mount the volume (/SHARE) or if it can be
used by only one user (/NOSHARE) •

/TR

Specifies the kind of character translation
used in read and write operations on an
unlabeled magnetic tape volume.

/VOL

Specifies the Volume Identifier for
magnetic tape.

/WAIT

Specifies whether operator assistance
is
required for performing a mount operation.

/WIN

Now also accepts the following
options:
USER:n, INDEX:n, (USER:n,INDEX:n), and FULL.

/WRITE

Specifies that a volume will be
write-enabled
(/WRITE)
or
write-locked (/NOWRITE).

New formats for displaying the contents
memory:
ASCII,
single-character
double-byte, and decimal.

ANSI

software
software

of a location in
ASCII,
Radix-50,

o.nly.)
Accesses
the contents of addresses in the
space of an I..;. and D-space task.
(RSX-1.lM..;.PLUS · systems

prints

(RSX-llM-PLUS syst.ems only.)
Accesses and
prints the. . cont~nts o.f pdqre~ses . . ;in . t}le
i.p$tructipn ~p~c¢ of an :I-- ariQ D,.._spape: task.;
PAR

~QW; ~disp1aysrthe;. add;~s.st·p:q''. a.r,;(?a~~~~~()~l>"fJ:()~/f\1-'.iP~fi~:l!~~t;';·~ft~~.,. :.'"'l
('J!his is new for RSX~llM .. )L ············· ···.· ·············· ··· · ., ...... "···~""'

REM

Now checks to see if an installed task is an active CL!.
so, it is not removed and an error message is displayed.

RUN

New keywords are:

SAV

/CMD

Passes the specified command line to the task
being run for processing.

/EST

Specifies whether or not a task will wait for
spawned tasks to complete and for RUN to emit
exit status.

/INC

Increments the address space allocated to a
task
that
runs
in a system-controlled
partition.

/!OP

Specifies that a privileged task can
the I/O page.

overmap

A saved RSX-llM-PLUS system is now bootable on RSX-llM.

xii

April 1983

SUMMARY OF TECHNICAL CHANGES
: Enables . reqo~nJtfon . .. Of
Larig\:la<Je. JD~L) ·comrna11qs:~

SET
(Cont.)

RSX~l]_M.) .

DIGIT.AL.
Command
(Thi$ keyword
is

te<;ognJtfoll of M~H commands.
~s·. OE;?W·.·fOr.·.· RSX~llM • .)
/NETUIC

{This

Specifies the UIC in which all DECnet-related
tasks are stored.

STP

/PLC TL

Displays or sets the pool limit parameters
used by the Pool Monitor Task (PMT).

/REMOTE

Now allows the setting of the initial baud
rate of a remote dial-up line for a terminal.

/RNDC

Defines
the
length
of
the
round-robin scheduling interval.

/RNDH

Executive

•

Defines the highest
considered
for
scheduling.

priority that will be
round-robin
Executive

•

/RNDL

Defines the
considered
scheduling.

priority that will be
Executive
round-robin

•

/SWPC

Defines the length
swapping interval.

/SWPR

Defines a
swapping.

/TERM

New terminal
LAlOO,
LA38,
VT131, VT132.

/TOP

Moves the top boundary of a system-controlled
partition.

The STOP command
command.

has

been

xiii

lowest
for

priority

single

Executive

•

range

for

Executive

•

LA12,
LA34,
types allowed:
VT101,
VT102, VT105, VT125,

replaced

the

BLOCK

(BLK)

April 1983

SUMMARY.OF TECHNICAL CHANGES
TAS

Now accepts a task-name parameter.
New keyword:
/DEV, which displays information
installed from a particular device.

UNB

New command.
Continues execution
stopped with the BLOCK command.

Indirect Command Processor

about

task

tasks

previously

(Indirect)

Indirect now accepts directives and command lines in lowercase as well
as in uppercase.
The following are new or revised directives:
.ASK

Now allows a default value and a timeout parameter
to be specified in the command line.

.ASKN

Now allows a timeout parameter to be specified
the command line.

.ASKS

Now allows a default value and a timeout parameter
to be specified in the command line.

• DATA

Now also allows a TAB after the command •

.ENABLE/
.DISABLE

New options
for enabling and disabling
(default setting and default action):

are

ATTACH

Enabled:
Indirect attaches to
for comment lines.

TI:

CONTROL-Z

Disabled:
Indirect
CTRL/Z is used
in
.ASKx directive.

DECIMAL

Disabled:
numeric
symbols
created or redefined as octal.

DELETE

Disabled:
the current command file
is not deleted when Indirect exits.

DETACH

Enabled:
Indirect detaches from
the
terminal
when
processing
command lines.

DISPLAY

Enabled:
Indirect displays
the
current
fields
for
the
.ASKx
directives and "@ <EOF>".

ESCAPE-SEQ

Disabled:
Indirect does not attach
to the terminal for escape-sequence
recognition.

MCR

Enabled: commands not processed by
Indirect are passed to the default
command line interpreter
(CL!) of
the terminal.

OVERFLOW

Disabled:
signed arithmetic
in
numeric expressions is not allowed.

xiv

exits
when
response to a
are

SUMMARY OF TECHNICAL CHANGES
.ENABLE/
.DISABLE (Cont.)

TIMEOUT

Enabled:
Indirect uses the timeout
parameters specified for the
.ASKx
directives.

TRACE

Disabled:
commands processed by
Indirect are not displayed on the
terminal.

TRUNCATE

Disabled:
truncate errors on
.READ directive are not ignored.

The GLOBAL option is now enabled by default.
• ERASE SYMBOL

Deletes a symbol from the global symbol table •

• IF ENABLED/
DISABLED

Tests the .ENABLE/.DISABLE options •

• OPENR

Opens a file for reading with the .READ command •

• PARSE

Parses strings into substrings •

.READ

Reads a record f·rom a file into a specified string
variable.

• SETD/.SETO

Redefines the radix of a numeric symbol •

.SETL

Defines or redefines a logical symbol and
the symbol a true or false value.

• TEST

Now also locates a substring •

• TESTDEVICE

Returns information about a device in the system •

.TESTFILE

file
exists
and
Determines if a specified
determines the physical device associated with a
logical name.

• TEST PARTITION

Returns
system.

information

about

partition

assigns

the

Tests whether the last question was answered
an
ALTmode
or
an ESCape.
Synonymous
<ESCAPE>.

with
with

Tests if the current
baseline configuration.

Contains the parameter defaults specified when the
current Indirect task was built.

<EOF>

Tests whether the last .ASKx or
.READ directive
resulted in reading past the end of the file.

Controls Indirect processing upon encountering
error.

The following are new or revised symbols:

operating

system

SUMMARY OF TECHNICAL CHANGES

•

Contains the class number of an
Indirect has finished processing.

<ERROR>

One of five symbols that define the exit status of
an executed CLI-specific command line.
The.other
symbols are <SEVERE>,
<SUCCES>,
<WARNIN>, and
<NOSTAT>.
These symbols are associated with the
numeric codes for <EXSTAT>.

Contains the error severity mask associated with
the error that Indirect has finished processing.

Tests the error code of a file, the exit status of
an executed CLI-specific command line, if <EOF> is
true, the value for <ERRNUM>, or if the .SETT
directive was used.

Contains build-time information about the Indirect
task or the string results from a more deeply
nested indirect command file.
The results are
sent to the calling indirect command file.

<FALSE>

Logical constant used for comparisons with the .IF
directive or as a default for the .ASK directive.

Returns the seven words
of
file
attribute
information
contained
in
the
FCS-11
File
Descriptor Block (FDB).

Contains the FCS-11 or I/O driver status code
resulting from a
.TESTFILE,
.OPENx, or
.READ
directive operation.

Contains the fully qualified specification for a
file referred to with the last .OPENx or .TESFILE
directive operation or in the last specification
for a nested command file.

<FMASK>

Contains octal values that represent answers
some of the system generation questions.

Contains the octal value of the
used to open the data files.

<IAS>

Tests whether the
current
Synonymous with <RSX-llD>.

<LOCAL>

Tests whether the terminal from which Indirect
running is a local terminal.

Contains the device name and unit
user's login account or SYO:.

the

Contains the login UIC of the current user or
current default UIC.

the

Contains the UIC in which DECnet-related tasks are
stored.

xvi

error

file

that

attributes

system

number

IAS.

April 1983

SUMMARY OF TECHNICAL CHANGES
<NETNOD>

Contains the DECnet node name for
RSX-11.

One of five symbols that define the exit status of
an executed CLI-specific command line.

Tests whether the last string entered in response
to an .ASKS directive or tested with a .TEST
directive contains only numeric characters.

<OCTAL>

Tests whether a value used in
directive operation is octal.

Tests whether the current user is privileged.

One of five symbols that define the exit status of
an executed CLI-specific command line.

One of five symbols that define the exit status of
an executed CLI-specific command line.

Contains the numeric code for the type
tested with a .TEST directive.

Contains the physical device
device for the system.

the

Contains tqe base-level number for the system.

Contains the current page length setting
terminal.

for

the

Contains the current page width
terminal.

for

the

Tests whether the last .ASK directive
waiting for a user response.

timed

out

Contains the baud rate
character transmission.

Contains the terminal type of
which Indirect is running.

<TRUE>

Logical constant used for comparisons with the .IF
directive or as a default for the .ASK directive.

One of five symbols that define the exit status of
an executed CLI-specific command line.

the

.ASKN

name

setting

system

.TEST

symbol
boot

host-to-terminal

for
the

terminal

from

The following are new switches:
/[NO]CLI

(/CLI default) Passes commands not processed by
Indirect to the default command line interpreter
(CLI) for the terminal. Synonymous with /[NO]MC.

/LB

Indicates that the specified file is a universal
library
of
command procedures and that the
specified module is the procedure to be executed.

xvii

SUMMARY OF TECHNICAL CHANGES
{/NOLO default) Indicates that when a new file is
executing, it can have access to the local symbols
created by its calling command file, and that any
local symbols created by the new command file will
be defined as local symbols for the calling
command file.

/LO

The following is new functionality in Indirect:
Parameter passing
Parameters for a command file can now be passed to Indirect for
processing.
The parameters are stored in the reserved local
symbols PO, Pl, P2, P3, P4, P5, P6, P7, P8, P9, and COMMAN.
Universal library support
When command procedures, which are indirect command files, are
inserted into a universal library with the Librarian Utility
Program {LBR), they can then be referenced with the
new
/LB:module switch.
Command libraries are built by creating a universal library and
insert1ng command files into it. The procedures in the library
can then be referenced in the form @command-library/LB:module.
Substitution format control
Format control is available for numeric values being converted to
string values and for string and logical values being placed in a
substitution operation.

xviii

CHAPTER 1
INTRODUCTION TO MCR

The Monitor Console Routine (MCR) serves as an interface between you
and the RSX-llM/M-PLUS system.
You issue MCR commands from a
terminal.
Before trying to use MCR commands, be sure that your terminal is set
to MCR.
You can verify this by pressing CTRL/C and getting the
explicit MCR prompt (see Section 1.1.1). If you would like MCR to be
the default command line interpreter for your terminal, have your
system manager set this up for you in the account file.

1.1

MCR COMMAND LINES

To issue an MCR command, type a command line in response to a default
(>)
or explicit MCR (MCR>) prompt. A command line consists of three
components: a command name, any required parameters, and a line
terminator.
It is not necessary to type the entire command name when submitting a
command.
MCR requires only the 3-letter abbreviation for a command
name, except for HELP, which must be entered in full.
The command
name is then followed by the command parameters.
For example, you can type the CANCEL command as follows:
>CAN taskname(BD)
The variable taskname is a parameter for the CANCEL command and
(BD)
signifies the RETURN key, the line terminator. As in this example,
the command you use often consists of the first three letters of the
command name.
Some commands, however, have 3-letter acronyms as
command names. For instance, the names for the ASSIGN and USER FILE
DIRECTORY commands are ASN and UFO, respectively.
With most of the commands, you can specify a longer form of the
command name.
This is unnecessary, however, because MCR only uses the
required three letters, but to make the intent of the command clear to
someone reading a printed copy of command input, you can type:
>CANCEL taskname(BD)

1-1

INTRODUCTION TO MCR
A space or a tab signals the end of the command name;
therefore, no
spaces or tabs are allowed within the command name itself. For
example,
>OPENREGISTER address
is permissible, while
>OPEN REGISTER address
is not.
Typically, a command parameter is a task name, the name of a file, or
a device specification.
A parameter can be modified by a keyword
(defined in Section 1.1.2).
You press the RETURN key
®ill
or the ALTmode or ESCape key
~
to terminate a command llne. MCR returns the default prompt after
processing a command line terminated by pressing the RETURN key.
MCR
suppresses
the default prompt after processing a command line
terminated by the ESCape key, except when the ESCape key has special
significance as a terminator (with the RUN and OPENREGISTER commands,
for example). MCR accepts subsequent unsolicited input even though
the default prompt does not appear.
When MCR parses a command line, it normally compresses any multiple
spaces and tabs and treats character strings beginning with a
semicolon (;) or an exclamation mark
(!)
as comments
(see Section
1.1.3).
When you use quotation marks ("") in the command line, however, MCR
parses that part of the line within the quotes exactly as you typed
it. No compression occurs. This allows you to use special characters
in your command line and to use American National Standard (ANSI)
X.327-1978 file specifications, which can have embedded spaces.
If you use only one quotation mark in the command line, MCR assumes an
ANSI file specification and does not compress the line past the
quotation mark.
(See the RSX-llM/M-PLUS I/O Operations Reference
Manual for more information on support for quotation marks.)

•

1-2

April 1983

INTRODUCTION TO MCR
1.1.1

The MCR Prompt

When you use MCR, there are three prompts that indicate a terminal
is
waiting for input from you:
the default prompt, task prompts, and the
explicit MCR prompt.
The default prompt and
task prompts are
described more fully in Chapter 2.
A terminal always sends to MCR any input
explicit MCR prompt (MCR>):

typed

response

the

You invoke the explicit MCR prompt by pressing the CONTROL (CTRL)
and the C key simultaneously.

key

MCR>command-input

However, CTRL/C does not invoke the MCR prompt in a
special case as
described
in the second item in the following list.
The description
of CTRL/C in Table 2-2 also describes two other situations in which
CTRL/C does not invoke the explicit MCR prompt.
The following notes explain various uses of the explicit MCR prompt:
1.

When a terminal is displaying the default prompt
(>),
there
is no guarantee that input typed in response to the prompt
will be directed
to MCR because another
task may have
attached to the terminal.
To ensure that MCR does receive
the input, press CTRL/C to invoke the MCR prompt.
After MCR
processes the command
line,
the terminal will display the
default prompt.

When a terminal is displaying a task prompt (tsk>),
you
invoke
MCR by pressing CTRL/C.
After
(or while)
processes the command line, the terminal will display
original task prompte

can
MCR
the

If you requested MCR to display information
(with the TIME
command, for example) and it is not displayed before the task
prompt appears, press the RETURN key.
This will display the
information and
then the original task prompt.
Also press
the RETURN key if you would like to know if MCR processed the
command line or if it returned an error message.
NOTE
If an attached
task
specifies
an
Asynchronous
System Trap
(AST)
upon
rece1v1ng unsolicited
input,
CTRL/C
causes an AST to occur, thereby gaining
the task's attention rather than MCR's.
Consequently,
the MCR prompt does not
appear.
3.

When any terminal is rece1v1ng output from a
task, you can
interrupt the output by pressing CTRL/C.
At the completion
of the current I/O operation,
the terminal displays the
explicit MCR prompt.
After MCR processes the command line
directed to it, the system resumes the interrupted output.

1-3

INTRODUCTION TO MCR
In all three cases, if the command line invokes a task, the task will
issue its own prompt.
You can respond to this prompt with another
CTRL/C, which invokes the MCR prompt.
You can then request another
task that issues its own prompt and so on.
(Note that because CTRL/C
does not abort the task that was active when you typed the CTRL/C,
it
is
possible
to
have
several tasks active at your terminal
concurrently.)

1.1.2

Keywords

Some of the MCR commands use keywords that affect a command parameter.
Keywords are similar in function to switches (described in Section
2.2). A keyword consists of a slash (/), followed by an alphanumeric
name,
and optionally followed by an equal sign {=) and the value for
the keyword, as follows:
/keyword=value
A keyword modifies the action of a command.
You can apply a keyword
directly to the command or to a command parameter, depending on the
command.
If the keyword follows the command name,
it modifies the
action of the command.
If the keyword follows a parameter, it
modifies the action for the parameter.
For example, the INSTALL command requires a file name parameter that
specifies the task to be installed. You can append keywords to this
file name.
One such keyword, /TASK, specifies the name under which
the task is to be installed. For example:
>INS BOB.TSK/TASK=AMBER
This command installs the task image file BOB.TSK with the name AMBER.
When you want to use the task, you invoke it with the name AMBER.
You can enter keywords in any order. They are command-specific
are defined in the descriptions of the commands (Chapter 3).

1.1.3

and

Comments

MCR treats a line of text as a comment if the first character in the
line is a semicolon
(;).
In addition, you can use the exclamation
point (!) to delimit comments within a command. The first exclamation
point starts the comment and the next exclamation point or line
terminator ends the comment. MCR ignores all text between the two
exclamation points.
For example:
>;

THIS LINE IS A COMMENT

>TAL !THIS IS A COMMENT STRING!

RMDEMO

Comments are especially useful to clarify commands in indirect command
files, which are described in Chapter 4.
To use the semicolon and exclamation point characters in
line, use quotation marks (see Section 1.1).

1-4

the

command

INTRODUCTION TO MCR
1.2

THE MCR INTERFACE

MCR parses the input you type to determine what the command line is
requesting and then responds appropriately to the input. To service a
request, MCR either uses an MCR overlay or activates an independent
task.
By following the procedures outlined in the following text, MCR
activates the appropriate overlay or task to service each command.
The required three letters of the command name are the
most
significant part of a command line. MCR uses the name to determine
the necessary overlay or task as follows:
1.

MCR searches a table containing names of commands serviced by
MCR itself.
If the table contains a matching command, MCR
either loads the corresponding overlay or
starts
the
secondary task ( ••• MCR), which invokes the correct overlay.
The overlay then proceeds to process the command line.
(On
single-user RSX-llM systems, all commands are serviced by
MCR ••• , the primary MCR task.
There is no secondary MCR
task.)

If the table does not contain a matching command, MCR
prefixes three dots (
)
to the command name and then
searches the System Task Directory (STD) for a task by that
name (that is, ••• tsk) • MCR returns an error if the STD does
not contain the specified task.

...

~.n···· ~~.x;--+Jr, .~~?~~~~,·.• ~~if di~~~a.:y::; a.·• ~~a
.~Ctly~;" :<tn~$Mge: 1 £ •·•· •.. t.sJ{: ··ts
a1re<la¥···. . ·:a7~.ive'·a·t:•t:r~> :t~·r;mi·n·a1~ . r·f: 'tr ..•..•. iSTJ:) C;otil:aihs· ~~<."tsk.arit:t•··1t ts
no~·. r11i:ip~ry9>~:~. t:l:t:E! ·i·~f>~~}n:9 :··t:e:r.nrifiql•, r.,q~. f".~9P?B9$. c:9·J?-<.fi,fi,,p·~qJ1.l' · iri;.on.~
:of· two ·wa:Y~·:'::..
·· ·
· ·. ,
· ·
·
.· · ·.··· ·. · · · · ·. ·. · · ·
,.
,

·.
. .

'·

. . ..

·.·:··
..
..
.

.·,

.= : .. ~ :

. .. : ~ ·.•.. : . . .. . .

•··.·+r·•·"~·~~:~1~:J5·.·: ~:~•:ri~ie··::~q·t:t'.v'~;,·.. ·~¢R:·:t~·q1.l~·~:t$: :i:t1~·. Ex·~ctt~1~·~.. ~9·/run.•·.t:·ne"

te1.sk.·•at· the•· ~$,~~··~.n9·.• ~~rwin<1~.j>

:. . . . . . . .. . .• :. . . . . . . . . ,..... .···•<<: . ·.·• .•·;:·.·····c
·• · ~*·i. ~c.l~f~~>' . ~~f i~~l~C~·~l'·~~~~~ q ~~~~.i,~1 '$~ . ; i~~~'· ~ti~~

·.·.,.•:.::::·' ·l'?. i.n;t~;.: ·:t:..: . . . . . . ·.· ..~~:.::',;~,rit'i}re· T: ~~f?l<:·•.:$. ;<ffsk :: . Atnag.~·~ . •. . . . .·.· . .· · . · · · · ,.·: .fi:~!ne:s·:t:.~~

· -::,:.

t:.TWP~I'1<lrY.·t:a~~:: ~!$l<'f'J1l1.t'.··;wh~::r;e:i)'if1····i,s· ·:the \J.lniF :·nwnher 0£·· :·t:he'
'.·•·.~·. ·te•.I"iqin,~·~•:••:· .. tha.t:·····•.x.••4:?st:Je9··.:··;q·er~ozµ~a11.d·••. ::·.: .• r.t:···-~a.s[{••···~:~k;'rnri.•·• is. ,c:;r~·t·eady
:· · ••·•-'·•· iry~·~~.¥.+·e4.··~·.•.· ~GR.·•;'.f~·~uest:~. tJ:~,~ • ~~·esqtJ·\1~:'·,t<>··t"µ,ll•·•. f:h<lt· . ···verslon ·p~
·:.·:<~A~•··' ·.t:,9sJ<•·.· a~'i •t9~·>•.i.s~·91.m.t .•. J::~'.pn.i·ll9·i·:{•······ ·When···.tskTnn ·~~'.i~~::~ ,the

· $~~gut.~:.ve <~'u:t:9~A~Jt;:~.r~ y, .•. geJ..~·t:e:§< ;.~·~·$;·.· s:'.l:P . ~nt~·y.-··· •·

On···R~X--•llM--J?LUS•·sY:s~~ms,i~~'R:·.•.·.first::·a~o~.!:> f'o·r ~tt· iirist.~)1,led veir·s;)5n ..... of
tskT111l·. ······.·alld·'.•·rJ.:?.qu~~t'5•t~Jie·•··:E.xe~utiye;,t:.<:>:::urytt· ...... :rf··.·•·····oI:\e'A<>e·s·· ri.o.t.: ...~*is·t·ii;
MSR.•.· c: reates ·····a\····~.e~pofa~y· f3Tf>:ent:fY:l·• na.lfl•~•·•~••.·.······th·e·•··.•·•··:tas~ . .•. .·>.t~kTnJ1; ar19. •.•.•. . 1:~~r1
reqpT·t:>t:.s•.•·•·.•.• .·. tf)<:t. : E!Xe9Qt:iy·~. ·~J:..o··; .rp.f.l.< ~P.e<(~a.:~J<.<. · WbeI'l.\P§k.".l'nI'l E!.;.i1::9;:.\1::ll.~·
E~esu1: i ye . .•a.titpma.tica.I:J.:Y:•· Cl~J,J~~~s.·.··:i<t$> S'fDi·/en1:r¥•
·

1.3

MCR COMMAND SUMMARY

The MCR commands described in Chapter 3 are listed here by category.
This command summary provides a compact overview of the facilities
available at your terminal. Commands followed by (NP) are available
to all users.
Commands followed by (P) are available only to
privileged users.
Commands followed by (NP,P) are nonprivileged
commands with privileged options.
Commands followed by (P,NP) are
privileged commands with nonpriviieged options.

1-5

INTRODUCTION TO MCR
Initialization Commands
ACS {P)

Allocate or discontinue
checkpoint file on disk.

ASN (NP,P)

Define or delete a logical device assignment.
Display current assignments on your terminal.

BOOT (P)

Bootstrap a new system
transfer control to it.

DMOUNT (NP, P)

Dismount a volume by marking the volume for
dismount and releasing its control blocks
(complement of MOUNT).

FLAGS (NP, P)

Create, display, or
event flags.

HOME (NP, P)

Alter the values contained in various fields
of the home block of a Files-11 disk volume.

INITVOLUME (NP)

Initialize a disk, DECtape, or magnetic
to produce a Files-11 volume.

INSTALL (P)

Install a task in the system.

LOAD (P)

Load a nonresident device driver into memory.

MOUNT (NP, P)

Mount a volume by creating its control blocks
and declaring the volume on-line for access
by the file system.

REDIRECT (P)

Redirect all I/O requests from
device to another.

SET (NP, P)

Alter or display
characteristics.

TIME {NP,P)

Enter the time and date into the system.
Display the time and date on your terminal.

UFD (NP, P)

in a
Create a User File Directory (UFO)
Master File Directory (MFD) on a Files-11
volume.

the

into

eliminate

system,

use

memory

group

one

device,

and

global

tape

physical
or

task

Informational Commands
ACT (NP)

Display on your terminal the names of active
tasks that were requested from that terminal.

ATL

Display on your terminal the names and status
information for active tasks.

(NPj

. (~sxSriM8.P4US ·~yg]tent$ OrtlY~J ni'.sp1~y ·.on .. your
t.er'm"in.al ;1:~.e:.jn~)t\E?j~<·fl·n<?·~;t;~«ttts . rlnf·or.m,at:ion for
e.n.tir:i{e~· 1rrY:t.:lllr:!>:9o:tn'tl\O:n \l.~J;oa:lci.· Pireqtdr'y ••

CLQU:!WE (NP)

Display on your terminal
tasks in the clock queue.

DEVICES (NP)

Display on your terminal information about
peripheral devices recognized by the system.

LUNS (NP)

u1spiay on your terminal the list of static
logical unit number (LUN) assignments for a
specific task.
1-6

information

about

INTRODUCTION TO MCR
PARTITIONS (NP)

Display on your terminal
each partition in memory.

TAL (NP)

Display on your terminal the names and status
of all tasks in the system or the name and
status of a specific task.

TASKLIST (NP)

Display on your terminal
each installed task.

description

Task Control Commands
ABORT (NP, P)

Terminate execution of a running task.

ALTER (P)

Alter the priority of a task.

BLOCK (NP, P)

Block a task.

CANCEL (NP, P)

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

FIX (P)

Fix a task in a partition in memory (the task
becomes memory-resident).

REASSIGN (P)

Change logical unit number (LUN)
for a task.

REMOVE (P)

Remove a task from the system (complement
INSTALL) •

RESUME (NP, P)

Resume execution of a suspended task.

RUN (NP,P)

Initiate the execution of a task.
The task
may run immediately, after a time delay, or
in synchronization with the system clock.
Periodic rescheduling is optional.

UNBLK (NP, P)

Unblock a previously blocked task (complement
of BLOCK).

UNFIX (P)

Make a memory-resident
(complement of FIX).

UNLOAD (P)

Remove a loadable device driver
(complement of LOAD).

UNSTOP (NP, P)

Resume execution
task.

task

assignments
of

nonresident
from

memory

internally

stopped

System Maintenance Commands
BRK {P)

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

OPEN {P)

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

SAVE (P)

Copy the current system image into the system
image file from which the system was booted.

1-7

INTRODUCTION TO MCR
SSM

( P)

Insert text into the error log file.

only.<)

c.reat

Multiuser Protection Commands
ALLOCATE (NP, P)

Allocate a device to a user (establishes
device as the user's private device).

BRO (NP, P)

Broadcast a message to one terminal or
set of terminals.

BYE {NP)

Log out of the system.

DEALLOCATE (NP,P)

Deallocate a private
{allocated)
{complement of ALLOCATE).

HELLO or
LOGIN (NP)

HELP (NP)

Display the contents of a help file.

the
to

device

Command Line Interpreter Commands
CLI {P,NP)

Work with a command
other than MCR.

interpreter

{CLI)

DCL {NP)

Issue a DIGITAL Command
Language
command from a terminal set to MCR.

(DCL)

1-8

line

CHAPTER 2
SYSTEM CONVENTIONS

This chapter discusses basic concepts of the RSX-llM/M-PLUS Files-11
file system and highlights aspects of file handling that directly
relate to user functions.
The chapter also discusses devices,
terminals, and tasks.
The last section discusses briefly the Account
File Maintenance Program (ACNT).

2.1

FILES-11

RSX-llM/M-PLUS includes a software system called Files-11 to oversee
the storage and handling of files.
In RSX-llM/M-PLUS, a file is an
owner-named area on a volume, and volum~s are magnetic media such as
disks, DECtape, and magnetic tapes.
Two RSX-llM/M-PLUS utilities and
three MCR commands help you to prepare volumes for use with Files-11:
•

Disk Volume Formatter Utility (FMT)

•

Bad Block Locator Utility (BAD)

•

INITIALIZE VOLUME (IN!)

•

MOUNT (MOU)

USER FILE DIRECTORY (UFD)

The utilities are described in the RSX-llM/M-PLUS Utilities
The commands are described in Chapter 3 of this manual.

Manual.

Files-11 supports three types of specially formatted volumes:
disks,
DECtapes, and magnetic tapes.
(Files-11 magnetic tapes conform to the
American National Standard X3.27-1978.)
For a volume to become a Files-11 volume, you must initialize it with
the IN! command. A volume that has not been initialized by IN! is a
"foreign" volume.
On RSX-llM, foreign volumes do not have to be
mounted for you to work with them (although it is wiser to mount them
for protection purposes);
on RSX-llM-PLUS, the volumes must be
mounted as foreign (MOUNT /FOR) •
A system utility called the File Transfer Utility Program (FLX) allows
you to access foreign volumes in DIGITAL's DOS-11 or RT-11 format.
FLX translates files on such volumes into Files-11 format.
In most
cases, a DECtape will have a foreign format and therefore require the
use of the FLX utility. See the RSX-llM/M-PLUS Utilities Manual for a
full description of FLX.
Before Files-11 can access a file, the volume that contains ~ne file
must be known to the system. You make a Files-11 volume known to the
system by issuing the MOUNT command for the device on which the volume
is loaded.
2-1

SYSTEM CONVENTIONS
2.1.1

File Ownership and Directories

When you create a file, the system places the file name in a User File
Directory (UFD) and stores your current user Identification Code (UIC;
see Section 2.2.1) in the file header to indicate that you are the
owner of the file.
In most cases, the UFD corresponds to your UIC,
but a file can be listed in a UFD that is not related to your UIC.
It
is also possible for your file to be listed simultaneously in more
than one UFD.
(The files will have different file-IDs.)
Each user has a default UFD corresponding to his or her UIC.
The UFD
is on a default system device (SY:), which is specified by the system
manager when the user's account is created.
A UFD is itself a file, which you must explicitly create by means of
the MCR UFD command (see Chapter 3). You specify a UFD in the format
[g,m] where g and m are octal numbers in the range 1 through 377 (0 is
reserved).
The numbers represent the file owner's group and member
number, respectively. The actual name of the UFD is a concatenation
of the group and member numbers, terminated by .DIR.
For example, the
name of the directory that corresponds to the UFD [203,65]
is
2030n5.DIR.
(Note that leading zeroes are added to the UFD to make g
and m three digits each.)
All UFOs oh a volume are listed in the volume's Master File Directory
(MFD),
which corresponds to UFD [O,O]
and
is therefore named
000000.DIR.
The directories (the UFOs and the MFD) list the.names of
files and contain pointers to each file's header. The file header
contains information about the file's owner and the physical location
of the file segments; the header occupies one or more blocks of the
volume's index file ([O,O]INDEXF.SYS).
To delete a UFD, you can use the Peripheral Interchange Program
(PIP)
to first delete all of the files contained in the UFD (thereby freeing
the space for future use) by typing:
PIP>[g,m]*.*;*/DE
After you delete all the files, use PIP to delete the UFD by typing:
PIP>[O,O]gggmmm.DIR;*/DE
The variable gggmmm is the concatenation
number components of the appropriate UFD.

Refer to
the RSX-llM/M-PLUS
description of PIP.

Manual

2.1.2

Utilities

the

group
for

and

member
detailed

File Protection

To access a file, you must know the UFD in which it is listed.
This
knowledge, however,
is not sufficient to guarantee access. You must
also satisfy conditions specified in a protection mask associated with
the file you wish to access.
The volume that contains the file must
be mounted before the file system can access the file.

2-2

SYSTEM CONVENTIONS
Every file has a protection mask that describes the types of access
allowed to each of four user groups. RSX-llM/M-PLUS allows four types
of access:
Read

The user, or the user's task, may read, copy, print,
type the file, and, if it is a task, run it.

Write

The user, or the user's task, may add new data to the
file by writing to space already allocated to the file.

Extend

The user, or the user's task, may change the
disk space allocated to the file.

Delete

The user, or the user's task, may delete the file.

amount

The four user groups are defined by UIC:
System

The operating system itself and privileged users
having group numbers of 10 octal or less).

(those

Owner

The user having the same UIC as the
created under.

one

the

file

was

Group

All users having the same group number as
file was created under.

the

one

the

World

All users.

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

This command allows you to specify
default
file
protection for all files subsequently created on the
initialized volume.

UFD

This command establishes access rights to a UFD file
only.
A user often allows read access to a UFD but
denies write, extend, or delete access to the files
listed within it.

MOUNT

This command allows you, while mounting a volume, to
specify the default file protection to be given to files
created on the volume. This protection overrides the
protection established with the INI command.

PIP

This utility has an option that
alter access rights to files.

enables

the

owner

To gain access to a file, a user must satisfy the protection mask of
both the file to be accessed and the UFD in which the file is listed.
For example, to write to an existing file, you need at least read
access to the UFO and write access to the file.
To create a new file,
you need both write and extend access to the UFD.

2.2

FILE SPECIFICATIONS

MCR uses a standard format for referring to files in a command line.
The format is a string consisting of one or more input and output file
specifications, as follows:
outfilel ••• ,outfilen=infilel ••• ,infilen

2-3

SYSTEM CONVENTIONS

The variable outfile is an output file specification and infile is an
input file specification.
The dots
{ ... )
indicate that you may
include any number of file specifications in the string,
the number
being determined by the receiving command or task.
The command line
(the line of file specifications plus the task or command name) cannot
exceed 80 characters
(or,
for half-duplex terminals, the maximum
buffer size set for your terminal).

Some commands and tasks may not require the outfile portion. When
is omitted, you might also be able to omit the equal sign (=).

The individual file specifications (whether input or output) have
following format:

the

ddnn: [g,m]filename.type;version/switchl .•• /switchn
ddnn:
Specifies the physical or logical device unit on which the volume
containing the file resides.
The device unit is expressed as a
2-character alphabetic device name and an optional 1-, 2-, or
3-digit octal unit number,
followed by a colon (for example,
TT104:
or LPl:).
If you do not specify a unit number,
it
defaults to O.
The default device is your system device (SY:).
[ g ,m]

Specifies the User File Directory (UFD)
in which the file
is
listed.
The variables g and m are octal numbers from 0 through
377 that represent the file owner's group and member number,
respectively.
The square brackets are a mandatory part of the
UFD syntax. The default is the current User Identification Code
(UIC;
see Section 2.2.1) to which your terminal is set.
filename
Specifies the name of the file, an alphanumeric string from O
through 9 characters in length (however, there are exceptions to
this, depending on what program you are working with). A period
always separates the file name from the file type.
You must
specify the file name.
No default is applied.
If you want to include special characters in the file name
(for
example, semicolons or exclamation marks), place quotation marks
around the name so that MCR will parse the name exactly as you
typed it.
If you use only one double quotation mark, MCR assumes
an ANSI magnetic tape file name and parses the. name as such.
(See Section 1.1 for more information on using quotation marks.)
type
Consists of a 1- through 3-character alphanumeric mnemonic that
identifies the nature of the file's contents, or it can be null.
For example, .FTN indicates that the file contains a FORTRAN
source program and
.OBJ indicates that the contents are object
(compiled) code. Some conventional and default RSX-llM/M-PLUS
file types are listed in Section 2.2.4. A semicolon (;) always
separates the file type from the version number.

2-4

April 1983

SYSTEM CONVENTIONS
version
Consists of an octal number from 1
through
77777
that
distinguishes various versions of a file.
For example, when a
file is created, the system assigns it a version number of 1 by
default.
Thereafter, each time the file is opened and, unless
you specify otherwise, the file system creates a new file with
the same file name and file type, but with a version number
incremented by one. Note that if a file has a version number of
77777, no more versions of it can be created.
The numbers -1 and 0 have special significance: -1 implies the
lowest existing version of a file and 0 implies the highest

existing version.
The default is the highest version of the file.
/switch (or /keyword)
Consists of an ASCII name that identifies a task or command
option.
Options generally modify the task's function in some way
or provide information that the task needs to respond correctly
to the command line.
The switch itself can be in one of three forms:
/sw

Sets the switch action.

/-SW

Negates the switch action.

/NOsw

Negates the switch action.

The number of values permitted and the interpretation of a switch
depend on the task to which the switch is directed.
You can also modify switches with arguments.
These arguments may
be ASCII strings, octal numbers, or decimal numbers.
The
following rules apply:

2.2.1

•

Numbers terminated by a decimal point (.) are decimal.

•

Numbers preceded by a pound sign (#) are octal.

•

Whether the default for a numeric value is octal or
decimal depends on the command or task to which the
switch is directed and on the switch i~self.

•

You can precede any numeric value by a plus (+) or
(-) sign;
plus is the default.

•

A plus or minus_ sign, if present, must precede the pound
sign
(#)
of an explicit octal number
(for example,
-#323).

minus

User Identification Codes (UICs)

On .·RSX--llM . ·. J3ystemsthat•·.·. d6·.·· . . no.t sl1p£>9rt. · 1nu1 tiuse.r protection, each
ter-rni!lal . ha~, at any ()n.e t.iJ1le, One Us.er Identification Code (UIC}. A
·terminal's associat.ed UIC i~. d;etermined by the last SET /UIC conunand
issued for t~e terminal:. or is [200; 200] i.f the .terminal •s UIC. has not
been al~ered since .sy~tem 9eneration.

2-5

SYSTEM CONVENTIONS

The system uses t . he. current·. ~!C of the· iSf;Uin9 terminal·· when.ever . you
.omit the UlC field· of a file specification. The sys;tem alsg checks
this UIC against.the pro.tection mask of any .... file that you want to
accE!ss;
the check det:er~ines access rights to the file {see;.sect.·ion
2.1 .. 21 ..
On multiuser protection systems, a terminal has two UICs:
a
protection UIC and a default UIC.
The system checks the protection
U!C against a file's protection mask to determine a user's access
rights to the file.
The default UIC determines the UFD of the file to
be accessed whenever you omit the UIC field in the file specification.
{See Section 2.1.l for more information on UFDs.)
How the system sets these two UICs depends on the privilege status of
the user logged in at the terminal. When a nonprivileged user logs
in, the terminal assumes the user's login UIC as its protection UIC.
The login UIC also becomes the initial default UIC for the terminal.
You can issue the SET /UIC command to alter the default UIC, but the
protection (login) UIC remains unchanged~
When a privileged user logs in, the terminal also assumes the login
UIC as the protection and default UICs.
However, when you issue the
SET /UIC command, the system alters both of these UICs instead of just
the default UIC.
Because the protection UIC is also changed, the
system no longer knows your login UIC.
{This does not apply to
RSX-llM-PLUS systems on which Resource Accounting is active because
the accounting system keeps a record of every user's login UIC.)

2. 2. 2

Wildcards

Wildcards allow you to specify more than one file
in a single
specificaton
by
placing
them in one or more fields of the
specification. A wildcard causes the system to ignore the contents of
the wild field and to select all the files that satisfy the remaining
explicitly specified fields.
Asterisk wildcards
{*)
can be used
in any part of the
file
specification except the device-unit field, which must be explicitly
supplied or defaulted to SY:
(see Section 2.2.3).
The following
examples illustrate the advantage of using the asterisk wildcard:
PIP>PROG.MAC;l,PROG.OBJ;l,PROG.TSK;l/DE
This command line deletes the three individual files specified.
(The /DE switch instructs PIP to delete the files.) Since the
three files have the same file name and version number, but
different types, the following command line would delete the same
files:
PIP>PROG.*;l/DE
This command line also deletes any other fil~s
(on the default
device in the default UFD) named PROG with a version number of 1.
You should check existing files before using wildcards
(for
example, by issuing the command line PIP>PROG.*;l/LI).

2-6

SYSTEM CONVENTIONS

File Specification Defaults

2.2.3

You can omit any field in a command-line file specification except the
r11e name.l When you omit one or more fields in a file specification,
the system assumes the following defaults:

Default

Field
ddnn:

The pseudo device unit SY:.2

[g ,m]

The default UIC (see Section 2.2.1)
specified
each terminal in one of the following ways:
1.

At system generation

RSX-llM-PLUS

(see

System

for

the RSX-llM or
Generation
and

Installation Guide)
2.

By means of the SET command (see Chapter 3)

By means of the HELLO command
3)

(see

Chapter

filename

No default
(except for the BOOT
command).
A
specification must include an explicit file name or a
wildcard within the file-name field
(see Section
2.2.2).

type

Any 1- through 3-character alphanumeric mnemonic, one
of the types listed in Section 2.2.4, or nulla
Default types depend on the task to which the
specification
is
directed
and
whether
the
specification refers to an input or an output file.
For example,
the FORTRAN compiler defaults the type
of an input file to .FTN and the type of an output
file to .OBJ.

version

For input files, the highest existing version number.
For output files, the highest existing version number
plus 1.

/switch

2.2.4

Switch defaults are established by
and commands.

individual

tasks

Conventional and Default File Types

RSX-llM/M-PLUS has a set of conventional and default file types used
to
reflect
the
contents of a
file.
(The defaults used by
DIGITAL-supplied software are described in the manuals that pertain to

1. The BOOT command
See Chapter 3.

the

only

exception

this

rule.

( $)
in the
2. The BOOT command and specification of a dollar sign
INSTALL and RUN command lines default to device LB:.
See Chapter 3.

2-7

SYSTEM CONVENTIONS
the individual programs.) Although you can assign your own 3-character
file types, it is convenient to use the following types:
T~e

File Contents

BAS

BASIC-11 language source program (default)

BAT

Batch file

B2S

BASIC-PLUS-2 source program (default)

CBL

COBOL language source program (default)

CLB

Indirect command file library (default)

CMD

MCR or task
default)

COR

SLP correction file

DAT

Data (as opposed to a program;
specified)

DIR

Directory
default)

FTN

FORTRAN IV, FORTRAN IV-PLUS, and FORTRAN-77
source program (default)

LOG

Log of batch processing session (default)

LST

Listing file (default)

MAC

MACR0-11 source program (default)

MAP

Task Builder memory allocation map (default)

MLB

Macro library (default)

OBJ

Object program (output from the MACR0-11 assembler or
a compiler; default)

ODL

Task Builder overlay description (default)

OLB

Object module library (default)

PAT

Correction file used by assembler to create a patched
object module (convention; must be specified)

POB

Patched object module input file used by
utility (convention; must be specified)

SML

System macro library (default)

STB

Symbol table

SYS

Bootable system image (default)

TMP

Temporary file

TSK

Task image (default)

TXT

Text file

ULB

Universal library file (default)

(default)

commands

(for

(an

indirect

(convention;

example,

command

file;

must be specified)
convention;

User

File

must

Directory;
language

the

PAT

(default)

(convention;

2-8

must be specified)

April 1983

SYSTEM CONVENTIONS
2.2.5

Examples of File Specifications

In the following examples, the three letters followed by a right-angle
bracket
(>)
are standard task prompts for the respective system
programs.
the MACR0-11 source file CRGPT.MAC and create the
• Assemble
object output file CRGPT.OBJ.
UFD [200,200] on device DMO:
is specified for both files.
MAC>DMO: [200,200]CRGPT.OBJ=DMO: [200,200]CRGPT.MAC
the file SBG.OBJ;5.
The output file specification is
• Delete
The input device
not applicable and therefore is omitted.
defaults to SY:.
PIP>[200,200]SBG.OBJ;5/DE
•

Task-build the object file CRGPT.OBJ (.OBJ is the default file
type for object files).
The output file will be named
CRGPT.TSK because .TSK is the default file type for the Task
Builder's output file.
The device and UFD are also defaulted.
TKB>CRGPT=CRGPT

•

Delete all files with the name TESTDAT, regardless of type or
version.
The system uses default values for the device and
UFD.
PIP>TESTDAT.*;*/DE

2.3

DEVICES

A primary function of the operating system is to manage all connected
peripheral devices and thus maintain efficient system performance.
Peripheral devices are the actual hardware elements that make up the
computer
system.
During system generation, the system manager
explicitly describes all peripheral devices attached to the system.
Devices within multiuser protection systems are subject to a special
set of MCR functions (described in Section 2.3.5).
Each device has a unique identifier.
The identifier consists of two
alphabetic characters, which form a logical device name (see Section
2.3.4), and an optional 1-, 2-, or 3-digit octal unit number, followed
by a colon
(:).
If you omit the optional octal unit number~ the
system defaults to unit O.
See the RSX-llM or RSX-llM-PLUS System Generation and Installation
Guide for-a--list of the peripheral devices supported by the respective
operating system.

2-9

SYSTEM CONVENTIONS
2.3.1

Logical Unit Numbers

A task performs I/O operations using logical units identified by
numbers,
called logical unit numbers
(LUNs),
rather than using
specific device units.
You assign a LUN to a specific device before
the task actively uses the LUN.
You can make the LUN assignment at
one of three points:
1.

At task-build time

From within the task at run time using
directive

the

ALUN$

Executive

With the REASSIGN command after the task has
and while it is dormant

been

installed

Refer to the RSX-llM/M-PLUS I/O Drivers Reference Manual or the
appropriate language user's guide for more information about logical
unit numbers.

2.3.2

Pseudo Devices

A pseudo device is a device-unit name that usually corresponds to a
real physical device.
This association is declared through the
commands ASSIGN and REDIRECT.
Pseudo devices provide a shorthand
method for referencing the physical devices (for example, the pseudo
device name SY:
refers to the user's system device).
Table 2-1 lists
some of the RSX-llM/M-PLUS pseudo devices.
Table 2-1
Pseudo Devices
Pseudo Device

Name

Console listing device

CL:

Console output device

CO:

System library device

LB:

Terminal input/output device

TI:

User's system device

SY:

Spooling device (RSX-llM-PLUS only)

SP:

In a given task, LUN 1 may be assigned to CL:,
the console listing
device.
When the task references LUN 1, the data is sent to whatever
device CL: has been redirected to.
You can redirect CL:
to any
appropriate device (a line printer or a terminal, for example) without
affecting the task's execution.
A pseudo device redirected to a terminal assumes the privilege status
of the terminal
to which it is redirected.
If the terminal is
privileged, CL:
becomes privileged when it is redirected to that
terminal.
But if CL:
is subsequently redirected to a nonprivileged
terminal, it will also become nonprivileged.

2-10

SYSTEM CONVENTIONS
The normal procedure is to redirect the console output device (CO:) to
the main operator's terminal and CL:
to the line printer.
The system
automatically redirects TI:, the most commonly used pseudo device,
depending on how a task has been activated:

2.3.3

•

When you issue the RUN command to activate a task immediately,
the system redirects the TI:
for that task to your terminal.

•

If, in a task, the Executive directives RQST$ or SPWN$
activate another task,
that task's TI: defaults to the TI:
of the task that issued the directive. A privileged task can
specify an alternate TI:
for the activated task.

•

If the Executive enters a task into the clock queue for
activation
after
a specified interval, the task's TI:
defaults to CO:.
(Both the RUN command and the Executive
directive RUN$ allow a task to be activated at a specified
interval from the time the command or directive was issued.)

The Null Device

Program testing often requires an available input or output device.
The null device (NL:) can be used for either of these purposes. NL:
is neither a pseudo nor physical device, but, most of the time, it is
considered to be a pseudo device.
When a task reads from NL:, NL:
returns the code for end-of-file
returns the code for
(IE.EOF).
When a task writes to -NL:, NL:
success (IS.SUC) but discards the output.
As an example, if you are testing a program that normally generates
large amounts of printout, you can assign the appropriate LUN to NL:
rather than wasting paper or disk space.

2.3.4

Logical Device Names

Logical device names provide another means by which tasks can maintain
device independence.
(On RSX-llM, the availability of logical device
names is a system generation option.
On RSX-llM-PLUS,
it is always
included in the system.) A logical device name has the same syntax as
a physical device unit.
It consists of a 2-letter ASCII name and an
optional 1- or 2-digit octal unit number, followed by a colon (:).
The name can either be equivalent to a standard RSX-llM/M-PLUS device
name
(for example, DM:), or it can consist of two letters picked at
random (for example, ZZ:). Before you run a task that refers to a
logical device rather than a physical device, you must issue the
ASSIGN command to associate the logical device name the task uses with
a physical device unit (see Chapter 3).
NOTE
The names II:
and RD:
are used by
DIGITAL software. Using these names as
logical device names
could
produce
undesirable results.

2-11

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

exist

RSX-llM/M-PLUS

•

Global assignments apply to all tasks running in the system.

•

Local assignments apply only to tasks initiated from the
terminal used to make the assignments.
Any terminal can
define or delete its own set of local assignments.

•

Login assignments apply only to systems that support multiuser
protection.
When a user issues the HELLO (or LOGIN) command
to log in on the system, the system automatically establishes
one or more login logical device assignments. The login
assignments apply only to tasks initiated from the terminal
while the current user is logged in. Only privileged users
can define or delete login assignments.

2.3.5

Public, Private, and Unowned Devices

Systems
that
support
multiuser
protection
impose
special
characteristics on devices.
Devices can be public, private, or
unowned. These characteristics are defined as follows:
•

A public device is a device that anyone logged into the system
can use.
A privileged user can make a device public by
issuing the SET /PUB command. If a privileged user mounts a
volume on a public device, all system users can access files
on the volume without having to mount the volume themselves
(depending on the volume and file protection specified for the
volume). A public device cannot be allocated and can only be
dismounted by a privileged user with the DISMOUNT /DEV
command.
(See Chapter 3 for descriptions of the MOUNT,
DISMOUNT, and SET commands.)

•

A private device is a device that a user has allocated by
means of the ALLOCATE command. Only privileged users and the
owner of a private device can access the device for use within
the Files-11 file system. If a nonprivileged user allocates a
device and mounts a volume on the device, other nonprivileged
users cannot access the volume; privileged users can access
the volume by issuing a MOUNT command.

•

An unowned device is a device that is neither public nor
private.
If a user, either privileged or nonprivileged,
mounts a volume on an unowned device, all other users can
issue subsequent MOUNT commands and thus access the volume.
Nonprivileged users can allocate and
unowned device.
Privileged users
unowned device.

2-12

mount a volume on an
can also set public an

SYSTEM CONVENTIONS
A privileged user can designate any device in the system as a public
device.
The devices most commonly made public are the system disk (by
default) and the system library device.
The ALLOCATE command (see Chapter 3) makes an unowned device private
to the user issuing the command. Allocating a device prevents any
other nonprivileged user from accessing the device.
(Privileged users
can override a nonprivileged allocation.)
When a user accesses a
device without allocating it, other users can then access and/or
allocate that device.
The DEALLOCATE command (see Chapter 3) changes a private device back
to an unowned device, thereby allowing other users to gain access to
it.
Privileged users can deallocate any private device no matter who
owns it.
Nonprivileged users can deallocate only their own private
devices. When a user logs out, the system automatically dismounts and
deallocates any private devices belonging to that user.
For efficient
use of system resources, however, users should deallocate devices as
soon as the devices are no longer needed.

·To:.a~(!~ s;i:;··· •(.i··•··.· yo1.t.l!11~·•····.•9.1:L. a,·.·.f'p~slc?•l.• .• •~rev :i%e···• .J1'1:·.····?:t1:••.·• ~~~.tt:I.:Itt'f '"7P4l.J~l . ·y~Y$ttel1l.,:·.•·· Y()l.:J

·.111~ !J:~:··••··~·~···~·~ B>•J·~~.9e,.t:P..7· \.~'?:~.~:;·.··•·•A<>ffill.lf.h~.·~tx .•.•.<1'.f:;,~.···"?? ;um:7. • . . t~.•····r~C>t:. ·.·, . . ·~.?Fn:t?:t•t:.•7~·•···•······•·•·•C?.1:'::
·A'.$/·. i:9c/••···.•~•······•·•····.·. . :~()P~~;tt..••.• •.···p1;,'pe·r:••·.~.·•.• ,tpan. ··· · •·· . . tr:i·l~·sf+•J>~;··Y'?u:•·.~ti·~··.t:.··•.lt19~P:t·.·t:b~
·t:or·e,ig11·•w:i·t:'.b· tbe,·:.< . . tl!."oa:·:k.eyw<:>i:"d~>
·· · ·· · · · · ·· · ·· · · · · · · · .•.·:yq:tum~•i·~~
· ··
>·: ·: ·:·: ..... :_;. ·<. ·. ·..
......... ,~ •• _:" ..' ..........: :::.··· ••• ;_:.·:.............. ·.< ·.-,_.-:·: :" •• ,·.....-_.... ,. ,.: .-:. :/ ·::.;· ·::.·

2. 4

,<·::·:··.:~·

.......

!·. : .... ·.:.

·. ::·' :......... ..

TERM INA LS

The terminal is the primary channel of communication between the user
and the computer system.
Each terminal
in a system has a number
associated with it, which is displayed when you log in.
You can also
refer to any terminal that you use as TI:, and you can work from more
than one terminal at the same time.
In RSX-llM/M-PLUS, several terminals can operate concurrently.
Each
terminal operates independently of others in the system so that each
can run tasks at the same time.
For example, the PIP utility and the
MACR0-11 assembler can run concurrently from different terminals.
(The same task can also run concurrently from different terminals,
although each copy of the task running will have its own identifier.
See Section 2.5.4 for more information.)

2.4.1

Input Prompts

When you use MCR, there are three prompts that indicate a terminal
waiting for input from you:
•

The default prompt (>)

•

The task prompt (tsk>)

The MCR prompt (MCR>)

2-13

SYSTEM CONVENTIONS
The default prompt (>) at the beginning of a new line indicates that
the
terminal
is ready to accept unsolicited input.
The term
unsolicited implies that no specific task has requested input from the
terminal.
Whatever you type
in response to the default prompt is
directed to MCR.
(An abnormal si tua ti on can occur, however, if a task
either solicits input or attaches to the terminal without displaying a
task prompt. A soliciting or attached task might receive input that
you intended for MCR.
See Section 2.4.4 for information on attached
terminals.)
When MCR receives unsolicited input,
it identifies,
analyzes, and responds appropriately to the input.
When MCR activates a task to service
prompts:

command,

the

task

normally

tsk>
The variable tsk is a 3-character task name.
tasks identify themselves by a
3-character
should do the same.)

{All DIGITAL system
prompt and user tasks

As long as a prompting task has attached to a terminal, the task
receives all sol}cited input entered at the terminal until the task
detaches (see Section 2.4.4). The terminal discards all unsolicited
input.
An unattached task, however, may not receive solicited input
because another task could solicit input from the terminal before you
can type a response to the prompt for the unattached task. The
intervening task would then receive the input intended for the
unattached task.
To avoid this situation, every task that solicits
input from a terminal should perform the following sequence of
actions:
1.

Attach to the terminal.

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

Solicit input (issue a read ·request) •

The MCR prompt (MCR>)

2.4.2

is described in Section 1.1.1.

Special Character Keys and Control Characters

You can request the system to control terminal operation by means of
special character keys and control characters. The relevant special
character keys are TAB, ESCape (or ALTmode), RETURN, and DELETE
(or
RUBOUT).
In this manual, the symbols
CT@,
m, ~,and (fill,
respectively, denote these keys. A control character is produced when
you type a letter key while pressing the CTRL (control) key.
In this
manual, a control character is written CTRL/n where n is the variable
ietter key.
When you type CTRL/R, CTRL/U, or CTRL/Z, the Executive and the
terminal driver display AR,
Au, or AZ at the issuing terminal and
perform the related function. When you type CTRL/C, the explicit MCR
prompt
(MCR>)
is displayed.
{If
the terminal is set to recognize
commands from DCL or a user-written CL!,
CTRL/C would display that
prompt instead.) For the other control characters, the Executive does
not return a display.
Table 2-2 lists all the special character keys and control characters,
and describes the function of each.

2-14

SYSTEM CONVENTIONS
Table 2-2
Special Character Keys and Control Characters
Character

Description

RETURN

The RETURN key terminates a line of input and advances
the cursor or print head to the beginning of the next
line.

ESC

The ESC key terminates a line of input without moving
the cursor or print head. When used to terminate an
MCR command, it suppresses the default MCR prompt.
See the descriptions of the OPEN and RUN commands (in
Chapter 3), which have special uses for the ESC key.
In systems that selected the appropriate optional
facility at system generation, the ESC key can be the
first character in an escape sequence
(see
the
RSX-llM/M-PLUS ·I/O Drivers Reference Manual and the
description of t~SET /ESCSEQ command in Chapter 3 of
this manual).

DELETE

The DELETE key deletes the last character typed at the
terminal and further contiguous characters if the key
is pressed repeatedly.
On non-CRT terminals,
the
first DELETE typed deletes a character and prints a
backslash (\) followed by a display of the deleted
character.
Subsequent deletions cause the system to
display the deleted characters.
Then, when you enter
the first non-DELETE character, the system prints a
terminating backslash followed by the character typed.
For example:
first DELETE
second DELETE
third DELETE
i---first non-DELETE

lfr~

MISTKAE\EAK\AKE
The result is MISTAKE.
On a CRT terminal that supports backspacing (a system
generation option in RSX-llM;
always
included in
RSX-llM-PLUS) and has been declared to be a CRT
terminal by the SET /CRT=ttnn:
command, the DELETE
key moves the printing position one space to the left
and erases any character displayed in that position.
For example, to correct the word MISTKAE,
press the
DELETE
key
three
times to erase E, A and K
respectively.
The result is MIST.
Then type AKE to
get MISTAKE.
(Note that when DELETE deletes a character in the last
character position on the right of the screen, the
last character appears to remain and the next-to-last
character disappears.
However, the system has in fact
deleted the last character. You can type CTRL/R to
··--.;~.,,.,
VCL. J.J..:f

~~;c
'
.._,. ... ._,•I

(continued on next page)

2-15

SYSTEM CONVENTIONS
Table 2-2
(Cont.)
Special Character Keys and Control Characters
Character
CTRL/C

Description
CTRL/C typed either as the first character in the line
or when the terminal
is sending data causes MCR to
prompt for command
input with the explicit prompt
MCR>.
If the terminal is set to a CLI other than MCR,
typing CTRL/C displays the explicit prompt for
the
CLI.
(Two special effects of CTRL/C are described in
the following text.)
If a task is prompting for input when you type CTRL/C,
MCR displays its explicit prompt, then returns control
to the interrupted task after receiving a single line
of input.
(An exception arises when an attached task
specifies an Asynchronous System Trap -- AST -- for
unrequested characters.
In this case, CTRL/C causes
an AST to occur, thereby gaining the task's attention
rather than MCR's.)
Special effects:
•

If the last character entered at the terminal
was CTRL/S, CTRL/C resumes output suspended by
the CTRL/S.

•

If a terminal has been set to
"hold screen"
mode by the SET /HOLD command, CTRL/C has the
effect of a SET /NOHOLD command;
that is,
CTRL/C disables hold screen mode.
(The hold
screen feature is, in some cases, a system
generation option in RSX-llM but is always
included in RSX-llM-PLUS.)

See Section
CTRL/C.

1.1.1

for

information

using

CTRL/I
or
TAB

CTRL/I (or TAB) moves the cursor or print head
to
the next horizontal tab stop on the line.
The system
establishes tab stops at every eighth
character
po s i t ion in the 1 in e ( 8 , 1 6 , 2 4 , and so on) •

CTRL/K

CTRL/K causes a vertical tab by performing
feeds.

CTRL/L

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

CTRL/O

CTRL/O alternately suppresses and resumes the display
of output at your terminal.
It allows you to skip
over any unwanted output and then continue the display
at a later point.

four

line

(continued on next page)

2-16

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

Description

CTRL/O
(Cont.)

When you type the first CTRL/O, the system discards
the output it is sending to your terminal rather than
displaying it.
(The system can send the output much
faster when it does not also have to display it.) When
you
type
the second CTRL/O,
the system begins
displaying the output at the point it has reached in
sending it
(not from where you typed the first
CTRL/O).
If you do not type another CTRL/O,
the
system continues to display the output until
it
reaches the end. The effect of CTRL/O also depends on
the state of the terminal when you type the character.
If the terminal is attached to a task other than MCR,
CTRL/O suppresses the display of the task's output
until you type another CTRL/O to resume the display
(as described previously).
However, if the terminal
is not attached to another task, CTRL/O suppresses
only
the remainder of the line currently being
displayed.
Subsequent lines of output will still be
displayed.

CTRL/Q

CTRL/Q typed after a CTRL/S resumes output suspended
by the previous CTRL/S..
(This feature is a system
generation option in RSX-llM but is always included in
RSX-llM-PLUS.)

CTRL/R

Typing CTRL/R before typing a line terminator
(RETURN
or ESC)
causes the system to retype the current line
on a new line, omitting any deleted characters.
You
can then continue typing the remainder of the line.
For example:
MISTKAE\EAK\AKE AR
MISTAKE
If the current line is empty and you issue CTRL/R from
the explicit MCR prompt
(MCR>), CTRL/R performs a
carriage return and line feed.
CTRL/R is echoed as
AR.
(This feature
is a system generation option in
RSX-llM but is always included in RSX-llM-PLUS.)

CTRL/S

Typing CTRL/S while the terminal is rece1v1ng output
suspends additional output until you type CTRL/Q or
CTRL/C. The suspended output is merely delayed, not
discarded as with CTRL/O.
The combined functions of
CTRL/Q and CTRL/S are convenient when using a CRT
terminal.
(This feature is a system generation option
in RSX-llM but is always included in RSX-llM-PLUS.)

CTRL/U

Typing CTRL/U before typing a line terminator
(RETURN
or ESC) deletes the current line. The system responds
with a carriage return and line feed and displays a
new prompt so that the line can be retyped.
(continued on next page)

2-17

SYSTEM CONVENTIONS
Table 2-2 (Cont.)
Special Character Keys and Control Characters
Character
CTRL/U
(Cont.)

Description
The system also displays a CTRL/U when you begin to
type a command line but do not press the RETURN key
before the timeout count expires.
(The timeout count
is specified at system-generation time.) Again, a new
prompt is displayed.
CTRL/U is echoed as AU.
(This control character works
only with the full-duplex terminal driver.)

CTRL/X

Typing CTRL/X clears the terminal typeahead buffer.
The
typeahead
buffer
temporarily
stores input
characters until the terminal driver can pass them to
the task.
When the typeahead buffer is full, input
characters are not accepted. Typing CTRL/X clears the
buffer.
(This control character works only with the
full-duplex terminal driver.)

CTRL/Z

Typing CTRL/Z indicates end-of-file. It is used to
indicate to system tasks such as MAC, PIP, and TKB
that you are finished and the task may exit.
CTRL/Z
is echoed as AZ.

2.4.3

Terminal Privilege

You can issue privileged commands only from a privileged terminal. On
multiuser protection systems, individual users are either privileged
or nonprivileged.
When you log in, the terminal assumes your
privilege status. On other systems, a terminal's privilege status is
determined initially at system generation. You can also use the SET
/[NO]PRIV command (see Chapter 3) at a privileged terminal to modify
the privilege status of your own and any other terminal connected to
the system,,
CAUTION
You must take great care
terminal
is
privileged.
commands can destructively
with system operation.

2.4.4

when
any
Privileged
interfere

Attached and Unattached Terminals

A terminal is attached when all input and output are directed to or
from a task other than MCR. For example, when you invoke a task (such
as the text editor EDI), the task usually attaches to the terminal so
that no other task can use the terminal for I/O. When you wish to
exit (by typing CTRL/Z, for example), the task is detached from the
terminal and subsequent input is usually directed to MCR.
Since an attached terminal directs all input to the dedicated task,
you must either exit from the task or type CTRL/C to gain MCR's
attention before attempting to communicate with MCR.
(See Section
1.1.1 for a description of CTRL/C as a means of temporarily gaining
MCR's attention.)
2-18

SYSTEM CONVENTIONS
See the RSX-llM/M-PLUS I/O Drivers Reference
information on terminals and terminal drivers.

2.4.5

Manual

for

Slaved Terminals

You can dedicate a terminal exclusively to one or more tasks by
issuing a SET command option that sets the terminal to slave status.
(A special I/O function issued by a task can also set a terminal to
slave status.) The difference between a slave terminal and an attached
terminal is that a slave terminal rejects all unsolicited input,
including CTRL/C, but excepting CTRL/O, CTRL/Q, and CTRL/S. Attached
terminals, as described in the preceding section, do accept CTRL/C.
Until you issue another MCR command (or a task issues another special
I/O function)
to delete the slave status, the terminal can only be
used to communicate with tasks soliciting input from the terminal.
Slaved terminals are often dedicated to real-time applications.
See the RSX-llM/M-PLUS I/O Drivers
terminals and terminal drivers.

2.5

Manual

for

information

TASKS

The basic executable unit of an RSX-llM/M-PLUS system is the task.
A
task is either privileged or nonprivileged. A privileged task has
special device and memory access rights that a nonprivileged task does
not have.
Because of their special access rights, privileged tasks
are potentially hazardous to a running system whereas nonprivileged
tasks are not.
The following sections give only cursory information about tasks.
Consult
the RSX-llM/M-PLUS Task Builder Manual for a complete
description.

2.5.1

Partitions

A task runs in a predetermined contiguous area of memory
partition. A partition has the following characteristics:
•

A name

•

A defined size

•

A fixed starting address

•

A defined type

called

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

2-19

SYSTEM CONVENTIONS
2.5.1.1 Partition Types - There are two types of partitions in
tasks can execute:

•

System-controlled

•

User-controlled

which

In a system-controlled partition, the Executive allocates available
space to accommodate as many tasks as possible at any one time. This
allocation may involve shuffling resident tasks to arrange available
space into a contiguous block large enough to contain a requested
task. Only mapped systems support system-controlled partitions.

·Ai u~e~-c()~·tr-()11.~d·.· .·.·partt··ti.oh.> ..• how~ver,, .• f·s .e.~glusiv.~·1'/ ~lloc~Eed···:•~o .· ·• ·. on.e

. ·•

t~~¥ <1t<· a. >·t.~1n~···.····. 'Ph.is tyf)e . • of pC;trtlt:i9r1 •i.~·· . suppor;t:ecl,\by bo;t:.J:i <1nilil?P~Cl
a:n.ci: unmqpP'f~d.':FtSX~+1M systems~
·
· · ··
·· ·
···
·

In both types of partitions, the Executive can temporarily move
(checkpoint) a resident task to a disk to make space available for
another task.

2.5.I.2 Subpartitions -RSX-llM users can subdivide a user-controlled
partition . into as . many as seven nonoverlapping subP,cartitions. .Like
its parent main partition, . a subparti:tion c·an. contain only one task at
one ti.me. Since the subparti.ti:ans occupy the same physical memory <as
the main partition, tasks ;cannot :be .simul tane:ously · reside.nt. ;i°; : both
the . rnatn . partition and •· one ;o-r m.are ,SUQpartiti,ons .: But sinc;e ec:fo'h
subpa rti t ion can col'l\t.ai n a task, :up ;to seven .tasks can potentially run
in :par;al}el wi.thin a, chepkpolnte,d::.main ;t~a,rtit;ion.,
1

RSXjllM :uses subparti tions to reclaim: large storage areas i.n unmaipp~d
systlem$.
For example, when a large tas'k that requires a main
partition . is either . no.. longer active or . can . be
checkpointed,
subpartltioning allows t:he partition space to be used' for a number of
~m9'~.~et:' .t.~.s){s,

2.5.2

Multiprogramming

Tasks compete for system resources (including memory) on the basis of
priority and resource availability.
The priority of a task is
determined by a number assigned when the task is created by the Task
Builder, when it is installed, or when it is run. The number is in
the range l through 250(10), where 250 is the highest priority.
The
highest priority task that has access to and can use all the resources
it needs has control of the CPU.
A task often becomes blocked when it requests system services.
For
example, it can block itself as it waits for an I/O transfer to
complete. While the task is blocked in this way, the Executive looks
for another task to use the CPU. The chosen task will be the one that
has the highest priority and whose needed resources are available.

2-20

SYSTEM CONVENTIONS
2.5.3

Creating a Task

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

Enter a program in a supported
editor ..

source

language

through

Submit the source code to the
appropriate
(assembler/compiler) to produce an object file.

Submit the object file to the Task Builder to produce a
image file.

Use the INSTALL command to install the task image file in the
system or use the install-run-remove option of the RUN
command (see Section 2.5.5.1).

translator
task

The output files that result from Steps 1, 2, and 3 are each stored on
a Files-11 volume.

2.5.4

Task-Naming Convention

''on /~sx;...;!lt*t• m#l.t'.~tis~r·.•rp'fd#~¢#ion• '$y•stems t'··· ·lllc>te . .· . . . .than· ' one .,c~i;>t··,<>f . . . . . ~n
·'ins'ta1:.teti . task> who.se. name· is in· the form .... )(~~ /,p.an J:?~.>~P~J\l~
~i#lul.t:l:l.neo\1:$ :ly,.(('hC)~~V~J 'fi ·. .•ttl.ete . •. q an'·.· 9n1y· ·be> . . ()ne·· .cop;{ . ;~ p~~·y7 . . ·.·•· f' rp~ . ···/ . •<il'.le•
·.5.~.r.ni~.ri~J).,·.·. .~~9·

y()µ'·.· ... requ~s;t. ·: a: .··tas~:: . ·.·ith~'t. ·ts a.1 reap·y;·•q·<:t.~·y·e, :~P~·
anttc6Jt1~t:iq.·~·~1¥:;.c•r.~a.t.~s.·:·E1 .·.n.artte· ·...fqr a··• c.opy··••·•·. :. o.f ••.·. the, ·i:-~99e·~t:·eR.··· t<3·~·k::
t$kTnn·,,. ~l;lere . t:~k · . jsthe ~~¢hara6t:~r task· . . name and···Tnni:s. the ·octal'
·11t1it. number. of the rec:ruei;~ingtermJnal• · aoweveI•r to......... ref'e(.·••t•o; .... that
task:. ··fr"'om .··th~· ·.... reque$t.ing. termin<llt yoµ ····only ·n?~9" . . t:q ?P~c:i¥y the
37'.'cha.racter t.af;k name Jtsk) •...

a~. :i, (lnQ,t~~r:;.. te};·mlpc:1l,······ ~CR .·: ~tiris a•. task· .called :PI<PT2~··· '.ro <~t&:rt .l?I:PT2
· :f·.rotrt'''TT2;,:··.·.·e.ntet ·the,·c·omm;and•:···· ·

. . . . . .;;>.~&~£~'; ·>······ ·
·;tI!i );'i ;.:;;; :"i;B:;. 7
....
~~g~~~·!~~!<0.~~i~~b( ~d~~;Q~'·~~~%'!;'fil<(~;:~~;,rn~~.:~~i i'r2.!J.S C~P!' ·;g~

l?Jl? :froin,.,apo.ttie:r ·'be:r~in.p;.l,. a .. t:lr.~y.A~eq.e.9 ·9s~r Jl1.q$t;t::YPe·:•· ·

:· •: ··.·•:"?~~·9::•····~£~~·~·····,:······ •.• .:.· · •· • ·•· .<::•·····;»·/·./'.
. ,......, .... , .............. '

·.:,~: ~·-"-" .· "'·-'"·'·~·;.;.-~·· ·.".·'_

. .,

n:ecessa.~y ..·. ·in:,.most. cases..

.·.• . .· · ·.· .· •· •·. ·. ·. .

;'··<:___~'._·,_.:,:.--_./ :. .:.:·,.·<::· >~.:

'< ·•

< >

.....

/"·_::_~·f.::.='.:="/i

··• :

dri RSX- ihl sy,.t:•.i.~ : \lfi ;\ .nlJIDhe~.. f~ r eel'.IDt riaTS . rarige .· frOm ..•. 0 •.• through

77(8), altho(lg}'i it . is poss.ible to have terminals connected to the
syste1n J:hat have. t~rm~nCil numb~rs c3rea,ter•·'. . than•.J7 •.. ·.·.· How7Yl:?f1 ».. b~c.ause
of the xxxTnn nami99 convention for RSX-11M, i f you try t.o• run an
active inst9lled task from a t.e,rminal whose. unit number .··is.···. greater
than 77, the task will have an incorrect name or you will get an error
message.

Note that the naming convention does not apply to tasks
the· RUN command.

2-21

requeited

SYSTEM CONVENTIONS

For example, i f you request PI~ from ·.TTlOO ~, MCR runs a
PIPTAO. To abort PIPTAO. from TTIOO: I enter >the. command:

task

>ABO PIP
MCR aborts the correct copy of PIP. However, to abort TTIOO:'s copy
of PIP from another terminal, a privileged user must either specify
the full task name (tskTnn) or use the'ABORT command's /TERM keyword.
For .example, either . of the · :followin9 ·command 'lines·' issued "from a
privileged terminal abort TTlOO!'s copy :of PIPi
·

>ABO

2.5.5

Installing a Task

When you install a task with the INSTALL command or a form of the RUN
command,
the system records a number of task parameters in a
system-resident list called the System Task Directory (STD).
These
parameters include the name of the task and the address on the volume
that contains the task image. An installed task is defined as a task
that has an entry in the STD;
it need not be resident in memory nor
competing for system resources.
The system considers a task dormant
(not active) until a request is made for it to run.

2-22

SYSTEM CONVENTIONS
The concept of dormant and active tasks is important in a
real-time
system.
A dormant task does not use any memory outside of the
Executive (it requires only an STD entry and need not be resident),
yet when the task
is needed to service a
real-time event, the
Executive quickly and efficiently
introduces
it
into
active
competition for
system resources.
An
installed
task's STD entry
enables this quick response because the STD contains all
the
parameters the system needs to retrieve the requested task.
You can run an installed dormant task by issuing the RUN command, or
another task can request the task to run by issuing an Executive
directive, such as RQST$ (Request), RUN$ (Run), or SPWN$ (Spawn).
When the Executive receives a request to run a
series of actions:

task,

performs

Places the task in active competition for
system
(including memory) with other resident tasks.

Allocates the necessary resources as they become free.

Brings the task into memory when there is space available
in
its
partition.
(The Executive can checkpoint a
lower
priority checkpointable task, if there is one, to make
room
for the requested task.)

resources

If another task fully occupies the partition in which the new task is
to be
installed and no resident task can be checkpointed, the system
places the task in a queue of other requested tasks, each waiting
for
space to become available in its partition.
Note that the number of
installed dormant tasks can, and usually will, far exceed
the number
of active tasks.

issued from:TT1:
or from any prlV'Ueged.terminal also. aborts the task
originally referred
to as $CALC in the RUN command issued from
terminal TTl:.
;···.·

.. ,

O~ .RSX.:-l1fllt~PLiJS ... systems 1 .· ..·..•MCg /ctls.o.·•·n.amEts .the •. . . ta$k •'r'rl1J1, . . ·Where . JUl. is tti~

unit nuI\lber of the terminal that .requested the>task.
To refer. to task
TTnn'in a command i:ssued frorrrthat terminal, you . can omit the task
name altogether-.. For ~xample, i f you issue the following command from
TT377:
>RUN<$CALC

2-23

SYSTEM CONVENTIONS

2.6

NONPRIVILEGED USE OF ACNT

RSX-llM/M-PLUS systems provide an Account File Maintenance Program
(ACNT)
for creating and maintaining an account file for a multiuser
protection system. The account file contains entries for all the UICs
that have been authorized for use in the system. One UIC can be
shared by several users, each user having his or her own password.
A nonprivileged user can run the ACNT program to change his or her
password.
All other ACNT options are privileged. The ACNT task must
first be installed by a privileged user before a nonprivileged user
can run it.
When you run the ACNT program, it identifies itself and
immediately
prompts for your current password. ACNT then searches the account
file for the entry that matches the UIC and password.
When ACNT
locates the correct entry, it prompts you for the new password or an
ESCape.
If you enter a new password, ACNT changes your current
password to the new one.
If you press the ESCape key, ACNT leaves
your current password unchanged. The prompt also shows the maximum
character length allowed for a password.
If you do not enter your current password or enter it incorrectly,
ACNT issues an error message and exits. You must run the ACNT program
again to change your password.
After ACNT changes the password or you press the
displays the message OPERATION COMPLETE and exits.

ESCape

key,

ACNT

See the RSX-llM/M-PLUS System Management Guide for more information on
ACNT and its privileged options.

2-24

SYSTEM CONVENTIONS
Examples:
>RUN ACNT
* ACCOUNT FILE MAINTENANCE PROGRAM
Password { <=6 chars. ) :
ANGEL
Type <ESC> to leave entry unchanged
Password ( <=6 chars. ) :
(§9)
OPERATION COMPLETE

>RUN ACNT
* ACCOUNT FILE MAINTENANCE PROGRAM
Password ( <=6 chars. ) :
ANGEL
Type <ESC> to leave entry unchanged
Password ( <=6 chars. ) :
DEVIL
OPERATION COMPLETE

>RUN ACNT
* ACCOUNT FILE MAINTENANCE PROGRAM *
Password { <=6 chars. ) :
ANGEL
Type <ESC> to leave entry unchanged
Password ( <=6 chars. ) :
TOOLONG
ACNT -- Syntax or command input error
OPERATION COMPLETE
>RUN ACNT
* ACCOUNT FILE MAINTENANCE PROGRAM
Password { <=6 chars. ) :
JANGEL
ACNT -- Cannot find account
OPERATION COMPLETE

2-25

CHAPTER 3
MCR COMMANDS

This chapter describes all of the MCR commands.
The commands are
a1phabetical order regardless of function or privilege status.
The descriptions of the commands and messages given
observe the following notational conventions:

this

chapter

•

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

•

Square brackets ([]) indicate optional entries in a command
line or file specification.
Note that when an option is
entered, the brackets are not included.
Square brackets are also a part of the User
File Directory
(UFD)
and User
Identification Code
(UIC)
syntax ([group,
member]). When you use a UFD or UIC (in a file specification,
for example), brackets are required syntax elements;
that is,
they do not indicate optional entries.

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

(The value 255.

is base 10;

the

value

The following subheadings appear in the detailed command descriptions
that follow.
Subheadings that do not apply to a particular command
are simply omitted from the command description.

3-1

MCR COMMANDS
COMMAND NAME
This heading identifies the command name in capital letters.
The
minimal MCR command abbreviation is shown on the upper right or left
margin. The text following this subheading describes the command's
function.
A (NP)
following the command name indicates that the
command is nonprivileged. A (P) following the command name indicates
that the command is privileged. A (NP,P) indicates a nonprivileged
command with privileged optionse
A (P,NP)
indicates a privileged
commanct with nonprivileged options.
Format
This subheading is followed by the command format and a description of
all parameters.
Command-Related Error Messages
Error messages specific to the command appear under this subheading.
The command may also produce the common error messages listed in
Appendix A. These common error messages are not listed with the
individual commands.

3-2

MCR COMMANDS

ABO
ABORT (NP,P)
The ABORT command terminates execution of
a
specified
task.
Nonprivileged users can abort nonprivileged tasks requested from the
issuing terminal on systems with multiuser protection
or
any
nonprivileged
task
on
systems
without
multiuser protection.
Nonprivileged users can also abort privileged tasks requested from the
issuing terminal if the tasks have requested an exit AST service
routine with the SREX$ form of the SPECIFY REQUESTED EXIT AST
Executive directive. Privileged users can abort any task.
When a task that has specified an exit AST service routine is aborted,
it
enters
the
routine instead of being aborted immediately.
Privileged tasks enter the specified AST routine each time a valid
abort request is issued.
However, future exit ASTs are not queued
until the first exit AST has been effected. Nonprivileged tasks enter
the specified AST routine only once. After that, any valid attempt to
abort the task succeeds.
See the RSX-llM/M-PLUS Executive Reference Manual for more information
on the SPECIFY REQUESTED EXIT AST directive. Note that the issuing
terminal receives no indication that the task being aborted was
actually aborted or that it received the abort AST instead.
Aborting a task forces an orderly termination of the
To effect the termination, the system:

specified

task.

•

Performs I/O rundown. Cancels I/O for all non-file-structured
devices.
Allows I/O for file-structured devices to complete
and then deaccesses the files. Detaches all attached devices.
(I/O rundown may take a considerable amount of time for tasks
connected to a network node.)

•

Requests the Task Termination Notification program (TKTN) to
display a message on the aborted task's issuing terminal
giving the reason for the termination.
(If the /PMD keyword
is specified and the task is not checkpointed, the task's
registers are also displayed.)

•

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

•

If the system supports the ALTER PRIORITY directive (a system
generation option), alters the task's running priority to 247
(unless the exit AST service routine has been specified).
A
task must be memory-resident to be aborted; this change in
running priority usually causes a quick return
for
a
checkpointed task.

If the command includes the optional keyword /PMD, it forces the
system to produce a postmortem dump of the aborted task. The dump is
generated even if the task was not built with the Task Builder /PM
switch or installed with the INSTALL /PMD=YES keyword.
Format:
ABO[RTl taskname[/PMD] (/TERM=TTnn:]

3-3

MCR COMMANDS

ABO (Cont.)
taskname
The name of the task to be aborted.
If you omit the taskname,
the command attempts to abort task TTnn.
(The variable nn is the
octal unit number of the issuing terminal.)
Likewise, if you specify only the first three characters
taskname, ABORT defaults the taskname to tskTnn.

the

/PMD
A keyword that requests a Postmortem Dump of the aborted task.

Examples:
>ABO MAC
Task "MACT3 " terminated
Aborted via directive or CLI
MCR (the command line interpreter for these examples)
aborted
a
task called MACT3,
even though the command, issued from
TT~:, specified only the 3-letter task name.
On RSX-llM and RSX-llM-PLUS systems, the command >ABO MACT3,
issued
from any privileged terminal,
would have the same
effect.
;Qn ,RSXrllM-PL(JS $Y:S~~ms, ... ~h.e. c9~and • ?AB.a . . MA(! /TE:~M='rT3:,
iss.ued' 'fr'dm a?!C)~h~r (p~iyil:.eg~d) ~.~r~inal 1 wo'uld have the same
.~•~l:~¢t; ..

'>ABO
Task "TT7
" terminated
Aborted via directive or CLI
MCR aborted the task, TT7, from TT7:;
the task name does
have to be specified to abort task TTn.

not

Command Error Messages:

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

TASK MARKED FOR ABORT
A previous request has already been made to abort
specified
task,
but the abort has not yet occurred.

the
The

task marked for abort is probably not currently resident

memory or
it has outstanding
I/O
(for
tape-positioning operation must complete).

3-4

example, an MM:

MCR COMMANDS

ABO (Cont.)
ABO -- TASK NOT ACTIVE
The specified task is not currently active.
Messages from Task Termination Notification program (TKTN):
TKTN displays information about task aborts,
ABORT command or by some other means.
format:

whether
ml... -

J.UI::

..:i :

caused
-

- • •

Ul..::SlJJ.CIY

1... -

UCl.::S

by
the

TASK "taskname" TERMINATED
abort cause
Following the displayed cause for the abort is a
list of the
task's
registers at the time of the abort (if the task was not
checkpointed).
The possible causes of an abort are described
in
the following messages:
ABORTED VIA DIRECTIVE OR CLI
Either an Executive directive or a
CLI command
another task caused the task to be aborted.

issued

ABORTED VIA CLI
POSTMORTEM DUMP WILL BE GENERATED
A CLI command aborted the task and
Dump.

requested

Postmortem

11/40 F.P. EXCEPTION
The task encountered a
floating
point exception while
executing on a PDP-11/40 and no SST routine was specified to
process the trap.
AST ABORT. BAD STACK
An AST could not be effected because the
could not be pushed onto the task's stack.

AST

parameters

CHECKPOINT FAILURE. READ ERROR
The task could not be read
checkpo inted. ·

back

into

memory

after

being

IOT EXECUTION
The task executed an IOT instruction and no SST routine
specified to process the trap.
LOAD FAILURE. READ ERROR
The task could not be loaded because of a hardware error.

3-5

was

MCR COMMANDS

ABO (Cont.)
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) or, in the case of a privileged task switching
to system state, 376(8), and no SST routine was specified to
process the trap.
ODD ADDRESS OR OTHER TRAP FOUR
The task executed a word instruction with an odd address or
referenced a nonexistent memory location in an unmapped
syste~, and no SST routine
was specified to process the
trap.
PARITY ERROR
A parity error occurred while the task was executing.
The
task was fixed in memory so that the memory could not be
reused by another task.

BtJS RUNS A.RE OFFLINE OR NOT PRESENT
(:RSX-l1M-PLU~

multiprocessor system:s pnly.) The t:ask,

ce>nunop ·. tijat i t is ~apped \tp, was ~nstalled with an a'ffinity
a~1cm,:or····:aF~bus· ·r:un:·that.,·is · o·ff lln.e.

RESERVED INST EXECUTION
The task executed an illegal instruction and no SST
was specified to process the trap.

routine

SST ABORT. BAD CSM PARAMETERS
(B..~x;_·1114°-!PLUS systems O'.nly .. ) . '!'he ·tas~· execut~d ·a··.· cs~. (Ca l1
;inf,l~,ruqt,.ion w~~tr•···~l1Yel:J.,i.d ;p~famet~rs.

to. superJJ't.sgr. 14'od,e:l
SST ABORT. BAD STACK

An SST could not be effected because the SST parameters
could not be pushed onto the task's stack, or a stack
overflow was detected in an unmapped system, as indicated by
a nonzero value in the header guard word.
TASK EXIT WITH OUTSTANDING I/O
The task exited with one or more outstanding I/O requests.
Tasks should terminate all I/O operations before exiting.
The system does, however, process all outstanding I/O.

3-6

MCR COMMANDS

ABO (Cont.)
TASK INSTALLED IN MORE THAN ONE SYSTEM
The task image file has been installed
in more than one
system.
When a
task is installed,
pointers to various
system data structures are stored in the task header in the
task
image file.
If a task is installed in more than one
system, the header contains pointers for the last system in
which the task was installed. When the task is loaded for
execution, the loader verifies that the header contains
valid pointers for the current system. When a task has been
installed in more than one system, the loader check fail~
and the task is aborted.
T-BIT TRAP OR BPT EXECUTION
The task either set the T-bit in the Processor Status Word
or executed a Breakpoint Trap instruction,
and no SST
routine was specified to process the trap.

TRAP EXECUTION
The task executed a TRAP instruction and no SST routine
specified to process the trap.

3-7

was

MCR COMMANDS

ACS
ALLOCATE CHECKPOINT SPACE (P)
The ALLOCATE CHECKPOINT SPACE (ACS) command allocates or discontinues
a checkpoint file on disk for systems that support the dynamic
allocation of checkpoint space.
The disk containing the checkpoint
file must be in Files-11 format.
Only one checkpoint file per disk is
allowed, but numerous disks can each contain a checkpoint file.
In
general,
sufficient checkpoint space is twice the total amount of
memory that all of the running tasks will use.
When the system needs checkpoint space,
it searches the checkpoint
files
in the order in which they were created.
If space is not
available in the first file created (the primary file),
it searches
for space in the second file created (the secondary file), and so on.
An ACS command that discontinues a checkpoint file may not take effect
immediately.
If the specified file contains one or more checkpointed
tasks, the tasks must be returned to memory before the system can
discontinue the file.
However, once the request to discontinue the
file has been made, the system does not use the file for any more
checkpointed tasks.
Format:
ACS ddnn:/BLKS=n
ddnn:
A device unit that contains a mounted Files-11 disk.
number (nn) is not specified, it defaults to O.

If the unit

/BLKS
/BLKS=n.
A keyword that specifies the number (n)
of blocks on
the disk to be allocated for the checkpoint file.
(A block is
512 decimal bytes.) For example, the command
>ACS DB:/BLKS=250.
allocates 250(10) blocks for a checkpoint file on DB:.
When n is O, the system discontinues the use of the checkpoint
file;
the file is neither deleted nor truncated.
However, the
use of the file is discontinued only after all of the tasks that
are
checkpointed
to
it can be brought into memory and
checkpointed elsewhere.
For example, the command
>ACS DB:/BLKS=O
discontinues the checkpoint file on disk DBO:.
This does not
mean that the space allocated to the checkpoint file is freed.
The system checkpoint file
[O,O]CORIMG.SYS retains the space
initially allocated by the ACS command so that the space will be
available the next time it is needed.
If you want to free the

3-8

MCR COMMANDS

ACS (Cont.)
space allocated to the system checkpoint file after its
been discontinued, use the following commands:

use

has

>ACS ddnn:/BLKS=O
ACS -- CHECKPOINT FILE NOW INACTIVE
>PIP [O,O]CORIMG.SYS/TR
You must set the block size of the checkpoint file to 0 to
discontinue it before you can truncate it. Do not issue the PIP
command line until the "Checkpoint file now inactive" message has
been displayed.
PIP cannot determine if the checkpoint file is
still in use, so issuing the command line could cause volume
corruption and/or a system crash.
Examples:
>ACS DS:/BLKS=250.
>ACS DB:/BLKS=l024.
Allocates a primary checkpoint file on DS: and a secondary
checkpoint file on DB:. The primary file is 250(10) blocks
long and the secondary file ~s 1024(10) blocks long.
When
the system searches for checkpoint space, it will first look
in the file on DS: and then in the file on DB:.
>ACS DS:/BLKS=O
Discontinues use of the checkpoint fiie on DS:.
Command Error Messages:
ACS

CHECKPOINT FILE ALREADY IN USE ON DEVICE
A previous ACS command established a checkpoint file on the
volume mounted on the specified device unit. A volume can
contain only one checkpoint file.

ACS -- CHECKPOINT FILE NOW INACTIVE
This message appears after you issue an ACS command to
discontinue a checkpoint file and the file does not contain
any checkpointed tasks. The message indicates that use of
the file was discontinued immediately after the command was
issued. If the file is still in use, TKTN will issue a
message when the file is finally discontinued.

The ACS conunand was Issued on an RSX-ilM system that did not
include support of d'ynamic allocation of. checkpoint space at
s;ystem generation.
(All RSX'.""'llM-PLUS systems include this
feature.)

3-9

MCR COMMANDS

ACS (Cont.)
~cs

-- FILE I/O ERROR nnn.
The ACS command detected an error when it tried to allocate
or open the checkpoint file.
The code nnn.
is an FCS error
code that defines the cause of the error.
See
the
IAS/RSX-11 I/O Operations Reference Manual.
(If the code is
-24, the message may indicate that the disk, usually a
fixed-head disk,
does not have enough contiguous space to
allocate the file.
The normal implication of the code -24
is "device full".)

ACS

FILE NOT IN USE
A checkpoint file was not in use on the device specified
the ACS command.

ACS -- NOT FILES-11 DEVICE
The command specified a device
Files-11 disk.
The specified
mounted Files-11 disk.

*** ddnn:

that did not contain a
device unit must contain a

-- CHECKPOINT FILE NOW INACTIVE

The message, issued by TKTN, indicates that a
request to
discontinue use of a checkpoint file on device ddnn:
has
finally been satisfied.
The need
to
return checkpointed
tasks from the discontinued file back into memory caused the
delay between the request and this message.

*** tsknam CHECKPOINT SPACE ALLOCATION FAILURE
The task could not be checkpointed because there was not
enough room in the system checkpoint file and checkpoint
space was not allocated in the task image file.
Either make
the system checkpoint file bigger or create a second one.
Note that tasks built with the /AL switch are checkpointed
to their task
image file if the system checkpoint file is
full.

3-10

MCR COMMANDS

ACT
ACTIVE (NP)
The ACTIVE command displays at the entering terminal the names of all
active tasks that have that terminal as their TI:.
On RSX-llM-PLUS
systems, the display includes the octal unit number of the terminal
that initiated each task.
When the ACTIVE command is issued with /ALL (ACT /ALL), the
all active tasks in the system are displayed.

names

The ACTIVE command can also be issued with /TERM (ACT /TERM=TTnn:)
display the names of all the active tasks for a specific terminal.

Format:
ACT[IVE]

[/keyword]

/keyword:
/ALL
/TERM=TTnn:
Examples:
RSX-llM systems
>ACT
MCR •••
• • • MCR
>ACT /ALL
RMDEMO
MCR •••
• • • MCR
FllACP
••• PIP
>ACT /TERM=TT7:
••• PIP

>
RSX-llM-PLUS systems
>ACT
MCR •••
ACTT17

( TTl 7:)
(TTl 7:)

>ACT /ALL
LDR...
(COO:)
RMDEMO
(TT62:)
MCR...
(TT17:)
FllACP
(COO:)
DSOOFl
(COO:)
DSOlFl
(COO:)
LSTACP
(COO:)
DB03Fl
(COO:)
AT.Vn
(VT6:)
QMG...
(COO:)
HRC •••
(COO:)
PIPTAl
(TTlOl:)

>ACT /TERM=TT107:
LBRTA 7
(TTl 07:)

>
3-11

MCR COMMANDS

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

devices,

other

users'

private

devices

The system automatically deallocates your private devices when you log
out (issue the BYE command)~
You can also allocate a device to a specific terminal rather than
TI:. This allows you to allocate a device to a virtual terminal.

Format:
ALL[OCATEl dd[nn:]

[=llnn:]

[/keyword]

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

NOW ALLOCATED

llnn:
The optional name of a logical device, which the system creates
and assigns to the physical device being allocated.
(This is a
local assignment as created by the ASSIGN command.) Specifying a
logical device name is helpful when using the /TYPE keyword in an
indirect command file.
/keyword
One of the following:
/TERM=TTnn:
Specifies the terminal number (TTnn:) to which the
is to be allocated.

device

/TYPE=dev
Specifies the type of device wanted when doing a generic
allocation.
Instead of allocating a specific device, the
command allocates the first available device of the
specified type.
dev is the physical name of the device
(for example, RP06, RK07).

3-12

MCR COMMANDS

ALL (Cont.)
On RSX-llM,
devices:

this

keyword

RA60
RA80/8l

RK06
RK07
RLOl
RL02
RP02

RP03
RP05
RP06
RP07
RM03

RM05
RM80
RS03
RS04
RX50

specified

RC25
RCF25
RDSl

valid

for

following

the

Examples:
>ALL DK2:
Allocates disk DK2:.
>ALL DK:
Allocates disk DKO:.
>ALL DKl:/TERM=VTl:
Allocates disk DKl:
VTl:.

the

virtual

terminal,

>ALL DK=XXO:
ALL -- DK3:
NOW ALLOCATED
Allocates the first available logical unit of DK
(in this
case, disk DK3:,
since units 0, 1, and 2 were allocated
previously or are public devices) and assigns it the logical
name XXO:.
>ALL DB/TYPE=RP06
Allocates any available RP06 disk.
Command Error Messages:
ALL -- DEVICE ALLOCATED TO OTHER USER
The specified device has already been allocated
user.

1. The formatter name
TU45/TU77/TU78/TE16.

appears

only

3-13

the

drive

another

not

April 1983

MCR COMMANDS

ALL (Cont.)
ALL -- DEVICE ATTACHED
The specified device cannot
attached to a running task.
ALL -- DEVICE dd:

allocated

because

NOT IN SYSTEM

The specified device driver does not exist in the system, or
the data base for the device driver is not in the system or
in the driver's task image.
ALL -- INVALID KEYWORD
The specified keyword
command.

cannot

used

with

the

ALLOCATE

device.

Pseudo

devices

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

device.

Public

ALL -- PSEUDO DEVICE ERROR
The specified device is a
cannot be allocated.

pseudo

ALL -- PUBLIC DEVICE

ALL -- USER LOGGED ON TERMINAL
The command attempted to allocate a terminal that has been
logged-in by another user. Logged-in terminals cannot be
allocated.

3-14

MCR COMMANDS

ALT
ALTER (P)
The ALTER command
installed task.

changes

the

static

running

priority

Format:
ALT[ER]

taskname /keyword(s)

taskname
The name of the task whose priority is to be altered.
/keyword(s)
One or more of the following:
/PRI=n
Changes the task's static priority, and,
if the system
supports the ALTER PRIORITY directive, the task's running
priority.
(All RSX-llM-PLUS systems support the directive.)
/RPRI=n
Changes the task's running priority only
(valid only
systems that support the ALTER PRIORITY directive).

The priority is in the range 1 to 250(10).
The system assumes that
the priority you specify is octal unless you include a period (.).
Examples:
RSX-llM systems
>ALT TEST /PRI=~O.
Alters the static and
60(10).

running

priority

task

TEST

>ALT CMFRUN /RPRI=70.
Alters the running priority of task CMFRUN to 70(10).
RSX-llM-PLUS systems
>ALT ABC/PRI=lOO./TERM=TT~:
Alters the static and running
100 (10).

3-15

priority

task

ABCT6

MCR COMMANDS

ASN
ASSIGN (NP,P)
The ASSIGN command defines, deletes,
or displays logical device
assignments.
Logical device assignments associate logical names with
physical devices, pseudo devices, or other logical devices. When you
assign a
logical name to a
pseudo or logical device, the system
resolves the assignment to the associated physical device.
There are
three types of logical device assignment:
global, local, and login.
•

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

•

Local assignments apply only to tasks
initiated from the
terminal
used
to make the assignments.
Any terminal can
define or delete its own set of local assignments.

•

Login assignments occur only in RSX-llM systems that support
multiuser protection and all RSX-llM-PLUS systems. When a
user issues a HELLO command to log into the system, the system
automatically assigns the logical name SY: to the user's
system device, which is the device that contains the user's
files.
The login assignments apply only to tasks initiated
from the terminal while the current user is logged
in.
Only
privileged users can define or delete login assignments.

The system uses local assignments before it uses login and global
assignments,
and login assignments before global assignments.
If you
make a local assignment using a logical device name that is already
used
in a
login assignment,
the system uses the local assignment.
When you delete the local assignment (using ASN=),
the system goes
back to using the login assignment.
A logical-device name has the same syntax as a real device unit;
it
consists of a 2-character ASCII name (alphabetic) and an optional 1or
2-digit octal
unit number,
followed
by a
colon (:).
The
2-character name can either be equivalent to a standard RSX-llM/M-PLUS
device name (for example, DK:) or it can be two letters picked at
random (for example, ZZ:).
When you install a
task or the system processes an ASSIGN LUN
directive,
the system scans the logical device table before the
physical device table when searching for a
specified device.
As a
result,
a
user can define logical device names that are identical to
physical device names even though
the logical
and physical device
names do not refer to the same physical device.
The system resolves a
specified device name to
the first matching table entry found.
Therefore,
if a logical device name is identical to a physical device
name, the logical name has precedence.
The following legend explains the terms used in the descriptions
the various ASN formats for nonprivileged and privileged users.

3-16

MCR COMMANDS

ASN (Cont.)
pp
The physical, logical, or pseudo device name.
nn
The unit number.
11

The logical device name.
tt
The terminal device name.
Nonprivileged formats:
ASN ppnn:=llnn:
Assigns the logical name llnn: to device ppnn:.
The command
establishes a local assignment for the issuing terminal.
A.SN
Displays all local and login logical-device assignments
the issuing terminal.

for

ASN = [ 11 nn : ]
Deletes the local assignment of the specified logical-device
name;
or deletes all local logical-device assignments for
the issuing terminal if the command omits llnn:.
Privileged formats:
ASN ppnn:=llnn:/GBL
Defines a global assignment that associates the logical name
llnn: with device ppnn:.
ASN /GBL
Displays all global, local, and login
terminals in the system.

assignments

for

all

ASN =(llnn:J/GBL
Deletes the specified global logical-device assignment;
or
deletes all global assignments if the command omits llnn:.
ASN ppnn:=llnn:/LOGIN(/TERM=ttnn:]
for
a
Establishes a
login logical-device
assignment
if the
specified terminal or for
the
issuing terminal
command omits /TERM=ttnn:.
ASN /TERM=ttnn:
Displays all local and login logical-device assignments
the specified terminal.

3-17

for

MCR COMMANDS

ASN (Cont.)
ASN =llnn:/LOGIN[/TERM=ttnn:]
Deletes the login logical-device assignment indicated by the
name llnn:
for
a specified terminal or for the issuing
terminal if the command omits /TERM=ttnn:.
ASN =/LOGIN(/TERM=ttnn:]
Deletes all
login logical-device assignments
for
the
specified terminal or for
the
issuing terminal
if the
command omits /TERM=ttnn:.
ASN =(llnn:]/TERM=ttnn:
Deletes the local logical-device assignment indicated by the
name llnn:
for
the specified terminal;
or deletes all
local logical-device assignments for the specified terminal
if the command omits llnn:.
Example:
>ASN
>ASN
>ASN
>ASN
>ASN
US2:
USl:
SY:
>ASN
US?.:
USl:
SY:
GBO:
>ASN
US?.:
>ASN
>ASN
>ASN
>ASN
>ASN
ZZO:
XYO:

DP:=SY:
DP:=USl:
DT:=US2:
DK:=GBO:/GBL
DTO:
DPO:
DPO:
/GBL
DTO:
DPO:
DPO:
DKO:
=US/.:

LOCAL TI LOCAL TI LOGIN TI LOCAL TI LOCAL TI LOGIN TI GLOBAL

!Define SY:
!Define USl:
!Define US2:
!Define global logical device name GBO:
!List local and login assignments
TTO:
TTO:
TTO:
!List all assignments
TTO:
TTO:
TTO:
!Eliminate local logical device name

!Eliminate all global assignments
!Eliminate local logical device name
USl:
DK:=XY:
!Assign XY: to DK:
XY:=ZZ:
!Assign ZZ: to XY:
!Display assignments
DKO:
LOCAL TI-TTO:
DKO:
LOCAL TI-TTO:

=/GBL
=USl:

Command Error Messages:
ASN -- DEVICE NOT TERMINAL
The /TERM keyword used in the ASN command did not specify
terminal.

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

3-18

MCR COMMANDS

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

Task name

•

Task control block physical address (octalj

•

Partition name

•

Partition control block physical address (octal)

•

Partition base and limit physical addresses (octal)

•

Task's running priority and default priority

•

Task status flags

•

TI: terminal physical device-unit

•

Nonbuffered and buffered I/O counts (decimal)

•

Task local event flags

•

Task registers
tasks only)

and

Processor

Status

Word

(memory-resident

I
The displayed task status flags are from the Task Control Block
(TCB)
or the Partition Control Block (PCB). The ATL command displays the
name of the bit if the bit is set to 1 at the time of the display.
Bits set to 0 are not displayed. Flag names are three characters long
and correspond to the last three characters of the mnemonic defining
the status bits.
For example, AST represents the bit T2.AST and
indicates that the task is processing an Asynchronous System Trap.
Names prefixed by a minus sign {-) indicate that the bit represents
the complement of the condition. For example, -CHK indicates that the
task is not checkpointable.
If the task is not in memory (the OUT flag is displayed}, the contents
of the PC (program counter) , the PSW (Processor Status Word) , and the
registers are not displayed.

3-19

April 1983

MCR COMMANDS

ATL (Cont.)
The following list gives the flag names and
each one.
Status
ABO
ACP
AST
BLK
CAF
CAL
-CHK
CIP
CKD
CKP
CKR
CLI
CMD
DSP
DST
-EXE
FXD
GFL
HLD
HLT
LDD
MCR
MPC
MSG
MUT
NET
NRP
NSD
-PMD
OUT
PRO
PRV
PRVD
RDN
REM
REX
ROV
RST

RUN
SEF
SIO

SLV
SNC
SPN

brief

explanation

Description
Task is being aborted.
Task is an Ancillary Control Processor (ACP) •
Task is processing an AST.
Task is blocked by a CLI command.
Task cannot be checkpointed due to checkpoint space
allocation failure.
Checkpoint space is allocated in task image.
Task is not checkpointable.
Task
is
blocked
for
checkpoint
in
progress
(RSX-llM-PLUS) •
Task has checkpointing disabled (RSX-llM).
Task is checkpointed
(RSX-llM)
or
blocked
for
checkpoint in progress (RSX-llM-PLUS) •
Task checkpoint request pending.
Task is a CLI task.
Task is executing a CLI command (RSX-llM-PLUS) •
Task was built
with
separate
Iand
D-space
(RSX-llM-PLUS) •
Task ASTs are disabled.
Task is not in execution.
Task is fixed in memory (RSX-llM) or partition is fixed
in memory (RSX-llM-PLUS).
Task has its group global event flags locked.
Task is half-loaded (RSX-llM).
Task is being halted.
Task's load device has been dismounted (RSX-llM-PLUS).
Task was activated by MCR.
Task
has
mapping
change
and
outstanding
I/O
(RSX-llM-PLUS) •
Task aborted, waiting for TKTN message.
Task is a multiuser task (RSX-llM-PLUS).
Network protocol.
Task is mapped to nonresident partition (RSX-llM).
Task cannot receive data (no send data allowed).
Suppress Postmortem Dump on SST abort.
Task is out of memory (RSX-llM) or partition is out of
memory (RSX-llM-PLUS).
Task has prototype TCB (RSX-llM-PLUS) .
Task is privileged.
Task was privileged but has been set nonprivileged
(RSX-llM-PLUS) ..
Task I/0 is being run down=
Task is to be removed on exit.
Task has abort AST effected or in progress.
Task has resident overlays.
Task is restricted (used by layered software).
Task is executing on another processor
(RSX-llM-PLOS
multiprocessing systems only).
Task is stopped for an event flag(s).
Task is waiting for terminal I/O (RSX-llM-PLUS).
Task is slaved.
Task uses commons for synchronization (RSX-llM-PLUS).
Task is being suspended.

3-20

MCR COMMANDS

ATL (Cont.)
SPNA
STP
STPA
WFR
WFRA
XHR

Task was suspended prior to AST.
Task is stopped for terminal input.
Task was stopped prior to AST.
Task is in a "wait-for" state.
Task was in a "wait-for" state prior to AST.
Task has an external header (RSX-llM-PLUS).

Format:
ATL [taskname]
Example:
>ATL
LDR ••• 112050 LDRPAR 112404 00253100-00255~00 PR! - 248. DPRI - 248.
STATUS: -CHK FXD STP -PMD PRV NSD
TI - COO:
roe - o. BIO - o. EFLG - 000001 000000 PS - 170000
PC - 120354 REGS 0-6 120212 010364 177777 107646 074714 10"7614 120166
RMDEMO 053550 GEN
046020 01036700-01065600 PR! - 225. DPRI - 225.
STATUS: -CHK WFR -PMD PRV MCR
TI - TTO:
IOC - O. BIO - O.
EFLG - 000021 040000 PS - 170010
PC - 125234 REGS 0-6 000000 136257 132066 000000 136321 134560 121166
FllACP 111550 GEN
067150 01164600-01230~00 PR! - 149. DPRI - 149.
STATUS: STP ACP -PMD PRV NSD CAL
TI - COO:
roe - o. BIO - o. EFLG - 000002 000001 PS - 170000
PC - 135244 REGS 0-6 000010 000066 000016 000000 067420 111550 120244
MCR ••. 110160 SYSPAR 114514 00202600-00212600 PR! - 160. DPRI - 160.
STATUS: STP -PMD PRV MCR CLI NSD CAL
TI - TT51:
IOC - O. BIO - O.
EFLG - 000001 040000 PS - 170000
PC - 122436 REGS 0-6 000000 120476 122032 120432 010554 043552 120366

3-21

MCR COMMANDS

BLK
BLOCK (NP,P)
The BLOCK command blocks an installed task.
It declares to the system
that the specified task is not eligible to execute or to compete for
memory.
On multiuser protection systems, nonprivileged users can only
block active tasks requested from the issuing terminal.
Privileged
users can block any task.
On systems without multiuser protection,
any user can block any task.
However, the following tasks cannot be blocked: ACP tasks, CLI tasks,
tasks being aborted, and tasks that are exiting.
Blocking a task sets the block bit in the Task Control Block
(TCB).
When a task's block bit is set, the task is ineligible to compete for
system resources.
To clear the block bit,
issue the MCR UNBLOCK
command or,
if the task is active, abort the task.
(Unblocking or
aborting a task are the only ways to cancel the BLOCK command.)
A blocked task has an effective priority of 0.
If the task is
checkpointable,
any task can checkpoint it.
Once checkpointed, the
blocked task is ineligible for memory contention.
A blocked task that
is then aborted is automatically unblocked by the system.
If the task
had previously specified a requested exit AST, the task is unblocked
and the AST declared for it.
Format:
BLK (taskname] (/TERM=TTnn:]
taskname
If taskname is not
The name of the task to be blocked.
the command attempts to block the task requested from
specified,
the issuing terminal (task TTnn).
/'I'~.f(~=TTnn :.

A privileged RSX-llM-PLUS.keyword that specifies
initiated from the<specified terminal be blocked.

that

task

Examples:
>BLK TST
Blocks task TSTT3n, prohibiting it from further execution.
TT36:
is the terminal from which the task was initiated.
>BLK .MAS/TERM=TT23:.

3-22

MCR COMMANDS

BOO
BOOT (P)

The BOOT command bootstraps a system that exists as a task image file
on a Files-11 volume.
It provides a convenient means of terminating
one system and initiating another, especially on minimum hardware
configurations.
For example, BOOT can be used to terminate a
real-time system and initiate a program development system.
The BOOT command
operation.

immediately

terminates

the

system

currently

Bootable systems are special task image files that have
headers. Examples of such systems are RSX~llM and RSX-llS.

in
task

Format:
BOO[T]

[filespec]

filespec
The standard RSX-llM/M-PLUS file specification in the form:
dev:[ufd]filename.type;ver
This specifies the file from which a new system is to be loaded.
Defaults applied to the file specification are:
dev:

The system device LB:

[ufd]

The UIC under which BOOT is running

filename

RSXllM

type

SYS

version

The latest version

Note that BOOT is the only command
specification to omit the file name.
Table 3-1 lists all of the valid
RSX-llM-PLUS.

bootable

that

devices

allows
for

the

file

RSX-llM

and

Table 3-1
Valid Bootable Devices
RSX-llM
RLOl/02
RK05
RK06/07
RM02/03/05/80
RP07
RA60
RA80/81
RC25

RSX-llM-PLUS
RP02/03
RP04/05/06
RS03/04
RXOl/02
RXSO
RD51
DECtape
MLll

RLOl/02
RK05
RK06/07
RM02/03/05/80
RP07
RA60
RA80/81

3-23

RC25
RP02/03
RP04/05/06
RD51
RX50
MLll

I
April 1983

MCR COMMANDS

BOO (Cont.)

I
Restrictions:
For a virgin system boot, the boot device physical unit number
(unit plug)
must equal
the logical unit number in the virgin
system.
Otherwise, the initial SAVE command line will not work.
It is not possible to correctly boot
under the following circumstances:

large

virgin

Executive

When booting a mapped RSX-llM or
from an unmapped RSX-llM system

RSX-llM-PLUS

system

When booting a 22-bit RSX-llM
from an 18-bit RSX-llM system

RSX-llM-PLUS

system

Booting from an unmapped RSX-llM system: If the Executive being
booted has anything fixed
in memory above 27.SK words (for
example, drivers, tasks, or commons), it will not be read
into
memory, causing problems when you try to run the system.
This
happens because BOOT moves the bootstrap code in an unmapped
system to the top of memory less .SK (28K - .SK) and can only
read in the virgin system image up to this location
(27.SK).
Anything above 27.SK is not read in.
Booting from an 18-bit RSX-llM system: If the system image being
booted is larger than the running system, not all of the image
will be read into memory.
Again, BOOT only reads in the image up
to the beginning of the bootstrap code.
If the Executive has
anything fixed in memory above this location, BOOT will not read
it in and the new system will not run properly.
If the Executive Debugging Tool (XDT)
has been generated into the
system,
XDT displays the following when an RSX-llM/M-PLUS system is
booted for the first time:

XDT: baselevel
XDT>
where baselevel is the base level number for the system.
Typing the G key ~u response to the prompt returns control to
RSX-llM/M-PLUS and causes the system to come up normally.
After the
system has been saved, XDT does not reappear unless a user sets .a
breakpoint or issues the BRK command, or the system crashes.
(See the
RSX-llM or RSX-llM-PLUS Guide to Writing an
I/O Driver
for a
description of XDT.)

3-24

April 1983

MCR COMMANDS

BOO (Cont.)
Example:
>BOO TEST
Bootstraps from the system device the
the file TEST.SYS.

system

contained

Command Error Messages:
BOO -- DEVICE NOT IN SYSTEM
The booting system does not contain
needed for the device being booted.

the

data

structures

BOO -- DEVICE OFFLINE
An attempt was made to boot a file on an off-line device.
BOO

DPB ERROR
A bad Directive Parameter Block was created by BOOT.
This
error
indicates that the system itself has faulted.
If the
error persists, submit a Software Performance Report
(SPR)
to DIGITAL.

BOO -- FILE NOT CONTIGUOUS
An attempt was made to load a system from
file.
System images must be contiguous.

noncontiguous

BOO -- INVALID LOAD DEVICE
BOOT detected a
residence device.

device

that

was

invalid

system

the

system

BOOT did not consider the file to be a system image
probably because the file is formatted improperly.

file,

BOO -- LABEL BLOCK READ ERROR
An attempt was made to read the label block
image file, but the attempt failed.

BOO -- NOT A SYSTEM IMAGE

BOO -- NO TRANSFER ADDRESS
BOOT did not consider the file to be a system image file
because the specified transfer address in the label block
appears to be corrupted.

3-25

MCR COMMANDS

BRK
BREAKPOINT TO EXECUTIVE DEBUGGING TOOL (P)
The BRK command passes control to the Executive Debugging Tool (XDT)
if it has been generated into the system. If XDT is not in the
system, the command has no effect. See the RSX-llM or RSX-llM-PLUS
Guide to Writing an I/O Driver for a description of XDT. Note that,
if successful, the command halts all system activity; proceeding from
a breakpoint normally restores the system to the state that existed
when the BRK command was issued.
When XDT gains control, it prints the message
BE: nnnnnn
XDT>
on the console terminal to indicate that XDT now has control. All XDT
commands
are available for use in debugging the Executive or
user-written drivers. To return control to MCR, enter the P command;
MCR then prompts with a right-angle bracket (>).

Format:
BRK
Example:
>BRK
BE: 1245e10
XDT>P

3-26

MCR COMMANDS

BRO
BROADCAST (NP,P)
The BROADCAST command displays a specified
terminals, as follows:

message

one

•

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

•

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

message

You can also create an indirect command file to contain one or more
lines of input to
the command.
Each line specifies the target
terminal and the message ·to be broadcast.
(Privileged users can
broadcast a message simultaneously to all
terminals.) To use the
command file, enter after the command name the file specification
preceded by an at sign (@).
If the message cannot be broadcast within 20(10) seconds,
displays the following message at the issuing terminal:

the

system

BRO -- Message failed to reach TTnn:
If a privileged user specifies multiple terminals (ALL:
or LOG:), the
system returns one error message for each busy terminal.
If you have used SET /NOBROadcast so that you will not receive any
messages sent by the BRO command, the user sending the message will
receive an error message.
Formats:
BRO[ADCAST] TTnn: message
BRO[ADCAST] @filespec
BRO[ADCAST] ALL:message (Privileged format)
BRO[ADCAST] LOG:message (Privileged format)

NOTE
Each format can be entered on
two
successive lines by pressing the RETURN
key immediately after the command name;
this
invokes the direct task format.
For example:
>BRO[ADCAST] (8DJ
BRO>TTnn:message
To exit from
type CTRL/Z.

the

direct

3-27

task

format,

MCR COMMANDS

BRO (Cont.)
TTnn:
The terminal to receive the broadcast message.
message
The message to be broadcast. This is an ASCII character string
that cannot exceed the length of one line (80 characters). Note
that an exclamation mark (!) cannot be broadcast.
Usually, BRO uses uppercase letters when it displays the message.
When you use the direct task format, however, BRO displays the
message exactly as you typed it.
f ilespec

The specification of a file containing one or more message
in the format:

lines

TTnn: message
user-name message
or, for privileged users:
ALL:message
LOG:message
ALL:
Privileged option. Indicates that the message is to be sent to
all terminals connected to the system (this does not include
slaved terminals, virtual terminals, or terminals that have the
broadcast option disabled).
LOG:

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

user-name
... Tl1~.•tl~er 11am~·()f·. the· pe.r$.on .who is·.·< · to . ·•. . .•. recelve.••.•... t,he . . . ·b.roadcps~
me~sqge . · .(~SX--;llM--~LU!3 .. • sy~tems ·.· . . . w1 ~fi . ·. . R~.source·.· ~qQo.pnJ:Jng·. ·.·. o.nly) .•
····Yoq 9an speqtfy. uset.~r1am~ to qe .•. th.e·: last.·riame.·-0{ th~ u~~r . . fNAlVJEJ
··.or·.·.· the, · fi~st.·...•... il)l~.i.aJ< . . ~ryd •la?t l'li:lrne. .· (I •. NAME)·~' ... ·.Yol1 .~Ust·.·.t~se :.a.
blank OX tab .after: .•US.:~X~name• to· . sepa.rat;e. ·.it f;r()m the. 1tle$sage

· :tex:t .

wb~~. y1:it1. ~pt:qf.fi ·:µ·s.er~l'lkrr1~· fl~st na;me orilyJ; Bl~O :makes .... ?tn ·~xact.
mat:ch pet.we.en .the name you· e.Iltier •and a name in t.he acco·unt· file.:.
~:'.·

· .. ·."='_ ..._.:_:.· ... :.·.··

.-·:'-.::·.::.~··.· .....'·.:=: ':·

-.··.. ·.· ·. :;,··. ~= ··:_:,.=-","·,,;,;--·. '."::_·.:.-:"·> ··.·.'.";. ·..._,:-

;.,.. ;.

:ff•·····• f:h.e . ·.· ·. µ·~.er;· ·.····~~b~~·~~···.i·.l't~. thf:······.ttie·~~Fl·~··~··········r~ 1..•~~.9.e.4 .·. . i.n ·:tir9.m.•·. :ItlQ.i.¢•.··.·····tii.r1n•··•··•·.9~0·.
·t::e.rtniriali theL mes$age ·is ·. ·.serit. t::P ·all ·of them.,

•.

3-28

MCR COMMANDS

BRO (Cont.)
The BRO command displays the message in one of the following formats:

RSX-llM systems and RSX-llM-PLUS systems without Resource Accounting
dd:month:yr hh:mm
message

From node::TTnn:

to TTnn:

RSX-11M;...PLUS systems with Resource Accounting
dd:month:yr hh:m.rn
message

From node::user-name (ttnn:)

to TTnn:

dd:month:yr hh:mm

From node::user-name {ttnn:)

to user;_name

m~ssa,ge

The variable node is the name that was selected for your system during
system generation.
It is also your DECnet name if your system is on
the network.
Examples:

RSX-llM systems and RSX-llM-PLUS systems without Resource Accounting
>BRO TT51: PRIVILEGED TESTING.

PENDING CRASH.

displays
10-AUG-81 13:35
From QUASAR::TT52:
PRIVILEGED TESTING. PENDING CRASH.

to TT51:

>BRQ(fil_J)
BRO>TT~l:

More testing.

Crash likely.

displays
10-AUG-81 13:37
From QUASAR::TT52:
More testing. Crash likely.

to TT51:

>BRO LOG:System going down in 5 minutes for reboot.
displays
10-AUG-81 13:40
From QUASAR::TT52:
SYSTEM GOING DOWN IN 5 MINUTES FOR REBOOT.

·1.0~AU(;-Rl .· .·. ·13 :10 ··
THIS> IS' ANOTHER.

to TT51:

JONES

3-29

MCR COMMANDS

BRO (Cont.)
Note:
The BROADCAST command uses the write-breakthrough feature of the
terminal driver, a system generation option always generated with
an RSX-llM multiuser protection system and all RSX-llM-PLUS
systems.
If the system supports the feature, the broadcast
message, under most circumstances, reaches all target terminals.
If the system does not support the write-breakthrough feature,
the write defaults to a write logical block;
the message cannot
break through any type of I/O at the terminal.
Command Error Messages:

I
BRO -- COMMAND INPUT ERROR
The BROADCAST task did not receive the
(Usually an indirect command file could
Reenter the command line.

command line.
not be found.)

BRO -- COMMAND SYNTAX ERROR
The command line had an improper format.
BRO -- ILLEGAL DEVICE SPECIFIED
The specified device was not a terminal.
BRO -- MESSAGE FAILED TO REACH TTnn:
The message could not be displayed within 20(10) seconds
the terminal specified by TTnn~.
BRO

PRIVILEGED COMMAND
A nonprivileged user entered a privileged option of the
command,
that is, attempted to broadcast one message to all
connected or logged-in terminals.

BRO -- USER NOT RECEIVING MESSAGES

•

The terminal to
SET /NOBROadcast.

which

the

3-30

message

was

sent

has

been

April 1983

MCR COMMANDS

BYE
BYE (NP)
The BYE command logs you out of a multiuser protection system.
The
system writes a logout message on the console terminal (CO:), displays
a terminating message on the initiating terminal, aborts any active
nonprivileged and some privileged tasks that belong to you, dismounts
volumes mounted by you (an exception is when you are a privileged user
and you have mounted a public device -- mounted public volumes remain
mounted), and deallocates any private devices you had allocated
previously.
Upon logging out a terminal, BYE performs the following actions:
1.

Checks to see if the terminal's current command
line
interpreter (CLI) has requested a silent logout. If so, BYE
does not display any information and does not execute the
system logout command file.

If silent logout is not requested, BYE resets the default CLI
for the terminal to MCR, resets the terminal so that it can
receive
broadcast
messages,
and
executes
LB: [l,2]SYSLOGOUT.CMD, the system logout command file.

Informs the full-duplex terminal driver or DECnet that the
terminal is logging out. BYE issues a QIO directive that the
terminal driver uses to hang up remote lines or that DECnet
uses to break the connection.
This action can be controlled by the /[NO]HOLD keyword.
If
you specify /HOLD, BYE logs out the terminal but the line is
not hung up. If you specify /NOHOLD, BYE logs out the
terminal and the line is hung up.
(/NOHOLD is the default.)

The way in which BYE aborts (or does not abort) a task active on the
terminal being logged out depends on the task and its privilege
status.
All tasks with abort ASTs and all nonprivileged tasks that are active
at your terminal when you issue the BYE command are aborted. If a
nonprivileged task has requested an exit AST service routine by means
of a SPECIFY REQUESTED EXIT AST directive (SREA$ or SREX$), BYE allows
the task to enter this service routine. BYE requests each of these
tasks to exit (abort), causing the requested exit AST to be entered
for the task. For all of these nonprivileged tasks, BYE allows a
user-specified time interval during which the AST can be executed for
the task. At the end of the time interval, which is specified when
the BYE task is built (the default is O or not to wait at all), if the
task has not exited or if the AST service routine has not been
entered, BYE aborts the task normally (a second requested exit AST
cannot be declared for a nonprivileged task) and also aborts any other
nonprivileged tasks that are still active.

3-31

MCR COMMANDS

BYE (Cont.)
BYE aborts a privileged task that has requested an AST service routine
in the same way as a nonprivileged task. However, any privileged
tasks that have not exited by the end of the time interval are not
necessarily aborted.
The task itself must determine if it will be
aborted or not. Privileged tasks that did not request the AST service
routine remain active.
Format:
BYE [/(-][NO] HOLD]
Example:
>BYE
Have a Good Evening
13-May-81 18:47 TT13: is logged off QUASAR
Depending on the time of day, the system displays "Have a Good
Morni.ng," "Have a Good Afternoon," or "Have a Good Evening."
On ..·'R.sX:f1';M7rtu$''.sysEems . ~f1~t.•.· s\lpp()t tf·ci~v.·~Bcour\.tfngi,.•.··.· the . . '• .BYE' '" g9riuna.na>
provJa·e~·· additionµl.• ... information .••• (Pr?vided .•.·.that . .·. y()t:r· io.gged · .·.irr· .afte.i:- .cPu
ac:count:ing. ~as initiated}• The additional.·. informq.t:ion. consists o·f<tf1e
total· time logged in, the amount of CPU time used·, and the total
number of tQ.sks.

Example:
>BYE
Connect time: 172
MINS.
CPU time used: 63
SECS.
Task total:
48
Have a Good Afternoon
14-MAY:-81 17:23 TT: 30

Note that some ta·sk~, :inclu(!ing BYE,. ·s'pawfi or .·.request
These. other tcisks are al so i nc1 qde'd: · in the .t.ask total. ·Fqr ~.x.a.mple,
when Y.()l1 ip·SU~ aci RU~~d.~iqediat:ely C()n\,f1''c9,nd, the. CPU . ac:coul'lt. in~ .: sys.tern
r•eqords . •th~'~Er.·:t~~ks:.~· . •. •. •. . .• th~.·. . Mc~.···.· . . ~Ps.K·.:~,9.·e'}{epl,lte 1;h~.··•·.RU~.···.··qofil~¢l·r;l~:' :.\ItilS'~~LL
to•···.··ins;:t:all J::.b:~ t;?JS•k-, a•?)d ·t:he •. ·ac:tug'l e.:&,ecution: ofthe .task·.~
·

Command Error Message:
BYE

-- SYNTAX ERROR
A keyword other than a

form

/HOLD

(/HO[LD] ;/NOHO[LD] 1

/-HO[LD]) was specified in the command line.

3-32

MCR COMMANDS

CAN
CANCEL (NP,P)
The CANCEL command cancels time-based initiation requests for a
task.
These
requests
result
from a RUN$ directive or any of the
time-synchronized variations of the MCR RUN command and are placed
in
the clock queue.
(Note that you must be privileged to use these forms
of the RUN command~)
Only a privileged user can issue a CANCEL
initiated from the entering terminal.

command

for

task

not

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

all periodic rescheduling and time-based
requests for task XKE.

3-33

initiation

MCR COMMANDS

Driver common
Fixed in memory
Long I/O
Last load failed
Not shuffleable
Out of memory
Parity error
Position independent
Read-only common
Usually, the status bits will indicate
is either fixed 1n memory {FXD) or out

3-34

region

MCR COMMANDS

3-35

MCR COMMANDS

CLI
COMMAND LINE INTERPRETER (P,NP)
The CLI command sets up for use a command line interpreter other than
MCR,
such as DCL or a user-written CLI.
A CLI task receives
unsolicited input from a terminal and then attempts to interpret the
input as a command.
On RSX-llM, you can have up to 15 alternate CLis
running on your system at one time (the number is selected when the
system is generated).
On RSX-llM-PLUS, the number is always 16, which
includes MCR.
Before you use an alternate CLI,
it must be installed with
/CLI=YES option.
(See the description of the INSTALL command.)

the

All of the CLI command keywords and subkeywords can
three characters.

truncated

can

Formats:
CLI /keyword=cliname
CLI /INI[T]=cliname[/subkeyword(s)]
cliname
The name of the alternate
characters in length.

CLI.

This

name

Keywords:
/DISABLE=cliname
Disables the specified CLI.
The CLI cannot accept any
commands.
This effectively stops system use by terminals
set to this CLI until the CLI is enabled again.
The system
sends a message to the CLI informing it that it has been
disabled if the CLI was initialized with the /MESSAGE
subkeyword specified.
/ELIM~cliname

or /ELIM=*

Removes all of the data structures for the specified CLI or,
if the wildcard (*) is used, for all of the alternate CLis.
After this command is executed, the CLI task can be removed
(see the description of the REMOVE command).

Individual CLis can be eliminated only if no terminals are
set to them.
When you use the wildcard option, all CLis
except MCR are eliminated. Any terminals set to a non-MCR
CLI are disabled.
The terminals can be enabled again by
setting them to any valid CLI
{after
it
has
been
initialized)
or
to MCR
(which does not need to be
initialized). CLis that were initialized with the /MESSAGE
subkeyword receive a message from the system informing them
that they have been eliminated.
/ELIM=* is intended to be used during
procedure.

3-36

the

system

shutdown

MCR COMMANDS

CLI (Cont.)
/ENABLE=cliname
Enables a previously disabled CLI.
The CL! can now accept
commands.
If the CL! was initialized with the /MESSAGE
subkeyword specified, the system sends a message to the CL!
informing it that it is now enabled.
While a CL! is disabled, the terminal remains set to it.
To
set the terminal
to an enabled CLI, issue the SET /CL!
command from another terminal (privileged users only).
/INIT=cliname[/subkeyword(s)]
Initializes the data structures for
the specified CL! so
that terminals can be set to it.
The CLI task must have
been installed with the /CLI=YES option.
All CLis except
MCR must be initialized before they can be used.
If the /MESSAGE subkeyword is specified, the system sends a
message to the CLI,
informing the CL! that it has been
initialized.
Subkeywords:
/CPR=" string"
Specifies the CTRL/C prompt string.
The string
inside the quotation marks has the same syntax as
the MACR0-11
.ASCII directive
(see the PDP-11
MACR0-11 Language Reference Manual).
You must
supply characters such as RETURN (<15>)
and LINE
FEED
(<12>)
because
they are not supplied
automatically.
For example:
/CPR="<l5><12>/MCR>/"
sets up the string for MCR's CTRL/C prompt.
This
means that when you type a CTRL/C, the system
issues a RETURN/LINE FEED and
then displays the
prompt MCR>.
A null string (/CPR="") specifies that
wi 11 be issued.

prompt

If you want to use double quotation marks or
slashes
within
the
string,
use
different
characters as the
string
delimiters.
(The
delimiters can be any character that is not used
in the string.)
Default:
/CPR="<l5><12>/cli/" where
name of the CL!.

3-37

cli

the

MCR COMMANDS

CLI (Cont.)
/DISABLE
Initializes the CL! in disabled mode.
The system
rejects any commands issued from the terminal
until the CL! is enabled.
Default:

The CL! is enabled.

/DPR="string"
Specifies the default prompt to be issued when an
empty command line is entered. As with /CPR, the
string inside the double quotation marks has the
same syntax as the MACR0-11 .ASCII directive. You
must supply characters such as RETURN
(<15>)
and
LINE FEED
(<12>)
because they are not supplied
automatically.
A null string (/DPR="") specifies that
should be issued.

prompt

/DPR="<l5><12>/>/"

/LGO
Specifies that the CL! will accept commands from
unlogged-in terminals.
This allows the CL! to
execute the commands without the user having to
log in. An application can, for example, use the
terminal for data entry only and not allow it
access to the system.
The terminal
is under
complete control of the CL! task. You can only do
what the CL! allows.
It is up to the CL! to do any user validation or
security checks. Also, be careful when doing any
file I/O from tasks running on an unlogged-in
terminal because the UIC and privileges for the
terminal are undefined.
Default: Commands from unlogged-in terminals will
be rejected by the system and not passed to the
CL!.

3-38

MCR COMMANDS

CLI (Cont.)
/MESSAGE
Specifies that the CLI wants to receive messages
from the system.
The system messages inform the
CLI of events such as its being enabled or
disabled, or if a terminal is being set to the CLI
or if it is being dissociated from the CLI.
(See
the RSX-llM/M-PLUS System Management Guide for a
list of the messages and their format.)~~Default:
The CLI does not receive
the system.

messages

from

/NULL
Specifie~ that the CLI will accept
empty command
buffers resulting from a user pressing the RETURN
key as the first character in a command line.
No
prompt is issued.

Default:
The command is not passed to the CLI and
the default prompt is issued.
/PRIV
Specifies that a user must be privileged to set
the terminal to the CLI.
(See the description of
the SET command.)
Default: A nonprivileged user can set his or
own terminal to the CLI.

her

/PROMPT
Specifies that the CLI wants to receive prompt
requests if a task that was started in order to
execute a command exits.
Default:
The dispatcher issues a prompt
request is not passed to the CLI.

and

the

/QUIET
Specifies that the MCR commands HELLO and BYE do
silent logins and logouts, respectively.
(See the
descriptions of these commands.) The keyword also
suppresses messages from the dispatcher.

3-39

MCR COMMANDS

CLI (Cont.)
/RESTRICT
Specifies that only the CLI can
issue the SCLI$
directive to set a terminal to itself.
(See the
RSX-llM/M-PLUS Executive Reference Manual.)
Note that you cannot use /RESTRICT for
whose names are in the form ••• xxx.

CLI

tasks

/TASK=taskname
Specifies the name of the task that will act as
the CLI.
Use this keyword if the name of the task
is different from the name of the CLI.
/MESSAGE=cliname:"message-text"
Sends an ASCII message to the CLI
if it has the message
attribute set for it (by the /MESSAGE subkeyword).
If the
CLI does not have the attribute set, the command
issues an
error message.
/SHOW
(Nonprivileged keyword.) Displays information about each CLI
on the system.
The
information includes the name of the
CLI, the task that
implements the CLI,
the number of
terminals set to the CLI, several status bits for the CLI,
and whether the CLI is active.
The following list gives the meaning of the status bits:
ACT

CLI is active (always shown for MCR).

DSB

CLI is currently disabled.

PRV

CLI was initialized with the /PRIV

subkeyword.

You

must

(including TI:)
RST

privileged

set

terminal

to this CLI.

CLI was
initialized
with
the
/RESTRICT
subkeyword.
Only the CLI can set a terminal to
itself.

3-40

MCR COMMANDS

CLI (Cont.)
/UNOVR
Clears the override bit set for the terminal's CLI.
When
the
HELLO
command
enters
the
command
file
LB:(l,2]SYSLOGIN.CMD, the terminal is set to a specific CLI.
However,
an override bit is also set so that the command
file can execute from MCR.
Clearing the override bit
ensures that commands issued from the terminal will go to

the correct CLie
/UNOVR is only useful with SYSLOGIN.CMD, immediately
chaining to a user's LOGIN.CMD, or exiting.

before

Examples:
>CLI /SHOW
MCR
MCR •.•
DCL
••. DCL

ACT

~isplays

information about the CLis currently
the system.

installed

>CLI /INI=TCP/LGO/MES/TASK=PROMPT
Initializes the task PROMPT as a CLI.
The command line
specifies that the CLI will be called TCP, it will accept
commands from unlogged-in terminals,
and
it will
receive
messages from the system.
(Note that PROMPT must first be
installed with the /CLI=YES option before
it can
be
initialized as a CLI.)
Command Error Messages:
CLI -- CLI ALREADY EXISTS
You attempted to initialize a CLI that already exists in the
system.
CLI -- CLI DOES NOT ACCEPT MESSAGES
The CLI was not initialized with the /MESSAGE keyword,
so
its message attribute bit has not been set.
The CLI is
unable to receive any messages.
CLI -- CLI IN USE
You attempted to eliminate a CLI that
set to it.

still

has

terminals

because

another

CLI -- DEVICE ATTACHED
The CLI command cannot do a /SHOW
task has attached the terminal.

3-41

display

MCR COMMANDS

CLI (Cont.)
CLI -- FEATURE NOT SUPPORTED
The system does not support alternate CLis.
CLI -- ILLEGAL KEYWORD VALUE
You specified an
subkeyword.
CL!

invalid

string

with

the

/CPR

/DPR

A CL! cannot be initialized with /RESTRICT if
the CL! task is in the form ••• xxx.

the

name

ILLEGAL USE OF RESTRICT SWITCH

CL! -- INVALID KEYWORD
An incorrect keyword was specified in the command line.
CLI -- MAX NUMBER OF CLIS ALREADY PRESENT
You attempted to initialize another CLI,
but the maximum
number of CLis allowed in the system has already been
reached.
CLI -- NO POOL SPACE
Not enough space in pool is present
specified in the command line.

the

operation

CL! -- OUTPUT'ERROR
An I/O error occurred while output was
terminal.

being

sent

the

CL! -- PARTITION TOO SMALL TO BUFFER INFORMATION
The /SHOW subkeyword did not have enough space to buffer the
display information.
Try reinstalling the MCR task with a
larger increment,
using the
/INC
keyword
(see
the
description of the INSTALL command).
If the error persists,
submit a Software Performance Report (SPR).
CL! -- PRIVILEGED COMMAND
Nonprivileged users can only use the /SHOW keyword.
CL! -- SYNTAX ERROR
The command line was not entered correctly.
CL! -- TASK NOT A CL!
You attempted to
initialize a CL!
installed with the /CLI=YES keyword.

task

that

was

not

CL! -- TASK NOT IN SYSTEM
The specified
attempted to
system.

CL! task
eliminate

has not been installed or you
a CLI whose name is unknown to the

3-42

MCR COMMANDS

CLQ
CLOCK QUEUE (NP)
The CLOCK QUEUE
(CLQ)
command displays on the entering terminal
information about tasks currently in the clock queue.
The information
consists of the task names, the next time each task is to be run, and
each task's reschedule interval,
if one was specified. The system
places a task in the clock queue if the task was activated by the RUN
command,
which specified a time-based option, or by the RUN$
directive.
Format:
CLQ[UEUE]
Example:
>CLQ
TASKl Scheduled at 22-APR-81 10:24:30:00
TASK2 Scheduled at 22-APR-81 10:30:00:00 Reschedule interval 30M

>
The first task in the queue will run at 10:24:30:00
(hour:
minute:
second: clock tick);
it has not been rescheduled.
The second task in the queue will next run at 10:30:00:00
and is scheduled to run every 30 minutes.

3-43

MCR COMMANDS

DCL
DIGITAL COMMAND LANGUAGE (NP)
The DCL command allows you to issue DCL commands from a terminal that
is set to MCR.
Instead of MCR processing the command line, DCL
processes it.
The DCL task must be installed before it can do command
processing.
See the RSX-llM/M-PLUS Command Language Manual for
descriptions of the DCL commands.
Format:
DCL command-line
Examples:
>DCL SET DEF LB:
Issues the DCL command that sets the default device for
entering terminal to be LB:
(the system device).

the

>DCL TYPE [303,24]USERS.TXT
Issues the DCL command that displays a file on the entering
terminal.
The file is USERS.TXT, which is in UFD [303,24].

3-44

MCR COMMANDS

DEA
DEALLOCATE (NP,P)
The DEALLOCATE command releases a private (allocated) device, thereby
allowing other users ~o access it.
(This command applies only to
systems that support multiuser protection.) Nonprivileged users can
only deallocate private devices that they themselves have allocated.
A privileged user can deallocate any device in the system.
Note that when an owner of a private device logs out (issues the BYE
command), the system deallocates all that user's private devices.
However, if the system detects an error while attempting to deallocate
a device, it stops and does not deallocate that device or any
remaining devices. The related error message does not state which
device caused the error.
If an allocated device has been mounted, it must be dismounted
you deallocate the device.

before

Format:
DEA(LLOCATE]

[ddnn:J

ddnn:
The device·unit name and number of the private device to be
deallocated. If the command line does not specify a device unit,
the system deallocates all private devices owned by the user
logged in on the issuing terminal.
Example:
>DEA DM:
Deallocates disk DM:. The deallocated
mounted or allocated by other users.

3-45

device

can

now

MCR COMMANDS

task name
The name of the task that you want to debug._ If you do not
specify a task name, DEBUG looks for task TTnn, _which is the task

currently running from your terminal.
ODT as the debugging aid):

3-46

MCR COMMANDS

3-47

MCR COMMANDS

DEV
DEVICES (NP,P)
The DEVICES command displays the symbolic names of all devices or all
of a particular device type or the name of a specific device. The
device names appear in one column;
second and subsequent columns
contain additional information about each device.
Formats:
DEV[ICES]
DEV[ICES] dd:
DEV[ICES] ddnn:
DEV[ICES] /LOG
dd:
The type of devices for which you
displayed.

want

the

information

The specific device for which you
displayed.

want

the

information

ddnn:

/LOG
Displays all logged-in terminals.
On Rsx:-,11)M-PLU~ 15~~,tell\~·, .
di;spl~Yi ¥ 1i;nc,lW,j,\e{s,.,,, rtt\:e:;
Ac·coun:t;1:ni9' is :r·U!'n~i~n91,;;
l:qg:i~ 1Hi1~~ ,~
.. .

or /LOG, the
. Als,0 ,, if Resource
date and time of
first initial and

last'na\m~··"of:i
'.'.' /·:.
.::-.::
.,,,.,_ ..: , -. . ,,.,
·>::~

:,·~f:>J~:··:t:·.:(,<

Examples:
RSX-llM systems
>DEV
DBO:
DBl:
DB2:
DB3:
DBS:
OMO:
DMl:

ORO:
DRl:
LPO:
MMO:
MMl:
TTO:
TTl:
TT2:
TT3:
TT4:
TT5:

Public Mounted Loaded Type=RP06
Public Mounted Loaded Nowrite Type=RP05
Public Mounted Loaded Type=RP05
TTnO: - Private Loaded Type=RP05
Offline Loaded Type=RP05
Loaded Nowrite Type=RK06
TT60: - Private Loaded Type=RK06
Offline Loaded Type=RM03
Loaded Type=RM03
Public Loaded
TT60: - Private Loaded
TTlO: - Private Loaded
Loaded
Loaded
[312,1] - Logged On Loaded
Loaded
[302,310] - Logged on Loaded
Loaded

3-48

MCR COMMANDS

DEV (Cont.)
TT6:
TT7:
TTlO:
COO:
NLO:
TIO:
CLO:
LBO:
SYO:

[306,14] - Logged On Loaded
[50,25] - Logged On Loaded
[306,50] - Logged On Loaded
Loaded
LPO:
DBO:
DBO:

>DEV
TT2:
TT4:
TT6:
TT7:
TTlO:

/LOG
[312,1]
[302,310]
[306,14]
[ 7' 25]
[306,50]

>
>DEV DBl:
DBl:
Public Mounted Loaded Nowrite Type=RP05

>
>DEV TT30:
TT 3 0 :
[ 7 , 3 0]
CLI
LINES
LOWER
ECHO

[7,30]
MCR
BUF
24.
TERM
PRIV
NOHOLD
NOVFILL HHT

80.
HFILL
VT52
OWNER
NOSLAVE NOESC
NOFDX
WRAP

NONE
CRT
NOR PA

SPEED=(9600:9600)
BRO
NOA BAUD
NOFORM NOREMOTE
NOEBC
TYPEAHEAD

RSX-llM-PLUS systems
>DEV DB: (if privileged)
DBO:
Offline Loaded Type=unknown
DBl:
Offline Loaded Type=unknown
DB2:
Mounted Loaded Label=DEVUTIL Type=RP05
DB3:
Public mounted Loaded Label=USERSl Type=RP06
>
>DEV TT23:
TT23:
2-FEB-81 10:20 0
J. WHITE
[7' 20]
[7' 20]
CLI
MCR
BUF
80.
HFILL
SPEED=(9600:9600)
0
LINES
24.
TERM
VTlOO
NONE
NOABAUD
OWNER
BRO
PRIV
CRT
NO FORM NOREMOTE
LOWER
NO HOLD NOSLAVE NOESC
NOVFILL HHT
NOFDX
NOR PA
NOEBC
TYPEAHEAD
ECHO
WRAP
>
>DEV /LOG
TTll:
[304,6]
2-FEB-81 08:28 1
R. SMITH
[7' 306]
TT12:
[7,25]
[7,25]
2-FEB-81 08:42 1
M. BROWN
TT13:
[7,201]
[7,201]
2-FEB-81 10:24 1
J. STORM
TT15:
(7,325]
2-FEB-81 08:08 0
P. JONES
[7' 325]
Notes:
The following notes describe the information that can
subsequent columns.

appear

the

•

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

•

PUBLIC indicates that the device has been set public.

3-49

MCR COMMANDS

DEV (Cont.)

•

NOWRITE indicates that the volume is software write-locked
(write operations are not allowed on the volume).

•

TYPE indicates the device type.

•

MARKED FOR DISMOUNT indicates that a mountable device has been
requested to be dismounted, but the dismount operation has not
yet been completed.

•

OFFLINE indicates that, although the system tables contain
entries for
this device,
the host configuration does not
contain the related device, or the device was powered down at
the time of the boot.

•

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

•

LOADED indicates that a loadable device
loaded.

currently

•

UNLOADED indicates that a loadable device driver is
not loaded.

currently

•

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

driver

[uic]

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

the

user

logged

the

The lines in the display for
a specific terminal
list the
characteristics that have been set for the terminal.
The
description of the SET command gives all of the available
characteristics.

3-50

MCR COMMANDS

OMO
DISMOUNT (NP,P)
The DISMOUNT command requests the file system to mark the volume for
dismount and release the control blocks.
Marking a volume for
dismount prevents programs from opening additional
files on the
volume.
After all files open on the volume are closed, the Ancillary
Control Processor (ACP) releases the control blocks and dismounts the
volume.
If a single user has mounted a volume, the DISMOUNT command declares
the volume logically off line.
If multiple users have mounted- a
volume, the volume remains accessible until all users have dismounted
it.
When you dismount a volume,
the DISMOUNT command prints on your
terminal a message about whether or not a final dismount has been
initiated. When the dismount operation completes, either through the
Files-11
disk
system or the ANSI magnetic tape system
(ANSI
X3.27-1978), the command prints on the console terminal
(CO:)
the
message:

*** ddnn:

DISMOUNT COMPLETE
NOTE
Do not remove the volume until after you
have received this message.
If you
remove the volume beforehand,
it might
be corrupted and the next volume placed
on the device drive will probably become
corrupted.

There may be a considerable delay between the time you issue the
command and the printing of this message if a number of I/O requests
are pending and/or a number of files are open on the volume.
users can only dismount volumes that they have
A privileged user can dismount any mounted volume.

~onprivileged

Formats:
>DMO ddnn:

[["]label["]]

[/keyword(s)]

>DMO /USER [/keyword(s)]

3-51

mounted.

MCR COMMANDS

OMO (Cont.)
ddnn:
The device unit that holds the volume to be dismounted.
label
The Files-11 volume label may be up to 12(10)
characters in
length for disk and DECtape, and
up to six characters for
magnetic tape.
It is used to verify that the proper volume is
being dismounted.
A volume label is optional (if the command
omits a label, no volume label check is performed).
If

volume

label
for a magnetic tape
contains
must be enclosed
in quotation marks.
the MOUNT command for
the list of

special
See the
special

(Privileged keyword.) Dismounts all users from a
device.
This
keyword must be specified
if
dismounting a public device.

specific
you are

charact~rs,

description
characters.

it
of

Keywords:
/DEV

/USER
Dismounts all volumes that a user has mounted.
/TERM=ttnn:
(Privileged keyword.) Dismounts all volumes that a
the specified terminal has mounted.

user

/LOCK=option
Allows logical I/O to a volume after it is dismounted.
If
the drive supports software spin-dow~, you can also specify
whether or not the disk should be left spinning after the
dismount.
For magnetic tapes, /LOCK can be used to dismount
and remount a tape without having to reload the tape.

pnL !Rsx'71~M•,

on·•· RSXA.11.M~P:.

j)!\1 : +~i .if J'ld·••. µµ'.

The options for the /LOCK keyword are:
/LOCK=Nounload
/LOCK=Unload
/LOCK=Virtual
When you specify the Nounload option
(/LOCK=N),
DISMOUNT
clears the volume valid bit and does not spin down the disk
or unload the tape.
This option only inhibits access to the
volume.
This option is the default lock value for volumes
mounted as foreign and with no ACP specified.
(See the
description of the MOUNT command.)

3-52

MCR COMMANDS

OMO (Cont.)
When you specify the Unload option
(/LOCK=U)
for disks,
DISMOUNT clears the volume valid bit and, if the drive
supports the spin-down function, spins down the disk.
When
you specify /LOCK=U for tapes, DISMOUNT rewinds and unloads
the tape. Depending on the hardware, this may only place
the unit off line at load point or it may completely unload
the tape and close the autoload tape ring.
The /LOCK=U
option is the default lock value for all volumes mounted
with a standard ACP.
The usual procedure after dismounting
a volume that uses a standard ACP is to remove the volume
from the drive.

The Virtual option is privileged. When you specify /LOCK=V,
DISMOUNT does not clear the volume valid bit and does not
spin down the disk or unload the tape.
The Executive still
permits logical I/O to the volume. For example, the task
image of an installed task can reside on a disk that has
been dismounted with the /LOCK=V option.
However, the file
system cannot access the volume.
This option is the default
when dismounting the system disk prior to saving the system.
Examples:
>DMO DMl:AMBER
Dismounts the volume labeled AMBER on device unit DMl:.
If
a single user has mounted the volume, the command dismounts
the volume.
If more than one user has mounted the volume,
the volume remains mounted for the other users.
>OMO DMl:/DEV
Places the volume on device unit DMl:
logically off line
and releases all control blocks. Users can no longer access
the device.
>DMO /USER/TERM=TT17:
Dismounts all volumes mounted by terminal TT17:.
>DMO DKO:
DMO -- TT60:

dismounted from DKO:

*** Final dismount

initiated

Begins the dismounting process for DKO:. When the DISMOUNT
COMPLETE message is printed on the console terminal, the
volume can be removed from the drive.

3-53

April 1983

***

MCR COMMANDS

OMO (Cont.)
Command Error Messages:

I
DMO -- WARNING -- TASKS INSTALLED FROM ddnn:
The disk being dismounted has tasks installed from it.
DMO
dismounts the disk, but you can still run the tasks until
the disk has spun down. Use the TAS command to find out
which tasks are installed.

DMO -- CHECKPOINT FILE STILL ACTIVE
The command attempted to dismount a volume that contained an
active checkpoint file.
The volume cannot be dismounted
until the checkpoint file has been discontinued.
Issue an
ACS command to discontinue the file and reissue the DMO
command when the system issues a message to indicate that
the checkpoint file is inactive.
DMO -- DISMOUNTING SYSTEM DISK
This message should only occur during a system generation or
during system shutdown. Since the system disk is a public
device, it can be dismounted only by a privileged user.
DMO -- DISMOUNT IS NOT NECESSARY FOR CASSETTES
Self-explanatory.
ddnn:

This is an informational message only.

IS ATTACHED BY TASK taskname
DMO attempted to dismount an attached device.
Because DMO
processes the mount list several times before exiting, a
device could be dismounted if the task to which it belongs
detaches before DMO exits.
If the device is dismounted, a
normal dismount message appears later.

3-54

April 1983

MCR COMMANDS

OMO (Cont.)
DMO -- NO VOLUME LIST
The command specified a magnetic tape for
volume label list does not exist.

which

mounted

TOO MANY DEVICES ATTACHED, NO FURTHER ATTACH MESSAGES
DMO issues this message when eight
(or more)
devices are
attached during a DMO /USER operation. A message is printed
for the eighth .device, but not for any number over that.
DMO -- VOLUME NOT MOUNTED
The specified device was not mounted.
OMO -- VOLUME NOT MOUNTED BY TI:
The command specified a dismount operation for a volume that
was not mounted
from the issuing terminal or the command
specified the wrong device name for a tape set.
OMO -- WRONG VOLUME LABEL
The volume label and the label specified in the command
not match.

3-54.1

did

MCR COMMANDS

FIX
FIX-IN-MEMORY (P)
The FIX command loads and locks a task into its partition. Subsequent
requests for
running the task are serviced more quickly because the
task is memory-resident and does not have to be loaded from the disk
before it can run. The system can fix a task in memory only when the
partition in which it is to be fixed becomes available.
Fixed tasks remain physically in memory even after they exit.
Therefore,
they do not have to be reloaded when a request is made to
run them.
(Note that reexecuting fixed tasks is not always practical;
to reexecute, the task must initialize all
impure data and LUN
assignments at run time.) Only an UNFIX or REMOVE command can free the
occupied memory partition.
The following restrictions apply to the fixing of tasks:
•

On RSX-llM systems, checkpointable tasks cannot be fixed.
On
RSX-llM-PLUS systems, checkpointable tasks should not be fixed
because fixing a checkpointable
task
makes
the
task
noncheckpointable.

•

Active tasks cannot be fixed.

•

A task must be installed before it can be fixed.

Format:
FIX taskname[/keyword]
The variable taskname is the name of the task to be fixed in
memory.

3-55

MCR COMMANDS

FIX (Cont.)
Examples:
>FIX XKE
Fixes task XKE in its partition.

Command Error Messages:
FIX -- PARTITION BUSY
The partition in which the task was to
occupied, so the task could not be fixed.

fixed

was

FIX -- TASK ACTIVE
The specified task is already active.
be fixed.

Active

tasks

cannot

FIX -- TASK ALREADY FIXED
The specified task was already fixed in memory.
FIX -- TASK BEING FIXED
The specified task was already being fixed.

FIX -- TASK CHECKPOINTABLE

(RSX-:UM systems .only .. )
fix.e(j, . }n . me!llo.ry... ·... ·Rem

noncn~c~pqi Qt9p~e

UPKP

cP,eckpointable task cannot
~he. ,.;taslf... anp,. ·.. i~;Sta~l
it
... · :You; :Can. then fix the task

be
.as

.memory"'
FIX -- TASK HAS NO READ ONLY SEGMENT
An attempt was made to fix
the read-only segment of a
multiuser task,
but the spcified task does not have a
read-only segment.
FIX -- TASK NOT IN SYSTEM
The specified task has not been installed in the system.
uninstalled task cannot be

3-56

MCR COMMANDS

FLA
GROUP GLOBAL EVENT FLAGS (NP,P)
The FLA command creates, eliminates, or displays group global event
flags.
Group global event flags provide each UIC group with 32 event
flags in addition to the 32 common and 32 local event flags.
Group
global event flags are similar in use to the common event flags (see
the RSX-llM/M-PLUS Executive Reference Manual). However, only those
tasks running under the same group UIC can use the group global event
flags for that group.
Nonprivileged users can only create or eliminate
flags for their login group UIC.

group

global

event

Privileged users can create or eliminate group global event flags
any group.

for

Format:
>FLA[GS]

[ [ggg] /keyword]

(ggg]
Represents the group for which the group global event
to be created; defaults to login UIC group.

flags

are

Keywords:
/CRE
Creates group global event flags for
group.
If the flags already exist
delete, the delete flag is cleared.

the
but

specified UIC
are marked for

/ELIM
Eliminates group global event flags for the specified UIC
group.
Event flags are not eliminated until the access
count reaches O. If the access count is greater than O, the
flags are marked for delete.
When you omit the group number and keyword specification, the
displays all the group global event flags in the form:
ggg

access count

event flags

command

[DEL]

where [DEL] indicates group global event flags marked for delete.
Examples:
>FLA 303/CRE
Creates group global event flags for all tasks running under
the UIC group number 303. All flags are initialized to 0
when created.

3-57

MCR COMMANDS

FLA (Cont.)
>FLA
303

000010 000000

Displays the access count (1) and event flags set
(in this
case,
flag 68) for the UIC group 303. The access count is
the number of tasks using the event flags.
The group global event flags are represented by two octal
words.
The first word contains event flags 65 through 80
(from right to left) and the second word contains event
flags 81 through 96 {from right to left).
>FLA 303/ELIM
Eliminates group global event flags for UIC group 303.
Command Error Message:
FLA -- ILLEGAL FUNCTION
The /CRE keyword was specified, but the event flags already
existed
(even though they may have been marked for delete),
or the /ELIM keyword was specified, but the event flags were
already eliminated or ma;ked for delete.

3-58

MCR COMMANDS

HEL/LOG
HELLO or LOGIN (NP)
The HELLO and LOGIN commands log you in on a terminal to gain access
to a multiuser protection system.
Before you log in, the system
rejects all MCR commands except HELLO, LOGIN, and HELP.
Parameters to
the HELLO command are a last name or User Identification Code (UIC)
and a password. The system validates these parameters according to
entries in an account file.
If the name or UIC and password match an entry in
the system performs the following actions:

the

account

file,

Checks to see if the terminal's current command
line
interpreter
(CLI)
has requested a silent login.
(Silent
logins are available only on systems with multi-CLI support.)
If so,
HELLO does not display the login text file or the
user's login command file, does not execute the system login
command file,
and does not set the default CLI for the
terminal.

Assigns
system
already
the one

Establishes the
default UIC.

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

Displays a system identification, the current date,
and the
time the user logged in on the terminal.
If the CLI requests
silent login, the information is not displayed.

If the system supports alternate CLis,
sets the terminal's
default CLI to be the one specified in the user's account
file.

Displays the contents of the file LB:[l,2]LOGIN.TXT.
If
CLI requests a silent login, LOGIN.TXT is not displayed •

the login logical device name SYO:
to the user's
disk unless the user's logical system device is
the same as physical device SY:.
(The system disk is
that contains the user's files.)
user's

. :io~?/#~*.l~l_:*·~;1'tu$,)U·i¥····
terntf~a,lf ·. ·.. HEL,~o·;: ··a
.a

UIC,

which

the

initial

the

. ···.···.··.:AS:#••·i>'.i\'.r.s······'.'·'~•~·i.~
·run t:•·r:am F~•·~·.·. .:·
·.·.·~lr.·21~·~1rC~~
. . . ~f1o\V:e:ve·rj./_' . . J;fr .:

BATCFh:TXT.·. does.. nqF: ~*;is·~, 6~4~·() ...· .•·•.· .Ci·.;~pl~y~.· ··e~l~:•.r}{l';• .•. • ·.•·. •,BEJ.f~Q.·.·:
dqes . not ......a.ispl~Y .•... a11ylogin··tex.t::·file'. on ·a··virtua1 .... t:errilfn·a·1
unless<a batchj9}:) 1$ being run .from. it•

Executes the system command file LB:[l,2]SYSLOGIN.CMD (if it
exists)
unless the CLI requests a silent login.
Before the
file is invoked, HELLO instructs the system to override the
user's default CLI and use MCR to process the file.
(This
allows SYSLOGIN.CMD to use MCR commands.)
SYSLOGIN.CMD is
invoked with the terminal privileged and slaved.

3-59

MCR COMMANDS

HEL/LOG (Cont.)
HELLO passes the following information to SYSLOGIN.CMD:
Default system device
Login UIC
Last name
First initial
If terminal is to be privileged
If terminal is to be slaved

( xxn:)
([g,m])
(P or NP)
(S or NS)

If SYSLOGIN.CMD exists, it must do the following:
•

Check the appropriate parameter to see if
the
terminal should be privileged or nonprivileged and
set the terminal accordingly and then check the
appropriate parameter to see if the terminal should
be slaved or nonslaved and
set
the
terminal
accordingly.
NOTE
It is important to set a terminal's privilege
status before its slave status. Otherwise, a
nonprivileged user could become privileged.

•

If your system has multi-CL! support,
issue the
command CLI /UNOVR to instruct the system to use the
user's CLI.
The CLI would be MCR, DCL, or a
user-written CLI.
If a default CLI is not specified in the account
file,
the terminal is set to MCR.
If the specified
CLI is not present in the system, HELLO issues an
error message and the user cannot log in.

The following code is an example of
(using Indirect):

.SLAV:

system

.ENABLE SUBSTITUTION
.ENABLE QUIET
.IF PS = "P" .GOTO SLAV
SET /NOPRIV=TI:
.IF P6 = "S" .GOTO OVER
SET /NOSLAVE=TI:

..;CLEAR
,
OVERRIDE BIT
•

OVER:

CLI /UNOVR
• DISABLE QUIET
.SETS FILE Pl+P2+"LOGIN.CMD"
.TESTFILE 'FILE'
.IF <FILERR> = 1 .CHAIN 'FILE'/LO

.END:

3-60

command

file

MCR COMMANDS

HEL/LOG (Cont.)
10. If LB: [l,2]SYSLOGIN.CMD does not exist, HELLO executes the
user's LOGIN.CMD if it exists. Before executing, HELLO sets
the user's
slaved
or
nonslaved
and
privileged
or
nonprivileged status and clears the CLI override bit.
11. After invoking HELLO, if the user does not enter a name or
UIC and password, HELLO prompts for them.
If the user does
not respond to the prompt within a certain time interval,
HELLO times out. The timeout interval is specified when the
HELLO task is built.
if the interval is zero (0), HELLO does
not time out.
If logins-have been disabled for your system, HELLO displays the
reason for this.
If desired, the person who disables logins can
create or edit LB:[l,2]NOLOGIN.TXT to include the reason.
Formats:

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

• >HEL[LO]
e

uic
}
{ username

that

the

user

allows

the

/password~

>HEL[LO]~

Account or name:
Password:

• >HEL[LO]
Password:

uic
}
{ user name

password~

uic
} ~
{ user name
password~

uic
Your User Identification Code
(UIC).
following four UIC representations:

The

command

g,m
[ g ,m]
g/m
[g/m]
To suppress part of the display of the file
slash form (that is, g/m or [g/m]).

use

the

The variables g and m are octal numbers from 1 through
represent group and member numbers, respectively.

377

that

user name
Your last name, which can be entered in place of a UIC.
password
An alphanumeric password=
If you type the password i u response
to the prompt PASSWORD:, the system does not display (echo) the
typed characters.

3-61

MCR COMMANDS

HEL/LOG (Cont.)
If the HELLO command was successful, the system displays the following
message:
system i.d.
dd-mm-yy hh:mm Logged on Terminal TTnn:

xxxnnnn

greeting
[login-text]
system i.d.
One of the following, depending on the system:
RSX-llM BLnn

[g,m] System

RSX-llM-PLUS V02 BLnn

node name

[g,m] System

node name

dd-mm-yy
The current date.
hh:mm
The time the user logged in.
xxxnnnn
'

· Ain

·...

·,;,

RS'Xi-llM.,-PLUS

se~s'fon.

greeting
One of the following, depending on the time of day:
Good Morning
Good Afternoon
Good Evening
login-text
The contents of LOGIN.TXT (or BATCH.TXT).
the contents of the file as follows:

system

displays

If you use the.slash form when specifying the UIC the first
time you log in, the display concludes at the first percent
sign (%) in the file.
Subsequent logins on any one day (using
the slash form) do not display the contents of the text file
unless the file has been edited.
(The percent sign is used to
separate new messages from old ones.)

•

If you do not use the slash form,
the system displays the
entire file.
(Note that you can type CTRL/O to end the
display after the first percent sign.)

I
I

The

If the login text file does not exist, the message
MESSAGE FILE ERROR -26
is displayed.

3-62

April 1983

MCR COMMANDS

HEL/LOG (Cont.)
Examples:

RSX-llM systems
>HEL
Account or name:
Password:

AMBER

RSX-llM BL32
[4,54] System
QUASAR
2-FEB-81 10:03 Logged on Terminal TT20:
Good Morning
2-FEB-81

*** NEW DISK CONFIGURATION ***
DBO:

System and User disk

>
(User typed CTRL/O to stop output.)
>HEL [301/365] /BOB
RSX-llM BL32
[4,54] System
2-FEB-81 10:06 Logged on Terminal TT20:
Good Morning
>HEL 301/365
PASSl"10RD:
RSX-llM BL32
[4,54] System
3-FEB-81 09:45 Logged on Terminal TT17:
Good Morning

>
>HEL 301,3n5 /BOB
RSX-llM BL32
[4,54] System
3-FEB-81 09:45 Logged on Terminal TT17:
Good Morning
2-FEB-81

*** NEW DISK CONFIGURATION ***

>
(User typed CTRL/O to stop output.)

3-63

MCR COMMANDS

HEL/LOG (Cont.)
RSX-llM-PLUS systems

>HEL 303/24/79584
RSX-llM-PLUS V02 BLlO
[2,54] System
02-FEB-81 17:58 Logged on Terminal TT30: as WRT17

CASTOR

Good Afternoon

>
>HEL 303,24
PASSWORD:
RSX-llM-PLUS V02 BLlO
[2,54] System
02-FEB-81 18:01 Logged on Terminal TT30: as WRT17

CASTOR

Good Evening
30-JAN-81
Batch
(User typed CTRL/O to stop output.)

>
Command Error Messages:
Note that if you use the LOGIN command to log in instead of HELLO, the
error messages are preceded by LOG.
HEL -- ACCOUNT FILE OPEN FAILURE
The account file was open for another user or the disk
containing the account file was not mounted. Reenter the
command line.
_..;. .ACCOUNT FILE RECORD(S)

LOCKED

· (RSX..;.llM~PLUS system$ only.) HELLO could
account record~ Reenter the '<command .Jine.

access

not

HEL -- ASSIGN FAILURE
HELLO could not assign your system device.
.

(RSX-11M.-PLUs . . systems·. only.) .•• ·The: ·Reso·~rce···AccountAng system
requires space< in secof).daiy pool to allocate .a l)ser Account
Block {UAB}~. ·. ·. If . ·s.ufficient ~pace is .· npt: ayailable . in
secondary poo~, ·. nonprivileg~d . 1.rsers cannot fog in~ .. (The
Resource Accounting sys1:em qcpepts a switc·h, /PQOL RESERV.E 1
that penni t;.s th:e system rnG\nag,e,r td alter 'the ~~condary pool
limit.. ?ee the RSX'""llM/M...;.PLUS System Mariagement Guide for
complet.e details.)

3-54

MCR COMMANDS

HEL/LOG (Cont.)
HEL -- CANNOT FIND PHYSICAL LB:
HELLO could not open the file because LB:

was not assigned.

HEL -- CANNOT SET CLI
(Multi-CLI systems only.) The command line interpreter (CLI)
is installed in the system, but HELLO failed to set the
terminal to the CLI.
HEL -- CLI NOT IN SYSTEM
(Multi-CLI systems only.) You could not log in because the
default CLI specified for you in the account file is not
installed in the system.
HEL -- INVALID ACCOUNT
The name or UIC specified in the command is not stored in
the account file or the password specified does not match
the name or UIC given.
HEL -- LOGINS ARE DISABLED
The system was in the process of shutting down or the
command SET /NOLOGON has been issued.
You cannot log in at
these times.
HEL -- LOW POOL - NONPRIVILEGED LOGINS DISABLED
To save space in pool,
the
nonprivileged users to log in.

system

will

not

allow

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

HEL

;_~ •· J?RlV'ttEGED

USER <LOGGED ·.wl'l'HdUT :UAB

(RSX~llM.-PLus· systems only;..)
This m~'!;)Sq<Je . .•.·•' ind'i(!ates . . ···.·.that:
there was • not ....· sufficient .. space .in s~cx>ndarYJ;>~ql .for the
Re<So urce . . 1\CC'()~nt~n~ ~ys·t~nr • ~o al locate a llsejr 'AF?<>ttnt .· · Block

(UAB) .•. ·•,··.· aowev~r1·· ····.the··• systent . ·.·.permi.ts . priy.ileged.·users .•.•·to.···).09

in, although the accounting system will ne>t ·. · ke~p> tra~k . of
their use of the operating system. Se,e the RSX~llM/M'-PLUS

SystemManagement Guide~

MCR COMMANDS

HEL/LOG (Cont.)
HEL -- SPAWN FAILURE
The Executive directive SPAWN failed to assign your system
device or the Executive directive RPOI failed to chain to
Indirect to execute the login command file.
HEL -- SYNTAX ERROR
The format of the command line for HELLO was incorrect.
HEL -- TERMINAL ALLOCATED TO OTHER USER
The issuing terminal was already allocated to another user.
You cannot log in on a terminal allocated to someone else.
HEL -- TIMEOUT ON RESPONSE
You did not respond to the HELLO prompt before the timeout
count elapsed.
(The timeout count is specified when the
HELLO task is built.)
HEL -- WARNING

** DEFAULT DEVICE NOT IN SYSTEM

Your default system device is not in the system,
so HELLO
did not make the assignment.
However, you are still logged
in.

3-66

MCR COMMANDS

HELP
HELP (NP)
The HELP command displays the contents of the general help file for
your system.
The default help file is LB: [l,2]MCR.HLP.
HELP is the
only MCR command that you can issue without logging in.
The display
usually contains information on how to log in on the terminal, but
each installation can change the contents of its help file to suit
specific needs.
Formats:
HELP% [qualifierl]
HELP[/keyword]

[qualifier2]

[qualifierl]

[ ••• qualifier9]

[qualifier2]

[ ••• qualifier9]

%
Displays the text contained in [current-uic]HELP.HLP.
be logged in to request HELP %.

You

must

Keywords (all mutually exclusive):
/CLI:cliname
Directs HELP to the help file for a command line interpreter
(CLI) in LB:[l,2]cliname.HLP.
If you are in your own CLI and omit the keyword, the default
help file is LB:[l,2]MCR.HLP.
/DCL
Specifies that the help
text
begins
in
the
file
LB:[l,2]DCL.HLP.
This is the default for terminals set to
DCL.
/FIL:[filespec]
Specifies any file where help text is located.
If you do
not give a complete file specification, the defaults are
LB:[l,2]filename.HLP.
If you only use /FIL:,
the default
help file is LB:[l,2]MCR.HLP.
/GRO
Instructs HELP to use
[group,l]HELP.HLP on the default
volume as the root help file. Group help files allow users
with the same group number to share common help files for
that group.
/LOC
Displays the text contained in
directory on the default volume.
to the HELP % command.

3-67

HELP.HLP in the default
This keyword is equivalent

MCR COMMANDS

HELP (Cont.)
/MCR
Specifies that the help
text
begins
in
the
file
LB:[l,2]MCR.HLP.
This is the default for terminals set to
MCR.
/OUT:filespec
Saves the text of the help file (or files) in the specified
file.
If you do not specify a file, HELP puts the help text
in a file named .;l. If you do not use the /OUT keyword,
HELP displays the files on your terminal.
/xxx
Specifies that the help
text
begins
in
the
file
LB:[l,2]xxx.HLP, where xxx is the name of a CLI. This
keyword produces the same results as specifying /CLI:xxx.
The format of a HELP.HLP file is:
1

FIRST-QUALIFIER-1
Text
that
will
FIRST-QUALIFIER-1.

displayed

you

type

HELP

FIRST-QUALIFIER-2
Text that will be displayed if you type HELP FIRST-QUALIFIER-1
FIRST-QUALIFIER-2.

SECOND-QUALIFIER-2
Text that will be displayed if you type HELP FIRST-QUALIFIER-I
SECOND-QUALIFIER-2.

SECOND-QUALIFIER-1
Text
that
will
SECOND-QUALIFIER-I.

displayed

you

type

HELP

The numerals are level numbers and range from one through nine
inclusive.
Level numbers must be the first character of their line
and the qualifiers that follow must be uppercase.
Arbitrary strings
of blanks or tabs are allowed between level numbers and qualifiers.
If a qualifier begins with a dollar sign ($) or a slash (/), the $ or
I is ignored.
HELP interprets its command line in a strictly nested fashion.
When
searching for qualifiers in a help file, HELP begins by iooK1ng for a
line containing level number 1, followed by the first qualifier
specified in the command line. If successful and no other qualifiers
were specified, the subsequent help text is displayed. Otherwise, the
search continues for a line containing level number 2, followed by the
second qualifier specified in the command line. Again, if no other
qualifiers were specified, the subsequent help text is displayed.
This correspondence of qualifier position in the HELP command line
with level numbers in the help file continues until the last qualifier
is found.

3-fi8

MCR COMMANDS

HELP (Cont.)
HELP permits references within the help file to other files that
contain large blocks of text and/or additional level numbers and their
qualifiers. Indirect references to other files decreases search time
and also allows more flexible use of the help file. To reference
another file from within the help file, specify an at sign (@) as the
first nonblank character on a line followed by a file specification.
For example:
@filespec
The variable filespec is any legal RSX-llM/M-PLUS file specification.
The default file type is .HLP. However, if a file type other than
.HLP is specified, HELP uses the specified file type as the default in
succeeding
indirect
references.
For example, if you specify
@filename.TXT, HELP uses .TXT as the default file type in future
indirect references.
The file version number always defaults to the
highest existing version.
The file referenced in this manner has the same format as the help
file.
Note' that if the indirect file contains level numbers, the
level numbers must be greater than the level number in the help file
that precedes the call to the indirect file. For example, if the help
file contains the following lines:
1 EXAMPLE
@HELPEXAMPLE
then HELPEXAMPLE.HLP can only contain level
(the numerals 2 through 9).

numbers

greater

than

HELP also allows you to share text between two or more similar or
synonomous qualifiers in the help file. To do this, specify a pound
sign (#) followed by the similar qualifier as the first nonblank
character on a line. For example, to relate the qualifiers LOGIN and
HELLO, the help file would contain the following lines:
l LOGIN
*HELLO
l HELLO
See Ben Smith for an account and password.
Note that the qualifier that contains the displayed text must be of
the same level number as all the qualifiers that refer to it. Also,
since HELP searches the help file sequentially, the qualifier must
appear after all those that refer to it.
~long with one-word synonyms, you can also use string
example:

1 UTILITIES
2 RUNNING
= TASKS EXECUTING
1 TASKS
2 EXECUTING
Always begin the string synonym with qualifier 1.

synonyms.

For

MCR COMMANDS

HELP (Cont.)
Example:
The following is an example of a help file:
The seneral form of the HELP command i$l
HELP [oualifier1J Caualifier2J r ••• ~ualifier9J
This disPlass text from the ssstem helP file.
The other seneral form of the HELP co••arid is:
HELP X [aualifierlJ toualifier2l

t.~.aualifier9J

This disPlass infor11ation fro11 a user's own help file.
ssntax is not lesal until sou are loss&ed in.

This

1 LOGIN
IHELLO
1 SPELLING
Ts Pe HELP SPELLING DICTIONARY followed bs
sou want to sPell.
2 DICTIONARY

the

word

The file DICTIONARY.HLP tnot included in
this
exaaPlel contains an abridsed li&tins of freauentlY
misspelled words.
@DICTIONARY
1 HELLO

See Ben Johnson for an account and password.
1 CREATE

NOTE
When creatins a help file' the first line
should be blank since it is not disPlased.
Bs convention, each line should besin with a

blank or
tab;
the lines cannot besin with the di~its 1 throush
9 since these would be interpreted as level numbers.
Also' dePendinS uPon the tsPes of devices in sour
confisuration, some Practical restrictions should be
imposed.
For example• to accommodate VTOSBs, lines of
text should not be more than 72<10) characters lons and
a block of text should not be 11ore than 20(10) lines.
If there are level n+1 aualifiers, the~ should be
•entioned in the text so that the~ are known to exist.
Si•ilarls, level 1 aualifiers should be added to the
text disPlased when onls HELP is tsPed+

3-70

MCR COMMANDS

HELP (Cont.)
If a system contained this help file,
display in response to HELP L:

you

would

get

the

following

>HELP L
See Ben Johnson for an account and password.

>
The qualifier HELLO is the synonym defined for
LOGIN
(L),
so HELP
displays the text following HELLO for both qualifiers.
(Note that a
qualifier may be specified by the fewest
initial characters that
unambiguously define it.)
Command Error Messages:
HEL -- AMBIGUOUS HELP QUALIFIER
The qualifier does not specify a unique part of the help
file.
Further characters must be supplied.
Examine the
command line that HELP displayed below the error message and
specify the last qualifier displayed more completely.
HEL -- AMBIGUOUS HELP SYNONYM
The qualifier referenced as a synonym was not unique.
HEL -- CANNOT INITIALIZE FILE STORAGE REGION CORRECTLY
The HELP text could not be buffered adequately.
command line.

Reenter the

HEL -- CANNOT OPEN OUTPUT FILE
The output file specified with the /OUT:filespec keyword
cannot be created.
This message can occur for several
reasons.
For example, the device may be write-locked or you
do
not have the necessary access privileges for
the
specified UFD.
REL

EXCESSIVELY NESTED OR RECURSIVE SYNONYMS
A string synonym used in the help
defined recursively.

file

has

probably

been

HEL -- HELP FILE ERROR nnn
The help file could not be opened for the reason specified
by the FCS code nnn.
If the code number is -26, the help
file does not exist.
See the IAS/RSX-11 I/O Operations
Reference Manual for definitions of the error-COdes.
HEL -- HELP SYNONYM NOT FOUND
The help file referenced a synonym, but
include it.

3-71

the

file

did

not

MCR COMMANDS

HELP {Cont.)
HEL -- ILLEGAL SWITCH - NOT LOGGED IN
You attempted to reference a local or group help file or
output help text to another file without being logged in.
Log in on the system and then enter the HELP command line.
HEL -- IMPROPER HELP FILE FORMAT
The help file is not in proper format and cannot be
Either edit the file or reenter it in proper format.

used.

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

the

HEL -- INDIRECT HELP FILE SYNTAX ERROR
HELP encountered a syntax error either in a
another file or in the indirect file itself.

reference

HEL -- SWITCH SYNTAX ERROR
You specified a keyword incorrectly.
line.

Reenter

the

command

HEL -- UNKNOWN HELP QUALIFIER
The help file does not contain the last qualifier
in the command line below the error message.

3-72

displayed

MCR COMMANDS

HOM
HOME (NP,P)
The HOME command allows you to modify certain fields in the home block
of a Files-11 disk volume. After you make the changes, HOME performs
extensive checks to ensure that a good home block is written back onto
the volume.
If any of these checks fail, HOME attempts to place an
alternate home block on the first free block on the home block search
path.
If this is completed successfully, HOME issues a warning
message about the new home block. However, you should copy the volume
as soon as possible because the alternate home block could be
destroyed while the volume is mounted.
To use the HOME command, you must first install the INI task with
task name ••• HOM as follows:

the

>INS $INI/TASK= ••• HOM
The difference between INI and HOME is that IN! writes the home block
of a volume whereas HOME changes the information in the home block
(without changing anything else). Because the HOME command and the
INI command are implemented within the same task, they share many of
the same error messages. See the description of the INI command for
explanations of these common messages.
Also be aware that you cannot use the HOME command on RSX-llM V3.2 (or
earlier versions) or on RSX-llM-PLUS Vl.O and get the desired results.
Format:
HOM(E] ddnn:volume-label/keyword(s)
ddnn:
The volume whose home block you want to modify.

volume-label
The current label for the volume.
/keyword(s)
The specifications for the fields you want to modify in the home
block.
Each keyword defaults to the value specified for the
particular field when the volume was initialized.
The keywords
do not change the files created by the INI command.
Keywords:
/DENS=density
Checks the density of a floppy disk.
If specified, the
drive density is compared against the keyword value for
consistency. Acceptable values are: HIGH and LOW.

3-73

MCR COMMANDS

HOM (Cont.)
/EXT=block-count
Specifies the default file-extend size.
A file must be
extended when it has used all of its allocated space. Legal
values for block-count range from 1 through 255(10).
Note that if you specify /EXT=O, no files {including the
system files)
can be extended. Therefore, although there
may be free space on the disk volume, unless there are also
free file headers, new files cannot be created on the
volume.
{If there are no free headers and the index file
cannot be extended, no new files can be created.)
/FPRO=[system,owner,group,world]
Specifies the default protection for the files on the
volume.
Access codes consist of four 4-code groups in the
access rights word as follows:
R WE D -

Read
Write
Extend
Delete

In each instance, the absence of the code
user class is denied the access right.

means

that

the

The user classes (system, owner,
group,
world)
are
positional. That is, the location of the word in the string
defines the user class to whom the code applies. The order
is:
[system,owner,group,world]
The square brackets are required syntax.
Substitute an asterisk (*) for the access codes to force the
default value for a specific class.
/LRU=directory-count
Specifies the approximate number of directories that will be
accessed simultaneously. The FllACP maintains a list of the
most recently used directories. The value you specify for
/LRU sets the number of entries in this list. In general,
directory operations can be speeded up significantly by
increasing the number of entries.
If a directory appears in the list, no disk I/O is required
for finding the directory in the Master File Directory
{MFD). In addition, directory operations do not require the
directory file header to be read. If you do not use /LRU,
the default for directory-count is the value specified when
the volume was initialized.
Legal values for directory-count range from 1 through
127(10).
Note that increasing the value for /LRU increases
the number of File Control Blocks (FCBs) used and may
increase
tne
amount
of system pool used.
See the
appropriate system generation manual for more information.

3-74

MCR COMMANDS

HOM (Cont.)
Also note that if you specify /LRU=O, the FllACP will not
keep a
list of directories.
This is not recommended and
could have an adverse effect on system efficiency.
/MXF=f ile-count
Specifies the maximum number of files allowed on the volume.
This number corresponds to the number of file headers in the
volume's index file.
The value for /MXF includes the five
system files and cannot be greater than the total number of
bits allocated to the index file bitmap. Use the following
algorithm to determine the maximum number of files allowed
on your volume:
maximum= (4096.)*(current-number-of-index-file-bitmap-blocks)
The number of
index
file bitmap blocks depends on the
maximum number of files currently allowed on the volume.
Use the /VI keyword to obtain this number and read the
description of the /INF keyword
for
the !NI command to
determine how many index file bitmap blocks are on the
volume.
Note that you also cannot reduce the maximum number of files
already specified for the volume.
/NAME=new-volume-label
Specifies a new label for the volume.
/OVR (P)
Instructs the HOME command to override label processing so
that a
volume can be modified without specifying a volume
label.
/OWNER=[group,member]
This keyword
is
Specifies the owner of the volume.
Legal group and member numbers range
identical to /UIC.
The square brackets are required
from 1 through 377(8).
syntax.
/PRO=[system,owner,group,world]
Specifies the default protection for a volume. Access codes
consist of four 4-code groups in the access rights word as
follows:

R - Read
Write
C - Create
D - Delete

W -

In each instance, the absence of the code
user class is denied the access right.

3-75

means

that

the

MCR COMMANDS

HOM (Cont.)
The user classes
(system, owner,
group,
world)
are
positional.
That is, the location of the word in the string
defines the user class to whom the code applies.
The order
is:
[system,owner,group,world]
The square brackets are required syntax.
Substitute an asterisk (*) for the access codes to force the
default value for a specific class.
/UIC=[group,member]
Specifies the owner of the volume~
Legal group and member
numbers range from 1 through 377(8).
The square brackets
are required syntax.
This keyword
is
identical to the
/OWNER keyword.
/VI
Lists the HOME keywords and their values for
volume •

•

the

specified

/WIN=retrieval-pointer-count
Specifies the number of mapping pointers to be allocated for
file windows.
A file window consists of a number of mapping
pointers and is stored in memory when the file
is opened.
(See the IAS/RSX-11
I/O Operations Reference Manual for a
description
of
~-mapping
pointers.)
The
retrieval-pointer-count must be 1 through 127(10).
Example:
>HOM DKO:TEST/MXF=2357./VI
** Volume information for DKO:
Label
/Cha
/Ext
/Fpro
/Lru
/Mxf
/Pro
/Uic
/Win

TEST
[]

100.
[RWED,RWED,RWED,R]
3.
2357.

[RWED,RWED,RWED,RWEDJ
[1,1]
7.

Maximum possible files = 4096.
The Homeblock revision count is 1, Last revised on ll-AUG-81

Volume created on ll-AUG-81 at 19:47:37

3-76

April 1983

MCR COMMANDS

HOM (Cont.)
Command Error Messages:

NOTE
If you receive an error message that is
not listed here, see the description of
the INI command for an explanation of
the message.
<bell>*** ATTENTION ***<bell>
THIS VOLUME IS OPERATING WITH A REPLACEMENT HOME BLOCK
PLEASE TAKE THE ACTION OUTLINED IN THE DOCUMENTATION
HOME could not ensure that a good home block would be written
back to the volume, so it has placed an alternate home block on
the first free block on the home block search path. The new home
block is not allocated to or mapped by any file.
You should copy
the volume as soon as possible because many operations on a
mounted volume could destroy the replacement home block.
HOM -- FAILED TO FIND HOME BLOCK
HOME could not locate the home block of the volume.
HOM -- FAILED TO PLACE ALTERNATE HOME BLOCK
When HOME cannot ensure that a good home block will be written
back to the volume, it attempts to place an alternate home block
on the first free block of the home block search path.
This
message indicates that the attempt failed.
Note that your volume
may be corrupted and therefore unmountable.
HOM -- MXF LESS THAN OR EQUAL TO THE EXISTING VALUE
The value specified with /MXF was less than or equal to the
maximum number of files already specified for the volume.
This
value must be greater than the current number of files allowed.
HOM -- SWITCH IS NOT LEGAL IN THIS MODE
You attempted to use INITIALIZE
with the HOME command.

keywords

and/or

their

options

HOM -- WRONG VOLUME LABEL
The volume label specified in the command line did not match
volume's current label.

3-77

the

MCR COMMANDS

INI
INITVOLUME (NP)
The INITIALIZE VOLUME command produces a Files-11 volume (see Section
2.1).
On disk and DECtape, the command initializes the volume
(destroys all existing files), writes a dummy bootstrap and a home
block, and builds the directory structures. On magnetic tape, the
command writes a volume label according to the ANSI X3.27-1978
standard and writes a dummy file that destroys all existing files.
Note that a magnetic tape volume produced by the IN! command is
considered to be a null volume. If you are going to transport a newly
initialized tape to a non-RSX-llM/llM-PLUS system, you might first
have to make the null volume comply fully with the ANSI standard. To
produce an ANSI-standard volume, you must write an actual file or a
null file on the tape. You can use the following command line to do
this:
PIP>ddnn:DUMMY=NL:

On multiuser protection systems, you can initialize a volume only on
allocated, private devices (that is, a device you have allocated). On
RSX-llM systems that do not support multiuser protection, a user must
be privileged to initialize a volume.

Selecting appropriate values for the command parameters requires an
in-depth
knowledge
of Files-11.
Refer to the IAS/RSX-11 I/O
Operations Reference Manual for details of the Files-11 disk and ANSI
magnetic tape structures.
Format:
INI[TVOLUME] ddnn: ["]volume-label["] [/keyword(s)]
Note that you can use a hyphen (-) as the last character on a
line to extend the INI command line when selected keywords cause
it to exceed 80 characters (or whatever buffer size has been
specified
for the terminal).
You can use any number of
continuation lines, but the total command line cannot exceed
512(10) characters.

ddnn:
The device unit name and number of the volume to be initialized.

3-78

MCR COMMANDS

INI (Cont.)
["]volume-label["]
The volume label. This may be up to 12(10) characters in length
for disk and DECtape, and up to 6 characters for magnetic tapes.
The label identifies the volume and must be specified.
For magnetic tapes, the volume label is usually a reel number
that uniquely identifies the tape. The number is assigned by the
installation and, according to the ANSI standard, cannot be
duplicated within an installation.
When you specify a volume label for the magnetic tape, you can
use the following characters: the uppercase letters A through Z,
the digits 0 through 9, and the following special characters:
<space>

" % & I

(

)

* + , -

• I

: < => ? ;

To use a label that contains a special character, enclose the
label in quotation marks ("label"). To use a quotation mark in a
label, you must use two quotation marks within the quoted string.
For example, the label T"l% has to be specified in the command
line as "T""l%". Any lowercase letters specified in a volume
label are converted to uppercase before any operations are
performed on the volume.
/keyword(s)
The specifications for various characteristics
volume to have upon initialization.

you

want

the

Keywords:
/ACCESS="character"
Allows the owner of a magnetic tape volume to specify the
access protection for the volume. INI places "character" in
VOLl (the accessibility field), which is usually blank.
Legal values for "character" are the uppercase letters A
through Z, the digits O through 9, and the following special
characters:
<space> ? " % & '

(

)

* + , - • I : < = > ?

The default value for "character" is a space.
Note that if any nonblank character is specified,
privileged user will be able to mount the volume.

only

/BAD=[option]
Indicates that bad-block processing is to be included in the
volume initialization.
Consequently, bad blocks on the
volume will be marked as in-use and cannot be allocated to
files.

3-79

MCR COMMANDS

INI (Cont.)
The brackets surrounding each option
The options are:

are

required

syntax.

[MAN]

Accept a bad block list specified
terminal.

[AUTO]

Read the bad-block descriptor file on the
last track of the volume created by the
manufacturer's diagnostic routines or the
Bad Block Locator Utility (BAD).

[NOAUTO]

Ignore the bad-block descriptor
perform no bad-block processing.

[AUTO,MAN]

Read the bad-block file and, when done,
accept blocks specified from the terminal.

[OVR]

Include the last track in the BADBLK.SYS
file.
This option assumes that the bad
block file is located on the last good block
before the last track. The option is only
valid
for
devices
that
contain
manufacturer-recorded bad block data in the
last tracks (that is, DL:-, DM:-,
and
DR:-type devices).

[OVR,MAN]

Override
the
manufacturer's
bad-block
descriptor file and accept blocks specified
from the terminal.

If the command line specifies [MAN],
blocks as follows:

INI

from

file

prompts

for

the

and

bad

INI>LBN (S) =
Bad blocks can then be entered in the format;
blocknum:number
where blocknum specifies the bad block number and number
specifies the number of sequential bad blocks beginning at
blocknum.
INI requires the colon when you specify a sequence of bad
blocks=
Both blocknum and number default to decimal unless
preceded by a pound sign (#).
To specify a single block, simply enter the block number and
omit the colon.
To specify a sequence of bad blocks, separate each series of
blocks with a space, tab, or comma.
For example, the
command line:
INI>LBN(S}=l00:2,3,200:100,45:1
enters blocks 100, 101, 3, 200 through 299, and
blocks.

3-80

bad

MCR COMMANDS

INI (Cont.)
A null line (pressing the RETURN key in response to the
prompt)
displays the bad blocks. The first number in the
display represents the beginning block of the sequence; the
second number is the number of bad blocks in the sequence.
(Note that the numbers are decimal.)
To terminate bad block
ESCAPE key.

input,

type

CTRL/Z

press

the

The default option is /BAD=[AUTO].
INI obtains the bad
block information from the manufacturer-recorded bad-block
descriptor file located on the last track of an RK06/07,
RLOl/02, or RM02/03/05/80/RP07 disk.
!NI also searches the
last track for a bad-block descriptor file created by the
BAD utility.
~

/DENS=density
Sets the bit density (bits per inch or bpi)
of a magnetic
tape loaded on a TE16, TU16, TU45, TSll, TSVOS, TU80, TU77,
or TU78 tape drive. Legal keyword values are:

/DENS=800
/DENS=l600
/DENS=6250
/DENS=HIGH
/DENS=LOW
Defaults:
/DENS=6250 for TU78 volumes
/DENS=l600 for TSll/TSV05/TU80 volumes
/DENS=800 for all others.

The /DENS keyword checks the density of a floppy disk in an
RX02 drive or of a tape on a TS11/TSV05/TU80 drive.
If a
/DENS value is specified, the drive density is compared to
the keyword value for consistency.
If a /DENS value is not
specified, no consistency check is performed and the volume
is initialized at its current density.
/EXT=block-count
Specifies the number of blocks by which a file is to be
extended when the file has used all of its allotted space.
Legal values for block-count range from 1 through 255(10).
Default: /EXT=S.
Note that if you specify /EXT=O, no files
(including the system files) can be extended. Therefore,
although there may be free space on the disk volume, unless
there are also free file headers, new files cannot be
created on the volume.
(If there are no free headers and
the index file cannot be extended, no new files can be
created.)

3-81

April 1983

MCR COMMANDS

INI (Cont.)
/FPRO=[system,owner,group,world]
Specifies the default protection for files created on the
volume being
initialized.
Access codes consist of four
4-code groups in the access rights word as follows:
R W E D -

Read
Write
Extend
Delete

In each instance, the absence of the code
user class is denied the access right.

means

that

the

The user classes
(system, owner,
group,
world)
are
positional.
That is, the location of the word in the string
defines the user class to whom the code applies. The order
is:
(system, owner, group, world]
The square brackets are required syntax.
Substitute an asterisk (*) for the access codes to force the
default value for a specific class.
Default file protection:

/FPRO=[RWED,RWED,RWED,R].

/INDX=index-file-position
Specifies the logical block number for the index file.
The
keyword can be used to force the index file, the Master File
Directory (MFD),
and
the storage allocation file
to a
specific volume location, usually to minimize access time.
Four possibilities are available:
BEG

Place the index
volume.

MID

Place the index file at the middle of the volume.

END

Place the index file at the end of the volume.

BLK:nnn -

Place the
number.

index

Defaults: /INDX=MID
(disk
DECtape II, and MLll).

file

the

devices),

beginning

the

specified

/INDX=BEG

the

block

(DECtape,

/INF=initial-index-file-size
Specifies the number of file headers to allocate initially
in the index file.
The five system files (INDEXF.SYS,

BITMAP.SYS, BADBLK.SYS, CORIMG.SYS, and 000000.DIR) are
included in the value for /INF.

3-82

not

MCR COMMANDS

INI (Cont.)
Defaults
DECtape
DECtape II
RA60
RASO

RA81
RC25/RCF25
RD51
RFll
RK05
RK06
RK07
RLOl

RL02
RM02/RM03
RM05
RM80
RP02
RP03
RP04/RP05
RP06
RP07
RS03/RS04
RX01/RX02
RX50
MLll

16
16
12308
7314
51699
1565
602
16
147
834
1654
314
629
4049
25593
7461
1230
2460
5283
10478
51699
16
16
16
varies with disk size

The maximum number of file headers that can be allocated to
a volume is either determined by the value specified with
the /MXF keyword or is defaulted.
The default number
is
based on the size of the volume (see the description of /MXF
for the calculation). The maximum number of file headers
determines if the volume will have a 1-, 2-, or 3-header
index file.
You need to determine the maximum number of file headers
allowed on the volume before you can calculate the number of
headers that will be preallocated initially. The number of
preallocated file headers is determined by either the value
you specify with /INF or a formula that uses the value you
specify with /MXF.
The following list gives the three
general formulas (one for each type of index file):

1-header index file
headers = maximum/2
headers

The initial number of preallocated
headers.

maximum

The maximum number of
~ith /MXF).

files

file

(specified

If headers is less than 100(10), INI preallocates 16(10)
file headers for your volume.

2-header index file
headers= maximurn/2 or 25593(10), whichever is larger

3~83

April 1983

MCR COMMANDS

INI (Cont.)
3-header index file
headers= maximum/2 or 51699(10), whichever is larger
See the description of the /MXF keyword for more information
on multiheader index files.
/LRU=directory-count
Specifies the approximate number of directories that will be
accessed simultaneously.
The FllACP maintains a list of the
most recently used directories.
The value specified for
/LRU sets the number of entries in this list.
In general,
directory operations can be speeded up significantly by
increasing the number of entries.
If a directory appears in the list, no disk I/O is required
for
finding the directory in the Master File Directory
(MFD).
In addition, directory operations do not require the
directory file header to be read.
Legal values for directory-count range from 1 through
127(10).
Note that increasing the value for /LRU increases
the number of File Control Blocks
(FCBs)
used and may
increase
the
amount
of system pool used.
See the
appropriate system generation manual for more information.
Also note that if you specify /LRU=O, the FllACP will not
keep a
list of directories. This is not recommended and
could have an adverse effect on system efficiency.
Default:

/LRU=3

/MXF=f ile-count
Specifies the maximum number of files allowed on the disk
volume.
This number corresponds to the number of file
headers in the voiumeis index file (see the description of
the /INF keyword).
The value for /MXF includes the five
system files and must be less than or equal to the number
specified for
the device in Table 3-2.
In general, for a
disk of size N, the default number of files is calculated as
follows:
default-MXF = (((N-((N+4095.)/4096.)+9.)*127.)/258.)
The value also decides if the volume will be a Files-11
level 401 or 402 volume.
Level 402 volumes will have a
multiheader index file and allow up to 65,500 files on them.
!NI creates the multiheader index file and modifies the
volume's home block automatically if the value specified is
greater than 25,593.
(If 65K index file support is not
specified for the IN! tas~, the largest value allowed for
/MXF is 25,593.
With 65K support, the largest value is
65,500.) Note that such volumes are not backwards compatible
from RSX-llM V4.0 or from RSX-llM-PLUS V2.0.
IN! issues a
warning message about the incompatibility when it creates a
structure level 402 volume.

3-84

MCR COMMANDS

INI (Cont.)
Table 3-2
Number of Files Allowed on Volumes

Device

Theoretical
Maximum
Value

Default
Value

DECtape
DECtape II
RA60 disk
RASO disk
RA81 disk
RC25/RCF25 disks
RD51 disk
RFll disk
RK05 disk
RK06 disk
RK07 disk
RLOl disk
RL02 disk
RM02/RM03 disks
RM05 diskl
RM80 disk
RP02 disk
RP03 disk
RP04/RP05 disks
RP06 disk
RP07 diskl
RS03 disk
RS04 disk
RXOl disk
RX02 disk
RX50 disk
MLll disk

Maximum
Number of
Index
Headers
I

278
34
1
247
30
1
65500
24617
3
65500
14629
3
65500
54815
3
25045
3130
1
9633
1204
1
499
62
1
2357
294
1
13344
1668
1
26466
3308
2
5034
629
1
10074
1259
1
64798
8099
3
65500
30781
3
65500
14923
3
19680
2460
1
39365
4920
2
65500
10567
3
65500
20956
3
65500
62007
3
499
62
1
1003
125
1
238
29
1
481
60
1
388
48
1
varies with size of disk

Default
Number of
Index
Headers
I

1
1
1
1
3
1
1
1
1
1
1
1
1
1
2
1
1

1
1
1
3
1

1
1
1
1

1. Not backwards compatible by default.
NOTE
A
Files-11
volume
requires
five
files -- INDEXF.SYS,
BITMAP.SYS,
BADBLK.SYS,
CORIMG.SYS, and 000000.DIR -- to create the disk
structure
(see
the IAS/RSX-11 I/O Operations
Reference Manual).
Thus, the /MXF value must be
computed by the maximum number of user UFOs and
files plus the five files required for the Files-11
structure.
/OWNER=[g,m] (disks, DECtapes, and magnetic tapes)
/OWNER="owner" (magnetic tapes only)
Specifies the owner of the volume.
It is similar to /UIC,
but for magnetic tapes allows you to use a syntax other than
[g ,mj. iOWNER=~~owner!! allows yuu to change the entire
"owner identifier" field in the volume label block if this
is necessary for interchange with other systems.
3-85

April 1983

MCR COMMANDS

INI (Cont.)
/PRO=[system,owner,group,world]
Specifies the default protection for a volume. Access codes
consist of four 4-code groups in the access rights word, as
follows:
R WC D -

Read
Write
Create
Delete

In each instance, the absence of the code
user class is denied the access right.

means

that

the

/PRO=[RWED,RWED,RWED,RWED].

/UIC=[group,member]
Specifies the owner of the volume.
Legal group and member
numbers range from 1 through 377(8). The square brackets
are required syntax.
Default:

/UIC=[l,l)

/VI

•

Lists all of the IN!
specified volume •

keywords

and

their

values

for

the

/WIN=retrieval-pointer-count
Specifies the number of mapping pointers to be allocated for
file windows. A file window consists of a number of mapping
pointers and is stored in memory when the file is opened.
(See the IAS/RSX-11 I/O Operations Reference Manual for a
description
of
--mapping
pointers.)
The
retrieval-pointer-count must be 1 through 127(10).
Default:

/WIN=7.

3-86

April 1983

MCR COMMANDS

INI (Cont.)
Examples:
>INI DKl:ICTSVOL2/UIC=[2,5]/INDX=BEG/FPRO=[RWED,RWE,RW,R]
The INITVOLUME parameters used in the example are:
DKl:

Device unit

ICTSVOL2

Volume label

/UIC

User
Identification Code
owner:
group=2, member=5

/INDX=BEG

Index file location, forced to beginning of
volume

/FPRO

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

the

volume

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

)INI DKO:TEST/EXT=lOO./VI

** Volume information for DKO: **
Label
/Bad
/Cha
/Ext
/Fpro
/Indx
/Inf
/Lru
/Mxf
/Pro
/Uic
/Win

TEST
[Auto]
[]

100.
[RWED,RWED,RWED,R]
Mid
147.
3.
294.
[RWED,RWED,RWED,RWED]
[ 1, 1]
7.

Theoretical maximum files

2357.

Command Error Messages:
INI -- ALLOCATION FOR SYS FILE EXCEEDS VOLUME LIMIT
The system was unable to allocate a
system
specified block because of
intermediate
end-of-volume.

file
from
the
bad blocks or

INI -- BAD BLOCK FILE CORRUPT - DATA IGNORED
Although automatic bad block recognition was selected,
the
bad block data on the disk was not in the correct format and
was therefore ignored.

3-87

MCR COMMANDS

INI (Cont.)
INI -- BAD BLOCK FILE FULL
The disk had more than 102(10) bad regions on it.
INI -- BAD BLOCK HEADER I/O ERROR
An error was detected in writing the bad-block file header.
INI -- BLOCK(S) EXCEED VOLUME LIMIT
The specified block (or blocks) exceeded the
of the volume.

physical

size

INI -- BOOT BLOCK WRITE ERROR
An error was detected in writing the volume boot block.
INI -- CHECKPOINT FILE HEADER I/O ERROR
An error was detected in writing the checkpoint file header.
INI -- COMMAND I/O ERROR
INI encountered an I/O error while reading the command line.
INI -- COMMAND TOO LONG
The command,
including continuation
maximum length of 512(10) characters.

lines,

exceeded

number

the

INI -- DATA ERROR
The command specified a bad-block
region that was too large.

contiguous

INI -- DEVICE NOT ALLOCATED TO THIS TERMINAL - ddnn
The command line specified a private device that was
allocated
to a terminal other than the one from which the
command was issued.
INI -- DEVICE NOT IN SYSTEM - ddnn
The command line specified
system configuration.

device

not

the

current

!NI -- DEVICE NOTMOONTED FOREIGN
Or1 RS)C-llM-J;'LOS1 a volupie mus.t he
rnoun~ed . forei<jn . (M?UNT
/FORJ l:>ef0:fi'e ·it c(ln. be. iJ1ltialtzea· (or .mqdified ·by HOME}.
'·

On RSX~I.I~1.· a vo·lfj.n1~ c~p.>pe

•••

•

unmquntea·· or•· 1Jlol1ntea· ~or~fgn~

INI -- DEVICE NOT READY - ddnn
The command line specified a device that was not ready
up to speed) •

3-88

(not

MCR COMMANDS

INI (Cont.)
INI -- DEVICE OFFLINE
The specified device is in
on-line.

the

system

but

not

presently

INI -- DEVICE WRITE LOCKED - ddnn
The command line specified a volume that was write-locked
and therefore could not be initialized as a Files-11 volume.
INI -- DISK IS ALIGNMENT CARTRIDGE
The last track on an RKOn/07, RLOl/02, or RM02/03/05/80/RP07
identified the volume as an alignment cartridge, which
cannot be initialized as a Files-11 volume.
An alignment
cartridge
is specifically formatted
for aligning disk
read/write heads.
INI -- DRIVER NOT LOADED
The command line specified a device for which the driver has
not been loaded.
INI -- DUPLICATE BLOCK{S) FOUND
INI attempted to define a block as bad that had already been
defined as such.
INI -- FAILED TO ATTACH DEVICE - ddnn
INI could not attach the specified device.
INI -- FAILED TO READ BAD BLOCK FILE
The command was unable to read
from
the
last
track
of
RM02/03/05/80/RP07 disk.
INI

the
an

bad block information
RK0f1/07,
RLOl/02,
or

FAILED TO READ MANUFACTURER'S BAD SECTOR FILE

A disk read {hardware} error occurred when INI attempted

to
read
the
manufacturer-recorded
bad block data on a
last-track device.
Reenter the command line and include the
/BAD=OVR option.

INI -- FAILED TO READ SOFTWARE BAD SECTOR FILE
The software-detected bad sector file could not be read.
Reenter the command line and include the /BAD=OVR option.
INI -- HOME BLOCK ALLOCATE WRITE ERROR
While INI was overwriting a bad
error occurred.

home-block

area,

INI -- HOME BLOCK I/O ERROR
An error was detected in writing the volume home block.

3-89

write

MCR COMMANDS

INI {Cont.)
!NI -- ILLEGAL ARGUMENT VALUE
This message can occur for one
reasons:
The value specified with
The value specified with
The value specified with
the device type.
The value specified with
The value specified with
!NI

the

following

/EXT was greater than 200(10).
/INF was less than 16(10).
/INF or /MXF was too large for
/LRU was greater than 127 (10).
/WIN was greater than 127 (10).

ILLEGAL KEYWORD VALUE
The value you specified with the keyword is illegal.
the description of the keyword for the legal values.

Check

IN! -- ILLEGAL UIC
The UIC you specified with the /UIC keyword is not a valid
one or is in an incorrect format.
Legal values for U!Cs are
1 through 377(8) and are in the format [g,m].
·
!NI

INDEX FILE BIT MAP I/O ERROR
An error was detected in writing the index-file bitmap.

IN! -- INDEX FILE I/O ERROR
An error was detected in writing the index-file header.
IN!

I/O ERROR ON DEVICE ddnn:

A fatal hardware error occurred on the specified device.
!NI

I/O ERROR SIZING DEVICE - ddnn
The system encountered an I/O error
disk.

while

sizing

RFll

!NI -- MAGTAPE LABEL MUST BE SPECIFIED
The command attempted to initialize a magnetic tape
specifying the required volume label.

without

INT -- MAGTAPE DEVICE ERROR - ddnn
While positioning the magnetic tape, the system
an I/O error.

encountered

!NI -- MAGTAPE WRITE ERROR - ddnn
While writing to the magnetic tape, the
an I/O error.

3-90

system

encountered

MCR COMMANDS

INI (Cont.)
INI -- MANUFACTURER'S BAD SECTOR FILE CORRUPT
The manufacturer-recorded bad block data on a last-track
device is in an inconsistent format.
Reenter the command
line and include the /BAD=OVR option.
INI -- MFD FILE HEADER I/O ERROR
An error was detected in writing the Master
(MFD) file header.

File

Directory

INI -- MFD WRITE ERROR
An error was detected in writing a block in the Master
Directory (MFD).

File

INI -- MUTUALLY EXCLUSIVE SWITCHES SPECIFIED
The keywords /ACCESS, /OWNER, and /UIC cannot
in the same command line.

specified

INI -- NO BAD BLOCK DATA FOUND
Although automatic bad-block specification was selected, no
bad-block file was found on the volume.
This is only a
warning;
INI continues and initializes the volume.
INI -- NOT FILE STRUCTURED DEVICE
The system
device.

does

not

support

Files-11

the

specified

INI -- NULL FILE HEADER I/O ERROR
An error was detected in writing null-file
index file.

headers

the

INI -- PREALLOCATED TOO MANY HEADERS FOR SINGLE HEADER INDEX FILES
The number you specified with the /INF keyword was greater
than 25598(10);
therefore, the volume would have to have a
multiheader index file.
INI -- PREALLOCATION INSUFFICIENT TO FILL lST INDEX FILE HEADER
The number you specified with the /INF keyword was less than
25588 (10).
INI

PREALLOCATION INSUFFICIENT TO FILL lST AND 2ND INDEX FILE
HEADERS
The number you specified with the /INF keyword was less than
51694 (10).

3-91

MGR COMMANDS

INI (Cont.)
INI -- PRIVILEGE VIOLATION
This message can occur for the following reasons:

INI

•

Only privileged users can use the /OVR keyword.
(This is an error message for the HOME command.)

•

Only privileged users can initialize
nonmultiuser protection system.

Only

private

storage

bitmap

PUBLIC DEVICE - ddnn
The command line specified a public
devices can be initialized.

INI

volumes

device.

STORAGE BITMAP FILE HEADER I/O ERROR
A fatal hardware error occurred while
file header was being initialized.

the

INI -- STORAGE BITMAP FILE I/O ERROR
An error was detected in writing the storage allocation file
header.
INI

SWITCH IS NOT LEGAL FOR THIS DEVICE TYPE
A keyword was specified that cannot be used with the
specified device. Check the description of the keyword for
the valid devices.

INI -- SWITCH I$ NOT LEGAL IN THIS MODE
You attempted to use HOME keywords and/or their options with
the INI command.
INI -- SYNTAX ERROR
This message can occur for the following reasons:
•

The value specified with the
more than one character long.

/ACCESS

keyword

was

•

The volume label for an ANSI magnetic tape contained
an invaiid character.

•

Illegal syntax was used during the manual
bad block numbers.

input

••• HOM

INI -- THIS PROGRAM MUST BE INVOKED AS AN MCR FUNCTION
The task must be installed with
••• INI.

3-92

the

task

name

MCR COMMANDS

INI (Cont.)
INI -- UNDEFINED DENSITY SELECTION
The command line specified an illegal density value.
INI -- UNIT DOES NOT SUPPORT 800 BPI
The command line specified 800 bpi for a drive that does not
support 800 bpi.
INI -- UNIT DOES NOT SUPPORT 1600 BPI
The command line specified 1600 bpi for a
not support 1600 bpie

drive

that

does

drive

that

does

INI -- UNIT DOES NOT SUPPORT 6250 BPI
The command line specified 6250 bpi for a
not support 6250 bpi.

INI -- UNIT DOES NOT SUPPORT HIGH/LOW DENSITY SELECTION
The command line specified HIGH or LOW density for a device
for which the /DENS HIGH and LOW options are undefined.
INI -- UNIT DOES NOT SUPPORT DENSITY SWITCH
The command line specified multiple densities for
that does not have multiple density capability.

device

INI -- UNIT IS NOT AT LOW DENSITY
The command line specified that a floppy disk in an RX02
drive be initialized at low density, but the floppy was
formatted at high density.
INI -- UNIT IS NOT AT HIGH DENSITY
The command line specified that a floppy disk in an RX02
drive be initialized at high density, but the floppy was
formatted at low density.
INI -- VALUE OF (INF + 5) EXCEEDS /MXF
The value specified with the /INF keyword plus 5
(for the
five system files)
is greater than the maximum number of
files specified with /MXF.
INI -- VOLUME MOUNTED FILES-11
An attempt was made to initialize a mounted Files-11 volume.
Mounted Files-11 volumes cannot be initialized.

··rRsx;..;IlM•P:r..us· sy~t:ems only~ f · 1'he ·commano

line

that was···· mo~nted . • . for~ig.n, but <with
inH.ializ~.· . ~ yolunte>on RSX,_.llM-PLUs,. you .canl'lot
ACP name when the volume. is. mounted as foreign.

device

3-93

MCR COMMANDS

INI (Cont.)
INI -- VOLUME NAME TOO LONG -

(volume name)

The command line specified a volume label that exceeded 6
characters for magnetic tape devices or 12(10) characters
for disk or DECtape devices.
INI -- WARNING -- BLOCK 0 IS BAD
Block 0 of the specified volume, the boot block, was bad.
Therefore, a bootable image cannot be placed on this volume.
This is only a warning;
INI continues and
initializes the
volume.
INI -- WARNING -- THIS VOLUME IS NOT BACKWARDS COMPATIBLE
INI has created a structure level 402 volume because the
value specified with the /MXF keyword was greater than
25,593.
Level 402 volumes cannot be used on versions of
RSX-llM previous to V4.0 or on RSX-llM-PLUS Vl.O.

3-94

MCR COMMANDS

INS
INSTALL (P)
The INSTALL command makes a specified task known to the system.
An
installed task is dormant (not active) until the Executive receives a
request for it to run.
INSTALL accepts optional keywords that provide
parameters that were not specified when the task was built or that
override previously specified parameters.
When you install a task, the system creates a Task Control Block (TCB)
for
the task in a memory-resident table called the System Task
Directory (STD).
The task parameters contained in the TCB enable the
system to run the task when requested to do so by an MCR command or a
system directive.
You cannot run a task until it has been installed
(see Section 2.5).
{Note that the RUN command has an option that
automatically installs and removes a task before and after running
it.)

A TCB contains both the address of the load-device Unit Control Block
(UCB)
and the Logical Block Number
(LBN) of the task image file.
Because task image files are contiguous, the Executive can load the
task
image in one transfer when an MCR command or system directive
requests an installed task.
(However, if the task is greater than 32K
words, loading requires more than one transfer.)
When you install a task in a virgin system, the system stores the task
image file's LBN in the task header. When the system is saved, the
SAVE task places the file identification, rather than the file's LBN,
in the TCB.
Then when the system is rebooted, it opens the task file
and stores the new current LBN of the task in the TCB.
If a task has
been deleted, the system cannot open the task file when the system is
rebooted.
The system then automatically removes the task's TCB from
the STD.
A saved system does not retain the physical addresses of installed
tasks.
The Disk Save and Compress (DSC) and Backup and Restore (BRU)
utilities can compress and copy a disk containing a saved system, thus
moving the task files to different physical locations.
However,
because the TCB entries contain task file identifications rather than
LBNs, the system can function normally when it is rebooted.

Format:
INS [TALL]

($] filespec [/keyword (s)]

f ilespec
The file specification in the form:
ddnn:[g,m]filename.type;version

3-95

MCR COMMANDS

INS (Cont.)
The type defaults
remaining fields.

TSK;

standard

defaults

apply

the

When you· specify$ in the command line, ddnn: defaults to LB:,
and [g,m] defaults to the current system UIC (usually, [1,50] for
an unmapped system and [1,54] for a mapped system).

Note that if LB: has been reassigned to another device and that
device's system UIC contains privileged tasks built for another
system, your system will crash.
Keywords:

· _._. ·. <. · ··<•> > ·>
)'"ii <·•·..· < \_ .·.· •·••·• . • . ·.·.·"·•• • .
.·/•c·:
>:. ·.)
·; :.;:.r ..1;(RSX..-llM-PLUS _mQ.l~iproces~o:r: systems onl_y.)_. ~.llQ~s

~l~'.f'~rc~x,.:ua.iJ
•<

>_.

.•.... ·.·•··

YQU

· ·:?pec:ify the ·specific_ respurc.es_ -(affil'}ity)·_·. -.req'(J~red __ forO:t:ask·
'"··t·execl.l;t.ion. _ . Th~ .Siq~a;re hrp.ckets a;r~. ·required -~yrita.x.: ·-•· _L~:ga:l

· .:valu~s _. fior_ tne _.processor: specifi··cat:.iion (x).___ are/\,: B, q, 'and
;p.< ~egalJ .. valµe~;·for. Ut{J:·iBUS run -~Peoi·.ficat.ion$f.(~h are E·,: . F,
H, .Ji, K, ;~., M;,; ·~;(:( Pt! ~-'
and T.
t
· i:.~g;j·7
1
: ;
; I r
+•; :; .when :~<>.u •§p
fth,e. /;A:...•e:~q!r~, t.~.ELi•s.ta1lie.d 'task x+.uns
1

f'"·~+s:'.·~-Rr+1~:
:· . f»n ,, i~~~'-t*·;+ ~·®1~~-~~~i··i•i~Q;;.
· . . . t;:Qtl.}l.~Oted; ..;.: ... '..> '. .... ;;..: .... ,....... ....
. ,.,,.b.?{~,,\~n~~-:,i-~Q~~'
.. , . ,.,,.
... , ...

sa,l~-i-~~l t·~~~e·:f~!:~

/CKP=option
Specifies whether or not a task will be checkpointable. The
options are YES and NO.
If you specify /CKP=YES {the
default for checkpointable tasks), checkpointing is allowed.
If you specify /CKP=NO, checkpointing is disabled for the
task.
The /CKP keyword overrides the /CP switch specified at
build.

task

On systems that support the dynamic allocation of checkpoint
space, the task image file does not need to contain
allocated checkpoint space. The presence of the /CKP=YES
keyword instructs the system to allocate checkpoint space,
when required, for the task from a checkpoint file.
(See
the
ACS
command
for more information on allocating
checkpoint space.)
On _ RS){'"'."llM systems, if .a .task was. built with the /XH switch,
t:.he /CKP keywor<:l is di sabled· for.> the task~

3-%

MCR COMMANDS

INS (Cont.)
/CLI=option
Specifies that the task being installed is a
command
line
interpreter
(CLI).
The options are YES and NO.
You must
install a CLI with the YES option before you can set a
terminal
to that CLI
(SET /CLI) or work with the CLI by
means of the CLI command.
/INC=size
(Mapped systems only.)
Increments
the
address
space
allocated to a
task that runs in a
system-controlled
partition.
The variable size is the number of additional
words of address space to allocate.
The increment is
usually expressed in octal, but may also be expressed
in
decimal by appending a period.
This keyword overrides the EXTTSK or PAR option used at
task-build
time.
Tasks that specify the size of the
partition in which they are
running
use this keyword to
identify how much dynamic space they may allocate to symbol
tables or buffers.
Tasks such as MAC, TKB,
PIP, VFY,
and
AT.
(Indirect) use the space from the end of the task image
to the end of their address space as dynamic memory.
In
effect, the /INC keyword defines the number of words in this
dynamic region.
You cannot extend a task that uses memory-resident overlays.
(See the RSX-llM/M-PLUS Task Builder Manual.)
Default:
Either the size specified at
zero (0).

task-build

time

/IOP=option
Specifies that a privileged task can overmap the I/O page.
The options are YES and NO.
If you specify /IOP=YES,
INSTALL assumes that the task will overmap the I/O page (APR
7)
and,
if the task
is larger than BK words, issues a
warning message.
If you specify /IOP=NO,
INSTALL assumes
that the task does not need to use the I/O page. No warning
message is issued.
/IOP complements the Task Builder /IP switch.
Specifying
/IP
informs
INSTALL
that the task
is
intentionally
overmapping the I/O page.
Default:

/IOP=YES.

/PAR=pname
Overrides the partition name specified at task-build time.
In an unmapped system, the specified partition must have the
same base address as the partition for which the task was
bui 1 t.

3-97

MCR COMMANDS

INS (Cont.)

If the keyword specifies a nonexistent partition, the system
issues a warning message and attempts to install the task in
the GEN partition.
Default: TKB uses the name GEN.
(See the RSX-llM or
RSX-llM-PLUS System Generation and Installation Guide for an
explanation of multiuser system""Cf"efaults.)
/PMD=option
Requests a Postmortem Dump if the task aborts.
The two
options are YES and NO.
If you specify /PMD=YES, a
Postmortem Dump occurs if the task aborts because of an SST
error condition.
If you specify /PMD=NO, no dump is
requested at SST abort time.
To generate a dump, the Postmortem Dump task PMD ••• must be
installed in the system.
This keyword overrides the /PM
switch specified at task-build time.
Default:

Specified at task-build time.

/PRI=number
Specifies the priority for the task. The value range is 1
through 250(10), where 250 is the highest priority. The
standard numbering conventions apply:
octal by default,
decimal if followed by a period.
Default:

/PRI=50.

3-98

MCR COMMANDS

INS (Cont.)

/SLV=option
Specifies slave status for the task.
The options are YES
and NO.
If you specify /SLV=YES, data sent to the installed
task is marked with the terminal number (TI:)
of the task
sending
it. When the installed task receives the data, the
system sets the task's TI:
to that associated with the
data.
This keyword overrides the /SL switch specified at
task build.
If you specify /SLV=NO, the TI:
when the task receives data.

3-99

of the task does not change

MCR COMMANDS

INS (Cont.)

Default:

Specified at task build.

/SYNC=option
(RSX-llM-PLUS multiprocessor systems only.)
Synchronizes
task use of a common.
The options are YES and NO.
This
keyword permits several tasks to share a common and use the
common for synchronization.
If you specify /SYNC=YES for
two or more tasks, only one of the tasks can execute at one
time.
Note that
if one of the tasks becomes blocked, the
others compete to execute.
The /SYNC keyword prevents inconsistent data that occurs as
the result of race conditions.
For example, if two tasks
access a common, t~e /SYNC keyword ensures that only one
task executes at one time.
This prevents the second task
from reading or writing the common while the first
task
is
execcJting.
Default:

/SYNC=NO.

/TASK=taskname
Specifies the name by which the system refers to the task.
Default:
The name specified at task-build time or the first
6 characters of the file name.
(See the RSX-llM or
RSX-llM-PLUS System Generation and Installation Guide for an
explanation of multiuser system defaults.)

/UIC=[group,member]
Specifies the UIC for the task~
The square brackets are
required syntax.
You can also override the UIC with the RUN
command.
The task UIC determines the file-protection class
(system,
owner, group,
world)
to which a
task belongs and thus
directly influences file access.
Note that file protection
may differ from file to file.

3-100

April 1983

MCR COMMANDS

INS (Cont.)
Default:
specified at task-build time.
This
default
applies only to tasks started by a SPWN$, RPO!$, or RUN$
directive or a RUN command that specifies a
time delay
before run time.
Tasks started by typing the name as a
command (for example, PIP and TKB) run under the default UIC
of the terminal from which the command was issued.

3-100.1

April 1983

MCR COMMANDS

INS (Cont.)

Examples:
>INSTALL SCAN
Installs task SCAN.

Priority and UIC are defaulted.

>INSTALL DMl: [l,lll]SCAN.TSK;4/PRI=l03
Installs task SCAN, file type TSK, version 4 on device DMl:,
group number 1, member number 111, with a priority of
103 (8).
>INS MAC/INC=4096./PAR=SYSCTL
Installs task MAC in the system-controlled partition
and increases the task size by 4096(10) words.

SYSCTL

Command Error Messages:
INS -- ADDRESSING EXTENSIONS NOT SUPPORTED
The command tried to install a task with a VSECT
(virtual
section) into a system that does not support the feature.
INS -- BASE ADDRESS MUST BE ON 4K BOUNDARY
The base virtual address of the task was not on a
boundary. This message applies only to mapped systems.

INS -- BASE MISMATCH COMMON BLOCK common-name
The base address of the partition did not match that of
common block.

the

INS -- CANNOT INSTALL PRIVILEGED TASK FROM NON-PRIVILEGED TERMINAL
This message applies to multiuser protection systems only.
A nonprivleged user attempted to install a privileged task.
Only a privileged user can install a privileged task.

3-101

MCR COMMANDS

INS (Cont.)
INS -- CAN'T INSTALL DIRECTIVE COMMON
An attempt was made to install a task in a directive common,
which the system does not support.
INS -- CAN'T INSTALL EXECUTIVE COMMON
The executive commons (on systems that support executive
partitions)
cannot be installed at run time.
The commons
must be installed with the VMR INSTALL command.
(See the
RSX-llM/M-PLUS System Management Guide).

INS -- CHECKPOINT AREA TOO SMALL
The area allocated for checkpointing the task was smaller
than the partition into which the task was being installed.
This message applies only to systems that do not support the
dynamic allocation of checkpoint space.
INS -- CHECKPOINT SPACE TOO SMALL, USING CHECKPOINT FILE
This is a warning message only.
The checkpoint space
allocated
in the task image file is too small for the size
of the task (usually because of the /INC keyword).
The
system supports the dynamic allocation of checkpoint space
and will therefore use a checkpoint file to contain the
checkpointed task.
INS

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

INS -- COMMON BLOCK NOT LOADED common-name
The specified common block was linked to the task but had
not been installed in the system.
Install the common block,
then install the task.
INS -- COMMON BLOCK OCCUPIED
An attempt was made to load a task into a common block
was already occupied.

that

INS -- COMMON BLOCK PARAMETER MISMATCH common-name
Parameters of a common block did
task's label block.

not

match

those

the

INS -- COMMON BLOCK SEGMENT COUNT ERROR
The command installed a resident library with overlays, but
the number of overlay segments specified in the task header
was different from the number specified in the segment
descriptions.

3-102

MCR COMMANDS

INS (Cont.)
INS -- EXTERNAL HEADERS NOT SUPPORTED
INSTALL first checks to see that the task was built with /XH
specified.
Then,
it checks the feature mask bit of the
system to see if external headers are supported.
When
external header support is not included in the system, you
cannot install a task with an external header.
INS -- FILE NOT CONTIGUOUS
An attempt was made to install a noncontiguous task
file.
Task images can only be contiguous files.

image

INS -- FILE NOT PROPERLY CLOSED
An attempt was made to install a file that was not properly
closed
(that is, locked). Since the file is locked, it is
probably corrupted.
Install a new copy of the file.
INS -- FILE NOT TASK IMAGE
Data in the label block was not correct, indicating that the
file was not a task image.
INS -- FILE PROTECTION VIOLATION
An attempt was made to install a task to whose image file
you do not have proper access. You must have read access to
install a task image file.
INS -- ILLEGAL DEVICE ddnn:
The device specified at task build by the assign
(ASG)
option does not exist in the system. This is a warning
message only. The task is installed.
INS -- ILLEGAL DEVICE/VOLUME
The specified device was not a valid task-residence device.
INS -- ILLEGAL FIRST APR
(Mapped systems only.) A privileged task, built to run using
APR 4 or 5 as its base, was too large. Using APR 4, th~
task was larger than 12K; using APR 5, the task was larger
than 8K.
If the Executive has been built to support 20K of address
space, APR 5 is the only valid base APR for tasks mapping
into the Executive. A privileged task that does not map
into the Executive must use APR 0 as its base.
(See the
RSX-llM/M-PLUS Task Builder Manual for a description of the
/PR switch.)
INS -- ILLEGAL PRIORITY
The value of the priority specified in the command
of range (that is. not l through 250 decimal)~

3-103

was

out

April 1983

MCR COMMANDS

INS {Cont.)

INS -- LENGTH MISMATCH COMMON BLOCK blockname
The length parameter for the common block, as described in
the label block for
the task
image, did not match the
corresponding length parameter defined in the system.
A
task's label block data must match system data for that task
before it can be installed.
INS -- LOW POOL, TRY LATER
(Systems with pool monitoring support only.) During low pool
conditions,
the Pool Monitor Task
(PMT ••• )
temporarily
disables
install-run-remove
and
/CMD
requests
for
nonprivileged users.
INS -- NO CHECKPOINT SPACE, ASSUMING NOT CHECKPOINTABLE
This is a warning message only.
The command attempted to
install the task as checkpointable, but the task was not
built as checkpointable and therefore had no checkpoint
space allocated in its task image file.
Because the system
does not support the dynamic allocation of checkpoint space,
it considers the task not to be checkpointable.
INS -- NO CHECKPOINT SPACE OR DYNAMIC CHECKPOINT FILE
An attempt was made to install either an external header
task
(/XHR=YES) or a checkpointable task (/CKP=YES) , but no
checkpoint space or dynamic checkpoint file was available
for it.
INS -- NO ROOM AVAILABLE IN STD FOR NEW TASK
No dynamic memory was available to enter the Task Control
Block
(TCB)
in the System Task Directory (STD) • The task
could not be installed.

3-104

MCR COMMANDS

INS (Cont.)
INS -- NOT ENOUGH APRS FOR TASK IMAGE
(Mapped systems only.) The Task Builder allows the user to
specify the virtual base address of a task image as a
multiple of 4K.
Privileged tasks that access the Executive
start
at either virtual address 100000{8)
for a 16K
Executive or at virtual address 120000(8)
for a
20K
Executive.
If the virtual base address is set too high,
there are not enough APRs remaining to map the task image.
(See the RSX-llM/M-PLUS Task Builder Manual for information
on privileged tasks.)
INS

PARTITION NOT COMMON
A partition specified for a common area or
defined as a common partition.

3-104.1

library

not

MCR COMMANDS

INS (Cont.)
INS -- PARTITION parname NOT IN SYSTEM, DEFAULTING TO GEN
This is a warning message only.
The specified partition
does not exist, so the system attempts to install the task
in the GEN partition.
INS

PRIVILEGED TASK LARGER THAN 12K
A privileged task was larger than 12K words.
Privileged
tasks on an unmapped system have a maximum size of 12K.

INS

PRIVILEGED TASK NOT MAPPED TO I/O PAGE
A privileged task was larger than SK
and
therefore
overlapped the I/O page. This message occurs if the task is
installed with the /IOP=YES option.

INS -- SPECIFIED PARTITION FOR COMMON BLOCK
An attempt was made to install a task in a common block.
INS -- SPECIFIED PARTITION TOO SMALL
The task being installed was larger than the partition
which it was being installed.

into

INS -- TASK AND PARTITION BASES MISMATCH
(Unmapped systems only.) The base of the partition
match the base of the task being installed.

did

not

INS -- TASK IMAGE ALREADY INSTALLED
The requested task image, which was checkpointable, had
already been installed. On systems that do not support the
dynamic allocation of checkpoint space, checkpointable tasks
that have checkpoint space allocated can be installed only
once; other tasks can be installed more than once (under
different names).
INS -- TASK IMAGE I/O ERROR
INSTALL could not read the task image
rewrite
the
task
image
header.
write-locked.)

file or could
device
(The

not
is

INS -- TASK IMAGE VIRTUAL ADDRESS OVERLAPS COMMON BLOCK blockname
The virtual addresses reserved for the task image overlap
those reserved for the common block specified in the
message. A corruption of the task image file probably
caused the overlap.

3-105

MCR COMMANDS

INS (Cont.)
INS -- TASK MAY NOT BE RUN
This message can be issued for the following reasons:
1.

An attempt was made to run a CLI task.
CLI tasks
are activated by the system;
they cannot be
activated with the install-run-remove option of the
RUN command.

INS -- TASK NAME ALREADY IN USE
An attempt was made to install a task with the same name
one already in the system.
>·.· ···~·:-:·:,·:· :>·

-:= . '

TASK ·NoT> INSTAtLED. WITH 'ExTERNA·L· HEA:DER

(RSx-!nM-~LUS sy\.'tems bnl;r.J This )s a warnifig message to

in~:lc;ate . t.hat : .the s'pecified ta:sk . ls . . fnstallled :with: .\it.s
header in· pool_ ·(;'the dy·pamic storage r~9d<.ml ..
:T;ASK: REQUIRE~! iS!Y'S'l'EM1 · ,CONT.RQLLED:··_··:PART'.:£TION
'

i !

. ..•. • . • ... :

! . : ]" (,

: .•..· . . . .

:' •..·•....... ·.........·

. .· ...· . ·•.

·: < . •.• :• . '

. . .. (R~X ;1.lr-t· sys~etn~. pnly. 'l <An1 ·attemp·'t was . m.ade . t<), 1 '. i nstalT . a
·+ ·•·jH:t 'T'•'t:a1!k .•· ·-1ttr~tJ: ~- i~si<bpi,·lt ·. ~it.h:· ~xt:e:r:nail· ::be<rde-r: ·•'(·,l:){ii:);rts'1.l'ppoT~ an~"
. ., · "' i:\as

··~::~·;;,; :•lb~

> .•

100

{:~Kli: V8~:, :'t~A' :(FrKP;:;Y~S~··. · ·Spq!:··it~~*~ ·r;:mµ~~
)nrrPP1't~q:l,lleCJ ;pa.r:t:j:t;:j;6g .. ·
<hf'(=:Vi~·;-·d.·.=.'.f\(~'.f~

i·~

: .. · • ···' ..... ;

.·

.· .. :.· .··

~·,.

INS -- TOO MANY COMMON BLOCK REQUESTS
A task made too many requests for common blocks.
limited to seven requests.
INS

A task

TOO MANY LUNS
A task requested more than 255(10) LUNs to be assigned.

TNS

UNDEFINED COMMON BLOCK blockname
A task referenced a common block that had not been defined
in the system.
Usually,
this message indicates that the
task was built for another system.

3-106

MCR COMMANDS

INS (Cont.)
INS

WARNING -- PRIVILEGED TASK OVERMAPS THE I/O PAGE
A privileged task that is mapped into the Executive is
usually also mapped into the I/O page to access the
registers for the KTll and other devices. Many tasks do not
require this access and can use the additional 4K words of
virtual address space for the task image.
This message
warns that a task that may require access to the I/O page
might have grown too large.

3-107

MCR COMMANDS

LOA
LOAD (P)
The LOAD command reads a nonresident (loadable) device driver into
memory and, if necessary, relocates the data base constructs and
interrupt-vector linkages required to allow access to the device.
On
RSX-llM-PLUS
systems,
the task CON constructs interrupt-vector
linkages.
The LOAD command eliminates the need to link infrequently used device
drivers
permanently into the Executive.
(Executive support of
loadable device drivers is a system generation option on RSX-llM
systems but is always included on RSX-llM-PLUS systems.) The result is
the potential for an increase in the amount of system dynamic memory.
You can load drivers that are up to 8K words in
however, that the loadable device driver itself
locations above 4K.

length.
Note,
must map to any

The driver for a device, for example ZY:, can indicate association
with a partition by allocating one word in the driver and labeling it
with the global symbol $ZYCOM. If $ZYCOM is defined in a driver, you
cannot load the driver until you create ZYCOM (LOA writes the PCB
address of ZYCOM into $ZYCOM).
Format:
LOA[D] dd:[/keyword(s)]
dd:
A 2-character ASCII loadable device driver name.
Keywords:
/PAR=parname
Specifies the partition (parname) into which the
to be loaded.

driver

On RSX-llM system~, th.e· s:peci fled' partition
,partition or ,a system..,.cot'ltroHed partition.

All loadable drivers are usually placed in the
same
partition, by convention DRVPAR. This has the advantage of
preventing fragmentation of the GEN partition.
on. RSX..,.llM systems,. tMs c.orivention ·nprm(:ll];y

E;!nsu:res

that

a11 •. •. . : 1.o:;:aap1~: .iiffive~er j f~lt\aI~ < . . J:>tlpw <~ 44~ >i? ... m~ll\oryy·· .(the ·

,q:.~i!JJlJm ~ysrt::em: im~9e.?si.~·e· :.~QI:. t:~,e YS~V'F!}J:.a~k pn .R$X:7"l:~~:}:..·

When the command line omits this keyword, the system loads
the driver into the partition specified when the driver was
built.

3-108

MCR COMMANDS

LOA (Cont.)

/SIZE=parsize
Specifies the minimum size (in words) of the partition into
which the driver is to be loaded. If the partition is
system-controlled, a subpartition will be created at this
size.
parsize is rounded up to the next highest
(octal) words and must be less than 100000.

unit

100

/HIGH
If the partition is system-controlled, /HIGH causes the
driver to be loaded as high in the partition as possible;
absence of /HIGH loads the driver as low in the partition as
possible.
If the partition is not system-controlled, the driver
occupies the entire partition whether or not you specify
/HIGH.
Examples:
>LOAD

MM:

!LOAD TU16 DRIVER (MMDRV)

>LOA

LP:/PAR=DRVPAR

!LOAD LPll DRIVER (LPDRV) INTO DRVPAR

Notes:
•

Rigid instructions for building loadable device-driver tasks
are defined in the RSX-llM or RSX-llM-PLUS Guide to Writing an
I/O Driver.
Note that the system generat1or1 procedures
include provisions to simplify the task building of drivers.

•

It is not possible to make all device drivers loadable.
not all loadable drivers can have loadable data bases.

3-109

", ,...._

n.1..:>v 1

MCR COMMANDS

LOA (Cont.)

•

The LOAD command requires that a driver's TSK and STB files
reside under the system UIC on the system disk (LB:).
For
example, the command
LOA

DT:

requires that the files DTDRV.TSK and DTDRV.STB reside on LB:
under
the appropriate system UIC.
The command SET /SYSUIC
displays and defines the system UIC;
the usual values,
however,
are
[1,50]
for an unmapped system and [1,54] for a
mapped system.
•

The LOAD command does not initiate
space in a partition.

checkpointing

•

The LOAD command requires pool space as follows:

free

If the driver data base is being loaded,
the
needs contiguous pool space equal to its size.

In a mapped system, each interrupt entry in the driver
needs pool space for an Interrupt Control Block (!CB).

If the driver is being
loaded
into a
system-controlled
partition,
the Partition Control Block (PCB) needs pool
space.

data

base

Command Error Messages:
LOA -- CANNOT LOAD/UNLOAD A PSEUDO DEVICE
The device you attempted to load is a pseudo device.
devices do not have drivers.

Pseudo

LOA -- CTB name DOES NOT EXIST

systems only.) The
with the /CTB keyword
resid~nt data base.
(RSX-UM-PLUS

specified

Controller Table name
does not exist in the

LOA ..... _ CTB NAME name IS A DUPLICATE.
(RS}{~liM-PLUS

systems only~)< The loadable data base contains
Controller Table {CTB) wHh a name that is the same as a
C:TB name in the resident data base.
names must be
unique.

LOA .-.;;;.cTB nafue IS NO'f· . ·SUPPORTED BY:DRIYER,.··.NoT··.LoAoEP

(i~s'.}{-:~iM.-PLUS sys£e~s.i(>P,1x~J>Th~

device . . dtiver-'s •. dispatcil

~abl~.··. do~s not: haye ag .the .Controller Table mnentonic.s. that
·the r:est .of the data b<Jse J the DCBs .and CTBsJ •.. irnpl ~es. .thqt

~t~ . •.·.·.has·~·•··•·. · •·. or.·•. the ... · CTB<f.i . ~•··• defective..
A·d~fe.<:.tive·. .·CTB .. may
corrt:aJn<a wrong<nameo~ if:s.lJn.kto tne DC::B may be wrong~
·

3-110

MCR COMMANDS

LOA (Cont.)

LOA -- DEVICE dd:

NOT IN SYSTEM

The data base for the device driver was not in the system or
in the driver's task image.
LOA -- DEVICE NOT MOUNTED
The system device (LB:) was not mounted.
LOA -- DRIVER ALREADY RESIDENT
The specified device driver had already been
permanently resident.

loaded

load

LOA -- DRIVER BEING LOADED OR UNLOADED
The Executive was effecting
unload the driver.

another

request

LOA -- DRIVER BUILT WITH WRONG EXECUTIVE STB FILE
The STB file for the driver was not compatible with the
current Executive.
The task build probably specified an
RSXllM.STB file that was not for the current system.

LOA -- FILE filename HAS ILLEGAL STB FORMAT
The driver's STB file contained an illegal
data record format.

object

code

task

LOA -- FILE filename NOT A VALID DRIVER TASK IMAGE
The driver's task image was either overlaid or
header.

3-111

had

MCR COMMANDS

LOA (Cont.)
LOA -- FILE ddDRV.TSK NOT CONTIGUOUS
The file ddDRV.TSK was not contiguous.
all "task" images) must be contiguous.
LOA

Device drivers (like

ILLEGAL DRIVER TASK APR USAGE
A device driver must be built for APR 5 and must be
than
8K
(for example,
PAR=DRVPAR:l20000:40000).
message applies to mapped systems only.

less
This

LOA -- ILLEGAL VALUE FOR SYMBOL symname IN FILE filename
The symbol symname is defined to an illegal value in file
ddDRV.STB.
This can occur for several reasons, some general
and some specific to individual symbols.
For example,
symbols cannot have odd values, most symbols cannot be
defined as zero, $ddTBL must exist and have a value less
than $ddEND,
and mapped loadable drivers cannot reference
$INTSV.
LOA -- INSUFFICIENT POOL SPACE
The required
available.

amount

system

dynamic

memory

was

not

LOA -- INSUFFICIENT ICB POOL SPACE FOR CPU CPx

There is not enough processor-de.pendent dynamic . rnemory to
allocate an Interrupt Control. Block for the CPU designated
in . the . e:rror. message. . This message . applies only
to
RSX,...llM-',PtUS inultlprocessor, .I- and D~space ..·syst.ems ...
LO.A _;... INTERRUPT VECTOR ALREADY IN USE
(RSX-llM sys~ems on}y.} A drive·r intep~upt v~ctor . p.oes

::Point. to one .. of. the nonsense: in;terr;upt. entr.y: . . po,lntsi~

not

LOA -- INVALID DRIVER DATA BASE AT OFFSET xxxx IN FILE filename
The driver had an invalid data base value at offset xxxx
relative to the symbol $ddDAT.
This can occur for three
general reasons.
1.

An invalid value, for example, D.UCB was odd.

The value for a word is not within the bounds of the
loadable data base.
LOAD produces an error message
citing the offending value.

An element is missing from the loadable data base.
LOAD
attempts to verify one kind of data structure as another
kind.
For example, if a DCB is missing, LUAU tries to
verify the following UCB as the DCB.
LOAD cites the DCB
as being incorrect.
3-112

MCR COMMANDS

LOA (Cont.)

,,:,

:·· . .

(flp~71lf1

syste1ns oqly.J Th~ · i.np·~rruJ?.t.
vector'
address
specffJ~d: in
the driver .a.ata :base :was t()O hig}}: for .the

·:.

Sl1FFffri~· ~.rst.~Jl.l:•
, . '

; : "-'. : : . .: :

: . '.-. ·. .

.. :

. : .

. ..

. :

... '

·..... =.

. .. : : ·.: . ·... ; ·.. : ... ; : :- :::. .. ;

.. . : .

: . ..

. : . . . : .. : : : =.: : . : . '·:.

=.; ' ~ ·.. :: . : . : . : ·.. .. . . . .. ·. :

. . . ' .: .; .'

·. . .•·. .r.ks.•x~j1•.iM~.!)\t·.~.s.:•.:sY:st··~!n:sl·•·····on1•y•····.)·········•.f6.µ·•·.···~•.r•e•····.·. ·a.t}:.•empt•.1•.n9:. .•tC).······•~•.?·~A :tT••.·:.hh•.•. ·•.ee· ·.
:.:.9(~.v.·. ~ }··.•· . . ···~?J:" •. :¢i·.••••.J\1,?\. E>.P.~Y~t· '9~,v19. . ~·•·•: w
. .•. .•. i. th.• .•:Ci .lp?da..b;•. .r.·. <c1.• a. ta J:>. a·s. . <e.·.·.·.·.~

··:·t?P~¢.~·.a1·$.~p<:>~,•·.(K~.~ria.m~J·i."~tli9})·.q~·~:in~s .,.i::h!•.•·•1.Qf:(itJon: ••. ?f

.••t:h$:·

'·•···I<·~J?·i·.•···•ts•··not.·•·:~·~f*r:t!9:··in,•·• tm~·.··J.<:>fA.a.t>1~·~la.t.a..<}>as.~·... · Refer.• •. •to the·
· Rsx+.i1~HJ?tus•xGuicl~ • • th· . • wrttlQg•·•~:;\n •.•.r/o•'·•Drfver.,

:toA.. T°7:•:.~.8~·;.~A.s£1f o'.F:. ·G.~~·:t1em~•·. wttL ·No~ .A¢k.~·~~··~~s•'f1il:~e.
.•:. J.R$x~~i.MfJ?~Qs.·•··sys1:e~t:r•··C)~l,y.~:> ·.:¥tiu ·~I'~·: .a.tke~p)~i:n~'. i1:~ ·10aa ·

the
9ri\i'er · .. l<:)t' .a MAS?E3JJS ·i:ievi·c~ \'iit.h a> loadable data base;; rf
·····~hJ:$• ·'Opeiat.:L<>n ·rs·. ):,.a: ·.1ie·.· •.•s·u.q<t$s·$:f"'ci1I ···two c<>lldit.i'ons.' must .

.exist.:

'..

. i~·

The appr•q'pria·t~ slot in the CTB../{C'(:)nt:ro1lei' T<;~.'ble)··· must

· · exi.sJ::·. · ·

......

····;

·.:·:·: .. ·.·,

. wh~:il'y()~ get 'tl1:i.'$; error me.ss·a9e,

one

of .. these

q.Qes. .. :11e>t::.: ex;Jst:•· 'Rgf.et . to t;l:I~·.R.SX...;l1M:""'l?.L.US· GUli:ie
••art. I/o.· Driver.

LOA -- LOADABLE DRIVER SUPPORT NOT IN SYSTEM
The system generation option to support loadable device
drivers was not chosen or necessary routines are not in the
Executive.
LOA -- OPEN FAILURE ON FILE filename
LOAD encountered
specified file.

error

attempting

open

the

(RSX-llM systems only.} An attempt was made to load a device
driver into a common partition. 'A device driver cannot be
loaded into a commoq partition.

LOA "'.'"- PARTITION/REGION>riame IS A COMMON
(Rsx...:11M...:PLUS systems only.) An attempt was made to load a
device driver into a common partition or region. A device
driver cannot be loaded into a common partition or region.

3-113

MCR COMMANDS

LOA {Cont.)

.:i·/i.i·•·:

·LOA --~>.•PAHTitio~/t(~GfpfN>/naI!l.~·· I~i>~o:r····A··.···coMMON

(•llS){-llM±E>Cqs•···~sY,ptefus••···<>nlf •••).i/.l'bei·sym~<>l $.aa•co~·······•·••·: . ~···s···.·.···.····.··•<:JI()~~ll.y.

·<.in·• .. ·.

deJ.ined . . · ·.
·the·•dl'.'i\{er;;·. ·''I'he, l(artJ.~ion•• ddCOftli existsi/P·~t,·•···i·.~i
·is ·not a c;ommo,r:r · .·.partition o:r regicm;.

i.·.·········.· ......·.<······i·( . .• ·.·.· · · .• · · . · ·.

/ • ·.· ·. ••

•· (RSX~llM..,.PLUS ~ystem::i only-.) ··.You· are. a~tell\pting : \to . load
H

' . ·

driver into a ·partit;:iqn that doeS; .not ;exist. i~ the· system,
o.r LO~D :found .a sY:mbql $xxCOf4: in th,e, dr;iver ·and< the reg~on
xxCOM does not exist in the system .. ·
LOA -- PARTITION parname TOO SMALL
The partition into which the driver was to be loaded was not
large enough to contain it.
LOA -- REGION/PARTITION name IS A COMMON
You have attempted to load a device driver into a common
partition or region. A device driver cannot be loaded into
a common partition or region.
LOA

SYMBOL symname IS DOUBLY DEFINED BY FILE filename
The symbol symname is defined twice in the specified file.
Duplicate symbols are illegal. The driver is not loaded.

LOA -- SYMBOL symname IS UNDEFINED IN FILE filename
The symbol symname was found in the specified file, but
symbol was not defined.

the

LOA -- TASK IMAGE I/O ERROR IN FILE filename
The device is probably write-locked. LOAD could not read
the task image file or could not rewrite the task image
header.

3-114

MCR COMMANDS

LOA (Cont.)
JjQfi ·,;.;.•··,;...······TOO MANY SYMBOLS< OF

THE FORM $x:k'l'M0···1N>FTtE•·· fllenarne

. \.\·:>········· .• < >•···· ........... :.•·>········.. ·<•.·.•·······> ·:····.·.. ·.·

·(RSX~l.l1Y1-:PLVS.·.sy.~te!Ili·· . . <>niy.~J LOA.I) f~····. 9tt:empting .· .. ·.·: t<>...... ¢xt:r~9t:
glp~l)~l . •. .•. <~yrnbt)1s

<>f·· t:h~ f9rin $){x'fMQ.• frp!Il .t:he·. . . ar~ver·\~ .• : $yml;)pl
<l~flI)i<t}pn.fJl~······· Th~re ar.~·. . ·Jl;l<?r.~. ~ymb<?ls of· •this · fo.rm than
- -~-.O~P:.::_·:_·<;.:9.ri:.·.:_· . _::p··+.-:9:~-~·?;~.·:·~
,.. · ·.·... ,
LOA

zi>.:~k~~f~d:•···~····\·kii.a••
. h~~~··; ±•.~4fu~~·tJ·~:~. V~:~f~d~ . ~h~·······.·•ik···· ij~g·.
:' . '. ·\. .: ;·. . ·.-:-.: _.--:,:· .· .· ·.· : _.·:._.·. ··.,: -: ·. . ;·> ·.:
~.:

.·:::_::~: ·.:> ...··~:·:_.::·.>··:_:_: . '. . ··. ·:·: ·...: ... ·. ::':.·:·.:·" '. ·.:.-.<>.·: . .:/:" ·:. >:':- .·._-:-:.....:: .... ·_,_· -"·:· ·.: .: .;:: . ; ...

· · · •·'.· . ··~···<:.ic·~sxl:i.:i~.q~~£qs··:~.Y~#~~$i········.(y~J.y• •.•Jf.• .• xoli:····;~·~·~.•~· . ·. att~'mpted .•···to
<lrJyEf r.·••• .: t:l;.1<:tt:•<•·•.•···•···.•EiJ?'~PtJt~i7·• •;. i~p·. : i.Jilt~.F:F·HPt:.<· ~: .• ye~t:C>X

that

I·o•aa····· a
i s·•··•. . not

·p.qln.t~l'l<il t:p c;1....l'.l??5:~n~~· .lq~e·t:r.qpt: . Ttt~ry. ppi.pt· address~. ··.· ·. Tht'Ei
Ai~l . •. u$ya'.f·1:¥....·. C:(:\:}~·~ed • ·1:Jy ·9 p.r-evipti$ly. Jpa.ded. d(i.'it.er that has:

used this<vect:or-.··..

·•·•·.·.· · ·. ·. · . · .· . ••···. . <· ..............·. · > ·

••····.td¥.n
·~.~·.!3·••·'.0:p·r.r·~ctfy .• ·~:Lo•a~·•~·~· :~.· ~ · ·~· · · · · ~·~i•;~;#·::•.> ·•· · m·~· ·•:· • p•r9l?ie1n ·mu·st······ ·. b.e
.cor·recf:ed ·befor:e the device is b?,:'9.µ9ht on. line:~ ·
'·'.· ·••·••••: ./•.• •.••/•···•>i:•·•··•·.·····•·•2.••·i'•••••. ·••iJ

··;i;{L./>}; . . . .• •.·:• • • •·•.• • · · ·;· ·;: .·.•.• •;• ·•·•

>•••••••·····

·· ··..

>·· ..:. :·.:·.-.·:-.:.:--:.:-'

J40zi' i2.i~~~•~I~G. ~ '!<RB~ hame :r.M~~~;O~;::·.y~·~~~;. nnn TOO <HIGH

{R;;ii~-P~&£~~~tem~ ;~j'~,y'i~~~~~~ atctrnwB7fl. t;o ~<>f<i · a·

iirfv~r·.> ttj~~····· sJ;>eG\ffi~~

ari:~ ·irif~r·J7·<i·J?t:· vector address that

i?-;!··~·~J~r·:t;.li~n··· t:PeJ'li,gp:est ti~t!lll$$Ll:>l'~ :v.e·ct:ot<:adqi.ess.
sys;t;em··~
·

·W}lep ye>µ .... 9~t .·t:hi$

corre:ctly.

You

m~$:$qge,

must

use

~Pf\£?.>

q.as . .·. . . . Jpaded

thg.re:c.on.tiguratjory s~rvlces· tq

~qjt.Ist: ·t.h¢• v$ct(?t.·.(i.q.<;ltg9s.ir1 . . . tpe .. fl.piy~}'." }.l~f::<:>r~•·····•···p;J_clc:i~9
the
on line. {See the RSX~i'JM/M~PLUS System Management

device

Gµide ·. f:oi rnqre<•·iriforrti:apipn p11.··· t;bg.·: ~e¢9n·fig1.rrati9n ser.vtc.gs ..• }
LOA -- WARNING - LOADABLE DRIVER LARGER THAN 4K

Loadable drivers can be up to 8K words in length.
The
driver must explicitly map to any location above 4K words.

3-115

MCR COMMANDS

LUN
LOGICAL UNIT NUMBERS (NP)
The LUN command displays the static LUN assignments for a specified
task.
(Static assignments are those recorded in the task's disk image
file.) The display consists of a list of physical device units in one
column and their corresponding LUNs in an adjoining column.
When the specified task is running, the display does not necessarily
reflect the running task's assignments.
For example, an Executive
directive issued from within the task (ASSIGN LUN) can alter the LUN
assignments.
If the specified task was initiated by the install-run-remove option
of the RUN command, the task has no static LUN assignments.
In this
case, LUN displays the message:
LUN -- TASK NOT IN SYSTEM
Format:
LUN[S]

taskname

Example:
>LUN XKE
TIO:
1.

SYO:
SYO:

2.
3.

SYO:
LBO:

4.
5.
The display shows static assignments for
LUNs 1, 2, 3, 4,
and 5, which are recorded in the task image file header;
no
other LUNs are statically assigned to the task XKE.

Command Error Messages:
LUN -- NO LUNS
The task that is the argument of the LUN command did not
have any logical assignments.
This is an informational
message.
LUN -- TASK NOT IN SYSTEM
The specified task is not installed or the task
initiated by the
install-run-remove option of the
command.
This is an informational message.

3-116

was
RUN

MCR COMMANDS

MOU
MOUNT (NP,P)

The MOUNT command allows the file system software access to physical
devices.
For all volumes on these devices, MOUNT creates the file
system control blocks that the Ancillary Control Processors (ACPs) use
to support data access on the device. MOUNT also declares, provided
an on-line access path exists, that the volume is logically on line
for access.
The command then requests the ACP to mount the volume or
volume set. Mounting a volume also resets the QIO and Error counts to
zero (0). These counts are used by the Error Logging facility.
The MOUNT command supports three types of devices:
file-structured,
sequential, and non-file-structured. Disks and DECtapes are examples
of file-structured deviceso These devices are usually controlled by
FllACP, which supports Files-11 Structure Level 1. Magnetic tapes are
an example of a sequential device. These tapes are usually controlled
by MTAACP, which supports both ANSI (X3.27-1978) and unlabeled tape
formats. Non-file-structured devices do not have to be mounted on
RSX-llM but must be mounted foreign on RSX-llM-PLUS.
When you mount a Files-11 or magnetic tape volume, there are several
default ACPs that MOUNT can use. MOUNT first defaults the ACP name to
ddnnFl. This allows you to tailor the ACP that controls a specific
volume and then name that ACP after the volume.
For example, if you
tailor FllACP for an RK06 disk and install it as DMOlFl, then when you
issue a MOUNT command for DMl:, MOUNT searches for the ACP DMOlFl.
For disks, if MOUNT cannot find an ACP whose name is in the form
ddnnFl,
it searches for an ACP whose name is in the form ddAACP and
then FllACP. For magnetic tapes, the default ACPs are ddnnFl, ddAACP,
and then MTAACP.
Note that (for privileged users) these defaults can
be overridden by using the /ACP keyword.
It is recommended for slow disk devices such as DECtape that a
separate ACP be used. Thus, you should install a copy of FllACP as
DTAACP for DECtape and a copy as DDAACP for DECtape II.
RSX-llM systems permit specific tasks, such as INI and DSC, access to
unmounted volumes. However, it is necessary to mount a magnetic tape
if it is an ANSI standard tape or if you want to process the tape as
an unlabeled tape with FCS or RMS on a system that supports ANSI
magnetic tapes.
If the system does not support ANSI tapes, FCS
processes unmounted magnetic tapes as unit record devices,.

Rsx""'.'t.~t-t+l'~us ·~y.s·¢~ra$•• .·q;e·n.:v·····~·&~~~·· •t:$••··· uO.moun:~~a'···Riq:1·µ~~$': ··. . :··.'r~~;·.··.•·••·/F'~Rlei~r··
·k~yw()ro ··.••a1iows. ;. ·yoµ ···t~t •. · · • +:~~~~·.·.•cM'.<l;IJ~W•••.·•·•·•~Q~~tjg~. ···•·••··•·••••.•·for••••·.·. •·•·llrif(jp~a,.~~7?.·.·.···.91::
p():J'.ls~a,gda:f:~: y9I~UJ.7:~:.•<·, ,r9:'.r: . • 7~.i;1WPl~:,>·~9:·i~·i:Pi:c;tl:!·Z~·••••.·~·····.•·~·~s~· .... ,. :a·):. F:·~:J-7~'.~:1':\..:.
voiumet . . •.Ycrp· m9§t.fi~st::mount. tp~···· volµf(le · CiE>: I::<H:~j,g;n;:.a.rid:·· ·~h.·/:L~sue,:···:t:lle ·
nu:. command~ ('fl'ou sh()ql(J . not :'.sp~c:~. ~y:: ~n ·ACI?:•J
·
When a device is dismounted, outstanding I/O is allowed to complete,
but no additional files can be accessed on that volume (see the
description of the DISMOUNT command).

3-117

April 1983

MCR COMMANDS

MOU (Cont.)
MOUNT also classifies devices and volumes into three other types:
public, shared, and nonshared. A public volume is one that all system
users can access. Public volumes are the only type supported by
nonmultiuser systems.
A shared volume is one that can be mounted
multiple times by multiple users. A nonshared volume (private) is one
allocated to a single user.
See Chapter 2 for more information on
device types.
A nonprivileged user can only mount a volume on:
•

The user's private device.
No other user can access or mount
the volume until the volume is dismounted and deallocated.

•

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

Only one user can mount a magnetic tape volume (or volume set) at
time.

one

Some file attributes and positioning information can be supplied after
the volume is mounted with the MAG utility.
For more information, see
the IAS/RSX-11 I/O Operations Reference Manual.
If the
waits
device
issues

device is not ready when you attempt to mount the volume, MOUNT
from 30 to 60 seconds for the device to become ready.
If the
is still not ready after the waiting period has elapsed, MOUNT
an error message.

The following descriptions of the MOUNT command formats illustrate the
parameters and keywords associated with Files-11 volumes and with ANSI
magnetic tapes. All the keywords are collectively described following
the format descriptions.
You can use a hyphen (-) as a line terminator to extend the MOUNT
command line when selected keywords cause the command to exceed 80
characters (or whatever buffer size has been specified for the
entering terminal). You can use any number of continuation lines, but
the total command line cannot exceed 255(10) characters.
Note that since the override volume label keyword
(/OVR)
is a
privileged option of the MOUNT command in a multiuser protection
system, a nonprivileged user must always specify a volume label.
Formats:
Files-11 Disk or DECtape Format:

MOU[NT] ddnn:[label] [/keyword(s)]
ddnn:
Device unit on which the volume is to be mounted.
none; must be specified.

Default:

3-118

April 1983

MCR COMMANDS

MOU {Cont.)
label
The Files-11 volume label may be null or up to 12(10)
characters in length.
It is used to ensure that the correct
volume is being mounted.
In a multiuser protection system,
the
command
must include a volume label unless the
privileged /OVR keyword is present.
/keyword(s):
MOUNT keywords for Files-11 devices
values in the volume's home block.

override

corresponding

/ACP=option

/PRO=option

/DENS=density

/PUB

/EXT=block-count

/[NO]SHARE

/FOR

/UIC=uic-spec

/FPRO=[system,owner,group,world]

/UNL

/LOCK=option

/VI

/LRU=directory-count

/[NO]WAIT

/OVR

/WIN=option

/PARM="user parameters"

/[NO]WRITE

ANSI Magnetic Tape Format:
Magnetic tapes, unlike disks and DECtapes, can be mounted by the
set as well as singly.
In fact, when you mount a single magnetic
tape, you are mounting a set consisting of only one tape. A tape
set consists of logically related records or files written on one
or more reels of tape.
Only the first tape in the set has to be
loaded on a device at the time the MOUNT command is issued, but
all tapes in the set can be loaded on different devices when the
command is issued.
The tape set is identified by a File Set Identifier.
Each tape
in the file set is identified by a Volume Identifier. By
default, the File Set ID is the same as the Volume ID of the
first reel of tape in the set.
If this is true for your tape
set, it is not necessary to specify the Volume IDs for the tapes
(although it is recommended).
Volume Identifiers should be assigned by the system
should be unique within the installation.
The
usually the reel number of the physical tape.
Identifier, however, is a name chosen by the user to
or her own tape.

3-119

manager and
Volume ID is
A File Set
refer to his

MCR COMMANDS

MOU (Cont.)
If your tape set processing uses more volumes than you specified
with the /VOL keyword,
you can use any expired or newly
initialized tape for the output volume.
For input, you can use
only the next volume in the tape set.
To determine if the new
input tape is the correct one, the system checks the tape's File
Set ID,
file sequence number,
and file section number.
If
specified, the system also checks the Volume ID.
MOU(NT] device-list:[file-set-ID]

[/keyword(s)]

device-list
One or more device names on which the volume or volume set
is to be mounted.
More than one device name can be
specified only for multivolume ANSI magnetic tape sets.
If
the command specifies more than one device name, the names
must be separated by commas and enclosed
in parentheses,
that is:
(ddn: ,ddn: ,ddn: ••• ).
Note that when you specify more than one device name, you
must always access the tapes through the first name given in
the device list.
(This also applies when you dismount the
tape set.)
If you attempt to access a tape through another
device name, you will get an error message.
file-set-ID
The File Set Identifier (or File Set ID)
can be up to 6
characters in length.
The File Set ID is the name you
choose for the tape set.
By default, it is the same as the
first Volume Identifier (Volume ID) in the volume set.
To
create a tape set with a File Set ID that is different from
the Volume ID of the first tape in the set, specify both the
File Set ID and the first tape's Volume ID.
If you are mounting a newly initialized tape,
you can
specify your own File Set ID by using a
form of the
following command line (note that the /VOL keyword
is used
because the File Set ID and Volume ID are not the same):
>MOU MM:MYSET/VOL=A234
See the description

/VOL

for

information

about

Volume IDs.
File Set IDs can use the following characters:
the digits 0
through 9,
the uppercase letters A through Z, and the
following special characters:
<space> !

% &

(

)

* + , -

•

I :

<=> ?

To use a name that contains a special character, enclose the
name in quotation marks.
To use a quotation mark in the
name, you must use two quotation marks within the quoted
string.
For example, the label T"l% should be specified as
II

T" "1%".

3-120

MCR COMMANDS

MOU (Cont.)
Any lowercase letters specified in a File Set ID or Volume
ID are converted to uppercase before any operations are
performed on the tape.
Any other invalid character is
converted to a question mark (?).
/keyword(s):
/ACP=option

/OVRFSID

/BS=n

/PARM="user

/CC=option

/PRO=option

/DENS=densitv

/PUB

/FOR

/RS=n

/FPRO=protection-spec

/[NO]SHARE]

/[NO]HDR3

/TR=option

/[NO]LABEL

/UIC=[uic]

/LOCK=option

/VI

/OVR

/VOL= (list)

/OVRACC

/[NO]WAIT

/OVREXP

/[NO]WRITE

parameters~

Keywords:

/ACP=option (P)
Specifies the name of the ACP to be used as the file
The option can be
processor for the volume being mounted.
the name of a task that is installed as an ACP or it can be
UNIQUE, which specifies that a dedicated ACP is to be used
for the volume.
You only need to specify an ACP in special cases.
If an ACP
has
been written for a customer application in your
installation, you will need to use that ACP for volumes used
by that application.
When you specify the UNIQUE option, MOUNT creates a copy of
the FllACP if the device is a disk or DECtape or of MTAACP
if the device is a magnetic tape. This unique ACP is given
a name in the form ddnnFl or ddnnAP. When the volume is
dismounted and the file processor exits, the ACP
is
automatically removed.
Default:

Depends on the device type.

3-121

April 1983

MCR COMMANDS

MOU (Cont.)
/BS=n
Specifies the block size for an unlabeled magnetic tape
volume or the block size for files on an ANSI labeled tape
that are Level 1 or 2 (do not have an HDR2 record).
The
value for n can be from 14 (for unlabeled tapes) or 18 (for
ANSI tapes) through 16000. /BS also specifies the default
block size for newly created files on an ANSI magnetic tape.
/CC=option
Specifies the record type for an unlabeled magnetic tape
volume, or the record type for files on ANSI labeled tapes
that are Level 1 or 2 (do not have an HDR2 record)
or that
are Level 3 but do not have a system code (HDR CP 61)
beginning with DEC or OS. The options are:
FOR
LIST
NONE
These options correspond to the
OPEN statement.

FORTRAN

keywords

for

the

/DENS=density
The density (bits per inch or bpi) of the medium loaded on
the drive.
Acceptable density values depend on the device
type as indicated below:
TE16
TSll
I

TSV05
TU45
TU77
TU78
TU80

800 bpi (or
1600 bpi
1600 bpi
800 bpi (or
800 bpi (or
1600 bpi or
1600 bpi

LOW) or 1600 bpi

(or HIGH)

LOW) or 1600 bpi (or HIGH)
LOW) or 1600 bpi (or HIGH)
6250 bpi

Defaults:
TE16
TSll

TSV05
TU45
TU77
TU78
TOSO

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

If you specify more than one device type in the command
line but do not specify a density, the default is the
lowest density supported by all of the devices.
/EXT=block-count
Specifies the number of blocks by which a file can be
extended
when it exhausts its space allocation.
The
block-count must be 1 through 255(10).
Default:
The
initialized.

value

specified

3-122

when

the

volume

was

April 1983

MCR COMMANDS

MOU (Cont.)
/FOR
Indicates a foreign

(non-Files-11) volume.

On RSX-llM, this keyword is recommended but not required for
mounting foreign volumes.
If you do not mount the volume,
access to the volume is unrestricted.
If you specify /FOR·
when you mount a volume on a private device, no one else can
access it.

If you do not specify an ACP name (with /ACP=option) 1 a file
system (an ACP) cannot access the volume. Absence of an ACP
name permits tasks (such as !NI, DSC, BAD, or user tasks
executing
non-file-structured
device
QIOs)
access to
non-Files-11 volumes.
/FPRO=protection-spec
Specifies the default file protection for files created on a
Files-11 disk while the disk is mounted.
The protection
specification has two formats:
(SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWED)
or
[RWED,RWED,RWED,RWED]
The access codes consist of four 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
applicable user is denied the access right.
Default:

that

the

Values taken from volume home block.

/[NO]HDR3
Specifies whether an HDR3 label is to be written when
creating new files.
The /NOHDR3 keyword is needed only when
it is known that the target system cannot handle a tape with
an HDR3 label.
This keyword has no other effect or
application.
Default:

/HDR3.

3-123

MCR COMMANDS

MOU (Cont.)
/[NO]LABEL
Specifies that a magnetic tape volume is in ANSI
(/LABEL) or unlabeled (/NOLABEL). Default: /LABEL.

format

/LOCK=option
Specifies the default value for the DISMOUNT /LOCK keyword.
On RSX;...llM, this keyword is valid
. vol:ume.s •

only

for

magnetic

tape

The options are:
No unload
Unload
Virtual

When you specify the Nounload option (/LOCK=N),
the volume
valid bit is cleared, but the disk is not spun down or the
tape unloaded.
This
is the default option for volumes
mounted foreign and no ACP specified. For example, when you
want to initialize a volume as a Files-11 volume, you first
issue
a MOUNT command with the /FOR keyword.
After
initializing the volume, the usual procedure is to dismount
it and then issue another MOUNT command, using a standard
ACP.
Since the default lock value is N, the volume remains
spinning or loaded and you can immediately issue the MOUNT
command that specifies the ACP.
When you specify the Unload option (/LOCK=U) for disks,
volume valid bit is cleared and, if the drive supports
spin-down function, the disk is powered down.
When
specify this option for tapes,
the tape is rewound
unloaded.
This option is the default lock value for
volumes mounted with a standard ACP.

the
the
you
and
all

On Rsx.:.i1M~.·P·L·.ti.? j~yst.~m.··.·.s·;···;-1.:.·q···u···•·:··. c. a.·.•·.n. n. . ·.~t•··•····.s•. . P..•.e.ci.~y.·•·: · /LOC'l(;:::V: · fO'r ···a;:

muiti.udi·t:••• ·aevic~< < J;for .....·. >e~<a~~ley .• · al'l: J~p4~> · µ~1e.$s
. •. . •.·.~•.rf·1·; Y.·.i..•·.·.l.e.·.· 9· · ·•.ea
:.·.:.•..·.·•··.· ..·.u.$e···.··• r•.·.•·.•. : ....·. ·..•:• .•.:.~e. ••. e.·.·.•·•.<. :· · ·~..:.•..h• e .. 9~~8:ti!?t~i9~1
':·-.q,.~~p~<:l'..: . . ,;.~p.t . : : .'.m.Q~r..e; ,~,i'.nf,.0-rina:t~iQn'.:.. . , , ,_,, -- ,
, < --- · ,;·...~.;=;of.·· :Hhe
<.•.·••.

The Virtual option is privileged. When you specify /LOCK=V,
the volume valid bit is not cleared and the disk is not spun
down or the tape unloaded.
See the
details.

description

the

DISMOUNT

command

for

/LRU=directory-count
Specifies the approximate number of directories that will be
accessed simultaneously while the volume is mounted.
The
FllACP maintains a
list of the
most
recently
used
directories.
The value specified for /LRU sets the number
of entries in this list.
In general, directory operations
can be speeded up significantly by increasing the number of
entries.
3-124

April 1983

MCR COMMANDS

MOU (Cont.)
If a directory appears in the list, no device I/O is
required for
finding
the directory in the Master File
Directory {MFD).
In addition, directory operations do not
require the directory file header to be read.
Legal values for directory-count range from 0 through
127(10).
Note that increasing the value for /LRU increases
the number of File Control Blocks
{FCBs)
used and may
increase
the
amount
of system pool used.
See the
appropriate system generation manual for more information.
Also note that if you specify /LRU=O, the FllACP will not
keep a list of directories.
This is not recommended and
could have an adverse effect on system efficiency.
If you do not use /LRU, the default for directory-count
the value specified when the volume was initializedo

/OVR {P)
For disks and DECtapes,
instructs the MOUNT command to
override label processing so that a volume can be mounted
without specifying a volume label.
For magnetic tapes, instructs the MOUNT command to override
File Set ID processing on the first tape of a tape set so
that a volume can be mounted without specifying a
File Set
ID.
When you specify /OVR, the File Set ID is taken from the
first volume in the set.
However, MOUNT still checks the
IDs for the remaining volumes in the set.
This prevents
improper tape processing.
{Note that Volume IDs for the
tape volumes are overridden if they are not specified,
whether or not you use /OVR.)
/OVRACC (P)
Instructs the MOUNT command to override the
an ANSI magnetic tape volume.

protection

for

Instructs the MOUNT command to override the expiration
on the tape volume(s).

date

/OVREXP (P)

/OVRFSID (P)
Instructs the MOUNT command to ignore File Set Identifiers
on the second and subsequent magnetic tape volumes of a
multivolume set.
/OVRFSID
may
cause
improper
tape
processing.
This keyword should be used only if you know
the volume does not conform to the ANSI standard.

3-125

MCR COMMANDS

MOU (Cont.)
/PARM="user-parameters"
Instructs the MOUNT command to pass nonstandard parameters
from the command line to a foreign ACP. The user-parameter
string can consist of up to a maximum of 40(10) characters
enclosed in quotes (").
The quotation marks are not
included when the characters are counted.
If the quoted parameter itself includes a quotation mark,
the quotation mark must be followed by another quotation
mark.
This keyword is valid only with foreign (/FOR) volumes.
/PRO=protection-spec
Specifies the default volume protection for a Files-11 disk.
The protection specification has two formats:
(SYSTEM:RWCD,OWNER:RWCD,GROUP:RWCD,WORLD:RWCD)
or
[RWCD,RWCD,RWCD,RWCD]
The access codes consist of four 4-code groups in the access
rights word as follows:
R - Read

w - Write
C - create at volume level; extend at file level
D - Delete
In each instance, the absence of the code means
applicable user is denied the access right.
Default:

that

the

Values specified when the volume was initialized.

/PUB
Specifies that the volume is accessible by all users,
depending on the volume and file protection set for the
volume. The drive on which the volume is mounted is
deallocated and set public if necessary.
Defaults:

/PUB if the volume is public
/SHARE if the volume is not allocated or set public
/NOSHARE if the volume is allocated to a user

See Chapter 2 for more information on public devices.
/RS=n
Specifies the number of characters in a record for unlabeled
magnetic tape volumes or the number of characters in a
record for files on ANSI labeled tapes that are Level 1 or 2
(do not have an HDR2 record) • The value for n can be from 1
through the value specified with /BS.

3-126

MCR COMMANDS

MOU {Cont.)
/[NO]SHARE
/SHARE specifies that a volume can be mounted multiple times
by one or more users. Each user who mounts the volume gains
access to it based on the volume and file protection
established for the volume when it was first mounted. After
all users have issued a DISMOUNT command and all file
activity has ceased, the volume is released by the file
processor. The volume is deallocated and set nonpublic if
necessary.

/NOSHARE specifies that the volume is reserved for dedicated
use by the first user who mounted the volume.
No other
users can access the volume. The drive on which the volume
is mounted is allocated to the user's terminal and set
nonpublic if necessary.
, Defaults:

/PUB if the volume is public
/SHARE if the volume is not allocated or set public
/NOSHARE if .the volume is allocated to a user

/TR= option
Specifies the kind of character translation used in read and
write operations on an unlabeled magnetic tape volume.
The
options are:
NONE

No translation takes place.

EBCDIC

Translation from EBCDIC to ASCII for read;
ASCII to EBCDIC for write.
(Note that
translations
are
not
completely
symmetrical.
Some characters in one set
do not have equivalent characters in the
other set.)

UTl, UT2,
UT3

Translation
done
by
user-supplied
Translation
tables
that
have
been
previously linked into MTAACP.
Up to
three tables may be linked.

Default: no translation takes place.
(See the IAS/RSX-11
I/0 Operations Reference Manual for more information on
character translation.)
/UIC=[uic]
Specifies the User Identification Code (UIC) for the volume
owner in the form [group,member]. The square brackets are
required syntax. The numbers for group and member range
from 1 through 377(8). This UIC overrides the one specified
when the volume was initialized.

3-127

MCR COMMANDS

MOU (Cont.)
/UNL
Specifies that the volume index file should be unlocked for
write access by a system user. When locked, the index file
is read-only;
when unlocked, it is read or write.
This
keyword
is typically required when you are recovering lost
blocks or performing other maintenance with the VFY utility.
(See
the
RSX-llM/M-PLUS
Utilities
Manual
for more
information.) Note that this Keyword has nothing to do with
device write-locking.
Default:

locked.

/VI
Displays the volume information on the entering terminal.
The
information displayed is the characteristics with which
the volume was mounted.
For Files-11 volumes, the volume information format is:
Volume Information
Class:
Files-11
Device:
ddnn
Volume label:label
Owner:
[uic]
Protection:
[system,owner,group,world]
Default:
[system,owner,group,world]
Processor:
ACP name

For last-track devices (for example, DL:, DM:, and DR:)
and
for
DU:-type devices, /VI also displays, in octal, the pack
serial number of the volume.
For foreign volumes, the volume information format is:
Volume Information
Class:
Foreign
Device:
ddnn
Volume label:label
For magnetic tape volumes, the volume information format is:
Volume Information
Class:
ANSI labeled tape or Unlabeled tape
Device:
ddnn
Fileset ID;
id
Volume ID:
id
Owner:
[uic]
Processor:
ACP name
For magnetic tape, the volume information repeats the device
and
label
lines if multiple units were specified and omits
the volume protection and characteristics defaults
(volume
protection and characteristics do not apply to magnetic
tapes) •

3-128

April 1983

MCR COMMANDS

MOU {Cont.)
/VOL=(list)
Specifies the Volume Identifier
(Volume ID)
for an ANSI
magnetic tape.
If you specify more than one Volume ID (for
a multivolume tape set), the Volume IDs must be separated by
commas.
Initially, the tape with volume-ID-1 must be physically
loaded on the first device unit specified in the command
line. The remaining tapes may or may not be loaded on other
units specified in the command line.
You must specify
Volume IDs in the order in which the volumes make up the
volume set because the system searches for and/or requests
each successive volume in the specified Volume ID order.
The second and succeeding volumes should be mounted on the
additional un1~s in the order in which they were specified
in the command line or as requested by console messages from
MTAACP.
If more tapes are required than were specified at mount
time, MTAACP automatically adds additional volumes to the
set.
When the command line is issued, the system checks the tape
on the first drive to ensure that it is the first volume of
file-set-ID (see the format for MOUNT command lines for
magnetic tapes).
If you do not specify the /VOL keyword,
the system does not check the Volume ID for the tape.
For compatibility with previous RSX-llM/M-PLUS releases, the
command line
>MOU MM: (A, B ,C)
is equivalent to the command line
>MOU MM:A /VOL=(A,B,C)
/[NO]WAIT
Specifies whether you require operator
assistance
in
performing the mount.
The main use of this keyword is for
batch jobs, indirect command files,
or terminals distant
from the machine room.
If you specify /WAIT in an interactive mount, a message
concerning the mount is sent to the operator's console and
the mount is not completed until the operator takes action.
If you specify /NOWAIT in a batch job or indirect command
file,
or if the mount is interactive, no message appears.
The volume must have been previously placed on the device
and readied for access (spun up/brought on-line).
Default:

/NOWAIT.

3-129

MCR COMMANDS

MOU (Cont.)
/WIN=option
Specifies the number of mapping pointers to be allocated for
file windows. A file window consists of a number of mapping
pointers and is stored in memory when the file
is opened.
(See the IAS/RSX-11 I/O Operations Reference Manual for a
description of retrievar{)ointers.) The number of retrieval
pointers must be less than 129(10).
/WIN accepts the following options:
n

All files are set up with this
default
unless
overridden
on
access;
legal values are 1 through
127(10) or the FULL option.

USER:n

User default value for the volume.

INDEX:n

Number of pointers to
the index file window

(USER:n,INDEX:n)

If n is not the same for both of
these, defaults to the user default
value for the volume default and to
the number specified for the index
file

FULL

Windows are created that map as
much of the file as possible;
FULL
can be used for n in all of these
options.

allocate

Default:
The number of pointers specified in the home block
with either the INI or HOME command.
/[NO]WRITE
/WRITE specifies that write operations are allowed on the
volume
(the volume is software write-enabled) within the
limits of volume and file protection.
/NOWRITE specifies that write operations are not allowed
the volume (the volume is software write-locked).
Default:

Write operations are allowed.

Examples:
>MOU DMl:AMBER
Mounts the volume on device unit DMl:.
(In this example,
the optional parameters have not been specified.
Therefore,
MOUNT uses the parameter values in the volume's home block.)
No volume information is displayed.

3-130

MCR COMMANDS

MOU (Cont.)
>MOU (MTO:,MT1:,MT2:)MYSET /VOL={VOL1,VOL2,VOL3)
Mounts the volume set MYSET on units MTO:, MTl:, and MT2:.
Initially, VOLl must be physically loaded on MTO:;
the
first volume in a set must always be loaded on the first
unit specified in the command. VOL2 and VOL3 may or may not
be loaded when the command line is issued.
If they are
loaded, they can reside on the remaining units in any order
(for example, VOL3 could be loaded on MTl:).
The system searches for the next volume in a set by Volume
ID rather than by unit number;
the order in which volumes
are listed in the command line is the order in which the
system searches for and/or requests the volumes.
If VOL2
and VOL3 are not loaded, the system requests each in turn.
The volumes can be loaded on either MTO:, MTl:, or MT2:.
>MOU DMl:SYS004/LRU=9/VI/WIN=20
Mounts the volume labeled SYS004 on DMl:.
The command line
reserves space for nine directory File Control Blocks {FCBs)
to remain in the ACP's pool or system pool, displays the
volume information, and changes the default window block
size for files opened on this volume to 20(10).
Command Error Messages:
See the IAS/RSX-11 I/O
Operations
definitions of the I/o--e(ror codes.

Reference

Manual

for

MOU -- AMBIGUOUS KEYWORD
<command-line>
The abbreviation used for a keyword in the command line was
too short for MOUNT to distinguish it from another keyword.
Reenter the command line, using a longer form of the
keyword.
MOU -- COMMAND INPUT ERROR
<I/O error code and text>
An error occurred while MOUNT was attempting to read
command line.
Correct the error condition listed
reenter the command line.

the
and

MOU -- COMMAND SYNTAX ERROR
<command-line>
The command line is not in the proper format.
The incorrect
part of the command line is enclosed in brackets. Reenter
the command line, using the correct syntax.
MOU -- DEVICE DRIVER NOT LOADED
The device driver for the specified device is not loaded.
Load the device driver, using the LOAD command, and reenter
the command line.

3-131

MCR COMMANDS

MOU (Cont.)
MOU -- DEVICE NOT MOUNTABLE
The specified device cannot be mounted. Some devices do not
require mounting although the media are removable. Verify
that you are using the correct device and reenter the
command line if necessary.
MOU -- DEVICE NOT READY
The specified device returned a device-not-ready status or
failed to respond within approximately 60 seconds. Verify
that you are using the correct device, ready the device, and
reenter the command line.
MOU -- DEVICE STATUS CHANGED DURING MOUNT
The device status for the specified device changed between
the initial device classification and the final setting up
of the data structures.
This is usually the result of
another
user
mounting
or
dismounting
the
volume
simultaneously with the command in error. Verify the device
status and reenter the command line.
MOU -- FAILED TO ALLOCATE SUFFICIENT DYNAMIC STORAGE
Mounting a volume may require a significant amount of
primary or secondary pool for data structures and the ACP.
Either MOUNT or the ACP was unable to allocate enough space
in pool. Wait until activity on the system has lessened and
then reenter the command line.
MOU -- FAILED TO SET VOLUME VALI.D BIT
<I/O error code. and text>
(RSX-.1.lM-PIJUS systems only.) A hard:ware volume val id bit is
by certa.in ha.r;dwa. re.. .When .the. attempt was made
to set this ha'rdwar;e status bit, .· .the . driver . returned an
error.. Gorrt?c.t the. harqwarepr-oblem and.reenter the command
line.

maint.ained

MOU -- FAILED TO START ANCILLARY CONTROL PROCESSOR
The Executive was unable to start the ACP task.
The task
may be exiting or there may not be sufficient resources.
Reenter the command line at a later time.
MOU -- FllMSG NOT INSTALLED
The task FllMSG is not installed.
to install it.

Ask your

system

manager

MOU -- I/O ERROR ON DEVICE
<I/O error code and text>
An I/O error occurred in the file system software while
accessing
the device.
The line enclosed in brackets
contains the specific error code returned by the system or
the device driver. Correct the error condition and reenter
the command line.

3-132

MCR COMMANDS

MOU (Cont.)
MOU -- INCOMPATIBLE DEVICES FOR MULTI-VOLUME SET
The specified devices are incompatible in one or more of the
following ways:
1.

All must be either disk or magnetic tape devices.

All

must

either

public,

allocated,

not

allocated~

If magnetic tapes, all must support either 7-track
or 9-track and all must support a common density.

Verify the device specifications
line.

and

reenter

the

command

MOU -- INCORRECT FILE SET IDENTIFIER
The File Set ID specified in the command line does not match
that in the File Set ID field of the HDRl label. Determine
the correct File Set ID and reenter the command line, or
reenter the command line specifying the /OVRFSID keyword.
MOU -- INCORRECT VOLUME IDENTIFIER
The Volume ID specified in the command line does not match
that in the Volume ID field of the VOLl label. Determine
the correct Volume ID and
reenter the command line, or
reenter the command line without specifying any Volume ID.
MOU -- INCORRECT VOLUME LABEL
The volume label specified in the command line does not
match the volume label
in the home block.
Determine the
correct volume label and reenter the command line, or mount
the volume specifying the /OVR keyword.
MOU -- INSUFFICIENT PRIVILEGE FOR ATTEMPTED OPERATION
An option specified in the command line
user be privileged.

requires

that

the

MOU -- INTERNAL LOGIC ERROR
An internal programming error has been detected.
This may
be
the
result
of
an unusual software or hardware
configuration or option selection. Retry the operation.
If
the error persists, vary the options selected.
In any case,
submit a Software Performance Report (SPR)
with a console
listing of the command lines and error messages and as much
information on the circumstances of the error as possible.
MOU -- MAGTAPE IS NOT SHAREABLE, DEVICE IN USE
The specified device is already mounted, or the command line
requested shared or public access to the device. Magnetic
tapes are sequential devices and are processed sequentially.
Only one user can access a tape at one time.
Reenter the
command line, specifying the /NOSHARE keyword.

3-133

MCR COMMANDS

MOU (Cont.)
MOU -- MOUNT IS NOT NECESSARY FOR CASSETTES
Self-explanatory.

This is an informational message only.

MOU -- MOUNT NOT SUPPORTED FOR DEVICE CLASS
Although the specified device is mountable, MOUNT is unable
to process the command line for this class of device. MOUNT
supports only Files-11 random-access devices and labeled
(ANSI) and unlabeled sequential tape devices. MOUNT does
not support communications class devices such as DECdataway
or DECnet.
MOU -- MULTI-VOLUME DISK NOT SUPPORTED
MOUNT only supports multivolume ANSI magnetic tape sets.
MOU -- NO HOME BLOCK FOUND OR STRUCTURE NOT SUPPORTED
FllACP was unable to locate a valid home block on the
volume.
The volume is either uninitialized, corrupted, or
in an unsupported format such as Files-11 Structure Level 2
or RT-11.
(Certain utilities such as FLX support other
formats such as DOS-11 and RT-11.) These volumes must be
mounted with the /FOR keyword.
MOU -- NO SUCH DEVICE AVAILABLE
The specified device name and unit was not found in the
logical or physical device tables. Determine the correct
device name and unit number and reenter the command line.
MOU -- NOT FIRST VOLUME OF TAPE SET
Tape sets must be read from the first volume.
The first
tape volume of the tape set was not loaded on the first tape
drive specified in the command line.
MOU -- OPERATION INVALID TO SPOOLED DEVICE
The specified device has been redirected to an intermediate
device for spooling.
Generally, only unit record devices
are spooled and are usually not mountable. If the device is
mountable, the queue spooler processor servicing the device
must be stopped and the device unspooled.
MOU -- PARAMETER CONFLICT WITH ALREADY MOUNTED VOLUME
The volume was already mounted foreign and Files-11 access
was requested or the volume was mounted Files-11 and foreign
access was requested.
MOU -- REQUESTED DENSITY NOT AVAILABLE
The density specified in the command line is not supported
by the specified devices.
Either specify the correct
density or select hardware that supports the
desired
density.

3-134

MCR COMMANDS

MOU (Cont.)
MOU -- TAPE NOT ANSI OR INCORRECT TAPE FORMAT
The tape labels did not conform to the ANSI standard or the
tape is not an ANSI labeled tape.
Specify other tape
formats with the /NOLABEL and /FOR keywords.
MOU -- UNIT ALLOCATED TO OR IN USE BY ANOTHER USER
Another user has allocated the device or a task has the unit
attached.
Verify that the volume is loaded in the correct
unit, that the correct unit is specified, and that no other
user has allocated the device.
MOU -- UNIT OFFLINE

(.~$*++JM±l?pti§•.•·.··i$.y~'.#~m,$.·•··:·9n:i.:Y<~?f'•/'1.:ti~.·:·:$.r;>,~~.;~.:~~·•~~.• . . .·:9~y~q~ . . .:. . ·•·.H~'.~.~i:·.···· ·wa•.s··.:
n~<>~: . ·. . ·. 9~ . . . . ; 1~.rG····. ··~t.•.. ····~~•~•.· · •·.·. .•.·~·r:r. ••'.':1~~·... P?r:: ·. ~:?"t~t·~\~~~c1:~ ; :. ~ ~'.~)~l"l.Ps·t·:~'.<?
(.)P:~r:a•.~··~fll)~.··••.•>····.B~+.79~:. . . ~pq.7~~;~< . :tt;n.±.t:.•·. . ?~·t····•·····•·.A~: .• :/:~1'1.~·······•·•····•~l"l.it:.·. . . ·.:~.·~fr.•.·.···••.J19:.Vf..;
~Yeii$~p1e'.'.,.•····· pl~·~~·········~·re·.·.··cl'eY:l.s7 . . 9~'.•.· lit¢~· . ·.\'/i~.n: ~11~ 779\<>ll·~i~ti,:r;.a):J.q~. ·
~.er;ytp:e.f? . •<:· . •.·.. <'Re.ent:e.r ... th~,,·.<f:?tnlt1alld . . •.•.•. . . }.ine ••...·.··>··· .{S~e . < ,.'th~
RS:X~lJ:l!t/f'l7"~~t1S . · · · · · · • sy§tem ·> ,Manp,:gement · .· Gµi c1e ·fQ•;r x i.nt'<:>:r;mat:.ion: /on
t:.lte> .rec<:>.nf :i.9 uEati.Qn.• · .· $epvi9e~ .... )
MOU

UNIT SPECIFIED MORE THAN ONCE IN MULTI-VOLUME SET
A device can only be specified once for a
set.

multivolume

tape

MOU -- UNRECOVERED DEVICE ERROR
After the standard number of retries, the I/O operation
still could not be successfully completed.
This error
message usually indicates an error in the media.
Correct
the problem and reenter the command line.
MOU -- VOLUME ALREADY MOUNTED
The volume is already mounted as nonshareable or is a public
volume and cannot be mounted a second time.
Mounted Magnetic Tape Messages
Messages that begin with xxxxxx are from the Ancillary Control
Processor (ACP) that is servicing your ANSI magnetic tape volume.
The messages are generated by volume-switching operations for
multivolume tape sets.
A message first appears on the console terminal.
If no action is
taken before a timeout interval elapses, the message appears
again on the console terminal and on the terminal that issued the
command line.

3-135

MCR COMMANDS

MOU (Cont.)
These messages do not occur during the execution of the MOUNT
command, but rather as a result of operations performed by a
system utility or user application program.
xxxxxx

EXPIRATION DATE NOT REACHED ON VOLUME volume-id ON ddnn:
MOUNT ANOTHER VOLUME ON DRIVE ddnn: OR PLACE ON-LINE TO USE

A new output volume is being opened and the expiration date
has not been reached. A new volume can be placed on line,
in which case its expiration date is also checked.
If the
same volume or another volume with the same Volume ID is
placed on line, the volume is overwritten even though it is
not expired.
This message occurs only on volume switching. If a program
is creating a file and specifies the file position of a file
whose expiration date has not been reached, the create
operation terminates with IE.EXP.
xxxxxx -- MOUNT NEXT VOLUME ON DRIVE ddnn:
The ACP does not know the name of the next volume in the
tape set.
The next volume must be placed on the drive
specified. When this message appears, the action to be
taken depends on whether a program is currently reading or
writing the set as follows:
1.

When writing, the ACP accepts any tape that has
been properly initialized. The expiration date of
the first file on the tape is checked to verify
overwrite access.
If the write-ring is missing
when the tape is placed on line, the program
writing to the tape will receive an error message.

When reading, the next volume of the current volume
set must be placed on the drive specified in the
message. The Volume ID is not checked, but other
consistency checks are made, depending on the type
of read operation currently in progress.

xxxxxx -- MOUNT volume-id ON DRIVE ddnn:
Place the volume specified in the message on the drive
indicated.
The ACP knows the name of the volume because
either multiple Volume IDs were specified in the command
line or the ACP has already processed (and therefore
remembers) the Volume ID while the tape set has been
mounted.
xxxxxx -- PLACE DRIVE ddnn:

ON-LINE

The next device drive requested in a multivolume,
operation is off line.
xxxxxx -- REQUESTED ACTION FOR DRIVE ddnn:

multiunit

NOT COMPLETED

This is a reminder message. It indicates that a condition
reported in a previous message from xxxxxx has not yet been
taken care of.

3-136

MCR COMMANDS

MOU (Cont.)
xxxxxx -- REQUESTED ACTION FOR TASK taskname ON DRIVE
ddnn: NOT COMPLETED/PLEASE COMPLETE OR ABORT TASK
This is a reminder message.
delay.

It is displayed

after

long

xxxxxx -- WRONG VOLUME MOUNTED ON DRIVE ddnn:

A subsequent volume of a multivolume tape set has been
placed on line, but the ACP does not think it is the correct
volume.
This condition can occur for the following reasons:
1.

The MOUNT command line specified explicit volume
IDs and the volume that should be mounted is not
the one on the drive.

The ACP has learned the volume sequence of the
current tape set because of previous processing
while the set has been mounted and the volume that
should be mounted is not the one on the drive.

The volume on the drive is not in ANSI format.

A hardware error prevented the ACP from reading any
of the labels in the label set at the beginning of
the volume.

Some other inconsistency in the
has been encountered.

3-137

volume

label

set

MCR COMMANDS

OPE
OPENREGISTER (P)
The OPENREGISTER command allows examination and optional modification
of a word of memory. To open a location within a task, the task must
be fixed in memory.
By default, OPEN displays a location and its contents in octal.
Special control characters allow you to also have the information
displayed in ASCII, Radix-50, double-byte, or decimal format.
To
specify a different format, type the desired control character
followed by the ESCape key. You can do multiple conversions for the
same location on one line. The display remains on the same line until
you open the next location.
You use the same control characters to insert new values into a
location in ASCII, Radix-50, double-byte, or decimal format. In this
case, type the desired control character followed by the new value and
then press the RETURN key to insert the new value and open the next
location.
Format:
OPE[N] memory-address [+ or - n] [/keyword]
memory-address /contents [control-character] [value] line-terminator
The first line is the OPEN command line. The second line is the
general format in which OPEN displays the contents of the
location. After that, you can display and change the contents in
various formats.
memory-address
A 1- to 8-digit octal memory address (location).

+ or - n
One or more optional octal numbers to be added to
from the memory address.

subtracted

/keyword
One of the keywords defined later in
apply only to mapped systems.

this

text.

The

keywords

control-character
One or more optional special characters used to display values or
insert new values in octal, ASCII, single-character ASCII,
Radix-50, double-byte, or decimal format. The special characters
and their related formats are:

I - octal (default format)
" - ASCII
- single-character ASCII
% - Radix-SO
\ - double-byte
- decimal

3-138

MCR COMMANDS

OPE (Cont.)
line-terminator
The line terminator directs the subsequent action of OPEN.
Any
value that is entered
replaces the contents of the word whose
address and current value are shown in
the first part of the
display line.
The slash (/) is part of the display line.

ESCape or ALTMODE:
ESC (ALTMODE) terminates acceptance
of further
input and
is the only exit from the OPEN
command.
If used after a special control character, it
converts the contents of a location from octal to the
desired format.

RETURN:
the next sequential location is opened.
If
used after a
special control character and new value
sequence, it inserts the new value
in the specified
format into a location.

Circumflex (up-arrow on some
previous location is opened.

*®TI!

terminals)/RETURN:

the

@®TI!

Asterisk/RETURN
pointed to by
opened.

at sign/RETURN:
the
location
the contents of the opened location is

Right-angle bracket/RETURN:
the contents of the open
location
is
treated as a
branch
instruction.
The
effective address of the branch
is the next opened
location.
You cannot supply a value
(modify the
current open location) and close the location with a
right-angle bracket/RETURN.
Keywords:
/AF F = [ :: P x 1 'JB y]

(RSX-llM-PLUS multiprocessor systems only.)
Accesses an
address relative to the specified processor's I/O page.
The
square oracke~s are required syntax.
/CPJ=CPx
(RSX-llM-PLUS multiprocessor systems only.)
Accesses
address relative to the specified CPU partition.

/DRV=dd:

Accesses an address relative to the beginning of
partition
that
contains the loadable driver for
specified device.

3-139

the
the

MCR COMMANDS

OPE (Cont.)
/KNL

Accesses the first 32K of Executive memory.

/PAR=partition-name
(RSX-llM systems only.) Accesses an address relative to
beginning of the specified partition.

the

/REG~reg ion- name

(RSX-llM"'."PLUS systems only .. ) Accesses an
the beginning of the sped fied regiqn.
/TASK=taskname
Accesses an address relative to the specified task (the task
partition).
Note that the task must be fixed.
Tn at) R~){-tlM-PJ:ilJS system supportin(j: user· · I.the keywotd ~ccesses and pr1ri1:s the cdnt:eI'lts
the user ~p.ta space:.

I
,., .....

,(Rp:x~lUJ!..:PLOs· .: ··:sy~J~ms .·. only.J:. ]\ccess~s ··.· and
contents of ~9diesses'·. fn the data. space of
·ta~lt • : ·Note tfa\t: the task ml1~t be . £ix ed•
.~¥:~"t:~1ffs·:. that . support usex I-- ·and .o~~tpa~e.J
_

.. ,

/TA$i<f :

3-140

April 1983

MCR COMMANDS

OPE (Cont.)
After accepting the first input line, OPEN finds the
to be accessed by using either:
•

The keyword (in a mapped system)

•

The specified address as the actual address

memory

location

When /DRV, /PAR, /REG, and /TASK are used, the supplied memory address
(a virtual address in the partition) is modified by + or - n. The
absolute address thus formed is used to display the second line shown
in the command format.
In particular, the virtual address (task,
partition, or kernel) and its contents are displayed.
You may then
enter an optional replacement value, followed by a line terminator.
On mapped RSX...;.llM systems, an attempt to specify an illegal location
or . access beyond the limits of the partition causes an· error message.
You are limited to the specified memory region (TASK, PAR, or PRV).
However, if you do not use· a keyword in the c9mma!lq liI'l~, OPEN can
access any address of physical memory.
On unmapped RSX-llM systen:1s.,
any location in physical memory cah be accessed.

3-140.l

MCR COMMANDS

OPE (Cont.)

Examples:

Command Error Messages:
OPE -- BYTE ADDRESS
The address specified as the argument to
was an odd address.
An even address
(for example,
3000)
is
address (for example, 3001) is illegal.

3-141

the

OPEN

legal.

command
An

odd

MCR COMMANDS

OPE (Cont.)
OPE -- INPUT I/O ERROR
In attempting to read the next
error.

command,

OPEN

detected

OPE -- INVALID ADDRESS
The address specified as an argument by the OPEN command
referenced a nonexistent memory location, an address outside
of the specified partition, or an address outside of the
task's virtual address space.
OPE -- TASK NOT FIXED
An attempt was made to open a virtual location in a task.
Since the task was not fixed, it may or may not have been in
memory when you issued the OPEN command.
This message
indicates that the task was not in memory.

3-142

MCR COMMANDS

PAR
PARTITION DEFINITIONS (NP)
The PAR command displays a description of each memory partition in the
system.

3-143

April 1983

MCR COMMANDS

PAR (Cont.)

Format:
PAR [TITIONS]
Examples:
RSX-llM systems

>PAR
TT PAR 114670 00120000 00040000 MAIN TASK
EXCOMl 114624 00160000 00014500 MAIN COM
EXCOM2 114560 00174500 00006100 MAIN COM
SYS PAR 114514 00202600 00010000 MAIN TASK
TKNPAR 114450 00212600 00010000 ·MAIN TASK
DRVPAR 114404 00222600 00030300 MAIN SYS
114340 00222600 00002100 SUB DRIVER -DB:
114240 00224700 00001200 SUB DRIVER -DK:
114140 00226100 00003100 SUB DRIVER -OM:
114040 00231200 00003000 SUB DRIVER -DR:
113240 00245000 00001300 SUB DRIVER -LP:
113104 00246300 00004300 SUB DRIVER -MM:
112450 00252600 00000300 SUB DRIVER -CO:
LDRPAR 112404 00253100 00002500 MAIN TASK
BASIC2 112340 00255600 00040000 MAIN COM
FCSRES 112274 00315600 00040000 MAIN COM
TSTPAR 112230 00355600 00100000 MAIN TASK
GEN
112164 00455600 03322200 MAIN SYS
( PMT ••• )
045214 00455600 00006200 SUB
(DCLT5 )
072740 01151100 00035600 SUB
074670 01206700 00020300 SUB ( ••• MCR)
( ••• HEL)
072240 01242600 00037600 SUB
( ••• PIP)
102350 01302400 00132300 SUB
( ••• EDT)
074624 01472500 00131300 SUB
(TT13 )
074334 01714100 00057100 SUB
(AT.T51)
063724 01773200 00060000 SUB

3-144

MCR COMMANDS

PAR {Cont.)
RSX-llM-PLUS systems
>PAR
SYS PAR 117734 00174400 00010000 MAIN
065230 00174400 00010000 TASK
<TKTN >
SPLPAR 117767 00204400 00012000 MAIN
DRVPAR 117624 00216400 00140000 MAIN
117340 00216400 00003100 DRIVER (DB:)
117274 00221500 00001300 DRIVER {DK:)
117164 00226100 00001300 DRIVER (DS:)
117120 00227400 00004000 DRIVER (DM:)
036314 00233400 00001600 DRIVER (DX:)
116744 00236400 00001100 DRIVER (LP:)
116700 00237500 00003600 DRIVER (MM:)
116634 00243300 00035300 RW COM !TTCOM
116550 00300600 00015600 DRIVER (TT:)
116504 .£)0316400 00001300 DRIVER (RD:)
116440 00317700 00001300 DRIVER (VT:)
116374 00321200 00000100 DRIVER {NL:)
036044 00321300 00001300 DRIVER (DT:)
036504 00322600 00003200 DRIVER (DR:)
LDRPAR 117560 00356400 00002600 MAIN
116054 00356400 00002600 TASK
< .... LOR>
TSTPAR 117514 00361200 00040000 MAIN
SECPOL 117450 00421200 00022000 SEC POOL
GEN
117404 00443200 04734600 MAIN
115454 00443200 00070600 TASK
<FllACP>
073400 00534000 00006000 TASK
<TT36 >
052274 00542600 00003500 RO COM + ••• EDI+
060774 00571400 00020100 TASK
<QMG ••• >
037210 00620100 00036100 TASK
<HRC ••• >
045104 00656200 00026400 TASK
<RMDEMO>
040240 00716200 00070600 TASK
<DSOOFl>
043300 01007000 00070600 TASK
<DSOlFl>
044474 01077600 00070600 TASK
<LSTACP>
062254 01170400 00040000 TASK
<SYS LOG>
061340 01230400 00012100 TASK
<LPPO >
061674 01242500 00012100 TASK
<LPPl >
061774 01254600 00037100 TASK
<BAP2 >
063050 01313700 00037100 TASK
<BAPl >
070100 01401400 00035400 TASK
<AT.T36>
071114 01437000 00035400 TASK
<AT.V3 >
037474 01474400 00074500 TASK
<EDTT3 >
072244 01571100 ·00026500 TASK
<PARV3 >
042100 01631100 00064500 TASK
<TT47 >
037540 01715600 00102700 TASK
<EDIT25>
064534 02050500 00033500 TASK
<TTF6 >
037724 02143000 00134300 RW COM !RMSRES!
070574 02340500 00041700 TASK
<LOGT17>

3-145

MCR COMMANDS

REA
REASSIGN (P)
The REASSIGN command reassigns a task's Logical Unit Numbers
(LUNs)
from one physical device unit to another.
The reassignments affect
only the static assignments recorded in the task's image file on disk.
The command does not affect a memory-resident task.
Hence, REASSIGN
has no effect on the assignments of a currently executing task nor on
those of a task that is fixed in memory.
Format:
REA[SSIGN]

taskname lun ddnn:

taskname
The name of the task.
lun
The Logical Unit Number of the task.
ddnn:
The new device unit, which can be a physical, logical, or
device.

pseudo

Examples:
>REA TSKl 3 TTO:
Reassigns LUN 3 of task TSKl to device TTO:.
>REA GNRL 2 TTl:
Reassigns LUN 2 of task GNRL to device TTl:.
>REA TEST 3 XX:
Reassigns LUN 3 of task TEST to logical device XX:.
Command Error Message:
REA -- LUN OUT OF RANGE
An attempt was made to reassign a LUN that was greater than
the maximum number of LUNs allocated to the task when it was
built.

3-146

MCR COMMANDS

RED
REDIRECT (P)
The REDIRECT command redirects all I/O requests previously directed to
one physical device unit to another physical device unit.
The
REDIRECT command is especially useful if I/O units required for a task
are not working.
The command does not affect any I/O requests already
in the I/O queue.
You cannot redirect the following device units:
•

The pseudo device TI:

(nor can a device be redirected to TI:)

•

An attached device

•

A device unit containing a mounted volume

In addition, you cannot redirect a pseudo device to
you redirect a terminal to the null device.

itself,

nor

can

You can redirect a logged-in terminal to a device other than a
terminal
(except for the null device), but it is not generally
advisable to do so because terminal I/0 would be written to the device
and that could destroy the boot block.
If you do redirect a terminal
to another type of device, you should redirect the terminal to itself
before you log out.
Format:
RED[IRECT] nddnn:=oddnn:
nddnn:
The new device
directed.

unit

which

subsequent

requests

will

oddnn:
The old device unit from which requests have been redirected.
Example:
>RED TT3:=TT6:
Redirects all I/O requests for device TT6: to device
(RED TT6:=TT6: restores I/O requests for TT6:.)

TT3:.

Command Error Messages:
RED -- CIRCULAR REDIRECT ERROR
The attempt to redirect a device would result in a
list of redirections.

circular

RED -- DEVICE NOT REDIRECTABLE
An attempt was made to redirect
redirected.

3-147

device

that

cannot

April 1983

MCR COMMANDS

RED {Cont.)
RED -- NEW DEVICE NOT KNOWN TO SYSTEM
The new device specified by the REDIRECT command was not
known to the system (did not exist in the device tables).
RED -- OLD DEVICE ATTACHED
An attempt was made to redirect an attached device.
RED -- OLD DEVICE MOUNTED
An attempt was made to redirect a mounted device.
RED -- OLD DEVICE NOT KNOWN TO SYSTEM
An attempt was made to redirect an unknown
device did not exist in the device tables).

device

(the

RED -- PSEUDO DEVICE REDIRECT ERROR
An attempt was made to redirect one pseudo device to another
pseudo device.
RED -- TI REDIRECT ERROR
An attempt was made to redirect the pseudo device TI:.
device cannot be redirected.

This

RED -- TT REDIRECT ERROR
An attempt was made to redirect a terminal
device.
This combination is not allowed.

3-148

the

null

April 1983

MCR COMMANDS

REM
REMOVE (P)
The REMOVE command deletes an entry (a task name) from the System Task
Directory
(STD)
and thereby removes the task from the system. The
removal of a task from the system makes the task unknown to the
system.
This action is the complement of INSTALL. All that remains
of the task in the system is the task image file.
REMOVE also checks to see if the task is an initialized CLI.
REMOVE issues an error message.

so,

To remove a task that is currently executing, you must first abort the
task.
Format:
REM[OVE]

[ddnn:] taskname

ddnn:
The device from which the task was installed.
taskname
The name of the task to be removed.

· o.n· ·R·sx~i1.M,...1'tus syste'ms ~ the· .REMOVE> c6mtriarid .apdepts a .. ke}tWo rd .. that
.·~·~. 1.o:w9 . . . •. . J,;l:3.~. .rs;·. t.9: r~moy(i!. .·.· . ·t'~<Jt91'1~ .~tp~.· iti~ ..¢o.Il1#ion. Block' J'.)i.:r,~~t.9FY.·. ·.{~.·~Pl.·.~.
·The "for·nlat. i.s:..

·· · ·

'.I;~·E:~ ·~~9'~<>rFn~rcie. /B..eq
Example:
>REM SCAN
Removes the task named SCAN from the system.
file is not deleted.

The task image

Notes:
•

If a task that is the object of a REMOVE command is fixed, the
command unfixes the task and then removes it.

•

REMOVE cancels
specified task.

•

REMOVE unlinks a task from all ICS/ICR interrupts.

•

REMOVE deallocates all receive-by-reference and receive-data
packets for the task and detaches all attached regions.
(See
the RSX-llM/M-PLUS Executive Reference Manual.)

all

time-based

schedule

requests

for

the

Command Error Message:
REM -- CLI IN USE
An attempt was made to remove a CLI that was still active.
Before a CLI can be removed, its CPB must be eliminated with
the CLI command.

3-149

MCR COMMANDS

RES
RESUME (NP,P)
The RESUME command continues execution of a previously suspended task.
A nonprivileged user can issue the RESUME command only for tasks
initiated from the issuing terminal. A privileged user can direct the
RESUME command to any suspended task.
Format:
RES[UME] taskname [/TERM=TTnnn:]
taskname
The name of the task to be resumed.
/TERM=.TTnnn.:
{RSX..,.llM.~PLUS systems only.). A privileged keyword
task ll}ltiated from. the s·pecifJ~d terminal

Example:
>RES RX7
Resumes task RX7.
Note:
A task cannot suspend any task other than itself.
command allows such a suspended task to proceed.

The

RESUME

Command Error Message:
RES -- TASK NOT SUSPENDED
The task specified
suspended.

the

3-150

RESUME

command

line

was

not

MCR COMMANDS

RUN
RUN (NP,P)
The RUN command initiates the execution of a task.
cause a task to be:

The

command

can

• Run immediately (NP)
• Run at a time increment from now ( p)
• Run at a time increment from clock unit synchronization ( p)
• Run at an absolute time of day (P)

• Installed, immediately run, and removed on exit (NP)
All of these options, except
with or without rescheduling.

install-run-and-remove,

are

available

·.*·**··.· ..

oni.·•g$~p~1M.,.;·J:=>·pOsi•·.·•·y(:).ti.··•···¢~tjnt>t···•·ru.~· ,a·1:.a~1~··?~~?l~.•· . . ~ri;e· •. ·.·......
···.fotm·. ·.·.·.·.<ff.•. ·.:.~he
t~sJ<......pa1ne., .· .·.·. ~hat .•.•.•. . .·. .· is.1·. ·.·•· . .··•X9~ ·>}?~J'ln.9·t . .· .·• ~p£)9iJy . i>•RtIN . . · .·. .·•• •• J~J<:l<'. •.. ··.·.·i··'l'J:le . . . ., . ,. .. x}{x
·.·(~ftd.fC~·~$$$). ~o~m •i·~·iH~~q: .f9,r;.·tl1§!.·. ·.J,?.t"H't:H}Yt>~ .<=Rl?Y 0 t :Jp(:!:.···•t<:lfil<1· .·.y!lli.<=l1· is
ne.ver·:·e?{.eq:qte!f~

Formats:
RUN has five format variations.
1.

Run immediately (nonprivileged option).
RUN taskname [/UIC=[g,m]]
taskname
A 1- to 6-character task name.
/UIC
(Privileged option on multiuser systems only.)
The UIC
under which the task will be requested to run.
This UIC
also determines which files the task can access.
The UIC has the format [g,m], where g and m represent
the group and member numbers, respectively.
Legal group
and member numbers range from 1 through 377(8).
The
square brackets are required syntax.
When you use /UIC, RUN locates the task image file
in
the specified UIC (on device SY:) and runs the task from
that UIC.
The specified UIC also becomes the default
and protection UICs for the task.
When you do not use /UIC, RUN looks for the task image
file
in the System Task Directory (STD) to see if the
task is already installed.
If RUN finds the task,
it
proceeds to run it.
If RUN does not find the task, it
looks for the file in the UIC (on device SY:)
to which
the terminal
requesting the task is set, and then
installs and runs the task.
The terminal's UIC becomes
the default a~d protection UICs for the task.

3-151

MCR COMMANDS

RUN (Cont.)

Note that on mapped systems, you can request a task to
run that is not in the STD.
MCR invokes a catchall task
to install
and
run the
uninstalled
task.
See the
RSX-llM/RSX-llS
or
RSX-llM-PLUS Release Notes for
information about the catchall task.

See the description of /UIC under Format 5 for
by nonprivileged users and tasks.

its

use

Default:
the UIC of the terminal that
command (/UIC is not specified).

the

RUN

issued

Run at a time increment from now (privileged option).
RUN taskname dtime [/RSI=magu] (/UIC= [g ,m]]
taskname
A 1- to 6-character task name.

dtime
The time at which the task will
be
initiated
in time
units
from command
issuance.
This time parameter
consists of two fields:
a magnitude field and a
units
field.
The parameter is in the form magu where mag is
the magnitude and u is one of the following time units:
T, S, M, or H.
The magnitude is the number of units to be clocked.
It
cannot exceed
24 hours
in the specified unit and is
decimal by default.
The unit fields are T, S, M, and H:
T

Ticks.
A tick is a clock interrupt.
The
rate
at which interrupts occur depends on the type of
clock installed
in the system.
For a
line
frequency clock,
the tick rate is either 50 or
60 per second, depending on the line
frequency.
For a programmable clock,
a maximum of 1000
ticks per second is available.
The frequency is
selected at system generation.
T can be any positive value
maximum length of 15 bits.

from

through

s
Seconds.
S can be any positive value
through a maximum length of 15 bits.

from

Minutes.
M can be any
through 1440(10).

from

3-152

positive

value

MCR COMMANDS

RUN {Cont.)
H

Hours.
H can be
through 24(10).

any

positive

value

from

/RSI
The reschedule interval. The format is the same as for
dtime.
The reschedule interval specifies how often the
task is to be rerun.
Thus, each time the specified
interval of time lapses, an initiation request is made
for the specified task.
If the magnitude is equal to O,
then the reschedule
interval i.s set to 1. Specifying /RSI=OH is the same as
specifying /RSI=lH.
Note that the CANCEL and
effect of this keyword.
Default:

REMOVE

commands

clock

unit

negate

the

no rescheduling.

/UIC
See Format 1.
3.

Run at a time increment
(privileged option).

from

synchronization

The system determines the task start-time by waiting for the
first specified time unit
(hour, minute, second, tick) to
increment and then waiting for the specified time to elapse.
RUN taskname sync [dtime] [/RSI=magu] [UIC=[uic]]
taskname
A 1- to 6-character task name.
sync
H - Synchronize on the next hour

M - Synchronize on the next minute

s - Synchronize on the next second
T - Synchronize on the next tick
dtime

See Format 2.
If present, dtime is added' to the
synchronization unit to produce the actual run time for
running the task.
/RSI
See Format 2.
/UIC
See Format 1.

3-153

MCR COMMANDS

RUN (Cont.)
4.

Run at an absolute time of day (privileged option).
RUN taskname atime [/RSI=magu] [/UIC=[uic]]
taskname
A 1- to n-character task name.
atime
Absolute time of day at which
Input format is hh:mm:ss.

initiate

this

task.

hh - Hours {decimal assumed)
mm - Minutes {decimal assumed)
ss - Seconds (decimal assumed)
/RSI
See Format 2.
/UIC
See Format 1.
5.

Install, run immediately, and remove on exit.
RUN [ddnn:] [$]filename [/keyword{s)]
ddnn:
The device unit on which the task image file resides.
$

Specifies that the file can be found in the System Task
Directory on device LB:
(if ddnn: is not specified).
The SET /SYSUIC command defines the system directory.
By convention, the directory is [l,50] on an unmapped
system and [1,54] on a mapped system.
If you do not specify $, RUN searches for the task image
file in the UIC (on device SY:) to which the terminal
requesting the task is set.
(This is similar to Format
1 when /UIC is not specified.)
qri.·.··· RSXf
.·sy~t:~ltl'~ 1 .:.·. i f .·. ·:··y6~ ·s~~ci fy .• $ '.i.~n<i ~· the.. · .· .·.· · ta.sk
i1llil9e .• f:ile cannot .~~<fiound. Jn, ~~~ sys.t~m·· i<li~~qtoJY.i RUN ·

ifM:.JJ?Lus

.• ·.

~:i<l.1:C~es.· .·····t:;e:••.···.•·. ·lib.;arr~/T.···•··~··i·.r~g7<>~y:· . .•. . .~.·~

q~·nv~n,~~~n·r ... t~agrc 4·~r·.£Jl·•.-$~l ~L · ')>··· · r ·

qev~g~

·LB:·•·•.

Note that if LB: has been reassigned to another device
and that device's system UIC contains privileged tasks
built for another system, your system will crash.

3-154

MCR COMMANDS

RUN (Cont.)
filename
The name of the task image file to be run.
Keywords:
/CKP=option
Specifies whether or
not
a
task
will
be
checkpointable.
The options are YES and NO.
If
you specify /CKP=YES
(default for checkpointable
tasks), checkpointing is allowed.
If you specify
/CKP=NO, checkpointing is disabled for the task.
The /CKP keyword overrides the /CP switch specified
at task build.
On systems that support the dynamic allocation of
checkpoint space, the task image file does not need
to contain allocated
checkpoint
space.
The
presence of the /CKP=YES keyword instructs the
system to allocate checkpoint space for the task
when required from a checkpoint file.
/CMD="command-lirie"
Passes the specified command line to the task for
processing.
The command line must begin with the
task's acronym and it must be valid for the task
(for example,
if the task being installed is MAC,
"command-line" must be a valid MACR0-11 command
line)
or a syntax error will occur. When the task
has finished executing the command line,
the task
is removed.
/EST=option
Specifies whether or not a task will wait for
spawned tasks to complete and for RUN to emit exit
status. The options are YES and NO.
If you
specify /EST=YES,
the parent task waits for any
task it spawns to complete and for RUN to emit exit
status before continuing.
If you specify /EST=NO,
the parent task does not wait for exit status from
RUN;
as soon as the spawned task begins running,
the parent task continues executing.
Default: /EST=YES; parent tasks do
until RUN emits exit status.

not

continue

/INC=size
Increments the address space allocated to a task
that runs
in a system-controlled partition.
The
variable size is the number of additional words of
address
space to allocate.
The increment is
usually expressed in octal, but can also
be
expressed in decimal by appending a period.

3-155

April 1983

I
I

MCR COMMANDS

RUN (Cont.)
This keyword overrides the EXTTSK or PAR option
used at task-build time.
Tasks that specify the
size of the partition in which they are running use
this keyword to identify how much dynamic space
they may allocate to symbol tables or buffers.
Tasks such as MAC, TKB, VFY, and AT.
use the space
from the end of the task image to the end of their
address space as dynamic memory.
In effect, the
/INC keyword defines the number of words in this
dynamic region.
On RSX-llM/M-PLUS systems, you cannot extend a task
that
uses memory-resident overlays.
(See the
RSX-llM/M-PLUS Task Builder Manual.)
Default:

The size specified at task-build time.

/IOP=option
Specifies that a privileged task can overmap the
I/O page.
The options are YES and NO.
If you
specify /IOP=YES, RUN assumes that the task will
overmap the I/O page
(APR7) and, if the task is
larger than 8K words, issues a warning message.
If
you specify /IOP=NO, RUN assumes that the task does
not need to use the I/O page. No warning message
is issued.
/!OP complements the Task Builder /IP switch.
Specifying
/IP informs RUN that the task is
intentionally overmapping the I/O page.
Default:

/IOP=YES.

/PAR=parname
Specifies the partition in which the task is to
installed.
Default:

Partition specified at task-build time.

/PMD=option
Requests a Postmortem Dump when the task aborts.
The options are YES and NO.
If you specify
/PMD=YES, a Postmortem Dump is requested for the
task
if
it aborts because of an SST error
condition.
If you specify /PMD=NO,
no dump is
requested at SST abort time.
To generate a dump, the Postmortem Dump task PMD ..•
must be installed
in the system.
This keyword
overrides the /PM switch specified at task-build
time.
Default:

Specified at task-build time.

3-156

MCR COMMANDS

RUN (Cont.)
/PRI:::number
{Privileged keyword.) Specifies the priority of the
task.
The value range is 1 through 250(10), where
250 is the highest priority.
Standard number
conventions apply:
octal by default, decimal if
followed by a period.
(This keyword is ignored if
specified by a nonprivileged user.)
Default:

/PRI=50.

/SLV=option
Specifies the slave status of the task.
The two
options are YES and NO. If /SLV=YES, data sent to
the insta~led task is marked with the TI:
of the
sending task. When the installed task receives the
data, the system sets the task's TI:
to that
associated with the data. This keyword overrides
the /SL switch specified at task build.
If /SLV=NO, the TI: of the task
when receiving data.
Default:

does

not

change

Specified at task-build time.

/TASK=taskname
Specifies the name the task will use while it is
running. This name is a temporary assignment only.
If taskname is not found in the STD, MCR names it
TTnn by default, where nn is the unit number of the
requesting terminal.

·,./T,:J:M~B#riM-: . (.)·.~ ·z~iM.E~rt~f:

.. . .. .. .· ii.< ·~·. < i <i t

(Rs~~J.~tf'I.1J~ · systl!l!\s with ~,.'~JJll~ '. "'~~~~~~~g~

only.) >•··>$e~s\•.:a.>J:J111ef····. 1~~Jt·~.f()r a,·····t.·a·~l{. that 1.1~~~ the· .
CJ?U •. · .. whe.n the . t:hn~ .+imt't ·. expir:es, >the·· task
aborted and.····.a message.is···di.splayed:..

i.s

You can specifythe time limit in minutes (M) or
seconds (SJ; M is the defau:tt. The number of time
units (nJ can be octal (the default). ()r dec1Il'\al if
followed by a period. The maximum value allowed· is
65,536(10).
If the t.ask is pd vi leged, the

3-157

keywo~d

is ignored ..

MCR COMMANDS

RUN (Cont.)
/UIC=[g,m]
Specifies the UIC under which the task will be
requested to run. The square brackets are required
syntax.
If you specify a UIC, the UIC becomes the default
UIC for the task.
However, your protection UIC
becomes the protection UIC for the task. If you do
not specify a UIC, your default and protection UICs
become the default and protection UICs for the
task.
(See the previous description of /UIC for
the effects for privileged users and tasks.)
Default: the UIC of the terminal that
RUN command.

issues

the

command

was

Examples:
)RUN TR7 15M
Runs task TR7 15 minutes
issued.

from

the

time

the

>RUN XKE 15M/RSI=90S/UIC=[3,l]
Runs task XKE 15 minutes from the time the command was
issued, rescheduling it every 90 seconds, with a UIC of
[3,1].

>RUN DK2: $MAC
Runs the task in file DK2:MAC.TSK from the system directory.
The task is automatically installed, run, and removed on
exit.
Notes:
•

If the command requests the task to run immediately (Format
1), it establishes the terminal from which the task was
initiated as the pseudo device TI:. For Formats 2, 3, and 4,
the system establishes the issuing terminal as the pseudo
device CO:.

•

A run-immediately command (Format 1), if terminated with an
ESCape character instead of a RETURN, echoes the default
prompt when the requested task exits and not when MCR has
finished initiating the task. This facility enables you to
determine when a task that is not producing output on a
terminal has exited.

•

The install-run-remove format (Format 5) also establishes the
terminal from which the command was issued as the pseudo
device TI: and causes the default prompt to be displayed on
TI:
when the task exits.
This form of the command is
especially useful when the space available in the dynamic
storage region (pool) is low because the memory necessary for
a Task Control Block (TCB)
returns to pool when the task
exits ..

3-158

MCR COMMANDS

RUN (Cont.)
Command Error Messages:
RUN

INVALID TIME PARAMETER
A specified time field was incorrect.

RUN

TASK BEING ABORTED
A request for the execution of a task was made, but the task

was

being

aborted either because of an unrecoverable error

or an abort command or directive issued by a user.

3-159

MCR COMMANDS

SAV
SAVE (P)

The SAVE command copies the current RSX-llM/M-PLUS system image
(the
contents of main memory)
into the system image file from which the
current image was booted.
{The system image file is a special task
image file named, by convention, RSXllM.SYS.) The command saves the
image so that a hardware bootstrap or the BOOT command can later be
used to reload and restart it.
On RSX-llM,
the system image cannot be greater than 124K;
on
RSX-llM-PLUS,
there is no size restriction.
The size of the system
image file determines the maximum size that can be saved
on
RSX-llM-PLUS, but there are other restrictions on the system image
file:
it must be contiguous and it must be large enough to contain
all of secondary pool.
(SAVE saves secondary pool because prototype
Task Control Blocks - TCBs - are contained in it.)
All RSX-llM/M-PLUS system images reside on a file-structured volume as
a specially formatted task image:
the image does not have a task
header. There may be more than one system image on a volume
(for
example, a program development system and a production or test
system), and nonprivileged tasks can be installed in several system
images at the same time.
To determine the minimum size for a system image file, compute the
formula of four times the size plus two (4*SYSIZ+2). For example:
28K requires 114.

blocks

32K requires 130.

blocks

124K requires 498.

blocks

256K requires 1026.

blocks

You can save system images on any of the following devices:
RSX-llM systems

RLOl/02
RK05
RK06/07
RM02/03/05/80
RP07
RA60
RA80/81
RC25

RSX-llM-PLUS systems

RD51
RP02/03
RP04/05/06
RXOl/02
RX50
RS03/04
DECtape

RLOl/02
RK05
RK06/07
RM02/03/05/80
RA60
RA80/81
RC25

RP02/03
RP04/05/06
RP07
RDSl
RX50
MLll

MLll

I
3-160

April 1983

MCR COMMANDS

SAV (Cont.)
To successfully save a system, the SAVE command requires that:

On an R.sx:-'iiM

Error logging is not active.

All tasks must be installed from LB:.

No checkpoint files are active.

No volumes except the load device are mounted.

The load device can be successfully dismounted.

No tasks have outstanding I/O.

No tasks are connected to interrupts.

All drivers, active tasks, fixed tasks and, on RSX-llM-PLUS
systems, all loaded commons and secondary pool reside within
the amount of main memory that SAVE will write to the system
image file.

syst'eint: SAVE must tun from CO:.

An error is reported if any of these requirements are not met.
SAVE is active when the memory-resident system image is copied to
disk. Because of this, VMR considers SAVE to be an active task in the
system image. This is correct because SAVE is the task that starts
the system after a boot.
The Executive references the file images of installed tasks by
physical addresses
(Logical Block Numbers, or LBNs). A saved system
does not always retain the physical disk addresses of installed tasks.
For example, the Disk Save and Compress Utility Program (DSC) can
compress and copy a disk containing a saved system, thus moving the
task files to different physical locations. Therefore, SAVE converts
the LBNs of all installed tasks into file identifications and stores
these
in the TCBs.
Since the TCB entries contain task file
identifications rather than LBNs after a system sava, the system can
function normally when it is rebooted even if LBNs have changed in the
meantime.

3-161

MCR COMMANDS

SAV (Cont.)
Upon system rebooting, SAVE reopens the task file and stores the new
LBN of the task in the TCB.
If a task has been deleted, the system
cannot open the task file when the system is rebooted.
In this case,
the system automatically removes the task's TCB from the STD.

When the bootstrap block is written, the physical disk-block address
of the system image file is stored with it. However, the file can be
deleted.
If there is file system activity, the blocks previously
allocated to the system image may be reallocated to another file. A
subsequent bootstrap that uses the boot block could possibly cause
random data to be loaded.
Upon rebooting a saved system, SAVE:
•

Selects the system clock

•

If the last memory partition is system-controlled, sizes
memory and extends the partition so that it uses all available
memory

•

On multiuser protection systems, validates that
device is not allocated and then sets it public

•

Sets the context of the
privileged, and nonslaved

•

Outputs a system identification message

•

Redirects all pseudo devices to the boot device

•

Mounts the system disk

•

Initiates the file [l,2]STARTUP.CMD on the booted device

console

terminal

the

boot

logged

in,

Format:
SAV[E]

[/keyword(s)]

Keywords:
/WB
Indicates that a hardware boot block pointing to the system
image is to be written to the system device. The new boot
block points to the file that is saved with the SAVE
command.
Thus, on the next hardware bootstrap, this saved
file will be loaded.
If the command line omits the /WB
keyword,
the boot block still points to the prior system
image, which may have been overwritten.

3-162

MCR COMMANDS

SAV (Cont.)
/MOU=" string"
Automatically issues a MOUNT command at
mount the system disk.

system

startup

The MOUNT command line ("string") that you specify must be
enclosed within quotes and must be in the proper format
(that is, including all necessary slashes (/) or equal signs
(=)).
Note that SAVE does not check the syntax of the
string.
/SFILE="filespec"
Automatically
initiates
an
indirect
command
file
([l,2]STARTUP.CMD)
on the boot device at system startup.
This keyword allows you to specify another indirect command
file.
The command file you specify must be enclosed within quotes.
Note that SAVE does not check the syntax of filespec.

Example:
>SAV
The current status of the system is saved on the system
disk.
System changes made by the REDIRECT command or other
MCR commands are also saved with the system image that is
resident in main memory.
Command

Error Messages
last) :

(RSX-llM-PLUS-only

messages

are

described

SAV -- BAD TASK FILE VBN, TASK REMOVED - taskname
SAVE removed the specified task because it contained a 1....-,:i
UCIU
virtual block number
(VBN)
in its file header.
The task
image file has probably been corrupted.

3-163

MCR COMMANDS

SAV (Cont.)
SAV -- BOOTED DEVICE'S DRIVER NOT LOADED
VMR has been used to unload the driver for the system
(booted)
disk.
Using another system, use VMR to load the
driver and then reboot the system.
SAV -- BOOTED DEVICE NOT IN SYSTEM - dd nnn mmmmmm
When the system was booted, SAVE could not find the booted
device
(device name dd,
physical unit number nnn, CSR
mmmmmm) in the system data structures.
For example, the
system was booted from DB3:, but the system data structures
include only DBO: and DBl:.

:.;()ti .Rs!~.:::r1M4~:tus:·•.~:~3::tif>itqces~·qF...~~~¥~~.si:.··jth~·. ~?:oE .aevice•···•~us1:
·P~t•(:li·I"'·~At:~·y-· C:Pn~~~t. · ~A ·t~e :·t~r:~.e:~ •pt:()c:~s~()J:'•·•~· · rt.·.·····cannot··•··be

··~oru1·~~t;ie9.'f::ia

a bus•

it;ct;t.

··· ·

SAV -- CANNOT FIND HOME BLOCK
SAV could not find the device's home block when searching
for
it or, on RSX-llM-PLUS systems, an error occurred while
SAV was attempting to read the home block.
SAV -- CHECKPOINT FILE STILL IN USE ON ddnn:
The system cannot be saved because a checkpoint file on the
specified device is still active. Deallocate the checkpoint
file (see the ACS command)
and reenter the SAVE command
line.
SAV -- CO:

REDIRECTED TO CO:

(RSX-llM s;ys:tems only.) The conso'le o\,ltput d)riv~r ls active.
is not active, the system may 'be cor:rupted •. You can
us~ tl1e :OJ?:E~ '1ommand to redi r~ct co:
to the; teJ;minal from
which .. :you are . running· SAVE.
If . it

SAV

COMMON, DRIVER OR TASK ABOVE SYSTEM IMAGE FILE LIMIT
A system cannot be saved if addresses for a memory-resident
structure are higher than the highest address of main memory
written to the system image file.
Use the PARTITION
DEFINITIONS command
(PAR)
to determine the cause of the
problem. This includes the running task image of SAVE.

SAV -- DISMOUNT COMPLETE FOR ddnn:
This is an informational message.
The message indicates
that TKTN is not installed in the running system.
If the
load device is mounted when SAVE starts, SAVE attempts to
dismount it.
Since TKTN is not installed, the dismount
complete message from DMO is not displayed on the console
terminai.
As a substitute, SAVE writes this message to the
terminal.

3-104

MCR COMMANDS

SAV (Cont.)
SAV -- ERROR ATTEMPTING TO DISMOUNT ddnn:
If the load device is mounted when SAVE is initiated, SAVE
issues a DISMOUNT command to MCR when the save operation is
complete.
This message indicates
that
the
dismount
operation was not successful. The system may be usable, but
it is recommended that you reboot and issue a DISMOUNT
command.
SAV

ERROR LOGGING STILL ACTIVE
A system cannot be saved while error logging is active.
Disable error logging and reenter the SAVE command line.

SAV -- INDEX FILE HEADER CHECKSUM ERROR
While rebooting a saved system, SAVE detected a checksum
error in the file header of the index file.
The error
causes the system to halt.
The disk has probably been
corrupted.
SAV -- INDEX FILE HEADER READ ERROR
While rebooting a saved system, SAVE detected an error in
the file header of the index file.
The error causes the
system to halt.
SAV -- LABEL BLOCK I/O ERROR
In attempting to save the system image, SAVE wrote the
transfer address in the label block of the system image
file.
An error occurred during this write attempt.
The
disk could be corrupted.
SAV -- MCR IS NOT INSTALLED
When a system is booted, SAVE uses MCR to mount
disk. Use VMR to install the MCR ••• task.

the

system

SAV -- MUST BE RUN FROM TERMINAL CO:
SAVE is not being run from the terminal to which the pseudo
device CO:
is redirected.
(This is not a requirement on an
RSX-llM-PLUS system.)
SAV -- NO POOL SPACE
There is not enough space in pool to contain checkpoint
information when SAVE tries to force resident read/write
commons to their file images.

3-165

MCR COMMANDS

SAV (Cont.)
SAV -- NOT A VALID SAVE DEVICE
An attempt was made to save a system on a device that is not
part of the system I/O data structures (this generally
implies that $SYSIZ+2 and $SYSIZ+6 are corrupted)
or SAVE
does not support the device.
SAV -- OPEN FILE(S) ON ddnn:
There are open files
Manager is stopped.

ddnn:.

Ensure

that

the

Queue

SAV -- SYSTEM MAY NOT BOOT CORRECTLY
The file [system-uic]SAV.TSK was not found on the boot
device.
If SAVE must be checkpointed to redirect and mount
the booted device, the system disk will be overwritten,
causing unpredictable results.
SAV -- SYSTEM MAY NOT WORK - LARGER THAN MAIN MEMORY
This message indicates that the booted system has less main
memory than the saved system image file and that a structure
resident in the system- image file is completely or partially
absent in the booted system.
If the system can run without
the structure, the UNLOAD and UNFIX commands can be used to
remove the nonexistent structures.
SAV -- $SYSIZ DOES NOT POINT AT SYSTEM IMAGE FILE
SAVE determines the location of the system image t11e on tne
system disk by examining the locations near the Executive
label $SYSIZ.
SAVE then makes several validation checks on
that file.
If those checks fail, SAVE does not write to the
disk on the assumption that it could corrupt the disk by
writing to something that is not a system image file.
The
system image or the system image file has been corrupted.
Examine several locations after $SYSIZ and then reboote
SAV -- TASK ACTIVE IN ANOTHER SYSTEM, TASK REMOVED -

taskname

The task is installed in another system as well as in the
booted system.
Since the task is active and mapped to
dynamic regions in the other system, it cannot be run in the
booted system.

3-166

MCR COMMANDS

SAV (Cont.)
SAV -- TASK FILE DELETED, TASK REMOVED - taskname
While rebooting a saved system, a file
identification that
appears in the Task Control Block (TCB) could not be found
in the index file on the boot device.
This indicates that
the file has been deleted.
SAV -- TASK FILE HEADER ERROR, TASK REMOVED - taskname
When SAVE read the task header to restore the LBN of the
task file,
the checksum was bad or there was a file number
mismatch. Therefore, the task was removed.
SAV -- TASK FILE HEADER READ ERROR, TASK REMOVED - taskname
SAVE removed the specified task because it
the task's file header.

could

not

read

SAV -- TASK FILE HEADER WRITE ERROR, TASK REMOVED - taskname
When SAVE attempted to reassign the LUNs of the task or to
rewrite
a
mapping window PCB address,
it could not
successfully rewrite the task header.
Therefore, the task
was removed.
SAV -- TASK HEADER READ ERROR
SAVE detected an I/O error while reading in a task header to
write the file identification into the TCB. This error
causes the system to halt.
SAV -- TASK HEADER READ ERROR, TASK REMOVED - taskname
SAVE detected an I/O error while reading in a task header to
reassign LUNs or to remap the mapping windows. Therefore,
the task was removed.
SAV -- TASK LABEL BLOCK READ ERROR, TASK REMOVED - taskname
When SAVE attempted to reassign the LUNs of the task to the
current system, the task's label block could not be read
(the label block contains the static LUN assignments).
Therefore, the task was removed.
SAV -- TASK TOO BIG FOR PARTITION, TASK REMOVED - taskname
The current CPU has less memory than the system image file.
This
message
indicates
that the last partition has
contracted such that the indicated task cannot fit into it,
eveA if everything else is removed from the partition.
SAV

TASK taskname HAS OUTSTANDING I/O
A system cannot be saved if a task is
complete.

3-167

waiting

for

I/O

MCR COMMANDS

SAV (Cont.)
SAV -- TASK taskname IS ACTIVE AND CHECKPOINTED
You cannot save a system if it contains an active and
checkpointed task.
This restriction prevents a possible
system crash because, if the task was installed in another
system image file,
the task image could be corrupted when
the task was run in the second system.
SAV -- TASK taskname IS CONNECTED TO AN INTERRUPT VECTOR
Disconnect the task from the interrupt vector or
and reenter the SAVE command line.

abort

it,

SAV -- TASK taskname NOT INSTALLED FROM AN LB:
Use the TAS
All tasks must be installed from an LB:.
command to determine which tasks are not. Reenter the SAVE
command line after removing the tasks or installing them
from an LB:.
SAV -- VOLUME STILL MOUNTED ON ddnn:
The volume on device ddnn: was still mounted when the SAVE
command line was issued.
A system cannot be saved with
volumes mounted.
Dismount the volumes and reenter the SAVE
command line.
If necessary,
use the DEVICES command to
determine which volumes are mounted.
SAV -- VOLUME STRUCTURE NOT SUPPORTED
While rebooting a saved system,
SAVE determined from the
disk's home block that the disk's structure is not supported
by the current version of RSX-llM/M-PLUS.
This error causes
the system to halt.
SAV -- (WARNING) NONEXISTENT LUN ASSIGNMENT FOR TASK taskname
The physical device to which SAVE was attempting to reassign
a LUN does not exist in the booted system.
This condition
is resolved if the task performs a
run-time assignment to
the LUN;
otherwise,
the task will encounter an error
condition when it attempts to use the LUN.

Additional

RSX-llM~PLUS

•.. :· .. :: ·.=,_··.

...

Command• Error

·.": .. .... / ·. :, . .

.,: ·.·.: ·..·_;:·. ·_.'.' :.

; ..... ·: .":· ..... ·:· ......,

.....· .=·: ....: ··, ·. ··.: ·.. ~·,.-. ... .

: .-.:'

,.·.•. . . ·s~v.····.-.w-.(iBOQ·T~P~····.····lJE.~ic~······•·.cAN~6~•:s.E•.'••g~()uqa~·:hNf~N]~~····
......

.......

Thete·'.Wa$ an ·~ffbr' when· sAva•···atteiftpted to' btihg .either·'·. the
'.: . . . ·····.

·· ... : · ·... ,

:·.:·.

:: ...

.·.··· :·.··.·

·,·_::.:.· .'

.unit . . •.···.•.•or·····• . . ~ontr.ollet:···<~f·<>t:h_~·.··.···.••h<>:o~ed ·. ·./ <]~vicE!,·•. ······ion ·'·····line..

The·

}!!xecuttye is .•.·c,ot"rupteif 1.,.,~lje d.evii?~ .<1riyeI'.·.· . ~oes .• 11ot:.•· W()rk,: ·•.or
.··.the·•·:<levlce.··dqeS•·. . . no,t:··. . 'wop.f< . .,• 'fheI'~·,·~.·~.· ·np.,·t"ec9yet'Y. . . P~ocecjure .••

3-168

MCR COMMANDS

SAV (Cont.)

3-169

MCR COMMANDS

SET
SET (NP,P)
The SET command dynamically changes characteristics
information about the system, tasks, and devices.

and

displays

Nonprivileged users can change the characteristics of their own
terminals (pseudo device TI:) and any privately allocated device.
Privileged users can change the characteristics of any device and also
of any task and of the system. All users can display information
about any device or task or about the system.
The following two lists describe
nonprivileged and privileged users.

all

the

available

options

for

(TI:)

and

specified)

Nonprivileged options:
•

Establish characteristics for the issuing terminal
for private devices

•

Set the default UIC for the issuing terminal

•

Display the status (determined by the
all terminals and other devices

•

Display statistics about system dynamic memory

keyword

Privileged options:
•

Establish characteristics for any device in the system

•

Establish the default UIC for any terminal in the system

•

Establish the default UIC for DECnet-related tasks

•

Establish the system UIC.
on R~x~11M-PLUS syste~s, .also eistablish the library ·. urc used
tqAD q9ll\ll\an~t {iJ1q J:be iµ$:t;all~run~r~move optipl'l of. the
RUN c~nnnand

by , t;h~.

•

Set a device to public status so
access the device

•

Create partitions and subpartitions

•

Move the top boundary of a partition

•

Add space to the dynamic core pool

•

Modify the pool limit parameters used by the Pool Monitor Task

•

Enable write check on devices that support it

3-170

that

any

system

user

can

MCR COMMANDS

SET (Cont.)

•

Specify the maximum number of I/O packets to
to optimize I/O performance

•

Specify the maximum size to which a task can extend itself.

•

Enable or disable the ability to log
multiuser protection system

preallocated

terminals

Improper use of the SET command from a privileged terminal can result
in a situation in which privileged user input will not be accepted.
Avoid the following two situations:
•

All privileged terminals in the system are slaved and cannot
enter unsolicited
input to MCR,
and logins are disabled.
Nonprivileged terminals cannot enter privileged commands and
therefore
cannot
reset the privileged terminals to be
nonslaved.
See the description of the /SLAVE keyword
in the
"Keywords" section in the following pages.

•

The buffer length of all the nonslaved, privileged terminals
is shorter than 14 bytes on RSX-llM and shorter than 2 bytes
on RSX-llM-PLUS.
The terminal buffer is then too small for a
privileged user to enter many important commands required to
continue system operation or to alter the status of other
terminals.
See the description of the /BUF keyword in the
"Keywords" section in the following pages.

Also, some keywords (/ABAUD, /EBC, /FDX, /HFILL, /HHT, /LINES, /RPA,
/TERM, /TYPEAHEAD, /VFILL,
and /WRAP)
are only supported with the
full-duplex terminal driver.
The full-duplex terminal driver is a
system generation option in RSX-llM systems but is always included in
RSX-llM-PLUS systems. Note that if you select the full-duplex driver
on RSX-llM, you must also select the get/set multiple characteristics
option to display or set any terminal-related characteristics.
Format:
SET /keyword=values
Only one keyword per command line is permitted. You can prefix
most keywords with NO to negate or disable the function of the
keyword.
(Exceptions are noted in Table 3-3. The system returns
a syntax error message whenever NO precedes one of these
keywords.) The keywords are described in alphabetical order
following Table 3-3.

3-171

MCR COMMANDS

SET (Cont.)
Table 3-3
SET _Keywords
Keywords

Type
Device
Characteristics

/[NO]ABAUD[=TTnn:]
/[NO]BRO[=TTnn:]
/BUF=ddnn: [size]
/CLI=TTnn: [cli]
/[NO]CRT[=TTnn:]
/DCL [=TTnn:]
/[NO]EBC[=TTnn:]
/[NO]ECHO[=TTnn:]
/[NO]ESCSEQ[=TTnn:]
/[NO]FDX[=TTnn:]
/[NO]FORMFEED[=TTnn:]
/HFILL=TTnn:[value]
/[NO]HHT[=TTnn:]
/[NO]HOLD[=TTnn:]
/LINES=TTnn:[value]
/[NO]LOWER[=ddnn:]
/MCR[=TTnn:]
/[NO]OPT=[ddnn:opttyp:fairness-count]
(RSX-llM-PLUS systems only)
/[NO]OVLP[=ccn]
(RSX=llM-PLUS systems
/[NO]PRIV[=TTnn:]
/[NO]PUB[=ddnn:]
/[NO]REMOTE[=TTnn:[speed]]
(continued on next page)

3-172

MCR COMMANDS

SET (Cont.)
Table 3-3
(Cont.)
SET Keywords
Type

Keywords
/[NO]RPA[=TTnn:]
/[NO]SERIAL[=TTnn:]
(RSX-llM-PLUS systems only)
/[NO]SLAVE[=TTnn:]
/SPEED=TTnn: [recv:xmit]
/TERM=TTnn: [value]
/[NO]TYPEAHEAD[=TTnn: [size]]
/UIC[=[uic] [:TTnn:]]
/[NO]VFILL[=TTnn:]
/[NO]WCHK[=ddnn:]
/[NO]WRAP[=TTnn:]

Enable/Disable
Login
(privileged
options)

/[NO]LOGON

I/O Packet

/MAXPKT[=n]

Library or
System UICs

/L IB UIC [ = [ u i c ] ]
(RSX-llM-PLUS systems only)
/NETUIC[=[uic]]
/SYSUIC [= [uic]]

Memory
Allocation
(see notes
before error
messages)

/MAIN=pname[:base:size:type]
(RSX-llM systems;
synonym for /PAR on RSX-llM-PLUS
systems;)
/NOMAIN=pname
/MAXEXT[=size]

/NOC EX
(RSX-llM-PLUS systems only)
/PAR=pname[:base:size[:type]]
(RSX-llM-PLUS systems only)
(continued on next page)

3-173

April 1983

MCR COMMANDS

SET (Cont.)
Table 3-3
(Cont.)
SET Keywords
Type

Keywords
/NOPAR=pname
(RSX-llM-PLUS systems only)
/POOL [=top]
/SEC POL
(RSX-llM-PLUS systems only)

/SUB=mname:sname[:base:size]
(RSX-llM systems only)
/NOSUB=mname:sname
(RSX-llM systems only)
/TOP
Pool
Monitor Task

/PLCTL [=[high] [:[low] [: [frz] [: [basep]]]]

Console
Output Task

/CO LOG

System
Tuning

/RNDC [=nn]

•

J
I

/RNDH [=nn]

I
I

/RNDL [=nn]

/SWPC [=nn]
/SWPR [=nn]
Keywords:
/ABAUD [=TTnn:]
(Full-duplex terminal driver
only.)
Enables
autobaud
detection for
the remote dial-up line for the specified
terminal.
The terminal driver samples the line's first
input character, tries to determine the incoming baud rate,
and sets the interface speed accordingly.
A nonprivileged user can display all the terminals that have
autobaud detection enabled, but only a privileged user can
enable the option for a specific terminal.
When you omit =TTnn: 1 the system displays all the
with autobaud detection.

terminals

3-174

April 1983

MCR COMMANDS

SET (Cont.)
Examples:
>SET /ABAUD=TTlO:
Enables autobaud detection for TTlO:.
>SET /ABAUD
ABAUD=TT4:
ABAUD=TTS:
ABAUD=TT6:
ABAUD=TTlO:
Displays all the terminals
detection enabled.

that

have

autobaud

/NOABAUD[=TTnn:]
(Full-duplex terminal driver only.)
Disables
autobaud
detection for the specified terminal.
The terminal driver
does not attempt to determine the incoming baud rate for the
remote dial-up line.
A nonprivileged user can display all the terminals that have
had autobaud detection disabled, but only a privileged user
can disable the option for a specific terminal.
When you omit =TTnn:, the system displays all the
that do not have autobaud detection.

terminals

Examples:
>SET /NOABAUD=TT6:
Disables autobaud detection for TT6:.
>SET /NOABAUD
NOABAUD=COO:
NOABAUD=TT4:
NOABAUD=TT6:
NOABAUD=TT7:
Displays all the terminals
autobaud detection enabled.

that

not

have

/BRO[=TTnn:]
Enables the broadcast option for the specified terminal.
The terminal can receive messages sent from other terminals
with the BROADCAST command.
When you omit =TTnn:, the system displays all the
that can receive messages.

terminals

/BRO is valid only on systems that have multi-CL! support.

3-175

MCR COMMANDS

SET (Cont.)
Examples:
>SET /BRO=TT7:
Enables the broadcast option for TT7:.
>SET /BRO
BRO=COO:
BRO=TT4:
BRO=TT5:
BRO=TT6:
BRO=TT7:
Displays all the terminals that have the broadcast
option enabled.
/NOBRO[=TTnn:]
Disables the broadcast option for the specified terminal.
The
terminal cannot receive messages sent from other
terminals. The terminal also cannot receive messages from
the SHUTUP program until the last five minutes before~system
shutdown.
It is recommended that you not use the /NOBRO
keyword unless you need to because you could miss important
messages.
When you omit =TTnn:, the system displays all the
that cannot receive messages.

terminals

/NOBRO is valid only on systems that have multi-CLI support.
Examples:
>SET /NOBRO=TT4:
Disables the broadcast option for TT4:.
>SET /NOBRO
NOBRO=TT4:
NOBRO=TTlO:
Displays all the terminals that have the broadcast
option disabled.
/BUF=ddnn: [size]
Sets or displays the default buffer size of the specified
device. A nonprivileged user can display the buffer size of
any device but can only set the buffer size of TI:.
A
privileged user can set the buffer size for any device.
The specified size must be greater than 0 and less than or
equal to 255(10).
If ddnn:
is a terminal, the specified
size must be greater than 15(10) and less than or equal to
255(10).
/BUF is particularly useful for defining line
printer width (80 or 132 decimal columns)
and the maximum
number of characters allowed in a command line.

3-176

MCR COMMANDS

SET (Cont.)
When you omit size, the system displays the buffer
the specified device.

size

Example:
>SET /BUF=LPO:
BUF=LPO:l32.
Displays the current buffer size of LPO:=
>SET /BUF=TT1:40.
Sets TTl: buffer size to 40(10).
/CLI=TTnn: [cl i]
Defines the default command line interpreter (CLI)
for the
specified
t9'I"minal.
The CLI can be MCR, DCL, or a
user-written CLI.
(However, note that before a CLI can be
used, it must be installed with the INSTALL /CLI=YES
command.)
A nonprivileged user can display the default CLI for any
terminal but can only set the CLI for TI:. A privileged
user can set the default CLI for any terminal.
When you omit cli, the system displays the
CLI for the specified terminal.

current

default

/CLI is valid only on systems that have multi-CLI support.
Examples:
>SET /CLI=TI:
CLI=TI:MCR
Displays the current default CLI for TI:.
>SET /CLI=TI:ACLI
Sets the default CLI for TI:

to ACLI.

/COLOG
This keyword is documented with the Console Output
(COT) in the RSX-llM/M-PLUS System Management Guide.

Task

/CRT[=TTnn:]
Defines the specified terminal as a Cathode Ray Tube
(CRT)
and enables the backwards deletion option.
Typing the
RUBOUT or DELETE key moves the printing position one space
to the left and erases any character displayed in that
position.
A nonprivileged user can display all terminals defined as
CRTs but can only define TI: as a CRT. A privileged user
can define any terminal as a CRT.

3-177

MCR COMMANDS

SET (Cont.)
When you omit =TTnn:, the system displays all the
that are defined as CRTs.

terminals

Examples:
>SET /CRT=TT3:
Enables the backwards deletion option for terminal
TT3:.
>SET /CRT
CRT=TT3:
CRT=TT4:
Displays all the terminals that have the backwards
deletion option enabled.
/NOCRT[=TTnn:]
Deletes the CRT status of the specified
disables the backwards deletion option.

terminal

and

A nonprivileged user can display all the terminals not
defined as CRTs but can only delete CRT status for TI:.
A
privileged user can delete CRT status for any terminal.
When you omit =TTn:, the system displays all
that are not defined as CRTs.

the

terminals

Examples:
>SET /NOCRT=TT4:
Disables the backwards deletion option for TT4:
>SET /NOCRT
NOCRT=TTO:
NOCRT=TTl:
NOCRT=TT2:
NOCRT=TT4:
Displays all the terminals that have the backwards
deletion option disabled.
/DCL[=TTnn:]
Enables the recognition of DiGITAL Command Language
(DCL)
commands at the specified terminal.
Commands entered in
response to the default prompt are submitted to DCL.
To return a terminal to MCR command
DCL command SET TERMINAL MCR.

recognition,

type

the

A nonprivileged user can display all the terminals that
recognize DCL commands but can only enable DCL recognition
for TI:.
A privileged user can enable
DCL
command
recognition for any terminal.

3-178

MCR COMMANDS

SET (Cont.)
When you omit =TTnn:, the system displays all the
that have DCL command recognition enabled.

terminals

/DCL is valid only on systems that have multi-CLI support.
Examples:
>SET /DCL=TT3:
Enables DCL command recognition for TT3:.
>SET /DCL
DCL=TT3:
DCL=TT7:
DCL=TTlO:
DCL=TT12:
Displays all
commands.

the

terminals

that

recognize

DCL

/EBC[=TTnn:]
(Full-duplex terminal driver only.)
Enables the
8-bit
character option. The terminal driver passes all eight bits
of the input characters to the specified terminal.
A nonprivileged user can display all terminals that have the
option enabled but can only enable the EBC option for TI:.
A privileged user can enable the EBC option for any
terminal.
When you omit =TTnn:, the system displays all the
that have the EBC option enabled.

terminals

Examples:
>SET /EBC=TT3:
Enables the EBC option for terminal TT3:.
>SET /EBC
EBC=TT3:
EBC=TTS:
Displays all the
option enabled.

terminals

that

have

the

EBC

/NOEBC[=TTnn:]
(Full-duplex terminal driver only.)
Disables the 8-bit
character option.
Before passing the input characters to
the device, the terminal driver removes the parity bits.

A nonprivileged user can display all terminals that have the
option disabled but can only disable the EBC option for TI:.
A privileged user can disable EBC for any terminal.
When you omit =TTnn:, the system displays all the
that have the EBC option disabled.

3-179

terminals

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOEBC
NOEBC=TTO:
NOEBC=TTl:
NOEBC=TT2:
NOEBC=TT4:
Displays all terminals that have
disabled.

the

EBC

option

>SET /NOEBC=TT3:
Disables the EBC option for terminal TT3:.
/ECHO[=TTnn:]
Instructs the terminal driver to
typed on the specified terminal.

display

each

character

A nonprivileged user can display all terminals that echo
typed characters but can only enable the echo option for
TI:.
A privileged user can enable the echo option for any
terminal.
When you omit =TTnn:, the system displays all the
that have the echo option enabled.

terminals

Examples:
>SET /ECHO=TT3:
Enables the echo option for terminal TT3:.
·>SET /ECHO
ECHO=TTl:
ECHO=TT3:
Displays all the
option enabled.

terminals

that

have

the

echo

Instructs the terminal driver to inhibit the display of
input characters typed on the specified terminal.

all

/NOECHO[=TTnn:]

on Rsx~11M system$ with the half-dup~ex . termina~
i.s. §1way£) .· ~?l'l<led •. On~y J!lput
$9:1i.crt:eq . ··by .a··1::~$){·.J$·.·•···n9t\··.ecti9e.d. ~ll~1l ¥RP ~peQify ...lNOEC.H(l,.

Note that

dfi'1er, ..•.. l1nsolicitt?d .. inpµ~

A nonprivileged user can display all terminals that do not
echo typed characters but can only disable the echo option
for TI:o
A privileged user can disable the echo option for
any terminal.
When you omit =TTnn:, the system displays all the
that have the echo option disabled.

3-180

terminals

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOECHO
NOECHO=TTO:
NOECHO=TT2:
NOECHO=TT4:
Displays all the terminals that do not echo
characters.

typed

>SET /NOECHO=TT3:
Disables the echo option for terminal TT3:.
/ESCSEQ[=TTnn:]
Enables the recognition of escape sequences from
the
specified terminal.
The terminal driver treats the Esc·
character as the beginning of an escape sequence rather than
as a line terminator.
See the RSX-llM/M-PLUS I/O Drivers
Reference Manual for
further
information abo~ escape
sequences.
A nonprivileged user can display all terminals that can send
and receive escape sequences but can only enable escape
sequence recognition for TI:.
A privileged user can enable
escape sequence recognition for any terminal.
When you omit =TTnn:, the system displays all the
that can send and receive escape sequences.

terminals

Examples:
>SET /ESCSEQ=TT3:
Establishes TT3:
as a terminal that can send
receive escape sequences.

and

>SET /ESCSEQ
ESCSEQ=TT3:
ESCSEQ=TTS:
ESCSEQ=TTlO:
Displays all the terminals
receive escape sequences.

that

can

send

and

sequences

the

/NOESCSEQ[=TTnn:]
Disables the recognition
specified terminal.

escape

A nonprivileged user can display all terminals that do not
recognize escape sequences but can only disable the option
for device TI:.
A privileged user can disable escape
sequence recognition for any terminal.
When you omit =TTnn:, the system displays all the
with escape sequence recognition disabled.

3-181

terminals

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOESCSEQ=TT3:
Disables escape sequence recognition for TT3:.
>SET /NOESCSEQ
NOESCSEQ=TTO:
NOESCSEQ=TTl:
NOESCSEQ=TT2:
NOESCSEQ=TT3:
NOESCSEQ=TT4:
Displays all the terminals
receive escape sequences.

that

cannot

send

/FDX [ =TTnn:]
(Full-duplex terminal driver only.) Instructs the terminal
driver to accept input from the specified terminal while
simultaneously outputting to it.
A nonprivileged user can display all the
full-duplex
terminals but can only enable the option for TI:. A
privileged user can enable the full-duplex option for any
terminal.
When you omit =TTnn:,
full-duplex terminals.

the

system

displays

all

the

Examples:
>SET /FDX=TT3:
Declares that TT3:

is a full-duplex terminal.

>SET /FDX
FDX=TTl:
FDX=TT3:
Displays all the full-duplex terminals.
/NOFDX[=TTnn:]
(Full-duplex terminal driver only.) Disables the full-duplex
~ne terminal driver does not simultaneously process
input and output from the specified terminal.

op~1on;

A nonprivileged user can display all terminals that have the
full-duplex option disabled but can only disable the option
for TI:.
A privileged user can disable the full-duplex
option for any terminal.
When you omit =TTnn:, the system displays all the
that have the full-duplex option disabled.

3-182

terminals

MCR COMMANDS

SET {Cont.)
Examples:
>SET /NOFDX=TT3:
Disables the full-duplex option for terminal TT3:.
>SET /NOFDX
NOFDX=TTO:
NOFDX=TT2:
NOFDX=TT3:
NOFDX=TT4:
Displays all the terminals that
input and output simultaneously.

not

process

/FORMFEED[=TTnn:]
Indicates that the specified terminal has
feed.

hardware

form

A nonprivileged user can display all terminals that have
hardware form feed but can only declare it for TI:.
privileged user can declare it for any terminal.
When you omit =TTnn:, the system displays all the
that have a hardware form feed.

a
A

terminals

Examples:
>SET /FORMFEED
FORMFEED=TTl:
Displays all the terminals that
form feed.

have

hardware

>SET /FORMFEED=TT3:
Declares that TT3:

has a hardware form feed.

/NOFORMFEED[=TTnn:]
Indicates that the
hardware form feed.

specified

terminal

will

not

have

A nonprivileged user can display all terminals that do not
have a hardware form feed but can only specify the option
for TI:. A privileged user can specify the option for any
terminal.
When you omit =TTnn:, the system displays all the
that do not have a hardware form feed.

terminals

Examples:
>SET /NOFORMFEED
NOFORMFEED=TTO:
NOFORMFEED=TT2:
NOFORMFEED=TT4:
Displays all the terminals
hardware form feed.
3-183

that

not

have

MCR COMMANDS

SET (Cont.)
>SET /NOFORMFEED=TT3:
Specifies that TT3:
feed.

will not have a hardware form

/HFILL=TTnn:[value]
(Full-duplex terminal driver only.) Specifies the number of
fill characters
(value)
that the terminal driver places
after a carriage return when outputting to a terminal.
The
range for value is 0 through 7.
A nonprivileged user can display the number of
fill
characters for any terminal but can only change the value
for TI:.
A privileged user can specify the number of fill
characters for any terminal.
When you omit value, the system displays the fill
value for the specified terminal.

character

Examples:
>SET /HFILL=TT3:
HFILL=TT3:0
Displays the number of fill characters for TT3:.
>SET /HFILL=TT3:3
Specifies for TT3:
that
follow a carriage return.

three

fill

characters

/HHT[=TTnn:]
(Full-duplex terminal driver only.)
Indicates
to
the
terminal driver that the specified terminal has a hardware
horizontal tab.

A nonprivileged user can display all terminals that

have
hardware horizontal tab but can only declare it for TI:.
privileged user can declare it for any terminal.

When you omit =TTnn:, the system displays all the
that have a hardware horizontal tab.

terminals

Examples:
>SET /HHT
HHT=TT4:
HHT=TT6:
HHT=TT7:
Displays all the terminals that
horizontal tab.

have

hardware

>SET /HHT=TT3:
Declares that TT3:

3-184

has hardware horizontal tabs.

MCR COMMANDS

SET (Cont.)
/NOHHT[=TTnn:]
(Full-duplex terminal driver only.)
Indicates that the
specified terminal does not have a hardware horizontal tab.
A nonprivileged user can display all terminals that do not
have a hardware horizontal tab but can only declare it for
TI:.
A privileged user can declare it for any terminal.
When you omit =TTnn:, the system displays all the
that do not have a hardware horizontal tab.

terminals

Examples:
>SET /NOHHT
NOHHT=TTO:
NOHHT=TTl:
NOHHT=TT2:
Displays all the terminals
hardware horizontal tab.

that

not

have

not

have

hardware

>SET /NOHHT=TT3:
Declares that TT3:
horizontal tab.

does

/HOLD[=TTnn:]
Enables hold-screen mode at the specified CRT terminal.
When hold-screen mode is enabled,
the terminal displays
output one screenful at a time.
The screenful of output
remains on the screen until you type the SCROLL key while
pressing the SHIFT key.
The terminal then refills the
screen.
You can also advance the screen contents one line
at a time by typing the SCROLL key.
Hold-screen mode is useful when copying files to terminals
that normally transmit output at high baud rates (9600, for
example). Note, however, that hold-screen mode may not be
appropriate for use with certain types of programs (editors
or terminals using different speeds for
input and output,
for example) •
A nonprivileged user can display all terminals currently in
hold-screen mode but can only place TI:
in hold-screen
mode.
A privileged user can place any
terminal
in
hold-screen mode.
When you omit =TTnn:, the system displays all the
currently in hold-screen mode.

terminals

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

3-185

MCR COMMANDS

SET (Cont.)
>SET /HOLD
HOLD=TT3:
HOLD=TT7:
HOLD=TT12:
Displays all the terminals that
mode enabled.

have

hold-screen

/NO HOLD [ =TTnn:]
Disables hold-screen mode at the specified CRT terminal.
A nonprivileged user can display all terminals not in
hold-screen mode but can only disable the option for TI:. A
privileged user can disable hold-screen mode for
any
terminal.
When you omit =TTnn:, the system displays all the
that have hold-screen mode disabled.

terminals

Examples:
>SET /NOHOLD=TT3:
Disables hold-screen

~ode

for terminal TT3:.

>SET /NOHOLD
NOHOLD=TTO:
NOHOLD=TT3:
Displays all the terminals that
mode disabled.

have

hold-screen

/LIBUic[=:[uicJ]
UIC for the
s UIC usually
tasks •. When

(RSX-llM_;PLUS
nonprivileged
contains
you issue
name with
searches for
found · the
[3

the.·. •task

3-186

MCR COMMANDS

SET (Cont.)
/LINES=TTnn:[value]
(Full-duplex terminal driver only.) Establishes the number
of lines per page (value) for the terminal. The range for
value is 1 through 255(10). To specify a decimal value,
place a period (.) after the number.
A nonprivileged user can display the number of lines per
page for any terminal but can only specify the number for
TI:. A privileged user can specify the number of lines per
page for any terminal.
When you omit value, the system displays the number of lines
per page for the specified terminal.
Examples:
>SET /LINES=TT3:
LINES=TT3: 24.
Displays the number of lines per page for TT3:.
>SET /LINES=TT3:20
Specifies in octal the number of
for TT3:.

lines

per

page

/LOGON
(Privileged keyword.) Enables logging in on terminals
multiuser protection system.

(Privileged keyword.) Disables logging in on terminals in
multiuser protection system.

/NOLOGON

/LOGON and /NOLOGON clear and set a flag checked by the
HELLO command when a user attempts to log in on a terminal.
/NOLOGON provides a means of preventing users from accessing
the system during such activities as system maintenance or
account file maintenance.
/LOWER [=ddnn:]
Specifies that lowercase characters on a terminal or line
printer are not to be converted to uppercase when they are
received from the device driver.
Note that this keyword
only affects input from a terminal, not output to a
terminal.
A nonprivileged user can display all devices that do not
convert lowercase characters to uppercase but can only
specify the option for TI:. A privileged user can specify
the option for any terminal or line printer.
When you omit =ddnn:, the system displays all the devices
for
which
lowercase characters are not converted to
uppercase.

3-187

MCR COMMANDS

SET (Cont.)
Examples:
>SET /LOWER=TT3:
Inhibits conversion of lowercase characters
uppercase when they are received from TT3:.

>SET /LOWER
LOWER=LPO:
LOWER=TTl:
LOWER=TT3:
LOWER=TT7:
Displays all the devices for which lowercase
characters are not converted to uppercase.
/NOLOWER [ =ddnn:]

Resets the characteristics for the terminal or line printer.
For terminals,
lowercase characters received on input are
automatically converted to
uppercase
and
echoed
as
uppercase.
The keyword has no effect on characters output
to the terminal. For line printers,
lowercase characters
output to the device are printed as uppercase.
A nonprivileged user can display all the devices that
perform this conversion but can only specify the option for
TI:.
A privileged user can specify the option for
any
terminal or line printer.
When you omit =ddnn:, the system displays all
the
for which conversion to uppercase is specified.

devices

Examples:
>SET /NOLOWER
NOLOWER==LPl:
NOLOWER=TTO:
NOLOWER==TT2:
NOLOWER==TT4:
Displays all
the devices
that
automatically
convert lowercase characters to uppercase.
>SET /NOLOWER==TT3:
Resets TT3:
so that lowercase characters
automatically converted to uppercase.

are

/MAIN=pname[:base:size:type]
(On RSX-llM-PLUS systems, synonym for /PAR.) Establishes the
specified partition as a main partition. A nonprivileged
user can only display the base, size, and type of a main
partition.
pname
The 1- to 6-character alphanumeric partition name.

3-188

April 1983

MCR COMMANDS

SET (Cont.)
:base
The physical base address of the
as a number of 64-byte blocks.

partition,

specified

:size
The size of the partition, specified
64-byte blocks.

number

:type
The partition type:

SYS

A system-controlled task partition

COM

A common partition

DEV

A common partition mapping into the
registers

device

User-controlled and
system-controlled
task
partitions
contain user tasks. Common partitions are used for resident
libraries and common blocks. Device partitions are used by
nonprivileged tasks to access device registers in the
external page, such as those for the UDC and ICS/ICR-11.
Base and size can be entered in any of the following formats
(nnnn is a number in bytes to which the system applies a
multiplication factor to determine the value used):
Format

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 (in words) are:
Octal
Decimal
Octal K
Decimal K

O<=base<l77777
O.<=base<65535
OK<=base<3777K
O.K<=base<2047.K

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

For system-controlled partitions, size may range from
1920.K or any valid representation of these limits.
For example, any of the following
allocate a 2048(10}-byte partition.
40
32.
lK

3-189

inputs

for

size

to
will

MCR COMMANDS

SET (Cont.)
If you omit base, size, and type, the system displays the
values of these parameters for the named partition.
If the
named partition is a task partition, the system also
displays the parameters of all its subpartitions.
Examples:
>SET /MAIN=SYSPAR:420:140:TASK
Defines a main partition named SYSPAR as
a
user-controlled partition whose base address is
42000(8) and whose length is 14000(8) bytes.
>SET /MAIN=SYSPAR
MAIN=SYSPAR:0420:0140:TASK
Displays the parameters of the main partition
SYSPAR. Note that if the main partition is a task
partition
and
contains
subpartitions,
the
parameters of the subpartition are also displayed.
/NOMAIN=pname
(On RSX-llM-PLUS systems, synonym for
keyword.)
Eliminates the specified
system.

privileged
/NOPAR;
partition from the

Example:
>SET /NOMAIN=SYSPAR
Eliminates the
system.

main

partition

SYSPAR

from

the

/MAXEXT[=size]
(Privileged keyword.) Establishes the maximum size to which
a task can extend itself beyond its mapped array area by
means of the EXTEND TASK directive (see the RSX-llM/M-PLUS
Task Builder Manual for
information about arrays and the
RSX'=llM/M-PLUS Executive Reference Manual for a description
of the directive).
The keyword is only valid on mapped RSX-llM systems that
selected the EXTEND TASK directive option during system
generation and on all RSX=llM-PLUS systems.
Note that a
nonprivileged user can display the maximum size to which a
task can extend itself (but not change the size).
The maximum size can be expressed in four formats:
n

nK
n.
n.K
See the description of the /MAIN
definition of these size values.

3-190

/PAR

keyword

for

MCR COMMANDS

SET (Cont.)
When you omit =size, the system displays the current maximum
size in the format:
MAXEXT=m
where m is an octal number equal
64-byte blocks allowed for a
indicates 20K words) •

to the maximum size in
task
(for example,
1200

Examples:
>SET /MAXEXT=20.K
Establishes 20.K as the maximum size
task can extend itself.

which

>SET /MAXEXT
MAXEXT=l2000
Displays the current maximum size to which a
can extend itself.

task

/MAXPKT[=n]
Specifies the maximum number of I/O packets to be retained
in a separate queue for use by the QIO directive. The
number of retained packets
(n)
is used to optimize the
servicing of QIO requests.
The range for n is 0 through
15(10).
A nonprivileged user can only display
current number of available I/O packets.

the

maximum

and

When you omit =n, the system displays the maximum number and
the current number of available I/O packets in the format:
MAXPKT=m. : c •
where m.
is the maximum number of and c.
number of available I/O packets.

the

current

Examples:
>SET /MAXPKT=l2.
Sets the maximum number of I/O packets retained
for optimization of I/O servicing to 12(10).
>SET /MAXPKT
MAXPKT=l2.:3.
Displays the maximum and current number of I/O
packets.
The maximum number of I/O packets to be
retained explicitly for QIO processing is 12(10).
Three packets are currently available.

3-191

MCR COMMANDS

SET (Cont.)
/MCR[=TTnn:]
Enables MCR command recognition at the specified terminal.
Commands entered in response to the default prompt are
submitted to MCR.
A nonprivileged user can display all the terminals that
recognize MCR commands but can only specify the option for
TI:. A privileged user can enable MCR command recognition
for any terminal.
When you omit =TTnn:, the system displays all the
that recognize MCR commands.

terminals

/MCR is valid only on systems that have multi-CL! support.
Examples:
>SET /MCR
MCR=TTl:
MCR=TT2:
MCR=TT3:
Displays all
commands.

the

terminals

that

recognize

MCR

>SET /MCR=TT4:
Enables MCR command recognition for TT4:.
/NETUIC[=[uic]]
Specifies the UIC in which all DECnet-related tasks are
stored.
The keyword applies only to systems that selected
the external communication products option during system
generation.

()n RSX.,..llftl, if you did -not select support for
sys:t;em'9~n:~raj:io-n, NE'eUid'Ydefaults to - S,YSUlC'.'

DECnet

A nonprivileged user can display the current network
but only a privileged user can set or change it.
When you omit
network urc.

=[uic],

the

system

displays

Examples:
>SET /NETUIC
NETUIC=[20,34]
Displays the current network UIC.
>SET /NETUIC=[ll0,3]
Sets the network urc to (110,3].

3-192

the

urc,

current

MCR COMMANDS

SET (Cont.)

3-192.1

April 1983

MCR COMMANDS

SET (Cont.)

Displays all the disk
optimization enabled.

3-193

MCR COMMANDS

SET (Cont.)

Displays all the devices that
queue optimization enabled.
/OVLP [::ccn]
(RSX-llM;...PLUS systems only.) Enables overlap seek support
for
the specified device· controller.
Overlapped seek
support is available only on DM and RH device controllers
(RH controllers are for DB:- and DR:-type devices).

A nonprivileged user can only display the device controllers
that have overlap seek support enabled. A privileged user
can enable overlap seek for any device controller that
supports it.
When Y()U omit =ccn, the system displays all the device
controllers that have overlapped seek support enabled.
Examples:

>SET /OVLP=DMA
Enables

>SET /OVLP
OVLP=RHB
OV+.J->:::.D,M.A .
Displays. all .. tJi¢:. device

p<>ntro11ers

over~(;lppe9 •. . ~~:e·k.· . . sup{><>rt..•.ery(;lbl~d·"

;,.

;:·:·:

..... ,.

·:···.· .. · : · · · · ·

{R~~ .... llM:~Pt.t:Je; :. ~Ystell\s .}>n1-y:.J: .. pi 5aple:s

:for····M·fe . • • speci·~·~··~~··•.deyt.9~·! ~9ntroller •

3-194

seek· 5upport

MCR COMMANDS

SET (Cont.)

•

3-195

April 1983

MCR COMMANDS

SET (Cont.)

3-196

MCR COMMANDS

SET (Cont.)

/PLCTL[=[high] [:[low] [: [frsiz] [ :basep]]]]
(Privileged keyword.) Sets the pool limit parameters used by
the Pool Monitor Task (PMT). The following list defines the
parameters:
high

The high pool limit in bytes.

low

The low pool limit in bytes.

frsiz

The minimum byte size of the largest free pool
block required for avoiding low-pool action by
the Pool Monitor Task.

basep

The base task priority, which is the lowest
priority a nonprivileged task can have and
still be eligible for memory contention during
times of low pool;
this priority remains in
effect until pool conditions improve.
Note
that only those tasks requested while the
system is in a low pool state are affected.

The following list defines the limits of the parameters:

84.

<= frsiz <= high

<= basep <= 250.

low <= high <= total size of system pool

The following list gives the defaults for the parameters:
high

1600.

bytes

low

600.

bytes

frsiz

200.

bytes

basep

51.

See the RSX-llM/M-PLUS
System
Management
Guide
for
information on determining the values for the parameters.
When you omit the parameters,
the
current parameters for the system.

system

displays

the

pool

limit

Example:
>SET /PLCTL
PLCTL=l600.:600.:200.:51.
Displays the current settings for the
parameters.

3-197

MCR COMMANDS

SET (Cont.)
/POOL [=top]
Increases the size of the dynamic storage region
(pool).
The parameter top specifies the first location in memory to
be used for user partitions. You specify the location in
units of 64-byte blocks. The location can be given as an
octal or decimal number.
A nonprivileged user can
dynamic storage region.

only

display

the

size

the

When you omit =top, the system displays
dynamic storage region in the format:

the

size

the

The first location for user partitions
(displayed
bytes with two trailing zeros suppressed).

POOL=top:max.:total.
top

max.
The longest free block (displayed in words).
total.
The total pool space (displayed in words).
Examples:
>SET /POQL;::l200
Establishes 120000(8) as
for user partitions.

the

beginning

location

>SET /POOL
POOL=l200:03380.:06322.
Displays the first location for user partitions,
the longest free block, and the total of all pool
space (the first free block is at 120000, the
longest free block is 3380 decimal words, and the
total pool space is 6322 decimal words).

/PRIV[=TTnn:]
Establishes the specified terminal as a privileged terminal.

A nonprivileged user can only display the terminals that are
privileged.
A privileged user can set any terminal to be
privileged.
When you omit =TTnn:, the system displays all the privileged
terminals.

3-198

MCR COMMANDS

SET (Cont.)
Examples:
>SET /PRIV=TTl:
Establishes TTl:

as a privileged_ terminal.

>SET /PRIV
PRIV=TTO:
PRIV=TTl:
Displays all the privileged terminals.
/NO PR IV [ =TTnn:]
Establishes the specified terminal to be nonprivileged.
A nonprivileged user can only display the terminals that are
nonprivileged. A privileged user can set any terminal to be
nonprivileged.
When you omit =TTnn:,
nonprivileged terminals.

the

system

displays

the

all

Examples:
>SET /NOPRIV
NOPRIV=TT2:
NOPRIV=TT3:
Displays all the nonprivileged terminals.
>SET /NOPRIV=TTl:
Establishes TTl:

as a nonprivileged terminal.

/PUB [ =ddnn:]
(RSX-llM multiuser protection systems and
RSX-llM-PLUS
systems only.) Establishes the specified device as a public
device. A public device is one that can be accessed by all
system users.
Note that allocated and already mounted
devices cannot be set public.
(Devices can be set public
before they are mounted.)
A nonprivileged user can display all the public devices, but
only a privileged user can establish a device as public.
When you omit =ddnn:, the system
devices.

displays

all

Examples:
>SET /PUB=LP:
Establishes LPO:

3-199

as a public device.

the

public

MCR COMMANDS

SET (Cont.)
>SET /PUB
PUB=DBO:
PUB=DBl:
PUB=LPO:
Displays all the public devices.
/NOPUB= [ddnn:]
(RSX-llM multiuser protection systems and
RSX-llM-PLUS
systems
only.)
Establishes the specified device as a
nonpublic device. A nonprivileged user can display the
devices
that were previously set public but are now
nonpublic, but only a privileged user can make a public
device nonpublic.
Note that mounted devices cannot lose
their public status.
When you omit =ddnn:, the system displays all
actually in use that are not public devices.

the

devices

Examples:
>SET /NOPUB
NOPUB=DKO:
NOPUB=DKl:
Displays all the private and
devices.

unowned

{nonpublic)

>SET /NOPUB=LPO:
Establishes LPO:

as a nonpublic device.

/REMOTE[=TTnn: [speed]]

Declares that the specified terminal is connected to a modern
and can be connected by means of a dial-u~ network.
The
terminal has a line to a DHll, DHVll, DLll, DLVll, DZll, or
DZVll multiplexer.
A nonprivileged user can display all remote lines, but only
a privileged user can declare a terminal as a remote line.
Specifying speed establishes the initial baud rate
(answer
speed)
of the remote dial-up line for the specified
terminal.
You may specify an answer speed only for DHlls,
DHVlls,
DZlls,
and
DZVlls, which are variable-speed
multiplexers.
{You cannot specify an answer speed for DLlls
or DLVlls.)
Valid speeds for the DHll are O, 50, 75, 110, 134.5,
200,
300,
600,
1200, 1800, 2400, 4800, 9600,
{user-specified baud rate A), and EXTB (user-specified
rate B) •

150,
EXTA
baud

Valid speeds for the DHVll are 75,
110, 134.5, 150,
600, 1200, 1800, 2000, 2400, 4800, 9600, and 19200.

300,

3-200

April 1983

MCR COMMANDS

SET {Cont.)
Valid speeds for the DZll and DZVll are 50, 75, 110, 134.5,
150, 300, 600, 1200, 1800, 2000, 2400, 3600, 4800, 7200, and
9600.
When you omit =TTnn:, the system displays all the remote
terminals. When you omit speed, the current setting for the
terminal remains in effect.

I
•

Examples:
>SET /REMOTE
REMOTE=TT1:1200
REMOTE=TT2:0
REMOTE=TT4:0
Displays all the terminals that are currently
as remote dial-in lines.

set

>SET /REMOTE=TT3:1200
Sets the terminal line corresponding to TT3:
remote
dial-in line.
The initial baud
(answer speed) for the line will be 1200.

as a
rate

/NOREMOTE[=TTnn:]
Declares that the terminal's
connected to a modem.

line

local

line

not
•

A nonprivileged user can display all local lines, but only a
privileged user can declare a terminal as local.
When you omit =TTnn:, the system displays all the local
lines
(including DLll, DLVll, DHll, DHVll, DZll, and DZVll
multiplexers) •

Examples:
>SET /NOREMOTE=TT3:
Declares that the terminal line
local line.

for

TT3:

>SET /NOREMOTE
NOREMOTE=TTO:
NOREMOTE=TT3:
Displays all the local lines
(including DLll,
DLVll, DHll, DHVll, DZll, and DZVll multiplexers).
/RNDC [=nn]
Defines the length of the Executive round-robin scheduling
interval
in ticks.
The parameter nn can be an octal value,
or decimal if followed by a period (.). The minimum value
for nn is O.
See the RSX-llM or RSX-llM-PLUS System
Generation and Installation Guide for more information.

3-201

•

April 1983

MCR COMMANDS

SET (Cont.)
A nonprivileged user can display the value for the interval,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the interval.
Examples:
>SET /RNDC
RNDC=6.
Displays the current
scheduling interval.

length

the

round-robin

>SET /RNDC=lO.
Sets the length of the interval to 10(10) ticks.
/RNDH[=nn]

•

Defines the highest priority (1 through 250 decimal)
that
will be considered for Executive round-robin scheduling.
The class must be higher than the one specified with /RNDL.
See the RSX-llM or RSX-llM-PLUS System Generation and
Installation Guide for more information.
A nonprivileged user can display the value for the priority,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the priority.
Examples:
>SET /RNDH
RNDH=l50.
Displays the current highest priority class
is considered for round-robin scheduling.

that

>SET /RNOH=l20.
Sets the highest priority class to 120(10).
/RNDL[=nn]

•

Defines the lowest priority (1 through 250 decimal)
that
will be considered for Executive round-robin schedulinge
The class must be lower than the one specified with /RNDH.
See the RSX-llM or RSX-llM-PLUS System Generation and
Installation Guide for more information.
A nonprivileged user can display the value for the priority,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the priority.

3-202

April 1983

MCR COMMANDS

SET (Cont.)
Examples:
>SET /RNDL
RNDL=l
Displays the current lowest priority class that is
considered for round-robin scheduling.
>SET /RNDL=20.
Sets the lowest priority class to 20(10).
/RPA [ =TTnn:]
(Full-duplex
terminal
driver
only.)
Enables
the
read-pass-all option of the terminal driver.
The terminal
driver passes all
input characters
(including
special
function characters such as CTRL/C)
to the driver input
buffer.
A nonprivileged user can display all terminals that have the
option enabled but can only enable the read-pass-all option
for TI:. A privileged user can enable the read-pass-all
option for any terminal.
When you omit =TTnn:, the system displays all the
that have the read-pass-all option enabled.

terminals

Examples:
>SET /RPA
RPA=TTO:
RPA=TTl:
Displays all the terminals where input characters
are passed directly to the input buffer for the
full-duplex terminal driver.
)SET /RPA=TT3:
Enables the read-pass-all option for TT3:.
/NORPA[=TTnn:]
{Full-duplex
terminal
driver
only.)
Disables
the
read-pass-all option.
The terminal driver does not pass
special function input characters (such as CTRL/C) from the
terminal to the driver input buffer.
A nonprivileged user can display all terminals that have the
option disabled but can only disable the read-pass-all
option for TI:.
A privileged user can
disable
the
read-pass-all option for any terminal.
When you omit =TTnn:, the system displays all the terminals
that do not pass special function characters to the terminal
driver input buffer.

3-203

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NORPA
NORPA=TT2:
NORPA=TT4:

Displays all the
terminals
read-pass-all option disabled.

that

have

the

>SET /NORPA=TT3:

Specifies that TT3:
not pass special function
input characters to the input buffer for the
full-duplex terminal driver.

systems·only.}·Displays secondary·P<>ol use· otf
The display is fo the· following .forma.t; ·

The number of freeblocks in second(lry pool in units of
32 ...word (decimal) blocks.
secsiz

The size of secondary
(decimal) blocks.

pool

units

32-word

pct fr

The percentage of free blocks in secondary pool.
Example:
>SET: /SECPOL

SECPOL=28 5 .>:640 •• : 44 %

amount of
/S~E.I~LI =T'rn

n•:·]

. •. (RSX~llM-J?LUS systems: onl}f.J (;auses unsolicited·

··. : tf1e . ·. specified terminal. to be p-rocess~d .serially rather ·... ····.·•.·• .
'i•J:l. papal let ... usually, i f y<.:>u ... enter 9nother ... comm.ana... Jin~
.before.: a P.revious. <:e>mmand. line. ha:s . completed .• executing., t11·~
· s;yst~m. P+.o<:-es13,es·.·~he.··. second•·.• Tine· -19.• parallel . · with••. the .. first;.:
ltll1er1 you request. serial execution >of .qommanc! li.tJeSf t~o.i:.1:eve~; •
t~e· ·System. processes the first command .. lin.e ·...• and
then: the;
secondcommand . line . . after t:he: first . iS·. finished.

kn.,:gri 1eged •use~• can diSpraycan.• alonlythe.• t<'.rmi.nat s . tha~. h~~~<
fqr·?
vi

th~ 'Se'(ial ·optl:con
···Tt:~·
Privileged

termil)al. ·

enabled, but

·enable

3-204

en(lble tl'.le QP~ton ·.
the ·opti.on for· .aqy:::

MCR COMMANDS

SET (Cont.)

/SLAVE[=TTnn:]
Establishes the specified terminal as one that can enter
data only if it is solicited from a task by a READ QIO$.
Thus, the specified terminal always rejects unsolicited
input (other than CTRL/O, CTRL/Q, and CTRL/S}.
A nonprivileged user can display all slave terminals but can
only establish TI:
as a slave terminal.
Privileged users
can establish any terminal as a slave terminal.
When you omit =TTnn:, the system displays all the
currently classified as slaved.

3-205

terminals

MCR COMMANDS

SET {Cont.)
Examples:
>SET /SLAVE=TT3:
Establishes TT3: as a terminal
enter data solicited by a task.

that

can

only

>SET /SLAVE
SLAVE=TT3:
Displays all the slaved terminals.
/NOSLAVE[=TTnn:]
Removes slave status from a specified terminal.
A nonprivileged user can only display
the
nonslaved
terminals. A privileged user can set any slaved terminal to
be nonslaved.
When you omit =TTnn:, the system displays all the
terminals.

nonslaved

Examples:
>SET /NOSLAVE
NOSLAVE=TTO:
NOSLAVE=TTl:
NOSLAVE=TT2:
NOSLAVE=TT4:
Displays all the nonslaved terminals.
>SET /NOSLAVE=TT3:
Sets TT3:

to be nonslaved.

/SPEED=TTnn: [recv:xmit]

Establishes the receive and transmit baud rate for terminals
attached to the system through a DHll, DHVll, DZll, or DZVll
variable-speed multiplexer. The argument "recv" is the baud
rate at which characters are input to the computer from the
terminal and the argument "xmit" is the baud rate at which
characters are output to the terminal from the computer.
Both must be specified in setting the speed.
If neither
argument is specified, the current settings are displayed.
A nonprivileged user can display the speed settings for any
terminal, but can only set the speed for TI:. A privileged
user can set the speed for any terminal.

Valid baud rates for the DHll are O,
50,
75, 110, 134.5,
150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, EXTA
(user-specified baud rate A}, and EXTB (user-specified baud
rate B) •

3-206

April 1983

MCR COMMANDS

SET (Cont.)
Valid baud rates for the DHVll are 75, 110, 134.5, 150, 300,
600, 1200, 1800, 2000, 2400, 4800, 9600, and 19200.
Valid baud rates for the DZll and DZVll are 50, 75, 110,
134.5, 150, 300, 600, 1200, 1800, 2000, 2400, 3600, 4800,
7200, and 9600.
If you have a DZll or DZVll, the receive and transmit baud
rates must be the same because these multiplexers do not
support split speeds.

3-206.1

April 1983

MCR COMMANDS

SET (Cont.)
Examples:
>SET /SPEED=TT3:
SPEED=TT3:2400:2400
Displays the current speed setting for TT3:.
>SET /SPEED=TT3:9600:9600
Sets the receive and transmit baud rates for
to 9600.

TT3:

·.1suB=rnn.ame .:.~riam¢:£ :i,ase.:.si
(R~x.-1111 . . . . sy~~~s

p~~P<3;:rtJticms· . •. ?an

m.a.in ·part{tion.S:•
mname . ·

The 1~ to
:$.uppartiti()ri
·this partition.

l~ to
6-character
subpar.tltfbn
name;.
The
subpartition. being defi11ed. b~come~. a subpa:rtition Qf
main . . ·J;>ar.tition .specifi.ea . •.·in mname.•
,,, -~'.· ·,:·' ;,,: .·.. ·:'·· ..'.: ~- : .'.'. :'.'. '. :··.·. .·.'.!."=:"'·!· ··_, ,,, .. ·.· . '. '.'

base ... address•.. ·. of. ·<~h~
as a numbe:r- of. 64-J:>yte bJ9·9k;s;.~·
.·.·· .... ·. i

stil?Pattiti on·,

i .·.; ;···•·>/ ; 5' <'

The size ofthe s.ubpa:r.tition} ·sPec.ifl~d ·as. a
.·. 64;byt~ b1()ck.s

·.· ·. . ..·.. ·. . . . . · · · ·.·.·. .... ·. i \. .· · · · · · · · · ·

~~fuP.t?:C ·

·.....

·Base ana• .. sfze can.be enter~di~· ani•of.the '.f~l foiNing :fo~rnats'
{nnnri i s . a. number in bytes to wh i.c;h. the system applies a
mul tipLication factor to determine the value used):
Fo.rmat

Calculated Value

nnnn
nnnn ..
nnnK
nnn.K

Octal {nnnn*lOO}
Decimal (nnnn. *·64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

Valid ranges for calculated values (in words) are:
Octal
Decimal
Octal K
Decimal K

O<=base<lOOOO
O.<=base<4096.
OK<=base<200K
O.K<=base<2047.K

3-207

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

MCR COMMANDS

SET (Cont.)
For . example I any of the folJ,o:wing
allocate a 204e (lO)'"'"bYte partition.

inputs

'llber1 you . omit ?ase and ~i ze., the system a is·plays the cilrrept
. values f.qr . t:ri:e. named subpin::ti tion .•
Example:

in
SYSPAR •.· The base. address for.MCRPAR
44500{8] and its length is 5600 (8) bytes.

part~J::ion

/NOSUB=rnname:sname
(RSX-llM systems only; privileged option.) Eliminates the
named subpartition (sname) from the specified main partition
(mname) ••
Exan.tple:

>SET /NOSUB=SYSPAR:MCRPAR
Eliminate:> the subparti ti on MCRPAR from
pa'rtitfo'n ··sYSPAR.

the

main

/SWPC [=nn]

•

Defines the number of clock ticks for a single Executive
swapping interval.
The parameter nn is in the range 0
through 45,568(10) and can be an octal value, or decimal if
followed by a period (.). See the RSX-llM or RSX-llM-PLUS
System Generation
and
Installation
Guide
for
more
information.
A nonprivileged user can display the value for the interval,
but only a privileged user can change the value.

When you omit =nn, the system displays the current value for
the interval.
Examples:
>SET /SWPC
SWPC=30.
Displays the current number of clock ticks for the
swapping interval.
>SET /SWPC=60.
Sets the new swapping interval to 60(10).

3-208

April 1983

MCR COMMANDS

SET {Cont.)
/SWPR [=nn]
Defines a priority range for
Executive swapping.
The
parameter nn is in the range 0 through 127(10) and can be an
octal value, or decimal if followed by a period (.}.
The value for /SWPR affects the installed priority of all
tasks.
Each task
is
initiated at its installed priority
plus the value for nn (priority + nn}.
While the task
is
executing,
its priority is decremented until it becomes the
installed priority minus the value for
nn
(priority - nn}.
When the priority reaches this lower limit, the task is
swapped out so that another task with a higher priority can
execute.
The priority for the new task changes in the same
way.
See the RSX-llM or RSX-llM-PLUS System Generation and
Installation Guide for more information.

A nonprivileged user can display the value for the priority,
but only a privileged user can change the value.
When you omit =nn, the system displays the current value for
the priority range.
Examples:
>SET /SWPR
SWPR=5.
Displays the current
priority range.

value

for

the

swapping

>SET /SWPR=lO.
Sets the new priority range to 10(10).
/SYSUIC[=[uic]]
Establishes the UIC for the system and all system tasks.
On
most unmapped systems,
the system UIC is [1,50];
on most
mapped systems, the system UIC is [1,54].
These UIC values
are the initial defaults on virgin systems.
The UIC also
becomes the default UIC used by the LOAD command and
the
install-run-remove option of the RUN command.
A nonprivileged user can display the system UIC, but only
privileged user can change it.

When you omit =[uic], the system displays the current system
UIC.
Examples:
>SET /SYSOIC
SYSUIC=[l,54]
Displays the current system UIC.
>SET
Sets the system UIC to [3,54].

3-209

April 1983

•

MCR COMMANDS

SET (Cont.)
/TERM=TTnn: [value]
(Full-duplex terminal driver only.) Establishes the terminal
type (value) for the specified terminal.
Supported standard
terminal types are:
ASR33
ASR35
KSR33
LA12
LA30P

LA30S
LA34
LA36
LA38
LAlOO

LA120
LA180S
VT05B
VT50
VT52

VT55
VT61
VTlOO
VT101
VT102

VT105
VT125
VT131
VT132

A nonprivileged user can display the terminal type for any
terminal but can only establish the term1nal type for TI:.
A privileged user can establish the terminal type for any
terminal.
When you omit the value parameter, the system
terminal type for the specified terminal.

displays

the

MCR also accepts an alternate form of the command. You can
specify the terminal type and equate it to the desired
terminal.
This
automatically
associates
certain
characteristics of the particular terminal type with the
specified terminal.
(See the RSX-llM/M-PLUS I/0 Drivers
Reference Manual for a list of the implicit characteristics
for each terminal type.) The command is in the format:
SET /term-type=TTnn:
where term-type is one of the standard terminal types.
that the terminal types are mutually exclusive.

Note

The half-duplex terminal driver also accepts the /term-type
form of the command.
However, the only legal terminal types
for the half-duplex driver are /ASR33, /LA30S, and /VT05B.
The command associates implicit characteristics of the
terminal type with the specified terminal, but, unlike the
full-duplex terminal driver,
the types are not mutually
exclusive.
The following list describes the effects of the keywords for
the half-duplex terminal driver:
/ASR33

Converts lowercase letters
to
uppercase
before they are output to the terminal.

/LA30S

Indicates that fill characters necessary for
the LA30S terminal are used after a carriage
return. The number of fill characters used
depends on the current carriage position at
the time the carriage return occurs.

/VT05B

Sets a vertical fill of three nulls after a
line feed on 60 Hz systems and of four nulls
on 50 Hz systems.

3-210

MCR COMMANDS

SET (Cont.)

Examples:
)'SET /TERM=TT3:
TERM=TT3:VT52
Displays the terminal type for TT3:.

>:SET /TERM=TTl:LA36
Establishes TTl:

as an LA36 terminal.

>SET /LA36=TT1:
Same effect as previous example;
as an LA36 terminal.

establishes TTl:

You can also use an alternate command form to display all
the terminals that are not of a specific type. The format
is as follows:
SET /NOterm-type
Note that you cannot negate a terminal type for a terminal.
You can only display the terminals n~t of a specific type.
Negating terminal type returns a syntax error since the
terminal would be of indeterminate type.
/TOP=pname:value
Directs MCR to move the top boundary of the specified
system-controlled partition up or down the amount indicated
by the value parameter, or sets the partition size to that
amount.
The keyword modifies the top boundary of a
partition even if the partition has tasks installed in it.
If you modify the partition so that it may be too small to
hold the tasks installed in it, MCR displays a warning
message but modifies the partition anyway.
pname
The 1- to 6-character alphanumeric
system-controlled partition.

name

for

the

five

formats:

value
The number of 64-byte blocks.
The value parameter can be supplied in
+value, -value, value, +* or *, and -*

3-211

MCR COMMANDS

SET (Cont.)
+value
Moves the top boundary up by the specified amount.
Moving the top boundary up makes the partition
larger.
NOTE
You can supply the value in the same units
as the base and size parameters in the
/MAIN
or
/PAR
keywords
described
previously.
-value
Moves ~he top boundary down by the specified
amount.
Moving the top boundary down makes the
partition smaller.
value
Establishes the total partition size equal to
specified value by moving the top boundary.

the

+* or *
Moves the top boundary up as far as possible.
This format causes the top boundary to move to the
bottom boundary of the partition above it or to
the top of memory if the partition is the top
partition in memory.

-*
Moves the top boundary down as far as possible.
This format causes the top boundary to move down
to the top of the first
fixed
task,
common, or
driver
in the partition at the time the /TOP
keyword is executed.
If nothing
is loaded into
the partition, the partition assumes a size of one
64-byte block.
Examples:
>SET /TOP=TSTPAR:+S
Moves the top boundary
64-byte blocks.

TSTPAR

far

five

>SET /TOP=PAR23:-*
Moves the top boundary of PAR23
possible.

3-212

down

MCR COMMANDS

.,\~ ~
\ \ y\i,.

SET (Cont.)

\.)

/TYPEAHEAD[=TTnn~
(Full-duplex terminal driver only.) Instructs the terminal
driver to store input characters in a buffer before passing
the characters to a requesting task.
Thus, characters input
between requests are not lost.

A nonprivileged user can display all terminals that have
typeahead option enabled but can only enable the option
TI:.
A privileged user can enable typeahead for
terminal.
These rules also apply to the size of
typeahead buffer.
When you omit =TTnn:, the system displays all the
that have typeahead enabled.

the
for
any
the

terminals

Examples:
>SET /TYPEAHEAD
TYPEAHEAD=TTl:
TYPEAHEAD=TT2:
TYPEAHEAD=TT7:
TYPEAHEAD=TT12:
Displays all the terminals for which the terminal
driver stores input characters in a buffer before
passing them to a task.
>SET /TYPEAHEAD=TT3:
Enables the typeahead option for TT3:.
/NOTYPEAHEAD[=TTnn:]
(Full-duplex terminal driver only.) Disables the typeahead
option;
the terminal driver does not store input characters
in a buffer to prevent their loss.
A nonprivileged user can display all terminals that have the
typeahead option disabled but can only disable the option
for TI:.
A privileged user can disable typeahead for any
terminal.
When you omit =TTnn:, the system displays all the
that have typeahead disabled.

3-213

terminals

MCR COMMANDS

SET (Cont.)
Examples:
>SET /NOTYPEAHEAD
NOTYPEAHEAD=TTO:
NOTYPEAHEAD=TT4:
Displays all the
disabled.

terminals

that

have

typeahead

>SET /NOTYPEAHEAD=TT3:
Disables the typeahead option for TT3:.
/UIC[=[uic] [:TTnn:]]
Establishes the specified UIC as the default UIC for the
terminal.
Unless TTnn:
is specified, the default UIC is
set for TI:.
If the system supports multiuser protection
{some RSX-llM and all RSX-llM-PLUS systems) and you are a
privileged user,
the command also sets the terminal's
protection UIC (see Section 2.2.1).
In a single-user system, all tasks run from the terminal are
run with the UIC of the terminal.
In a multiuser protection
system, a privileged user can override the terminal UIC with
the /UIC keyword for the RUN command.
External MCR function
tasks are also requested with the terminal's UIC.
These
tasks are the MCR MOUNT, INSTALL, DISMOUNT, and UFO commands
{which run as tasks) and all system-supplied software.
A nonprivileged user can only display and change the default
UIC for TI:. A privileged user can display and change the
default UIC for any terminal.
When you omit =[uic],
the system displays the current
default UIC for TI:.
When you omit =[uic] but specify
=TTnn:, the system displays the current default UIC for that
terminal.
Examples:
>SET /UIC
UIC=[l0,10]
Displays the current default UIC for terminal TI:.
>SET /UIC=[303,3]
Sets the default UIC for terminal TI:

to [303,3].

>SET /UIC=TT12:
UIC= [ 12, 20]
Displays the current default UIC for TT12:.

3-214

MCR COMMANDS

SET (Cont.)
/VFILL[=TTnn:]
(Full-duplex terminal driver only.)
Enables the vertical
fill characters option for the specified terminal.
The
option instructs the terminal driver to add four fill
characters following each line feed.
A nonprivileged user can display all terminals that have the
vertical fill characters option enabled but can only enable
it for TI:.
A privileged user can enable the option for any
terminal.
When you omit =TTnn:, the system displays all the terminals
that have the vertical fill characters option enabled.
Examples:
>SET /VFILL
VFILL=TTO:
VFILL=TTl:
Displays all the terminals that have the
fill characters option enabled.

vertical

>SET /VFILL=TT3:
Instructs the full-duplex terminal driver to add
four fill characters following each line feed at
TT3:.
/NOVFILL [ =TTnn:]
(Full-duplex terminal driver only.)
Disables the
fill characters option for the specified terminal.

vertical

A nonprivileged user can display all terminals that have the
vertical fill characters option disabled but can only
disable it £or TI:.
A privileged user can disable the
option for any terminal.
When you omit =TTnn:, the system displays all the terminals
that
have the vertical
fill characters vertical fill
characters option disabled.
Examples:
>SET /NOVFILL
NOVFILL=TT2:
NOVFILL=TT4:
Displays all the terminals that have the
fill characters option disabled.
>SET /NOVFILL=TT3:
Disables the option for TT3:.

3-215

vertical

MCR COMMANDS

SET (Cont.)
/WCHK [ =ddnn:]
Specifies that all write operations are to be followed by a
write check for
all Files-11 disk devices except DX:
and
DY:. The checks assure the reliability of data transfers to
the specified disk.
However,
writing is slowed because
there are two I/O operations instead of just one.
On RSX-llM, Executive support for write checking is a system
generation option and must be selected for this command to
have any effect.
On RSX-llM-PLUS,
support for
write
checking is always included.
A nonprivileged user can only display the devices that have
write checking enabled. A privileged user can enable write
checking for any device that supports it.
When you omit =ddnn:, the system displays all the
disk devices that have write checking enabled.

Files-11

Examples:
>SET /WCHK
WCHK=DBO:
WCHK=DKO:
Displays all the Files-11 disk devices
write checking enabled.

that

have

for

the

>SET /WCHK=DKl:
Enables write checking for DKl:.
/NOWCHK[=ddnn:l
Specifies that-write checking is
specified device.

disabled

A nonprivileged user can only display the devices that have
write checking disabled.
A privileged user can disable
write checking for any device.
When you omit =ddnn:, the system displays all the Files-11
disk devices except DX:
and DY:
that have write checking
disabled.
Examples:
>SET /NOWCHK
NOWCHK=DBl:
Displays all the devices that
checking but have it disabled~
>SET /NOWCHK=DKl:
Disables write checking for DKl:.

3-21~

support

write

MCR COMMANDS

SET (Cont.)
/WRAP [ =TTnn : ]
(Full-duplex terminal driver only.) Enables the wrap-around
option.
The wrap-around option instructs the terminal
driver to generate a carriage return/line feed sequence when
the number of input characters exceeds the terminal's buffer
size. The carriage return/line feed sequence is transparent
and does not appear in the input buffer.
A nonprivileged user can display all terminals that have the
wrap-around option enabled but can only enable it for TI:.
A privileged user can enable wrap-around for any terminal.
When you omit =TTnn:; the system displays all the
that have the wrap-around option enabled.

terminals

Examples:
>SET /WRAP
WRAP=TTl:
WRAP=TT2:
Displays all the terminals for which a carriage
return/line feed sequence is generated following
an input string that exceeds the terminal's buffer
size.
>SET /WRAP=TT3:
Enabies the wrap-around option for TT3:.
/NOWRAP[=TTnn:]
Disables the wrap-around option;
the terminal driver does
not accept input characters beyond the buffer size for the
terminal.
A nonprivileged user can display all terminals that have the
wrap-around option disabled but can only disable it for TI:.
A privileged user can disable the option for any terminal.
When you omit =TTnn:, the system displays all the
that have the option disabled.

terminals

Examples:
>SET /NOWRAP
NOWRAP=TTO:
NOWRAP=TT4:
Displays all the
terminals
wrap-around option disabled.

that

have

>SET /NOWRAP=TT3:
Disables the wrap-around option for TT3:.

3-217

the

MCR COMMANDS

SET (Cont.)
Notes on Memory Allocation Keywords (see Table 3-3):
•

If a partition contains an installed task common or loaded
driver and a keyword (for example, /NOMAIN or /NOSUB) attempts
to eliminate the partition, the system rejects the command.

•

on. RSX-ilM systems,· .a keyword 'th~'f eii~inates a main Parf:ition
also ..... eliminates .. all, its !;l\b:partitiol'.lS• ....... A keyW,p.rd theit
'eliminates . a .. ·. . $Pecified subpar.tition 'eliminates only that
specified. ·subpa·rti.t·ion.

·• i·on RSX~I.lM systems fl ·if a. keywqrd a.,t~eiripts. t.o el iinfn~te..~ ·. r~ain

·.pp.rtition that ha•$ .s11b:pp.rtittop:s i:J'l whi.ch. t;asks.. ·are ·.installed,
t:,he $Y~t:,em rejects: :t!fte .~:e,:~o.r:q until <tbo$e• tasks are removed
·from· ,the·.· $Ubpaxtlt'i9n.s.

•

When defining a main partition or a subpartition, the name
must not already be defined as a partition. In addition, a
main partition cannot overlap any other main partition, nor
can a subpartition of a main partition overlap any other
subpartition of the main partition. An exception is for DEV
partitions,
which can overlap.
Subpartitions cannot be
created on the I/O page.

•

On RSX'--HM systems,· all :pa·r·titions exc·ept the resident loader
par:titio•n, LDRPAR, are c-0n;sid•e1red to be· urser partitions :by the
/POOL k'e)fWOrd •. Th'us, for example, SYS.PAR is considered to be
a user .partition.
·
· .,

•

Once you allocate space to the dynamic storage region (pool),
the space can never be recovered for use in partitions.

•

System-controlled partitions cannot include
subpartitions
explicitly defined by the SET command. An attempt to define
subpartitions in system-controlled partitions in this way will
be rejected. The Executive dynamically defines subpartitions
in a system-controlled partition as they are needed for tasks
installed in the partition.

Command Error Messages:
SET -- ALIGNMENT ERROR
An attempt was made to create
address or size conflicted
physical memory size.

a partition, but the base
with existing partitions or

SET -- CANNOT REMOVE EXECUTIVE COMMON
The executive commons (on systems that support executive
partitions) cannot be removed from the running system. The
executive commons must be installed and removed with VMR
(see the RSX-llM/M-PLUS System Management Guide).
SET -- CLI IS RESTRICTED
An attempt was made to set a terminal to a CLI, but the CLI
was initialized with the /RESTRICT subkeyword. This means
that only the CLI itself can set a terminal to the CLI.

3-218

MCR COMMANDS

SET (Cont.)
SET -- CLI REQUIRES THE TERMINAL TO BE LOGGED IN
An attempt was made to set a terminal to
terminal is not logged in.
The CLI
commands from logged-in terminals.

a CLI, but the
will only accept

SET -- DEVICE BUSY
An attempt was made to set a terminal characteristic
terminal that is busy (attached).

for

SET -- DEVICE NOT TERMINAL
An attempt was made to set terminal
device that is not a terminal.

characteristics

SET -- DEVICE NOT VARIABLE SPEED MULTIPLEXER
An attempt was made to set the baud rate for a terminal that
was
not
attached to a DHll, DHVll, DZll, or DZVll
multiplexer.

SET -- FEATURE NOT SUPPORTED
The command keyword specified a feature or device
currently not incorporated into the system.

that

SET -- INVALID SPEED
The multiplexer line does not support the requested speed,
or the command specified unequal receive and transmit baud
rates for a DZll or DZVll.
The DZll and DZVll do not
support split speeds.
SET -- LINE NOT DZll
The command attempted to set to remote a line that
attached to a DZll multiplexer.

was

not

SET -- NON EXISTENT MEMORY
An attempt was made to define
memory.

partition

nonexistent

SET -- PARTITION ALREADY EXISTS
An attempt was made
already in use.

define

partition

with

name

An attempt was made to move the top boundary of a
with
the /TOP keyword.
This can be done only
system-controlled partitions.

with

SET -- PARTITION NOT SYSTEM-CONTROLLED

3-219

April 1983

MCR COMMANDS

SET (Cont.)
SET -- SPACE USED

An attempt was made to create a partition or subpartition in
a storage area already occupied.
SET

TASK INSTALLED IN PARTITION

An attempt was made to eliminate a partition or subpartition
that contains installed tasks.

:•s.£rr· ~;; 'Tbo< MAN&''SOBPARTITiONS
'.·.···(·~sil•iir-t•·. ··.'.s·y~.t~~.s •.·.·····.o~•.ly··~···>••········An···· a·t.teri\pt···••·w~·s made
'~nan .• ~~ven • . p1:1bpaJ:'t1tions; ~ .• ·. ·. A
max imUft1. o~j. seven s(lbpaitit ions.~.
-: . ·.· . . . : .· ' ·.· .. ·. ·.>:·. :.. _·;: . . ·. :· -~ .·: .· '

S.ET .;_~:. lJNI(NOWt-1 MA.lN

par.ti ti on . is

.•.more
to> a

PARTiTl()N

{RSX .... HM systems only.) An attempt
sµbpartition· in a nonexistent .main
US'.ER <pA.RTITION >32K NOT PERMITTED

(RSX-llM systems only.) The command attempted to create a
partition gxeater than 32K.
User-controlled partitions
greater than 32K cannot be crep.ted in systems that (lo not
support extended logical address space, a system generation
··option.

SET -- WRITE CHECK NOT SUPPORTED

An attempt was made to enable write checking on a device
that does not support it. See the description of the /WCHK
keyword for the valid devices.

3-220

MCR COMMANDS

SSM
SYSTEM SERVICE MESSAGE (P)
The SSM command inserts text into the error
appears in error log reports produced by
generator.

log
the

file.
error

The text
log report

For information on the report generator, see the RSX-llM/M-PLUS
Logging Manual.

Error

Format:
SSM message
message
Any text string up to a maximum of 79 characters.
Example:
>SSM TESTING VOLUME INTEGRITY ON DKl:, POSSIBLE FORMAT ERRORS.
Inserts the message into the error log file.

3-221

MCR COMMANDS

3-222

MCR COMMANDS

TAL
TASKLIST - ATL FORMAT (NP)
The TAL command displays the names and status of all tasks or of a
specific task installed in the system. The display format is the same
as that of the ACTIVE TASK LIST (ATL) command. See the ATL command
for a description of the printout.
Format:
TAL [tasknarne]
taskname
The name of a specific task.
Examples:
RSX-llM systems
>TAL
LDR ••• 112050 LDRPAR 112404 00253100-00255600 PRI - 248. DPRI - 248.
STATUS: -CHK FXD STP -PMD PRV NSD
TI - COO: IOC - O. BIO - 0. EFLG - 000001 000000 PS - 170000
PC - 120354 REGS 0-6 120212 010364 177777 107646 074714 107614 120166
RMDEMO 053550 GEN
046020 01036700-01065600 PRI - 225. DPRI - 225.
STATUS: -CHK WFR -PMD PRV MCR
TI - TTO:
IOC - 0. BIO - 0. EFLG - 000021 040000 PS - 170010
PC - 125234 REGS 0-6 000000 136257 132066 000000 136321 134560 121166
FllACP 111550 GEN
067150 01164600-01230600 PRI - 149. DPRI - 149.
STATUS: STP ACP -PMD PRV NSD CAL
TI - COO: roe - o. BIO - o. EFLG - 000002 000001 PS - 170000
PC - 135244 REGS 0-6 000010 000066 000016 000000 067420 111550 120244
MCR •.• 110160 SYSPAR 114514 00202600-00212600 PRI - 160. DPRI - 160.
STATUS: STP -PMD PRV MCR CLI NSD CAL
TI - TT51:
IOC - 0. BIO - O. EFLG - 000001 040000 PS - 170000
PC - 122436 REGS 0-6 000000 120476 122032 120432 010554 043552 120366
RSX-llM-PLUS systems
>TAL
••• RMD 006246+ GEN
114020 00741000-00770200
STATUS: -EXE -CHK -PMD PRV PRO XHR
TI - NONE IOC - O. BIO - O. EFLG - 001400
.•• DMO 006224+ GEN
114020 00741000-00756500
STATUS: -EXE -PMD PRV PRO
TI - NONE IOC - O. BIO - O. EFLG - 001326
,,:· . '.··:.:·'''.T:\f<:>'·'."'

....·

. ~h·.:

PRI - 225.

DPRI - 225.

000000
PRI - 160.

DPRI - 160.

000000

..... :G·P·$·•,::···;~~~···•·.•··~i.u~.·.·s.i:·~~l·····:•••:<:-l->··•:•.••·••£<>i.~a·•~I~<J••·····•the•·.·····•·'l'c$•••·•···f.i.e1.a £·0.r·.····.•···,1 . :.. ta·sJ(

...·.· · · ·..a:t . . h~'t.>:;·the .• t<ask i.s .±nstall~d. in .• ·seporid~ry. pool•.. ·xn:.·.·•tlie TAL
· · ilA~Pla:Y~<'·'tl'l.~se t,~.sks · •. ·.follow• J::b~····. i;ask:s . . ins i;:al 1 ed ·.~.n •·,primzu::y pool.

3-223

MCR COMMANDS

TAS
TASKLIST (NP)

The TASKLIST command displays a description of
The display contains:

•

each

Task name

Task version identification

Partition name

Task priority

Size of task in bytes (octal)

Load device identification

Disk address logical block number (octal)

Task memory state

installed

task.

Qn :RSk-llf.t~PL~~i,[···.;the· ·····d·f~pl a·Y . . .•.i.1·.~·t~. ········tj~~·. ,. t.a·.s]<:s .itl~t~••1.i~c1· i·n pr . i~~~·~· ·p9q.l
and then t;;p,ose :installed···. in :~eg<>:ndqpy .pQQlo.

Format:
TAS[KLIST]

[taskname] [/DEV=ddnn:]

taskname
The name of a specific task.
/DEV=ddnn:
Displays the names and status of all
specified device.

tasks

installed

the system
both taskname and /DEV,
information about the task installed from that device.

I f you specify

from

the

displays

Examples:
>TAS
LOR .•• 07.05
TKTN
03.3
RMDEMO X03.03
MTAACP 0006
FllMSG VOOlO
MCR ••• 3.2
TAST17 01
••• STO 000005
••• BYE 01.5
FllACP M0235
SECFCP M0235
DTAACP M0235
••• OMO 03.2
••• I NI 03.1

LDRPAR
SYS PAR
GEN
GEN
GEN
SYS PAR
GEN
SY SPAR
GEN
FCPPAR
GEN
GEN
GEN
GEN

248.
248.
225.
200.
200.
160.
160.
151.
150.
149.
149.
149.
140.
140.

00002200
00010000
00013700
00013000
00005400
00010000
00025000
00010000
00040000
00040000
00026200
00026200
00040000
00040000

3-224

LB0:-01035303 FIXED
LBO :-01126742
SY0:-00352100
DS0:-00000777
SY0:-01053030
LB0:-01051626
LB0:-01051676
SY0:-01136540
LB0:-01051337
LB0:-01052445
SY0:-00055463
SY0:-01052554
LB0:-01051403
LB0:-01051561

April 1983

MCR COMMANDS

TAS (Cont.)
••• MOU 03.01
••• UFD V0407

GEN
GEN

140. 00040000 LB0:-01051653
140. 00040000 LB0:-010

{User typed CTRL/O to suppress further output.)
>TAS /DEV=DRO:
DROOFl M0323 SY SPAR 149.
FllACP M0323 GEN
149.
DBOlFl M0323 GEN
149.
DB07Fl M0323 SYS PAR 149.
ERR LOG Vl. 01 GEN
148.
PMD ••• 04.0
GEN
140.
HRC ••• 02
GEN
140.
SYS LOG 1. 02
GEN
130.
••• INS 06
GEN
100.

00055700
00044000
00044000
00044000
00042200
00015200
00055100
00016300
00035400

LB0:-00475656 FIXED
LB0:-00315566
LB0:-00315566
LB0:-00315566 FIXED
LB0:=00335276
LB0:-00503535
LB0:-00505331
LB0:-00504250
LB0:-00502750

The displays contain from left to right:
task name, task version
identification, partition name,
task priority, task size, load
device identification, logical block number on the load device,
and task memory state. On a processor with less than 124K words
of memory, the size field {fifth column) contains 6-digit rather
than 8-digit numbers.
FIXED indicates that the task is fixed in memory.
CHECKPOINTED indicates that the task has been
memory to make room for a higher priority task.

swapped

out

If the task version identification is missing (the rest of the
line is offset to the left) or garbage, the task was installed
from a disk that has since been removed from the drive or
replaced by another one.
Command Error Message:
TAS -- TASK NOT IN SYSTEM
The task specified in the
installed in the system.

3-225

command

line

not

currently

MCR COMMANDS

TIM
TIME (NP,P)
The TIME command allows you to:
•

Set the current time of day (privileged)

•

Set the current date (privileged)

•

Display the current time and date

Format:
TIM[E]

[hrs:mins[ :secs]]

[ml/day/year]

or
TIM[E]

[hrs:mins[ :secs]] [day-m2-year]

hrs
Hours in the range 0 through 23.
mins
Minutes in the range 0 through 59.
secs
Seconds in the range 0 through 59 (optional parameter).
ml
Numeric representation of the month in the range 1 through 12.
m2
Three-letter abbreviation for the month.
day
Day in the range 1 through 31.
year
Year in the range 0 through 99.
thus 1981 is entered as 81.

The year is

relative

1900,

Notes:
•

When the command specifies neither time nor date, the system
displays the current time and date on the entering terminal.

•

If a privileged user specifies the time and date, the command
sets the clock and calendar.
If only the time is specified,
only the clock is set;
if only the date is specified, only
the calendar is set.

3-226

MCR COMMANDS

TIM (Cont.)

•

A privileged user can specify the
order.

time

•

The form used to specify the date does not affect the display
format.
The date is always displayed as day-month-year.

•

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

and

date

terminating

period

Examples:
>TIM
10:23:31 26-MAR-81
Displays the current time and date.
>TIM 11:37 4/19/81
Sets the time to 11:37:00 and the date to 19-Apr-81.

3-227

either

MCR COMMANDS

UFO
USER FILE DIRECTORY (NP,P)
The UFD command creates a User File Directory
(UFD)
on a
Files-11
volume and enters its name into the Master File Directory (MFD).
(See
Section 2.1.1 for further information about UFDs.)
Before creating a UFD, you must first initialize and
MOU) the volume.

mount

(!NI

and

On multiuser protection systems, a nonprivileged user can create a UFD
only on a volume mounted on a
privately allocated device.
A
privileged user can create a UFD on any mounted volume.
Format:
UFD ddnn:[volume-label] [g,m] [/keyword(s)]
ddnn:
Device unit containing the volume on which the UFD being
will reside.
Default: none;

created

must be specified.

volume-label
If specified, the label is compared with the label on the volume.
If the names match, a UFD can be created.
If they do not match,
the command is rejected.
Default: null;

no check is made.

[g,m]
The UIC for the UFD.
The UIC establishes the owner of the UFD.
The variables g and m represent the group and member numbers,
respectively, and can be in the range 1 through 377(8).
The
square brackets are required syntax.
Default: none;

must be specified.

/ALLOC=number
The number of directory entries for which space in the UFD is to
be allocated.
The specified number is rounded up to the next
multiple of 32(10).
Default: 32(10)
/PRO=[system,owner,group,world]
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
nu Delete

3-228

MCR COMMANDS

UFO (Cont.)
In each instance, the absence of the code
class is denied the access right.

means

that

the

user

The square brackets are required syntax.
Defaults:

[RWED,RWED,RWED,R]

Example:
>UFD DMl: [l, 1]
Creates a user file directory (UFD) for the UIC
[1,1]
on
DMl:.
The name and file number of the UFD file are entered
into the MFD.
The name of the UFD is 001001.DIR;l, and its
owner is UIC [1,1].
Command Error Messages:
UFD -- CAN'T READ MCR COMMAND BUFFER
The UFD was initiated by a RUN command rather than as an MCR
command.
UFD -- DIRECTORY ALREADY EXISTS
The requested UFD already existed on the volume.
UFD -- FAILED TO CREATE DIRECTORY
No space existed on the volume or an I/O error occurred.
UFD -- FAILED TO ENTER IN MFD
There was no room in the MFD or on the
error occurred on the volume.

volume,

I/O

UFD -- HOME BLOCK I/O ERROR
An error was detected while the volume home block was
read.

being

UFD -- NOT FILES-11 DEVICE
The volume on which the UFD was to be created was not
Files-11 volume and therefore could not support UFDs.

UFD -- VOLUME NOT MOUNTED
The volume on which a UFD is to be created must be mounted.
UFD -- WRITE ATTRIBUTES FAILURE
An error was encountered while the attributes of either
MFD or the newly created UFD were being written.

the

UFD -- WRONG VOLUME
The volume label and the label specified in the command line
did not match.

3-229

MCR COMMANDS

UNB
UNBLOCK (NP,P)
The UNBLOCK command continues the execution of a previously blocked
active task or allows a previously blocked dormant task to execute if
it is requested to do so.
{See the description of the BLOCK command.)
On systems with multiuser protection, a nonprivileged user can unblock
any active task running from the issuing terminal. A privileged user
can unblock any task. On systems without multiuser protection, any
user can unblock any task.
The system automatically unblocks an active task when it is aborted.
Format:
UNB[LOCK]

[taskname] [/TERM=TTnnn:]

taskname
The name of the task.
If you omit taskname, the command unblocks
the task requested from the issuing terminal {task TTnn).

Examples:
>UNB TST
Unblocks task TSTT36 and allows it to continue executing.
{TT36:
is the number of the terminal from which the task is
running.)
>UNB MAS/TERM:::TTZ3:

;\1hplpc~s-tas,k}~ASt2·~ af!;q ·~~;1:~w9 Jt;··.··.t:o.p~n~.J~µ~ ~eecl)t:in9.

3-230

MCR COMMANDS

UNF
UNFIX (P)
The UNFIX command frees a fixed task from memory. This allows tasks
that have been waiting for the partition in which the fixed task
resides to compete for the partition. However, if a fixed task exits
or aborts, it still occupies the physical memory in the partition.
UNFIX is the complement of the FIX command.
Format:
UNF[IX] taskname
taskname
The name of the ~ask.

Examples:
>UNFIX XKE
Unfixes task XKE, freeing the partition in which it
for task competition.

resides

Command Error Message:
UNF -- TASK NOT FIXED
An attempt was made to unfix a task that was not fixed.

3-231

MCR COMMANDS

UNL
UNLOAD (P)
The UNLOAD command removes a loadable device driver from memory. If a
device is mounted, attached, or has outstanding I/O, its driver cannot
be unloaded. Also, the UNLOAD command cannot remove a data base from
memory, even if the data base was loaded by means of the LOAD command.
To unload a device driver from memory, the driver's symbol table (STB)
file must reside on the system device (LB:) under the system UIC. The
SET /SYSUIC command displays and defines the system UIC, but usual
values are [1,50) for unmapped systems and [1,54] for mapped systems.
Format:
UNL[OAD] dd:
dd:
A 2-character ASCII device name.
Example:
>UNL LP:
Unloads the loadable device driver for device LP:.
Command Error Messages:

UNL --.DEVICE ddnn:

HA?'. ~NITS ATTACHED'· BUSY, ANl)/OR MOUNTED

.Fm RSX-HM message•
thatj . . i~ ~t;t~ph~<i,

is the first or only unit
lllounted, . . · f.tn<l/or ·. bps oµtst.(lnrling I/O.
Ther~fq~e,· tbe·.·'<lriv~r ·P~nn<?t be•.· unload.ea«.

UNL -- DEVICE dd:

Device ddnn:

NOT IN SYSTEM

No such device exists in the system.
UNL -- DEVICE NOT MOUNTED
The system device (LB:) was not mounted.
UNL -- DRIVER BUILT WITH WRONG EXECUTIVE STB FILE
The STB file for the
current Executive.

driver

not

compatible

with

the

UNL -- DRIVER CANNOT BE UNLOADED
The UNLOAD command attempted to remove a
permanently
resident device driver (that is, a driver built as part of
the Executive).
UNL -- DRIVER NOT LOADED
The device driver specified in the UNLOAD command
not resident in memory.

3-232

line

was

MCR COMMANDS

UNL {Cont.)
UNL -- FILE filename HAS ILLEGAL STB FORMAT
The driver's STB file contained illegal object code or data.
UNL -- ILLEGAL VALUE FOR SYMBOL symname IN FILE filename
The symbol symname is defined to an illegal value by the
file ddDRV.STB.
Since ddDRV.STB had to pass a previous
inspection by the LOA command, there probably has been a
procedural error or ddDRV.STB has been corrupted.
UNL ,_;,_, LOAJ;>ABLE 'DRIVER SUPPORT NOT IN :SYST,EM

( RS:X-}1M :systems, ori~y ~) ·. ·. Th~ · opt.fen to .. ~upporJ: ·.·. · loadah~e
<:levice drivers was not .chosen· when· the s¥$t~f[l J,V'a$ 9e.net:'<:lt:.~d •..
UNL -- SYMBOL symname IS DOUBLY DEFINED BY FILE filename
The symbol symname is defined twice in the specified file.
Duplicate systems are illegal.
The driver remains loaded.
UNL -- SYMBOL symname IS UNDEFINED BY FILE filename
The symbol symname was found in the specified file, but
symbol is not defined.

3-233

the

MCR COMMANDS

UNS
UNSTOP (NP,P)

The UNSTOP command continues execution of a task that has been stopped
internally by the Executive. Examples of stopped tasks are tasks that
have issued a STOP$S or RCST$ (RECEIVE DATA OR STOP) directive.
A nonprivileged user can only unstop tasks being run from the
terminal. A privileged user can unstop any stopped task.

issuing

Format:
UNS [TOP]

[taskname] [/TERM=TTnnn:]

taskname
The name of the task.
If you omit taskname, the command unstops
the task being run from the issuing terminal (task TTnn).

Examples:
RSX-llM and RSX-llM-PLUS systems:
>UNS TST
Clears the stop bit for task TSTT17 and allows it to
continue executing.
(TT17:
is the number of the terminal
from which the task is running.)
RSX-llM-PLUS systems only:
>UNS LAR/TERM=TT131:
Clears the stop bit
continue executing.
( TDl) •

for task LARTDl and allows it to
The task is being run from TT131:

3-234

April 1983

CHAPTER 4
THE INDIRECT COMMAND PROCESSOR

This chapter describes the Indirect Command Processor (Indirect) and
indirect command files as well as the processor directives that
control the execution of Indirect.
Note that parameter defaults and ranges for the Indirect directives
are specified in the build file for the Indirect task. These values
are installation-specific and can be changed.
This facility also
applies to initial command line and default UIC processing, which are
discussed in Section 4.2.
Ask your system manager
for
more
information.

4.1

INDIRECT COMMAND FILES

There are two types of indirect command files: indirect task command
files and indirect command line interpreter (CLI) command files. The
following sections describe these files.

4.1.1

Indirect Task Command Files

An indirect task command file is a text file containing a list of
task-specific command lines.
Rather than retyping a commonly used
sequence of commands, you can type the sequence once, store it in a
file, and direct the task to read the file for its commands instead of
prompting at the terminal. Tasks respond to commands contained in an
indirect command file as if the commands were entered directly from
the terminal. Most system-supplied tasks on RSX-llM/M-PLUS, such as
MACR0-11 or the Task Builder, accept indirect task command files.
To initiate indirect task command files, replace the command line for
a task with a file specification, preceded by an at sign (@). The
task requesting input then accesses the specified file and starts to
read and respond to the commands contained within it. For example, to
initiate a file of MACR0-11 commands from MCR, input the following:
>MAC @INPT. CMD ~
The MACR0-11 Assembler accesses the file and then executes the command
lines contained within the file INPT.CMD.
The default file type for indirect task command files is .CMD.
Thus,
the command line in the previous example could also be input as
follows:
>MAC (<lINPTffi)

4-1

THE INDIRECT COMMAND PROCESSOR
Some tasks allow nested command files (one file invokes another). See
the appropriate task documentation for the maximum nesting depth
allowed.
Note that indirect task command files can only contain
valid
task-specific command lines.
The Indirect directives (described in
Section 4.6) cannot be used in such command files.

4.1.2

Indirect CLI Command Files

An indirect CLI command file is a text file containing a list of
CLI-specific command lines and special directives that allow you to
control command file processing (see Section 4.3).
The indirect
command processor (Indirect, which runs under the task name AT.) reads
the indirect CLI command file, interprets the directives, and passes
the CLI commands to the CLI.
To initiate an indirect CL!
command
file,
enter
the
file
specification, preceded by an at sign (@), whenever the CLI can accept
input. For example:
>@CLII PT. CMD ~
The default file type for indirect CLI command files is also .CMD.
Thus, the command line in the previous example could also be input as
follows:
>@CLIIPT ~
Indirect CLI command files can also be nested. The maximum level of
nesting depends on the version of the Indirect task you are using.
Ask your system manager about the version or look at the build file
for the Indirect task.
Note that the Indirect directives described in this chapter can only
be used in indirect CLI command files. All further references to
indirect command files refer to CLI command files.

4.2

INDIRECT COMMAND PROCESSOR

When processing an indirect command file, the Indirect task (AT.)
first reads the command file and interprets each command line either
as a command to be passed directly to the CL! or as a request for
action by Indirect. The directives to Indirect are distinguished by a
period (.) as the first character in the line.
The Indirect directives form a procedural language that allows you to:
1.

Define and assign values
symbols

Substitute a symbol's value into any line of the command file

Perform arithmetic

Manipulate strings

Display text on the user's terminal

Ask questions of a user

4-2

logical,

numeric,

and

string

THE INDIRECT COMMAND PROCESSOR
7.

Control the flow of a command file

Call subroutines

Detect error conditions

10.

Test symbols and conditions

11.

Create and access data files

12.

Parse commands and data

13.

Enable or disable any of several operating modes

14.

Control time-based and parallel task execution

Two directives (.BEGIN and .END) permit you to block structure the
command file and create Begin-End blocks. Modular, block-structured
command files are easier to debug and maintain.
More importantly,
Begin-End blocks isolate local symbol definitions as well as labels
and thus conserve symbol table space.
When you define a symbol, Indirect creates an entry for the definition
in an internal symbol table.
These symbol table entries retain their
definitions throughout the execution of the command file
if defined
locally or throughout the execution of all levels of nested command
files if defined globally.
Local ·symbols defined within a block,
however, retain their definitions only throughout the execution of the
commands within that block;
they are erased from the symbol table
when Indirect encounters an .END directive.
An Indirect directive (.ENABLE GLOBAL;
Section 4.6.12)
allows the
definition of some symbols as global to all file levels.
Otherwise,
each time Indirect enters a deeper level (and if the /LO switch has
not been specified;
Section 4.5), it masks all symbols defined by the
previous level out of the symbol table so that only symbols defined in
the current level are available.
These symbols are local only to the
level of the file in which they are defined. When control returns to
a previous level, the symbols defined in that level become available
once again and the ones from the lower level are lost.
When Indirect reaches the end of the highest level
indirect command
file,
it displays the message
(unless
inhibited by the .DISABLE
DISPLAY directive)

>@ <EOF>
and then exits.
Indirect displays on the requesting terminal every CLI command line as
it is executed.
However, if Indirect is activated by @f ilename/-MC or
by @filename/-CLI, CLI command lines in the Indirect file are
the CLI
converted to comments with a leading exclamation point (!);
command lines are displayed but not executed.
An Indirect file can also include comments, which the processor prints
at the requesting terminal. Comments that begin a line interpreted by
the CLI have a leading semicolon (;).
(In some cases,
the semicolon
can be preceded on the same line by a directive to Indirect.) Comments
that appear after the start of a CLI command line have a
leading
exclamation point
(!).
All
lines in an indirect command file that
begin with a period in column 1 followed by a semicolon
(.;)
are
treated as comments but are not displayed when the file is processed.

4-3

THE INDIRECT COMMAND PROCESSOR
Indirect attaches the terminal while processing contiguous comment
lines that begin with a semicolon. This permits you to type CTRL/0
and suppress a lengthy comment.
Output is resumed by typing another
CTRL/O or is resumed at the next CL! command line or Indirect
directive statement in the command file.
Note that no command or comment lines are displayed if
is in effect.

.ENABLE

QUIET

References to task names in an indirect command file follow the rules
used for MCR and DCL.
If the task was started as an external CL! task
(for example, MAC, PIP, OMO), it may be referenced by its 3-character
name
(xxx).
Thus, such directives as .!FINS, .IFACT, and .WAIT need
only specify the 3-character task name;
Indirect can then find the
correct task.
However, you can always refer to a specific task by
using its full 6-character name ( ••• xxx or xxxtnn).
If you do not specify a file name in the initial command line,
Indirect can construct the name of a default file to be opened. The
default file
is named INDINixxx.CMD, where xxx is null or the
three-character task name that was used to initiate Indirect. Note,
however, that this facility is currently disabled.
To enable it, the
value in the build file for the Indirect task must be changed.

If a specified command file cannot be found
in the current UIC,
Indirect can also search for the file in another UIC. However, to
enable this facility, the value in the build file
for the Indirect
task must be changed to be nonzero.
If the new value is 1, Indirect
searches for the file in LB: [sysuic]
on RSX-llM systems and in
LB: [libuic] on RSX-llM-PLUS systems.
If the new value is greater than
377(8), Indirect considers it to be the octal equivalent of the UIC
(on LB:) to be searched.

4.3

SUMMARY OF INDIRECT DIRECTIVES

The Indirect directives described in this chapter are listed here by
category.
A detailed description of each directive is presented in
alphabetical order in Section 4.6.
Label Definition
.label:

Assigns a name to a line in the command
so that the line may be referenced.

file

Symbol Definition
.ASK

logical symbol and
Defines or redefines a
assigns the symbol a true or false value.

.ASKN

Defines or redefines a numeric symboi
assigns the symbol a numeric value.

.ASKS

Defines or redefines a string symbol and
assigns the symbol a character string value.

.ERASE

Deletes
all
local
definitions
or
a
definition •

. SETT/.SETF

Defines or redefines a logical symbol and
assigns the symbol a true or false value.

4-4

or
global
single global

and

symbol
symbol

April 1983

THE INDIRECT COMMAND PROCESSOR
.SETN

Defines or redefines a numeric symbol
assigns the symbol a numeric value.

and

• SETD/.SETO

Redefines the radix of a numeric symbol •

.SETL

Defines or redefines a logical symbol and
assigns the symbol a true or false value.

.SETS

Defines or redefine~ a string symbol and
assigns the symbol a character string value.

File Access
.DATA

Specifies a single line of data to output
a file.

.CHAIN

Closes the current indirect
commands from another file.

. CLOSE

Closes a file •

.OPEN

Creates and opens an output data file (if the
file exists, creates a new version and opens
it) •

.OPENA

Opens an existing file and appends subsequent
data
(does
not create a new version).
Defaults to .OPEN if the file does not exist.

.OPENR

Opens a file
directive.

• PARSE

Parses strings into substrings •

.READ

Reads a record from a file into
string variable.

for

reading

file

with

and

the

to
uses

.READ

specified

Logical Control
• BEGIN

Marks the beginning of a Begin-End block •

• END

Marks the end of a Begin-End block •

.EXIT

Terminates processing of either Indirect or
the current command file, returns control to
the invoking terminal or to the previous
level, and optionally sets special symbol
<EXSTAT> value.

• GOSUB

Calls a subroutine within the command file •

• GOTO

Branches to a label within the command file •

Defines logical end-of-file. Terminates file
processing and exits.
This directive is
equivalent to the .STOP directive.

.ONERR

Branches to a label upon detecting a specific
AT. error condition.

.RETURN

Effects an exit from a subroutine and returns
to
the
line
immediately following the
subroutine call.

4-5

THE INDIRECT COMMAND PROCESSOR
.STOP

Terminates indirect command file processing
and optionally sets Indirect exit status.
This directive is equivalent to the logical
end-of-file (/) directive.

Logical Tests
.IF

Determines whether or not a symbol
a condition •

• IFACT/.IFNACT

Determines whether or not a task is active •

• IFDF/.IFNDF

Determines
defined.

• IFENABLED/
• IFDISABLED

Tests the .ENABLE/.DISABLE options •

• I FINS/. IFNINS

Determines whether or not a task is installed
in the system.

.IFLOA/.IFNLOA

Determines whether or not a device driver
loaded.

.IFT/.IFF

Determines whether a logical symbol
or false.

.TEST

Tests the l~ngth of
locates a substring.

.TESTDEVICE

Returns information about
system.

.TESTFILE

Determines if a specified file exists and
determines the physical device associated
with a logical device name (performs device
translation) •

• TESTPARTITION

Returns information about a partition in
system.

whether

not

satisfies

symbol

string
a

true

symbol

device

the

Enable or Disable an Operating Mode
• ENABLE/. DISABLE

Enables or disables control of the
modes:
substitution
timeout parameter
lowercase
terminal attachment
data
global symbol
symbol radix
command line echo
command display
field display
command passing to default CLI
file deletion
truncate error suppression
escape
escape-sequence recognition
control-Z exit
overflow

4-6

following

THE INDIRECT COMMAND PROCESSOR
Increment or Decrement Numeric Symbols
~DEC

Decrements the value of a numeric

hu
~I

one.
• INC

Increments the value of a numeric
one.

symbol

Execution Control
.DELAY

Delays the execution of an
indirect
file for a specified period of time.

command

.PAUSE

Suspends the indirect command file
and allows user action.

processor

.WAIT

Waits for
a specified
task to
complete
execution
and
sets
the special symbol
<EXSTAT> with the completed task's
exit
status.

.XQT

Initiates a task, passes a command line to
it,
and continues indirect command file
processing without waiting for
the task to
complete.

Special Purpose

4.4

SYMBOLS

The indirect command processor enables you to define symbols.
These
symbols can then be tested or compared to control flow through the
indirect command file.
They may also be substituted in CLI commands,
data
records for data files,
or comments to be displayed on the
terminal.
Symbol names are ASCII strings from one through six characters in
length.
They must start with a letter (A through Z) or a dollar sign
($). The remaining characters must be alphanumeric or a dollar sign.
There are three symbol types:
•

Logical

•

Numeric

•

String

A logical symbol has either a true or false value.
A numeric symbol can have a numeric value in the range of 0 through
n5535(10).
The symbol can be defined to have either a decimal or
octal
radix.
The radix
is relevant only when the symbol
is
substituted (see Section 4.4.2).
A string symbol has as its value a string of ASCII characters, with
length of 0 through 132(10) characters.

4-7

THE INDIRECT COMMAND PROCESSOR
A symbol's type (logical, numeric, or string) is defined by the first
assignment directive that assigns a value to the symbol. Assignment
directives can assign:

4.4.1

•

A true or false value to define a logical symbol
(Defined by .ASK, .SETL, .SETT, or .SETF.)

•

An octal or decimal number to define a numeric symbol
(Defined by .ASKN, .SETN, .SETO, or .SETO.)

•

A character string to define a string symbol
(Defined by .ASKS, .READ, or .SETS.)

Special Symbols

Indirect automatically defines special symbols dependent upon specific
system characteristics and
the replies to queries presented during
command file execution.
As with symbols,
special symbols can be
compared,
tested, or substituted and have three types:
logical,
numeric, and string. All special symbols have a common format:
angle
brackets (<>) enclose the special symbol name.

4.4.1.1 Special Logical Symbols - The special logical symbols
assigned a true or false value under the following circumstances:

are

Symbol

Value

Set to true if last string entered in response to an
.ASKS directive or tested with a .TEST directive
contains only alphanumeric characters.
An empty
string also sets <ALPHAN> to true.

Set to true if last question was
ALTmode or ESCape.
Otherwise,
false.

Set to true if the current operating system is a
baseline configuration.
{This option is used during
system generation to determine what resources are
available
for
the
system generation process.)
Otherwise, <BASLIN> is set to false.

Set to true if answer to last query was
(the RETURN key was pressed once)
or
occurred.

<EOF>

Set to true if the last
.READ or
.ASKx directive
resulted
in reading past the end of the file.
Otherwise, <EOF> is set to false.

Set to true if any of the
following conditions are
true
(<ERRNUM>, <EXSTAT>, and <FILERR> are described
in Section 4.4.1.2):
•

answered with an
<ALTMOD> is set to

defaulted
a timeout

<FILERR> is less than O, if a negative error
was returned

4-8

code

THE INDIRECT COMMAND PROCESSOR
•

If an exit status
(<EXSTAT>)
<WARNING> was returned

•

<EOF> is set to true

<ERRNUM> is not 0

•

If you used the command line .SETT <ERSEEN>

The command line .SETF <ERSEEN>
conditions:
•

<FILERR> is set to 0

<EXSTAT> is set to 0

•

<EOF> is set to false

•

<ERRNUM> is set to 0

value

sets

the

worse

than

following

Set to true if last question was
ALTmode or ESCape.
Otherwise,
false.

<FALSE>

Logical constant used for comparisons with the
.IF
directive or as a default for the .ASK directive.

<IAS>

Set to true if the current operating system is IAS.
Otherwise,
<IAS>
is false.
Always false
in an
RSX-llM/M-PLUS system.

<LOCAL>

Set to true if the terminal from which Indirect is
executing (TI:) is a local terminal.
If the terminal
is remote, <LOCAL> is set to false.

Set to true
if the system on which Indirect is
running
is mapped;
set to false if the system is
unmapped.
Always true in an RSX-llM-PLUS system.

Set to true if the last string entered in response to
an
.ASKS directive or tested with a .TEST directive
contains only numeric characters.
An empty string
also sets <NUMBER> to true.

<OCTAL>

Set to true if the answer to the last .ASKN directive
or the radix of the numeric symbol tested in the last
.TEST directive is octal or if the last string tested
with
a
.TEST
directive contained all numeric
characters in the range 0 through 7.

Set to true if the current user is privileged.
Its
value
is determined
from the flag contained in the
terminal data base.
The flag is set at login or with
the MCR SET /PRIVilege command.

<RAD50>

Set to true if last string entered in response to an
.ASKS directive or tested with a .TEST directive
contains
only
Radix-50
characters.
Radix-50
characters are the uppercase alphanumeric characters
plus period (.) and dollar sign ($).
A blank is not
a Radix-50 character
in this context.
An empty
string also sets <RAD50> true.

4-9

answered with an
<ESCAPE> is set to

THE INDIRECT COMMAND PROCESSOR
<RSXllD>

Always false in an RSX-llM/M-PLUS system.

Set to true if timeout mode is enabled and the
.ASKx
directive
timed out waiting for a
response.

last
user

<TRUE>

Logical constant used for comparisons with the
directive or as a default for the .ASK directive.

.IF

4.4.l.2 Special Numeric Symbols - The
assigned the following values:

special

numeric

symbols

are

Symbol

Value

Controls the way in which Indirect processes errors.
The symbol
is treated as an 8-bit mask.
For each
class of error that a user's
.ONERR target routine
processes
(see Section 4.6.21), the appropriate bit
is set in the mask.
If the bit is clear,
Indirect
exits after printing the error information.
If the eighth bit, which is the sign bit or 200(8),
is set, Indirect does not print any information about
the error.
The initial default value for <ERRCTL>
is 1, which
implies that only class 1 errors can be handled with
an .ONERR address and that error messages will be
printed.
Note that if you attempt to trap errors
other than default class 1,
processing
cannot
continue in most cases.
The error service routine is
limited to a fatal
error message and
.EXIT.
The
internal state of Indirect is indeterminate in all
but class 1 error cases.
See Section 4.8 for a list of
their assigned class values.

error

messages

and

Assigned the class number of an error that Indirect
has finished processing.
This value can be used for
processing specific error types with an
.ONERR
routine.
See Section 4.8 for a list of
their assigned class numbers.

error

messages

and

Assigned the error severity mask associated with the
error that
Indirect has finished processing.
This
bit mask corresponds to the bit mask <ERRCTL> used to
control the processing.

Assigned the value of O, 1, 2, 4, or 17 depending on
the exit status from the last CLI command line
executed or from the last
.WAIT taskname directive
where taskname was activated by the .XQT directive.

4-10

THE INDIRECT COMMAND PROCESSOR
This special numeric symbol
is modified at the
completion of a synchronous CLI command line or at
the comoletion of a
.WAIT directive.
The
.EXIT
directive can also modify <EXSTAT>.
The value is
returned from the task that has completed if the task
exits with status.
Otherwise, the value is returned
from the CLI.
The values O, 1,
2,
4, and 17 and
their corresponding special symbols indicate:
0
1
2
4

Warning
Success
Error
Severe error
The task could
exit status.

not

return

Assigned the FCS-11 or I/O driver status
code
resulting
from
a
.TESTFILE,
.OPENx, or .READ
directive operation.
See the RSX-llM/M-PLUS I/O
Drivers Reference Manual for a description of the
codes.

Assigned the octal value of the file attributes
were used to open the data files.

that

Assigned the value of the current system memory
in K words (K is 1024.).

size

<SPACE>

Assigned the number, in octal, of free bytes in the
internal symbol table for Indirect.
The number does
not reflect the amount of space that could be gained
by the automatic extension of the Indirect task.

Assigned the length of the string entered in response
to the last .ASKS directive or the string tested by
the last .TEST directive.
The symbol
is also set
when a command file is invoked (<STRLEN> contains the
number of variables used in the command line) and as
the result of a .PARSE statement.

Assigned the numeric code for
tested with a .TEST directive.
the following code numbers:

the type of symbol
The symbol types have

String - 4
Numeric - 2
Logical - 0
<SYSTEM>

Assigned an octal number to represent
system on which Indirect is running.
for an RSX-llM system;
the value
RSX-llM-PLUS system.

Assigned the unit number of the user's default device
(SY:) •

Assigned the current page length setting for the
terminal.
Indirect attempts to determine the length
when you first invoke it.
ir tne inrormat1on is not
available, <TICLPP> defaults to 24(10).

4-11

the operating
The value 1 is
6 is for an

THE INDIRECT COMMAND PROCESSOR
<TICWID>

Assigned the current page width setting for
the
terminal.
Indirect attempts to determine the width
when you first invoke it.
If the information is not
available, <TICWID> defaults to 80(10).

Assigned the baud rate for
transmitting characters
from the host system to the terminal.
Indirect
attempts to determine the baud rate when you first
invoke
it.
This
information
is
useful for
determining the quality and quantity of information
to be transmitted.
The following list gives the
octal value that corresponds to the baud rates:
1
2
3
4
5
6
7
10
11
12

0
50
75
100
110
134
150
200
300
600

13
14
15
16
17
20
21
22
23
24

1200
1800
2000
2400
3600
4800
7200
9600
EXTA
EXTB

Assigned the terminal type of the terminal from which
Indirect is running.
Indirect attempts to determine
the terminal type when you first invoke it.
If the
attempt fails, <TITYPE> is set to zero (0).
See the
RSX-llM/M-PLUS I/O Drivers Reference Manual for a
list of the values that correspond to the terminal
types.

4.4.1.3 Special String Symbols - The
assigned the following string values.

special

Value

Symbol

4-12

string

symbols

are

THE INDIRECT COMMAND PROCESSOR

<CLI>

of the
Assigned the acronym
(3 through 6 letters)
current command line interpreter (for example, DCL or
MCR) •

Contains the parameter defaults specified when the
current Indirect task was built.
See the module INDCFG
in the system procedure library LB: [l,2]INDSYS.CLB for
more details.

<DATE>

Assigned the current date;

When Indirect is first initiated, contains build-time
information about the Indirect task.
The information
includes the version number of the task and the time
the task was built. Afterwards, contains the string
results from a more deeply nested indirect command
file.
The results are sent to the calling command
file.

Assigned the seven words of file attribute information
contained in the FCS-11 File Descriptor Block (FDB).
The information is from the FDB used in the last .OPENx
operation. See the IAS/RSX-11 I/O Operations Reference
Manual for a description of fi~ attributes and the
values of each field.

Assigned the fully qualified specification for the file
referred to with the last .OPEN, .OPENA, .OPENR, or
.TESTFILE directive operation,
or
in
the
last
specification for a nested command file.

<FMASK>

Contains octal values representing answers to some of
the system generation questions.
Refer to the module
INDSFN
in
the
system
procedure
library
LB: [l,2]INDSYS.CLB for an explanation of the values.

4-13

format is dd-mmm-yy.

THE INDIRECT COMMAND PROCESSOR

•

Assigned the device name and unit number of the user's
login account on multiuser protection systems.
On
other systems, <LOGDEV> is assigned SYO:
(the system
device) •

Assigned the login UIC of the current user on multiuser
protection systems;
format
is
[ggg,mmm].
On other
systems, <LOGUIC> is assigned the current default UIC.

Assigned the UIC in which DECnet-related tasks are
stored on the system volume;
format is [ggg,mmm].
<NETUIC> is used with <SYSUIC> and <LIBUIC> to separate
the components of the system.

Assigned the DECnet node name of the system.
If the
system is not on the DECnet system,
<NETNOD> is
assigned RSXll.

Used as part of a dump routine in the command library
file LB: [l,2]INDSYS.CLB.
This lS a DIGITAL-supplied
symbol and it is highly recommended that you not use
it.

Assigned the physical name for the boot device for
system.
The device name is in the form ddn.

the

Assigned the device mnemonic
(two letters)
user's default device (SY: ) ;
format is dd.

the

Assigned the operating system's base level number.

Assigned the system UIC;

<TIME>

Assigned the current time;

format is hh:mm:ss.

<UIC>

Assigned the current UIC;

format is [ ggg ,mmm] •

4.4.2

format is [ggg ,mmm].

Numeric Symbols and Expressions

A numeric symbol is a string of digits representing a value in the
range of 0 through 177777(8) (0 through 65535 decimal if immediately
followed by a period or if decimal mode has been enabled).
If an
arithmetic operation yields a result outside of this range, a fatal
error occurs and the message
AT. -- NUMERIC UNDER- OR OVERFLOW
is displayed.
A numeric symbol or constant may be combined w1~n ano~ner numeric
symbol or constant by a logical or arithmetic operator to form a
numeric expression.
Arithmetic operators are used to add
(+),
subtract (-), multiply (*), and divide (/).
Logical operators are the
inclusive OR (!), logical AND (&), and NOT (#).
No embedded blanks or
tabs are permitted between operators.

4-14

April 1983

THE INDIRECT COMMAND PROCESSOR
Numeric expressions are evaluated from left
to
right
unless
parentheses are used to form subexpressions that are evaluated first.
For example, the directive lines:
.SETN Nl 2
.SETN N2 3
.SETN N3 Nl+N2*4
assign numeric symbol N3 the value 24(8) whereas the directive lines
.SETN Nl 2
.SETN N2 3
.SETN N3 Nl+(N2*4)
assign numeric symbol N3 the value 16(8).
Numeric expressions are permitted as second operands in numeric .IF
and .SETN directives.
They are also permitted as range and default
arguments in .ASKN and .ASKS directives.
The directives .EXIT and
.STOP permit numeric expressions to represent exit status.
With each numeric symbol, Indirect associates a radix -- either octal
or decimal.
The radix of a numeric symbol changes each time the
symbol is assigned a new value. If you use a numeric expression to
assign a new value to a symbol and all operands in the expression are
octal, then the symbol is set to octal.
If any operand in the
expression is decimal, the symbol is set to decimal. For example:
.SETN Nl 2
.SETN N2 3.
.SETN N3 Nl+3
.SETN N3 Nl+3.
.SETN N3 Nl+N2

Nl
N2
N3
N3
N3

is octal
is decimal
is octal
is decimal
is decimal

You can also assign a new value to a symbol with the .ASKN
See Section 4.6.3 for more information.

directive.

The .SETO and .SETD directives allow you to change the
numeric symbol without changing the value of the symbol.

radix of a
For example:

.SETN Nl 10.
.SETO Nl

Nl
Nl

10 decimal
12 octal

See Section 4.6.31 for more information on .SETO and .SETD.
The radix of a numeric symbol does not affect arithmetic operations or
comparisons.
The radix is important only when substituting a numeric
symbol into a string. If the radix of the symbol is octal, the value
of the symbol is substituted into the string as an octal number. If
the radix is decimal, the value is substituted as a decimal number.
For example:
.SETN Nl 10.
; Nl = 'Nl'
.SETO Nl
; Nl = IN 1 I

Nl = 10 decimal
Displayed as ; Nl
Make Nl octal
Displayed as ; Nl

4-15

10
12

THE INDIRECT COMMAND PROCESSOR
If you substitute a numeric symbol into a string and the substituted
number
is decimal, a period (.) following the symbol name causes a
trailing period to be included
in the string
(following
the
substituted number).
For example:
Nl = 10 decimal
Displayed as ; Nl
Make Nl octal
Displayed as ; Nl

.SETN Nl 10.
; Nl = 'Nl.'
• SETO Nl
; Nl = 'Nl. I

10 •
12

You can also force a numeric symbol to be substituted as an octal or
decimal number by using a substitution format control string.
For
example:
Nl = 10 decimal
Displayed as ; Nl
Displayed as ; Nl

.SETN Nl 10.
; Nl
'Nl%D I
; Nl = 'Nl%0'
See Section 4.4.5.1
control strings.

4.4.3

for

information

10
12

substitution

format

String Symbols, Substrings, and Expres$ions

A string constant is a string of any printable characters enclosed by
quotation marks.
Empty strings are also permitted.
The number of
characters cannot exceed 132(10).
For example:
"ABCDEF"
1111

String symbols may have the value of any string constant.
The value
is assigned by a .SETS or .ASKS directive.
For example, the directive
statements
.SETS
.SETS

Sl
S2

"ABCDEF"
Sl

assign string symbol S2 the
ABCDEF) •

value

string

symbol

(that

is,

A substring facilitates the extraction of a segment from the value of
a
string symbol.
You can use substrings only in second operands of
.SETS and .IF directives.
For example, the directive statements
.SETS
.SETS

Sl
S2

"ABCDEF"
81(1:3]

assign string symbol S2 the value of string symbol Sl beginning
character one and ending at character three {that is, ABC).

You can also use the syntax
[n:*]
to extract the characters from
position n to the end of the string.
For example, the directive
statements

.SETS
.SETS

Sl
82

"ABCDEF"
81[3:*]

assign string symbol S2 the value CDEF.
You can combine a string constant, symbol, or substring with another
string constant, symbol, or substring by the string concatenation
operator (+) to form a string expression.

4-16

THE INDIRECT COMMAND PROCESSOR
String expressions are permitted as second operands in .SETS and
.IF
directives where the first operand is a string symbol.
For example,
the directive statements
.SETS
.SETS
.SETS

Sl
S2
S3

"A"
"CDEF"
Sl+"B"+S2 [l: 3]

assign string symbol S3 the value of the concatenation of string
symbol
Sl, string constant "B", and the first three characters of
string symbol S2 (that is, ABCDE).

4.4.4

ti ij :tels

Parameters for a command file can be passed to
Indirect
for
processing. The parameters are stored in the following reserved local
symbols:
PO, Pl, P2, P3, P4, P5, Pn, P7, PB, P9, COMMAN
issuing command line,
The symbol COMMAN contains everything in the
including the specification for
the command file.
The symbols PO
through pg contain individual elements of the command line.
The
elements are delimited by spaces.
With the .GOSUB directive (see Section 4.6.16), any parameters to the
right of the label and to the left of a comment are transferred to the
symbol COMMAN.
The value of COMMAN can then be parsed to obtain
formal call parameters.

4.4.5

Symbol Value Substitution

Substitution can occur in any command line.
Indirect can use the
values assigned
to logical, numeric, string, or special symbols by
replacing a normal parameter (for example, a device unit)
with the
symbol name enclosed
in apostrophes
(for example, 'DEV'). When a
previous
directive
has
enabled
substitution
mode
(.ENABLE
SUBSTITUTION),
Indirect
replaces
the symbol name enclosed
in
apostrophes with the value assigned to the symbol.
When Indirect encounters an apostrophe, it treats the subsequent text,
up to a second apostrophe, as a symbol name.
Indirect then searches
the table of symbols for the corresponding symbol and substitutes the
value of the symbol
in place of the symbol name and surrounding
apostrophes in the command line.
For example, the first three lines in the following example appear
in
an indirect command file. When the processor executes these lines, it
displays the last two lines at the entering terminal •
• ASKS DEV MOUNT ON DEVICE?
.ENABLE SUBSTITUTION
MOUNT I DEV'
>* MOUNT ON DEVICE?
>MOUNT DK2:

[S]: DK2:

4-17

THE INDIRECT COMMAND PROCESSOR
DK2:
was entered in response to the displayed question.
This reply
assigned
the string value DK2:
to
string symbol DEV.
Then when
Indirect read:
MOUNT

DEV'

it substituted for 'DEV' the value assigned to DEV
(that is, DK2:).
If substitution mode was not enabled,
Indirect would simply have
passed the line to the CLI as it appeared in the command
file
(that
is, MOUNT 'DEV').
If substitution mode is enabled, an apostrophe signals the beginning
of a string symbol.
Thus, to include a single quote as text within a
command 1 ine, rather than as the start of a symbol, you must replace
the single quote with two contiguous apostrophes ('').
If substitution mode is enabled, Indirect displays
line

the

command

file

DON''T SHOOT
as
DON'T SHOOT

4.4.5.1 Substitution Format Control - The
conversion
of
numeric
values to strings and the placement of string and logical values in a
substitution operation can be controlled with a format control string.
The control string is in the following form:
••• 'symbol%controlstring' •••
The control string begins with the percent sign (%) and ends with the
second of the two apostrophes that denote the substitution operation.
The control
string consists of one or more of the
following
characters:
C

Compress leading, embedded, and trailing blanks, and
embedded nul 1 s.

Force the conversion of a numeric symbol to decimal.

Force the conversion of a numeric symbol to octal.

Perform signed conversion for a numeric symbol.

Perform magnitude conversion for a numeric symbol.

Return leading zeros for a positive numeric value.

Right-justify the resulting
string,
decimal characters if necessary.

Left-justify the resulting string, truncating to 'n' decimal
characters if necessary.

Convert the variable to Radix-SO characters.

If the symbol being substituted is numeric, convert the low
byte to its equivalent ASCII character and substitute it.

4-18

truncating

remove

'n'

THE INDIRECT COMMAND PROCESSOR
If the symbol being substituted is a string, convert the
first character to its octal representation and substitute
it.
Indirect does not perform a consistency check on the control string.
If you specify conflicting format characters, Indirect uses the last
one specified.

4.5

SWITCHES

The indirect command processor accepts six switches:
/CLI, /LB, and /LO.

/TR,

/DE,

/MC,

Switch

Function

/(NO]TR

Displays a trace of the indirect command file on the
entering
terminal.
This function
is useful
for
debugging an indirect command file&
Each command line,
including
Indirect directive statements, is displayed.
As each Indirect command line is processed, a number
representing the nesting depth of the command file is
displayed, followed by an exclamation mark and the
command line.
If the command line causes some action
to occur, the next printed line indicates the action;
usually,
this line consists of the CLI commands issued
as a result of the previous directive.
The default is
/NOTR.

/(NO]DE

Indicates that the
indirect command file
is to be
deleted when its processing
is complete unless a
logical end-of-file
(/)
or
.STOP
directive
is
e~countered before the end of the file.
The default is
/NODE.

/(NO]MC

Passes commands not processed by Indirect to the
default
command
line interpreter
(CLI)
for your
terminal.
This switch is synonymous with /[NO]CLI.
The default is /MC.

/[NO]CLI

Passes commands not processed by Indirect to the
default
command
line
interpreter
(CLI)
for your
terminal.
This switch is synonymous with /[NO]MC.
The
default is /CLI.

/LB

Indicat~s
that the specified file
is a
universal
library of command procedures and that the specified
module is the procedure to be executed.

When command procedures, which are indirect command
files,
are inserted into a universal library with the
Librarian Utility Program
(see the
RSX-llM/M-PLUS
Utilities Manual), you can then reference them with
/LB:module.
Command libraries are built by creating a universal
library and
inserting command files into it.
You can
then reference the procedures in the library with the
following command line:
@command-library/LB:module

4-19

THE INDIRECT COMMAND PROCESSOR

The default file type for a command library is .CLB.
If you do not specify a module (@command-library/LB),
Indirect attempts to locate a module called .MAIN ••
If you do not specify a library name (@/LB:module), the
following actions occur:
•

If the command is issued from the terminal or
from a file that is not in the library,
Indirect ignores the /LB switch and treats the
command
line
as
though
you
had
used
@module.CMD.
Note that if the command is
issued from a command file, the default device
and directory of the specified module are the
same
as those for the current file, not
necessarily the same as those for the terminal.

•

If the command was issued from within
a
library, the specified module is searched for
in the current library.

These default actions for an unspecified library allow
a collection of procedures to be developed in a given
directory with the @/LB:module or .CHAIN /LB:module
commands.
When the procedures are then placed in a
library, no source changes are required.
Example:
The command file PARAM.CMD contains parameter
definitions
for the .SETN directive and the
command file SYSPRC.CMD contains system-specific
procedures.
use the following command lines to
create the command library and enter the command
files into it:
LBR>SYSTART.CLB/CR::::UNI:CMD
LBR>SYSTART.CLB=PARAM/IN:PARAM
LBR>SYSTART.CLB=SYSPRC/IN:PROCED
You can then use the following command
reference the command library modules:
@SYSTART/LB:PARAM
@SYSTART/LB:PROCED

lines

!Define global symbols
!Run init procedure

DIGITAL supplies a library of command procedures.
library is LB:[l,2]INDSYS.CLB and it contains
following procedures:

The
the

INDCFG

Displays the current build parameters
for the running Indirect task.

INDDMP

Dumps to the terminal the
the Indirect symbol table.

contents

INDPRF

A sample procedure
file-name strings.

fully

INDSFN

Returns
information.

4-20

system

parse

configuration

THE INDIRECT COMMAND PROCESSOR
INDVFY

Displays the values
special symbols.

all

the

QIOERR

Returns a string expansion
<FILERR> error codes.

the

• INDEX

Displays an index of the
the library.

procedures

The following command line shows the format
invoking a command procedure in the library:

in
for

@LB: [l,2]INDSYS/LB:procedurename
Before you attempt to access a command procedure, make
sure that INDSYS.CLB is in LB: [1,2].
If it is not in
this directory, your system manager must copy the
library off of the source kit for the system.
(On
RSX~llM,. the library is included with the source
files
fqr 8CR, which are in UFD [ 12, 10] .} .
/[NO]LO

Indicates that when a new command file is executing, it
can have access to the local symbols created by its
calling command file,
and that any local symbols
created by the new command file will be defined as
local symbols for the calling command file.
The
default is /NOLO.

Use any combination of the switches in the command line
@filename/switches
or directive statement
.CHAIN filename/switches
The switches you specify in the terminal command line that initiates
Indirect processing are used as defaults when executing the following
commands:
@filename[/switches] or .CHAIN filename[/switches].
This
does not apply, however, for the /DE switch;
the default is always
/NODE.

4.6

DESCRIPTION OF INDIRECT DIRECTIVES

Directives must be separated from
their
CLI-specific commands by at least one space.
command line is allowed.

4-21

arguments
and
from
Only one directive per

April 1983

THE INDIRECT COMMAND PROCESSOR
You can insert any number of
places of a command line:

blanks

and

horizontal

•

At the start of the command line

•

Immediately following the colon (:) of a label

•

At the end of the command line

tabs

three

This allows you to format the command files for readability.
The
recommended procedure is to begin labels in column one and everything
else in column nine (after one horizontal tab).
An important exception is the lines processed between .ENABLE and
no blanks or tabs are removed from these
.DISABLE DATA directives;
lines. For example:
.IFT Z .GOTO 10
MAC @ASM
.10:
TKB @BLD
.OPEN DATFIL
.DATA XXXXX
.ENABLE DATA
This is data
that goes into
the data file •
• DISABLE DATA
.GOTO 20
Note that the .DISABLE DATA statement must begin in column 1 or
Indirect will place it in the data file. You can also use the .CLOSE
directive in place of .DISABLE DATA. It too must begin in column 1.

4.6.1

Define a Label

Labels always appear at the beginning of the line; they may~~
line with additional directives and/or a CLI command, on a line with a
comment, or on a line by themselves. When control passes to a line
with a label, the line is processed from the first character after the
colon.
Commands do not have to be separated from the label by a space.
Only
one label is permitted per line.
Labels are one through six
characters in length and must be preceded by a period and terminated
by a colon. A label may contain only alphanumeric characters and/or
dollar signs ($).
It is also possible to define a label as a direct access label;
once
the label is found; its position in the command file is savede This
allows subsequent jumps to frequently called labels or subroutines to
be effected quickly. The first statement processed after a jump to a
direct access label is the one on the next line. The maximum number
of direct access labels you can define within an indirect command file
depends on the version of the Indirect task you are using.
(The
maximum number is specified in the task build file.) If you define
more than the maximum number allowed, the subsequent direct access
labels replace the earliest and so on. The smaller the number of
direct access labels, the larger the amount of free symbol table
space.
To declare a label for direct access, leave
colon blank.

4-22

the

line

following

the

THE INDIRECT COMMAND PROCESSOR
Examples:
•

inn.
u v.

.l.

.ASK A
.IFT A .GOSUB 200

.200:
.;THIS IS THE START OF A SUBROUTINE

.RETURN

4.~.2 Ask a Question and Wait for a Reply

The .ASK directive prints a question on the terminal, waits for a
reply, and sets a specified logical symbol to the value of true or
false, depending on the reply.
If the symbol has not already been
defined,
Indirect makes an entry in the symbol table.
If the symbol
has been defined,
Indirect resets its value
(true or false)
in
accordance with the reply.
Indirect exits with a fatal error if the
symbol was previously defined as a string or numeric symbol.
Formats (brackets are required syntax):
.ASK ssssss txt-strng
.ASK [default:timeout] ssssss txt-strng
.ASK [:timeout] ssssss txt-strng
where:
ssssss

The 1- to 6-character symbol to be assigned a true or
false value.

txt-strng

The question or prompt that Indirect displays.

default

used
if the question is
The default response;
answered with an empty line
(null) or if timeout
occurs. The default can be <TRUE> or <FALSE> or
another logical variable.

timeout

The timeout count.
Indirect waits this long
for a
response, then applies the default answer.
The
format for timeout is nnu, where nn is the decimal
number of time units to wait and u is T (ticks), S
(seconds), M (minutes), or H (hours).
The timeout
count is valid only if timeout mode is enabled
(.ENABLE TIMEOUT).

The entire .ASK statement must fit on one command line.
Note that if you omit the default value but specify a
the colon is required for positional identification.

4-23

timeout

count,

THE INDIRECT COMMAND PROCESSOR
When executing an .ASK directive, Indirect displays txt-strng prefixed
by an asterisk and suffixed with "? [Y/N] :".
Indirect recognizes five
answers:
1.

Set symbol ssssss

~ t~

... _?.
'
"
l
Set s ym bo 1 s s s s s s to( fa 1 s e,.,:.J
........

Set symbol
value.
~

to false ''()r to user-specified
indicates the RETURN key.

default

Set symbol
ssssss
to true and set the special
logical
symbol
<ESCAPE> to true only if escape
~·
indicates
recognition has been enabled.
the ESCAPE or ALTMODE key.

5•

tTRL!Z)

If Control-Z mode
is enabled,
set <EOF>
and proceed, else exit immediately.

to true

Example:
The directive statement
.ASK INSPIP DO YOU WANT TO INSTALL PIP
displays
>* DO YOU WANT TO INSTALL PIP? [Y/N]:
on the terminal.
Symbol INSPIP will be set to true or false after you
type Y, N, the RETURN key, or the ESCAPE key (if escape recognition is
enabled).

4.6.3

Ask for Definition of a Numeric Symbol

The .ASKN directive prints on the terminal a
request for a
value,
waits for it to be entered, optionally tests the range for the
numeric
response and/or applies a default value, and sets the
specified symbol accordingly.
If the symbol has not previously been
defined, Indirect makes an entry in the symbol table.
If the symbol
has already been defined, Indirect resets its value in accordance with
the reply.
Indirect exits with a
fatal
error
if the symbol was
previously defined as a logical or string symbol.
Formats (brackets are required syntax):
.ASKN ssssss txt-strng
.ASKN [low:high:default:timeout] ssssss txt-strng
where:
ssssss

The 1- to 6-character symbol to be assigned a numeric
value.

txt-strng

The question or prompt that Indirect displays.

low:high

A numeric
response.

expression

giving

default

A numeric expression or
value.

symbol

4-24

the

range

giving

the

for

the

default

THE

timeout

INDIRECT COMMAND PROCESSOR

The timeout count. Indirect waits this long for a
response, then applies the default answer.
The
format for timeout is nnu: where nn is the decimal
number of time units to wait and u is T (ticks), S
(seconds), M (minutes), or H (hours).
The timeout
count is valid only if timeout mode is enabled
(.ENABLE TIMEOUT).

The entire .ASKN statement must fit on one command line.
Note that if you omit any
preceding
brackets,
any
identification.

of the
colons

parameters within the square
are
required for positional

The command line cannot exceed 132(10) characters in length.
When
executing an .ASKN directive, Indirect displays txt-strng prefixed by
an asterisk and suffixed with [O]: to indicate that the response is
considered as octal or [D]:
to indicate that the response is
considered as decimal. The reply must be a number either within the
specified range or in the range O through 177777 (8) (by default) or O
through n5 5 3 5 (1 o) •
If the response is outside the specified range, the message
AT. -- VALUE NOT IN RANGE
is displayed and the query repeated.
If an arithmetic operation yields a result greater than 177777(8) when
computing the actual value of any of the arguments (low, high, or
default), a fatal error occurs and the message
AT. -- NUMERIC UNDER- OR OVERFLOW
is displayed.
If the response is an empty line (null) and a default value (default)
was not specified, Indirect applies a default of o. Note that in this
case, the range, if specified, must include o.
The response may be either octal or decimal; a leading pound sign (#)
forces octal, a trailing period ( .) forces decimal. In the absence of
both, Indirect applies a default radix. The default radix is decimal
if either the range or default values are decimal expressions
(followed by a period). Otherwise, the default radix is octal (unless
decimal mode has been enabled). Indirect displays the default type as
either [O] or [D].
To force a default decimal radix without specifying a range
use the following construction:
.ASKN (::O.] A ENTER VALUE
or
.ENABLE DECIMAL
.ASKN A ENTER VALUE

4-25

argument,

THE INDIRECT COMMAND PROCESSOR
Examples:
•

The directive statement
.ASKN

SYM

DEFINE NUMERIC SYMBOL A

displays
>*DEFINE NUMERIC SYMBOL A [O]:
on the terminal where:
[O] is the default radix (octal).
Indirect then
entered.
•

defines

symbol

SYM

according

the

The directive statement
.ASKN [2:35:16:208] NUMSYM DEFINE NUMERIC SYMBOL A
displays
>* DEFINE NUMERIC SYMBOL A [O R:2-35 D:l6 T:20S]:
in the format [x R:low-high D:default T:timeout]
where:
x

O if the default radix is octal or D if it is
decimal.

R:low-high

The specified range.

D:default

The specified default.

T:timeout

The specified timeout count
default answer is applied.

Indirect then checks
specified range.
•

that

the

response

string

before

the

The directive statement
.ASKN [NUMSYM+l0:45:NUMSYM+l0] SYM DEFINE NUMERIC SYMBOL B
displays (assuming the value of 16 octal for NUMSYM)
>* DEFINE NUMERIC SYMBOL B [O R:26-45 D:26]:

4. 6. 4

Ask for Definition of a String Symbol

~i
~

The .ASKS directive prints on the terminal a request for a
value to define a specified symbol and optionally tests that the
number of characters in the response string falls within the specified
range.
If the symbol has not previously been defined, Indirect makes
an entry in the symbol table. If the symbol has already been defined,
Indirect resets its value in accordance with the reply. Indirect
exits with a fatal error if the symbol was defined previously as a

4-26

THE INDIRECT COMMAND PROCESSOR
logical or numeric symbol.
If the number of characters is out of
specified range, the message

the

AT. -- STRING LENGTH NOT IN RANGE
is displayed and the question repeated.
Formats (brackets are required syntax):
.ASKS ssssss txt-strng
.ASKS [low:high:default:timeout] ssssss txt-strng
where:
ssssss

The 1- to 6-character symbol to be assigned a
value.

txt-strng

The question or prompt that Indirect displayso

low:high

A numeric expression giving the range for the number
of characters permitted in the response string.

default

A string expression
value.

timeout

The timeout count.
Indirect waits this long for a
response,
then applies the default answer.
The
format for timeout is nnu, where nn is the decimal
number of time units to wait and u is T (ticks), S
(seconds), M (minutes), or H (hours).
The timeout
count is valid only if timeout mode is enabled
(.ENABLE TIMEOUT).

symbol

giving

the

string

default

The entire .ASKS statement must fit on one command line.
Note that if you omit any
brackets,
any
preceding
identification.

of the
colons

parameters within the square
are
required
for positional

When executing an
.ASKS directive,
Indirect displays
txt-strng
prefixed by an asterisk (*) and suffixes it with (S] :. The reply must
be an ASCII character string.
Examples:
•

The directive statement
.ASKS NAM PLEASE ENTER YOUR NAME
displays
>*PLEASE ENTER YOUR NAME (S]:
on the terminal.
Indirect then defines symbol
to the string reply entered.

4-27

NAM

according

THE INDIRECT COMMAND PROCESSOR
•

The directive statement
.ASKS [1:15::10S] MIDNAM PLEASE ENTER YOUR MIDDLE NAME
displays

>* PLEASE ENTER YOUR MIDDLE NAME [S R:l-15 T:lOS]:
in the format [S R:low-high T:timeout]
where:

4.6.5

The symbol type (string).

R:low-high

The specified range for number of characters.

T:timeout

The specified timeout count.

Begin Block

The .BEGIN directive marks the beginning of a Begin-End
block must be terminated with an .END directive.

r=)

blo~jle'

Labels and local symbols defined following the
.BEGIN directive are
local to the block instead of being used throughout the entire command
file.
Therefore, labels and local symbols defined inside a block lose
definition outside the block.
(Labels and symbols defined outside a
block retain definition throughout the file.)
Labels and symbols
defined outside a block and then modified within the block, however,
assume and retain the value assigned in the block.
Labels and local symbols defined within a block lose definition with
an
.ERASE LOCAL directive statement (see Section 4.6.14) or with the
.END directive
.BEGIN must be the only directive on a command line.
For example, the
.BEGIN directive cannot appear on the same line as an .IF directive.
Format:
• BEGIN
as the only directive on the line.

/ ~.
4.6.6

Continue Processing Using Another File

( .CHAIN

)

The .CHAIN directive closes the current file,
erases all"--lo~/
symbols, clears any .ONERR arguments, empties the direct access Ta5el
cache, and continues processing using command lines from another file.
However,
the .CHAIN directive does not close data files or change the
nested-file level.
Format (brackets not part of syntax):
.CHAIN filename[/switches]
where filename is the name of the file that contains the new command
lines and /switches are any of the optional switches described in
Section 4.5.

4-28

THE INDIRECT COMMAND PROCESSOR
Example:
The directive statement
• CHAIN OUTPUT
transfers control to the file OUTPUT.CMD.

4.6.7

Close Secondary File

The .CLOSE directive closes the secondary
directive.

file

opened

.OPEN

Format (brackets not part of syntax) :
.CLOSE [#n]
where:
#n

An optional file number in the range 0 to x-1, where x is
the number of file-open FDBs specified in the build file
f o r the Ind i rec t task •
( x i s the max i mum number o f f i l es
that can be open simultaneously.) The default is #0. You
can substitute a numeric symbol for the value n by
enclosing the symbol in apostrophes.
/·"'_.:~

4.6.8

Output Data to Secondary File

\ • DATA

The .DATA directive specifies text that is to be output to a secondary
file previously opened by an .OPEN directive.

When Indirect processes the text string that follows the .DATA
directive, it ignores the leading space (if present), assuming it to
be a separator between the directive and the text string.
Any other
spaces are transferred to the data file.
If a TAB follows the
directive, it is transferred to the file.
If no other characters
follow the directive, a blank line is transferred to the file.
This
processing has the following results:
Command File
.DATA fooID
.DATA fooID
• DATA @) foo ID
• DATA @) foo ID
.DATA ID

Open File
foo 00'.J
foo ID
@J foo ID
@l
foo ID
null line

Note that if a comment follows a .DATA statement (that is,
.DATA
data !comment), Indirect also outputs the comment to the secondary
file because it cannot tell if the comment pertains to the .DATA
statement itself or to the data being output to the file.

4-29

"-..___./

THE INDIRECT COMMAND PROCESSOR
Format (brackets not part of syntax):
.DATA [#n]

txt-strng

where:
txt-strng

The text to be output to the secondary file.

An optional file number in the range 0 to x-1, where
x is the number of file-open FDBs specified in the
build file for the Indirect task.
(x is the maximum
number of files that can be open simultaneously.) The
default is #0.
You can substitute a numeric symbol
for
the
value
x by enclosing the symbol
in
apostrophes.

The command line cannot exceed 132(10) characters and the specified
text string cannot continue onto the next line.
If a secondary file
is not open, an error condition exists;
Indirect issues an error
message and begins error processing.
Example:
.SETS SEND "THIS IS DATA"
.OPEN TEMP
.DATA 'SEND'
.CLOSE
These directives output THIS IS DATA to the secondary
(.DAT is the default file type for a data file).

file

TEMP.DAT
···~~

4.6.9

(/,- --- \

Decrement Numeric Symbol

(

.DEC

)

Indirec~

The .DEC directive decrements a numeric symbol by one.
with a
fatal error if the symbol was defined previously as a logical
or string symbol.
Format:
.DEC ssssss
where:
ssssss

The 1- to 6-character numeric symbol.

Example:
.DEC X
This directive decrements by 1
symbol X.

4.6.10

the

value

assigned

Delay Execution for a Specified Period of Time

The .DELAY directive delays further
specified period of time.

4-30

processing

the

numeric

THE INDIRECT COMMAND PROCESSOR
Format:
.DELAY nnu
where:
nn

The decimal number of time units to delay.

T - ticks
S - seconds
M - minutes
H - hours

The parameter nn is decimal by default, or
pound sign (#). For example:

octal

preceded

lOS is 10(10) seconds
#lOS is 10(8) seconds
If quiet mode is disabled when
Indirect issues the message

the

.DELAY

directive

executed,

AT. -- DELAYING
When the time period expires and the task resumes, Indirect issues the
message
AT. -- CONTINUING
Example:
The directive statement
.DELAY 20M
delays processing for 20(10) minutes.

4.6.11

Disable Option

The .DISABLE directive disables a specified operating mode previously
activated by an .ENABLE directive. See Section 4.6.12 for operating
mode information.
Format:
.DISABLE option[,option ••• ]
The following is a list of the operating modes that can be disabled:
ATTACH
CONTROL-Z
DATA
DECIMAL
DELETE

DETACH
DISPLAY
ESCAPE
ESCAPE-SEQ

GLOBAL
LOWERCASE
MCR
OVERFLOW
QUIET

TIMEOUT
TRACE
TRUNCATE
SUBSTITUTION

Note that when you disable detach mode from a command file and then
request a task or CLI command to display information, the command file
may not be able to continue executing. The task or CLI command may
need to attach to the terminal to display the information but will not
be able to do so because Indirect cannot detach from the terminal.

4-31

THE INDIRECT COMMAND PROCESSOR
4.6.12

Enable Option

.ENABLE

The .ENABLE directive is used to invoke several operating modes. Each
mode is independent of the others;
all of them can be active
simultaneously. When Indirect starts to process a file, the initial
settings are:
ATTACH
CONTROL-Z
DATA
DECIMAL
DELETE
DETACH
DISPLAY
ESCAPE
ESCAPE-SEQ

enabled
disabled
disabled
disabled
disabled
enabled
enabled
disabled
disabled

GLOBAL
LOWERCASE
MCR
OVERFLOW
QUIET
SUBSTITUTION
TIMEOUT
TRACE
TRUNCATE

enabled
enabled
enabled
disabled
disabled
disabled
enabled
disabled
disabled

In attach mode, Indirect attaches to a terminal when displaying
comment lines.
In detach mode, it detaches from the terminal when
processing command lines. Enabling both of these modes allows you to
type CTRL/O to suppress a lengthy comment.
Enabling Control-Z mode allows a command file to detect a CTRL/Z
response to a question and continue processing. If Control-Z mode is
disabled and you type CTRL/Z in response to an .ASKx question,
Indirect exits.
If Control-Z mode is enabled, the special symbol
<EOF> is set to true and Indirect continues processing the command
file.
In data mode, Indirect outputs lines that follow an .ENABLE DATA
directive sta~ement to a secondary file.
(The .DATA directive sends a
single line of text to a secondary file;
see Section 4.6.8.) To
disable data mode, the .DISABLE DATA (or .CLOSE) statement must begin
in the first column. Otherwise, Indirect copies the statement itself
into the data file. The .ENABLE DATA directive also has an optional
argument (#n) that specifies which file the data is to go into.
See
the description of the .DATA directive (Section 4.6.8) for more
information.
In global symbol mode, symbol names that begin with a dollar sign ($)
are defined as global to all levels of indirect f1lest once such a
symbol has been defined, all levels recognize it. Symbols that do not
begin with a dollar sign are recognized only within the level that
defines them.
In decimal mode, all numeric symbols are
default as decimal instead of as octal.

created

In delete mode, the current command file is
processes the last command line in the file.

deleted

redefined
when

Indirect

In display mode, Indirect displays the current fields for the .ASKx
directives and @ <EOF>.
If display mode is disabled, Indirect
displays only the text string for the .ASKx directive and suppresses
@ <EOF>.
In MCR mode, commands not processed by Indirect are passed to the
default CLI of the terminal.
The CLI might be MCR, DCL, or a
user-written CLI. MCR mode is equivalent to the functions of the /CLI
and /MC switches.

4-32

THE INDIRECT COMMAND PROCESSOR
In lowercase mode, characters read from the terminal in response to
.ASKS directives are stored in the string symbol without lower- to
11nni:>r("'.::l~P

("'nnui::.r~inn_

'T'hi::.

ri::.nri::.~i::.nt-.::it-inn

("'h.::ir.::i("'ri:>r~

~innifi("'.::int-

;h~~- -;;;P~~-i~9- -~t~ing~-·- c~;~- s~~ti;~-4·: 6:is)--~i~~;-the -: IF-ai~;~ti~;

distinguishes between lowercase and uppercase characters.
In substitution mode, Indirect substitutes a string for a symbol. The
symbol must begin and end in apostrophes ('symbol'). For example, if
the symbol A has been assigned the string value THIS IS A TEST, then
every 'A' will be replaced by THIS IS A TEST. When substitution mode
is enabled, Indirect performs substitutions in each line before
scanning the line for directives and CLI commands.
(While obeying a
.GOTO label directive, however, Indirect ignores any undefined symbols
encountered before the target line, that is, the line containing the
specified label.)
Escape recognition (.ENABLE ESCAPE) permits the response to an .ASK,
.ASKN, or .ASKS directive to be an escape character. A question
answered with a single escape character sets the special logical
symbol <ESCAPE> to true. The escape character must be used only as an
immediate terminator to the question;
if one or more characters
precede the escape character, an error condition exists. In this
case, the message
AT. -- INVALID ANSWER OR TERMINATOR
is printed and the question repeated. Note that if you press the
ESCAPE key in response to an .ASK directive, the specified logical
symbol (ssssss of .ASK ssssss txt-st~ng) is also set to true.
Escape-sequence recognition (.ENABLE ESCAPE-SEQ) forces Indirect to
attach to the terminal for escape-sequence recognition, using the
IO.ATT!TF.SEQ I/O function. In this mode, the result of an .ASKx or
.READ statement from the terminal will contain the terminating escape
character and escape sequence as documented in the full-duplex
terminal driver chapter of the RSX-llM/M-PLUS I/O Drivers Reference
Manual.
Overflow mode allows signed arithmetic in numeric
expressions.
Enabling the mode provides for numeric expressions and operations that
otherwise would result in the "Numeric under- or overflow" error
message.
Quiet mode is valid only in systems that support parent-offspring
tasking;
the directive performs no function in systems that do not
support parent-offspring tasking. In quiet mode, the processor does
not echo CLI command lines or comments.
The command lines are
executed normally and, if they return a message or display, the
message or display is printed on the terminal.
In timeout mode, Indirect uses the timeout parameters specified with
the .ASKx directives. Indirect waits for the timeout count to elapse
and then applies the default answer to the directives.
Timeout mode
must be enabled (the default) to use the timeout counts for the .ASKx
directives.
In trace mode, command lines that Indirect has processed are displayed
on the terminal. As each line is processed, it is displayed with its
nesting level and an exclamation mark (!). Trace mode is equivalent
t-0 the function of the /TR switch.
In truncate mode, Indirect ignores any truncate errors on a .READ
directive. A truncate error occurs when a line in a file is too long.
If the full record cannot fit within the 132(10)-character limit of
the symbol, the record is truncated.

4-33

THE INDIRECT COMMAND PROCESSOR
Formats (brackets not part of syntax) :
.ENABLE option[,option ••• ]
.ENABLE DATA [#n]
where:
#n

An optional file number in the range 0 to x-1, where x
is
the number of file-open FDBs specified in the build file
for the Indirect task.
(x is the maximum number of files
that can be open simultaneously.) The default is #0.
You
can substitute a numeric symbol
for
the value n by
enclosing the symbol in apostrophes.

Examples (assuming that MCR is the default CLI for the terminal):
•

Substitution mode:
.ENABLE SUBSTITUTION
.ASKS FIL SPECIFY SOURCE FILE
MAC
'FIL'='FIL'
When the file is executing, the corresponding lines
at the terminal are:

displayed

>* SPECIFY SOURCE FILE [S]: SOURCE
>MAC SOURCE=SOURCE
•

Global symbol mode:
The following two lines appear in
called TESTl:

indirect

command

file

.ENABLE GLOBAL
.SETS $X "TEST"
A file called TEST2.CMD contains the following lines:
.ENABLE SUBSTITUTION
@TESTl
MAC '$X' ,'$X'='$X'
Therefore, MCR displays the following when the file
is run:

TEST2.CMD

>MAC TEST,TEST=TEST
>@ <EOF>
•

Escape recognition mode:
;IF YOU WANT A LIST OF OPTIONS, TYPE <ESC> •
• ENABLE ESCAPE
.ASKS A ENTER OPTION
.IFT <ESCAPE> .GOTO LIST

.LIST:

;OPTIONS ARE: A (ADD), S (SUBTRACT), M (MULTIPLY)

If you press the ESCAPE key in response to ENTER
lines displayed at the terminal are:

4-34

OPTION,

the

THE INDIRECT COMMAND PROCESSOR
>;IF YOU WANT A LIST OF OPTIONS, TYPE <ESC>.
>* ENTER OPTION [S] :
®9
>;OPTIONS ARE: A (ADD) 1 S (SUBTRACT)j M (MULTIPLY}
•

Quiet mode:
.ASK QUIET DO YOU WANT COMMAND LINES SUPPRESSED
.IFT QUIET .ENABLE QUIET
.IFF QUIET .DISABLE QUIET
ACT
If the response is affirmative, Indirect displays
tasks but not the ACTIVE command. For example:
>DO YOU WANT COMMAND LINES SUPPRESSED?
MCR •••
ACTT17
AT.Tl?

•

the

active

[Y/N] : Y

Control-Z mode:
.ENABLE CONTROL-Z
.ASK RESP DO YOU WISH TO CONTINUE
.IFT <EOF> .GOTO CLENUP
.IFF RESP .GOTO CLENUP
If you type CTRL/Z in response to the question, <EOF>
to true and Indirect transfers to CLENUP.

4.6.13

set

End Block

The .END directive marks the end of the Begin-End block.
If
encounters more
.END directives than
.BEGIN directives,
processing terminates and the following message is displayed:
AT.

-- ILLEGAL NESTING

Format:
.END
as the only directive on the line.

_ .>~
4. 6 .14

l . ERASE /

Delete Symbols

def~~

The .ERASE directive deletes all local or global symbol
or a specific global symbol definition. When you define a symbol,
either locally (by defining a symbol value) or globally
(by enabling
global symbol mode and preceding the symbol name with a dollar sign
($)), Indirect creates an entry in the symbol table.
The
.ERASE
directive erases either all local or all global entries, or a specific
global entry, in the table.
Following an .ERASE directive, you can redefine symbol values as
as symbol type.
Formats:
.ERASE LOCAL
.ERASE GLOBAL
.ERASE SYMBOL global-symbol

4-35

well

THE INDIRECT COMMAND PROCESSOR
An .ERASE LOCAL directive outside of a Begin-End
local symbols defined within the current file.

block

An .ERASE LOCAL directive within a Begin-End block erases
local symbols defined within the block.

erases

all

only

those

However, note that the following actions also occur:
1.

Local symbols defined within a nested file
that file exits.

are

erased

when

Local symbols defined within a
with • END.

block

are

erased

Local symbols defined outside of Begin-End blocks
are
visible, modifiable, and not erasable within a Begin-End
block.

An .ERASE GLOBAL, either outside
erases all global symbols.

Begin-End

within

Begin-End

block,

global

symbol.

An .ERASE SYMBOL global-symbol erases the specified
(Individual local symbols are not erasable.)
Example:
.ERASE LOCAL
This directive erases
indirect command file •

all

local

symbol

definitions

used

the

• ERASE SYMBOL $SWITC
This directive erases the single global symbol "$SWITC."
. :::~"'- ..

4.6.15

Exit Current Command File

.EXIT~)

The .EXIT directive terminates processing of the current comma~-i"f~
or Begin-End block and returns control to the previous-level command
file or, if the directive is executed within a block, to the line
following the .END directive. If the directive is encountered at the
uppermost indirect nesting level, Indirect exits and passes control to
the CLI (see the .STOP directive, Section 4.6.33).
The .EXIT directive also allows you to optionally specify a
copy into the special symbol <EXSTAT>.

value

the

Format (brackets not part of syntax) :
.EXIT [value]
where value is an optional numeric expression
special symbol <EXSTAT>.

copied

Examples:
The following line appears in an indirect command file called TESTl:
@TEST2

4-36

THE INDIRECT COMMAND PROCESSOR
The file TEST2.CMD contains the following line:

.EXIT
When Indirect encounters the .EXIT directive in TEST2, control returns
to TESTl.CMD.
If the .EXIT directive in TEST2.CMD includes a numeric expression, for
example:
.EXIT N+2
Indirect evaluates the expression and copies the value into <EXSTAT>.
/',,/_,,, ...-;.:;~

4.6.16

Call a Subroutine

eOSUB )

The .GOSUB directive saves the current position in an indirect comrrrn-~
file and then branches to a label.
The label identifies an entry
point to a subroutine that is terminated by a .RETURN directive.
When you issue a .GOSUB directive from within a Begin-End block,
Indirect saves the current block context and then scans down the file
searching for the first occurrence of the subroutine label. Note that
during the scan,
Indirect ignores any intervening .BEGIN or .END
directives.
The .RETURN directive restores previous block context.
Thus, the subroutine can be contained within a Begin-End block.
The maximum nesting depth for subroutine calls depends on
specified in the build file for the Indirect task.

the

number

Format:
.GOSUB label parameters
where label
is the label that designates the first line of a
subroutine, but without the leading period and trailing colon. Any
parameters to the right of the label and to the left of a comment are
transferred to the reserved local symbol COMMAN.
The value of COMMAN
can then be parsed with the .PARSE directive (see Section 4.6.25)
to
obtain formal call parameters.
Example:
The directive statement
.GOSUB EVAL
transfers control to the subroutine labeled .EVAL:.
,

4.6.17

Branch to a Label

•... · "....
··-

(.GOTO

The .GOTO directive causes a branch from one 1 ine in an in'ct-rr~
command file to another. All commands between the .GOTO directive and
the specified label are ignored. Branches can go forward or backward
in the file.
The target of a .GOTO branch from within a Begin-End block must be
contained in that block~
The
~GOTO
directive cannot branch into
another block. When Indirect encounters a .GOTO directive within a
Begin-End block, it searches for the specified label
in that block.

4-37

)

THE INDIRECT COMMAND PROCESSOR
Since Indirect only searches the one Begin-End block, you can use
same label more than once in a command file.

the

Format:
.GOTO label
where label is the name of the label, but without the
and trailing colon.

leading

period

Example:
The directive statement
.GOTO 100
transfers control to the line containing the label .100:.

Q
~

4.6.18

Logical Test

A number of directives make tests; if the test is true, Indirect
processes the remainder of the command line. Logical tests can be
combined into a compound logical test by using the .AND and .OR
directives.

4.6.18.1 Test If Symbol Meets Specified Condition (.IF) The .IF
directive compares a numeric or string symbol with another expression
of the same type to determine if one of several possible conditions is
true.
If the condition is satisfied, Indirect executes the remainder
of the command line.
When comparing a string symbol with a string expression, Indirect
compares the ASCII values of each operand's characters (from left to
right) one by one. An operand is considered greater if the first
nonequal
character has a greater value than the corresponding
character in the other operand. Numeric symbols are compared strictly
on the basis of magnitude.
Format:
.IF symbol relop expr directive-statement
where:
symbol

The 1- to 6-character numeric or string symbol.

re lop

One of the following relational operators:
EQ or
NE or
GE or
LE or
GT or
LT or

- Equal to

<> - Not equal to
>= - Greater than or equal to
<= - Less than or equal to
> - Greater than
< - Less than

ex pr

An expression of the same type as symbol.

directivestatement

The Indirect command line
condition is satisfied.

4-38

to be

processed if the

THE INDIRECT COMMAND PROCESSOR
Examples:
.. SETS X "A"

.SETS Y "a"
.IF X LT Y .GOTO 200
The ASCII value of string symbol X is less than the ASCII value of
string symbol Y, which satisfies the less-than condition. Thus,
control passes to the line containing the label .200: •
. SETN Nl 2
.SETN N2 7
.IF Nl <= N2 PIP /LI
With the condition satisfied (numeric symbol Nl less than or equal
numeric symbol N2), the PIP command is processed •
• SETS Sl "AAb"
• SETS S2 "AA"
.SETS S3 "BBBB"
.IF Sl >= S2+S3[1:1]

.INC N

Since the condition where string symbol Sl is greater than or equal to
string symbol S2 concatenated with the first character of string
symbol S3 (AAb >= AAB)
is satisfied,
Indirect increments numeric
symbol N.

4.6.18.2 Test If Task Is Active or Dormant
.IFACT or .IFNACT directive tests whether a tas
dormant (.IFNACT).
If the test is true, the rest of
processed.
If the specified task is not installed,
the dormant condition.
Formats:
.IFACT

taskname directive-statement

.IFNACT

taskname directive-statement

where:
taskname

A 1- to 6- character legal task name.

directivestatement

The Indirect command line to be processed if the
condition is satisfied.

Examples:
.IFACT

REPORT

.GOTO 350

.IFNACT

REPORT

RUN REPORT
-··'"·-~

,,,----···-~--~ - -- - . )
4.6.18.3 Test If Symbol Is Defined or Not Defined (.IFDF/IFNDF) ~The
.IFDF or .IFNDF directive tests whether a logical numeric,
symbol has been defined {.IFDF) or not defined (.IFND
is true, the rest of the command line is processed. This
does not test the value of the symbol.
___

4-39

THE INDIRECT COMMAND PROCESSOR
Formats:
.IFDF

ssssss

directive-statement

.IFNDF

ssssss

directive-statement

where:
ssssss

The 1- to 6-character symbol being tested.
The
symbol can be local, global, or an Indirect
special symbol.

directivestatement

The Indirect command line
condition is satisfied.

to be processed if the

Examples:
.IFDF

.GOTO 100

.IFNDF

.ASK A DO YOU WANT TO SET TIME

4.6.18.4 Test If Task Is Installed Or Not Installe
The
.IFINS or
.IFNINS directive tests whether
{.IFINS) or not installed (.IFNINS) in the system.
true, the rest of the command line is processed.
Formats:
.IFINS

taskname

directive-statement

.IFNINS

taskname

directive-statement

where:
taskname

A 1- to 6-character task name.

directivestatement

The Indirect command line to be processed if the
condition is satisfied.

Examples:
.IFINS

PIP

.GOTO 250

.IFNINS

PIP

INS $PIP

/..

Test If Mode Is Enabled Or Disabled( (. IFENABLED/. IFDISABL~O.y·/
- The
.IFENABLED or .IFDISABLED directive t~t:h~-arr·~'tJ·per'a"Eing
mode has been enabled with the .ENABLE directive or disabled with the
.DISABLE directive.
(See the description of the .ENABLE directive in
Section 4.6.12 for the list of operating modes.)

4. 6 .18. 5

Formats:
.IFENABLED option directive-statement
.IFDISABLED option directive-statement

4-40

THE INDIRECT COMMAND PROCESSOR
where:
option

The same operating mode option (with the exception
of
DATA)
used with the .ENABLE or .DISABLE
directive, or FULL-DUPLEX, POTASK, or FMS.
(FMS
is valid only on RSX-llM-PLUS systems.)

directivestaternent

The Indirect command line to be processed if the
condition is satisfied.

4.6.18.6 Test If Driver Is Loaded Or Not Loaded ct.IFLOA/.IFNLOA} The • IFLOA or • IFNLOA directive tests whether a ·--·a-r·tver- i-s.-..1.o.aded
(.IFLOA} or not loaded (.IFNLOA) in the system.
If the test is true,
the rest of the command line is processed.
Note that for purposes of
this directive, resident drivers are assumed to be loaded.
Formats:
.IFLOA dd:

directive-statement

.IFNLOA dd:

directive-statement

where:
dd:

A device driver

directivestatement

The Indirect command line to be processed if the
condition is satisfied.

Examples:
.IFLOA DK:

.GOTO 250

.IFNLOA DK:

LOA DK:

4.6.18.7 Test If Symbol Is True Or False
.IFF directive tests whether a logical
the test is true, Indirect processes the
line.

The
.IFT or
rue or false.
If
remainder of the command

Indirect exits with a fatal error if the symbol
previously defined as a numeric or string symbol.

being

tested

was

Formats:
.IFT

ssssss

directive-statement

.IFF

ssssss

directive-statement

where:
ssssss

The 1- to 6-character logical symbol being tested.

directivestatement

The Indirect command line to be processed if the
condition is satisfied.

Examples:
.IFT

.GOTO

100

.IFF

.GOTO

200

4-41

April 1983

THE INDIRECT COMMAND PROCESSOR
4.6.18.8 Compound Tests - You can combine .IF tests by using the .AND
and .OR directives.
In addition, an implied .AND is effected when
more than one .IF appears on the same line without being separated by
an .AND directive.
The .AND directive takes precedence over the .OR directive as shown in
the following example:
.IFT A .OR .IFT B .AND .IFT C .GOTO D
That is, Indirect reads the line as:
• IFT A .OR (. IFT B .AND • IFT C)

.GOTO D

Examples:
.IFT A .AND .IFF B

.GOTO HELP

If the logical symbol A is true and the logical symbol
control passes to the line containing the label .HELP: •

false,

If the logical symbol A is true or if the logical symbol B
the RUN command is issued.

false,

• IFT A .IFF B

.GOTO HELP

Same effect as the previous directive (.AND implied) •
• IFT A .OR

.IFF B RUN .PIP

.6.19

I . INC

Increment Numeric Symbol

Indirec~//

The .INC directive increments a numeric symbol by one.
with a fatal error if the symbol was previously defined as a logical
or string symbol.
Format:
.INC ssssss
where:
SSS SSS

The 1- to 6-character numeric symbol being incremented.

Example:
• INC B
Increment by l the value assigned to the numeric symbol B.

4.6.20

Define Logical End-of-File

The logical end-of-file directive (/) terminates file
exits. The message

I
processing

>@ <EOF>
is then displayed (if display mode has not been disabled}.

4-42

and

THE INDIRECT COMMAND PROCESSOR
Format:

I
as the first nonblank character on a line.
You can use this directive at any location in the command file to
quickly terminate file processing, but care should be taken to avoid
an inadvertent exit.
Example:
.ASK CONT DO YOU WISH TO CONTINUE
.IFT CONT .GOTO 100
.100:

4.~.21

Branch to Label on Detecting an Error

If Indirect detects one of the following errors:
•

Task not installed in system (.XQT,

•

Undefined symbol

•

Bad syn tax ( • XQT,

•

Unrecognized command

•

String substitution error

•

Symbol type error (.IF,

•

Redefinition of a symbol to a different type
(.ASK,
• ASKS, • SETT, • SETF, • SETL, • SETN, • SETD, • SETO, • SETS)

Data file error (.OPEN,
.OPENA,
.OPENR,
.DATA,
.READ between .ENABLE DATA and .DISABLE DATA)

• WAIT,

.WAIT)

• DELAY)

.IFT,

.IFF, .INC, .DEC)
.ASKN,

.CLOSE,

control passes to the line containing the specified label.
This
feature provides you with a means of gaining control to terminate
command file processing in an orderly manner.
Note that the .ONERR directive applies only to the error conditions
listed;
errors returned
from a task external to
Indirect (for
example, an MCR syntax error)
are not processed by the
.ONERR
directive.
Format:
.ONERR

label

Upon detecting an error, the processor passes control to the line
starting with
.label:.
The
.ONERR directive must be issued before
Indirect encounters the error condition.
If the directive is executed
(one of the listed errors is encountered), error processing passes to
the specified label.
If the label specified by the
.ONERR directive
does not exist and an error condition has occurred, command processing
terminates.

4-43

THE INDIRECT COMMAND PROCESSOR
Once an .ONERR condition has occurred, another .ONERR
be issued to trap a future error.

directive

must

The .ONERR directive works with the special symbol <ERRCTL> (see
Section 4.4.1.2).
For each class of error that an .ONERR target
routine processes, the appropriate bit is set in the symbol.
The
initial default value for <ERRCTL> is 1, which implies that only class
1 errors can be handled with an .ONERR routine.
(Note that if you
attempt to process errors other than default class 1, Indirect cannot
continue in most cases. The error service routine is limited to a
fatal error message and .EXIT.
The internal state of Indirect is
indeterminate in all but class 1 error cases.) See Section 4.8 for a
list of error messages and their assigned class values.
Example:
.ONERR

100

Upon detecting one of the
the line labeled .100:.

4.6.22

er~or

conditions, Indirect passes control to

Open Secondary File

The .OPEN directive opens a specified secondary file as an output
file.
The .DATA directive is used to place data in this secondary
file.
Format (brackets not part of syntax):
• OPEN [#n] filename
where:
filename

A file to be opened as an
file type is .DAT.

output

file.

An optional file number in the range O to x-1, where x
is the number of file-open FDBs specified in the build
file for the Indirect task.
(x is the
maximum number
of files that can be open simultaneously.) The default
is #0. You can substitute a numeric symbol for the
value n by enclosing the symbol in apostrophes.

The

default

Note that you cannot include a comment that begins with a semicolon
(;comment) in an .OPEN statement. Doing so results in a syntax error.
(Comments that begin with an exclamation mark
(!comment)
are
accepted.)
Example:
.OPEN SECOUT
This directive opens the file SECOUT.DAT as an output file.

4.6.23

Open Secondary File for Append

The .OPENA directive opens a secondary file and appends all
data to the file.

4-44

THE INDIRECT COMMAND PROCESSOR
Format {brackets not part of syntax):
.OPENA f#nl

filename

where:
filename

A secondary file to be opened with subsequent
appended to it. The default file type is • DAT.

data

An optional file number in the range O to x-1, where x
is the number of file-open FDBs specified in the build
file for the Indirect task.
(x is the maximum number
of files that can be open for append simultaneously.)
The default is #0.
You can substitute a numeric symbol
for the value n by enclosing the symbol in apostrophes.

Note that you cannot include a comment that begins with a semicolon
{;comment)
1n an
.OPENA statement.
Doing so results in a syntax
error.
(Comments that begin with an exclamation mark
(!comment)
are
accepted.)
If the specified file does not already exist, .OPENA becomes the .OPEN
directive by default.
Example:
.OPENA SECOUT
This directive opens the file SECOUT.DAT as an output file and appends
subsequent data to it.
/ _,,..
_

4.6.24

.OPENR

Open File for Reading

The
.OPENR
directive.

directive

opens

··''"'··''".---....."\

file

for

reading

with

th~----·--..~D

Format (brackets not part of syntax):
• OPENR [#n]

filename

where:
filename

A file to be opened for reading.
is • DAT.

The default file type

An optional file number in the range O to x-1, where

x
is the number of file-open FDBs specified in the build
file for the Indirect task.
{x is the maximum number
of files that can be open for reading simultaneously.)
The default is #0.
You can substitute a numeric symbol
for the value n by enclosing the symbol in apostrophes.
Note that you cannot include a comment that begins with a semicolon
{;comment)
in an
.OPENR statement.
Doing so results in a syntax
error.
(Comments that begin with an exclamation mark
(!comment)
are
accepted.)
Examples:
• OPENR INDADD

4-45

THE INDIRECT COMMAND PROCESSOR
This directive opens the file INDADD.DAT for reading
directive •

with

the

.READ

• OPENR DATLIB.ULB/LB:DATINP
This directive opens for reading the library
contained in the universal library DATLIB.

4.~.25

module

DATINP

that

Parse Strings into Substrings

The .PARSE directive parses strings in a command line
Format:
.PARSE <string> <control-string> <varl> <var2> •••

<varn>

The string is broken up into substrings as specified by the control
string.
The substrings are stored in the specified variables. The
first character of the control string delimits the first substring,
the second character of the control string delimits the second
substring, and so on. The last character of the control string
is
repeated
if the number of variables exceeds the length of the control
string.
If you specify more variables than substrings, the additional
variables are set to null strings.
If you specify less variables than
the number of substrings that can be parsed, the last variable
contains the unparsed fragment of <string>.
The symbol <STRLEN> contains the actual number of substrings
Indirect processed (including explicit null substrings).

that

Example:
.PARSE COMMAN" ," FILE Al A2 A3 A4 AS
Given that COMMAN contains "TESTFILE IND,MCR,,LOA", this directive has
the following results:
FILE
Al
A2
A3
A4
AS

TESTFILE
IND

MCR
null
LOA
null

<STRLEN> contains a 5.

4. 6. 26

Pause for Operator Action

/~
•

PAUSE )

comm~~

The .PAUSE directive interrupts processing of an indirect
to wait for user action. A .PAUSE directive causes Indirect to stop
itself. You can then perform some operations and subsequently cause
the task to resume.
Format:
• PAUSE
When Indirect stops itself, it displays the following message
entering terminal:
AT. -- PAUSING.

TO CONTINUE TYPE "command taskname"

4-46

the

THE INDIRECT COMMAND PROCESSOR
where:
command

The command line to be issued to resume the task.

taskname

The name of the Indirect task.

You then type the appropriate command
Indirect then displays the message:

line

resume

the

task.

the

command

line

AT. -- CONTINUING
and it continues processing where it left off.
Note that the .PAUSE directive is legal only
interpreter for your terminal is MCR or DCL.

~"'~

4.6.27