Digital PDFs

DEC-11-OXDUA-B-D

November 1975

339 pages

Original

9.4MB

Document:	RSX-11D User's Guide
Order Number:	DEC-11-OXDUA-B-D
Revision:	0
Pages:	339
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11d/RSX11D_V6.2_Feb77/DEC-11-OXDUA-B-D_RSX-11D_Users_Guide_197511.pdf

OCR Text

RSX-11D
User's Guide
Order No. OEC-11-0XOUA-B-O

RSX-11D
User's Guide
Order No. DEC-11-0XDUA-8-D

RSX-11 D Version 68 (Version 6.1)

digital equipment corporation · maynard. massachusetts

First Printing, June, 1975
Revised, November, 1975
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may be used or copied only in accordance with the terms of such
license.
Digital Equipment Corporation assumes no responsibility for the use or
reliability of its software on equipment that is not supplied by
DIGITAL.

(S) 1975 by Digital Equipment Corporation

The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM

DECsystem-10
DEC tape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8

MASSBUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-IO
TYPESET-11

10/77-15

CONTENTS
Page
PREFACE

CHAPTER

0.1
0.2
0.3

MANUAL OBJECTIVE AND READER ASSUMPTIONS
STRUCTURE OF THE MANUAL
ASSOCIATED DOCUMENTS

INTRODUCTION

1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.7.S
1.7.9
1.S
1.9
1.10
1.11
1.12
1.13
1.14
1.15
1.16
1.17

RSX-11D COMPONENTS
RSX-11D EXECUTIVE
MONITOR CONSOLE ROUTINES (MCR)
FORTRAN LANGUAGE AND OBJECT TIME SYSTEM
MACRO ASSEMBLER
TASK BUILDER
UTILITY PROGRAMS
Peripheral Interchange Program (PIP)
Edi tor (EDI)
File Transfer Program (FLX)
Verification (VFY)
Source Language Input Program (SLP)
File Compression (SQZ)
Dump Utility (DMP)
Librarian (LBR)
ZAP Utility Program (ZAP)
FILE CONTROL SERVICES
DEVICE HANDLER TASKS
ON-LINE DEBUGGING TECHNIQUE
BATCH CAPABILITY
SYSTEM GENERATION
TASK ACCOUNTING
HARDWARE ERROR LOGGING
ON-LINE HARDWARE DIAGNOSTICS
MEMORY PARITY CHECKING
SYSTEM TEST PACKAGE

FUNDAMENTAL RSX-11D CONCEPTS

2.1
2.1.1
2.1.2
2.1.3
2.2
2.2.1
2.2.2
2.2.3
2.3
2.4
2.5
2.6

PARTITIONS
User-Controlled Partitions
System-Controlled Partitions
Memory Protection
TASKS
Overlays
Multiuser Tasks
Task Interaction
SCHEDULING TASK EXECUTION
CHECKPOINTING
DEVICE INDEPENDENCE
PRINT FILE SPOOLING, DESPOOLING, AND INPUT
SPOOLING
SHAREABLE GLOBAL AREAS

2.7

iii

x
x
xi

1-2
1-3
1-3
1-4
1-4
1-4
1-5
1-5
1-5
1-5
1-6
1-6
1-6
1-6
1-6
1-7
1-7
1-7
l-S
l-S
l-S
l-S
1-9
1-9
1-9
1-10

2-1
2-1
2-1
2-3
2-3
2-3
2-5
2-5
2-7
2-S
2-S
2-9
2-9

CONTENTS (Cont.)
Page
CHAPTER

CHAPTER

RSX-1lD CONVENTIONS

3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.5
3.6

DEVICE-RELATED CONVENTIONS
Pseudo-Devices
System Device (SY)
Terminal Interface (TI)
Console Input (CI) , Console Output (CO),
and Console Log (CL)
Message Output (MO)
Spooling Output (SP)
Batch Pseudo Device (BP)
Logical Unit Numbers (LUNs)
SUPPORTED FILE STRUCTURES
Files-II
Files-II Volumes
File Format
Master File Directory
User File Directory
File Ownership
User Identification Code
Volume and File Protection
COMMAND SYNTAX AND FILE SPECIFIERS
Defaults in File Specifiers
RSX-1lD File Types
Asterisk Conventions (wildcards)
Examples of Command Strings
INDIRECT FILES
TERMINAL CONVENTIONS
CARD READER CONTROL CONVENTIONS

USER/SYSTEM INTERFACE

4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.2
4.2.1

MONITOR CONSOLE ROUTINE
4-1
MCR Organization
4-1
Command and Slave Terminals
4-1
Activating MCR
4-2
User Privileges
4-2
Entering System Commands
4-3
MCR Timeout
4-3
TASK RUN-TIME UICs AS FUNCTION OF USER TYPE 4-4
Error Reporting
4-4

GENERAL USER COMMANDS

5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.11.1

ABORT COMMAND (ABO)
ACTIVE TASK LIST COMMAND (ACT)
BYE COMMAND (BYE)
LIST COMMON BLOCKS COMMAND (COM)
CONTINUE COMMAND (CON)
DEVICES COMMAND (DEV)
DISMOUNT VOLUME COMMAND (DMO)
HELLO COMMAND (HEL)
LOG COMMAND
LOGICAL UNIT NUMBERS COMMAND (LUNS)
MOUNT COMMAND (MOU)
Format for Mounting Multivolume Magnetic
Tape

3-1
3-1
3-2
3-3
3-3
3-3
3-3
3-3
3-4
3-4
3-4
3-5
3-5
3-7
3-8
3-8
3-8
3-9
3-15
3-15
3-16
3-18
3-18
3-19
3-19
3-22

5-2
5-3
5-8
5-9
5-10
5-11
5-12
5-14
5-16
5-17
5-18
5-21

CONTENTS (Cant.)
Page

CHAPTER

5.12
5.13
5.14
5.15
5.15.1
5.15.2
5.15.3
5.15.4
5.15.5
5.16
5.17
5.18
5.19
5.20
5.21

OPERATE COMMAND (OPR)
PARTITIONS COMMAND (PAR)
PASSWORD COMMAND (PWD)
QUEUE COMMAND (QUE)
Queue a File for Printing
List Elements in Queue (ILl)
List All Elements in Queue (/AL)
Kill (Delete) Elements in Queue (/KI)
Modify a Queue Entry (/MO)
RESUME COMMAND (RES)
RUN COMMAND (RUN)
SYSTEM STATUS COMMAND (SYS)
TASK LIST COMMAND (TAS)
TIME COMMAND
TERMINAL STATUS CO~llirnND (WHO)

PRIVILEGED USER COMMANDS

6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.10.1
6.11
6.12
6.13
6.14
6.15
6.16
6.17
6.18
6.19
6.20
6.21
6.22
6.23
6.24
6.25
6.26
6.27
6.28

ABORT COMMAND (ABO)
ALTER PRIORITY COMMAND (ALT)
BAD BLOCKS COMMAND (BAD)
BOOTSTRAP COMMAND (BOO)
CANCEL COMMAND (CAN)
DISABLE COMMAND (DIS)
DISMOUNT VOLUME COMMAND (DMO)
ENABLE COMMAND (ENA)
FIX-IN-MEMORY COMMAND (FIX)
INITIALIZE VOLUME COMMAND (INI)
MAN Option for IBAD Keyword
INSTALL TASK COMMAND (INS)
LOAD COMMAND (LOA)
MEMORY UNLOCK (MEM)
MOUNT VOLUME COMMAND (MOU)
OPEN REGISTER COMMAND (OPE)
OPERATE COMMAND (OPR)
ENTER PASSWORD COMMAND (PWD)
QUEUE COMMAND (QUE)
REASSIGN COMMAND (REA)
REDIRECT COMMAND (RED)
REMOVE COMMAND (REM)
RUN COMMAND (RUN)
SAVE COMMAND (SAVE)
SET COMMAND (SET)
TIME COMMAND (TIM)
USER FILE DIRECTORY COMMAND (UFD)
UNFIX COMMAND (UNF)
UNLOAD COMMAND (UNL)

MAGNETIC TAPE VOLUMES

7.1
7.2
7.3
7.4

INITIALIZING TAPE VOLUMES
MOUNTING A VOLUME SET
DISMOUNTING THE VOLUME
OPERATOR INTERACTION WITH THE MAGNETIC
TAPE FILE SYSTEM

5-23
5-25
5-26
5-27
5-28
5-32
5-33
5-33
5-35
5-39
5-40
5-42
5-52
5-53
5-54

6-2
6-3
6-4
6-6
6-9
6-10
6-11
6-12
6-13
6-14
6-18
6-22
6-27
6-28
6-29
6-31
6-34
6-35
6-36
6-37
6-38
6-40
6-41
6-47
6-52
6-55
6-56
6-58
6-59

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

CONTENTS (Cont. )
Page
CHAPTER

APPENDIX A
A.l
A.2
A.2.I
APPENDIX B
B.l
B.2
B.2.1
APPENDIX C
C.l
C.2
APPENDIX D
D.l
D.2
APPENDIX E
E.l
E.2
E.2.1
E.2.2
E.2.3
APPENDIX F
F.l
F.2
APPENDIX G
G.l
G.2
APPENDIX H
H.l
H.2
APPENDIX I
1.1
I.2
I.2.1

NODE POOL STATUS PROGRAM
MCR COMMAND SUMMARY AND ERROR MESSAGES
MCR COMMAND SUMMARY
MCR ERROR MESSAGES
Messages from Task MCRERR

A-I
A-II
A-52

PIP COMMAND SUMMARY AND ERROR MESSAGES
PIP COMMAND SUMMARY
PIP ERROR MESSAGES
PIP Error Codes

B-1
B-4
B-IO

FLX COMMAND SUMMARY AND ERROR MESSAGES
FLX COMMAND SUMMARY
FLX ERROR MESSAGES

C-l
C-3

DMP COMMAND SUMMARY AND ERROR MESSAGES
DMP COMMAND SUMMARY
DMP ERROR MESSAGES

D-l
D-l

EDI COMMAND SUMMARY AND ERROR MESSAGES
EDI COMMAND SUMMARY
EDI ERROR MESSAGES
Command Level Informational and Error
Messages
File Access Warning Messages
Error Messages that Result in Restarting
the Editing Sessions

E-l
E-6
E-6
E-IO
E-Il

SLP COMMAND SUMMARY AND ERROR MESSAGES
SLP COMMAND SUMMARY
SLP ERROR MESSAGES

F-l
F-l

LBR COMMAND SUMMARY AND ERROR MESSAGES
LBR COMMAND SUMMARY
LBR ERROR MESSAGES

G-l
G-3

SQZ COMMAND SUMMARY AND ERROR MESSAGES
SQZ COMMAND SUMMARY
SQZ ERROR MESSAGES

H-l
H-l

VFY COMMAND SUMMARY AND ERROR MESSAGES
VFY COMMAND SUMMARY
VFY ERROR MESSAGES
VFY Error Codes

I-I
I-2
1-3

CONTENTS (Cont.)
Page
APPENDIX J
J.l
J.2
APPENDIX K
K.l
K.l.l
K.l.2
K.l.3
K.l.4
K.2
APPENDIX L
L.l
L.l.l
L.2
APPENDIX M
M.l
M.2
APPENDIX N

ZAP COMMAND SUMMARY AND ERROR MESSAGES
ZAP COMMAND SUMMARY
ZAP ERROR MESSAGES
MACRO-II ASSEMBLER COMMru~D
ERROR MESSAGES

J-l
J-l
SU~~RY

AND

COMMAND SUMMARY
K-l
Summary of Macro Assembler Control Switches K-l
Listing Control Switches
K-l
Function Control Switches
K-4
Assembler Control Switches
K-6
MAC ERROR MESSAGES
K-6
TKB COMMAND SUMMARY AND ERROR MESSAGES
TKB COMMAND SUMMARY
TKB File Switches
TKB ERROR MESSAGES

L-l
L-2
L-5

BATCH COMMAND SUMMARY AND ERROR MESSAGES
COMMAND SUMMARIES
BATCH ERROR MESSAGES

M-l
M-2

SYSTEM STANDARD ERROR CODES
FIGURES
Page

Figure

2-1
2-2
2-3

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

3-4
5-1
5-2
5-3
5-4
5-5
6-1
8-1

Physical Memory Divided into Partitions
Overlay Structure
Multiuser Tasks
Use of Event Flags for Intertask
Communication
Use of the Common Area for Intertask
Communication
Use of SEND/RECEIVE Directive
Sample Files-II File Structure
Files-II File Access Scheme
Format of File Protection Word
Formula for Determining Task File Access
Category
Sample Output from QUE ILl Function
Sample Execution of IKI Function
Sample Execution of fMO Function
Sample Execution of fMO Function (Default)
Sample TASK LIST Listing and Descriptions
of Listed Items
Format of Open Register Command Output
Sample POOL Execution and Termination

vii

2-2

2-4
2-6
2-6
2-7
2-10
3-7
3-11
3-12

3-14
5-32
5-34
5-37
5-38
5-44
6-32
8-2

CONTENTS (Cont.)
TABLES
Page
Table

3-1
3-2
3-3
3-4
3-5
3-6
4-1
5-1
5-2
5-3
5-4
5-5
5-6
5~7

6-1
6-2
6-3
6-4
B-1
I-I
K-l
K-2
L-l

RSX-llD Device Mnemonics
Default LUN Assignments
Filename Specifier Defaults
RSX-llD File Specifier Defaults
Terminal Control Conventions
Card Reader Control Conventions
UIC of an Executing Task
ACT Task Status Characters
OPR Switches
Defaults in QUE File Specifiers
QUE Command Optional Switches
/MO Option Switches
Defaults in Task Image File Specifiers
SYS Switches
Defaults in BOO File Specifiers
Defaults in INS File Specifiers
Operate Option Switches
UFD Switches
PIP Error Codes
VFY Error Codes
Argument Values for Listing Control
Switches
Function Control Arguments
Task Image File Switches

viii

3-2
3-4
3-16
3-17
3-20
3-22
4-5
5-5
5-24
5-29
5-30
5-36
5-40
5-43
6-7
6-26
6-34
6-57
B-10
I-4
K-2
K-5
L-2

PREFACE

0.1

MANUAL OBJECTIVE AND READER ASSUMPTIONS

The objective of this manual is to provide the user with an
introduction to the basic concepts of RSX-IID and to describe the use
of the terminal interface with the system.
The manual is intended for use by two types of users:
general and
privileged. Functions available to the general user are restricted to
those required for program development and checkout.
Functions
available to the privileged user provide the means for system control
and modification.
For the general user, no other manuals in the RSX-IID documentation
set are prerequisite to the use of this manual. The privileged user,
however, may wish to become familiar with the RSX-IID System Manager's
Guide.

0.2

STRUCTURE OF THE MANUAL

The manual is divided into three major chapter groupings. Chapters 1
through 4 introduce the user to the system. Chapters 5 and 6 detail
actual system commands.
Appendices A through N provide summary
information.
to

Chapter 4 describes gaining access to the
system, and using the system.

logging

onto

the

system,

RSX-IID,

its

Chapter 1 through 3 provide an introduction
components, file structure, and conventions.

Chapter 5 describes the system commands
users of the system.

that

are

available

all

Chapter 6 describes the system commands
privileged users.

that

can

only

used

volumes

within

the

system

node

pool

Chapter 7 describes the
system.

use

magnetic

Chapter 8 describes the use and operation
program.

tape
of

the

Appendixes A through N contain command summaries
for frequently-used RSX-IID components.

and

error

messages

The following conventions are used to describe
string formats:
1.

CD indicates ALTmode or ESCape.

0.3

examples

and

command

indicates a RETURN.
All
command
lines
are normally
terminated by pressing RETURN unless otherwise
noted
in the text.

In all cases, except where
[UIC]
or
brackets signify optional parameters.

[UFD]

is specified,

ASSOCIATED DOCUMENTS

A synopsis of each manual in the RSX-llD documentation set is provided
in the RSX-llD Documentation Directory, Order Number DEC-ll-OXUGA-C-D.
The directory also defines the readership of each manual in the set.

CHAPTER 1
INTRODUCTION

RSX-llD is

a resource-sharing executive designed
to run on the
PDP-ll/45, PDP-II/50, and PDP-ll/70.
It provides an ideal
environment for both real-time data
processing
and
multiuser
applications.
It includes the following features:
PDP~11/40,

Memory protection on a task-by-task* basis
Multiuser approach to
user-developed tasks

both

system-provided

tasks

and

for

task

User-defined memory partitions
Modular approach to program development
An extensive set of monitor console routines (MCR)
control from any terminal
MCR routines for system control
A task overlay system to reduce the amount of memory required
for tasks
Priority and
execution

time-slice

techniques

for

scheduling

Capability to assign priorities (1 through 250)

task

to tasks

Checkpointing (roll-out/roll-in) based on task priority
Shared disk-resident and memory-resident libraries containing
often-used routines
Batch capability to allow execution of job streams read
a peripheral device
Macro call capability for file and I/O operations
Device independence for I/O flexibility

*A task is the basic executable unit in RSX-llD.

1-1

from

INTRODUCTION
A file control system for processing RSX-llD
standard
(Files-II) disk and DECtape volumes, as well as ANSI standard
multivolume magnetic tape
Task approach to device handlers to
user-written handler tasks

allow

incorporation

File and volume protection
System access protection
Capability to define task attributes during
task building,
rather
than
during
assembly/compilation,
for greater
flexibility
Accounting to
resources

provide

statistics

task

use

system

Spooling of print files
Support of Massbus devices
Support of analog/digital devices
Automatic logging of hardware errors
On-line diagnostics capability
Power recovery support
System-performed memory parity checking
System generation capability, on-line or off-line

1.1

RSX-llD COMPONENTS

The RSX-llD system consists of the following software components:
An Executive to control the internal operation of the system
A set of monitor console routines (MCR)
to communicate with the system
An additional set of MCR
control of the system

commands

that enable the

that

allow

centralized

A FORTRAN compiler and object time system COTS) and
assembler
A task builder
to create
relocatable object modules

loadable

task

user

MACRO

images

from

Utility programs
File control services (FCS)
Device handler tasks to service I/O requests
On-line debugging aid (ODT) and trace capability to assist in
program development

1-2

INTRODUCTION

Batch stream processor
System generation package
Task accounting package
Hardware error logging package
System test package

1.2

RSX-llD EXECUTIVE

The main function of the RSX-llD Executive is system control
(e.g.,
scheduling tasks, controlling task interaction, checkpointing, placing
tasks in partitioned memory, and interfacing with the user via MCR).
The Executive also provides the user with a set of system directive
commands which can be included in MACRO and FORTRAN programs to
request Executive services.
System directive commands provide the follriwing services for executing
tasks:
Starting, scheduling, canceling,
other tasks

terminating,

and

resuming

Fixing a task in memory or releasing it
Enabling a task to run or disabling it
Enabling or disabling checkpointing for a task
Obtaining information about the status of tasks
Setting event flags,
testing
them,
capabilities related to event flags

and

performing

other

Handling software and hardware interrupts (RSX-llD traps)
Handling input/output
The Executive is
Reference Manual.

1.3

described

detail

the

RSX-llD

Executive

MONITOR CONSOLE ROUTINES (MCR)

The monitor console routines (MCR) provide an interface between the
user and the system. MCR provides the user with complete task control
features.
The user issues MCR commands to request system programs
(e.g., FORTRAN for
task development)
and to schedule and execute
tasks.
From MCR, the user can obtain
system:

the

The time of day and date
A list of active tasks

1-3

following

information

about

the

INTRODUCTION

A list of partitions and common areas
A list of the physical
generated

devices

A list of the logical units
devices for a task

and

for

which

their

the

system

associated

was

physical

In addition, the user can log information about the system.
The MCR commands for the above functions are described in Chapter 5.
MCR also provides the user with the capability to initialize RSX-llD
file-structured
(Files-II)
volumes,
to mount and dismount Files-II
volumes, to establish user file directories (UFDs), and to establish
passwords.
(Files-II and UFDs are discussed in Section 3.2). These
and other MCR commands used for centralized control of the system,
including the capability to enter time and date and to control spooler
operation, are described in Chapter 6.

1.4

FORTRAN LANGUAGE AND OBJECT TIME SYSTEM

RSX-llD FORTRAN is an ANSI standard FORTRAN IV language accompanied by
an object time system (OTS). FORTRAN programs can be compiled into
object code, or they can be converted into assembly-language source
statements
that,
in
turn,
can
be
assembled
with
other
assembly-language modules.
The OTS is an object library of commonly used FORTRAN routines that
can be called by FORTRAN programs. The user selects the OTS library
that is appropriate for his applications.

1.5

MACRO ASSEMBLER

The RSX-llD MACRO assembler allows the user to take full advantage of
the PDP-II programming language, system directives, and the RSX-llD
file control services (FCS).
(See section 1.8.) During assembly,
MACRO detects errors and produces output indicating the type of errors
found, thus simplifying the process of locating program errors.

1.6

TASK BUILDER

The task builder creates loadable core images from assembled or
compiled tasks.
It links relocatable object files and resolves any
references to global symbols, common areas, and shared libraries. The
task builder also provides an overlay descriptor language to construct
task overlays. The overlay descriptor language simplifies the process
of dividing a
task into overlaid segments and specifying loading
methods.
The task builder provides switches that specify
certain
task
attributes.
Because switch information is specified during task
building, such information can be changed without reassembling or

1-4

INTRODUCTION
recompiling the task.

The switches indicate the following:

Whether the task can be checkpointed. Normally,
tasks that
are not time critical when a higher priority task is
requested are regarded as checkpointable
Whether the task can be aborted by
Executive directive

the

operator

Whether the task is multiuser
Whether the task is privileged
Whether the task uses the
available on PDP-ll/40)

floating

point

processor

(not

Whether the task is subject to accounting
Whether the task may be fixed in memory and other factors
that control the execution of the task and define its
attributes
The task builder stores the task on disk in a form that can be
dynamically loaded anywhere in the system's memory;
the task is not
restricted to operating in a fixed memory area.

1.7

UTILITY PROGRAMS

The R8X-llD utility programs described in the following sections
permit
file operations such as copying, editing,
transferring,
verifying, compressing, dumping, modifying, and creating libraries.

1.7.1

Peripheral Interchange Program (PIP)

PIP is used to copy files from one device to another, for example,
from disk to printer, to rename files, to list files, and to delete
files.

1.7.2

Editor (EDI)

EDI is used to enter source programs into the system and to modify
them as needed.
A large set of easy-to-use commands makes EDI an
effective program development tool.

1.7.3

File Transfer Program (FLX)

FLX performs the following file conversions:
From DOS-II to Files-II format
From Files-II to DOS-II format

1-5

INTRODUCTION
From RT-II to Files-II format
From Files-II to RT-II format
From DOS-II to DOS-II format
From RT-II to RT-II format
From Files-II to Files-II format
FLX also allows the user to:

1.7.4

List directories
volumes

cassettes,

RT-II

volumes,

DOS-II

Delete files from DOS-II and RT-II volumes

Initialize cassettes, RT-II volumes, or DOS-II volumes

Verification (VFY)

VFY checks the consistency and accuracy of system files on a Files-II
device (for example,' disk).
It also prints the number of available
blocks in a volume, locates files that could not otherwise be
accessed, and lists the names of files for the volume's index file.

1.7.5

Source Language Input Program (SLP)

SLP is a batch-oriented editing program that is
maintain source language files on disk.

1.7.6

used

create

and

File Compression (SQZ)

SQZ removes unnecessary spaces and tabs from MACRO source program
files.
Additionally,
the SQZ program removes comment lines. The
resultant file requires less storage space.

1.7.7

Dump Utility (DMP)

DMP enables the user to obtain a printout of files, in either ASCII or
octal format.

1.7.8

Librarian (LBR)

LBR provides the user with the capability to create
disk-resident libraries of object and source modules.

1-6

and

maintain

INTRODUCTION
1.7.9

ZAP Utility Program (ZAP)

The ZAP utility program provides a facility
modifying task image files and data files.
patches can be made to task image or data files
recreate the file.

1.8

for examining and
With ZAP, permanent
without having to

FILE CONTROL SERVICES

File control services (FCS) provide the user with record-oriented and
block-oriented file I/O and additional functions required for file
control, such as open, close, and delete operations.
At the FCS
level,
the user issues macro calls to specify desired file control
operations.
FCS supports both sequential and direct access files.
Sequential
access is device independent and can be used for both record-oriented
and Files-II structured devices. Direct access is used for Files-II
structured devices only. Data records can be either fixed length or
variable length.
When record I/O is used, a program
records in either of two ways:

can

gain

access

individual

By moving the data to a user-defined buffer (move mode) ,

By using FCS parameters to index into the desired
buffer and process the data there (locate mode) •

block

When block I/G is used, a program can gain access to an entire file
block. This file block is delivered to a user-specified buffer within
the user program. This allows the user to eliminate the space and
time overhead associated with record buffering. By opening the file
as either a single-user or a shared file, a task can indicate whether
other tasks can gain access to the file during its processing. Access
can also be restricted by assigning specified volume and file access
protection to a volume or file. See Section 3.2.8.

1.9

DEVICE HANDLER TASKS

In RSX-llD, support of PDP-II devices is provided by device handler
tasks which perform the necessary functions that enable physical I/G
operations.
Because device handlers are tasks within RSX-llD, 'the user does not
fill memory with handlers that are not required.
Infrequently-used
handlers can be loaded when needed by the user and then unloaded after
use.
In addition, because handlers are tasks, the user can write his own
handlers to service nonstandard devices. See the IAS/RSX-IID Guide to
Writing Device Handler Task.

1-7

INTRODUCTION
1.10

ON-LINE DEBUGGING TECHNIQUE

The on-line debugging technique (ODT) for RSX-IID is a system aid for
debugging programs that have been assembled or compiled and task
built. From the keyboard, the user interacts with ODT to achieve the
following results:
Print the contents of any
examination or alteration.

location

the

task

for

Run the entire program or any portion of it using
the
breakpoint feature to halt the program at specified points
Search the program for specific bit patterns
Search the
location

program

for

words

that

refer

specific

Calculate offsets for relative addresses
Fill a block of words or bytes with a designated value
A Trace capability is also provided to aid in the debugging of FORTRAN
and MACRO-II programs.

1.11

BATCH CAPABILITY

The RSX-IID batch facility provides for job execution in background
mode.
Each job can consist of control information and data.
Control
information includes such functions as requests to compile or assemble
tasks and
to execute them.
A variety of switches gives the user
desirable options.
The batch stream is read onto disk from a peripheral device,
for
example, a card reader. Once on the disk, the system examines the job
requests and schedules them.

1.12

SYSTEM GENERATION

The RSX-IID software system distributed to the user
is capable of
performing all system functions once it is built onto the system disk.
However, RSX-IID provides a system generation program that can be used
to tailor
the system to
the processing requirements of individual
installations.

1.13

TASK ACCOUNTING

RSX-IID accounting facilities enable the system manager
to determine
how executing tasks are using the system resources. Accounting
statistics provide the following information for each task:
The amount of computer memory used
The elapsed execution time

1-8

INTRODUCTION
Central processor time used
Peripheral device access count
A log of the I/O
Disk storage in use for individual disk areas.
Task accounting is described in detail in the RSX-IID System Manager's
Guide.

1.14

HARDWARE ERROR LOGGING

An error logging facility is included in RSX-IID to enable the system
manager to determine the status of the system hardware. Error logging
creates a file that contains a record of hardware errors occurring on
the central processing unit and peripheral devices.
The system
manager can request at any time, a summary of errors by device or a
list of all errors.
It is also possible to obtain a listing of errors
that occurred during a specified time span.

1.15

ON-LINE HARDWARE DIAGNOSTICS

The hardware error diagnostic handlers are a complete set of special
purpose handlers that enable the system manager to find and analyze
problems on peripheral devices. These handlers run in parallel with
other handlers on an active RSX-IID system.

1.16

MEMORY PARITY CHECKING

RSX-IID checks for the occurrence of parity errors in main memory and
in cache on the PDP-ll/70.
If a parity error occurs, the system
performs one of the following actions:
1.

If the parity error is detected in the Executive portion of
memory,
system
operation
halts
to
prevent
system
deterioration. An analytical dump of the system can then be
taken.
See the' description of the core dump analyzer (CDA)
in the RSX-IID System Manager's Guide.

If the parity error is in the user's memory area, the system
terminates the task,
indicating that fact in the task's
status information.

If the error occurred in the PDP-ll/70 cache,
the system
determines whether a user-specified limit for the number of
error allowed in one minute has been exceeded.
If it has
been exceeded, the cache group is turned off.

1-9

INTRODUCTION
NOTE
The task and memory locked down as a
result of a ma1n memory parity error
cannot be used until they are released
by means of the MEM MCR function.
Cache errors never result in the locking
of a task in memory.

1.17

SYSTEM TEST PACKAGE

The system test package is designed to systematically test the PDP-II
software while it is running RSX-IID. The hardware is also tested by
a subset of the test tasks.

1-10

CHAPTER 2
FUNDAMENTAL RSX-llD CONCEPTS

RSX-llD schedules tasks to execute in defined areas of memory called
partitions.
The concepts of partitions, tasks, and scheduling are
essential to an understanding of the capabilities and flexibility of
the RSX-llD system.

2.1

PARTITIONS

Partitions contain executing tasks and tasks that are permanently
resident
(fixed) in memory, regardless of whether they are executing.
When an RSX-llD system is generated, the system manager defines the
size and number of partitions to suit the hardware configuration and
processing needs. All memory not required for the RSX-llD Executive
and system subroutines is available for partitions.
The system
manager specifies the name, size, and base address of each partition
and also indicates whether it is user-controlled or system-controlled.
Unless a task is fixed in memory, it is automatically removed from the
partition upon termination. A fixed task can be unfixed only when it
is quiescent.

2.1.1

User-Controlled Partitions

A user-controlled partition can contain only one task at a
time.
Because the user has complete control over activity in such a
partition, it provides an ideal environment
for
a
real-time
application. The exact partition size can be specified for tasks that
are normally resident, permitting maximum use of memory.

2.1.2

System-Controlled Partitions

A system-controlled partition, one in which the RSX-llD Executive
handles task execution, can contain one or more tasks at a time. The
system controls the placement of tasks in memory.
The
only
restriction is that a task cannot be loaded into a partition until
there is enough contiguous memory available within the partition.
The system-controlled partitions are intended for
the execution of
user
tasks that do not necessarily have real-time requirements, MCR
functions, and other system-related tasks
(for example,
the I/O
system) .
See Figure 2-1 for an example of memory divided into
user-controlled and system-controlled partitions.

2-1

FUNDAMENTAL RSX-llD CONCEPTS
System controlled partitions can operate on either a priority basis or
on a time-scheduled basis as defined by the system manager during
system generation.
The sequence of events that
occur
in
a
priority-oriented partition is described in the RSX-llD Executive
Reference Manual. The algorithm for the time-scheduled partition is
descrIbed In the RSX-llD System Manager's Guide.
Because of the large overhead required, tasks are not moved in memory
during execution to make room for additional tasks.
If sufficient
memory is available within a partition, however, additional tasks can
be loaded.

RSX-llD
EXECUTIVE
AND
SYSTEM SUBROUTINES
Teletype Handler

User-Controlled Partition

Disk Handler

User-Controlled Partition

Mcr Functions
System-Controlled Partition
MCR Dispatcher
User Task
Shared Areas

System-Controlled Partition

User Task
User's
Memory
Area

User Task
User-Controlled
Partition
Running One Task

User-Controlled Partition

Figure 2-1
Physical Memory Divided Into Partitions

2-2

FUNDAMENTAL RSX-IID CONCEPTS
2.1.3

Memory Protection

The memory area allocated to a task is accessed via memory management
hardware.
A task's memory area is protected from other tasks
executing in the system; and the tasks can access only those areas
allocated to it. Access rights, read or write, are also controlled by
the hardware.
Those portions of memory that are used by one or more tasks, such as
shared libraries and common areas, also are protected.
Shared
libraries can be used by many tasks.
For this reason,
they are
re-entrant
(read only).
Common areas can be either pure or impure
(read/write); and the memory management hardware controls access.
Care must be taken when a common area is shared between tasks with
read/write access.
In this case, the burden is on the programmer to
maintain synchrony.

2.2

TASKS

A task is the basic executable unit in RSX-IID. Once a source task
has been assembled or compiled, task built to make it relocatable, and
installed into the system, it is referred to as a task. One or more
source programs can be combined during assembly/compilation or task
building to form one task.
When a task is installed in RSX-llD, the system establishes an entry
in an in-memory directory called the system task ~irectory (STD).
This entry holds information concerning the task's Image on disk.
When a request for
task execution is made, the system uses this
pointer to load the task image into memory and start its execution.
Tasks can also be fixed in memory, to allow faster task initiation and
rescheduling by the system. Each task can execute independently or in
conjunction with other tasks in its own or other partitions. Such
task interaction is described in Section 2.2.3.
Tasks can be
requested for execution in any of the following ways:
· By a user at a terminal
· By an executing task
· By a request in a batch stream
· Through a time-dependent schedule

2.2.1

Overlays

RSX-IID supports an overlay development function that can be used to
reduce the amount of memory required for a program. For example, a
task can be divided into several segments: a main segment that must
be resident throughout task execution and other segments that are used
less frequently, which are loaded into memory only when needed.
Segments can control program operation by calling other segments. The
called segments constitute the overlays. An overlay is brought into
memory to replace resident code that is no longer needed.
The main
segment also provides a storage area for information that is to be
passed from overlay to overlay.
The memory requirement for the overlay area is equivalent to the size
of the largest overlay. The memory requirement for the task is the
area of the main segment plus the area required for
the largest
overlay.
2-3

FUNDAMENTAL RSX-llD CONCEPTS

As an example of overlaying, consider the program whose task structure
is depicted in Figure 2-2. The program consists of five segments: a
main segment, and segments A, B, C, and D.
Segments C and D can
overlay each other.
Within segments C and D, certain portions can
also be overlaid. Figure 2-2 illustrates the space required for
the
program on disk and the memory area required for the program's
execution.

ON DISK

IN MEMORY

MAIN SEGMENT

Space for C and Cl,
Cl and C~ OR Space
for D, Dl and 02,
OR 01, D2, and D3

C2
D
Dl
D2
03

Figure 2-2
Overlay Structure

2-4

FUNDAMENTAL RSX-IID CONCEPTS
2.2.2

Multiuser Tasks

A multiuser task can be requested for execution by more than one user.
For
example,
terminals
5,
7, and 8 can run the same task
independently. Both system tasks and user-written tasks can be built
as multiuser tasks.
In many cases, multiuser tasks are divided into pure and impure areas.
The
term pure area indicates that the area remains unchanged during
task execution (has read-only access). The term impure area indicates
that the area is modified during execution (has read/write access) .
When a task consisting of a pure and an impure area is run by more
than one user, only one copy of the pure area resides in memory.
One
copy of the impure area is required for each user.
Figure 2-3 depicts
a
partition containing multiuser
tasks.
Therefore, dividing a
multiuser task into pure an9 impure areas results in conservation of
memory for the executing tasks.

2.2.3

Task Interaction

Because many tasks can execute at the same time, four
techniques for
task interaction are provided:
global event flags, a common area,
shared access to data files, and SEND/RECEIVE Executive directives.
RSX-IID provides a set of 32 global event flags that can be set and
tested by all tasks in the system. Using the global flags, a task can
wait for another task to perform a designated function before resuming
execution.
The waiting task tests a specified event flag;
when the
executing task has performed the designated function,
it sets the
flag,
thus allowing
the waiting task to resume. The use of global
event flags should be coordinated by the system manager.
Figure 2-4
depicts the use of event flags.
Common areas are read-write shareable global areas (see Section 2.7)
and are created and installed in the same way as tasks.
Figure 2-5
shows the use of the common area for
intertask communication.
Many
tasks can read from or write into common areas.
Thus, a task can read
information from an I/O device, store it in a common area, and set a
global event flag to notify another task that data is available for it
in that common area.
Shared data files provide the same function as common areas except
that they are maintained on a Files-II volume rather than in main
memory.
SEND/RECEIVE Executive directives allow tasks to transmit
the system node pool as the data storage medium.

2-5

data

using

FUNDAMENTAL RSX-llD CONCEPTS

TASK A PURE AREA
Terminal 5 -----

TASK A IMPURE AREA
OTHER ESECUTING TASKS

Terminal 7

•

TASK A IMPURE AREA

Terminal 8

•

TASK A IMPURE AREA

Partition

Figure 2-3
Multiuser Tasks

USER TASK A
I

I USER TASK B

Global
Event Flags

Waits for flag 35 to be set

Sets flag 35 after specified event

Figure 2-4
Use of Event Flags for Intertask Communication

2-6

FUNDAMENTAL RSX-IlD CONCEPTS

RSX-IID EXECUTIVE
Shared Libraries

Puts Data
in the
Common Area

User Task A

User Task B

Removes Data
from the
Common Area

Common Area

Figure 2-5
Use of the Common Area for Intertask Communication

2.3

SCHEDULING TASK EXECUTION

Under RSX-lID, a task can be requested for immediate execution or
it
can be scheduled for execution at a later time. The scheduling
request can originate from the user or from another executing task.
In a priority-oriented partition, scheduling always depends on task
priority (1 through 250; where 250 is the highest or most urgent
priority)
and memory availability within the desired partition.
In a
time-scheduled partition, scheduling always depends on the
time
scheduler, which give each task in turn an opportunity to execute.
In addition to the scheduling performed automatically in a partition
by the Executive,
the user can schedule tasks based on any of the
following factors:

2-7

FUNDAMENTAL RSX-IID CONCEPTS
· A request to execute the task in a number of minutes, seconds, or
clock ticks from the issuance of the request, for example, in 30
minutes, and optionally, to reschedule
the task at specified
intervals.
· A request to execute the task at a certain time of day and at
specified intervals thereafter: for example, at 10:00 p.m. and
every ten minutes thereafter.
· Synchronization with the next clock tick, second, minute, or
hour, and optionally, to resche6ule the task at specified
intervals.
When a task of a higher priority than the currently running task is
scheduled for execution in a priority-oriented partition, the task
currently in memory is checkpointed and replaced by the higher
priority task if necessary. See Section 2.4.
Both the terminal user and tasks executing within the system can
affect the order of task execution.
If necessary, the user can cancel
the scheduled request and then reschedule tasks
at
specified
intervals.

2.4

CHECKPOINTING

Checkpointing is the option of suspending the operation of one task to
allow the running of another task. The suspended task is placed on a
user-designated checkpoint disk device in a form that allows the
system to reload and restart the task when memory is again available.
The ta~k is ~estarted from the interruption point, not from
the
beginning.
In a system-controlled, priority-oriented partition, checkpointing
occurs to allow the running of a task with a higher priority.
In a
system-controlled, time-scheduled partition, checkpointing can occur
when the currently executing task exceeds its time limit.
At task build time the user must designate those tasks that cannot be
checkpointed.
For
example,
checkpointing
frequently
is not
appropriate
for
real-time
applications.
Checkpointing,
a
roll-out/roll-in operation, can be used for both system-controlled and
user-controlled partitions.
NOTE
A task that can be fixed
cannot be checkpointed.

2.5

memory

DEVICE INDEPENDENCE

One of the major factors in determining whether a program can run is
resource availability,
that is, whether the necessary peripheral
devices are free for use. To allow greater flexibility in the area of
resource availability, RSX-IID provides device independence. This
feature permits a programmer to code a program with input and output
assigned to logical units rather than to specific physical devices.
Before scheduling the task for execution, the user can assign physical
devices to the logical units specified in the task's I/O.
If the task
uses the default device assignments, that is, devices that are readily
available for use, the user need not assign devices.
2-8

FUNDAMENTAL RSX-llD CONCEPTS
2.6

PRINT FILE SPOOLING, DESPOOLING, AND INPUT SPOOLING

RSX-llD provides three types of file spooling:
1.

Automatic output spooling to disk,

Automatic despooling of disk files queued for printing,

Automatic input spooling from a card reader to disk.

Output spooling eliminates program contention for
line printers,
teleprinters,
and other serial output devices.
Because programs do
not have to wait to use a serial device, higher system throughput
is
achieved.
The need to wait for a particular device is removed by temporarily
redirecting
the output intended for the serial device to a disk file.
This temporary redirection is defined as automatic output spooling.
The files redirected
to the disk are later produced on the original
device.
This process is defined as despooling.
RSX-llD provides two levels of automatic output spooling/despooling.
On
the simplest level, the automatic output spooler can queue files
for the single device despooler which prints them one at a time on a
first-in/first-out basis. Only one output device is used at a time.
On a more sophisticated level, the automatic output spooler and
the
terminal user both can queue files for printing.
In this case, the
multiple device despooler is used.
It sends queued files for printing
on a priority basis.
Up to
28 devices can be used for despooled
output simultaneously.
The input spooler eliminates program contention for
the card reader
and serves as a batch job input device. Card files are read onto a
disk and placed under a specified UFD (see Section 3.2.5).
NOTE
Spooling can be enabled and
only by a privileged user.

2.7

disabled

SHAREABLE GLOBAL AREAS

Shareable global areas
(SGAs)
consist of shareable
task
image
libraries and common areas.
SGAs are created by the task builder, and
are stored on disk.
Shareable task image libraries provide a storage area for
subroutines
that
perform often-needed functions,
for
example,
file control
services (FCS)
routines.
By installing such subroutines
in
the
system, the user avoids their duplication into each task that requires
them.
The one copy stored in the library can be used by all
tasks
without requiring additional physical space in the task's area of
memory, although the task's address space is used.
Shareable libraries are dynamically loaded into memory when a
task
that uses
them becomes active and are automatically released from
memory when they are no longer required by any task running
in
the
system.

2-9

FUNDAMENTAL RSX-IID CONCEPTS
Common areas are normally used to pass shared data from one executing
task to another (see Section 2.2.3) (for example, commonly-used tables
of reference data).
Like shared libraries,
they are dynamically
loaded when required, but are written back to disk when released on
the assumption that the data has been modified.
Like
tasks, SGAs are files on disk.
Therefore, all
the file
protection conventions described in Section 3.2 apply.
In addition,
there is a set of access rights assignable to the code and data of
SGAs. When a task binds to an SGA, the requested access is specified.
When the SGA is installed, the access permitted to binding tasks is
specified. Finally, on installation of the task, the access requested
by the task is validated against that permitted by the SGA as
installed.
NOTE
SGAs can be installed
only
privileged user, usually,
the
manager.

by
a
system

Five SEND/RECEIVE Executive directives provide for
the transfer of
data blocks of up to 255 words from one task to another. The
recipient task need not be in memory at the time of the transfer. The
data blocks will be queued for
the attention of the task when it
returns to memory_ SEND/RECEIVE Executive directives are described in
the RSX-IID Executive Reference Manual. Their use is illustrated in
Figure 2-6.

RSX-llD Executive

Shared Libraries

User Task A

IReceiving block I

!+--

User Task B

I Sending block I
I

Figure 2-6
Use of SEND/RECEIVE Directive

2-10

CHAPTER 3
RSX-llD CONVENTIONS

To simplify operations, RSX-llD
respect to the following items:

observes

certain

conventions

with

To ease the transition from other DEC systems to RSX-llD, many of
conventions used by other DEC systems are followed by RSX-llD.

the

Peripheral devices
Files
Filename strings
Indirect files
Terminal control

3.1

DEVICE-RELATED CONVENTIONS

All peripheral devices are referred to using a 2-letter name and a lor 2-digit unit number followed by a colon (for example, DKO: and
TT12:). If the unit number is omitted, the system uses unit 0 by
default:
for example LP:
indicates line printer o. Peripheral
devices can be referred to by mnemonics or by pseudo-device names.
Pseudo-devices are linked by the system manager to regular device
mnemonics. Logical unit numbers of each task are in turn asso~iated
with
peripheral
devices
to
provide another level of device
independence. Table 3-1 lists the mnemonics of devices supported by
RSX-IID.

3.1.1

Pseudo-Devices

In addition to supporting actual physical devices, RSX-IID provides
seven pseudo-devices:
system disk
(SY),
terminal interface (TI),
console input (eI), console output (CO), console log
(CL), message
output (MO) , batch
(BP), and spooling output (SP). The linking of
pseudo-devices to physical devices permits a system manager
to
dynamically determine the physical devices that will send or receive
system information.

3-1

RSX-IID CONVENTIONS
Table 3-1
RSX-IID Device Mnemonics
NAME
TTn:

3.1.2

DEVICE
(0

- 63 )

User Terminal

DKn:
DFn:
DPn:
DSn:
DBn:
MTn:
MMn:
DTn:

RK05 Disk
RFll Disk
RP03 Disk
RS03 or RS04 Disk
RP04 Disk
TUIO Magnetic Tape
TU16 Magnetic Tape
DEC tape

PPn:
PRn:

Paper Tape Punch
Paper Tape Reader

LP:

Line Printer

CR:
CT:
AFn:

Card Reader
Casse t te Tape
AFCll Analog Input

LSn:

LPS AID Converter

ADn:

ADOI AID Converter

UDn:

UDCll
Universal Digital Controller

SY:

System Disk

TI:

Individual Terminal Interface

CI:

Console Input

co:

Console Output

CL:

Console Log

MO:

Message Output

SP:

Spooling Output

BP:

Batch pseudo-device

System Device (SY)

The system device is the disk
(OK, DP, or DB)
that contains the
operating system currently loaded into memory. The term SY indicates
the device on which the system disk is mounted.

3-2

RSX-llD CONVENTIONS
3.1.3

Terminal Interface (TI)

Terminal interface (TI) is the logical device specification for a
terminal.
Each terminal has a unique TI. The system uses TI to
determine which terminal requested execution of a specific task.
For
identification purposes each task is assigned the TI of the requesting
terminal. When more than one user has activated the same task,
the
task name and TI assignment provide the system with a means of
determining which task is associated with a particular terminal.

3.1.4

Console Input (eI), Console Output (CO), and Console Log (eL)

Pseudo-device CI is used by the system manager to communicate with the
system.
Pseudo-device CO is used by the system to communicate with the
manager.
Pseudo-device CL is used for the listing of files;
directed to the printer.

3.1.5

system

normally output is

Message Output (MO)

The pseudo-device MO is used to provide detailed error messages. When
an error occurs,
the system prints a message; however, if MO is
loaded, more explicit information is also presented. The advantage of
treating message output as a pseudo-device is that the MO device
handler needs to be resident in memory only when additional messages
would be helpful, for example, during program development. MO should
be loaded when Utility programs are in use, because they depend
critically on it for error message generation.

3.1.6

Spooling Output (SP)

Pseudo-device SP is used for all spooled output files.
Use of SP
enables the spooled output to be temporarily written to any Files-II
formatted device.

3.1.7

Batch Pseudo Device (BP)

Pseudo-device BP is used in place of TI to execute batch jobs. Use of
BP permits the queue manager to identify those output files generated
by tasks initiated by batch. These files are concatenated by the
queue manager and queued for output once the batch job completes.
Batch automatically red~rects the BP device to the originating TI
terminal.
It temporarily sets both the originating TI terminal and
the SP pseudo-device to spooling status.
The TI terminal remains
spooled for
the duration of the execution of the batch job. The
terminal reverts to its spooled or non-spooled state at conclusion of
the batch job.

3-3

RSX-llD CONVENTIONS
3.1.8

Logical Unit Numbers (LUNs)

Logical unit numbers (LUNs) provide the mechanism for programs to
maintain device independence.
The logical unit numbers used in a
program can be assigned by means of device mnemonics to any available
peripheral device
that performs the desired function.
LUNs can be
assigned by the programmer at assembly time or at task build time, or
by the task at run time. Because the system provides default LUN
assignments, it is not always necessary to assign a LUN to a
task.
Default LUN assignments are listed in Table 3-2.
Table 3-2
Default LUN Assignments

3.2

LUN

ASSIGNMENT

1
2
3
4
5
6

SY:
SY:
SY:
SY:
TI:
CL:

SUPPORTED FILE STRUCTURES

RSX-llD provides support for two file structures: Files-II for disk
and DECtape volumes, and ANSI Standard Level 3 for single-volume or
multivolume magnetic tape.
Because Files-II is an integral part of
RSX-ll and its operation, it is discussed in detail in this section.
For an in-depth description, see the IAS/RSX-ll I/O Operations
Reference Manual.
ANSI Standard Level 3 conforms to
the proposed revision of the
following American National Standard document, dated June 19, 1974:
Magnetic Tape Labels
And File Structure
For Information Interchange
Order No.

ANSI X3.27-l969

ANSI Standard Level 3 is also discussed in detail
I/O Operations Reference Manual.

3.2.1

the

IAS/RSX-ll

Files-II

Files-II is a general purpose file control system that provides a
facility for the dynamic creation, extension, and deletion of files on
disk or DEC tape.
Designed into Files-II is a scheme for volume and file protection
which allows the owner of a volume or file to deny access to other
users in the system. This scheme for volume and file protection

3-4

RSX-IID CONVENTIONS
provides the key to system protection, in that only users with access
privileges to the system device are allowed access to the system.
Methods for gaining system access, and volume and file protection are
explained in later sections.

3.2.2

Files-II Volumes

A Files-II volume is a collection of files which reside on a single
disk or DECtape.
The system can directly address each file on the
volume by means of file pointers which reside in the volume's
directory files.
Each Files-II volume has two kinds of directory files that are used
for file management:
the Master File Directory (MFD) file, and the
User File Directory (UFD) files.
The Master File Directory (MFD) file is automatically generated by the
file system when a volume is initialized as a Files-II volume, and is
used to store pointers to all of the User File Directory (UFO)
files
on the volume. MFDs are described in greater detail in Section 3.2.4.
User File Directory (UFD) files are created as needed. They are used
to store pointers to all of the files belonging to, or associated
with, the user whose account number (UIC)
corresponds with the UFD
file name.
UIC is described in Section 3.2.7. UFDs are described in
greater detail in Section 3.2.5.

3.2.3

File Format

All Files-II files, whether MFD, UFD, or user file, have the same
basic format
(see Figure 3-1 for illustration of a sample Files-II
file structure). All have a file header area, and one or more data
area(s).
The file header area contains all the pertinent information required
by the file system to process the file.
For the purposes of this
introduction, the user need be familiar with only the following
fields:

File Owner Field
The file owner field contains the account number
(UIC)
of
the user who created the file.
UICs are described in
Section 3.2.7.
File Name Field
The file name field contains the name assigned to the file
when it was created. File names can be a maximum of nine
alphanumeric characters long, and are discussed in Section
3.3.
File Type Field
The file type field contains the mnemonic that identifies
the file by its functionality:
for example, FTN defines a
FORTRAN source file.
File types are discussed in Section
3.3.

3-5

RSX-IID CONVENTIONS
Version Number Field
The version number field identifies the particular version
or generation of the file. Version numbers are discussed in
Section 3.3.
File Protection Field
The file
describes
describes
Ex tend,
discussed

protection field contains a 16-bit code
that
who is allowed access to the file.
It also
the type of access allowed
(i.e. , Read, Wr i te,
or
Dele te) .
Volume and file protection are
in Sec tion 3.2.8.

Data Pointer Field
The data pointer field describes the physical allocation of
the file on the volume. Each data area pointer describes a
physically contiguous portion of the file. See Figure 3-2.
By establishing pointers to blocked data in the files header area, as
opposed to storing the data immediately following the files header,
the system accomplishes two things:
(1) All files on the volume have
the same structural format, regardless of functionality;
(2) All
fragmented or noncontiguous areas of the volume can be put to optimum
use;
that is, a file can be expanded by merely attaching another
pointer to a blocked data area to its file header.
Users should always address data in a file-relative manner.
The
translation of file-relative addresses into physical addresses is
performed by the file system and is completely transparent to the
user.

3-6

RSX-IID CONVENTIONS

FILE HEADER AREA
FILE OWNER FIELD (UIC)
FILE NAME FIELD
(from 1-9 alphanumeric chars.)
FILE TYPE FIELD
VERSION NUMBER FIELD
FILE PROTECTION FIELD
DATA POINTER FIELD(s)
r--

DATA AREA A POINTER
DATA AREA B POINTER

(

DATA AREA N POINTER

DATA AREA B

DATA AREA A

Figure 3-1
Sample Files-II File Structure

3.2.4

Master File Directory

The Master File Directory (MFD) is used by the file system to locate
requested UFOs.
The MFD of the system device serves a dual purpose:
it aids the file system to locate UFOs on that volume, and it is used
by the operating system to identify users logging onto the system.

3-7

RSX-IID CONVENTIONS
Under RSX-IID, only users with UICs (account numbers) that correspond
to established UFD file names listed in the MFD on the system volume
are allowed access to the system.
The Master File Directory (MFD) is automatically generated when the
volume is initialized as a Files-II volume. Files-II volumes can be
initialized only by the system manager or another privileged user.
See Section 6.10.
Once the MFD file is established, the system manager or privileged
user can begin establishing UFD files. For each UFD file created, its
file name and location are recorded in the MFD file.

3.2.5

User File Directory

The User File Directory (UFD) files are used by the file system to
locate user files that are associated with or owned by the UFD's
owner.
UFO files are generated, as needed, by the system manager or another
privileged user.
See Section 6.24. When a user file is created, a
pointer to the file's header area is established in the owner's UFO.
The protection attributes assigned to the UFO establish the access
rights to the files it points to. That is, a user whose access rights
are not consistent with the protection attributes assigned to the UFO
is not allowed access to any of the files pointed to.
See Section
3.2.8.

3.2.6

File Ownership

File ownership is determined by the UIC stored in the file owner field
of the file header.
The user whose account number (UIC) exactly
matches the UIC stored in the file owner field is considered, by the
system, to be the file's owner.

3.2.7

User Identification Code

User Identification Codes (UICs) are unique account numbers assigned
to each user by the system manager. For a UIC to be valid, the system
manager or privileged user must have first created a corresponding UFO
on the system device.
UICs perform the following functions:
1.

Identify the user as one
system. See Section 5.8.

Identify the user as a privileged or nonprivileged user.
A
privileged user is assigned a UIC with a group code of 10
octal or less.

Identify the user's access privileges.

Establish the user's default UFD.

3-8

with

authorized

access

See Section 3.2.8.

See section 3.3.1.

the

RSX-llD CONVENTIONS
NOTE
Under RSX-llD, tasks are normally run
using
the UIC under which the user
logged onto the
system.
See
the
discussion of the RUN command in Chapter
6 for exceptions to this rule.
Whenever a UIC specification is required, it is
brackets and specified in the following format:

always

enclosed

[ggg,mmm]
where:
ggg

is an octal
representing
number.

ranging
from I
number
to
377
user's group or department
the

mmm

is an octal number
ranging from I
to
377
representing
the user's unique
identification
within the group or department.

Example
[200,200]

3.2.8

Volume And File Protection

Files-II provides the user with a multilevel
scheme for
protecting
volumes and files against unauthorized access.
This is accomplished
by allowing the user to specify protection attributes for
the entire
volume,
as well as for each file within the volume regardless of the
file's hierarchy or functionality.
Four types of actions can be permitted on a
file;
read, write,
extend, and delete.
Tasks that are allowed to perform any combination
of these actions are also divided into four categories:
System - This category comprises all tasks that run under a
system account number.
System account numbers (UICs)
are those having a group number of 10 octal or less;
i.e., [2,200].
Owner

- This category comprises all tasks that run under a
UIC that matches
the Ule in the file's file owner
field.

Group

- This category comprises all tasks that run under a
UIC whose group number matches the group number of
the UIC in the file owner field of
the file being
accessed.

World

- Any task not
included
described above.

the

three

directory

containing

the

desired

= a means of distinguishing among various forms of
the same file.
For example, a source FORTRAN file
might be named COMP.FTN, while the object file
associated with that program might be called
COMP.OBJ. File types are discussed in Section
3.3.2.
The file type and version are always
separated by a semicolon.

jversion

an octal number used to differentiate
among
versions of a file.
For example, when a file is
first entered using the Editor, it is assigned a
version number of 1. If the file is subsequently
opened for editing, the Editor keeps the original
file for backup and creates a new file with the
same filename and type, but with a version number
of 2.
Version numbers can range from 1 to 77777
octal.

/switch

is usually an optional qualifier.
Switches are
normally used either to direct the execution of a
task, or to qualify an input parameter.

Defaults in File Specifiers

If any of the elements of the filename string, except the filename, is
omitted, the system uses a default value.
A task can establish
defaults for a file. When a
task does not specify defaults,
the
defaults listed in Table 3-3 apply.

3-15

RSX-IID CONVENTIONS
Table 3-3
Filename Specifier Defaults
STRING ELEMENT
dev:

SYSTEM DEFAULT
If omitted in the first or only file specifier, SY
is assumed.
If omitted in the
second
through
n
file
specifiers, the device, specified or default, for
the previous file specifier is used.

[ufd]

If omitted in the first or only file specifier,
the UFD which corresponds to the UIC under which
the task is running is used.
If omitted in the
second
through
n
file
specifiers, the UFD, specified or default, for the
previous file specifier is used.

filename

No default -- must be specified either explicitly
or implicitly using an asterisk as described in
Section 3.3.3, except in certain PIP and FLX
strings.

. type

A meaningful file type (e.g., if a list file is
created, the system assigns it a file type of
.LST). See Section 3.3.2 for a list of default
file types.

;version

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

3.3.2

RSX-IID File Types

RSX-IID has a defined set of file types that the system uses when the
type is omitted from a filename string. While the user can assign his
own file types, the file types presented in Table 3-4 are easy to use.
File types can be defaulted in most commands. For example, if the
FORTRAN compiler is given the source file XYZ to compile, it
automatically searches for filename and type XYZ.FTN.

3-16

RSX-llD CONVENTIONS
Table 3-4
RSX-llD File Specifier Defaults
FILE TYPE

MEANING

BIS

A Batch input stream

CMD

A file containing a list of commands to
program (i.e., an indirect file)

DAT

A data file (as opposed to a program file)

DIR

A directory file (e.g., a UFD directory)

EXE

A Batch execute file

FOR

A Batch FORTRAN file

FTN

A FORTRAN language source program

LIB

A Batch Library file

LIS

A Batch listing stream

LST

A file in print-image format

MAC

A MACRO assembly-language source program

MAP

A file associated with Task Builder output

MLB

A macro library file

OBJ

An object program (output from MACRO or FORTRAN)

ODL

An overlay file

OLB

An object library file

SAV

An RSX-l1D system image file, or a file
by the EDI utility program

SML

A System Macro Library file

SOB

A Batch concatenated object file

SPR

A spooled output file

SRT

A Sort work file

STB

A symbol table file

TMP

A temporary file

TSK

A file that has been task built

3-17

system

generated

RSX-IID CONVENTIONS
3.3.3

Asterisk Conventions (wildcards)

In addition to relying on defaults in the filename string,
the user
also can place asterisks (*) in the string to indicate a particular
element of the string that is to be ignored (wildcard).
By ignoring
the content of elements within a string, the user can affect more than
one file at a
time.
For example,
to delete three files named
PROG.MACil,
PROG.OGJil,
and PROG.TSKil,
the following wildcard
specification can be used rather than three explicit delete requests.

PIP)PROG.*il/DE
The four characters, PIP), printed by the syst:m as a prompting
sequence,
indicate that the PIP utility is runnIng. PIP is used to
delete the files. The rest of the command is typed by the user.
If the file PROG exists with other version numbers (e.g., PROG.MACi2),
they are not affected by the delete request.
Not all system programs accept wildcards:
conjunction with commands to PIP.

their

primary

use

An asterisk can be placed in any portion of the filename string except
the device indicator, which must always be specified or defaulted to
SY.

3.3.4

Examples of Command Strings

In the following examples, the first three letters and the right angle
bracket (»
are printed by the system. The remaining characters are
typed by the user.
MAC)DKO: [200,200]CRGPT=DKO: [200,200]CRGPT
A request to assemble CRGPT.MAC and call the object program CRGPT.OBJ.
Both files are on DKO under [200,200].
PIP)ABCD.MAC=ABBD.MAC/RE
A request to rename (/RE) file ABBD.MAC to ABCD.MAC.
on device SY under the default UFD.

Both

files

are

filename

string

PIP)SBG.OBJ:S/DE
A request to delete file SBG.OBJ:S. The
omitted because it is not applicable.

output

TKB)CRGPT=CRGPT
A request to task build the object
named CRGPT.TSK because TSK is
Builder.

file CRGPT.OBJ.
The output is
the default file type for the Task

PIP)CRGPT.*i*/DE
A request to delete all files with the name CRGPT, regardless of
type or version.

3-18

file

RSX-llD CONVENTIONS
3.4

INDIRECT FILES

An indirect file is a sequential file containing a list of cQmmands.
The commands contained in the file are task specific, that is, they
can be interpreted only by a specific task such as MACRO-II or the
Task Builder.
Rather than repeatedly typing commonly used sequences of commands, the
user can type the sequence once and store it on a file. To execute
the sequence, the user types an at sign (@)
and then the filename.
The affected task (for example, MACRO-II or Task Builder) locates the
indirect file and executes the commands contained therein.
For
example,
MCR)MAC @CMDFIL.CMD
In response to the command, MACRO-II accesses the file CMDFIL.CMD
all of its commands.

for

NOTE

3.5

An indirect file may contain any command
that is interpretable by the task to
which it is directed, but no others.

Indirect files can be created using the
Editor utility program, as described in
the RSX-llD Utility Programs Procedures
Manual.

Not all system programs allow the use of
indirect command file specifiers. The
user
should
carefully
read
the
appropriate system program documentation
before atte~pting to use the programs.

TERMINAL CONVENTIONS

Several special keyboard characters that cause specific functions to
be performed are recognized by the system.
These functions are
described in Table 3-5. Most of them require the holding down of the
CTRL (control) key while a second character is pressed; e.g., CTRL C.

3-19

RSX-IID CONVENTIONS
Table 3-5
Terminal Control Conventions
KEYS

FUNCTION

CTRL C

Causes MCR to be activated.
prompt characters, MCR).

The

system

prints

the

NOTE
Typing CTRL C does not affect the
of any tasks currently running.

execution

CTRL Z

Logical end-of-file;
when typed in response to a
prompt from most system programs, causes that program
to exit.

RETURN

Terminates the current line and causes the system to
print the prompt for the next command. All lines are
terminated using RETURN unless otherwise noted in the
documentation.

RUBOUT

Causes the most recently typed character to be deleted
from the command string. RUBOUT echoes as a backslash
(\). Successive typing of RUBOUT causes the most
recently typed characters to be deleted. One character
is deleted for each successive pressing of RUBOUT.

ALT

Terminates MCR.
Normally used when requesting
a
program
(user or system) that is to interact with the
operator after the command is executed
(e.g., RUN
..• MAC (ALT».
NOTE
On some keyboards, the
"ESC".

ALT

key

labeled

CTRL I

Causes a horizontal tab. Tab stops are set, by the
software, at every eighth character position (e.g., 9,
17,25,33).

CTRL K

Causes a vertical tab of one line.

CTRL L

Causes a form feed to the top of the next page.

3-20

RSX-llD CONVENTIONS
Table 3-5 (Cont.)
Terminal Control Conventions
KEYS

FUNCTION

CTRL 0

Interrupts system output to the
terminal.
Successive
pressings of CTRL 0 cause output to start and stop.
For example, if a directory listing on the terminal
is
requested and the first few lines present the desired
information, CTRL 0 can suppress the printing of the
rest of the directory.
(Large TTY Handler only)*

CTRL R

Causes the system to print the current terminal line.
When errors make the line difficult to read, pressing
CTRL R produces a clear copy.
Input can continue on
the newly-printed line (large TTY handler only).

CTRL U

Cancels the current input line. The prompt (e.g., MCR>
or PIP»
is not printed on the next line, but the
system is ready for the typing of a new command.

CTRL X

Causes a user-written program named TTYNnn to execute;
nn is the two digit unit number of the terminal with
which the program is to interact during execution.

CTRL S
and
CTRL Q

These two keys correspond to XON and XOFF respectively.
(Pressing CTRL Q (XOFF) stops output to the terminal
until CTRL S (XON) is pressed.
Unlike CTRL 0,
the
XON/XOFF function stops and starts output without any
loss of characters. The silo of the VT05 terminal
generates XON/XOFF automatically.
(Large TTY Handler
only)*

*The system manager
is responsible for
installing the large TTY
handler.
Installation usually is performed during system generation.

3-21

RSX-11D CONVENTIONS
3.6

CARD READER CONTROL CONVENTIONS

The card reader handler recognizes three control characters.
The
control character code identifies the alphanumeric format for either
029 card codes or 026 card codes, or it indicates end-of-file.
Table
3-6 defines the control characters.
Control character codes appear in column 1 of a multipunch control
card;
however, they are not transferred to the user's buffer nor
included in the word count.
Table 3-6
Card Reader Control Conventions
CARD COLUMN 1
MULTIPUNCH

MEANING

12-11-0-1-6-7-8-9

End-of-file ASCII mode*

12-0-2-4-6-8

029 mode

12-2-4-g

026 mode

NOTE
Control Cards must
streams.

*End-of-file binary
columns 1 to 8.

mode

enclose

requires

3-22

the

input

same

data

multipunches

card

CHAPTER 4
USER/SYSTEM INTERFACE

4.1

MONITOR CONSOLE ROUTINE

The Monitor Console Routine (MCR) is the terminal interface between
the user terminal and the RSX-llD operating system. This interface is
accomplished by means of simple MCR System Commands.
MCR's system command
following functions.

repertoire

enables

the

user

perform

the

Gain access to the system
Initiate and terminate execution of user/system programs
Adjust, modify, and control the system environment

4.1.1

MCR Organization

MCR services are organized internally as a re-entrant dispatcher
task
and a set of independent system command tasks. The individual command
tasks are called by the dispatcher task as needed and are released
automatically after execution.
The dispatcher portion of MCR must be
requests
(system commands)
for MCR
terminal.

4.1.2

active in order
to receive
function tasks from the user

Command And Slave Terminals

User terminals consist of two distinct classes:
slave terminals.

command terminals and

Command terminals are used to activate MCR and thus gain access to the
system.
Once system access is established, the terminal is used to
initiate system commands, or respond to system prompts.
Slave terminals, on the other hand, are passive.
They can only
respond to or interact with user tasks. For example, a slave terminal
might be used in a process control environment to display or print out
data relevant to an ongoing operation;
or in a data processing
environment to communicate data to an order-entry system.

4-1

NOTE
Any attempt to use a designated slave
terminal
as
a command terminal is
ignored by the system.
The classification
(command or slave)
of terminal use is
the
responsibility of the system manager, or another privileged user. The
system manager can establish a terminal as being system or slave by
issuing the SET system command.
The SET command is described in
Chapter 6.

4.1.3

Activating MCR

The dispatcher portion of MCR must be active in order to receive
requests
(system commands)
for MCR function tasks from the user
terminal. Activating MCR consists of typing CTRL C on the terminal
keyboard. When MCR becomes active, the following prompt is issued:
MCR>
At this point the link between the user and MCR is established.
If the user has not gained access to the system (i.e., logged-on), the
only MCR system command available for use is the HELLO command (see
Section 5.8). The HELLO command identifies the user
to the system,
establishes the user's privileges (see Section 4.1.4), and grants the
user access to the system. When access has been granted, the user can
execute MCR system commands and access files consistent with his
access privileges.
NOTE
The typing of CTRL C does not affect the
execution
of
any
tasks
currently
running.

4.1.4

User Privileges

The system determines user privileges by the UIC under which the user
logs-on.
Privileged users are assigned UICs whose group code is 10
octal or less. Nonprivileged users are assigned UICs with group codes
greater than 10 octal. UICs are assigned to the user by the system
manager.
Two categories of users are granted access to
privileged and nonprivileged.

the

operating

system:

A nonprivileged user uses the system on a day-to-day basis, but is ~ot
responsible for
its maintenance and control. A subset of MCR system
commands is provided for this user. These commands are descriped in
Chapter 5.
A privileged user, like a nonprivileged user, uses the system on a
day-to-day basis, but also has responsibility for the maintenance and
control of the operating system. This user has access to the general

4-2

USER/SYSTEM INTERFACE
MCR system commands described in Chapter
privileged commands described in Chapter 6.

4.1.5

well

to the

Entering System Commands

System commands are entered in response
to the MCR prompt
(MCR».
Once
the prompt is issued, MCR waits for a system command to be
entered immediately following the right angle bracket character
(».
If the system command is not entered within a preset period of time,
MCR times out.
(See Section 4.1.6).
To reactivate MCR, the user need
only retype CTRL C.
System commands (command lines) are entered in the following format.
MCR>Command [command string]
where:
Command

is the system
performed.

command string

if required, are
command
modifiers
or
qualifiers. Command string formats vary from
command to command, and for this reason, are
individually described in their respective
command descriptions.
See
User
Command
Chapters 5 and 6.

command

function

The system command line, typed in by the terminal user, is stored by
the MCR dispatcher. The dispatcher then initiates the corresponding
MCR system command task and exits. The MCR system command task then
interprets the command line that the dispatcher stored and performs
the desired function. The command task executes under the UIC under
which the user logged in.
When the system command task exits, the MCR dispatcher is or is not
reactivated depending on how the command line was terminated.
If the
command line was terminated by a RETURN,
the MCR dispatcher
is
reactivated for that terminal.
If the command line was terminated by
an ALTMODE, the MCR dispatcher does not reactivate.
In this case, the
user must enter CTRL C to reactivate to MeR.

4.1.6

MCR Timeout

MCR waits for a specific length of time
(5 minutes set at system
generation, unless changed by the system manager) for a command to be
entered. See the SET command in Chapter 6.
If this wait time is
exceeded, MCR times out.
At timeout, all information, since the
previous line terminator is lost.
When MCR times out, a carriage return occurs, and
the terminal does
not respond to commands typed in by the user.
To re-establish
communications with MCR, the user must type CTRL C.

4-3

USER/SYSTEM INTERFACE

4.2

TASK RUN-TIME urcs AS FUNCTION OF USER TYPE

Table 4-1 illustrates what the UIC of an executing task will be as a
function of how the task is initiated by a privileged or nonprivileged
Also refer
to
user and the state of the task prior to initiation.
Section 5. for non-privileged versions of run command and Section 6.
for privileged version.
A user can initiate a task from a terminal in anyone of four ways:
1.

MCR>xyz

e.g., MCR>PIP

MCR>RUN .•. xyz

e.g., MCR>RUN .•. PIP

MCR>RUN $file-specification

e.g., MCR>RUN $EDI

MCR>RUN file-specification

e.g., MCR>RUN [200,200]MYTASK

4.2.1

Error Reporting

Errors encountered by system command tasks are reported in the form of
error messages listed on the user terminal. Error messages consist of
a 3-letter command task name and two dashes (--) followed by the error
message text.
Example
SYS -- COMMAND SYNTAX ERROR
The RSX-1ID system error messages
are
listed
and
described
alphabetically in Appendix A.2. The only messages that do not have
the 3-letter prefix are those issued by the task MCRERR.
Section
A.2.l describes these messages.

4-4

Table 4-1
Ule of an Executing Task

TASK ALREADY INSTALLED

TASK ALREADY INSTALLED, BUT TO BE
REMOVED WHEN NO AeTlVE VERSIONS

TASK NOT INSTALLED

Method
of
Initiation

Privileged
User

Nonprivileged
User

Privileged
User

Nonprivileged
User

Privileged
User

Nonprivileged
User

User's Ule

Not applicable

I Task's Ule I Illegal

Not applicable

I User's Ule I User's Ule

User's Ule

User's rJIe

User's Ule

(J)

tr:I

I Task's Ule I Illegal

Task's Ule

User's Ule

Task's Ule

User's Ule

~
til

..c::

(J)

NOTES

I
U1

The user's Ule is the Ule specified in
the HELLO command when the user logged
onto the system.
The task's Ule is the Ule specified
during the building of the task, or when
the task is installed, or when
an
explicit Ule is given in a RUN command.
If no Ule is specified, the user's Ule
becomes the task's Ule when the task is
actually activated.

..:I

tr:I

1-3
tr:I

):=I

()

tr:I

CHAPTER 5
GENERAL USER COMMANDS

The general user commands listed below are available
to all
Commands are presented in alphabetic order in this chapter.
ABORT
ACTIVE TASK LIST
BYE
CONTINUE
DISMOUNT
HELLO
LOG
LUNS
MOUNT
OPERATE
PASSWORD
QUEUE
RESUlvlE
RUN
SYS
TIME
WHO

NOTE
Please
reread
the
Preface
for
explanation of characters
( , /, [],
etc.)
that indicate
command
format
conventions.

5-1

users.

GENERAL USER COMMANDS
ABORT

5.1

ABORT COMMAND (ABO)

FUNCTION:
The ABORT (ABO) command allows the terminal user to terminate the
execution of tasks which have been initiated from that terminal.
FORMAT:
ABO[RT]6taskname[,taskname, .•. ]
where:
taskname is the name of the task being aborted.
EXAMPLE:
MCR)ABO •.• MAC,RICK
The above command causes the execution of the tasks named MAC and RICK
to be terminated.

5-2

GENERAL USER COMMANDS
ACTIVE TASK LIST

5.2

ACTIVE TASK LIST COMMAND (ACT)

FUNCTION:
The Active Task List (ACT) command enables the terminal user
to
obtain a list of the tasks active within the system, along with
status information about the tasks.
FORMAT:
ACT8[taskname] [/switch(s)]
where:
taskname

is the name of the task whose status information
is
to be listed.
If taskname is not specified,
all of the
tasks having
the same TI as
the
terminal from which the command
is issued are
listed.

/switch(s)

is one or more of the following switch options:
NOTE
If no switch is specified,
the following
information is listed for all active tasks
having the same TI as
the
terminal from
which the command was issued:
Task Name
Task Status (see Table 5-1)
TI Device

/FU

specifies that a full listing of th~ named task's
status
information is to be generated. Use of
this switch has the following restrictions:
1.

It can be specified
specified.

5-3

only

when

taskname

GENERAL USER COMMANDS
2.

It cannot be specified in conjunction with the
/ALL swi tch.
Specifying
/FU
causes
information to be listed:

the

Task Name
Task Status (see Table 5-1)
TI Device
Run Priority
Partition
Real Memory Starting Address
Number of Active Versions
Requesting Task's Name
Registers
RS, PC, RO, Rl, R2, R3, R4, R5, SP
Event Flags 1-16
Event Flags 17-32
ATL Flags Word
STD Flags Word
Event Flag Masks
Mark Time Count
ATL Node Address (Kernel Virtual)
STD Node Address (Kernel Virtual)
Maximum Task Size
I/O Pending Count
I/O In Progress Count
Pool Limit Count
Pool Usage Count
Global Libraries and Commons (if any)
PARS-- 0-7
PDRS-- 0-7

5-4

following

GENERAL USER COMMANDS
Table 5-1
ACT Task Status Characters
CHARACTERS

DESCRIPTION

Load request queued

Load request unqueued

Load request failed

Task running

Task AST queued

Task suspended

Task waiting for event flag 1-16

Task waiting for event flag 17-32

Task waiting for event flag 33-48
Task waiting for event flag 49-64

Task waiting for event flag 1-64

Task exited

I/O rundown required

I/O rundown in progress

I/O rundown finished

I/O rundown failure

Task termination fault

Task termination notice requested

Task suspended for

Task suspended for checkpoint

Record request queued

Record request succeeded

Record request failed

Parity error

5-5

termination notice

GENERAL USER COMMANDS

ISH

Specifies that a shorter version of the /FU
listing is required. The following information is
1 is ted:
Task Name
Task Status (see Table 5-1)
TI Device
Run Priority
Partition
Real Memory Address

/ALL

Specifies that every active task in the system is
to
be listed.
Use of this switch has the
following restrictions:
1.

It cannot be specified in conjunction with the
/FU switch.

It cannot be specified in conjunction with the
/TI=dev switch.

The following
task:

information

is listed

about

each

Task Name
Task Status (see Table 5-1)
TI Device
/TI=dev

Specifies that all of the tasks of a specific TI
are to be listed. dev is the terminal identifier
for the specified TI.
The following
information
is listed about each task:
Task Name
Task Status (see Table 5-1)
TI Device

EXAMPLES:
1.

MCR)ACT
TT ••.. WO TT07
..• ACT RN TT07
•• PIP WO TT07

MCR)ACT •.. PIP
.•• PIP WO TT07

5-6

GENERAL USER COMMANDS
3.

MCR)ACT ••. PIP/S8
.•• PIP WO TT07 055 GEN

MCR)ACT ••• PIP/AL/S8
.•. PIP WI TT01 055 GEN
.•. PIP WI TT02 055 GEN

233300

213300
244400

MCR)ACT •.• FLX/FU
.•• FLX WO TTOO 050 GEN
371000 ACT VERS 002 REQ TASK •.. MCR
REGS 174000 002510 021322 000010 027522 000000 000101 000101
000342
EV 1-16 000000 EV 17-32 140000 ATL FLGS 000200 STD FLGS 060100
EV MASKS 000002 000003 040647 030040 MKTM CNT 000
ATL ADDR 107000 STO ADDR 103700 TSK SIZE 063700
I/O PEND 003 I/O PROG 001 POOL LIM 040 POOL USE 014
GBLS SYSRES
PARS 003720 004120 004320 004520 000000 000000 000000 001747
PDRS 077606 077606 077606 013206 000000 000000 000000 071502

•

MCR)ACT /ALL
DP ...• WO TTOO
TT .... WO TT10
OK •.•• WO TTOO
LP ••.. WO TTOO
OF. . .• WO TTOO
DT •.•. WO TTOO
MT •.•. WO TTOO
· •• MCR WO TTI0
· .• ACT WO TT07
MO •... WO TT05
... TKB RN TTOO

MCR)ACT /TI=TTI0
TT •.•• WO TTI0
· •. MCR WO TT10

MCR)ACT .'-.PIP/TI=TT2/FU
.•• PIP WI TT02 055 GEN
213300 ACT VERS 001 REO TASK •.. MCR
REGS 174004 167762 004644 013522 000000 006003 000040 013710
000236
EV 1-16 000000 EV 17-32 040000 ATL FLGS 000200 STD FLGS 020100
EV MASKS 100000 000256 000401 000002 MKTM CNT 000
ATL ADDR 106300 STD ADDR 100660 TSK SIZE RO 007300 RW 021600
I/O PEND 002 I/O PROG 000 POOL LIM 040 POOL USE 003
PARS 002143 002351 002306 000000 000000 000000 000000 001747
FDRS 061206 035102 021206 000000 000000 000000 000000 071502

5-7

GENERAL USER COMMANCS
BYE

5.3

BYE COMMAND (BYE)

FUNCTION:
The BYE command provides the user with a facility for logging-off
a
terminal.
The only command MCR recognizes after this command
is executed is HELLO. The BYE command has no effect on active
tasks previously initiated from this terminal.
FORMAT:
BYE
EXAMPLE:
MCR>BYE

5-8

GENERAL USER COMMANDS
COMMON BLOCKS

5.4

LIST COMMON BLOCKS COMMAND (COM)

Refer to the SYS /COM command in Section 5.18.

5-9

GENERAL USER COMMANDS
CONTINUE

5.5

CONTINUE COMMAND (CON)

FUNCTION:
The CONTINUE Command (CON) is used to continue the execution of a
task that as selected the SUSPEND action parameter option when
using the message output handler task.
FORMAT:
CON[TINUE]~taskname[,taskname, •.. ]

EXAMPLES:
MCR>CON XKE
MCR>CONTINUE XKE,NKIll
In the examples above the respective requests are to:
1.

Continue task XKE.

Continue task XKE and task NKIII.

5-10

GENERAL USER COMMANDS
DEVICES

5.6

DEVICES COMMAND (DEV)

Refer to the SYS /DEV command in Section 5.18.

5-11

GENERAL USER COMMANDS
DISMOUNT

5.7

DISMOUNT VOLUME COMMAND (DMO)

FUNCTION:
The Dismount Volume (DMO) command 'allows the user
to logically
dismount
(make invisible to
the system) a previously mounted
volume.
DMO deletes the Volume Control Block
(VeB)
and
its
extensions,
thus declaring the volume to be logically off-line,
and rendering it inaccessible.
Before shutting down an RSX-IID system, all volumes should be
logically dismounted to ensure that no files are currently being
accessed. Any files currently being accessed when the system is
shut down may contain inconsistent data.
If the volume contains files
following message is issued,
aborted:
DMO -- VOLUME BUSY.

currently being accessed,
the
and
the dismount operation is

TRY AGAIN LATER

FORMAT:
DM06dev: [volumelabel] [/UIC=[uic]] [/LOCK]
where:
dev:

is the device specifier for
volume is mounted.

the

device

which

the

volumelabel
is label of the volume being dismounted.
If specified,
the value entered is compared with the corresponding
value in the VCB.
If unequal,_ the volume
is not
dismounted.
/UIC=[uic]
is the
volume UIC.
Like
the volume label,
it
compared to
its corresponding entry in the VCB.
unequal, the volume is not dismounted.
/LOCK

is
If

If this option is specified, the volume is marked for
dismount regardless of whether files are currently
accessed on it.
Further accesses are
then disallowed
and
the volume is actually dismounted only when all
current file accesses are terminated.

If the DMO command is issued for any volume of a multivolume magnetic
tape file, all of the mounted volumes are automatically dismounted.

5-12

GENERAL USER COMMANDS
The following message is issued by the file processor when the logical
dismount is completed and it is safe to physically remove the volume
from the system:
FllACP - - DKO:

** DISMOUNT COMPLETE **

The first six characters of the message (FllACP) are the· task name of
the file processor, and may vary with the device and the manner in
which it was mounted.
EXAMPLES:
1.

MCR)DMO OKl:
In this example, the VCB for
the volume mounted
deleted, and the volume becomes inaccessible.

DKl:

MCR)DMO DKl:RICKSVOL/UIC=1300~300]
In this example, the VCB for
the volume mounted on DKl:
is
interrogated.
If it contains a volume label of "RICKSVOL II and a
UIC of U[300,300]", the VCB is deleted, and
the volume becomes
inaccessible; otherwise, the volume remains mounted.

MCR)DMO MTl:VOLUMl
In this example, the VCB for
the volume mounted on MTl:
is
interrogated.
If it contains a volume label of VOLUMI the VCB is
deleted;
otherwise the volume remains mounted.

If the specified volume is one of a multivolume magnetic
tape file,
all of the mounted volumes of the file are automatically dismounted.

5-13

GENERAL USER COMMANDS
HELLO

5.8

HELLO COMMAND (HEL)

FUNCTION:
The HELLO command (HEL) allows the user to log onto a
terminal
and be identified as a valid user by the system.
It also
identifies the user as a general or privileged user.
(See
Section 4.1.4.)
FORMAT:
HEL[LO]~[uic]

NOTES
1.

If the user-entered
[UIC]
(brackets
required)
does not have a corresponding
UFD on the system device
(SY:),
system
access
is denied and the following
message is issued:
HEL -- CANNOT FIND DIRECTORY FILE

If the UFD is password-protected,
following prompt is issued:

the

PASSWORD>
The user must enter the correct password
immediately following the prompt.
(The
user-entered password does not print on
the terminal.)
3.

If the user-entered password is
in
error, system access is denied and the
following message is issued:
HEL -- ILLEGAL PASSWORD

EXAMPLES:
1.

The log-on procedure for a nonpassword-protected UIC is:
MCR>HELLO [200,200]
MCR>

5-14

GENERAL USER COMMANDS
2.

The log-on procedure for a password-protected urc is:
MCR>HELLO [200,200]
PASSWORD>
MCR>
NOTE
The password entered by the user is
printed on the terminal.

5-15

not

GENERAL USER COMMANDS
LOG

5.9

LOG COl1MAND

FUNCTION:
The LOG command allows
the user
to
type a comment on the
terminal.
This feature can be used to note information about the
current system.
Data typed following this command has no effect
on the system.
- FORMAT:
LOG~

comment-line
or
comment-line
or
comment-line

EXAMPLE:
MCR>LOG STANDARDS CHANGED BY 20 MG.
PER CUP.
or
MCR>;
STANDARDS CHANGED BY 20MG.
PER CUP.
or
MCR>!
STANDARDS CHANGED BY 20MG.
PER CUP.
NOTE
A log message can fill an entire line.

5-16

GENERAL USER COMMANDS
LUNS

5.10

LOGICAL UNIT NUMBERS COMMAND (LUNS)

FUNCTION:
The Logical Unit Numbers (LUNS)
command lists, on the user's
terminal,
the physical device units and corresponding logical
unit numbers for an indicated task or
tasks.
This command is
used when the operator wants to determine which physical devices
a task requires.
FORMAT:
LUN[S]~taskname[,taskname, •.. ]

EXAMPLE:
MCR> LUN •.. SYS

**** ... SYS

T'I'O 6

CLO 5
LPO 3
SYO 1,4
TECHNICAL NOTES:
The LUNS command lists:
1.

I/O assignments taken from the task's disk image

Only the devices to which assignments have been made

Any run-time changes in LUN assignments made by an active task are not
reflected in the listing.

5-17

GENERAL USER COMMANDS
MOUNT

5.11

MOUNT COMMAND (MOU)

FUNCTION:
The MOUNT command (MOU) allows the user to make a selected volume
visible
to the system.
MOU creates the Volume Control Block
(VCB) and declares that the volume is logically on-line for
access by the File Control Primitives.
FORMAT:
The format listed below is the general format for
the MOUNT
command.
MOUNT for multivolume magnetic
tape
is somewhat
different in format, and is discussed in section 5.11.1.
MOU[NT]~dev:volumelabel[keyword(s)]

where:
dev:

is the device specifier for the device that contains the
volume being mounted.

volumelabel
is the volume label of the volume being mounted.
The
label specified is compared to the label field of the
volume's home block,
to ensure that the physically
mounted volume is the one to be logically mounted (made
visible) by the system.
NOTE
Disk and DEC tape volumes are allowed to contain
null
(all zeros) volume labels.
In this case,
the volume label need not be specified.
The
system assumes a null label.
/keyword(s)
are optional modifiers that allow the user
to override
the volume characteristics that were assigned to the
volume when it was initialized. The following
keyword
options are provided.

5-18

GENERAL USER COMMANDS
NOTE
Notations listed to the left of keyword
equate to the following:

options

* Applies to disk and
DEC tape only
Overrides the corresponding
option specified at INITVOL

+ Applies to magnetic tape only
/CHA=[characteristic word]
This option changes the device characteristic
word. Possible parameters for this option are:

FOR

-not an RSX-IID structured volume
(FOREIGN).
When this parameter is
specified DCF
is
automatically
assumed.
ATCH -device
may
be
attached
for
exclusive use by one task.
DCF -device control functions permitted;
removes restrictions.
NOTE
ATCH and DCF are legal for magnetic
only when it is mounted as FOREIGN.

tape

Example
/CHA=[FOR,ATCH]

/UNL
This option specifies that the volume's index file is to
be left unlocked, thus giving tasks write access to the
index file.

/DENS=magnetic tape density
Possible parameters are:
800 for 800 BPI
1600 for 1600 BPI

5-19

GENERAL USER COMMANDS
Example
/DENS=800
/ACP=task name
This option allows the user to designate the
is to be the file processor for the volume.

task

that

Example
/ACP=DSKFI
*=

/EXT=default file extend increment in blocks
Example
/EXT=5

/FPRO=[default file protection]
This option allows the user to change the default file
protection assigned to new files created on the volume.
Each entry consists of from one to four letters which
have the following meanings.
R - for READ access

W - for WRITE access
E - for EXTEND access
D - for DELETE access
The absence of one of these letters in an
signifies the access right is denied to the user.

entry

Protection code subparameters (system,owner,group,world)
are positional;
therefore, the location of entry in the
parameter string defines the user
to whom the codes
apply.
Example
/FPRO=[RWED,RWED,RW,RW]
In this example, group and world are denied
Delete access.
*=

Extend

and

/LRU=number of directories to keep pre-accessed
Example
/LRU=3

/OVRFSID
This option is used
to override the set identifier
check. This option is required when processing magnetic
tape with inconsistent file set identifiers.

5-20

GENERAL USER COMMANDS

jOVREXP
This option is used to override the expiration date
check.
Allows the user to overwrite unexpired magnetic
tape files.

5.11.1

Format For Mounting Multivolume Magnetic Tape

The following format should be
tape.

used

mount

multivolume

magnetic

MOU [NT]b.l-1T (nl [,n2, .•. ,nn] ) : (labell [,labe12, ... ,labeln]
[/keyword (s) ]
where:
n

is the logical tape drive number(s)
(in
the order of
selection)
representing the drive(s) to be dedicated to
the processing of the multivolume set.
If only one
drive
is being dedicated,
the parentheses may be
omi t ted.

label

is the volume label{s) (in order)
that constitute
the
volume-set.
Only the volume label for the first volume
in the set need be specified.
If further
labels are
specified,
they will be used by the file processor to
validate further volumes as they are requested.
If no
further
labels are specified, it is up to the user to
ensure that the correct volume is placed on
the
appropriate drive when requested.
NOTE
A separate unit number need not be specified for
each volume In the se~.
The file processor
processes volumes sequentially down the list of
specified units, until the last unit is reached.
If more volumes are to be processed, a mount
request,
for
the next sequential volume to be
mounted is issued for one of the units listed.

jkeyword(s)
See keywords provided for the
command.

5-21

general

class

Mount

GENERAL USER COMMANDS
TECHNICAL NOTES:
Because of the large number of options available with the MOU
command, it may not be possible to enter the entire command
string on a single line. For this reason, MOU has been modified
to accept multiline commands. To accomplish this, the user must
follow the procedure outlined below.
1.

Initiate MOU as follows:
MCR>MOU
When MOU is ready
following prompt:

command

lines,

issue

the

MOU>
2.

At this point, multiple lines can be typed in to MOU.
Each
line except the last must contain a hyphen (-) as the last
character entered.
When MOU recognizes the hyphen, it
assumes that the command line is incomplete, and reissues the
MOU> prompt for more parameters.
When the last line is
entered
(no hyphen), MOU begins processing the command. See
example number 3.

EXAMPLES:
1.

MCR>MOUNT DKl:SYS004
In this example, a request is made to mount disk volume SYS004 on
DKl:. None of the volume's attributes are to be overridden.

MCR>MOU MT(1,2}: (RICK,SHEILA,LAURA,JEN)
In this example, a request is made to mount multivolume magnetic
tape.
Logical tape units 1 and 2 are reserved for processing.
At the time the mount request is being processed,
tape volume
RICK
must be physically mounted on logical tape unit 1;
otherwise, the label check will fail. No label check is made for
tape unit 2 until the file processor is ready to process the next
volume (SHEILA).

MCR>MOU
MOU>DKl:ACCTSYS/WIN=lO.MOU>/LRU=4/FPRO=[R,RWED,R,]

5-22

GENERAL USER COMMANDS
OPERATE

5.12

OPERATE COMMAND (OPR)

FUNCTION:
The OPERATE (OPR) command enables the terminal user to direct the
output processing of the Multi-Output Despooler. See Section
2.6.
FORMAT:
OPR[ATE]~dev:/switch[,dev:/switch, ... ]

where:
dev:

is the device specifier for the Multi-Output
device being controlled.

Despooler

/switch

is the command modifier
that directs OPR
OPR switches are described in Table 5-2.

operation.

5-23

GENERAL USER COMMANDS
Table 5-2
OPR Switches
SWITCH

DESCRIPTION

ISP

Start printing, on the specified device, all files
whose
forms-type
match
the forms-type currently
specified for this device.

lAB

Abort printing of the current file on the specified
device. Select the next eligible file for processing.
NOTE
Although the aborted file
is removed from
the
queue,
it is not deleted. Therefore it is still
available and can be requeued for printing at some
later time.

1ST

Stop printing of the current file on the specified
device.
Printing of the file
is stopped in place.
Printing can be resumed by specifying one of the IRS
switches;
or it can be aborted by specifying the lAB
switch.

IRS

Resume printing of the current file
device.

IRS:T

Resume printing of the current file from
the last
encountered form feed.
If no previous form feed was
encountered, printing begins at the top of the file.

IRS:TOF

Restart printing
beginning.

the

current

the

file

specified

from

the

NOTE
All of the IRS options can be used without
previous stop option having been issued.

EXAMPLES:
1.

MCR>OPR TTl:/ST
In this example, the user has directed that the printing of files
on TTl:
be suspended.

MCR>OPR TTI:/RS:TOF
In this example, the user has directed that the printing on TTl:
be resumed, and that the file be reprinted from the beginning.

5-24

GENERAL USER COMMANDS
PARTITIONS

5.13

PARTITIONS COMMAND (PAR)

Refer to the SYS /PAR command in Section 5.18.

5-25

GENERAL USER COMMANDS
PASSWORD

5.14

PASSWORD COMMAND (PWD)

FUNCTION:
The PASSWORD Command (PWD) allows the terminal user to change
create a password for his UFD on the system disk.

FORMAT:
PWDil[ufd]
where:
[ufd]

is the UFD receiving the new password.

When the above command
is
prompting message is issued.

received

PWD,

the

following

PASSWORD>
The user now enters the desired password
immediately following
the right angle bracket (».
The newly entered password is not
typed on the terminal.
NOTE
Only the UFD which corresponds to
the
UIC under which the user logged on can
be changed.

EXAMPLE:
MCR>PWD [200,200]
PASSWORD>
MeR>

5-26

GENERAL USER COMMANDS
QUEUE

5.15

QUEUE COMMAND (QUE)

FUNCTION:
The QUEUE command (QUE) is the terminal user's interface
to
the
RSX-llD queue manager task.
The Queue Manager maintains a queue
of elements.
Each element defines a Files-II file specification
for a file that is to be printed on a line printer or a terminal.
The QUE command provides the user with the ability to perform the
following functions:
1.

Print queue files on a line printer or terminal.

List user-related elements in the
queue.

List all elements in the queue manager task's queue.

Kill
(delete)
user-related
manager task's queue.

Modify user-related
task's queue.

queue

element(s)

the

manager

task's

the

queue

manager

NOTE
QUE works
Spooler.

only

with

the

Multi-Unit

FORMAT:
The format of the QUE command varies depending on the function
b~ing
performed.
The format for each function is described in
its respective section.

5-27

GENERAL USER COMMANDS
5.15.1

Queue A File For Printing

This function of the QUE command allows the user to queue
files for printing on a line printer or terminal.

file

(default

FORMAT:
QUEt. [dev: =] inf ile-l [ ,inf ile-2, •.. , inf ile-n] [/swi tch (es) ]
or
QUE @indirect
where:
dev:=

is the optional listing device
LP: ) •

infile

is a file specifier for the file(s)
being queued for
printing.
(See Table 5-3 for a list of defaults in QUE
file specifiers.)

specifier

NOTE
QUE allows wildcard specifiers.

/swi tch
( es)

is one or more of the QUE option switches.
(See Table 5-4).
QUE option switches are global;
that
is,
they may be specified once for an entire list of
input file specifiers.
They may be appended to any of
the file specifiers in a list.
However, if a switch is
specified repeatedly, the last value specified is used.

@indirect is an indirect command file specifier.
NOTE
The QUE function
indirection.

5-28

supports

three

levels

GENERAL USER COMMANDS
Table 5-3
Defaults in QUE File Specifiers
Specifier

Default

dev:

SY:

[ufd]

specifier,
For the first or only file
to the urc
the UFD which corresponds
under which the user logs on.
through
file
second
n
For
the
specified
or
UFD
specifiers,
the
previous
file
defaulted
for
the
specifier.

filename

Must be specified.

. type

.LST

iver

The la test version for

5-29

the file.

GENERAL USER COMMANDS
Table 5-4
QUE Command Optional Switches
SWITCH

DESCRIPTION

DEFAULT

/PR:nnn

Set the priority of output selection to
nnn (nnn is a decimal number ranging
from 1 to 250).

/PR:50

/FO:n

Set the output forms type to n (n is a
decimal number ranging from 0 to 6).

/FO:O

Specific form types are defined by the
system manager; for example, form type
o should correspond to standard line
printer forms (single ply, 11" xIS");
form type 2 could correspond to payroll
check forms; form type 3 could correspond
to standard billing forms.
/CO:nn

Set the number of copies to be printed to
nn (nn is a decimal number ranging
from 1 to 31).

/CO:l

/DE

Delete the input file after it has been
spooled.

/-DE

/TE

Test for forms alignment.
This switch
is used to ensure that the desired
forms are properly aligned in the
receiving device.

None

The priority entry is automatically
set to 250, and the forms type entry
is se t to 7.
This option, although documented in this
chapter, is normally used by the system
manager; it is also normally preceded by
the following privileged MCR system command:
IJICR)OPR LP: /CH

5-30

GENERAL USER COMMANDS
EXAMPLES:

MCR>QUE TEST
In this example, the latest version of file TEST.LST, residing in
the user's directory file on SY:, is queued for printing.
The
following options are assigned to the queued entry.

- Printing device

LP:

(defaul t)

- Priority

(defaul t)

- Forms type

(default)

- Number of copies

(defaul t)

- Delete

(defaul t)

MCR>QUE TTl:=TEST.MAC/PR:250/CO:4/DE
In this example, the latest version of file TEST.MAC, residing in
the user's directory file on SY:, is queued for printing.
The
following options are assigned to the queued entry.

- Printing device

TTl:

- Priority

250

- Forms type

o (defaul t)

- Number of copies

- Delete

Yes

MCR>QUE [20,20]TEST,DKl:TEST.MAC,TEST.CMD/PR:250
In this example,
the latest version of the file TEST.LST,
residing 1n the directory file [20,20] on SY:, and the latest
version of files TEST. MAC and TEST.CMD,
residing
in directory
file
[20,20]
on DKl:, are queued for printing.
The following
options are assigned to each file entry.
- Printing device

LP:

- Priority

250

- Forms type

o (defaul t)

- Number of copies

1 (default)

- Delete

No (default)

5-31

(default)

GENERAL USER COMMANDS
4.

MCR>QUE [202,12]*.MAC
In this example, the latest version of all files of the type MAC
residing
in directory file
[202,12]
on SY:, are queued for
printing.
The following options are assigned
to
the queued
entries.
-

5.15.2

LP: (default)
50 (default)
o (defaul t)
1 (defaul t)
No (default)

Printing device
Priority
Forms type
number of copies
Delete

List Elements In Queue

(/LI)

The list function (/LI) of the QUE command allows the user to obtain a
listing of all entries in the queue manager task's queue.
Output from
this function provides the user with pertinent information concerning
the status of each entry in
the queue, as well as the options
specified for each entry.
A sample queue listing,
along with a
description of
the
information it provides, is contained in Figure
5-1.
1

DEV

ACT

ACCOUNT

LPO
TT5
TTl
TT5

[200,200]
[200,200]
[200,200]
[200,200]

FILE SPECIFICATION

SEQ PRI

DPO:TEST.LSTi6
DKl:RSXMAC.SMLi17
DKO:TEST.MACi40
DPO:QUE.CMDi3

100
4 240
2 20
3 50

0
0
0
0

4
1
1
1

*
*

DEV/A= Destination device.

ACT

Asterisk denotes an input file which is currently
being output by the Despooler.

ACCOUNT

UIC of user who queued the request.

FILE SPECIFICATION
Input file specification

SEQ

Sequence number
that
inactive queued entry.

PRI

Priority of output selection.

The forms types.

Number of printed copies.

Delete/Preserve indicator.
An asterisk
indicates
the file
is
to be preserved after output is
complete.

uniquely

Figure 5-1
Sample Output from QUE /LI Function
5-32

identifies

GENERAL USER COMMANDS
FORMAT:
QUE~/LI

EXAMPLE:
MCR>QUE /LI
DEV ACT

ACCOUNT

FILE SPECIFICATION

LPO
TTS
TTl
TTS

[200,200]
[200,200]
[200,200]
[200,200]

DPO:TEST.LSTi6
DKl:RSXMAC.SMLi17
DKO:TEST.MACi40
DPO:QUE.CMDi3

S.lS.3

SEQ
4
2

PRI FO
100
240
20

CO P

0
0

4
1
1

*
*

List All Elements in Queue (/AL)

The list all (/AL) performs the same function as list (LI) except. that
all entries in the queue are printed regardless of the user's UIC.

S.lS.4

Kill (Delete) Elements in Queue (/KI)

The kill function (/KI) allows the user to delete elements from the
queue manager
task's queue. The user accomplishes this deletion by
specifying the entry's queue sequence number as a parameter to the /KI
function.
Queue entry sequence numbers can be obtained by executing
the QUE command with the /LI function specified.
NOTE
Any attempt to delete a queued entry
with an account number that is not the
user's results in a privilege violation
error message.

FORMAT:
QUE~/KI:seq[:seq: ..• :seq]

where:
:seq

is the sequence
deleted.

number

for

the

queued

entry

being

Two formats for specifying sequence numbers are supported:
a single
defined sequence number
(:seq)
or a range of sequence numbers
( : seql-seqn) .

S-33

GENERAL USER COMMANDS
A single defined sequence numbers is specified by entering a colon (:)
followed by the sequence number.
When this format is used, the
sequence number is interpreted as a command to delete a single queued
entry.
A range of sequence numbers is specified by entering a colon
(:)
and
the beginning sequence number, followed by a dash (-) and the ending
sequence number. When this format is used, the sequence numbers are
interpreted as a command
to delete all entries whose consecutive
sequence numbers start with the number specified to the left of the
dash and end with the number specified to the right of the dash.
Any combination of formats can be used in the same /KI command line;
however,
the maximum number of individual combinations is ten.
See
Figure 5-2 for a sample execution of the /KI function.
DEV ACT

ACCOUNT

FILE SPECIFICATION

SEQ

PRI FO

LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO

[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]

DPO:RCVAST.MAC;45
DPO: SETBLD. Cr1D; 3
DPO:PRTX.MAC;3
DPO:PRT.MSG;3
DPO:OPR.MAC;17
DPO:OPRBLD.CMD;5

25
26
27
28
29
30
1
3
4
5
7
8
13
14
15
16
17

55
55
55
55
55
55
50
50
50
50
50
50
50
50
50
50
50

DPO:SET.MACill
DPO:MAC12.CMD;4
DPO:SPRODT.CMD;2
DPO:INLINE.MAC;51
DPO:FORMAT.MAC;23
DPO:SETUP.MAC;15
DPO:IOAST.MAC;25

DPO:SPR2.MACi60
DPO:SPRBLD.CMDil0
DPO:TSTBLD.CMDi6
DPO:TEST.MACi22

2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1

CO P
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*

Listing of
queued entires before
execution of
/KI function

QUE>/KI:27-30:1:3-5:7-8:13
QUE>/LI
DEV ACT

ACCOUNT

FILE SPECIFICATION

SEQ

PRI FO

CO P

LPO
LPO
LPO
LPO
LPO
LPO

[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]

DPO:RCVAST.MACi45
DPO:SETBLD.CMDi3

25
26
14
15
16
17

55
55
50
50
50
50

1
1
1
1
1
1

DPO:SPR2.MAC;60

DPO:SPRBLD.CMDil0
DPO:TSTBLD.CMDi6

DPO:TEST.MACi22

Figure 5-2
Sample Execution of /KI Function

5-34

2
2
1
1
1
1

*
*
*
*
*
*

Listing of
queued entries after
execution of
/KI function

GENERAL USER COMMANDS
EXAMPLES:
1.

MCR>QUE /KI:2:6:l0:l2
In this example, the queued entries whose sequence numbers are 2,
6, 10, an~ 12 are deleted from the queue manager task's queue.

MCR>QUE /KI:2:6-l2:l4
In this example, the queued entry 2, the entries 6 through 12,
and entry 14 are deleted from the queue manager task's queue.

5.15.5

Modify A Queue Entry (/MO)

The modify function (/MO) allows the user
to change
originally specified for a queued entry or entries.

the

option(s)

The following queued entry fields can be modified by the /MO function.
listing device
priority
forms type
number of copies
delete option
FORMAT:
QUE~[dev:=]/MO:seq[:seq .•. :seq] [/switch(es)]

where:
dev:

is the new listing device specifier.
If dev:
is
specified, it must be followed by an equal sign (=).

:seq

is the sequence number of the queue entry being
modified. Sequence numbers can be entered individually
or in a range of sequence numbers.
See Section 5.15.3.
NOTE
When the /MO function
is
executed,
the
specified queue entry is deleted and replaced
with a modified version of the original entry.
Therefore,
the
original
sequence
number
disappears and is replaced with a number one
greater than the highest number in the queue at
the time
the modify function
is executed.
Figures 5-3 and 5-4 contain sample executions
of the /MO function.

5-35

GENERAL USER COMMANDS
/switch (es)
is the option modification switch(es).
switches are described in Table 5-5.

Modification

Modification switches can be appended only to the
sequence number in the command line.

last

NOTE
If the /DE switch is
assumed.

not

specified,

/-DE

Table 5-5
/MO Option Switches
SWITCH

DESCRIPTION

DEFAULT

/PR:nnn

Change the priority of the queued
entry to nnn (where nnn is a decimal number ranging from 1 to 250).

none

/FO:n

Change the form type to n (where
n is a decimal number ranging from
1 to 6).

none

/CO:nn

Change the number of copies to nn
(where nn is a decimal number ranging from 1 to 31).

none

/DE

Change the delete/preserve indicator to dele te.

/-DE

5-36

GENERAL USER COMMANDS
QUE /LI
DEV ACT

ACCOUNT

FILE SPECIFICATION

SEQ

PRI FO

LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO
LPO

[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]

DPO:BPR.ODLi7
DPO:RICK.MACi14
DPO:BPRBLD.CMDi20
DPO:INIT.MACi37
DPO:TEMP.SAVi2
DPO:HANK.BISi1
DPO:BPRMAC.MACi5
DPO:UTIL.MACi3
DPO:ERRMES.MACi4
DPO:MAIN.MACi32
DPO:MAIN.MAC:32
LPO:CLOSE.MACi12

1
2
3
4
5
6
7
8
10
11
12

50
50
50
50
50
50
50
50
50
50
50
50

0
0
0
0
0
0
0
0
0
0
0
0

CO P
1
1
1
1
1
1
1
1
1
1
1
1

*
*
*
*
*
*
*
*
*
*
*
*

Listing of
queued entries prior
to execution of /MO
function

MCR>QUE TT1:=/MO:2:6:9-12/FO:2/PR:55/DE
MCR>QUE /LI
DEV ACT

ACCOUNT

FILE SPECIFICATION

SEQ

PRI FO

TTl
TTl
TTl
TTl
TTl
TTl
LPO
LPO
LPO
LPO
LPO
LPO

[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]

DPO:RICK.MACi14
DPO:HANK.BISi1
DPO:ERRMES.MACi4
DPO:LOGGER.MACi3
DPO:MAIN.MACi32
DPO:CLOSE.MACi12
DPO:BPR.ODLi7
DPO:BPRBLD.CMDi20
DPO:INIT.MACi37
FPO:TEMP.SAVi2
DPO:BPRMAC.MACi5
DPO:UTIL.MACi3

13
14
15
16
17
18
1
3

55
55
55
55
55
55
50
50
50
50
50
50

5
7
8

2
2
2
2
2
2
0
0
0
0
0
0

MCR>
NOTE
the
Note that the sequence numbers for
entries being modified were deleted and
replaced with modified entries having
new sequence numbers.

Figure 5-3
Sample Execution of /MO Function
(with Option Switches Specified)

5-37

CO P
1
1
1
1
1
1
1
1
1
1
1
1

*
*
*
*
*
*

Listing of
queued entires after
execution
of /MO
function

GENERAL USER COMMANDS
QUE /LI
DEV ACT

ACCOUNT

TTl
TTl
TTl
TTl
TTl
TTl
LPO
LPO
LPO
LPO
LPO
LPO

[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]

FILE SPECIFICATION

SEQ

PRI FO

DPO:RICK.MACi14

DPO:INIT.MACi37
DPO:TEMP.SAVi2
DPO:BPRMAC.MACi5
DPO:UTIL.MACi3

13
14
15
16
17
18
1
3
4
5
7
8

55
55
55
55
55
55
50
50
50
50
50
50

DPO:HANK.BISil

DPO:ERRf.1ES.MACi4
DPO:LOGGER.MACi3
DPO:MAIN.MACi32
DPO:CLOSE.MACi12

DPO:BPR.ODLi7
DPO:BPRBLD.CMDi20

2
2
2
2
2
2
0
0
0
0
0
0

CO P
1
1
1
1
1
1
1
1
1
1
1
1

*
*
*
*
*
*

Listing of
queued entries prior
to execution of /MO
function

MCR>QUE /MO:13-18
MCR>QUE /LI
DEV ACT

ACCOUNT

FILE SPECIFICATION

SEQ

PRI FO

CO P

TTl
TTl
TTl
TTl
TTl
TTl
LPO
LPO
L'PO
LPO
LPO
LPO

[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]
[200,200]

DPO:RICK.HACi14

19
20
21
22
23
24
1
3
4
5
7
8

55
55
55
55
55
55
50
50
50
50
50
50

1
1
1
1
1
1
1
1
1
1
1
1

LPO:HANK.BISil

DPO:ERRMES.MACi4
DPO:LOGGER.MACi3
LPO:MAIN.MACi32
DPO:CLOSE.MACi12

DPO:BPR.ODLi7
DPO:BPRBLD.CMDi20
DPO:INIT.MACi37
DPO:TEMP.SAVi2
DPO:DPRMAC.MACi5
DPO:UTIL.MACi3

2
2
2
2
2
2
0
0
0
0
0
0

NOTE
Note that the sequence numbers, as in
Figure 5-3, were deleted and replaced
that the
with new ones.
Note also,
delete option for the specified entries
were automatically changed to preserve
(/-DE)

Figure 5-4
Sample Execution of /MO Function
(Defaul t)

5-38

*
*
*
*
*
*
*
*
*
*
*
*

Listing of
queued entries after
execution
of /MO
function

GENERAL USER COMMANDS
RESUME

5.16

RESUME COMMAND (RES)

FUNCTION:
The RESUME command allows the user to continue execution of a
previously suspended
task or
tasks.
Suspended tasks can be
resumed only from the terminal from which they were initiated.
FORMAT:
RES[UME]~taskname[/TI=dev]

[,taskname-l[/TI=dev] , ..• ]

where:
taskname

is the name of the task being resumed.

/TI=dev

is an optional switch (appended to the taskname)
which
allows the user
to resume any task in the system by
specifying its TI (dev is the device mnemonic for
the
terminal corresponding
to the TI under which the task
is run).

EXAMPLES:
1.

MCR>RESUME XKE

MCR>RESUME XKE, NKlll,240Z

In the examples above the requests are to:
1.

RESUME Task XKE.

RESUME Task XKE, Task NKlll, and Task 240Z.

5-39

GENERAL USER COMMANDS
RUN

5.17

RUN COMMAND (RUN)

FUNCTION:
The RUN command allows the user to initiate task
images
(output
from the RSX-IID Task Builder) that have not been installed. RUN
causes a selected task image to be installed temporarily,
loaded
and executed and removed upon termination.
The task attributes are those specified at task build time.
The
only exception is the task name, which is converted to the first
six characters of the filename.
The task runs under the UIC that the terminal is logged in under.
FORMAT:
RUNbfilename[/TIM=NX]
or
RUNb$filename

where:
filename

is the file specifier for the task image.
contains
a list of defaults in task
specifiers.

Table 5-6
image file

$filename instructs the system that the requested
task
image
resides in a predetermined UFD.
This UFD is defined by
the system manager at system generation time.
Table 5-6
Defaults in Task Image File Specifiers
SPECIFIER

DEFAULT

dev:

SY:

[ufd]

UFD that corresponds to the UIC under which the user

logged on
filename

Must be specified

. type

.TSK

iver

The latest version for the file

5-40

GENERAL USER COMMANDS
OPTION
/TIM=nx
n

is a decimal number indicating the number of time units
(x) of central processor time that the task is allowed.

indicates the type of time unit and can be one
following.
H
M
S
T

the

hour
minutes
seconds
ticks

The amount of time specified must be no greater
than 24 hours.
For example,
24H, l440M, and 86400S are the maximum amounts for
hours, minutes, and seconds, respectively.
If /TIM is not included and accounting is specified for the task,
the maximum amount of processor time allowed is five minutes.
If
the task is still running after five minutes of processor
time
has been used and /TIM was not specified, the system aborts the
task.
EXAMPLE:
MCR>RUN DKl:RICK.TSKi3(D
In this example, task image RICK.TSKi3 is installed, loaded and
executed, and removed upon termination.
RICK.TSKi3 resides in
the user's directory file on DKl:.

5-41

GENERAL USER COMMANDS
5.18

SYSTEM STATUS COMMAND (SYS)

The system status command (SYS) lists on the
terminal
the names of
tasks associated with anyone or all of the following system lists and
queues.
· Active task list (ATL)
· Memory required list (MRL)
· Clock queue (CKQ)
· Global common directory (GCD)
· Checkpointable task list (CTL)
· I/O request queue (IRQ)
· Fixed task list (FTL)
· System task directory (STD)
· Physical unit directory (PUD)
· Task partition directory (TPD)
· SEND/RECEIVE queue (SRQ)
· Asynchronous system trap queue (ASQ)
For each list, SYS prints the list name and the names of all
tasks
that have entries or are entered in that list.
In the case of the SRQ
and ASQ, SYS prints the queue name and the names of all
tasks
that
have nodes in that queue.
The function and content of system lists
and queues are described in the RSX-IID Executive Reference Manual.
SYS can also print the names of shared global areas (SGAs) to which
tasks in the system task directory (STD) are bound and provide
the
following information:
1.

List all installed tasks.

List the device known to the system.

List the partition defined at system generation.

Each list contains information related to the specific category.
FORMAT
SYS [/switch[:opt]]
where:
switch = anyone of the valid switches listed in Table 5-7.
is the default switch.
opt

/BRF

a partition name if /MRL or /CTL is specified, or a
device name and unit number if /IRQ is specified.
No
colon follows the unit number.

5-42

GENERAL USER COMMANDS
Table 5-7
SYS Switches
SWITCH

FUNCTION
li~t.

/ATL

Lists the names of tasks in the active task

/MRL [: opt]

Lists the names of tasks in the memory required
list.
If the output from SYS is to be restricted
to a particular partition, use the opt parameter;
for example, /MRL:GEN indicates that the names of
tasks installed in the GEN partition and contained
in the MRL are to be printed.

/CKQ

Lists the names of tasks in the clock queue.

/GCD

Lists the names of libraries and common
the global common directory.

/IRQ[:opt]

Lists the names of tasks with entries in the
I/O
request queues.
If the
IRQ for a particular
device is desired,
the opt parameter must be
included to designate the device;
for example,
/IRQ:DKO causes the IRQ associated with the DK
handler to be listed.

/CTL [:opt]

Lists the names of tasks in the checkpointable
task list.
If the output from SYS is to be
restricted to a particular partition, use the opt
parameter;
for example, /CTL:GEN indicates that
the names of tasks running in the GEN partition
and contained in the CTL are to be printed.

/FTL

Lists the names of tasks in the fixed task list.

/SRQ

Lists the names of tasks that
for them.

/ASQ

Lists the names of tasks in the ATL that have ASTs
queued for them.

/SGA

Lists the names of all tasks in the STD that are
bound to one or more sharable global area and the
shared global areas to which each is bound.

/BRF

Lists the names of all tasks in the ATL, MRL and
CKQ.
/BRF is used by default if no switches are
included in the SYS command.

/FUL

Lists all of the above
produced by using /SGA.

/TAS

Lists the names of and the following
information
for
installed tasks:
version number, default
partition and priority, task size, and fixed and
multiuser indicators. See Figure 5-5.

5-43

have

except

areas

SENDS

that

queued

which

GENERAL USER COMMANDS
Table 5-7 (Cont.)
SYS Swi tches
SWITCH

FUNCTION

/DEV

Lists the name and PUD address of each symbolic
device known to the system.
On the listing,
devices for which a device handler is resident are
indicated by two asterisks
(**). A redirected
device is followed by the mnemonic of the device
to which it was redirected. Spooled and mounted
(MOU) devices are indicated by the words SPOOLED
and MOUNTED, respectively. The number following a
spooled device is its current forms type.

/PAR

List the following description of each memory
partition in the system:
name, base address
(octal), size
(octal),
and
partition
type.
Partition type can be:
U
S
T

(user-controlled),
(system-controlled, priority-oriented),
(system-controlled, time-scheduled).

Lists the following description of each installed
shareable
global
area:
name, base address
(octal), size, UIC, access, position independent
or blank, creation date.

/COM

NOTE
Each scan performed by SYS inhibits task
switching for a significant period of
time. Therefore, SYS /FUL should not be
issued frequently.

FllACP

V0205

3
GEN

45678
245 021500 DP 0-00000005357 FIXED

Task name

Version number of task

Default partition name

Priority of task

Size of task (octal)

Device identification

Disk address (octal)

Contains the word "FIXED" if the task is fixed in memory, or
CHECKPOINTED" if the task is checkpointed.
Figure 5-5
Sample TASK LIST Listing and Descriptions of Listed Items
5-44

GENERAL USER COMMANDS
EXAMPLES
1.

MCR>SYS /ATL
ATL:

DP •..•

TT ..••

SPR2 .•

DLLEX

DK ....

LP .•.•

MCR>SYS /MRL
MRL:
... MAC

. . • TKB

CRF .••

MCR>SYS /CKQ
CKQ:
NO ENTRIES

MCR>SYS /IRQ
IRQ:
TTO:
... PIP

... FLX

CIO:

NO ENTRIES
COO:

NO ENTRIES
CLO:

NO ENTRIES
SYl:
NO ENTRIES
IPO:

NO ENTRIES

5-45

Os .•.•

OT . . • . . • . MCR

... SYS

MO .•..

GENERAL USER COMMANDS

MCR>SYS /CTL
CTL:
.•• SYS

.•. PIP

DLLEX

MCR>SYS /CTL:GEN
CTL:
..• SYS

DLLEX

MCR>SYS /FTL
FTL:
FIIACP

MCR>SYS /SRQ
SRQ:
NO ENTRIES

NCR>SYS /ASQ
ASQ:
NO ENTRIES

5-46

GENERAL USER COMMANDS
10.

MCR>SYS /SGA
ACCLOG SYSRES
ERRLOG SYSRES
MO •••• SYSRES
SPR .•• SYSRES
SPR2 .. SYSRES
••• ACT PROOT •
.•• BOO SYSRES
... CNF SYSRES
.•• OMP PROOT. SYSRES
..• EOI PROOT. SYSRES
..• FLX PROOT. SYSRES
..• FOR SYSRES
..• INS SYSRES
... LBR PROOT. SYSRES
..• MAC PROOT. SYSRES
..• MCR PROOT •
.. • PIP PROOT. SYSRES
..• QUE PROOT. SYSRES
.•• REM SYSRES
.•• RJE SYSRES
..• SYS SYSRES
.•• TKB SYSRES
..• VFY PROOT. SYSRES
NOTE
PROOT indicates that the task is multiuser and has a
read-only segment in its root. This is the segment
of the task that is shared among all versions of the
task.

11.

MCR>SYS /BRF
ATL:
OP . • • • . • . RJE
MO. . • .

TT ••..

OK .•..

. •. EOI

MRL:
NO ENTRIES
CKQ:
NO ENTRIES

5-47

LP .•..

OS .•••

OT . • . • . . • MCR

.•. SYS

GENERAL USER COMMANOS
12.

MCR>SYS /FUL
ATL:
OP • • • • . . • RJE
MO. • • •

TT •..•

OK ••.•

. •. EOI

MRL:
NO ENTRIES
CKQ:
NO ENTRIES
FTL:
F11ACP
GCO:
SYSRES
CTL:
.•. SYS

.•. MAC

SRQ:
NO ENTRIES
ASQ:
NO ENTRIES
IRQ:
TT:
NO ENTRIES
CI:
NO ENTRIES
OK:
NO ENTRIES
DP:
NO ENTRIES

5-48

LP ••..

OS ••..

OT • • . . . • • MCR

••• S~

GENERAL USER COMMANOS
13.

MCR>SYS /TAS
ACCLOG 0203
CRF ..•
00
OK ••..
06A
OLLEX
03
OP ....
06
OS •...
07
OT .••. V005B
ERRLOG 0321
FIIACP 00225
FIIMSG VOO07
LP .•..
05
MO ..•• V003F
MT •••.
06
POOL
lA
SPR ••• V006A
SPR2 •. V006A
TT ••..
0602
.TKTN. V05
.•• ABO V19
· .• ACT VOl
· •• ALT V05
•• BOO V005C
· •• BYE VOl
· .• CDA 0302
· .• CNF 00003
· •• OEV V15
· •• OLL 01
.•• OMO VOOll
· •• OMP 00004
· •• EDI 06
· •• FIX V19
· •• FLX M04
· •• FOR OYOI
· •• BEL VOl
· •• INI VOO06
· .• INS V0050
· •• LBR X03.4
· •. LOA V14
· •. LUN VI0
· .• MAC 014
· •• MCR V41
.•• MOU V0417
.•• OPE V33
· •• OPR V006A
..• PIP 01320
•.• PWD VOl
· •• QUE V006A
· •• REA V23
· •• REO V25
· .• REM V09
· .• RES V18
· .• RJE 00124
· •• RJP 00124
.•. RUN V004A
· .• SAV 0601
· •. SET V03
· •. SYS lA
· .• TIM V15
· •• TKB 19
• •• UFO V0415

GEN
GEN
GEN
GEN
SYOISK
GEN
GEN
GEN
GEN
GEN
GEN
GEN
GEN
GEN
GEN
GEN
TTY
GEN
MCR
GEN
MCR
GEN
MCR
GEN
GEN
GEN
GEN
GEN
GEN
GEN
MCR
GEN
GEN
GEN
GEN
GEN
GEN
MCR
GEN
GEN
MCR
GEN
GEN
GEN
GEN
GEN
GEN
GEN
MCR
GEN
MCR
GEN
GEN
GEN
GEN
GEN
GEN
GEN
GEN
GEN

235
050
248
050
248
248
248
200
220
200
248
100
248
050
100
090
248
249
221
221
221
098
221
065
250
221
050
075
055
060
221
055
050
221
075
150
050
221
221
050
230
075
221
221
055
221
100
221
221
150
221
250
250
221
221
221
150
221
050
075

5-49

003200 OP 0-00000050241
037300 OP 0-00000045654 MULTI-USER
003400 OP 0-00000046654
027200 OP 0-00000226525
003500 OP 0-00000046775
003400 OP 0-00000047145
004300 OP 0-00000047661
011000 OP 0-00000053135
022700 OP 0-00000054167 FIXEO
004700 OP 0-00000051505
003200 OP 0-00000047753
003600 OP 0-00000053076
005700 OP 0-00000050144
001600 OP 0-00000021630 MULTI-USER
010400 OP 0-00000017347
011400 OP 0-00000021154
014100 OP 0-00000054064
003000 OP 0-00000032265
003300 OP 0-00000021166 MULTI-USER
006300 OP 0-00000024762 MULTI-USER
003300 OP 0-00000022446 MULTI-USER
015000 OP 0-00000006432
000600 OP 0-00000015544 MULTI-USER
057600 OP 0-00000077035
003400 OP 0-00000220017
001600 OP 0-00000016565 MULTI-USER
023000 OP 0-00000173415
005600 OP 0-00000051723
030500 OP 0-00000015511 MULTI-USER
047500 OP 0-00000057131 MULTI-USER
003700 OP 0-00000025707 MULTI-USER
061400 OP 0-00000030017 MULTI-USER
040300 OP 0-00000104543 MULTI-USER
024000 OP 0-00000046313 MULTI-USER
023200 OP 0-00000054104 MULTI-USER
020500 OP 0-00000046341 MULTI-USER
064300 OP 0-00000102327 MULTI-USER
003600 OP 0-00000025767 MULTI-USER
004300 OP 0-00000032330 MULTI-USER
100500 OP 0-00000030572 MULTI-USER
002400 OP 0-00000030170 MULTI-USER
011200 OP 0-00000053014
005300 OP 0-00000045717 MULTI-USER
011500 OP 0-00000030675
030500 OP 0-00000012715 MULTI-USER
006500 OP 0-00000045775 MULTI-USER
022600 OP 0-00000030137 MULTI-USER
004200 DP 0-00000045727 MULTI-USER
002700 OP 0-00000030773 ttlULTI-USER
014300 OP 0-00000046236 MULTI-USER
003200 OP 0-00000046052 MULTI-USER
037400 OP 0-00000227533
037300 OP 0-00000174417
005000 OP 0-00000047442 MULTI-USER
006500 OP 0-00000006451
004600 OP 0-00000046060 MULTI-USER
007300 DP 0-00000046622 MULTI-USER
002300 OP 0-00000032051 MULTI-USER
075700 OP 0-00000062374 MULTI-USER
006400 DP 0-00000051752 MULTI-USER

GENERAL USER COMMANDS
.•• UNF
.•• UNL
••• VFY
.•• WHO
14.

V16
VII
D0520
VOl

MCR>SYS /DEV
TTO 141500
CIO 141562
COO 141644
CLO 141726
SY1 142010
IPO 142072
NTO 142154
SPO 142236
WKO 142320
LP1 142402
XXO 142464
BPO 142546
MOO 142630
DT3 142712
DT2 142774
DT1 143056
DTO 143140
CT1 143222
CTO 143304
CRO 143366
LPO 143450
TT20 143532
TT17 143614
TT16 143676
TT15 143760
TT14 144042
TT13 144124
TT12 144206
TT11 144270
TT10 144352
TT7 144434
TT6 144516
TT5 144600
TT4 144662
TT3 144744
TT2 145026
TTl 145110
MT1 145172
MTO 145254
DSO 145336
DP1 145420
DPO 145502
DK3 145564
DK2 145646
DK1 145730
DKO 146012
SYO 146074

221
221
055
221

MCR
MCR
GEN
GEN

**
TTO
TTO
TTO
DPO
DSO
DSO

**
**
**
** MOUNTED
**

** SPOOLED

**
**
**
**
**
**
**
**
**
**
**
**
**
**
**
** MOUNTED
**
** MOUNTED
**
**
**
**
DPO

5-50

002700
002700
037300
001500

DP
DP
DP
DP

0-00000045307
0-00000046006
0-00000021203
0-00000021174

MULTI-USER
MULTI-USER
MULTI-USER
MULTI-USER

GENERAL USER COMMANDS
15.

16.
17.

MCR>SYS /PAR
SYOISK 113200
MCR
116700
GEN
133700
TTY
735000

003500
015000
601100
014400

MCR>SYS /COM
SYSRES 174600

016400

S
S
U

1,1

RO LIB PI 05/06/75

MCR>SYS /ATL
ATL:
DP • . • . • • . RJE

TT .•.•

OK .•..

MO ••••
18.

MCR>SYS /MRL
MRL:
NO ENTRIES

5-51

LP •.••

OS •••.

DT • . • • . • . MeR

•.• SYS

GENERAL USER COMMANDS
TASK LIST

5.19

TASK LIST COMMAND (TAS)

Refer to the SYS /TAS command in Section 5.18.

5-52

GENERAL USER COMMANDS
TIME

5.20

TIME COMMAND

FUNCTION:
The TIME command (TIM) allows the user to list the time and
on the terminal.
FORMAT:
TIME
EXAMPLE:
MCR>TIME
11/14/74 13:45:00

5-53

date

GENERAL USER COMMANDS
5.21

TERMINAL STATUS COMMAND (WHO)

The terminal status command (WHO) indicates which terminals are in
use, provides the UIC of the user, and indicates whether the user
terminal is privileged or slave. It also indicates those terminals
that were defined during system generation but which are not currently
in use.
FORMAT
WHO
EXAMPLE
MCR>WHO
TTO [l,l]PRIVILEGED
TT 1 [ 101 , 30 ]

5-54

CHAPTER 6
PRIVILEGED USER COMMANDS

Privileged user commands
that appear
to
commands
are
actually
nonprivi1eged
capabilities for the privileged user.

duplicate
commands

A list of the privileged user commands follows.
ABORT

OPEN

ALTER

OPERATE

BAD

PASSvJORD

BOOT

REASSIGN

CANCEL

REDIRECT

DISABLE

REMOVE

DISMOUNT

RUN

ENABLE

SAVE

FIX

SET

INITVOL

TIME

INSTALL

UFD

LOAD

UNFIX

MOUNT

UNLOAD

MEMORY
Commands are presented in alphabetic order.
NOTE
Please
reread
the
Preface
for
explanation of the use of characters
( / [ ] etc.)
tha t
indicate
command
format conventions.

6-1

nonprivi1eged
with enhanced

PRIVILEGED USER COMMANDS
ABORT

6.1

ABORT COMMAND (ABO)

FUNCTION:
The Abort command (ABO) allows the privileged user
the execution of a specified task.

terminate

FORMAT:
ABO[RT]~taskname[/TI=dev]

where:
taskname

is the name of the task being aborted.

/TI=dev

is an optional switch (appended to
the taskname)
which allows the user
to abort any task in the
system, by specifying its TI.
(dev) is the device
mnemonic for the terminal corresponding to the TI
under which the specified task is running.
NOTE
If the requesting task was initiated at
the
requesting
terminal,
or
if the
designated task is not a multiuser
task,
the /TI switch is not required.

EXAMPLES:
1.

MCR)ABO SCAN

MCR)ABO SCAN/TI=TT1S

6-2

PRIVILEGED USER COMMANDS
ALTER

6.2

ALTER PRIORITY COMMAND (ALT)

FUNCTION:
The Alter priority command (ALT) allows the privileged
alter the priority of an active task or tasks.

user

FORMAT:
ALT[ER]Ataskname[/TI=dev]/PRI=nnn[,taskname[/TI=dev]/PRI=nnn, .•• ]
where:
taskname

is the name of the task being altered.

/TI=dev

is an optional switch (appended to
the taskname)
which allows the user to alter the priority of any
task in the system by specifying its TI.
(dev) is
the device mnemonic for the terminal corresponding
to the TI under which the task runs.
NOTE
If the requesting task was initiated at
the
requesting
terminal,
or if the
designated task is not a multiuser
task
the /TI switch is not required.

/PRI=nnn

is the switch used to specify the new task
priority.
nnn is a decimal number ranging from 1
to 250.

EXAMPLE:
MCR)ALT SCAN/PRI=75

6-3

PRIVILEGED USER COMMANDS
BAD

6.3

BAD BLOCKS COMMAND (BAD)

FUNCTION:
WARNING
Any data stored on disk pack will
destroyed
when
the BAD command
executed.

be
is

The BAD BLOCKS command (BAD)
is used
to locate any unusable
blocks on a disk pack.
In addition the BAD command records their
locations in the last good block on the disk prior
to
the
initialization of the disk with the INITVOL command.
The BAD
command maybe executed simultaneously with other RSX-llD tasks
which do not require the disk under test. The detection of bad
blocks is desIrable for any type of disk pack, especially for
multisurface disk packs, which, even when new, may contain
several bad blocks.
The BAD command detects bad blocks by writing a special worst
case pattern in each block of the disk. Then, each block is read
to verify the data. As bad blocks are detected,
the locations
and the number of bad blocks are collected. When all blocks have
been tested, the collected data is written into the last good
block on the disk.
After testing, the following message is printed and BAD exits
MCR:
BAD--TOTAL NO.

OF BAD BLOCKS

= nnnnn

where nnnnn is the total number (decimal)
of bad blocks found in all sets.*
* There can be up to 102 sets of bad blocks.
Each set can
describe from 1 to 256 contiguous bad blocks.
If this maximum of
102 sets is exceeded the following error message is printed:
BAD--BAD BLOCK FILE OVERFLOW
When INITVOL is executed using the IBAD = [AUTO]
option, blocks
identified as bad in the bad block data are allocated so they
cannot be used for data storage. At the same time, the last good
block on the disk pack (which includes the bad block data) is
allocated, saving the data for subsequent initialization
(e.g.,
in case a mistake is made in entering the INITVOL information).

6-4

PRIVILEGED USER COMMANDS
FORMAT:
The BAD command format is:
BAD~dev:

where:
dev:

is the device specifier for the disk under test

EXAMPLE:
MCR)BAD DKl:
BAD--TOTAL NO.

OF BAD BLOCKS=42

In the above example, disk DKI is searched for
bad blocks are detected.

bad

blocks;

ERROR MESSAGES:
Errors detected during BAD processing are reported
to the user
via error messages listed on the user's terminal. These error
messages are detailed in Section A.2.
TECHNICAL NOTES
1.

The disk must be off-line (i.e., not mounted).

The disk must be formatted.

The disk device must be a valid Files-II supported device.

The user will be warned not to use the disk pack as a system disk
if block 0 is found
to be bad (block 0 is used to store the
bootstrap record).

BAD first writes the worst case pattern 26 (decimal) blocks at a
time.
If an error occurs, it then tests each individual block of
the 26.
It is possible for
individual block testing to be
successful, thereby indicating hardware malfunctions on long data
transfers.
As long as the test of individual blocks
is
successful, BAD does not report errors.
The user may notice this situation if error logging is running
while BAD is testing the disk. When BAD reports no bad blocks
and error logging reports errors, the problem is probably in the
disk controller rather than the particular disk volume.

6-5

PRIVILEGED USER COMMANDS
BOOT

6.4

BOOTSTRAP COMMAND (BOO)

FUNCTION:
The BOOTSTRAP command (BOO) allows the privileged user to perform
either of the following mutually exclusive operations.
1.

Stop the present operating system and bootstrap
or another system from any system device.

that

system

Copy a bootstrap block on to block 0 of the specified device
from a specified RSX-llD system image file on the same
device.

FORMAT:
The BOOT command can be specified
in
Each format is discussed separately.

four

different

formats.

Format 1
800[T]

When this format is used, BOOT issues the following prompt:
BOO)
The user must now enter another carriage return.
When executed in this format
the BOOT command causes the latest
version of the file RSX.SAV (residing in the default directory file of
the system disk) to be bootstrapped into memory.
Format 2
BOO[T]~filespec

where:
filespec

is the file specifier for the file that contains,
as
its first record, the bootstrap routine to be
used in re-bootstrapping
the operating system.
Table 6-1 contains a list of default values for
BOOT file specifiers.

When this format is used,
the BOOT command causes the bootstrap
routine
to be loaded from
the file specified by ~filespec".
This
bootstrap routine then loads the remainder of the file
into memory
thus starting up the new RSX-llD system.

6-6

PRIVILEGED USER COMMANDS
Format 3
BOO[T]~/WB

where:
/WB is the write bootstrap switch.
When this format is used, a bootstrap routine is written on block 0 of
the system device.
The bootstrap routine is copied from virtual block
one of the latest version of file RSX.SAV residing
in the default
directory file on the system device.
Format 4
BOO[T]~filespec/WB

where:
filespec

is the file specifier for the file that contains,
as its first virtual block, the bootstrap routine
to be used.
Table 6-1 contains a list of default
values for BOOT file specifiers.

When this format is used, the bootstrap routine which is contained as
the first virtual block, in the specified file, is copied out to block
o of the specified device.
Table 6-1
Defaults In BOO File Specifiers
SPECIFIER

DEFAULT

dev:

SY:

ufd

The UFD which corresponds with
the UIC under which the user logged on

filename

RSX

. type

.SAV

iver

Latest version

TECHNICAL NOTES
1.

All devices, except the one from which the bootstrap operation is
to be accomplished, should be dismounted.

When a re-bootstrap is to
take place,
the currently
system should be quiescent (i.e., no tasks running)

The device from which a task is installed is recorded
in
that
task's STD entry.
Therefore, after bootstrapping a new system,
any installed tasks must be present at the same place on
their
original devices;
e.g., a system pack cannot be moved from DKO
to OKI and then bootstrapped using the BOOT command.

6-7

running

PRIVILEGED USER COMMANDS
4.

Only as much memory as was specified at
loaded during the bootstrap operation.

SYSGEN

The file specified to BOO must have been created by
must not have been moved or copied after creation.

time

will

SYSGEN,

and

EXAMPLES:
1.

MCR)BOO
In this example, the system is re-bootstrapped using the latest
version of the system image file RSX.SAV which resides in the
default directory file on device SY:).

MCR)BOO DKl: [lO,lO]SYS.SAV
In this example, the system is re-bootstrapped using the latest
version of the system image file SYS.SAV which resides in
directory file [10,10] on device DKl:).

MCR)BOO /WB
In this example, a bootstrap routine is copied from virtual block
one of the system image file RSX.SAV (which resides in the
default directory file on SY:) to block 0 of device SY:.

MCR)BOO DKl: [lO,lO]SYS.SAV/VlB
In this example, a bootstrap routine
is copied,
from virtual
block one of the system image file SYS.SAV (which resides in
directory file [10,10] on DKl:) to block 0 of device DKl:.

6-8

PRIVILEGED USER COMMANDS
CANCEL

6.5

CANCEL COMMAND (CAN)

FUNCTION:
The CANCEL command (CAN) allows the
periodic rescheduling of tasks.

privileged

user

cancel

FORMAT:
CAN[CEL]Ataskname[/TI=dev] [,taskname[/TI=dev] , .•. ]
where:
taskname

is the name of the task being canceled.

/TI=dev

is an optional switch (appended to the task name)
which allows the user to alter the priority of any
task in the system by specifying its TI.
(dev) is
the device mnemonic for the terminal corresponding
to the TI under which the task runs.
NOTE
If the requesting task was initiated at
the
requesting
terminal,
or if
the
designated task is not a multiuser
task
the /TI switch is not required.

EXAMPLES:
1.

MCR)CANCEL XKE
Cancels all scheduled requests for task XKE (terminates
rescheduling) •

periodic

MCR)CANCEL XKE,NKlll
Cancels all scheduled requests for
(Terminates periodic rescheduling.)

6-9

task

XKE

and

NKlll.

PRIVILEGED USER COMMANDS
DISABLE

6.6

DISABLE COMMAND (DIS)

FUNCTION:
The DISABLE command (DIS) allows the privileged user
to inhibit
task execution without actually removing
the
task from the
system. Disabled tasks cannot be initiated until
they are
enabled through the ENABLE command issued by a privileged user
(see Sec t ion 6.8).
FORMAT:
DIS[ABLE]~taskname[,taskname, •.. ]

where:
taskname is the name of the task being disabled.
EXAMPLE:
MCR)DIS SCAN,RICK
In this example, the tasks SCAN and RICK are disabled.
Neither
of these
tasks can be initiated until a privileged user issues
the ENABLE command.

6-10

PRIVILEGED USER COMMANDS
DISMOUNT

6.7

DISMOUNT VOLUME COMMAND (DMO)

FUNCTION:
The DISMOUNT VOLUME command (DMO) , for the privileged user,
is
functionally
the
same as for a nonprivileged user;
the
difference is that only a privileged user is allowed to dismount
the system volume.

6-11

PRIVILEGED USER COMMANDS
ENABLE

6.8

ENABLE COMMAND (ENA)

FUNCTION:
The ENABLE command (ENA) reverses
command (see Section 6.6).

the

effects

the

DISABLE

FORMAT:
ENA[BLE]~taskname[,taskname, ..• ]

where:
is the name of the task being enabled.

taskname
EXAMPLE:
1.

~CR)ENA

SCAN

MCR)ENA SKE,RICK,JEN
In the examples above,
tasks SCAN, SKE, RICK,
enabled, thus making them available for execution.

6-12

and

JEN

are

PRIVILEGED USER COMMANDS
FIX

6.9

FIX-IN-MEMORY COMMAND (FIX)

FUNCTION:
The FIX-IN-MEMORY command (FIX) allows the privileged user to FIX
a
task in its default partition;
i.e., to dedicate memory to a
task for faster response to requests for execution.
The user
cannot FIX a task unless it was built as a fixable task.
FORMAT:
FIX~taskname [/TI=dev] [, taskname [/TI=dev] , ••. ]

where:
taskname

is the name of the task being fixed in memory.

/TI=dev

is an optional switch which specifies the TI under
which the task is to be fixed.
dev is the device
mnemonic for the terminal corresponding to the TI
under which the task is to run.

EXAMPLES:
1.

MCR>FIX XKE

MCR>FIX JAG,240Z
In the examples above, the tasks XKE, JAG, and 240Z are fixed
their default partitions.

An SGA can be fixed in memory by writing a dummy task
that uses
that SGA.
The dummy task should be built with the following
options, which are described in Chapter 3 of the RSX-llD Task
Builder Reference Manual:
/-CP /-FP /FX
STACK = 10
UNITS = 0
LIBR = sga name

COMMON

sga name

Example of dummy task:
. fiiCALL EXIT$C
START:
EXIT$C
END START

in case task is executed

The dummy task uses 96 words;
this includes the task header and
mInImum stack size, plus one FTL entry. The above approach is
the optimal solution to fixing an SGA.
Fixing the dummy task guarantees the loading and fixing of
the
SGA it uses.
Both the task and SGA should be installed in the
same partition.

6-13

PRIVILEGED USER COMMANDS
INITVOL

6.10

INITIALIZE VOLUME COMMAND (INI)

WARNING
Any data stored on the volume will be destroyed when
is executed.

INI

FUNC'I'ION:
The INITIALIZE VOLUME command (INI) provides the privileged user
with a
facility for producing new Files-II structured volumes.
Files-II structured volumes are discussed in detail in the
IAS/
RSX-1l I/O Operations Reference Manual.
---FORMAT:
INI[TVOL]~dev: [volumelabel] [/keyword(s)]

where:
dev:

is the device specifier for
media.

any

file

structured

volumelabel

is the label being assigned to the volume.
NOTE
to
12
Volume labels can be from 1
alphanumeric characters in length. The
only exception is magnetic
tape volumes
which
are
from I
to 6 alphanumeric
characters in length.
Volume label must
magnetic tape.

/keyword(s)

specified

for

define the volume characteristics.
If no keywords
are specified,
the default characteristics are
used (see individual keyword descriptions).
The
following keyword options are provided.
NOTE
Notations listed to the left of
options, equate to the following:

keyword

*= Valid for disk and DECtape only
**= Valid for magnetic tape only
/UIC=[group number,mernber number]

6-14

PRIVILEGED USER COMMANDS
Default
/UIC=[l,l]
/PRO=[system,owner,group,world]
This keyword allows the user
to establish
volume
access
privileges.
Each
entry
consists of from one to four letters which
have the following meanings:
R - for READ access
W - for WRITE access
E - for EXTEND access
D - for DELETE access
The absence of a code letter means the access
right is denied to the user.
Protection
code
subparameters
(system,owner, group,world)
are positional;
therefore, the location of the entry in the
parameter string defines the user to whom the
codes apply.
Example
/PRO=[RWED,RWED,RW,RW]
In this example, group and world
extend and delete access.

are

denied

Default
/PRO=[RWED,RWED,RWED,RWED]
NOTES

On magnetic tape,
the
protection
option delete is equated to write,
since write access implies
total
access
because of tne sequential
nature of magnetic tape.

Extend access
may
be
specified
without write access. This implies
that the user may extend the last
file on the volume, but not write on
the volume in any other manner.

/MXF=maximum number of files allowed on this
volume. The highest maximum permitted is one
half the number of blocks on the volume or
65535 decimal, whichever is less.

6-15

PRIVILEGED USER COMMANDS
Example
/MXF=lOO
Default
One fourth the number of blocks
volume

the

same

/EXT=default file extension size in blocks.
Defaul t
/EXT=5

/FPRO=[default file protection]
This parameter is entered
format as the /PRO keyword.

using

Defaul t
/FPRO=[RWED,RWED,RWE,R]

/CHA=[characteristic words]
This
keyword
defines
the
device
characteristics. The possible parameters for
this keyword follow.
ATCH - device may
be
attached
exclusive use by one task.
DCF

- device
control
permitted;
e.g.,
logical.

for

functions
Read/Write

Example
/CHA=[ATCH,DCF]
Defaul t
No ATCH and no DCF

/INF=number of file headers
initial index file.

allocate

the

Defaul t
/INF=16

/WIN=default window size for file access to this
volume.
Represents the number of retrieval
pointers.
Default
/WIN=7

6-16

PRIVILEGED USER COMMANDS

/LRU=number of direct.ories to keep pre-accessed
while
volume
is in use.
For optimized
directory access this
value
should
be
slightly higher
than the expected number of
concurrent users of the volume.
Default
/LRU=3

/DENS=magnetic tape density
Enter 800 for 800 BPI, or 1600 for 1600 BPI.
Defaul t
/DENS=800

/INDX=Option - Index file position.
Options are:
BEG - beginning of volume
MID - middle of volume
END - end of volume
BLK:number - logical block number
Example
/INDX=BLK:100
Defaul t
/INDX=MID
/BAD=[options]-Initialize bad block file.
are:

Options

AUTO - use bad block data left on volume
by BAD command (see Section 6.3).
MAN

- enter bad
blocks
in
format
described in section 6.10.1.

If both options are
separated by a comma.
Example
/BAD=[AUTO]
or
/BAD=[AUTO,MAN]
Defaul t
none

6-17

used,

they

must

PRIVILEGED USER COMMANDS

6.10.1

MAN Option for /BAD Keyword

When "MAN" is specified as the /BAD Keyword option, INI will issue the
following prompt:
INI)BAD=
This prompt is issued after the INI command line is terminated,
before INI begins processing (initializing) the requested volum~.

and

After INI issues the prompt, the user can begin entering bad block
location data.
Bad block data is entered immediately following the
equal sign (=) in the following format.
INI)EAD=u [ ,n]
where:
u

is the logical block number,
in
initial bad block in the group.

octal,

the

is the number, in oc tal, of consecutive blocks
contained in the group.
If omitted, a value of
one is assumed.
NOTE
If a decimal number is used for either u
or n,
it must be followed by a decimal
po in t (.).

After the first group of bad blocks is entered, INI reissues the
prompt. The user can, if necessary, enter more bad block data by
simply repeating the above procedure.
To terminate,
the user need only enter a carriage return
immediately following the equal sign (=) without entering data.
Upon termination, the initial INI command line, including the bad
block
data,
is
processed,
and the requested volume is
initialized.
TECHNICAL NOTES
Because of the large number of options available with the INI
command,
it may not be possible to enter the entire command
string on a single line. For this reason, INI has been modified
to accept multiline commands. To accomplish this, the user must
follow the procedure outlined below.
1.

MOU must be initiated as follows:
MCR)INI
When INI is ready to
prompt is issued.

INI)

6-18

command

lines,

the

following

PRIVILEGED USER COMMANDS
2.

At this point, multiple lines can be typed in to INI.
Each
line except the last must contain a hyphen (-) as the last
character entered.
When INI recognizes the hyphen,
it
assumes that the command line is incomplete, and reissues the
INI) prompt for more parameters.
When the last line is
entered
(no hyphen), INI begins processing the command. See
example number 3.

EXAMPLES:
1.

MCR)INI DK1:TESTPACK/CHA= [ATCH,DCF]/BAD= [AUTO]
In this example, a disk volume on OK1:
following characteristics:

Volume label

- TESTPACK

UIC

Volume Protection

- System

RWED

Owner

RWED

Group

RWED

World

RWED

is initialized

with

the

[1,1]

Maximum number of
files

- 1200

Default file extension

- 5

File protection

- System

RWED

Owner

= RWED

Gtoup

= RWE

WORLD

Characteristic word

- ATCH and DCF

Index file position

- MID

Bad blocks

- Automatically accounted for.

Number of headers
in index file

- 16

Window size

- 7

Number of pre-accessed
directories

- 3

MCR)INI DK1:TESTPACK/PRO=[RWED,RWED,RW,R]/CHA=[ATCH,DCF]/BAD=[ MAN]
INI)BAD=6.,10.
INI)BAD=12.
INI)BAD=

6-19

PRIVILEGED USER COMMANDS
In the above example, a disk volume on DKl:
the following characteristics.

Volume label

- TESTPACK

UIC

- [1,1]

Volume protection

- System

RWED

Owner

RWED

Group

World

Maximum number of
files

- 1200

Default file extension

- 5

File protection

- System

RWED

Owner

RWED

Group

RWE

~vorld

is initialized

Characteristic word

- ATCH and DCF

Index file position

- MID

Bad blocks

- 6 through 17, and 12

Number of headers
in index file

- 16

Window size

Number of pre-accessed
directories

- 3

with

MCR>INI
INI> DK2:FREDjUIC=[30l,275]/LRU=2INI> /PRO=[RWED,RWED,R,]/INDX=BEGINI> /MXF=lOOO.
MCR>
In the above example, a disk volume DK2:
following characteristics:

6-20

is initialized with the

PRIVILEGED USER COMMANDS
Volume label

- FRED

UIC

Volume protection

- System

RWED

Owner

RWED

Group

World

No access

[310,275]

Maximum number of
files

- 1000.

Default file extension

File protection

- System

RWED

- Owner

RWED

- Group

RWE

- World

Characteristic Word

- No ATCH and no DCF

Index file position

- BEG

Bad blocks

- Not accounted for

Number of headers in
index file

- 16

Window size

- 7

Number of pre-accessed
directories

- 2

6-21

PRIVILEGED USER COMMANDS
INSTALL

6.11

INSTALL TASK COMMAND (INS)

FUNCTION:
The INSTALL TASK command (INS) installs tasks and sharable global
areas
(SGAs) in the system.
It can also override or extend some
of the attributes assigned to
the task by the
task builder.
These overrides are specified in the form of keyword parameters
appended to the task image file specifier(s) in the INS command
line.
FORMAT:
INS [TALL] ~f ilespec [/keyword (s) ] [ , filespec [/keyword (s) ] , .•. ]
or
INS[TALL]~@indirect

where:
filespec

is the file specifier for
the image
(task or
sharable global area) being installed. Table 6-2
contains a list of
defaults
in
INS
file
specifiers.

/keyword (s)

option parameter(s) used
to override or extend
arguments
assigned
at task-build
time.
The
following keyword options are provided:
/PAR=partition name
This option specifies the
which the
task or global
installed.

partition into
area
is to be

On the installation of a sharable global area
(SGA)
INSTALL will recognize
the special
pseudo partition name $$$EXT, and will align
that SGA on the external page in real memory.
Furthermore, the SGA will be flagged as if it
were loaded but no actual load will occur.
This function allows a
task
to bind to a
area, for example, and reference
common
locations symbolically in the external page.
Example
/PAR=GEN
/PAR=$$$EXT

(for SGAs only)

Defaul t
In order:
The partition specified when
the task or SGA, or if none,

6-22

building

PRIVILEGED USER COMMANDS
The partition specified as
during system generation.

the

default

jPRI=priority-number (decimal)
This option specifies the execution priority
to be assigned to the task.
Priority ranges
from a low of 1 to a high of 250.
Example
jPRI=200
Defaul t
jPRI=50
jTASK=taskname
This option allows the user to assign a name
This
to the
task or SGA being installed.
name overrides the one assigned by the Task
Builder.
Task names can be from 1 to 6
alphanumeric characters in length.
Example
jTASK=RICK
jPOOL=pool-limit (decimal)
This option allows the user to assign a
pool limit to the task being installed.

new

The pool limit value can be from 0 to 255
decimal, and represents the maximum number of
8-word nodes that the task is allowed to use
at one time.
Example
jPOOL=lOO
Defaul t
jPOOL=40 (established by task builder)
jUIC=[uic]
This option allows the user
to change
task's UIC, or the owning UIC of an SGA.
Example
jUIC=[ll,ll]

6-23

the

PRIVILEGED USER COMMANDS
/RUN[=REM]

(run-remove)

This option is different from the above
mentioned options, in that it does not change
any task attributes. When /RUN is specified,
it directs INS to install the specified task
and run it.
If the optional subparameter
li=REM"
is
appended to /RUN, it specifies that the named
task is to be removed after execution.
/TIM=allowable run time expressed as nH,
or nT.

nM,

nS,

This option allows the user
to specify the
length of time the task is allowed to run. n
is the decimal number of hours, minutes,
seconds, or ticks the task is allowed to run.
Hours, minutes, seconds,
or
ticks
are
represented as H, M, S, or T, respectively.
Example
/TIM=20M

(task is to run 20 minutes)
NOTE

This keyword has no effect if system
accounting is not running, or if the
task being installed was task built
as a non-accountable task.
In the
latter case, however, a diagnostic
message is issued. See Chapter 2 of
the RSX-llD System Manager's Guide.

/ACC=non-owner access expressed as RO, RW, or NA
This switch allows the user to specify the
access privileges afforded non-owners of a
specified SGA. A non-owner of a SGA is one
whose UIC does not exactly match that of the
SGA. RO, RW, and NA equate to read only,
write only, no access, respectively.
Example
/ACC=RO
Default
/ACC=NA

6-24

PRIVILEGED USER COMMANDS
/LI and /CM
These options are used to specify that the
entity being installed is either a library
(/LI) or a common area (/CM). By definition,
a
common
area
has
read/write access.
Application of the /CM switch ensures that
such data is written back to the SGA file
when all binding tasks become inactive.
See
Chapter 5 of the RSX-llD System Manager's
Guide.
Default
/CM
NOTE
Install determines that the
file
being installed is a sharable global
area. The switches /ACC, /LI, and
/CM
have
no
effect
on
the
installation of ordinary tasks.
/INC=task size increment
This switch overrides the EXTTSK task builder
option.
It specifies the decimal number of
words by which the upper read/write area of
the task is to be extended.
The value
specified will be rounded up to the next 32
word boundary.
This option is illegal for
shareable global area.
Example
/INC=2048
Allocates as additional
address space.

the

task's

Chapter 7 or
the RSX-llD Task Builder Reference
describes the building of a shareable global area.

Manual

All SGAs to which a task is bound must be installed before
the task is installed.
They need not be installed before
building the task.

Default
Either 0 or the EXTTSK value.
TECHNICAL NOTES:

6-25

PRIVILEGED USER COMMANDS
Table 6-2
Defaults in INS File Specifiers
SPECIFIER
dev:

DEFAULT
If omitted in the first or
SY:
is used.

only

file

specifier,

If omitted in the
second
through
n
file
specifiers, the device specified or defaulted from
the previous file specifier is used.
[ufd]

If omitted in a file specifier,
the UFD that
corresponds to the UIC under which the user logged
on is used.

filename

Must be specified •

. type

.TSK

iver

The latest version for the file.

EXAMPLES:
1.

MCR)INS SCAN
In this example, the latest version of the
task image file
SCAN.TSK is selected, and
the task image which it contains is
installed. None of the task attributes that were assigned to the
task at task-build time are changed.

MCR)INS DK1:[11,2]SCAN.;3/PRI=103,RICK/TASK=HELP
In this example, the tasks to be installed reside in directory
file [11,2] on DK1:.
Version;3 of task image file SCAN.TSK, and
the latest version of task image file RICK.TSK are selected. The
task images contained in these files are installed into the
system, with the following modifications being made to them.
Task image SCAN will have its priority changed to 103, and task
image RICK will have its name changed to "HELP".

6-26

PRIVILEGED USER COMMANDS
LOAD

6.12

LOAD COMMAND (LOA)

FUNCTION:
The LOAD command
(LOA)
allows the user
to specify that an
indicated device handler be made resident in memory and ready for
service. I/O requests to a device are not honored unless the
requested device handler is resident.
FORMAT:
LOA[D]~handler-name[:]

where:
handler-name

is the task name of the handler to be loaded.

EXAMPLE:
MCR>LOAD LP
The line printer device handler
requests to the LUN assigned
honored.

6-27

is
to

loaded
into memory.
I/O
the line printer can now be

PRIVILEGED USER COMMANDS
MEl-10RY

6.13

MEMORY UNLOCK (MEM)

FUNCTION:
The MEMORY UNLOCK command allows the user to ~nlock tasks
that the
Executive locked in memory as a result of a main memory parity error.
Parity error handling is discussed in The RSX-IID System Manager's
Guide.
FORMAT:
MEM[ORY]ll[taskname] [/switches] [,taskname[/switches]] [, ••• ]
taskname

is optional.
If specified, it is the name of the
task to be freed.
MEM searches the ATL and
unlocks the first locked task encountered with the
specified name. The task name must be included if
a series of specifications are included in' the
command.

switches

can be either or both of the following options.

/TI=xxn

indicates that the first locked
task encountered
in the ATL with the specified TI
is to be
unlocked. The value xxn is the device mnemonic;
for example, TT3.
If both taskname and TI are specified in the MEM
command,
the first locked task encountered in the
ATL with the specified taskname and TI assignment
is freed.
indicates that all locked tasks are to be freed.
If both taskname and /AL are specified, all locked
tasks with the specified taskname are freed.

/AL

If both /TI and /AL are specified, all
tasks with the specified TI are freed.

locked

If taskname, /TI, and /AL are specified, all
locked tasks with the specified taskname and TI
are freed.
EXAMPLES:
MCR)MEM

/AL

MCR)MEM ABC/TI

6-28

PRIVILEGED USER COMMANDS
MOUNT

6.14

MOUNT VOLUME COMMAND (MOU)

The MOUNT volume command (MOU) for the privileged user has the same
format as MOU for the nonprivileged user.
The privileged user does,
however, have three switch options that are not available to
the
nonprivileged user. These options are as follows:
jUIC=[uic]
This option specifies the volume UlC to be
used for
the duration that the volume is
mounted.
Example
jUlC=[ll,ll]
jOVR
This switch allows the user to
volume label check.

override

the

NOTE
This option must be specified when
mounting magnetic
tapes with blank
volume labels.

jPRO=[system, owner, group, world]
This option allows the user
to change
the
volume
access
privileges.
Each
entry
consists of from one to four letters which
have the following meanings.
R - for READ access
W - for WRITE access
E - for EXTEND access
D - for DELETE access
The absence of one of these letters in an
entry signifies that the access right is
denied to the user.
Protection code subparameters (system, owner,
group, world) are positional;
therefore, the
location of an entry in the parameter string
defines the user to whom the codes apply.

6-29

PRIVILEGED USER COMMANDS
Example
/PRO=[RWED,RWED,RW,RW]
In this example, group and world
extend and delete access.

are

denied

EXAMPLE:
MCR>MOU DKl:SYS004/UIC=[200,200]
In this example, a request is made to mount disk volume SYS004 on
DKl:. A request is also made to replace the volume's default UIC
with "[200,200]".

6-30

PRIVILEGED USER COMMANDS
OPEN

6.15

OPEN REGISTER COMMAND (OPE)

FUNCTION:
The OPEN Register command (OPE) allows the privileged user
to
open a memory address
(gain access to it) for examination and
optional modification.
the
When a location is opened the specified memory address and
contents of the address are listed on TI:. The format of this
message is shown in Figure 6-1.
FORMAT:
OPE [N]~memory address [+or-n] [/opt.ion (s)]
where:
memory address address (octal)

is the location to be opened.

is an optional number to be added
to
the memory
address,
if positive, or subtracted from the
memory address, if negative.

/option (s)

The following options specify the address space to
which the memory address applies:
NOTE
If no option is specified, the address is
interpreted as an absolute memory address.
If an option is specified, the address is
interpreted as a virtual address within
the specified address space.
/TASK=task name [/TI=dev]
/PAR=partition name
/KNL=specifies kernel virtual address
space

6-31

PRIVILEGED USER COMMANDS
FORMAT
memory-address contents/new-value or line-terminator
where:
memory-address

(printed by the system)
virtual address

is the

6-digit

(octal)

contents/

(printed by the system) is the 6-digit
(octal)
value at the memory-address, followed by a slash
(/)

new-value

(typed in by user) is the new value entered into
the memory-address

line-terminator

(typed in by user) is one of the optional line
terminators: see list of line terminators below
Line Terminator Options

ESC

- ESCape or ALTMODE: end of command.
The ESC
(or
ALTMODE)
key is the only means of exit from the
OPEN MCR function.

- carriage return:
opened.
-

up~arrow

return:

the next sequential location

the previous location is opened.

asterisk carriage return:
the location pointed to
by the final contents of the opened location is
opened.

*CR

Figure 6-1
Format of Open Register Command Output
EXAMPLES:
1.

MCR)OPEN 4 10/KNL
000014 060014/350
000016 071005/@
In this example, the value of the memory address is 4, "n" equals
10
(a positive number
that is added
to
the memory address
yielding the effective address ~000014").
The option specified
is Kernel Virtual. The System responds by printing the address
(000014) and the contents of the address (060014), followed by a
slash.
The user responds by en ter ing
the new val ue 11350 II ,
followed by a carriage return.
Terminating the line by a
carriage return causes the next sequential location to be
displayed. The dialogue is then terminated by entering ALTMODE.

MCR)OPEN 4/TASK=ABC
000004 111111/

6-32

PRIVILEGED USER COMMANDS
In this example, memory location 4 of task "ABC" is opened.
The
memory address
(000004)
and its contents (111111) are printed.
After examining the contents of this address,
the operator can
either enter a new value or examine other locations by typing one
of the line terminator options.
3.

MCR)OPE 4
000004 0305/20054

In this example, absolute location 4 is displayed,
to con ta in "20054".

6-33

and

modified

PRIVILEGED USER COMMANDS
OPERATE

6.16

OPERATE COMMAND (aPR)

The OPERATE command (aPR), for the privileged user, has the same
format as aPR for the nonprivileged user. The privileged user does,
however, have three switch options that are not available to the
nonprivileged user. These options are described in Table 6-3.

Table 6-3
Operate Option Switches
SWITCH

DESCRIPTION

/CHG

Set the forms type in the PUD of the specified
When printing of the current file
device to 7.
has completed, the user can mount new forms on the
device and queue a test pattern file to test for
forms alignment (see QUE command option ITE,
section S.lS.)

IFO:n

Set the forms type in the PUD of the specified
device to n (where n is a decimal number ranging
from 0 to 6) • Processing of files requlr1.ng the
specified
forms type and device type begins
automatically.

IRE

Recycle all ac tive orders and requeue them as
Au toma t ically begin processing queued
inact.ive.
files, directed to the specified device, having
matching forms types.

6-34

PRIVILEGED USER COMMANDS
PASSWORD

6.17

ENTER PASSWORD COMMAND (PWD)

The ENTER PASSWORD command (PWD) is functionally the same for
the
privileged user as it is for
the nonprivileged user, with this
exception:
the privileged user can change the password for any UFD on
any volume that is not protected against system access.

6-35

PRIVILEGED USER COMMANDS
QUEUE

6.18

QUEUE COMMAND (QUE)

FUNCTION:
The QUEUE command for the privileged user has the same format as
the
QUE command for
the nonprivileged user. The privileged user does,
however, have the option of deleting (/KIL) or modifying any queued
entry in the Queue Manager tasks queue.
The ~ormat of the delete or modify command is identical
to the
nonprivileged delete or modify command format.
The only important
distinction is that any privileged user that modifies a queued entry
becomes the owner of the modified entry.

6-36

PRIVILEGED USER COMMANDS
REASSIGN

6.19

REASSIGN CCMMAND (REA)

FUNCTION:
The REASSIGN command
(REA)
allows the operator to
logical unit numbers
(LUNs)
of a particular
task
physical device unit, and assign them to another.

reassign
from one

FORMAT:
REA[SSIGN]~taskname~lunlist~devunit:

where:
taskname

name of the task whose LUNs are being reassigned.

lunlist

list of one or more logical unit numbers separated
by commas.

devunit

new device
number.

unit

symbol

followed

the

unit

EXAMPLES:
JO~

MCR)REASSIGN

3 TTO:

MCR)REA BILL 2,3,4 TTl:

MCR)REA SAM 5 NONE
In the examples above, the requests are to:
1.

REASSIGN, in task JOE, logical unit number 3 to device TTO.

REASSIGN, in task BILL, logical unit numbers 2, 3
device TTl.

REASSIGN, in task SAM, logical unit number 5 to NONE.
If 5
was previously assigned to LPO, for example, nothing would be
printed on LUN 5.

and

TECHNICAL NOTES:
1.

The REASSIGN command
task's disk image.

performs

The REASSIGN command does not affect a memory-resident task.

Removing and re-installing a task will restore its LUNs to
original assignments specified at task build time.

6-37

reassignments

the

indicated

their

PRIVILEGED USER COMMANDS
REDIRECT

6.20

REDIRECT COMMAND (RED)

FUNCTION:
The REDIRECT command (RED) allows the operator
to redirect all
I/O requests from one physical device unit to another.
This
command can be used if one of the I/O units needed for a task
is
inoperable for some reason.
FORMAT:
RED[IRECT]~new~dev:=old-dev:

where:
new-dev:

is the new device unit symbol,
followed
optional unit number (zero is assumed).

is notation signifying the redirect action.

old-dev:

is the old device unit symbol,
followed
optional unit number (zero is assumed).

NOTE
TI: cannot be designated as old-dev,
it can be designated as new-dev.

but

EXAMPLES:
1.

MCR)REDIRECT TT3:=TT6:

MCR)RED TT=LP:

MCR)RED LP:=LP:
In the examples above the requests:

Redirect all I/O requests from device TT6 to device TT3;

Redirect all I/O requests from device LPO to device TTO.

Reverse the redirection specified in example 2.

TECHNICAL NOTES:

The RED command does not redirect any I/O already in
Previous I/O requests are not transferred.

If, through a sequence of Redirect commands, the user establishes
a redirect chain which returns to old-dev, the following message
is issued, and the RED command is rejected:
RED -- CIRCULAR REDIRECT CHAIN

6-38

the

queue.

PRIVILEGED USER COMMANDS
Example:
MCR)RED TT2:=TTl:
MCR)RED TT3:=TT2:
MCR)RED TTl:=TT3:
RED -- CIRCULAR REDIRECT CHAIN

6-39

PRIVILEGED USER COMMANDS
REMOVE

6.21

REMOVE COMMAND (REM)

FUNCTION:
The REMOVE command (REM) allows the privileged user
inactive, unfixed task out of the system.

take

It also allows the removal of sharable global areas whose binding
tasks are not installed.
FORMAT:
REM [OVE]llnamel [/switch] [,name2 [/switch] , .•• ]
or
REM[OVE]ll@indirect
where:
name

is the name of a
being removed.

/swi tch

an optional switch used to identify sharable
global areas to be removed. The following switch
values are available for use:

@ind irec t

task

sharable

global

area

/LI

identifies the named
being a library.

global

area

/CM

identifies the named
being a common area.

global

area

file

is an indirect command file specifier for
which contains a list of REMOVE commands.
NOTE

Three levels of indirection are supported.
EXAMPLES:
1.

MCR)REM SCAN
In this example, the task SCAN is removed from the system.

MCR)REM SCAN,XKE,JAG
In this example, tasks SCAN, XKE, and JAG are
system.

removed

from

the

In this example, the library "S0MLIB" is removed, providing
none of its binding tasks are installed.

that

MCR)REM SOMLIB/LI

6-40

PRIVILEGED USER COMMANDS
RUN

6.22

RUN COMMAND (RUN)

FUNCTION:
The RUN command allows the privileged user to initiate
any of six different forms as follows:
execution

task

tasks

memory

when

becomes

Request the
available.

Execute a task, contingent upon immediate memory availablity

Run a task at a specified future time and, optionally,
it periodically

Schedule the task for running at a specified future time and,
optionally, rerun it periodically

Synchronize the running of a
task
optionally, rerun it periodically

Run a task that is not installed in the system.
the RUN command is described in section 5-17.

with

time

rerun

unit

This form of

NOTE
1.

If the user is running an uninstalled
switch options available for use are

task, the only

jUlC=, jPAR=, jPRl=.
2.

The default UIC for the general user is the UIC under
which the user logged on. For the privileged user,
the default UIC of the task being run is used.

6-41

and,

PRIVILEGED USER COMMANDS
RUN
REQUEST form of command
The "Request " form of the RUN command
request the execution of tasks.

allows

the

operator

NOTE
If memory is not available, the task will be queued until
memory becomes available.
FORMAT:

RUN~taskname[options] [,taskname[options] , ... ] ~
where:
taskname

is the name of the task being run

options

are any of the following:
/PRI

priority number

(decimal)

/PAR

partition name

/UIC

[user identification code]

EXAMPLES:
MCR>RUN SCAN~
MCR>RUN SCAN/PAR=XYZ/PRI=5SG)
l<lCR>RUN XKE, NKlll/PRI=lO, SCAN
MCR>RUN XKE/UIC=[ll,l]

TECHNICAL NOTE:
contingent

upon

priority

Execution
is
availability.

See Section 4.2 for a description of the UIC under which
task will run.

6-42

and

memory

the

PRIVILEGED USER COMMANDS
RUN
EXECUTE form of command
The "Execute" form of the RUN command allows task execution contingent
upon priority.
NOTE
If no memory is available
in
specified
or default partition,
request is rejected.

the
the

FORMAT:

RUN~taskname/MEM[/options] [,taskname/MEM[/options] , •.• ] ~
where:
taskname

is the name of the task being run

options

are any of the following:
/PRI

priority number

/PAR

partition name

/UIC

[user identification code]

EXAMPLES:
MCR>RUN SCAN/MEM®
MCR>RUN SCAN/MEM/PRI=lOO/PAR=XXX/UIC=[l,3]

MCR>RUN SCAN/MEM/PRI=25,240Z/PAR=Z/PRI=99G)
TECHNICAL NOTES:
1.

Execution is contingent upon priority.

The t, Execute"
form of
checkpointing to occur.

the

RUN

6-43

command

does

not

cause

PRIVILEGED USER COMMANDS
RUN
RUN form of command
The "Run" form of the RUN command allows the operator to schedule
tasks in terms of "delta time from now" with the option to
specify periodic reschweuling,
run
priority,
and
memory
partition.
FORMAT

RUN~taskname~time[options] [,taskname~time[options] , .•. ]

where:
taskname

is the name of the task being run

time

is the "delta time from now" the task is to begin
execution. Delta time is expressed as nH, nM, nS,
or nT where n is the decimal number of hours,
minutes, seconds, or ticks.

options

are any of the following:
/RSI

reschedule interval expressed as nH,
nM, nS, or nT

/PRI

= priority number

/PAR

partition name

/UIC

[user identification code]

(decimal)

EXAMPLES:
1.

MCR>RUN XKE 15M@

MCR>RUN XKE 15M/RSI=90S/UIC=[3,1]G)

MCR>RUN XKE 15M/RSI=GOS/PRI=150/PAR=XYZ~

MCR>RUN XKE 15M,NKlll 20M,240Z 25M®
In the examples above, the requests are to:

Run task XKE 15 minutes from now

Run task XKE 15 minutes from now, rescheduling
seconds. The user identification code is [3.1]

Run task XKE in 15 minutes, rescheduling it every 90 seconds,
assigning it a priority of 150, and running it in partition XYZ.

Run task XKE in 15 minutes, run task NKlll in 20 minutes, and run
task 240Z in 25 minutes.

6-44

every

PRIVILEGED USER COMMANDS
RUN
SCHEDULE form of command
The "Schedule" form of the RUN command allows the operator
to
schedule tasks in terms of absolute time of day, with the option
to specify periodic rescheduling, run priority, and memory
partition.
FORMAT:

RUN~taskname~time [options]

where:
taskname

is the name of the task being run

time

is the absolute time of day the task is to begin
execution.
Time is expressed as hours: minutes:
seconds [:ticks]

options

are any of the following:
/RSI

reschedule in terval, expressed as nH,
nM, nS, or nT.

/PRI

priority number

/PAR

partition name

/UIC

[user identification code]

EXAMPLES:
1.

MCR>RUN XKl l2:23:l5G)

MCR>RUN XKE l2:00:00/RSI=6M/PRI=99/PAR=XYZG)

MCR>RUN SCAN 23:30:00/RSI=lOM/PRI=200G)

MCR>RUN XKE 1:OO:OO,240Z 1:30:00/UIC=[111,1]G)
In the examples above the requests are to:

Schedule task XKl at 12:23:15.

Schedule task XKE at 12:00, reschedule it every six minutes,
assign it a priority of 99, and execute it in partition "XYZ".

Schedule task SCAN at 23:30, reschedule
assign it a priority of 200.

Schedule task XKE at 1:00, task 240Z
identification code of [111.1]).

6-45

it
at

every
1:30;

ten

minutes,

(with

user

PRIVILEGED USER COMMANDS
RUN
SYNCHRONIZE form of command
The "Synchronize" form of the RUN command allows the operator
to
synchronize the scheduling of a task in terms of delta time from
. clock unit synchronization", with the option to specify periodic
rescheduling, run priority, and memory partition.
FORMAT:

RUN~taskname~startime~+time[options] G)
where:
taskname

is the name of the task being run

star time

is the synchronization clock unit as follows:
H

synchronize on the next hour.

synchronize on the next. minute.

synchronize on the next second.

synchronize on the next. tick.

time

is the delta time increment that is added
to
the
synchronization clock unit yielding
the actual
st.art time.
Time is expressed as nH, nM,
nS, or
nT where n
is the number of hours, minutes,
seconds, or ticks.

options

are any of the following:

/RSI

rescheduling interval expressed as nH,
nM, nS, or nT

/PRI

priority number

/PAR

part.ition name

/UIC

[user identif ication code]

EXAMPLES:
MCR>RUN NKlll H+IOMG)
MCR>RUN NKlll S+10M/PRI=10,240Z M+OS/RSI=15S/PRI=90@
In the example above the requests are t.o:
1.

Synchronize task NKlll, schedule for 10 minutes
hour.

Synchronize task NKlll, schedule for 10 minutes after
the next
second, assign it a priority of 10; Synchronize task 240Z,
schedule it for 0 seconds after the next minute, rescheduling it
every 15 seconds, and assign it a priority of 90.

6-46

after

the

PRIVILEGED USER COMMANDS
SAVE

6.23

SAVE COMMAND (SAVE)

WARNING
The SAVE command should be executed only
when the system is quiescent.
FUNCTION:
THE SAVE command is used to record the core image of an RSX-IID
system on the disk from which it was originally bootstrapped, so
that a bootstrap can reload it and start up the system.
FORMAT:
SAV[E]~[/switch]

where:
/switch

is one of the following optional switches:
IMOU=dev: [dev: ... :dev:]
This switch is used to allow the system
to be saved with the specified devices
mounted. See Technical Note 3.

ILOG=TTn: [TTn: ... :TTn:]
This switch is used to allow the system
to be saved with the specified terminals
logged on.

INO, /NOX, /NOT, /NOXT
These switches all inhibit automatic
memory expansion or truncation when the
saved image is rebooted.
If none of
these switches is used, SAVE determines
exactly how much memory exists
and
expands
or
truncates
the
highest
partition in the system.
NOTE
If the user attempts to save a
system that still has volumes
mounted or terminals logged on,
and the /MOU or /LOG switches
have not been specified,
the
save will not occur.

6-47

PRIVILEGED USER COMMANDS
EXAMPLE:
1.

MCR>SAVE
In this example, the current status of the system is saved on the
disk from which it was originally bootstrapped. System changes
made by the REDIRECT or other MCR commands are also saved with
the system dore image.

MCR>SAVE~/MOU:DFO:

In this example, the system is saved with DFO:

6-48

mounted.

PRIVILEGED USER COMMANDS
TECHNICAL NOTES
1.

Because the SAVE command provides a copy of a completed
system configuration, it must be used only when the system is
quiescent.
SAVE ensures that
the system is quiescent by
searching
the system data base for any of the following
conditions:
Mounted devices,
Users logged onto terminals other than the
which the SAVE command was issued,

one

from

Tasks with I/O in progress,
Tasks being loaded or checkpointed,
Shareable global areas being loaded or, in
the case
of read/write common areas, being recorded on disk,
Tasks loaded or fixed beyond
file,

the

end

the

SAVE

Shareable global areas including the read-only root
of multiuser tasks loaded beyond the end of the save
file.
If any of
these conditions
appropriate error message.

detected,

SAVE

issues

The SAVE command will attempt
to record
(on
the system
device)
all memory specified at SYSGEN time.
If more memory
exists than was declared at SYSGEN, only the declared memory
will be saved.
If, however, less memory exists than was
declared at SYSGEN, only the amount
that exists will be
saved.
For a PDP-ll/70, no more than l24K will be saved.

SAV will not permit the system
to be saved with volumes
mounted or
terminals logged on, unless the appropriate /MOU
or /LOG switches are specified.
In the case where the /MOU switch is specified, for
Files-II
volumes the user must take the following information into
account:
a.

When a volume is mounted, volume control data
is
established in memory to reflect the volume's current
file status.
This data is updated with every file
operation.

When a volume is dismounted,
reset.

If the user selects to save the system with volumes
mounted,
the volume control data for each mounted volume
is saved reflecting the current status of the volume.
It
is imperative that no file activity occur on the volume
between the time the system was saved, and
the next
bootstrapping of the system. Otherwise, the integrity of
the volume will be destroyed.

6-49

the volume's control data is

PRIVILEGED USER COMMANDS
d.

When the system is re-bootstrapped,
the status of the
volume must be exactly the same as it was when the system
was saved, or
the integrity of the volume will be
destroyed on the very first file operation.
NOTE
After the system is re-bootstrapped, and before
the user can
any file activity has occurred,
execute the following commands to ensure the
integrity of any volume:
MCR>DMO dev:
MCR>MOU dev:
This will reset the volume's control
reflect the current volume status.

data

the
In the case where the /LOG switch is specified when
system
is re-bootstrapped,
the specified terminals are
automatically logged on having the same UIC and privilege
they had when the system was saved.
4.

When a saved system is rebooted or restarted, the system is
expanded or truncated automatically to the amount of physical
memory available unless the /NOXT switch was used when
the
system was saved.
Because SAVE is active when a save is performed, it is active
when the reboot/restart occurs.
It is, in fact, the task
SAVE that restarts an RSX-IlD system and performs the memory
size calculations.
To expand the system, SAVE determines how much physical
memory responds by testing memory in 4K word increments on a
PDP-lI/40, 45, or 50 or by reading the memory size register
on PDP-II/70.
If the address at the top of memory is greater
than that at the last save, or at system generation if no
save was performed, SAVE performs the following steps:
Increases the size of the
partition,

last

(highest

addressed)

Adjusts the hole pointer,
Prints a explanatory message
which the SAV was initiated.

the

terminal

from

If the actual memory is less than the amount contained in the
save file,
SAVE attempts to truncate one or more partitions
starting from the highest end of memory.
Truncation fails
and an appropriate message is printed under the following
circumstances:
Any occupied partition size reduces to zero,
Any truncation occurs in an occupied
partition,

6-50

user-controlled

PRIVILEGED USER COMMANDS
Truncation in a
extensive that
does not exist.

system-controlled partition is so
a previous occupied area of memory

In summary, unoccupied partitions can be truncated to size
zero.
Unoccupied parts of system-controlled partitions also
can be truncated.
Successful truncation results in
a
descriptive message printed at the terminal.
5.

Irrespective of any previous memory expansion or
truncation,
the save file is always the length specified at system
generation and only that amount of memory is saved.
This
fact is the reason for the checking described in technical
note 1 on entities loaded beyond the end of the save file.

Chapter 5 of the RSX-IID System Generation
contains more details about SAVE.

6-51

Reference

Manual

PRIVILEGED USER COMMANDS
SET

6.24

SET COMMAND (SET)

FUNCTION:
The SET command provides the privileged user with a facility for
changing
the
terminal default UIC,
the MCR timeout,
the
terminal's characteristics and privileges, for
setting
or
clearing output spooling on a device and for controlling cache
memory on PDP-ll/70.
FORMAT:
SET~[/keyword(s)]

where:
/keyword

is one or
specified,
represent.
provided:

more op~ional keywords which, when
alter or set the default values they
The following keyword options are

/UIC=[group,member]
This option allows the user
to change the
therminal default UIC to the one specified to
the right of the equal sign(=).
Example:

/UIC=[200,200]

/TMO=nnnnn
This option allows the user to change the MCR
timeout value. The number nnnnn is a decimal
value (any number up to 32767)
representing
the number of seconds MCR is to wait for a
command before timing out.
Example:

/TMO=90

/LA30S=dev: [dev: ... :dev:]
This option defines the specified
as having LA30S characteristics.
Example:

device(s)

/LA30S=TTl:TT2:

/LA30P=dev: [dev: ... :dev:]
This option defines the specified
as having LA30P characteristics.
Example:

device(s)

/LA30P=TTl:TT2:

/KSR33=dev: [dev: ••. : dev : ]
This option defines the specified
as having KSR33 characteristics.

6-52

device(s)

PRIVILEGED USER COMMANDS
Example:

/KSR33=TTl:TT2:

/PRV~dev:[dev: •••• :dev:]

This option defines the specified
as privileged terminal device(s).
Example:

device(s)

/PRV=TTl:TT2:

/SLV=dev:[dev: •••• :dev:]
This option defines the specified
as slave terminal device(s).
Example:

device(s)

/SLV=TTl:TT2:

/ -PRV=dev: [dev: •..• : dev: ]
This option defines the specified device(s)
as nonprivileged terminal device(s).
Example:

/-PRV=TTl:TT2:

/-SLV=dev: [dev: •... :dev:]
This option defines the specified
as nonslave terminal device(s).
Example:

device(s)

/-SLV=TTl:TT2:

/SP=dev: [dev: •••. :dev:]
This option defines the specified device(s)
as being available to the output despooler
for the spooling of spooled output files.
Example:

/SP=LP:TTl:

/-SP=dev: [dev: ••• :dev:]
This option defines the specified device(s)
as no longer being available to the output
despooler for the spooling of output files.
Example:

/-SP=TTl:TT2:

/INB=dev: [dev: ••. :dev:]
This option defines a terminal(s)
intermediate buffering.
Example:

having

/INB=TT3:

/ - INB=dev: [dev: •.• : dev : ]
This
option
discontinues
intermediate
buffering on the specified terminal(s).
/CAC=n
This option specifies the

6-53

number

parity

PRIVILEGED USER COMMANDS
errors that can occur in a PDP-ll/70 cache
group in one minute before
the Executive
turns the group off. The value n can be from
1 to 32,767 (decimal). The default value for
n is 50. Parity error handling is discussed
in the RSX-llD System Manager's Guide.
/CAC=ONn
This options allows the user
to
turn on a
PDP-ll/70
cache
memory
group that had
previously been turned off.
The value n
indicates the number of the group.
/CAC=OFn
This option allows the user
to turn off a
PDP-ll/70 cache memory group that is on.
The
value n indicates the number of the group.
EXAMPLE:
1.

MCR)SET /UIC=[20,20]/TMO=90/LA30S=TTl:TT2:
In this example, the following actions are performed:

The system UIC is set to [20,20].

The MCR timeout is set to 90 seconds.

TTl:

and TT2:

are defined as having LA30S characteristics.

MCR)SET /LA30S=TTl:TT2:TT3:/PRV=TTl:TT2:/SP=TT3:
In this example, the following actions are performed.
a.

TTl:, TT2:, and
characteristics.

TTl:

TT3:
is made available to
spooling of output files.

and TT2:

TT3:

are

defined

having

LA30S

are defined as being privileged terminals.

6-54

the

output

despooler

for

the

PRIVILEGED USER COMMANDS
TIME

6.25

TIME COMMAND (TIM)

FUNCTION:
The Time command (TIM) allows the operator to list the time and
date, or to alter the time and date values in the system clock
calendar.
FORMAT:
TIM[E]6[time]6[date]
where:
time is specified in the format hour:minute:second
date is specified in the format month/day/year
NOTE
If the TIME command is executed without param~ters,
the
time and date that the system is currently running under
will be listed.
Also,
if either or both of
the
parameters
(time
or
date)
are
specified,
the
corresponding field in the system will be altered to the
value specified by the parameter.
EXAMPLE:
1.

MCR)TIM 9:10:20 3/21/75
In this example the time and date in the system clock
are changed to 9:10:20 and 3/21/75, respectively.

6-55

calendar

PRIVILEGED USER COMMANDS
USER FILE DIRECTORY

6.26

USER FILE DIRECTORY COMMAND (UFD)

FUNCTION:
The User File Directory command
(UFD)
creates a user file
directory (UFO) on the specified volume and enters its file name
into the master file directory (MFD). The UFO command accepts
the
[group,owner]
number as both the UFD name and the file
owners' UIC.
FORMAT:
UFD~device: [uic] [/switch]

where:
device:

specifies the device that contains the
be acted upon.

[uic]

is the UIC of

~he

volume

UFO being created.
NOTE

The brackets which enclose the UIC
required part of the parameter.
/swi tch

is one or more of the
described in Table 6-4.

optional

UFO

are

switches

EXAMPLE:
MCR>UFO DKl: [l,l]/ALLOC=lOO.
In the example above, the request creates the UFO on disk device
DKI with the UIC [1,1] as the directory name; space is allocated
for 100 directory entries.

6-56

PRIVILEGED USER COMMANDS
Table 6-4
UFD Switches
SWITCH
/PRO

DESCRIPTION
This switch allows the owner of the directory to
selectively permit access to his file.
This
switch is specified in the following format:
/PRO=[system,owner,group,world]
NOTE
If the /PRO switch is not specified,
the
default file protection for the volume is
used.

/ALLOC

This switch allows the owner of the directory
pre-allocate space for a specified number
directory entries. This switch is specified
the following format:
/ALLOC=number-of-entries
NOTE
The number specified is assumed to be
octal;
the number may be specified with a
trailing decimal point to represent a
decimal value. The default is 32 octal.

6-57

to
of
in

PRIVILEGED USER COMMANDS
UNFIX

6.27

UNFIX COMMAND (UNF)

FUNCTION:
The Unfix command
(UNF)
allows
"Fixed" tasks from memory.

the

privileged

user

free

FORMAT:
UNF[IX]~taskname[/TI=dev]

[,taskname[/TI=dev] , .•• ]

where:
taskname

is the name of the task being unfixed.

/TI=dev

is an optional switch (appended to the
taskname)
which allows the user
to unfix any task in the
system by specifying its TI
(dev is the device
mnemonic for the terminal corresponding to the TI
under which the task is run).

EXAMPLES:
1.

MCR>UNFIX XKE

MCR>UNFIX 240Z,NKlll
In the example above the requests:

Unfix task XKE, freeing it from memory;

Unfix task 240Z and Task NKlll.

6-58

and,

PRIVILEGED USER COMMANDS
UNLOAD

6.28

UNLOAD COMMAND (UNL)

FUNCTION:
The UNLOAD command (UNL) causes the indicated device handler
to
exit, releasing its memory and causing the device to become
inaccessible.
FORMAT:
UNL[OAD]nhandler-name[:]
EXAMPLE:
1.

MCR>UNLOAD LP
In the example above the request unloads the line printer handler
task.

6-59

CHAPTER 7
MAGNETIC TAPE VOLUMES

The magnetic tape file system is a privileged task named MTAACP that
provides file primitive services to FCS. The file system also uses an
associated message task named FIlMSG that must be installed before a
magnetic tape volume can be mounted.
The magnetic tape file system processes tape volumes that have been
initialized through the INITVOL MCR function.
The mounting and
dismounting of a volume set is accomplished using the MOU and DMO MCR
functions.
Once a volume set is mounted, all volume
transparent to the FCS level of the system.

reel

switching

NOTE
It is not necessary that all
volume set be mounted on
simultaneously.

7.1

~eels

in a
tape units

INITIALIZING TAPE VOLUMES

Initializing a magnetic tape volume is an important step in preparing
a magnetic tape file system for use. All protection is at the volume
level;
therefore, to ensure proper use of volume sets, each volume
must have a unique volume identifier (label). The system manager
should establish a method of assigning unique volume labels and
external identification.

7.2

MOUNTING A VOLUME SET

The MOU MCR command is used to mount the volume set.
The following
information should be kept in mind when mounting a volume set.
1.

Any number of tape units can be assigned to the volume set.
All units must be compatible with ~ach other (i.e., they must
be either 9- or 7-track and 1600 or 800 bpi).

All volume labels or only the first volume label in
can be specified. See the examples below.

7-1

the

set

MAGNETIC TAPE VOLUMES
The number of volume labels specified in
the MOUNT command
affects the form of the operator mount message printed on the
console.
The system assigns
relative
volume
numbers
sequentially, starting with volume 1 and continuing through
the list of volumes.
The system assumes that the volumes, in
the volume set are mounted physically as indicated in the MOU
command.
However, only relative volume 1 is verified at mount
time;
the verification of subsequent volumes
is performed when
these volumes are needed.
3.

Volumes produced by the magnetic tape file system of RSX-IID
versions
before
version
6
(.FL300)
are
recognized
automatically.
The volumes produced under previous versions
can only be read;
they never can be written by the magnetic
tape file system.

The file set identifier,
the file section number,
and
the
file
sequence number
in HDRI file labels are used by the file system to
identify individual volumes in a set of volumes.
The following are examples of MOU commands for volume sets.

7.3

MCR>MOU MTO:ISTVOL

lSTVOL is the first volume of
a volume set.
It is mounted
on MTO which is the unit on
which all
subsequent volumes
are to be mounted.

MCR>MOU MT(O,l) : (lSTVOL,2NDVOL)

lSTVOL is mounted on
MTO.
2NDVOL either
is or will be
mounted on MTI.
If 2NDVOL is
not mounted when required, a
message requesting
operator
action
is
printed on
the
console.

DISMOUNTING THE VOLUME

The DMO MCR command is used to dismount a volume set.
The following
information should be kept in mind when dismounting a volume set.
1.

All units assigned to the volume set are dismounted
dismounting of any unit assigned to the volume set.

Individual DISMOUNT COMPLETE messages are printed on
the
operator's console for each unit assigned to the volume set.

All units are rewound and placed off-line unless the unit
currently off-line or rewinding.

7-2

the

MAGNETIC TAPE VOLUMES
7.4

OPERATOR INTERACTION WITH THE MAGNETIC TAPE FILE SYSTEM

The magnetic tape file system issues messages to the console output
device
(CO)
through the file system message task (FllMSG).
These
messages are requests for operator action. The operator
is expected
to perform the requested action for the specified tape unit and then
place the unit on-line.
The magnetic tape file system automatically detects that the requested
unit has been placed on-line and restarts the process that was
attempted before the request was issued.

7-3

CHAPTER 8
NODE POOL STATUS PROGRAM

The node pool status program (POOL) provides the privileged user with
statisitics about pool usage, and prints these statistics on the
terminal. Once the POOL program is initiated, it executes every two
seconds and prints the number of nodes available (unused) in the pool
along with the largest contiguous amount of node space.
All numbers
(decimal) are in terms of 8-word nodes.
Type the following command to cause POOL to execute:
MCR>RUN POOL@
See Figure 8-1.
To terminate POOL execution, the user must press CTRL C to obtain
MCR> prompt and enter the following command:

the

RES POOL®
This causes POOL to print summary information and exit.
information consists of the following:
1.

The largest contiguous amount of node space

The smallest amount of node space

The largest number of available nodes

The smallest number of available nodes.

The

This summary information is accumulated from the
time
initiated, to the time it is terminated.
See Figure 8-1.

8-1

summary

POOL

NODE POOL STATUS PROGRAM
MCR>RUN POOLeD
NODES
NODES
NODES
NODES
NODES
NODES

745
759
751
753
746
742

LARGEST
LARGEST
LARGEST
LARGEST
LARGEST
LARGEST

HOLE
HOLE
HOLE
HOLE
HOLE
HOLE

113
113
113
113
113
113

MCR>RES POOLeD
NODES = 728
LARGEST
LARGEST NUMBER OF NODES = 759
SMALLEST NUMBER OF NODES = 728
LARGEST HOLE = 113
SMALLEST HOLE = 113

HOLE

113

Figure 8-1
Sample POOL Execution And Termination

8-2

APPENDIX A
MCR COMMAND SUMMARY AND ERROR MESSAGES

A.I

MCR COMMAND SUMMARY

ABORT (Non-privileged)
ABO~taskname[,taskname, ... ]

ABORT (Privileged)
ABO~taskname[/TI=dev]

ACTIVE TASK LIST (Non-Privileged)
ACTA[taskname] [/switch(es}]
Switches:
/FU - Full listing
ISH - Short listing
/TI~dev - All tasks for specified TI
ALTER PRIORITY (Privileged)
ALTAtaskname [/TI=dev]/PRI=nnn[,taskname [/TI=dev]/PRI=n nn, •.. ]
BAD BLOCKS (Privileged)
BADAdev:
BOOTSTRAP (Privileged)
Format I
BOO
BOO>
Format 2
BOOAfilespec
Format 3
BOO~/WB

A-I

MCR COMMAND SUMMARY AND ERROR MESSAGES
Format 4
BOO~filespec/WB

BYE (Non-Privileged)
BYE
CANCEL (Privileged)
CAN~taskname[/TI=dev]

[,taskname[/TI=dev] , ••. ]

CONTINUE (Non-Privileged)
CON~taskname[,taskname, .•. ]

DISABLE (Privileged)
DIS~taskname[,taskname, .•. ]

DISMOUNT VOLUME (Non Privileged)
DMO~dev: [volumelabel] [/UIC=[uic]] [/LOCK]

DISMOUNT VOLUME (Privileged)
Same as non-privileged with this exception:
only
user is allowed to dismount the system volume.
ENABLE (Privileged)
ENA~taskname[,taskname, ••• ]

FIX IN MEMORY (Privileged)
FIX~taskname[/TI=dev]

[,taskname[/TI=dev] , .•. ]

HELLO (Non-Privileged)
HEL~[uic]

PASSWORD>
INITIALIZE VOLUME (Privileged)
INI~dev: [volumelabel] [/keyword(s)]

Keywords
/UIC=[uic]
/PRO=[system,owner,group,world]

A-2

privileged

MCR COMMAND SUMMARY AND ERROR MESSAGES
/MXF=maximum number of files allowed on this volume
/EXT=default file extension size in blocks
/FPRO~[default

file protection]

/CHA=[characteristic word]
ATCH or DCF or both
/INF=number of file headers in file index
/WIN=default window size for file
/LRU=number of directories to keep accessed
/DENS=magnetic tape density
800 or 1600
/INDX=index file position option
BEG - beginning of volume
MID - middle of volume
END - end of volume
BLK:nnn - logical block number
/BAD=option (Initialization of bad block file)
AUTO - use bad block data left on
volume by BAD command task.
MAN - enter bad blocks manually.
INI>BAD=u [ ,n]
INSTALL TASK (Privileged)
INS.1filespec [/keyword (s)] [,filespec [/keyword (s)] , .•. ]
or
INS.1@indirect
Keywords
/PAR

partition name

/PRI

priority-number (decimal)

/TASK

taskname

/POOL

pool-limit (decimal)

/UIC

[uic]

/RUN

[REM]

/TIM

(run-remove)

allowable run time expressed as nH,
nS, nM, or nT.

A-3

MCR COMMAND SUMMARY AND ERROR MESSAGES
/ACC = non-owner access expressed as
RO - read only
RW - write only
NA - no access (default)
/LI

library file

/CM

common area

/INC = task size increment
LOAD (Privileged)
LOA~handler-name

LOG COMMENT (Non-Privileged)
LOG~comment-line

or
i~comment-line

or
!~comment-line

LOGICAL UNIT NUMBERS (Non-Privileged)
LUN~taskname[,taskname, ... ]

MEMORY UNLOCK (Privileged)
MEM~taskname[/options] [,taskname, ..• ]

Keywords
/AL - all such tasks
/TI

TTn - all tasks with this TI

MOUNT VOLUME (Non-Privileged)
MOU~dev:volumelabel[keyword(s}]

Keywords
/CHA=[characteristics word]
FOR -

foreign volume

ATCH - device can be attached exclusively
by one task
DCF - device control functions allowed
/UNL (volumes index file is unlocked)
/DENS

= magnetic

tape density

A-4

MCR COMMAND SUMMARY AND ERROR MESSAGES
800 or 1600
/ACP

taskname (file processor for the volume)

jEXT

default file extend increment in blocks

jFPRO = [default file protection]

jLRU = number of directories to keep pre-accessed
jOVRFSID (override the set identifier check)
jOVREXP (override the expiration date check)
Format for Mounting Multi-volume Magnetic Tape
MOU~MT(nl[,n2, ••. ,nn]): (labell[,labeI2, ... ,labeln]) [/keyword(s)]

MOUNT (Privileged)
MOU~dev:volumelabel[jkeyword(s)]

Keywords
All of the above-mentioned keywords, plus the following:
JUIC =[uic]
jOVR (override the volume label check)
jPRO = [system,owner,group,world]

OPEN REGISTER (Privileged)
OPE~memory

address[+ or -n] [/options]

Options
jTASK = taskname[/TI=dev]
jPAR = partition name
jKNL (specifies kernel virtual address)
OPERATE (Non-Privileged)
OPR~dev:jswitch[,dev:jswitch, ..• ]

Switches
jSP - Start printing

JAB - Abort printing
JST - Stop printing
JRS - Resume printing

jRS:T - Resume printing from last
encountered form feed.

A-5

MCR COMMAND SUMMARY AND ERROR MESSAGES
/RS:TOF - Resume printing from top-of-file
OPERATE (Privileged)
OPR~dev:/switch[,dev:/switch, ••. ,dev:/switch]

Switches
All of the above mentioned switches plus the following:
/CHG - Change forms
/FO:n - Set the form type to n
/RE - Recycle all active orders and
requeue them as inactive
PASSWORD (Non-Privileged)
PWD~[ufd]

PASSWORD>password
PASSWORD (Privileged)
Same as non-privileged with this exception;
the privileged user
can change the password for any UFO on any volume not protected
against system access.
QUEUE (Non-Privileged)
Queue a File For Printing
QUE~[dev:=]infile-I[,infile-2, ..• ,infile-n] [/switch(es)]

or
QUE~@indirect

Switches
/PR:nnn - Set the priority
(default /PR:50)

output

selection

/FO:n

- Set form type to n (default /FO:O)

/CO:nn

- Set number of copies to nn (default /CO:l)

/DE

- Delete file after printing (default /-DE)

/TE

- Test for forms alignment

List Elements in Queue
QUE~/LI

Kill (Delete) Elements in Queue
QUE~/KI:seg[:seq: .•. :seg]

Modify Elements in Queue

A-6

nnn

MCR COMMAND SUMMARY AND ERROR MESSAGES
QUE~[dev:=]/MO:seq[:seq: ..• :seq] [/switch(es)]

Swi tches
/PR:nn

- Change priority to nnn.

/FO:n

- Change form type to n.

/CO:nn

- Change number of copies to n.

/DE

Change delete/preserve
(default /-DE)

ind ica tor

REASSIGN (Privileged)
REA~taskname~lunlist~dev:

REDIRECT (Privileged)
RED~new-dev:=old-dev:

REMOVE (Privileged)
REM~namel [/swi tch]

[,name2 [/swi tch] , ... ]
or

RE[VJ~@ ind irec t

RESUME

(Non-Privileged)

RES~taskname[/TI=dev]

[,taskname[/TI=dev] , ... ]

RUN (Non-Privileged)

RUN~f ilename

RUN~$filename

RUN (Privileged)
(Request)

RUN~taskname[/option] [,taskname[/option] , ••• ]

Options
/PRI=priority number

(decimal)

/PAR=partition name
/UIC=[user identification code]
(Execute)

RUN~taskname/MEM[/option] [,taskname/MEM[/option] , ••• ]

A-7

delete

MCR COMMAND SUMMARY AND ERROR MESSAGES
Options
/PRI=priority number

(decimal)

/PAR=partition name
/UIC=[user identification code]
(Run)

RUN~taskname~time[/options] [,taskname~time[/options] , ••. ]

Options
/RSl=reschedule interval expressed as
nH, nM, nS, or nT
/PRl=priority number (decimal)
/PAR=partition name
/UlC=[user identification code]
(Schedule)

RUN~taskname~time[/options]

Options
/RSl

reschedule interval expressed
as nH, nM, nS, or nT

/PRl

priority number

/PAR

partition name

/UlC

[user identification code]

(decimal)

(Synchronize)

RUN~tasknamells tar timell+time [/opt ions]

Options
/RSl

rescheduling interval expressed as
nH, nM, nS, or nT

/PRl

priority number

/PAR

partition name

/UlC

[user identification code]

/TlM

timeout limits for accountable tasks

(decimal)

SAVE (Privileged)
SAV~[/switch]

Swi tches
/MOU=dev: [dev: ... dev:] - save system with dev:

A-8

mounted

MCR COMMAND SUMMARY AND ERROR MESSAGES
/LOG=TTn:[TTn: •.• :TTn:] - save system with specified
terminals logged on.
/NOXT -

inhibit memory expansion/truncation on reboot.

SET (Privileged)
SET~[/keyword(s)]

Keywords
/UIC=[group,member]
/TMO=nnnnn

- change MCR
nnnnn.

timeout

value

/LA30S=dev: [dev: ... :dev:]

- device
has
characteristics

LA30S

/LA30P=dev: [dev: ... :dev:]

has
- device
characteristics

LA30P

/KSR33=dev: [dev: ... :dev:]

- device
has
characteristics

KSR33

device
is
defined
as
privileged terminal device

/PRV=dev: [dev: ... :dev:]
/SLV=dev: [dev: .•• : dev : ]

- device is defined as
terminal device

slave

/-PRV=dev: [dev: •.. :dev:]

- device
is
defined
as
a
non-privileged terminal device

/-SLV=dev: [dev: ... :dev:]

device
is
defined
as
non-slave terminal device
to

a
the

/SP=dev:[dev: ... :dev:]

- devices
available
Output Despooler

/ -SP=dev: [dev: ..• : dev : ]

- devices no longer available to
the Output Despooler

/INB=dev:[dev: ... :dev: [

- device is defined as having
intermediate buffering.

/-INB=dev: [dev: ... :dev:]

- device is defined
in te rmed ia te
recended.

haveing
buffering

SYS (Non-Privileged)
SYS~[/switch [:opt]]

Switches
/ATL

- List names of tasks in the active task list

/MRL [:opt]

- List names of tasks in memory required list

/CKQ

- List name of task in the clock que

/GCO

- Lists names of Libraries and cornman

A-9

area

MCR COMMAND SUMMARY AND ERROR MESSAGES
the global common directory
/IRQ [: opt]

- List names of tasks with entries in
request queue

/CTL [: opt]

the

I/O

List name of tasks in the checkpointable task
list

/FTL

- List names of tasks in the fixed tasks list

/SRQ

- List names of tasks that
for them

/ASQ

- List names of tasks in the ATL that have ASTs
queued for them

/SGA

- List names of tasks in the STD and
to which each is bound

/BRF

- Lists names of tasks in the ATL, MRL, or CKQ

/FUL

- Lists all the above except /SGA

/TAS

- Same as TAS command

/DEV

- Same as DEV command

/PAR

- Same as PAR command

/COr.1

- Same as COM command

TIME (Non-privileged)
TIM
TIME (Privileged)
TIM~[time]~[date]

USER FILE DIRECTORY (Privileged)
UFD~dev: [uic]

[/switch]

Swi tches
/PRO=[system,owner,group,world]
/ALLOC=number-of-entries
UNFIX (Privileged)
UNF~ taskname [/TI=dev]

[, taskname [/TI=dev] , ... ]

UNLOAD (Privileged)
UNL~handler-name[:]

WHO (Non-Privileged)
WHO

A-IO

have

sends

the

queued

SGAs

MCR COMMAND SUMMARY AND ERROR MESSAGES
A.2

MCR ERROR MESSAGES

The error messages in this appendix are listed in alphabetic order by
issuing task. The only exceptions are the messages issued by the task
MCRERR.
It prints the user-entered command that caused the error and
then, on the following line, prints the error message. Messages with
no 3-letter prefix can be identified as coming from MCRERR.
These
messages are presented in Section A.2.l
ACT -- INVALID ADDRESS IN A.TI
The active task list contains a TI that has an invalid address.
Notify the DEC software specialist.
ACT -- INVALID DEVICE
The device mnemonic, specified by the user, is either invalid
specified in a nonstandard format.

ACT -- INVALID SWITCH
The user specified a switch that ACT does not recognize.
Either
the switch is not an ACT switch, or it was specified in the wrong
forma t.
ACT -- INVALID SWITCH COMBINATION
The user specified switches that are mutually exclusive; see the
description of ACT in Chapter 5 to determine which switches can
be used together.
ACT -- INVALID TASK NAME
The user specified a task name that either contains more than 6
alphanumeric characters or one that contains a non-alphanumeric
character.
ACT -- NO TASKS ACTIVE ON TERMINAL
or
ACT

TASK NOT ACTIVE
Self-explanatory.

ACT -- TOO MANY TASKS FOR BUFFER
ACT can only process a maximum of 10 active tasks, and the active
task list contains more than 10. Only the first 10 tasks in the
queue are listed at the user terminal.
To make ACT handle more than 10 active tasks, the system manager
This is
must
task build ACT to accommodate more tasks.
accomplished by modifying ACT's size, and
the size of its
processing buffer (MAXTSK).

A-II

MCR COMMAND SUMMARY AND ERROR MESSAGES
ACT -- THE /FU SWITCH REQUIRES A TASK NAME
Self-explanatory.
BAD -- BAD BLOCK FILE OVERFLOW
More than 102 groups of bad blocks (each group consisting of from
I to 256 bad blocks) were detected.
The disk pack is defective.
BAD -- BLOCK 0 BAD - DO NOT USE AS SYSTEM DEVICE
This is a warning message;
it requires no user action.
BAD has
terminated normally;
and all bad block information is available
for INITVOL.
BAD -- DEVICE HANDLER MISSING
The required disk handler task is not loaded.
Load the required handler and retry the command.
BAD -- DEVICE NOT IN SYSTEM
The specified device was not included as a usable device when the
system was generated.
That is, there is no PUD entry for the
device.
The user most likely typed
the
device
mnemonic
incorrectly.
BAD -- DISK ATTACH FAILED
The specified disk is currently attached by another task.
wait until the attaching task releases the disk, then
command.

retry

the

NOTE
If
the specified disk
is
currently
attached by another
task,
there is a
good chance the user specified the wrong
device mnemonic.
BAD -- DISK ERROR
An unaccountable error occurred on the
likely a hardware error.

specified

device;

most

Insure that the device is properly cycled up and on line,
then
retry the command.
If the error reoccurs, notify field service.

A-12

MCR COMMAND SUMMARY AND ERROR MESSAGES
BAD -- DISK MOUNTED
The specified disk is logically mounted.
That is, a MOU command
was issued for the device.
BAD cannot process bad blocks for a
logically mounted disk.
Execute the DMO command for the device, then retry the command.
BAD -- DISK NOT READY
The specified disk device is inaccessible;
hardware error.

probably

due

Insure that the device is properly cycled up and on-line,
then
retry the command.
If the error reoccurs, notify field service.
BAD -- DISK WRITE LOCKED
The specified disk device is inaccessible for write operations.
Set the write enable switch and retry the command.
BAD -- FAILED TO READ MCR COMMAND BUFFER
BAD failed to obtain the command line with which it was invoked.
This will occur
if BAD is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.

the

failure

BAD -- FAILED TO WRITE BAD BLOCK FILE
Either an error occurred when BAD attempted
to write
the bad
block information, or
the last 256 blocks of the disk are
unusable.
BAD -- ILLEGAL DEVICE
The device mnemonic, specified by the user, is either invalid
specified in a non-standard format.

BAD -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

BOO -- ASSIGN LUN ERROR -- CODE -nn
The system is unable to assign a LUN to the device being booted.
The reason for the failure is determined by -nn, where -nn is a
system standard error code. See Appendix N.

A-l3

MCR COMMAND SUMMARY AND ERROR MESSAGES
BOO -- CANNOT FIND SYSTEM DEVICE PUD
The system device (SY) PUD cannot be found.
This will occur if
SY was redirected to itself, or if the PUD entry itself is
corrupted.
Redirect SY to a valid system device, then retry the command.
the error reoccurs, call the DEC software specialist.

= -nn

BOO -- COMMAND I/O ERROR CODE, CODE

The TTY handler is unable to obtain a command line from the
terminal.

user

Notify the DEC software specialist.
BOO -- COMMAND SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

BOO -- ERROR CLOSING FILE filename CODE = -nn
The file system is unable
to close the specified file.
The
reason for
the failure
is determined by -nn, where -nn is a
system standard error code. See Appendix N.
BOO -- FILE NOT AN RSX IMAGE
Self-explanatory.
BOO -- FILE NOT CONTIGUOUS
The file is either corrupted, or not an RSX system image file.
BOO -- GET LUN ERROR -- CODE

= -nn

The system is unable to get a LUN for tbe device being booted.
The reason for
the error is determined by -nn, where -nn is a
system standard error code. See Appendix N.
BOO -- INDIRECT COMl-'IAND SYNTAX ERROR
The user specified an indirect command file specifier in a format
that does not conform to syntax rules.
Refer to the command description for the correct syntax.

A-14

MCR COMMAND SUMMARY AND ERROR MESSAGES
BOO -- INDIRECT FILE DEPTH EXCEEDED
The indirect command file, specified by the user, has an indirect
command file specification as one of its commands. BOO can only
process one indirect command file at a time.
Recreate
the
manually.

indirect

command

file,

BOO -- INDIRECT FILE OPEN FAILURE, CODE

enter

the

commands

= -nn

BOO is unable to open the specified indirect command file.
The
reason for
the failure is determined by -nn, where -nn is a
system standard error code. See Appendix N.
BOO -- INVALID SWITCH
The user specified a un-recognizable
recognized by BOO is /WB.

switch.

The

only

switch

BOO -- ILLEGAL DEVICE/VOLUME
The device mnemonic, specified by the user, does not
device syntax.
BOO

conform

ILLEGAL DEVICE/UNIT NUMBER
Either the device mnemonic is illegal;
not recognized by the
system, or
the unit number exceeds the prescribed range for the
device.

BOO -- ILLEGAL FILENAME
either
contains
The user specified a file name that
non-alphanumeric character, or one that is greater
than
alphanumeric characters in length.

a
9

BOO -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
Self-explanatory.
BOO -- ILLEGAL GET COMMAND LINE ERROR, CODE -nn
The system, while processing a get command line directive,
encountered an unexplainable error condition.
Either the system
software is corrupted, or the hardware has failed.
-nn is
the
get command line error code.
Notify the DEC software specialist.

A-IS

MCR COMMAND SUMMARY AND ERROR MESSAGES
BOO -- ILLEGAL UIC
The UFD specified by the user is either
nonexistent.

illegally

BOO -- I/O ERROR RSX IMAGE FILE filename, CODE

formatted

= -nn

The file system encountered an error while reading the specified
file.
The reason for the failure is determined by -nn, where -nn
is a system standard error code. See Appendix N.
BOO -- I/O ERROR (CODE = -nn) WRITING BLOCK 0
Probable hardware error;
the QIO issued by BOO was valid, but
the write to block 0 failed.
The reason for the failure is
determined by -nn, where -nn is a system standard error code.
See Appendix N.
BOO -- NO WILD CARDS ALLOWED
Self-explanatory.
BOO -- NOT BOaTABLE DEVICE
The specified device is not a mass storage device.
BOO -- ONLY ONE FILESPEC (OUTPUT) ALLOWED
Self-explanatory.
BOO -- OPEN FAILURE FILE filename, CODE

= -nn

BOO failed to open the specified file.
The reason for
the
failure is determined by -nn, where -nn is a system standard
error code. See Appendix N.
BOO

QIO FAILURE (CODE = -nn) WRITING BLOCK 0
A QIO issued by BOO was rejected; BOO may be corrupted.
The
reason for
the failure
is determined by -nn, where -nn is a
system standard error code. See Appendix N.

BOO -- SYSTEM IS NOT QUIESCENT
The user attempted to execute BOO while tasks were
in the system.

still

active

Execute ACT to determine which tasks remain active.
Terminate
the active tasks or wait for them to finish executing, then retry
the BOO command.

A-16

MCR COMMAND SUMMARY AND ERROR MESSAGES
CON -- COMMAND SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

CON -- ILLEGAL ERROR/SEVERITY CODE nl n2 n3
CON failed in its attempt to issue a message to
the user
terminal.
nl contains the value in Rl at the time of the
failure; n2 contains the value in R2;
and n3 contains the
return address after calling the error message routine.
NOTE
The high order byte in
between 0 and 2.

reflects

the

severity

code

message

CON

The low order byte in Rl reflects the error
was trying to issue.
Notify the DEC software specialist.
CON -- TASK taskname NOT ACTIVE
or
CON

TASK taskname NOT IS SYSTEM
Self-explanatory.

CON -- UNABLE TO READ MCR COMMAND LINE
CON failed to obtain the command line with which it was
invoked.
This will occur if CON is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.

the

failure

DMO -- COMMAND I/O ERROR
The DMO task is unable to obtain a command
terminal.

line

from

the

user

Notify the DEC software specialist.
DMO -- DEVICE NOT IN SYSTEM
The user specified a device that was not included as a usab'e
device when the system was generated. That is, there is no PUD
entry for the device. The user most likely typed
the device
mnemonic incorrectly.

A-l7

MCR COMMAND SUMMARY AND ERROR MESSAGES
DMO -- DEVICE NOT MOUNTABLE
The user specified a device that cannot be mounted;
reader.

e.g.,

card

DMO -- HANDLER NOT RESIDENT
The user specified a device
handler is not resident.

for

which

the

appropriate

device

Load the required device handler task and retry the command.
DMO -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
Self-explanatory.
DMO -- INVALID UIC
The UIC specification, entered by the user, either does not match
the volume's UIC; or it was entered in the wrong format.
DMO -- INVALID VOLUME LABEL
The volume label, specified by
volume's label.

the

user,

does

not

match

the

for

the

DMO -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

DMO -- VOLUME BUSY - TRY AGAIN
There are open files on the volume.
Wait for the files to be properly closed, then retry the command.
DMO -- VOLUME NOT MOUNTED
Self-explanatory.
HEL -- DIRECTIVE FAILURE
An undefinable error occurred during the execution of HEL.
Retry the command.
software specialist.

the

error

A-I8

reoccurs,

notify

the

DEC

MCR COMMAND SUMMARY AND ERROR MESSAGES
HEL -- ILLEGAL PASSWORD
System access is denied. The specified password does
the password stored in the requested UFO.

not

match

HEL -- READ FAILURE ON DIRECTORY ENTRY
Either the specified UIC does not correspond
to a UFD on the
system device.
Either
the system device is not mounted or the
hardware has failed.
Notify the system manager.
HEL -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

INI -- ALLOCATION FOR SYS FILE EXCEEDS VOLUME LIMIT
Either the user specified /INDX=BLK:n where the value for n was
too high;
or
the user specified /INDX=END and
the value
specified in /INF=n was too large.
Retry the command with a lower value specified.
INI -- BAD BLOCK HEADER I/O ERROR
INI is unable to retrieve
specified disk volume.

the

bad

Retry the
following:

the

problem

command.

block

Rerun BAD

Rerun INI with /BAD=[AUTO] specified.

data

area

persists,

If the problem still persists, the hardware has
field service.

from

the

perform

the

failed.

Notify

INI -- BAD BLOCK FILE FULL - TASK ABORTED
Either the bad block file was full from a previous BAD execution,
or the user specified more bad blocks than the bad blocks file is
able to store. The disk is not usable.
INI -- BLOCK(S) EXCEED VOLUME LIMIT
The user specified a range of bad blocks that exceed the range of
blocks available on the desired volume.

A-19

MCR COMMAND SUMMARY AND ERROR MESSAGES
INI -- BOOT BLOCK WRITE ERROR
INI has failed in its attempt
to format
the
block.
One of the following conditions exists:
1.

The disk device is off line

The bootstrap block (block 0)

The device is write locked

The hardware has failed.

disks

bootstrap

is bad

INI -- CHECKPOINT FILE HEADER I/O ERROR
INI is unable to wr ite the volume's checkpoint file header
One of the following conditions exists:

The device is off line

The device is not write enabled

The volume has a bad block

The hardware has failed.

area.

INI -- DATA ERROR
The user entered bad block data in an incorrect format.
Re-enter the command using the correct format.
INI -- DEVICE NOT IN SYSTEM
The specified device was not included as a usable device when the
system was generated.
That is, there is no PUD entry for the
device.
The user most likely typed
the
device
mnemonic
incorrectly.
INI -- DEVICE NOT READY
The requested device is not completely cycled up.
Wait for the device to become ready, then retry the command.
INI -- DEVICE WRITE LOCKED
Set the device write enable switch, then retry the command.
INI -- DUPLICATE BLOCK(S) FOUND
The user specified bad block data for blocks that already
in the bad blocks file.

A-20

appear

MCR COMMAND SUMMARY AND ERROR MESSAGES
INI -- FILE CORRUPT -- DATA IGNORED
The volume's bad block data is inconsistent.
Re-execute BAD, then retry the INI command.
INI -- HANDLER NOT RESIDENT
The required device handler is not resident.
Load the required device handler and retry the command.
INI -- HOME BLOCK ALLOCATE WRITE ERROR
INI has failed in its attempt to allocate space for the
horne block. One of the following conditions exists:
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

volume's

INI -- HOME BLOCK WRITE ERROR
INI has failed in its attempt to write the volume's
data. One of the following conditions exists.
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

horne

block

INI -- INDEX FILE BIT MAP I/O ERROR
INI has failed in its attempt to write the volume's
map. One of the following conditions exists:
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

index

bit

INI -- INDEX FILE HEADER I/O ERROR
INI has failed in its attempt to write the
One of the following conditions exists:

A-21

index

file

header.

MeR COMMAND SUMMARY AND ERROR MESSAGES
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

INI -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
or
INI

ILLEGAL KEYWORD VALUE
Self-explanatory.

INI -- ILLEGAL UIC
The user specified a UIC that either does not
syntax, or is not in the range of valid UICs.

conform

UIC

The specified magnetic tape device cannot be accessed for one
the following reasons:

INI -- MAGTAPE DEVICE ERROR

The device is off line

The device is not write enabled

The hardware has failed.

INI -- MAGTAPE LABEL MUST BE SPECIFIED
Self-explanatory.
INI -- MAGTAPE WRITE ERROR
INI is unable to initialize a magnetic tape volume for one of the
following reasons:
1.

The device is off line

The device is write protected

The hardware has failed.

INI -- MFD FILE HEADER I/O ERROR
INI is unable to write
following reasons:

the

MFD

A-22

file

header

for

one

the

MCR COMMAND SUMMARY AND ERROR MESSAGES
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

INI -- MFD WRITE ERROR
INI is unable to write the MFD file
reasons:
1.

The ~evice is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

for

one

the

following

the

following

INI -- NOT FILES-II DEVICE
Self-explanatory.
INI -- NULL FILE HEADER I/O ERROR
The hardware has failed.

Notify field service.

INI -- STORAGE BIT MAP FILE HEADER I/O ERROR
INI is unable to format the bit map
reasons:
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

for

one

INI -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

INI -- VOLUME MOUNTED
INI cannot process a logically mounted volume.
If the device mnemonic was correctly specified, execute DMO to
dismount the volume,
then retry the command; otherwise, retry
the command with the device mnemonic correctly specified.

A-23

MCR COMMAND SUMMARY AND ERROR MESSAGES
INS or INV -- COMMAND I/O ERROR
INI is unable to get a command line from the user terminal.
Notify the DEC software specialist.
INS or INV -- COMMAND SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

INS -- DATE MISMATCH GLOBAL AREA area-name FILE filename
The task being installed is linked with a global area that
different version than the one currently installed.
Remove the current version;
then retry the command.

replace it with the latest

version,

INS -- FLAGWORD MISMATCH GLOBAL AREA area-name FILE filename
Either the flag word field of the global area is corrupted,
the corresponding field in the task image is corrupted.

Rebuild.either the offending task or global area, and
command.

the

retry

INS -- GLOBAL AREA ACCESS REQUEST VIOLATION FILE filename
The task being installed is denied access to the specified global
area. One of the following conditions exists:
1.

The task contains an illegal reference or link to the
area

The global area is protected against access.

global

Rebuild the task correctly and retry the command.
INS

GLOBAL AREA NAME ALREADY IN USE
The user attempted to install a global area
one that is already installed.

whose

Either remove the global area already installed, or
new one, giving it a new name.
INS or INV -- UNKNOWN DEVICE dev:

name

matches

rebuild

the

FILE filename

A device assigned to a LUN at task build time is not one that was
generated into the system. This is a diagnostic message;
the
task image was successfully installed. The user must, however,
reassign the LUN to a valid device before running the task.

A-24

MCR COMMAND SUMMARY AND ERROR MESSAGES
INS or INV -- ILLEGAL DEVICE/VOLUME dev:
The user specified a device that is not recognized by the system.
It is either an illegal device, or the device was improperly
specified.
INS or INV -- ILLEGAL DIRECTORY
The user specified a UFO in a format that
syntax rules.

does

not

conform

INS or INV -- ILLEGAL ERROR/SEVERITY CODE nl n2 n3
INS failed in its attempt to issue a message to
the user
terminal.
nl contains the value in Rl at the time of the
failure; n2 contains the value in R2;
and n3 contains the
return address after calling the error message routine.
NOTE
The high order byte in
between 0 and 2.

reflects

the

severity

code

message

CON

The low order byte in Rl reflects the error
was trying to issue.
Notify the DEC software specialist.
INS or INV -- ILLEGAL FILENAME filename

The specified filename contains non-alphabetic characters, or
is more than 9 characters in length.

INS or INV -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
Self-explanatory.
INS or INV -- ILLEGAL GET COMMAND LINE ERROR CODE -nn
The system, while processing a get command line directive,
encountered an unexplainable error. Either the system software
is corrupted, or the hardware has failed.
-nn is the error
return code.
Notify the DEC software specialist.
INS or INV -- ILLEGAL HEADER DATA FILE filename
The task image header block is corrupted;
Rebuild the task;

then retry the command.

A-25

the task is unusable.

MCR COMMAND SUMMARY AND ERROR MESSAGES
INS or INV,-- ILLEGAL LABEL DATA FILE filename
the

The task image contains inconsistent information;
corrupted and, therefore, unusable.
Rebuild the task;

file

then retry the command.

INS -- ILLEGAL OPTION ON SHARABLE GLOBAL AREA filename
The user specified the IINC keyword option for a sharable
area.

global

Retry the command without the IINC switch specified.
INS or INV -- ILLEGAL POOL LIMIT FILE filename
The pool limit established in the
task image file header
is
illegal; either file header is corrupted, or the value specified
for the IPOOL switch exceeds 255.
Rebuild the task;

then retry the command.

INS or INV -- ILLEGAL PRIORITY FILE filename
The task image file header is corrupted;
Rebuild the file;

the file is not usable.

then retry the command.

INS or INV -- ILLEGAL SWITCH
The user specified a switch that INS does not recognize.
Either
the switch is not an INS switch, or it was specified in the wrong
format.
INS or INV -- ILLEGAL TASK STATUS WORD FILE filename
The task status word of the
task
corrupted;
the file is not usable.

header

Either the UIC in the task image file's header is
the UIC specified in the INS command line is bad.

corrupted,

Either rebuild the task and retry the command,
command with the UIC correctly specified.

the

Rebuild the file;

image

file's

then retry the command.

INS or INV -- ILLEGAL UIC FILE filename

INS or INV -- IMPROPER SIZE DATA FILE filename
The task image file is corrupted.
Rebuild the task, then retry the command.

A-26

retry

MCR COMMAND SUMMARY AND ERROR MESSAGES
INS or INV -- INDIRECT COMMAND SYNTAX ERROR
The user entered an indirect command file specifier in
that does not conform to syntax rules.

Retry the command
specified.

correctly

with

the

indirect

command

file

format

INS or INV -- INDIRECT FILE DEPTH EXCEEDED
The indirect command file, specified by the user, has an indirect
command file specification as one of its commands.
INS can only
process one indirect file at a time.
Recreate the originally
replacing the erroneous
commands it represents.

specified
indirect
command
file,
command file specifier with the actual

INS or INV -- INDIRECT FILE OPEN FAILURE filename
The requested indirect command file
specified or implied device.

cannot

Insure that the indirect file specifier
and retry the command.

was

located

correctly

the

entered,

INS or INV -- I/O ERROR TASK IMAGE FILE
INS encountered an error while processing
the specified
image file.
One of the following conditions exists:
1.

The device is off line

The device is not write enabled

The volume has bad blocks

The hardware has failed.

task

INS -- LENGTH MISMATCH GLOBAL AREA area-name FILE filename
Either the task image file's label block is corrupted, or the GCD
in a global area is corrupted.
Rebuild either the task image or
command.

global

area,

then

retry

the

Either the task's memory mapping registers or memory
invalid.

limits

are

INS or INV -- MEMORY MAPPING CONFLICT FILE filename

Rebuild the file, then retry the command.

A-27

MCR COMMAND SUMMARY AND ERROR MESSAGES
INS or INV -- NO NODE AVAILABLE FOR FILE filename
The system is saturated with active tasks;
nodes available to run INS.
Either wait for pool nodes to become
system manager.

there

available,

are
or

pool

notify

the

INS or INV -- NO ROOM IN STD FOR NEW TASK taskname
The number of allowable
installed
tasks,
specified at system
generation, has been reached.
The named task cannot be installed
until some of the previously installed tasks are removed.
In the
case of INV,
the system data base or SGNljINV have been
corrupted.
Notify the system manager, if using INS.
the DEC software specialist.

using

file,

INV,

notify

INS or INV -- NON CONTIGUOUS TASK IMAGE FILE
Ei ther the file is
corrupted.

not

task

image

Either retry the command with the correct
rebuild the task, then retry the command.

file

specified;

the

INS or INV -- OPEN FAILURE FILE filename
INS failed to open the specified task image file for
One of the following conditions exists:

The requested file does not exist in the specified UFD

The UFD does not exist

The file is protected against write access

The volume is not mounted

The volume is off line

The device is not write enabled

The hardware has failed

update.

INS -- SHARABLE GLOBAL AREA HAS NO OWNING UIC filename
All SGAs must be built or installed having a owning UIC.
Either rebuild the SGA specifying a UIC,
command with the JUIC switch specified.

retry

the

INS or INV -- SPECIFIED PARTITION IS TOO SMALL FILE filename
Self-explanatory

A-28

install

MCR COMMAND SUMMARY AND ERROR MESSAGES
INS -- STARTING APR MISMATCH GLOBAL AREA area-name FILE filename
Either the APR field in the global area is corrupted,
corresponding field in the task image is corrupted.

Rebuild either the offending task image or global area and
the command.

the
retry

INS or INV -- TASK NAME ALREADY IN USE FILE filename
The user is attempting to install a task whose name
to a previously installed task.

assigned

Either remove the previously installed task replacing
it with
this one, or assign a different name to this task via the /TASK
keyword.
INS -- TASK REQUIRES MORE THAN 7 GCD'S
The specified task image is linked to more than 7 GCD'S.
Rebuild the task changing the number of GCD'S to 7 or less.
INS -- TICKS PER SECOND IN SCOM INVALID
This is a system
specialist.

software

problem;

notify

the

DEC

software

INS or INV -- TIMEOUT SPECIFIED ON NON ACCOUNTABLE TASK
Self-explanatory. This is a diagnostic message;
successfully completed.

the install was

INS -- UNDEFINED GLOBAL AREA area-name FILE filename
The specified task is linked to a global area that has
installed.

not

been

Install the required global area, then retry the command.
INS or INV -- UNDEFINED PARTITION FILE filename
The user specified the /PAR switch either at task build time,
at install time. The specified partition does not exist.

Either rebuild the task, or retry
partition name correctly specified.

the

INS or INV -- UNKNOWN KEYWORD IDENTIFIER
Self-explanatory.

A-29

the

INS

command

with

MeR COMMAND SUMMARY AND ERROR MESSAGES
INS -- WATCHDOG TIMER OVERFLOW
The value specified in the /TIM switch exceeds 24 hours in hours,
minutes, seconds, or ticks.
INV -- CANNOT INSTALL GLOBAL REGIONS
Sharable Global areas cannot be installed during SYSGEN phase
Defer installation until phase 2 or later.

INV -- CANNOT INSTALL MU TASKS WITH RO AREAS
The user is attempting to install a multi-user task
that has a
read only root,
which cannot be done during phase 1 of system
generation.
Defer installation of these tasks until phase
2 or
la ter •
INV -- CANNOT INSTALL TASKS BOUND TO GLOBALS
During phase one of SYSGEN, tasks
that are bound
to sharable
global areas cannot be installed.
Defer installation of these
tasks until phase 2 or later.
LUN -- CAN'T READ MCR COMMAND BUFFER
LUN failed to obtain the command line with which it was
invoked.
This will occur
if LUN is
invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.

the

failure

LUN -- FATAL I/O ERROR
The device, on which the specified task is installed,
accessed.
One of the following conditions exists:

cannot

The requested file does not exist in the specified UFD

The UFD does not exist

The file is protected against write access

The volume is not mounted

The volume is off line

The device is not write enabled

The hardware has failed

A-30

MCR COMMAND SUMMARY AND ERROR MESSAGES
LUN -- NO LUN ASSIGNMENT
or
LUN -- NO LUNS
Self-explanatory.
LUN -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

MEM -- GET LINE ERROR
MEM failed to obtain the command line with which it was invoked.
This situation can occur if MEM is invoked using the RUN command.
Retry the command by typing the following line.
MCR)MEM

options

If the failure reoccurs, notify the DEC software specialist.
MEM -- ILLEGAL SWITCH
An illegal switch or a nonexistant device for TI= was specified,
or a series of specifications were included with one or more
tasknames omitted.
Retry the command.
MEM -- PRIVILEGED USER FUNCTION ONLY
Self-explanatory.
HEM -- taskname SPECIFIED VERSION NOT LOCKED
Either the task specified in the MEM command was not locked
memory or a typing error was made when typing the command.

MEM -- SYNTAX ERROR
Self-explanatory.
MOU -- ACP TASK NOT INSTALLED
Self-explanatory.
Install
task the desired ACP task and/or
verify that the ACP task name was correctly specified, then retry
the command.

A-3l

MCR COMMAND SUMMARY AND ERROR MESSAGES
MOU -- ALL UNITS MUST HAVE SAME NUMBER OF TRACKS
All units dedicated to a magnetic tape volume
same;
that is, all 800 BPI or all 1600 BPI.

set

must

the

Retry the command with the correct device types specified.
MOU -- BAD BLOCK ON DEVICE
Either the hardware has failed, or there is an inconsistency with
the medium;
for example, a seven track tape on a nine track
drive.
MOU -- COMMAND I/O ERROR
The TTY handler is unable to
user's terminal.

obtain

command

line

from

the

ready

Notify the DEC software specialist.
MOU -- DEVICE IS NOT MOUNTABLE
Self-explanatory.
MOU -- DEVICE NOT READY
The requested device is not completely
s ta te) .

cycled

(in

Wait for the device to become ready, then retry the command.
MOU -- DEVICE NOT IN SYSTEM
The specified device was not included as a usable device when the
system was generated.
That is, there is no PUD entry for the
device.
The user most likely typed the
device
mnemonic
incorrectly.
MOU -- FILE SYSTEM MESSAGE TASK (FIIMSG) MUST BE INSTALLED
Self-explanatory;

install task FIIMSG, then retry the command.

MOU -- HANDLER TASK NOT RESIDENT
The handler task for the device being mounted is not resident.
Load the required device handler task, then retry the command.

A-32

MCR COMMAND SUMMARY AND ERROR MESSAGES
MOU -- OTHER VOLUME STILL ON LINE
The user is attempting
to mount a volume on a device that
previously contained a volume that was never dismounted.
The
user most likely removed the volume from the device and replaced
it with a new volume, without having issued a DMO command for the
previous volume.
Replace the current volume with the previous one.
Issue
the
appropriate DMO command, then replace the dismounted volume with
the next volume to be mounted.
Retry the MOU command.
MOU -- ILLEGAL FUNCTION FOR NON PRIVILEGED TERMINAL
Self-explanatory.
MOU -- HOME BLOCK NOT FOUND
MOU is unable to obtain the required mount information from
volume's horne block. One of the following conditions exist:

MOU

The volume is not a Files-II volume

The hardware
is malfunctioning.
For
drive's read/write heads are misaligned.

example,

the

disk

I/O SYSTEM ERROR
An undefinable error occurred during the execution of MOU.
Retry the command.
software specialist.

the

error

There is no space available in
volume control block.

the

reoccurs,

notify

the

DEC

pool

for

the

MOU -- NO SPACE FOR VCB
system

node

Retry the command.
If the failure persists, the system should be
rebuilt with a larger node pool.
MOU -- PARITY ERROR ON DEVICE
This is a hardware failure;

notify field service.

MOU -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

MOU -- UNIT DOES NOT SUPPORT 1600 BPI
The user specified 1600 BPI for a
support
800 BPI.
MOU defaults
processing the command.

A-33

tape drive that
to 800 BPI and

can only
continues

MeR COMMAND SUMMARY AND ERROR MESSAGES
MOU -- VOLUME IS NOT ANSI FORMAT
Either the hardware is malfunctioning or the volume is not an
ANSI standard volume.
In either case,
the volume cannot be
mounted.
MOU -- WRONG VOLUME
The volume's label does not match the label specified in the
command line. The volume is not mounted.

MOU

Retry the command with the correct volume label specified.
OPE -- BYTE ADDRESS
The user is attempting to open an odd numbered address location.
OPE -- CAN'T READ MCR COMMAND BUFFER
OPE failed to obtain the command line with which it was invoked.
This will occur if OPE is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.

the

failure

OPE -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
Self-explanatory.
OPE -- INPUT I/O ERROR
The TTY handler is unable to obtain a command line from the
terminal.

user

Notify the DEC software specialist.
OPE -- INVALID ADDRESS
The address specified by the user either is not in the
valid memory addresses, or was incorrectly specified.

range

OPE -- NUMBER TOO LARGE
Self-explanatory.
OPE -- OUTPUT ERROR
The TTY handler is unable
terminal.

issue

Notify the DEC software specialist.

A-34

message

the

user's

MeR COMMAND SUMMARY AND ERROR MESSAGES
OPE -- PARTITION NOT IN SYSTEM
Self-explanatory.
OPE -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

OPE -- TASK NOT FIXED IN CORE
or
OPE

TASK NOT IN SYSTEM
Self-explanatory.

OPR -- ILLEGAL ERROR CODE RECEIVED FROM SPR2 .•
An internal error has occurred. The multiple device despooler
task has delivered an error code that is not within the range of
acceptable error codes.
Notify the DEC software specialist.
OPR -- ILLEGAL SWITCH COMBINATION
The user specified a stop switch that conflicts either with a
begin spooling switch, and/or a resume switch, for the same
device.
OPR -- INVALID DEVICE SPECIFICATION
The user has specified a device that is not a system generated
device or the device specified is not a carriage controlled unit
record device; e.g., line printer or teleprinter.
OPR -- INVALID OR NONEXISTENT FORM TYPE SPECIFIED
The user specified a form type that is not in the range of

with

6.
OPR -- INVALID SWITCH OR SWITCH VALUE
Self-explanatory.
OPR -- NO COMMAND LINE SPECIFIED
The user typed the OPR
command specification.

command

A-35

without

following

MCR COMMAND SUMMARY AND ERROR MESSAGES
OPR -- NO DEVICE SPECIFIED
or
OPR -- NO SWITCH SPECIFIED
Self-explanatory.
OPR -- SEND/REQUEST TO SPOOLER TASK FAILED
The send/request directive to either the queue manager task (SPR)
or
the multiple device despooler task (SPR2) has failed.
Either
or both of the tasks are not installed.
OPR -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

OPR -- UNKNOWN ARGUMENT TO /RS:

the

command

description

for

the

SWITCH

Self-explanatory.
PWD -- DIRECTIVE FAILURE
An undefinable error occurred during the execution of PWD.
Retry the command.
software specialist.

the

error

reoccurs,

notify

the

DEC

PWD -- NONEXISTENT ACCOUNT
The user is attempting to assign a password to a nonexistent UFD.
PWD -- NON SYSTEM ACCOUNT MAY ONLY MODIFY OWN PASSWORD
Self-explanatory.
PWD -- READ OR WRITE FAILURE ON DIRECTORY ENTRY
One of the following conditions exists:
1.

The UFD does not exist

The file is protected against write access

The volume is not mounted

The volume is off line

The device is not write enabled

The hardware has failed

A-36

MCR COMMAND SUMMARY AND ERROR MESSAGES
PWD -- SYNTAX ERROR
Self-explanatory:
correct syntax.
QUE -- DEVICE dev:

refer

the

command

description

for

the

DOES NOT CONTAIN A DIRECTORY

The user has queued a file to be printed, however
the device
designated as the input device does not contain a directory. All
queue orders up to the device in error have been processed.
Re-enter the command from the point of error specifying a correct
input device.
QUE -- DEVICE dev:

IS NOT SPOOLABLE

The user has queued a file to be printed onto a device that is
not a spoolable device.
Spoolable devices are unit-record
carriage controlled devices: e.g., line printer or teleprinter.
QUE -- ERROR OPENING filename -nn
An error has occured opening the file designated by "filename".
The reason for the failure is determined by -nn, where -nn is a
system standard error code. See Appendix N.
All file specifications up to the file
in error have been
processed.
Correct the error and reinput the command from the
point of failure.
QUE -- ERROR READING SPRQUEUE.SYS FILE -nn
An error has occurred while reading the queue file.
The reason
for
the error is determined by -nn, where -nn is a system
standard error message. See Appendix N.
Notify the system manager.
QUE -- GET COMMAND LINE ERROR -1
An error occurred while reading the indirect command
device has cycled down or the file is corrupted.

file.

The

Obtain a listing of the queue file to determine which commands of
the indirect file have been processed.
Correct the errant
indirect file condition and resume processing from the point of
failure.
QUE -- GET COMMAND LINE ERROR -2
An open failure has occurred on the specified
file.
One of the following conditions exists:

A-37

indirect

command

MCR COMMAND SUMMARY AND ERROR MESSAGES
1.

The user directory does not permit read access to the file.

There is a problem with the
cycled down).

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

physical

device

(e.g.,

device

QUE -- GET COMMAND LINE ERROR -3
The user specified an indirect file in a
conform to syntax rules.

format

that

does

not

QUE -- GET COMMAND LINE ERROR -4
The maximum depth of three indirect files has been exceeded.
Locate the point within the indirect files where the fourth level
of
indirection has been specified.
Delete this level of
indirection. All of the commands up to this point have been
processed. Specify the fourth level of indirection as a separate
command to QUE.
Resume processing of the original indirect
command files at the command following the fourth level of
indirection.
QUE -- NO FILES QUEUED
The user has requested a list of the queue file, but no files are
queued.
This message will also occur if the file
[1,4]SPRQUEUE.SYS is
locked.
If the file
is locked, notify the system manager who
will take the appropriate action.
QUE -- SEQUENCE NUMBER NOT SUPPLIED FOR MODIFY OR KILL
The user has entered a modify
required sequence number.

kill

command

omitting

the

QUE -- SYNTAX ERROR [text string in error]
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

If the command was a modify or kill command, obtain a listing of
the queued file
to determine what part of the command has been
processed. Re-enter the modify or kill command from the point of
failure, correcting the syntax error.
For all other queue
commands no processing has occurred.
Re-enter
the command
correctly.

A-38

MCR COMMAND SUMMARY AND ERROR MESSAGES
REA -- DEVICE NOT IN SYSTEM
The user specified a device mnemonic that has not been
into the system.

generated

REA -- FATAL I/O ERROR
REA, either while reading or writing the task header, encountered
an error. One of the following conditions exists:
1.

The requested file does not exist in the specified UFD

The UFD does not exist

The file is protected against write access

The volume is not mounted

The volume is off line

The device is not wr ite enabled

REA -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
OR
REA

ILLEGAL LUN NUMBER
Self-explanatory.

REA -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

REA -- TASK NOT IN SYSTEM
Self-explanatory.
RED -- CAN'T READ MCR COMMAND BUFFER
REA failed to obtain the command line with which it was
invoked.
This will occur
if RED is invoked using the RUN command, as
opposed to the prescribed method of invoking RED.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.

the

failure

RED -- CIRCULAR REDIRECT CHAIN
The user,
through a
sequence of
Redirect
commands,
established a chain of redirection which returns to old-dev.

A-39

has

MCR COMMAND SUMMARY AND ERROR MESSAGES
RED -- DEVICE NOT KNOWN TO SYSTEM
The user specified a device mnemonic that has not been
into the system.

generated

RED -- HANDLER NOT RESIDENT
This message informs the user that the
redirected device is not resident.
successfully complected.

device handler for
the
The redirect has been

RED -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
Self-explanatory.
RED -- SOURCE DEVICE, OR ITS EXISTING REDIRECT, IS ATTACHED
Self-explanatory; wait until the device becomes
abort the process that has it attached.

unattached,

RED -- SOURCE DEVICE, OR ITS EXISTING REDIRECT IS ATTACHED
Self-explanatory;

dismount the device and retry the command.

RED -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

command

description

for

the

REM -- COMMAND SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

REM -- FAILED TO OPEN @ FILE
The requested indirect command file cannot be found on the volume
indicated.
Either
the file does not exist of the file was
specified incorrectly.
REM -- ILLEGAL ERROR/SEVERITY CODE nl n2 n3
REM failed in its attempt to issue a message to
the user
terminal.
nl contains the value in Rl at the time of the
failure;
n2 contains the value in R2;
and n3 contains the
return address after calling the error message routine.

A-40

MCR COMMAND SUMMARY AND ERROR MESSAGES
NOTE
The high order byte in Rl reflects
severity code between 0 and 2.

the

The low order byte in Rl reflects the
error message REM was trying to issue.
Notify the DEC software specialist.
REM -- ILLEGAL FUNCTION FOR NON-PRIVILEGED USER
Self-explanatory.
REM -- ILLEGAL SWITCH
The user specified a switch that REM does not recognize.
Either
the switch is not a REM switch, or it was specified in the wrong
format.
REM -- INCONSISTENT SWITCH SPECIFIED
The user specified a switch combination that is confusing to REM.
REM -- MAX @ FILE DEPTH EXCEEDED
The indirect command file, specified by the user, has an indirect
command file specification as one of its commands.
REM can
process only one indirect file at a time.
Either recreate
the originally specified file replacing
the
offending
indirect
file
specifier
with the commands if
represents, or enter the required commands manually.
REM

TASK taskname FIXED IN MEMORY.
A task that is fixed in memory cannot be removed.
Unfix the task, then retry the command.

REM

TASK taskname HAS NONZERO POOL USAGE COUNT
The user is attempting to remove a task
that
activity, and
that activity is on-going;
other task, or an I/O operation.
Wait for the initiated
command.

activity

A-4l

complete,

has
initiated an
e.g.
initiated an
then

retry

the

MCR COMMAND SUMMARY AND ERROR MESSAGES
REM -- TASK taskname IS ACTIVE
or
REM -- TASK taskname NOT IN SYSTEM
or
REM

taskname NOT IS SYSTEM
Self-explanatory

REM -- library-name HAS NON-ZERO INSTALL COUNT
The user is attempting to remove a
tasks linked to it.

library

that

has

installed

Remove the installed tasks, then retry the command.
RUN

CAN'T READ MeR COMMAND BUFFER
Run failed to obtain the command line with which it was invoked.
This will occur if RUN is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.

the

failure

RUN -- HANDLER NOT RESIDENT TO LOAD TASK
The device handler task, required to load the requested from
volume on which it resides, is not in the system.

the

Load the required handler task, then retry the command.
RUN -- INSUFFICENT POOL NODES
There are not enough available pool
task.

nodes

run

the

desired

Either wait for a node to become available, or notify the system
manager.
If this has been a persistent problem, the system
manager may want to reconfigure the system.
RUN -- INVALID KEYWORD
The user specified a keyword that either is not a valid
or was specified in an illegal format.

keyword,

RUN -- INVALID TIME PARAMETER
The value assigned to the iRS I
specified in the wrong format.

A-42

switch

either

invalid,

MCR COMMAND SUMMARY AND ERROR MESSAGES
RUN -- INVALID UIC
The UFD specified by the user either
specified in an illegal format.

does

not

exist,

was

RUN -- INVALID PRIORITY
The priority specified in the /PRI switch either exceeds the
maximum allowable (250), or was specified in an illegal format.
RUN -- MEMORY UNAVAILABLE
or
RUN

PARTITION NOT IN SYSTEM
Self-explanatory.

RUN -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

DEC

RUN -- TASK ALREADY ACTIVE
or
RUN -- TASK DISABLED
or
RUN

TASK NOT INSTALLED
Self-explanatory.

RUN -- UNRECOGNIZED DIRECTIVE ERROR
An undefinable error occured during the execution of RUN.
Retry the command.
software specialist.

the

error

reoccurs,

notify

SAY -- *DIAG* SYSTEM CLOCK CHANGED TO A KWIl [L or P]
The system was generated as having a KWIIL or KWIIP clock.
SAY
found
that the clock present in the system is opposite from the
one specified.
SAY continues processing and the system is
started with the clock found as the system clock.
SAV -- *FATAL* BAD BOOT IN LOW MEMORY
The first 32-word block of memory has been corrupted;
most
likely by hardware. One of the following conditions exists:

A-43

MCR COMMAND SUMMARY AND ERROR MESSAGES
1.

The bootstrap routine was written by a
adhere to the rules.

user

who

failed

The hardware failed.

Someone or some running task corrupted real address O.

SAV -- *FATAL* FAILED TO READ MCR BUFFER
SAV failed to obtain the command line with which it was invoked.
This will occur
if SAV is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
persists, notify the DEC software specialist.

the

failure

SAV -- *FATAL* ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
Self-explanatory.
SAV -- *FATAL* dev:

IS STILL LOGGED ON

The user attempted to execute SAV with the specified
still logged on.
Either re-enter the command with the /LOG switch
log the terminals off, and retry the command.
SAV -- *FATAL* dev:

terminal(s)

specified,

IS STILL MOUNTED

The user attempted to execute SAV with
still mounted.

the

specified

Either re-enter the command with the /MOU switch
dismount the devices and retry the command.

device(s)

specified,

SAV -- *FATAL* NO SYSTEM CLOCK RESPONSE, RSX-llD CANNOT RUN
Neither the line frequency clock nor the programable clock will
respond to SAVe
Either there is no clock on the system, or the
clock does not work.
Notify your field service engineer.
SAV -- *FATAL* RO ROOT OF taskname IS LOADED BEYOND END OF SAVE FILE
The read-only root of the named multiuser task is either active
or fixed at an address beyond that which is to be saved. All
active versions of the task must be deactivated
to unload the
read-only root of the task.
SAV -- *FATAL* RO ROOT OF taskname IS LOADING
The Executive has initiated the I/O operations to load the
read-only root of a multiuser task. This is a separate operation
from that used for the impure copies of a multiuser task.

A-44

MCR COMMAND SUMMARY AND ERROR MESSAGES
SAV -- *FATAL* SHAREABLE GLOBAL sga IS LOADED BEYOND END OF SAVE FILE
The named SGA is either active or fixed at an address beyond that
which is to be saved.
One of the following steps must be
performed:
1.

Unload all active or fixed tasks that use the
the SGA to be unloaded.

Reload the SGA at a lower addresss.

SGA

allow

SAV -- *FATAL* SHAREABLE GLOBAL sganame IS LOADING OR EXITING
The Executive has initiated the I/O operations to load an SGA or
write a read/write SGA to disk. The SGA has one of the following
states: load request pending
(GS.LRP), load request queued
(GS.LRQ), and record request queued (GS.RRQ).
The system is not quiescent and a SAVE cannot be performed
these states have disappeared.

until

SAV -- *FATAL* SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

for

the

SAV -- *FATAL* SYSTEM HAS INSUFFICIENT MEMORY
PARTITION parname WAS OCCUPIED BEYOND AVAILABLE MEMORY
THE SYSTEM IS NOT RUNNABLE
This situation is caused by an attempt to truncate a system in
which some entity (task or SGA) was loaded beyond the available
memory.
This error can be caused by bad memory that results in SAVE'S
assuming that such memory does not exist.
If so, call your field
service engineer.
If not, the newly booted system was saved too
large to run on this configuration.
SAV -- *FATAL* TASK taskname HAS I/O IN PROGRESS
The named task has a nonzero I/O in progress count;
therefore,
the system is not quiescent. Wait for the I/O to complete or
abort the task.
SAV -- *FATAL* TASK taskname IS LOADED BEYOND END OF SAVE FILE
The named task is either active or fixed at an address beyond
that which is to be saved. One of the following must be done:
1.

Unfix the task, if it is fixed,

Unload the handler, if the task
load it at a lower address,

Terminate the active task and perhaps
lower address,

Wait for the task to terminate normally.
A-45

handler,
run

and
at

MCR COMMAND SUMMARY AND ERROR MESSAGES
SAV -- *FATAL* TASK taskname IS LOADING OR CHECKPOINTING
The Executive has initiated
the I/O operations to load or
checkpoint the named task.
The task has one of the following
states: load request pending
(TS.LRP), load request queued
(TS.LRQ) ,
The system is not quiescent and a SAVE cannot be performed
these states have disappeared.

until

SAV -- *FATAL* 11/40 TRAP ECO (KTll-D) NECESSARY TO RUN RSX-llD
SAVE detected that a PDP-ll/40 hardware modification
(ECO)
necessary for operation of RSX-llD is either not present or is
failing to operate correctly.
Notify your field service engineer.
SAV -- PARTITION parname EXPANDED BY nnnn*32 (DEC) WORD BLOCKS
SAVE found more memory than was specified at the last save of the
system or at system generation if no previous save occurred. The
extra amount of memory is nnnn
(decimal)
32-word blocks.
The
total memory size has been printed in a previous message. The
named partition has been expanded to use the extra memory.
SAV -- PARTITION parname TRUNCATED BY nnnn*32 (DEC) WORD BLOCKS
SAVE found less memory than was specified at the last save or at
system generation if no previous save occurred. The difference
in memory size is indicated by nnnn
(decimal)
32-word blocks.
The total memory size has been printed in a previous message.
The named partition has been truncated to fix
the memory
available.
SAV -- THE FOLLOWING EMPTY PATRITION(S) TRUNCATED TO ZERO SIZE:
parnamel
parname2

The system has been successfully reduced in size but all of the
named partitions are completely beyond the available memory. Any
attempt to run a
task already installed in one of these
partitions causes the task to be queued on that partition's
memory required list (MRL). The task remains on the MRL until it
is aborted.
Any attempt to install a task in such a partition
results in an INS error message to the effect that the
task is
larger than the partition.
SET -- CAN'T READ MCR COMMAND BUFFER
SET failed to obtain the command line with which it was invoked.
This will occur if SET is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.
A-46

the

failure

MCR COMMAND SUMMARY AND ERROR MESSAGES
SET -- CAN'T SET CHARACTERISTICS FOR THIS TYPE TERMINAL
Self-explanatory;
incompatible.
SET

the

characteristics

specified

are

ILLEGAL CACHE VALUE
A number that was not in the range I through 32,767 (decimal) was
specified in the /CAC=n switch.
Retry the command using a number within the specified range.

SET -- ILLEGAL FUNCTION FOR MACHINE TYPE
The /CAC switch was specified while running on a
than a PDP-II/70.

computer

other

SET -- ILLEGAL FUNCTION FOR NON-PRIVILEGED TERMINAL
or
SET -- PARAMETER ERROR - BAD DEVICE NAME
or
SET -- SPECIFIED DEVICE IS NOT A TERMINAL TYPE DEVICE
OR
SET

SPOOLING NOT SUPPORTED IN THIS RELEASE FOR THIS DEVICE
Self-explanatory.

SET -- SYNTAX ERROR
Self-explanatory;
correct syntax.
SPR

DEVICE dev:

refer

the

command

description

for

the

NOT FOUND IN PUD TABLE

A file has been queued via a PRINT$ macro to a nonexistent system
device. The queue entry is automatically dequeued.
SPR -- ERROR ISSUING SEND REQUEST TO SPR2 .•

-nn

An error occurred when SPR issued a Send/Request directive to the
despooler
task (SPR2 .. ). The reason for the error is determined
by -nn, where -nn is the directive status word (DSW) error code.
SPR -- ERROR ON RECEIVE -nn
An error occurred while SPR was receiving a
Send/Request
directive.
The reason for the error is determined by -nn, where
-nn is the directive status word (DSW) error code.

A-47

MCR COMMAND SUMMARY AND ERROR MESSAGES
SPR -- ERROR READING SPRQUEUE.SYS FILE
or
ERROR WRITING SPRQUEUE.SYS FILE
or
ERROR OPENING SPRQUEUE.SYS FILE
or
ERROR CLOSING SPRQUEUE.SYS FILE

-nn
-nn
-nn
-nn

An error occurred when SPR attempted to access the queue file.
The reason for the error is determined by -nn, where -nn is the
directive status word (DSW) error code.
NOTE
If the error is persistent, the queue file is corrupted.
Perform the queue error procedure documented in the
RSX-IID System Managers Guide.

SPR

INVALID SEQUENCE NUMBER
The sequence number for a kill or modify command
correspond to any sequence number in the queue.

does

not

Retry the command with the correct sequence number specified.
SPR

SPRQUEUE.SYS FILE CAPACITY EXCEEDED
The SPRQUEUE.SYS file has a capacity of 2047 queue orders.
This
capacity has been exceeded, and
the last order has not been
queued.
Avoid adding more orders to be despooled.
Allow the despooler
task to process sufficient orders to create space in the queue.
Then, retry the command.

SPR2 •• -- DEVICE dev:, FAILED TO OPEN FILE
The despooler was unable to open an output file on device (dev:).
The open order is automatically aborted by the despooler. Either
the file to be opened was deleted after a request to print it was
queued, or the volume on which the file resides was dismounted.
SPR2 .. -- DEVICE dev:

TIMED OUT

Three minutes have elapsed since a QIO output order was issued to
device
(dev:).
The multiple device despooler has received no
notification from the handler that the order has completed. This
error normally occurs when the line printer is not in a ready
state, and will be accompanied by a not ready message issued by
the device handler. This message requires no user action.
SPR2 •. -- GET$ ERROR - DEVICE dev:

ERROR CODE -nn

An input error occurred on the device that contains the file
being transfered to device dev:.
The reason for the error is
determined by -nn, where -nn is a system standard error code.
See Appendix N. This message does not require user action.
A-48

MCR COMMAND SUMMARY AND ERROR MESSAGES
SPR2 •• -- GET$ ERROR - DEVICE dev:

- ERROR CODE 40

The despooler encountered an input record size, on device dev:,
that is greater
than 256 bytes.
Printing of the input file is
automatically aborted.
See Appendix N.
SPR2 •. -- INTERNAL ERROR - BAD SEND/REQUEST FROM .•• OPR
OPR, as a result of an aPR command issued by the user,
issued a
send/request directive to the despooler. The request code does
not match the appropriate send/request assigned codes.
Document the occurrence along with the aPR
notify the DEC software specialist.

command

issued,

and

SPR2 •• -- INTERNAL ERROR -- DUPLICATE DEVICES ON DEVICE dev:
The queue manager task directed the despooler
task to
transfer
data to a device (dev:) that is currently being used.
Perform
the corrective action detailed in the RSX-llD System Managers
Guide.
SPR2 •• -- INTERNAL ERROR -- FAILED TO ASSIGN LUN
The despooler task was unable to assign the LUN for a given
device.
This message will be issued as a result of a system
generation in which the required device was deleted.
Perform the corrective action
Manager's Guide.

detailed

the

RSX-IID

System

SPR2 •• -- INTERNAL ERROR -- TOO MANY SIMULTANEOUS DEVICES
The despooler task notified the queue manager
task that it is
The queue
capable of processing n devices simultaneously.
manager task, however, delivered n+l process orders.
Perform the corrective action
Manager's Guide.

detailed

the

RSX-IID

System

SPR2 •• -- INTERNAL ERROR - ZERO COPIES SPECIFIED
The queue manager task requested a despooler operation on a file,
but it also requested that no copies are to be printed. The
queue file may be corrupt.
Perform the corrective action
Manager's Guide.

detailed

the

SPR2 .• -- I/O ERROR ON DEVICE dev: - ERROR CODE

-nn

RSX-IID

System

An I/O error occurred during an output operation on device
(dev:).
The reason for the error is determined by -nn, where -nn
is a system standard error code. See Appendix N.
This message
does not require user action.

A-49

MCR COMMAND SUMMARY AND ERROR MESSAGES
SPR2 .• -- QIOW$ FAILURE ON DEVICE dev: DSW=-nn - DEVICE IN WAIT
A QIO directive error occurred on device dev:.
The reason for
the error is determined by -nn, where -nn is the directive status
word (DSW) error code.
Correct the error
command:

condition,

aPR dev:/RS

to continue

aPR dev:/AB

to abort the operation

SPR2 .• - SEND/REQUEST TO SPR ...
Task SPR •.•

then

issue

the

appropriate

aPR

FAILED

is not installed;

install the task.

SYS -- ILLEGAL SWITCH
The user specified a switch that SYS does not recognize.
Either
the switch is not a SYS switch, or it was specified in the wrong
format.
SYS -- SYNTAX ERROR
The user entered a SYS command in a format that does not
to syntax rules.

conform

TIM -- CAN'T READ MCR COMMAND BUFFER
TIM failed to obtain the command line with which it was invoked.
This will occur
if TIM is invoked using the RUN command, as
opposed to the prescribed method.
Retry the command using the prescribed format.
reoccurs, notify the DEC software specialist.
TIM

the

failure

ILLEGAL FUNCTION FOR NON-PRIVILEGED USER
A non-privileged user is not allowed to modify the time or date.

TIM -- SYNTAX ERROR
Self-explanatory;
correct syntax.

refer

the

command

description

the

UFD -- DEVICE NOT IN SYSTEM
The user specified a device mnemonic ,that has not been
into the system.

A-50

generated

MCR COMMAND SUMMARY AND ERROR MESSAGES
UFO -- DIRECTORY ALREADY EXISTS
Self-explanatory.
UFO -- FAILED TO CREATE DIRECTORY
The device is write
command.

write

locked;

enable

and

retry

the

UFO -- FAILED TO ENTER IN MFD
The UFO command task is unable to establish a
master file directory to the newly created UFD.

pointer

the

directory

I/O

operation

FLX -- FILE ALREADY EXISTS
The user specified an output file
(DOS) device specified.

that

already

exists

Reenter the file specifier using a new or corrected filename.
FLX -- FILE NESTING EXCEEDED
More than one level of indirect files was specified.
Retry with only one level of indirect file specified.

C-4

the

FLX COMMAND SUMMARY AND ERROR MESSAGES
FLX -- FILE NOT FOUND
The named file does not appear in
specified.

the

requested

directory,

Retry with the file name and directory correctly specified.
FLX

FILE OUT OF SEQUENCE
A cassette multivolume file is being accessed out of sequence.
This is a warning message.
stopped by the user.

FLX

The

transfer

will

continue

encountered

during

indirect

unless

@FILE SYNTAX ERROR
A syntax error
processing.

was

command

Edit the indirect command file using either EDI or SLP.

Rerun FLX using the corrected command file.

file

FLX -- FMTD ASCII RECORD FORMAT BAD
or
FLX -- FMTD BINARY RECORD FORMAT BAD
Either the file is corrupted, or the file is not of the specified
type.
If the file is corrupted, there is no recovery possible.
file type is incorrect, retry with the correct type.

the

FLX -- INCORRECT # IN/OUT SPECS
The user specified more than one output specification.
Retry the command with the proper syntax;
specification.

i.e., only one

output

FLX -- INVALID DEVICE
The user specified a device that cannot be utilized as an input
or output device;
i.e., trying to read from a line printer.
Retry with a legal device specified.
FLX -- INVALID DOS OR RT-II FILE SPEC
or
FLX -- INVALID RSX FILE SPEC
The file specifier does not conform to proper syntax;
or
specified device is not supported for the desired operation.
Reenter the file specifier with the proper syntax.

C-5

the

FLX COMMAND SUMMARY AND ERROR MESSAGES
FLX -- INVALID SWITCH
The user has specified a switch that is not a FLX switch, or does
not conform to proper syntax.
Reenter the command specifying the correct switch.
FLX -- I/O ERROR
One of the following conditions exists.
1.

The specified device is not on-line.

The specified volume is not mounted.

A hardware error has occurred (i.e., bad tape).

Ensure that the device is on-line, and the volume is
and in good condition.

Reenter the command.

mounted

FLX -- I/O ERROR DELETING LINKED FILE
An uncorrectable error occurred while a DOS OK
being deleted.

file

was

RSX

No action required - the file is effectively deleted.
FLX -- I/O ERROR INITIALIZING DIRECTORY
/00, /RT, or /RS switch not specified
volume initialization command; or

for

DOS,

RT,

One of the following conditions exists:
1.

The specified device is not on-line.

The specified volume is not mounted.

A hardware error has occurred (i.e., bad tape).

Ensure that the device is on-line, and the volume is
and in good condition.

Reenter the command with the required switch specified.

mounted

FLX -- I/O ERROR ON COMMAND INPUT
An unexpected error in command input was encountered from
an indirect command file or TI:; FLX exits.
Restart FLX.

C-6

either

FLX COMMAND SUMMARY AND ERROR MESSAGES
FLX -- I/O ERROR ON LIST FILE
An error occurred on the output device during a /01 or /LI
sequence.
A hardware problem exists in the output device (e.g.,
device powered down).
1.

Rectify the condition.

Retry the command.

FLX -- OUTPUT DEVICE FULL
The DOS or RT-ll output volume does not contain enough space
the output file.

for

Delete any unnecessary files, and rerun the job.
FLX -- OUTPUT FILE SPEC NOT ALLOWED
The user specified an output file specifier for
does not allow an output file specifier.

command

that

Reenter the command without an output file specifier.
FLX -- RECORD TOO LARGE
FLX has detected an input record
specified or
implied record size
corrupted.

that is larger
than the
for
the file - the file is

The file in question cannot be used with FLX.
FLX -- SPECIFIED RECORD SIZE BAD, 512.

USED

The record size specified by the /FA or /FB switch is not
acceptable. A record size of 512 (decimal) bytes is assumed.
This is a warning message - no action is required.
FLX -- UNABLE TO ALLOCATE FILE
The output volume for
the
space - the volume is full.

specified

file

has

available

Delete any unnecessary files, and rerun the job.
FLX -- UNABLE TO OPEN FILE
The requested file cannot be located in the specified directory.
Reenter the command with the correct file specified.
FLX -- UNABLE TO OPEN LIST FILE
The list file cannot be opened under the specified file name
ufd;
specified device may not be a valid RSX volume.

and

Reenter the command specifying the correct file name, device
ufd.

and

C-7

FLX COMMAND SUMMARY AND ERROR MESSAGES
FLX -- UNDIAGNOSABLE REQUEST
FLX does not recognize the command line syntax.
Reenter the command using the proper syntax.
FLX -- /CO FILES FROM MT:

NOT ALLOWED UNLESS BL:

SPEC

When transferring files from MT:, the /CO switch can be specified
only when the /BL switch is also specified.
Reenter the command specifying the /BL switch.
FLX --

* IN OUTPUT UIC NOT ALLOWED

The ufd field of the output file contains a wild card.
Reenter
the
specified.
FLX

command

with

the

output

file

ufd

explicitly

* IN VERSION NUMBER NOT ALLOWED
A wild card was detected in the version number field
specifier.
Reenter
the
specified.

command

with

all

C-8

version

numbers

file

explicitly

APPENDIX D
Dlo1P COMMAND SUM.ft-lARY AND ERROR MESSAGES

D.I

DMP COMNAND SUMMARY

The DMP utility has one command.

D.2

outfile=infile/switch

Dump a file onto the printer.

where switch = AS

Data should
mode.

dumped

ASCII

BA:n:m

Specifies a base block address.

BL:n:m

Specifies the
first
and
logical blocks to be dumped.

Data should be dumped in byte octal
forma t.

Includes the
data dumped.

the

Causes the current version of
to be printed on the listing.

DMP

Causes starting
(logical)
block
number
and
a
contiguous
or
non-contiguous indication for
the
file to be printed.

MD [: n]

Controls line number
sequencing
during a memory image dump.

file

header

last

DMP ERROR MESSAGES

DMP -- BAD DEVICE NAME
The user has specified an illegal device in a filespecifier.
Reenter the command specifying the correct device.
DMP -- BLOCK SWITCH REQUIRED IN LOGICAL BLOCK MODE
Self-explanatory -- /BL switch must be specified.
Reenter the command with the /BL switch specified.

D-1

DMP COMMAND SUMMARY AND ERROR MESSAGES
DMP -- CANNOT FIND INPUT FILE
The requested file cannot be located in the specified directory.
Reenter the command with the correct filename and ufd specified.
DMP -- COMMAND SYNTAX ERROR
The user has entered a command in a format that does not
with syntax rules.

conform

Reenter the command with the correct syntax.
DMP -- FAILED TO ASSIGN LUN
The user has specified an illegal device in a file specifier.
Reenter the command with the correct device specified.
DMP -- FAILED TO READ ATTRIBUTES
The user has attempted to access a file for
have read access privileges.

which

does

not

Rerun DMP under the correct UIC.
DMP -- ILLEGAL SWITCH
The user has specified a switch that is not a valid DMP switch.
Reenter the command with the correct switch specified.
DMP -- I/O ERROR ON INPUT FILE
or
DMP -- I/O ERROR ON OUTPUT FILE
An error has occurred during I/O to the file, e.g., the device is
off-line.
Correct the situation and retry the command.
DMP -- NO INPUT FILE SPECIFIED
The user has terminated a command without entering an input
specifier.

file

Reenter the command with an input file specified.
DMP -- NO LISTS OR WILD CARDS ALLOWED
The user either entered a command with more
than one input
output filename or entered a wild card in a file specifier.

Reenter the command with only one input file specifier and
output file specifier -- No wild card specifiers allowed.

one

D-2

DMP COMMAND SUMMARY AND ERROR MESSAGES
DMP -- OPEN FAILURE ON INDIRECT FILE
The requested indirect command file does not exist as
One of the following conditions exists.

specified.

The user directory area is protected against an open.
(The
user's UIC is not recognized by the RSX-llD Executive as
being valid for that user directory area.)

A problem exists on the physical device (e.g., device
down) .

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

cycled

DMP -- OPEN FAILURE ON INPUT FILE
or
DMP -- OPEN FAILURE ON OUTPUT FILE
One of the following conditions exists:
1.

The named file doesn't exist as specified.

The volume hasn't been mounted.

The specified file directory does not exist.

A problem exists on the physical device (e.g., device
down).

Determine which condition exists.

Rectify the condition.

Rerun DMP.

D-3

cycled

APPENDIX E
EDI COMMAND SUMMARY AND ERROR MESSAGES

E.l

EDI COMMAND SUMMARY
ADD
A[DD]string

Add the text specified by
"string"
to the end of the
current line.

ADD AND PRINT
AP string

Same as ADD, except the new
current line is printed out.

BEGIN
B[EGIN]

Sets the current line pointer
to
the top of the block
buffer or input file.

BLOCK ON or OFF
BL[OCK] [ON] or [OFF]

Switch editing modes.

BOTTOM
BO[TTOM]

Sets the current line pointer
to the bottom of block buffer
or input file.

CHANGE
[n]C[HANGE]/string-l/string-2

CLOSE
CL[OSE] filespec

Search
for
string-l
and
replace
it with the
text
specified in string-2.
n
allows the user to repeat the
command,
thus
allowing
string-2 to be substituted
for string-l n times.
Transfer the rema1n1ng lines
in the block buffer and the
input file into the output
file,
then close both the
input file and the output
file.

CLOSES
CLOSES

Close secondary input
and
begin selecting
from the input file.
E-l

file,
lines

EDI COMMAND SUMMARY AND ERROR MESSAGES
CLOSE AND DELETE
CDL filespec

Same as the CLOSE command
except that the input file is
deleted.

CONCATENATION CHARACTER
CC character

Change command concatenation
character
to
the specified
character (default is &).

CTRL/Z
~Z

DELETE
D[ELETE] en] or

Same as EXIT if in Edit Mode;
otherwise,
it
causes
an
immediate exit of EDI.
Delete the current and next
n-l lines, if n is positive;
delete n lines preceding the
current line,
but not the
current
line,
if
n
is
negative.

[-n]

DELETE AND PRINT
DP[n] or [-n]

Same as DELETE except that
the
new
current line is
pr in ted out.

END
Same as the BOTTOM command.

E [ND]
ERll.SE
ERASE en]

Erase
the
entire
block
buffer, the current line, and
the next n blocks.

EXIT
EX[IT]

Same as CLOSE command except
that when files are closed,
EDI exits.

EXIT AND DELETE
EDX filespec

Exit
from
the
editing
session,
close
the output
file, delete the input file.

EXIT TO BATCH
EB

Input and output files
closed.
Output
file
delivered to Batch as
input job.

FORM FEED
FF

Insert form feed
buffer.

FILE
FI[LE] filespec

into

are
is
an

block

Transfer lines from the input
file to the file specified by
filespec.

E-2

EDI COMMAND SUMMARY AND ERROR MESSAGES
FIND
[n]F[IND] string

Find the line starting with
"string"
or,
if
n
is
specified
the
nth
line
starting with "string".

INSERT
I [NSERT] [str ing]

Insert "string"
immediately
following
the current line.
If Ii str ing"
is null,
EDI
enters Input Mode.

KILL
KILL

Terminate
this
editing
session;
close
input and
output files;
delete
the
output file.

LINE CHANGE
[n]LC/string-l/string-2

Same as CHANGE except that
all occurrences of string-l
in the current
line
are
changed to string-2.

LIST ON LINE PRINTER
LP

List the text in
the block
buffer or
input file on the
line printer, starting with
the current line.

LIST ON TERMINAL
LI[ST]

Print on user
terminal all
lines in block buffer or all
remaInIng lines
in
input
file,
starting at +n current
line.

LOCATE
[n]L[OCATE] string

Search the block buffer
for
"string"
or,
if
n
is
specified, the nth occurrence
of "str ing" •

MACRO
MA[CRO] x definition

Define macros from
MCALL.

the

file

Define
macro
"definition".

MACRO CALL
~1C [ALL]
MACRO EXECUTE
nM[x]a

Execute
Macro
x
executions
passing
numeric argument a.

MACRO IMMEDIATE
n<definition>

for
n
it
the

Immediate Macro - this allows
the
user
to
define and
execute a macro in one ~tep.

E-3

EDI COMMAND SUMMARY AND ERROR MESSAGES
NEXT
N[EXT] [n] or

[-n]

Establish
a
line + or - n
current line.

NEXT PRINT
NP[n] or [-n]

new
current
lines from the

Next Print;
same as Next
command, but the new current
line is printed out.

OLD PAGE
OL[DPAGE] n

Back up to page n.

OPENS
OPENS filespec

Open secondary input file.

OUTPUT ON or OFF
OU[TPUT] [ON] or [OFF]

Turn output on or off.

OVERLAY
o [VERLAY]

[n]

Delete the current line and
the next n-l lines, and enter
Input Mode.

PAGE
PAG [E] [n]

Enter Block Data Mode, if not
already in Block Data Mode,
and read page n into
the
block buffer.

PAGE FIND
[n] PF [IND] str ing

Identical
to FIND
command
except
that
it
searches
successive pages until
the
nth occurrence of "string" is
found.

PAGE LOCATE
[n]PL[OCATE] string

Same
as
LOCATE
command,
except that successive pages
are searched for
the value
specified by "string".

PASTE
PA[STE]/string-l/string-2

PRINT
P[RINT] [n]

The same as the LINE CHANGE
command except that all lines
in the remainder of the input
file
or block buffer are
searched
for
string-I.
Wherever found,
string-l is
replaced with string-2.
Print out the next line,
and
the next n-l lines, on the
terminal.

READ
REA [0] [n]

Read the next n pages
the block buffer.

E-4

into

EDI COMMAND SUMMARY AND ERROR MESSAGES
RENEW
REN [EW] en]

Write the current buffer, and
read in the next page.

RETYPE
R [ETYPE] [s tr ing ]

Replace the current line with
the
text of "string".
If
"string" is null~
the line
is deleted.

SAVE
SA [VEl en] [filespec]

Save the current line, and
the next n-l lines, in the
file specified by filespec.

SEARCH & CHANGE
SC/string-l/string-2

Search for string-I,
in
the
block buffer or
input file
starting
with
the
line
following
the current line.
When
string-l
is
found,
replace all occurrences
in
line with string-2.

SELECT PRIMARY
SP

Select primary input file.

SELECT SECONDARY
SS

Select secondary input file.

SIZE
SIZE n

Specify maximum number
of
lines to be read
into the
block buffer on a sngle READ.

TAB ON or OFF
TA[B] [ON] or [OFF]

Turn automatic tabbing on
off.

TOP
T[OP]

Same as BEGIN command.

TOP OF FILE
TOF

Returns to
the
top of
the
input file,
in Block Data
Mode, and saves all pages
previously edited.

TYPE
TY[PE]n

Same as PRINT command except
that the current line pointer
does not change.

UNSAVE
UNS[AVE] [filespec]

Retrieve the lines which were
previously saved on filespec
and insert them immediately
following the current line.

E-5

EDI COMMAND SUMMARY AND ERROR MESSAGES
VERIFY ON or OFF
V [ERIFY] [ON] or

[OFF]

Allows user to select whether
or
not search and change
commands are to be verified.

WRITE
W[RITE]

E.2

Write the current block to
the output file,
and erase
the contents of the buffer.

EDI ERROR MESSAGES

The four classes of EDI error messages are:
Command level informational and error messages
File access warning messages
Error messages that result in restarting the editing session
Fatal error messages that result in ED! closing all files and
terminating its execution
The following sections describe all the messages that may be displayed
in each class.
If the recovery procedure is not evident, a suggested
user action is supplied.

E.2.l

Command Level Informational and Error Messages

Messages in this class indicate either information that is designed to
be helpful to the user or errors that were encountered on the previous
command. All messages in
this class are enclosed within square
brackets and are followed by a prompt for a new command.
For example,
the
following output occurs if a delete command encounters an
end-of-buffer in block mode.
[EDI -- *EOB*]

*
Note that immediately following the message, EDI outputs
to prompt for the next command.

asterisk

The messages in this class follow.

[EDI -- ALREADY PASSED THAT PAGE!]
The user has attempted to access a page number that is less
than
the current page.
Prior pages can be accessed only via the
OLDPAGE command.
If the PAGE command has been
incorrectly entered, retype
the
command with the proper page number.
Else use an OLD PAGE command
to access the desired page.

E-6

EDI COMMAND SUMMARY AND ERROR MESSAGES
[EDI -- BUFFER CAPACITY EXCEEDED BY]
offending line
[LINE DELETED]
A READ,
UNSAVE,
INSERT, or OVERLAY command has caused
the
capacity of
the block buffer
to be exceeded.
The line that
caused the overflow is displayed and deleted.
If a new file is being created, empty the
command and continue the editing session.

buffer

with

WRITE

If an existing file is being edited,
it may be possible
to
continue via a RENEW or WRITE command.
Otherwise use the CLOSE
command to close the output file and save all edits.
Reopen
the
output file as the input file and using the SIZE command, reduce
the number of lines read into each buffer;
then, using the PAGE
LOCATE command, search to the position in the file where editing
is to continue.
Occasionally a file that was not created by EDI causes this
message
(i.e., an attempt
to open the file for input produces
this message).
If this occurs, the following procedure may be
used to successfully edit the file.
does
This

Start the editing session by specifying a filename that
not correspond
to any file in the current directory.
causes EDI to create a new file and enter input mode.

Type carriage return to enter edit mode.

Using the SIZE command, reduce the number of lines read
each buffer.

Use the KILL command to terminate the creation of the file.

When EDI prompts for a new file specification, enter the name
of the desired file.

[EDI

into

CONCATENATING CHAR CHANGED TO "&"]
The user has changed the command concatenation character and an
OLDPAGE, TOF, or TYPE command has caused it to be changed back to
i.

&" •

Use
the CC command
to
concatenation character.

reestablish

the

desired

command

[EDI -- CREATING NEW FILE]
The input file specified in the command does not exist and EDI
has created a new file.
EDI automatically enters Input mode and
awaits the input of text lines.
If the intent is to create a new file,
continue
the editing
session entering new lines as required.
Otherwise, enter Edit
mode by typing carriage return;
use
the KILL command
to
terminate the creation of the new file;
and when EDI prompts for
a new file specification, enter the correct file specification.

E-7

EDI COMMAND SUMMARY AND ERROR MESSAGES
[EDI -- ILL CMD]
A command that is not recognized by EDI has been entered;
or a
command that is not compatible with the current edit mode has
been attempted (e.g., a READ command in line-by-line data mode).
[EDI -- ILL NUM]
A non-numeric character has been specified in a numeric field or
a negative number has been entered where only positive numbers
are allowed.
[EDI -- ILL STRING CONST]
A search string specified in a CHANGE, LC, PASTE, or SC command
contains only one command concatenation character, or does not
contain a
matching
string
termination
character
(e.g.,
PASTE/ALPHABETA whereas PASTE/ALPHA/BETA is correct).
[EDI

ILLEGAL IN BLOCK ON MODE]
An attempt has been made to execute a command that is illegal
block mode (e.g., an OUTPUT ON or OFF command).

[EDI

ILLEGAL FILE NAME GIVEN IN CLOSE OR EXIT]

[EDI

FILE WAS NOT RENAMED]

A syntactically incorrect file specifier has been given in a
CLOSE or EXIT command or the attempt to rename the output file
has failed.
The output file is closed under
the name of the input file
without any loss of information.
The Peripheral Interchange
Program (PIP) can be used to rename the file to the desired name.
[EDI

MACRO NOT DEFINED]
An attempt has been made to execute a macro with the
but the specified macro has not been defined.
Use the MACRO command to define
execute it with the M command.

the

desired

macro

M command,
and

then

[EDI -- MACRO NUMERIC ARG UNDEFINED]
A macro has been executed with an M command that did not contain
a numeric argument and the body of the referenced macro contains
the numeric argument replacement character Hi".
Retype the command specifying the appropriate numeric argument.
[EDI

MCALL FILE DOES NOT EXIST]
An MCALL command has been executed to define a set of macros, but
the file MCALL does not exist in the current directory.
The desired set of macro definitions may exist under another UIC.
If this is the case, use PIP to copy or rename the MCALL file
into the current directory.

E-8

EDI COMMAND SUMMARY AND ERROR MESSAGES
[EDI -- NO INPUT FILE OPEN]
A PAGE, READ or RENEW command has been attempted and a new file
is being created.
These commands can be executed only when an
input file is being edited.
[EDI -- NO MATCH]
A CHANGE command has specified a string to be changed that is not
in the current line.
[EDI

OVERLAYING PREVIOUSLY DEFINED MACRO]
A MACRO command has resulted in the redefinition of a previously
defined macro.
This message is merely to make the user aware
that the previous definition is no longer in effect.

[EDI -- SAVE FILE DOES NOT EXIST]
A file was specified in an UNSAVE command that cannot be
in the respective directory.

located

Examine the file specifier to ensure its correctness.
If the
filespecifier
is in error, correct the error, then retry the
command.
[EDI

SECONDARY FILE ALREADY OPEN]
An attempt has been made to open a secondary input file when
another secondary input file is already open. Alternatively, a
CLOSE or KILL command has been executed or an error has been
encountered that causes EDI to restart and the secondary file is
found to be open from the previous edit.
The former case
represents an error, whereas the latter informs the user that he
still has a secondary file open.
Close the secondary input file using the CLOSES command, and then
open the desired secondary file with the OPENS command.

[EDI -- SECONDARY FILE CURRENTLY SELECTED FOR INPUT]
A CLOSE or KILL command has been issued or an error
EDI to restart, when the secondary input file
selected for input.

has caused
is open and

Issue an SP command, CLOSES command and proceed.
[EDI -- SYNTAX ERROR]
A command has been entered that is syntactically incorrect.
[EDI -- TOO MANY CHARS]
A CHANGE, LC, PASTE, or SC command has resulted in a line
that
contains too many characters. EDI limits the length of a line to
132 characters.
Retype the line to ensure that the line is valid.

E-9

EDI COMMAND SUMMARY AND ERROR MESSAGES
[EDI -- *BOB*]
The beginning-of-buffer has been reached.
The current
pointer points to just before the first line in the buffer.
new text lines can be entered before the first line.

line
Thus

[EDI -- *EOB*]
The end-of-buffer has been reached.
The current line pointer now
points to
the beginning of the buffer.
Thus if new lines are
inserted they appear before the first line in the buffer.
[EDI -- *EOF*]
The end-of-file has been reached on the input file.
If the editing session is complete, use the CLOSE or EXIT command
to close
the output file.
Otherwise use the TOF command to
return to the first block in the file and then continue editing
the file.

E.2.2

File Access Warning Messages

Messages in this class represent attempts on the part of the user
to
access directories, files, or devices that are not present in the host
system.
Each message is prefixed with
EDI
and after the message is displayed, EDI returns to command
prints an asterisk to request input.

level

and

The messages in this class follow.
EDI

DEVICE NOT IN SYSTEM - TRY ANOTHER COMMAND
A FILE, OPENS, SAVE, or UNSAVE command contains the specification
of a device that does not exist in the host system.
Reissue the command, specifying only
system.

devices

available

the

EDI -- FILE DOES NOT EXIST
An attempt has been made in a FILE or SAVE command
to create a
file under a ufd that has no directory on the specified volume.
WARNING
The remaining error messages in
this class should not
occur and represent failures
in EDI.
If such errors
persist,
consult
your
DEC
software
support
representative.

E-10

EDI COMMAND SUMMARY AND ERROR MESSAGES
EDI

BAD DEVICE NAME

EDI

BAD FILE NAME

EDI

DEVICE NOT READY

EDI

FILE ALREADY OPEN

EDI

RENAME NAME ALREADY IN USE

EDI

RENAME ON TWO DIFFERENT DEVICES

EDI

WRITE ATTEMPT TO LOCKED UNIT

E.2.3

Error Messages That Result in Restarting the Editing Sessions

The error messages described in this section are caused by conditions
encountered by EDI that make it impossible to continue the current
editing session. EDI closes all open files (with the exception of the
secondary input file),
reinitializes, and then prompts for the next
file to be edited.
As with file access warning messages, each message in
prefixed with:

this

class

EDI -After the appropriate message has been displayed, EDI prompts with:
EDI>
The editing session may be terminated at this point by typing carriage
return or can be continued by entering the next file specifier.
If a
secondary file was open when error condition was encountered,
the
secondary file must be closed using the EDI commands.
The messages in
this class follow.
EDI -- BAD RECORD TYPE-FILE NO LONGER USABLE
The record type defined in the header block of the input file
(primary input, secondary input, UNSAVE, or MCALL)
is not
supported by File Control Services (FCS) and thus the file cannot
be used for input to EDI.
The referenced file has been created without using FCS or
the
file structure on the volume is damaged.
If the latter is the
case, the disk structure verification program VFY should be run
to determine the extent of the damage.
EDI -- FILE IS ACCESSED FOR WRITE
The input file (primary input, secondary input, UNSAVE, or MCALL)
is currently being written by another task.
Wait for the file to be written and then retry the command.

E-ll

EDI COMMAND SUMMARY AND ERROR MESSAGES
EDI -- FILE IS LOCKED TO WRITE ACCESS
The output file
(text output, FILE, or SAVE)
is currently
accessed for
shared read by one or more tasks and is locked
against all writers.
Wait for all readers of
command.

the

file

finish,

then

retry

the

EDI -- ILLEGAL RECORD ATTRIBUTES - FILE NOT USABLE
The record attributes defined in the header block of
the
input
file
(primary input, secondary input, UNSAVE, or MCALL) are not
supported by FCS and thus the file cannot be used for
input
to
EDI.
The referenced file has been created without using FCS or
the
file
structure on
the volume is damaged.
If the latter is the
case, VFY should be run to determine the extent of the damage.
EDI

PRIMARY FILE NOT PROPERLY CLOSED - NOT USABLE - EDITOR
WILL RESTART

When the primary input file was last written, a close chech was
specified and
the writing task did not properly close the file
(e.g., the task was aborted.) Thus the file attributes were not
written and the file may contain inconsistent data.
Exit from EDI by typing carriage return.
Run the peripheral
interchange program
(PIP)
and use the JUN switch to unlock the
file.
Reinitiate EDI and try to recover the data in the file.
EDI

PRIVILEGE VIOLATION
A privilege violation
following reasons:

occurs

during

file

access

for

the

The specified volume is not mounted.

The UIC under which EDI is running does not possess
necessary privileges to access the specified directory.

the

The UIC under which EDI is running does not possess
necessary privileges to access the specified file.

the

Exit from EDI by typing CTRL Z.
Determine
the cause of the
privilege violation.
If the volume is not mounted, then mount it
using the MeR MOUNT command.
Otherwise reinitiate EDI under a
UIC
that has appropriate access privileges to both the specified
directory and the file.
EDI -- RECORD IS TOO LARGE FOR USER BUFFER
The input file (primary input, secondary input, UNSAVE, or MCALL)
being accessed was not created by EDI (or SLP) and contains
records that are too large. The maximum record length supported
by EDI is l3i bytes.

E-12

EDI COMMAND SUMMARY AND ERROR MESSAGES
EDI -- SECONDARY FILE NOT PROPERLY CLOSED - NOT USABLE
When the secondary input file was last written, a close check was
specified and the writing task did not properly close the file
(e.g., the task was aborted).
Thus the file attributes were not
written and the file may contain inconsistent data.
Exit from EDI by typing carriage return.
Run PIP and use the JUN
switch to unlock the file.
Reinitiate EDI and try to recover the
data in the file.
WARNING
The remaining error messages in
this class should not
occur and represent failures
in EDI.
if such errors
persist consult your DEC software support representative.
EDI

BAD DIRECTORY SYNTAX

EDI

DUPLICATE ENTRY IN DIRECTORY

EDI

END OF FILE

EDI

ILLEGAL RECORD ACCESS BITS - FILE NOT USABLE

EDI

ILLEGAL RECORD NUMBER - FILE NOT USABLE

E.2.6 Fatal Error Messages that Result in EDI Closing All Files and
Terminating Its Execution - The fatal error messages represent system
andjor hardware error conditions which make it impossible for
EDI to
continue execution.
All files are closed and EDI terminates its
execution. The output file may be truncated.
Each error _message is
prefixed with:
EDI
and followed by the exit message:
[EDI -- EXIT]
on the next line.
The advanced user can utilize the truncated version of an output file
in
the following manner
to save the editing performed prior to the
fatal error condition
1.

Use PIP to rename the truncated version of the output file to
avoid confusion.

Restart the editing session on the original input file.

Issue an OPENS command specifying the
secondary file.

Issue an SS command to select the secondary file for input.

Issue an ERASE command to erase the first block of the
input
file unless the
truncated output file did not contain the
entire first block.

E-13

renamed

file

the

EDI COMMAND SUMMARY AND ERROR MESSAGES
6.

Issue as many READ 1 and WRITE commands as necessary to reach
the EOF on the secondary file.

Issue an SP command to select the primary file for input.

Issue a CLOSES command to close the secondary file.

Issue a WRITE command to ensure the last
into the output file.

10.

Issue as many READ 1 and ERASE
bypass all
input file blocks
renamed file.

11.

Continue the normal editing session.

block

was

written

commands as necessary to
which are complete in the

The messages in this class follow.
EDI -- CALLER'S NODE EXHAUSTED
System dynamic storage has been depleted and insufficient space
is available to allocate the control blocks necessary to open,
close, read, or write a file.
This probably is a system failure, but also could represent a
transient
overload condition.
Wait until system load has
diminished and reinitiate EDT.
EDI -- DEVICE FULL
Insufficient space exists on the output
output file (text output, FILE, or SAVE).

volume

extend

Determine which volume is being written on.
If it is required
that the specified file be written on this volume, then space
must be made available. Use PIP to purge (/PU) or delete
(IDE)
unwanted files.
EDI -- FILE HEADER CHECKSUM ERROR
An input file (primary input, secondary input, UNSAVE, or MCALL)
has a header block that does not contain a proper checksum.
The file structure on the specified volume is damaged.
to determine the extent of the damage.

Run

VFY

EDI -- FILE HEADER FULL
Insufficient retrieval pointer space exists in the header
to extend an output file (text output, FILE, or SAVE).

block

An attempt is being made to create an output file that is larger
than can be described in a file header block. Split the file
into two or more files and process them separately.

E-14

EDI COMMAND SUMMARY AND ERROR MESSAGES
EDI -- INDEX FILE FULL
File header block is not available to create an output file (text
output, FILE, or SAVE).
When a volume is initialized, the
maximum number of files that may be created on the volume is
established. An attempt has been made to exceed this maximum.
Determine which volume is being referenced.
If it is required
that the specified file be created on this volume, then space
must be made available. Use PIP to purge (/PU) or delete
(/DE)
unwanted files.
WARNING
The following error messages signify
hardware problems.
If possible, all
important files should be removed from
the volume.
If errors persist, consult
the DEC field service representative.
EDI

BAD BLOCK ON DEVICE

EDI

FILE PROCESSOR DEVICE READ ERROR

EDI

FILE PROCESSOR DEVICE WRITE ERROR

EDI

HARDWARE ERROR ON DEVICE

EDI

PARITY ERROR ON DEVICE

WARNING
The remaining error messages in this
class should not occur and represent
failures in EDI.
If
such
errors
persist,
consult
your DEC software
support representative.
EDI

BAD DIRECTORY FILE

EDI

BAD PARAMETERS ON A QIO

EDI

INVALID FUNCTION CODE ON A QIO

EDI

NO BLOCKS LEFT

EDI

REQUEST TERMINATED

EDI

WRITE ATTRIBUTE DATA FORMAT ERROR

EDI

UNEXPECTED ERROR - EDITOR WILL ABORT

TASK " .•• EDI" TERMINATED

E-15

APPENDIX F
SLP COMMAND SUMMARY AND ERROR MESSAGES

F.I

SLP COMMAND SUMMARY

The SLP utility has only one command.
outfile[,listfile/SP or -SP]=infile[/switch]
Performs
batch-oriented
editing
to create and
maintain source language
files on disk or
tape
cassette.
where switch

and where

F.2

AU and -AU

Enable and disable
the
editing
audit
trail,
which
indicates
the
changes made during the
most
recent
editing
session.

BF and -BF

Enable and disable blank
fill when an audit trail
is being produced.

DB and -DB

Enable and disable double
spaced listing.

SP and -SP

Enable and disable
the
spooling of listing files
to
a
file
structure
volume.

SLP ERROR MESSAGES

SLP error messages are issued in two different formats:
SLP followed by two dashes and the error message.
If
applicable,
the command line in error is printed on the next
line.
SLP followed by two
offending filename.

dashes,

F-l

the

error

message

and

the

SLP COMMAND SUMMARY AND ERROR MESSAGES
EXAMPLES
SLP -- SYNTAX ERROR
RICKSFILE;MAC,LP:=SHIRLEY.MAC;2
or
SLP -- OPEN FAILURE LINE LISTING FILE filename
SLP error messages, descriptions, and suggested user
follows.

actions

are

SLP -- COMMAND SYNTAX ERROR
command line
A syntax error has been detected in a command.
This error is fatal,
reinitialized.
That
specifier correctly.

and
is,

causes the editing session to be
the user must re-specify the file

SLP -- ILLEGAL DEVICE NAME
command line
The device specified is not a legal device.
This is a
error;
it causes the editing session to be reinitialized.

fatal

Re-specify the file specifier correctly.
SLP -- ILLEGAL DIRECTORY
command line segment
The directory (ufd) specified is not legally specified. This
a
fatal
error;
it
causes
the editing session to
reinitialized.

is
be

Re-specify the file specifier correctly.
SLP -- ILLEGAL ERROR/SEVERITY CODE pI p2 p3
This error indicates an error in the SLP program.
Retry the command.
If the error persists, contact your DEC field
support representative.
SLP -- ILLEGAL FILE NAME
command line segment
A file specification is greater than 30 characters in length or
contains a wild card
(i.e., an asterisk in place of a file
specification element). This is a fatal error;
it causes the
editing session to be reinitialized.
Re-specify the file specifier correctly.

F-2

SLP COMMAND SUMMARY AND ERROR MESSAGES
SLP -- ILLEGAL GET COMMAND LINE ERROR
This error indicates an error in the SLP program.
Retry the command.
If the error persists, contact your DEC field
support representative.
SLP -- ILLEGAL SWITCH
command line segment
The switch is not a legal SLP switch. This is a fatal error;
causes the editing session to be reinitialized.

Re-enter command line with correct switch specified.
SLP -- INDIRECT COMMAND SYNTAX ERROR
command line
The filename specified for the indirect file does not adhere to
the proper syntax. This is a fatal error;
the currently opened
files are closed, and SLP is reinitialized.
Respecify the indirect file specifier correctly.
SLP -- INDIRECT FILE DEPTH EXCEEDED
command line
More than two indirect files have been specified.
This is a
fatal error;
the currently opened files are closed and SLP is
reinitialized.
Respecify the indirect file specifier correctly.
SLP -- INDIRECT FILE OPEN FAILURE
command line
The indirect file can't be found on the specified volume.
This
is a fatal error;
the currently opened files are closed and SLP
reinitializes.
a.

Respecify the file specifier correctly.

Ensure that the volume is on line and mounted.

SLP -- I/O ERROR COMMAND INPUT FILE
An attempt to read command input has failed.
a.

Ensure that the volume is on line and mounted.

Retry the command.

F-3

SLP COMMAND SUMMARY AND ERROR MESSAGES
SLP -- I/O ERROR COMMAND OUTPUT FILE
An attempt to write command output (i.e., an error
failed.
a.

Ensure that the volume is online and mounted.

Retry the command.

message)

has

SLP -- I/O ERROR CORRECTION INPUT FILE filename
An I/O error has been detected during a read
input file.

Insure that the volume is online and mounted.

Retry the command.

the

correction

SLP -- I/O ERROR LINE LISTING FILE filename
An error has been detected during the writing of the line listing
file.
Usually indicates a problem with a device (disk error,
etc.)
a.

Ensure that the volume is online and mounted.

Retry the command.

SLP -- I/O ERROR SOURCE OUTPUT FILE filename
An attempt to write into the source output file has failed.
a.

Ensure that the volume is on line and mounted.

Retry the command.

SLP -- OPEN FAILURE CORRECTION INPUT FILE filename
The specified correction input file cannot be found;
following conditions exists.

one of

the

The user directory is protected against an open.

There is a problem with the physical device (e.g., device not
online) .

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

This is a fatal error;
SLP reinitializes.

the currently opened files are closed and

Determine which of the above conditions exists.

Rectify the condition.

Respecify the file specifier correctly.

F-4

SLP COMMAND SUMMARY AND ERROR MESSAGES
SLP -- OPEN FAILURE LINE LISTING FILE filename
The file can not be opened for one of the following reasons:
1.

The user directory is protected against an open.

There is a problem with the physical device (e.g., device not
on 1 ine) .

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

This is a fatal error;
reinitialized.

causes

the

editing

session

Determine which of the above conditions exists.

Rectify the condition.

Respecify the filespecifier correctly.

the

SLP -- OPEN FAILURE SOURCE OUTPUT FILE filename
The specified source output file can not be opened;
following conditions exists:

one

The user directory is protected against an open.

There is a problem with the physical device (e.g., device not
on line).

The volume is not mounted.

The specified file directory does not exist.

There is insufficient space on the disk.

This is a fatal error;
reinitialized.

causes

the

editing

session

Determine which of the above conditions exists.

Rectify the condition.

Respecify the file specifier correctly.

SLP -- PREMATURE EOF CORRECTION INPUT FILE filename
An out-of-range line number has been specified in a correction
file or from the terminal e.g., -1000 has been specified for an
800 line file.
1.

Terminate the current editing session.

Restart
number.

the

editing

session,

F-5

entering

the

correct

line

SLP COMMAND SUMMARY AND ERROR MESSAGES
SLP -- PREMATURE EOF COMMAND INPUT FILE
This is caused by typing CTRL Z at the terminal, which sends an
end-of-file to SLP before the / is read. SLP types out SLP),
indicating that a new file specification is expected.
Restart the editing session at the point
inadvertently typed.

F-6

where

the

CTRL/Z

was

APPENDIX G
LBR COMMAND SUMMARY AND ERROR MESSAGES

G.I

LBR COMMAND SUMMARY
COMPRESS
outfile/CO:size:ept:mnt:=infile

CREATE
outfile/CR:size:ept:mnt:type

DELETE
outfile/DE:module-1

Physically
deletes
logically deleted records
on a file and puts all
free space at the end of
the file.
Allocates a
contiguous
library file on a direct
access device.
Deletes library modules
and their
associated entry points
from a file.

[:module-2: .•• :module-n]
DELETE GLOBAL
outfile/DG:global-1

Deletes specified library
module entry
points from a file.

[:global-2: ••. :global-n]
INSERT
outfile/IN=infile-1

Inserts library
into
a library file.

[,infile-2, .•. ,infile-n]
LIST
outfile[,listfile]/switch(es)
/switch(es)=LI

modules

Lists all modules in
library file.

the

Lists all modules in
library
file
and
their entry points.

the
all

Lists all modules in
the
library file and
their
entry
points,
and
provides a
full module
description
including
size, date of insertion,
and version.

G-I

LBR COMMAND SUMMARY AND ERROR MESSAGES
REPLACE
outfile/RP=infile-l
[,infile-2, .•. ,infile-n]
or

Replaces, and in
cases,
inser ts

certain
library

modules
file.

library

outfile=infile-l[/RP]
[,infile-2[/RP] , •.. ,infile-n[/RP]]
SPOOL
outfile,listfile/SP

The
listing
file
is
spooled out for printing.

G-2

LBR COMMAND SUMMARY AND ERROR MESSAGES
G.2

LBR ERROR MESSAGES

LBR -- ILLEGAL GET COMMAND LINE ERROR CODE
The system, for some reason, is unable to read
This is an internal system failure.

command

line.

Retry the command.
LBR -- INPUT ERROR ON filename
The file system, while attempting to process an input
detected an error.

file,

There is a problem with the physical device (e.g., device
down) .

has

cycled

Retry the command.
LBR -- COMMAND SYNTAX ERROR
command line
The user has entered a command in a format that does not
to syntax rules.

conform

Reenter the command with the correct syntax.
LBR

OUTPUT ERROR ON filename
A write error has occurred on
following conditions exists.

the

The volume is full.

The device is write protected.

The hardware has failed.

If the volume is full,
files and rerun LBR.

output

the user should

file.

delete

any

One

the

unneccessary

If the device is write protected the user should write enable the
device, and retry the command.
If the hardware has failed, the user can swap devices and
or wait until the device is repaired, and rerun LBR.

retry,

LBR -- ILLEGAL SWITCH
command line
The user specified a non-LBR switch
invalid context.

legal

switch

Reenter the command line with the correct switch specifications.

G-3

LBR COMMAND SUMMARY AND ERROR MESSAGES
LBR -- INSUFFICIENT DYNAMIC MEMORY TO CONTINUE
The partition in which LBR is running is too small.
Remove the task (LBR) , install it
retry the command.

larger

partition,

and

LBR -- INVALID LIBRARY TYPE SPECIFIED
The user specified an illegal library type in a CREATE command.
OBJ is currently the only valid type.
See Section 7.5.2.
Reenter the command with OBJ specified or implied by default.
LBR -- COMMAND I/O ERROR
LBR encountered an error while retrieving a command line.
Rerun the job.
LBR -- INDIRECT FILE OPEN FAILURE
command line
The requested indirect command file does not exist as
One of the following conditions exists.

specified.

The user directory area is protected against an OPEN.

A problem exists
cycled down).

The volume is not mounted.

The specified file directory does not exists.

The file does not exist as specified.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

with

the

physical

device

(e.g.,

device

LBR -- INDIRECT COMMAND SYNTAX ERROR
command line
The user specified an indirect file in a
conform to syntax rules.

format

Reenter the command with the correct syntax.

G-4

that

does

not

LBR COMMAND SUMMARY AND ERROR MESSAGES
LBR -- BAD LIBRARY HEADER
Either the file is not a library file, or the file is corrupted.
1.

If the file is not a library file, retry the command
proper library file specified.

with

If the file is a proper library file, the user should run the
VFY utility program against the volulme to determine if it is
corrupted.

If the volume is corrupted, it must be reconstructed,
it can be used.

before

LBR -- INDIRECT FILE DEPTH EXCEEDED
command line
An attempt has been made to exceed one level of indirect
files.

command

Rerun the job with only one level of indirect command file.
LBR

I/O ERROR IN INPUT FILE
A read error has occurred on an input file.
conditions may exist.

One of the following

A problem exists with the physical device (e.g.,
up) .

The file is corrupted or the format is wrong.
exceeds 132 bytes.)

The file is a non-object file.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

not

cycled

(Record leng th

(Source file, etc.)

LBR -- OPEN FAILURE ON FILE filename
The file system, while attempting to open a file, has detected an
error. One of the following conditions may exist.
1.

The user directory area is protected against an open.

A problem exists
cycled down).

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

Insufficient contiguous space to allocate the file.

with

the

G-5

physical

device

(e.g.,

device

LBR COMMAND SUMMARY AND ERROR MESSAGES
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

LBR -- INVALID EPT AND/OR MNT SPECIFICATION
The user, when specifying a /CR or /CO command, entered an EPT or
MNT value which was greater than 4096.
Retry the command with the correct value specified.
LBR -- POSITIONING ERROR ON filename
The device is write-locked.
If the device is write-locked, write-enable it and retry.
LBR -- EPT OR MNT EXCEEDED IN filename
The EPT or MNT table limit has been reached during the
of an Insert or Replace command.

execution

Copy the library,
COMPRESS command.

using

Retry the command.

increasing

the

table

space,

the

LBR -- DUPLICATE MODULE NAME "name" IN filename
An attempt has been made to insert (without replacement) a module
into a library that already contains a module with the specified
name.
1.

Determine if the specified input file is the correct file.

If the input file is correct, the user must decide whether to
delete the duplicate module from the library file and insert
the new one. or replac~ the duplicate module by rerunning
LBR with the /RP switch appended to the input file specifier.

LBR

GET TIME FAILED
This error occurs when LBR attempts to execute a GET Time
Parameters directive and fails.
The error is caused by some
system malfunction.
Retry the command.

LBR -- NO MODULE NAMED "module"
The user has attempted to delete a module
specified library file.

that

not

Determine if the module name is misspelled, or if
library file is specified.

Retry the command with module name correctly specified.

G-6

the

the
wrong

LBR COMMAND SUMMARY AND ERROR MESSAGES
LBR

INVALID NAME -- IIname"
A module name or entry point that contains
character has been specified for deletion.

non-Radix-50

NOTE
Radix-50 characters consist of the letters of
the
alphabet A through Z, the numbers a through 9, and the
special characters period (.) and dollar sign ($).
Retry the command with a valid name.
LBR -- LIBRARY FILE SPECIFICATION MISSING
The user has entered a command
file.

without

specifying

the

library

Retry the command with the library file specified.
LBR -- ILLEGAL SWITCH COMBINATION
The user has
combination.

specified switches
See Section 7.6.

tha t

canno t

executed

Retry with command switches in the proper sequence.
LBR -- NO ENTRY POINT NAMED name
The user has attempted to delete an entry point that
the specified library file.

not

Determine if the entry point is misspelled, or if
library file is specified.

the

Retry the command with the entry point correctly specified.

wrong

LBR -- DUPLICATE ENTRY POINT NAMED "name" IN filename
An attempt has been made to insert a module into a library
when both contain an identically named entry point.

file

Determine if the specified input file is the correct
If not, retry with the correct input file specified.

file.

If the input file is the correct file, the user may
the duplicate entry point from the library and rerun.

delete

LBR

TOO MANY OUTPUT FILES SPECIFIED
The user has specified more than two output files.
following assumptions:

LBR makes the

The first output file specified is the output library file.

The second output file specified is the listing file.

The third through n files specified to the left of the
sign are ignored.

No action is required.
were not specified.

equal

LBR continues as though the extra file(s)

G-7

LBR COMMAND SUMMARY AND ERROR MESSAGES
LBR -- I/O ERROR ON OUTPUT FILE
A write error has occurred on
following conditions exists.

the

output

file.

One

the

The volume is full.

The hardware has failed.

The device is write protected.

The user does not have write access privileges to the file.

If the volume is full, the user
files, and retry the command.

should

delete

any

unnecessary

If the hardware has failed, the user can swap devices and retry
the command, or wait until the device is repaired, and retry the
command.
If the device is write protected, the user
it, and retry the command.

should

write

enable

the

System

input

library

If the user does not have write access, consult
Administrator who can take necessary action.
LBR -- EXACTLY ONE INPUT FILE MUST APPEAR WITH /CO
The user has specified no file or more
file in the /CO command.

than

one

Retry the command with only one input file specified.
LBR -- FATAL COMPRESS ERROR
The user's input library file is corrupted or is
file.
No recovery is
reconstructed.

possible.

The

file

not

question

library
must

LBR -- EPT OR MNT SPACE EXCEEDED IN COMPRESS
The user has specified an EPT or MNT table size for
the output
library file
that is not large enough to contain the EPT or MNT
entries used in the input library file.
Reenter
the
specified.

command

with

larger

EPT

MNT

table

size

LBR -- ERROR IN LIBRARY TABLES, FILE filename
The library file is corrupted, or is a non-library file.
If the file is corrupted no restart is possible;
be reconstructed.

the

If the file is a non-library file,
the user should
command with the correct library file specified.

G-8

file

must

retry

the

LBR COMMAND SUMMARY AND ERROR MESSAGES
LBR -- INVALID FORMAT, INPUT FILE filename
The specified input file is not a standard format object file
the input file is corrupted.

Reenter the command with the correct input file specified.
LBR -- OPEN FAILURE ON LBR WORK FILE
The file system, while attempting to open the LBR work file,
detected an error.

has

NOTE
The LBR work file is created on the volume from which LBR
was installed.
One of the following conditions exists:
1.

The volume is full.

The device is write protected.

A problem exists with the physical device.

Determine which of the above conditions exists.

Rectify the condition.

Retry the command.

LBR -- MARK FOR DELETE FAILURE ON LBR WORK FILE
When LBR begins processing commands, it automatically creates a
work file,
and automatically marks it for delete.
For some
reason, this marking for delete failed.
The work file constitutes a lost file, because it does not appear
in any file directory.
The file may be deleted by running the utility (See Chapter 9).
LBR -- ILLEGAL FILENAME
command line
The user has entered one of the following:
1.

A file specifier which contains a wild card.

A file specifier which does not contain a filename or type.

Reenter the command correctly.
LBR -- ILLEGAL DEVICE/VOLUME
command line
The device specifier does not conform to the proper syntax.

G-9

LBR COMMAND SUMMARY AND ERROR MESSAGES

NOTE
A device specifier consists of 2
followed by one or two octal digits.

ASCII

characters

Retry the command with the correct device syntax specified.
LBR -- ILLEGAL DIRECTORY
command line
The ufd field in a file specifier does not conform to the
syntax.

proper

NOTE
ufd syntax consists of a left square bracket, followed by
one to three octal digits, followed by a comma, followed
by one to three octal digits, followed by a right square
bracket.
Retry the command with the correct ufd syntax.
LBR

WORK FILE I/O ERROR
A write error has occurred on the LBR
following conditions exists.
1.

The volume is full.

The device is write protected.

The hardware has failed.

If the volume is full,
files and rerun.

the user

should

work

file.

delete

If the device is write protected, the user
the device, and retry the command.

any

should

One

the

unnecessary
write

enable

If the hardware has failed, the user can swap devices and
or wait until the device is repaired and rerun LBR.

retry,

LBR -- VIRTUAL STORAGE REQUIREMENTS EXCEED 65536 WORDS
This error may occur with maximum size libraries and a single
command line which logically deletes a large number of modules
and entry points, and continues to replace them with an equally
large number of modules and entry points having highly dissimilar
names.
Normally, this message indicates some
error.

sort

internal

Rerun the job, but divide the complicated command line
several smaller command lines which do the same operations.

G-lO

system
into

APPENDIX H
SQZ COMMAND SUMMARY AND ERROR MESSAGES

H.l

SQZ COMMAND SUMMARY

The Squeeze utility has only one command.
SQZ outfile=infile-l
[,infile-2, ... ,infile-n]

H.2

Reduces the size of
programs.

SQZ ERROR MESSAGES

SQZ -- INDIRECT FILE OPEN FAILURE
The requested indirect command file does not exist as
One of the following conditions exists.

specified.

The user directory file is protected against an open.

A problem exists
cycled down) •

The volume is no t moun ted.

The specified file directory does not exist.

The file does not exist as specified.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

with

the

physical

device

{e.g.,

device

SQZ -- INDIRECT COMMAND SYNTAX ERROR
The user has specified an indirect file in a format that does not
conform to syntax rules.
Reenter the command with the correct syntax.
SQZ -- INDIRECT FILE DEPTH EXCEEDED
The maximum depth of indirect command files is one level.
An
attempt has been made to reference an indirect command file when
the current depth of indirect command is already one.
Rerun the job with one level of indirect files.
H-l

SQZ COMMAND SUMMARY AND ERROR MESSAGES
SQZ -- COMMAND I/O ERROR
SQZ has encountered an error while retrieving a command line.
Reenter the command.
SQZ -- COMMAND SYNTAX ERROR
The user has entered a command in a format that does not
with syntax rules.

conform

Reenter the command with the correct syntax.
SQZ -- ILLEGAL SWITCH
The user has specified a switch where none is allowed.
SQZ
no switches, therefore, any switch specification is illegal.

has

Reenter the command without switch specifications.
SQZ -- ILLEGAL FILE SPECIFICATION
The user has entered one of the following:
1.

A file specifier which contains a wild card.

A file specifier which does not contain a filename or type.

Examine the command in error.

Reenter the command correctly.

SQZ -- OUTPUT FILE OPEN ERROR
The file system, while attempting to
(SQZ.TMP),
has
detected an error.
conditions may exist.

open the output file
One of the following

The user directory file is protected against an open.
(The
user's UIC is not recognized by the RSX-1ID Executive as
being valid for that user directory area.)

A problem exists
cycled down) .

The volume is not mounted.

The specified file directory does not exist.

The device is full or write protected.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

with

the

H-2

physical

device

(e.g.,

device

SQZ COMMAND SUMMARY AND ERROR MESSAGES
SQZ -- OUTPUT FILE I/O ERROR
A write error has occurred on
following conditions exists.

the

output

One

file.

The device is full or is write protected.

The hardware has failed.

the

NOTE
The file SQZ.TMP remains intact.
If the volume is full, delete any
SQZ.

unnecessary

files

and

rerun

If a hardware error has occurred, swap devices and rerun SQZ,
wait until the device is repaired, and rerun SOZ.

SQZ -- OUTPUT FILE RENAME ERROR
SCZ has failed in its attempt to rename the SQZ.TMP file
to
the
name specified
in
the output file specifier.
SQZ restarts and
the SQZ.TMP file remains intact.
Rename the SQZ.TMP file to the desired
utility program.

name

using

the

PIP

SQZ -- INPUT FILE OPEN FAILURE
The file system, while attempting to open an input file,
has
detected an error. One of the following conditions may exist.
1.

The user directory file is protected against an open.
(The
user's UIC
is not recognized by the RSX-IID Executive as
being valid for that user directory area) •

A problem exists
cycled down) .

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

with

the

H-3

physical

device

(e.g.,

device

SQZ COMMAND SUMMARY AND ERROR MESSAGES
SQZ -- INPUT FILE I/O ERROR
A read error has occurred on an input file.
conditions may exist.
with

the

physical

One of the following
device

(e.g. ,

device

wrong

(1 ine

length

A problem exists
cycled down) .

The file is corrupted or the format
exceeds 132 bytes) •

The file is a nonsource file.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command.

H-4

(Object file, etc. )

APPENDIX I
VFY COMMAND SUMMARY AND ERROR MESSAGES

1.1

VFY COMMAND SUMMARY
DELETE
listfile,scratchdev=indev/DE
or indev/DE

Resets the marked-for-delete
indicators in the file header
area of those files marked
for deletion, but were never
actually deleted.

FREE
listfile=indev/FR
or indev/FR

Prints out the available
space on a volume.

LIST
listfile, scratchdev=indev/LI
or indev/LI

Lists the entire index file
by file identification.

LOST
listfile, scratchdev=indev/LO
or indev/LO

REBUILD
listfile, scratchdev=indev/RE
or indev/RE
UPDATE
listfile, scratchdev=indev/UP
or indev/UP
READ CHECK
listfile=dev:/RC[:n]
or dev :/RC [: n]

Scans the entire file
structure looking for
files
that
are
not
in
any
directory.
Recovers blocks that appear
to be allocated, but are not
contained in any file.
Allocates blocks that appear
to be available, but
are
actually allocated to a file.
Checks that every block
of every file on specified
volume can be read.

I-I

VFY COMMAND SUMMARY AND ERROR MESSAGES
1.2

VFY ERROR MESSAGES

VFY -- COMMAND SYNTAX ERROR
The command does not conform to command syntax rules.
Re-enter the command with the correct syntax specified.
VFY -- FAILED TO ALLOCATE SPACE FOR TEMP FILE
The volume used for the temp file is full.
Use PIP to delete any unnecessary files, and rerun VFY.
VFY -- FAILED TO ATTACH DEVICE
or
VFY -- FAILED TO DETACH DEVICE
or
VFY -- ILLEGAL DEVICE
The file specifier entered contains an illegal device.
Reenter the command with the correct device specified.
VFY -- ILLEGAL SWITCH
The switch specified is not a valid VFY switch.
Reenter the command with the correct switch specified.
VFY -- I/O ERROR ON INPUT FILE
or
VFY -- I/O ERROR ON OUTPUT FILE
One of the following conditions exists:
1.

The device is not online.

The device is not mounted.

The hardware has failed.

Determine which of the above conditions exists.

Rectify the condition.

Rerun VFY.

VFY -- NO DYNAMIC MEMORY AVAILABLE - PARTITION TOO SMALL
VFY does not have enough buffer space to run.
The system manager must rebuild VFY to increase buffer space.

1-2

VFY COMMAND SUMMARY AND ERROR MESSAGES
VFY -- OPEN FAILURE ON BIT MAP
or
VFY -- OPEN FAILURE ON INDEX FILE
or
VFY -- OPEN FAILURE ON LISTING FILE
or
VFY -- OPEN FAILURE ON TEMPORARY FILE
One of the following conditions exists:

1.2.1

VFY is not running under a system UIC, but it should be.

The named file does not exist as specified.

The device has not been mounted.

Determine which of the above conditions exists:

Rectify the condition.

Rerun VFY.

VFY Error Codes

If VFY cannot access the message files because the system device (SY:)
is not mounted or MO is not loaded, errors are reported in the
following format
VFY -- ERROR CODE nne
where
nne

is one of the error codes contained in Table I-I.

Refer to Section 1.2 for error description and suggested user action.

1-3

VFY COMMAND SUMMARY AND ERROR MESSAGES
Table I-I
VFY Error Codes
ERROR
CODE
1.
2.
3.
4.
5.

6.
7.
8.

9.
10.
11.
12.
13.

VFY ERROR MESSAGE IS:
ILLEGAL DEVICE
OPEN FAILURE ON BIT MAP
OPEN FAILURE ON TEMPORARY FILE
FAILED TO ALLOCATE SPACE FOR TEMP FILE
FAILED TO DETACH DEVICE
FAILED TO ATTACH DEVICE
COMMAND SYNTAX ERROR
I/O ERROR ON INPUT FILE
I/O ERROR ON OUTPUT FILE
ILLEGAL SWITCH
OPEN FAILURE ON LISTING FILE
OPEN FAILURE ON INDEX FILE
NO DYNAMIC MEMORY AVAILABLE - PARTITION TOO SMALL

1-4

APPENDIX J
ZAP COMMAND SUMMARY AND ERROR MESSAGES

J.l

ZAP COMMAND SUMMARY
ZAP>dev:infile[/switch]
or
MCR>ZAP@dev:infile[/switch]
where switch

J.2

= AB

ZAP
commands
are
treated
as
absolute byte addresses within the
file.

Line segment data is listed on user
terminal.

File is opened for read-only.

ZAP ERROR MESSAGES

ZAP -- NO SUCH RELOCATION REGISTER
Relocation registers are numbered 0 through 7.
Retry command using the correct relocation register number.
ZAP -- ADDRESS NOT WITHIN SEGMENT
The specified
specified.

address

Retry command
number.

using

the

was

not

correct

within
address

the

overlay

segment

overlay

segment

ZAP -- NO SUCH SEGMENT
The starting disk block was not the start of any segment
task image.

Retry command using the correct starting disk block address.

J-l

the

ZAP COMMAND SUMMARY AND ERROR MESSAGES
ZAP -- TOO MANY ARGUMENTS
More arguments were given in a command than were expected.
Retry the command using the correct command syntax.
ZAP -- NO SUCH INTERNAL REGISTER
The character following a dollar sign was
internal register.

not

the

name

Retry command using the correct internal register name.
ZAP -- UNRECOGNIZED COMMAND
Possibly, the command contained an illegal character.
Retry command using correct command syntax.
ZAP

NO OPEN LOCATION
A modification command was given with no location open to receive
the data.
Open the desired location and perform modification.

ZAP -- CANNOT BE USED IN BYTE MODE
The commands, @,
as a byte.

and> cannot be used when a location

open

Open location in word mode if it is an even address.
ZAP -- ERROR IN FILE SPECIFICATION
The file specification was not properly formed.
Reenter the file specifier.
ZAP -- OPEN FAILURE FOR TASK IMAGE FILE
The file to be modified could not be opened.
Possibly it does
not exist, or
is locked, or the device was not mounted, or the
user does not have write access to the file.
Check the file specifier for errors; check that the
properly mounted, check file permissions using FIP.

volume

command

ZAP -- ERROR ON COMMAND INPUT
An I/O error occurred while a command was being read.
Possible hardware error;
hardware is operational.

check hardware

J-2

and

retry

ZAP COMMAND SUMMARY AND ERROR MESSAGES
ZAP -- I/O ERROR ON TASK IMAGE FILE
An I/O error occurred while reading or writing
modified.
Possible hardware error;
hardware is operational.

check hardware

and

the
retry

file

command

ZAP -- NOT A TASK IMAGE FILE
An error occurred while the segment description tables were being
constructed.
Possibly, the file is not a task image, /AB was not
specified, or the task image is defective.
Reinitiate ZAP and specify the /AB switch in the file specifier.
ZAP -- VERIFY FAILURE
The V command determined that the actual contents of
did not match the expected contents.

location

Error could be in an indirect file or unexpected content in the
task file.
Locate cause of error, correct error, and retry
command.

J-3

APPENDIX K
MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES

K.I

COMMAND SUMMARY

The MAC command string format is as follows:
objectfile/switch,listfile/switch=sourcel,source2, •.. ,
sourcen/switch
where:
objectfile

- object file specifier for the object
of compliation in the for~at:

file

output

dev:[UIC]filename.tYPiver
listfile

- listing file in the format:
dev: [UIC]filename.tYPiver

source

- input source file specifier in the format
dev:[UIC]filename.tYPi ver

/switch

- assembler control switch. Section 7.3 contains a
summary of the assembler control switches and
their descriptions.

K.I.I

Summary Of Macro Assembler Control Switches

K.I.2

Listing Control Switches

The following switches may only appear in the Listfile specifier.
Switch

Function

/LI:arg

Printed listing requested

/NL:arg

No printed listing requested
NOTE

The optional values for n:arg" are described in
Table K-I.
K-l

MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES
Table K-I
Argument Values for Listing Control Switches
Argument

Function

Default

SEQ

list

Controls the listing of source line sequence
numbers.
Error flags are normally printed on
the line preceding the questionable source
statement.

LOC

list

Controls the listing of the location counter
(this
field
would
not
normally
be
suppressed) .

BIN

list

Controls the listing of the generated
code.

BEX

list

Controls listing of binary extensions;
that
is,
those locations and binary contents
beyond
the source statement.
This is a
subset of the BIN argument.

SRC

list

Controls the listing of the source code.

COM

list

Controls the listing of comments. This is a
subset of the SRC argument and can be used to
reduce listing
time and/or
space
where
comments are unnecessary.

list

Controls listing of macro
repeat range expansions.

definitions

and

list

Controls the listing of
repeat range expansions.

Macro

and

no list

Controls listing of macro expansions.

MEB

no list

Controls listing of macro expansion binary
code.
A LIST MEB causes only those macro
expansion statements producing binary code to
be listed.
This is a subset of the ME
argument.

CND

list

Controls
the
listing
of
unsatisfied
conditions and all .IF and .ENDC statements.
This argument permits conditional assemblies
to be listed without including unsatisfied
code.

no list

Controls listing of all listing directives
having no arguments (those used to alter the
listing level count).

TOC

list

Controls listing of table of contents on pass
I of the assembly.
The full assembly listing
is printed during pass I of the assembly.

K-2

binary

calls

MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES
Table K-I (cont)
Argument Values for Listing Control Switches
Argument

Defaul t

TTM

Console
mode

Controls listing output format.
The TTM
argument (the default case)
causes output
lines to be
truncated
to 72 characters.
Binary code
is printed with the
binary
extensions below the first binary word.
The
alternative (.NLIST TTM) to Teletype mode
is
line printer mode.

SYM

list

Controls the listing of the symbol table
the assembly.

Function

K-3

for

MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES
K.I.3

Function Control Switches

The following
specifier.

switches

may

only

appended

the

Swi tch

Purpose

/EN:arg

Enable the function specified as "arg".

/DS:arg

Disable the function specified as "arg".

objectfile

NOTE
The optional values for "arg" are described in Table K-2.

K-4

MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES
Table K-2
Function Control Arguments
Argument

Default

ABS

disable

Enabling of this function produces absolute
binary output;
i.e., input to the Paper Tape
Software System Absolute Loader.

AMA

disable

Enabling of this
function
directs
the
assembly of all relative addresses (address
mode 67) as absolute addresses (address mode
37).
This switch is useful during
the
debugging phase of program development.

CDR

disable

The statement .ENABL CDR
causes
source
columns 73 and greater to be
treated as
comment. This accommodates sequence numbers
in card columns 73-80.

FPT

disable

Enabling
of
this
function
causes
rather
than
floa ting-poin t
trunca tion,
• DSABL
rounding, as is otherwise performed.
FPT returns to floating point rounding mode.

disable

Enabling of
function
causes
the
this
Assembler
to accept lower case ASCII input
instead of converting it to upper case.

LSB

disable

Enable or disable a local symbol block.
While
a local symbol block is normally
entered by encountering a new symbolic label
or
.PSECT directive,
.ENABL LSB forces a
local symbol block which is not terminated
until a label or a .PSECT directive following
the .DSABL LSB statement is encountered.

PNC

enable

The statement • DSABL PNC inhibits binary
output until an .ENABL PNC is encountered.

REG

enable

The statement .DSABL REG inhibits the default
register definitions. That is, until .DSABL
REG is seen, the following code is implied as
be ing presen t:

Function

RO=%O
RI=%l
R2=%2
R3=%3
R4=%4
R5=%5
SP=%6
PC=%7
The .ENABL REG statement may be used
to
re-enable these definitions. Such use is not
recommended.
GEL

enable

The statement .DSABL GBL inhibits attempts to
resolve references which remain undefined at
the end of pass
1,
as
being
global
references.

K-5

MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES
K.I.4

Assembler Control Switches
Function

Switch
/PA:I

Assemble file during Pass I only

/PA: 2

Assemble file during pass 2 only
NOTE

The above switches
specifier.

apply

only

the

sourcefile

the

listingfile

/SP

Spool output (default)

/-SP

Do not spool output
NOTE
The above switches apply
specifier.

K.2

only

MAC ERROR MESSAGES

MAC -- COMMAND I/O ERROR
An error has been returned by the file system during MACRO-II's
attempt to read a command line. This is an unconditionally fatal
error, causing MACRO-II to exit to the Executive.
No MACRO-II
restart is attempted when this message appears.
MAC -- COMMAND SYNTAX ERROR
An error has been detected in the syntax of the MACRO-II
line.

command

MAC -- ILLEGAL FILENAME
Neither the device name nor the filename is present in the input
file specifier
(i.e.,
the input file specifier is null), or a
wildcard convention (asterisk) is employed in an input or output
file specification. Wildcard specifiers (*) are not permitted in
MACRO-II file specifiers.
MAC -- ILLEGAL SWITCH
An illegal switch is specified for a file, an illegal value is
specified with a switch, or an invalid use of a switch has been
detected by MACRO-II.

K-6

MACRO-II ASSEMBLER COMMAND SUMMARY AND ERROR MESSAGES
MAC -- INDIRECT COMMAND SYNTAX ERROR
The name of the indirect command file
(@filename)
specified
the MACRO-II command line is syntactically incorrect..

MAC -- INDIRECT FILE DEPTH EXCEEDED
More than one indirect command file (@filename) is specified in
the MACRO-II command line.
(Only one level of indirect command
files is permitted in MACRO-II.)
MAC -- INDIRECT FILE OPEN FAILURE
The
indirect command file specified
MACRO-II command line does not exist.

I'@filename"

the

MAC -- INVALID FORMAT IN MACRO LIBRARY
The library file has been corrupted or it was not. produced by the
Librarian Utility Program (LBR).
MAC -- I/O ERROR ON INPUT FILE
In reading a record from a source input file or macro library
file,
an error was detected by the file system, e.g., a line
containing more than 132(10)
characters is encountered.
This
message may also indicate that a device problem exists or that
either a source file or a macro library file has been corrupted
with incorrect data.
MAC -- I/O ERROR ON MACRO LIBRARY FILE
Same meaning as I/O ERROR ON INPUT FILE, except that the file
a macro library file and not a source input file.
MAC

I/O ERROR ON OUTPUT FILE
In writing a record to the object output file or
the listing
output file,
an error was detected by t.he file system. This
message may also indicate that a device problem exists or
that
the storage space on a device has been exhausted (i.e., the
device is full).

MAC -- OPEN FAILURE ON INPUT FILE
The file specified as ufilename" in the input file specifier does
not exist.
MAC -- OPEN FAILURE ON OUTPUT FILE
MACRO-II is unable to create the specified output file.
MAC -- SYMBOL TABLE OVERFLOW
Available symbol table space in dynamic memory has been exceeded.

K-7

APPENDIX L
TKB COMMAND SUMMARY AND ERROR MESSAGES

L.I

TKB COMMAND SUMMARY

The TKB command string format is as follows:
image[/switch(es)] ,map, [/switch(es)]symbol[/switch(es)]=input/switch(es)
where:
image

is the relocatable executable
file) in the format:

task

file

(.TSK

dev: [UIC]filename.tYPiver
map

is the listing device in the format:
dev:

symbol

is the STB file which contains all the global
symbols defined in this task. This file has the
format:
dev: [UIC]filename.tYPiver

input

is the .OBJ file to be task built in the format:
dev: [UIC]filename.typeiver

/switch(es)

is one or more of the TKB control switches.

L-l

TKB COMMAND SUMMARY AND ERROF. MESSAGES
L.l.l

TKB File Switches

Table L-l
Task Image File Switches
Switch

Function

/AB

The task is abor t.able.

/CP

The task is checkpointable.
is assumed.

/DA

A debugging aid is to be loaded wi th the
task.
This
switch causes ODT.OBJ, which resides in the system area
(SY:[l,l],) to be automatically included in
the
task
image. /-DA is assumed.

/DS

The task can be disabled.

/FP

The task uses floating point.

/FX

The task can be fixed in memory.

/FX is assumed.

/HD

The task image includes a header.

/HD is assumed.

/MU

The task is multiuser.

/FI

The task contains only position-independent code.
is assumed.

/PR

The task is privileged.

/SQ

The segments in the task image file are constructed of
P-sections
in the order in which they were encountered
during
input file processing.
The default,
/-SQ,
causes the segments to be constructed alphabetically by
P-section name.

/TA

The task is accountable.

/TR

The processor T bit is to be set in the initial PS word
of the task.
/-TR is assumed.

/XT:n

Exit after any n diagnostics
assumed.

/AB is assumed.
/-CP (not

checkpointable)

/DS is assumed.
/FP is assumed.

/-1'1U is assumed.
I-PI

/-PR is assumed.

/-TA is assumed.

are

produced.

If no swi tches are specified, the resultant task image
following default attributes:

file

/-XT

has

the

/AB,/CP,/-DA,/DS,/-FP,/FX,/HD,/-MU/-PI,/-PR,/-SQ,/-TA,/-TR,/-XT
Memory Allocation Map File Switches
/CR

Produce a cross reference listing.

ISH

Produce a short map.

/SP

Spool the memory allocation file.
L-2

/-CR is assumed.

/-SH is assumed.
/SP is assumed.

TKB COMMAND SUMMARY AND ERROR MESSAGES
Table L-l (cont)
Task Image File Switches
Switch

Function
Symbol Definition File Switches

IPI

The task image contains only position-independent code.
Therefore,
the symbol definition file is written as a
relocatable file (i.e., the symbol definitions may be
relocated). I-PI is assumed.
Input Object File Switches

ICC

The specified file contains concatenated object files.
Note that when ICC is used, it results in an additional
pass of the object file and, therefore, should be used
judiciously.

IDA

The specified file contains a debugging aid (e.g., ODT)
transfer address.
This switch must be included to
specify a debugging aid with a transfer address as an
input file.
It is included so that experimental or
private copies of debugging aids other than ODT may be
included in the task image.

ILB

The specified file contains a user relocatable library
(as built by the RSX-llD Librarian; refer to Part II
of this manual). This library will be searched
to
resolve undefined global symbols.

IMP

The specified file contains an overlay description of
the Task to be built.
If this switch is present, it
must appear on the first input file specification.
See
below.

ISS

Perform selective symbol search.

TKB>/MP
ENTER OPTIONS:
TKB>

OPTIONS

TKB>I

L-3

I-SS is assumed.

TKB COMMAND SUMMARY AND ERROR MESSAGES

OPTIONS:

= ANY DIGIT -- ABORT THE BUILD

ABBRT
ABSPAT

SGNAM:PADDR:VALUE:VALUE: •.• :VALUE

ACTFIL

NUM

= devnam:unit:unit: ..• :unit

ASG

ASG default assignments:
Symbolic
LUN
SYO
SYO
SYO
SYO
TI
CL

1
2
3

4
5
6

BASE

BOUND

COMMON

CNAME:ACCESS:APR

EXTSCT

CNAME:LENGTH

EXTTSK

TASK EXTENSION

FMTBUF

BUFFER EXTENSION

GBLDEF

SNAME:VALUE

GBLPAT

SGNAM:SNAME+OFFSET:VALUE:VALUE: ••. :VALUE

LIBR = LNAME:ACCESS:APR
MAXBUF

= MAXIMUM RECORD BUFFER SIZE

ODTV = SNAME:LENGTH
PAR = PNAME
POOL

= PNUM

PRI

= PNUM

STACK = SNUM
TASK

TASKNAME

TSKV

ADDRESS OF TASK SST VECTOR

UIC = [PROJ,PROG]

L-4

TKB COMMAND SUMMARY AND ERROR MESSAGES
UNITS

L.2

NUNIT

TKB ERROR MESSAGES

The Task Builder produces diagnostic and fatal error messages.
messages are printed in the following forms:

Error

TKB -- *DIAG*-error-message
or
TKB -- *FATAL*-error-rnessage
Some errors are dependent upon correction from the terminal.
If the
user is entering text at the terminal, a diagnostic error message can
be printed, the error corrected, and
the task building sequence
continued.
If the same error is detected by the Task Builder in an
indirect file, the Task Builder cannot request correction and thus the
error is termed fatal and the task build is aborted.
Some diagnostic error messages are simply informative and advise the
user of an unusual condition.
If the user considers the condition
normal to his task, he can install and run the task image.
This appendix tabulates the error messages produced by the Task
Builder.
Most of the error messages are self-explanatory. The Task
Builder prints the text shown in this manual in upper case letters.
In some cases,
the Task Builder prints the line in which the error
occurred, so that the user can examine the line which caused the
problem and correct it.

ILLEGAL GET COMMAND LINE ERROR
System error.

(No recovery.)

COMMAND SYNTAX ERROR
invalid-line
The invalid-line printed has incorrect syntax.

REQUIRED INPUT FILE MISSING
At least one file is required for a task build.

ILLEGAL SWITCH
invalid-line
The invalid line printed contains an illegal switch or switch
value.

NO DYNAMIC STORAGE AVAILABLE
The Task Builder needs additional symbol table storage and
cannot obtain it. The input has exceeded the Task Builder's
capability.

L-5

TKB COMMAND SUMMARY AND ERROR MESSAGES

ILLEGAL ERROR/SEVERITY CODE
System error.

(No recovery.)

COMMAND I/O ERROR
I/O error on command input device.
or possible hardware error.)

(Device may not be online

INDIRECT FILE OPEN FAILURE
invalid-line
The invalid-line contains a reference to a command input file
which could not be located.

INDIRECT COMMAND SYNTAX ERROR
invalid-line
The invalid-line printed contains a
indirect file specification.

syntactically

incorrect

MAXIMUM INDIRECT FILE DEPTH EXCEEDED
invalid-line
The invalid-line printed gives the file reference
exceeded the permissible indirect file depth (2).

10.

I/O ERROR ON INPUT FILE file-name

11.

OPEN FAILURE ON FILE file-name

12.

SEARCH STACK OVERFLOW ON SEGMENT segment-name

that

The segment segment-name is more than 16 branch segments from
the root segment.
13.

PASS CONTROL OVERFLOW AT SEGMENT segment-name
The segment segment-name is more than 16 branch segments from
the root segment.

14.

FILE file-name HAS ILLEGAL FORMAT
The file file-name contains an object module whose format
not valid.

15.

MODULE module-name AMBIGUOUSLY DEFINES P-SECTION p-sect-name
The p-section p-sect-name has been defined in two modules not
on a common path and referenced ambiguously.

L-6

TKB COMMAND SUMMARY AND ERROR MESSAGES

16.

17.

MODULE module-name MULTIPLY DEFINES P-SECTION p-sect-name
1.

The p-section p-sect-name has been defined
segment with different attributes.

A global p-section has been defined in more than one
segment along a common path with different attributes.

the

same

MODULE module-name MULTIPLY DEFINES XFR ADDR IN SEG
segment-name
This error occurs when more than one
root has a start address.

18.

module

comprising

MODULE module-name ILLEGALLY DEFINES XFR ADDRESS
addr

the

p-sect-name

The module module-name is in an overlay segment and has a
start address. The start address must be in the root segment
of the main tree.
19.

P-SECTION p-sect-name HAS OVERFLOWED
A section greater than 32K has been created.

20.

MODULE module-name AMBIGUOUSLY DEFINES SYMBOL sym-name
Module module-name references or defines a symbol
whose definition cannot be uniquely resolved.

21.

sym-name

MODULE module-name MULTIPLY DEFINES SYMBOL sym-name
Two definitions for
the relocatable symbol sym-name have
occurred on a common path.
Or
two definitions for an
absolute symbol with the same name but different values have
occurred.

L-7

TKB COMMAND SUMMARY AND ERROR MESSAGES
22.

SEGMENT seg-name HAS R-O SECTION
An attempt has been made to allocate a read-only p-section in
an overlay segment. The build continues with R-W attribute
forced.

23.

SEGMENT seg-name HAS ADDR OVERFLOW:

ALLOCATION DELETED

Within a segment, the program has attempted to allocate more
than 32K. A map file is produced, but no task image file is
produced.
24.

ALLOCATION FAILURE ON FILE file-name
The Task Builder could not acquire sufficient contiguous disk
space to store the
task image file.
(If possible, delete
unnecessary files on disk to make more room available.)

25.

I/O ERROR ON OUTPUT FILE file-name
This error may occur on any of the three output

26.

LOAD ADDR OUT OF RANGE IN MODULE module-name
An attempt has been made to store data in
outside the address limits of the segment.

27.

files~

the

task

image

TRUNCATION ERROR IN MCDULE module-name
An attempt has been made to load a global value greater
than
+127 or less that -128 into a byte. The low-order eight bits
are loaded.

28.

number UNDEFINED SYMBOLS SEGMENT seg-name
The Memory Allocation File lists
segment.

29.

each

undefined

symbol

INVALID KEYWORD IDENTIFIER
invalid-line
The invalid-line printed contains an unrecognizable keyword.

30.

OPTION SYNTAX ERROR
invalid-line
The invalid-line printed contains unrecognizable syntax.

31.

TOO MANY PARAMETERS
invalid-line
The invalid-line printed
parameters than required.

32.

contains

keyword

with

ILLEGAL MULTIPLE PARAMETER SETS
invalid-line
The invalid-line printed contains multiple parameters
keyword which only allows a single parameter.

L-8

for

TKB COMMAND SUMMARY AND ERROR MESSAGES
33.

INSUFFICIENT PARAMETERS
invalid-line
The invalid-line contains a keyword with an insufficient
number of parameters to complete the keyword meaning.

34.

TASK HAS ILLEGAL MEMORY LIMITS
An attempt has been made to build a task whose
the partition boundary.

35.

size

exceeds

OVERLAY DIRECTIVE HAS NO OPERANDS
invalid-line
All overlay directives except .END require operands.

36.

ILLEGAL OVERLAY DIRECTIVE
invalid-line
The invalid-line printed contains an
directive.

37.

unrecognizable

overlay

OVERLAY DIRECTIVE SYNTAX ERROR
invalid-line
The invalid-line printed contains a syntax error.

38.

ROOT SEGMENT MULTIPLY DEFINED
invalid-line
The invalid-line printed contains the second .ROOT
encountered. Only one .ROOT directive is allowed.

39.

LABEL OR NAME IS MULTIPLY DEFINED
invalid-line
The invalid-line printed contains a name that has
appeared on a .FCTR, .NAME, or .PSECT directive.

40.

directive

already

NO ROOT SEGMENT SPECIFIED
The overlay description did not contain a .ROOT directive.

41.

BLANK P-SECTION NAME IS ILLEGAL
invalid-line
The invalid-line printed contains
does not have a p-section name.

42.

.PSECT

directive

that

The invalid-line printed contains a p-section attribute
is not recognized.

that

ILLEGAL P-SECTION ATTRIBUTE
invalid-line

L-9

TKB COMMAND SUMMARY AND ERROR MESSAGES
43.

ILLEGAL OVERLAY DESCRIPTION OPERATOR
invalid-line
The invalid-line printed contains an unrecognizable
in an overlay description.

44.

TOO MANY NESTED .ROOT/.FCTR DIRECTIVES
invalid-line
The invalid-line printed contains a
.FCTR
exceeds the maximum nesting level (32).

45.

operator

directive

TOO MANY PARENTHESES LEVELS
invalid-line
The invalid-line printed contains a parenthesis that
the maximum nesting level (32).

46.

that

exceeds

UNBALANCED PARENTHESES
invalid-line
The invalid-line printed contains unbalanced parentheses.

47.

ILLEGAL BASE OR TOP ADDRESS OFFSET
The task is too large to fit into the space allowed by
or TOP= keywords.

48.

BASE=

ILLEGAL LOGICAL UNIT NUMBER
invalid-line
The invalid-line printed contains a device assignment to a
unit number larger than the number of logical units specified
by the UNITS keyword or assumed by default if the UNITS
keyword is not used.

49.

ILLEGAL NUMBER OF LOGICAL UNITS
invalid-line
The invalid-line printed contains a number
greater that 250.

50.

ILLEGAL NUMBER OF ACTIVE FILES SPECIFIED

51.

ILLEGAL BASE OR TOP BOUNDARY VALUE
invalid line

52.

ILLEGAL POOL USAGE NUMBER SPECIFIED
invalid line

logical

unit

The pool request is greater than 255 or it is zero.
53.

ILLEGAL DEFAULT PRIORITY SPECIFIED
invalid-line
The invalid-line printed contains
250.

L-10

priority

greater

than

TKB COMMAND SUMMARY AND ERROR MESSAGES

54.

ILLEGAL ODT OR TASK VECTOR SIZE
SST vector size specified greater than 32 words.

55.

ILLEGAL FILENAME
invalid-line
The invalid-line printed contains a wild card (*) in
specification. The use of wild cards is prohibited.

56.

file

ILLEGAL DEVICE/VOLUME
invalid line
The device/volume string is too long.

57.

LOOKUP FAILURE ON FILE filename
invalid-line
The invalid-line printed contains a filename which cannot
located in the directory.

58.

ILLEGAL DIRECTORY
invalid-line
The invalid-line printed contains an illegal UFD.

59.

INCOMPATIBLE REFERENCE TO A LIBRARY P-SECTION p-sect-name
A task has attempted to reference more storage in a shareable
global
area than exists in the shareable global area
definition.

60.

ILLEGAL REFERENCE TO LIBRARY P-SECTION p-sect-name
A task has attempted to reference a p-sect-name existing in a
resident library (shareable global area) but has not named
the library in a COMMON or LIBR keyword.

61.

RESIDENT LIBRARY MEMORY ALLOCATION CONFLICT
keyword-string
One of the following problems has occurred:
three

shareable

been

specified

More than
specified.

The same shareable global area has
than once.

been

Shareable global areas whose memory
have been specified.

allocations

BASE or TOP specifications conflict.

L-ll

global

have

areas

overlap

TKB COMMAND SUMMARY AND ERROR MESSAGES

62.

LOOKUP FAILURE RESIDENT LIBRARY FILE
invalid-line
No symbol table or task image file found
global area on SYO under UFD [1,1].

63.

for

the

shareable

INVALID ACCESS TYPE
invalid-line
Requested access to shareable global area was not RW or RO.

64.

ILLEGAL PARTITION/COMMON BLOCK SPECIFIED
invalid-line
User defined base or length not on
defined length = O.

65.

word

bound

66.

PIC LIBRARIES MAY NOT REFERENCE OTHER LIBRARIES
invalid-line

67.

ILLEGAL APR RESERVATION
APR specified on COMMON or LIBR keyword that is
range 0-7.

total

the

I/O ERROR LIBRARY IMAGE FILE
or

read

LIBRARY REFERENCES UNDEFINED LIBRARY
A shareable global area specified by LIBR
references another area which is undefined.

70.

not used.

71.

INVALID APR RESERVATION
APR specified on a LIBR or COMMON
shareable global area.

72.

memory

outside

An I/O error has occurred during an attempt to open
the Task Image File of a shareable global area.
69.

user

NO MEMORY AVAILABLE FOR LIBRARY library-name
Insufficient virtual memory available to cover
needed ~y referenced shareable global areas.

68.

keyword

COMPLEX RELOCATION ERROR - DIVIDE BY ZERO:
module-name

for

COMMON

absolute

MODULE

A divisor having the value zero was detected
in a complex
expression.
The result of the divide was set to zero.
(Probable cause - division by an undefined global symbol.)

L-12

TKB COMMAND SUMMARY AND ERROR MESSAGES
73.

WORK FILE I/O ERROR
I/O error during an attempt to reference data stored by the
Task Builder 1n a work file.
Possibly an attempt to extend
the file when no more space is available on the volume.

74.

LOOKUP FAILURE ON SYSTEM LIBRARY FILE
The
Task
Builder
cannot
find
the
system
Library
(SYO: [l,I]SYSLIB.OLB) file to resolve undefined symbols.

75.

UNABLE TO OPEN WORK FILE
Work file device is not mounted or has not been
as Files-II, or there is no space on the volume.

76.

NO VIRTUAL MEMORY STORAGE AVAILABLE
Maximum permissible
recovery) .

77.

initialized

size

the

work

file

exceeded

(no

MODULE module-name NOT IN LIBRARY
The Task Builder could not find the module named
switch in the library.

78.

INCORRECT LIBRARY MODULE SPECIFICATION
invalid-line
The invalid-line contains a module name with
character.

79.

non-Radix-50

LIBRAFY FILE filename HAS INCORRECT FORMAT
A module has been requested from a library file that
empty module name table.

80.

the

has

that

has

RESIDENT LIBRARY IMAGE HAS INCORRECT FORMAT
invalid-line
The invalid-line specifies a shareable global area
one of the following problems:
1.

The library file image has a header.

The shareable global area references another shareable
global area with invalid address bounds (i.e., not on 4K
boundary) •

The shareable global area has invalid address bounds.

L-13

TKB COMMAND SUMMARY AND ERROR MESSAGES
81.

PARTITION partition-name HAS ILLEGAL MEMORY LIMITS
The user has attempted
length exceeds 16K.

82.

not used.

83.

ABORTED VIA REQUEST
input-line

build

privileged

task

The input-line contains a request from the user to abort
task build.
84.

not used

85.

END OF FILE REACHED BEFORE .END DIRECTIVE IN file-name
The overlay description file named in this message
contain a .END directive as required.

L-14

does

whose

the

not

APPENDIX M
BATCH COMMAND SUMMARY AND ERROR MESSAGES

M.I

COMMAND SUMMARIES

$COBOL
$COBOL[/sws]

[src/SOURCE]

[obj/OBJECT]

[list/LIST]

[!comments]

$COPY
$COPY [dev:]filename.type/OUTPUT [dev:]filenamel. type [+dev:filename2.type[/INPUT]] [!comments]

$CREATE
$CREATE filename. type

[!comments]

$DATA
$DATA [!comments]
$DELETE
$DELETE filenamel

[filename2 .•. filenamen]

[!comments]

$DIRECTORY
$DIR [filename. type/DIRECTORY]
$DISl-lOUNT
$DISMOUNT lun:

[ ! commen ts]

$EOD
$EOD
$EOJ
$EOJ
$FORTRAN

M-l

[filenamel. typel [/INPUT]]

[!comments]

BATCH COMMAND SUMMARY AND ERROR MESSAGES
$FORTRAN [/sws]

[src/sw]

[obj/OBJECT]

$JOB [/swi tches]

[! commen ts]

[list/LIST]

[!comments]

$JOB

$LINK
$LINK[/switches]

[obj/OBJECT]

[lib/LIBRARY]

[map/MAP]

[task/EXECUTE]

[!comments]

$ IvIACRO
$MACRO [/sws]

[src/SOURCE]

[obj/OBJECr]

[I is tiL 1ST]

[! commen ts]

$MESSAGE
$MESSAGE[/WAIT] message
$MOUNT
$MOUNT dev[/PHYSICAL]

[/switch]

[/VOLUME=x]

[/VID=x] Iun:/LOGICAL [!comments]

$PRINT
$PRINT[filespecl [filespec2 ... filespecn]
$RUN
$RUN filespec
$SORT
$SORT [jsws]

M.2

[inf ile/INPUT]

[outf ile/OUTPUT]

[specf ile/SPECIFICATION]

[! commen ts]

BATCH ERROR MESSAGES

BAT -- ERROR MISSING JOB CARD
1.

A $JOB card did not follow in sequence after a $EOJ.

A $JOB card was omitted at the beginning of the input file.

The submitted $JOB command has an error (i.e., MCR
specified from a non-privileged terminal).

mode

was

In each of the above cases, the error message is printed and all
of the images on the input file are flushed until the next valid
$JOB command is encountered.
Place a $JOB card or command at the appropriate place or
the erroneous $JOB command and resubmit the job.
BAT

correct

ERROR READING INPUT FILE
A physical error has been encountered while the input job file is
read, or an input file contains extraneous records following a
$EOJ command.

M-2

BATCH COMMAND SUMMARY AND ERROR MESSAGES
Verify, by some copy or editing operation, that the file is error
free, and resubmit the job. If extraneous records follow an $EOJ
but all valid jobs have been processed correctly, delete the
extraneous records before the next submission of the batch job.
BAT -- ERROR WRITING OUTPUT FILE
An attempt to issue a write to a disk file has failed
lack of file space on the disk
Delete superfluous files and resubmit the job.

M-3

due

APPENDIX N
SYSTEM STANDARD ERROR CODES

CODE

DESCRIPTION

-01

Unavailable Pool node
or
Bad parameters

-02

Invalid function code

-03

Device not ready

-04

Parity error on device

-05

Un-assigned LUN

-06

Handler task not resident
or
Illegal user buffer

-07

Device not attached

-08

Device already attached

-09

Device not attachable

-10

End of file detected

-11

End of volume detected

-12

Write attempted to locked unit

-13

Data overrun

-14

Send/Receive failure

-15

Request terminated

-16

Privilege violation

-17

Not used

-18

Illegal overlay request

-19

Odd byte count (or virtual address)

-20

Logical block number too large

N-l

SYSTEM STANDARD ERROR CODES
CODE

DESCRIPTION

-21

Invalid UDC module #

-22

UDC connect error

-23

Caller's nodes exhausted

-24

Device full

-25

Index file full

-26

No such file

-27

Locked from file access

-28

File header full

-29

Accessed for write

-30

File header checksum failure

-31

Write attribute data format error

-32

File processor device read error

-33

File processor device write error

-34

File already accessed on LUN

-35

File ID, file number check

-36

File ID, sequence number check

-37

No file accessed on LUN

-38

File was not properly closed

-39

Open - No buffer space available for file

-40

Illegal record size

-41

File exceeds space allocated; no space

-42

Illegal operation on file descriptor block

-43

Bad record type

-44

Illegal record access bit set

-45

Illegal record attributes bit set

-46

Illegal record number

-47

Multiple block Read/Write - not implemented
yet

-48

RENAME - 2 different devices

N-2

- Too large

SYSTEM STANDARD ERROR CODES
CODE

DESCRIPTION

-49

RENAME - new file already in use

-50

Bad directory file

-51

Can't rename - old file system

-52

Bad directory syntax

-53

File already open

-54

Bad file name

-55

Bad device name

-56

Bad block on device

-57

ENTER - duplicate entry in directory

-58

Not enough stack space (FCS or FCP)

-59

Fatal hardware error on device

-60

File ID was not specified

-61

Illegal sequential operation

-62

End of tape detected

-63

Bad version number

-64
to

Unused

-94
-95

Invalid priority (>250.)

-96

Invalid LUN

-97

Invalid event (>64.)

-98

Part of DPB out of user's space

-99

DIC or DPB size invalid

N-3

INDEX
ABO,
5-2, 6-2
ABORT command, 5-2, 6-2
Account numbers, 3-8
ACT, 5-3
Activating MCR, 4-2
ACTIVE TASK LIST command, 5-3
ALT, 6-3
ALTER PRIORITY command, 6-3
ALTMODE, 3-20
ANSI standard, 3-4
BAD, 6-4
BAD BLOCKS command, 6-4
BATCH, 1-8
command summary, M-1
error messages, M-2
pseudo device (BP), 3-1, 3-3
BOO, 6-6
BOOTSTRAP command, 6-6
BP, 3-1, 3-3
BYE, 5-8
CAN, 6-9
CANCEL command, 6-9
Card reader control conventions,
3-22
Checkpointing, 2-8
CI, 3-1, 3-3
CL, 3-1, 3-3
CO, 3-1, 3-3
COM, 5-9
Command, 4-3
Command line, 4-3
Command string, 3-15
Command syntax, 3-15
Command terminal, 4-1
Common areas, 2-10
CON, 5-10
Console input (CI), 3-1, 3-3
Console log (CL), 3-1, 3-3
Console output (CO), 3-1, 3-3
CONTINUE command, 5-10
Conventions, 3-1
CTRL C, 3-20
CTRL I, 3-20
CTRL K, 3-20
CRTL L, 3-20
CTRL 0, 3-21
CTRL Q, 3-21
CTRL R, 3-21
CTRL S, 3-21
CTRL U, 3-21
CTRL X, 3-21
CTRL Z, 3-20
Data pointer, 3-6
Default file specifiers, 3-15, 3-16
INDEX-1

Default file type, 3-16
Despoo1ing, 2-9
dev:, 3-15
DEV, 5-11
DEVICES command, 5-11
Device conventions, 3-1
Device handler, 1-7
Device independence, 2-8
DIS, 6-10
DISABLE command, 6-10
DISMOUNT VOLUME command, 5-12, 6-11
DMO, 5-12, 6-11
DMP, 1-6
command summary, D-1
error messages, D-1
Dump utility (DMP), 1-6
EDI, 1-5
command summary, E-1
error messages, E-6
Editor (EDI), 1-5
ENA, 6-12
ENABLE command, 6-12
ENTER PASSWORD command, 6-35
Entering system commands, 4-3
Error reporting, 4-4
Examples of command strings, 3-18
Execute form of RUN, 6-43
File compression (SQZ), 1-6
File name, 3-5, 3-15
File owner, 3-5
File ownership, 3-8
File protection, 3-6, 3-9
File specifiers, 3-15
File structures, 3-4
File Transfer Program (FLX), 1-5
File type, 3-5, 3-16
Files-II, 3-4
format, 3-5
volumes, 3-5
FIX, 6-13
FIX-IN-MEMORY command, 6-13
FLX, 1-5
command summary, C-l
error messages, C-3
FORTRAN, 1-4
General user commands, 5-1
ABO,5-2
ACT, 5-3
BYE, 5-8
COM, 5-9
CON, 5-10
DEV, 5-11
DMO, 5-12
HEL, 5-14

MOU, 5-18, 6-29
MOUNT command 5-18, 6-29

General user commands (cont.),
LOG, 5-16
LUN, 5-17
MOU, 5-18
OPR, 5-23
PAR, 5-25
PWD, 5-26
QUE, 5-27
RES, 5-39
RUN, 5-40
SYS, 5-42
TAS, 5-52
TIM, 5-53
WHO, 5-54
Group, 3-9

Node pool status program, 8-1
Nonprivileged user, 4-2
OPE, 6-31
OPEN REGISTER command, 6-31
OPERATE command, 5-23, 6-34
OPR, 5-23, 6-34
Overlays, 2-4
Owner, 3-9

Hardware error logging, 1-9
HEL, 5-14
HELLO command, 5-14
Indirect files, 3-19
INI, 6-14
Initialize tape volumes, 6-14,
7-1
INITIALIZE VOLUME command, 6-14
INS, 6-22
LBR, 1-6
command summary, G-l
error messages, G-3
Librarian (LBR) , G-3
LIST COMMON BLOCKS command, 5-9
LOA, 6-27
LOAD command, 6-27
LOG, 5-16
Logical unit numbers, 3-4
LOGICAL UNIT NUMBERS command, 5-17
LUN, 3-4, 5-17

PAR, 5-25
Partitions, 2-1
PARTITIONS command, 5-25
PASSWORD command, 5-26
Peripheral Interchange Program
(PIP), 1-5
PIP, 1-5
command summary, B-1
error codes, B-lO
error messages, B-4
POOL, 8-1
Privileged user, 4-2
Privileged user commands, 6-1
ABO, 6-2
ALT, 6-3
BAD, 6-4
BOO, 6-6
CAN, 6-9
DIS, 6-10
DMO, 6-11
ENA, 6-12
FIX, 6-13
INI, 6-14
INS, 6-22
LOA, 6-27
MEM, 6-28
MOU, 6-29
OPE, 6-31
OPR, 6-34
PWD, 6-35
QUE, 6-36
REA, 6-37
RED, 6-38
REM, 6-40
RUN, 6-41
SAV, 6-47
SET, 6-52
TIM, 6-55
UFD, 6-56
UNF, 6058
UNL, 6-59
Pseudo devices, 3-1
PWD, 5-26, 6-35

MACRO Assembler, 1-4
MACRO-II,
command summary, K-l
control switches, K-l
error mes'sages, K-5
Magnetic tape volumes, 7-1
MAN option for /BAD keyword, 6-18
Master file directory, 3-7
MCR, 4-1
command summary, A-I
error messages, A-I0
MCR timeout, 4-3
MEM, 6-28
Memory parity checking, 1-9
Memory protection, 2-3
Message Output (MO), 3-1, 3-3
MFD, 3-7
MO, 3-1, 3 - 3 .
QUE, 5-27, 6-36
Monitor Console Rout1ne (MCR) , 1-3, QUEUE command, 5-27, 6-36
4-1

INDEX-2

TI, 3-1, 3-3
TIM, 5-53, 6-55
TIME command, 5-53, 6-55
TKB, 1-4
command summary, L-l
error messages, L-4
file switches, L-2
• type , 3-15

REA, 6-37
REASSIGN command, 6-37
RED, 6-38
REDIRECT command, 6-38
REM, 6-40
REMOVE command, 6-40
Request form of RUN, 6-42
RES, 6-39
RESUME command, 6-39
RETURN, 3-20
RUBOUT, 3-2'0
RUN, 5-40, 6-41
RUN command, 5-40, 6-41
execute, 6-43
request, 6-42
run, 6-44
schedule, 6-45
synchronize, 6-46

SAVE command, 6-47
Schedule form of RUN, 6-45
SEND/RECEIVE, 2-11
SET, 6-52
SET command, 6-52
Shareable global areas, 2-9
Shareable libraries, 2-9
Slave terminal, 4-1
SLP, 1-6
command summary, F-l
error messages, F-l
Source Language Input Program (SLP)
1-6
SP, 3-1, 3-3
Spooling, 2-9
Spooling output (SP), 3-1, 3-3
SQZ, 1-6
command summary, H-l
error messages, H-l
/switch, 3-15
SY, 3-1, 3-2
Synchronize form of RUN, 6-46
SYS, 5-42
System commands, 4-3
System device, 3-1, 3-2
System generation, 1-8
System standard error codes, N-l
SYSTEM status command (SYS), 5-42
System test package, 1-9

UIC, 3-8, 4-4
UFD, 3-8, 6-56
ufd, 3-15
UNF, 6-58
UNFIX command, 6-58
UNLOAD command, 6-59
User file directory, 3-8, 6-56
User identification code, 3-8
User privileges, 4-2
Utility programs, 1-5
DMP, 1-6
EDI, 1-5
LBR, 1-6
SLP, 1-6
SQZ, 1-6
VFY, 1-6
ZAP, 1-7
Verification (VFY) , 1-6
Version number, 3-6
iversion, 3-15
VFY, 1-6
command summary, I-I
error codes, 1-4
error messages, 1-2
Volume protection, 3-9
WHO, 5-54
Wildcards, 3-18
World, 3-9
ZAP, 1-7

TAS, 5-52
TASK, 2-3
Task accounting, 1-8
Task Builder (TKB) , 1-4
Task interface, 2-6
Task LIST command, 5-52
Task scheduling, 2-7
Terminal conventions, 3-19
Terminal interface (TI), 3-1, 3-3
Terminal status command (WHO),
5-54

INDEX-3

command summary, J-l
error messages, J-l

RSX-llD User's Guide
DEC-ll-OXDUA-B-D
I

READER'S COMMENTS
NOTE:

This form is for document comments only. Problems
with software should be reported on a Software
Problem Repcrt (SPR) form.

Did you find errors in this manual?

If so, specify by page.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.

Is there sufficient documentation on associated system programs
required for use of the software described in this manual? If not,
what material is missing and where should it be placed?

Please indicate the type of user/reader that you most nearly represent.
[] Assembly language programmer
[] Higher-level language programmer
[] Occasional programmer (experienced)
[] User with little programming experience
[] Student programmer
[] Non-programmer interested in computer concepts and capabilities
Name

Date __________________________

Organization _________________________________________________________________
Street ________________________________________________________________________
City ____________________________ State _____________ Zip Code _______________
or
Country
If you require a written reply,

please check here.

[]

-------------------------------------------------------------Fold lIere------------------------------------------------------------

------------------------------------------------ Do Not Tear - Fold lIere and Staple ----------------------------------------------FIRST CLASS
PERMIT NO. 33
MAYNARD, MASS.
BUSINESS REPLY MAIL
NO POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES

Postage will be paid by:

Software Communications
P. O. Box F
Maynard, Massachusetts 01754

digital equipment corporation

Printed in U.S.A.