Digital PDFs

AA-H625A-TC

June 1979

376 pages

Original

15MB

Document:	RSX-11M System Generation and Management Guide
Order Number:	AA-H625A-TC
Revision:	0
Pages:	376
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V3.2_Jun79/2_Operation/AA-H625A-TC_RSX-11M_V3.2_System_Generation_197906.pdf

OCR Text

•

~·

RSX-11M
System Generation
and Management Guide
Order No. AA-H625A-TC

RSX-11 M Version 3.2

•

.
-

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

digital equipment corporation . maynard, massachusetts

First Printing, June 1979

•·
The information in this document is subject to change without notice
and should not be construed as a conunitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
a:nd may only be used or copied in accordance with the terms of such
license.

•

No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

1979 by Digital Equipment Corporation

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

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

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

5/80-14

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

•

CONTENTS
Page

PFlEFACE
CHAPTER

CHAPTER

INTRODUCTION

1-1

1.1
1.1.1
1.1.2
1.2
1. 3
1. 4
1. 5

OVERVIEW OF SYSTEM GENERATION
Preparing for SYSGEN
The System Generation Command Files
SYSTEM GENERATION FEATURES
FORMAT OF SYSGEN QUESTIONS
LOGICAL FLOW OF SYSGEN QUESTIONS
INVOKING THE SYSGEN COMMAND FILES

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

SETTING UP FOR SYSTEM GENERATION

2-1

2.1
2.2

2-1

2.4.1
2.4.2
2.5

SYSTEM GENERATION ENVIRONMENTS
BOOTSTRAPPING PROGRAMS INTO PROCESSOR
MEMORY
THE RSX-llM SYSTEM GENERATION DISTRIBUTION
KIT
Types of Distribution Kits
Contents of the RSX-llM Release Kit
Standalone DSC
The RSX-llM Baseline System
BACKING UP YOUR DISTRIBUTION KIT AND
BOOTSTRAPPING THE BASELINE SYSTEM
Backing Up Tape Distribution Media
Backing Up Disk Distribution Media
START-UP DISPLAY SEQUENCE

GETTING STARTED

3-1

3.1
3 .1.1
3 .1. 2

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

3.3.2

BIG DISK DISTRIBUTION KITS
Online SYSGENs and PREPGENs
Standalone SYSGENs and PREPGENs
DUAL RK05 DISTRIBUTION KITS
Online SYSGENs and PREPGENs
Standalone SYSGENs and PREPGENs
RLOl DISTRIBUTION KITS
Online SYSGENs and PREPGENs
Standalone SYSGENs and PREPGENs

SUMMARY OF SYSGEN PHASE I QUESTIONS

4-1

4.1
4.2
4.3
4.4
4.5

SUMMARY OF SYSGEN PHASE I SETUP QUESTIONS
SUMMARY OF TARGET AND HOST QUESTIONS
SUMMARY OF EXECUTIVE QUESTIONS
SUMMARY OF TERMINAL DRIVER QUESTIONS
SUMMARY OF PERIPHERAL QUESTIONS

4-1
4-3
4-5
4-11
4-13

DETAILS OF SYSGEN PHASE I

5-1

5.1

SYSGEN SETUP QUESTIONS

5-2

2.3
2.3.1

2.3.2
2.3.3
2.3.4
2.4

CHAPTER

3.2
3.2.1
3.2.2

3.3
3.3.1
CHAPTER

•
CHAPTER

iii

1-1

2-1
2-2
2-2
2-3
2-4
2-5
2-5
2-5
2-7
2-9

3-3
3-4
3-4
3-5
3-6

CONTENTS
Page

CHAPTER

.......

5.2
5.3
5.4
5.5
5.6
5.7

TARGET CONFIGURATION DEFINITION QUESTIONS
HOST CONFIGURATION QUESTIONS
EXECUTIVE QUESTIONS
TERMINAL DRIVER QUESTIONS
PERIPHERAL QUESTIONS
DETAILS OF SYSGEN PROCESSING

5-10
5-15
5-17
5-35
5-43
5-75

SUMMARY OF SYSGEN PHASE II QUESTIONS

6-1

6.1
6.2

SUMMARY OF SYSGEN PHASE II QUESTIONS
SUMMARY OF LOADABLE DRIVER BUILD PHASE

6-1
6-2

DETAILS OF SYSGEN PHASE II

7-1

7.1
7.2
7.3

DETAILS OF SYSGEN PHASE II
DETAILS OF LOADABLE DRIVER BUILD PHASE
DETAILS OF SYSGEN PHASE II PROCESSING

7-3
7-15
7-17

VMR COMMANDS

8-1

8.1
8.2
8.3
8.3.1
8.3.2
8.4
8.5

8-1
8-2
8-3
8-4
8-4
8-4
8-5
8-7
8-8
8-10
8-11
8-13
8-14
8-18
8-20
8-21
8-22
8-23
8-24
8-25
8-29
8-32
8-48

8.6

STARTING VMR
VMR FILE SPECIFIERS
COMMAND SYNTAX
Keywords
Comments
COMMAND SUMMARY
VMR COMMAND DESCRIPTIONS
ALT
ASN.
CAN
DEV
FIX
INS
LOA
LUN
PAR
REA
RED
REM
RUN
SAV
SET
TAS
TIM
UNF
UNL
VMR ERROR MESSAGES

SYSGEN PHASE III

9-1

9.1
9.2

DETAILS OF SYSGEN PHASE III
BLDUMD.CMD FILE DETAILS

9-1
9-11

INSTALLATION VERIFICATION PROCEDURE

10-1

•

10.1
10.2
10.2.1
10.3

INTRODUCTION
HARDWARE
System I/O Exerciser
SOFTWARE

10-1
10-1
10-1
10-1

a-so

8-51
8-52
8-53

CONTENTS
Page
10.3.l
10.3.2
10.4
10.4.1
10.4.2
10.4.3
10.4.4
10.5

CPU-bound Load Test
System Utilities Verification
OPERATING PROCEDURES
Configuration Restrictions
Operating Environment
Operating Instructions
Sample Console Dialogue
ERROR CODES

10-2
10-2
10-2
10-2
10-3
10-3
10-4
10-14

SYSGEN ERROR MESSAGES

11-1

APPENDIX A

SYMBOLS FOR SAVED ANSWER FILES

A-1

APPENDIX B

RMDEMO

B-1

INTRODUCTION
HARDWARE REQUIREMENTS
BENEFITS OF USING RMDEMO
RMDEMO DISPLAY FIELDS
DISPLAY CONFIGURATION OPTIONS

B-1
B-2
B-2
B-3
B-4

CONSOLE DRIVER AND CONSOLE OUTPUT TASK

C-1

OPERATING COT
Task Interfacing with COT
Using the REDIRECT Conunand with COT
COMMAND DESCRIPTIONS
Conunands that Control the Console
Conunands that Control the Log File
Conunands that Control Both the Console
and the Log File
CONSOLE OUTPUT 'l'ERMINAL ERROR MESSAGES

C-1
C-2
C-2
C-3
C-3
C-4

THE QUEUE MANAGER

D-1

NARRATIVE INTRODUCTION AND REVIEW
REFERENCE EXAMPLE
QUEUE MANAGER COMMAND DESCRIPTIONS
STOP
START
SPOOL
UN SPOOL
ASSIGN
DEASSIGN

D-1
D-3
D-3
D-3
D-4
D-6
D-8
D-8
D-9

THE RSX-llM I/O EXERCISER

E-1

INTRODUCTION
What IOX Does
Setting Execution Conditions
Controlling the I/O Exercise
Devices Supported by IOX
SUMMARY OF IOX COMMANDS
INSTALLING, INVOKING, AND RUNNING IOX IN AN
EXERCISE EXAMPLE
Installing IOX
Invoking IOX
Setting Up Your Test Configuration

E-1
F.-1
E-2
E-2
E-3
E-3

•

•
CHAPTER

B.l
B.2
B.3
B.4
B.5
APPENDIX C
C.l
c.i.1
c. l. 2
C.2
C.2.1
C.2.2
C.2.3
C.3
APPENDIX D
D.l
D.2
D.3
D.3.1
D.3.2
D.3.3
D.3.4
D.3.5
D.3.6
APPENDIX E

..
•

E.l
E.1.1
E. l. 2
E. l. 3
E. l. 4
E.2
E.3
E.3.1
E.3.2
E.3.3

C-5
C-6

E-5
E-5
E-6
E-6

CONTENTS
Page
E.3.4
E.3.5
E.3.6
E.3.7
E.4
E.4.1
E.4.2
E.4.3
E.5
E.5.1
E.5.2
E.5.3
E.5.4
E.5.5
E.6
E.6.1
E.6.2
E.7
E.7.1
E.7.2
E.7.3
E.7.4
E.8
E.8.1

E.8.2
E.8.3
E.9
E.10

Setting Up Execution-Time Parameters
E-6
Selecting Units for an I/O Exercise
E-7
Starting an IOX Exercise Execution
E-7
Exiting from IOX
E-7
IOX OPERATIONAL MODES
E-7
Conunand Mode
E-8
Execution Mode
E-8
Interactive Mode
E-8
SETTING EXECUTION-TIME PARAMETERS
E-9
Setting General Execution-Time Conditions E-9
Setting Execution Conditions for Units
with Files-11 Volumes
E-10
Setting Execution Conditions for NonFile-Structured Volumes
E-10
Setting Execution Conditions for Measuring
System Activity
E-il
Directing the Operating System to Execute
Non-IOX Tasks
E-12
I/O EXERCISE OUTPUT
E-12
Activity Reports
E-13
Error Reports
E-14
DISPLAYING IOX STATUS INFORMATION
E-14
Displaying Parameter Settings
E-14
Displaying Unit Status
E-15
Displaying the Units in Your
Conf igurat!,on
E-16
Displayinif the Pa-ttern Setting
E-16
STARTING AND CONTROLLING IOX EXECUTION
E-16
Disabling Interruptions to an I/O
Exercise
E-17
Interrupting IOX to Enter Commands
E-17
Terminating an I/O Exercise and Restarting
IOX
E-17
USING INDIRECT COMMAND FILES WITH IOX
E-17
COMMAND DESCRIPTIONS
E-18
ABORT
E-20
BAD BLOCKS
E-21
BUFFERSIZE
E-22
CONFIGURE
E-22
CONTROL C
E-23
DENSITY
E-24
DESELECT
E-25
ERRORLIMIT
E-25
EXECUTE
E-25
EXIT
E-25
FILESll
E-26
HELP
E-26
INTERLEAVE
E-26
ITERATIONS
E-27
LOGFILE
E-27
PARAMETERLIST
E-28
PATTERN
E-30
PRINT SUMMARY
E-30
PROCEED
E-30
RANDOM
E-31
REPORTERRORS
E-31
RESTART
E-31
RETRIES
E-31

•

CONTENTS
Page
RUNTIME
SELECT
SPY
START
SUMMARYTIME
TEMPORARYFILE
VERIFY
VOLUMECHECK
WAIT
WRITECHECK
IOX MESSAGES
IOX Task Builder Command File

E-32
E-32
E-33
E-33
E-33
E-34
E-34
E-34
E-35
E-35
E-36
E-45

SYSTEM CONVENTIONS

F-1

RSX-llM UIC CONVENTIONS
Group Number
Member Number
NAMING CONVENTIONS

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

APPENDIX G

BUILDING A 4K FCS RESIDENT LIBRARY

G-1

APPENDIX H

HELP TEXT FILES

H-1

APPENDIX I

HARDWARE BOOTSTRAP PROCEDURES

I-1

HARDWARE BOOTSTRAP ROUTINES
RM792-YB Bootstrap ROM
MRll-DB Bootstrap ROM
BM873-YA Bootstrap ROM
BM873-YB Bootstrap ROM
M9301-YA or M9301-YB Bootstrap ROM
M93.0l-YC Bootstrap (PDP-11/70 Only)
M9301-YF Bootstrap ROM

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

•

E.11
E.11.1
APPENDIX F
F.l
F.1.1
F.1.2
F.2

I.l
I.1.1
I.1. 2
I.1.3
I. l. 4
I.l. 5
I.1.6
I. l. 7

FIGURES
:FIGURE

1-1
1-2
2-1
2-2
5-1
5-2

•
•

7-1
B-1

SYSGEN Steps
SYSGEN Command Files and How They
Interrelate
Copying Tape Distribution Kits
Copying Disk Distribution Kits
Processing Steps in SYSGEN Phase I
End-of-Section and End-of-Execution
Breakpoints in the Flow of SYSGEN Phase I
SYSGEN Phase II Processing Steps
Example of RMDEMO Display

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

TABLES
'i'ABLE

5-1
E-1
F-1

SYSGEN Prompt I,ines
Summary of IOX Commands
System Identification Codes

vii

5-45
E-3
F-4

•

•
PREFACE

MANUAL OBJECTIVES
The RSX-llM System Generation and Management Guide is for use in
generating
the
RSX-llM operating system.
This guide provides
information on how to generate an RSX-llM system tailored to a
particular
installation's hardware configuration and application
requirements.

INTENDED AUDIENCE
System generation is a fairly complicated process.
To
fully
understand what is taking place, readers should be familiar with
RSX-llM and its component tasks. This guide is directed toward system
managers (those responsible for tailoring and maintaining installation
specific RSX-llM systems.

STRUCTURE OF THIS DOCUMENT
First, read Chapters 1, 2, and part of 3. Then follow the specific
instructions in Chapter 3.
For complete details on the Phases of
system generation, read Chapters 5, 7, and 9.
Chapter 1 contains an overview of the system generation process.
It
acquaints you with the various phases involved in producing a tailored
system.
Chapter 2 describes the distribution kits
copying the media.

and

Chapter 3 provides information on preparing the
initiating system generation.

•

supplies
host

methods

system

and

for
on

Chapter 4 provides a summary of the Phase I questions •
Chapter 5 provides complete details for the Phase I questions.
Chapter 6 provides a summary of the Phase II questions.
Chapter 7 provides complete details for the Phase II questions.
Chc1pter 8 describes the commands and operation of the Virtual Monitor
Console Routine
(VMR), which initializes the target system in the
final stage of system generation.

Chapter 9 describes the optional phase

system

generation,

Phase

that

system

III.

Chapter 10 describes the means
generation process was a success.

confirming

Chapter 11 supplies an interpretation of the system
messages.

the

generation

error

•

Note that Chapters 5 and 7 conclude with details of an actual system
generation (Chapter 5 contains Phase I, Chapter 7 contains Phase II).
Appendix A defines the symbols of a saved answer file.
Appendix B describes the system display task RMDEMO.
Appendix c describes the Console Output Task
commands.

(COT)

and

defines

COT

Appendix D describes the queue manager.
Appendix E describes the I/O
commands.

Exerciser

(IOX)

and

defines

the

IOX

Appendix G is a listing that describes the means of building a 4K
resident library.

FCS

Appendix F describes RSX-llM system conventions.

Appendix H describes how to use support for DEC supplied Help files.
Appendix I details hardware bootstrap ROMs.

ASSOCIATED DOCUMENTS
The RSX-llM Documentation Directory briefly describes all the manuals
in the RSX-llM documentation set and provides a brief synopsis of each
manual's contents.
The following
lists the manuals most closely
allied to the purposes of this guide:
RSX-llM/M-PLUS
RSX-llM/M-PLUS
RSX-llM/M-PLUS
RSX-llM/M-PLUS

Executive Reference Manual
MCR Operations Manual
I/O Drivers Reference Manual
Task Builder Manual

•

CHAPTER 1
INTRODUCTION

The system generation process, SYSGEN, defines a user
RSX-llM
operating system tailored to meet a specific PDP-11 configuration.
SYSGEN provides the flexibility to generate an RSX-llM system that
fits the many variations of the hardware configuration as well as the
software elements.
This chapter provides an introduction that helps you tailor RSX-llM to
meet your hardware and software needs.

1.1

OVERVIEW OF SYSTEM GENERATION

The system generation process consists of logical
steps
that
ultimately produce an RSX-llM system.
Figure 1-1 summarizes these
steps from preparation and planning,
invoking the SYSGEN command
files,
creating the tailored system, and placing the system on a
taq1et media.

1.1.1

Preparing for SYSGEN

First, backup your RSX-llM distribution kit and become familiar with
the baseline system. The backup copy insures against destruction of
the data on the kit and provides a base for updates to the operating
system that you may receive in the future. The baseline system
controls the system resources during system generation.

''-'

Chapter 2 provides information about the distribution kits and how to
copy the kits to a backup volume.
Chapter 2 also describes the
RSX-llM baseline system.

1.1.2

The System Generation Command Files

RSX-llM indirect command files control system generation.
These
command files are collectively known as SYSGEN. The SYSGEN command
files:
•

Permit you to define the features
excluded from) your system

•

Perform MACR0-11 and Task Builder
executable image of the system

•

Define the system memory requirements

1-1

processing

included
to

(or

produce

INTRODUCTION

Backup
Backup
Tape Volume or Disk Volume

1. Plan for system generation
by reading documentation
and setting up your
hardware configuration.

Distribution Kit
2. Setup for system
generation:
A. Copy the distribution
kit.
B. Bootstrap the baseline
system into processor
memory.

Processor Memory
Baseline
RSX11M.SYS

PDP-11 and Peripherals
3. Define your system by
answering questions in
SYSGEN Phase I:
A. Invoke SYSGEN.

• [200,200] SYSGEN.CMD
• Soun" F;1.,

Command
Files
Selected
Source Files

Command
Files
Object Files

B. Answer questions.
• Command Files
•Selected
~
Source Files
- ~

J·

C. Assemble the executive.
Create a bootable image
of your system in SYSGEN
Phase 11:
A. Invoke SYSGEN2.

SY:
• Command Files _ ~
• Object Files~

B. Task build (TKB) the
Executive device drivers, ~--..._,
and privileged tasks.

Target Volume
RSX11M.TSK

Command Files~~
C. Install your system
tasks and set up
partitions using VMR.

RSX11M.TSK~

RSX11M.SYS~ - - - - . .....

....,...._ _ _

D. Bootstrap your system
in.to processor memory.

Figure 1-1

SYSG EN Steps

1-2

._~

----.~/

RSX11M.SYS

""'

RSX11M.SYS

INTRODUCTION

UTLOBJ

xxx.CMD

::::::Ej
::::::Ej

xxx.OBJ -

,
xxx.CMD

RSX11M.TSK -

~~LJ
I~

UETP

>
.....

5. If necessary, create
executable images of
nonpriv. tasks or of
lab 1/0 peripherals in
SYSGEN Phase Ill:
• Task build nonpriv
or subsystem object
module.

.....

.> •
_....
.....

Install these tasks with
Executive and other
system tasks using
VMR.

c. -- ~
.....
_....c-~
-v
_,....

RSX11M.TSK

RSX11M.SYS

6. Ensure that your system
runs properly by testing
it with the Installation
Verification Procedure.

--e

Figure 1-1 {Cont.}

SYSGEN Steps

SYSGEN executes in three phases or parts.
In Phase I, you define the
target configuration and assemble the Executive and device drivers.
In Phase II,
you task build the Executive, device drivers,
and
privileged system tasks.
In Phase III, you optionally task build
nonprivileged tasks.
When SYSGEN completes processing of Phase I, it has produced object
and command files
to be used as input to SYSGEN Phase II.
Upon
completing Phase II, SYSGEN has produced a system image, complete with
loadable drivers and privileged tasks.
You can then, if necessary,
continue with Phase III and build {or rebuild) nonprivileged tasks.

1.2

SYSTEM GENERATION FEATURES

The system generation dialogue is divided into phases,
designed to generate a separate section of the system:

•

each

phase

Phase I

Ask SYSGEN dialogue questions and assemble source files
for
the Executive,
device drivers, and, if requested,
laboratory and industrial I/O subsystems.

Phase II

Task Build the Executive,
device drivers,
and
all
privileged tasks, define partitions for the system image,
load device drivers, and install tasks.

Phase III -- Optionally, Task Build unprivileged utilities.
SYSGEN Phase I is divided into sections.
The sections either define
logical parts of an RSX-llM system or provide control information for
SYSGEN. The following list shows the sections in SYSGEN Phase I along
with a description of the function performed in each section.

1-3

INTRODUCTION
SYSGEN
Section

Function

Setup

Defines for SYSGEN how to use saved answers
(described below)
and, in general, allows you to
specify the way SYSGEN executes.

Target

Defines for SYSGEN the hardware characteristics of
your target system.

Host

Specifies
whether
you
are
running
SYSGEN
standalone
(on the baseline system) or online (on
a previously generated RSX-llM system)
and also
allows you to specify how you want SYSGEN to
handle listings and maps.

E:Kecutive

Defines the Executive features you want to include
in your RSX-llM target system.

Terminal Driver

Defines the type of terminal driver you
your target system and the software
supported by the driver.

Peripherals

Describes control information for the peripherals
includ~d
in your target system, such as Control
Status Register (CSR) address and vector addresses
for the peripherals.

Assembly

Provides you the opportunity to edit executive
build files or laboratory and I/O build files
before assembly of Executive
and
laboratory
subsystem source files.

want in
features

SYSGEN provides the means to inhibit execution of MCR command lines
during SYSGEN Phase I. This feature allows you to perform a SYSGEN
without actually executing the commands that create, delete, assemble,
or build task images.
MCR command inhibition permits you to follow a
logical path through
SYSGEN without altering existing files.
More importantly it provides
an excellent opportunity for a user to become familiar with SYSGEN
before actually performing a full or "live~ SYSGEN.
SYSGEN provides the means to save answers to questions asked during
SYSGEN Phase I and Phase II. These answers are saved in a file called
SYSSAVED.DAT. You can use this feature to select options and features
for multiple target configurations or to vary the options and features
generated for operating systems to be used on the same processor.
When used in conjunction with MCR command inhibition, you can trace
the logical flow of SYSGEN and then use the saved answers to generate
an actual system.
Three features permit you to execute SYSGEN Phase
I
without
interruption.
When used with saved answers, these features allow you
to generate an RSX-llM operating system unattended.
These three features are:
•

End-of-Section Breakpoints

•

End-of-Execution Breakpoints

•

End-of-Disk Breakpoints

1-4

•

INTRODUCTION
1.3

FORMAT OF SYSGEN QUESTIONS

SYSGEN questions provide a simple means for selecting the features you
want in your system.
Based on your responses, SYSGEN generates
various command files that control the assembly and task building of
your system.
The following question is an example
SYSGEN questions:

that

shows

the

form

most

* 2. Have you made a copy of the distribution kit? [Y/N]:
Each SYSGEN question is preceded by an asterisk and a number.
In
SYSGEN Phase I, there ar~ seven sections;
the questions in each
section are numbered beginning with question number 1. The number is
followed by the text of the question. The text of the question is
followed by a prompt generated by the RSX-llM indirect command file
processor, in this case [Y/N] :.
When SYSGEN asks a question that requires a number as a response,
the
indirect command file processor generates a prompt that specifies the
defaults and appropriate ranges or options, for example:

* 35. Number of preallocated QIO packets [D R:0.-15. D:S]:
The character D following the bracket indicates that the following
numbers are decimal.
R:
specifies the range of numbers you can
enter, in this case from 0 through 15.
D:
following the range
specifies the default value SYSGEN uses when you enter only a carriage
return.
SYSGEN also asks questions that require ASCII strings as responses:

* 50. Memory dump device

(ddu:)

[D: NL:] [S]:

In this case, the character D following the open bracket indicates the
default.
[S]: specifies that an ASCII string response is required.
Where there are exceptions to these general
prompts to explain how to answer questions.

rules,

SYSGEN

displays

When you answer a question with an incorrect value, SYSGEN displays a
message that describes the error and suggests a procedure to correct
the problem.
Error messages are listed alphabetically in Chapter 11.

1.4

LOGICAL FLOW OF SYSGEN QUESTIONS

As described above, questions in SYSGEN sections are numbered.
the questions asked are
However, SYSGEN never asks all questions;
based on the response to previous questions.

)

SYSGEN includes some features automatically when you select certain
option's and prints a message to inform you of their inclusion. More
importantly, when you select an option that requires an option that
you excluded, SYSGEN automatically includes the excluded option and
informs you.

1-5

INTRODUCTION
If you request DBMS support in Executive question
1,
SYSGEN
automatically includes Files-11 support
(which would ordinarily be
asked for in Exective question 2) and displays a message specifying
that Files-11 support is being included:

* 1. Will DBMS-11 be used [Y/N] :Y
Files-11 ACP support will be included
If you had not
question 2:

selected

DBMS,

SYSGEN

would

have

asked

Executive

* 1. Will DBMS-11 be used [Y/N] :N
* 2. FILES-11 ACP [Y/N] :Y
1.5

INVOKING THE SYSGEN COMMAND FILES

As described above, system generation is controlled by command files
known,
collectively, as SYSGEN. There is one command file to control
each phase of SYSGEN:
SYSGEN.CMD
SYSGEN2 .CMD
SYSGEN3.CMD

Controls execution of SYSGEN Phase I
Controls execution of SYSGEN Phase I I
Controls execution of SYSGEN Phase III

You invoke each of these as you
command file:

would

invoke

any

RSX-llM

indirect

@filename
where @ invokes the RSX-llM indirect command file processor and
filename specifies the filename of the command file.
You need not
specify the filetype .CMD when you execute these files.
When each indirect command file completes execution, it generates
prompt:

the

@<EOF>
This prompt indicates that a SYSGEN phase has completed execution.
you want to execute the next Phase, you must invoke it explicitly.

As explained above, each of the three main SYSGEN command files must
be explicitly invoked.
However, SYSGEN.CMD
(the control file for
Phase I) invokes secondary control files, as shown in Figure 1-2.
SYSGEN invokes other command files depending on the type of requests
you make during the SYSGEN dialogue.
These secondary command files
all have the pref ix SGN in their filenames rather than the SYS pref ix
used in the major command files.
SGNEXEC and SGNPER are invoked when you specify that you want to
answer executive and peripherals questions.
SGNICIS or SGNIP is
called when you specify that you have laboratory or I/O subsystem
peripherals
in your configuration.
SGNTT is invoked when you are
answering questions that define terminal driver characteristics.

1-6

INTRODUCTION

'-''

@SYSGEN

@SYSGEN2

@SYSGEN3

SYSGEN2.CMD

SYSGEN3.CMD

,..
::111111111111111111111111111111:.

SYSGEN.CMD

SGNEXEC.CMD

SGNICIS.CMD

Figure 1-2

SGNPER.CMD

SGNIP.CMD

SGNTT.CMD

SYSGEN Command Files and How They Interrelate

1-7

·~I

CHAPTER 2
SETTING UP FOR SYSTEM GENERATION

This chapter provides information on the following topics:

2.1

•

System generation environments

•

Bootstrapping programs into processor memory

•

RSX-llM distribution kit and baseline system

•

Backing up the distribution kit and bootstrapping the baseline
system

•

Startup Display Sequence

SYSTEM GENERATION ENVIRONMENTS

When you generate RSX-llM, an operating system controls the processor.
In an online environment, you are generating RSX-llM under control of
an operating system that has already been
tailored
to
your
hardware/software environment. When you must generate RSX-llM without
such an operating system, you must use the RSX-llM baseline system.
In general, if you are generating RSX-llM in an online environment,
you need not go through many of the setup procedures described below.
If you are generating a new system online, you should protect existing
files and data;
SYSGEN creates and deletes files and uses many UICs
during its execution. You can protect existing files and data by
isolating devices used by SYSGEN from system devices.
For example, if
your system device is normally DBO:
and you have another unit
available, run SYSGEN using DBl:
(for example, ASN DBl:=SY:).
If you are generating RSX-llM on the baseline system, you must
the procedures described in this chapter.

2.2

BOOTSTRAPPING PROGRAMS INTO PROCESSOR MEMORY

Your PDP-11 processor must have a control program resident
in its
memory before you can use the hardware resources.
For the RSX-llM
system generation, two systems are used to control system resources:
the Disk Save and Compress (DSC) standalone system and the RSX-llM
baseline system. DSC is discussed briefly later in this chapter and
in detail
in the RSX-11 Utilities Manual. The following sections
discuss the RSX-llM baseline system.

2-1

SETTING UP FOR SYSTEM GENERATION
These systems are loaded into memory using hardware bootstrap routines
in PDP-11 Read~only Memory (ROM).
Ensure that you know which of the
bootstrap ROMs is in your processor.
The keys on the console panel of your processor provide control
functions you can use to bootstrap control programs into processor
memory. These console functions are contLolled by switches which vary
in appearance on different processors.
Refer to the Processor
Handbook for your processor for explanations of these functions.

2.3

THE RSX-llM SYSTEM GENERATION DISTRIBUTION KIT

.....

RSX-llM distribution kits are the tape or disk media that contain the
source, object, task, and command files you need to build your RSX-llM
system.
Regardless of whether your kit is a disk kit or a tape kit, RSX-llM
system generation is always done using disks;
if you receive a tape
distribution kit, the tape(s) contains images for a particular type of
disk kit.
There are three types of kits:
the dual RKOS kit, the RLOl kit,
and
the big disk kit. The term "big disk kit" refers to the type of kit
on which the entire distribution kit can be stored on a single disk
volume.
Big disk media can be one of the following:
RK06/RK07
RM02/RM03
RP02/RP03
RP04/RP05/RP06
This section describes the types of RSX-llM distribution
contents of each kit, and how to backup a kit.

2.3.l

kits,

the

Types Of Distribution Kits

RSX-llM is distributed on either disk or tape. Whether your kit is on
disk or tape, create a backup copy on disk before you try to generate
you.r system.
The backup of the distribution kit provides a base against which you
can update your system when you receive patches from DEC. Also, the
backup provides you with a spare volume with which to retry SYSGEN in
case you destroy important files or otherwise make your system
unusable.

2.3.1.1 Disk Distribution Kits - Disk kits are distributed on three
types of disk media.
The following list shows the disk type and the
number of disks in the kit:
Type of
Kit

Number of
Disks

RKOS
RLOl
Big Disk Kit (the RK06 or RK07 only)

6
4

For big disk kits, only RK06 or RK07 disks are physically distributed,
other big disk kits are furnished on magtape.
2-2

SETTING UP FOR SYSTEM GENERATION
2.3.1.2 Tape Distribution Kits - RSX-llM is distributed on 6 types of
tape kits.
Each tape must be copied to disk using DSC before
performing the SYSGEN;
each tape contains DSC images for the
appropriate type of disk. After you copy the tape to disk, the disk
can be booted. All tapes are 9-track tapes. The following list shows
the type of disk to which the tape must be copied, the number of tapes
in the kit, the tape length, and the tape density before generating
your system.
Type of
Disk
RKOS
RL01/RL02
RK06/RK07
RM02/RM03
RM02/RM03
RP02/03
RP04/05/06
RP04/05/06

'-'

2.3.2

Number of
TaEes
6
2
4
l
l
l
l
l

Tape
Length {feet)

Tape
Densit:i {bEi~

600
2400
600
2400
2400
2400
2400
2400

800
800
800
800
1600
800
800
1600

Contents of the RSX-llM Release Kit

There may be several disks used during SYSGEN, depending on which kit
you have.
Each disk has a volume label that describes the contents of
the~ disk.
The following sections describe the contents of all three
types of kits in terms of the contents of the volume in the RK05 kit.

2.3.2.1 Volumes on the RKOS Distribution Kit - The following list
shows the volume name of each of the disks in the RK05 distribution
kit, along with a brief description of the files on the volume.
RSXM26

This disk contains the files that comprise the
baseline system;
this disk also contains various
standalone systems used during system generation,
for example, DSCS8, DSCS16, and PRESRV.

EXCSRC

This disk contains the source files for the
RSX-llM Executive;
this disk also contains other
files used by SYSGEN, including MAC and BIGMAC.
Also
included on this volume are standalone
versions of DSC: DSCS8 and DSCS16.
This volume
contains the Backup and Restore utility (BRU)
files and the files to produce Help text files.
For information on the help text files,
see
Appendix H.

DRVSRC

This volume contains the source files for the
drivers.
This volume also contains the K-series
routines.

MCRSRC

This disk contains the source files for MCR, the
shuffler,
broadcast
(BRO),
console output task
(COT), and the account file maintenance program
(ACNT) •

PRVOBJ

This disk contains the object files for RSX-llM
privileged tasks, as well as .ODL and .OLB files.

UT LO BJ

This disk contains the object files for
RSX-llM utilities and nonprivileged tasks.
2-3

the

SETTING UP FOR SYSTEM GENERATION
2.3.2.2 Volumes on the RLOl Distribution Kit - The following list
shows the volume name of each of the disks in the distribution kit,
along with a brief description of the contents of the volume.
RSXM26

This disk contains the
baseline system

files

that

comprise

the

MAPS RC

Contains all the files required to build mapped
systems.
The files in this volume correspond to
the following volumes in the RK05 kit:
EXCSRC
DRVSRC
PRVOBJ
All task
systems.

files

are

UIC

[1,54]

for

mapped

UN MS RC

Contains all the files required to build unmapped
systems.
The files in this volume correspond to
the same volumes as in MAPSRC, above.
However,
task files for unmapped systems reside in urc
[l,50].

RLUT'IL

Contains files corresponding to the files
following volumes on the RK05 kit:

the

UTLOBJ
MC RS RC
This disk also contains the Backup and Restore
utility
(BRU) files and the files to produce Help
text files.
For information on the help text
files, see Appendix H.

2.3.2.3 Volume on Big Disk Kits - The volume name of the disk for
large disk kits is RSXM26.
This volume contains all the source,
object and other files required for system generation.

2.3.3

Standalone DSC

All distribution kits include standalone versions of the Disk Save and
Compress
(DSC)
Utility.
DSC is used to create backup copies of the
distribution kit.
There are two versions of the standalone DSC utility, DSCS8 and
DSCS16.
DSCS8 is used with 800 BPI (and 1600 BPI) tape devices and
DSCS16 is used with 1600 BPI tape devices only.
Disk kits include copies of both versions in UIC [1,51].
Included in each tape kit is a 600-foot, 9-track 800 BPI magnetic tape
that contains a hardware bootable, standalone version of the Disk Save
and Compress Utility (DSCS8).
Use the DSC tape to copy tape kits to
disk.

2-4

SETTING UP FOR SYSTEM GENERATION
2.3.4

The RSX-llM Baseline System

If you do not have an RSX-llM operating system for your host computer
(your host computer is·the computer on which you are performing the
system generation), you need an operating system to control the host's
resources while you generate an RSX-llM operating system.
DEC
provides the RSX-llM baseline system for this purpose.
During SYSGEN, many files are created,
installed and removed,
then
deleted.
Also,
these files are contained in many UICs in order to
separate one type of file from another.
Among other reasons,
the
tasks on the baseline system are used to make these types of file
manipulation functions possible.
Execution of baseline system tasks is controlled by MCR
Monitor Console Routine).

(the

RSX-llM

The baseline system is an RSX-llM operating system that comprises only
those software tools you need to generate a more complex system
tailored to your specific configuration.

2.4

BACKING UP YOUR DISTRIBUTION KIT AND BOOTSTRAPPING THE BASELINE SYSTEM

When you receive the RSX-llM distribution kit,
you should make a
backup copy of the kit to ensure against accidents to the files and
data on the kit and to provide a base for system updates.
This section describes the procedures for backing
distribution media.

2.4.1

tape

and

disk

Backing Up Tape Distribution Media

When you receive tape distribution media, use the hardware bootable
DSC tape to copy the tape media to disk because the system generation
program requires disk volumes for its processing.
Once you copy the
distribution media from tape, the tape is your backup copy of the kit.
The procedure for copying from tape to
baseline system is shown in Figure 2-1.

'-"

disk

and

bootstrapping

Step 1 in Figure 2-1 is bootstrapping the standalone version
Disk Save and Compress Utility (DSC) into processor
DSC provides the functions
required to copy the
distribution
media.
(For a complete description
functions, refer to the RSX-11 Utilities Manual.)

the

of the
memory.
RSX-llM
of DSC

To bootstrap DSC, mount the DSC tape you receive with the
distribution kit and the disk to which you are writing, and
follow the hardware bootstrap procedures for your particular
bootstrap
ROM.
The
PDP-11
hardware bootstrap routine
bootst:aps the standalone version of DSC into processor memory
and gives DSC control of the system.
DSC displays the
following line when it is ready:
RSXllS V2.2 BL26
DSCS8>

DISK SAVE AND COMPRESS UTILITY V3.0

You can then enter the DSC command lines to create disk
of the distribution media.

2-5

copies

SETTING UP FOR SYSTEM GENERATION

Tape Containing
Standalone DSC

Processor Memory

TapeKitQ

1. Hardware bootstrap DSC
standalone system into
processor memory.
2. Copy your distribution
kit using DSC.

Backup Disk Volume
Baseline
System

3. Hardware bootstrap the
RSX-11 M baseline system
into processor memory.
4. Verify your system disks
using the VFY utility.
Goto SYSGEN Part I

Figure 2-1

Copying Tape Distribution Kits

Step 2 in Figure 2-1 is copying the tape distribution media to disk
using DSC.
The following is the general format for entering
DSC command lines to copy from tape to disk:
DSC>outdevice:=indevice:
where DSC> is the DSC prompt, outdevice:
specifies the disk
device to which DSC is copying data, and indevice:
is the tape
input device with the tape distribution media mounted.
When the tape media is copied to disk,
you
bootstrap the baseline system and invoke SYSGEN.

can

hardware

Step 3 in Figure 2-1 is to hardware bootstrap the RSX-llM baseline
system into processor memory to control the system resources
while SYSGEN is executing.
To bootstrap the baseline system, mount the disk on which the
baseline system resides,
and follow the hardware bootstrap
procedures for your particular bootstrap ROM.
The PDP-11
hardware bootstrap routine bootstraps the baseline system into
processor memory, giving control of the system to the baseline
system. Section 2.5 describes the startup display sequence.
Step 4 in Figure 2-1 is to verify the integrity of the disks you are
using
for
system
generation.
Use the File Structure
Verification Utility (VFY) to ensure the integrity of these
disks.
(The RSX-11 Utilities Manual provides details of all
the functions performed by VFY.)
Use the following command lines to ensure the
disk:
>RUN $VFY
VFY>/RC

2-6

integrity

2.4.2

Backing Up Disk Distribution Media

You can back up disk distribution media to either disk or tape backup
volumes.
Figure 2-2 outlines the procedure for creating a backup copy
of disk distribution media.

Distribution Kit

RSX·1~
Baseline
System

"-"

Processor Memory
1. Hardware bootstrap the
RSX-11 M baseline system
into processor memory.

Baseline
System

BOOT

Distribution Kit

E3
~·

2. Install the software
bootstrap routine using
the MCR INSTALL
command:
INS $BOO
3. Software bootstrap
standalone DSC into
processor memory using
the MCR Boot command:
BOO [1,51] DSC58

Standalone
DSC

Distribution Kit

E3
Backup Volume
•·

4. Copy your distribution
kit using the standalone
DSC system.
5. Verify your system disks
using VFY.
Processor Memory
6. Hardware bootstrap the
RSX-11M baseline system
into processor memory.

RSX11M.SYS

Goto SYSGEN Part I

..
Figure 2-2

Copying Disk Distribution Kits

2-7

Baseline
System

SETTING UP FOR SYSTEM GENERATION
Step l

in Figure 2-2 is to hardware bootstrap the RSX-llM baseline
system into processor memory to control the system resources
while SYSGEN is executing.
To bootstrap the baseline system, mount the disk on which the
baseline system resides,
and follow the hardware bootstrap
procedures for your particular bootstrap ROM.
The PDP-11
hardware bootstrap routine bootstraps the baseline system into
processor memory, giving control of the system to the baseline
system.
Section 2.5 describes the startup display sequence.

Step 2 in Figure 2-2 is to install the MCR BOOT command (the software
bootstrap routine)
into memory.
Using the BOOT command, you
can bootstrap the standalone version of DSC into processor
memory.
You then use DSC to copy the kit.
To install BOOT,
enter the command line:
>INSTALL $BOO
The software bootstrap routine has the same effect as the
hardware bootstrap routine,
that is, it bootstraps DSC into
processor memory and gives DSC control of the system.
Step 3 in Figure 2-2 is bootstrapping the standalone version of the
Disk Save and Compress Utility (DSC) into processor memory.
DSC provides the functions required to back up and restore data
on the RSX-llM distribution media.
(For a complete description
of DSC functions, refer to the RSX-11 Utilities Manual.)
To bootstrap DSC, using the software Boot task,
enter the
command
BOO
[l,5l]DSCS8.
The software bootstrap routine
bootstraps the standalone version of DSC into processor memory
and gives DSC control of the system.
DSC displays the
following line when it is ready:
RSXllS V2.2 BL26
DSCS8>

DISK SAVE AND COMPRESS UTILITY V3.0

You can then enter the command lines to create
distribution media.

copies

the

Step 4 in Figure 2-2 is copying the disk distribution media to disk
using DSC.
The following is the general format for entering
DSC command lines to copy from disk to disk:
DSC>outdevice:=indevice:
where DSC> is the DSC prompt, outdevice:
specifies the device
to which DSC is copying data,
and indevice:
is the input
device with the distribution media mounted.
When the media is copied, you can use the disk copy of
media to bootstrap the baseline system and invoke SYSGEN.

the

Step 5 in Figure 2-2 is to verify the integrity of the disks you are
using
for
system
generation.
Use the File Structure
Verification Utility (VFY) to ensure the integrity of these
disks.
(The RSX-11 Utilities Manual provides details of all
the functions performed by VFY.)
Use the following command line to ensure
disk:
>RUN $VFY
VFY> /RC
2-8

the

integrity

SETTING UP FOR SYSTEM GENERATION
/RC is the Read Check switch. This switch reads from the disk
ensuring that each block on the disk that is allocated to a
file can be read.
If VFY reports that it cannot read a block,
call
your ldcal DIGITAL Software· Support Specialist for
assistance.
Step 6 in Figure 2-2 is to hardware .bootstrap the RSX-llM baseline
system into processor memory to control the system resources
while SYSGEN is executing.
To bootstrap the baseline system, mount the disk on which the
baseline system resides,
and follow the hardware bootstrap
procedure for your particular bootstrap ROM.
The PDP-11
hardware bootstrap routine bootstraps the baseline system into
processor memory, giving control of the system to the baseline
system.
Section 2.5 describes the startup display sequence.
When you complete this procedure, you can invoke the SYSGEN procedure,
as described in Chapter 3.

2.5

START-UP DISPLAY SEQUENCE

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

NOT IN CONFIGURATION*

Where:
dd=device NAME.
nn=unit NUMBER.
(Devices not in the configuration are declared OFFLINE and the display
OFFLINE is appended to these devices as part of the output of the MCR
Devices command).
Then the system displays:
RSX-llM <vers-num><base-level><mem-siz>[mapped]
>RED DDNN:=SYO:
>RED ddnn:=LBO:
>MOU ddnn:volname
>@[l,.2]STARTUP
Where:
<vers-num>

- The release version number (for example,
release 3.2 of RSX-llM is V3.2).

<base-level>

- The software development group at DIGITAL
periodically brings together new versions
of the
software
under
development.
Internal groups may use this software to
ensure correct operation and to build new
software.
These development milestones
are called base levels.
For example,
release 3.2 of RSX-llM is base level
BL26.

2-9

SETTING UP FOR SYSTEM GENERATION

<mem-siz>

- The memory size (in the form of nnnk)
of
the machine on which the system was
bootstrapped.

[mapped]

- Mapped is displayed for systems built
use the Memory Management Unit.

ddnn:

- Device name and unit number of
device.

the

boot

vol name

- The name of the volume that contains
booted system.

the

[l,2]STARTUP

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

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

2-10

CHAPTER 3

GETTING STARTED

This chapter describes the pre-processing steps which prepare the host
system for the system generation procedure.
Each type of distribution kit is described in a separate
Read the section that pertains to your kit as follows:
•

Big disk distribution kits, Section 3.1

•

Dual RKOS distribution kits, Section 3.2

•

RLOl distribution kits, Section 3.3

section.

To perform a SYSGEN, you must be privileged.
Privileged status
insures that the command files can access as well as create and delete
files in various UFDs.
To perform a PREPGEN, privileged status is not required;
a PREPGEN
does not create or delete files (if requested, a PREPGEN creates the
file SYSSAVED.DAT). Also, a PREPGEN uses the UFD that corresponds to
the default UIC of the terminal to find command files and create
SYSSAVED.DAT.
NOTE
If you wish to direct listings or maps
to a device other than SY:, LB:, or TI:,
you should load the driver and then
mount the device before you begin the
system generation process.

3.1

BIG DISK DISTRIBUTION KITS

If you have a previously generated RSX-llM version
Section 3.1.1.

3.2

If you do not have a running RSX-llM
read Section 3.1.2.

system

3-1

version

3.2

system,

read

available,

GETTING STARTED
Online SYSGENs and PREPGENs

3.1~1

The following lists the pre-processing
· SYSGEN or PREPGEN:
1.

Mount the baseline system disk.

steps

perform

online

device

SY:.

For example:

>MOU DB2:RSXM26
2.

Assign the baseline system disk to
For example:

the

pseudo

>ASN DB2:=SY:
3.

The system generation command files require an indirect
command file processor with extended symbol table space. For
mapped systems, this is a 12K-word version (BIGIND).
For
unmapped systems, this is a 14K-word version (BIGIND). If
the running system contains the SK-word indirect
(without
symbol table space extensions), remove the task AT. and
install BIGIND specifying a priority of 10(10). For example:
>REM ••• AT.
>INS $BIGIND/PRI=l0.

If performing a
example:

SYSGEN,

set

the

UIC

[200,200].

For

>SET /UIC=[200,200]
This is not required to perform a PREPGEN.
5.

Initia:te SYSGEN Phase I.

For example:

>@SYSGEN
6.

3.1.2

For a summary of the Phase I questions, read Chapter 4.
For
a detailed description of Phase I questions, read Chapter 5.

Standalone SYSGENs and PREPGENs

The following lists the pre-processing steps to perform
PREPGEN using the baseline system.
1.

SYSGEN

The system generation command files require an indirect
command file processor with extended symbol table space. For
mapped systems, this is a 12K-word version (BIGIND).
For
unmapped systems, this is a 14K-word version (BIGIND). The
baseline system contains the SK-word version, which lacks
sufficient symbol table space.
Remove the task AT. and
install BIGIND specifying a priority of 10(10). For example:
>REM ••• AT.
>INS $BIGIND/PRI=l0.
3-2

GETTING STARTED
3.

Initiate SYSGEN Phase I.

For example:

>@SYSGEN
4.

3.2

For a summary of the Phase I questions, read Chapter 4.
For
a detailed description of Phase I questions, read Chapter 5.

DUAL RKOS DISTRIBUTION KITS

The dual RKOS distribution kit requires two RKOS drives.
When SYSGEN
completes processing of the Executive source disk (EXCSRC), you must
replace the disk with the driver source disk (DRVSRC) so that SYSGEN
can access the driver source files.
This is known as an end-of-disk
breakpoint (EOD). Note that if your host configuration includes more
than two RKOS drives, you can override these breakpoints. See Chapter
5 for details.

3.2.1

Online SYSGENs and PREPGENs

The following lists the pre-processing
SYSGEN or PREPGEN:
1.

Mount the baseline system disk.

steps

perform

online

device

SY:.

For example:

>MOU DK:RSXM26
2.

Assign the baseline system disk to
For example:

the

pseudo

>ASN DK:=SY:
3.

The system generation command files
require an indirect
command file processor with extended symbol table space.
For
mapped systems, this is a 12K-word version
(BIGIND).
For
unmapped systems,
this is a 14K-word version (BIGIND).
If
the running system contains the 8K-word version
(without
symbol table space extensions),
remove the task AT.
and
install BIGIND specifying a priority of 10(10).
For example:
>REM ••• AT.
>INS $BIGIND/PRI=l0.

If performing a
example:

SYSGEN,

set

the

UIC

[200,200].

For

>SET /UIC=[200,200]
This is not required to perform a PREPGEN.
5.

If performing a PREPGEN, mount the Executive source disk and
assign this device to the pseudo device LB:.
For example:
>MOU DKl:EXCSRC
>ASN DKl:=LB:
This is not required to perform a SYSGEN;
a
SYSGEN
automatically issues Mount and Assign commands for the device
that contains the Executive source files.

3-3

GETTING STARTED
6.

Initiate SYSGEN Phase I.

For example:

>@SYSGEN

3.2.2

For a summary of the Phase I questions, read Chapter 4.
For
a detailed descripti-0n of Phase I questions, read Chapter 5.

Standalone SYSGENs and PREPGENs

The following lists the pre-processing steps to perform
PREPGEN using the baseline system:
1.

SYSGEN

The system generation command files
require an indirect
command file processor with extended symbol table space.
For
mapped systems, this is a 12K-word version
(BIGIND).
For
unmapped systems,
this is a 14K-word version (BIGIND).
The
baseline system contains the SK-word version, which lacks
sufficient symbol table space.
Remove the task AT.
and
install BIGIND specifying a priority of 10(1-0).
For example:
>REM ••• AT.
>INS $BIGIND/PRI=l0.

Initiate SYSGEN Phase I.

For example:

>@SYSGEN
5.

3.3

For a summary of the Phase I questions, read Chapter 4.
For
a detailed description of Phase I questions, read Chapter 5.

RLOl DISTRIBUTION KITS

The RLOl distribution kit requires
or a PREPGEN.
However, you can
single RLOl provided that you have
secondary storage device can be
different type.

two RLOl drives to perform a SYSGEN
perform a SYSGEN or PREPGEN using a
a secondary storage device.
The
a magtape unit or a disk drive of a

3-4

GETTING STARTED
To generate a system using two RLOl drives,
you simply load the
baseline system disk
(RSXM26)
and either the mapped source disk
(MAPSRC) to generate a mapped system or the unmapped source disk
(UNMSRC) to generate an unmapped system.

To generate a system using a single RLOl drive,
you must copy the
contents of
[11,10]
from the mapped or unmapped source disk (MAPSRC
for mapped target systems, UNMSRC for unmapped target systems)
to
secondary storage.
Later, during SYSGEN Phase II, you will copy these
files from secondary storage onto the baseline disk under
[1,24].
Note that both the mapped and unmapped source disks contain a bootable
copy of RSX-llM. Thus, if you are running standalone, you must boot
the proper disk (MAPSRC for mapped target systems, UNMSRC for unmapped
target systems), copy [11,10] to secondary storage, and then reboot
using the baseline system disk.
If your secondary storage device is a disk drive of a different type
and the driver is loadable, you can specify this drive as the device
that contains the Executive sources (obviously, you must first copy
the mapped or unmapped sources to this drive).

3.3.l

Online SYSGENs and PREPGENs

The following lists the pre-processing
SYSGEN or PREPGEN:
1.

steps

Mount the baseline system disk.

perform

online

For example:

>MOU DL:RSXM26
If you are using a single RLOl drive, you must first copy the
contents of
(11,10] from the mapped or unmapped source disk
to secondary storage.
To generate a mapped system, mount
(MAPSRC)
and copy the contents
storage.
For example:

the mapped
of
(11,10]

source disk
to secondary

>MOU DL:MAPSRC
>FLX MM:/ZE
>FLX MM:/DO=DL: (11,10]*.*/RS
To generate an unmapped system, mount the unmapped source
disk
(UNMSRC)
and copy the contents of (11,10] to secondary
storage.
For example:
>MOU DL:UNMSRC
>FLX MM:/ZE
>FLX MM:DO=DL: [11,10]*.*/RS
When the copy completes, dismount and unload the mapped or
unmapped source disk and mount the baseline system disk.
For
example:
>MOU DL:RSXM26
2.

Assign the baseline system disk to
For example:
>ASN DL:=SY:

3-5

the

pseudo

device

SY:.

GETTING STARTED
3.

The system generation command files require an indirect
command file processor with extended symbol table space. For
mapped systems, this is a 12K-word version
(BIGIND).
For
unmapped systems,
this is a 14K-word version (BIGIND).
If
the running system contains the SK-word indirect
(without
symbol table space extensions),
remove the task AT. and
install BIGIND specifying a priority of 10(10). For example:
>REM ••• AT.
>INS $BIGIND/PRI=l0.

If performing a SYSGEN, set the UIC to [200,200] For example:
>SET /UIC=[200,200]
This is not required to perform a PREPGEN.

Initiate SYSGEN Phase I.

For example:

>@SYSGEN
6.

3.3.2

For a summary of the Phase I questions, read Chapter 4.
For
a detailed description of Phase I questions, read Chapter 5.

Standalone SYSGENs and PREPGENs

The following lists the pre-processing steps to perform
PREPGEN using the baseline system:
1.

SYSGEN

Hardware bootstrap the system using the device that contains
the baseline system disk (RSXM26) as the boot device. This
will bring up the unmapped baseline system.
If the host
system includes the memory management unit and you are
generating a mapped system, software boot the mapped baseline
system.
For example:
>INS $800
>BOO [l,54]RSX11M
If you are using a single RLOl drive, you must first hardware
bootstrap the mapped or unmapped source disk. Then copy the
contents of [ll,10] to secondary storage.
To generate a mapped system, hardware bootstrap the system
using the device that contains the mapped source disk
(MAPSRC) as the boot device.
Then copy the contents of
(11,10] to secondary storage. For example:
>FLX MM:/ZE
>FLX MM:/DO=DL: (11,10]*.*/RS
To generate an unmapped system, hardware bootstrap the system
using the device that contains the unmapped source disk
(UNMSRC) as the boot device.
Then copy the contents of
[ll,10] to secondary storage. For example:
>FLX MM:/ZE
>FLX MM:/DO=DL: [11,10]*.*/RS

3-6

GETTING STARTED
When the copy operation completes, halt the system and remove
the mapped or unmapped source disk from the drive.
Then,
reboot using the baseline system disk.
2.

The system generation command files
require an
indirect
command file processor with extended symbol table space.
For
mapped systems, this is a 12K-word version
(BIGIND).
For
unmapped systems,
this is a 14K-word version (BIGIND).
The
baseline system contains the SK-word version,
which lacks
sufficient symbol table space.
Remove the task AT.
and
install BIGIND specifying a priority of 10(10).
For example:
>REM ••• AT.
>INS $BIGIND/PRI=l0.

Initiate SYSGEN Phase I.

For example:

>@SYSGEN
4.

For a summary of the Phase I questions, read Chapter 4.
For
a detailed description of Phase I questions, read Chapter 5.

3-7

•
CHAPTER 4
SUMMARY OF SYSGEN PHASE I QUESTIONS

This chapter provides summary information for SYSGEN Phase I.
The
chapter is meant to help familiarize you with the SYSGEN questions and
as reference for when you become familiar with SYSGEN.

4.1

SUMMARY OF SYSGEN PHASE I SETUP QUESTIONS

The following list comprises the possible setup questions
Phase I.

for

SYSGEN

Not all of the questions are pertinent;
the order of the questions
depend upon the distribution kit you are using as well as the
responses to the questions.
For complete details and the implications
of your responses, see Chapter 5.
1.

Inhibit MCR command lines (Type <ESC> for explanation)
An affirmative response permits you to follow the logical flow of
a specific SYSGEN, without actually executing commands that
assemble, build, or delete files.
The manual refers to this as a
PREPGEN.
A negative response indicates that you wish to perform
SYSGEN.

"live"

Have you made a copy of the distribution kit
If you are performing a SYSGEN, this question insures that you
have copied the distribution kit.
Following a negative reply,
SYSGEN exits to allow you to do so.

Use saved or canned answer files for input responses
This question permits you to use a saved answer file as responses
to SYSGEN questions.

Undefined answer wakeup
If you are using a saved answer file, an affirmative response to
this question instructs SYSGEN to precede necessary questions
(either a question you did not answer or a question for which a
saved response does not exist)
with a CTRL/G (bell). Thus,
SYSGEN alerts you when a response is required.

Use saved host configuration
If you are using a saved answer file,
an affirmative response
indicates that SYSGEN can use your previous host responses.
For
example,
you are
performing
SYSGEN
on
the
same
host
configuration.
4-1

SUMMARY OF SYSGEN PHASE I QUESTIONS
6.

use saved peripheral configuration
If you are using a saved answer file, an affirmative response
indicates
that you do not wish to change the peripheral
configuration.

Skip end of section (EOS) breakpoints
If you are using saved answer files, an affirmative response
permits SYSGEN to continue after each section of Phase I.

Skip end of execution (EOX) breakpoints
If you are using a saved answer file, an affirmative response
instructs SYSGEN to continue after assembly or task build
operations complete. For example, you are certain that all
device drivers will assemble correctly.

Skip end of disk (EOD) breakpoints
Dual RKOS kits only. An affirmative response indicates that you
do not have to change RKOS disks. For example, you have more
than two RKOS drives available (one for the baseline system, one
for the Executive source files, and one for the device driver
source files).

10.

Save responses (i.e.:

create

S~SSAVED.DAT)

An affirmative response instructs SYSGEN to create the file
SYSSAVED.DAT, which can later be used as input to SYSGEN. See
Chapter 5.
11.

UIC for SYSSAVED files if not [current UIC]
If you are using a saved answer file, SYSGEN assumes that the
file is in the UFD corresponding to the current UIC. Enter a UIC
to override this default. Also, if you are creating the file
SYSSAVED.DAT (a Yes response to question 10), SYSGEN will create
the file in the UFD corresponding to the current UIC.
Again,
enter a UIC to override this default.

12.

UIC for SYSGEN command files if not [current UIC]
SYSGEN assumes the command files are in
If you have moved them, enter a UIC.

[200,200]

for

SYSGENs.

If you are performing a PREPGEN (a Yes reply to question 1),
SYSGEN assumes the command files are in the UFD corresponding to
the current UIC. If they are not, enter a UIC.
13.

Clean up files from previous GENs
If you are performing a SYSGEN, disk space becomes critical.
An
affirmative
response
instructs
SYSGEN to delete old and
unnecessary files created during previous SYSGENs (for example,
RSXBLD.CMD and RSXASM.CMD).

14.

Device, when ready, for Executive sources (ddu:) [D: SY:]

4-2

•

SUMMARY OF SYSGEN PHASE I QUESTIONS
NOTE
If you are using the RLOl or the dual RKOS distribution
kit,
there is no default response to this question;
you
must enter the device that contains the Executive source
files.
For big disk kits, SYSGEN assumes that the Executive source files
are on SY:. Enter a device specification if not.
15.

Driver source files device (ddu:)
Dual RKOS kits only.
driver source files.

Enter the device that contains

the

device

>ASN SY:=LB:
>PIP /FR
Following the free block display, SYSGEN changes the UIC to [11,10].
>SET /UIC=[ll,10]

4.2

SUMMARY OF TARGET AND HOST QUESTIONS

The SYSGEN Phase I target and host questions ask you to define the
target and host configurations.
Target questions define hardware
features in your configuration as well as the attached peripheral
devices.
Host questions determine, primarily, how you want to handle
listings.
The following list comprises the possible target
for SYSGEN Phase I.

and

host

questions

Target
1.

Processor (e.g.:

11/34, LSI-11)

Enter the target processor type.

Does processor have a switch register
Enter Yes if the target processor has a switch register.

Generating RSX-llS
Enter Yes if you wish to generate an RSX-118 system.

Memory size (in K-word blocks)
Enter the number of K-word blocks of memory for the target
processor. Note that memory blocks must be a multiple of 4K.

Mapped
Enter Yes if you are generating a mapped system.
Note
mapped system requires a minimum of 24K-words of memory.

that

Any K-series laboratory devices
Enter Yes if the target configuration
laboratory peripheral options.

4-3

includes

the

K-series

SUMMARY OF SYSGEN PHASE I QUESTIONS
7.

Extended arithmetic element (KEll-A/B EAE) present
Enter Yes if the target processor contains the PDP-11 EAE option.

Floating point processor (FP-11) present
Enter Yes if the target processor
option.

the

floating

includes

the

point

Floating instruction set (FIS) present
Enter Yes if the target
instruction set processor.

10.

includes

configuraton

If using KWll-P as system clock:

floating

number of intrps./sec.

If you are using the KWll-P programmable clock as the system
clock, enter the number of interrupts per second. Note that the
number of interrupts must evenly divide into 10,000.
11.

Line frequency:

A-60Hz B-50Hz [D: "A"]

Enter the line frequency.
12.

The default is 60Hz.

KWll-Y Watchdog timer support
Enter Yes if the target configuration includes the KWll-Y.

13.

Memory parity support
Enter Yes if the target configuration contains parity memory.

14.

Cache memory
In conjunction with memory parity support, cache memory speeds
main memory operations.
Enter Yes if your system includes it.

15.

Highest interrupt vector (If 0 will be computed)
SYSGEN automatically computes the highest interrupt
vector
address.
Enter a value greater than 400 if you require vector
space for devices not specified during SYSGEN.

16.

Devices
Enter the device mnemonic for all pseudo and
to be included in the target configuration.
Enter an asterisk (*)

peripheral

devices

for a list of devices and mnemonics.

For a device-type with
multiple
controllers,
enter
the
device-type,
an equal sign (=), and the number of controllers.
For example, DK=2. Note that SYSGEN assumes one controller for
the device-type if you omit the equal sign.
SYSGEN prompts for a device mnemonic until
entry (or the question) with a period (.).

4-4

you

terminate

the

SUMMARY OF SYSGEN PHASE I QUESTIONS
Host

"--'
4

Are you running SYSGEN standalone (on the baseline system)
Enter Yes if you are not running SYSGEN on a previously generated
RSX-llM system.

Is a line printer available
Enter Yes if the host configuration includes a
line
(The printer can be used for listing and map files.)

printer.

Spool assembly listing and Executive and driver maps
Enter Yes if you want these files spooled to the line printer.
Enter No if you want to save the files, but not print them.

Does the listing/map device have at least 120 columns
Enter Yes if the printer has at least
SYSGEN forces narrow listings.

Assembly listings device (ddu:)

120

columns.

Otherwise,

[D: NL:]

Usually, assembly listing files are not required.
If you
or require these files, enter a device specification.
6•

Map d ev i c e for Exec u t iv e and de v i c e d r iv er s

( d du : )

[ D:

For unmapped systems, maps are required.
specification if you do not want to use SY:.

Enter

For mapped systems, the maps may prove helpful.
specification if you do not want to use SY:.

Enter

desire

s Y: ]
device

a
a

device

Be advised that you should not enter NL:.
EOS

* Do you want to:

<CR>-continue R-repeat section E-exit P-pause

A response of carriage return begins Executive option generation.

4.3

SUMMARY OF EXECUTIVE QUESTIONS

The following list comprises the possible Executive questions for
SYSGEN Phase I. Not all of the questions appear during an actual run
of SYSGEN.
For example, some options require Executive support of
other options;
SYSGEN automatically includes Executive support if it
is required in your system.
For complete details on the Executive
options and their implications, refer to Chapter 5.
Unless otherwise noted, a Yes response includes Executive support
the option.•
1.

for

Will DBMS-11 be used
Enter Yes to include Data Base Management System
details on DBMS, see the DBMS-11 documentation.

4-5

support.

For

SUMMARY OF SYSGEN PHASE I QUESTIONS
2.

FILES-11 ACP
Enter Yes to include the services described in the IAS/RSX-11 I/O
Operations Reference Manual.

RMS record locking and placement control
Enter Yes to include support for the Record
See the RMS documentation for details.

System.

Non-resident tasks (task loader)
Enter Yes
loader:
of a task
read of a

Management

to include support for the task loader.
The task
reads a task into memory; performs a checkpoint write
image from memory to disk; or performs a checkpoint
task image from disk into memory.

Loadable task loader
Enter Yes to include support for the loadable task loader.
The
loadable task loader reduces the amount of address space required
for the Executive.

Memory managment (PLAS) directives
Enter Yes to include support
directives.
These directives
physical memory.

the
memory
management
for
allow tasks greater span of

Send/Receive by reference directives
Enter Yes to include support for the
directives.

send/receive

reference

Get mapping context directive
Enter Yes to include support for this directive.

Address checking
Enter Yes to include Executive support for address checking.
This option provides boundary and alignment checks on addresses
passed by users in P.xecutive directives.

10.

I/O rundown
Enter Yes to include Executive support for I/O rundown.
This
option helps insure system integrity by cleaning up outstanding
I/O before allowing a task (for example Dismount) to exit.

11.

Multi-user protection
Enter Yes to generate a multiuser protection system. This option
protects against destructive interference between users.

12.

ANSI magtape
Enter Yes to include Executive support for ANSI magnetic tapes.

~~,

4-6

SUMMARY OF SYSGEN PHASE I QUESTIONS
13.

On-line formatting (FMT) or on-line user-mode diagnostics
Enter Yes to include support for
the volume format
utility (FMT) and User-Mode Diagnostics (UMDs).

14.

Loadable device drivers
Enter Yes
drivers.

15.

include

Executive

support

for

loadable

loadable,

AST and cancel selective MARKTIMEs
Enter Yes to permit
(ASTs)
and provide
requests.

17.

device

Should the default for all applicable drivers be loadable
Enter Yes to default drivers that can be loaded to
rather than resident.

16.

(hardware)

processing of Asynchronous System Traps
the ability to cancel selective marktime

Task termination and device not ready messages (TKTN)
Enter Yes to include this option.

18.

Power fail recovery
Enter Yes to include this option.

19.

Install, request, and remove or exit
Enter Yes to include this feature of the Run command.
This
feature helps optimize use of Executive dynamic memory resources.

20.

Large (20K) Executive
Enter Yes to generate an
increase pool space.

21.

Executive

larger

than

16K

and

thus

Logical device assignment
Enter Yes to include support for the MCR Assign command.

22.

Logging of device errors and timeouts
Enter Yes to permit the error logging subsystem to
device errors and write status information in a file.

23.

Logging of undefined interrupts
Enter Yes to permit the error logging subsystem to
to undefined interrupt vectors in a file.

24.

25.

intercept

record

traps

Enter Yes to permit the error logging susbsystem to record
and main memory parity error information in a file.

cache

Logging of memory parity errors

Do you intend to include a user-written driver
Enter Yes if you have written your own device driver(s).
SYSGEN
will permit you to
include your drivers when it assembles the
Executive.

4-7

SUMMARY OF SYSGEN PHASE I QUESTIONS
26.

Include routine $GTWRD
Enter Yes to include support for the $GTWRD Executive routine.
a word from a user-defined
This routine obtains,
or fetches,
buffer.

27.

Include routine $PTWRD
Enter Yes to include the $PTWRD Executive routine.
sends a word to a user-defined buffer.

28.

This

routine

Disk writecheck
Enter Yes to include disk writecheck support. When enabled, this
option increases data reliability, but decreases disk throughput.

29.

Executive debugging tool

(XDT)

Enter Yes to include the Executive Debugging Tool (XDT).
XDT is
useful in debugging privileged tasks and user-written drivers.
30.

Rotating pattern in data lights
Enter Yes to include this
rotate
in a pronounced
idle.

31.

option.
The processor data lights
circular pattern when the processor is

Industrial network or DECnet
Enter Yes to include industrial network or DECnet support.

32.

Queue manager and queued print spooler
Enter Yes to include complete spooling support.

33.

Group global event flags
Enter Yes to include Executive support for group
flags and MCR support for the Flags command.

34.

global

event

Enter code for directives
Enter an asterisk (*) for a list of the Executive directives and
then
enter
the letter(s)
that correspond to the desired
directives.
A percent sign
(%)
selects all
the directives.
Terminate the question with a period (.).

35.

Number of pre-allocated QIO packets
Enter a numeric response in the range 0 to 15
number of QIO packets to allocate from pool.

specify

the

A response of 0 excludes the option.
Note that the default response is 5. Therefore,
if you simply
enter carriage
return, you select the option and allocate 5 I/O
packets from pool.
36.

Size of data transfer vector in words
Enter a numeric response in the range 5 to
33 to specify the
number of MOV instructions to
include
in the data transfer
vector.

4-8

i.,...,

SUMMARY OF SYSGEN PHASE I QUESTIONS
37.

Round-robin scheduling interval in ticks
Enter a numeric response in the range O to 1000
round-robin scheduling interval.

specify

the

A response of 0 excludes the option.
Note that the default response is 5. Therefore,
if you simply
enter carriage return, you select the option and specify 5 clock
ticks as the scheduling interval.
38.

Highest priority class for consideration
Enter a numeric response in the range 1 to 249 to specify
highest, eligible priority class for round-robin scheduling.

39.

the

Lowest priority class for consideration
Enter a numeric response in the range 1 to the response entered
in question 38 to specify the lowest, eligible priority class for
round-robin scheduling.

40.

Executive level disk swapping interval
Enter a numeric response in the range 0 to 5000
disk swapping interval.

specify

the

A response of 0 excludes the option.
Note that the default is a value equal to the round-robin
scheduling interval multiplied by 6. Therefore, if you simply
enter carriage return, you select the option and specify 6 times
the round-robin interval as the swapping interval.
If you did not select round-robin scheduling (response of 0 to
question 37), the default is 30. Therefore, if you simply enter
carriage return, you select Executive level disk swapping and
specify 30 as the swapping interval.
41.

Swapping priority
Enter a numeric response in the range 1 to 20 to specify the
range over which lower priority tasks may checkpoint higher ones.

"-"

The default response is 5, which is highly recommended.
42.

Size of dynamic storage region (POOL) in words
Enter a numeric response that is in the range 256 to 16384 and
multiple of two.

43.

Seconds between printer not ready messages
Enter a numeric response in the range 0 to 255 to specify
number of seconds between line printer not ready messages.

the

A response of 0 suppresses the messages.
If you make a non-zero entry, the value must be greater than 15.

4-9

SUMMARY OF SYSGEN PHASE I QUESTIONS
If you simply enter
Note that the default is 30 seconds.
carriage return,
the message appears every 30 seconds when the
(out of paper, or 'offline,
for
line printer is not ready
example}.
44e

Seconds between card reader not ready messages
Enter a numeric response in the range 0 to 255.
A response of 0 suppresses the messages.
If you make a non-zero entry, the value must be greater than 15.
Note that the, default is 30 seconds.
If you simply enter
carriage return, the message appears twice a minute when the card
reader is not ready.

45.

System crash register and stack dump device CSR
Enter 0 to exclude this option.
Otherwise,
response in the range 160000 to 177700.

enter

numeric

Note that the default response selects the option and dumps the
Executive stack and registers on the console terminal following a
system crash.
46.

Checkpointing:

A-Yes

B-With system ckpnt.

file

Enter A to include checkpointing, B to include checkpointing to
system checkpoint files
(and support the Allocate Checkpoint
Space (ACS} command}, or carriage return to exclude checkpointing
altogether.
47.

System controlled partitions:

A-Yes B-With auto compaction (SHF}

Enter A to include system controlled partitions,
B to
include
system controlled partitions with the shuffler (SHF), or carriage
return to exclude support for system controlled partitiona.
48.

Dump analysis:

A-PANIC

B-Crash (CDA)

Enter A to include the panic dump routine (PANIC), B to
include
the crash dump analyzer
(CDA),
or carriage return to exclude
support for memory dumps following a system crash.
It is recommended that you select either PANIC or CDA.
49.

Output notification device CSR
Enter a numeric value in the range 160000 to 177700 to specify
the CSR address for the CDA routine to output crash notification.

50.

Memory dump device (ddu:)
Enter the device mnemonic and unit number for the device you wish
the CDA routine to direct memory dumps.

51.

CSR address of dump device
Enter a numeric response in the range 160000 to 177700 to specify
the CSR address of the console terminal.
The default response is the default CSR
dump device.

4-10

address

the

memory

SUMMARY OF SYSGEN PHASE I QUESTIONS

52.

CSR address of PANIC dump device
Enter a numeric response in the range 160000 to 177700 to specify
the CSR address of the device for the PANIC routine to dump the
Executive stack and registers.
The default response causes PANIC to dump the stack and registers
to the console terminal.

4.4

SUMMARY OF TERMINAL DRIVER QUESTIONS

The following list comprises the possible
for SYSGEN Phase I.
l.

Terminal driver desired (A/B/C/D,

terminal

driver

questions

* prints table)

Enter an asterisk to print a
list of the available terminal
drivers.
Then enter A to select the half duplex terminal driver
that you tailor to your system requirements,
B to select the
tailored (user-oriented) half duplex terminal driver, C to select
the full duplex terminal driver, or D to select the baseline half
duplex terminal driver.
Chapter 5 lists the options included in
the user-oriented and full duplex terminal drivers.

Unsolicited input timeout value in seconds
Enter a numeric response in the range 0 to 2540 to specify the
interval,
in seconds, that the full duplex terminal driver waits
before discarding unsolicited terminal input.
A response of 0 inhibits the full
unsolicited input timeout feature.

duplex

terminal

driver

Note that the default response is 120 seconds. Therefore, if you
simply enter carriage return, you select this feature and specify
that the driver timeout after two minutes.
3.

Pass form feeds directly to the terminal
Enter Yes to suppress conversion of
feeds.

form

feed

into

line

Automatic carriage return/line feed
Enter Yes to generate a carriage return and line feed whenever
the terminal buffer is filled, either on output or echo.

Task checkpointable during terminal input
Enter Yes to allow tasks to displace
memory during terminal input.

checkpointable

tasks

from

Unsolicited input character AST
Enter Yes and a task attaching to a terminal can specify
entry point on receiving unsolicited input characters.

4-11

AST

SUMMARY OF SYSGEN PHASE I QUESTIONS
7.

Write with CTRL/O cancellation
Enter Yes to permit write requests with CTRL/O cancellation to
print to the terminal, regardless of whether or not the terminal
has suppressed output by CTRL/O.

Breakthrough write
Enter Yes and breakthrough write requests can
terminal, regardless of terminal I/O activity.

recognize

feed

followed

and

treat

escape

sequences

line

characteristics

Get multiple characteristics
Enter Yes to allow
individual terminals.

12.

the

Escape sequence handling
Enter Yes to
terminators.

11.

CTRL/R (retype)
Enter Yes and CTRL/R sends a carriage return/line
by the input buffer to the terminal.

10.

tasks

determine

Set multiple characteristics
Enter Yes to allow tasks to set or reset characteristics of their
TI:
terminal.
Privileged tasks can set characteristics of any
terminal.

13.

Get terminal driver options
Enter Yes to allow tasks to determine
options were selected during SYSGEN.

14.

which

driver

Hold screen mode
Enter Yes to allow terminals (with special
output into pages that fit on the screen.

15.

terminal

hardware)

break

Transparent read/write
Enter Yes to provide support for
I/O functions
(IO.RAL and
IO.WAL)
that bypass character filtering and permit output of up
to 32K bytes.

16.

Settable 'case conversion for input
Enter Yes to permit the driver to selectively, on a
basis, convert lower case input to upper case.

17.

per-terminal

Read after prompt
Enter Yes to permit a read after prompt request to act like a
write to the terminal followed by a read.
This reduces overhead
and eliminates context switching.

4-12

SUMMARY OF SYSGEN PHASE I QUESTIONS
18.

Read with no echo
Enter Yes to permit issuing read functions (IO.RLB,
IO.RVS,
IO.RPR) specifying that terminal input not be echoed.

19.

and

Read with special terminator
Enter Yes to permit any character less than 40 octal or greater
than 174 octal to terminate a
read with special terminator
request.

20.

CRT rubout support
Enter Yes to select the backspace-deletion function.

21.

Terminal-host synchronization
Enter Yes to allow CTRL/S and CTRL/Q from a terminal.

22.

User terminal input buffering
Enter Yes to
place
input
characters
non-checkpointable task buffer as received.

23.

allocate

buffers

large

enough

contain

read

LA30P support
Enter Yes to
include support for an LA30P;
this
discarding the second of two rapidly typed characters.

25.

into

Variable length terminal input buffering
Enter Yes to
requests.

24.

directly

prevents

Hardware unrecoverable input error support
Enter Yes to permit the full duplex terminal driver to pass
characters received after a hardware error to the soliciting
task, with notification.

26.

Device independent cursor positioning
Enter Yes to permit cursor positioning coordinates without
specifying
terminal-type;
the full duplex terminal driver
determines terminal-type.

4.5

SUMMARY OF PERIPHERAL QUESTIONS

The following list comprises the possible peripheral
SYSGEN Phase I.
Read Chapter 5 for details on
questions and the SYSGEN prompt lines.

questions for
the peripheral

Enter [L/R,] vector, CSR for:
1.

CR Controller 0 [D: 230,177160]
Respond with a carriage return to use the default vector and
CSR assignments for the first CRll card reader.
You must
enter the vector and CSR addresses of subsequent CRll
controllers.

4-13

SUMMARY OF SYSGEN PHASE I QUESTIONS
1.

CT Controller 0 [D: 260,177500]
Carriage return uses the default vector and CSR assignments
for the first TAll cassette controller. Subsequent TAll
controllers do not have default assignments.

DF Controller 0 [D: 204,177460]
Carriage return uses the default vector and CSR assignments
for the first RFll controller. Subsequent RFll controllers
do not have default assignments.

MS Controller 0 [D: 224,172522]
Carriage return uses the default vector and CSR assignments
for the first TSll controller. Subsequent TSll controllers
do not have default vector assignments.

PP Controller 0 [D: 74,177554]
Carriage return uses the default vector and CSR assignments
for the first PCll controller. Subsequent PCll controllers
do not have default assignments. See Chapter 5.

PR Controller 0 [D: 70,177550]
Carriage return uses the default vector and CSR assignments
for the first PCll/PRll controller. Subsequent controllers
do not have default assignments. See Chapter 5.

UD Controller 0 [D: 234,171776]
Carriage return uses the default vector and
for UDCll, Universal Digital Controller.

CSR

assignments

XB Controller 0 [D: 124,172414]
Carriage return uses the default vector and CSR assignments
for the first DAll-B parallel line interfac~ controller.
Subsequent
DAll-B
controllers
do
not
have
default
assignments.

Enter [L/R,] vector, CSR, number of drives, unit number of first drive,
[O=offset recovery support/NO=no support] for:
2.

DB Controller O [254,176700,,0,0]
Enter two commas (,,) followed by the number of disk drives
for the first RHll or RH70 controller. This will use the
default vector and CSR assignments, specify 0 as the unit
number of the first drive, and include offset recovery
support. Subsequent controllers default only the unit number
of the first drive (to 0).

4-14

·~

SUMMARY OF SYSGEN PHASE I QUESTIONS
2.

DR Controller 0 [D: 254,176700,,0,0]
Enter two commas (,,) followed by the number of disk drives
for
the first RHll or RH70 controller. This will use the
default vector and CSR assignments, specify 0 as the unit
number of the first RM02 or RM03 drive, and include offset
recovery.
Subsequent controllers default only the unit
number of the first drive (to 0) •

•

·Enter [L/R,] vector, CSR, number of drives for:
3.

DD Controller 0 [D: 300,176500]
Enter two commas (,,) followed by the number of drives for
the first TU58 controllero This will use the default vector
and CSR assignments for
the
DECtape
II
controller.
Subsequent TU58 controllers do not have default responses.

DL Controller 0 [D: 160,174400]
Enter two commas (,,) followed by the number of drives for
the first RLll controller. This will use the default vector
and CSR assignments for the RLOl cartridge disk controller.
Subsequent RLll controllers do not have default responses.

DP Controller 0 [D: 254,176714)
Enter two commas (,,) followed by the number of drives for
the first RPll controller. This will use the default vector
and CSR assignments for
the RP02/03
disk
controller.
Subsequent RPll controllers do not have default responses.

DT Controller 0 [D: 214,177342]
Enter two commas (,,) followed by the number of drives for
the first TCll controller. This will use the default vector
and CSR assignments for the DECtape controller.
Subsequent
TCll controllers do not have default responses.

DX Controller 0 [D: 264,177170]
Enter two commas (,,) followed by the number of drives for
the first RXll controller. This will use the default vector
and CSR assignments for the RXOl floppy disk controller.
Subsequent RXll controllers do not have default responses.

DY Controller 0 [D: 264,177170]
Enter two commas (,,) followed by the number of drives for
the first RX211 controller. This will use the default vector
and CSR assignments for the RX02 floppy disk controller.
Subsequent RX211 controllers do not have default responses.

MM Controller O [D: 224,172440]
Enter two commas (,,) followed by the number of drives for
the first RHll, RH70, TM02, or TM03 controller. This will
use the default vector and CSR assignments for the first
TU45, TU16, TE16, or TU77 magtape controller. Subsequent
controllers of this type do not have default responses.

4-15

SUMMARY OF SYSGEN PHASE I QUESTIONS
3.

MT Controller 0 [D: 224,172522]
Enter two commas (,,) followed by the number of drives for
the first TMll, TMAll, or TMBll controller. This will use
the default vector and CSR assignments for the first TS03,
TUlO, or TElO magtape controller. Subsequent controllers of
this type do not have default responses.

Enter [L/R,] vector, CSR, F=full duplex/H=half duplex,
E=error detec. unit/NO=no, C=char. detec
number of sync characters in leader for:
4.

unit/NO=no~

XQ Controller [D:,,H,E,C]
Enter the vector address (from floating vector space starting
at 300), the CSR address (from floating address space
starting at 160010), followed by four commas
(vector,
CSR,,,,) and the number of sync characters in a sync leader
for the first DQll synchronous line interface.
This will
specify a half duplex line with error and character detection
units. Subsequent DQlls default half duplex and error and
character detection unit specification.

Enter [L/R,] vector, CSR, number of drives, unit number of first drive for:
5.

DS Controller 0 [D: 204,172040,,0]
Enter two commas (,,)
followed by the number of RS03/04
drives for the first RHll or RH70 controller. This will use
the default vector and CSR assignments and specify 0 as the
unit
number
of
the first RS03/04 drive.
Subsequent
controllers default only the unit number of the first drive
(to 0) •

Enter [L/R,] vector, CSR, highest unit number <O to 7> for:
6.

DK Controller 0 [D: 220,177404]
Enter two commas (,,) followed by the highest unit number
(the number of RK05 drives minus one, if you want the first
unit number to be 0) for the first RKll controller.
This
will use the default vector and CSR assignments for the RK05
disk controller and, assign 0 as the unit number of the first
drive if you enter number of drives minus one for highest
unit number. Subsequent RKll controllers do not have default
responses.

Enter vector, CSR, VT11/VS60, number of CRT monitors for:
7.

GR Controller 0 [D: ,172000,,l]
You must enter the vector address and whether the connected
terminal(s)
is a VTll or a VS60; the CSR address and the
number of CRT monitors default to 172000 and 1 respectively.

4-16

SUMMARY OF SYSGEN PHASE I QUESTIONS
Enter [L/R,] CSR, number of A/D channels for:
8.

AD Controller 0 [D: 176770]
Enter a single comma
(,)
followed by the number of A/D
channels for the first ADOl-D analog-to-digital converter
controller. This will use the default CSR assignment for the
controller.
Note that this device is used in non-interrupt
mode and therefore, does not use an interrupt vector address
assignment.
The CSR address does not default for subsequent
ADOl-D controllers.

Enter [L/R,] vector, CSR, number of A/D channels for:

AF Controller 0 [D: 134,172570]
Enter two commas (,,) followed by the number of A/D channels
for the first AFCll analog-to-digital converter controllers.
This will use the default vector and CSR assignments for the
AFCll controller. Subsequent controllers do not have default
responses.

Enter [L/R,] clock vector, CSR, polarity mask, D=D/A channel/NO=no,
maximum number of samples/second, DRK=DRll-K/NO=no
(,DRll-K CSR) for:
10.

AR Controller 0 [D: ,170400,,,,,170420]
Enter the clock vector address (from floating vector space
starting at 300), a comma (,) to use the default CSR address,
the polarity mask word, whether or not a D/A channel
is
present, the maximum number of samples per second, whether or
not the DRll-K option is present, and, if present, a comma
(,)
to
use the default CSR address for the DRll-K.
Subsequent ARll controllers default only the CSR address of
the DRll-K options.

Enter [L/R,] clock vector, CSR, #A/D channels, G=gain ranging option/NO=no,
polarity mask, bandwith filter channel select delay,
number of D/A channels, D=digital I/O option/NO=no,
maximum number of samples/second for:
11.

LS Controller 0 [D: ,170400,,,0,0,0,NO]
Enter the clock vector address (from floating vector space
starting at 300), a comma (,) to use the default CSR address,
the number of A/D channels, whether or not the gain ranging
option is present, four commas (,,,,) (to specify 16 bi-polar
channels, no bandwith filter delay, no D/A channels, and no
digital I/O option),
followed by the maximum number of
samples per second for
the
first
LPSll
controller.
Subsequent LPSll controllers do not default the CSR address.

4-17

SUMMARY OF SYSGEN PHASE I QUESTIONS
Enter [L/R,] vector, CSR {, number of UMRs) for:
12.

LA Controller 0 [D: 300,170460,0]
Enter two commas {,,) for the first LPAll controller.
This
will use the default assignments and excludes LPAll-K UNIBUS
Mapping Register support.

Enter [L/R,] vector, CSR, # drives, O=offset recovery/NO=no offset rec. for:

L3.

DM Controller 0 [D: 2L0,177440,,0]
Enter two commas {,,) followed by the number of drives for
the first RK611 controller. This will use the default vector
and CSR assignments for the RK06/07 disk controller and
include
offset
recovery
support.
Subsequent
RK611
controllers do not have default responses.

Enter [L/R,] vector, CSR, F=full duplex/H=half duplex,
number of characters in sync leader for:
14.

XL Controller 0 [D: , ,H]
Enter the vector address (from floating vector space),
the
CSR address (from floating address space starting at 175610),
whether the line is half duplex or full duplex
{the default
is half duplex), and the number of sync characters in a sync
leader for the first DLll-E interface. Subsequent DLll-Es do
not have a default response.

14.

XP Controller 0 [D: ,174770,H]
Enter the vector address {from floating vector space starting
at 300)
followed by two commas (,,) and the number of sync
characters in a sync leader for
the first DPll interface.
This will use the default CSR assignment and specify a half
duplex line. Subsequent DPlls default only the half duplex
parameter.

14.

XU Controller 0 [D: ,,F]
Enter the vector address {from floating vector space starting
at 300), · the CSR address
(from floating address space
starting at 160010), whether the line is half duplex or full
duplex
(the default is full duplex), and the number of sync
characters in a sync leader for
the first DUll
line
interface.
Subsequent DUlls default only the full duplex
parameter.

14.

XW Controller 0 [D:

, ,H]

Enter the vector address (from floating vector space starting
at 300),
the CSR address
(from floating address space
starting at 160010), whether the line is half duplex or full
duplex
(the default is half duplex), and the number of sync
characters in a sync leader for
the first DUPll line
interface. Subsequent DUPlls do not have default responses.

4-18

SUMMARY OF SYSGEN PHASE I QUESTIONS
Enter [L/R,] vector, CSR, F=full duplex/H=half duplex/P=primary HDX for:
15.

XM Controller 0
Enter the vector address (from floating vector space starting
at 300),
the CSR address
(from floating address space
starting at 160010), and whether the line is full duplex or
half duplex for
the first DMCll interprocessor link. Note
that if the line is half duplex and the primary station, you
must enter P.

Enter [L/R] vector, CSR, printer type
(, [KMC timeout count <O=no KMC>, KMC vector, KMC CSR]) for:
16.

LP Controller 0 [D: 200,177514,LA180,0,300,160130]
Enter three commas (,,,) for the first LPll controller. This
will use the default vector and CSR assignments and exclude
KMC line printer support.

Enter number of modules, module number of first for:
17.
17.
17.
17.
17.
17.
17.

UD Controller
UD Controller
UD Controller
UD Controller
UD Controller
UD Controller
UD Controller

0 ADUOl analog input module
0 analog output module
0 bi-stable output module
O digital interrupt module
O digital sense module
0 I/O co~nter module
0 single-shot output module

The UDCll supports seven modules;
enter the number
module and the module number of the first.

each

Enter [L/R,] terminal number to redirect to (TTn:) for:
18.

CO Controller 0 [D: O]
Carriage return uses TTO:
output driver.

Enter [L/R,] NUM$
19.

as the terminal

DLll's <ZL>, NUMo

DHll's, NUM.

for

the

console

DZll's, NUM.

DJll's for:

The terminal driver [D: l,O,O,O]
Enter carriage return to specify
asynchronous line interface.

that

you

have

one

DLll

Note that this question appears only if you selected the user
oriented or the baseline terminal drivers;
the full duplex
terminal driver is always loadable.

4-19

SUMMARY OF SYSGEN PHASE I QUESTIONS
Enter NUM.
20.

DLll's <ZL>, NUM.

DHll'S, NUM.

DZll'S, NUM.

DJll's for:

The terminal driver [D: l,O,O,O]
Enter carriage return to specify that you have one DLll
asynchronous line interface. This question appears only if
you selected the full duplex terminal driver.

Enter vector, CSR for:
21.

ZL Controller 0 [D: 60,177560]
Carriage return uses the default vector and CSR assignments
for
the first DLll asynchronous line interface. Subsequent
DLlls do not have default responses.

Enter vector, CSR, highest line number <O to 15>
(,answer speed, DMll-BB vector, DMll-BB CSR) for:
22.

DH Controller 0 [D:

,,,300,0,0]

Enter the interrupt vector address
(from floating vector
space),
the CSR address (from floating address space), and
the highest line number (O=one line, 15=sixteen lines). This
will exclude DMll-BB support for the first DHll interface.
If the DHll includes DMll-BB modem support,
you must also
enter the answer speed
(300 is the default), the DMll-BB
interrupt vector address (from floating vector space),
and
the DMll-BB CSR
(from floating address space). Subsequent
DHlls do not have default responses.

Enter vector, CSR, highest line number <O to 15> for:
23.

DJ Controller O
Enter the interrupt vector address
(from floating vector
space),
the CSR address (from floating address space), and
the highest line number (O=one line,
15=sixteen lines)
for
the first DJll multiplexer.

Enter vector, CSR, highest line number <O to 7> [,answer speed]
24.

DZ Controller 0 [D:

for:

, , ,OJ

Enter the interrupt vector address
(from floating vector
space),
the CSR address (from floating address space), and
the highest line number (O=one line, ?=eight lines)
for
the
first
DZll multiplexer.
This will exclude DZll modem
support.
If you wish modem support, enter the answer speed
baud rate.

4-20

·-

SUMMARY OF SYSGEN PHASE I QUESTIONS
If you selected an MM device, SYSGEN requests
number as follows:
51.

MM controller 0 unit

formatter

The default is unit number

the

TM02/03

formatter

[D R:0-7 D:O]

If you selected a DB device, SYSGEN requests drive type as follows:
52.

Contr 0 unit

is an RP04,05/RP06 [D:RP06]

The default is RP06.

If you selected
53.

DL device, SYSGEN requests drive type as follows:

Contr 0 unit

is an RL01/RL02 [D:RLOl]

The default is RLOl.

If you selected a DM device, SYSGEN requests drive type as follows:
54.

Contr 0 unit 0 is an RK06/RK07 [D:RK06]
The default is RK06.

If you selected a DP device, SYSGEN requests drive type as follows:
55.

Contr 0 unit 0 is an RP02/RP03 [D:RP03]
The default is RP03.

If you selected a DR device, SYSGEN requests drive type as follows:
56.

Contr 0 unit 0 is an RM02/RM03 [D:RM03]
The default is RM03.

If you selected a DS device, SYSGEN requests drive type as follows:
57.

Contr 0 unit O.

is an RS03/RS04 [D:RS04]

The default is RS04.

If you selected a DY device, SYSGEN requests drive density as follows:
58.

Contr 0 unit O.

is SINGLE/DOUBLE density

You must specify whether the
double density.

4-21

RX02

drive

single

SUMMARY OF SYSGEN PHASE I QUESTIONS
If you selected ICS/ICR subsystems or DSS/DRS modules, SYSGEN asks the
following questions.
1.

Expanded comments for ICS/ICR questions
Enter Yes for explanatory text.

Do you want task activation from unsolicited interrupts
Enter Yes to permit the driver to initiate a
driver receives unsolicited input.

The

the

standard

234.

171776.

The

CSR address
Enter the CSR address.
The standard
acceptable range is 160000-177700.

when

IC controller 0 vector address
Enter the interrupt vector address.
The acceptable range is 234-774.

task

Is it an ICR-11
Enter Yes to specify an ICR-11, No to specify an ICS-11.

Number of A/D converter modules in this ICS/ICR
Enter the number of modules in the range 0-16.

A/D converter module number
Enter the A/D converter module number in the range 0-35.

Number of expansion multiplexers
Enter a value in the range 0-7.

The ICS/ICR subsystem consists of six modules.
SYSGEN requests the
number of modules (questions 12-17) and the module number of each
(question 9).
12.

Number of D/A converter modules in this ICS/ICR

13.

Number of single-shot output modules in this ICS/ICR

14.

Number of bi-stable output modules in this ICS/ICR

15.

Number of digital sense modules in this ICS/ICR

16.

Number of digital interrupt modules in this ICS/ICR

17.

Number of I/O counter modules in this ICS/ICR

(module name} module number

10.

Restore module status on power and error recovery
Enter Yes to select this option.

11.

How many line errors are acceptable per second
If you selected option 10, enter a value in the range 0-5000.

4-22

SUMMARY OF SYSGEN PHASE I QUESTIONS
18.

Expanded comments for DSS/DRS questions
Enter Yes for explanatory text.

19.

Number of DRS-11 modules
Enter a value in the range 0-16. Questions 20, 21, and 22
pertain to DRS-11 modules;
if you enter O,
these are
omitted.

20.

Restore module status on power and error recovery
Enter Yes to select this option

21.

DRS-11 CSR address
Enter a value in the range 160000-177700.

22.

DRS-11 vector address
Enter a value in the range 300-774.

23.

Number of DSS-11 digital input modules
Enter a value
question 19.

24.

the

range

0-16

minus

the

response

DSS-11 CSR address
Enter a value in the range 160000-177700.

25.
~

DSS-11 vector address
Enter a value in the range 300-774.

26.

Task activation from unsolicited interrupts
Enter Yes to select this option.

If your system includes IP11/IP300 support, SYSGEN asks the
questions.
1.

following

Extended comments for IP11/IP300
Enter Yes for explanatory text.

Treat all controllers as one unit
Enter Yes to
controllers.

generate

single

SCB

Any latching digital output modules
Enter Yes to include support in driver.

Any single-shot output modules
Enter Yes to include support in driver.

4-23

and

UCB

for

all

SUMMARY OF SYSGEN PHASE I QUESTIONS
5.

Direct output via QIO
Enter Yes to simplify coding, but increase overhead.

Any non-interrupting digital sense modules
Enter Yes to assemble c6de for this module.

Any interrupting digital sense modules
Enter Yes to assemble code for this module.

Any change-of-state modules
Enter Yes to assemble code for this module.

Any counter modules
Enter Yes to assemble code for this module.

10.

Direct input via QIO
Enter Yes to simplify task code at the expense of overhead.

11.

Unsolicited interrupt support
Enter Yes and tasks can monitor unsolicited
the interrupting modules.

12.

from

Event flag linkage to interrupts
Enter Yes to permit
through event flags.

13.

interrupts

tasks

monitor

digital

interrupts

Any D/A converters
Enter Yes to assemble code for this module.

14.

Any A014 A/D converters
Enter Yes to assemble code for this module.

15.

Any A020 A/D converters
Enter Yes to assemble code for this module.

16.

How many output bytes should be saved on powerfail
Enter a value in the range 0-3048(10).

17.

IPll vector
Enter a value in the range 60-774.
234.

18.

The

standard

vector

Base address
Enter the IPll base address (base address is CSR minus 377
octal).
The default for the first controller is 171000 and
171400 for the second. Acceptable range is 160000-177400.

4-24

CHAPTER 5

DETAILS OF SYSGEN PHASE I

This chapter contains detailed descriptions of
questions by sections. The phase 1 sections are:
•
•
•
•
•
•

SYSGEN

Phase

Setup Questions
Target Questions
Host Questions
Executive Questions
Terminal Driver Questions
Peripherals Questions

The questions are listed in numeric order.
Not all the questions
appear;
the order of the questions is based on your responses. Also,
the peripherals section follows a strict numeric order, not logical
sequence.
Figure 5-1 shows the processing steps that take
Phase I.

SYSGEN.C~
SYO:

place

during

SYSGEN

1. Invoke SYSGEN.

SYSSAVED.DAT

SYSSAVED~
Target ~me

or
Terminal Input
or
A Combination
of the Abovu.

SYSS.AVED.DAT
RSX MC.MAC

SYSTB.MAC

RSXJl1SM.CMD
RSXDRVASM.CMD
RSXBLD.CMD
SGMPARM.CMD
ICSBLD.CMD
ICRBLD.CMD

2. Answer SYSGEN Part I
Questions.
• Setup questions
•Target questions
• Host questions
• Executive questions
• Terminal driver
questions
• Peripherals questions

101

Figure 5-1

3. Assemble the executive,
device drivers, terminal
driver, and privileged
tasks.

-i>E~

RSXASM.CMD

RSXDRVASM.CMD
RSXBLD.CMD
SGMPARM.CMD
ICSBLD.CMD
ICRBLD.CMD

v{- 3 RSX11M.OBJ

Processing Steps in SYSGEN Phase I

5-1

rSXMC.MAC
SYSTB.MAC

DETAILS OF SYSGEN PHASE I
Step 1 in Figure 5-1 is invoking SYSGEN, as described in Chapter 3.
Step 2 in Figu~e 5-1 is answering the questions in each of the
sections in SYSGEN Phase I. For this process, you c~n answer all
the questions explicitly at your terminal,
you can use saved
answers,
or you can use a combination of saved answers and
explicit answers.
As you answer the Phase I questions that define your system,
SYSGEN is building files that correspond to your answers.
These
files are the output of SYSGEN Phase I:
SYSSAVED

SYSSAVED is the file
that contains symbols
that
correspond to your answers to SYSGEN Phase I questions.
SYSSAVED.CMD is used as input to later
SYSGENs.
SYSSAVED.DAT is the output from a SYSGEN.

RSXMC.MAC

RSXMC.MAC is the assembler source file
that comprises
the executive features defined during SYSGEN Phase I.
This file is assembled in Step 3.

SYSTB.MAC

SYSTB.MAC is the assembler source file
that contains
the data structures for devices selected during SYSGEN
Phase I.

RSXASM.CMD

RSXASM.CMD is the command file that
of the executive.

RSXDRVASM.CMD

RSXDRVASM.CMD is the command
assembly of the device drivers.

RSXBLD.CMD

RSXBLD.CMD is the command file that controls
building of the executive.

SGNPARM.CMD

SGNPARM.CMD is the RSX-llM indirect command processor
file
that contains symbols defined in SYSGEN Phase I
for use in controlling SYSGEN Phase II processing.

ICTAB.MAC

ICTAB.MAC contains the ICS/ICR data structures.

controls

assembly

that

controls

file

the

task

Step 3 in Figure 5-1 is the assembly of the executive, device drivers,
terminal driver, and privileged tasks.
Input to Step 3 is output of Step
those files above.

refer

description

SYSGEN controls the assembly and creates an object
corresponds to the system you defined in Step 2.
If all assemblies are successful, SYSGEN completes
displays the <EOF> prompt.

5.1

file

execution

of
that
and

SYSGEN SETUP QUESTIONS

The SYSGEN Phase I setup section asks questions that provide SYSGEN
with information describing the way you want the program to execute,
input to SYSGEN, and what kind of output you want from SYSGEN.

5-2

DETAILS OF SYSGEN PHASE I
SYSGEN asks a series of questions that define whether to:
•

Execute MCR commands

•

Use saved answers as input to SYSGEN

•

Use breakpoints

When you are generating a system for the first time, you may
follow the logical
flow through the SYSGEN command files.
case, the setup section of SYSGEN asks the question:

wish to
For this

* l~ Do you want to inhibit the execution of MCR commands [Y/N]:
An affirmative response to this question prevents SYSGEN from creating
or deleting files as well as inhibiting MACR0-11 and the Task Builder
execution, UIC modification, device mounting, and logical assignments.
When you inhibit MCR commands, SYSGEN asks all Phase I
questions as
usual, and creates SYSSAVED.DAT if you request it, but doesn't execute
MCR commands required to build a system.
This feature allows you to practice the system generation to see how
SYSGEN asks questions and to plan the way you want to answer questions
when MCR commands are not inhibited in later system generations.
SYSGEN provides breakpoints, or pauses in execution,
generation.
There are three types of breakpoints:
•

End-of-Section (EOS) Breakpoints

•

End-of-Execution (EOX) Breakpoints

•

End-of-Disk (EOD) Breakpoints

during

system

These breakpoints are used for various purposes, but can be overridden
so that SYSGEN can execute unattended when that is appropriate.
End of section breakpoints are pauses at the end of each section of
SYSGEN dialogue questions.
In SYSGEN Phase I, there are six sections
of dialogue questions.
You can choose to answer the questions in all
sections without interruption or you can direct SYSGEN to pause after
you answer each section.
This breakpoint in the dialogue gives you
the opportunity to:
•
•
•
•

Continue the dialogue
Repeat the ~ection of question, perhaps to correct
answers
Exit the SYSGEN program
Suspend execution of the SYSGEN program (.PAUSE)

Note that if you type CTRL/Z in response to any question, SYSGEN exits
cleanly (for example, closes all files).
Figure 5-2 shows where End-of-Section breakpoints occur in the flow of
SYSGEN Phase I.
Execution breakpoints
(EOX)
in the SYSGEN procedure occur after
completion of a MACRO assembly or a Task Build operation. SYSGEN can
pause at these points to ensure successful completion of the assembly
or build operation.
When you know files will execute successfully,
you can direct SYSGEN to continue processing without the breakpoint
pause.

5-3

DETAILS OF SYSGEN PHASE I
Figure 5-2 shows where End-of-Execution breakpoints occur in the
of SYSGEN Phase I.

flow

@SYSGEN
1
Setup Questions
1
EOS
1
1

Host and Target Questions
1

EOS
1
1

Executive Questions
1
EOS
1

Peripherals Questions
1

EOS
Executive Assembly
EOX
Executive Task Build
EOX
Terminal Driver Task Build

EOX
Privileged Tasks Task Build
1

EOX
Figure 5-2

End-of-Section and End-of-Execution Breakpoints in
the Flow of SYSGEN Phase I

.•
As shown in Figure 5-2, a flow of execution through SYSGEN Phase I can
be interrupted by end-of-section breakpoints.
During Phase II, SYSGEN
execution can be interrupted by end-of-execution breakpoints.
You can
direct SYSGEN to override these breakpoints and execute unattended by
means of questions asked in the setup section of SYSGEN Phase I.

5-4

DETAILS OF SYSGEN PHASE I
End-of-disk breakpoints (EOD) occur in system generations with RKOS
distribution kits. After SYSGEN completes processing with the EXCSRC
volume in the RKOS kit, SYSGEN prompts you for the next disk required:

* EOD *If not in [dduu:], enter driver source files device
(dduu:)
At this point, you remove EXCSRC from the drive and
DRVSRC.

replace

with

In the same cases, where your configuration includes more than two
drives, you can override EOD breakpoints to run SYSGEN unattended.
Parts I, II, and III of SYSGEN all reside in UFD [200,200].
However,
whi.le it executes, SYSGEN resets the UIC under which it runs to store
files in appropriate UFD's.
When you stop SYSGEN execution, for any reason, and want to
execution later, ensure that you set your UIC to [200,200].

resume

The following' is a list of the questions.
* 1. Inhibit MCR command lines (Type <ESC> for explanation)
This option permits you to perform a PREPGEN;
the SYSGEN
questions
are
asked in the logical order
(based on your
responses), but SYSGEN inhibits the processing of MCR commands and
commands that assemble, build, create, or delete files.
A PREPGEN
permits you to follow the logical flow of a SYSGEN and helps
familiarize you with the questions specific to your SYSGEN. Also,
a PREPGEN allows you to schedule actual SYSGEN processing;
you
perform a PREPGEN, save the responses
(answer Yes to setup
question 10), and then submit the saved answer file for SYSGEN
processing at your convenience.
NOTE
To successfully complete a PREPGEN, you
must mount all required volumes as well
as establish logical assignments for
pseudo devices SY: and LB:. Refer to
Chapter 3.
If you respond Yes, SYSGEN asks Setup Question 3;
No, SYSGEN asks Setup Question 2.

if you

respond

* 2. Have you made a copy of the distribution kit
A copy of the distribution kit insures that you have a backup copy
in case you inadvertently delete important files or data during
the system generation process. Also, a backup copy serves as a
base for future updates.
If you answer this question No, SYSGEN displays the message:
SGN -- You are or will be running on the original copy of the
distribution kit.
Make a copy via the standard procedure and
restart.
SYSGEN then exits to allow you to copy the media.

5-5

DETAILS OF SYSGEN PHASE I

* 3~ Use saved or canned answer file for input responses
This question permits you to direct SYSGEN to use a saved answer
file
(either a canned or a SYSGEN created one) as input. If you
respond Yes, SYSGEN uses a file named SYSSAVED.CMD to obtain
responses to questions. Note that SYSGEN does not save responses
for ICS/ICR, DSS/DRS, or IP11/IP300 devices; you must enter the
responses
for these devices.
Question 10 provides details
concerning saved answer files.
If you respond Yes, SYSGEN asks you whether or not you want to
re-answer the host or device configuration questions and bypass
breakpoints in Setup Questions 4, S, 6, 7, and 8: these questions
provide options for use with saved answers. If you respond No and
you are using the RKOS kit, SYSGEN asks question 9;
for other
kits SYSGEN asks question lD.

* 4. Undefined answer wakeup
This feature causes the terminal bell to ring when SYSGEN
encounters an undefined symbol when using the saved answer file
SYSSAVED.CMD (SYSGEN precedes the question with a CTRL/G).
This question is asked only if you responded
(Use saved answers).

Yes

question

* 5. Use saved host configuration
This question allows you to use previously-defined (saved) answers
to host section questions.
In the case where you are running
SYSGEN online and already have all the listings you need, you may
want to redefine the host answers in the saved answer file
(SYSSAVED.CMD) to redefine the way SYSGEN handles listings.
An
affirmative response implies that you are performing a SYSGEN on
the same, or similar, configuration you used to create the saved
answer file.
This question is asked only if you responded
(Use saved answers).

Yes

question

* 6. Use saved peripheral configuration
This question provides you
the
opportunity
to
use
the
previously-defined (saved) peripheral configuration contained in
the file SYSSAVED.CMD.
If you respond Yes to this question, SYSGEN uses the saved
peripheral configuration specified by the symbols $DEV, $DV2, and
$DV3. If you respond No, SYSGEN asks Executive question 16. Note
that a negative response does not affect the saved answers and
does not permit you to change vectors or CSRs of previously
defined devices.
A negative response permits you to change only
the number of controllers;
respond No to add
or
delete
controllers.
This question is asked only if you responded
(Use saved answers).

5-6

Yes

question

DETAILS OF SYSGEN PHASE I

* 7. Skip end of section (EOS) breakpoints
This question allows you to choose whether or not to skip
End-of-Section
(EOS)
breakpoints. At these breakpoints, you can
select whether to continue SYSGEN questions, repeat questions in
the preceding sections
(to correct wrong answers), exit from
SYSGEN, or cause SYSGEN to pause. This feature is also one which
in combination with other features defined in this section, allows
you to run unattended SYSGENs.
Breakpoints occur at the following points in SYSGEN Phase I:
•
•
•

After the Target and Host section
After the Executive and Terminal Drivers section
After the Peripherals questions

If the answers in SYSSAVED.CMD already define the system you want
to generate, you can direct SYSGEN to complete execution of Phase
I without interruption by answering Yes to this question.
Note that the laboratory and I/O peripherals questions cannot be
repeated
(as can Executive questions).
However, if you specify
repeat at the EOS breakpoint, SYSGEN renames SYSSAVED.DAT to
SYSSAVED.CMD so that you can continue where you left off.
This question is asked only if you responded
(Use saved answers).

Yes

question

* 8. Skip end-of-execution (EOX) breakpoints
End-of--Execution
(EOX)
breakpoints occur after the
MACR0-11
assembler and the Task Builder complete execution.
If you know
that processing will complete successfully, answer Yes to direct
SYSGEN to process without pausing at completion of MACR0-11 or
Task Builder execution.
If you answer No, SYSGEN pauses after execution of these tasks
allow you to check and correct the results.

This question is asked only if you responded
(Use saved answers).

Yes

question

* 9o Skip end of disk (EOD) breakpoints
The dual RKOS distribution kit imposes a breakpoint when you must
change disks after assembling the Executive. You must swap the
EXCSRC disk with the DRVSRC disk to assemble the device drivers.
An affirmative (Yes) response to this question implies that a
third disk drive is available and that the drive contains the
driver source files.
Thus, SYSGEN can assemble the Executive,
using the EXCSRC disk,
and then assemble the device drivers,
without interruption, using the drive that contains the driver
source files.
If you respond Yes to this question, you are asked
(in question 15) to identify the device that contains the driver
source files.
Note that this device can be a third RK05 drive or
a drive of a different type.
(If a drive of a different type
is
used,
the volume must completely contain the contents of the
DRVSRC disk.
Also, the driver must be loaded and you must mount
the volume.)

5-7

DETAILS OF SYSGEN PHASE I

* 10. Save responses (i.e.:

create SYSSAVED.DAT)

When you respond Yes to this question and request a saved answer
file,
SYSGEN creates an indirect command file named SYSSAVED.DAT.
This file consists of .SET directives which assign values to the
symbols defined by your responses to SYSGEN questions (indirect
command file processor
directives
are
described
in
the
RSX-llM/M-PLUS MCR Operations Manual).
For example, when you
enter a processor type in response to target question 1
(such as
•11/70), SYSGEN writes the following line to the file SYSSAVED.DAT:
.SETS $TPR "11/70"
Appendix A lists all the symbols that SYSGEN defines in a saved
answer file and identifies the option that each symbol represents.
You can then use the saved answer file as input to a later SYSGEN
simply by renaming the file to SYSSAVED.CMD and responding Yes to
question 3. Thus, saved answer files permit you to generate
duplicate or similar systems without the need to answer the SYSGEN
questions.
More importantly, you can edit the SYSSAVED.DAT file to correct an
errant response or to alter specific system characteristics.
For
example, you generate a system, but do not include 20K Executive
support and then find you need more DSR space. The saved answer
file permits you to generate the same system, except with support
for a 20K Executive;
simply edit SYSSAVED.DAT and set symbol $20K
to true (.SETT $20K). Then rename SYSSAVED.DAT to SYSSAVED.CMD
and submit the command file as input to SYSGEN. All the options
you included in the 16K Executive system are then included in the
20K Executive system. To correct an errant response, enter Exit
at the next end-of-section breakpoint or respond with CTRL/Z to
any question
(CTRL/Z closes SYSSAVED.DAT and exits SYSGEN). You
can then edit and rename the command file and restart SYSGEN.
If you alter specific system characteristics, be sure to read the
detailed description of those options/features. Some options,
like cat and mouse, are mutually exclusive and some options
require or automatically include other options.
Note that in extreme cases where you change the system complexion,
it is more practical to perform a complete SYSGEN rather than
attempt to edit the saved answer file.
For example, do not toggle
the settings for $11S or $MAP, since these symbols effect
system-wide characteristics.
You can delete any number of responses in SYSSAVED.CMD;
SYSGEN
asks the respective question when a symbol is missing from the
saved answer file.
In this case,
it is especially useful to
specify undefined answer wakeup (respond Yes to question 4).
NOTE
SYSGEN does not
save
answers
for
DRS/DSS, ICS/ICR, or IP11/IP300 devices.

5-8

DETAILS OF SYSGEN PHASE I

* ll. UIC for SYSSAVED files if not [defaultuic]
If you want to use saved answer files, enter the UIC of the saved
answer file you are using or will create.
In certain cases, you
may want to have features for various systems, each system created
under a different UIC.
If you respond with a carriage return, SYSGEN uses your current
UIC for saved responses.
Otherwise, enter the UIC under which you
want responses saved.

* 12. UIC for SYSGEN command files if not [sysgenuic]
This question allows you to select
looks command files.

the

UIC

under

which

SYSGEN

If you are not inhibiting MCR lines, sysgenuic is
[200,200].
If
you are inhibiting MCR lines, sysgenuic is the same as the default
UIC of the terminal when you invoke SYSGEN.

* 13. Clean up files from previous GENs
In cases where you are generating multiple systems on the same
media,
SYSGEN creates files that may not be appropriate from one
system to the next.
This question gives you the oppoftunity to
request that SYSGEN delete all such unnecessary files.
This question is asked only if you respond No to Setup Question
(Inhibit MCR commands).

* 14. Device, when ready, for Executive sources (ddu:) [D:SY:]:
Enter the device type and unit number
(ddu:)
for
the unit
containing the Executive source files
(on volume EXCSRC), for
example, DK!:. The trailing colon is appended by SYSGEN when it
is omitted.
The default when you are using a big disk distribution kit is SY:.
This question is always asked.
NOTE
If you are performing a PREPGEN, SYSGEN
does not issue a Mount command for the
Executive source device.
(See Chapter
3.)

* 15. Device, when ready, for driver sources (ddu:)
This question appears only if you are using the dual RKOS
distribution kit and responded Yes to question 9 (skip end-of-disk
breakpoints).
Enter the device type and unit number
(ddu:)
for
the unit
containing the driver source files (DRVSRC), for example, DK3:.
The trailing colon is appended by SYSGEN when it is omitted.

5-9

DETAILS OF SYSGEN PHASE I
5.2

TARGET CONFIGURATION DEFINITION QUESTIONS

This section of questions defines the processor type and options,
system type, and peripheral devices included in the target system.

* 1. Processor (e.g.:

11/34, LSI-11) (5:6]

Enter the target processor type.
Valid entries are:
11/03
11/04
11/05
11/10
11/15
11/20

11/23
11/34
11/35
11/40
11/45
11/50

11/55
11/60
11/70
LSI-11

This question is always asked.

* 2. Does processor have a switch register
The switch register is the register that contains the toggle
settings on the front panel of your processor. Certain processors
(the 11/34, for example) may have neither toggles nor a switch
register.
If your processor does not have a switch register, you are
restricted from' using the Executive directive, GSSW$ (Get Sense
Switch), which reads the contents of the switch register.
This question appears only if your processor, as defined in Target
Question 1, is a PDP-11/03, 11/04, 11/34, or 11/60. Other
processors always include a switch register.

* 3. Generating RSX-llS
The answer to this question specifies whether you
an RSX-llM or RSX-llS system.

are

generating

This question is always asked.

* 4. Memory size (in K-word blocks) [min:max]
Enter the amount of memory for your processor in 1024-word blocks.
The legal range is from 16K through 1920K; but depends on the
minimum and maximum memory sizes for your processor.
SYSGEN
calculates the range values (min and max) based on your response
to question 1.
The table below shows the minimum and
RSX-llM-supported PDP-11 processors.

maximum

memory

sizes

Note that memory size must be specified in 4K increments.

5-10

for

DETAILS OF SYSGEN PHASE I
Processor
LSI-11, 11/03
11/04
11/05 I 11/10
11/15 I 11/20
11/70 I
all others

Default Memory Size
llM
llS
min
~ ~
-8- ms.!
not supported
28
16
28
8
28
16
8
28
28
16
8
28
28
32
1920
124
32
16
8
124
124

In the category "all others," above,
the processors
PDP-11/34, 11/35, 11/40, 11/45, 11/50, 11/55, and 11/60.

are

the

J>.

NOTE
If your processor is an 11/70 and you
want the 22-bit addressing option, you
must specify a memory size of 128K or
greater.

* 5. Mapped
The answer to this question specifies whether the target system
includes the Memory Management Unit (KT-11).
If it does, enter
Yes to generate a mapped system. This question is always asked.
The memory size you specify in question 4 must be consistent with
the mapping option;
you must have at least 24K of memory to
generate a mapped system and a maximum of 28K to generate an
unmapped system.
The LSI-11, PDP-11/03, 11/04, 11/05, 11/10,
processors do not support mapped systems.

11/15,

and

11/20

You must answer Yes if your processor has more than 28K of memory.
If you enter a memory size inconsistent with the mapping option,
SYSGEN displays an error message and repeats both questions.
If you respond Yes to this question, SYSGEN automatically includes
Executive support for address checking and I/O rundown (see
Executive questions 9 and 10).

* 6. Any K-series laboratory devices
The K-series laboratory options are a set of real-time data
acquisition modules which interface to the PDP-11 family of
computers.
Answer YES if you want support for the K-series software routines
(see the RSX-llM/M-PLUS I/O Drivers Reference Manual).
If you
enter Yes, SYSGEN automatically includes connect to interrupt and
AST and cancel selective marktime support.

* 7. Extended arithmetic element (KEll-A/B EAE) present
The extended arithmetic element (EAE) is a hardware feature that
performs
signed
integer
multiplication,
division,
multiple-position shifts, and normalization.
The EAE performs
these functions significantly faster than software subroutines.

5-11

DETAILS OF SYSGEN PHASE I
This question is not asked if the processor has memory management
and is not asked for non-UNIBUS PDP-lls {for example, the PDPll/03
and LSI-11).

* 8. Floating point processor (FPll) present
The PDP-11 floating point processor
(FPll-A,C,E)
performs all
floating point arithmetic operations and converts data from
integer to floating point format and vice versa.
The FPll-A is
available for the PDP-11/34 processor. The FPll-C is available on
the PDP-11/45, 11/50, 11/55, and 11/70 processors. The FPll-E is
available for the PDP-11/60 processor. Also, there is a floating
point option for the 11/23 that is compatible with the FPll.
This question does not appear for other processors.
If the target processor is a PDP-11/60, floating point support
automatically included and the question is not asked.
This feature should not be confused with the floating
set (FIS) available on the PDP-11/40 processor.

instruction

If you respond No to this question, Target Question 9 is asked.
If you respond Yes to this question, SYSGEN automatically includes
Executive support for Asynchronous System Traps (AST support) (see
Executive question 16).

* 9. Floating instruction set (FIS) present
The floating instruction set
(FIS)
feature
includes hardware
functions that perform floating point add, subtract, multiply, and
divide instructions.
This feature
is available only on the
LSI-11, PDP-11/03, and 11/40.
This question is asked only if the target processor is one
above.

* 10. If using KWll-P as system clock:

listed

number of ints/sec.[0:1000.)

RSX-llM/S requires a real-time clock for operations. Three clocks
are available:
the KWll-P programmable frequency clock, the
KWll-L line frequency clock, and the DLll-W line frequency
clock/console.
If your system has a KW-llP and you want to use
this clock as your system clock, the acceptable range is from 1
through 1000.
A response of 0 indicates there is no programmable clock in this
configuration or that you want to use the line frequency clock.
This question is not asked
PDP-11/03, or PDP-11/23.

your

processor

the

LSI-11,

The number of interrupts you select must be divisible evenly
10000.

into

More than 100
(decimal)
clock interrupts-per-second
greatly
increases system overhead;
you should carefully consider the
impact on your system before specifying a number greater than 100
(decimal) per second.

5-12

DETAILS OF SYSGEN PHASE I

* 11. Line frequency:

A- 60 Hz B- SO Hz [Default:

•A•]

You can specify a line frequency of either 50 or 60 hertz. In the
USA, line frequency is always 60 hertz. The default response is
60 hertz.
This question is always asked.

* 12. KWll-Y Watchdog timer support
The KWll-Y watchdog timer is a hardware clock ,that constantly
attempts to time-out system activity. The executive refreshes the
timer at every clock interrupt. If the system faults or if a
hardware failure occurs and the timer expires, a signal is
generated to indicate that the system has been corrupted.
This question is always asked.
If you select this feature, the system you generate will run only
on a configuration that includes the KWll-Y watchdog timer. If
you attempt to boot your system on a configuration that does not
include a KWll-Y watchdog timer, the system crashes immediately.

* 13. Memory parity support
If your system includes parity memory and
support to detect parity errors, enter Yes.

you

want

Executive

This question is always asked.
If you respond No to this question, Target Question 14 (cache
memory) is not asked. If you respond Yes to this question, SYSGEN
asks Target Questions 14 and 15.

* 14. Cache memory
Cache memory
processors.

available

PDP-11/34,

If your system includes cache memory and
support to detect parity errors, enter Yes.

11/60,
you

and

want

11/70

Executive

This question is asked only for the processors listed above when
you select memory parity support (Target Question 13) for those
processors.
*15. Highest interrupt vector (If O will be computed) [0:774]
The response to this question specifies the highest interrupt
vector address.
If you respond 0 (or carriage return) or with a
value less than 400, SYSGEN calculates this address based on your
answers to the peripheral questions.
This question is always asked •

•

Enter a value greater than 400 if you require vector
devices that will not be specified during this SYSGEN.

5-13

space

for

DETAILS OF SYSGEN PHASE I
NOTE
SYSGEN does not write this symbol to
SYSSAVED.DAT
until you complete the
peripheral section.

* 16. Devices
This question allows you to enter,
in mnemonic form,
the
peripherals and pseudo-devices for your configuration. To help
select the appropriate d~vice mnemonic, enter an asterisk
{*) to
generate a list of devices.
The following is a list of the
peripheral devices that RSX-llM supports:
Device
Mnemonic
AD
.l\F

AR
CR
CT
DB
DD
OF
DK
DL
OM
DP
DR
DS
DT
DX
DY
GR
IC
IP
IS

LA
LP
LS
MM
MS
MT
pp

PR
UD
XB
XL
XM
XP
XQ
XU

Controller{s)

Description

Analog-to-Digital Subsystem
ADOl-D
Low Level Analog Input Subsystem
AFCll
Analog Real-Time Module
ARll
Punched Card Reader
CRll CMll-F
TAll TU60
Cassette Drive
Disk Drive
RP04 RP05 RP06
DECtape Drive
TU58
Fixed-head Disk Drive
RFll
DECpack Cartridge Disk Drive
RKll RK03 RK05
Disk Drive
RLll RLOl RL02
Disk Drive
RK611 RK06
Disk Drive
RPll RP02 RP03
Disk Drive
RM02 RM03
RS03 RS04
Fixed-head Disk Drive
DECtape Drive
TCll TU56
Floppy Disk System
RXll RXOl
Floppy Disk System
RX211/RX02
Graphics Display System
VTll VT60
!CS ICRll
Subsystems
Subsystems
IPll/IP300
Subsystems
DRS DSSll
LPAll
Laboratory Peripheral Accelerator
LP LS LVll LA180
Line Printers
Laboratory Peripheral System
LPSll
TU16 TU45 TU78 TE16 Tape Drives
TS04
Tape Drive
TMll TUlO TElO TS03 Tape Drives
High-Speed Paper Tape Reader
PCll
PRll PCll
High-Speed Paper Tape Punch
UDCll
Universal Digital Control Subsystem
DAll-B
Unibus Link
Single Asynchronous Serial Line Interface
DLll-E
Network Link
DMCll-E
Synchronous Line Interface
DPll
NPR Synchronous Line Interface
DQll
Synchronous Line Interface
DUll
Synchronous Line Interface
DUPll

5-14

DETAILS OF SYSGEN PHASE I
Enter devices in the form:
device[=controllers]
where device is the device mnemonic and controllers is the number
of controllers for the device type. Brackets denote an optional
entry and are not part of the syntax.
If you omit the controller
entry
(=controllers), SYSGEN assumes one controller for that
device type.
Terminate this question by entering a period(.)
either
the last controller you enter or on a line by itself.
r

following

Generally, there may be one controller for several devices of a
given type.
For example, four RK05 drives can be connected to one
RKll controller.
In this case, all you are required to enter in
response
to this question is DK;
SYSGEN defaults to one
controller for all four drives.
If you make a mistake and specify a device type that is not
included in the target configuration, enter device=O. Also, if
you specify the wrong number of controllers, you can correct this
by reentering; SYSGEN uses the most recent response for duplicate
entries.
For example,
if your system
includes
two
RKll
controllers
(four RK05 drives)
and dne TCll DECtape controller
(two TU56 drives),
the following sequence corrects an errant
response of three RKlls, two TU58s, and on~ RLll.
Devices:
Devices:
Devices:
Devices:
Devices:
Devices:
Devices:

DK=3
DT=2
DL
DK=2
DT
DL=O

To specify the number of paper tape
device controllers, you must consider
the number of PCll reader/punch and the
number
of PRll readers.
Enter the
number of PClls as PP=n, where n is the
number of PCll controllers.
Enter the
number of PRll controllers as PR=k,
where
k
is
the
number
of PRll
controllers plus n (the number of PCll
controllers).
For example,
if your
system includes one PCll and two PRlls,
enter the following:
PP=l
PR=3

5.3

HOST CONFIGURATION QUESTIONS

This section of questions defines the configuration on which
running SYSGEN.

5-15

you

are

DETAILS OF SYSGEN PHASE I

* 1. Are you running SYSGEN standalone (on the baseline system)
This question
standalone.

specifies

whether

you

are

running

online

If you respond Yes, SYSGEN assumes that you cannot spool
and maps and does not ask Host Question 3.

listings

Note that if you are running SYSGEN online,
you cannot
listings or maps directly to the line printer (LP:).

direct

* 2. Is a line printer available
This question is asked to allow you to specify the device to which
maps and listings are sent (line printer if Yes, terminal if No).
If you respond NO, you cannot specify that the line printer
is the listing device.

(LP:)

* 3. Spool assembly listings and Executive and driver maps
This question allows you to specify whether or not to spool
listings.
For example, you can direct listings to an intermediate
device.
If you want the listings spooled to the line printer
respond Yes to this question.
If you want to save the listings
but not spool them, respond No to this question.

* 4. Does the listing/map device have at least 120 columns
If the listing device does not have at least 120 columns, SYSGEN
creates a narrow listing file for map listings.
For information
on narrow listings, refer to the descriptions of the /LI switch
for MACR0-11 and the /WI switch for the Task Builder.

* !). Assembly listing file device {ddu:)

[D:

•NL:•]

This question allows you to choose whether or not to direct
listings to an RSX-llM logical or pseudo device or to not generate
them at all.
Specify LP:
to send the listings to the line printer if you are
running standalone,
to a disk device (dduu:) if you are running
online, and NL:
(the null device) to direct SYSGEN not to produce
assembly listings.
NOTE
SYSGEN does not load the driver for
device you specify.

the

* 6. Map device for Executive and device drivers (ddu:)

[D: mapdevice]

The response to this question defines the default device to
you want to direct the Executive and device driver maps.
It is recommended that you specify a device for these maps.

5-16

which

DETAILS OF SYSGEN PHASE I
For unmapped systems, you should specify a device, since the maps
are required to determine the size of the Executive and to layout
memory partitions in SYSGEN Phase II.
Note that you can override the device for driver maps in Phase II.

5.4

EXECUTIVE QUESTIONS

This section allows you to choose which
options you want included in your system.

The RSX-llM/M-PLUS Executive Reference Manual
directives and Executive options.

the

RSX-llM

fully

Executive

describes

these

Answer Yes to the features you want included in your system •

* 1. Will DBMS-11 be used

.$DBM

For details on DBMS-11, refer to the DBMS-11 documentation.
This question appears only if the target processor memory is
greater than 96K, the system is mapped, and you are not generating
RSX-llS.
If you select DBMS-11 support, SYSGEN automatically includes
Executive support for:
Asynchronous System Traps (AST support);
Memory management directives;
and Send/receive by reference
directives. See Executive questions 16, 6, and 7 respectively.

* 2. FILES-11 ACP
If you do not select Files-11 ACP, none of the services described
in the IAS/RSX-11 I/O Operations Reference Manual are generated in
your system.
If DBMS-11 is requested (Executive Question 1)
not asked.

this

DEC-supplied software uses the Files-11 ACP;
that you select this option.

You specify the appropriate FllACP
SYSGEN Phase II.

application

for

your

question

recommended
during

If you are generating an RSX-118 system, this question is bypassed
and Files-11 ACP is not included in your system.

i~l?1S

* 3. RMS record locking and placement control

RMS is the DIGITAL Record Management System. RMS record locking
and
placement control
is a feature of the RSX-llM Record
Management System and is described in the RMS documentation.
If you selected Files-11 ACP (Executive Question 2) or if it is
included in your system by default,
this question is asked.
Otherwise, the question is bypassed and RMS-11 is not supported.

5-17

DETAILS OF SYSGEN PHASE I

* 4o Non-resident tasks (task loader)

0)(\

Non-resident task support allows tasks that are
resident in your system to be loaded from disk.

not

permanently

If you do not include support for the task loader, all tasks
be installed and fixed into the system image by VMR.

must

It is highly recommended that you select this option.
RSX-llS does not support
appear.

this

option;

the

question

does

not

* 5. Loadable task loader
The RSX-llM task loader reads tasks scheduled for execution from
disk.
Making the task loader loadable is an RSX-llM Executive
feature that reduces the amount of address space required for the
Executive (excluding pool), freeing space for additional Executive
dynamic storage.
If you answer No to this question, the loader is linked into the
Executive and requires up to 2400 bytes of Executive virtual
address space. By making the loader loadable (responding Yes to
this question), those 2400 bytes become available for use as
dynamic storage (pool space) or for other Executive features.
This option is not available on RSX-llS, on unmapped
if non-resident task support is not included.

systems,

NOTE
The loadable loader must be
VMR at the end of Phase II.

loaded

* 6. Memory management (PLAS) directives
Memory management (PLAS) directives provide functions that allow
tasks to dynamically modify mapping of their physical addresses in
memory. These directives also allow tasks to dynamically create
and delete common blocks.
The following lists the memory management directives:
ATTACH REGION
CREATE ADDRESS WINDOW
CREATE REGION
DETACH REG ION
ELIMINATE ADDRESS WINDOW
GET MAPPING CONTEXT
MAP ADDRESS WINDOW
RECEIVE BY REFERENCE
SEND BY REFERENCE
UNMAP ADDRESS WINDOW
Memory management directives are restricted
systems.
Therefore, the question is not
systems.

to use on mapped
asked for unmapped

If you selected DBMS-11 (Executive Question 1) memory management
directives are included by default and this question is not asked.

5-18

DETAILS OF SYSGEN PHASE I
If you select this option, SYSGEN automatically includes support
for address checking (option 9) and I/O rundown (option 10).
If you do not select memory management directives,
you cannot
include Executive support for send/receive by reference directives
(question 7).
The memory management
(or PLAS)
1000(10) words to the Executive.

directives

add

approximately

* 7. Send/Receive by reference directives
The SEND/RECEIVE by reference directives allow one task to send to
another task a reference to an area within a region. The receiver
task is given a specified access which allows it to map to or
delete the region.
If you selected DBMS support, SYSGEN automatically includes
Executive support for
the send/receive by reference directives;
this question is not asked.
If you did not include support for
directives, this question is not asked.
If you did not select DBMS-11, but
directives, this question is asked.

the

memory

management

included

memory

management

* 8. Get mapping context directive
This directive returns to the issuing task parameters describing
the
current
window-to-region
mapping
assignments.
These
parameters allow you to restore the mapping context using the
memory management CREATE ADDRESS WINDOW directive.
This question appears only if memory management directive
was included.

support

If you select this feature, Executive support for address checking
(option 9) and I/O rundown (option 10) are automatically included.

* 9. Address checking
This feature directs the Executive to perform boundary checks,
alignment checks, and modulus checks on addresses passed by users
in Executive directives.
Note that if you are generating a mapped system, address
is automatically included;
this question is not asked.

checking

running

This feature ensures RSX-llM system integrity by cleaning up
outstanding task-related I/O before allowing a task to exit.

all

Address checking is recommended
fully-debugged application system.

unless

you

are

* 10. I/O rundown

It is recommended that you select this feature;
I/O rundown is
recommended unless you are running a fully-debugged application
system.
This feature is automatically included if you are
generating a mapped system.
5-19

DETAILS OF SYSGEN PHASE I

* 11. Multi-user protection
This feature prevents tasks initiated at one terminal from
interfering with tasks initiated at other terminals. Multi-user
protection provides for public and private d~vice ownership and
login and logoff with password protection.
When you select this feature, SYSGEN
following terminal driver features:
•
•
•
e

automatically

includes

the

Read with special terminator
Breakthrough write
Read with no echo
CTRL/R support

Select multi-user protection support only if your system
or more of main memory.

has

Multi-user protection support is not
system;
the question is not asked.

RSX-llS

Multi-user protection increases
approximately 100(10) words.

the

available
si~e

the

Executive

32K

fv\_

* 12. ANSI Magtape ACP

This feature provides support for volume and file labels that
conform to the ANSI standard for industry-compatible tapes.
This
feature requires Executive AST support;
if you select ANSI
magtape ACP support, SYSGEN automatically includes AST support.
RSX-llS systems do not support ANSI magtapes;
asked.

the question is not

ANSI magtape ACP support increases the size of
approximately 40(10) words.

the

Executive

ovtP

* 13. On-line formatting (FMT) or on-line user-mode diagnostics
On-line formatting or on-line user-mode diagnostics enable the
Executive and device drivers to perform special I/O functions and
return additional device status information required by online
diagnostic tasks.
(For information on diagnostic tasks, see the
RSX-llM/M-PLUS User Mode Diagnostics Manual and the
RSX-11
Utilities Manual for online formatter (FMT) information.)
RSX-llS systems do not support online user mode
the FMT task;
the question does not appear.

diagnostics

nor

Lo)7

* 14. Loadable device drivers

This feature allows you to load and unload most device drivers
dynamically using MCR and VMR Load and Unload commands. Only the
industrial and process control device drivers
(UDC,
ICS/ICR,
IP11/IP300, and DRS/DSS) and the VT11/VS60 graphics driver are not
loadable.
When you select this option, SYSGEN generates loadable
drivers;
however, SYSGEN makes all data bases resident.
This question is always asked.

5-20

device

DETAILS OF SYSGEN PHASE I
The full duplex terminal driver requires loadable device driver
support.
Therefore,
if you wish to include the full duplex
terminal driver, you must include loadable driver support.

* 15. Should the default for all applicable drivers be loadable
•

If loadable device driver support is included, this question
specifies
that
all drivers
(except UDC,
ICS/ICR, DRS/DSS,
IP11/IP300, and VT11/VS60) are to be built as loadable by default
If you
(you can override the default in the peripheral se~tion).
respond No to this question, all drivers (except the full duplex
terminal driver, if selected) are built as resident.
The response to this question sets the default,
either
L
(loadable) or R (resident) for responses to peripherals questions.
You can override the default you set with the response to this
question in your responses to peripherals questions.
If loadable device driver support is not requested,
will be resident, and this question does not appear.

all

drivers

* 16. AST and cancel selective MARKTIMEs
This option allows the processing of Asynchronous System Traps and
permits you to cancel a single marktime request.
This feature is automatically included when you select any of
following:
•
•
e
e
•
•

the

ANSI magtape ACP support
Floating point processor
DBMS-11
LA driver (LPAll-K)
Console logging driver
K-series device support routines

If you exclude this option, the terminal
unsolicited input character ASTso

driver

cannot

support

If you want AST support, but do not need the ability to cancel a
specific marktime request, enter Yes.
You can then edit RSXMC.MAC
and remove cancel select1ve mark time support
(locate the line
C$$SMT=O and delete it).

"'
* 17. Task· termination
and device not ready messages (TKTN)
This feature directs RSX-llM to automatically generate DEVICE
READY and task termination messages.

NOT

You must select this option if you want Post Mortem Dump (PMD) and
Snapshot Dump (SNAP$) support.

* 18. Power fail recovery
•

This feature provides for automatic system recovery in the event
of power failure.
Device drivers and tasks that specify a power
fail AST are notified when power returns. The option is required
to support powerfail ASTs.

5-21

DETAILS OF SYSGEN PHASE I

* 19. Install, request, and remove on exit :t lttf.
This feature (the MCR Run command) reduces the number of .installed
tasks in memory, thereby optimizing the use of system memory
resources and minimizing use of pool. Refer to the description of
the Run command in the RSX-llM/M-PLUS MCR Operations Manual for
details of ~he functions provided by this feature.
This feature is not available for RSX-llS systems.

* 20. Large (20K) Executive
This feature allows you to generate an Executive larger than 16K
in order to increase the size of the Executive's virtual address
space, typically to provide more pool. This reduces to SK the
maximum size of privileged tasks.
If you are
bypassed.

generating

* 21. Logical device assignment

unmapped

system,

this

question

! LGD

This feature (the MCR ASN command) allows you to assign a logical
name to a physical, pseudo, or other logical device. Assignments
may be made on a per-terminal (local) or system-wide basis
(global).
This option comes to you as highly recommended.

* 22. Logging of device errors and timeouts $I>ro
This feature (Error Logging) causes disk and tape device errors to
be intercepted and status information describing the error to be
written to a disk file for analysis.
When you select this
feature,
checkpointing
and the SEND/RECEIVE directives are
automatically included in your system.
RSX-llS systems do not support the error logging subsystem;
question does not appear.

this

* 23. Logging of undefined interrupts
This feature directs the Executive to check for traps to undefined
interrupt vectors and to store information about these traps in a
disk file for analysis.
When you select this feature, checkpointing and the SEND/RECEIVE
directives are automatically included in your system.
RSX-llS systems do not support the error logging subsystem;
question is not asked.

this

* 24. Logging of memory parity errors
This feature directs the Executive to log cache and memory
error traps in a disk file for analysis.

parity

When you select this feature, SYSGEN automatically
non-resident
task
support,
checkpointing support,
send/receive directives.

includes
and the

5-22

...

DETAILS OF SYSGEN PHASE I
This question will only be asked if you
support.

specified

memory

parity

RSX-llS systems do not support the error logging subsystem;
question is not asked.

this

* 25. Do you intend to include a user-written driver !fUWD
User-written drivers can
Executive.

included

the

assembly

the

If you answer Yes, questions concerning the Executive routines
$GTWRD (GET WORD) and $PTWRD (PUTWORD) are asked. You will also
have the opportunity in SYSGEN Phase II, to add a user-written
driver to your Executive.

* 26. Include routine $GTWRD
This feature (the $GTWRD Executive routine) is used to obtain a
word from a user-defined buffer. Refer to the RSX-llM Guide To
Writing an I/O Driver for information on how this routine is used.
This question is not asked if you
user-written driver.

not

intend

include

* 27. Do you require routine $PTWRD
This feature (the $PTWRD Executive routine) is used to send a word
to a user-defined buffer. Refer to the RSX-llM Guide To Writing
an I/O Driver for information on how this routine is used.
This question is not asked if you
user-written driver.

not

intend

include

* 28. Disk writecheck
Writecheck support increases the data reliability of disks at the
cost of a degradation in disk throughput. If selected, writecheck
may be enabled/disabled dynamically on a per-drive basis via the
MCR Set command.
Writecheck is supported for all disks except the RXOl, RX02, and
the RLOl. Disks supported are: DB, DF, DK, DM, DP, DR, and DS.
If you specify writecheck support and issue an MCR Set /WCHK
command in a running system, the driver performs a read after each
write. If the data cannot be read or does not match the data
written, the data is rewritten and another read attempt is
performed.
RSX-llS does not support disk writecheck;
appear •

•

5-23

the question

does

not

DETAILS OF SYSGEN PHASE I

* 29. Executive Debugging Tool (XDT)
The Executive Debugging Tool (XDT) provides a subset of ODT-11
commands to be used in system state. If selected, XDT is included
in the Executive. This allow$ interactive debugging of Executive
modules, privileged tasks, I/O drivers, and interrupt service
routines.

•

This feature includes consistency check code in the dynamic memory
routines.

* 30. Rotating pattern in data lights
This feature causes the PDP-11 CPU lights to rotate
pronounced circular pattern when the processor is idle.

This feature functions only on the 11/45, 11/50, 11/55, and 11/70
PDP-11 processors.
This question appears only for the target
processors listed above.

* 31. Industrial network or DECnet
This optian allows for the inclusion of DECnet or industrial
network support.
Refer to DECnet documentation for details on
DECnet;
refer
to
Industrial
Products
documentation
(IPll/IP300/DPM50 Application Programmer's Manual) for details on
the industrial network.
When you select this option, SYSGEN automatically includes:
•

ACP support

•

AST and cancel selective marktime support

•

Logical device assignment support

•

Loadable device driver support

•

Address checking support

•

Get partition parameters directive support

•

Get task

•

Extend task directive support

pa~ameters

directive support
/

* 32. Queue manager and queued pr int spooler $PRN
The queue manager and queued print spooler provide user-controlled
spooling support for RSX-llM systems. Refer to Appendix D for a
description of the features of RSX-llM print spoolers.
If you select this option, the required support is built into the
Executive.
If you respond No, you will be asked in Phase II
whether or not you want to build the serial despooler.

This questi-0n is asked only for mapped systems.
.~l

5-24

DETAILS OF SYSGEN PHASE I
*33. Group global event flags
Group global event flags provide each group
(in
the
UIC
specification
[group,member]}
of system users with 32 (decimal}
additional event flags.
For more information on group global
event flags, refer to the RSX-llM/M-PLUS MCR Operations Manual •

•

* 34. Enter code for directives
Use this option to include system directives, as indicated by
associated letter in the table below.

the

Enter * to display table of directives.
Enter % to include all directives.
Enter
to terminate the question.
For descriptions of the directives listed
RSX-llM/M-PLUS Executive Reference Manual.
A- Get partition parms
c- Send/Receive
E- Extend task
G- Get sense switch

below

refer

the

B- Get task parameters
D- Alter priority
F- Connect to interrupt vector
H- Stop bit

If you do not select get partition parameters (option A}
and get
task parameters
(option B}, the MCR ASN, ATL, DEV, PAR, TAL, and
TAS commands will not execute correctly.
If you select DBMS-11 or DECnet support, SYSGEN automatically
includes
Stop Bit, Get Partition Parameters,
and Get Task
Parameters support.
Also, the extend task directive is included
by default.
If you select ANSI magtape support and error logging support for
device timeouts and parity errors, SYSGEN automatically includes
Send/Receive support.
If you select loadable driver support, Connect To Interrupt Vector
support is included.

If you select K-series
support is included.

devices,

Connect

Interrupt

Vector

If the target processor does not have a switch register, SYSGEN
does not allow the inclusion of the Get Sense Switch directive.

* 35. Number of pre-allocated QIO packets [0:15.:5.]
I/O throughput is enhanced by pre-allocating a number of I/O
packets from the dynamic storage region, leaving them available
for quick use by Queue I/O.
The Executive maintains a Last In First Out
(LIFO}
list of
preallocated I/O packets;
you specify the maximum size of this
list with your response to this question. When any I/O packet is
required,
the Executive removes one from this list.
If the list
is empty, the Executive allocates the packet from dynamic memory;
a
significantly slower operation.
When any I/O packet is
deallocated, the packet is linked into the list, provided that the
list is not full.

5-25

DETAILS OF SYSGEN PHASE I
Thus, in each I/O request, two fast LIFO operations replace the
slower general pool allocations and deallocations, saving several
hundred microseconds. Some I/O requests involving an ACP require
two I/O packets and, therefore benefit twice as much.
Each I/O packet you preallocate requires 18 words from pool.
To
determine the number of I/O packets to preallocate, consider the
normal fluctuation in the total number of I/O requests.
The
fluctuating total number is always smaller than the number of
outstanding I/O requests.
Enter a number in the range O.
packets to be pre-allocated.

to 15., indicating the

number

The default is 5.
Enter 0 to exclude pre-allocated QIO packets.

* 36. Size of data transfer vector in words

[5:33.:33.J~fJ-r\/

An additional speed improvement is achieved by optimizing data
transfers in the Executive module BLXIO. One improvement is the
use of a series of MOV instructions which is used to save time on
loop control. This is called the data transfer vector.
Enter a number in the range 5. to 33., to specify the number of
MOV instructions in the vector.
If you enter a value of 16, for
example, a 36-word data transfer enters the loop control three
times as opposed to 36 times if there were only one MOV
instruction in the vector.
The default is 33.
This question does not appear for unmapped systems.

* 37. Round-robin scheduling interval in ticks
When many competing memory-resident tasks have equal priority, the
Executive tends to give CPU time more frequently to tasks that
appear first in the Active Task List (ATL).
Entries in the ATL
with equal priority normally appear in the order in which the
tasks were installed.
To avoid this problem, RSX-llM provides the round-robin scheduling
option.
This Executive scheduling algorithm periodically rotates
(when the specified number of ticks elapses)
tasks of equal
priority within the Active Task List, ensuring that tasks of equal
priqrity share CPU time.
The overall effect is to evenly
distribute the use of CPU time, giving each task of equal priority
time at the head of the Active Task List.
Round-robin scheduling refers to the algorithm whereby each task
of a group of tasks is successively given preference when
allocating available processor time. The actual algorithm used in
RSX-llM is to locate the first task within each priority class
that is not blocked from executing, give it a slice of processor
time, and when it completes, move that task to the end of its
respective priority class.
Compute-bound tasks tend to actually
round-robin,
whereas I/O-bound tasks tend to remain at the front
of their respective priority class.

5-26

•

DETAILS OF SYSGEN PHASE I
Round··robin scheduling does not affect the normal competition for
CPU time of tasks with different priorities.
It also does not
affect tasks not in the range set by the response to SYSGEN Phase
I Executive questions 38 and 39.

•
•

Round-robin scheduling affect~ only those tasks in an ATL
memory} that are neither blocked nor in the wait£or state •

{in

Tasks that are checkpointed or in a partition wait queue
affected.

not

are

Round·-robin scheduling costs little in terms of Executive overhead
{time and size} •
If you do not want this option, enter

If you want this option, enter a number in the range
1000. SYSGEN then asks questions 38 and 39.

through

The default is 5.

* 38. Highest priority class for consideration [1.:249.:150.]

Round robin scheduling executes for a specified range of priority
classes.
A typical range is 1. to 150. Permissible range is 1.
to 249.
I
This entry is the highest priority class eligible for round
scheduling. Default is 150.

robin

This question appears
scheduling option.

robin

only

you

selected

the

* 39. Lowest priority class for consideration [l.:high.:l]
This is the
scheduling.

lowest

priority

class

Range is 1. to {highest priority class
question 38}.

round

-r

eligible

for

round

robin

entered

response

selected

the

round

Default is 1.
This question appears
scheduling option.

only

you

robin

* 40. Executive level disk swapping interval [0:5000.:low.:Vij; Qtt\

Disk swapping is an Executive feature that varies the priority of
memory resident tasks with the same priority so that those tasks
can share the use of memory resources. The feature swaps tasks to
disk based on the swapping algorithm.

•

The swapping algorithm creates an "effective" task priority using
the swapping interval
{the response to this question} and the
swapping priority {the response to question 41}.
The swapping
interval specifies a time parameter, in which the Executive scans
the partition list and modifies the effective priority of a
resident task.
The swapping priority is an absolute numeric value
that specifies the range through which a task varies its priority.
{The range is negative swapping priority through positive swapping
priority.}
5-27

DETAILS OF SYSGEN PHASE I
The Executive uses a byte in the task header to maintain the
swapping priority; symbol S$$WPR in RSXMC.MAC. The symbol S$$WPR
is equated to the swapping priority specified in question 41.
Each time a task is read into memory, the Executive initializes
the swapping priority in the task header to the value +S$$WPR (for
example, +5 if you specify 5 as the swapping priority in question
41).
Then, when the swapping interval expires, the Executive
decrements the swapping priority of each memory-resident task by
one until the task is checkpointed or until the swapping priority
reaches the minimum value -S$$WPR (for example, -5).

After decrementing the swapping priority of each task in the
partition, the Executive determines whether or not an eligible
task on disk can checkpoint a task in the partition.
The
Executive compares the running priority of the non-resident task
with the effective priority of the resident task (effective
priority is the sum of the running priority and the swapping
priority). Lf the non-resident task can fit in the resident
task's space and if, due to the decrementing of swapping priority,
the priority of the non-resident task is higher, the non-resident
task can checkpoint the resident task.

•

This procedure executes for tasks competing for each
main
partition (except DEVICE and COMMON partitions) and for the
highest priority, non-resident task assigned to each partition.
If you select this option, SYSGEN automatically
for checkpointing.

includes

support

The permissible range is O to 5000. The default is a value that
is equal to the round robin scheduling interval multiplied by 6.
If the round robin scheduling interval was 0 (you excluded
support), this default is 30.
To disable this option, enter 0.

* 41. Swapping priority (1:20.:5] 1
The swapping priority determines the range over which lower
priority tasks may checkpoint higher ones;
the larger the
swapping priority, the greater the range.
With a swapping
priority of "S", a task running at priority "P" will have an
effective priority range (for checkpointing) from "P+S" to "P-S"
as long as it resides in memory.
Enter a number in the range 1 to 20. It is recommended
enter the default swapping priority of 5.
This question is asked only if Executive level disk
requested.

that

you

swapping

was

* 42. Size of dynamic storage region in words (256.:16384.:1024.] f.DSA
RSX-llM uses the dynamic storage region (pool) to perform many
functions.
For example, the Executive uses this memory space to
process I/O or time-dependent scheduling requests.

5-28

l
,.

DETAILS OF SYSGEN PHASE I
Rather than allocate a fixed amount of memory for each function,
the RSX-llM Executive makes use of a dynamically allocated memory
space called the dynamic storage region
(DSR).
As demands for
space are made, the necessary memory is allocated from this region
using a first-fit algorithm. When allocated space is no longer
needed, it is released back to the pool of available memory.

•

Dynamic memory requirements for a
system
depend
on
the
configuration, application, and degree of system loading.
Enough
memory must be available to satisfy peak demands;
otherwise a
degradation in system performance will occur and the system could
hang with a DSR deadlock •

•

On the other hand, if too much memory is made available,
never used and is thus wasteful of system resources.

The maximum size of the dynamic storage region is limited by
physical memory in an unmapped system.
In a mapped system, the
total size of the Executive, resident drivers,
and the dynamic
storage region must not exceed 16K if you responded No to question
20 or not exceed 20K if you responded Yes to question 20.
NOTE
In a mapped system,
the automatic VMR
process attempts to allocate as much
pool as possible
(up to the maximum
Executive size).
If you do not edit the
command file (SYSVMR.CMD) that performs
this,
the response to this question is
not critical.
The following list specifies some RSX-llM functions that use
Use this list to calculate how much memory you
dynamic memory.
should allocate.
Tasks:
Each task installed in the system
words for a task control block.

requires

least

I/O Requests:
Each I/O request results in the allocation of an
18-word I/O packet, which is queued to the appropriate device
driver.
SEND DATA and SEND BY REFERENCE Message:
Each Send Data or Send
by Reference message sent to a task results in an 18-word
message packet being allocated to hold the requisite data.

Partitions
and
Subpartitions:
Each
main
partition
and
subpartition requires a partition control block of at least 14
words to describe its memory.
In addition,
for each active
task,
fixed task, and loaded driver in a system-controlled
partition, (whether the tasks are checkpointed or in memory) a
PCB is built and allocated in the dynamic storage region.

• '··"

5-29

DETAILS OF SYSGEN PHASE I
Open Files:
Each open file requires 18 words for a file control
block
and 18 words for a window block which contains
virtual-to-logical block mapping pointers.
The file system ACP
(FllACP)
may be built to store File
Control blocks in its own task image rather than in dynamic
storage region.
(See details of SYSGEN Phase I I.)
The more
space allocated at task build time, the less the demand will
be on the pool. However, if the allocated space becomes used
up, the overflow will use the dynamic storage region.
Mounted Volumes:
Each mounted volume requires 18 words for a
volume control· block, 18 words for the index file window
block, and 18 words for the index file control block.
In
addition,
three 18-word control blocks are required to hold
information pertaining to the last three directory files that
were accessed.
For systems that contain I/O optimization, MOU
will try to allocate a window block for
the index file of
sufficient size to contain all of the retrieval pointers.
This could require up to 208 words.
If the space is not
available,
MOU will default to 18 words. Space-saving hint:
The directory least-recently-used (LRU) table default is three
18-word file control blocks. The effect of this table is a
significant increase in the speed of directory operations.
If
this level of performance is not required, a volume may be
mounted using the /LRU keyword, thereby reducing the number of
FCBs used.

•
"·

Clock Queue Entries:
Each clock queue entry requires eight words.
These entities represent mark time, schedule, and periodic
scheduling requests.
AST-Related Processing:
Each powerfail,
receive,
and floating
point processor AST trap-enable for active tasks requires
eight words for an AST control block.
I/O Buffers: All terminal output is buffered in the terminal
driver before transferring information to the user buffer.
Each solicited and unsolicited input request requires a
42-word input buffer.
Card Images: Card images read from the CM/CRll are buffered by
the card reader driver before transferring the translated
information to the user buffer.
Binary output requires an
80-word buffer, whereas ASCII input requires a 4-word buffer.
LPSll and ARll Synchronous Functions:
Each LPSll/ARll synchronous
function requires 20 words for a sample control block.
Task Headers:
In a mapped system, the task header is copied into
a block of memory allocated from the dynamic storage region.
Approximately 64 words (dependent upon the number of LUNS and
window blocks)
are required for each task that is in memory
(i.e, in execution and not checkpointed, or inactive and
fixed).
Task

Linked to ICS/ICR-11 Interrupts:
Each task linked
to
ICS/ICR-11 interrupts requires 16 words of dynamic memory,
plus six words for each interrupt linkage.

Data Bases for Loadable Drivers: Data bases that are loaded into
a system with a loadable driver require space equal to the
size of the data base.

5-30

•

DETAILS OF SYSGEN PHASE I
Loadable Drivers:
Loaded drivers on a mapped
for interrupt linkage as follows:

require space

•

14 words per interrupt
non-error-logging drivers

entry

for

single-controller,

•

22 words per interrupt
non-error-logging drivers

entry

for

multi-controller,

•

14 words for the first
(or only)
interrupt entry for
error-logging drivers,
plus 6 words for each additional
interrupt entry for error-logging drivers

•
•

~ystem

Checkpointing: Systems with dynamic checkpoint space allocation
require 8 words to describe each checkpoint file and 8 words
for each task checkpointed to a checkpoint file.
Memory Management Directives: Systems supporting the
memory
management directives require 6 words per task (active or
fixed) for each region a task is attached to.
This includes
the task region and all static and dynamic commons.
Connect to Interrupt: Systems supporting the connect to interrupt
directive require 22 words for each Interrupt Transfer Block
(ITB)
used for each interrupt
vector
serviced
by
a
connect-to-interrupt directive.
Error Logging: Variable-length packets are allocated for each
logged error which has not been serviced by the error logger.
(See the RSX-llM/M-PLUS Error Logging Reference Manual.)
After you calculate the size of the DSR, add approximately
percent to cover possible pool fragmentation conditions.

12-18

Note that you can later extend this initial allocation
MCR Set /POOL command.

using

This entry must be in multiples of two
range of entries is 256. to 16384.

permissible

words.

The

the

The default is 1024.

* 43. Seconds between printer not ready messages [O: 255.: 30.) $

f f'J R

This question is asked if a line printer was specified in the
peripheral configuration and you included TKTN support (the TKTN
task prints the message).
Specify the number of seconds between printer not ready
An entry of 0 suppresses the messages altogether.
The default is 30. If you make
value of this entry is 15.

non-zero

entry,

the

messages.
minimum

* 44. Seconds between card reader not ready messages (0:255.:30.]

•

This question is asked if a card reader was specified in the
peripheral configuration and you included TKTN support (the TKTN
task prints the message).
Specify the number of seconds between card reader not ready
messages. An entry of zero suppresses the messages altogether.

5-31

DETAILS OF SYSGEN PHASE I
The default is 15.
If you enter a non-zero value, the minimum value of the
15.

* 45. System

crash
[0:177700:177564]

and

stack

dump

entry

device

CSR

~SD

If the system crashes and this option is included,
the
stack and registers are dumped to the selected device.

•

Executive

Enter the CSR address of the device. The normal device is the
console terminal, which has a CSR address of 177564. This is the
default device.
Enter O to suppress this option.
If you enter a non-zero value, it must be in the range
177700.

* 46. Checkpointing:

160000

A- Yes B- With system checkpoint file

Checkpointing allows the Executive to displace tasks
partition to yield memory to tasks of higher priority.

from

The goal of checkpointing is to avoid preempting the execution of
lower-priority tasks unless a higher-priority task can make use of
the memory resources allocated to the lower-priority task.
This
optimizes the use of processor memory while maintaining a priority
scheduling algorithm.
In some cases,
an activated task cannot execute because
partition in which the task must execute is occupied.

the

If the partition is occupied by a task (TASKA, for example)
that
is both checkpointable and has a priority lower than the task that
is waiting (TASKB, for example), the Executive may move the task
with the lower priority (TASKA) to disk, thus making room for the
higher priority task (TASKB) waiting on disk.
When the higher priority task (TASKB) is stopped or allows its
priority to be lowered, the lower priority task (TASKA) on disk
may be moved back into memory to continue execution.
This task (TASKA) continues execution from the point at
was interrupted.

which

RSX-llM supports checkpointing in both user-controlled
and system-controlled partitions.

partitions

Enter A if you want checkpointing.
(SYSGEN automatically includes
checkpointing if you selected Executive level disk swapping.)
Enter B if you want checkpointing with a system checkpoint file.
Selection of this
(B) option allows checkpointing into a system
checkpoint file rather than requiring space in each checkpointable
task image.
Enter carriage return to exclude this feature.

5-32

~·

•

DETAILS OF SYSGEN PHASE I
If you select checkpointing with a system checkpoint file (B), you
must allocate space for the file when you start up the system, for
example,
in STARTUP.CMD.
Refer to the
RSX-llM/M-PLUS
MCR
Operations Manual for more information.
Note that if you exclude checkpointing support, the terminal
driver cannot support task checkpointing during terminal input.
This option does not apply to RSX-118 systems;
omitted.

* 47. System-controlled partitions:

the

question

A-Yes B-Yes With auto

compaction

(SHF)
This option allows as many tasks as will fit into a partition to
be simultaneously resident. The allocation of partition memory is
automatic and is carried out by the RSX-llM Executive dynamically.
Enter A if you want system-controlled partitions.
Enter B if you want system-controlled
compaction (the Shuffler task).

partitions

with

automatic

When the Executive determines that there is insufficient memory to
load a waiting task into a system-controlled partition, the
shuffler executes
(following an allocation failure during an
attempt to allocate memory from a system-controlled partition).
The shuffler scans Partition Control Blocks searching for a
system-controlled partition which has at least one eligible task
waiting for memory. When such a partition is found, the shuffler
attempts
to compact the memory partition and thus form a
contiguous space large enough to contain the waiting task.
The shuffler algorithm consists
system-controlled partition.

two

passes

through

each

In the first pass, the shuffler unconditionally checkpoints all
stopped, checkpointable tasks.
(This includes all tasks stopped
for terminal input if you select option 5 in the terminal driver
section of Phase 1.) The shuffler then starts at the beginning of
the system-controlled partition and tries to move
(shuffle)
all
tasks that are positioned above a gap of free space down to the
base of the free space. When the shuffler completes its first
pass,
all stopped, checkpointable tasks are checkpointed and all
free space in the system-controlled partition has been merged into
one hole at the top of the par ti ti on.
(However, there may be
additional holes below these tasks that cannot be shuffled.)

•

If the shuffler completes its first pass and some eligible tasks
are still waiting for space in the partition,
the shuffler
executes its second pass.
In the second pass,
the shuffler
creates an ascending, priority-ordered list of the tasks in the
partition.
It then uses this list to determine if the size of the
waiting task is less than the sum of the free space and the size
of one or more of the lower priority, checkpointable tasks.
If,
and only if, the size of the waiting task is less than this sum,
the lower priority tasks are checkpointed.
Unmapped systems do not support system-controlled partitions.

5-33

DETAILS OF SYSGEN PHASE I
If you select DBMS-11, this feature (A} is included by default.
However, the shuffler (B} is not;
if you want the shuffler, you
must select it.
This option does not apply to RSX-llS systems;
question.

* 48. Dump Analysis:

SYSGEN

omits

the

c /~ ~

A- PANIC B- Crash (CDA)

If the dump routine option is omitted and a system failure occurs,
it may not be possible for the user to capture vital data on the
state of the system at failure time. The RSX-llM Guide to Writing
an I/O Driver describes the PANIC dump routine. The CDA crash
dump routine is normally used in debugging new drivers or
privileged tasks after the drivers or tasks crash the system.
It
provides a means of generating a formatted dump of memory on a
line printer or a terminal. For more detailed information, refer
to the RSX-llM/M-PLUS Crash Dump Analyzer Reference Manual.
Enter A if you want the panic dump routine
Enter B if you want crash dump analysis (CDA)

supp~rt

If you select B, SYSGEN asks Executive Questions 49, SO,
52.

51,

and

* 49. Output notification device CSR [160000:177700:177564]
This question appears if you selected B (crash dump support}.
Enter the CSR of the device to which the crash notification is to
be output. Typically, this will be the console device (177564}.

* 50. Memory dump device

(ddu:}

[3:4]

This question appears only if crash dump
was selected.

analysis

(CDA)

support

Enter the mnemonic and unit number of the device on which you want
a memory dump. Note that the memory dump device must be part of
the target hardware configuration, but not necessarily generated
into the target system. Supported devices are OT, DK, MT, MS, MM,
DB, DM, DL, DD, and DR.
Avoid, if possible, using your system device
device.

5-34

the

crash

dump

DETAILS OF SYSGEN PHASE I

* 51. CSR address of dump device [160000:177700:default]
Enter the CSR address of the dump device. The default depends
the type of device you specify as the crash dump device:

•

Device
'rype

Default
CSR

DT
DK
MT
MM
DB
DL
DM
DR
DD
MS

177342
177404
172522
172440
176700
174400
177440
176700
175600
172522

* 52. CSR address of PANIC dump device (160000:17700:177564]
If panic dump was selected, enter the CSR address of the indicated
panic dump device.
Normally,
this is the CSR address of the
console device, which is also the default.
This device must
printer-compatible
at a time.

be
a
device.

paper
tape,
terminal,
or
line
The device must receive a single byte

This question is asked only when you request
(option A in Executive Question 48).

5.5

panic

dump

support

TERMINAL DRIVER QUESTIONS

This section allows you to choose which of the RSX-llM terminal
drivers you want as part of your system. The section also allows you
to specify terminal driver options.
Terminal driver options are described fully in the RSX-llM/M-PLUS
Drivers Reference Manual.

I/O

Answer Yes to the options you want included in your system.

* 1. Terminal driver desired (A/B/C/D, * prints table)--m
This question allows you to select the terminal driver you want to
include in your system.
RSX-llM systems use one of two terminal
drivers:
•

Half duplex (baseline, no
options;
and tailored,
default)

•

Full duplex

options;
tailorable,
user-oriented options

you select
included by

Enter A to select the half duplex terminal driver that you tailor
(specify specific options) to meet the needs of your system.

5-35

DETAILS OF SYSGEN PHASE I
Enter B to select the user-oriented half duplex terminal
The user-oriented driver includes the following options:
•

Automatic carriage return/line feed

driver.

(option 4)

Note
checkpointable during terminal input
(option 5).
• Task
that
if
you
did
not
include Executive support for
checkpointing, this option is excluded
user-oriented terminal driver.
•

when

you

select

the

Unsolicited input character AST (option 6).
Note that this
option requires Executive AST support. Therefore, if you did
not include Executive AST support,
this option is excluded
when you select the user-oriented terminal driver.

•

Write with CTRL/O cancellation (option 7)

•

Breakthrough write (option 8)

•

CTRL/R retype (option 9)

•

Get multiple characteristics (option 11)

•

Get terminal driver options (option 13)

•

Transparent read/write (option 15)

•

Settable case conversion for input (option 16)

•

Read after prompt (option 17)

•

Read with no echo (option 18)

•

Read with special terminator

•

CRT rubout support (option 20)

•

Terminal-host synchronization (option 21)

•

Variable length terminal input buffering (option 23)

(option 19)

If you want more or fewer options with the half duplex terminal
driver,
you should select the tailorable half duplex terminal
driver (enter A).
Enter c to select the full duplex terminal driver.
This driver
requires a mapped system and loadable driver support. The full
duplex driver includes the following options:
•

Passes form feeds directly to the terminal

•

Automatic carriage return/line feed

•

Task checkpointable during terminal input
(option 5).
Note
that this option requires Executive support for checkpointing.
Therefore, if you did not include checkpointing support,
this
option is excluded when you select the full duplex terminal
driver.

•

5-36

•

(option 3)

(option 4)

DETAILS OF SYSGEN PHASE I
•

Write with CTRL/O cancellation (option 7)

•

Hold screen mode (option 14)

•

Transparent read/write (option 15)

•

Settable case conversion for input (option 16)

•

Read with no echo (option 18)

•

Read with special terminator (option 19)

•

Terminal-host synchronization (option 21)

•

User terminal input buffering (option 22)

•

Variable length terminal input buffering (option 23)

•

LA30P support (option 24)

•

Hardware unrecoverable input error support (option 25)

•

Device independent cursor positioning (option 26)

Enter D to select the baseline terminal driver.
Note that this
driver and a multiuser protection system are mutually exclusive.
The baseline driver is a minimum half duplex terminal driver with
no SYSGEN options.

* 2. Unsolicited input timeout value in seconds (!'fl

This option is available with the full duplex terminal driver
only;
the question does not appear if you responded A, B, or D to
question 1.
The full duplex driver discards unsolicited input upon the
expiration of the timeout value that you specify. Valid timeout
range is 0 to 2540 seconds.
Enter 0 to inhibit the full
input timeout feature.

duplex

terminal

driver

unsolicited

Enter carriage return (the default timeout· value is 120 seconds)
or specify the number of seconds (in the range 1 to 2540) to wait
to timeout on unsolicited terminal input.

* 3. Pass form feeds directly to the terminal
This question appears only if you responded A or B to question 1
(selected the tailorable or pre-tailored half duplex terminal
driver).
The half duplex driver normally converts a form feed into
feeds.
Enter Yes to suppress this conversion.

5-37

line

DETAILS OF SYSGEN PHASE I
NOTE
If your system includes an LA120 or an
LA180S terminal, you must respond Yes to
this question and include the option.
This option
driver.

adds

approximately

24(10)

words

the

terminal

* 4. Automatic carriage return/line feed
This question appears only if you responded A to question l
(selected the tailorable half duplex terminal driver);
the
user-oriented driver and the full duplex driver include the option
by default.
If you respond Yes to this option (or if the option is included by
default), the terminal driver generates a carriage return and line
feed when the terminal buffer is filled on output or echo.
(You
can examine or alter terminal buffer size with the MCR Set /BUF
command.) This option adds approximately 70(10)
words to the
terminal driver.

* S. Task checkpointable during terminal input
This question is omitted if you responded with C to question l;
the full duplex driver includes the option automatically. Also,
since a response of B to question l selects a pre-tailored haLf
duplex driver, this question does not appear.
The question appears only if your response to question l was A and
you included Executive support for checkpointing.
If you select this option, checkpointable tasks can be displaced
from memory during terminal input by another task. This option
adds approximately 110(10) words to the terminal driver.
NOTE
This option can only be included in
systems that contain Executive support
for checkpointable tasks.

* 6. Unsolicited input character AST
This question appears only if you responded A to question l
and
included
Executive
support
for ASTs;
when possible,
the
user-oriented and full duplex drivers include the option by
default.
If you select this option, a task that attaches to a terminal can
specify an AST entry p~int upon receiving unsolicited input from a
terminal (for example, CTRL/C gains the task's attention rather
than MCR).
This option adds approximately 160(10) words to the
full duplex terminal driver and approximately 70(10) words to the
half duplex terminal driver.

5-38

DETAILS OF SYSGEN PHASE I
NOTE
This option
support.

requires

Executive

AST

* 7. Write with CTRL/O cancellation
This question appears only if you responded A to question 1.
If you select this option, a task that issues a write request with
CTRL/O cancellation can print to the terminal when the target
terminal has suppressed output with CTRL/O.
This option adds
approximately 16(10) words to the terminal driver.

* 8. Breakthrough write
This question appears if you responded A or C to question 1.
If
you selected multiuser protection support, SYSGEN automatically
includes this option.
If you select this option, a privileged task that issues a
breakthrough write request can print to a terminal regardless of
current or outstanding
I/O
activity.
This
option
adds
approximately 96(10) words to the full duplex terminal driver and
approximately 245(10) words to the half duplex terminal driver.
NOTE
When you select this option, SYSGEN
automatically includes terminal driver
support for
the CTRL/R retype option
(option 9). Together, these two options
add approximately 160(10) words to the
full
duplex
terminal
driver
and
approximately 275(10) words to the half
duplex terminal driver.

* 9. CTRL/R retype

.._.,,.

This question appears if you responded A or C to question
did not select the breakthrough write option (option 8) •

and

If you select this option, the terminal driver sends a carriage
return/line feed
followed by the contents of the input buffer
whenever you type CTRL/R at the terminal.
This option adds
approximately 64(10) words to the full duplex terminal driver and
approximately 32(10) words to the half duplex terminal driver.
r

* 10. Escape sequence handling
This question appears if you responded A or C to question 1.

•

If you select this option,
the terminal driver recognizes and
treats escape sequences as line terminators for all solicited
input
except
read-pass-all
or
read-with-special-terminator
requests.
This option adds approximately 128(10) words to the
full duplex terminal driver and approximately 160(10) words to the
half duplex terminal driver.

5-39

DETAILS OF SYSGEN PHASE I

* 11. Get multiple characteristics

MLC-

This question appears if you responded A or C to question 1.
If you select this option, a task can determine
physical
characteristics
(for example, CRT, VT52, slaved, or VTlOO) of
individual terminals. The task RMDEMO makes use of this option,
for example.
This option adds approximately 96(10) words to the
full duplex terminal driver and approximately 110(10) words to the
half duplex terminal driver.

* 12. Set multiple characteristics

This question appears if you responded A or C to question 1.
If you select this option, a task can set or reset physical
characteristics
(for example, CRT, VT52, slaved, or VTlOO) of its
TI:
terminal. A privileged task can use this option to set
physical characteristics of any terminal
in the system. This
option adds approximately 256(10) words to the terminal driver.

* 13. Get terminal driver options
This question appears if you responded A or C to question 1.
If you seiect this option, a
task can determine which of the
terminal driver options were selected during system generation.
This option adds approximately 32(10) words to the full duplex
terminal driver and approximately 64(10) words to the half duplex
terminal driver.

* 14. Hold screen mode
This question appears only if you responded A to question 1.
If you select this option and your terminal(s)
include special
hardware,
the terminals can break stream output into pages that
fit on the screen.
(Note that an unsolicited CTRL/C disables hold
screen mode.)
NOTE
When you select this option, SYSGEN
automatically includes terminal driver
support for the transparent read/write
option (option 15).
This option
driver.

adds

approximately

92(10)

words

the

terminal

* 15. Transparent read/write
This question appears only if you responded A to question
did not include the hold screen option (option 14).

and

The terminal driver normally filters terminal input on both input
and output.
This permits the recognition of control characters
that have special meaning (for example, escape)
or require fill

5-40

DETAILS OF SYSGEN PHASE I
characters
(for example, carriage return).
If you select this
option, the terminal driver provides support for I/O functions
(IO.RAL and IO.WAL)
that bypass character filtering and permits
output of to 32K bytes. This option adds approximately 48(10)
words to the terminal driver.

* 16. Settable case conversion for input
This question appears only if you responded A to question 1.
The terminal driver normally accepts and echoes characters as
received.
If you select this option, you can selectively enable
(using the MCR Set /LOWER command)
so
that
the
driver
automatically converts lower case input to upper case. This
option also allows the terminal driver to recognize the brace
character
(175) and the tilde c:haracter (176) as ASCII characters
rather than a form of escape when the terminal is set to lower
case. This option adds approximately 30(10) words to the terminal
driver.

* 17. Read after prompt
This question appears if you responded A or C to question 1.
If you select this option, a read after prompt request acts like a
write to the terminal followed by a read. This reduces the
overhead of one I/O request and eliminates context switching.
Also, this option removes the execution window, provided the
terminal is not attached, by which one task can prompt and another
task initiate terminal I/O before the first task (the prompting
task) had time to issue its read request.
This option adds
approximately 128(10) words to the full duplex terminal driver and
approximately 185(10) words to the half duplex terminal driver.

* 18. Read with no echo
This question appears only if you responded A to question 1 and
did
not include multi-user protection support.
(Multi-user
protection support automatically includes this terminal driver
option.)
If you select this option, you can issue the read functions
IO.RLB,
IO.RVS, and IO.RPR and specify that the driver not echo
terminal input. This option adds approximately 48(10)
words to
the terminal driver.

* 19. Read with special terminator
•

This question appears only if you responded A to question 1 and
did
not include multi-user protection support.
(Multi-user
protection support automatically includes this terminal driver
option.)
The line terminators for a normal read are carriage return or
escape.
If you select this option, any character less than 40
octal or greater than 174 octal can terminate a read with special
terminator
request.
However,
escape
sequences cannot be
recognized in this mode. Also, note that if the terminal
is set
to lower case, only 177 octal and characters less than 40 octal
can act as terminators. This option adds approximately 45(10)
words to the terminal driver.
5-41

DETAILS OF SYSGEN PHASE I

* 20. CRT rubout support
This question appears if you responded A or C to question 1.
If you select this option, the terminal driver echoes rubouts or
deletes
on
a
CRT
terminal
as backspace-space-backspace;
effectively, this option erases the character from the CRT screen
when you type rubout or delete.
This option adds approximately
64(10) words to the terminal driver.

* 21. Terminal-host synchronization
This question appears if you responded A to question 1.
If you select this option, you can start and stop terminal output
by typing CTRL/S (to stop) and CTRL/Q (to start). This option is
useful for high speed display terminals.
NOTE
If your system includes a VT50 terminal
with the copier option, you must respond
Yes to this question and
include the
option.
This option
driver.

adds

approximately

84(10)

words

the

terminal

* 22. User terminal input buffering
This question appears only if you responded A to question 1.
The terminal driver normally receives characters and stores the
characters in the Executive address space until receiving a line
terminator.
Upon receiving a line terminator, the driver copies
the contents of the buffer into the requesting task's input
buffer.
If you select this option, the driver, provided that the
task
is not checkpointable, places the input characters directly
into the task buffer as the characters are received. This option
adds approximately 12(10) words to the terminal driver.

* 23. Variable length terminal input buffering

"""'·

This question appears only if you responded A to question 1.
Normally, terminal driver input buffers are 80 bytes long, which
implicitly limits the maximum size of a terminal input request as
well as the size of the minimum buffer allocation from dynamic
memory.
If you select this option, the terminal allocates buffers
large enough to satisfy the read request. The largest buffer can
be 255 bytes long.
This option adds approximately 24(10) words to
the terminal driver.
....

5-42

DETAILS OF SYSGEN PHASE I

* 24. LA30P support
This question appears only if you responded A to question 1.
The LA30P DECwriter connects to the processor via a single
buffered interface.
If you do not select this option, the second
of two rapidly typed characters may be discarded by the terminal
driver.
NOTE
Choose this option only if your system
includes
an
LA30P
terminal;
the
terminal driver properly supports all
other combinations of DEC terminals and
interfaces.
This option
driver.

adds

approximately

48(10)

words

* 25. Hardware unrecoverable input error notification

the

terminal

ff~ _ie:

This question appears only if you responded C to question 1.
If you select this option, the full duplex terminal driver detects
and flags framing errors, character parity errors,
and data
overruns and then passes the input character(s) to the requesting
task with notification (including type) of an input error.
If you
do not select this option,
the driver discards hard receive
errors.
This option adds approximately 32(10) words to the
terminal driver.

* 26. Device independent cursor positioning
This question appears only if you responded C to question 1.
If you select this option,
the full duplex terminal driver
supports terminal
independent cursor positioning commands. When
you specify a cursor positioning character, the driver outputs a
cursor positioning character string before it outputs the buffer.
This option adds approximately 192(10) words to the terminal
driver.

5.6

PERIPHERAL QUESTIONS

This section of questions describe the peripheral devices included in
your target configuration. The questions define unique hardware and
software information that RSX-llM uses to communicate with peripheral
devices.
SYSGEN generates questions only for those devices you
specified in response to target configuration question 16.

During this section, you enter device-dependent parameters which
define addressing information as well as special attributes for the
peripheral devices.
SYSGEN displays a prompt line that describes the
required parameters and then a specific device question, which
includes any default values for the parameters.

··~·

5-43

DETAILS OF SYSGEN PHASE I
If you selected loadable driver support, the general form of a
prompt is:

SYSGEN

Enter [L/R,] parameterl, parameter2, ••• parametern for:
where:
L/R

is an optional parameter that specifies whether the
driver is loadable
(L)
or resident. Note that you
specified the default value for this parameter in your
response to Executive question 15. If your response to
question 15 was No, all drivers are resident unless you
override the default by specifying L.
Likewise, if
your response to question 15 was Yes, all drivers are
loadable unless you override the default by spacifying
R.
The process control drivers (UDC,
ICS/ICR, IP11/IP300
and DRS/DSS drivers) and the VT11/VS60 graphics driver
are not loadable;
this parameter does not appear for
these drivers since they are always resident.
The full duplex terminal driver is always loadable;
this parameter does not appear for the full duplex
terminal driver.
If you override the default (specify an Lor an R), you
must terminate this parameter with a comma (,), even if
it is the only parameter on the line.

parameter is a device dependent parameter (parameters

through

n) •

If you did not select loadable driver support, the general form
SYSGEN prompt is:
Enter

parameterl~

parameter2, ••• parametern for:

where parameters 1, 2, through n are device dependent parameters.
In the SYSGEN prompts,
parameters enclosed in brackets
([])
are
permitted only in the response for the first controller. Parameters
enclosed in parenthesis (()) are required only if the indicated option
is present in the target system.
Some devices require common parameters.
To display the specific
device question, SYSGEN groups the devices that require common
parameters together and then shares the respective SYSGEN prompt line.
Table 5-1 lists all the SYSGEN prompt lines and the devices that use
each.
The device specific questions display default values
for
the
parameters listed in the SYSGEN prompt line. When the question does
not display a parameter, you must enter a value for that parameter. A
comma
(,)
is the parameter delimiter. Note that blanks or tabs are
not permitted between parameters.
When you specify a required parameter or override the default value,
SYSGEN applies a minimum and maximum range (the acceptable range) for
each parameter.
If the value you enter is not within the acceptable
range, SYSGEN issues an error message that identifies the parameter by
number, according to its position in the prompt line.
Note that if
your system includes loadable driver support,
the optional L/R
parameter is not included in the parameter count.
For example, if you

5-44

DETAILS o:F SYSGEN PHASE I

enter 300 as the CSR address for a CRll controller (SYSGEN prompt 1),
SYSGEN displays:
SGN -- Parameter (#2) "300" out of range 160000 to 177700

RETRY

and then repeats the question.
The number in parenthesis is the
parameter count (excluding L/R if applicable) and the value in quotes
is the invalid parameter.
CAUTION
When you enter a numeric response, do
not
include
a
period
(to specify
decimal) or a pound sign
(to specify
octal).
This will cause an error;
SYS GEN
attempts
to
validate
your
response and does not permit explicit
decimal or octal entries.
values
within
the
Enter
numeric
acceptable range. SYSGEN interprets the
response to be octal or decimal as
required.
Refer to the detailed description if you
are unsure of the base for a specific
numeric response.
Table 5-1
SYSGEN Prompt Lines
Enter [L/R,] vector, CSR for:
Devices that use this prompt are (group l
devices):
CRll card
reader
(CR:),
TAll cassette (CT:), RF disks (OF:), TS04 magtape
(MS:), PCll paper tape punch (PP:), PCll/PRll paper tape reader
(PR:),
UDCll universal digital controller (UD:), DAll parallel
line interface (XB:)
Enter [L/R,] vector, CSR, number of drives, unit number of first drive,
[O=offset recovery support/NO=no support] for:
Devices that use this prompt are (group 2
disk packs (DB:), RM02/03 disks (DR:)

devices):

RP04/05/06

Enter [L/R,] vector, CSR, number of drives for:
Devices that use this prompt are (group 3 devices):
TU58 DECtape
II
(DD:), RLOl cartridge disks (DL:), RP02/03 disks (DP:), TCll
DECtape (OT:), RXOl floppy disk (DX:), RX02 floppy disk
(DY:),
TU45/TU16/TE16/TU77 magtapes (MM:), TS03/TU10/TE10 magtapes (MT:)
(continued on next page)

5-45

DETAILS OF SYSGEN PHASE I
Table 5-1 (Cont.)
SYSGEN Prompt Lines
Enter [L/R,] vector, CSR, F=full duplex/H=half duplex,
E=error detec.
unit/NO=no, C=char. detec.
number of sync characters in leader for:
Devices that use this prompt are
synchronous line interface (XQ:)

(group

unit/NO=no,

devices):

DQll

Enter [L/R,] vector, CSR, number of drives, unit number of first drive for:
Devices that use this prompt
disks (DS:)

are

(group

devices):

RS03/04

Enter [L/R,] vector, CSR, highest unit number <O to 7> for:
Devices that use this
cartridge disks (DK:)

prompt

are

(group

devices):

RK05

Enter vector, CSR, VT11/VS60, number of CRT monitors for:
Devices that use this prompt are (group 7
graphics display;processor and scope (GR:)

devices):

VT11/VS60

Enter [L/R,] CSR, number of A/D channels for:
Devices that use this prompt are
analog-to-digital converter (AD:)

(group

devices):

ADOl

devices):

AFCll

Enter [L/R,] vectot, CSR, number of A/D channels for:
Devices that use this prompt are
analog-to-digital converter (AF:)

(group

Enter [L/R,] clock vector, CSR, polarity mask, D=D/A channel/NO=no,
maximum number of samples/second, DRK=DRll-K/NO=no,
(,DRll-K CSR) for:
Devices that use this prompt are
laboratory peripheral system (AR:)

(group

devices):

ARll

Enter [L/R,] clock vector, CSR, #A/D channels~ G=gain ranging option /NO=no,
polarity mask, bandwith filter channel select delay,
number of D/A channels, D=digital I/O option/NO=no,
maximum number of samples/second for:
Devices that use this prompt are
laboratory peripheral system (LS:)

(group

devices):

LPSll

(continued on next page)

5-46

DETAILS OF SYSGEN PHASE I
Table 5-1 (Cont.}
SYSGEN Prompt Lines
Enter [L/R,] vector, CSR (, number of UMRs} for:
Devices that use this prompt are
(group
laboratory peripheral accelerator (LA:}

devices}:

LPAll-K

Ent er [L/R,] vector, CSR, #drives, O=offset recovery/NO=no offset rec.
1

Devices that use this prompt are
cartridge disks (OM:)

(group

devices}:

for:

RK06/07

Enter [L/R,] vector, CSR, F=full duplex/H=half duplex
number of characters in sync leader for:
Devices that use this prompt are
(group 14 devices}:
DLll-E
asynchronous
line
interface
(XL:} , DPll synchronous line
interface (XP:}, DUll synchronous line interface
(XU:}, DUPll
synchronous line interface (XW:)
Enter [L/R,] vector, CSR, F=full duplex/H=half duplex/P=primary HDX for:
Devices that use this prompt
interprocessor link (XM:}

are

(group

devices}:

DMC

Enter [L/R,] vector, CSR, printer type
(, [KMC timeout count <O=no KMC>, KMC vector, KMC CSR]) for:
Devices that use this
prompt
are
LA180/LS11/LP11/LV11 line printers (LP:)

(group

devices}:

Enter number of modules, module number of first for:
Devices that use this prompt are (group 17 devices):
UIX:
ADUOl
analog input module,
UDC analog output module, UDC bi-stable
output module, UDC digital interrupt module,
UDC digital sense
module, UDC I/O counter module, UDC single-shot output module
(all UD:}
Enter [L/R,] terminal number to redirect to (TTn:} for:
Devices that use this prompt are
(group 18 devices}:
Console
output device (pseudo device CO:) with console logging enabled
Enter [L/R,] num.

DLll's <ZL>, num.

DHll's, num.

DZll's, num.

Devices that use this prompt are (group 19 devices}:
terminal driver, baseline terminal driver

DJll's for

Half duplex

(continued on next page)

5-47

DETAILS OF SYSGEN PHASE I
Table 5-1 (Cont.)
SYSGEN Prompt Lines
Enter num.

DLll's <ZL>, num.

DHll's, num.

DZll's num.

Devices that use this prompt are (group 20 devices):
terminal driver

DJll's for:
Full duplex

Enter vector, CSR for:
Devices that use this prompt are
asynchronous line interface (TT:).
as ZL.

(group 21 devices):
DLll
SYSGEN refers to this device

Enter vector, CSR, highest line number <O to 15>
(, answer speed, DMll-BB vector, DMll-BB CSR) for:
Devices that use this prompt are
(group 22 devices):
DHll
terminal interface (TT:). SYSGEN refers to this device as DH.
Enter vector, CSR, highest line number <O to 15> for:
Devices that use this prompt are
(group 23 devices):
DJll
terminal interface (TT:). SYSGEN refers to this device as DJ.
Enter vector, CSR, highest line number <O to 7> [, answer speed] for:
Devices that use this prompt are
(group 24 devices):
DZll
terminal interface (TT:). SYSGEN refers to this device as DZ.
The following is a detailed description of all the possible peripheral
questions.
Enter [L/R,] vector, CSR for:
1.

CR controller 0 [D:230,177160]
Enter the interrupt vector address (the default value is 230}
and the CSR address
(the default value is 177160} for the
first CRll card reader controller.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent CRll controllers do not default the vector and CSR
assignments;
you must enter a value within the acceptable
range.

CT controller 0 [D:260,177500]
Enter the interrupt vector address (the default value is 230)
and the CSR address
(the default value is 177160) for the
first TAll cassette controller.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.

5-48

DETAILS OF SYSGEN PHASE I
Subsequent TAll controllers do not default the vector and CSR
assignments.;
you must enter a value within the acceptable
range.
1.

DF controller 0 [D : 2 0 4 , 177 4 6 O]
Enter the interrupt vector address {the default value is 204)
and the CSR address
{the default value is 177260) for the
first RFll controller.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent RFll controllers do not default the vector and CSR
assignments;
you must enter a value within the acceptable
range.

MS controller 0 [0:224,172522]
Enter the interrupt vector address {the default value is 224)
and the CSR address
{the default value is 172522) for the
first TSll controller.

If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR.
Subsequent TSll controllers do not default the vector and CSR
assignments;
you must enter a value within the acceptable
range.

"-''

PP controller 0 [D: 74, 177554]
Enter the interrupt vector address (the default value is 74)
and the CSR address
{the default value is 177554) for the
first PCll controller.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent Pell controllers do not default the vector and CSR
assignments;
you must enter a value within the acceptable
range.

PR controller 0 [0:70,177550]
Enter the interrupt vector address (the default value is 70)
and the CSR address
(the default value is 177550) for the
first PCll/PRll controller.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent PCll/PRll controllers do not default
CSR
assignments;
you must enter a value
acceptable range.

5-49

vector
within

and
the

DETAILS OF SYSGEN PHASE I
1.

UD controller 0 [0:234,171776]
Enter the interrupt vector address (the default value is 234)
and the CSR address
(the default value is 171776) for the
UDCll controller.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
After you specify the interrupt vector address and the CSR
address for the UDCll, SYSGEN immediately prompts for UDCll
module information using SYSGEN prompt line 17. For clarity,
this section lists the prompt lines in numeric order, not in
logical sequence.
If you ware performing a SYSGEN and
included a UDCll controller, the questions for UDCll would
follow the vector and CSR assignments.

XB controller O [0:124,172414]
Enter the interrupt vector address (the default value is 124)
and the CSR address
(the default value is 172414) for the
first DAll-B interface.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent DAll-B interfaces do not default the
CSR
assignments;
you must enter a value
acceptable range.

vector
within

and
the

Enter IL/R,] vector, CSR, number of drives, unit number of first drive,
[O=offset recovery support/NO=no support] for:
2.

DB controller 0 [254,176700,,0,0]
Enter the interrupt vector address (the default is 254),
the
CSR address (the default is 176700), the number of RP04/05/06
drives (there is no default for this parameter),
the unit
number of the first drive (the default for the first physical
unit number is 0), and whether or not the controller supports
offset
recovery
(the default is O,
to support offset
recovery) for the first RHll or RH70 controller.
Offset recovery support provides a higher degree of data
integrity in environments where disk packs are frequently
moved from drive to drive. This support moves the disk head
on either side of the cylinder centerline in an attempt to
pick up a stronger signal.
Thus, offset recovery support
allows data to be read in instances where it could not
otherwise be recovered.
If you use the default values (enter two commas (,,) followed
by the number of drives), the acceptable range for the number
of drives is 1-8.

5-50

_.,

DETAILS OF SYSGEH PHASE I
If you do not use the default values, the
(response) are:
vector
CSR
number of drives
unit number of first drive
off set recovery

acceptable

ranges

60-774 (octal)
160000-177700 (octal)
1-8 (decimal)
1-7 (decimal)
O or NO

Subsequent RHll or RH70 controllers for IB:
unit number of the first drive (to 0).

default only the

NOTE
You can only specify offset recovery
support for the first DB controller.
If
you include support for
the
first
controller, you automatically include
off set recovery support for subsequ~nt
controllers.
Likewise,
if you exclude
support,
you exclude offset recovery
support for subsequent controllers.

~·

After you enter the parameters for each RHll or RH70
controller
included in your system, SYSGEN immediately
prompts for drive type using SYSGEN prompt line 52.
For
clarity, this section lists the prompt lines in numeric
order, not in logical sequence.
If you were performing a
SYSGEN and included an RHll or RH70 controller for DB:
devices (RP04/05/06), the questions that specify the type of
drive would follow the DB controller parameter specification.
2.

DR controller 0 [D:254,176700,,0,0]
Enter the interrupt vector address (the default is 254),
the
CSR address
(the default is 276700), the number of RM02/03
drives (there is no default for this parameter), the physical
unit number of the first drive
(the default is 0), and
whether or not the controller supports offset recovery
(the
default is o, to support offset recovery) for the first RHll
or RH70 controller.
Offset recovery support provides a higher degree of data
integrity in environments where disk packs are frequently
moved from drive to drive. This support moves the disk head
on either side of the cylinder centerline in an attempt to
pick up a stronger signal.
Thus,
offset recovery support
allows data to be read in instances where it could not
otherwise be recovered.
If you use the default values (enter two commas (,,) followed
by the number of drives), the acceptable range for the number
of drives is 1-8.

5-51

DETAILS OF SYSGEN PHASE I
If you do not use the default values, the
(response) are:
vector
CSR
number of drives
unit number of first drive
offset recovery

acceptable

ranges

60-774 (octal)
160000-177700 (octal)
1-8 (decimal)
0-7 (decimal)
O or NO

Subsequent RHll or RH70 controllers for DR:
unit number of the first drive (to 0).

default only the

NOTE
You can only specify offset recovery
support for the first DR controller.
If
you include support for
the
first
controller, you automatically include
off set recovery support for subsequent
controllers.
Likewise,
if you exclude
support,
you exclude offset recovery
support for subsequent controllers.
After you enter the parameters for each RHll or
RH70
controller
included in your system, SYSGEN immediately
prompts for drive type using SYSGEN prompt line 56.
For
clarity, this section lists the prompt lines in numeric
order, not in logical sequence.
If you were performing a
SYSGEN and included an RHll or RH70 controller for DR:
devices (RM02/03), the questions that specify the type of
each
drive
would
follow the DR controller parameter
specification.
Enter [L/R,] vector, CSR, number of drives for:
3.

DD controller 0 [D:300,176500]
Enter the interrupt vector address
(the default value is
300),
the CSR address (the default value is 176500), and the
number of DECtape II drives (there is no default for
this
parameter) for the first TU58 ~ontroller.
The acceptable range for the number of DECtape II
1-2.

drives

If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent TU58 controllers do not default the vector and CSR
assignments;
you must enter a value, within the acceptable
range, for the vector and CSR assignments as well as the
number of drives.
3.

DL controller 0 [D:l60,174400]
Enter the interrupt vector address
(the default value is
160), the CSR address (the default value is 174400), and the
number of RLOl/02 disk drives (there is no default for
this
parameter) for the first RLll controller.
The acceptable range for the number of RLOl/02 disk drives is
1-4.
5-52

DETAILS OF SYSGEN PHASE I
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.

-~·

Subsequent RLll controllers do not default the vector and CSR
assignments;
you must enter a value, within the acceptable
range, for the vector and CSR assignments as well as the
number of RLOl/02 drives.
After you spec1fy the vector and CSR assignments and the
number of RLOl/02 drives, SYSGEN immediately prompts for
drive type using SYSGEN prompt line 53.
For clarity, this
section lists the prompt lines in numeric order, not in
logical sequence.
If you were performing a SYSGEN and
included an RLll controller for DL: devices (RLOl/02), the
questions that specify the type of drive would follow the DL
controller parameter specification.

DP controller 0 [D:254,176714]
Enter the interrupt vector address
(the default value is
254),
the CSR address (the default value is 176714), and the
number of RP02/03 disk drives (there is no default for this
parameter) for the first RPll controller.
The acceptable range for the number of RP02/03 disk drives is
1-8(10).
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent RPll controllers do not default the vector and CSR
assignments;
you must enter a value, within the acceptable
range, for the vector and CSR assignments as well as the
number of RP02/03 drives.
After you specify the vector and CSR assignments and the
number of RP02/03 drives, SYSGEN immediately prompts for
drive type using SYSGEN prompt line 55.
For clarity, this
section lists the prompt lines in numeric order, not in
logical sequence.
If you were performing a SYSGEN and
included an RPll controller for DP: devices (RP02/03), the
questions that specify the type of drive would follow the DL
controller parameter specification.

DX controller 0 [D:264,177170]
Enter the interrupt vector address
(the default value is
264),
the CSR address (the default value is 177170), and the
number of RXOl floppy disk drives (there is no default for
this parameter) for the first RXll controller.
'rhe acceptable range for
drives is 1-2.

the

number

RXOl

floppy

disk

tf you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.

5-53

DETAILS OF SYSGEN PHASE I
Subsequent RXll controllers do not default the vector and CSR
assignments;
you must enter a value, within the acceptable
range, for the vector and CSR assignments as well as the
number of RXOl floppy disk drives.
3.

DY controller 0 [D:264,177170]
Enter the interrupt vector address
(the default value is
264),
the CSR address (the default value is 177170), and the
number of RX02 floppy disk drives (there is no default for
this parameter) for the first RX211 controller.
The acceptable range for
drives is 1-2.

the

number

RX02

floppy

disk

If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR~
Subsequent RX211 controllers do not default the vector and
CSR
assignments;
you must enter a value, within the
acceptable range, for the vector and CSR assignments as well
as the number of RX02 floppy disk drives.
After you specify the vector and CSR assignments and the
number of RX02 drives, SYSGEN immediately prompts for drive
density using SYSGEN prompt line 58.
For clarity,
this
section lists the prompt lines in numeric order, not in
logical sequence.
If you were performing a SYSGEN and
included an RX211 controller for DY:
devices (RX02), the
questions that specify the density of each RX02 drive would
follow the DY controller parameter specification.
3.

MM controller 0 [D:224,172440]
Enter the interrupt vector address
(the default value is
224),
the CSR address (the default value is 172440), and the
number of TU45, TU16, TE16, or TU77 magtape drives (there is
no default for
this parameter) for the first RHll or RH70
controller, TM02 or TM03 tape controller.
The acceptable range for the number of tape drives is 1-8.
If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent controllers of this type do not default the vector
and CSR assignments;
you must enter a value, within the
acceptable range, for the vector and CSR assignments as well
as the number of tape drives.
After you specify the vector and CSR assignments and the
number of TU45, TE16, TU16, or TU77 tape drives, SYSGEN
immediately prompts for the TM02 or TM03 number using SYSGEN
prompt line 51. For clarity, this section lists the prompt
lines in numeric order, not in logical sequence.
If you were
performing a SYSGEN and included an MM:
device (TU45, TU16,
TE16, or TU77), the questions that specify the TM02 or TM03
number
would
follow
the
MM
controller
parameter
specification.

5-54

DETAILS OF SYSGEN PHASE I
3.

MT controller 0 (0:224,172522]
Enter the interrupt vector address
{the default value is
224),
the CSR address {the default value is 172522), and the
number of TS03, TUlO, or TE!O magtape drives
{there is no
default for this parameter)
for the first TMll, TMAll, or
TMBll controller.

The acceptable
1-8(10).

range

for

the

number

tape

drives

If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent controllers of this type do not default the vector
and CSR assignments;
you must enter a value, within the
acceptable range, for the vector and CSR assignments as well
as the number of tape drives.

.-~

Enter [L/R,] vector, CSR, F=full duplex /H=half duplex,
E=error detec.
unit /NO=no, C=char. detec unit /NO=no,
number of sync characters in leader for:
4.

XQ controller 0 [D:,,H,E,C]
The vector address for the DQll synchronous line interface is
assigned from the floating vector space starting at 300.
Thus, there is no defaul~ vector address for the DQll. Enter
a vector address between 300 and 774. Consult Field Service
if the vector address is unknown.
The CSR address for the DQll synchronous line interface is
assigned from the floating address space starting at 160010.
Thus, there is no default CSR assignment for the DQll. Enter
a CSR address between 160010 and 177700. Consult Field
Service if the CSR address is unknown.
The first DQll line defaults to a half duplex line {H), with
an error detection expander unit
{E), and a character
detection expander unit {C). Enter F, NO, or NO respectively
to override these defaults.
There is no default value for the parameter that specifies
the required number of sync characters in a sync leader. You
must enter a value in the range 3-14(10). A typical response
is 4-6.
If the line is to run at high speeds or if the
expected system load is to be heavy, specify a greater number
of sync characters.
Subsequent DQll lines do not default any of the parameters;
you must enter values for the vector and CSR assignments
{vector range is 300-774, CSR range is 160010-177700 both
octal), whether the line is half duplex {H) or full duplex
(F), whether an error detection expander unit is present
(E)
or not
(NO), whether a character detection expander unit is
present (C) or not (NO), and the required number of sync
characters in a sync leader (range is 3-14 decimal).

5-55

DETAILS OF SYSGEN PHASE I
Enter [L/R,] vector, CSR, number of drives, unit number of first drive for:

DS controller O (0:204,172040,,0]
Enter the interrupt vector address (the default value is
204), the CSR address (the default value is 172040), the
number of RS03/04 disk drives (there is no default value for
this parameter), and the unit number of the first RS03/04
drive (the default value is 0} for the first RHll or RH70
c,ontrol ler.
The acceptable range for the number of RS03/04 drives is 1-8.
If you do not use the default values, the
are:
vector
CSR
number of drives
unit number of first drive
Subsequent RHll or RH70 controllers
number of the first drive (to 0).

acceptable

ranges

60-774 (octal)
160000-177700 (octal)
1-8 (decimal)
0-7 (octal)
default

only

the

unit

After you enter the parameters for each RHll or RH70
controller
included in your system, SYSGEN immediately
prompts for drive type using SYSGEN prompt line 57.
For
clarity, this section lists the prompt lines in numeric
order, not in logical sequence. If you were performing a
SYSGEN and included an RHll or RH70 controller for DS:
devices (RS03/04), the questions that specify whether each
drive is an RS03 or an RS04 would follow the DS controller
parameter specification.
Enter [L/R,] vector, CSR, highest unit number <O to 7> for:
6.

DK controller 0 (0:220,177404]
Enter the interrupt vector address (the default value is
220), the CSR address (the default value is 177404), and the
highest RKOS unit number (there is no default value for this
parameter) for the first RKll controller.
The acceptable range for the highest RK05 unit number is 0-7.
Note that if you want the first RK05 unit number to be O,
enter the number of RK05 drives minus one as the highest unit
number.
If you do not enter the default vector and CSR assignments,
the
acceptable
range
is
60-774 for the vector and
160000-177700 for the CSR, both in octal.
NOTE
Fixed platter RKOS drives (RK05F) are
handled as two units. The first of each
RKOSF pair must be an even unit number;
for example, 0 and i, 2 and 3. Be sure
to take this into account when you
calculate the highest RK05 unit number.

5-56

DETAILS OF SYSGEN PHASE I
Enter vector, CSR, VTll/VS60, number of CRT monitors for:
7.

GR controller O [D:,172000,,l]
RSX-llM supports the graphics
following restrictions.

display

subsystem

with

the

One 1 and only one, VTll or VS60 in the system

The graphics display driver does not operate on PDP-11/70
processors in 22-bit mode; memory size must be less than
or equal to 124K-words.

For systems using the VTll, the display buffer of the
task driving the VTll must completely reside in the low
28K-words of system memory

The vector address for the graphics display subsystem is
assigned from the floating vector space starting at 300.
Thus, there is no default vector address for the graphics
display subsystem.
Enter a vector address between 300 and
774. Consult Field Service if the vector address is unknown.
After you specify the vector address, enter the CSR address
(the default value is 172000), whether the connected terminal
is a VTll or a VS60 (there is no default for this parameter),
and the number of CRT monitors (the default value is 1).
If you do not enter the default values for the CSR assignment
and the number of CRT monitors, the acceptable range is
160000-177700 for the CSR and 1-2 for the number of CRT
monitors, all in octal.
NOTE
Only the VS60 can drive two CRT monitors
independently.
Thus,
if your system
includes the VTll you must specify one,
the default value, for the number of CRT
monitors.
Enter [L/R,] CSR, number of A/D channels for:
8.

AD controller O [0:176770]
The ADOl-D analog-to-digital converter is a non-interrupt
device.
Therefore, you do not enter an interrupt vector
address.
Enter the CSR address (the default value is 176770) and the
number of A/D channels
(there is no default for this
parameter) for the first ADOl-D controller.
The acceptable range for the number of A/D channels is
1-64(10).
If you do not enter the default value for the CSR
assignment, the acceptable range is 160000-177700 (octal).
Subsequent ADOl-D controllers do not default
the
CSR
assignment;
you must enter a value within the acceptable
range.

5-57

DETAILS OF SYSGEN PHASE I
Enter [L/R,] vector, CSR, number of A/D channels for:
9.

AF controller 0 (0:134,172570]
Enter the interrupt vector address
(the default value is
134), the CSR address (the default value is 172570), and the
number of A/D channels
(there is no default for this
parameter) for the first AFCll controller.
The acceptable range
1-1024(10).

for

the

number

A/D

channels

If you do not enter the default values for the vector and CSR
assignments,
the acceptable range is 60-774 for the vector
and 160000-177700 for the CSR, both in octal.
Subsequent AFCll controllers do not default the vector and
CSR
assignments;
you must enter a value, within the
acceptable range, for the vector and CSR assignments as well
as the number of A/D channels.
Enter [L/R,] clock vector, CSR, polarity mask, D-D/A channel /NO=no,
maximum number of samples/second, DRK=DRll-K/NO=no
(,DRll-K CSR) for
10.

AR controller 0 [D:,170400,,,,,170420]
The clock vector address for the ARll controller is assigned
from the floating vector space starting at 300. It is
located at an offset of four (4) from the beginning of the
ARll vector space.
Thus, there is no default clock vector
address for the ARll. Enter a clock vector address between
300 and 774.
Consult Field Service if the clock vector
address is unknown.
The standard CSR address for the ARll is 170400. Specify the
address of the first word of the ARll CSR group (the default
value is 170400). If you do not enter the default CSR
address, the acceptable range is 160000-177700.
The polarity mask word specifies whether an individual
channel is uni-polar or bi-polar;
it corresponds one-to-one
with the 16 possible channels.
A 1-bit designates
a
uni-polar channel and a 0-bit designates a bi-polar channel.
The acceptable range for the polarity mask word is 0-177777
octal
(0 specifies 16 bi-polar channeis, 177777 specifi~s 16
uni-polar channels).
The ARll module includes a D/A converter.
However, support
for the D/A is optional in the driver.
If you do not include
support (enter NO for parameter 4),
the driver will be
significantly shorter.
The maximum number of samples must be evenly divisible
10,000 and within the acceptable range of 1-2500(10).

into

The ARll does not include the 16-bit digital I/O option that
is available with the LPSll. However, you can achieve the
same functionality using the DRll-K.
The· DRll-K must be
jumper selected to use the 16 individual input lines without
interrupts.
If the DRll-K option is present, enter the CSR
address of the DRll-K (the default value is 170420). If you
do not enter the default DRll-K CSR address,
the acceptable
range is 160000-177700, octal.
5-58

•

DETAILS OF SYSGEN PHASE I
Subsequent ARll controllers default only the CSR address of
the
DRll-K option;
you must enter values within the
acceptable ranges. Also, if subsequent ARll controllers do
not
include the DRll-K option, you must exclude this
parameter.

•

Enter [L/R,] clock vector, CSR, #A/D channels, G=gain ranging option /NO•no,
polarity mask, bandwith filter channel select delay,
number of D/A channels, D=digital I/O option /NO=no,
maximum number of samples/second for:
11.

LS controller o [D:,170400,,,o,o,o,No]
The clock vector address for the LPSll controller is assigned
from the floating vector space starting at 300. It is
located at an offset of four (4) from the beginning of the
LPSll vector space. Thus, there is no default clock vector
address for the LPSll. Enter a clock vector address between
300 and 774 octal. Consult Field Service if the clock vector
address is unknown.
The standard CSR address for the LPSll is 170400.
Specify
the address of the first word of the LPSll CSR group (the
default value is 170400). If you do not enter the default
CSR address, the acceptable range is 160000-177700 octal.
The next parameter is the numbet of A/D channels;
enter a
value in the range 1-64(10)
to specify the number of A/D
channels on the first LPSll controller.
You must then enter whether or not the gain ranging option is
present.
If the gain ranging option is present, you must
specify the polarity mask word and the bandwith filter
channel select delay (if required).
The polarity mask word specifies whether an individual
channel is uni-polar or bi-polar;
it corresponds one-to-one
with the 16 possible channels.
A 1-bit designates
a
uni-polar channel and a 0-bit designates a bi-polar channel.
'.rhe acceptable range for the polarity mask word is 0-177777
octal
(0 specifies 16 bi-polar channels, 177777 specifies 16
uni-polar channels).
With bandwith filtering enabled, the LPSll driver imposes a
software delay between changing channels on the multiplexer
and initiating an A/D conversion. This delay can range from
85 usec to 8.5 msec.
Consult the LPSll documentation to
determine the proper delay for your application.
Note that
the response must be in 100 usec units (for example, specify
25 to delay 2.5 msec). The acceptable range is 0-85.
Enter
0 to disable bandwith filtering.

•

If your system includes the D/A option, enter the number of
channels in the range 0-10(10). A response of 0 indicates
the option is not present.
The first two D/A channels
correspond
to
the X and Y registers of the display
controller. Up to eight additional D/A channels may be
specified if the external D/A option is present.

5-59

DETAILS OF SYSGEN PHASE I
The LPSll supports a digital I/O and relay module. You must
specify whether or not the option is present. You then enter
the maximum number of samples per second.
The acceptable
range is 1-2500(10). Note that this value must be a multiple
of 10,000 (1, 2, 4, 5, 8, 10, 16, 20, 25, 40, 50, 80, 100,
125, 200, 250, 400, 500, 625, 1000, 1250, 2000, or 2500).
Enter [L/R,] vector, CSR (, number of UMRs) for
12.

LA controller 0 [D:300,170460,0]
Enter the interrupt vector address
(the default value is
300),
the CSR address (the default value is 170460), and the
number of UNIBUS Mapping Registers (UMRs) for the LPAll-K.
The UMR parameter applies only to PDP-11/70 processors with
extended memory
(22-bit mapping) support. Enter a value to
specify the maximum number of UMRs that the LPAll-K driver
can use to map all currently active LPAll-K I/O transfers.
See the RSX-llM/M-PLUS I/O Drivers Reference Manual for
details.
NOTE
The vector address is assigned from
floating vector space.
Consult Field
Service if the location is unknown.
Also,
the required CSR address is that
of the first word of the LPAll CSR
group.
Again, consult Field Service if
unknown.

Enter [L/R,] vector, CSR, # drives, O=offset recovery /NO=no offset rec.
13.

for:

DM controller 0 [230,177440,,0]
Enter the interrupt vector address
(the default value is
210),
the CSR address
(the default value is 177440), the
number of RK06/07 disk drives (there is no default for
this
parameter), and whether or not the controller is to support
offset recovery (the default is to include offset recovery
support (O)) for the first RK611 controller.
The acceptable range for the
1-8(10).

number

RK06/07

drives

Offset recovery support provides a higher degree of data
integrity in environments where disk packs are frequently
moved from drive to drive. This support moves the disk head
on either side of the cylinder centerline in an attempt to
pick up a stronger signal.
Thus,
offset recovery support
allows data to be read in instances where it could not
otherwise be recovered.
If you do not use the default vector and CSR assignments, the
acceptable range is 60-774 for the vector and 160000-177700
for the CSR, both octal.

5-60

11111\,

DETAILS OF SYSGEN PHASE I
Subsequent RK611 controllers do not default the vector and
CSR
assignments;
you must enter a value, within the
acceptable range, for the vector and CSR assignments as well
as the number of RK06/07 drives.
NOTE
Yo·u can only specify offset recovery
support for
the first controller.
If
you include support for the first RK611
controller, you automatically include
offset recovery support for subsequent
controllers.
Likewise,
if you exclude
support,
you exclude offset recovery
support ·
for
subsequent
RK611
controllers.
After you enter the parameters for each RK6ll controller
included in your system, SYSGEN immediately prompts for drive
type using SYSGEN prompt line 54. For clarity, this section
lists the prompt lines in numeric order, not in logical
sequence.
If you were performing a SYSGEN and included an
RK611 controller for DM: devices (RK06/07), the questions
that specify whether each drive is an RK06 or an RK07 would
follow the DM controller parameter specification.
Enter [L/R,] vector, CSR, F=full duplex /H=half duplex,
number of characters in sync leader for:
14.

XL controller 0 [D:,,H]
The vector address for the DLll-E asynchronous line interface
is assigned from the floating vector space starting at 300.
Thus, there is no default vector address for
the DLll-E.
Enter a vector address between 300 and 774. Consult Field
Service if the vector address is unknown.
The CSR address for the DLll-E asynchronous line interface is
assigned from the floating address space starting at 175610.
Thus, there is no default CSR assignment for
the DLll-E.
Enter a CSR address between 175610 and 177700 octal. Consult
Field Service if the CSR address is unknown.
The first DLll-E line defaults to a half
Enter F to specify a full duplex line.

duplex

line

(H).

~rhere

is no default value for the parameter that specifies
the required number of sync characters in a sync leader. You
must enter a value in the range 3-14(10). A typical response
is 4-6.
If the line is to run at high speeds or if the
expected system load is to be heavy, specify a greater number
of sync characters.
Subsequent DLll-E lines do not default any of
you must enter values for the vector an~
(vector range is 300-774, CSR range is
whether the line is half duplex (H) or full
the required number of sync characters in
(range is 3-14).

5-61

the parameters;
CSR assignments
175610-177700)'
duplex (F), and
a sync leader

DETAILS OF SYSGEN PHASE I
14.

XP controller 0 [D:,174770,H]
The vector address for the DPll synchronous line interface is
assigned from the floating vector space starting at 300.
Thus, there is no default interrupt vector address for the
DPll.
Enter a vector ·address between 300 and 774 octal.
Consult Field Service if the vector address is unknown.
If you
The standard CSR assignment for the DPll is 174770.
do not enter the default CSR address, enter a value in the
range 160000-177700 octal.
The first DPll line defaults to a half
Enter F to specify a full duplex line.

duplex

line

( H) •

There is no default value for the parameter that specifies
the required number of sync characters in a sync leader. You
must enter a value in the range 3-14(10). A typical response
is 4-6.
If the line is to run at high speeds or if the
expected system load is to be heavy, specify a greater number
of sync characters.
Subsequent DPll lines default only the half duplex parameter
(H);
you
must enter values for the vector and CSR
assignments (vector range is
300-774,
CSR
range
is
160000-177700 both octal), and the required number of sync
characters in a sync leader (range is 3-14 decimal).
14.

XU controller 0 [D:,,F]
The vector address for the DUll synchronous line interface is
assigned from the floating vector space starting at 300.
Thus, there is no default interrupt vector address for the
DUll.
Enter a vector address between 300 and 774 octal.
Consult Field Service if the vector address is unknown.
The CSR address for the DUll synchronous line interface is
assigned from the floating address space starting at 160010.
Thus, there is no default CSR assignment for the DUll. Enter
a CSR address between 160010 and 177700 octal. Consult Field
Service if the CSR address is unknown.
The first DUll line defaults to a full
Enter H to specify a half duplex line.

duplex

line

(F).

There is no default value for the parameter that specifies
the required number of sync characters in a sync leader You
must enter a value in the range 3-14(10). A typical response
is 4-6.
If the line is to run at high speeds or if the
expected system load is to be heavy, specify a greater number
of sync characters.
Subsequent DUll lines default only the full duplex parameter
(F);
you
must enter values for the vector and CSR
assignments (vector range is
300-774,
CSR
range
is
160010-177700 both octal), and the required number of sync
characters in a sync leader (range is 3-14 decimal).

5-62

DETAILS OF SYSGEN PHASE I
14.

XW controller O [D:,,H]
The vector address for the DUPll synchronous line interface
is assigned from the floating vector space starting at 300.
Thus, there is no default interrupt vector address for the
DUPll.
Enter a vector addres~ between 300 and 774 octal.
Consult Field Service if the vector address is unknown.
The CSR address for the DUPll synchronous line interface is
assigned from the floating address space starting at 160010.
Thus, there is no default CSR assignment for the DUPll.
Enter a CSR address between 160010 and 177700 octal. Consult
Field Service if the CSR address is unknown.
The first DUPll line defaults to a half
Enter F to specify a full duplex line.

duplex

line

(H).

There is no default for the parameter that specifies the
required number of sync characters in a sync leader. You
must enter a value in the range 3-14(10). A typical response
is 4-6.
If the line is to run at high speeds or if the
expected system load is to be heavy, specify a greater number
of sync characters •

.....

Subsequent DUPll lines do not default any of the parameters;
you must enter values for the vector and CSR assignments
(vector range is 300-774, CSR range is 160010-177700 both
octal), whether the line is half duplex (H) or full duplex
(F), and the required number of sync characters in a sync
leader (range is 3-14 decimal).
Enter [L/R,] vector, CSR, F=full duplex/H=half duplex /P=primary HDX for:

15.

XM controller O
The vector address for the DMCll interprocessor link is
assigned from the floating vector space starting at 300.
Thus, there is no default interrupt vector address for the
DMCll.
Enter a vector address between 300 and 774 octal.
Consult Field Service if the vector address is unknown.
The CSR address for the DMCll interprocessor link is assigned
from the floating address space starting at 160010. Thus,
there is no default CSR assignment for the DMCll.
Enter a
CSR address between 160010 and 177700 octal. Consult Field
Service if the CSR address is unknown.
Normally, the DMCll is a full duplex serial communications
link.
When the DMCll is used on a half duplex line, one end
of the line must be the primary station and the other end
must be the secondary station. Specify an H to indicate that
the line is a secondary station or P to indicate that the
line is a primary station •

5-63

DETAILS OF SYSGEN PHASE I
Enter [L/R,] vector, CSR, printer type
(, [KMC timeout count <O=noKMC>, KMC vector, KMC CSR]) for:
16.

LP controller 0 [D:200,177514,LA180,0,300,160130]
Enter the interrupt vector address
(the default value is
200),
the CSR address (the default value is 177514), and the
printer type (the default type is LA180)
for
the first LP
controller.
Valid printer types are:
LA180;
LPll-C;
L.Pll-D;
LPll-F;
LPll-H;
LPll-J;
LPll-K;
LPll-R;
LPll-S;
LPll-V;
LPll-W;
LPll-Y;
LPll-Z;
LSll;
LVll.
For printer
widths and speed, consult Field Service or the PDP-11
Peripherals Handbook.
If your system includes KMC line printer support,
you must
enter the KMC timeout count (the default of 0 excludes KMC
support), the KMC interrupt vector address (the default value
is 300), and the KMC CSR address
(the default value is
160130).
The timeout count specifies the interval in which the KMC
polls the line printer between print lines. This value is
measured in units of 50 micro seconds.
For example,
if you
enter 1, the KMC polls the line printer every 100 micro
seconds (as each print buffer empties). The acceptable range
is 0-100 decimal.
For slower printers, poll less frequently
(enter
a
higher
number);
the
polling
interval
increases/decreases UNIBUS latency.
The acceptable range for the KMC interrupt vector address
60-774
and
for
the
KMC
CSR address the range
160000-177700, both in octal.

is
is

NOTE
If you select KMC support, all printers
must use the KMC;
those that do not
will not operate.
You can connect a maximum
system.

eight

line

printers

the

Enter number of modules, module number of first for:
17.

UD controller O xxxx module
NOTE
If you specified a UDCll controller,
this
SYSGEN
prompt
line
and the
questions that follow appear immediately
after you enter the vector and CSR
assi~nments for the UDCll.
The UDCll supports up to 252 modules, which can be classified
into seven types:
•
•
•

Analog input
Analog output
Bi-stable output

5-64

....

DETAILS OF SYSGEN PHASE I
•
•
•
•

Digital interrupt
Digital sense
I/O counter
Single-shot output

Modules of the same type must occupy consecutive locations
within the UDCll.
Thus,
if there are seven analog input
modules and the first module starts at slot O, then the last
analog input module must be at slot 6. Module types cannot
overlap, but unassigned slots are permitted.
SYSGEN asks the following questions to establish UDCll module
boundaries.
You must enter the number of each module
contained in the UDCll and identify the slot for that module
to begin. The permissible range for each entry is 0-252(10).
Note, however, that SYSGEN decrements the range value for the
number o~ each module by the total number of previously
specified UDCll modules.
For example,
if you specify 50
analog input modules,
you are limited to 152 of the other
modules (maximum 252 UDCll modules).
Both responses are in
octal.
17.

UD controller 0 ADUOl analog input module

17.

UD controller 0 analog output module

17.

UD controller 0 bi-stable output module

17.

UD controller 0 digital interrupt module

17.

UD controller 0 digital sense module

17.

UD controller 0 I/O counter module

17.

UD controller 0 single-shot output module

Enter [ L/R,] terminal number to redirect to (TTn:) for:
18.

co controller 0 [D: 0]
This poorly phrased question requests a terminal number. The
console output driver redirects the pseudo device CO:
to the
terminal you specify.
The default is 0 (TTO:).
If you do not use the default value, the acceptable range
0-77 octal.

Enter [L/R,] num.
19.

DLll's <ZL>, num.

DHll's, num.

DZll's, num.

DJll's for:

The terminal driver [D:l,O,O,O]
This question appears only if you selected either one of the
half duplex drivers including the baseline driver.
(The full
duplex terminal driver is always loadable and appears in
question 20.)
For RSX-llM systems, you must generate
asynchronous terminal
interface into
does not require a DLll.
All responses are in decimal.

5-65

at least one DLll
the system. RSX-llS

DETAILS OF SYSGEN PHASE I
Enter the number of each type of terminal interface included
in your system.
The default response includes one DLll
asynchronous terminal interface.
If you do not use the
default response,
the acceptable range is 1-8 for the DLll
and 0-16 for the DHll, DZll, and DJll terminal interfaces.
Enter num.
20.

DLll's <ZL>, num.

DHll's, num.

DZll's, num.

DJll's for:

The termfnal driver [D:l,O,O,O]
This question appears only if you selected the full duplex
terminal driver.
Note that the optional Loadable/Resident
parameter does not appear since the full duplex driver
is
always loadable.
For RSX-llM system, you must generate
asynchronous terminal
interface into
does not require a DLll.

at least one DLll
the system. RSX-llS

All responses are in decimal.
Enter the number of each type of terminal interface included
in your system.
The default response includes one DLll
asynchronous terminal interface.
If you do not use the
default response,
the acceptable range is 1-8 for the DLll
and 0-16 for the DHll, DZll, and DJll terminal interfaces.
Enter vector, CSR for:
21.

ZL controller 0 [0:60,177560]
This question always appears;
you must include at least
DLll line interface in an RSX-llM system.

one

The standard interrupt vector address for the first DLll line
is 60. If you do not use the default vector assignment, the
acceptable range is 60-774 octal.
The standard CSR address for the first DLll line is 177560.
If you do not use the default CSR assignment, the acceptable
range is 160000-177700 octal.
If you specified more than one DLll, you must enter
vector and CSR assignment for each additional line.

the

Interrupt vector addresses for additional DLll lines are
assigned from the floating vector space starting at 300.
There is no default vector address for any additional DLll
lines.
You must enter a value within the range 300-774
octal. Consult Field Service if the interrupt vector address
of additional lines is unknown.
CSR addresses for additional DLll lines are assigned from
floating address space starting at 176000.
There is no
default CSR address for any additional DLll lines.
You must
enter a value within the range 176000-176770 octal. Consult
Field Service if the CSR address of additional lines is
unknown.

5-66

DETAILS OF SYSGEN PHASE I
Enter vector, CSR, highest line number <O to 15>
(, answer speed, DMll-BB vector, DMll-BB CSR) for:
22.

DH controller 0 [D:,,,300,0,0]
This question appears only if you
specified
a
DHll
asynchronous line interfaceo Note that the Loadable/Resident
parameter does not appear •

The interrupt vector address for the DHll is assigned from
floating vector space starting at location 300. Thus, there
is no default vector assignment for the DHll. Enter a vector
address between 300 and 774 octal. Consult Field Service if
the interrupt vector address is unknown.
The CSR address for
the DHll is assigned from floating
address space starting at 160010. Thus there is no default
CSR assignment for the DHll~ Enter a CSR address between
160010 and 177700 octal. Consult Field Service if the CSR
address is unknown.
The DHll can service up to 16 remote and local lines. Remote
lines occupy consecutive line locations.
Line assignment is
by groups of four.
Local lines also occupy consecutive line
locations and their assignment follows the assignment of any
remote lines specified. Enter the total number of lines
desired by specifying the highest line number in the range
0-15 decimal (O indicates one line, 15 indicates 16 lines).
If your DHll includes DMll-BB modem support, you must enter
the baud rate at which all DHll remote lines are answered.
The default answer speed is 300.
If you do not use the
default response, the acceptable answer speed baud rates are
50, 75, 110, 134.5, 150, 200, 300, 600, 1200, 2400, 4800, or
9600.
If included, you must also specify the DMll-BB vector
and CSR assignments. The default response of O excludes
DMll-BB modem support. To include DMll-BB modem support, you
must enter a value for the vector and CSR assignments.
The DMll-BB interrupt vector address is assigned
from
floating vector space starting at 300. Thus, you must enter
a value between 300 and 774 octal to include DMll-BB modem
support.
Consult Field Service if the interrupt vector
address is unknown.
The standard CSR address for the DMll-BB is 170500.
If you
include DMll-BB support, enter 170500 or a value within the
range 160000-177700 octal for the CSR assignment.
SYSGEN repeats this question for each DHll specified.
Enter vector, CSR, highest line number <O to 15> for:
23.

DJ controller O
This question appears only if you
specified
a
DJll
asynchronous
line
multiplexer.
Note
that
the
Loadable/Resident parameter does not appear. This is because
the DJll uses the same driver as the DLll and the DHll.

5-67

DETAILS OF SYSGEN PHASE I
The interrupt vector address for the DJll is assigned from
floating vector space starting at 300. Thus, there is no
default vector assignment for the DJll.
Enter a vector
address between 300 and 774 octal. Consult Field Service if
the vector address is unknown.
The CSR address for the DJll is assigned from floating
address space starting at 160010. Thus , there is no default
CSR assignment for the DJll. Enter a CSR address between
160010 and 177700 octal. Consult Field Service if the CSR
address is unknown.
Each DJll can service up to 16 asynchronous serial lines.
Enter the total number of lines by specifying the highest
line number in the range 0 to 15 decimal
(0 indicates one
line, 15 indicates 16 lines).
SYSGEN repeats this question for each DJll specified.
Enter vector, CSR, highest line number <O to 7> [, answer speed] for:
24.

DZ controller 0 [D:,,,O]
This question appears only if you
specified
a
asynchronous
line
multiplexer.
Note
that
Loadable/Resident parameter does not appear.

DZll
the

The interrupt vector address for the DZll is assigned from
floating vector space starting at 300. Thus, there is no
default vector assignment for
the DZll.
Enter a vector
address between 300 and 774 octal. Consult Field Service if
the vector address is unknown~
The CSR address for the DZll is assigned from floating
address space starting at 160010. Thus, there is no default
CSR assignment for the DZll. Enter a CSR address between
160010 and 177700 octal. Consult Field Service if the CSR
address is unknown.
Each DZll can service up to 8 asynchronous lines.
Enter the
total number of lines by specifying the highest line number
in the range 0 to 7 decimal
(0 indicates one line,
7
indicates 8 lines).
The DZll can maintain a full duplex connection through a Bell
103A type modem. However, modem support requires additional
code in the terminal database as well as in the driver and
thus increases system overhead;
select modem support only if
needed.
If you wish to include modem support, specify the
baud rate at which all DZll remote lines are to be answered.
Acceptable answer speed baud rates are 50, 75, 110, 134.5,
150, 200, 300, 600, 1200, 2400, 4800, or 9600. Note that the
default for this parameter (0) excludes modem support.
SYSGEN repeats this question for each DZll specified.

5-68

·-

DETAILS OF SYSGEN PHASE I
The following questions provide additional device information and
immediately follow the respective SYSGEN prompt line for controller
information.
*51.

MM controller 0 unit O.

formatter

[D R:0-7 D:O]

This question immediately follows parameter specification for
each MM controller (SYSGEN prompt line 3). You must identify
the number (the unit plug) for the TM02/03 formatter
(tape
controller)
on the RHll or RH70. The default is O. If you
do not use the default response, the acceptable range is 0-7.
SYSGEN repeats this question for each device
for each controller.
*52.

Contr 0 unit O.

unit

specified

is an RP04,05/RP06 [D:RP06]

This question immediately follows parameter specification for
each DB controller (SYSGEN prompt line 2). You must specify
the type of drive.
Enter RP06 (the default response), RP04
or RP05.
SYSGEN repeats this question for each device
for each controller.
*53.

Contr 0 unit O.

unit

specified

is an RL01/RL02 [D:RLOl]

This question immediately follows parameter specification for
each DL controller (SYSGEN prompt line 3). You must specify
the type of drive.
Enter either RLOl (the default response)
or RL02.
SYSGEN repeats this question for each device
for each controller.
*54.

Contr 0 unit O.

unit

specified

is an RK06/RK07 [D:RK06]

'rhis question immediately follows parameter specification for
each DM controller (SYSGEN prompt line 13). You must specify
the type of drive. Enter either RK06 (the default response)
or RK07.
SYSGEN repeats this question for each device
for each controller.
*55.

Contr 0 unit O.

unit

specified

is an RP02/RP03 [D:RP03]

This question immediately follows parameter specification for
each DP controller (SYSGEN prompt line 3). You must specify
the type of drive. Enter either RP02 or RP03
(the default
response).

SYSGEN repeats this question for each device
for each controller.
*56.

Contr 0 unit

unit

specified

is an RM02/RM03 [D:RM03]

This question immediately follows parameter specification for
each DR controller (SYSGEN prompt line 2). You must specify
the type of drive. Enter either RM02 or RM03
(the default
response).
SYSGEN repeats this question for each device
for each controller.

5-69

unit

~pecified

DETAILS OF SYSGEN PHASE I
*57.-

Contr O unit

is an RS03/RS04 [D:RS04]

This question immediately follows parameter specification for
each OS controller (SYSGEN prompt line 5). You must specify
the type of drive. Enter either RS03 or RS04
(the default
response).
SYSGEN repeats this question for each device
for each controller.
*58.

Contr 0 unit O.

unit

specified

is SINGLE/DOUBLE density

This question immediately follows parameter specification for
each DY controller (SYSGEN prompt line 3). You must specify
whether each RX02 drive is initially at single density or at
double density. Enter either SINGLE or DOUBLE.
SYSGEN repeats this question for each device
for each controller.

unit

specified

If your system includes ICS/ICR process I/O subsystems or DSS/DRS
modules, SYSGEN asks the following questions. Note that UDCll support
precludes ICS/ICR support;
ICS/ICR and UDCll are mutually exclusive.
*l.

Expanded comments for ICS/ICR questions
Expanded comments provide explanatory
answer the ICS/ICR questions.

*2.

text

that

helps

you

Do you want task activation from unsolicited interrupts
This option permits the ICS/ICR driver to initiate a task
when the driver receives unsolicited input.
The option
provides support for tasks to link to interrupts and obtain
activation data upon initiation.

*3.

IC controller 0 vector address
The standard vector address for the ICS/ICR subsystem is 234.
Enter a value within the range 234-774.
Subsequent IC
controllers obtain vector assignments from floating vector
space starting at 300. Consult Field Service if the vector
addresses are unknown.

*4.

CSR address
The standard CSR address for the ICS/ICR subsystem is 171776.
Enter a value within the range 160000-177700. CSR addresses
for subsequent IC controllers are assigned starting at 171766
and proceed downward in eight byte intervals (for example,
171766, 171756, and 171746).

*5.

Is it an ICR-11
Specify whether the subsystem is an ICR-11 or an ICS-11.
SYSG£N repeats this query for each IC controller specified.

*6.

Number of A/D converter modules in this ICS/ICR
The ICS/ICR subsystem supports up to 16 analog to digital
converter modules, each with 8 channels. Enter a value in
the range 0-16. If you enter a non-zero value, SYSGEN asks
question 7. SYSGEN repeats this question and, if applicable,
question 7, for each IC controller specified.

5-70

DETAILS OF SYSGEN PHASE I
*7.

A/D converter module number
Enter the module number in the range 0-15.

*8.

Number of expansion multiplexers
Enter a value in the range 0-7.

The ICS/ICH subsystem consists of six distinct modules:

• D/A converter
• Single-shot output
• Bi·-stable output
• Digital sense

• Digital interrupt
• I/O counter
SYSGEN prompts for the number of each module in your system (in
questions 12 through 17) and then asks for the module number of each
(in question 9).
*12.

Number of D/A converter modu+es in this ICS/ICR

*13.

Number of single-shot output modules in this ICS/ICR

*14.

Number of bi-stable output modules in this ICS/ICR

*15.

Number of digital sense modules in this ICS/ICR

*16.

Number of digital interrupt modules in this ICS/ICR

* 17.

Number of I/O counter modules in this ICS/ICR

*9.

(module name) module number
This question appears for each module you include (specify a
non-zero number of modules).
Enter a value in the range
0-15.

*10.

Restore module status on power and error recovery
This question appears only if the system includes a bi-stable
output, D/A converter, or I/O counter module
(non-zero
response to questions 14, 12, or 17 respectively).
If you select this option, the ICS/ICR driver restores the
state of all bi-stable digital outputs, analog outputs, and
I/O prescalar values on power recovery and recovery from
sustained serial transmission errors.

*11.

How many line errors are acceptable per second
This question appears only if you include the restore
status option (respond Yes to question 10).

module

When serial line errors exceed the limit you specify in
response to this question, the IC driver places the affected
subsystem offline (when the line errors cease, the driver
automatically places the subsystem online). Enter a value in
the range 0-5000.
5-71

DETAILS OF SYSGEN PHASE I

*18.

Expanded comments for DSS/DRS questions
Expanded comments provide explanatory
answer the DSS/DRS questions.

*19.

text

that

helps

you

Number of DRS-11 modules
Enter the number of DRS-11 digital output modules in the
range 0-16.
If you enter 0 1 SYSGEN omits questions 20, 21,
pnd 22.

*20.

Restore module status on power and error recovery
If you select this option, the DRS driver restores the state
of all 48 buffered digital output modules on power recovery
and recovery from sustained transmission errors.

*21.

DRS-11 CSR address
Enter a value for the CSR address in the range 160000-177700.

*22.

DRS-11 vector address
Enter a value for the vector address in the range 300-774.

*23.

Number of DSS-11 digital input modules
Enter the number of DSS-11 digital input modules. Note that
the total number of DRS-11 and DSS-11 modules cannot exceed
16. Thus, the acceptable range for this response is 0 to 16
minus the number of DRS-11 modules specified in question 19.
If you enter O, SYSGEN omits questions 24, 25, and 26.

*24.

DSS-11 CSR address
Enter a value for the CSR address in the range 160000-177700.

*25.

DSS-11 vector address
Enter a value for the vector address in the range 300-774.

*26.

Task activation from unsolicited interrupts
This option permits the DSS/DRS driver to initiate a task
when the driver receives unsolicited input.
The option
provides support for tasks to link to interrupts and obtain
activation data upon initiation.

If your system includes IP11/IP300 support, SYSGEN asks the following
questions.
Consult the IP11/IP300 documentation for details on the
IP11/IP300 I/O subsystem.
*l.

Extended comments for IP11/IP300
Expanded comments provide explanatory
answer the IP11/IP300 questions.

*2.

text

that

helps

you

Treat all controllers as one unit
If you respond Yes, SYSGEN generates one SCB and one UCB to
cover all IPll controllers. This creates the appearance of a
single, large !Pll controller with all of the I/O modules
connected to it.
This option results in a loss of system
efficiency and also decreases the total number of A/D
converters to sixteen.
5-72

DETAILS OF SYSGEN PHASE I
If you respond No, SYSGEN generates one SCB and one UCB for
each
IPll
controllers.
Each controller must then be
referenced with a different LUN.
If you enter No, each
controller can support sixteen A/D converters, but the
programmer must know which controller a particular I/O module
is on as well as the module index.
For example, consider a PDP-11 that has two IPll controllers.
Controller No.
0 has one M6011 digital output module (16
points) and eight A014 A/D converter modules. Controller No.
l has two M6011 modules (32 points), one M5010 digital input
module (32 points), and three A014 modules.
If
all
controllers
are treated as one unit (Y to the above
question), the driver will cause the system to respond as if
there were only one controller with 48 digital output points
(M6011), 32 digital input points (M5010), and eleven A/D
converter modules (A014).
*3.

Any latching digital output modules
Because the IP11/IP300 device driver determines the system
configuration at bootstrap or power-up time, it is not
necessary to specify how many of each type of module are
present.
You are asked whether you have (or will ever have)
each module type so that the code to support unused modules
will not be assembled.

*4.

Any single-shot output modules

*5.

Direct output.via QIO
This option allows a task to output to digital or single-shot
output modules without overmapping the I/O page. The option
simplifies task code, but increases overhead.
Note that the direct output via QIO support is not required
in order for FORTRAN support to work. However, if present,
it will not interfere with FORTRAN support.
question appears only if you include a latching digital
output module or a single-shot output module (Yes response to
question 3 or 4).
~rhe

*6.

Any non-interrupting digital sense modules

*7.

Any interrupting digital sense modules

*8.

Any change-of-state modules

*9.

Any counter modules

*10.

Direct input via QIO
This option allows a task to perform digital input with a QIO
directive rather than by mapping over the I/O page. The
option simplifies task code, but increases overhead.

•

Note that direct input via QIO is not required for FORTRAN
support to work. However, if present, it will not interfere
with FORTRAN support.
This question appears only if you responded
more of questions 6, 7, 8, or 9.

5-73

Yes

one

DETAILS OF SYSGEN PHASE I
*11.

Unsolicited interrupt support
The M5011, M5012, and M5013 interrupting modules can produce
unsolicited interrupts when certain input bits change state.
If you select this option, the interrupts can be monitored by
a task.
This question appears only if you responded Yes to question 7
or a.

*12.

Event flag linkage to interrupts
A task can monitor digital interrupts by linking a contiguous
group of event flags to interrupting bits.
If you select
this option, the driver sets the corresponding event flag
whenever its associated bit causes an interrupt.

*13.

Any D/A converters

*14.

Any A014 A/D converters

*15.

Any A020 A/D converters

*16.

How many output bytes should be saved on powerfail

•

The answer to this query reserves table space in the
IPll/IP300 driver.
If the answer to the query is n, 4*n
bytes are reserved. This space is part of the Executive, so
available pool space is correspondingly decreased.
At powerfail time, if there is not enough space in the table
to save all outputs, the excess outputs will be lost and will
not be restored.
This question appears only if the system includes one or more
output modules and you included Executive support for power
fail recovery. Output modules are the M6010, M6012, and
M6013 Latching Digital Output modules;
the M6011 Single-Shot
Output module;
and the A630 D/A Converter module.
The acceptable range is 0-3048(10).
Enter 0 (or carriage return) to disable output restoration.
*17.

IPll vector
Enter the interrupt vector address for the first IPll
controller.
The standard vector address, and the default
va1ue, is 234. If you do not use the default assignment, the
acceptable range is 60-774. Subsequent IPll controllers are
assigned vector addresses from floating vector space and
there is no default.
Enter a value within the acceptable
range. Consult Field Service if the IPll vector address is
unknown.

*18.

Base address
Note that this question requests the IPll base address and
not the CSR address.
The base address is the CSR address
minus 377 octal.
For the first IPll controller, the default base address is
171000.
For the second IPll controller, the default base
address is 171400.

5-74

DETAILS OF SYSGEN PHASE I
The

acceptable

range

for

the

IPll

base

address

160000-177400.

The third and subsequent IPll controllers are assigned base
addresses from floating address space and do not have default
responses. Enter a value within the acceptable range.
Consult Field Service if the IPll base address is unknown.

5.7

DETAILS OF SYSGEN PROCESSING

During a system generation, SYSGEN issues command lines and displays
comment lines.
This section uses a console listing from an actual
system generation to detail and describe the command lines as well as
interpret the more obscure comment lines.
The console listing appears below.
keyed to the listing.

It is followed by notes which

5-75

are

DETAILS OF SYSGEN PHASE I
RSX-llM V3.2 BL26
>RED DI...: ::::SY:
>l=\:ED DL: ::::LB t
>MOU DI... : RSXM26
>@DL:[l,2JSTARTUP
>* PL.EASE ENTER TIME AND DATE <HR:MN DD-MMM-YY> [SJ:

>@ <ECIF>
>INS $BOO
>BOD DI...: C :L , ~!i4 J

641\
RSX-llM V3.2 BL26
MAPPED
>RED DI...: ::::S¥:
>l\:ED Dl...:::::LB:
>MOU DI...: 1:wxM26
>@DL:c1,2JSTARTUP
>* PLEASE ENTER TIME AND DATE <HR:MN DD-MMM-YY) [SJ: 12:00 23-MAY-79
>TIM 12:00 23-MAY-79
>* ENTER LINE WIDTH OF THIS TERMINAi... CD D:132.J:
>SET /BUF=Tit132.
>ACS SY:/Bl...KS=512.

>; NOTE - The Baseline INDirect must be
>;
a Prioritv of 10. for SYSGEN.

rePl~ced

bY BIGIND with

>;
>;
>;

>REM ••• AT.
>INS SBIGIND/PRI=lO.

>C~ <EDF>
>REM ••• AT.
>INS SBIGIND/PRI=lO.
INS -···.. WAl:~NING ··· PRIVIl... EGED TASK OVEl1.'.MAPS I/O PAGE
A
>INS SBIGI\I\MAC/INC=50000
~
INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN
>ASN tll.. : :::SY:
>C~SYSGEN

>; RSX-11M Version 3+2 Bl...26 Svstem Generation 3.2.2c done on 23-MAY-79 at 12:01:

>; CoPvriSht <C> 1979 Disital EGuiPment Corporation' Mavnard Mass.

>; Rl...01 distribution kit

>*
>*
>*
>*
>*
>*
>*
>*

1+
2.
3.
10.
11.
12.
13.
14.

Inhibit MCR command lines <TvPe <ESC> for exPlanation>? [Y/NJ:
Have vou made a copy of the distribution kit? [Y/NJ:Y
Use saved or canned answer file for inPut responses? CY/NJ:
Save responses (i.e.: create SYSSAVED.DAT>? CY/NJ:Y
UIC for SYSSAVED files if not C200r200J [SJ:
UIC for SYSGEN command files if not c200,200J [SJ:
Clean UP files from Previous GENs? [Y/NJ:
Device, when readvr for Executive sources (ddu:> [SJ: Dl...1:

>MOU DI... :I. t M1!:iPGl:~c;
Dl...:I. !::::l...B~
>INS SY!'.1;1::•1p

>ASN

/Fl:~

>P IF'

DLO: HAS 33:1.5. BLOCKS FREE' 6925. BLOCKS USED OUT OF :1.0240.
LARGEST CONTIGUOUS SPACE = 33:1.5. BLOCKS
HE T I U I C:::: [ :I. :I. , :I. 0 ::I

Tardet conf iduration

.. Generatind
r:·
:1.1) [ S
6
/70
RSX-1:1.S? CY/N::I:
* . Memors size (in K-word blocks) R!32.-:l.920.J: 5:1.2
* .
::{<

:I.

roce~:;<:;o r

( P. !.:!. ~

3
4

:if(

~:5

l :I. /34,

I...~:; J ....

i:~: ~'.'i ....

i'1<'!F'F'Pl'.'.1T

["(/N::I ! "(

* 6

5-76

:I. :I.

DETAILS OF SYSGEN PHASE I
>*
>*
>*
>*
>*
>*
>*
>;
>;
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*

8.
10.
11.
12.
13.
14.
15+
16.
16.
16.
16.
16+
16+
16+
16+
16+
16.
16.

Floatinm Point Processor <FP-11) Present1 CY/NJ:Y
If usinm KW11-P as swstem clock: number of intrPs+/sec. CD R:o.-1000.J:
Line fre~uencY:
A- 60 Hz
B- 50 Hz
CD: 1 A1 J CSJ:
KW11-Y Watchdom timer suPPortT CY/NJ:
Memory Parity support? CY/NJ:Y
Cache memory? CY/NJ:Y
Himhest interrupt vector <If 0 will be computed) CO R:0-774J:
For device confimuration: "*" Prints device table' •.• Terminates in~uir~
Enter devices and number of controllers for devices which re~uire drivers
Devices CSJ: DB
Devices .CSJr DK
Devices [SJ: DS
Devices [SJ: DM
Devices [SJ: DX
Devices [SJ: TT
Devices CSJ: MM
Devices CSJ: DT
Devices [SJ: DL
Devices CSJI LP
Devices CSJI •

>P Processor:11/70

:::-;

MemorY Size:512K,MaPPed

Swstem:RSX-11M

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

1.
2.
4.
5.
6.

Are wou runnins SYSGEN standalone Con the baseline swstem>T CY/NJ:Y
Is a line Printer available? CY/NJ:
Does the listinm/maP device have at least 120 columns? CY/NJ:Y
Assembly listinms device (ddu:> CD: 1 NL: 1 J [SJ:
MaP device for Executive and device drivers Cddu:> CD: SY:J CSJ:

>* EOS * Do wou want to: <CR>-continue R-rePeat section E-exit P-Pause CSJ:

>; Executive 0Ptions

>;
>;

·'-'.

.•

>*
>*
>*
>*
>*
>*
>*
>*
>;
);
>*
>*
>*
>*
>*
>;
>;
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*
>*

Answer YCES> if the followinm support is desired
1.
2.
3.
4.
5+
6+
7.
8+
11+
12.
13+
14.
15+
17.
18.
19.
20.
21.
22.
23.
24.
25.
28.
29.
30.
31.
32.
33.

Will DBMS-11 be used? CY/NJ:
FILES-11 ACP ? CY/NJ:Y
RMS record lockinm a~d Placement control? CY/NJ:Y
Non-resident tasks (task loader)? CY/NJtY
Loadable task loader? CY/NJ:Y
Memorw manamement <PLAS> directives? CY/NJ:Y
Send/Receive bw reference directives? CY/NJ:Y
Get maPPinm context directive? CY/NJtY
Address checkinm suPPort will be included
I/O rundown suPPort will be included
Multi-user Protection? CY/NJtY
ANSI Mamtape ACP? CY/NJ:Y
On-line formattinm CFMT> or on-line user-mode diaanostics? CY/Nl:Y
Loadable device drivers? CY/NJ:Y
Should the default for all aPPlicable drivers be loadable? [Y/Nl:Y
AST support will be included
Cancel selective MARKTIMEs support will be included
Task termination and device not ready messames CTKTN>? [Y/NJ:Y
Power fail re~overY? CY/NJ.:Y
InstallY reauesty and remove on exit? [Y/NJ:Y
Larse C20K> Executive? CY/NJ:Y
Losical device assimnment? [Y/NJ:Y
Lomsinm of device errors and timeouts? CY/NJ:Y
Lossins of undefined interruPts? [Y/NJ:Y
Lomminm of memory Parity errors? [Y/NJ:Y
Do you intend to include a user-written driver? [Y/NJ:
Disk writecheck? CY/NJ:Y
Executive Debusmins Tool CXDT>T [Y/NJ:Y
Rotatinm Pattern in data lishts? CY/NJ:Y
Industrial network or DECnet? [Y/NJ:
Queue manaser and aueued Print spooler? [Y/NJ:Y
Group slobal event flass? [Y/NJ:Y

5-77

DETAILS OF SYSGEN PHASE I
>;

For directives: "*"Prints table, "•" Terminates inauirw' •x• Gets all
>* 34. Enter code for directives [SJ: %.
>* 35. Number of Pre-allocated QIO Packets CD R:0.-15. D:5.J:
>* 36. Size of data transfer vector in words CD R:5.-33. D:33.J:
>* 37. Round-robin schedulins interval in ticks CD R:0.-1000. D:s.J: 0
>* 40. Executive level disk swaPPins interval ED R:o.-sooo. D:Jo.J:
>* 41+ SwaPPins Priorithl CD R:1.-20. D:5.J:
>* 42+ Size of dhlnamic storase resion. <POOL> in words ED R:256.-16384. D:1024.J:
>* 4~~. Seconds between Printer not readhl messames [D R:0.-255. D:Jo.J: 255
>* 4!'.'i. Shlstem crash resister and stack dump device CSR EO R:0-177700 D:177564J:
>* 46+ CheckPointins:
A- Yes
B- With swstem ckPnt. file
CSJ: B
>* 4/. Shlstem cntrled Partitions: A- Yes
B- With auto comPaction (SHF> (SJ: B
A- PANIC B- Crash <CDA>
(SJ: B
>* 48. Dump analhlsis:
>* 49. OutPut notification device CSR [0 R:160000-177700 D:177564J:
>* ::-;o. Memorhl dump device (ddu:> CS R:3-4J: DKO
>* ::'il. CSR address of dump device [0 R:160000-177700 D:177404J: 177400

>; Terminal driver oPtions

>;
>;
>;

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

1. Terminal driver desired CA/B/C/D, * Prints table) CSJ: A
Answer Y<ES> if the followins SUPPort is desired
3.
4.
3.
6.
7.

>* 10.
>* 11.
>* 12.
>* 13.
>* 14.
>;
>* 16.
>* 17.
>;
>;
>* 20.
>* 21.
>* 22+
>* 23.
>* 24.

P•ss form feeds directlhl to terminal? [Y/NJ:Y
Automatic carria~e return/line feed? CY/Nl:Y
Task checkPointable durins terminal inPut? CY/NJ:Y
Unsolicited inPut character AST? CY/NJ:Y
Write with CTRL/O cancellation? CY/NJ:
Breakthroush write suPPort will be included
CTRL/R suPPort will be included
Escape seauence handlins? CY/NJ:
Get multiPle characteristics? CY/NJ:Y
Set multiPle characteristics? [Y/NJ:Y
Get terminal driver oPtions? CY/NJ:Y
Hold screen mode? CY/NJtY
Transparent read/write suPPort will be included
Settable case conversion for inPut? CY/NJ:Y
Read after Prompt? CY/NJ:
Read with no echo suPPort will be included
Read with special terminator support will be included
CRT rubout SUPPort? CY/NJ:Y
Terminal-host shlnchronization? [Y/NJ:Y
User terminal inPut bufferins? CY/NJ:Y
Variable lensth terminal inPut bufferins? CY/NJ:
LA30P support? CY/NJ:

>* EOS

* Do

>!l

Th:i.nk:in!:.1

>;
>;

~au

want to: <CR>-continue R-rePeat section E-exit P-Pause [SJ:

>; End of Executive aPtion Seneration at 12:12:49 on 23-MAY-79

>;
>il
>;
>;

>Y
>?J

>Y
>;

Pc·:~ r :i. Phc·:~ ra l

conf :i. !.'.11. 1 rat :i. on

aPPearins in smuare brackets
•r ••• J• can onlhl be
for the first contr,ller of a Particular device.
Pa ramc;·~tc-:,• r•:; aPPearins in Parentheses "< ••• )• onlhl need be specified
:i. f
the-:-~
indicated oPtion is Present on the tarset s~stem.
Pa ram<-:!t<-:~ r~:;
~;; F·· (·:·~ C :i. f :i. C-:~ d

The
default for
loadable drivers has been set to *TRUE*•
To override this settins enter R <resident) as the first Parameter
for
the
first
controller
of
the
~:;P0~c :i. f i 1.-:~1:.l
A/D and Laboratorhl devices: None specified
Interprocessor communication devices: None specified

Unit record devices: LP

5-78

DETAILS OF SYSGEN PHASE I
>; Enter CL/R,J vector' CSR, Printer twPe
>;
(,[KMC timeout count <O=no KMC>, KMC vector' KMC CSRJ> for:
>;

>* 16. LP controller 0 CDt 200,177514,LA180,o,300,160130J C:SJ:
>;

,1773\3\510,LPll-C

>; Disks: DB, DK, DL, DM, DS, DT, DX
>;
>; Enter C:L/R,J vector, CSR, number of drives' unit number of first drive,
>;
CO=offset recoverw suPPort/NO=no suPPortJ for:
2. DB control l<~r 0 i::D: 254,176700,,0,oJ
:i. !!i an RP04 '0~)/li:P06 C:M
:i.!!i an li:P04, 05/RP06 rn:
52. Cort'l:.r () •Jn it 2+ ii;; an RF'04, 05/F~P06 rn:
52. Contr· 0 1..1nit ~3. is an li:P04, o:5/RP06 CD:

52. Contr 0 uni·t. o.
52. Contr 0 •Jn it :I.•

C:S:J:
'' 4
li:P06:J [SJ:
RP06J CSJ:
RP06] [8]: RP05
RP06J C:SJ: RP04

>; Enter CL/R,J vector, CSR, hi•hest unit number <O to 7> for:
>;

6. DK controller 0

>;
>; Enter CL/R,J vector,

i::D: 220,177404]

C:S:J: '177400, 3

CSR, number of drives for:

>* 3. DL controller o CD: 160,174400]
>* 53. Contr 0 unit O. is an RL01/RL02 CD: RL01l

>* 53. Contr O unit 1. is an RL01/RL02 C:D: RL01l
>; Enter CL/R,] vectorr

C:Sl: '177520r 2

c:s:i:

C:SJ:

CSR, t drivesr O=offset recoverw/NO=no offset rec. for:

>* 13. DM controller O CD: 210r17744o,,oJ

>* 54. Contr 0 unit O. is an RK06/RK07 CD: RK06l
>* 54. Contr 0 unit 1. is an RK06/RK07 CD: RK06l
>; Enter CL/R,J vectorr CSR, number of drivesr
>;

C:SJ:
C:SJ:

,,2

C:SJ:

unit number of first drive for:

>* 5. DS controller O CD: 204,172040,,oJ
C:SJ: ,172090,2
>;
SGN -- Ille•al character in numeric response -- RETRY
>* 5. DS control)er 0 CDt 204r172040r,OJ
C:SJ: ,,2
>* 57. Contr 0 unit O. is an RS03/RS04 CD: RS04J
C:SJ:
>* 57. Contr 0 unit 1. is an ~S03/RS04 C:D: RS04J
C:SJ:
>;

); Enter C:L/R,J vector, CSR, number of drives for:

3. DT controller 0 CDt 214,177342J

3. DX controller 0 CD: 264,177170]

>;
>;

[SJ: ,,2

>;
>; Enter [L/R,J vector' CSR, number of drives for:
>;
[SJ: , ,2
>* ~'1. MM cont ro 11 <·:~ r () i:n: ~.~::.~4, :t. 7~:.~440 J
formatt<·:!r [ 0 1:no . -1 D!OJ:
>* ~::;~~.:; :I.:I. •+ MM <:~<:>nt ro 11 ~;~ r ()() un:i.t
MM control l~:!r
un:i.t :I. ·ro T'm<;it t ~:~ r [Cl f~: 0 .... 7 x:i:o::i:
>*
>;
>; Non-Ph~sical (pseudo) devices: co, TT, TI, CL~ LB, SY

() I

>; Enter CL/R,J num. DL:l.:l.'s <ZL>' num. DH:l.:l.'s,-num. DZ:l.l's, num. DJ:l.:1.'s for:
>;
CSJ!

>; Enter vector' CSR for:

>* 2:1.. ZL controller 0 i:n: 60,:1.775601

CS::I:

>?
>; Ent!·:·!Y' V<·:·•ctor' CSh'.v
>;

h:i.~.'.ih<·:·!~:;t Jin<-:·! numb~:!r <Oto :l.!5>
(vanswer speed' DM:l.:1.-BB vector, DM:l.1-BB CSR> for:

>* ~.~?. DH controll~:!r O i::nt
>* 22. DH controller 1 en:

, }' ,300,0,o::i

i::s::i:

,,,300,o,0::1

i::s::i:

5-79

3:1.0,:1.60020,:1.5,,300,110500
320v:l.60040,15

DETAILS OP SYSGEN PHASE I
>* 22. DH controller 2 CD: ,,,300,0,oJ

[SJ: 330,160060,5

>* EOS * Do wou want to: <CR>-continue R-rePeat section E-exit P-Pause CSJ:

>;
>; End of interrupt vector area has been set to 400
>;
>; Create Executive build files
>PIP RSXMC.MAC=LB:RSXMCO.MAC/AP

>;
>; Assemble the Executive

>PIP [ 11, 24J/NV:::RSXASM. CMD, RSXDRVASM. CMD
>PIP RSXASM.CMD;Q/DE,RSXDRVASM;o
>REM PIP
>*

>;
>;

•

1. Do wou wish to edit anw of the Executive files? CY/NJ:

>* EOS * Do wou want to: <CR>-continue R-rePeat section E-exit P-Pause CSJ:

>;SET /COFFEEBREAK=TI: Start of Executive assemblw at 12:31:45 on 23-MAY-79
>SET /UIC=C11,24J
>MAC @RSXASM
>;SET /NOCOFFEEBREAK=TI: Executive assemblw ended at 12:56:36 on 23-MAY-79
:_::·;

EOX * Did the Executive assemble correctlw? CY/NJ:Y

>;SET /COFFEEBREAK=TI: Start of device drivers assemblw at 12:56:45 on 23-MAY-79$
>SET /UIC=C11,24J
>MAC @l:::SXDRVASM
>;SET /NOCOFFEEBREAK=TI: Device drivers assemblw ended at 13:03:55 on 23-MAY-79
>* EOX * Did the device drivers assemble correctlw? CY/NJ:Y
); Prepare for task buildin•

>INS SY:$PIP
>PIP RSX.OBS=*•OBJ
>PIP *•OBJ;*/DE/NM
>PIP RSX11M.OBJ/RE=RSX.OBS
>SET /UJ:C:::[l ,~~4]
>PIP /NV=Cll,lO:JRSXBLD.CMD
>nEM PIP

>* EDS * Do wou want to: <CR>-continue R-rePeat section P-pause [SJ:

>;
>;
>; End of SYSGEN Phase I at 13:08:54 on 23-MAY-79
>;
To continue t~Pe: @[200Y200JSYSGEN2
>¥
>SET /LJIC=[200Y200J
>f.!1 <EOF>

5-80

DETAILS OF SYSGEN PHASE I
Notes:

This is the display from the hardware
unmapped system prior to SYSGEN.

boot

[1,50]

the

This is the software boot of the [1,54] mapped system.
Preparing for SYSGEN;
remove the SK-word indirect,
install
BIGIND
(priority of 10 permits other tasks, for example PIP,
to checkpoint AT.), install BIGMAC (increment of 50000 speeds
MACR0-11 assembly operations), assign the baseline system
disk to the pseudo device SY:, and initiate SYSGEN.
Distribution kit variance.
If you are performing a SYSGEN
using the dual RK05 kit or the RLOl kit, SYSGEN mounts and
assigns the source disk to LB:.
If you are performing a
PREPGEN, you must mount and assign the source disk to LB:.
Big disk distribution kits contain
commands are omitted.

the

source

files;

the

SYSGEN then installs PIP and displays the number of free disk
blocks.

PIP command to append temporary file to the assembly prefix
file.
RSXMC.MAC
now
contains
Executive options and
peripheral components.
PIP command to copy Executive and device drivers assembly
command files from [11,10] to [11,24]. SYSGEN then issues a
PIP command to delete the assembly command files from [11,10]
and removes PIP.
At this point, SYSGEN is ready to assemble the Executive.
Depending on the host processor and the options you selected,
Executive assembly takes anywhere from 20 minutes to 2 hours.
You have two options:
A)

Go have some coffee (note that if you responded B to
target question llv you will probably have some tea).

Read on for methods of correcting DSR space
and some space saving ·tips.

'-'··

5-81

problems

DETAILS OF SYSGEN PHASE I

If you select A, go have some coffee and read the description
following note number 8.
If you select B, read the following.
During the running of RSX-llM, it is possible to exhaust
dynamic memory.
This can occur if a large number of tasks
are installed, if many volumes are mounted, of if a number of
other conditions are present.
When you exhaust dynamic
memory space, the problem manifests itself _in the lack of
response from the system. Although the system looks like it
is operating successfully, it cannot accept any MCR commands
or complete execution of presently running tasks because they
all require dynamic memory.
Another manifestation of the problem may be I/O errors being
received by tasks or failures in the Loader due to pool
allocation failures. The only solution to this problem is to
bootstrap the system and make more dynamic space available
(SET /POOL), remove tasks, mount fewer volumes, rebuild FCP
with space for more file control blocks in its partition, or
rebuild the system with more dynamic memory.
The following
memory space.

lists

potential

methods

saving

dynamic

By including the install, request, and remove on exit
capability into a generated system, considerable dynamic
memory may be saved for tasks that are initiated from a
terminal.
The MCR RUN command will install the tasks when
needed and cause them to be removed when they exit (see the
RSX-llM/M-PLUS MCR Operations Manual). Thus, task control
blocks need not be permanently allocated. Typical tasks in
this category are the program development and utility tasks
provided with the RSX-llM system, (PIP, MAC, TKB, etc.).
The use of checkpointing and nonresident tasks,
where
appropriate,
can reduce the number of tasks that are
simultaneously in memory.
This saves space in a mapped
~ystem, sine~ fewer task headers need to be copied.
The file system ACP (FllACP) may be built to store File
Control blocks in its own task image rather than in the
dynamic storage region. The more space allocated at task
build time the less the demand will be on the pool. However,
if the allocated space becomes used up, the overflow will use
the dynamic storage region.
The directory least-recently-used table default is three
18-word file control blocks. The effect of this table is a
significant increase in the speed of directory operations.
If this level of performance is not required, a volume may be
mounted using the /LRU keyword, thereby reducing the number
of FCBs used.
See the description of the Mount command in
the RSX-llM/M-PLUS MCR Operations Manual.
Now go have some coffee; SYSGEN is ready to assemble the
device drivers.
When you return, read the description
following note number 9.

5-82

DETAILS OF SYSGEN PHASE I
At this point, SYSGEN is ready to assemble the device
drivers.
Read the following for the methods of correcting
DSR space problems and some space saving tips.
During the running of RSX-llM,
it is possible to exhaust
dynamic memory.
This can occur if a large number of tasks
are installed, if many volumes are mounted, or if a number of
other conditions are present.
When you exhaust dynamic
memory space, the problem manifests itself in the lack of
response from the system. Although the system looks like it
is operating successfully, it cannot accept any MCR commands
or complete execution of presently running tasks because they
all require dynamic memory.
Another manifestation of the problem may be I/O errors being
received by tasks or failures in the Loader due to pool
allocation failures.
The only solution to this problem is to
bootstrap the system and make more dynamic space available
(SET /POOL}, remove tasks, mount fewer volumes,
rebuild FCP
with space for more file control blocks in its partition, or
rebuild the system with more dynamic memory.
The following
memory space.

lists

potential

methods

saving

dynamic

By including the install,
request,
and remove on exit
capability into a generated system, considerable dynamic
memory may be saved for
tasks that are initiated from a
terminal.
The MCR RUN command will install the tasks when
needed and cause them to be removed when they exit
(see the
RSX-llM/M-PLUS MCR Operations Manual}. Thus, task control
blocks need not be permanently allocated. Typical tasks in
this category are the program development and utility tasks
provided with the RSX-llM system, (PIP, MAC, TKB, etc.}.
The use of checkpointing and nonresident tasks,
where
appropriate,
can reduce the number of tasks that are
simultaneously in memory.
This saves space in a mapped
system, since fewer task headers need to be copied.
The file system ACP (FllACP}
may be built to store File
Control blocks in its own task image rather than in the
dynamic storage region. The more space allocated at task
build time the less the demand will be on the pool. However,
if the allocated space becomes used up, the overflow will use
the dynamic storage region.
The directory least-recently-used table default is three
18-word file control blocks. The effect of this table is a
significant increase in the speed of directory operations.
If this level of performance is not required, a volume may be
mounted using the /LRU keyword, thereby reducing the number
of FCBs used.
Now read the description following note number 9.

5-83

DETAILS OF SYSGEN PHASE I
At this point, SYSGEN has assembled the Executive and all
selected device drivers. You have had some coffee (or tea)
and read some tips on conserving DSR space. SYSGEN installs
PIP to concatenate all existing object files cataloged under
the UFO (11,24] into a file RSX.OBS. PIP then deletes all
.OBJ files and renames RSX.OBS to RSXllM.OBJ if you are
generating an RSX-llM system or to RSXllS.OBJ if you are
generating an RSX-llS system.
SYSGEN then changes the UIC and creates a new version of the
build command file in [l,24] for mapped systems or (1,20] for
unmapped systems.
You are now ready to start SYSGEN Phase II and task build the
Executive and device drivers.

..._
'J

5-84

CHAPTER 6

SUMMARY OF SYSGEN PHASE II QUESTIONS

SYSGEN Phase II
is controlled
Initiate Phase II by typing

the

command

file

SYSGEN2.CMD.

>@SYSGEN2
This chapter provides a summary of
complete details.

6.1

Phase

II.

Read

Chapter

for

SUMMARY OF SYSGEN PHASE II QUESTIONS
1.

In what UIC is SGNPARM.CMD if not [current UIC]
Enter a UIC to override the default specified in Phase I.

Expanded comments desired for SYSGEN Phase II
Enter Yes for instructions during Phase I I processing.

Is SYSGEN still running online
Enter Yes if performing an online SYSGEN.

Is SYSGEN still running standalone
Enter Yes if performing SYSGEN standalone.

If not in dev enter object files device when ready (ddu:)
Enter the device that contains
device specified in Phase I).

object

files

privileged

task

Delete (uic) to insure enough space for SYSGEN Phase II
Enter Yes to delete mapped system if running unmapped or
delete unmapped system if running mapped.
See Chapter 7.

Have you already built the libraries, the Exec, and the loadable drivers
Enter Yes to skip Executive build and start
build.

(default

Create ANSLIB to support Big-buffering
Enter Yes to create ANSLIB as if ANSI magtape support was not
includedo

6-1

SUMMARY OF SYSGEN PHASE II QUESTIONS
9.

Add the lab device's Purdue ISA routines to library
Enter Yes to include Purdue ISA routines for IC:,
AR:, or LS:
devices.

10.

IS:,

UD:,

List Executive map
Enter Yes to print map of Executive global symbols.

11.

-FCP desired (Type <ESC> for explanation)

[D:MIDDLE]

Enter the FCP you wish to include in your system.
For mapped
systems, enter NON-MULTIHEADER, SMALL, MIDDLE, LARGE, PLAS,
or OTHER.
For unmapped systems, enter NON-MULTIHEADER,
SMALL, MIDDLE, or OTHER.

12.

SYSPAR's base address in 32 word blocks
Enter the base address of partition SYSPAR. The default
300 for systems that include FCPNMH and 301 if not.

13.

Build the unprivileged queue manager utilities
Enter Yes to build the nonprivileged queue manager utilities.

14.

Build the task PMD
Enter Yes to build the Post Mortem Dump task.

15.

Build RMDEMO
Enter Yes to build the system display task RMDEMO.

16.

Build the non-queue manager print spooler
Enter Yes to build the serial despooler.

17.

Edit any privileged task build files
Enter Yes to change partition statements for
tasks.

18.

19.

Map device for privileged tasks (ddu:)

[D:NL:]

These maps are rarely needed.
if you want them.

device

Enter a

the

privileged

specification

Edit SYSVMR.CMD
Enter Yes if you are generating an unmapped system.
If you
are generating a mapped system, SYSVMR.CMD typically produces
a valid system image. See Chapter 7.

6.2

SUMMARY OF LOADABLE DRIVER BUILD PHASE

The file SGNBLDDRV.CMD controls task builder
drivers and user-written drivers.

processing

loadable

During Phase II, SYSGEN calls this file to build loadable or
user-written drivers.
However,
you can initiate SGNBLDDRV.CMD as a
command file.
If you initiate SGNBLDDRV.CMD, you must
answer
questions 1-5;
if SYSGEN calls the file, these parameters are known.

6-2

SUMMARY OF SYSGEN PHASE II QUESTIONS
1.

Are you building drivers for a mapped system

Does your system include any user written drivers

Are you building drivers for an RSX-llS system

Does your system include the KMC-LP driver

Does your system have the full duplex terminal driver

Device for driver's maps
Enter a device specification for the task builder maps of the
drivers.

Spool maps
Enter Yes if you want the maps spooled.

Does the map device have at least 120 columns
Enter Yes for wide maps, No for narrow format maps.

Build all selected loadable drivers into DRVPAR
Enter Yes to build all the drivers
system-controlled partition DRVPAR.

10.

selected

for

the

for

loadable

Driver 2-character device mnemonic
Enter the 2-character device
driver you want to build.

11.

you

mnemonic

each

Driver partition name
Enter the partition name for each driver specified in
question 10.
(Default for mapped systems is DRVPAR. Default
for unmapped systems is devPAR where dev corresponds to the
2-character device mnemonic specified in question 10.)

12.

devPAR's partition base address
Enter the base address of the specified partition.

6-3

...

Allll\,

CHAPTER 7
DETAILS OF SYSGEN PHASE II

Input to SYSGEN Phase II consists of object and build files from
SYSGEN
Phase I.
Phase II builds the user-tailored Executive,
privileged tasks and, if selected, the loadable device drivers.
At
the completion of the task builder processing, SYSGEN Phase II
attempts to define memory partitions and installs the system image on
the target volume using the Virtual Monitor Console Routine (VMR).
SYSGEN Phase II requires four files:
RSXBLD.CMD,
RSXllM.OBJ,
SGNPARM.CMD and optionally, TTDRVBLD.CMD for the full duplex terminal
driver. These files must exist on the system disk. In addition, the
files for the UDC, DRS/DSSll, or ICS/ICR-11 common blocks must also
reside on the system disk if user tasks are going to access the device
registers.
The file RSXBLD.CMD directs the Task Builder in constructing the
user-tailored Executive.
SYSGEN Phase I creates this file based on
your responses.
The file RSXllM.OBJ is the concatenated object module file produced by
PIP from the user-tailored Executive object modules following the
assembly operation in Phase I.
The file SGNPARM.CMD serves as input to Phase II. This file insures
that Phase II processing is compatible with the responses from Phase
I•

The file TTDRVBLD.CMD directs the Task Builder in constructing the
full duplex terminal driver. SYSGEN Phase I creates this file when
you select the full duplex terminal driver.
Figure 7-1 shows the processing steps that take
PhclSe I I.

·•

7-1

place

during

SYSGEN

DETAILS OF SYSGEN PHASE I I

SY:
SYSGEN.CMD

1. Invoke SYSGEN2.

SY:

SGNPARM.CMD~

2. Answer SYSGEN Phase 11
questions.

A. Task build the
executive.
B. Task build terminal
driver.
PRIVILEGED
SOURCES

C. Task build privileged
tasks.

]

]
]

Target Volume

RSX11M.TSK - - - Map Listings of:
Executive
TT Driver
Priv Tasks

D. Generate maps.

Map Listings
$SYTOP

hih

~--+---

RSX11M.TSK

3. Define your memory
layout (i.e. the relationship
of the task image and
system partitions

4. Load your device drivers,
set your partition
parameters, and install
RSX11M.SYS using VMR.

Target Volume

Drivers
Partitions
Target Volume

Processor Memory
5. Boot your system.

Figure 7-1

RSX11M.SYS

SYSGEN Phase II Processing Steps
CAUTION

It is likely that you will exhaust RLOl
disk space on the mapped (MAPSRC) or
unmapped
(UNMSRC)
source disk.
This
prevents successful completion of SYSGEN
Phase II. Therefore, it is recommended
that RLOl kit users delete unused driver
source files (for devices not included
in
the system)
from
[11,10]
before
beginning SYSGEN. The following
lists
·seldom-used devices and thus the driver
source files.

7-2

- ----4

DETAILS OF SYSGEN PHASE II
Communication devices:
XBDRV.MAC
XLDRV.MAC
XPDRV.MAC
XQDRV.MAC
XUDRV.MAC
XWDRV.MAC

DAll-B
DLll-E
OPll
DQll
DUll
OUPll

UNIBUS link
Serial line
Synchronous
Synchronous
Synchronous
Synchronous

line
line
line
line

Process I/O and Laboratory devices:
ICDRV.MAC
IPDRV.MAC
ISDRV.MAC
UDDRV.MAC
LSDRV .MAC.
LADRV.MAC
ARDRV.MAC

ICS/ICRll
IPll/IP300
DRS/DSSll
UDCll
LPSll
LPAll
ARll

Subsystems
Subsystems
Subsystems
Subsystems
Laboratory system
Laboratory accelerator
Analog module

7.1

DETAILS OF SYSGEN PHASE II

In what UIC is SGNPARM.CMD if not [current uic]
The file SGNPARM.CMD contains the parameters from Phase I
that
are necessary in Phase II. SYSGEN Phase I creates this file in
the UFD corresponding to the default UIC specified in Phase I.
Enter a UIC to override the default.

Expanded comments desired for SYSGEN Phase II
Enter Yes if you are unfamiliar with SYSGEN processing;
provide instructions during Phase II processing.

comments

Is SYSGEN still running online
This question appears only if you responded No to Host question
1.
In Phase I, you specified that you were performing an online
SYSGEN. Enter Yes if that remains true.

Is SYSGEN still running stand-alone
This question appears only if you responded Yes to Host question
1.
In Phase I, you specified that you were performing a SYSGEN
using the baseline system. Enter Yes if that remains true.

If not in dev enter object files device when ready (ddu:)
This question appears only if you are using a dual RKOS or an
RLOl distribution kit. Enter the device that contains the object
files. Note that the default device is the device for the source
files specified in Phase I. Enter a device specification if you
have moved the disk to another drive.

If you are using a single RLOl drive
object files, enter No or None.
6.

and

have

not

copied

the

Have you already built the libraries, the Exec, and the loadable drivers
Note that SYSGEN truncates this question if you did not select
loadable driver support;
you are not asked whether or not the
drivers were previously built.

7-3

DETAILS OF SYSGEN PHASE I I

This question asks whether or not the Executive has been linked
together by the Task Builder. SYSGEN Phase I does not link the
Executive, it only assembles it. Therefore, the first
time you
encounter this question, it should be answered negatively.
Typically, before a partition can be laid out for
unmapped
systems,
the user needs a Task Builder map of the newly built
user-tailored Executive. This occurs later in SYSGEN2.CMD and
may require a lengthy off-line analysis of the partition layout
for the target system. After .analyzing the partition layout,
SYSGEN2.CMD
can
be re-initiated.
If,
at this point,
an
affirmative answer is typed, the process of building libraries,
device drivers and user-tailored Executive is skipped,
and
SYSGEN2.CMD advances to the dialogue to build the privileged
tasks.
If you respond Yes to this question, SYSGEN skips questions 7-10.
7.

Delete (uic) to insure enough space for SYSGEN Phase II
This question appears
distribution kit.

only

you

are

using

dual

RK05

Disk space on the dual RK05 kits is critical.
To avoid the
possibility of running out of free disk blocks, you should enter
Yes to this question (see the Caution below).
If you are generating an unmapped system and you respond Yes to
this question,
SYSGEN deletes the files for a mapped system (in
[1,54]) from the baseline system disk (RSXM26).
If you are generating a mapped system and you respond Yes to this
question, SYSGEN deletes the files for an unmapped system (in
[1,50]) from the baseline system disk (RSXM26).
CAUTION
If you are generating a mapped system
using an unmapped system (for example,
you booted the unmapped baseline system)
and
you delete the unmapped system
image.
You have destroyed your disk.
You
must make another copy of the
distribution kit and reboot.
Likewise
if you are generating an unmapped system
using a mapped system image and you
delete the mapped system.
In other
words, if you are running standalone, do
not d~lete the running system image;
generate an unmapped system using an
unmapped system image and generate a
mapped system using a mapped system
image.
8.

Create ANSLIB to support Big-buffering
If you did not select ANSI magtape support in Phase I,
this
question permits you to get big-buffering FCS support. When you
enter Yes, SYSGEN creates ANSLIB as it would if ANSI mag tape
support was included.

7-4

DETAILS OF SYSGEN PHASE I I
9.

Add the lab device's Purdue ISA routines to library
This question permits you to include the Purdue ISA routines with
IC:, IS:, UD:, AR:, or LS: devices. See the appropriate device
documentation for more information.

10.

List Executive map
The Executive map defines the Executive global symbols and their
locations
in memory.
These locations are used to layout
partitions.
If you are generating a large mapped system, the map
is not necessary.
If you are generating an unmapped system, the
map is required so that you know where to build the drivers.
If you respond Yes, SYSGEN prints or spools the map on
printer (if the system includes one) or terminal.

11.

the

line

support

FCP desired (Type <ESC> for explanation)
This question appears only if you selected
Phase I.

Files-11

Mapped RSX-llM systems support five versions of the file system:
•

2K-word non-multiheader (disk overlayed)

•

2.25K-word multiheader (disk overlayed)

•

SK-word fast multiheader (disk overlayed)

•

6.SK-word optimized multiheader (disk overlayed)

•

lOK-word resident (memory-resident overlayed)

Unmapped RSX-llM systems
system:

support

three

versions

the

file

This question permits you to select the FCP best suited
application needs and memory limits.

your

•

2K-word non-multiheader (disk overlayed)

•

2.25K-word multiheader (disk overlayed)

•

SK-word fast multiheader (disk overlayed)

The non-multiheader version (FCPNMH) is the m1n1mum size FllACP.
This FCP restricts files to a maximum of 26,112 blocks of 512
bytes (no multiheader files) and does not support RMS
record
locking.
Use FCPNMH with DECtapes, floppy disks, or with small
unmapped systems;
additional use in a large or multiuser system
is not recommended.
SYSGEN builds FCPNMH to run in partition
SYSPAR, which is 10000(8)
bytes long.
For unmapped systems,
SYSPAR starts at 30100(8).
If you want to change partition
parameters for FCPNMH, you must edit the build command file.
Enter NON-MULTIHEADER to select this version.
(FCPNMH is the
default for unmapped systems.)
The multiheader version (FCPSMO)
is a full
functionality and
heavily overlayed FllACP. Use FCPSMO with a small memory system.
Enter SMALL to select this version.

7-5

DETAILS OF SYSGEN PHASE II
The fast multiheader version (FCPMDl) stores as many File Control
Blocks (FCBs) as possible in its task image before overflowing
into the dynamic storage region.
Use FCPMDl for applications
which use the file system in a heavy open/close and read/write
environment; this version treats file creates, deletes, and
extends as secondary operations.
Enter MIDDLE to select this
version, (FCPMDl is the default for mapped systems.)
The optimized multiheader version (FCPLGl)
is a larger, less
overlayed FllACP and is not supported on unmapped systems. This
version limits disk overlay activity to exception cases and file
deletions.
Use
FCPLGl
for
development
systems and in
applications which extensively use the file system to create and
extend files.
FCPLGl is recommended for systems without strict
memory limitations as well as an alternative to a memory resident
structure for systems with limited memory. Enter LARGE to select
this version.
The resident version (FCPR02) is supported only on mapped systems
that include Executive support for memory management directives
(PLAS). This version eliminates disk overlay activity.
Use
FCPR02 for development systems and other high performance systems
that extensively use the file system to manipulate files.
Enter
PLAS to select this version.
When you select the FCP that best fits your memory limits, you
can consider Task Builder options that improve FCP performance.
For all versions except FCPNMH, the distribution kits include
multiple build command files for the FCPs. This permits you to
tailor an FCP, but does not require you to edit the build command
files.
To build a tailored FCP, enter OTHER in response to this
question; SYSGEN will pause prior to building the privileged
tasks to allow you to specify the FCP build command file that
best suits your application needs. The following lists the FCP
build command files and summarizes the task builder options of
each.
FCPNMHBLD.CMD
Size: 2.0K
No task builder options
FCPSMOBLD.CMD
Size: 2.25-2.5K
FCBs: 0
Shared directory buffer: 1 block
FCPSMlBLD.CMD
Size: 2.75-3.0K
FCBs: 32
Shared directory buffer: 1 block

,$'If~

7-6

DETAILS OF SYSGEN PHASE I I
FCPMDOBLD.CMD
Size: 3.6-4.0K
F'CBs: 0
Shared directory buffer: 1 block
FCPMDlBLD.CMD
size: 5.0-5.25K
FCBs: 32
Separate directory buffer: 3 blocks
FCPMD2BLD.CMD
Size: 6.l-6.4K
FCBs: 64
Separate directory buffer: 5 blocks
FCPLGOBLD.CMD
Size: 4.75-5.0K
FCBs: 0
Shared directory buffer: 1 block
FCPLGlBLD.CMD
Size: 6.4-6.7K
Io'CBs: 32
Separate directory buffer: 4 blocks
FCPLG2BLD.CMD
Size: 8.3-8.6K
FCBs: 64
Separate directory buffer: 8 blocks
Also includes separate buffer for index file bitmap
FCPLG3BLD.CMD

•

Size: 9.6-9.9K
FCBs: 128
Separate directory buffer: 12 blocks
Also includes separate buffer for index file bitmap
FCPCOOBLD.CMD
Size: 6.0-6.25K
FCBs: 0
Separate directory buffer: 0 blocks

7-7

DETAILS OF SYSGEN PHASE I I
FCPROOBLD.CMD
Size: 6.75-7.0K
FCBs: 0
Separate directory buffer: 1 block
FCPROlBLD.CMD
Size: 8.0-8.25K
FCBs: 32
Separate directory buffer: 4 blocks
FCPR02BLD.CMD
Size: 9.8-10.lK
FCBs: 64
Separate directory buffer: 8 blocks
Also includes separate buffer for index file bitmap
FCPR03BLD.CMD
Size: 13.0-13.25K
FCBs: 123
Separate directory buffer: 12 blocks
Also includes separate buffer for index file bitmap
For systems with several high-performance disks, it is possible
to increase file system throughput by mounting each volume with a
separate FllACP. Distinct ACPs allow a separate pool of FCBs for
each disk volume in each FllACP partition, and allows overlapping
directory requests on each volume.
The ACP default
name
algorithm of the Mount command simplifies specifying separate
ACPs
(see the RSX-llM/M-PLUS MCR Operations Manual).
For
example,
if your system includes DECtape, install a separate
version of FllACP
(the non-multiheader version,
FCPNMH,
is
adequate for DECtapes) with the name DTOlFl, the primary defauLt,
or DTAACP, the secondary default.

•

7-8

DETAILS OF SYSGEN PHASE II
NOTE
It is recommended that file system not
share a user-partition with tasks that
perform file-structured I/O, especially
in systems with minimal user memory.
The operation of RSX-llM is heavily
dependent on the file system. Nearly
all tasks request processing from it.
Thus,
for a system to operate properly,
the file system must be in a partition
where it can react promptly. Most tasks
request an I/O operation through FllACP,
and while this I/O operation is in
progress,
the
tasks
cannot
be
checkpointed.
Thus,
if
FllACP is
running in the same partition,
it may
not be able to be loaded into memory to
process the request and a
deadlock
situation can occur.

....

12.

SYSPAR's base address in 32 word blocks [100:1700:N]
This question appears for unmapped systems only. Note that the
default response
(N) is determined by the FCP you selected (300
for FCPNMH, 301 for another FCP).
SYSGEN uses the response to this question in a nominal attempt to
ease user burden in an unmapped system generation. SYSGEN
creates a file (SYSPAR.CMD) which contains the base address and
length of parition SYSPAR. However, SYSGEN cannot determine the
exact location for partition SYSPAR.
You should consult the map
of the Executive to determine where the Executive ends and thus
where to begin SYSPAR (symbol $SYTOP in the map of the Executive
is the highest Executive location).

13.

Build the unprivileged queue manager utilities
The response to this question specifies whether or not the
nonprivileged queue manager utilities are built by Phase II.
Appendix D describes the queue manager.

14.

Build the task PMD
The response to this question specifies whether or not the Post
Mortem Dump task is built by Phase II. The RSX-llM/M-PLUS Task
Builder Manual describes the PMD task.

15.

Build RMDEMO
The response to this question specifies whether or not the RMDEMO
task is built by Phase II. Appendix B describes RMDEMO.

'
16 ..

Build the non-queue manager print spooler
If you did not select support for the queue manager in Phase I,
this question permits you to build the serial despooler (V3.l
spooler).

7-·9

DETAILS OF SYSGEN PHASE I I
The serial despooler prints listings simultaneously with the
operat~on
of other tasks. The MACR0-11 assembler, Task Builder,
and FORTRAN compilers try to spool all listings or map files to
disk.
If neither the serial despooler nor the queue manager are
installed, the files remain on disk.
If the serial despooler is
installed, it is started and thus prints any files in its receive
list.
For optimum operation, the serial despooler should occupy its own
2K partition, although this is not necessary if the GEN partition
is large.
It can be built checkpointable or not checkpointable.
Under normal circumstances, the serial despooler deletes only a
small class of files after printing.
You can build a deleting
serial despooler by editing the
task-build
command
file
PRTBLD.CMD;
locate the line GBLPAT=PRT:$DELET and change it to
read GBLPAT=PRT:$DELET:l.
You may supply an alternative file deletion algorithm and include
it in task PRT. The module should define the global entry point
$DELCK. The routine is called with register RO containing the
FOB of the file just printed. On return, RO must be preserved
and the processor status C-bit should be set to indicate that the
file is to be deleted.
Use of this feature bypasses all of PRT's default file deletion
logic.
To include this module, insert it in the object library
PRT.OLB, and edit the task-build command file
PRTBLD.CMD,
deleting the following line:
GBLDEF=$DELCK:O
Before a file is printed, an identification page is generated.
This page contains the RSX-llM version number;
the date and
time;
and the device, UFO, and name of the file being printed.
In addition, the file name is printed in large block letters for
readability.
Two formats are available,
a large one
for
132-column printers, and a smaller one for SO-column printers.
identification page by
You may build PRT to omit the file
modifying a global patch in the task-build command file as
follows:
*F GBLPAT=PRT:$FLAG
GBLPAT=PRT:$FLAG:l
*C/l/O/
GBLPAT=PRT:$FLAG:O
Note that the value specified in the GBLPAT statement is used to
determine
the
number of title pages printed.
There are
additional options for specifying flag page size and the number
of trailing form feed characters to be printed. The task-build
command file, PRTBLD.CMD, contains detailed commentary concerning
these options.
SYSGEN then displays a list of the build
tasks to be built and asks question 17.

7-10

files

for

the

privileged

DETAILS OF SYSGEN PHASE I I
17.

'--"}

Edit any privileged task build files
A Yes response causes SYSGEN to pause to allow selective
of the privileged task build command files.
For mapped systems, it is not required that
build command files.

you

edit

editing
the

task

For unmapped systems, you may have to edit the privileged task
build command files so that the partition statements reflect
actual base addresses. All of the tasks to be built have task
build command files that specify either partition SYSPAR, GEN, or
PAR14K.
You specified the base address of SYSPAR in question 12.
Thus you do not have to edit the SYSPAR partition statement.
Partition GEN is assumed to be based at 40000(8)
and to be
40000(8)
bytes long.
You must edit the build command files if
this assumption is inaccurate. Also, partition PAR14K is assumed
to start at 40000(8) and to be 70000(8) bytes long.
The privileged tasks must always be rebuilt when the Executive
has been rebuilt.
The privileged tasks are linked to the
Executive symbol table file and map into the Executive address
space so that they may access various system lists and data
structures.
If the Executive is changed, these addresses change;
thus, the tasks have to be rebuilt.
The Line Text Editor (EDI) may be used to examine the PAR command
line in each file that may require modification.
Every file in
question must be checked, since a Partitions command which does
not reflect the requirements of the user-tailored system can
produce tasks which will not run or could crash the system.
For an unmapped system, tasks built to run in
proper task builder command.
Those built
partition specify

SYSPAR have the
to run in the GEN

PAR=GEN:40000:40000
For mapped systems, the respective commands are:
PAR=SYSPAR:O:lOOOO
PAR=GEN: 0: 40000
If alteration is necessary, the change may be accomplished as
shown below.
Suppose,
for example, the GEN subpartition is to
start at 50000(8). The above sequence would be changed to:
>EDI BOOBLD.CMD
[PAGE l]
*L PAR
PAR=GEN:40000:40000
*C/N: 4/N : 5
PAR=GEN:50000:40000
*EX
[EX! T]
There are two versions of MCR:
a single user version, MCR;
and
a multiuser version, MCRMU. The single user version processes
commands serially and runs in partition SYSPAR.
The multiuser
version consists of two tasks,
MCRMU and SYS.
Task MCRMU
receives commands in serial, but passes most on to task SYS for
processing.
The
multiuser
version achieves a degree of
parallelism since multiple copies of task SYS can be running (one
for each terminal).
Task MCRMU runs in partition SYSPAR while

7-11

DETAILS OF SYSGEN PHASE I I
task SYS runs in GEN.
Edit the task build command files to
change partition statements.
(Note that MCRMUBLD.CMD controls
the task-build of both MCRMU and SYS.)
The default partition for TKTN is SYSPAR.
edit the build command file.

Normally, you need not

The tasks BOO, DMO, AT., IN!, INS, LOA, MOU, SAV,
UFD,
and
UNL
build to run in GEN.
For unmapped systems, you will have to edit
the build command files
if partition GEN does not start at
40000 (8).
18.

Map device for privileged tasks (ddv:)

[D:NL:]

Usually, these maps are of little use to the mapped system user
and are not needed. The default response directs the maps to the
null device.
For an unmapped system user, the maps are of use if
you want to determine the exact size of the tasks.
If you want the maps, enter a device specification. Note that if
you enter other than LP:, SY:, LB:, TI:, or TT:, the device must
be mounted and a UFD entry of
[1,30]
for unmapped systems or
[1,34] for mapped systems must exist.
19.

Edit SYSVMR.CMD
SYSGEN Phase II creates a file
(SYSVMR.CMD)
to create the
partition structure, install tasks, and load loadable drivers.
This question permits you to edit the SYSVMR.CMD file.
For mapped systems, it is not necessary to edit this file;
although
it
may not produce an optimal system on small
configurations.
SYSVMR.CMD typically produces a valid mapped
system image.
The following depicts a mapped system partition
structure that results from executing SYSVMR.CMD

DEV common
(optional)

GEN

FCPPAR
(optional)
SYSPAR

DRVPAR
(optional)
TTPAR
(optional)
LDRPAR
(optional)

Executive

7-12

DETAILS OF SYSGER PHASE I I
For mapped systems, SYSVMR:
o

Extends pool space to the maximum size of the Executive
(either 16K or 20K).
If you do not want to use the
maximum amount of pool, edit SYSVMR.CMD;
locate the line
SET /POOL=* and change the wildcard specification to use
the value of $SYTOP rounded up to the next 32-word block.

If you selected the loadable loader, creates the partition
LDRPAR and installs and fixes the loader in it.

If you selected the full duplex terminal driver,
creates
partition TTPAR and loads the terminal driver into it.

If you selected loadable drivers, creates partition DRVPAR
and loads all loadable drivers built during the running of
Phase II into it.
If you do not want to load all drivers,
edit SYSVMR.CMD;
delete the load command for each driver
you wish to exclude. Note that you should load the system
disk driver first so that you can boot the system from an
unmapped system.

""1'.

NOTES
If you are restarting SYSGEN Phase II
(you
responded
Yes to question 6),
SYSGEN cannot determine which drivers
were built for the system. Therefore,
you must edit SYSVMR.CMD and insert the
load commands for the drivers.
SYSGEN uses wildcards
(*)
to create
DRVPAR's size as the sum total of all
drivers loaded at VMR time.
If you wish
to allow space for other drivers, edit
the partition statement and
specify
sufficient space.
Rather than delete command lines that
load drivers that you do not need, it is
suggested that you insert a semicolon
(;)
at the beginning of the line.
(VMR
treats such lines as comments.)
o

Creates partition SYSPAR
installs FCPNMH into it.

and,

you

If you selected other than
FCPPAR and installs the FCP.

Creates partition GEN (from end of last partition
of memory)

If you selected direct access to device registers for
IP11/IP300,
ICS/ICR,
UDCll,
or DSS/DRS devices, creates
DEV common, which overmaps the I/O page to permit direct
access to the device registers.

FCPNMH,

selected
creates

FCPNMH,
partition
to

top

For unmapped systems, it is not possible for SYSVMR.CMD to create
an ()ptimal partition structure; ·you must edit SYSVMR.CMD.
The
foll()wing depicts an unmapped 16K to 24K system that results from

7-13

DETAILS OF SYSGEN PHASE I I
executing SYSVMR.CMD.
Note that
does not create driver partitions.

for unmapped systems, SYSVMR

devPAR

1000
GEN
400
SYSPAR
300,301
Executive
0

For unmapped 16K -

24K systems, SYSVMR:

•

If you selected other than FCPNMH, establishes the top of
pool and the Executive at location 30100. If you selected
FCPNMH, establishes the top of pool and the Executive at
location 30000.

•

Creates partition SYSPAR. The base address, and thus the
length, depends on the FCP you selected. For FCPNMH,
SYSPAR starts at 30000 and is 10000 bytes.
For other than
FCPNMH, SYSPAR starts at 30100 and is 7700 bytes.

•

Creates partition GEN and attempts to
into it.

install

all

tasks

The following depicts an unmapped 24K-28K system that results
from executing SYSVMR.CMD.
Note that for unmapped systems,
SYSVMR does not create driver partitions.

devPAR

FCPPAR
(optional)
1300
PAR14K

1000

GEN
400

SYSPAR
300,301
Executive
0

7-14

DETAILS OF SYSGEN PHASE II
For unmapped 24K-28K systems, SYSVMR:

7.2

•

Establishes the top of pool and the Executive at location
30100 for other than FCPNMH or at location 30000 for
FCPNMH.
Be sure that this location is above the Executive
{for example, $SYTOP).

•

Creates partition SYSPARe The base address, and thus the
length,
depends on the FCP you selected. For FCPNMH,
SYSPAR starts at 30000 and is 10000 bytes.
For other than
FCPNMH, SYSPAR starts at 30100 and is 7700 bytes.

•

Creates partition PAR14K {base address is 40000, length is
70000 bytes)
and a subpartition GEN
{base address is
40000, length is 40000 bytes).

•

If you selected
FCPPAR.

other

than

FCPNMH,

creates

partition

DETAILS OF LOADABLE DRIVER BUILD PHASE

This section provides details for SYSGEN processing of loadable driver
task-build command files.
The file SGNBLDDRV.CMD controls the task building of loadable
and also permits incorporation of user written drivers.

drivers

This command file executes during SYSGEN Phase II when your system
includes loadable drivers or if you specified that you wish to include
a user written driver. Note that the file can be used by itself to
aid in task building {or re-task building) drivers.
If you initiate SGNBLDDRV.CMD, you must answer questions
SYSGEN calls the file, these parameters are known.

Are you building drivers for a mapped system

Does your system include any user written drivers

Are you building drivers for an RSX-118 system

Does your system include the KMC-LP driver

Does your system have the full duplex terminal driver

Device for driver's maps
Unmapped systems require these maps.
If you are
unmapped system, the default map device is SY:.

1-5;

generating

Typically, mapped systems do not require these maps.
If you
generating a mapped system, the default map device is NL:.

are

NOTE
If you want (or require)
the maps and
specify a device other than SY:, LP:,
LB:, TT:, or TI:, SYSGEN requires that
the device be mounted, ready, and that
the proper UFO
{[l,30]
for unmapped,
· [l ,34]
for mapped)
exists. Also, the
driver must be loaded~

7-15

DETAILS OF SYSGEN PHASE II
7.

Spool maps
This question does not appear if SYSGEN calls SGNBLDDRV since you
specified whether or not to spool listings and driver maps in
Phase I.

Does the map device have at least 120 columns
This question does not appear if SYSGEN calls SGNBLDDRV since you
specified whether or not the map device has 120 columns in Phase
I•

If you enter No, the task builder uses the /-WI switch
narrow maps.
9.

Build all selected loadable drivers into DRVPAR
This question appears for mapped systems only.
Normally, all
loadable drivers in a mapped system are built to run in partition
DRVPAR.
If you enter Yes, SYSGEN builds all the
selected in Phase I for partition DRVPAR.

loadable

drivers

you

If you enter No, SYSGEN prompts for the drivers you want to build
(see question 10).
10.

Driver 2-character device mnemonic
This question appears for unmapped systems and all systems that
include user written drivers. The question also appears if you
are generating a mapped system, but do not want to build all
selected drivers or if you wish to build mapped loadable drivers
for other than partition DRVPAR (responded No to question 9).
Enter the 2-character device mnemonic for each loadable driver
you want to build. SYSGEN then prompts for the partition name
(in question 11). When complete, enter carriage return.

11.

Driver partition name
The default for mapped systems is partition DRVPAR.
The default for unmapped systems is partition devPAR where dev is
the 2-character device mnemonic specified in question 10.
For unmapped systems, consider building the system disk driver
for
the
partition that corresponds to 2-character device
mnemonic. This is also recommended for other drivers that run in
their own partition (for example, TTPAR). A suggested partition
name for less frequently used drivers is DEVPAR. You can Load a
driver as you need it (after unloading other drivers).

12.

devPAR's partition base address
This question appears for unmapped systems only.
Enter the base address of the specified partition.

7-16

DETAILS OF SYSGEN PHASE II
7.3

DETAILS OF SYSGEN PHASE II PROCESSING

During a system generation, SYSGEN issues command lines and displays
comment lines. This section uses the console listing from the SYSGEN
described in Chapter 5 to detail and describe the command lines as
well as interpret the more obscure comment lines.
The console listing appears below.
keyed to the listing.

It is followed by notes which

7-17

are

DETAILS OF SYSGEN PHASE I I
>@SYSGEN2
>; RSX-11M Version 3.2 BL26 Swstem Generation Phase II

>; CoPwriSht <C> 1978 DiSital E~uiPment Corporation' Mawnard Mass.
>; SYSGEN Phase II started at 13:10:31 on 23-MAY-79

1. In what UIC is SGNPARM.CMD if not [200,200J [SJ:

>; RLOl distribution kit SYSGEN versions 3.2.2c I 2:3.2.2c
>; Continuation from SYSGEN Phase I done on 23~MAY-79 at 13:00:18

>*
>*
>*

2. Expanded comments desired for SYSGEN Phase II? [Y/NJ:
4. Is SYSGEN still runnin• stand-alone? [Y/NJ:Y
5. If not in DL1: enter obJect files device when readw (ddu:> [SJ:

>MOU DLl:MAPSRC
MOU -- OTHER VOLUME MOUNTED ·- DL..1 :
>ASN DL l. : :::LB:
>ASN SY: :::Tl'\:
>INS SYaPIP
>PIP /FR

DLO: HAS 2957. BLOCKS FREE, 7283. BLOCKS USED OUT OF 10240.
LARGEST CONTIGUOUS SPACE ::: 2750. BLOCKS

6. Have wou alreadw built the libraries, the Execr and the loadable drivers? [Y/NJS

>;
>; Start of Executive and driver build Phase at 13:11:44 on 23-MAY-79
>; Create swstem libraries

>•>INS $LBR

>SET /UIC=Clrl:l
>PIP ANSLIB. OLB/NV::sSYSLIB. OL.B •
>LBR ANSLIB/RP=LB:FCSMTA
MODULE 'ANSPAD" REPLACED
MODULE

ASSLUN

REPLACED

MODULE "BIGBUF' REPLACED
MODULE 'CLOSE

1:;:EPLACED

MODULE "CREATE" REPLACED
MODULE "DIRECT" HEPL.ACE[I
MODUl. . E "GET
MODULE

"GETSG

MODULE "OPEN

" REPLACED

.
ff

REPLACED
1:;:EPl...ACED

MODULE

"DF'FID

MODULE

"DPFNB

" 1:;:EPL.ACED

MDDLJl...E

"POINT

MODULE

"F'UTSQ " REPLACED

1:;:EPl...ACED

!':FPL.ACED

PUT

MODULE "l:;:DWAIT" 1:;:E:Pl...ACED
MODULE

"1:~ETADfi:"

1:;:EPl... ACED

MODULE

1:;:wBLI(

1:;:EPl...ACFD

MODULE

"WATSET" 1:;:EPl...ACED

MODULE

"WTWAIT"

1:~EF'l...ACED

7-18

]-----------------------------------~~~~~~~~~~~~~~~

DETAILS OF SYSGEN PHASE II
>BET /UIC•[1,24J
>PIP RSX11M+OLB;*/DE/NM
>L.BR 1:;:sx1lM/CR:80.: 640.: 2~7i6. •[ 1 l , :.;!4JRSX11M. OB ..I •
>REM PIP
>INS SY: $BIGTKB
INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN

>; Taskbuild the Executive

>INS SY:$PIP
>l:•IP r.:t,~~4J*•*;*/DE/NM
>REM P J:F•
>TKB @HSXBLD

>* EOX * Did the Executive build successfull~T CY/NJ:Y

>SET /UIC=[1,54J
>INS SY: $PIP
A
>PIP LB:/NV=RSX11M.STB ~
>REM PIP
>INS' SY:$PIP
>* 10+ List Exe~Jtiva maP? CY/NJ:

>; Build Loadable drivers

>*
>*

6. Device far driver's maps CD: NL:J CBJ:
9. Build all selected loadable drivers into DRVPART CY/NJ:Y

>SET /UIC•[1,24J
>TKB @[200,200JTTDRVBLD
>PIP C200,200JTTDRVBLD+CMD;*/DE
>PIP f.1,54JTTDRV+STB/TR
>TKB @.[200,200JDBDRVBLD
>PIP [200r200JDBDRVBLD+CMD;*/DE
>PIP C1r54JDBDRV.STB/TR
>TKB @r.200,260JDKDRVBLD
>PIP C200,200JDKDRVBLD.CMD;*/DE
>PIP Clr54JDKDRV+STB/TR
>TKB @C200,200JDLDRVBLD
>PIP r.200,200JDl...DRVBLD+CMD;*/DE
>PIP [1,54JDLDRV.STB/TR
>TKB @C200,200JDMDRVBl...D
>PIP r.200,200JDMDRVBLD+CMD;*/DE
>PIP [1,54JDMDRV.STB/TR
>TKB @C200,200JDSDRVBLD
>PIP C200,200JDSDRVBLD.CMD;*/DE
>PIP [1,54JDSDRV.STB/TR
>TKB @[200r200JDTDRVBLD
>PIP C200,200JDTDRVBLD+CMD;*/DE
>PIP [1,54JDTDRV.STB/TR
>TKB @[200,200lDXDRVBLD
>PIP r.200,200JDXDRVBLD.CMD;*/DE
>PIP Clr54JDXDRV.STB/TR
>TKB @[200,200JLPDRVBLD
>PIP C200,200JLPDRVBLD+CMDl*/DE
>PIP [1,54JLPDRV.STB/TR
>TKB @l200,200JMMDRVBLD
>PIP l200,200JMMDRVBLD.CMD;*/DE
>PIP C1,54JMMDRV.STB/TR
>;
>; End of library, Executive and driver build Phase at 13:25:50 an 23-MAY-79

}; Task Build the Privilemed tasks
>Y
>* 11+ FCP desired CTYPe <ESC> for exPlanation> [D! MIDDLEJ [SJ:
>* 13. Build the unPrivilesed oueue manamer utilities1 CY/NJ:Y
>* 14, Build the task PMD1 lY/NJtY
>* 15. Build RMDEMO? CY/NJ:Y
>* 17, Edit anY Privileged task build files1 CY/NJ!
>* l n. MdF' d<-:·'V :i. Ci:·:·! for p Y' :i. ,,,, :i. l (·:·~~.'.l(·:·!o'.'.i ta!:;k ~:; ( o'.'.ld•..1: ) [ D: NL.: J [ s J:

7-19

DETAILS OF SYSGEN PHASE I I
>;
>ASN NL.: ::::MP:
>ASN LB: ::::SY:
>ASN •::f...B:
>ASN ::::SY:
>ASN Dl...1 : ::::SY:
>ASN flLO: :::L.B:
>TKB @BOOBL.[I
>n<B @DMOBLD
>TKB @FCPMD 1 Bl...D
>TKE1 CHNDBl...D
>TKB @INIBLD
>TKB @INSBLD
>TKB @MCRMUBL..D
>TKB @MOUBl...D
>TKB @CmGBUt
>TKB @CmGCLIBLD
>TKB CWMGPRTBL.D
>Tl\B @LPPBl...fl
>TKB @F:l.1.MSGBLD
>TKB @MTABLD
>Tl\£< C~SAVBU•
>TKB @TKNBLD
:::>fKB @UFDBL[I
>TKB @LOABLI•
>Tl\B @UNLBLD
>TKB @PMDBU•
>TKB @RMDBLD
>TKB @Sl-IFBl...D
>TKB @ACNTBLD
>TKB @BYEBUt
>TKB @HELBLD
>TKB @BROBL..D
>TKB @SHUTUF'BLD
>TKB @ACSBLD
>TKB @ERFBLD
>TKB @ERLBLD

GENERATING SMALL. INDIRECT

·~--

>* EOX * Did the Privilesed tasks build successfullw? CY/NJ:Y

>REM TKB
>ASN LB: :=SY:
>ASN ::::LB:
>ASN =SYt
>ASN DLO t ::::SY:
>ASN nu.: :::LB:
>SET /UIC=C1,54J
>PIP /Fli:
£tl.O: HAS 12~13+ BLOC~~S Fli:Et~:, B98l+ flL.OCKS USED OUT CJF 10240.
LARGEST CONTIGUOUS SPACE = 1017+ BLOCKS

>;
>;
>;
>;
>;
>;
>;

SGN -- SYSGEN will now Pause to allow you to create wour
RSX1:1.M.SYS file using the followins exaffiPle. Ideally
Your swsteffi it should occupy the saffie nuffiber of blocks
as indicated in the exaffiPle.
PIP RSX:l.1M.SYS/NV/CO/BL:498.=RSX11M+TSK

AT.
PAUSING. HI CONTINUE TYPE •RES ••• AT•
PIP RSX11M.SYS/NV/CO/Bt...:498.~RSX11M.TSK
>RES ••• AT+

AT+ -- CONTINUING
>F~EM

PIP

>* 19. Edit SYSVMR+CMD? [Y/NJ:
>INS SY:$B()Cl;·-·i
>I NS ~>VMI:~; ·- l
>AHN SY: ::::l...J:l:
>VMr~

7-20

DETAILS OF SYSGEN PHASE II
ENTER FILENAME: @SYSVMR
VMF~ --· INSTALL.ED TASl"\S MAY NO 1...0NGEli: FIT IN PAIHITHIN
SET /TOP=DRVPAR:-*
POOl...=1200:5870+:05870+
L.Dli:F'Ali: 1:I.77;34 00 :I. :.wooo 00002400 MAIN TASK
DRVPAF~ :1.17420 00122400 000~50400 MAIN SYS
1:1.73:::;4 0 0 1 ::.! :~ 4 ()() 0000:.woo SUB DRIVER - DB:
:1.:1.72!'54 ()() 1 ~?.4400 0000:1.1()0 SUB DRIVER - DK:
:L 17:t.::i4 00:1.2~5~.'iOO oooo:uoo SUB DRIVER - DL:
1170!7i4 00127600 oooo:.;!~5oo SUB DRIVER - DM:
:t.167~.'i4 001;32~500 OOOOl.000 SUB
DRIVER - DS:
:t. :l.66~.'i4 001;B;300 000011.00 SUB DRIVER - DT:
1 :l.6~5!'.i4 00 :I. ~54400 00001400 SUB DRIVER - DX:
1164:'.'i4 ()() Bf.1000 0000:1.100 SUB DRIVER - LP:
1163!'.i4 00 :I. 37 :I. 00 0 0 ()() :3'7 0 0 SUB DRIVER - MM:
:I. :LC, 2 !'.'i 4 00 :I. 430()0 00010000 SUB DRIVER - TT:
SYSPAf~ :l.1!'.i6~:i4 001. !'.'i:3000 00010000 MAIN TASK
FCPPAli: :l :l!'.'i6 :t.O 0016:3000 00024000 MAIN SYS
GEN
115544 00207000 0;3571000 MAIN f,lYS
+l...DR 1.1
:I. l 76:34 L.Dli:PAR ~~48. 00002400 L.B0:-00016770 FIXED
ncrn
0~5. 94
:l.12~544 SYSPAR 248. 00010000 1...B0:-000201.65
,.,,.,,
.li:MD V01
,,... ,:..d+
:t:l.4644 GEN
00040000 1...B0:-0002:1.331
MTA1~C:P 0010
l.14044 GEN
'.~.!00. 000:1.3500 LB0:-00021064
••• :OMO ~?.2. 0() :Ll4344 GEN
160. 00040000 1...B0:-0001736'7
02. ()1. :I. :I. ;·5~.!44 SYSPAF~ 160+ 00010000 1...B0:-00020241
MCli:+
1.60+ 00040000 l...B0:-00020202
•+MOU 2::?. + :1.~.:; :1.:1.2744 GEN
.MCR O:L
l.12444 GEN
:1.60. 00020000 l...B0:-00020400
F:l.:l.1ACP Mo;·5:.:.!o :I. :l.~5444 FCPPAR 1.49+ 00024000 LB0:-00017605
PMD.
O~i
:1.:1.3444 GEN
140. 00020000 LB0:-00021444
SHF.
04
:t.12~.'i44 SY SPAR 10!'.'i. 00010000 l...B0:-00020304
• INS 04
:1.B~'i44 GEN
:1.00. 00040000 1...BOt-000:1.7657
• SAV 04. :.;!2 :1.:1.:u,44 GEN
100 • 00040000 l...B0:-00021233
.UFD V04 :I. 0 :l.1~.!244 GEN
100. 00040000 1...B0:-00020265
cmc-;.
·n5. 00040000 1...eo:-00020575
01+04 :l.:t.!'.);344 GEN
F'RT,
0:1.. 0 l
:I. :1.~'i044 GEN
'70 • 00001100 1...B0:-00020147
l...PPO
O:L.06 :1.14744 GEN
70. 00040000 1...eo:-00021000
.AT+ 04. 2:'.'i :1.:1. 3'744 GEN
6:'5. 00040000 1...B0:-0002000:1.
+Eli:F 02
:1.:1.4244 GEN
6:1.• 00040000 1...B0:-000201.75
60 • 00040000 LB0:-00020105
• INI 20. 0 :I. :1.:1.3644 GEN
!'.'i(). 00040000 1...eo:-eoo20650
• CHJE :I.• 0
:1.:1.~.'i244 GEN
.p1:n :I. • 0
:l.1!'.'i:l.44 GEN
!'50 • 00040000 LB0:-00020650
:t:l.4!544 GEN
+ACS 0 :I.
~:iO + 00040000 1...B0:-00020323
+
• BOO 03+4
:1.:1.4444 GEN
~50 • 00040000 1...B0:-00017451
El:~li:l...OG o::.!
:1.:1.4:1.44 GEN
!'.'iO. 00040000 l...B0:-00021.727
1 :1.;·5;·544 GEN
!'.'iO. 00040000 l...B0:-000212'74
+LOA 03.3
!'.'iO • ooo3?ooo 1...eo:-00021635
• HEI... 0:1.. :.;!4 :I. 13:1.44 GEN
::;o. 00003700 l...B0:-00020310
.BYE 02. :I.
:1.13044 GEN
:=.=;o • 00040000 l...BOt-00020544
.UNI... O~.! .t:i
:1.:1.2:1.44 GEN
l...PO:
1...CIADED
OBO:
LOADED
DB:I.:
l...CIA:OFD
DB2:
1...CIADED
DB3:
1...DADED
Dl\O:
l... DADED
01\:1.:
LOADED
DI\:?:
LOADED
DK:3:
1...DA:OFD
n1...o:
l...ClAOED
Dl...:1.:
l. . OAOED
OMO~
LOADED

"-'

..
..

... ..

,.._,.

'-'!.

....
....
.. ...
..
....
....
...
..
......
..

DM:I.:

1...DADED

D~:;o:

LOADED
l...Cl1()DED
l...Dt10ED

o~:;

:I.:

DTO ::
DT:I. t

LU(.~DED

:oxo:

1...Cl()[l[l)

DX:I.:

LOADED
LOADED
LOADED
l...CIAOFD
1...UAOED

MMOt

MM:I.:
TTO!
TT:I.:
TT::~:

l...01~DED

TT:!>:

l... DADFD
1...ClADFD

TT4:

7-21

DETAILS OF SYSGEN PHASE II
TT5:
TTIJ!
TT7:
TT1() !
TT11:

1...0AflED
L.DADEfl
LOADED
l..OAflED
l... OAflED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOAbED
LOADED
LOADED
LOADED
LOADED
LCIADED
LOADED
l... OADED
LOADED
LOADED
LOADED
LCIADED
LOADED
LOADED
LOADED
LOADED
LOADED
l... OADED
LOADED
LOADED
LOADED

TT12!

nn:
TT14!
TTl.:::;:
TT:l.6 !
TT1.'7:
TT2<>:
TT21:
rr2:.;~:

rr::.~3:

rr::!4:
TT2!':'i!
TT26!

TT2'7:
TT3():
TT31.:
TT32:
TT~~;3:

TT34:
rn:~;:

TB6:
TT~U:

TT40t

TT4l:
TT42:

TT4::n
TT44:
TT4:':i!
TT46:

TI<>:

coo:

no:
no:

CL..<>:
L..F.10:
SYOt
VMf(>'''Z

DBO:
DBO!

When the indirect file exits, boot in wour tar•et swstem,
set the date and time, and save the swstem with a bootstraP.
When wour svstem reboots itself, Purse the old task files.
An alternate version of SYSLIF.c called ANSLIB has been created
on the RSXM26 disk to take into account ANSI support and Bia-bufferina.
Since vou have selected ANSI ma~taPe suPPort wou maw want to
rebuild PIP and other utilities in SYSGEN Phase III to take
advanta~e of ANSI support.
Note this will cause an increase
in the size of the utilitv comPared with the non-ANSI version.
Don't

i;.:i:::M

1...nn

far~et

ta create accounts after

savin~

,'.'):3N :::=l...Dt.
; End of SYffiJEN Phase II at 14!36:36 on 23-MAY-'79

7-22

vour swstem

DETAILS OF SYSGEN PHASE II
NOTES
~·

SYSGEN mounts the mapped source disk, establishes logical
assignments, and issues a PIP command to display the amount
of free disk space.
This section creates the system libraries and uses the
librarian
(LBR)
to
replace
modules with their ANSI
equivalents •

The old libraries are deleted and then SYSGEN invokes LBR
create the Executive libraries.

SYSGEN deletes the task build maps.
SYSGEN creates a new symbol table (.STB) file
system STB file is no longer needed).

(the

baseline

This section builds the loadable drivers. Note that SYSGEN
deletes unnecessary driver build command files after the task
build completes and truncates the STB files.

This section builds th e ~rivileged tasks. Note that SYSGEN
builds the small version of the indirect command file
processor. If you want to build the larger version of AT.,
you must do so manually.
1

For mapped systems, build the 12K-word version
(BIGINDBLD.CMD) to gain symbol table space.

from

[1,24]

For unmapped systems, built the 14K-word version from
(BIGINDBLD.CMD) to gain symbol table space.

[1,20]

SYSGEN swaps the logical assignments of the pseudo devices
SY:
and LB:
and issues a PIP command to display free disk
space.
Kit variance. For RLOl and dual RKOS kit users, you must
create the file RSXllM.SYS based on the example. For big
disk kit users, SYSGEN creates this file.
SYSGEN installs Boot and VMR
assignments for VMR.

and

then

establishes

logical

This is a VMR warning message only. The message results from
the VMR command that contracts the driver partition (SET
/TOP=DRVPAR:-*).
The command file SYSVMR loads drivers,
issues the following display commands:

installs

tasks

and ,

SET /POOL
PAR
TAS
DEV
VMR then prompts to allow users to issue further commands
to exit.

At this point, the system generation process is complete. The RSXM26
disk contains a tailored and bootable RSX-11~ version 3.2 system
image. The following console display confirms it.

7-23

DETAILS OF SYSGEN PHASE I I

>:CNS $BOO
>MOU DL:RSXM26
>BOO Dl...:C:1'54J
MAf'f'ED
512K
RSX-11M V3.2 BL26
>RED DU =SY:
>RED DL: :::LB:
>MOU DL:RSXM26
>@DL:c1,2JSTARTUf'
>* PLEASE ENTER TIME AND DATE <HR:MN DD-MMM-YY> csJ: 12:00 6-JUN-79
>TIM 12:00 6-JUN-79
>* ENTER LINE WIDTH OF THIS TERMINAL CD 0:132.J:
>SET /BUF=TI:132.
>ACS SY:/BLKS=512·

>;
>; NOTE - The Baseline INDirect must be rePlaced bY BIGIND with
>;
a prioritw of 10. for SYSGEN.
);
);

>REM ••• AT+
>INS $BIGIND/f'R1=10.

>@ <EOF>

>
12:00:25 06-JUN-79
>;IT SEEMS OK
>DEV
LPO: OFFLINE LOADED
DBO: LOADED TYPE=RP06
DB1: LOADED TYPE=RP06
DB2: LOADED TYPE=Rf'04
DB3: LOADED TYPE=Rf'04
DKO: LOADED
UK 1 : I... OADE D
DK2: LOADED
DK~3: LOADED
DLO: PUBLIC MOUNTED LOADED LABEL=RSXM26 TYPE=RL01
DL1: LOADED TYPE=RL01
DMO: LOADED TYPE=RK06
DM1: LOADED TYPE=RK06
nso: LOADED TYPE=RS04
ns1: LOADED TYPE=RS04
DTO: LOADED
[IT :l : LOADED
DXO: LOADED
ox1: LOADED
MMO: LOADED
MM1: LOADED
TTO: CrJ - LOGGED ON LOADED
TT1: LOADED
TT2: LOADED
TT3: LOADED
TT 4: LOADED
TT5: LOADED
TT 6: LOADED
TT7: LOADED
TT10: LOADED
TT 11 : LOADED
TT12: LOADED
TTL5: LOADED
TT14: LOADED
TT15: LOADED
TT16: LOADED
TTl?: L.OADEU

7-24

DETAILS OF SYSGEN PHASE II
LOADED
LOADED
LOADED
LOADED
LOADED
TT~!5: LOADED
TT26: LOADED
TT27: LOADED
TT30: LOADED
TT31: LOADED
TT32: LOADED
TT33: LOADED
TT34: LOADED
TT35: LOADED
TT36S LOADED
TT37: LOADED
TT40: LOADED
TT4·U LOADED
TT42S LOADED
TT43: LOADED
TT44: LOADED
TT4·5: LOADED
TH6: LOADED
TIO:
TT~!O:

TT:;!1:
TT22:
TT23t
TT24:

coo

Tro:

CLO:
TTO:
LBOi:
DL.O:
SYO:
DL.OS
>PIP C1r54l*•*/PU
HCR -- TASK NOT IN SYSTEM
>INS $PIP
>PIP C1r54l*•*/PU
PIP -- FAILED TO DELETE FILE
DLO:C1r54lBOO.TSKf1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DLO:C1r54lDMO+TSKf 1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DLO:C1r54JIND.TSK;1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DLO:C1,54JINI.TSK;1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DLo:c1.54llNS.TSK;1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DLO:c1,54JLOA.TSK;1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DL0:[1,54lHOU.TSK;1 -- PRIVILEGE VIOLATION
PIP -- FAILED TO DELETE FILE
DLO:C1,54JSAV.TSK;1 -- PRIVILEGE VIOLATION
MCR>ABO PIP
p

TASK • ••• PIP' TERMINATED
ABORTED VIA DIRECTIVE OR HCR
AND WITH PENDING IO REQUESTS

>
);FORGOT TO CHANGE UIC• CAN'T DELETE FILES
•

>SET /UIC=:[1'54J
>PIP [1,54J*•*/PU
>PIP /FR
DLO: HAS 1242+ BLOCKS FREE• 8998. BLOCKS USED OUT OF 10240+
LARGEST CONTIGUOUS SPACE = 519+ BLOCKS

>REM PIP

>
7-25

•

CHAPTER 8

VMR COMMANDS

The Virtual Monitor Console Routine (VMR) is an RSX-llM system program
that allows complete configuration of an RSX-llM system image file for
booting. As its name suggests, VMR provides the capability to execute
Monitor Console Routine (MCR) commands that are directed to the disk
image of a system.
VMR supports a compatible subset of the MCR commands described in the
RSX-llM/M-PLUS MCR Operations Manual.
All VMR commands have the same
syntax and semantics as their MCR counterparts with the one exception
of the SAVE command.

8.1

STARTING VMR

You can start VMR four ways.
The first three methods apply when you
have
installed VMR and it is ready to be executed. The fourth method
installs VMR automatically, executes it, and then removes it on exit.
Methc)d 1:
>VMR @indirect
The system loads VMR and executes the specified indirect
file;
VMR then exits.

command

Meth<>d 2:
>VMR
The system loads VMR, and VMR responds with the following prompt:
ENTER FILENAME:
Methc)d 3:
>RUN VMR
The system loads VMR, and VMR responds with the following prompt:
ENTER FILENAME:
Methc)d 4:
>RUN $VMR
The system installs VMR from the pseudo device LB:
under the
system UIC
(normally, [l,50] or [l,54]) and loads it;
VMR then
responds with the following prompt:
ENTER FILENAME:

8-1

VMR COMMANDS
In all starting methods except method 1, VMR prompts with:
ENTER FILENAME:
At this point, you specify the file that contains the image of the
RSX-llM system you want to modify. VMR expects to find a symbol table
file of the same name as the system image file,
but with a
file
extension of .STB, on the same device and under the same UFO as the
system image file (except when you use the /IM switch;
see Section
8.2).
For example, suppose you enter the following file specifier in
response to the prompt:
RSXllS .SYS
A corresponding file, RSXllS.STB, must exist that contains the symbol
definitions for
the RSXllS.SYS system image. Note that the pseudo
devices LB:
and SY:
on the running system must refer to the disk
containing the system image file.
The system image and symbol table files are
produced by the RSX-llM Task Builder.

the

standard

format

Upon receiving a valid file specifier, VMR opens and reads the symbol
table file;
it also opens the system image file and verifies that the
file is actually a system image. VMR then prompts with
VMR>
You can now enter any valid VMR command or end VMR by typing CTRL/z.l
If you used method 1 to start VMR,
the specified file contains a
series of commands to be executed by VMR. The first record in the
file must contain a file specifier for the system image file
that is
to be modified.
In addition to specifying an indirect file to start VMR, you can
enter the following any time that VMR prompts for input:

also

@filespecifier
This directs VMR to extract input from the specified file
until
it
reaches an end-of-file and to return to the terminal for further
input. This feature of VMR is useful when you want to repeat a series
of commands for
several generated systems
(INSTALL commands, for
example).

8.2

VMR FILE SPECIFIERS

File specifiers accepted by VMR are in the standard RSX-llM format:
dev: [g,m]filename.type;ver[/IM]

CTRL/Z is typed by simultaneously depressing the CTRL and Z keys.

8-2

•

VMR COMMANDS
Parameters
dev:
The device unit on which the volume containing the desired file
is mounted
(for example, DKO or DTl). The name consists of 2
ASCII characters, followed by an optional 1- or 2-digit octal
unit number.
The default device is SYO.
[g ,m]

The User File Directory (UFD), consisting of a group number and a
member number.
The default is the UFD that corresponds to the
UIC under which VMR is running.
f ilemame

The name of the file.
An RSX-llM file name can be up to 9
alphanumeric characters long.
The file name and file type are
always separated by a period (.).
You must specify a file
name;
no default is applied.
typ
The file type, consisting of up to
3 alphanumeric characters.
The defaults are SYS for system image files and CMD for indirect
command files.
ver
The version number in the range
default is the highest version.

through

77777(8).

The

/IM
A switch option that, when attached to the system image file
specification and used with the SAVE command, .overrides the VMR
requirement for the symbol table file.
This is the only switch provided with VMR. You use it to write
non-RSX-llM system images to secondary media in bootstrappable
format.
When you use the IM switch with the file specification, the only
command VMR will accept is the SAVE command. This switch is
useful when you use an RSX-llM system as a host system to develop
and create small, main memory resident systems that must be
loaded from a serial medium (such as paper tape).

8.3

COMMAND SYNTAX

You do not have to type an entire command name to VMR.
VMR accepts
the first three characters of a command and then searches for a blank
or tab followed by the command parameters or by a carriage return if
there are no parameters.
Because a blank or a tab is required before
parameters, VMR does not allow embedded blanks in a command name.
If
you enter a command incorrectly, VMR displays an error message at your
terminal.

8-3

VMR COMMANDS
The following example illustrates the TIME command.
Note that
square brackets in the example indicate that the "E" is optional:

the

VMR>TIM[E] <CR>
14:00:04 21-MAY-79

8.3.l

Keywords

Some commands use keywords that generally apply to a command argument.
A
keyword
consists
of
a
slash
(/),
followed by an ASCII
identification, and optionally followed by an equal sign (=)
and the
value of the keyword, as follows:
/keyword=value
You can enter keywords in any order. As an example of keyword usage,
the INSTALL command requires a file name argument specifying the task
to be installed. You can append keywords to the file name. One such
keyword,
/TASK, specifies the name under which the task is to be
installed.
VMR>INS BOB.TSK/TASK=AMBER
This command causes the task contained in the file named BOB.TSK to be
installed with a name of AMBER. Keywords are command specific and are
defined with each command.

8.3.2

Comments

VMR treats a line of text as a comment if the first character in the
line is a semicolon
(;).
In addition, you can use the exclamation
mark (1) to delimit comments in a command. The first exclamation mark
starts the comment and the next exclamation mark or end of line
terminates the comment.
VMR ignores all text between the two
exclamation marks.
For example:
VMR>;

THIS LINE IS A COMMENT

VMR>TAS !THIS IS A COMMENT STRING!
Comments are especially useful to clarify commands in VMR indirect
command files.
(Refer to the RSX-llM/M-PLUS MCR Operations Manual for
further information about indirect command files.)

8.4

COMMAND SUMMARY

The VMR commands described in this chapter are listed below by
category.
This command summary provides a compact overview of the
facilities available through VMR. The detailed descriptions of the
VMR commands given in Section 8.5 are presented in alphabetical order.
Initialization Commands
ASSIGN

Define or delete a global logical device assignment.
List current assignments on console terminal.

INSTALL

Install a task into the system image.

8-4

"'~.

VMR COMMANDS
LOAD

Load a device driver.

REDIRECT

Redirect all I/O requests from one physical device
another.
Write the system image of memory
media in bootstrappable format.

SET

onto

secondary

Set system and terminal characteristics;
define
partition
partitions;
display
~erminal
and
characteristics on entering terminal.
display

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

Unload a device driver.

Informational Commands
DEVICES

Display on the entering terminal a list of
devices defined in the system image.

LUNS

Display on the entering terminal
assignments for an indicated task.

PAR'rITIONS
TASK LIST

the

peripheral

list

LUN

Display on the entering terminal
the
partitions defined in the system image.

list

Display on the entering terminal a list of
installed in the system image.

all

tasks

Task Control Commands
ALT:E:R

Alter the priority of a task.

CANCEL

Cancel the time-based initiation requests for a task.

FIX

Fix a task in system image.

REASSIGN

Change a task's LUN assignment.

REMOVE

Remove a task from the system image.

RUN

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

UNFIX

Unfix a task from the system image.

8.5

VMR COMMAND DESCRIPTIONS

The following subheadings are used
in
the
detailed
command
descriptions
in this section.
Subheadings that do not apply to a
particular command are omitted from the command description.

~·

8-5

VMR COMMANDS
COMMAND NAME
This subheading consists of the command name in capital letters.
The
minimal VMR command acronym is shown on the right margin. The text
following the name describes the command's function.
Format
The command format is given, and all parameters are described.
Parameters
Parameters are listed and described.
Examples
Examples of using the command are shown.
Notes
A list of special considerations that may assist you in using the
command properly appears under this subheading.

...

8-6

VMR COMMANDS

ALT
ALT'ER
Use the ALTER command to change the static priority
task.

installed

Format
ALT[ER] taskname /PRI=priority

Parameters;
taskname
The name of the task whose priority is to be altered.
/PIH
_,._.,....,..

...

The keyword that changes the task's static priority.
priority
The new priority to be assigned to the specified task, from l
250 (decimal).

Example
>ALT TEST /PRI=248.
Alter the static priority of task TEST TO 248(10).

8-7

VMR COMMANDS

ASN
ASSIGN
Use the ASSIGN command to define, delete,
or display logical-device
assignments.
Logical-device assignments are a way to associate
logical names with physical devices, pseudo devices, or other logical
devices.
When you assign a logical name to a pseudo or logical
device, the system resolves the assignment to the associated physical
device.
There are three types of logical-device assignment:
global,
local, and login. VMR supports the manipulation of global assignments
only.
See the RSX-llM/M-PLUS MCR Operations Manual for additional
information on local and login assignments.
The manipulation of global assignments applies to
running system.

all

tasks

the

A logical-device name has the same syntax as a physical device unit.
It consists of a 2-character ASCII name (alphabetic) and an optional
1- or 2-digit octal unit number,
followed by a colon
(:).
The
2-character name can either be equivalent to a standard RSX-llM device
name (for example, DK:) or two letters picked at random (for example,
XY:).

When you install a
task, or the system executes an ASSIGN LUN
directive,
the system scans the logical device table before it scans
the physical device table when it searches for a specified device. As
a
result,
you can define logical device names that are identical to
physical device names even though the logical and physical device
names do not refer to the same physical device. The system resolves a
specified device name to the first matching table entry found.
If a
logical device name is identical to a physical device name, the
logical name has precedence.
Formats
ASN ppnn:=llnn:/GBL
Define a global assignment that associates the logical name llnn;
with device ppnn:.
ASN /GBL
Display all global assignments for the system.
ASN =[llnn:]/GBL
Delete the specified global logical-device assignment
global assignments if the command omits llnn:.
Parameters
pp
A physical, logical, or pseudo device name.

8-8

all

VMR COMMANDS
nn
A unit number.
11

A logical device name.

Examples
VM:R>ASN

DK:=GBO:/GBL

!Define global logical device
!name

VMR>ASN

/GBL
DKO:

!List all assignments

GBO:

VMR>ASN

=/GBL

GLOBAL
!Delete all global assignments

8-9

VMR COMMANDS

CAN
CANCEL
Use the CANCEL command to cancel time-based initiation requests for a
task.
These requests result from the RUN$ directive or any of the
time-synchronized variations of the VMR RUN command.
CANCEL does not affect the execution of the task that may be active in
the saved system image.
It removes only the time-based schedule
requests still in the clock queue.
Format
CAN[CEL] taskname
Parameter
taskname
The name of the task whose time-base initiation request is to
canceled.

Example
VMR>CAN XKE
Cancel all periodic rescheduling
requests for task XKE.

and

time-based

initiation

8-10

VMR COMMANDS

DEV
DEVICES
Use the DEVICES command to display on the entering terminal
the
symbolic names of all device-units or, optionally, all of a particular
device type defined in the system image.
The device names appear in a
single vertical
column.
A second column contains any additional
information about each device.

Formats
DEV[ICES]
DEV[ICES] dd:

Parameter
dd:
The particular device type to be displayed.

Examples
VMR>DEV

DBO:
DBl:
DB2:
DB3:
DKO:
DKl;
DK2:

LOADED
LOADED
LOADED
OFFLINE LOADED
LOADED
LOADED
LOADED

DSO:
DSl:

DTO:
DTl:
LPO:
MMO:
MMl:
PPO:
PRO:

LOADED
LOADED
LOADED
LOADED
LOADED
UNLOADED
UNLOADED

T'l'O :
T'I' 1 :

T'1'2:
T'r3:

T'N:
COO:
CLO:

SYO:
LBO:

TTO:

LPO:
DBO:
DBO:

VMR>DEV DK:
DKO:
LOADED
DKl:
DK2:
The~

following list describes the messages that can appear
in the
second column.
More than one message can appear on the same line.

8-11

VMR COMMANDS

•

OFFLINE indicates that, although the system tables contain
entries for this device, the system as saved did not contain
the related device.

•

LOADED indicates that the driver for the
and is currently loaded.

loadable

•

UNLOADED indicates that the driver for the device is
and is currently not loaded.

loadable

•

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

•

Absence of either LOADED or UNLOADED in the second column
indicates that the driver is permanently resident; it is
linked to a part of the Executive.

device

•.

8-12

VMR COMMANDS

FIX
FIX-- IN-MEMORY
Use the FIX-IN-MEMORY command to load a task into its partition in the
system image.
The system can service requests for running the task
more quickly because the task is memory-resident and does not have to
be loaded from the disk before it can run. VMR can fix a task in the
system imag,e only if the partition in which it is to be fixed
is
available.
On RSX-llS systems,
all
installed tasks must be fixed
since they cannot be loaded into the running RSX-llS system.
Fixed tasks remain in memory even after they exit. Therefore, they do
not have to be reloaded when a request is made to run them.
(Note
that re-executing fixed tasks is not always practical.) Only an UNFIX
or REMOVE command can free the occupied partition.
The following restrictions apply to the fixing of tasks:
•

Checkpointable tasks cannot be fixed,

•

Active tasks cannot be fixed,

•

A task must be installed before it can be fixed,

•

A task can only be fixed in a
system-controlled partitionso

task

Format
FIX t.askname

Parameter
taskname
The task that you wish to fix in memory.
Exa.mple

VMR>FIX XKE
Fix task XKE in its partition.

'-""''
8-13

partition,

and

not

VMR COMMANDS

INS
INSTALL
Use the INSTALL command to make a specified task known in the system
image, or to load a common into a common partition. An installed task
is dormant until the Executive receives a request for it to run.
The
optional keywords either provide parameters that were not specified at
task build or override parameters that were.
When a task is installed, VMR creates a Task Control Block
(TCB}
for
the task in a system image table called the System Task Directory
(STD}.
The task parameters contained in the TCB enable the system to
run the task when requested to do so by an MCR command, VMR command,
or a system directive.
A task cannot be run until you install it.
A task's TCB contains the address of the load-device Unit Control
Block (UCB} and the Logical Block Number (LBN) of the task image file.
The Executive can therefore load the task image in one transfer when
an MCR command or system directive requests an installed task.
(Loading requires more than one transfer if the task is greater than
32K words.)
When VMR installs a task in a virgin system,
it stores the task's
logical block numbers in the task header. When you save a system, the
SAVE command places the file identification, rather than the file's
LBN,
in the TCB. Then, when the system is rebooted, it reopens the
task file and stores the task's new LBN in its TCB.
If a task has
been deleted, the system cannot open the task file when the system is
rebooted. The system then automatically removes the task's TCB from
the STD. When VMR installs a task in a saved system image, it stores
the task's file identification, rather than the LBN,
in the TCB to
allow a reboot to occur successfully.
Also a saved system does not retain the physical addresses of
installed tasks.
The Disk Save and Compress
(DSC)
utility can
compress and copy a disk containing a saved system,
thus moving the
task files to different physical locations.
But because the TCB
entries contain task file identifications, rather than LBNs,
after a
system save, the system can function normally when it is rebooted.

Format
INS [TALL]

filespec [/keyword] [/keyword] •••

Parameters
f ilespec
A task image file specifier in the form:
dev: [group,member]filename.type;version
The type defaults
remaining fields.

TSK.

Standard

8-14

defaults

apply

the

.._

VMR COMMANDS
keyword
One of the keywords listed below:
/CKP=option
/INC==size
/PAR==pname

/SLV=option

/PMD==option

/TASK=taskname

/PRI ==number

/UIC=[group,member]

/PRO=[system,owner,group,world]

Keywords
/CKP=option

·'--".

The option is yes or no.
If CKP=YES (default for checkpointable
tasks),
checkpointing is enabled for
the task.
If CKP=NO,
checkpointing is disabled for the task.
The /CKP keyword overrides
build.

the

/CP

switch

specified

task

On systems that support the dynamic allocation of checkpoint
space,
the
task
image file does not need to contain allocated
checkpoint space.
The presence of the /CKP=YES keyword instructs
the system to allocate checkpoint space for
the task when
required from a checkpoint file.
/INC=size
The size is the number of additional words of address space to be
allocated to a task.
The extension size is usually expressed in
octal but may also be expressed in decimal by appending a period.
This keyword overrides the Task Builder's EXTTSK or PAR option
keyword.
Tasks such as MACR0-11, TKB, PIP, VFY, and AT.
use the
space from the end of the task image to the end of their address
space as dynamic memory in which to allocate symbol tables and
buffers.
The INC keyword defines the number of words in this
dynamic region.
The default size
is the size specified at
task-build time, or, if none specified at task build, zero.
/PAR=pname
A partition name
task-·build time.

that

overrides

the

partition

specified

If the keyword specifies a nonexistent partition, VMR issues a
warning message and attempts to
install the task in the GEN
partition.
Default:

TKB uses the name

GEN~

8-15

VMR COMMANDS
/PMD=option
The option is yes or no.
If PMD=YES, the system will perform a
post-mortem dump of the task if it aborts the task because of an
SST error condition.
If PMD=NO (the default from a task-build),
the system will not perform a dump at SST abort time.
To generate a dump, you must install
PMD...
in the system.

the

post-morem

This keyword overrides the Task Builder's
default is specified at task-build time.

/PM

dump

task

switch.

The

/PRI=number
The number is the priority at which the task is to be installed.
The value range is 1 through 250(10). Standard RSX-llM number
conventions apply to this parameter. The default is PRI=SO.
/PRO=[system,owner,group,world]
The

The PRO keyword establishes a protection mask for a common.
user groups are defined as:
•

System - All system tasks running under
less than or equal to 10(8).

•

Owner

- Tasks that run under the same UIC as the files owner.

•

Group

- Any task that is running under the same UIC group
the file's owner.

•

World

- Any task that does
categories.

not

fit

The PRO keyword establishes the access
The four types of access are:
•

Read

•

Write

•

Extend

•

Delete

UIC

one

rights

group

number

the

above

for

each

group.

the

system

For example:
INS COM/PRO[RWED,RWED,R,R]
gives read, write, extend, and delete access to
owner and read access to the group and world.

and

/SLV=option
The option is yes or no.
If the command specifies /SLV=YES, data
sent to the installed task is marked with the TI: of the sending
task. When the installed task receives the data, the system sets
the task's TI:
to that associated with the data. This keyword
overrides the Task Builder's /SL switch.
If the command specifies /SLV=NO, the TI: of the task does not
change when receiving data.
The default is specified at task
build.

8-16

VMR COMMANDS
/TASK=taskname
The name to be used to install the task. The default is the name
specified at task-build time or the first 6 characters of the
file name.

/UIC=[group,member]
The square brackets are required syntax. This UIC is the default
for the task.
You can override it with the RUN command. The
task QIC determines the file-protection class (system, owner,
group, world) in which a task belongs, and thus directly
influences file access. Note that file protection may differ
from file to file.
The default is from the task build. This default applies only to
tasks started by a RUN$ directive or a RUN command that specifies
a time delay before runtime. Tasks started by typing the name as
a command (for example, PIP and TKB) run under the default UIC of
the terminal from which the command was issued.
Exa111tples

VMR>INSTALL SCAN
Install task SCAN using the default priority and UIC.
VMR>INSTALL DKl: [l,lll]SCAN.TSK;4/PRI=l03
Install task SCAN, file type TSK, version 4 from device DKl:,
group number 1, member number 111, with a priority of 103(8).
VMR>INS MAC/INC=4096./PAR=SYSCTL
Install task MAC in the partition SYSCTL and
size by 4096 decimal words.

8-17

increase

the

task

VMR COMMANDS

LOA
LOAD
Use the LOAD command to load a nonresident device driver into the
system image. The LOAD command constructs the data base and interrupt
vector linkages required to allow access to the device. This command
eliminates
the
need to link infrequently used device drivers
permanently into the Executive.
(Executive support of loadable device
drivers is a system generation option.}
Format
LOA [D] dd: [/keyword=value] [/keyword] [/keyword] •••
Parameters
dd:
A 2-character ASCII device name.
keyword
One of the following three- or four-letter keywords:
/PAR=pname
/SIZE=psize
Keywords
/PAR=pname
The pname is a partition name. The PAR keyword is used to name
the partition into which the driver is to be loaded. It
overrides the partition specified at task build time.
/SIZE=psize
The psize is partition size.
The SIZE keyword is used to
establish the minimum size (octal words) of the partition into
which the driver is to be loaded. VMR rounds psize up to the
next largest unit of 100 octal. Psize must be less then 77741.
Examples
VMR>LOAD

MM:

!LOAD TU16 DRIVER (MMDRV)

VMR>LOA

LS:/PAR=DRVPAR

!LOAD LPSll DRIVER (LSDRV) INTO
!DRVPAR

Notes
1.

Guidelines for building loadable device-driver tasks are
rigidly defined.
These guidelines are described in the
RSX-llM Guide to Writinq an I/O Driver.
The
system
generation procedures include provisions to simplify the task
building of drivers.

8-18

VMR COMMANDS
2.

''--"

The LOAD command requires that a driver's TSK and STB files
reside under the same UFD and on the same disk as the system
image upon which you are working.
For example, the following
command requires that thE~ files DTDRV .TSK and DTDRV .STB
reside on SY:
under the current UIC.
LOA DT:

The LOAD command requires pool space as follows:
a.

If the driver data base is being loaded,
the command
needs pool space equal in size to the size of the data
base ..

The command needs pool space for an Interrupt Control
Block (ICB) for each interrupt entry point in the driver.

The command needs pool
Block (PCB).

space

8-19

for

Partition

Control

VMR COMMANDS

LUN
LOGICAL UNIT NUMBERS
Use the LUN command to display at the entering terminal the static LUN
assignments for a specified task.
(Static assignments are those
recorded in the task's disk-image fileg) The display consists of a
list of physical device units in one column, with the corresponding
LUNs in an adjoining column.
Format
LUN[S] taskname
Parameter
taskname
The task for which the LUNs are to be displayed.
Example
VMR>LUN XKE
SYO:
SYO:

1
2

CLO:
TT3:
TT3:
DKO:
TT3:

3
4
5

6
7

The display shows static assignments for LUNs 1
recorded in the task-image file header;
no
statically assigned to the task XKE.

8-20

through 7 as
other LUNs are

VMR COMMANDS

PAR
PARTITION DEFINITIONS
Use the PAR command to display on the entering terminal a description
of each memory partition in the system image. The display consists of
six columns that specify:

._,.,

.,,

Partition name

Partition Control Block address (octal}

Partition base address (octal}

Partition size (octal}

The partition type and, following the partition type,
partition occupant(s} -- task, driver, common, etc.,

6•

The name of partition occupant(s}.

Format

PAR [TITIONS]
Exa:mple

Name

'-'

'--"

PCB

VMR>PAR
TTPAR
117734
SY SPAR 117670
TKNPAR 117624
DRVPAR 117560
117340
117240
11 7140
117040
116740
116640
116540
116440
116340
116204
115550
LDRPAR 117514
BASIC2 117450
GEN
117404
060400
VMR>

Base

Size

00120000
00160000
00170000
00200000
00200000
00202000
00203100
00205600
00210100
00211100
00212200
00213600
00215700
00217200
00223100
00227700
00232300
00272300
00272300

00040000 MAIN
00010000 MAIN
00010000 MAIN
00027700 MAIN
00002000 SUB
00001100 SUB
00002500 SUB
00002300 SUB
00001000 SUB
00001100 SUB
00001400 SUB
00002100 SUB
00001300 SUB
00003700 SUB
00003000 SUB
00002400 MAIN
00040000 MAIN
00175000 MAIN
00040000 SUB

PAR/TASK Name

8-21

TASK
TASK
TASK
SYS
DRIVER DRIVER DRIVER DRIVER DRIVER DRIVER DRIVER DRIVER DRIVER DRIVER DRIVER TASK
COM
SYS
( ••• SAV}

DB:
DK:
DM:
DR:
DS:
DT:
DX:
DL:
LP:
MM:
CO:

the

VMR COMMANDS

REA
REASSIGN
Use the REASSIGN command to reassign a task's Logical Unit Numbers
(LUNs)
from one physical device unit to another. The reassignments
affect only the &tatic assignments recorded in the task's disk image
file.
The command does not affect a memory-resident task.
Therefore,
REASSIGN has no effect on the assignments for a task that is fixed or
loaded in memory.
Format
REA[SSIGN] taskname lun nud:
Parameters
taskname
The name of the task for which the LUNs are to be reassigned.
lun
The logical unit number.
nud

The new device unit, which can be a physical, logical, or
device.
Examples
VMR>REA JOE 3 TTO:
Reassign LUN 3 of task JOE to device TTO:.
VMR>REA BILL 2 TTl:
Reassign LUN 2 of task BILL to device TTl:
VMR>REA TEST 3 XX:
Reassign LUN 3 of task TEST to logical device XX:.

8-22

pseudo

VMR COMMANDS

RED
REDIRECT
UsE~

the REDIRECT command to redirect all I/O requests
physical device-unit to another physical device-unit.

from

one

Note that an attached device and the device TI: cannot be redirected.
In addition, one pseudo device cannot be redirected to another pseudo
device.

Format
RED[IRECT] nud:=old:

Parameters
nud:
The new device unit to which requests will be redirected.
old:
The old device unit from which requests have been directed.

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

to device TT3:.

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

8-23

to device TTO:.

VMR COMMANDS

REM
REMOVE
Use the REMOVE command to delete a task or region name from the system
image.
Removing a task from the system image makes the task unknown
to the system.
The action resulting from this command is the
complement of INSTALL.
The REMOVE command cannot remove an active task from a saved system.
An example of such a task is the SAVE task; an attempt to remove SAVE
from a saved system results in an error. ·The message TASK ACTIVE is
displayed.
Formats
REM[OVE] name
Parameter
name
The name of the task to be removed.
Example
VMR>REM SCAN
Remove the task named SCAN from the system image. The task-image
file remains unaffected. Note that tasks installed as ••• XXX can
be removed by
>REM XXX
or
>REM ••• XXX
Notes
1.

If a task that is the object of a REMOVE command is fixed,
the command automatically unfixes the task from the system
image.

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

You cannot remove a task if it has send or
packets queued to it.

8-24

send-by-reference

VMR COMMANDS

RUN
RUN
Use the RUN command to initiate the execution of a task.
which has four formats, can cause a task to be:

The command,

•

Started one clock tick after system boot

•

Started at a time increment from the system image time

•

Started at a time increment from clock unit synchronization

•

Started at an absolute time of day

All of these options are available with or without rescheduling.

Format 1
Run one clock tick after system boot
RUN taskname [/RSI=magu] [/UIC=[uic]]

Parameters
taskname
A 1- to 6-character taskname of the task that you wish the system
to run.
RSI
The reschedule interval. The format is the same as for dtime,
which is detailed below under format 2. The reschedule interval
specifies how often you want the system to rerun the task.
Each
time the interval of time you have specified lapses, the system
will make an initiation request for the task. The default is no
rescheduling.
UIC
The UIC that has the format [g,m] where g and m represent the
group and member numbers respectively.
Legal group and member
numbers range from 1 through 377(8).
The square brackets are
required syntax.
This is the UIC under which the task is
requested.
It determines which files the task may access.
The
default is the value established for terminal CO:.

Fo:rmat 2
Run at a time increment from the system image time
RUN taskname dtime [/RSI=magu] [/UIC=[uic]]

Parameters
taskname
A 1- to 6-character taskname.

8-25

VMR COMMANDS

dtime
The time at which the task is initiated in
current system image time. It has the form:

time

from

units

magu
mag
The magnitude
u

Time units specified as follows:
T

for ticks. A tick is a clock interrupt, and the rate at
which interrupts occur depends on the type of clock
installed in the system.
For a line frequency clock, the tick rate is either SO or
60 ticks per second, corresponding to the line frequency.
For a programmable clock, a maximum of 1000 ticks per
second is available.
(The frequency is selected at system
generation.)

for seconds.

M for minutes.
H

for hours.

The magnitude is the number of units to be clocked, but
magnitude value cannot exceed 24 hours in specified units.

the

Units = T.

Any Positive
bits).

value

valid

(maximum

Any Positive
bi ts) •

value

valid

(maximum

Units

Units= M.

The maximum magnitude is 1440(10).

Units

The maximum magnitude is 24(10).

RSI
See format 1, above.
UIC
See format 1, above.
Format 3

Run at a time increment from clock unit synchronization
The task start-time is determined by computing the number of
ticks until the next time unit's occurrence (hour, minute,
second, tick) and then adding on the number of ticks for the
specified time increment to elapse.
RUN taskname sync [dtime] [/RSI=magu] [/UIC= [uic]]

8-26

VMR COMMANDS
Parameters
taskname
A 1- to 6-character taskname.
syni::::
synchronize
synchronize
s
synchronize
T = synchronize

H
M

on
on
on
on

the
the
the
the

next
next
next
next

hour
minute
second
tick

dtime
Defined in format 2, above;
dtime, if present, is added to the
synchronization unit to produce the actual run time for running
the task.
RSI
See format 1, above.
UIC
See format 1, above.

Format 4
run at an absolute time of day
RUN taskname atime [/RSI=magu] [/UIC= [uic]]

Parameters
task name

A 1- to 6-character taskname.
atime
The absolute time of day when this task will be initiated.
format is hh:mm:ss.
hh
mm
SS

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

RSI
See format 1, above.
UIC
See format 1, above.

Examples
>HUN XKE 15M
Run task XKE 15 minutes from the current system image time.

8-27

Input

VMR COMMANDS

>RUN XKE 15M/RSI=90S/UIC=[3,l]
Run task XKE 15 minutes from the current system image
rescheduling it every 90 seconds, with a UIC of [3,1].

time,

Note
The correct value to be inserted in the clock for forms 2 through
4 is computed from the current value of the system time stored in
the system image. Thus, the system image time must be set before
any RUN requests are made or they may not occur at the correct
time after the system is booted.

8-28

VMR COMMANDS

SAV
SAVJ!:
Use the VMR SAVE command to write the image of a system onto a
sequential medium in bootstrappable format. With this command you can
copy an RSX-llS or a foreign system onto a tape or a floppy disk.
You
can then transport the tape or floppy to another computer and
bootstrap ,it, using a hardware bootstrap or the /BO switch in PRESRV
(refer to the description of the /IM switch in Section 8.2 of this
chapter).
System images created with the SAVE command on all media, except paper
tape, are in a format compatible with the logical tape format in
PRESRV.
Thus,
any of PRESRV's logical tape operations can be
performed on system images created with the SAVE command. System
images created by the SAVE command always start at the beginning of
the medium.
On paper tape, system images are created in absolute loader format and
must be bootstrapped with the absolute loader.

Format
SAV[E] ddnn: [label]

Parameters
ddnn:
The device-unit onto which the system image
Valid devices are as follows.
CT:
DD:
DT:
DX:
DY:
MM:
MS:
MT:
PP:

written.

Tape cassette
DECtape II
DECtape
Flexible diskette
RX02 floppy disk
TE/TU16/TU45 magtape
TS04 magtape
TE/TU10/TS03 magtape
Paper tape.

label
The file label name that must be specified for all secondary
It consists of from one to twelve
media except paper tape.
alphanumeric characters.

Example:
VMR>SAV MT:MYSYS
In this example,
the system image is written
bootstrappable
format.
System changes, made
commands, are also saved with the system image.

8-29

onto MT:
by other

in
VMR

VMR COMMANDS
Notes

When you use the /LI command .in PRESRV to list the contents
of a medium (other than paper tape) that contains one or more
system images created with the SAVE command, each system
image causes a line to be printed which contains the
following:
a.

VW (for VMR), indicated as the source device

The label specified in the SAV command line

A block size of 512

The number of 512-byte blocks
(excluding boot and label blocks)

The date and time that the system was saved

the

system

image

When you save RSX-llS systems on paper tape and you do not
apply the /IM switch to the system's file name, the last
1000(8) bytes of the system image are not written out.
This
allows space to accommodate the absolute loader. When you
specify the /IM switch with the system's file name,
the
entire system image is written out to paper tape.
In this
case, it is your responsibility to ensure that the system
image is not so large that it overlays the Absolute Loader.

When saving a system on paper tape,
contiguous blocks that
contain zero only and that begin on a 32-word address are
compressed into a 2-word descriptor.
This
compression
significantly reduces both the amount of paper tape required
and the time expended to create the tape and to read it into
memory.
After the entire image has been loaded into memory,
a short routine zeroes the appropriate blocks of memory
before passing control to the bootstrapped system.

When bootstrapping systems on media other than paper tape,
regardless of the size of the system image, the last 1000(8)
bytes of physical memory are not copied to accommodate the
bootstrap.

Systems saved on a TE/TU10/TS03, 9-track magtape drive can be
booted from a TE}TU16 drive, and vice-versa, but not on a
TS04.

When you specify the /IM switch with the system file
specifier, the SAVE command always uses a bootstrap that does
not enable memory management.

The maximum memory size of a mapped system is 124K words.
The SAVE command imposes maximum sizes on saved images in
mapped systems for certain devices.
If a mapped system is
saved, and its memory size is greater than the maximum size
imposed by the SAVE command for the specified device,
only
the amount of memory equal to the maximum size (starting at
physical location 0) is saved;
no diagnostic message
is
issued.
The devices for which the SAVE command imposes a
maximum size on saved system images are:
a.

Paper tape punch (PP) -

Flexible disk (DX) - 123K words

8-30

28K words

•

VMR COMMANDS
c.

Flexible disk (DY) in single density - 123K words

Cassette tape (CT) -

28K words

None of the bootstraps require that the target RSX-118 system
have a driver for the bootstrap device.

The MM:
drives are forced to 800 b.p.i.
the tape.

8-31

before

writing

VfllR COMMANDS

SET
SET
You can use the SET command to alter a number of system-wide
characteristics.
The following list describes all the available
options. The text in parentheses specifies keywords associated with
the options. The SET command allows you to:
•

Display the status (determined by the keyword
all terminals.

•

Establish device characteristics for any device in the
(BUF, CRT, ESCSEQ, LA30S, LOWER, REMOTE, SPEED ••• ,}.

system

•

Establish the default UIC
(UIC}.

system

•

Establish the system UIC used by the LOAD command
Install-Run-Remove option of the RUN command.

•

Set the status of any terminal in the system (PRIV or SLAVE}.

•

Create partitions

•

Add space to the system dynamic memory (POOL}.

•

Enable write check on devices that support it (WCHK).

for

any

terminal

specified}

the

and

for

the

Improper use of the SET command can result in a situation in which the
system will not accept privileged operator input. The following two
situations should be avoided:
•

The system does not have any non-slave, privileged terminals.
Non-privileged terminals cannot enter privileged commands.
Slaved terminals cannot enter unsolicited input to MCR.
See
the description of the /SLAVE keyword below.

•

The buffer length of all non-slave,
privileged terminals is
shorter than 14 bytes.
In this case, the terminal buffer is
too short to enter many important commands required to
continue system operation or alter the status of other
terminals.
See the description of the /BUF keyword below.

A number of SET command options (CRT, ESCSEQ, LOWER, and WCHK} require
Executive features that must be included at system generation.
If you
specify an option which has not been generated into the system image,
the SET command has no effect and results in an error.
VMR permits only one keyword per command.
You can
keywords by NO to negate or disable the function of
Exceptions are BUF, HFILL, LINES, TERM, POOLSIZE, POOL,
and SYSUIC;
VMR returns a syntax error when NO precedes
keywords.
Format
SET /keyword=values

8-32

pref ix most
the keyword.
SPEED, UIC,
one of these

VMR COMMANDS
Parc:ameter
/keyword=value
Either a device characteristics keyword or a memory allocation
keyword.
The device characteristics keywords are listed below:
/BUF=dev: [size]

/REMOTE[=dev:]

/CRT [==dev:]

/RPA [=dev:]

/ESCSEQ [=dev:]

/SLAVE[=dev:]

/EBC [ ==dev:]

/SPEED=dev: [recv:xmit]

/ECHO[=dev:]

/SYSUIC[=uic]

/FOX [ ==dev:]

/TERM=dev: [value]

/FORMFEED[=dev:]

/TYPEAHEAD[=dev]

/HFILL=dev: [value]

/UIC[=uic[:dev:]]

/HHT [ ==dev: ]

/VFI LL [ =dev:]

/LINES=dev: [value]

WCHK [ =dev:]

/LOWER [ =dev:]

/WRAP [=DEV: ]

/PRIV [=dev:]
The memory allocation keywords are listed below:
BOT
PAR
NO PAR

POOL
POOLSIZE
TOP

Device Characteristics Keywords
/BUF=dev: [size].
Sets or displays the default buffer size of the specified device.
If you omit the buffer size, this keyword causes the current size
to be displayed. The size you specify must be greater than 0 and
less than or equal to 255 decimal (for a terminal, the buffer
size must be greater than or equal to two).
BUF is particularly
useful for defining line printer width (80 or 132 columns).
/CR~r [ =dev: ] ,

The dev:
is not a cathode ray tube
(CRT)
terminal.
The CRT
keyword defines the terminal as a CRT and enables the backspace
deletion option. When the backspace deletion option is enabled,
typing the RUBOUT or DELETE key moves the printing position one
space to the left and erases any character displayed in that
position.
When you omit the device specification,
devices that are defined as CRTs.

8-33

VMR

displays

all

the

VMR COMMANDS
/NOCRT[=dev:],
The dev:
is a cathode ray tube
(CTR)
terminal.
The NOCRT
keyword deletes the CRT status of the specified device and
disables the backspace deletion option.
When you omit the device option, VMR displays all
that are not defined as CRTs.

the

terminals

/ESCSEQ [ =dev:]
The dev:
is a terminal.
The ESCSEQ keyword enables the
recognition of escape sequences from the specified terminal. The
terminal driver treats the ESC character as the beginning of an
escape sequence rather than as a line terminator.
See the
RSX-llM I/O Drivers Reference Manual for
further
information
about escape sequences.
When you omit the device specification, VMR
terminals that recognize escape sequences.

displays

all

the
~.

/NOESCSEQ [ =dev: ]
The dev:
is a terminal.
The NOESCSEQ keyword disables
recognition of escape sequences at the specified terminal.

the

When you omit the device option, VMR displays all the terminals
that do not support the recognition of escape sequences.
/EBC[=dev:],
The dev:
is a terminal. The EBC keyword enables the eight bit
character option.
The full duplex terminal driver will pass all
8 bits of the input characters to the specified device.
When you omit the device specification, the system will display
the devices that have the eight bit character option enabled.
/NOEBC[=dev:],
The
bit
the
the

dev:
is a terminal. The NOEBC keyword disables the eight
character option. The full duplex terminal driver strips off
parity bits of the input characters before passing them to
device.

When you omit the device specification, the system will display
the devices that do not have the eight bit character option
enabled.
/ECHO[=dev:],
The dev:
is a terminal.
The ECHO keyword enables the echo
option.
The full duplex terminal driver will display each
character that is typed on the specified device.
When you omit the device specification, the system
the devices that. have the echo option enabled.

8-34

will

display

VMR COMMANDS

/NOECHO[=dev:]
The dev:
is a terminal. The NOECHO keyword disables the echo
option.
The full duplex terminal driver will not display the
characters that are typed on the terminal.
When you omit the device specification, the system
the devices that have the echo option disabled.

will

display

/FDX[=dev:],
The dev:
is a terminal. The FDX keyword enbles the full duplex
option.
The full duplex terminal driver will accept input from
the specified device while simultaneously outputing to it.
When you omit the device specification, the system will
the devices that have the full duplex option enabled.

display

/NOFDX[=dev:],
The dev:
is a terminal. The NOFDX keyword disables the full
duplex option. The full duplex terminal driver will not process
input and output from the specified _device simultaneously.
When you omit the device specification, the system will display
the devices that do not have the full duplex option enabled.
/FORMFEED[=dev:],
The dev:
is a terminal. The FORMFEED keyword indicates that the
specified device has a hardware formfeed.
When you omit the device specification,
devices that have hardware formfeeds.

VMR

will

display

the

The dev:
is a terminal. The NOFORMFEED keyword indicates
the specified device does not have a hardware formfeed.

that

When you omit the device specification, VMR will display
devices on the system that do not have hardware formfeeds.

the

/NOFORMFEED[=dev:],

HFILL=dev: [value]
The value is a number between 0 and 7.
The HFILL keyword
specifies the number of file characters that the full duplex
terminal driver is to place after a carriage return when
outputing to the specified device.
When you omit the value parameter, VMR will display the number of
fill characters currently being output by the device driver to
the specified device.
/HHT[=dev:],
The
The dev:
is a terminal. Full duplex terminal driver only.
HHT keyword· indicates that the specified device has a hardware
horizontal tab.
When you omit the device specification, VMR will display
terminals on the system that have hardware horizontal tabs.

8-35

the

VMR COMMANDS
/NOHHT[=dev:],
The dev:
is a terminal.
Full duplex terminal driver only.
The
NOHHT keyword indicates that the specified device does not have a
horizontal tab.
When you omit the device specification, VMR will display
the terminals that do not have hardware horizontal tabs.

all

/LINES=dev: [value],
The value is a number between 1-255 that establishes the number
of lines per page on the specified device.
If you specify a
number that is larger than the number of lines per page possible
for a given device, VMR will default to the largest number
possible for that device.
When you do not specify a value, VMR will display the
page for the specified device.

lines

per

/LOG ON
Enables logging onto terminals in a multiuser protection system.
/NOLOGON
Disables logging onto terminals in a multiuser protection system.
LOGON and NOLOGON clear and set a flag checked by the HELLO
command when a user attempts to log onto a terminal.
This Set
option provides a means of preventing users from accessing the
system during system maintenance or account file maintenance
activity, for example.
/LOWER[=dev:],
The dev:
is a terminal.
The LOWER keyword specifies that
lower-case characters are not to be converted to upper case when
they are received from the specified terminal.
When you omit the device specification, VMR will display
terminals for which lower-case characters are not converted.

all

/NOLOWER[=dev:],
The dev:
is a terminal. The NOLOWER keyword resets the terminal
characteristics of the specified terminal so that lower-case
characters received on input are automatically converted to upper
case and echoed as upper case.
When you omit the device specification, VMR will display
terminals for which conversion to upper case is specified.

all

/PRIV[=dev:],
The dev:
is a terminal. The PRIV
terminal to privileged status.

keyword

When you omit the device specification,
privileged terminals on the system.

VMR

sets
will

the

specified

display

all

NOPRIV /NOPRIV[=dev:].
Sets the identified terminal to nonprivileged status. Absence of
=dev:
results in a display of all nonprivileged terminals.

8-36

VMR COMMANDS
/REMOTE[=dev:],
The dev:
is a terminal with a line to a DZll multiplexer.
(The
line can also be a DHll with the full duplex terminal driver.)
The REMOTE keyword declares that the specified terminal
is
connected to a modem and can therefore be connected to the system
by means of a dial-up network.
When you omit the device specification,
remote lines (including DHll lines).

VMR

will

display

all

/NOREMOTE[=dev:],
The dev:
is a line to a DZll multiplexer.
(The line can also be
a DHll with the full duplex terminal driver.) The NOREMOTE
keyword establishes the terminal's line as a local line not
connected to a modem.
When you omit the device specification, VMR will display all
local lines (including DLll, DHll, DJll, and DZll multiplexers).
/RPA[=dev:],
The device is a terminal.
The RPA keyword
enables
the
read-pass-all option. The full duplex terminal driver will pass
all characters input at the keyboard to the terminal's input
buffer.
When you omit the device specification, VMR will display all of
the devices on the system that have the read-pass-all option
enabled.
/NORPA[=dev:],
The dev:
is a terminal.
The NORPA key word disables the
read-pass-all option.
The full duplex terminal driver will not
pass special function characters (for example CNTRL C)
input at
the keyboard to the terminal's input buffer.
When you omit the device specification, VMR will display all the
devices
on the system that have the read-pass-all option
disabled.
/SLAVE [=de~v:]
The dev:
is a terminal. The keyword establishes the specified
terminal as one that can enter data only if it is solicited from
a task;
thus, the specified terminal always rejects unsolicited
input (other than CTRL/O, CTRL/Q, and CTRL/S).
When you omit the device specification, VMR
terminals currently classified as slaved.

will

display

all

/NOS LAVE [ ==dev: ] '
The dev:
is a terminal. The NOSLAVE keyword sets the
terminal to nonslave status.
When you omit the device specification, VMR
terminals currently classified as nonslave.

8-37

will

specified

display

all

VMR COMMANDS
/SPEED=dev: [recv:xmit],
The dev:
is a terminal. The recv argument is the baud rate at
which characters are input to the computer from the terminal.
The xmit argument is the baud rate at which the computer outputs
characters to the terminal. The SPEED keyword establishes the
receive and transmit baud rate for terminals attached to the
system through a DHll or DZll multiplexer. You must specify both
arguments when setting the speed. If you do not specify either
VMR will display the current settings.
Valid baud rates for the DHll are:
0, 110, 150, 200, 300, 600,
1200, 1800, 2400, 4800, 9600. A (user-specified baud rate A),
and B (user-specified baud rate B). Valid baud rates for the
DZll are:
O, 110, 150, 300, 600, 1200, 1800, 2000, 2400, 3600,
4800, 7200, and 9600. The receive and transmit baud rates for
the DZll must be the same;
the DZll does not support split
speeds.
/SYSUIC[=uic],
The uic has the format [g,m] and g and m are octal numbers that
represent a group and member respectively. The /SYSUIC keyword
establishes the UIC for the system and all system tasks. On most
systems,
the system UIC is
[1,54]. These UIC values are the
initial defaults on virgin systems.
This UIC becomes the default UIC used by the Load command and the
install-run-remove option of the Run command.
When you omit the UIC specification, VMR will display the current
UIC.
/TERM=dev: [value],
The dev:
is a terminal and value is a RSX-llM supported terminal
type.
The TERM keyword establishes the terminal type of the
specified device.
When VMR sets the
terminal
type,
it
automatically sets the HFILL, VFILL, CRT, FORMFEED, and HHT
characteristics for the terminal. The standard terminal types
are as follows:
ASR33

ASR35

KSR33

LA30P

LA30S

LA36

LA120

LA180S

VT05B

VT50

VT52

VT55

VT61

VTlOO

If you specify a terminal type that is unknown to VMR, VMR will
not set any device characteristics for the terminal. However,
VMR will store the value you have specified in the Unit Control
Block (UCB).
When you omit the value parameter, VMR will display the
type of the specified device.

terminal

Note that VMR will also accept another form of the
as follows:

command,

SET /term-type=dev:

8-38

SET

VMR COMMANDS
term-type
One of the standard terminal types listed above
dev:
An ASCII device name
For
example,
SET
/TERM=TT16:VT52.

/VT52=TT16:

equivalent

SET

/TYPEAHEAD[=dev:],
The dev:
is a
terminal.
The TYPEAHEAD keyword enables the
TYPEAHEAD option for
the specified device.
The full duplex
terminal driver will buffer input characters before passing them
to a
requesting task.
Thus characters input during periods
between requests will not be lost.
/NOTYPEAHEAD[=dev:],
The dev:
is a terminal. The NOTYPEAHEAD keyword disables the
TYPEAHEAD option for
the specified device.
The full duplex
terminal driver will not buffer characters to prevent their loss.
/UIC[=uic[:dev:]]
The specified UIC is established as the default UIC for
the
entering terminal unless dev:
is specified,.
If you specify
dev:, the default UIC is set for that terminal.
All tasks run
from the terminal are run with the UIC of the terminal, except in
a multiuser protection system.
In such a system, a privileged
user can override the terminal UIC with the UIC switch in the RUN
command.
Further, external MCR function tasksl are requested
with this UIC.
When you do not specify uic
(SET /UIC),
the current UIC
is
displayed.
If only dev:
is specified (SET /UIC:dev:), the UIC
for the specified terminal is displayed.
/VPILL [=dev:],
The device is· a terminal. The VFILL keyword enables the vertical
fill characters option for the specified device.
The full duplex
terminal driver will add 4 fill characters following
each
linefeed.
When you omit the device specification, VMR will display all of
the terminals on the system that have the VFILL option enabled.
/NOVFILL[=dev:],
The device is a
terminal.
The NOVFILL keyword disables the
The
vertical fill
characters option for the specified device.
full duplex terminal driver will not add any verticle file
characters following linefeeds.
When you omit the device specification, VMR will display all of
the terminals on the system that do not have the VFILL option
enabled.
l
These tasks are the MCR MOUNT,
INSTALL, DMO,
and
(which run as tasks) and all system-supplied software.

8-39

UFD

commands

VMR COMMANDS
/WCHK[=dev:],
The WCHK keyword specifies for all Files-11 devices except DX:,
DY:, and DL:
and magnetic tape (MM:, MS:, and MT:) that all
writes are to be followed by a write check.
This feature
provides high reliability for data transfers to the specified
disk. Executive support for write check is a SYSGEN option and
must be selected for this command to have any effect.
When you omit the device specification, VMR displays all Files-11
disk drives with write check enabled.
/NOWCH~[=dev:],

The NOWCHK keyword specifies that write check is to
for the specified device.
When you omit the device specification,
disks that support write check,
but
disabled.

disabled

VMR will display all
that have write check

/WRAP[=dev:],
The device is a terminal.
The WRAP keyword enables
the
wrap-around option for
the specified device. The full duplex
terminal driver
will
automatically
generate
a
carriage
return/linefeed sequence when the number of input characters
exceeds the buffer size of the specified device.
Both the
carriage return and linefeed are transparent and do not appear in
the input buffer.
When you omit the device specification, VMR will display all of
the terminals on the system that have the wrap-around options
enabled.
/NOWRAP[=dev:]
The device is a terminal. The NOWRAP keyword disables the wrap
around option for the specified device. The full duplex terminal
driver will not accept input characters beyond the input buffer
size.
When you omit the device specification, VMR will display all of
the terminals on the system that have the wrap a~ound option
disabled.
Example
>SET /BUF=LPO:
BUF=LPO:l32.
Displays the current buffer size of LPO:
>SET /BUF=TT1:40.
Set TTl:

buffer size to 40(10).

>SET /CRT=TT3:
Enable the backspace deletion
TT3:.

option

8-40

the

display

terminal

VMR COMMANDS
>SET /CRT
CRT=TT3:
Display all terminals that support the backspace deletion option.
>SET /ESCSEQ=TT3:
Establish terminal TT3:
sequences.

terminal

that

can

send

escape

>SET /ESCSEQ
ESCSEQ=TT3:
Display all terminals that can send escape sequences.
>SET /NOESCSEQ=TT3:
Disable support of escape sequences on TT3:.
>SET /LA30S=TT2:
>SET /LA30S
LA30S=TTO:
LA30S=TT2:
Set TT2: as an LA30S.
Display all LA30S terminals.
>SET /PRIV=TTO:
Set TTO: to a privileged terminal.
>SET /PRIV
PHIV=TTO:
PHIV=TTl:
Display all privileged terminals.
>SET /REMOTE=TT21:
Set the terminal line corresponding to TT21:
lineo

as a remote dial-in

>SET /REMOTE
REMOTE=TTl:
REMOTE=TT2:
REMOTE=TT3:
REMOTE=TT4:
REMOTE=TT21:
Display all terminals that are currently set
lines. TTl:, TT2:, TT3:, and TT4:
>SET /SLAVE=TT3:
Set TT3: to a slave terminal.
>SET /WCHK=DKl:
Enable write check on DKl:.

8-41

remote

dial-in

VMR COMMANDS
Memory Allocation Keywords
/BOT=pname:value,
The pname is a 1- to 6-character alphanumeric partition name and
value a number of 64-byte blocks. The BOT keyword directs VMR to
move the bottom boundary of the specified system-controlled
partition up or down the amount indicated by the value parameter.
The BOT keyword modifies the bottom boundary of a partition even
though it has tasks installed in it.
If you contract a partition
that contains an installed task or loaded driver, VMR displays a
warning message;
the task or driver may no longer fit in the
partition.
The value parameter can be supplied in five formats:
+value
Moves the bottom boundary up by the specified amount.
the bottom boundary up makes the partition smaller.

Moving

NOTE
You can supply the value
in the same
units as the base and size parameters in
the MAIN keyword described below.
-value
Moves the bottom boundary down by the specified amount.
Moving the bottom boundary down makes the partition larger.
value
Establishes the total partition size equal to
value by moving the bottom of the partition.

the

specified

+*or*
Note that
Moves the bottom boundary up as far as possible.
using this format will cause the bottom boundary to move up to
the bottom of the first fixed task or driver loaded into the
If there
partition at the time the BOT keyword is executed.
is nothing loaded into the partition, it will assume a size of
1 64-byte block.

-*
Moves the bottom boundary down as far as possible.
Using this
format will cause the bottom boundary of the partition to move
down to the top boundary of the partition below it or to the
top of the Executive if the effected partition is the lowest
partition in memory.
/MAIN=pname[:base:size:type]
Establishes a main partition.
pname
The 1- to 6-character alphanumeric partition name.

8-42

VMR COMMANDS
: basE~
The physical base address of
number of 64-byte blocks.

the

partition

specified

:sizE~

The size of the partition specified as a number of 64-byte
blocks.
The maximum size
is 0 to 1920.K words for a task,
common, or main partition.
:type
SYS for a main partition, DEV for a common partition that maps
the device registers, COM for a common partition, or TASK for
a task partition.
Main partitions
drivers.

are

allocated

for

user

tasks

and

loadable

Device partitions are allocated for device commons which are used
by tasks to access the device registers on the I/O page.
You may enter base and size in any of the following formats;
Format

Calculated Value

nnnn
nnnn.
nnnK
nnn.K

Octal (nnnn*lOO)
Decimal (nnnn.*64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

nnnn is a number to which a multiplication factor is applied to
determine the value used.
Valid ranges of calculated values are:
Octal
Decimal
Octal K
Decimal K

O<=base<l 77777
O.<=base<65535
OK<=base<3777K
O.K<=base<2047.K

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

For system controlled partitions, size may range from 0 to 1920.K
or any valid representation of these limits.
You can specify the base address of a partition through a
wildcard (*) for TASK or SYS partitions in a mapped system.
When
you specify a wildcard (*), VMR creates a partition at the lowest
address possible for a partition of the size you have specified.
You can also 'specify the size of a partition through a wildcard
(*)
for SYS partitions.
When you specify the wildcard (*), VMR
creates the largest possible partition starting at the base
address you have specified in the base parameter.
When you specify wildcards for both the base and size, VMR will
create a partition that will completely fill the first gap in the
existing partition layout.
If you do not specify base, size, or type, VMR will display the
values of these parameters for the named partition.
If the named
partition is a main task-controlled partition, VMR also displays
the parameters of all its subpartitions.

~·

8-43

VMR COMMANDS
/NOMAIN=pname
Eliminates a named partition from the system. The partition you
specify will be eliminated from the list of partitions and the
system.
If any tasks or commons are installed in or attached to
the partition, the partition will not be eliminated and VMR will
generate an error message.
SUB
is the keyword that establishes a subpartition.
Subpartitions
may only be established in user-controlled main partitions.
mname
is the 1- to 6-character
main
partition
name.
The
subpartition being defined becomes a subpartition in the named
main partition.
:pname
is the 1- to 6-character subpartition name. The subpartition
being defined becomes a subpartition of the main partition
specified in mname.
:base
is the physical base address of the subpartition, specified as
a number of 64-byte blocks.
:size
is the size of the subpartition,
64-byte blocks.

specified

number

Base and size may be entered in any of the following formats;
nnnn is a number to which a multiplication factor is applied to
determine the value used.
Format

Calculated Value

nnnn
nnnn.
nnnK
nnn.K

Octal (nnnn*lOO)
Decimal (nnnn.*64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

Valid ranges of values are:
Octal
O<=base<lOOOO
Decimal
O.<=base<4096.
Octal K
OK<=base<200K
Decimal K O.K<=base<2047.K

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

Example:
Any of the following inputs for size will allocate a 2048.
subpartition.

byte

40
32.
lK
l.K

If base and size are omitted,
the
displayed for the named subpartition.
8-44

current

values

will

VMR COMMANDS
NOSUB
is the keyword that eliminates the named
system.

subpartition

from

the

/POOL[=TOP]
Increases the size of the dynamic storage region.
TOP
The first location in memory used for partition allocation.
You specify TOP in units of 64-byte blocks. You can specify
it in octal or decimal. When you do not specify TOP, VMR
displays the current top of memory, the size of the longest
block of pool space in words, and the total number of words in
the pool. The display's format is:
POOL = top:max:total
where top is given in units of 64-byte
total are in decimal words.

blocks,

and

max

and

You can specify TOP as a wildcard (*). The wildcard directs VMR
to supply the maximum amount of pool possible. Specify the
wildcard as follows:
SET /POOL=*.
If more pool is requested than can be supplied, a warning message
is printed, and the maximum amount of pool possible is supplied.
/POOLSIZE[=value]
This command allows you to specify a total amount of pool
rather
than a top address.
If you do not specify a value, VMR will
display the current top of memory, the size of the longest block
of pool space in words,
and the total number of words in the
pool.
/TOP=pname:value
Where pname is a 1- to 6-character alphanumeric partition name
and value is a number of 64-byte blocks. The TOP keyword directs
VMR to move the top boundary of the · specified system-controlled
partition up or down the amount indicated by the value parameter.
The TOP keyword modifies the top boundary of a partition even if
the partition has tasks installed in it.
If you modify the
partition so that it is too small to hold the tasks installed in
it, VMR will display a warning message and modify the partition
anyway.
The value parameter can be supplied in five formats:
+value
Moves the top boundary up by the specified amount.
top boundary up makes the partition larger.
NOTE
You can supply the value in the same
units as the base and size parameters in
the PAR keyword described above.

8-45

Moving the

VMR COMMANDS
-value
Moves the top boundary down by the specified amount.
the top boundary down makes the partition smaller.

Moving

value
Establishes the total partition size equal
value.

the

specified

+* or*
Moves the top boundary up as far as possible.
Using this
format causes the top boundary to move to the bottom boundary
of the partition above it or to the top of memory if the
partition is the top partition in memory.

-*
Moves the top boundary down as far as possible.
Using this
format causes the top boundary to move down to the top of the
first fixed task, driver, or common loaded into the partition
at the time the TOP keyword is executed.
If nothing is loaded
into the partition, the partition assumes a size of l
64-byte
block.

Examples
>SET /MAIN=SYSPAR:420:140:TASK
Define a partition called SYSPAR whose base address
and whose length is 14000(8) bytes.

42000(8)

and

all

>SET /MAIN=SYSPAR
MAIN=SYSPAR:0420:0140:TASK
SUB=SYSPAR:MCRPAR:0445:0056
Display the parameters of the main partition SYSPAR
its subpartitions.

>SET /NOMAIN=SYSPAR
Eliminate main partition SYSPAR.
SET /MAIN=GEN:l000:6000:SYS
Define a main partition called GEN as a system-controlled
partition whose base address
is 100000(8) and whose length is
600000 (8) bytes.
>SET /POOL=420
Define the first location in memory for partition allocation
user defined partition can begin below 42000(8)).

(No

>SET /POOL
POOL=0420:150:430.
The first available location for
user partitions is 42000(8);
the longest free block is 150. words, and the total of all pool
space is 430. words.

8-46

VMR COMMANDS

If a partition currently hosts
installed tasks or loaded
drivers,
and a command
(for example, /NOMAIN) attempts to
eliminate the partition, VMR rejects the command.

When you define a partition, the name must not already be
defined as a partition.
In addition, a main partition cannot
overlap any other main partition.
(An exception is for DEV
partitions in the I/O page;
these can overlap.)

The numeric value convention (a number followed by a period
(.)
is explicitly decimal)
applies to all the SET command
numeric values.

The address specified with the POOL command must be lower
than the base address of the first partition in the system
with the exception of partition LDR for a
resident loader,
which is in the Executive;
LDR for loadable Loader.

Once you have allocated space to the dynamic storage region,
you cannot recover the space for use in partitions (you
cannot contract pool).

If the last partition is system-controlled, its top address
is modified by Save at boot time to reflect the actual top of
physical memory of the hardware in use •

•

8-47

VMR COMMANDS

TAS
TASK LIST
Use the TASKLIST command to display a description of each installed
task in the system. The display contains in columnar form, from left
to right:
1.

Task name

Task version identification

Task Control Block (TCB) address

Partition name

Task priority

Size of task in bytes (octal)

Load device identification

Disk address logical block number (octal) in a virgin system,
and the image or task file identification in a saved system
image

Task memory state

Format
TAS[KLIST]

Example
VMR>TAS
••• LDR 10
TKTN
03.94
MCR ••• 02.01
••• MCR 01
FllACP M0320
DBOFCP M0320
••• DMO 22.00
•..• INI 20.01
••• MOU 22.15
• • • UFD V0410
PMD ••• 04
SHF ••• 04
.... INS 04
••• SAV 04.22
••• BAD 05
• ., • AT. 04.24
• ., • BOO 03.4
.... ACS 01
LPINIT 01
• .. • PIP Ml332
.... LOA 03.3
• ,.• UNL 0 2 .8
VMR>

115450 LDRPAR 248.
113400 TKNPAR 248.
114300 SY SPAR 160.
112500 GEN
160.
115200 GEN
149.
115100 GEN
149.
114700 GEN
140 •
114500 GEN
140.
114200 GEN
140.
113700 GEN
140 •
113300 GEN
130.
113200 SY SPAR 105.
114400 GEN
100.
114100 GEN
100.
112600 GEN
100.
114600 GEN
65 •
115000 GEN
50.
113600 GEN
50.
113500 GEN
50.
113100 GEN
50 •
113000 GEN
50.
112700 GEN
50.

00002400 LBO:- FILE ID:(2177,15) FIXED
00010000 LBO:- FILE ID: (2247 ,14)
00010000 LBO:- FILE ID: (2234,15)
00012000 LBO:- FILE ID: (2251,14)
00024000 LBO:- FILE ID: (2252,14)
00063500 LBO:- FILE ID: (15221,124)
00040000 LBO:- FILE ID: (2230,14)
00040000 LBO:- FILE ID: (2232,14)
00040000 LBO:- FILE ID: (2240,14)
00040000 LBO:- FILE ID: (2246,14)
00020000 LBO:- FILE ID: (3775,30)
00010000 LBO:- FILE ID: (3256,546)
00040000 LBO:- FILE ID: (2231,14)
00040000 LBO:- FILE ID: (2237 ,14)
00137700 LBO:- FILE ID: (1462,23)
00057700 LBO:- FILE ID:(l467,15)
00040000 LBO:- FILE ID: (2226,14)
00040000 LBO:- FILE ID: (2224,14)
00015500 LBO:- FILE ID: (4346,32)
00054200 LBO:- FILE ID: (1511,15)
00040000 LBO:- FILE ID: (2233,15)
00040000 LBO:- FILE ID: (2250,14)

~--\

•

Allllt\
8-48

VMR COMMANDS
On a system image generated for a PDP-11/70 with more than 124K
words of memory, the size field (fifth column) contains 8-digit
rather than 6-digit numbers. This display is for a virgin system
image .•
FIXED indicates that the task is fixed in memory.
VMH.>TAS
• LDR.
TKTN
••• MCR
••• SYS
FllACP
••• DMO
••• INI
••• MOU
••• UFD
PMD •••
SHF •••
••• INS
••• SAV
••• BAD
PRT •••
••• BOO
••• ACS
••• PIP
••• PSE
••• AT.

LDR
248.
SYSPAR 248.
SY SPAR 160.
160.
GEN
FCPAR 149.
GEN
140.
GEN
140.
GEN
140.
GEN
140.
PMDPAR 130.
SY SPAR lOS.
GEN
100.
GEN
100.
GEN
100.
PMDPR
70.
GEN
so.
so.
GEN
so.
GEN
so.
GEN
GEN
1.

000000
010000
010000
010000
026000
040000
040000
040000
040000
020000
010000
040000
040000
040000
020000
040000
040000
OS4300
031600
040000

LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE

ID: ( 0 I 0) FI x ED
ID: (2S72,ll)
ID: (2S63,ll)
ID: (2S6S,ll)
ID: (2S76,ll)
ID: (2SS6,ll)
ID: (2SS7 ,11)
ID:(2S67,ll)
ID: (2S73,ll)
ID: (2610.12)
ID: (2606,11)
ID: (2S62,ll)
ID: (2S70,ll)
ID: (6162,34)
ID: (S210,6)
ID: (2273,30)
ID: (1066,22)
ID: (2627 ,11)
ID: (SSS2,4)
ID: (S013,4)

The preceding display is from a saved system.
It differs from a
virgin system in that the file ID of the task file, rather than
the logical block number, is displayed.

8-49

VMR COMMANDS

TIM
TIME
Use the TIME command to set the time
display the time and date.

day

and

the

date,

this

parameter

Formats
TIM[E]

[hrs:mins[:secs]]

[ml/day/year]

[hrs:mins[:secs]]

[day-m2-year]

or
TIM[E]

Parameters
hrs

Hours (range O through 23).

mins

Minutes (range O through 59).

secs

Seconds
(range
optional.

Num~ric

Three-letter abbreviation for month.

day

Day (range l

year

Year (range O through 99).
Year is relative
thus, 1977 is entered as 77.

through

,,..I
59);

representation of month (range 1 through 12).

through 31).
to

1900;

displays

the

Examples
>TIM
10:23:31 03-MAY-79
Display the current system image time and date.
>TIM 1:30 5/3/79
Set the time to 01:30:00 and the date to 03-MAY-79

Notes
1.

If you specify neither time nor date,
current system image time and date.

If you specify the time and date, VMR sets the system image
clock and calendar.
If you specify only the time, VMR sets
only the clock;
if you specify only the date, VMR sets only
the calendar.

You can specify the time and date in any order.

All numeric values are decimal.
used.

8-50

VMR

terminating

period

•

VMR COMMANDS

UNF
UNE~IX

Use the UNFIX command to free· a fixed task
UNFIX is the complement of the FIX command.

from

the

system

image.

If a fixed task exits or aborts, it still occupies
memory of the partition.

the

system

image

Format
UNF[IX]

taskname

Parameter
taskname
The task that you wish to unfix in memory.
Excample

>UNFIX XKE
Unfix task XKE, freeing the partition in which it resides.

,'"--'

8-51

VMR COMMANDS

UNL
UNLOAD
Use the UNLOAD command to remove a loadable device driver from the
system image. If a device is attached, its driver cannot be unloaded.
To unload a device driver from the system image, the driver's STB file
must reside on the same disk and under the UFD that corresponds to the
UIC of the system image file.
The UNLOAD command cannot remove a data base from the system
even if the data base was loaded by means of the LOAD command.
Format
UNL[OAD] dd:
Parameter
dd:
A 2-character ASCII device name
Example
VMR>UNL LS:

!UNLOAD LPSll DRIVER (LSDRV)

8-52

image,

VMR COMMANDS
8.6

VMR ERROR MESSAGES

Following are the VMR command error messages.
When a VMR error
message applies to more than one command, the applicable command is
indicated above the associated message description.
VMR -- ADDRESSING EXTENSIONS NOT SUPPORTED
INSTALL
You are trying to install a task that was built using the VSECT
(Virtual section)
directive into a system image that does not
support the VSECT feature.
VMR -- ALIGNMENT ERROR
The base address or size of the partition you are attempting
create conflicts with existing partitions or physical memory.

VMR -- BASE ADDRESS MUST BE ON A 4K BOUNDARY
INSTALL
The virtual base address of your task is
boundary.

not

aligned

VMR -- BASE MISMATCH COMMON BLOCK <common-name>
INSTALL
The base address of the partition does not match that of
common blocko
Applicable to unmapped system images only.

the

VMR -- CANNOT FIX A TASK IN A SYSTEM CONTROLLED PARTITION
FIX
This is a VMR restriction. To fix a task in a system-controlled
partition,
use the MCR Fix command and then save the system
image.
VMR -- CANNOT INSTALL TASKS FROM OTHER THAN LB:
INSTALL
When you SAVE a system, SAVE deletes from the system image all
tasks and commons that were not installed from the library device
LB:. Therefore, you cannot install a task or a common from other
than LB:.
VMR -- CANNOT LOAD/UNLOAD A PSEUDO DEVICE
LOAD AND UNLOAD
The device name you specified was that of
Pseudo devices cannot be loaded or unloaded.

pseudo

device.

VMR -- CHECKPOINT AREA TOO SMALL
INSTALL
The area you have allocated for checkpointing in your task
image
file
is smaller than the partition into which you are attempting
to install your task.
The system image does not support the
dynamic allocation of checkpoint space.

8-53

VMR COMMANDS
VMR -- CHECKPOINT SPACE TOO SMALL, USING CHECKPOINT FILE
INSTALL
This is a warning message.
The checkpoint space you have
allocated in your task image file is too small to hold your task
(usually because of the /INC keyword).
The system image supports
the dynamic allocatio.n of checkpoint space. It will use the
checkpoint file to store your task when it rolls it out to disk.
Since no checkpoint file exists when you boot your system, you
should consider this message to be a fatal error if it is issued
by any of the system tasks during the boot. These tasks are MCR,
MOU, SAV, and FllACP.
VMR -- CIRCULAR REDIRECT ERROR
REDIRECT
Your attempt to redirect a device has
result in a circular device list.

failed

because

would

during

from

VMR -- COMMAND I/O ERROR
The system has detected an
indirect file.

I/O

error

read

VMR -- COMMAND SYNTAX ERROR command line
The syntax of the printed command line is incorrect.
VMR -- COMMON BLOCK CURRENTLY INSTALLED
INSTALL
You are attempting to install a common
been installed.

block

that

has

already

INSTALL
A task's request for access to a common block has been
because the requested partition is a task partition.

rejected

VMR -- COMMON BLOCK IS A TASK PARTITION common-name

VMR -- COMMON BLOCK NOT LOADED common-name
INSTALL
The common block specified by VMR in the error message has been
linked to your task but it has not been installed. The common
block must be installed before your task can be installed.
VMR -- COMMON BLOCK OCCUPIED
INSTALL
An attempt was made to load a common block that was occupied.
VMR -- COMMON BLOCK PARAMETER MISMATCH common-name
INSTALL
The parameters of the common block named in the error message do
not match the parameters in the label block of the task that
references the common.
VMR -- COMMON BLOCK SEGMENT COUNT ERROR
INSTALL
The command attempted to
install a
resident library
with
overlays,
but the number of overlay segments in the task header
differs from the number specified in the segment descriptors.

8-54

VMR COMMANDS
VMR -- DEVICE ddn:

IS ATTACHED

UNLOAD
You are attempting to unload a driver that has one or more of its
device units attached.
The first attached unit is ddn:. You
cannot unload a driver that nas device units attached.
VMR -- DEVICE ddn:

NOT IN SYSTEM

DEVICES
The device you requested in the Device command does not exist
the system image.

SAVE
You are attempting to save an image on a
exist on your host system.

not

device

that

does

REDIRECT
You are attempting to redirect I/O requests to a device that does
not exist on your host system.
LOAD AND UNLOAD
You have specified a device in your load command for which
is no data base.
This is caused by one of two conditions:
1.

The device does not exist in the system device tables,

The driver file does not contain a loadable data base.

INSTALL
You have specified a device in your INSTALL command that has
been defined in the system image.

there

not

VMR -- DEVICE NOT MOUNTED
You have not mounted the device that contains
file.

the

system

image

VMR -- DEVICE NOT REDIRECTABLE
REDIRECT
The specified device cannot be redirected.
VMR -- DRIVER ALREADY RESIDENT
LOAD
You have specified a device driver that is already loaded or that
is permanently resident in the system image.
VMR -- DRIVER BUILT WITH WRONG STB FILE
LOAD
The symbol definition file for the driver is not compatible with
the Executive symbol definition file
for
the current system
image. This means that your driver has been built for
another
system and must be rebuilt before you can load it into the
curremt system.
UNLOAD
The symbol definition file for the driver is not compatible with
the symbol definition file of the current Executive.
This
probably means that the most recent copy of the driver
is built
for another Executive.
If they exist, try making older versions
of the driver have the highest file sequence number.

8-55

VMR COMMANDS
VMR -- DEVICE NOT TERMINAL
You have attempted
nonterminal device.

set

SET
terminal

characteristics

for

that

VMR -- DEVICE NOT VARIABLE SPEED MULTIPLEXER
SET
You have attempted to set the baud rate for a
not attached to a DHll or DZll multiplexer.
VMR

terminal

DRIVER CANNOT BE UNLOADED
UNLOAD
You have attempted to unload a permanently resident driver
is, a driver linked to the Executive).

(that

VMR -- DRIVER NOT LOADED
UNLOAD
You have specified a driver in your UNLOAD command
resident in memory.

that

not

VMR -- DRIVER REQUIRES RUNNING SYSTEM FOR LOAD/UNLOAD
LOAD
The driver you have requested has the symbols $ddLOA or $ddUNL in
its source. RSX-llM does not support those calls. Note however,
that these symbols are reserved for future use by the MCR LOAD
and UNLOAD commands.
VMR -- EXECUTIVE IS TOO LARGE
Your Executive is too large to be accommodated in the system
image.
If your Executive is larger than 16K words, this message
indicates that you have not included 20K Executive support during
SYSGEN.
If you did include support for a 20K Executive, this
message indicates that the Executive is larger than 20K.
In
either case, the system is unusable.
VMR

FILE name HAS ILLEGAL FORMAT
LOAD
Your driver's symbol definition file contains illegal object code
or data.

VMR -- FILE name HAS INCONSISTENT DATA
FIX-IN-MEMORY
You are attempting to fix a partition or a task that is logically
beyond the end of the system image file.
LOAD
The partition for loadable drivers is logically beyond the end of
the system image file.
Your driver task does not conform to the loadable driver
guidelines or the driver has an invalid loadable data base.
(Refer to RSX-llM Guide to Writing an I/O Driver.)
INSTALL
The partition of the common library you are attempting to load is
logically beyond the end of the system image file.

8-56

VMR COMMANDS
VMR -- FILE name NOT A VALID DRIVER TASK IMAGE
One of three things has occurred:

VMR

Your driver's task image has been overlaid,

Your driver has a header,

Your driver has referenced a resident library.
FILE NOT CONTIGUOUS

INSTALL
You have attempted to install a task from a
Task images must be contiguous files.

noncontiguous

file.

LOAD
The file ddDRV.TSK
contiguous.

not

contiguous.

This

file

must

VMR -- FILE NOT FOUND
You have requested a file that is not in the UFO
you have specified.

the

volume

VMR -- FILE NOT TASK IMAGE
INSTALL
The data in the label block of your task is incorrect, indicating
that your file is not a task image.
VMR -- ILLEGAL DEVICE/VOLUME
You have attempted to save
device. Valid devices are:

VMR

SAVE
your system

CT:

Tape cassette

DD:

DECtape I I

OT:

DECtape

DX:

Flexible diskette

DY:

RX02 floppy disk

MM:

TE/TU16/TU45 magnetic tape

MS:

TS04 magtape

MT:

TE/TU10/TS03 magnetic tape

PP:

Paper tape

image

invalid

ILLEGAL DRIVER TASK APR USAGE

LOAD
Your device driver must be built for APR 5 {addresses must
at 120,000)o

start

VMR -- ILLEGAL ERROR SEVERITY CODE code
This message indicates an internal failure in VMR.
If this error
message persists, contact a Digital software representative.

8-57

VMR COMMANDS
VMR -- ILLEGAL FILE S~ECIFICATION file specification
The file specification printed following the error message has an
illegal format or contains wild card specifiers.
VMR

ILLEGAL FIRST APR
You have built your task
following rules apply:

VMR

INSTALL
using an

incorrect

base

APR.

The

its

base

A nonprivileged task must be built with APR
APR.

A privileged task that wishes to map the Executive routines
and data structures must be built with APR 4 as its base APR
if the Executive is 16K words or less.

A privileged task that wishes to map the Executive routines
and data structures must be built with APR 5 as its base APR
if the Executive is 20K words or less.

A privileged task that does not map into the
be built with APR 0 as its base APR.

Executive

must

ILLEGAL FUNCTION
You have entered a command that VMR does not recognize.

VMR -- ILLEGAL GET COMMAND LINE ERROR CODE
This error indicates a system failure. If this message persists,
contact a Digital software representative.
VMR -- ILLEGAL KEYWORD VALUE
You have entered a value for a keyword that exceeds its limits.
VMR -- ILLEGAL OPERATION FOR UNMAPPED SYSTEM
SET
The specified keyword (/POOLSIZE)
is
only.

valid

mapped

systems

VMR -- ILLEGAL PRIORITY
INSTALL AND ALTER
You have specified a priority that is out of range (that is,
l to 250(10), inclusive).
VMR

not

ILLEGAL SWITCH /switch
The switch printed following the error message is
the context of the command line you have entered.

incorrect

VMR -- ILLEGAL USE OF WILDCARD
SET
In an unmapped system, specification of a wildcard (*) with the
/TOP, /BOT, and /POOL keywords is not permitted. Also, you
cannot specify a wildcard for the "size" parameter with task
partitions.

8-58

VMR COMMANDS
VMR -- ILLEGAL VALUE FOR SYMBOL symname IN FILE name
LOAD AND UNLOAD
LOAD or UNLOAD has determined that symbol symname in the STB file
name has been defined to an illegal value. This can occur for
several reasons, some general and some specific to
individual
symbols.
For example, in general, most symbols cannot be defined
to zero or to an odd number.
A specific example is the symbol
$INTSV.
$INTSV must not be referenced by mapped loadable
drivers.
VMR -- INCORRECT ASSIGNMENT OF SY:

OR LB:

This is a warning message. The device, SY:
and LB:
are not
assigned to the same device as the system image file you are
attempting to VMR.
VMR -- INDIRECT COMMAND SYNTAX ERROR command line
You have entered an improper indirect command file specifier.
VMR -- INDIRECT FILE DEPTH EXCEEDED command line
You have attempted to exceed more than
files.

two

levels

indirect

VMR -- INDIRECT FILE OPEN FAILURE command line
The indirect command file in the printed command line
be opened.

could

not

the

boot

VMR -- INSTALL DEVICE NOT LBO:
INSTALL
You have attempted to install a task from
device.

other

than

VMR -- INSTALLED TASKS MAY NO LONGER FIT IN PARTITIONS
SET
You have shortened a partition so that the tasks that are
installed in it may no longer fit.
This is a warning message.
VMR will shorten the partition even though this situation exists.
VMR -- INTERRUPT VECTOR ALREADY IN USE
LOAD
LOAD has determined that your interrupt vector does not point to
one of the nonsense interrupt entries in the system image. This
usually means that another driver is using the interrupt vector.
VMR -- INVALID DRIVER DATA BASE AT OFFSET xxxx IN FILE name
LOAD
The driver name has an invalid data base
relative to the symbol $ddDAT.

value

offset

xxxx

VMR -- INVALID INTERRUPT VECTOR
LOAD
You have specified an interrupt vector address
in your
data base that is too high for the current system image.

8-59

driver

VMR COMMANDS
VMR -- INVALID KEYWORD
You have specified a keyword that is incorrect in the context
your command.

VMR -- INVALID RECORD ADDRESS FOR FILE name
ANY COMMAND
The command has attempted to write outside of the system
file or at a byte boundary. Two possible causes are:

A corrupted system image or

An STB file that does not match the system image.

image

VMR -- INVALID SPEED
SET
This message can be caused by two things:

You have requested a speed that the multiplexer line you have
specified does not support.

You have specified unequal receive and transmit speeds for
DZll. The DZll does not support split speeds.

VMR -- INVALID TIME PARAMETER
RUN
The date or time field you have specified is incorrect.
VMR -- INVALID UIC
You have specified an illegal value for either a group number
a member number.
VMR

I/O ERROR ON INPUT FILE filename
An input I/O error occurred on the indicated file.

VMR -- I/O ERROR ON OUTPUT DEVICE
SAVE
SAVE has encountered an I/O error on
writing the system image.

the

output

device

while

VMR -- I/O ERROR ON OUTPUT FILE filename
An output I/O error occurred on the indicated file.
VMR - KEYWORD NOT SUPPORTED FOR THIS TERMINAL DRIVER
SET
The terminal driver specified during SYSGEN does not support the
specif1ed keyword
(for example,
typeahead is a
full duplex
terminal driver option only and your system contains the half
duplex driver).

8-60

VMR COMMANDS
VMR -- LENGTH MISMATCH COMMON BLOCK blockname
INSTALL
The length parameter for the common block, as described
in the
label block for the task image, does not match the corresponding
length parameter defined in the system image.
A task's label
block data must match system data for that task before it can be
installed.
VMR -- LINE NOT DZll
SET
You have attempted to set a line to remote that is not attached
to a DZll and your system contains the half duplex terminal
driver.
VMR -- LOADABLE DRIVER SUPPORT NOT IN SYSTEM
LOAD AND UNLOAD
You have attempted to load a device into or unload a device from
a system image that does not support loadable device drivers.
VMR

LOGICAL DEVICE NOT IN SYSTEM
ASSIGN
The device you have specified has not been defined and therefore
ASSIGN cannot find it in the logical device assignment table.

VMR -- LUN OUT OF RANGE
REASSIGN
You have attempted to reassign a LUN number that is higher than
the maximum number of LUNs that you allocated at task build.
VMR -- NO CHECKPOINT SPACE, ASSUMING NOT CHECKPOINTABLE
,INSTALL
This is a warning message.
You have attempted to install a
task
as checkpointable that you have not built as checkpointable.
This means that there is no checkpoint space allocated
in the
task
image :file. Since your system does not support the dynamic
allocation of checkpoint space, INSTALL does not consider the
task to be checkpointable.
VMR: -- NO LUNS
LUN
The task that you have specified as an argument of the LUN
command does not have any logical units assigned to it.
This is
not an error message;
rather, it is simply an indication that
there are no assignments to display.
VMR -- NO POOL SPACE
LOAD
The pool space required by the driver is
systE!m image.
VMR

not

available

the

NON EXISTENT MEMORY
SET
You have attempted to define a partition in nonexistent memory.

8-61

VMR COMMANDS
VMR -- NOT ENOUGH APRS FOR TASK IMAGE

INSTALL
The Task Builder allows you to specify the virtual base address
of a
task
image as a multiple of 4K. Privileged tasks that
access the Executive start at either virtual 100000(8)
or at
120000(8) depending on the size of the Executive. If the virtual
base address of the task is set too high,
there will
not be
enough APRs
rema1n1ng to map the task image.
(Refer to the
RSX-llM/M-PLUS Task Builder Manual for information on privileged
tasks.)
VMR -- OLD DEVICE ATTACHED

REDIRECT
You have attempted to redirect an attached device.
VMR -- OPEN FAILURE ON FILE filename
The indicated file cannot be opened.
VMR -- PARTITION ALREADY EXISTS

SET
You have attempted to define a partition with a name
use.

already

driver

VMR -- PARTITION IS BUSY

LOAD
The partition into which you attempted to load
full, therefore, your task cannot be loaded.

your

FIX
You have attempted to fix a task or common region partition
is full, therefore the task cannot be fixed.

that

VMR -- PARTITION name IS A COMMON

LOAD
into a common
You have attempted to load a device driver
partition.
A device driver cannot be loaded into a common
partition.
VMR -- PARTITION pname IS NOT A COMMON

LOAD
Partition xxCOM was found, but it is not a common partition.
VMR -- PARTITION pname NOT IN SYSTEM

LOAD
You are attempting to load a driver into a partition that does
not exist
in the system or LOAD found a symbol $xxCOM in the
driver and partition xxCOM does not exist in the system.
VMR -- PARTITION pname IS TOO SMALL

INSTALL
You are attempting to install a task that is too
partition you have specified.

8-62

large

for

the

VMR COMMANDS
VMR -- PARTITION NOT COMMON

INSTALL
A partition specified for a common area or library is not defined
as a common partition.
VMR -- PARTITION NOT IN SYSTEM
LOAD
The partition you have specified is not in the system image.
VMR -- PARTITION NOT SYSTEM CONTROLLED
The /TOP and /BOT
partitions only.

SET
are valid

keywords

for

system

controlled

VMR -- PARTITION par NOT IN SYSTEM, DEFAULTING TO GEN

INSTALL
This is a warning message.
You have attempted to install a
task
in a partition that does not exist.
VMR will attempt to install
the task in the partition GEN.
VMR -- PRIVILEGED TASK LARGER THAN 12K

INSTALL
You have attempted to install a privileged task that
is larger
than 12K words.
(Refer to the RSX-llM/M-PLUS Task Builder Manual
for information on privileged tasks.)
VMR -- POOL LINK ERROR AT xxxx BLOCK=yyyy zzzz
SET
When SET /POOL traced the pool linkage, it detected an error at
location xxxx in the system image.
The contents of xxxx is yyyy
and the contents of xxxx+2 is zzzz.
VMR -- PSEUDO DEVICE ASSIGNMENT ERROR

ASSIGN
You have attempted to assign a logical device name to
device.
Logical device names cannot be assigned
devices.

a
pseudo
to pseudo

VMR -- PSEUDO DEVICE REDIRECT ERROR
You have attempted to
pseudo device.

REDIRECT
redirect one

pseudo

device

another

VMR -- RECEIVE DATA OR BY REFERENCE LIST NOT EMPTY
REMOVE
A task with entries in its receive queues cannot be removed
the system image.

from

VMR -- SPACE USED

SET
You have attempted to create a partition in a storage
is already occupied.

8-63

area

that

VMR COMMANDS
VMR -- SPECIFIED PARTITION FOR COMMON BLOCK
INSTALL/
You are attempting to install a task into a common block.
VMR -- SPECIFIED PARTITION TOO SMALL
INSTALL
You are attempting to install a task into
smaller than the task.

partition

that

LOAD
You are attempting to install a driver into a partition
smaller than the driver.

that

VMR -- SYMBOL symname IS DOUBLY DEFINED BY FILE name
LOAD AND UNLOAD
The symbol symname is defined twice in
symbols are illegal.

file

name.

Duplicate

VMR -- SYMBOL symname IS UNDEFINED IN FILE name
LOAD AND UNLOAD
LOAD found the symbol symname in the file name, but the symbol is
not defined.
VMR -- SYNTAX ERROR
You have typed the command incorrectly.
VMR -- SYSTEM IMAGE IS RSX-llM-PLUS
You are attempting to use VMR on an RSX-llM-PLUS
file. This will not work and is not permitted.

system

image

VMR -- TASK ACTIVE
The task you have specified as an argument
active.
VMR

your

command

TASK ALREADY FIXED
FIX
You have attempted to fix a task in memory that is already
in memory.

fixed

VMR - TASK AND PARTITION BASES MISMATCH
INSTALL
The base of the partition does not match that of the task
installed. Applicable to unmapped system images only.

being

VMR -- TASK IS CHECKPOINTABLE
FIX
You have attempted to fix a checkpointable task
Checkpointable tasks cannot be fixed in memory.

8-64

memory.

VMR COMMANDS
VMR -- TASK IMAGE CURRENTLY INSTALLED
INSTALL
You are attempting to install a checkpointable task that has
checkpoint space allocated in its task image. The task has
already been installed. The system will allow you to
install
checkpointable tasks more than once subject to the following
rules:
1.

You must allocate checkpoint space for your task in a
checkpoint file.

You must use a different name for your
install it.

system

task

each

time

you

INSTALL
Your device is write-locked. VMR could not read
file or could not rewrite the task image header.

the

task-image

VMR -- TASK IMAGE I/O ERROR

VMR -- TASK IMAGE VIRTUAL ADDRESS OVERLAPS COMMON BLOCK block-name
INSTALL
The virtual addresses you have reserved for
the task
image
overlap those you have reserved for the common block specified in
the error message.
Corruption of the task image file may have
caused the overlap.
VMR -- TASK NAME ALREADY IN USE
INSTALL
You have attempted to install a task of
already in the system image.

the

same

name

one

VMR -- TASK NOT FIXED
UNFIX
You have attempted to unfix a task that is not fixed in memory.
VMR -- TASK NOT IN SYSTEM
You have referenced a task that you have
system.

not

installed

the

VMR -- TI REDIRECT ERROR
You have attempted to
cannot be redirected.

redirect

the

pseudo

device

TI:.

TI:

VMR -- TOO MANY COMMON BLOCK REQUESTS

•

INSTALL
You are attempting to install a
task that contains too many
common-block requests.
A task is limited to seven common block
references.
VMR -- TOO MANY LUNS
INSTALL
You are attempting to install a
task
255(10) LUN assignment requests.

8-65

that

contains

than

VMR COMMANDS
VMR -- TOP OF POOL SET TO value, REQUESTED AMOUNT NOT AVAILABLE
SET
You have requested more pool space than the system can provide,
so the maximum amount was used. This is a warning message.
VMR -- UNDEFINED COMMON BLOCK block-name
INSTALL
You are attempting to install a task that references a common
block that is not defined in the system image. This message may
indicate that the task was built for another system.
VMR -- UNKNOWN MAIN PARTITION
You are attempting an operation on a main
not exist in the system.

partition

which

does

VMR -- WARNING - LOADABLE DRIVER LARGER THAN 4K
LOAD
You are loading a driver that is larger than 4K words.
warning message.

This is a

VMR -- WARNING - PRIVILEGED TASK OVERMAPS I/O PAGE
INSTALL
A privileged task that is mapped into the Executive is often
mapped to the I/O page as well. However, many privileged tasks
do not require access to the I/O page and can use the extra 4K of
address space that would be allocated to the I/O page for the
task image. This message warns that a privileged task that may
require access to the I/O page does not have that access. If
your task does not require access to the I/O page, this message
can be ignored.
VMR -- WRITE CHECK NOT SUPPORTED FOR DEVICE
SET
You have attempted to enable write check on a device that does
not support it.
Write check is supported for all disks except
DL:, DX:, and DY:.

•

8-66

CHAPTER 9

SYSGEN PHASE III

This chapter lists and describes the questions in SYSGEN Phase III.

9.1

DETAILS OF SYSGEN PHASE III

Expanded comments for SYSGEN Phase III
Expanded comments
questions.

provide

descriptions

for

SYSGEN

Phase

III

ARE YOU RUNNING ON A MACHINE WITH AT LEAST 24K WORDS
If the current system has less than 24K-words of memory,
the
utility tasks cannot be built. SYSGEN displays the following
message and the exits.

,...,,.

SORRY, YOU CANNOT BUILD ANY UTILITIES AND/OR USER
DIAGNOSTICS WITH A MACHINE SMALLER THAN 24K WORDS!

MODE

If your system has at least 24K-words, SYSGEN continues.
ARE YOU BUILDING A MAPPED SYSTEM
SYSGEN uses the response to this question to determine
correct system UIC ([1,50] for unmapped, [1,54] for mapped).

the

DO YOU HAVE THE DUAL RK05 DISTRIBUTION KIT
If you are using the dual. RK05 kit, you must identify the RK05
units that contain the baseline system disk (RSXM26) and the
utility object files disk (UTLOBJ). SYSGEN asks the following
two questions.
IN WHICH DEVICE IS THE RSXM26 DISK MOUNTED (ddu:)
Enter the RK05 drive that contains the baseline system disk.
IN WHICH DEVICE IS THE UTILOBJ DISK mounted (ddu:)
Enter the RK05 drive that contains the utility object files.
SYSGEN then assigns the utility disk to the pseudo device
and the baseline system disk to the pseudo device LB:.

9-1

SY:

SYSGEN PHASE III
If you are not using the dual RKOS
question.

kit,

SYSGEN

asks

the

following

DO YOU HAVE THE RLOl DISTRIBUTION KIT
Enter No if you are using a big disk kit.
ARE YOU RUNNING ON A MACHINE WITH A LINE PRINTER
WAS ANSI MAGTAPE SUPPORT SELECTED IN SYSGEN PHASE I
WAS USER MODE DIAGNOSTIC SUPPORT SELECTED IN SYSGEN PHASE I
SYSGEN Phase III can build either utility tasks or user mode
diagnostic tasks or both.
The following questions determine
further action (the second question does not appear if you
respond No to this question).
DO YOU WANT TO (RE)BUILD ANY UTILITY TASKS
DO YOU WANT TO BUILD ANY USER MODE DIAGNOSTICS
***UTILITY TASKS***

IN ORDER FOR THE UTILITY TASKS TO USE ANSI FORMAT TAPE
THEY MUST BE BUILT WITH THE ANSI FCS ROUTINES. THESE
HOUTINES MAY CAUSE CERTAIN TASKS TO INCREASE BEYOND THE
NORMAL SK SIZE.
IF YOU WANT TO BUILD THE UTILITY TASKS WITH
ANSI MAGTAPE SUPPORT, YOU HAVE TO EDIT THE TASK
BUILD COMMAND FILES FOR THESE TASKS.
The task-build command file for a particular utility task
has to be edited only if the task size turns out to be above
SK words. This means that SYSGEN3 may have to be run a
second time.

MOST OF THE TASKS TO BE BUILT HAVE TASK BUILD
COMMAND FILES WHICH SPECIFY PARTITION GEN OR
PAR14K. GEN IS ASSUMED TO BE 40000(S) BYTES LONG
AND IS ASSUMED TO BE BASED AT 40000(S).
PAR14K IS A PARTITION WHICH IS 70000(S) BYTES LONG
. ; AND IS ASSUMED TO BE BASED AT 40000(S).
For a mapped system, no physical base addresses are required
for partitions, and the corresponding two lines above are
suppressed.

9-2

SYSGEN PHASE I I I

TASK FTB IS A FAST TASK BUILDER WITH LIMITED FUNCTIONALITY.
IT DOES NOT SUPPORT OVERLAYS OR GLOBAL CROSS-REFERENCE
BUT IT IS THREE TIMES FASTER THAN BIGTKB.
IT REQUIRES
A 20K PARTITION TO RUN IN AND IS NOT DISTRIBUTED IN TASK
IMAGE FORM. YOU MUST BUILD IT IF YOU INTEND TO USE IT.
THE TASK DSC IS THE DISK SAVE AND COMPRESS UTILITY.
IT IS
DISTRIBUTED AS A STANDALONE SYSTEM ON ALL DISTRIBUTION SYSTEMS
AS DSCSYS.SYS.
IT MAY ALSO BE BUILT AS A TASK, BUT IS NOT
DISTRIBUTED IN THAT FORM.
IT REQUIRES A 14K PARTITION TO RUN IN.
ALL OF THE TASK BUILD COMMAND FILES BUILD CHECKPOINTABLE
TASKS FOR USE WITH SYSTEMS WITH DYNAMIC ALLOCATION OF
CHECKPOINT SPACE.
IF YOUR SYSTEM DOES NOT SUPPORT
THIS OPTION, INSTALL WILL DEFAULT THEM TO NON-CHECKPOINTABLE.
IF YOU WISH YOU MAY BUILD TASKS WHICH ARE CHECKPOINTABLE
AND WHICH ALLOCATE SPACE IN THEIR TASK IMAGE BY CHANGING
THE /CP SWITCH TO THE /AL SWITCH IN THE BUILD COMMAND FILE.
NOTE: TASKS WHICH ALLOCATE CHECKPOINT SPACE IN THEIR
;
TASK IMAGE REQUIRE MORE DISK SPACE THAN TASKS THAT DON'T.
SET /UIC=[l,2x]
INS $EDI
SYSGEN then asks the following question:
Do you want to E edit and build, B -

build task tskname

where tskname is replaced by the name of the utility
(for example,
MAC).
Enter E if you must edit the build command file, B to simply
build the task, and carriage return to not build the
task.
SYSGEN
repE!ats the above question for the following utility tasks (each task
listed replaces tskname):
MAC
BIGMAC
TKB
BIGTKB
PIP
FLX
VFY
DMP
EDI
SLP
LBR
PSE
SYE
CRF
ZAP
BAD
VMR
FTB
CMP
PAT
DSC
CDA
EDT
FMT
IOX
If you enter E, SYSGEN invokes EDI and specifies
build command file (tsknameBLD.CMD) to be edited.
SYSGEN builds the task.

9-3

the corresponding
When you exit EDI,

SYSGEN PHASE III
SYSGEN then installs PIP and BIGTKB.
DO YOU WANT TO PRINT THE MAPS FOR THE UTILITY TASKS
The maps for the utility tasks
respond No.

are

little

use;

normally,

If you want the maps and specified a line printer, the maps will
be printed on the line printer. If you want the maps but did not
specify a line printer, they print on your terminal.
The next display depends on the distribution kit you are using.
The
RLOl and the dual RKOS kits require some preparation prior to building
the utility tasks. Read the pertinent section.
No preparations are necessary for big disk kits.
**RLOl KITS**
DEPENDING ON THE SECONDARY STORAGE MEDIUM AND THE NUMBER
OF TASKS TO BE COPIED, YOU MAY HAVE TO MOUNT A BLANK MEDIUM
IN THE DRIVE AFTER COPYING A TASK. THE RECOMMENDED NUMBER OF FILES
PER MEDIUM IS:
RKOS,RLOl AND MAGTAPE (TS03,RU10,TU16,TU45) - ALL TASKS WILL FIT
FLOPPY DISK AND DECTAPE - 4 TASKS PER DISK OR TAPE
CASSETTE - 1 TASK PER CASSETTE
IF YOUR SECONDARY STORAGE IS OTHER THAN RKOS, RLOl OR MAGTAPE,
AFTER COPYING A TASK, YOU WILL BE ASKED IF YOU WISH TO MOUNT
A NEW MEDIUM. IF SO THE INDIRECT FILE PROCESSOR WILL
PAUSE TO ALLOW TIME TO MOUNT IT.
THE FOLLOWING
DK
DL
DX
CT
OT
MT
MM
DY

ARE LEGAL SECONDARY STORAGE DEVICES:
(RKOS DISK, FOR RKOS DISTRIBUTION KITS ONLY)
(RLOl DISK, FOR RLOl DISTRIBUTION KITS ONLY)
(RXOl FLOPPY DISK)
(TU60 CASSETTE TAPE)
(TU56 DECTAPE)
(TS03, TElO, OR TUlO MAGTAPE)
(TU16, TE16, OR TU45 MAGTAPE)
(RX211 FLOPPY DISK)

* ENTER DEVICE FOR SECONDARY STORAGE [DOU]
The next query displayed
storage device.
*DK:

or DL:

[S] :

dependent

your

secondary

as Secondary Storage Device*

The following assumes DK:
storage device.

was

entered

the

until

the

device

secondary

PUT YOUR TARGET SYSTEM DISK IN DK:
* IS DK:

READY?

[Y/N]:

This query
response).

repeated

9-4

ready

SYSGEN PHASE III

* ENTER VOLUME LABEL OF DK:

[S]:

The device is then mounted using this volume label.
MOU DK:

label
*DX:
If DX:

LOI~

as Secondary Storage Device*

is not loaded, the MCR LOA command is issued.

DX:
*CT:,DT:,MT:, or MM:, as Secondary Storage*

The following assumes DT:
storage device.

was

entered

the

seconaary

If the secondary storage device is not loaded, the
command is issued.

MCR

LOA

LOJm DT:

**DUAL RK05 Kits**
* DO YOU HAVE AN EMPTY RK05 REMOVABLE DRIVE AVAILABLE?

[Y/N] :

If not, instructions are given for copying the task
files from secondary storage to the system disk.
If an empty drive is available, you are
the unit number.
* WHAT IS THE UNIT NUMBER OF THE EMPTY DRIVE?
The following assumes that DK2:

asked

image

identify

[O R:0-3]:

is the empty drive.

PLACE THE SYSTEM DISK IN DK2: AND START IT UP (WRITE
ENABLED). WE WILL COPY THE TASKS DIRECTLY TO THE SYSTEM DISK.
* IS THE SYSTEM DISK READY? [Y/N] :
This question is repeated until the disk
response). When ready, the disk is mounted.
MOU DK2:SYSTEM
*

WAS THE SYSTEM DISK MOUNTED SUCCESSFULLY? [Y/N] :
If not, the MOU command is issued again.
NOW WE BUILD THE REQUESTED UTILITY TASKS

ASN LP:=MP:
ASN TT:=MP:
ASN NL:=MP:
SE1~ /UIC=[l,20]
The selected utility tasks are now built.

9-5

ready

SYSGEN PHASE III
If using the RLOl or the dual RKOS kit, the build files are
copied to your secondary storage device and the old versions
are deleted. Depending on your secondary storage device,
either PIP or FLX is used to accomplish this (PIP for DL:,
DK:, or DX: as secondary storage and FLX for CT:, DT:, MM:,
MT:
as secondary storage).
The appropriate command is
issued following the task builder directive. The following
is an example of the display for a dual RKOS SYSGEN using an
RKOS (DK:) for secondary storage.
TKB @[l,2x] MACBLD
PIP DK: [l,Sx]/NV=[l,Sx]MAC.TSK
*WAS MAC COPIED SUCCESSFULLY?
PIP [l,Sx]MAC.TSK;O/DE

[Y/N]:

For brevity, the PIP and/or FLX commands, which appear only
if you are using an RLOl kit or the dual RKOS kit, are
omitted here.
Note that all commands are suppressed for a specific task if
that task was not selected to be rebuilt. The following
displays all of the tasks.
Similar commands are issued to build each of the selected
utility tasks.
In some cases, the old versions are purged
(PIP ••• /PU), leaving the most recent version,
instead of
being deleted
(PIP ••• /DE). The reason for this is to keep
tasks that may be required at later stages during SYSGEN.
TKB @[l,2x]MACBLD
TKB @[l,2x]BIGMACBLD
TKB @[l,2x]TKBBLD
TKB @[l,2x]BIGTKBBLD
TKB @[l,2x]PIPBLD
TKB @[l,2x]FLXBLD
TKB @[l,2x]VFYBLD
TKB @[l,2x]DMPBLD
TKB @[l,2x]EDIBLD
TKB @[l,2x]SLPBLD
TKB @[l,2x]LBRBLD
TKB @[l,2x]PSEBLD
TKB @[l,2s]SYEBLD
TKB @[l,2x]CRFBLD
TKB @[l,2x]ZAPBLD
TKB @[l,2x]BADBLD
TKB @[l,2x]VMRBLD
TKB @[l,2x]PATBLD
TKB @[l,2x]CDABLD
TKB @[l,2x]CMPBLD
TKB @[l,2x]FTBBLD
TKB @[l,2x]DSCBLD
TKB @[l,2x]SRDBLD
TKB @[l,2x]EDTBLD
TKB @[l,2x]RMSBCKBLD
TKB @[l,2x]RMSCNVBLD
TKB @[l,2x]RMSDEFBLD
TKB @[l,2x]RMSDFNBLD
TKB @[l,2x]RMSDSPBLD
TKB @[l,2x]RMSRTIBLD
TKB @[l,2x]VTECBLD
The task-builds are complete.

9-6

SYSGEN PHASE III
If user mode diagnostics were to be built, control passes to
the indirect command file BLDUMD.CMD (see Section 9.2}. The
task image files that have been built (utilities and/or user
mode diagnostics} will now be transferred to secondary
storage.
WE WILL PAUSE NOW TO ALLOW YOU TO COPY
- ANY FILES THAT WERE NOT SUCCESSFULLY TRANSFERRED
- THE DIAGNOSTIC TASKS
WHEN THE DIAGNOSTIC TASKS HAVE BEEN COPIED, YOU
M.~Y DELETE THEM FROM THIS DISK.
WHEN DONE, RESUME AT. AS SHOWN BELOW.
If only user mode diagnostics were selected to be built and
no utility task, an example of how to do the transfers is
displayed like the one below.
(PUT A BLANK MEDIUM IN MTO:}
>REM PIP
>INS [l,54]FLX;-l
>FLX MTO:/ZE
>FLX MTO:/DO=RK05.TSK/RS,TS03eTSK,TERM.TSK
>RES ••• AT e
AT.

PAUSING.

TO CONTINUE TYPE "RES ••• AT."

At this time, you may manually copy any files that were not
successfully transferred by the previous commands, and/or
the user mode diagnostics if they were selected to be built.
OMO DXO:
UNL DXO:
The secondary storage is dismounted and the driver unloaded.
If you have a dual-RKOS system, the task image files are now
resident
on
the target system disk.
Otherwise, the
following section of text is displayed to guide you in
transferring the task image files to the target system disk.
TO COPY THE TASK IMAGE FILES FROM THE SECONDARY
STORAGE MEDIUM TO THE SYSTEM DISK, PROCEED AS FOLLOWS
AFTER SYSGEN3 HAS TERMINATED:
If your secondary storage is DX, the following example
displayed (u is replaced by the actual unit number}:
(BOOT THE SYSTEM DISK}
>SET /UIC=[l,Sx]
>INS PIP
>LOA DX:
>MOU DXu:TASKX
>PIP =DXu:*. *
>OMO DXu:

REPEAT FROM HERE •••
REPLACE "TASKX" BY
ACTUAL VOLUME LABEL
••• TO HERE FOR ALL VOLUMES
USED FOR TRANSFER

>UNL DX:
>REM PIP
9-7

SYSGEN PHASE III
If your secondary storage is MT, MM, CT or DT, the following
example is displayed
(dd is replaced by the actual device
mnemonic, and u is replaced by the actual unit number):
(BOOT THE SYSTEM DISK)
>SET /UIC=[l,Sx]
>INS FLX
>LOA dd:
REPEAT FROM HERE •••
>FLX =ddu:*.*
••• TO HERE FOR ALL VOLUMES
USED FOR TRANSFER

•

>UNL dd:
>REM FLX
>INS PIP;-1
>@MT SK CO

MAKE TASK FILES CONTIGUOUS
A SERIES OF PIP COMMANDS FOLLOW

>@ <EOF>
>PIP MTSKCO.CMD;O/DE
>REM PIP
;

REM FLX
REM INI
REM UFD
REM PIP
***USER MODE DIAGNOSTICS***
Due to space limitations and the physical locations of files
on the RKOS distribution kits, the user mode diagnostics are
built in slightly differing ways.
Read
the
section
pertinent to your distribution kit.
SET /UIC=[l,20]
**RLOl Kits**
NOW WE BUILD AND COPY THE TASK TO THE SECONDARY
STORAGE MEDIUM.
DEPENDING ON THE SECONDARY STORAGE MEDIUM AND THE NUMBER
OF TASKS TO BE COPIED, YOU MAY HAVE TO MOUNT A BLANK MEDIUM
IN THE DRIVE AFTER COPYING A TASK. THE RECOMMENDED NUMBER OF FILES
PER MEDIUM IS:
RKOS,RLOl AND MAGTAPE (TS03,TU10,TU16,TU45) - ALL TASKS WILL FIT
FLOPPY DISK AND DECTAPE - 4 TASKS PER DISK OR TAPE
CASSETTE - 1 TASK PER CASSETTE
IF YOUR SECONDARY STORAGE IS OTHER THAN RKOS, RLOl OR MAGTAPE,
AFTER COPYING A TASK, YOU WILL BE ASKED IF YOU WISH TO MOUNT
A NEW MEDIUM. IF SO THE INDIRECT FILE PROCESSOR WILL
PAUSE TO ALLOW TIME TO MOUNT IT.
'l'HE FOLLOWING ARE LEGAL SECONDARY STORAGE DEVICES:
DK
(RKOS DISK, FOR RKOS DISTRIBUTION KITS ONLY)
DL
(RLOl DISK, FOR RLOl DISTRIBUTION KITS ONLY)
DX
.(RXOl FLOPPY DISK)
CT
(TU60 CASSETTE TAPE)
DT
(TU56 DECTAPE)
MT
(TS03, TElO, OR TUlO MAGTAPE)
MM
(TU16, TE16, OR TU45 MAG TAPE)

9-8

SYSGEN PHASE III
* ENTER DEVICE FOR SECONDARY STORAGE [DOU]
The next query displayed
storage device.
*DK:

or DL:

[S] :

dependent

your

secondary

·as Secondary Storage Device*

The following assumes DK:
storage device.

was

entered

the

secondary

until

the

device

ready

PUT YOUR TARGET SYSTEM DISK IN DK:

* IS DK:

READY?

[Y/N]:

This query
response).

repeated

* ENTER VOLUME LABEL OF DK:

[S]:

The device is then mounted using this volume label.
MOU DK:volume label
Control then passes to the indirect command file
(see that Section).
*DX:
If DX:

BLDUMD.CMD

as Secondary Storage Device*

is not loaded, the MCR LOA command is issued.

LOA DX:
TO COPY THE TASK IMAGE FILES FROM THE SECONDARY
s~rORAGE MEDIUM TO THE SYSTEM DISK, PROCEED AS FOLLOWS
AFTER SYSGEN3 HAS TERMINATED:
(BOOT THE SYSTEM DISK)
>SET /UIC = [l,Sx]
>INS $PIP
>LOA DX:
!REPEAT FROM HERE •••
>MOU DX:TASKX
REPLACE "TASKX" BY
ACTUAL VOLUME LABEL
>PIP = DX:*.*
>DMO DX:
! ••• TO HERE FOR ALL VOLUMES
!USED FOR TRANSFER
>UNL DX:
Control then passes to the indirect command file
(see Section 9.2).
*CT:, DT:, MT:, or MM:
The following assumes DT:
storage device.

as Secondary Storage Device*
was

entered

the

If the secondary storage device is not loaded, the
command is issued.

9-9

BLDUMD.CMD

secondary
MCR

LOA

SYSGEN PHASE III
LOA DT:
TO COPY THE TASK IMAGE FILES FROM THE SECONDARY
STORAGE MEDIUM TO THE SYSTEM DISK, PROCEED AS FOLLOWS
AFTER SYSGEN3 HAS TERMINATED:
(BOOT THE SYSTEM DISK)
>SET /UIC
[l,Sx]
>INS $FLX
>LOA DT:
REPEAT FROM HERE •••
>FLX = DT:*.*
••• TO HERE FOR ALL VOLUMES
USED FOR TRANSFER
>UNL DT:
>REM FLX
BLDUMD.CMD

Control then passes to the indirect command file
(see Section xxx).
**Dual RKOS Kits**
* DO YOU HAVE AN EMPTY RKOS REMOVABLE DRIVE AVAILABLE?

[Y/N]:

asked

image

identify

[O R:0-3]:

is the empty drive.

PLACE THE SYSTEM DISK IN DK2: AND START IT UP (WRITE
ENABLED). WE WILL COPY THE TASKS DIRECTLY TO THE SYSTEM DISK.
*IS THE SYSTEM DISK READY? [Y/N]:
· This question is repeated until the disk
response). When ready, the disk is mounted.

ready

MOU DK2:SYSTEM
* WAS THE SYSTEM DISK MOUNTED SUCCESSFULLY? [Y/N] :
If not, the MOUnt command is issued again.
If mounted successfully, control passes to
command file BLDUMD.CMD (see Section 9.2).

the

indirect

**All Kits Except RLOl Kit and RKOS Kits**
Control is passed directly to
BLDUMD.CMD (see Section 9.2).
End of SYSGEN Phase III.

9-10

the

indirect

command

file

SYSGEN PHASE III
9.2

BLDUMD.CMD FILE DETAILS

BLDUMD is the indirect command file to task-build all or selected User
Mode Diagnostics.
BLDUMD is called from SYSGEN Phase III if the
corresponding question is answered appropriately.
It may also be
called manually at any time with the following command:
>@[200,200]BLDUMD
The following is a detailed description of all the steps in BLDUMD.
BLDUMD <VERSION 03.1>
COPYRIGHT (C) 1976, 1977, 1979
DIGITAL EQUIPMENT CORP., MAYNARD, MASS.

01754

BUILD ALL OR SELECTED USER MODE DIAGNOSTICS.
;

* AFlE YOU HUNNING ON A MACHINE WITH AT LEAST 24K WORDS? [Y/N] :
If the answer is N, the
BLDUMD terminates.

following

text

displayed

and

SORRY, YOU CANNOT BUILD (OR RUN) THE USER MODE DIAGNOSTICS
ON A MACHINE WITH LESS THAN 24 K WORDSl
Otherwise, processing continues here.
As in the previous sections of
your distribution kit.

SYSGEN,

* DO YOU HAVE THE DUAL RKOS DISTRIBUTION KIT?

you

must

identify·

[Y/N] :

If you do, you are asked to identify the RKOS drives that
contain the UTLOBJ and RSXM26 disks. The UTLOBJ disk is
then assigned to SY:
and the RSXM26 disk is assigned to
LB:.

''-"'

* IN WHICH RKOS DRIVE IS THE UTLOBJ DISK MOUNTED? [O R:0-3]:
* IN WHICH RKOS DRIVE IS THE BAS LINE DISK MOUNTED? [O R: 0-3] :
The following assumes DKO:
for the RSXM26 disk.

disk

and

DK!:

If you replied negatively to the dual RKOS query,
query displayed is

the

for the

UTLOBJ

ASN DKO:=SY:
ASN DKl:=LB:

* IS THE CURRENT SYSTEM DISK AN RP02/03/04/05/05 OR RK06/07?
* DO YOU WANT EXPANDED COMMENTS FOR 'rHE UMD BUILD PROCEDURE?

[Y/N] :

Expanded comments provide a lot of descriptive text that the
experienced user might want to dispense with.

9-11

SYSGEN PHASE I I I

DIAGNOSTIC TASKS CAN BE BUILT FOR THE FOLLOWING DEVICES:
MNEMONIC
DB:
DB:
DB:
DF:
DK:
DM:
DM
DP:
DP:
DP:
DS:
DS:
DT:
MM:
MM:
MT:
MT:
TT:

DEVICE

RJP04/RWP04
RJ PO 5 /RWP 0 5
RJP06/RW~06

RFll/RSll
RKll/RKOS
RK611/RK06
RK611/RK07
RP11/RP02
RP11/RP03
RP11E/RPR02
RJS03/RWS03
RJS04/RWS04
TC11/T056
TJU16/TWU16
TJ Ul 6 /TWU 45
TMAll/TUlO
TMA11/TS03
TERMINAL

DIAGNOSTIC NAME
RP04
RPOS
RP06
RFll
RKOS
RK06
RK07
RP02
RP03
RPR02
RS03
RS04
TU56
TU16
TU45
TUlO
TS03
TERM

DRIVE
COMPATIBILITY COMP
* DO YOU WANT DIAGNOSTICS FOR A MAPPED SYSTEM? [Y/N] :
* IS THE TARGET SYSTEM AN 11/70 [Y/N]:
;
;

SET UIC=[l,2x]
If you are ~sing other than a dual RKOS distribution kit,
the task image files will be generated on the system disk,
and the next section is bypassed.
THE DIAGNOSTIC TASKS WILL BE STORED ON THE SYSTEM DISK BY DEFAULT.
IF YOUR SYSTEM DISK IS AN RKOS YOU MAY BE REQUIRED TO STORE THE
DIAGNOSTICS ON A SEPARATE DISK TO AVOID ALLOCATION PROBLEMS.
IF YOU HAVE THE DUAL RKOS RELEASE KIT, YOU SHOULD SPECIFY
THAT THE DIAGNOSTICS BE STORED ON ANOTHER DISK. IF YOU HAVE
A THIRD RKOS PUT THE PRIVOBJ DISK IN IT AND STORE THE DIAGNOSTICS
ON IT. OTHERWISE, STORE THEM ON LBO:.

* DO YOU WANT THE DIAGNOSTICS STORED ON ANOTHER DISK? [Y/N:]
If this question is answered with an N, the next section is
bypassed.
Otherwise, you are asked for the device mnemonic
and unit number of the disk where to store the diagnostics.

* ENTER THE OUTPUT DEVICE NAME AND UNIT NUMBER (E.G.

DKl)

[S]:

It is assumed in the following lines that you answered
question with DKl.

9-12

this

SYSGEN PHASE III

THE COMMAND BUILD FILE WILL NOW PAUSE WHILE YOU MOUNT DKl:
YOU MUST CREATE THE UFD'S [l,3x] AND [l,Sx] ON THE DISK
·; ('l'HE FORMER ONLY IF YOU WANT THE TASK BUILD MAPS) IF THEY
DO NOT ALREADY EXIST.
EXAMPLE:
>INIT DKl:DIAGNOSTICS
>MOUNT DKl:DIAGNOSTICS
>UIW DKl: [l,3x]
>Uli'D DKl: [l,Sx]
AT.

PAUSING. TO RESUME TYPE "RES ••• AT."
Whatever the system disk type is, processing continues here.

DIAGNOSTICS ARE GENERALLY RUN WITH THE FOLLOWING ATTRIBUTES:
PARTITION =
BASE ADDRESS
SIZE =

GEN
40000
40000

The last two lines appear only
diagnostics for an unmapped system.
;

IE~

you

are

building

YOUR SYSTEM IS DIFFERENT ANSWER YES TO THE FOLLOWING QUESTION.

* DO YOU WANT TO ALTER THE DEFAULT PARTITION ATTRIBUTES? [Y/N] :
~rhe

following three questions are bypassed if
this question with an N.

* ENTER THE PARTITION NAME (DEFAULT=GEN)

answered

are

building

[S]:

The following question is asked only
diagnostics for an unmapped system.

you

* ENTER THE PARTITION BASE ADDRESS (DEFAULT=40000)

[S]:

* ENTER THE PARTITION SIZE

you

(DEFAULT=40000)

[S]:

THE DIAGNOSTIC TASKS ARE NORMALLY BUILT TO TRANSFER DATA VIA
A 2000 OCTAL BYTE DATA BUFFER. YOU MAY SPECIFY A DIFFERENT
BUFFER SIZE BY ANSWERING THE NEXT QUESTION.
;

* ENTER THE BUFFER SIZE IN OCTAL BYTES (DEFAULT=2000)

[S]:

NORMALLY DIAGNOSTIC TASK BUILD MAPS ARE NOT REQUIRED.
IN THE UNLIKELY EVENT YOU NEED THEM, ANSWER "YES" TO THE
FOLLOWING QUESTION.
;

* DO YOU WANT TASK BUILD MAPS? [Y/N] :

* DO YOU WANT THE MAPS LISTED ON THE LINEPRINTER?

[Y/N] :

If you answered Y to the first question and N to the second
of the two questions above, the maps will be directed to UFD
[l,3x] on the output disk.

,..

9-13

SYSGEN PHASE III

NORMALLY YOU ENTER EACH DIAGNOSTIC NAME REQUIRED FOR YOUR SYSTEM.
AN ALTERNATE METHOD IS PROVIDED WHICH ALLOWS BUILDING ALL
.~VAILABLE DIAGNOSTICS. THIS METHOD REQUIRES ABOUT 500 BLOCKS OF
DISK SPACE ON THE OUTPUT DEVICE. THE DIAGNOSTICS THAT DO NOT APPLY
CAN BE DELETED AT A LATER TIME.
;

* DO YOU WANT TO BUILD ALL AVAILABLE DIAGNOSTICS? [Y/N] :
* HAVE ALL QUESTIONS BEEN ANSWERED TO YOUR SATISFACTION? [Y/N] :
If you answered these questions with N, processing will
restart at the beginning of BLDUMD. Otherwise, if you want
to build all diagnostics, the next section that asks for
diagnostic names is bypassed.
ENTER THE NAME OF THE DIAGNOSTIC TASKS TO BUILD, ONE AT
A TIME. WHEN DONE, ENTER A SINGLE CARRIAGE RETURN.
THE FOLLOWING IS A LIST OF VALID DIAGNOSTIC NAMES:
RP04,RPOS,RP06,RF11,RKOS,RK06,RP02,RP03,RPR02,RS03
RS04,TUS6,TU16,TU45,TU10,TS03,TERM
HERE IS A SAMPLE DIALOGUE TO BUILD THE RJP04/RWP04 DISK AND THE
TMA11/TS03 MAGTAPE DIAGNOSTICS ( <CR> = CARRIAGE RETURN) :
NAME [S] :RP04<CR>
NAME [S] :TS03<CR>
NAME [S] :<CR>
The next question requires as a response, the name of
next diagnostic to build, out of the list shown above.

the

* NAME [S] :
If an invalid name
following
message
repeated.

is entered (for example "XX"), the
is displayed, and the question is

;***** "XX" DIAGNOSTIC IS NOT AVAILABLE*****
The question"* NAME [S] :" is repeated.to allow you to enter
the names of all diagnostics to be built. When done, answer
with a single carriage return.
If you chose to build all the diagnostics, or when you have
entered the names of all the desired diagnostics, processing
continues here.
NOW WE TASK BUILD THE SELECTED DIAGNOSTICS

•

;
INS

$BIGTKB
TKB @UMDBLD
The command above builds the selected diagnostics, according
to specifications defined by the previous sections.
REM TKB
End of UMDBLD.

9-14

SYSGEN PHASE I I I
The following sample dialogue builds diagnostics for RK05,
TU16, and terminals to run on an unmapped system. The GEN
partition in that system starts at 50000.
The task image
files are directed to the target system disk which is put in
drive DKl:.
>@[200,200]BLDUMD

>;
>; BLDUMD <VERSION 03.1>

>; COPYRIGHT (C) 1976, 1977, 1979
>; DIGITAL EQUIPMENT CORP., MAYNARD, MASS. 01754

•

BUILD ALL OR SELECTED USER MODE DIAGNOSTICS •

>;
>* ARE YOU RUNNING ON A MACHINE WITH AT LEAST 24K WORDS? [Y/N] :Y
>* DO YOU HAVE THE DUAL RK05 DISTRIBUTION KIT? [Y/N] :
>* IS THE CURRENT SYSTEM DISK AN RP02/03/04/05/06 OR RK06? [Y/N]: Y
>* DO YOU WANT EXPANDED COMMENTS FOR THE UMD BUILD PROCEDURE? [Y/N] :
>* DO YOU WANT DIAGNOSTICS FOR A MAPPED SYSTEM? [Y/N] :
>SET' /UIC=[l,20]
>* DO YOU WANT THE DIAGNOSTICS STORED ON ANOTHER DISK? [Y/N] :Y
>* E:NTER THE OUTPUT DEVICE NAME AND UNIT NUMBER (E.G. DKl) [S]: DKl

>;
>; THE COMMAND BUILD FILE WILL NOW PAUSE WHILE YOU MOUNT DKl:
>; Y'OU MUST CREATE THE UFD'S [1,30] AND (1,50] ON THE DISK
>; (THE FORMER ONLY IF YOU WANT THE TASK BUILD MAPS) IF THEY
>; DO NOT ALREADY EXIST.

>;
AT. -- PAUSING. TO CONTINUE TYPE "RES ••• AT"
>MOU DKl:UNMOBJ
>RES ••• AT
AT. -- CONTINUING

>*
>*
>*
>*
>*
>*
>*
>*

DO YOU WANT TO ALTER THE DEFAULT PARTITION ATTRIBUTES? [Y/N] :Y
ENTER THE PARTITION NAME (DEFAULT=GEN) [S]:
ENTER THE PARTITION BASE ADDRESS (DEFAULT=40000) [S]: 50000
ENTER THE PARTITION SIZE (DEFAULT=40000) [S]:
ENTER THE BUFFER SIZE IN OCTAL BYTES (DEFAULT=2000) [S]:
DO YOU WANT TASK BUILD MAPS? [Y/N]:
DO YOU WANT TO BUILD ALL AVAILABLE DIAGNOSTICS? [Y/N] :
HAVE ALL QUESTIONS BEEN ANSWERED TO YOUR SATISFACTION? [Y/N] :Y

>;
>; JrnTER THE NAME OF THE DIAGNOSTIC TASKS TO BUILD, ONE AT
~HEN DONE, ENTER A SINGLE CARRIAGE RETURN.

>; A TIME.
>;
>*
>*
>*
>*

NAME
NAME
NAME
NAME

[SJ : RK05
(SJ : TU16
(S] : TERM
[S] :

>;
>; NOW WE TASK BUILD THE SELECTED DIAGNOSTICS

...

>;
>TKB @UMDBLD

>;
>@ <EOF>

9-15

CHAPTER 10

INSTALLATION VERIFICATION PROCEDURE

10.l.

INTRODUCTION

The RSX-llM Installation Verification Procedure checks out
the
software-hardware system that you created during the SYSGEN process.
The procedure does not replace the hardware diagnostics that DIGITAL
Field Service runs on individual devices nor does it substitute for
software testing during software development.
The procedure merely
verifies that your generated system has produced a working system with
the configuration that you requested during SYSGEN.
The Installation Verification Procedure consists of a
set
of
controlling CQmmand files that run a series of test modules that gives
the system a rigorous exercising. The procedure exercises two areas
of
the system:
hardware,
discussed in Section 10.2 and software,
discussed in Section 10.3.

10.:2

HARDWARE

As .a result of running this procedure,
you know what devices were
successfully generated into the system and you have verified the
functioning of all disk and tape units under operating system control.
The procedure operates the devices under varying system loads.

10.2.l

System I/O Exerciser

The system I/O exerciser verifies the functioning of all disk and tape
units on the system and identifies all devices to be tested. The
exerciser tests disks as Files-11 volumes (mounted automatically) that
are public or not allocated by another user. Also, the exerciser
tests DECtape,
cassettes,
and magtape by using AST driven QIO
requests.

•

After the test, the exerciser deletes all files that it has created on
these volumes.
However,
the exerciser does not modify the disk
structure or any existing disk data.
Be aware that the exerciser
overwrites tapes and destroys their contents.

10 •3

SOF'l WARE
1

The software verification modules of the procedure quickly access and
exercise those discrete system software components that can be
operated under command file control.
This operation tests the
completeness of the System Generation procedure.

10-1

INSTALLATION VERIFICATION PROCEDURE
10.3.1

CPU-bound Load Test

The ~PU-bound load test determines whether the system can handle a
heavy loading of parallel processing, compute-bound tasks. This test
determines whether the entire memory encompassed by the system
partition, GEN,
is available to the system.
This test uses the
checkpointing, swapping, and round-robin scheduling Executive options
when present.
Also,
this test uses the Send and Receive Executive
directives.
This test cannot be run in an unmapped system and
therefore is skipped in an unmapped system.

10.3.2

System Utilities Verification

This test invokes most of the standard RSX-llM system utilities and
verifies their presence and operation by using an indirect command
file routine.
The test invokes interactive editors and the ACNT
program to demonstrate that an executable task file exists.
You can
choose to execute some functions in these programs or exit from them
immediately.

OPERATING PROCEDURES

10.4

Your system must meet
certain
configuration
and
operational
requirements to run the entire Installation Verification Procedure.
These requirements follow.

10.4.1

Configuration Restrictions

•

The hardware verification section requires that the system
support ASTs.
The I/O exerciser and CPU-bound load test use
ASTs.

•

If the system is unmapped, the procedure does not execute
CPU-bound load test.

the

If your system does not support any of the following features,
the
CPU-bound load test cannot run. However, the procedure determines
whether your system supports the following features.
It does not run
the CPU-bound test if any are missing.
The required features for the CPU-bound load test are:
•

Send/Receive directives

•

Alter Priority directive

•

Get Partition Parameters directive

•

AST support

•

Dynamic checkpointing

10-2

INSTALLATION VERIFICATION PROCEDURE
10.4.2

~·

Operating Environment

•

Run the Installation Verification Procedure following the
completion of SYSGEN.
The devices to be tested cannot be
allocated to other users.

•

You should run the Installation Verification Procedure on a
stand-alone basis if possible.
The procedure puts a heavy
load on the system to the detriment of the throughput of other
system users.
The procedure should have an unlimited access
to system features and devices to properly do its assigned
task.

•

You must run the procedure from a privileged terminal.

•

The procedure runs from UIC [2,300]. If you wish,
you can
delete the entire contents of [2,300] after a successful run.

•

You must place scratch tapes on all magnetic tape drives,
including cassettes and DECtapes.
Files-11 initialized disks
must be placed on all disk drives.

•

The procedure can be repeated without the
rebuilding DEFINE.TSK if DEFINE is installed.

•

The procedure needs only one terminal to run.
If a second,
CRT terminal exists,
you can use it to run RMDEMO.
If one
terminal is a printing terminal, use it to run the procedure
to allow you to check the printout for errors.
If you must
run the procedure from a CRT terminal, you must watch the
terminal very closely to avoid missing important information
(for example, error messages) that you may need later.

10.4.3

necessity

Operating Instructions

Boot the system.

Allocate a large checkpoint space for the system.

Place scratch media on all DECtape,
cassette and magtape
drives.
Place initialized disk packs on all empty drives.
The packs need not be scratch packs because data is not lost
on them.

Execute the command file, SAM.

For example:

>@[2,300]SAM

From this point, the operating instructions are part of the
console dialogue,
which follows in Section 10.4.4, "Sample
Console Dialogue". When the procedure runs to completion,
examine the dialogue for error messages. These fall into
three categories:
system

A function did not
execute
because
this
intentionally does not contain the function.

A function did not execute because of a SYSGEN error.

A hardware problem occurred.

10-3

INSTALLATION VERIFICATION PROCEDURE
10.4.4

Sample Console Dialogue

The following console dialogue is from an actual session of running
the RSX-llM Installation Verification Procedure. It is included here
to guide you and give you an indication of what to expect when you run
your procedure.
Before you begin, mount the Executive source disk
(EXCSRC} and assign it to SY:.
>SET /UIC=[2,300]
>MOU DLO:/OVR
>PIP =DLO:SAM.CMD
>@SAM
*************************************************

;

RSX-llM INSTALLATION VERIFICATION PROCEDURE *

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

>SET /UIC=[2,300]
>INS LB: $PIP
>RUN ERRLOG
ERL -- ERROR LOG INITIALIZED

>;
>* DO YOU WISH TO RUN RMDEMO? [Y/N]: N
ERL -- ERROR LOG INITIALIZED

>* ENTER UNIT NUMBER OF TERMINAL [S] : 0

>;
>;
>;
>;
>;

**** NOTE ****

>;
>; TEST MEDIA MUST BE LOADED ON ALL TAPE AND DISK DRIVES.

USE SCRATCH

>; TAPES AND FILES-11 FORMAT DISKS.
>;
>; ALL MAGTAPES BEING TESTED ARE OVER-WRITTEN.

THE DISKS ARE
>; TESTED WITH FILE-STRUCTURED I/O WITH NO NEGATIVE EFFECT ON DATA
>; OR STRUCTURE.

>;
>; BEFORE PERFORMING THE FILE-STRUCTURED I/O TEST, ALL UNMOUNTED
>; DISKS ARE MOUNTED AUTOMATICALLY.
>* DO YOU NEED TO INITIALIZE ANY DISKS? [Y/N]: N

>;
>TIM
12:57:52 06-FEB-79
>; NEEDED UTILITIES WILL BE INSTALLED NOW.
>; **********
>; ************************************************************
>PIP TAILOR.DAT=DEVM.SAM/AP
>MAC DEFINE=[ll,10]RSXMC/PA:l,[2,300]DEFINE
>TKB DEFINE/PR/CP=DEFINE ,LB: [ 1,54] RSXllM.STB, [ 1,1] EXELIB/LB
>INS DEFINE/TASK=DEFINE
>PIP *.*/PU
>RUN DEFINE

>
>;
>;

* CPU-BOUND LOAD TEST *

>;
>INS DUMMY/TASK=DUMOO/PRI=40.
>INS LOGGER/TASK=LOGOO
>INS QTRUN /TASK=QTROO

10-4

'·~

.. -

INSTALLATION VERIFICATION PROCEDURE
>RUN DUMOO

>;
>;
>;
>;
>;
>;
>;

FOR THE NEXT FEW MINUTES A NUMBER. OF COMPUTE BOUND TASKS WILL BE
EXERCISING THE MEMORY, T.HE MULTI-TASKING CAPABILITIES OF THE
SYSTEM AND, IF INCLUDED IN THIS SYSTEM, THE ROUND-ROBIN SCHEDULER,
~~HE SHUFFLER, AND CHECKPOINTING.
THE ACTION OF THESE LAST THREE
lrnATURES CAN BE SEEN ON THE RMDEMO SCREEN. IF THE SYSTEM IS
PERFORMING PROPERLY, ALL OF THE "GEN" IS USED AND THE "QT"
TASKS ARE SHARING THE SYSTEM RESOURCES IN A MANNER CONSISTENT
>; WI TH TH:E: FEATURES AVA! LABLE. NOTE THAT CHECKPOINTING IS DISABLED
>; FOR THE SECOND HALF OF THE TEST.

*** THIS TEST RUNS FOR A MAXIMUM OY 6 MINUTES ***

>RUN QTROO

>TIM
12:59:51 06-FEB-79
>INS NUL3/TASK=QTOOOO
>INS NUL3/TASK=QT0100
>INS NUL3/TASK=QT0200
>INS NUL3/TASK=QT0300
>INS NUL3/TASK-QT0400
>INS NUL3/TASK=QT0500
>;
>>>>>> THE LOAD TEST IS RUNNING

<<<<<<

>TIM
13:06:15 06-FEB-79
>REM QTOOOO
>RE!M QTOlOO
>REM QT0200
>REM QT0300
>REM QT0400
>REM QT0500

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

* TEST COMPLETED *

* SYSTEM I/O EXERCISER *
THE FOLLOWING DEVICES HAVE BEEN GENERATED INTO YOUR SYSTEM. THOSE
LISTED AS "OFFLINE" ARE NOT PHYSICALLY PRESENT AND ARE NOT
TESTED. INDIVIDUAL MAG TAPE, DEC TAPE AND RK05 UNITS
CAN BE SHOWN ERRONEOUSLY AS ONLINE WHEN THE CONTROLLER IS ONLINE.
THEY ARE TESTED AND THE TEST FAILS AFTER SEVERAL MINUTES
OF ERROR MESSAGES.

•

>DEV
LPO:
DBO:
DBl:
DB2:
DB3:
DB4:
DDO:
DDl:
DKO:
DKl:
DLO:
DI..l:
OMO:
DMl:
DPO:

LOADED
OFFLINE LOADED TYPE=RP04
LOADED TYPE=RP04
OFFLINE LOADED TYPE=RP04
MOUNTED LOADED LABEL=RSX26 TYPE=RP04
OFFLINE LOADED TYPE=RP04
OFFLINE UNLOADED
OFFLINE UNLOADED
LOADED
LOADED
OFFLINE UNLOADED TYPE=RLOl
OFFLINE UNLOADED TYPE=RLOl
OFFLINE LOADED TYPE=RK06
LOADED TYPE=RK06
UNLOADED TYPE=RP02

10-5

INSTALLATION VERIFICATION PROCEDURE
DPl:
DRO:
DRl:
DSO:
DSl:
OTO:
DTl:
DXO:
DXl:
MMO:
MM!:
MTO:
MTl:
MSO:
TTO:
TTl:
TT2:
TT3:
TT4:
TTS:
TT6:
TT7:
TTl 0:
TTll:
TT12:
TT13:
TTl 4:
TTl 5:
TT16:
TT17:
TT20:
TT21:
TT22:
TT23:
TT24:
TT25:
TT26:
TT27:
TT30:
TT31:
TT32:
TT33:
TT34:
TT35:
TT36:
TT37:
NLO:

UNLOADED TYPE=RP02
OFFLINE UNLOADED TYPE=RM03
UNLOADED TYPE=RM03
OFFLINE UNLOADED TYPE=RS04
OFFLINE UNLOADED TYPE=RS03
OFFLINE LOADED
OFFLINE LOADED
OFFL INE ·LOADED
OFFLINE LOADED
UNLOADED
UNLOADED
OFFLINE LOADED
OFFLINE LOADED
OFFLINE UNLOADED
[2,300] - LOGGED ON LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED
LOADED

TIO:

COO:
CLO:
LBO:
SYO:
WKO:

TTO:

TTO:
DB3:
083:
DBO:

>;
>;
>; IF ANY DRIVERS ARE UNLOADED, THEY ARE LOADED NOW.

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

>LOA DP:
>LOA MM:/PAR=GEN
LOA -- INTERRUPT VECTOR ALREADY IN USE

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

>INS [2,300]IOX/TASK= ••• SIO
>MOU DBl:/OVR/VI

10-6

INSTALLATION VERIFICATION PROCEDURE

MOUNT-**VOLUME INFORMATION**
DEVICE = DBl:
CLASS
FILE 11
LABE:L
= RSXllM
UIC
= [1,1]
Accgss
[RWED,RWED,RWED,RWED]
CHAHAC = []
>MOU DKl:/OVR/VI
MOUNT-**VOLUME INFORMATION**
DEVICE = DKl:
CLASS
= FILE 11
LABEL
SYSTEM
UIC
[1,1]
ACCJ~SS
[RWED ,RWED ,RWED ,RWED]
CHAH.AC
[]
>MOU DKO:/OVR/VI
MOUNT-* *VOLUME INFORMATION**
DEVICE
DKO:
CLASS
= FILE 11
LABEL
UTIL
UIC
[2,300]
ACCESS
[RWED,RWED,RWED,RWED]
CHAlRAC
[]
>MOU DMl:/OVR/VI
MOUNT-**VOLUME INFORMATION**
DEVICE
DMl:
CLASS
FILE 11
LABEL
RSXM26
UIC
[1,1]
CLASS
[RWED ,RWED ,RWED ,RWED]
CHA:RAC
[]

>;
>;
>;

THE SYSTEM I/O EXERCISER WILL RUN FOR 3 MINUTES

>;
>TIM
13:06:18 06-FEB-79
>SIO @IOXCNF
SIO
DRIVER NOT LOADED
SIO -- FAILED TO ATTACH UNIT
SIO -- SUMMARY OF EXERCISER ACTIVITY AT 6-FEB-79 13:09:39
TIME
RUN: 3 MIN.
ELAPSED: 3 MIN.
REMAINING: 0 MIN.
DBl:
7,053. REQUESTS TOTALING 7,053. BLOCKS WITH NO ERRORS
DB3:
7,052. REQUESTS TOTALING 7,052. BLOCKS WITH NO ERRORS
DKO:
2,348. REQUESTS TOTALING 2,348. BLOCKS WITH NO ERRORS
DKl:
2,341. REQUESTS TOTALING 2,341. BLOCKS WITH NO ERRORS
DMl:
6,547. REQUESTS TOTALING 6,547. BLOCKS WITH NO ERRORS
IDLE-LOOP COUNT: 1,988. ITERATIONS
A C C U MU L A T E D

•

T 0 T A L S

TIME
RUN: 3 MIN.
ELAPSED: 3 MIN.
DBl:
7,053. REQUESTS TOTALING 7,053.
DB3:
7,052. REQUESTS TOTALING 7,052.
DKO:
2,348. REQUESTS TOTALING 2,348.
DKl:
2,341. REQUESTS TOTALING 2,341.
DMl:
6,547. REQUESTS TOTALING 6,547.
IDLE-LOOP COUNT: 1,988. ITERATIONS
>REM SIO
>TIM
13:10:05 06-FEB-79

10-7

REMAINING: 0 MIN •
BLOCKS WITH NO ERRORS
BLOCKS WITH NO ERRORS
BLOCKS WITH NO ERRORS
BLOCKS WITH NO ERRORS
BLOCKS WITH NO ERRORS

INSTALLATION VERIFICATION PROCEDURE

>;
>;

* TEST COMPLETED *

* UTILITIES VERIFICATION SECTION *

>;
>;
>;
>;
>;

>RUN DEFINE

>
>;
>;

* CMP VERIFICATION *

>TIM
13:10:17 06-FEB-79
>PIP COMPAR.CMD=SIOE.CMD
>1 INVOKE CMP TO COMPARE IDENTICAL FILES
>CMP TI:= COMPAR.CMD,SIOE.CMD
1)
COMPAR.CMD;l
2)
SIOE.CMD; l
NO DIFFERENCES FOUND
TI:=COMPAR.CMD,SIOE.CMD
>1 NO DIFFERENCES SHOULD HAVE BREN FOUND
>1
>1 INVOKE CMP TO COMPARE DIFFERING FILES
>CMP TI:FILE1.,FILE2.

*************************************************
1)
6
7

FILE.;l
.; IF CMP IS FUNCTIONING, THIS LINE FROM FILEl. IS DIFFERENT
.; THE REST OF THE LINES ARE IDENTICAL

***************
2)
6
7

FILE2.;l
.; THIS LINE IS THE FILE2. LINE WHICH DIFFERS FROM THE ABOVE.
.; THE REST OF THE LINES ARE IDENTICAL.

l DIFFERENCES FOUND
TI:=FILE1.,FILE2.
>1 ONE DIFFERENCE SHOULD HAVE BEEN FOUND
>PIP COMPAR.CMD;*/DE

>;
>TIM
13:10:46 06-FEB-79

>;
>;

* CMP VERIFICATION COMPLETE *

>;
>;

*ALL, BAD, INI, MOU, UFO, VFY, OMO, AND DEA VERIFICATION*

>;
>TIM
13:10:52 06-FEB-79

>;
>;
>;
>;
>;
>;
>;

THIS ROUTINE CHECKS THE DISK-ACCESSING MCR COMMANDS ALL, BAD, INI,
MOU, UFO, VFY, OMO AND DEA.
ALL AND DEA ARE TESTED ONLY FOR A MULTI-USER SYSTEM.
THIS ROUTINE REQUIRES EITHER ONE DISK DRIVE {OTHER THAN SY:) OR
DECTAPE OR ANSI SUPPORT FOR MAGTAPE. IT WILL NOT USE A PUBLIC
DISK. IF ONLY MAGTAPE IS AVAILABLE, A SUB-SET OF THE TEST IS RUN.

>;
>;
>INS $BAD

>;
>;

>DMO DKO:

10-8

•

INSTALLATION VERIFICATION PROCEDURE
>DE/l• DKO:
**"r DKO: --- DISMOUNT COMPLETE

>;
>;
>;
>;
>;
>; *** BE SURE THERE IS A SCRATCH MEDIUM ON DKO: ***

>;
>* DO YOU WI SH TO CONTINUE WITH THIS MODULE ? [Y/N] : Y

>;
>INS $VFY/TASK= ••• VFY
>ALL DKO:
>BAD DKO:
BAD -- DKO: TOTAL BAD BLOCKS= O.
>IN! DKO:UTIL/BAD=[AUTO]/UIC=[2,300]
>MOU DKO:UTIL/VI
MOUNT ** VOLUME INFORMATION **
DEVICE
= DKO:
CLASS
FILES 11
LABEL
= UTIL
UIC
[2,300]
ACCESS
[RWED,RWED,RWED,RWED]
CHA.R
[]
>UF'D DKO: [2,300]
>PIP DKO:=DISK.CMD
>VF'Y DKO: /FR
DKO: HAS 4634. BLOCKS FREE, 166. BLOCKS USED OUT OF 4800.
>DMO DKO:

>;
**"'r DKO:

-- DISMOUNT COMPLETE

>;
>DgA DKO:

>;
TIM
l3gl2:42 06-FEB-79
>REM VFY
>RgM BAD

>;
>;

*ALL, BAD, !NI, MOU, UFD, VFY, DMO, AND DEA*
* VERIFICATION COMPLETE *

* FLX VERIFICATION *

>INS [l,54]FLX/TASK= ••• FLX

>;
>;

THE FOLLOWING QUESTION WILL BE ANSWERED: DOES FILEX FUNCTION?

>;
>; THE TAPE ON DRIVE MMO: WILL BE OVER WRITTEN.

>;
>FLX MM:/ZE
FLX -- DEVICE HANDLER MISSING
>FLX MM:/DO=FI.LEX,FUNCTI.ONS/RS
FLX -- DEVICE HANDLER MISSING
>F'LX MM: /LI
FLX -- DEVICE HANDLER MISSING
>HEM FLX
>'1.'IM
13:13:07 06-FEB-79

10-9

INSTALLATION VERIFICATION PROCEDURE

>;
>;
>;
>;
>;
>;

* FLX VERIFICATION COMPLETE *
* DMP VERIFICATION *

>TIME
13:13:12 06-FEB-79
>INS SY: [l,54]DMP/TASK= ••• DMP
>DMP TI:=ASRC.XXX/AS/RC

DUMP OF DB3:[2~300]ASRC.XXX;l - FILE ID 2171,l,O
RECORD NUMBER 00. - SIZE 16. BYTES
000000

D M P

W 0

R K S

*** EOF ***
>REMOVE ••• DMP
>TIME
13:13:24 06-FEB-79

>;
>;
>;

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

* DMP VERIFICATION COMPLETE *
* CREF, PMD, AND PRT VERIFICATION *
THIS ROUTINE OPERATES THE FOLLOWING UTILITIES:
MAC,TKB,CREF,PMD,PRT
IF ALL ARE FUNCTIONAL, AN EXAMPLE OF A MACRO LISTING WITH SYMBOL
AND MACRO CROSS-REFERENCE LISTINGS ATTACHED ARE SPOOLED TO
THE LINE PRINTER, A TASK ARE RUN AND IT CRASHES AND A
POST-MORTEM DUMP LISTING OF THE CRASHED TASK IS SPOOLED.

>TIM
13:13:44 06-FEB-79
>INS [l,54]CRF/TASK= ••• CRF

>;
>MAC CRTEST,CRTEST/CR/-SP=CRTEST
>TKB CRTEST/PM=CRTEST

>;
>PIP CRTEST.LST/SP
PIP -- FAILED TO SPOOL FILE FOR PRINTING
DB3:[2,300]CRTEST.LST;4

>;
RUN CRTEST

>;
>REM CRF
TASK "TTO
" TERMINATED
ODD ADDRESS OR OTHER TRAP FOUR
PC=001236
PS=l70001
RO=OOOOOO
Rl=llllll
R2=022222
R3=033333

10-10

AllJ\,

INSTALLATION VERIFICATION PROCEDURE

.'--"

R4=044444
R5=055555
SP=OOll 72
POST MORTEM DUMP WI LL BE GENERATED
>TIM
13:14:10 06-FEB-79

>;
>;

* CREF, PMD AND PRT VERIFICATION COMPLETE *

>;
>;

>RUN DEFINE

>;
>;
>;

* DSC VERIFICATION *

>;
>TIMi
13:14:38 06-FEB-79
>SET /UIC=[2,300]

>; .BECAUSE YOU DO NOT HAVE A FLOPPY DRIVE OR DEC TAPE,
>; AN AUTOMATIC VERIFICATION OF DSC OPERATION IS DEEMED
>; IMPRACTICAL.
>; THE DSC TEST IS BEING SKIPPED.

>PIP *.TMP;*/DE
PIP -- NO SUCH FILE(S)
SY0:[2,300]*.TMP;*

>;
>;
>;

* LBR VERIFICATION *

>TIME
13:14:52 06-FEB-79
>INSTALL SY:[l,54]LBR/TASK= ••• LBR

>; Create an object module library.
>LBR OBJLIB/CR::::OBJ

>1 Insert three object modules into the library.
>LBR OBJLIB/IN=OBJCT1,0BJCT2,0BJCT3

>1 Insert an existing module into the library (error expected).
>LBR OBJLIB/IN=OBJCT2
LBR -- *FATAL*-DUPLICATE MODULE NAME "OBJ2

" IN OBJCT2.0BJ;l

>1 Replace two existing modules.
>LBR OBJLIB/RP=OBJCT1,0BJCT2
MODULE "OBJl
" REPLACED
MODULE "OBJ 2

" REPLACED

>1 Display the contents of the object module library.
>LBR OBJLIB/LE/FU
DIRECTORY OF FILE OBJLIB.OLB;l
OBJECT MODULE LIBRARY CREATED BY: LBR V06.00
LAST INSERT OCCURRED 6-FEB-79 AT 13:15:27
MNT ENTRIES ALLOCATED: 256; AVAILABLE: 253
EPT ENTRIES ALLOCATED: 512; AVAILABLE: 506
FILE SPACE AVAILABLE: 21897 WORDS
RECOVERABLE DELETED SPACE: 00150 WORDS
** MODULE:OBJl
ENT$Al

SIZE:00075

INSERTED:6-FEB-79

ENT$Bl

10-11

IDENT:ID 1

INSTALLATION VERIFICATION PROCEDURE
** MODULE: OBJ 2
.E:NT$A2

INSERTED:6-FEB-79

IDENT:ID 2

SIZE:00075 INSERTED:6-FEB-79

IDENT:ID 3

ENT$B2

** MODULE:OBJ3
.E:NT$A3

SIZE:00075

ENT$B3

>PIP OBJLIB.*;*/DE
>REMOVE ••• LBR
>TIME
13:15:59 06-FEB-79
>;
* LBR VERIFICATION COMPLETE *

>;
>;

* PAT VERIFICATION *

>;
>TIME
13:16:04 06-FEB-79
>INSTALL [l,54)PAT/TASK= ••• PAT
>1 Create an updated object file.
>PATCH PATCHD.PAT=OBJCTl,PATCHl
>1 Compare the updated object file with one of known quality.
>CMP TI:=PATCHD.PAT,PATCHD.XXX
1)
PATCHD.PAT;l
2)
PATCHD.XXX;l

NO DIFFERENCES FOUND
TI:=PATCHD.PAT,PATCHD.XXX
>PIP *.PAT;*/DE
>REMOVE ••• PAT
>TIME
13:16:22 06-FEB-79
>;
* PAT VERIFICATION COMPLETE *

>;
>;

* SLP VERIFICATION *

>; '

>TIME
13:16:27 06-FEB-79
>INSTALL [l,54]SLP/TASK= ••• SLP
>! Invoke the SLP Editor to edit a data file.
>SLP @SLPCMD
! "SLP OUTPUT.SLP,LIST.SLP/-SP=SLPDAT.XXX"
>! Verify that the editing was properly performed.
>CMP TI:=OUTPUT.SLP,SLPOUT.XXX
l) OUTPUT.SLP;l
2) SLPOUT.XXX;l
NO DIFFERENCES FOUND
TI:=OUTPUT.SLP,SLPOUT.XXX
>PIP *.SLP;*/DE
>REMOVE ••• SLP
>TIME
13:16:46 06-FEB-79
>;
* SLP VERIFICATION COMPLETE *

* INTERACTIVE UTILITIES VERIFICATION

>;
>;

ENTER A CHARACTER TO CONTINUE FROM EACH
EDITOR SUCCESSFULLY INVOKED AND CTRL Z TO EXIT FROM ACNT.

10-12

INSTALLATION VERIFICATION PROCEDURE

·~

>TIM
13:16:57 06-FEB-79
>EDI QQQQ.XXX
[CRiE:ATING NEW FI LE]
INPUT
>ABO EDI
TASK " ••• EDI" TERMINATED
ABORTED VIA DIRECTIVE OR MCR

>;
>PIP QQQQ.XXX;*/DE

>;
>INS [l,54]EDT
>ED 1r
EDT>
>ABO EDT
TA~K " ••• EDT" TERMINATED

ABORTED VIA DIRECTIVE OR

MCR

>;
>REM EDT
>ZAP
ZAP>
>ABO ZAP
TASK " ••• ZAP" TERMINATED
ABORTED VIA DIRECTIVE OR MCR
>INS [l,54]ACNT/TASK=ACNT
>RUN ACNT
* ACCOUNT FILE MAINTENANCE PROCEDURE *
OPTIONS ARE: A - ADD, C - CREATE, D - DELETE, E - EXAMINE,
L - LIST, M - MODIFY, S - SORT, CTRL/Z - EXIT
ENTER OPTION: ~z
OPERATION COMPLETE

>REIM ACNT
>TIM
13:17:22 06-FEB-79

>;
>;

* INTERACTIVE UTILITIES VERIFICATION COMPLETE *

>;
>UN:L MM:
UNL -- DRIVER NOT LOADED
>PIP *.DAT;*/DE

>;
>; IF ANY ERRORS HAVE BEEN LOGGED BY ERROR LOGGER, WHEN THE COMMAND FILE EXITS
>; YOU SHOULD PRINT SY:[2,300]ERRLOG.LST AND INVESTIGATE THE ERRORS.

>;
>ERF
ERF -- REQUESTED "ERRLOG" TO STOP LOGGING
ERL -- LOGGING ENDED AFTER 9 ERRORS
>INS LB:$PSE
> IN:S LB: $SYE
INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN

>PS.E SY:=SY:
>SYE SY:=SY:/-SP

>RUN ERRLOG
ERL -- ERROR LOG INITIALIZED

>REM PSE

10-13

INSTALLATION VERIFICATION PROCEDURE
>REM SYE

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

IF YOU WANT TO REMOVE FROM THE SYSTEM ALL FILES ASSOCIATED
WITH THIS PROCEDURE, ANSWER THE FOLLOWING QUESTION WITH N.
THE ANSWER Y (FOR "YES, SAVE") LEAVES THE TASK, DEFINE,
INSTALLED. ALL NECESSARY FILES REMAIN ON THE SYSTEM DISK TO
ENABLE A REPEAT RUN.
:00 YOU WISH TO SAVE THE PROCEDURE TO RUN AGAIN? [Y/N] :Y

-·

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

>TIM
13:18:07 06-FEB-79

*** END OF RSX-llM V3.2 INSTALLATION VERIFICATION ***

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

>@ <EOF>

>
ERROR CODES

10.5

The following text is a compilation of the error codes produced by the
various modules in the RSX-llM Installation Verification Procedure.
All the modules print an error number that is either the contents of
F.ERR(RO) for I/O errors or $DSW for Executive directive status codes.
DEFINE.TSK - System Configuration Module
When an error occurs, DEFINE.TSK prints "DEFINE ERROR # nn ccc", where
nn is the number of the error and ccc is the contents of F.ERR(RO) for
I/O errors or $DSW for Executive directive status.
Both F.ERR and
$DSW appear in octal word format.
Therefore, when the high-order byte
shows as a minus one, it indicates that the error is from an Executive
directive.
The number of the error refers to the instruction that
caused it.
Below is a list of possible error numbers and their
meanings.
ERROR #

DEFINITION

l
2

OPEN$W
OPEN$R

3
4

READ$
WAIT$

CLOSE$

6
8

CLOSE$
PUT$
EXIT$S

- OPEN TO CREATE CONFIG.CMD FILE FAILED
- OPEN FILE TAILOR.DAT FOR READ (FDB=FDTAIL)
FAILED
- READ OF FILE TAILOR.DAT FAILED (FDB=FDTAIL)
- WAIT FOR FILE TAILOR.DAT (FDB=FDTAIL)
FAILED
- CLOSE OF FILE TAILOR.DAT (FDB=FDTAIL)
FAILED
- CLOSE FAILED FOR CONFIG.CMD FILE
- OUTPUT TO CONFIG.CMD FILE FAILED
- EXIT FAILED

LOGGER.TSK - Monitoring Task for QT Load Tasks
When an error occurs, LOGGER.TSK prints "LOGGER ERROR # nn ccc", where
nn is the number of the error and ccc is the contents of F.ERR(RO) for
I/O errors or of $DSW for Executive directive status.
Both F.ERR and
$DSW appear in octal word format.
Therefore, when the high-order byte

10-14

INSTALLATION VERIFICATION PROCEDURE

shows as a minus one, it indicates that the error is from an Executive
directiveo
The number of the error refers to the instruction that
caused itfi Below is a list of possible error numbers and their
mec:mings.
E:RROR #

•

DEFINITION

OPEN$W

PUT$

4
5

PUT$
PUT$

PUT$R

14
15

WSIG$S
RCVD$C
ALUN$S
WTSE$C
SETF$S
SDAT$S
CLOSE$

16
17

GTIM$C
CLEF$S

10
11

12
13

- Failure of open for write to RUNLOG.DAT
file.
- Failure of open for write to ERRLOG.DAT
file.
- Failure of write to ERRLOG.DAT or RUNLOG.DAT
file.
- Failure of write to ERRLOG.DAT file.
- Failure of write to ERRLOG.DAT or RUNLOG.DAT
file.
- Failure of write to RUNLOG.DAT or ERRLOG.DAT
file.
- Wait for significant event directive failure.
- Receive data directive failure.
- Assign LUN directive failure.
- Wait for significant event directive failure.
- Set event flag directive error.
- Send data directive failure.
- Close failure of RUNLOG.DAT or ERRLOG.DAT
file.
- Get time directive failure.
- Clear event flag directive failure.

NULl.TSK - One Form of the QT Load Tasks
When a directive error occurs, the QT load task prints "TASK QTnn
ABORTING", where nn is the task number that identifies the specific
task. The module then displays an error identifying number as "ERROR
# n". It then displays the octal error code found in $DSW. The error
codes in $DSW are defined in the RSX-llM/M-PLUS Executive Reference
Manual or the RSX-llM Mini-Reference. Below is a list of possible
~or-numbers and their meanings.
E:RROR #

'-".

DEFINITION

SPND$S
RCVD$C

ALUN$S

MRKT$C
EXIF$S
DSCP$S
SDAT$S

5
6
7

ASTX$S
CLEF$C .

- Suspend directive issued by QT task failed.
- Receive Data directive failed (receive from
CONFIG).
- Assign Logical Unit Number directive failure
to use TT# received from CONFIG.TSK
- Mark Time directive failure.
- Exit directive failure.
- Disable Checkpointing directive failure.
- Send Data directive failure (send to LOGGER
before exiting). Insufficient dynamic
memory can cause this error.
- AST Service Exit directive failure.
- Clear Event Flag directive failure.

QTRUN.TSK - Start Up the QT Load Tasks
When an error occurs, QTRUN.TSK prints "QTRUN ERROR # nn ccc", where
nn is the number of the error and ccc is the contents of F.ERR(RO) for
I/O errors or of $DSW for Executive directive status. Both F.ERR and

10-15

INSTALLATION VERIFICATION PROCEDURE
$DSW appear in octal word format.
Therefore, when the high-order byte
shows as a minus one, it indicates that the error is from an Executive
directive.
The number of the error refers to the instruction that
caused it.
Below is a
list of possible error numbers and their
meanings.
ERROR #

DEFINITION

OPEN$W

2
3
4
6

OPEN$R
READ$
WAIT$
CLOSE$
CLOSE$

GPRT$C

PUT$

RSUM$S

RQST$S

WSIG$S

14
15
16

RSUM$S
RQST$S
SDAT$S

SDAT$S

18
19
20
21

RSUM$S
EXIT$S
GTIM$C
ALTP$C

MRKT$C

- Open failure on DVLREM.CMD or DVLSET.CMD
file.
- Open failure on TAILOR.DAT file.
- Read failure on TAILOR.DAT file.
Wait failure on TAILOR.DAT file.
- Close failure on TAILOR.DAT file.
- Close failure on DVLSET.CMD file or
DVLREM.CMD file.
- Get Partition Parameters Executive directive
failure.
- Write failure for .CMD files created by
QTRUN.
- Resume Executive directive failure for DUMMY
task.
Request Executive directive failure for
LOGGER task.
- Wait for Significant Event Executive
directive failure.
- Resume Executive directive failure.
- Request Executive directive failure.
- Send Data Executive directive failure
(failure of Send Data to QT task).
- Send Data Executive directive failure
(failure of Send Data to Logger task).
- Resume Executive directive failure.
- Exit Executive directive failure.
- Get Time Executive directive failure.
- Alter Priority Executive directive failure
(alteration of indirect command file
processor failed).
- Mark Time Executive directive failure.

10-16

CHAPTER 11
SYSGEN ERROR MESSAGES

All messages from SYSGEN appear in this chapter in alphabetical order.
The descriptions that follow each message explain the possible cause
and, as necessary, suggest remedial action.
SGN -- Attempt to use non-existent default for parameter parm -- RETRY

Explanation: A required parameter (number "parm") was missing
from the response to the current peripheral question. Reenter
the entire response. Note that the [L/R] parameter does not
count.
SGN -- Baseline terminal
protection selected.

driver

not

valid

option

with

multiuser

Explanation: The half duplex baseline terminal driver includes
no SYSGEN options and cannot execute in a multiuser protection
system (for example, breakthrough write is required but not
included). Choose a different terminal driver.
SGN -- CO driver not valid on RSX-llS systems -- SUPPRESSED

Explanation: RSX-llS systems cannot include the
(CO). SYSGEN ignores this entry.
SGN --

console

driver

cb driver not valid on unmapped system -- SUPPRESSED

Explanation: Unmapped systems cannot include the console
(CO). SYSGEN ignores this entry.
SGN -- Correct problems and reassemble the
continue when done.

bad

modules

SYSGEN

driver

will

Explanation: This message indicates that you detected an error
in assembling the Executive or the device drivers (you responded
No at either the Executive or driver EOX breakpoint). After you
correct the error, reassemble the bad modules and SYSGEN will
cont:inue.
SGN -- Correct problems -- SYSGEN will restart assemblies when done

Explanation: This message indicates that you detected an error
in assembling the laboratory peripheral devices.
After you
correct the error, SYSGEN will attempt to re-assemble the
laboratory peripherals common area(s).

11-1

SYSGEN ERROR MESSAGES
SGN -- DMll-88
specified

CSR address
RETRY

must

greater

than

157777

Explanation: If the system includes a DMll-88, the CSR address
must be greater
than or equal to 160000.
If not included, the
CSR address must be zero.
SGN -- DMll-88
specified

vector address
RETRY

must

greater

than

277

Explanation:

If the system includes a DMll-88,
the
interrupt
vector address must be greater than or equal to 300. If not
included, the vector address must be zero.

SGN -- Dynamic storage
words -- RETRY

space

must

multiples

two

Explanation: The system allocates pool in 4-byte sections.
Thus, the amount of pool must be a multiple of 4 bytes.
SGN -- GR not valid on system with more than 124K -- SUPPRESSED

Explanation: The graphics display driver (GR) does not execute
on 22-bit processors.
If your system includes a GR, the maximum
amount of memory is 124K. If you have a GR and wish to use
it,
type CTRL/Z and restart specifying 124K or less for memory size.
SGN -- Illegal character in numeric response -- RETRY

Explanation:

A character other than 0-7 for an octal response or
0-9 for a decimal
response was entered. Note that the use of
special characters (# or .) to indicate an explicit octal or
decimal response is forbidden.
SGN -- Illegal device mnemonic

Explanation:

This message applies only to dual RK~5 kit users
that
answered
Y to question 9
(skip end of disk
(EOD)
breakpoints).
If you wish to ignore EOD breakpoints,
you must
enter the device that contains the driver source files.
The
message indicates that you incorrectly specified the driver
source device;
enter a minimum of two characters.

SGN -- Illegal device mnemonic -- RETRY

Explanation:

You specified a drive type that the device does not
support (such as RP06 for a DL device).

SGN -- Illegal numeric answer -- RETRY

Explanation:

See the description of Illegal character in numeric

response.

11-2

SYSGEN ERROR MESSAGES
SGN -- Illegal printer specification -- Valid types are LPll-C, D,
H, J, K, R, S, V, W, Y, Z, LSll, LA180, and LVll -- RETRY

Explanation:
SYSGEN only supports the above named line printer
controllers.
If you have a different controller, refer to the
peripheral question concerning LP:
to match your
printer
characteristics with a DEC standard printer.
SGN -- Illegal trailing characters or extra parameters "parm" -- RETRY
Explanation: You have specified more parameters than allowed for
this response. Remember that parameters in brackets can only be
specified for the first controller of this type.
SGN -- Invalid directive code "direc-code"
Explanation: You have entered other than A, B,
I, or %. The line is discarded.

c, D, E, F, G, H,

SGN -- Invalid system device -- RETRY
Explanation:
The device specification for the
disk was improperly or incorrectly entered.

Executive

source

Big disk kits:
The default response is SY:;
enter either Y or
carriage
return.
Otherwise, you must enter at least two
characters to identify the device that contains the Executive
sources.
Dual RK or RLOl kits:
There is no default response to
question.
Enter the device
(minimum two characters)
contains the Executive sources.

this
that

SGN -- Listing files cannot be sent directly to LP: -- RETRY
Explanation: Spooled listings must go to a real device.
Also,
for online SYSGENs, maps cannot go directly to the line printer.
If you want to print at LP:, specify LPO:.
SGN -- Loadable driver support was not selected in the Executive
section of SYSGEN. Device cannot be made loadable -- RETRY
Explanation: You did not include loadable driver support in
system. All device drivers must be resident.

the

SGN -- Loadable/Resident indication not valid for this device -- RETRY

•
•

Explanation:
device.

Loadable or resident is

not

option

for

this

SGN -- Maps cannot be sent directly to line printer -- RETRY
Explanation:
Spooled maps must first go to a spool device.
Also, for online SYSGENs, the maps cannot go directly to the line
printer (specify LPO:).

11-3

SYSGEN ERROR MESSAGES
SGN -- Maximum of 1 CRT monitor possible with VTll -- RETRY
Explanation: A VS60 can support two CRT
supports only one.

monitors,

but

VTll

SGN -- Maximum of 8 printers allowed on a system with a KMC -- RETRY
Explanation:

The KMC-11 supports up to eight line printers.

SGN -- Maximum of nn.

controllers allowed for device dd -- RETRY

Explanation: The specified device supports nn controllers. Note
that pseudo devices can only indicate one controller. Terminal
driver hardware controllers are specified later.
SGN -- Memory size inconsistent with mapping option
Explanation: The maximum memory size for an unmapped system is
28K-words.
The minimum memory size for a mapped system is
24K-words. You have either specified
(in question 4, Memory
size) more than 28K-words of memory for an unmapped system
(question 5) or less than 24K-words of memory for a mapped
system.
SGN -- Memory not multiple of 4K
Explanation: When you specify memory siza, it must
multiple of 4.

even

Explanation: The UDC-11 supports a maximum of 252 modules.
have specified more than the maximum.

You

SGN -- More than 252.

modules specified -- RETRY

SGN -- Number of interrupts must be divisible into 10,000.
Explanation: The number of interrupts per second for the KWll-P
clock was not 1, 2, 4, 5, 8, 10, 16, 20, 25, 40, 50, 80, 100,
125, 200, 250, 400, 500, 625, 1000, 1250, 2000, 2500, or 5000.
Note that more than 100[10)
clock interrupts
significantly increases system overhead.

per

second

SGN -- Number of samples must be evenly divisible into 10000. -- RETRY
Explanation:

Sampling rate must be evenly divisible into 10000.

SGN -- Overlapping modules -- RETRY
Explanation: The last module specified attempts to use slots
that you have indicated occupied by other modules. Review your
configuration and try again.

11-4

SYSGEN ERROR MESSAGES
SGN -- Parameter (#N) "parm" out of range n to n -- RETRY
Explanation: The
indicated
parameter
(excluding
Loadable/Resident) is not within the acceptable range.
SGN -- Pausing to allow copying of [ggg,10] files to baseline disk
I

Explanation:

This message applies to RLOl kit users only.

SGN -- Pausing to allow editing of Executive source
Explanation:
informative.

This is not an error message;
the message is
It indicates that you wish to edit Executive files.

SGN -- Pausing to allow loading of EXCSRC disk
Explanation: This message applies to dual RKOS kit users only.
The message indicates that SYSGEN will pause while you load the
EXCSRC disk into the proper drive.
SGN -- The full duplex terminal driver requires memory management and
loadable driver support. If you desire the full duplex driver,
you must repeat the Executive questions and select these options.
Explanation: As the message states, you must include memory
management directives (PLAS) and loadable driver support to
select the full duplex terminal driver.
SGN -- Unable to determine system type -- assuming unmapped
Explanation: This message applies to RLOl kit users only.
When
you generate a mapped system, you must use a mapped system.
Likewise, when generating an unmapped system, use an unmapped
system.
This message indicates that the system UIC has been
changed and does not end in 0 or 4; SYSGEN must choose.
SGN -- Unit number must be an integer in the range O to 7
Explianation:

The crash device must be unit number 0-7 inclusive.

SGN -- Unrecognizable string "ddn" -- Ignored
Explanation: SYSGEN could not
Perhaps you omitted a comma.

parse

SGN -- Valid char detec expan unit indics.
(no) -- RETRY

•

the

are

indicated

"C"

(yes)

string.

and

"NO"

Explanation: Valid responses for this paramter are C,
to
indicate that controller includes character unit, and NO, to
indicate it does not.

11-5

SYSGEN ERROR MESSAGES
SGN -- Valid D/A present
(no) -- RETRY

"D"

indicators

Explanation:

DT,

DK,

MT,

MS,

MM,

Explanation:

The CDA routine does not
entered as a dump device.

SGN -- Valid DRll-K
(no) -- RETRY

Explanation:
indicate
not.

that

present

indicators

are

"NO"

to
parameter are D,
converter, and NO, to

Valid
responses for this
indicate that controller includes D/A
indicate that it does not.

SGN -- Valid devices:
DR -- RETRY

and

(yes)

DD,

DB,

DM,

DL,

support

the

device

you

"DRK"

(yes)

and

"NO"

Valid responses for
this parameter are DRK,
to
DRll-K is present, and NO, to indicate that it is

SGN -- Valid duplex indicators are "H" and "F" -- RETRY

Explanation:
indicate
line.

Valid
responses for this parameter are H,
to
half duplex line, and F, to indicate a full duplex

SGN -- Valid err detec expand unit
(no) -- RETRY ,

indics.

are

"E"

(yes)

and

Explanation:

Valid
responses for
this parameter are E,
to
indicate that error detection expander unit is present, and NO,
to indicate that it is not present.

SGN -- Valid indicators are "H", "F", and "P" -- RETRY

Explanation:

Valid responses for this parameter are H,
to
indicate half duplex line,
P,
to indicate primary station of
line, and F, to indicate full duplex line.

SGN -- Valid graphic

devic~

indicators are "VTll" and "VS60" -- RETRY

Explanation:

Valid responses for this parameter are VTll,
to
indicate a VTll graphics display device, and VS60, to indicate
VS60 graphics display device.
SGN -- Valid line speeds are 50, 75, 110, 134.5, 150, 200,
1200, 2400, 4800, and 9600 -- RETRY

Explanation:

300,

600,

The controller does not support the specified

line

speed.

11-6

SYSGEN ERROR MESSAGES

SGN -- Vail id
listing
{default)
RETRY

devices

are:

SY:,

TI:,

and

"None"

Explanation: When performing an RSX-llS system generation using
an !AS host system, the listing device must be SY: or TI:.
SGN -- Valid map devices
SY:) -- RETRY

are:

SY : ,

TI : ,

and

"None"

(default

Explanation: When performing an RSX-llS system generation
an !AS host system, the map device must be SY: or TI:.
SGN -- Valid offset
(no} -- RETRY

recovery

indicators

are

"O"

(yes)

and

using

"NO"

Explanation: Valid responses for this parameter are o, to
indicate
that all of this controller type support off set
recovery, and No, to indicate that none of the controllers of
this type support it.
SGN -- WARNING -- CPU does not have
switch directive not included

switch

sense

Explanation: The processor you specified does not have a switch
register.
Thus, you cannot use the get sense switch directive.
If you wish to include the directive, edit RSXMC.MAC and add the
line G$$TSS=O.
SGN -- WARNING -- Null device forced into system

Explanation: This message indicates that SYSGEN has forced the
null device into your configuration. The nu~l device is required
to redirect data normally sent to either the system disk or the
terminal driver (both of which your system does not include).
SGN -- WARNING -- Terminal driver forced into configuration

Explanation: RSX-llM requires a terminal driver for operation.
You forgot to specify a terminal driver so SYSGEN put one in for
you. Later, SYSGEN will ask which terminal driver you want to
use •

•

11-7

APPENDIX A

SYMBOLS FOR SAVED ANSWER FILES

Syml~

'-'.·

Definition

$TPH

.SETS

Processor type (for example "ll/60")

$SWH

.SETT
.SETF

Processor has a switch register
Processor does not have a switch register

$llS

.SETT
.SETF

Generating RSX-llS
Generating RSX-llM

$TMg

.SETN

Memory size in K-word blocks

$MAP

.• SETT
,.SETF

Generating mapped system
Generating unmapped system

$KSH

.. SETT
.. SETF

System includes K-series laboratory peripherals
System does not include
K-series
laboratory
peripherals

$EAE!

uSETT
.,SETF

System includes extended arithmetic element
System does not include
extended
arithmetic
element

$FPP

.. SETT
.SETF

System includes floating point processor
System does not include floating point processor

$FIS

.SETT
.SETF

System includes floating instruction set
System does not include floating instruction set

$PRO

.SETN

Number of KWll-P
excludes KWll-P)

$LIN

.SETS

Line frequency (A=60Hz, B=SOHz)

$WA'I'

.SETT
.SETF

System includes KWll-Y watchdog timer
System excludes KWll-Y watchdog timer

$MPR.

.,SETT
.SETF

System includes memory parity support
System excludes memory parity support

$CAH

.SETT
.SETF

System contains cache memory
System does not contain cache memory

$HIV

.SETN

Highest interrupt vector address
(if
highest
vector
specified
or
less than 400, SYSGEN
recalculates;
$HIV not saved until peripheral
section is complete)

$DEV

.SETS

Peripheral devices and number of controllers

A-1

clock

interrupts/second

SYMBOLS FOR SAVED ANSWER FILES
Symbol

Definition

$DV2
$DV3

.SETS
.SETS

Peripheral devices and number of controllers
Peripheral devices and number of controllers

$0NL

.SETT
.SETF

Online SYSGEN
Standalone SYSGEN

$LPR

.SETT
.SETF

Host includes a line printer
Line printer not available on host

$SPL

.SETS

"/SP" spool listings and maps,
"/-SP" do not spool

$PW!

.SETT
.SETF

Printer width at least 120 columns
Printer width less than 120 columns

$ALO

.SETS

Device mnemonic for assembly
trailing ":", SY:
is ""

listing

$MPD

.SETS

Device mnemonic for Executive
maps

and

$DBM

.SETT
.SETF

DBMS-11 support
No DBMS-11 support

$Fll

.SETT
.SETF

Files-11 ACP support
No Files-11 ACP support

$RMS

.SETT
.SETF

Record Management System support
No RMS support

$NRT

.SETT
.SETF

Non-resident task support
No task loader support

$LLR

.SETT
.SETF

Loadable task loader
Resident task loader

$MMD

.SETT
.SETF

Memory management directives support
No PLAS support

$SRR

.SETT
.SETF

Send/receive by reference support
No send/receive by reference directives

$GMC

.SETT
.SETF

Get mapping context support
No get mapping context directive

$ACK

.SETT
.SETF

Address checking support
No support

$IOR

.SETT
.SETF

I/O rundown support
No support

$MUP

.SETT
.SETF

Multiuser protection support
No support

$ANM

.SETT
.SETF

ANSI magtape support
No support

$0UD

.SETT
.SETF

Online formatting and user-mode diagnostic support
No support

$LOO

.SETT
.SETF

Loadable driver support
Resident drivers only

A-2

files

device

driver

•

SYMBOLS FOR SAVED ANSWER FILES
Symbol
$LLD

.SETT
.SETF

All loadable drivers loadable
All loadable drivers (except full
built as resident

$AS'.f

.SETT
.SETF

AST support
No support

$TK'.r

.SETT
.SETF

TKTN support
No support

$PRF

.SETT
.SETF

Power fail recovery support
No support

$IRR

.SETT
.SETF

Install-run-remove on exit support
No support

$20JK

.SETT
.SETF

20K Executive
16K Executive

$LGD

.SETT
.SETF

Logical device assignment support
No support

$OTO

.SETT
.SETF

Log device errors and interrupt timeouts
No logging

$UNI

.SETT
.SETF

Log undefined interrupts
No logging

$PAR

.SETT
.SETF

Log memory parity errors
No logging

$UWD

.SETT
.SETF

System to include user-written driver
No user-written drivers

$GTW

.SETT
.SETF

System includes get word Executive routine
System excludes get word Executive routine

$PTW

.SETT
.SETF

System includes put word Executive routine
System excludes put word Executive routine

$WCH

.SETT
.SETF

System supports disk writecheck
No support

$XD'.r

.SETT
.SETF

System supports Executive Debugging Tool
No XDT

$RO'.f

.SETT
.SETF

Rotating data lights
No rotating lights

$NE'.r

.SETT
.SETF

Industrial network and DECnet support
No network support

$PRN

.SETT
.SETF

System supports queue manager
No queue manager

$GGE

.SETT
.SETF

Group global event flag support
No support

C·

Definition

A-3

duplex

TTDRV)

SYMBOLS FOR SAVED ANSWER FILES
Symbol
$DRR

Definition
.SETS

Executive directives code:
"ABCDEFGHI"
(A= get partition parameters,
B=
get
task
parameters, C= send/receive, D= alter priority, E=
extend task, F= connect to interrupt vector, G=
get sense switch, H= parent/offspring tasking, I=
stop bit)

$NPK

.SETN

Number of pre-allocated QIO
speed optimizations)

$DTV

.SETN

Size of data transfer vector in words (if
$DTV=O)

$RRS

.SETN

Round-robin scheduling
round-robin scheduler)

excludes

$HIC

.SETN

Highest priority class for round-robin
(if $RRS=O, $HIC=O)

scheduling

$LOC

.SETN

Lowest priority class for
(if $RRS=O, $LOC=O)

scheduling

$DKS

.SETN

Swapping interval for
Executive
level
disk
swapping (O excludes Executive level disk swapping
support)

$SWP

.SETN

Executive level disk swapping
priority) (if $DKS=O, $SWP=O)

$DSA

.SETN

Size of dynamic storage region (pool space)

$PNR

.SETN

Seconds between line printer not ready messages (0
suppresses messages)

$CRR

.SETN

Seconds between card reader not ready messages
suppresses messages)

$RSD

.SETN

CSR address for register and stack dump device
(0
excludes stack and register dump following crash)

$CKP

.SETS

Checkpointing (A= checkpointing, B= checkpointing
with system checkpoint file,
empty string = no
checkpointing support)

$MEM

.SETS

System
controlled
partitions
(A=
system
controlled, B= with the shuffler, empty string =
no system controlled partitions)

$CRA

.SETS

Dump routine (A= PANIC, B= CDA, empty string =
memory dump routine)

$NOT

.SETN

CSR address for CDA crash notification device
$CRA not equal B, $NOT not in file)

(if

$MDD

.SETS

Device mnemonic for CDA memory dump (if
equal B, $MDD not in file)

not

$MDC

.SETN

CSR address of CDA dump device (if $CRA not
B, $MDC not in file)

$PDD

.SETN

CSR address of PANIC dump
equal A, $PDD not in file)

A-4

packets

interval

(0=

round-robin

device

range

(if

QIO

$NPK=O,

(swapping

$CRA

equal
not

SYMBOLS FOR SAVED ANSWER FILES
Sym~

Definition

$T'I'Y

.SETS

Terminal driver (A= tailorable half duplex, B=
user oriented half duplex, C= full duplex, D=
baseline half duplex)

$TMN

.SETN

Timeout value (if $TTY not equal c, $TMN not in
file)
(0 excludes support for unsolicited input
timeout feature)

$FHM

.. SETT
.SETF

Pass form feeds directly to terminal
Convert form feeds into 8 line feeds

$ACR

.SETT
.SETF

Support automatic carriage return/line feed
No support

$TCK

.SETT
.SETF

Task checkpointable during terminal input support
No support

$USC

.SETT
.SETF

AST on unsolicited input character
No support

$CNO

.SETT
.SETF

CTRL/O cancellation support
No support

$BW'S

.SETT
.SETF

Breakthrough write support
No support

$CNR

.SETT
.SETF

CTRL/R support
No support

$ESC

.SETT
.SETF

Process escape sequences
No support

$MLC

.SETT
.SETF

Get multiple characteristics support
No support

$SMC

.SETT
.SETF

Set multiple characteristics support
No support

$GTD

.SETT
.SETF

Get terminal driver options support
No support

$HSM

.SETT
.SETF

Hold screen mode support
No support

$TRW

.SETT
.SETF

Transparent read write support
No support

$SCC

.SETT
.SETF

Settable case conversion support
No lower to upper case conversion

$RAP

.SETT
.SETF

Read after prompt support
No support

$RNE

.SETT
.SETF

Read with no echo support
No support

$RST

.SETT
.SETF

Read with special terminator support
No support

$RUB

.SETT
.SETF

CRT rubout support
No backspace deletion

A-~)

SYMBOLS FOR SAVED ANSWER FILES
Definition

S:imbol
$THS

.SETT
.SETF

CTRL/S and CTRL/Q support
No support

$TIB

.SETT
.SETF

User terminal input buff er support
No support

$VTB

.SETT
.SETF

Variable length terminal input buffer support
No support

$L30

.SETT
.SETF

System includes LA30P
No LA30P

$HRE

.SETT
.SETF

Hardware unrecoverable input error support
No support

$DIC

.SETT
.SETF

Device independent cursor positioning support
No support

$EDX

.SETT
.SETF

Pause to allow editing Executive files
Do not pause

$ADR

.SETT
.SETF

Assembly listing device ready
Assembly listing device not ready

$INI

.SETT
.SETF

Assembly listing device must be initialized
Device is initialized

$AOL

.SETS

Assembly listing device label

$MOU

.SETT
.SETF

Mount assembly listing device
Need not mount device

$UFO

.SETT
.SETF

Create listing UFD
Do not create listing UFO

$IPE

.SETT
.SETF

Allow direct access to IP11/IP300 device registers
Do not allow direct access

$COB

.SETT
.SETF

Allow direct access to ICS/ICR modules
Do not allow direct access

$DUC

.SETT
.SETF

Allow direct access to UDCll modules
Do not allow direct access

$EXT

.SETT

Edit RSXMC to allow FORTRAN access
device registers
Do not edit

.SETF

laboratory

~
~

A-6

SYMBOLS FOR SAVED ANSWER FILES
Format of Saved Answers for Devices
Controller:
$$[device-mnemonic] [controller number]
For example:
.SETS

$$MMO

II I

2 II

Unit modifiers:
$[controller number] [device-mnemonic] [unit number]
For example:
.SETN
.SETS

$0MMO
$0DY1

"DOUBI..E"

............

•

A-7

~··

APPENDIX B

RMDEMO

B.l

INTRODUCTION

RMDgMo is a privileged task that displays information concerning task
activity
in an RSX-llM system. The display usually runs continuously
on a video terminal,
such as the VTOSB or the VT52.
A single
"snapshot" display can be run on a hard-copy terminal, such as an
LA36. The display format adapts automatically to the type of terminal
on which it runs.
Typically, RMDEMO is set running on a slaved terminal near the
computer as part of the system boot procedure.
Individual users can
also display RMDEMO on their terminals using the MCR command >RMD.
RMDEMO should be installed under the name ••• RMD for these commands to
work.
The display features include:
l~

Current date and time;

The currently active task;

All tasks, loaded drivers, and common blocks currently in
memory,
displayed in a graphic fashion to show their
individual memory requirements and locations relative to
other tasks;

The number of active tasks currently in memory,
the number
not currently resident,
and the total amount of memory
occupied by each group;

The current amount of available system dynamic memory
(pool
space),
including the largest available block and the number
of fragments;
and the worst case of pool space since
bringing up RMDEMO;

A graphic display of partition information;

The number of free blocks available on the system device
three or more additional mounted FILES-11 volumes;

The system error count sequence.

B-1

and

RMDEMO
RMDEMO scales the display to the memory size of the computer on which
it is executed.
The amount of memory displayed on the screen will
always be the next largest multiple of 32 words.
(In certain
instances,
this may cause an inaccurate amount of total memory to
appear.
For example, a 28K system running RMDEMO on an LA36 will
display somewhat over 29K of total memory. This anomaly in a rare
case was considered preferable to the alternative, which was to reduce
resolution in the display.)
Task locations and sizes displayed by RMDEMO should be considered
approximate. RMDEMO is primarily designed to provide a visual display
and system debugging tool.
It does not accurately measure task size
and location.

B.2

HARDWARE REQUIREMENTS

RMDEMO runs on RSX-llM and RSX-llS.
approximately SK.

B.3

It is non-overlaid

and

requires

BENEFITS OF USING RMDEMO

In general, RMDEMO is a useful task designed to allow either an
operator or user to view the current state of the operating system.
The information is presented in a graphic, easily comprehensible form.
There are a number of specific instances in which RMDEMO can help to
locate certain system lockout problems or bugs in application and/or
system-level software.
1.

Bugs and other situations that cause exhaustion of system
dynamic memory (resulting in unexplained system hangs) may be
detected and more easily reproduced and diagnosed.

Task checkpointing and swapping may be monitored -- and in
systems with limited memory, deadlock conditions may often be
more easily diagnosed.

Free space on a number of FILES-11 devices may be monitored
in real time, which may help in situations where online
storage is at a premium or where some program is running
wild.

B-2

RMDEMO
B.4

RMDEMO DISPLAY FIELDS

RSX-11M V3.2 BL26
512K
*IDLE* POOL~1386.:2686.:49.
:I. 386. : 2686. : 49.

rn:
:I. ;·5

:I. :I. 01\

our:
()

TMDMB PC M F.

DQ L R T

TCBMA 00 T 1+
:R::s OT A 1+
I L+ A AD
C + C CM

B
O
F
C

B MP MT
2 GP D 7
F • 0 E
C •
M

01\

• F· PP

())))-!>->><>-><-->

P •

21-JUN-79 11:52:42
DB1:178960+
DB2:68928. DB3:30857.

FREE~svo:35056+

TTPAF~

T
E

<->->->->->

<------>

SYSF'AI:~

T
T

TKNPAF~
DF~VF'Af~
l..I:tf~PAF~

T
D
T

BA!:IIC2 ("

0*******32******64******96******128*****160*****192*****224*****
E-P--T-TDC-0----------------------------------------------------

GEN

256*****288*****320*****352*****384*****416*****448*****480*****
Ef~l:~BEC~

32+

>
Figure B-1

Example of RMDEMO Display

The version number of the current
memory size.

The current date and time.

The currently executing task;
*IDLE* indicates that no task
is executing (the Executive is executing the idle loop).

Pool information in the format
line is:
X
Y
Z

system,

POOL=X:Y:Z

base

level,

where

the

and

first

size in words of the largest free block in pool;
total number of free words in the pool;
number of fragments in the pool free list.

and the second line records the worst case of pool since the
current execution of RMDEMO began.
(This second line will be
most useful on a slaved terminal that is started displaying
RMDEMO when the system is booted. Otherwise, this second
line gives worst-case pool
information from the time you
initiate the RMDEMO display on a termfnal.)

•

The number of free blocks on SYO:
FILES-11 devices •

Number of active tasks in memory and the amount of memory
they occupy, plus the number of active tasks checkpointed out
(not in memory) and the total memory they would require.

The name of each task in memory and a representation of other
information about the task, including size •

> active task

[
1

]

and up to 3 more

task not active, yet occupies memory
named common

B-3

selected

RMDEMO

=====

unnamed common, name displayed is first
attached task
loaded loadable driver, name displayed is
device mnemonic (see next entry)
task is not fixed in memory
task is fixed in memory

The hyphens ( -) or equals ( =) display
(very roughly)
the
amount and area of memory occupied by each task or driver.
Where the display shows only one delimiter ( <, !, +,
[,
(,
etc.),
the opening delimiter should be considered to appear
in the same position as the closing delimiter of the
preceding task.
8.

Loadable drivers loaded in memory,
identified by device
mnemonic.
Although drivers are not tasks,
they require
memory, and thus are displayed with tasks.

Partitions in the system.
Partition name comes first,
followed
by
a letter
identifying the partition type.
(Partition size is indicated in next entry.) The letters are
defined as follows:
T
S
D
C

task partition
subpartition
system-controlled (dynamic) partition
common partition

10. Partition size and location. The beginning of each partition
is marked by a letter in the same code as above, with the
following additions:
E
p

Executive
Pool (dynamic storage region)

The lines of asterisks (
proportional amount and
partition.

* ) represent (very
area

memory

roughly)
the
occupied by each

11. The system error count sequence as recorded by the error
logger.
If error logging is not included in the system,
ERRSEQ will always equal zero.

B.5

DISPLAY CONFIGURATION OPTIONS

Certain parameters can be altered by the user who wants to develop
special versions of RMDEMO. The source file, located in UFD[l4,10] on
your distribution kit, contains extensive comments that should enable
you to alter the code to move or delete fields in the existing
display, or design additional display pages. These are two parameters
that can be changed on-line, from a running RMDEMO display:
- the display rate (interval at which information is updated)
- the names of the FILES-11 devices in the free-space display area.
Type ESC (ALT MODE or SEL) to display the command formats for changing
these parameters.

B-4

•

APPENDIX C
CONSOLE DRIVER AND CONSOLE OUTPUT TASK

Two facilities in RSX-llM -- the Console Driver and the Console Output
Task
(COT) -- handle messages sent to the console device (CO:). COT
is cl privileged task usually installed and maintained by the System
Manager. You can use COT to direct messages to:
•

The default console output device (usually TTO:)

•

Any other terminal that you assign as the console device
the COT SET commands

•

A console message logging file

with

COT SET commands allow you to assign the destination of the messages
to calternate devices or to terminate messages to the console device or
logging device.
The Console Driver sends all messages to COT, which
forwards them to the terminal or logging device that you have
sele~cted.

COT permits you to specify any terminal as a console terminal and to
change that specification, using privileged MCR SET commands.
You are
not restricted to using TTO:
as the console terminal. You can also
change the name of the file to which COT writes.
(Any part of the
command file specification can be changed independently.)
If COT is
aborted or the system crashes, you can recover the information in the
log file by using the Peripheral Interchange Program (PIP)
to unlock
the file.
You can then print its contents.
(PIP is described in the
RSX-11 Utilities Manual.)
The ConsolE~ Driver and COT are supported on mapped RSX-llM systems.
They are not supported on RSX-llS systems, because RSX-llS does not
support the disk volumes you need to use the Console Driver's
write-to-a-file feature.

C.l

OPERATING COT

The COT commands control the selection and operation of the console
terminal or the log file either separately or together.
You can
start, control, and terminate console, log file, or COT operation by
using one of the following privileged MCR SET commands:

•

'--''

>SET /COTERM[=ttn:]
>SET /NOCOTERM
>SET /LOGFILE[=ddnn:] [uic] [filename.filetype]
>SET /NOLOGFILE
>SET /COLOG [=TTn:] [ddnn:] [uic] [filename. filetype]
>SET /NOCOLOG

C-1

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
NOTE
The brackets indicate optional entries.
However,
brackets must be entered when
specifying the UIC, as [UIC]
Once COT is running, COT processes all messages directed to CO:
(in a
QIO operation,
for example). COT gets the time, prints the message
and time on the console terminal, and writes the information in a
file.
The default terminal
is TTO:
and the default file
is
SYO:[l,4]CONSOLE.LOG, unless you specify another terminal or file.
COT also uses the MCR SET commands to change or stop output to a
terminal or file.
You can change any COT option without stopping and
restarting the entire task.

c.1.1

Task Interfacing with COT

Task interfacing with COT deals with the task's attempts
messages, attach to, or read from the console terminal.

send

Tasks can write messages to CO:. The buffer in COT accepts messages
up to 256(10) bytes long. Therefore, any task sending longer messages
must include carriage-returns/line-feeds in the text.
Setting the
buffer
size
to something other than 256(10)
bytes can cause
unpredictable results.
When you have a task that must send a message to the console terminal,
start the message with a CTRL/G. This message prints on the terminal
regardless of the effect of a previously entered SET /NOCOTERM
command.
The CTRL/G causes COT to send the message to TTO:
if no
terminal is currently designated as the console terminal.
The message
goes to the current console terminal if one is designated.
A task may not attach to CO:.
If a task attempts to attach to CO:, an
invalid function code error occurs.
Only a task with the name COT ••• may read from CO:.
If another task
attempts to read from CO:, an invalid function code error occurs.

C.1.2

Using the REDIRECT Command with COT

When COT is not running, the system data structure (UCB) for CO:
is
directed to TTO:.
Messages directed to CO:
therefore go to the
terminal driver (TTDRV) and then to TTO:. When COT starts,
however,
it directs CO:
to CO:
by adjusting the redirect pointer in the data
structure. COT then receives messages directed to CO:
and sends them
to CODRV, which is the driver for console output. Therefore, to
change the console terminal while COT is running, use the SET /COTERM
command.
When you use this command, COT changes the console terminal
by issuing an Assign LUN Executive directive.
If you use the REDIRECT
command to affect the console terminal assignment while COT is
running, device assignment problems or a system loop may occur as a
result.

C-2

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
You may encounter two conditions when using the REDIRECT command
affect the console terminal assignment while COT is running.
1.

If you redirect CO:
to another device,
the device handler
for the device at the end of the redirect chain receives the
message meant for CO:. This means that you bypassed COT
entirely. Therefore, messages do not go to CO: and they are
not written on the logging device.
The console driver (CODRV) must receive messages sent to CO:
for COT to work properly. CODRV receives the messages only
if CO:
is directed to CO:.

C.2

You can use SET /COTERM to specify a different terminal for
output.
If you do this, do not use REDIRECT to redirect that
terminal back to CO:. Using REDIRECT in this way causes a
system loop that prevents any other processing on the system.

COMMAHD DESCRIPTIONS

COT commands fall into three categories:
1.

Commands that control the console

Commands that control the log file

Commands that control both the console and the log file

In the commands in which you specify all the options, the options must
be specified in the order shown.
Left and right brackets indicate
that the enclosed specification is optional. However, brackets must
be entered when specifying the UIC as [UIC].
In
the
commands
that
have
optional
file
specifications
(ddnn:[UIC]filename.filetype),
the default file specification is
SYO:[l,4]CONSOLE.LOG. Leaving out the device causes SYO:
to be used
and leaving out the filename.filetype causes CONSOLE.LOG to be used.

C.2.1

Commands that Control the Console

The following commands either
console terminal.

start

(or

stop)

COT

assign

the

>SET /COTERM[=TTn:]
>SET /NOCOTERM
Desc,ription
>SET' /COTERM
If COT is running,
this command
(without the TTn:
assigns the default (TTO:) as the console terminal.

option)

If COT is not running, this command starts COT and assigns
default (TTO:) as the console terminal without a log file.

C-3

the

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
Option
TTn:
Specifies the terminal to be assigned as the console terminal.
If COT is running, using the command with this
the console terminal.

option

reassigns

If COT is not running, the command starts COT and assigns
specified TTn:
as the console terminal without a log file.

the

In either case,
command.

this

you

cannot

designate

log

file

with

Description
>SgT /NOCOTERM
This command terminates the output of messages to the console
terminal. You can restart the logging of messages on the console
tarminal by using the appropriate SET command.

C.2.2

Commands that Control the Log File

The following commands control both the log file
which it is written.

and

the

device

>SET /LOGFILE[=ddnn:] [[UIC]] [filename.filetype]
>SET /NOLOGFILE
Description
>SET /LOG FI LE [ =ddnn:]

(The def a ult is SY:)

If COT is running, this command terminates output to the current
log file and opens a new log file on the specified device. The
new log file is one version higher than the version of the
current file.
If COT is not running, this command starts COT with the default
log file
(if you do not use a file specification) on the
specified device.
This command does not assign a console
terminal.
The device-unit specification is ddnn:.
Options
[uic]
Specifies the UIC to which the log file is written.
must be used.

C-4

The brackets

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
filename.filetype
Specifies the file name and file type of the new log file.
If COT is running,
the command with this option specified
terminates the current log file and opens a new log file with the
name and type you specify •

•

If COT is not running, the command with this option specified
starts COT with a log file of the specified name and type.
No console terminal is assigned.
Desicription
>SE'T /NOLOGF·r LE
This command terminates writing to the log file.
It does not
open a new log file.
To start writing to a new log file, use the
appropriate SET command.

C.2.3

Commands that Control Both the Console and the Log File

The following commands control both the console and the
which messages are sent.

log

file

>SET /COLOG=[TTn:] [ddnn:] [[uic]] [filename.filetype]
>SET /NOCOLOG
Des,cription
SET /COLOG
If COT is not running, this command (without options) starts COT
using
the
defaults
terminal,
device,
UIC,
and
file
specifications. You can use the options to specify the terminal,
device, UIC, and log file that you want to use.
If COT is running, this command (without options)
names of the log file and console terminal.

displays

the

If you enter any options with this command, while COT is running,
you will get an error message.
Options
TTn:
Specifies the console terminal.
If you do not specify TTn:,
sets the console terminal to TTO:.

COT

If COT is not running,
the command with only this option
specified starts COT, assigned to TTn:. The ddnn:, UIC, and
filename.filetype options take the default value if you do not
specify them.

C-5

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
ddnn:
Specifies the device to which COT writes the log file.
option to change the device.

Use

this

If COT is not running, using the command with only this option
specified starts COT using the default file specification of
[l,4]CONSOLE.LOG on the ddnn:
that you specified. Because only
this option is present, COLOG sends messages to TTO:
[uic]
Specifies the UIC to which COT writes the log file.
If you do
not specify a UIC with the device ddnn:
or filename.filetype,
COT uses the default value of [1,4]. The brackets must be used.
filename.filetype
Specifies the file name and file type for COT to use when writing
messages to the log file.
If you do not specify the file name
and file type, COT uses the default file specification of
CONSOLE.LOG.
Description
>SET /NOCOLOG
This command terminates COT. Before COT exits, it redirects CO:
to TTO:.
However, if it cannot redirect CO:
to TTO:, COT sets
CO:
offline and exits.

C.3

CONSOLE OUTPUT TERMINAL ERROR MESSAGES

The following section lists the error messages COT can return, along
with their causes and user response, where possible. Messages appear
at the last terminal that issued a COT command.
COT

CONSOLE TERMINAL ASSIGN ERROR
Explanation: An error occurred when COT attempted to assign a
new console terminal. The error may be the result of specifying
an incorrect terminal unit number.
User Action:

Reenter the command with a new terminal number.

COT -- UNABLE TO SPECIFY AST, COT EXITING
Explanation: COT was unable to specify an AST for receiving
commands from MCR. COT exits after displaying this message.

SET

User Action: The probable cause of this error is an attempt
run COT on a system that does not include AST support.

COT -- FILE OPEN ERROR, FCS nnn
Explanation: An error occurred when COT tried to open a log
file.
The FCS error code is nnn and is printed as part of the
message.
User Action: Correct the problem designated
number and restart the log file.

C-6

the

FCS

error

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
COT -- FILE WRITE ERROR, FCS nnn
Explanation: An error occurred when COT tried to write to an
existing log file.
The FCS error code is nnn and is printed as
part of the message.
User Action: Correct the problem designated by the FCS error
number.
If the problem caused output to the log file to be
stopped, res.tart output to a log file with the appropriate SET
command.
COT -- NOT LOGGING ON A TERMINAL OR TO A FILE, COT EXITING
Explanation: This message is displayed if a SET /NOCOTERM or SET
/NOLOGFILE command causes all message handling to be turned off.
User Action:
Because COT exits after printing
restart COT with the appropriate SET command.

this

message,

COT -- UNABLE TO REDIRECT CO: TO TTO:
to

TTO:

Explanation: An error occurred when COT tried to read from
This is an informational message only.

CO:.

Explanation: COT was unable to legally redirect CO:
when exiting.
COT sets CO:
offline when this occurs.
User Action:

None.

COT -- CO READ ERROR

User Action:

None.

COT -- SYNTAX ERROR
Explanation:
line.

COT detected a syntax error when parsing a

User Action:

Check the syntax and reenter the command.

command

COT -- DRIVER NOT LOADED, COT EXITING
Explanation:
The console driver
operate properly and exits.

was

not

loaded.

COT

cannot

User Action:
If console driver support and loadable driver
support were requested during system generation, the console
driver must be loaded.
COT can then be restarted with the
appropriate SET command.
COT -- MAX CONSECUTIVE READ ERRORS, COT EXITING
Explanation: An error occurred on 10 consecutive read operations
when COT was trying to read from CO:. The probable cause is a
system failure external to COT. COT exits after displaying this
message.
User Action:
Determine the problem that caused
read errors and correct it.
Then restart COT.

C-7

the

excessive

CONSOLE DRIVER AND CONSOLE OUTPUT TASK
COT -- MAX CONSECUTIVE WRITE ERRORS, DISABLING LOGFILE
Explanation1 An error occurred on five
consecutive
write
operations to the log file. COT attempts to close the log file
and disables logging to the log file.
User Action: Determine the problem that caused the write errors
and correct it. Then restart message logging to the log file.
SET -- INVALID KEYWORD
Explanation:

MCR received an illegal SET command.

User Action:

Check the command syntax and retry the command.

SET -- PRIVILEGED COMMAND
Explanation:
terminal.

COT can only be run or changed

User Action:
command.

from

privileged

and

reenter

the

Explanation: More parameters are specified on the
than are allowed for the command.

command

line

Check the command parameter syntax and reissue

the

SET -- MORE COMMAND PARAMETERS THAN PERMITTED

User Action:
command.

SET -- FILE SPECIFICATION EITHER INVALID OR NOT SPECIFIED
Explanation: An invalid RSX-llM file specification was found
the command file.
User
Action:
specification.

Reissue

the

command

with

valid

in
file

SET -- DEVICE NOT IN SYSTEM
Explanation: The device name specified in the command is
part of the current system.
User Action: Check the system device
command with the correct device name.

table

and

not

reissue

a
the

SET -- YOU DO NOT HAVE THE PRIVILEGE TO ISSUE THIS COMMAND
Explanation: The command you issued can be executed only from
privileged terminal.
User Action1
command.

Log on to a

privileged

account

and

reissue

a
the

C-8

APPENDIX D
THE QUEUE MANAGER

This appendix is directed to the system manager or operator who is
setting up and running the Queue Manager on an RSX-llM system.
Except
where noted, all commands described here are privileged.
Most large systems will include the Queue Manager for the convenience
of multistream line printer spooling.
If not, the Serial Despooler,
PRT ••• , can be installed instead.
Note that the Queue Manager
includes QMGPRT, which installs as PRT ••• , to intercept output from
the PIP /SP switch and other utilities and system tasks.
See the
RSX-11 Utilities Manual for more detail.
This choice is made at
SYSGEN.
This chapter consists of a narrative introduction and review of the
process of setting up the Queue Manager, detailed descriptions of all
commands to the Queue Manager, and a listing of an indirect command
file to be included in the system STARTUP procedure as a reference
example.

D. 1

NARRMrIVE INTRODUCTION AND REVIEW

Here is the procedure for bringing the Queue Manager into the system.
This can be done interactively,
but in most cases it is more
convenient to include it in an indirect command file invoked as part
of the system's STARTUP procedures.
NotE~

that this procedure must be adapted for each installation.
The
example is based on the procedure used for the RSX-llM development
system. QUE setup commands allow considerable flexibility in setting
up the Queue Manager system. Dynamic alteration of the Queue Manager
is also permitted.
I-Install the Queue Manager.
utility tasks.

It is found with the privileged

INS QMG/PRI=70
2-Install the output despooler task (print processor).
INS LPP/PRI=70

...

This task installs automatically as LPPO.
You must install this task
for each physical device under the direction of the Queue Manager.
This task "owns" the output device and must have a name based on the
name of the device.
Thus,
the output despooler for LPl:
must be
installed under the name LPPl, using the TASK= option. There can be
up to 15 output devices controlled by the Queue Manager.

D-1.

THE QUEUE MANAGER

3-Install PRT •••
INS QMGPRT
This task installs automatically as PRT ••• and is the interface to
PIP and other tasks that use PRINT$ or .PRINT. The Queue Manager can
then accept jobs from the PIP /SP switch. Although this task has the
same name as the Serial Despooler used on previous versions of RSX-llM
(and available on V3.2), it is not the same task.
It replaces this
task.)
4-Install the Print Command Line Interpreter and the Queue Command
Line Interpreter.
INS QMGCLI/TASK= ••• PRI
INS QMGCLI/TASK= ••• QUE
The same task parses both the PR! and QUE commands and therefore
be installed twice, once under each name.

must

5-Start the Queue Manager.
QUE /START:QMG
This command starts the Queue Manager and initializes the default
queue PRINT. It creates the queue file QUEUE.SYS on SY: (1,7] if it is
not there.
The command also clears all assignments previously
recorded.
If the queue file was intact, all queues will still contain
their jobs, but are not assigned to print processors.
(Processors
will have to be spooled again.)
5-Spool the processor.
QUE LP:/SPOOL/FLAG:l/FORM:O
This command creates a queue LPQO (if it does not already exist)
and
starts the previously installed despool task LPPO. This task attaches
device LPO:
for despooling.
Queue LPQO is assigned to despooler
LPPO.
Repeat this step for each output device under control of the
Queue Manager.
The /FORM switch establishes this attribute of the despooler.
This
means the despooler accepts jobs initiated by Print commands with the
same /FORM attribute given. Jobs with other /FORM attributes remain
in the queue until a despooler with the proper /FORM attribute is
available.
The /FLAG switch sets the default number of flag pages that precede
each job.
If users specify /FLag in their Print commands, each file
in the job will be preceded by this many file flag pages as well.
6-Assign the default queue to processors.
QUE LP:/ASSIGN:PRINT
This command assigns the default queue PRINT to processor LPPO.
Normally, only the PRINT queue has to be assigned. Device-specific
queues are assigned to their device despoolers by /SPOOL.
This
assignment of device-specific queues is a default, however, and not a
requirement. A device-specific queue must exist for every spooled
device, but these queues also can be assigned to other devices.

D-2

THE QUEUE MANAGER
You can assign a queue to more than one processor and you can assign
more than one queue to a processor. You can assign a device-specific
queue to another device if necessary.
For example,
if printer LPO:
is temporarily unavailable, you could assign LPQO to LPl:.

D.2

REFERENCE EXAMPLE

Here is a listing of SY: [l,2]QMGSTART.CMD from the RSX-llM development
system:
;

INS DBO:QMG/PRI=70
INS DSO:LPP/PRI=70
INS DSO:QMGPRT
INS DSO:QMGCLI/TASK= ••• PRI
INS DSO:QMGCLI/TASK= ••• QUE
QUE /START:QMG
QUE LP:/SPOOL/FLAG:l/FORM:O
QUE LP:/ASSIGN:PRINT

D.3

QUEUE MANAGER COMMAND DESCRIPTIONS

Setting up the Queue Manager is controlled through
privileged functions applied to the QUE command.

number

The format of the Queue Manager setup commands is:
>QUE ddnn:/function[:option[s]]

[/sw[s]]

Whe.re:

ddnn: is the device name.
/function is the function to be performed.
:option is the option for that function [may be more than one].
/sw is the switch for that option
These commands allow a privileged user to attach or detach devices for
spooling,
start and stop devices, assign the default queue to devices
and start and stop the Queue Manager.

D.3.1

STOP

This function suspends a device or stops the Queue Manager.
>QUE ddnn:

/STOp[:option]
EOF
EOJ

>QUE /STOp:QMG
ddnn:
The device name is required with all options except /STO:QMG.
You cannot include a device when stopping the Queue Manager.

D-3

THE QUEUE MAllAGER
option
If you do not enter an option
immediately. This is a pause.

(null

option)

the

device

stops

EOF
The device stops at the end of the current file.
EOJ
The device stops at the end of the current job.
/STO:QMG
The Queue Manager stops at the end of the current job.
All
assignments of queues to devices are broken (deassigned). All
despooler tasks are detached from their devices.
The Queue
Manager exits.
Examples:
>QUE LPO:/STOP
This example stops printing on LPO:. No jobs will be taken from
queues assigned to the device, but jobs can still be added to
queues.
>QUE LP2:/STO:EOJ
This example stops printing on LP2:
job.

at the

end

the

active

>QUE /STOP:QMG
This example stops the Queue Manager.
QMG is marked for stop and
the current jobs are allowed to finish.

D.3.2

START

This command starts printing on a previously stopped device or starts
the Queue Manager after a STOP. This command counteracts STOP.
>QUE ddnn:/STArt[:option]
NExt
TOP
PAge:n
BAck:n
FOrward:n

[/sw]
/FOrm:n
/FLag:n

>QUE /STArt:QMG

•

ddnn:
A device name is required with all options except /STA:QMG.
cannot include a device when starting the Queue Manager.

D-4

You

THE QUEUE MANAGER
option
Option and switch are mutually exclusive fields.
othero

Use one or

the

If you enter nothing (null option), the device
from the point at which printing stopped.
resumes printing after a pause.

starts printing
This, in effect,

NExt
Printing starts at the top of the next job.
TOP
Printing starts at the top of the current file.
PAgE!: n
Printing starts at page n of the current file.
BAck:n
Printing starts n pages back from

the

point

which

was

Printing starts n pages forward from the point at

which

was

stoppE~d.

FOrward:n
stoppE~d.

STA::QMG
This option is entered without ddnn:
as it starts the Queue
Manager and initializes the default queue PRINT.
It creates the
file SY: [l,7]QUEUE.SYS if it is not there.
The command also
clears all assignments previously recorded.
If the queue file
was intact, all queues still contain their
jobs,
but are not
assigned to processors.
(Processors will have to be spooled
again .. )
/sw
The switch and option fields are ~utually exclusive.
Use one
the other.
You can enter more than one switch, however.

/FOrm:n
This switch resets the forms type of the despooler task from
type set with SPOOL.

the

/FLag:n
This switch resets the default number of
SPOOL.
Print jobs have n job flag pages
users specify /FLA in their print command,
will also be preceded by n file flag pages
flag pages.
n can be O, 1,2, or 3.

flag pages set with
preceding the job.
If
each file in the
job
in addition to the job

If you are using special forms in your printer,
you should
n=O so that no flag pages are printed on your special forms.

D-5

set

THE QUEUE MANAGER
Examples:
>QUE LPO:/STA
Start LPO:;

printing proceeds from where it was stopped.

>QUE LP2:/START:NE
Start printing with the next job queued to LP2:.
>QUE LP:/STA/FO:ll
Start printing on LPO:

with FORMS attribute reset to 11.

Notes:
Page-related options have no effect unless the user
LEngth:n quantity in the Print command.

specified

If restarting a processor to handle special forms types, you may
want to set FL to 0 to avoid printing banner pages on your
special forms.

D.3.3

SPOOL

This function attaches a device for despooling.
The command starts a
despool task, optionally creates a queue named after it, and assigns
the queue to the despool task.
>QUE ddnn:/SPool/sw
SPOOL creates queue ddQn (if it -does not already exist)
and
starts the despool task ddPn which must be installed previously
for device ddn. This attaches device ddnn:
for despooling by
the despool task ddPn open to jobs from queue ddQn.
/sw
More than one switch can be used with this function.
/FOrm:n
Sets the device despooler to accept jobs with forms type n.
You can set a despooler to accept more than one forms
the forms definition nust be duplicated.

type,

but

This number can be anything from 0 to 255.
These numbers are to
commands.

specified

your

The default is O.
users

their

If the right forms are not in an available printer,
then their
jobs
will be waiting until the printer has been stopped, the proper forms
put in place, and the printer restarted using the /FORMS:
qualifier
and the proper value for n in the START/ command.
Forms differ by their length and width.
forms table.

D-6

Both values can be set in the

THE QUEUE MANAGER

Setting width is simply a matter of how many columns are needed to
fill
in the form.
There are no standard widths for forms, but 80.
and 132. are the most common.
Setting length requires you to determine whether your forms are
standard length.

"Standard length" is any form length that can be set on your printing
hardware.
If t~e hardware can handle the form by setting a response
to a form-feed character <FF>, then it is a standard length form,
and
the form-feed is a "real~, i.e., hardware, form-feed.
If the form length cannot be set on the hardware,
then it is a
non-standard length.
In this case,
the form-feed <FF> must be
replaced by an appropriate number of line-feeds <LF>. This is called
a "simulated", i.e., software, form-feed.
You should determine which forms are used on your system and assign
each a number.
This number points to a table of form definitions.
The form definitions consist of a single 16-bit word. The length is
the low-order byte and the width is the high-order byte. The high bit
of the length byte is set when simulated forms
(forms whose length
cannot be set on your hardware) are needed. This form definition word
can be changed by editing the Task Builder command file for the
despooler task.
You must add a global patch statement of the
following form:
TKB>GBLPAT=INIT:FRMTBL+k:value
where k is the assigned form number multiplied by 2 (n*2) and value is
the form definition word (value= width+ <200*SIMFF> + <width*400>).
The following table shows the forms requirements for a hypothetical
installation.
The form names describe different uses that special
forms might be put to, but have no significance otherwise.
!~

Aiccordion
Paychecks
Invoices
Stationery
M~:>on Diary
Star Log

ASSIGNED n
0
1
2
3
4
5

WIDTH

LENGTH

SIMFF

132
40
80
80
22
112

66
10
66
66
43
113

N
N
N
N
y
y

(As shipped, FORMS:O is 66 lines long by 132 columns with real
form-feeds.
FORMS:l is 1 line long by 132 columns with simulated
form-feeds;
FORMS:2 is 2 lines long by 132 columns with simulated
form-feeds;
and so on through FORMS:66 which is 66 lines long by
132 columns with simulated form-feeds.
The remaining FORMS:n
entries are set to 1 line long by 132 columns with simulated
form-feeds.
Thus,
if you specify FORMS:43, when the printer
encounters a form feed, it counts the number of lines on the page
and subtracts that number from 43. The printer then reels off a
number of line feeds equal to the difference. You may find this
arrangement satisfactory if your installation rarely uses forms
other than standard line-printer paper, but if you have more than
one standard form, you will probably want to make the changes in the
forms table entries.
)
/FLag:n
Sets the number of flag pages to precede all jobs printed on the
device.
Note that if you are using special forms, you may want to

D-7

THE QUEUE MANAGER
set this att~ibute to 0 to avoid printing banner pages on your
special forms.
This also sets the number of file flag pages to be
printed when users specify the FLAGS switch in their Print commands.
Examples:
>QUE LPO:/SPOOL
Attach LPO:

for despooling.

>QUE LP3:/SP/F0:2
Attach LP3:

D.3.4

for despooling with forms set to 2.

UNSPOOL

This function removes a device from despooling.
The device no
longer is assigned to queue.
The despooler task exits. The
associated device-specific queue is not deleted.
>QUE ddnn:/UNSPool
UNSPOOL frees a device used in despooling for general use.
The
despool task for the device exits but its entries in queues assigned
to it remain in the queue file.
Example:
>QUE LPO:/UNSP
This example removes the device LPO:
despooler LPPO and the Queue Manager.

D.3.5

from

active

use

the

ASSIGN

This function creates a path between a queue and a despooler.
>QUE ddnn:/ASsign:queuename
ASSIGN is normally used to assign the default queue PRINT to one or
more despooler tasks, but you can assign any queue to any despooler.
Example:
>QUE LPO:/AS:PRINT
Assign PRINT queue to LPO:.
Notes:
Remember that SPOOL automatically assigns
queue
to
its
related
device.
For
automatically assigned to LPl:.

D-8

a device-specific
example,
LPQl is

THE QUEUE MANAGER
D.3.6
'--".

DEASSIGN

Thi:s function breaks the assignment of a queue to a despooler.
>QUE ddnn:/DEAssign:queuename
DEASSIGN eliminates the path between a queue and a despooler,
but
the queue still exists with all its jobs. Jobs can be added to the
queue, but none will be dequeued while the queue is not assigned.

·~·

D-9

~
I

APPENDIX E
THE RSX-llM I/O EXERCISER

..
E.l

INTRODUCTION

The RSX-llM I/O Exerciser (IOX) is a software tool that you can use to
diagnose hardware and software I/O problems. !OX is intended for use
by system managers, system operators, and system programmers who want
to test units in a hardware configuration to determine whether these
units are correctly executing I/O operations. In addition, !OX allows
you to measure system activity.
!OX provides a command language for executing test functions.
!OX
output consists of detailed error reporting and general information
describing system activity.
You should be familiar with information in the following
to effectively use !OX:
•

RSX-llM/M-PLUS Error Logging Reference Manual

RSX-llM/M-PLUS MCR Operations Manual

•

RSX-11 Utilities Manual

publications

What IOX Does

E.l~l

The I/O Exerciser (!OX) tests the I/O units in your
ensure that they correctly execute I/O functions.

configuration

!OX exercises I/O units on your system by writing a data pattern to a
volume on a unit and reading the data that was written. !OX then
checks to ensure that the pattern read matches the pattern written. A
mismatch between the written pattern and the pattern being read
indicates an error. !OX reports errors when they are encountered.
!OX also displays activity reports at specifed intervals and at the
completion of an I/O exercise.

.,,

!OX has a command language that you can use
functions. !OX provides commands to:
•

Set up units in a test configuration

•

Select specific units to be tested

•

Set I/O exercise execution conditions

E-1

direct

I/O

exercise

THE RSX-llM I/O EXERCISER
•

Control I/O exercise execution

•

Direct command
exercise

•

Measure system activity using the !OX idle loop

lines

RSX-llM

for

execution

during

Section E.2 summarizes, in alphabetical order, the IOX commands.
For
complete command descriptions, including formats and usage rules see
Section E.10.

E.1.2

Setting Execution Conditions

!OX execution-time parameters allow you to set conditions under which
an I/O exercise executes.
You set these parameters using commands to:
Specify the number
• deselecting
a unit

I/O

errors

!OX

before

tolerates

• Set the length of time between interval summary reports
• Direct summary reports to the log file !OX.LOG

~
:1

•

Specify the size of the temporary file
IOX uses when
exercises a unit containing a Files-11-formatted volume

•

Specify the size of the buffer !OX uses when
units containing non-file-structured volumes

For more information on how to use the !OX execution-time
see Sections E.3.4 and E.5.

E.1.3

exercises
parameters,

Controlling the I/O Exercise

!OX commands allow you to control execution of an I/O exercise.
execution control commands you can:
•

Interrupt execution of an I/O exercise to enter
interactively

•

Abort execution of an I/O exercise or a task

•

Deselect units from the test configuration

•

Display current execution
summary information

•

Modify execution parameters

•

Restart IOX

status,

E-2

parameter

!OX

Using

commands

settings,

and

THE RSX-llM I/O EXERCISER
E.1~4

Devices Supported by IOX

The following is a list of devices supported for IOX:
Abbreviation
DB:
DD:
DF:
DK:
DL:
DM:
DP:
DR:
DS:
DX:
DY:
CT:
DT:
MM:
MS:
MT:

RP04/:RP05/RP06
TU58
RFll
RKOS/:RKOSF
RL01/RL02
RK06/:RK07
RP02/:RPR02/RP03
RM02/03
RS03/RS04
RXOl
RX02
TU60
TU56
TU16/TE16/TU45/TU77
TS04
TU10/TE10/TS03

E.2

SUMMARY OF IOX COMMANDS

Table E-1 is an alphabetical list of IOX commands with
the functions each provides.

summary

Table E-1
Summary of IOX Commands
Command

Description

ABORT

Terminates execution of
normal completion

ABORT taskname

Terminates execution of a task
EXECUTE command

ABORT /A.LL

Terminates execution of all tasks initiated by the
EXECUTE command

BADBLOCKS

Enters the numbers of bad blocks in the IOX bad
block list; displays the blocks in the bad block
list

BUFFERSIZE

Sets the default size of the buffer IOX uses to
write and read when exercising a unit with a
non-file-structured volume

CONFIGURE

Adds a unit to your test configuration;
the units in your test configuration

displays

CONTROL C

Enables or disables the interruption of
exercise to enter a command interactively

I/O

exercise
initiated

before
by

the

IOX

(continued on next page)

E-3

THE RSX-llM I/O EXERCISER
Table E-1 (Cont.)
Summary of !OX Commands
Command

Description

DENSITY

Sets the tape density for magnetic tape testing;
displays
the current or default density and
characteristics word

DESELECT

Terminates testing on a unit

ERRORLIMIT

Sets the number of
deselects a unit

EXECUTE

Directs a command line to the operating system for
execution

EXIT

Exits from !OX to the operating system monitor

FILESll

Selects a unit with a Files-11 volume mounted;
directs !OX to protect the volume data structure
during an I/O exercise

HELP

Displays a summary description of !OX commands
your terminal

INTERLEAVE

Sets the block interleave factor for disk testing

ITERATIONS

Sets the number of times through the !OX idle loop
for the idle loop iteration count

LOGFILE

Directs activity reports and error reports
either your terminal or the log file !OX.LOG

PARAMETERL !ST

Displays the current settings for !OX parameters

PATTERN

Sets the test pattern !OX writes and reads
testing; display all test patterns

during

PRINTSUMMARY

Displays a summary report of !OX activity at
terminal

your

PROCEED

Resumes !OX test execution after it has
interrupted by CTRL/C in interactive mode

been

RANDOM

Enables or disables testing of random blocks
rather than sequential blocks during testing

REPORTERRORS

Enables or disables error reports directed to your
terminal

RESTART

Reinitializes !OX:
stops testing,
deconfigures
all units except default units,
deselects all
units, and resets all parameters to their default
values

RETRIES

Enables or disables retries of I/O
I/O drivers detecting I/O errors

RUNTIME

Sets the length of time !OX is to test units

errors

tolerated

before

!OX

operations

(continued on next page)

E-4

THE RSX-llM I/O EXERCISER
Table E-1 {Cont.)
Summary of IOX Commands
Cc•mmand

Description

SE:LECT

Selects a·unit with a
for an I/O exercise

SPY

Displays execution-time information for a specific
unit or for all selected units

S'I'ART

Begins an I/O exercise on selected units
configuration

SlJIMMARYTIME

Sets the time interval
reports

summary

TE:MPORARYFI LE

Sets the size of the temporary file
IOX uses
exercise units with Files-11 volumes mounted

VE:RIFY

Ensures that data can be read from a unit

VOLUMECHECK

Checks to determine whether a unit
has a Files-11 volume mounted

non-file-structured

between

interval

Specifies the algorithm IOX executes in
loop
WFtITECHECK

E. 3

INSTAJ~LING,

volume

its

your

tested
idle

Enables or disables write checks to disks

INVOKING, AND RUNNING IOX IN AN EXERCISE EXAMPLE

This section uses an example of a terminal session to show you how to
install and invoke IOX, set up your test configuration, set up
execution-time parameters, select units you want to exercise,
and
start the I/O exercise on those units.

E.3~1

Installing IOX

If IOX is not installed on your system, install IOX by using
command:

the

MCR

INS1~ALL

>INS !?IOX/INC=nn
where:
nn is l.2K words per device to be tested.
If your Executive was built with the Extend Task directive included in
it, you need not specify the INC keyword.
The Task Builder command file for IOX built IOX as a nonprivileged
task that is checkpointable and that runs at a priority of 50(10) in
the GEN partition.

E-5

THE RSX-llM I/O EXERCISER
E.3.2

Invoking IOX

If IOX is installed on your system, invoke it with the command:
>IOX
IOX responds by prompting you with
operating system:

the

task

name

assigned

the

IOX>
When you receive this prompt, you can enter !OX commands.
If IOX is not installed on your system, you can invoke it with the ·MCR
RUN command:
>RUN $IOX/INC=nn
where:
nn is l.2K bytes per device to be tested.
If your Executive was built with the Extend Task directive included in
it, you need not specify the INC keyword.
In this case, !OX names the task using your
prompts you using this task name.
For example:

terminal

number

and

TT36>
When you receive this prompt you can enter !OX commands.

E.3.3

Setting Up Your Test Configuration

All units have unit number 0 included in the IOX test configuration by
default.
You must explicitly configure any other units you want to
exercise.
For example:
IOX>CONFIGURE DKl:
IOX>CONFIGURE DK2:
IOX>CONFIGURE MMS:

E.3.4

Setting Up Execution-Time Parameters

You can set conditions that affect the execution of the I/O exercise.
For example,
you can specify the length of exercise execution time,
how often you want a report of exerciser activity,
and whether you
want the activity reports directed to the log file SYO:IOX.LOG. You
can also request IOX to determine whether the units being tested have
Files-11 volumes mounted.
The following commands are an example of how to set up
parameters for an I/O exercise:

execution-time

IOX>RUNTIME 10
IOX>SUMMARYTIME 4
IOX>LOGFILE YES
These commands direct IOX to execute the I/O exercise for 10 minutes,
generate an interval report every four minutes, and direct all reports
to the log file.
E-6

-.,

THE RSX-llM I/O EXERCISER
E.3.5

Selecting Units for an I/O Exercise

Once you have set up your test configuration, you can select units to
be tested.
Only units you explicitly select are exercised For
example:
IOX>Ei'ILESll DKl:
This command selects unit DKl:
for exercising.
When IOX executes,
only DKl:
is exercised. You can use either the SELECT command or the
FILESll command to select a unit for exercising. The FILESll command
is used in this example because it protects the file structure on a
Files-11 volume during an I/O exercise.

E.3.6

Starting an IOX Exercise Execution

After setting up your configuration and selecting the units you
exercised, begin the I/O exercise by entering the START command:

want

IOX>START
IOX then performs pattern checking on DKl:
for the length of time you
specified with the RUNTIME command (10 minutes). "When IOX completes
execution, it generates a summary report and the interval reports, and
directs them to the log file !OX.LOG. You can gain access to and
examine the log file after you exit from IOX by entering the command:
>PIP TI:=IOX.LOG
This command directs the PIP utility
terminal.

E.3.7

display

the

file

your

Exiting from IOX

You can exit from IOX and return control
monitor by using the EXIT command:

the

operating

system

IOX>gxrT

E.4

IOX OPERATIONAL MODES

IOX operates in three modes:
command,
Operational modes are controlled by
return on your terminal keyboard.

execution, and interactive.
means of CTRL/C and carriage

In most cases, CTRL/C causes RSX-llM to interrupt a
task and give
control to MCR, the keyboard monitor. You then receive the MCR prompt
(>) at your terminal.
However, by entering the CONTROL C command,
IOX allows you to use
CTRL/C in an alternate way:
you can use CTRL/C to interrupt an !OX
I/O exercise and give control to IOX rather than to MCR.
This section describes the operational modes and how to
CONTROL C command to control them.

E-7

use

the

IOX

THE RSX-llM I/O EXERCISER
E.4.1

Command Mode

When you invoke !OX by entering the command line described in Section
E.3.2, "Invoking IOX," !OX is in command mode waiting for you to enter
a command. When you press carriage return in command mode,
!OX
prompts you:
IOX>

)

When you enter CTRL/C in command mode, RSX-llM issues the
and the normal rules for ente~ing commands to MCR apply.

MCR

prompt

In command mode, you can use the CONTROL C command to enable or
disable
interruptions to an I/O exercise.
CONTROL C YES enables
interruptions,
allowing you
to
enter
commands
Interactively;
CONTROL C NO disables interruptions to an I/O exercise.

E.4.2

Execution Mode

When you begin an I/O exercise (by means of the
enters execution mode.

START

command),

!OX

If you have enabled interruptions to the I/O exercise by means of
CONTROL C YES, IOX will not accept any input from your terminal except
CTRL/C.- If you try to enter any other input, IOX responds with the
message:
Iox

ONLY

Ac ALLOWED

If you have disabled interruptions to the I/O exercise by means of
CONTROL_C NO, CTRL/C causes RSX-llM to issue the MCR prompt and
execution of the I/O exercise continues.
In this case,
execution of
the I/O exercise cannot be interrupted.

E.4.3

Interactive Mode

When CONTROL C YES is set, you can interrupt an I/O exercise to enter
commands interactively. When you enter CTRL/C, !OX prompts you:
IOX>
When you receive this prompt, you can enter any IOX command except the
following:
BUFFERSIZE
PATTERN (PATTERN with no arguments is permitted)
RUNTIME
RESTART
START
These five commands must be entered in command mode.
CTRL/C places IOX in interactive mode until you enter PROCEED.
In
interactive mode,
the I/O exercise continues to execute, but error
reports and activity reports directed to your terminal (if LOGFILE NO
is set)
are suspended until you enter PROCEED.
If you set LOGFILE
YES, error reports and activity reports are generated normally.

E-8

THE RSX-llM I/O EXERCISER
CTRL/C halts the IOX clock so that even though the I/O exercise is
continuing, it is not being timed by the IOX clock.
tonsequently, the
exeircise may run longer than you specify in the RUNTIME command.

E.S

•

SETTING EXECUTION-TIME PARAMETERS

Many IOX commands set IOX execution-time conditions, such as how long
The
IOX executes,
time between summary reports,
and so forth.
PARAMETERL~ST command displays all execution-time parameters
and the
value of their current setting.
For example:
IOX>PARAMETERLIST
CONTROL C=YES
LOGFILE; NO
RANDOM= YES
REPORTERRORS= YES
RETRIES= NO
VOLUMECHECK= YES
WAIT= YES
WRITECHECK= NO

BUFFERSIZE= 1024.
ERRORLIMIT= 10.
INTERLEAVE= 4.
ITERATIONS= 10.
PATTERN= 4.
RUNTIME= S.
SUMMARYTIME= 1.
TEMPORARYFILE= 500.

DYNAMIC MEMORY USAGE= 3278.:2248.:2248.:1.
There are five categories of execution-time
parameters are controlled by commands that:

These

parameters.

•

Set general execution-time conditions

•

Set execution-time conditions for units with Files-11 volumes

•

Set
execution-time
conditions
non-file-structured volumes

•

Set execution-time conditions for measuring system activity

•

Direct the operating system to execute non-IOX tasks

The following
categories.

E.5.1

sections

describe

the

commands

with

units

for

each

these

Setting General Execution-Time Conditions

General execution-time commands affect the execution of all
I/O
exercises. You are likely to want to set these commands each time you
run IOX;
therefore, you may want to put them in an indirect file.
LOGFILE

Allows you to direct IOX activity
file, !OX.LOG

RUNTIME

Allows you to set the length of time an
is to execute

SUMMARYTIME

Sets the
reports

ERRORLIMI'I'

Sets the number of I/O errors IOX tolerates before
deselects a unit from the test configuration

REPORTERRORS

Enables or disables error reporting

time

interval

E-9

between

reports

log

I/O

exercise

interval

summary
it

THE RSX-llM I/O EXERCISER
CONTROL C

Enables or disables interruptions to an I/O exercise

PATTERN

Sets the test pattern
exercising a unit

E.5.2

IOX

writes

and

reads

when

Setting Execution Conditions for Units with Files-11 Volumes

To set execution conditions for units with Files-11 volumes.
Use the
FILES-11 and TEMPORARYFILE commands. The FILESll command selects a
unit to be exercised;
the TEMPORARYFILE command specifies the default
size of temporary file IOX uses when it exercises the unit.
You can
override this default with the FILESll command.
Files-11 volumes are volumes formatted for use by the RSX-llM file
system, Files-11.
These volumes have data structures such as home
blocks, directories, and boot blocks on them.
The FILESll command
selects a unit with a Files-11 volume and allows you to exercise the
unit without destroying the data structures or files on the volume.
IOX uses a temporary file when it exercises a unit with a Files-11
volume.
IOX creates the temporary file on the volume to be tested and
marks the file for deletion.
IOX then selects a random block in the
temporary file to exercise. Because the temporary file is marked for
deletion, it is erased from the disk's file structure when the
exercise completes or IOX terminates.

E.5.3

Setting Execution Conditions for Non-File-Structured Volumes

To exercise units with non-file-structured volumes,
use the SELECT
command.
The SELECT command does not check for any of the Files-11
data structures;
it exercises the entire volume, destroying all data
on the volume.
Use the VOLUMECHECK command
(VOLUMECHECK YES)
to ensure that the
on the unit you select does not contain any Files-11 data
structures. VOLUMECHECK directs IOX to warn you if it finds such
structures on what you think is a non-file-structured volume.
volum~

You may set four execution conditions when you exercise units with
nonfile-structured volumes:
the default buffer size, the pattern
checking method, the bad block locations, and whether IOX performs
certain I/O operations during the exercise.

E.5.3.1 Setting the Default Buffer Size - Use the BUFFERSIZE command
to change the default size for
the buffer IOX uses when it does
pattern checking. When you invoke IOX, the default buffer size is
1024. You can override any default you set when you enter SELECT with
another buffer size.

E.5.3.2 Choosing a Pattern-Checking Method - IOX can exercise a unit
by writing to and reading from either random blocks or sequential
blocks on a volume.
You can control the pattern-checking method with
the RANDOM and INTERLEAVE commands.
If you specify RANDOM YES, IOX exercises randomly selected
the volume.

E-10

blocks

THE RSX-llM I/O EXERCISER
If you specify RANDOM NO,
IOX exercises sequential blocks on the
volume, beginning with block O.
IOX adds the interleave factor to the
location of the last block exercised and uses the result of the
addition to determine the next block to exercise.
For example:
RANDOM NO
INTERLEAVE 1000.
These commands direct IOX to begin at block
checks on blocks O, 1000, 2000, and 3000.

and

perform

pattern

E.5.3.3 Entering Bad Block Locations - Use the BAD BLOCKS command to
enter the locations of known bad blocks (that is, bad blocks located
by the RSX-llM BAD utility) on a volume.
IOX maintains a list of bad
blocks and ignores them during an I/O exercise.
!OX allows you to
enter the locations of bad blocks manually;
you must know where such
blocks are on the disk to use this command effectively.
See the
description of the BAD BLOCKS command in Section E.10 for
information
on how to enter the locations of bad blocks.

E.5.3.4 Controlling I/O Operations During the I/O Exercise - Use the
RETRIES and WRITECHECK commands to disable certain I/O operations
during an I/O exercise. RETRIES NO directs an I/O driver to not retry
an I/O operation when it receives an error. WRITECHECK NO directs an
I/O driver to not perform write checks on WRITE I/O operations.

E.5.4

Setting Execution Conditions for Measuring System Activity

IOX provides two commands for measuring
ITERATIONS.

system

activity:

WAIT

and

IOX executes an idle loop while it waits for units to complete I/O
operations.
It can execute either one of the following in this loop:
1.

The wait-for-event-flag algorithm

The instruction

.......,.

BICB -(SP), (SP)+
The BICB instruction takes a large amount of CPU time and can be
to measure I/O throughout.
The wait-for-event-flag algorithm is the default, but you can
it and execute the BICB instruction by entering the command:

used

disable

WAIT NO
You can determine the exact execution speed of the BICB instruction on
your processor by referring to the appropriate PDP-11 Processor
Handbook.
Using this information, along with the number of times !OX
executes the instruction,
as set by the ITERATIONS command, you can
estimate the level of system I/O throughput.
See the ITERATIONS command description in Section E.10.

E-11

THE RSX-llM I/O EXERCISER
E.5.4.1 The IOX Idle Loop Algorithm - The following code is provided
for you to measure the instruction times in the IOX idle loop. This
listing is the actual code in the IOX idle loop.
BCKGND: : TST
BMI
1$:
TST
BEQ
CLR
CALL
CALL
BR
5$:
TST
BMI
10$:
MOV
15$:
CALL
TST
BEQ
WTSE$S
·.EF$S
;T
BMI
TST
BNE
BR
20$:
BICB
25$:
DEC
BGT
ADD
ADC
ADC
BR

E.5.5

STOPFG
30$
ASTCFG
5$
ASTCFG
$DEQUE
CMDAST
BCKGND
RUNFLG
40$
$ITCNT,CNTI
$DEQUE
$WAIT
20$
#WAIEFN
#WAIEFN
STOPFG
30$
TTACTV
1$
25$
-(SP), (SP)+
CNTI
15$
#1,CNTA
CNTB
CNTC
BCKGND

;TIME FOR INTERVAL REPORT?
;IF MI YES
;STAY IN INTERACTIVE MODE?
;IF EQ NO
;YES, ASSUME WE WILL LEAVE IT
;DEQUEUE ALL PENDING DESELECTS
;CALL INTERACTIVE COMMAND INTERPRETER
; LOOP AGAIN
; ARE WE RUNNING?
;IF MI NO, ABORT
;SETUP ITERATION COUNT
;DEQUEUE ANY PENDING DESELECTS
;USE "WTSE$S" INSTRUCTION?
;IF EQ NO
;WAIT FOR IOX TO DO SOMETHING
;NOW CLEAR THE EVENT FLAG
;TIME FOR INTERVAL REPORT?
;IF MI YES
;"C ACTIVE?
;IF NE YES
;GO COUNT ITERATIONS
;WAIT
; ALL FINISHED?
; IF GT NO
;UPDATE IDLE LOOP COUNT
;RIPPLE CARRY

; LOOP AGAIN

Directing the Operating System to Execute Non-IOX Tasks

Use the EXECUTE command to direct commands to the operating system for
execution.
These tasks execute concurrently with an I/O exercise.
For example:
EXECUTE ••• BAD DKl:/LI
This command specifies that you want the operating system
the BAD utility.

execute

You can use the PARAMETERLIST command to display the status of tasks
you initiate using EXECUTE. See Section E.7, "Displaying I/O Status
Information," for details on these status reports.
You can use the
ABORT command to terminate one (ABORT taskname) or all (ABORT /ALL)
tasks initiated by EXECUTE.

E.6

I/O EXERCISE OUTPUT

IOX generates two types of output:
activity reports and error
reports.
Activity
reports
are
summaries
of IOX processing
information, such as how long an I/O exercise has run and how much
time remains for the I/O exercise to complete. Error reports show
such information as the block where an I/O error was encountered.

E-12

THE RSX-llM 'I/O EXERCISER
Activity Reports

E.6.1
~·

There are three types of activity reports:
•

Summary report -- an activity report summarizing IOX
for the entire I/O exercise

activity

•

Interval report -- an activity report summarizing IOX activity
in the time intervals set by the SUMMARYTIME command

•

Print summary -- a
report
displayed
at
your
terminal
summarizing the IOX activiiy in the interval between the last
summary report and the time you entered the PRINTSUMMARY
command.

Using the LOGFILE command, you can direct IOX to display summary
reports,
interval reports, and error reports at your terminal or you
can direct them to the log file IOX.LOG. The following lines show the
general format of IOX activity reports.
18-SEP-78
15:44:42 ******** EXERCISER STARTED ********
TIME -- RUN:
1 MIN.
ELAPSED:
1 MIN. REMAINING:
0 MIN.
DKO: -- 1,183. REQUESTS TOTALING 1,183. BLOCKS WITH NO ERRORS
IDLE-LOOP COUNT:
724. ITERATIONS
18-SEP-78

15:45:56 ******** EXERCISER TERMINATED ********

As shown above, the output of activity reports consists of lines
telling when exerciser events occured and lines containing status
information.
The exerciser event lines tell you when the exerciser began execution,
terminated execution, aborted execution,
started a log file, and
terminated entries to the log file.
The following line is an example
of a line describing an exerciser event:
18-SEP-78

15:45:56 ******** EXERCISER STARTED ********

There are five types of status information lines:
•

General user information:

date and time of report

•

Timing information:
time between reports,
total execution
time (to the nearest minute), and remaining execution time

•

Unit information:
number of I/O requests to the unit,
number
of blocks exercised, and number of errors encountered on the
unit

•

Idle loop information:
loop

•

Error reports:

number of iterations through the

idle

see Section E.6.2

Both summary reports and interval reports can be directed to either
your terminal or the log file by means of the LOGFILE command.
LOGFILE YES specifies that the summary information is directed to the
log file;
LOGFILE NO specifies that the summary information is
displayed at your terminal.
LOGFILE NO is the default.

''-'

To generate a print summary,
use the PRINTSUMMARY command.
This
report cannot be directed to the log file.
The print summary shows
the amount of IOX exercise activity in the interval between the last
interval report and the time you entered the PRINTSUMMARY command.

E-13

THE RSX-llM I/O EXERCISER
E.6.2

Error Reports

The following lines show the form of an IOX error report. At the same
time IOX is reporting this information, if error logging is enabled,
.the RSX-llM error logging program is also logging the error.
For
information on how the error logger handles the errors, refer to the
~SX-llM/M-PLUS Error Logging Reference Manual.
DKl:
UNRECOVERABLE ERROR AT BLOCK 358 (DECIMAL) 546 (OCTAL)
DKl: -- DATA ERROR ~T BLOCK 358 (DECIMAL) 546 (OCTAL)
GOOD DATA: 165555
BAD DATA:
167155 (OCTAL)
WORD POSITION:
308 (DECIMAL) 464 (OCTAL)
The error report comprises up to three lines. The first line tells
you the block number
(in decimal and octal) where the error was
encountered. The second line tells "good data" and "bad data." The
third line indicates the position of the word within the block (in
decimal and octal) where the error was encountered.
Only the first
error encountered in the block is reported.

E.7

DISPLAYING !OX STATUS INFORMATION

IOX provides four commands for displaying status information:
•

PARAMETERLIST - displays parameter settings

•

SPY - displays the status of a unit being tested

•

CONFIGURE - displays all devices in your configuration

•

PATTERN - displays all 11 IOX patterns

E.7.1

Displaying Parameter Settings

The PARAMETERLIST command displays the settings of IOX exercise
parameters at the time you enter the command. The following lines
show format of a PARAMETERLIST display.
TASK

STATUS

COMMAND LINE

••• BAD

QUEUED

DKO:/LI

------

DEVICE

LUN

BUFSIZE

TYPE

FILESIZE

DBl:
DB2:
MMl:

5.
6.
7.

512.
512.
1024.

Fll
Fll

500.
500.

------

BUFFERSIZE= 1024.
ERRORLIMIT= 10.
INTERLEAVE= 4.
ITERATIONS= 10.
PATTERN= 4.
RUNTIME= 5.
SUMMARYTIME= 1.
TEMPORARYFILE= 500.

NFS
CONTROL C= YES
LOGFILE;; NO
RANDOM= YES
REPORTERRORS= YES
RETRIES= NO
VOLUMECHECK= YES
WAIT= YES
WRITECHECK= NO

DYNAMIC MEMORY USAGE= 3278.:2248.:2248.:1.

E-14

•

THE RSX-llM I/O EXERCISER
For tasks initiated by the EXECUTE command, the PARAMETERLIST
displays:

command

•

The installed task name

( ••• BAD)

•

The execution status (QUEUED, ACTIVE, SUCCESS, WARNING, ERROR,
SV ERROR)

•

The command line elements you entered (DKO:/LI)

ACTIVE indicates that IOX is being executed.
The remaining status
indications
relate
to the Exit with Status
(EXST$)
Executive
directive.
For more information on these status indications, refer to
the RSX-llM/M-PLUS Executive Reference Manual.
For selected units, PARAMETERLIST displays the following information:
•

Device specifications (DBl:, DB2:, and MMl:)

•

Logical Unit Number (LUN)

•

Buffer size IOX uses for reads and writes (512(10)
for
with
Files-11
volumes;
1024(10)
for
units
non-file-structured volumes)

•

Type of volume mounted on unit (Fll for Files-11;
NFS for
non-file-structured volumes;
VFY for units being verified)

•

File size of the temporary file IOX uses for processing
with Files-11 volumes mounted

(5, 6, and 7)
units
with

units

The line describing dynamic memory usage is in the form:
totalmemory:freeblock:freebytes:fragments
totalmemory
Indicates the size of IOX dynamic memory in bytes.
f reeblock
Indicates the size of the
memory in bytes.

largest

free

block

IOX

dynamic

bytE~S

Indicates total free bytes available in IOX dynamic memory.
f raqments
Indicates the number of memory fragments in IOX dynamic memory.

E.7.2

Displaying Unit Status

The SPY command displays the status of the unit or units you are
exei~cising.
The following line is an example of a SPY command display
1 i nE~:
DBO:

-- TYPE=Fll

VBN=305.

I/O=AST QUEUED

FUNCTION=WRITE

This line indicates:
•

The unit being exercised (DBO:)

•

The current virtual block being exercised (305(10))

E-15

THE RSX-llM I/O EXERCISER
•

The type of volume mounted on the unit (Files-11)

I/O request status:

•

The type of I/O function being performed (write)

E.7.3

AST QUEUED, IN PROGRESS, or IDLE

Displaying the Units in Your Configuration

The CONFIGURE command displays all
system's configuration.

devices

that

are

part

your

For example:
IOX>CONFIGURE
This command produces the following display:
DBO ODO DFO DKO DLO OMO DPO ORO DSO DXO
DYO CTO OTO MFO MMO MSO MTO

E.7.4

Displaying the Pattern Setting

The PATTERN command displays all 11 possible patterns that IOX
and reads during testing.

writes

For example:
IOX>PATTERN
This command produces the following display:
1
2

3
4
5
6
7

8
9
10
11

000000,000000
177777,1 77777
125252,052525
165555,133333*
163126,163126
055555,155555
022222,122222
111111,111111
007417,007417
021042,021042
104210,104210

The asterisk indicates the default pattern that the system builds into
!OX.

E.8

STARTING AND CONTROLLING IOX EXECUTION

The START command begins execution of an I/O exercise on units
selected by the FILESll command and the SELECT command. Section E.3.6
describes how to use the START command.
The CONTROL C command enables or disables the use of CTRL/C to
interrupt an I/O exercise (see Section E.4). CONTROL C YES enables
interruptions to an I/O exercise;
CONTROL C NO disables-interruptions
to an I/O exercise.

E-16

THE RSX-llM I/O EXERCISER
E.8.1

Disabling Interruptions to an I/O Exercise

When you set CONTROL C NO the I/O exercise cannot be
interrupted.
That
is,
when you- enter CTRL/C, MCR prompts you and the rules for
entering commands to MCR apply.
The only way to terminate the I/O
exercise in this case is to use the MCR ABORT command:
>ABORT IOX

In~errupting

E.8.2

IOX to Enter Commands

When you set CONTROL C YES, you can interrupt IOX to enter commands
interactively by entering CTRL/C on your keyboard.
For example, you
can execute other tasks with the EXECUTE command or abort the I/O
exercise with the IOX ABORT command.
During this interactive session,
however, IOX suspends display of error reports and activity reports to
your terminal.
PROCEED directs IOX to resume displays of error reports and activity
reports at your
terminal.
When IOX is in interactive mode, these
reports are discontinued even though the exercise continues to
execute.

E.8.3

Terminating an I/O Exercise and Restarting IOX

The ABORT command terminates the execution of an I/O exercise and of a
task or tasks initiated by the EXECUTE command.
ABORT with no command qualifier terminates the
exercise before normal completion.

execution

I/O

ABORT with a task name terminates the execution of a task initiated by
the EXECUTE command.
For example:
ABORT ••• BAD
This command aborts the Bad Block Locator Utility (BAD).
ABORT /ALL terminates all the tasks initiated by the EXECUTE command
and removes the tasks from the list of tasks to be executed by IOX.
The RESTART command directs !OX to:

E.9

•

Deselect and detach all units

•

Remove all user-configured units

•

Reset all parameters to default values

•

Return IOX to its original memory size

USING INDIRECT COMMAND FILES WITH IOX

You can use indirect command files with !OX in command mode.
!OX
accepts only one level of
indirect command file;
nested indirect
files are not allowed.

E-17

THE RSX-llM I/O EXERCISER
You can use indirect command files to set up execution parameters for
exercises.
For example, the file RUNlO.IOX contains the following IOX
commands to set execution parameters:
LOGFILE YES
RUNTIME 10
SUMMARYTIME l
CONTROL C NO

•

To execute this indirect command file, you enter the command:
@RUNlO.IOX
IOX accesses the file RUNlO.IOX and executes the commands, setting the
execution-time parameters.
Comments are allowed on command lines.

E.10

COMMAND DESCRIPTIONS

This section provides complete descriptions of IOX commands and the
rules for entering them on command lines. The commands are arranged
in alphabetical order.
Notational Conventions
The paragraphs below describe the notational conventions used in this
section to define IOX command elements and how to enter them on
command lines.
Command Line Elements
!OX command lines consist of command lines and qualifiers.
You can
abbreviate both the command name and the qualifier using the rule
described below under "Command Abbreviations."
There are two types of command qualifiers:
one type requires
settings and the other requires YES/NO settings.

numeric

Default Values for Command Qualifiers
Where there is a default value for a command qualifier, that value
stated explicitly in the command description.

Use of Uppercase Characters
Where uppercase characters appear in a command line
uppercase characters must be entered as they are shown.

format,

the

Use of Lowercase Characters
Lowercase letters,
words,
specifications
represent
substituted.
For example:

or symbols in
command
line
format
variables for which values should be

dduu:

E-18

THE RSX-llM I/O EXERCISER
These letters represent the values
that
make
up
a
device
spec: i f i ca t :i on •
Values can be substituted for each of these variables
as appropr:iate.
Use of Colons (:)
Col<>ns are used in device specifications as delimiters.
In this case,
the colon is required.
Colons are also used to separate related parts
of cettain command line elements.
For example:
BADBLOCKS DK2:

70:3

The colon following the device specification is the specification
delimiter;
the colon in 70:3 is the command element separator;
it
means enter a sequence of 3 bad blocks beginning at block 70.
Command Abbreviations
Where short forms of commands or qualifiers are allowed, the shortest
form acceptable is represented by uppercase letters.
The following
example shows the abbreviations allowed for
the IOX LOGFILE YES
command:
LOgf ile Yes
This notation means that LO, LOG, LOGF, LOGFI, LOGFIL, and LOGFILE and
Y, YE, and YES are valid specifications for the LOGFILE command.
Use of Braces ( [])
Braces are used to denote optional entries in a command line.
Use of At Sign (@)
The at sign (@) is used to invoke an indirect command file.
The
sign precedes the file specification for an indirect command file:

@filename.filetype;version
All numeric values are entered in decimal,
with
device unit numbers and file version numbers.

E-19

the

exception

THE RSX-llM I/O EXERCISER

ABORT
Abort[taskname]
[ /ALL ]
The ABORT command terminates the execution of an I/O exercise and
any tasks initiated by the EXECUTE command.
ABORT with no command qualifier terminates the
I/O exercise before normal completion.

execution

ABORT with a task name terminates the execution
initiated by the EXECUTE command. For example:

of
a

an
task

ABORT ••• BAD
This command aborts the bad block locator utility.
ABORT /ALL terminates the execution of all the tasks initiated by
the EXECUTE command and removes the tasks from the list of tasks
to be executed by IOX.

E-20

THE RSX-llM I/O EXERCISER

BAD BLOCKS
BAdblocks ddnn:

[blocknum:number, ••• [number, ••• ] ••• ]

The BADBLOCKS command allows you to enter the block numbers of
bad blocks on the unit IOX is to test.
In the format above,
number specifies the number of sequential bad blocks beginning at
the specified block number {blocknum in the format).
The colon
is required when you specify a sequence of bad blocks in this
form.
For example:
BADBLOCKS DK2:

70:3

This command enters the block numbers 70, 71, and 72 in
bad block list.
You can also specify the address of
example:
BADBLOCKS DK2:

single

bad

the

block.

IOX
For

This command enters block 3 in the IOX bad block list.
You can use both of these forms on the
example:
BADBLOCKS DK2:

same

command

line,

for

100:2,3,300:100

This command enters blocks 100, 101, 3, and 300
the IOX bad block list.

through

When you enter only the device name, IOX displays the bad
in its bad block list.
For example:

399

blocks

BADBLOCKS DK2:
This command causes IOX to display:
00070:003
00100:002
00003:001
00300:100
The first number in the display represents the beginning of the
sequence of bad blocks;
the second number in the display
represents total bad blocks in a sequence of bad blocks.

Bad block numbers entered with the IOX BADBLOCKS command are
temporary and are used only by IOX in its testing. That is, IOX
ignores the bad blocks recorded by the manufacturer or such
utilities as BAD;
IOX uses only the blocks you enter with the
BADBLOCKS command.

E-21

THE RSX-llM I/O EXERCISER

BUFFERSIZE
BU.ffersize bytes

The BUFFERSIZE command changes the size of the buffer !OX uses
when exerc1s1ng units with non-file-structured volumes.
!OX
stores the specified buffer size in byte form (rounded up to the
next 4-byte boundary)
and !OX requests buffers of that size
dynamically, as necessary.
This command is not valid if units are currently selected.

CONFIGURE
CONFigure [dduu:]
The CONFIGURE command enters a unit in the test configuration.
(Units must be configured before they can be selected for testing
by the SELECT or FILESll commands.) The CONFIGURE command also
displays the units in the test configuration.
CONFIGURE with a qualifier adds a unit to the test configuration.
For example:
CONFIGURE DK20:
This command adds device DK20:

to the test configuration.

CONFIGURE with no qualifiers lists all the devices
configuration:

the

test

IOX>CONFIGURE
DBO:
DRO:

DBl:
DSO:

DB2:
DXO:

DDO:
DYO:

DFO:
CTO:

Unit 0 is configured by default.

E-22

DKO:
DTO:

DK20:
MFO:

DLO:
MMO:

DMO:
MSO:

DPO:
MTO:

THE RSX-llM I/O EXERCISER

CONTROL_C
CONTrol C [Yes]
[No ]
The CONTROL C command enables or disables the use
interrupt an I/O exercise.

CTRL/C

CONTROL C YES enables interruptions to
an
I/O
exercise;
CONTROL-C NO disables interruptions to an I/O exercise.
When you set CONTROL C YES you can interrupt an I/O exercise to
enter !OX commands-interactively. For example, you can execute
other tasks by means of the EXECUTE command or abort the I/O
exercise by means of the !OX ABORT command.
When you interrupt an exercise with CTRL/C, the
exercise
continues to execute, but error reports and activity reports are
not displayed at your terminal.
Further, CTRL/C causes the !OX
clock to stop at the next summary interval, even though the
exercise continues to execute. Therefore,
the execution times
shown in activity reports may not show how long the I/O exercise
actually executes.
When you set CONTROL C NO,
the I/O
exercise
cannot
be
interrupted.
When you enter CTRL/C, MCR prompts you and the
rules for entering commands to MCR apply.
The only way to
terminate the I/O exercise in this case is to use the MCR ABORT
command:
MCR>ABORT !OX

I'\

E-23

THE RSX-llM I/O EXERCISER

DENSITY
~..

DENSity dduu: [nnnn]
The DENSITY command sets the tape density and characteristics
word for !OX to use while testing magnetic tape units.
Three densities are legal for MT:

devices:

200, 556, and 800 BPI
Two densities are legal for MM:

devices:

800 and 1600 BPI
One density is legal for MS:

devices:

1600 BPI
The device must be
example:
IOX>DENS MT:

specified

when

setting

the

density.

For

556

This command sets the tape density for MT:
If you do not specify the density,
unit, as follows

testing to 556 BPI.

[nnnn], but specify the device

IOX>DENS MM:
IOX displays the current tape density setting and characteristics
word for MM: devices. For example:
DENSITY = 800 BPI CHARACTERISTICS WORD

E-24

04004 (OCTAL}

THE RSX-llM I/O EXERCISER

DESELECT
DESelect dduu:
The DESELECT command terminates testing on the specified device.
DESELECT terminates I/O operations to the specified unit, deletes
the bad block list associated with the unit,
deassigns the LUN
for the unit, and detaches the unit from the test configuration.
The unit remains in the configuration.

ERRORLIMIT
ERrorlimit number
The ERRORLIMIT command sets the number of errors tolerated
between interval reports before IOX deselects a device because of
too many errors.
For example:
SUMMARYTIME 2
ERRORLIMIT 10
If you request summary reports every two minutes and an error
limit of 10 errors, IOX allows up to 10 errors on a unit in that
2-minute interval before deselecting the unit.

EXECUTE
EXEcute taskname commandstring
The EXECUTE command directs a command line to RSX-llM for
execution.
You can enter the EXECUTE command while IOX is in
command mode or when IOX is in interactive mode.
In both cases,
output directed to your terminal from the spawned task is
displayed at your terminal whether or not an exercise is
executing.
All the rules for entering RSX-llM command lines and the use of
the SPWN$ directive apply to the parameters you enter on the
EXECUTE command line.
A practical example of the use of EXECUTE is to run the
utility to list the bad blocks on a volume at your terminal:

BAD

EXE ••• BAD DKO:/LI
This command line invokes the BAD utility, which then
bad blocks on a volume at your terminal.

lists

any

EXIT
EX.It
The EXIT command terminates IOX processing and exits from IOX
the operating system monitor.

E-25

THE RSX-llM I/O EXERCISER

FILES11
Filesll dduu:

filesize

The FILESll command selects a unit with a Files-11 volume for an
I/O exercise.
The unit must first be entered in the test
configuration with the CONFIGURE command.
The FILESll command performs the same function as the SELECT
command.
FILESll is used to select units with Files-11 volumes;
SELECT is used to select units with non-file-structured volumes.
An example of the FILESll command is:
FILESll DKl:

1000

This command selects the unit DKl:
for I/O exercising.
The
number 1000 overrides the file size of the temporary file IOX
uses to process units with Files-11 volumes mounted.
IOX uses a temporary file when it processes units with Files-11
volumes.
, You
can
set the size of this file with the
TEMPORARYFILE command.

HELP
Help
The HELP command displays a summary description of
·at your terminal.

IOX

commands

The INTERLEAVE command specifies the interleave factor
of blocks) for exercising units.

(in number

INTERLEAVE
INterleave number

When IOX writes the test pattern to disk,
it can write the
pattern to either random blocks or to a specified sequence of
blocks.
You can direct IOX to write to random blocks by entering
the RANDOM command:
RANDOM YES
When you direct IOX to write to a sequence of blocks
(RANDOM NO
is set),
use INTERLEAVE to specify the number of blocks to be
skipped before the next pattern is written.
For example:
RANDOM NO
INTERLEAVE 2
In this example, the interleave factor is set to two and !OX
writes to and reads from every second block on the disk (block O,
block 2, block 4, and so forth)
beginning at block O.
For
DECtapes, the only interleave factor allowed is 4.

E-26

THE RSX-llM I/O EXERCISER

ITERATIONS
ITerations number
The ITERATIONS command specifies the number of times IOX executes
its idle loop before it counts an iteration through the idle
loop.
For example:
ITERATIONS 10
IOX counts one iteration for every 10 times it executes its
loop.
The ITERATIONS command is used with the WAIT command
system activity.

idle

measure

LOG FILE
Logf ile [Yes]
[ No]
The LOGFILE command enables you to direct activity reports and
error
reports to either your terminal or to a log file called
SYO:IOX.LOG.
LOGFILE YES directs reports to the
log file;
LOGFILE NO directs reports to your terminal.
LOGFILE NO is the
default.
Other types of output
(from the PRINTSUMMARY command or
command, for example) are always directed to your terminal.

SPY

IOX notes the time you started the log file and the time you
Once
completed entering data to it
in the activity reports.
IOX.LOG is created, IOX appends data to the end of the file
without creating new versions of the file.
Refer to Section E.6, "I/O Exercise Output," for more information
on how to use the LOGFILE command.

E-27

THE RSX-llM I/O EXERCISER

PARAMETERLIST
PARameterlist
The PARAMETERLIST command displays the settings of the IOX
execution parameters at the time you entered the command.
It
also, displays information on currently selected devices,
active
tasks, and the amount of dynamic memory in use.
When you enter the
PARAMETERLIST
information in the following form:

command,

!OX

displays

IOX>PARAMETERLIST
TASK

STATUS

••• BAD

QUEUED

COMMAND LINE

------

-----------DKO:/LI

DEVICE

LUN

BUFSIZE

TYPE

DBl:
DB2:
MMl:

5.
6.
7.

512.
512.
1024.

Fll
Fll
NFS

------

-------·

FILESIZE

-------500.
500.

CONTROL C= YES
LOG FI LE-;; NO
RANDOM= YES
REPORTERRORS= YES
RETRIES= NO
VOLUMECHECK= YES
WAIT= YES
WRITECHECK= NO

BUFFERSIZE= 1024.
ERRORLIMIT= 10.
INTERLEAVE= 4.
ITERATIONS= 10.
PATTERN= 4.
RUNTIME= 5.
SUMMARYTIME= 1.
TEMPORARYFILE= 500.

DYNAMIC MEMORY USAGE= 3278.:2248.:2248.:1.
For tasks
initiated
by
the
PARAMETERLIST command displays:

EXECUTE

command,

•

The installed task name

The execution status (QUEUED, ACTIVE,
ERROR, SV ERROR)

•

The command line elements you entered (DKO:/LI)

the

( ••• BAD)
SUCCESS,

WARNING,

ACTIVE indicates that IOX is being executed.
The remaining
status indications relate to Exit with Status (EXST$) Executive
directive.
For more information on these status indications,
refer to the RSX-llM/M-PLUS Executive Reference Manual.
For selected
information:

units,

PARAMETERLIST

displays

the

following

•

Device specifications (DBl:, DB2:, and MMl:)

•

Logical Unit Number (LUN)

•

Buffer size IOX uses for reads and writes
(512(10)
for
units with Files-11 volumes mounted;
1024(10) for units
with non-file-structured volumes)

•

Type of volume mounted on unit (Fll
for non-file-structured volumes;
verified)

E-28

(5, 6, and 7)

for
VFY

Files-11;
NFS
for units being

THE RSX-llM I/O EXERCISER
•

File size of the temporary file IOX uses
units with Files-11 volumes mounted

for

processing

The line describing dynamic memory usage is in the form:
totalmemory:freeblock:freebytes:fragments
totalmemory
Indicates the size of IOX dynamic memory in bytes.

•

freeblock,
Indicates the size of the
memory in bytes •

largest

free

block

IOX

dynamic

bytes
Indicates total free bytes available in IOX dynamic memory.
fragments
Indicates the number of memory fragments in IOX dynamic memory •

•

E-29

THE RSX-llM I/O EXERCISER

PATTERN
PATtern [patternnumber]
The PATTERN command sets the pattern IOX writes and reads during
testing.
There are 11 patterns, each specified by one of the
following numbers:
Pattern
Number
1
2
3
4
5
6
7
8

9
10
11

·-

Pattern
000000,000000
177777, 1 77777
125252,052525
165555,133333
163126,163126
055555,155555
022222,122222
111111,111111
007417,007417
021042,021042
104210,104210

For example:
PATTERN 3
This command directs IOX to use the pattern 125252,052525 when it
writes to units for testing.
IOX places an asterisk (*) next to
the selected pattern when you display the patterns.
Pattern 4 is the default pattern.

PRINTSUMMARY
PRintsummary
The PRINTSUMMARY command prints the totals for I/O exercise
activity between the time of the last interval summary report and
the time you entered the PRINTSUMMARY command. These totals are
printed in the form of a summary report displayed at your
terminal. Section E.6, "I/O Exercise Output," shows the form of
a print summary report.

PROCEED
PROceed
The PROCEED command is used to resume display of IOX activity
reports and error reports at your terminal and to restart the IOX
clock after these functions have been suspended by CTRL/C.
CTRL/C suspends activity and error reporting and stops the IOX
clock.
PROCEED resumes reporting to your terminal and restarts
the IOX clock.

E-30

THE RSX-llM I/O EXERCISER

RANDOM
RAndlom

[Yes]
[No ]

The RANDOM command directs IOX to use a random num~er generator
to choose
the blocks on the disk being exercised.
RANDOM YES
directs IOX to use the
random number generator;
RANDOM NO
directs IOX to use the number of sequential blocks specified in
the INTERLEAVE command.
Refer to the command description of the
information on how to use INTERLEAVE.

INTERLEAVE

command

for

REPORTERRORS
REPorterrors [Yes]
[No ]

The REPORTERRORS command enables or disables IOX error
reports.
REPORTERRORS YES directs IOX to report errors;
REPORTERRORS NO
disables error reports.
REPORTERRORS YES is the default.
When you direct IOX to
report errors,
IOX directs
the error
reports either
to your
terminal or to the log file IOX.LOG,
depending on how you have set the LOGFILE command.
(See the
command description of LOGFILE for
information on how to use
LOG FILE.)
IOX error reports have the following form:
DKl:
DKl:

UNRECOVERABLE ERROR AT BLOCK 358 (DECIMAL) (OCTAL)
DATA ERROR AT BLOCK 358 (DECIMAL) (OCTAL)
GOOD DATA:
165555
BAD DATA:
167155 (OCTAL)
WORD POSITION:
308 (DECIMAL) 464 (OCTAL)

RESTART
RES tart
The RESTART command directs IOX to deselect and detach all units,
remove all user-configured units, reset all parameters to their
default values, and return the exerciser task to
its original
memory size.

RETRIES
RETries [Yes]
[No ]
The RETRIES command directs an I/O driver to either retry or not
retry an I/O operation after it receives an error on the first
attempt at the operation.
RETRIES is used when exercising units
with non-file-structured volumes.

E-31

THE RSX-llM I/O EXERCISER

·RUNTIME
Runtime minutes
The RUNTIME command specifies the amount of time in minutes
!OX is to test a unit or units. For example:

that

RUNTIME 2
This command directs !OX to exercise selected devices for two
minutes. If you specify RUNTIME o, IOX tests units continuously.
The default run time is five minutes.

SELECT
SElect dduu:

[buffsize]

The SELECT command selects a unit with a non-file-structured
volume for an I/O exercise. An example of the SELECT command is:
SELECT DK!:

2000.

This command selects unit DKl: for an I/O exercise and specifies
a buffer size of 2000(10) bytes for !OX proc~ssing.
The unit must be configured with the CONFIGURE command before you
can. select it.
The SELECT command allows an I/O exercise to destroy all the data
structures on the mounted volume. To ensure that the mounted
volume is not a Files-11 volume,· enter:
VOLUMECHECK YES
If you do not specify the buffsize parameter, the size
in the last BUFFERSIZE command applies.
The default buffer size is 1024 bytes.

E-32

specified
·""

THE RSX-llM I/O EXERCISER

SPY
SPy [dduu:]

The SPY command displays information describing the current
status of a unit or units. When you specify no device on the
command line, the status of all units is displayed.
SPY displays status information in the following form:
DBO:

-- TYPE=Fll

VBN=305.

I/O=AST QUEUED

FUNCTION=WRITE

This line indicates:
•

The unit being exercised (DBO:)

•

The type of volume mounted on the unit (Files-11)

•

The Virtual Block Number being tested 305(10).
(This
would
be
the
Logical Block Number
(LBN)
for an
unformatted volume)

I/O request status:

•

The type of I/O function being performed (WRITE)

AST QUEUED, IN PROGRESS, or IDLE

START
STa1rt
The START command starts execution of an I/O exercise on units
selected by the FILESll command and the SELECT command. Refer to
Section E.3,
"Installing, Invoking, and Running IOX in an
Exercise Example," for
information on how to use the START
command.

SUMMARYTIME
SUmmarytime [minutes]
The SUMMARYTIME command specifies the time interval
between interval summary reports.
For example:

minutes

SUMMARYTIME 15
This command specifies that you want a summary
every 15 minutes.
A

report

generated

value of 0 specifies that you want no summary reports.

The default for the interval between summary reports is 1 minute.

'-''
E-33

THE RSX-llM I/O EXERCISER

TEMPORARYFILE
TEmporaryfile [filesize]
The TEMPORARYFILE command is used when you want to exercise a
unit with a Files-11 volume mounted. TEMPORARYFILE specifies the
size in blocks of the temporary file !OX uses when it tests
file-structured devices.
This file is marked for deletion when
!OX exits.
Thus,
if !OX terminates prematurely, your file
structure is not corrupted with temporary files used by !OX.

VERIFY
VErify dduu:

[blocks]

The
VERIFY
command
is
used
with
units
that
have
non-file-structured volumes mounted.
VERIFY ensures that a
device is performing I/O correctly by reading the number of
blocks
(specified by the blocks parameter) from the specified
unit.
!OX performs no pattern checking with VERIFY;
exercise is performed.

that

is,

I/O

VOLUMECHECK
VOlumecheck [Yes]
[No ]

The VOLUMECHECK command enables or disables a check by !OX to
determine
whether
or
not
a
unit
being
tested
as
non-file-structured has a home block.
If you check for the home
block and !OX finds a home block on the unit, IOX issues a
message warning you that the unit has a Files-11 volume mounted
and you may be destroying vital information.
The default is VOLUMECHECK YES.

E-34

c:c~,

THE RSX-llM I/O EXERCISER

WAIT
WAit [Yes]
[No ]

The WAIT command is used with the ITERATIONS command to measure
system activity.
IOX executes an idle loop while it waits for
you to enter a command.
It can execute either one of the
following in this loop:
1.

The wait-for-event-flag algorithm

The instruction
BICB -(SP), (SP)+

The BICB instruction takes up a large amount of CPU time and
be used to measure I/O throughput.

can

The wait-for-event-flag algorithm is the default,
but you can
disable
it and execute the BICB instruction by entering the
command
WAIT NO
"Setting Execution Conditions
for
Ref er to Section E.5.4,
Measuring System Activity,"
for
information on how to use the
WAIT command~

WRITECHECK
WRitecheck [Yes]
[NO ]

THE WRITECHECK command enables or disables write checks by I/O
drivers when they perform I/O during an I/O exercise. WRITECHECK
is used to exercise units with non-file-structured volumes.
WRITECHECK YES directs the I/O driver to perform write checks;
WRITECHECK NO directs the I/O driver to disable write checks.
When an I/O driver performs an I/O operation,
it issues three
instructions:
WRITE, WRITE CHECK, and READ. By eliminating one
of these I/O operations, you can increase the speed of the I/O
exerc:ise.
Th~

default is WRITECHECK NO.

E-35

THE RSX-llM I/O EXERCISER
E.11

IOX MESSAGES

IOX displays the following messages. When it can determine that a
specific device unit is involved, IOX also displays the device unit.
dduu: -- BAD BLOCK, XXX (DECIMAL) XXX (OCTAL)
Explanation: The error code returned to IOX was IE.BBE (bad block
error).
User Action: Use the BADBLOCKS command to enter
into the IOX bad block list.

that

bad

•

block

dduu: -- DATA ERROR AT BLOCK XXX (DECIMAL) XXX (OCTAL)
GOOD DATA: XXXXXX BAD DATA: XXXXXX (OCTAL)
WORD POSITION: XXX (DECIMAL) XXX (OCTAL)
Explanation: IOX found an error when comparing the read data with
the written data. The position of the word within the IOX data
buffer is shown along with the good and bad data.
User Action: None. If the error persists, enter that block in
the
bad
block list by using the BADBLOCKS command (for
non-file-structured devices only.)
dduu: -- DATA OVERRUN AT BLOCK XXX (DECIMAL) XXX (OCTAL)
Explanation: IOX received an error return of IE.DAO. The record
size given was greater than that read. This error occurs on tape
devices only.
User Action:

None.

dduu: -- END OF VOLUME SEEN
Explanation: IOX attempted to write a record past the end of tape
marker.
User Action:

None.

dduu: -- ERROR THRESHOLD EXCEEDED
Explanation: The number of errors set with the ERRORLIMIT command
has been exceeded.
User Action: None. This is an information message only.
deselects the unit and continues testing the other devices.

IOX

dduu: -- FAILED TO DETACH UNIT
Explanation: This error is extremely rare because IOX
all units that it has attached and only those units.
User Action: None.

detaches

This is a possible operating system problem.
~!

E-36

THE RSX-llM I/O EXERCISER
dduu: -- FATAL HARDWARE ERROR
Explanation: The IE.FHE (fatal hardware error) I/O error code was
returned to IOX. IOX could not recover from the error.
User Action: Check the hardware.
dduu: -- I/O REQUEST ABORTED
Explanation: The IE.ABO I/O error code was returned to IOX.
QIO to the device failed •

User Action: None.
If the problem
code (Executive or driver).

persists,

dduu: -- I/O UNSATISFIED AT TIMEOUT - FUNCTION:

check

the

The
system

XXXX

Explanation: When IOX finishes processing, it waits five seconds
for I/O to stop. If a long tape is rewinding, this message may
occur. XXXX is the function that timed out:
READ, WRITE, or
REWIND.
User Action: None.
dduu: -- NO RESPONSE
Explanation: Unit did not respond to IOX command within one
minute.
The device may have been accidentally put offline or a
tape drive may have lost its column vacuum.
User Action: Check the device.
dduu: -- NOT READY
Explanation: The unit is not ready.
User Action: Check the device.
dduu: -- OFF-LINE
Explanation: The unit is offline.
User Action: Check the unit.
dduu: -- PRIVILEGE VIOLATION
Explanation: The device was
someone else ..

not

allocated

User Action: Check the ownership of the device.

E-37

was

mounted

THE RSX-llM I/O EXERCISER
dduu: -- UNIT CONTAINS FILE STRUCTURED VOLUME
Explanation: The VOLUMECHECK command found that the unit is file
structured because the file contains a home block. You are not
allowed to use the SELECT command on this unit.
User Action: !OX destroys information on non-file-structured
volumes.
Make certain that you really want this unit tested as a
non-file-structured volume.
dduu: -- UNIT NOT MOUNTED FOR NFS OPERATIONS
Explanation: You
tried
to
issue
a
command
non-file-structured device to a file-structured device.
User Action: Check
command.

the

device

configuration

and

for

reissue

the

could

not

dduu: -- UNEXPECTED ERROR XX
Explanation: !OX received an error
process.
XX is the error code.

code

that

User Action: None.
dduu: -- UNEXPECTED REQUEST TO QUEUE I/O - REQUEST ABORTED
Explanation: !OX receives an AST
deselected the device.

from

device

after

has

User Action: Check the device.
dduu: -- UNRECOVERABLE ERROR AT BLOCK XXX (DECIMAL) XXX (OCTAL)
Explanation: !OX received an IE.VER code from the
code indicates an unrecoverable error.

driver.

This

User Action: Check the device and the media.
dduu: -- VERIFICATION COMPLETE
Explanation: This is an information message.
the VERIFY command has completed.

The

operation

User Action: None.
dduu: -- WRITE-LOCKED
Explanation: The device is write-locked.
User Action: Check the device write-lock/write-enable switch.
dduu: -- WRITECHECK ERROR AT BLOCK XXX (DECIMAL) XXX (OCTAL)
Explanation: The write check operation failed at block XXX.
User Action: None.

E-38

THE RSX-llM I/O EXERCISER
IOX -- "@" SYNTAX ERROR
Explanation: There is an error in the indirect command file.
User Action: Check the indirect command file.
IOX -- "@" NESTING LEVEL EXCEEDED
Explanation: Only one level of nesting is allowed in an
command file ..

indirect

User Action: Check that the indirect command file
level of nesting.

only

has

one

IOX -- ABORTING DUE TO MCR/PDS COMMAND OR DIRECTIVE
Explanation: IOX was aborted from an external source, but did the
necessary housekeeping before exiting.
User Action: Restart IOX.
IOX -- BUFFER SIZE GREATER THAN DEFAULT
Explanation: The buffer size used in the SELECT command is
greater than the default buffer size in the BUFFERSIZE command.
User Action: Respecify the SELECT command.
IOX -- COMMAND NOT SUPPORTED
Explanation: This error indicates an attempted execution of the
EXECUTE command on a system that did not have the SPAWN directive
in the Executive.
User Action: You may have to do another system generation to
the SPAWN directive into your Executive.

get

IOX -- COMMAND I/O ERROR
Explanation: IOX detected an error when it tried
command that you were typing in at the terminal.

read

the

User Action: Retype the command.
IOX -- COMMAND VALID ONLY AFTER ABORT

Explanation: You tried to enter a command that cannot be entered
while IOX is running. These commands are: RUNTIME, BUFFERSIZE,
PATTERN, RESTART, and START.
User Action: Enter these commands in command mode.

E-39

THE RSX-llM I/O EXERCISER
IOX -- COMMAND NOT UNIQUE
Explanation: The command abbreviation that you entered
sufficient to distinguish it from another command.

was

not

User Action: Reenter the command with more letters.
IOX -- DRIVER NOT LOADED
Explanation: IOX tried to attach a device which had
driver.

unloaded

User Action: Load the driver.
IOX -- DUPLICATE BLOCK NUMBER
Explanation: The block number that you entered with the BADBLOCKS
command is already in the bad blocks list.
User Action: Reenter the command.
IOX -- ERROR ATTEMPTING TO READ HOME BLOCK
Explanation: When the VOLUMECHECK command has been given,
this
error occurs if IOX reads a home block or has an error trying to
read a home block. The error indicates that IOX has found a
file-structured volume and may destroy the information on it.
User Action: Stop IOX and check the disk that you have mounted on
that device unit.
!OX -- FAILED TO OPEN TEMPORARY FILE ON dduu:
Explanation: !OX could not find the necessary number of blocks on
the disk as specified in the FILESll command or the TEMPORARYFILE
command.
User Action: Specify a smaller file size.
!OX -- FAILED TO OPEN "@" FILE
Explanation: GCML failed to open the indirect command file.
User Action: Make sure that
indirect command file.

the

file

exists

and

reenter

the

!OX -- FAILED TO OPEN LOG FILE
Explanation: !OX could not open the log file.
User Action: The disk may be write
enough blocks.

E-40

protected

may

not

have

THE RSX-llM I/O EXERCISER
!OX -- FAILED TO CLOSE LOG FILE
Explanation: !OX could not close the log file.
User Action: Check the device.
!OX -- FAILED TO ATTACH dduu:
Explanation: IOX could not attach unit.
User Action: The device may be mounted or someone else attached
the unit.
Make sure that you have allocated the device and that
it is mounted foreign for RSX-llM-PLUS. For RSX-llM it does not
have to be mounted.
!OX -- FATAL FILES ERROR.

F.ERR= XXX PC+2= XXX

Explanation: An error occurred while IOX was trying to issue a
READ$ or a WRITE$ command.
F.ERR is the error code in the FOB.
PC+2 is the location of the error in IOX. IOX immediately exits.
User Action: Investigate the source of the error in the code.
!OX --

FA~rAL

ERROR.

DSW= XXX PC+2= XXX

Explanation: A directive issued by IOX did not work. DSW is the
directive status word.
PC+2 is the location of the failure in
IOX. !OX immediately exits.
User Action: Investigate the source of the error in the code.
IOX -- FILES OPERATIONS NOT SUPPORTED ON dduu:
Explanation: You entered a FILESll command to a
not a Files-11 volume.

volume

that

User Action: Reenter the command for the correct device or use
different command.

IOX -- ILLEGAL DENSITY
Explanation: The density that you specified for the
incorrect. The device does not support that density.

device

User Action: Reenter the command using
device.

density

different

IOX -- ILLEGAL UNIT SPECIFICATION
Explanation: The syntax of the unit specification is incorrect.
User Action: Reenter the command.

E-41

THE RSX-llM I/O EXERCISER
IOX -- INVALID BLOCK NUMBER

Explanation: The block number that you entered for the
command was not a valid block number for that device.

BADBLOCKS

User Action: Reenter the command using a different block number.
IOX -- INVALID TASK NAME
Explanation: The task name that you entered is invalid. That is,
the task name is incorrect, the task does not exist, or the task
is not installed.
User Action: Reenter the task name or determine whether the
exists or is installed.

task

IOX -- INVALID PATTERN NUMBER
Explanation: You tried to set a data pattern for IOX to
I/O testing that IOX did not recognize.

use

User Action: Check the PATTERN command and
data pattern.

correct

reenter

the

for

IOX -- INVALID COMMAND - TYPE H FOR HELP
Explanation: You entered a command that IOX did not recognize.
User Action: Enter H (for help)
commands.

and

IOX

displays

all

its

IOX -- NO BUFFER SPACE
Explanation: IOX could not extend
larger buffer.

make

room

for

needed

User Action: Reinstall IOX with a larger increment.
IOX -- NO LUNS AVAILABLE
Explanation: This is an unlikely message because IOX allows 250
devices.
Unless you have more than 250 devices, this message may
indicate a system problem.
User Action: If you
software specialist.

have

less

than

250

devices,

call

your

IOX -- NO ACTIVITY REMAINS - ABORTING
Explanation: All disk testing and all tasks are
the run time has expired.
User Action: None.

E-42

finished

before

THE RSX-llM I/O EXERCISER
!OX -- NO ACTIVITY TO START
Explanation: You issued the START command
configuration or units to exercise.

without

User Action: Configure and define the devices that
exerc:ise.
!OX -- ONLY

defining

the

you

want

ALLOWED

Explanation: You previously entered the CONTROL C YES command to
enable interruptions to !OX. Therefore, !OX does not accept any
other input but CTRL/C.
User Action: Enter CTRL/C then enter the command.
IOX -- SYNTAX ERROR
Explanation: The command line that you entered contained a syntax
error.
User Action: Reenter the command line.
!OX -- TASK NEVER EXECUTED
Explanation: The task that you tried to abort is not on the
of tasks initiated by the EXECUTE command.

list

User Action: Check your list of tasks
EXECUTE command.

the

initiated

!OX -- TASK "XXXXXX" CURRENTLY ACTIVE
Explanation: You tried to execute a task that was already active.
XXXXXX is the task name.
User Action: None.

"""'

!OX -- TASK "XXXXXX" EXECUTION COMPLETE.

STATUS= NNNNNN

Explanation: The task completed execution.
name. NNNNNN is the task status.
User Action: None.

E-43

XXXXXX

the

task

THE RSX-llM I/O EXERCISER
!OX -- TASK "XXXXXX" NOT INSTALLED
Explanation: The task name "XXXXXX" is not installed
be executed as requested.

and

cannot

User Action: Install the task.
!OX -- TASK "XXXXXX" UNABLE TO EXECUTE
Explanation: IOX could not execute the task
time.

within

specified

User Action: Try to reexecute the task.
!OX -- UNABLE TO ASSIGN LUN TO dduu:
Explanation: You tried to access
system.

unit

that

not

the

User Action: Check the system configuration.
!OX -- UNIT NOT A MAGTAPE
Explanation: You tried to issue a DENSITY
that is not a magnetic tape device.

command

device

User Action: Reissue the command.
!OX -- UNIT NOT SELECTED
Explanation: You issued a device-dependent command to a device
that you have not selected with the SELECT command or the FILESll
command.
User Action: Determine which device you want to affect and select
it with the SELECT or FILES-11 command.
!OX - UNIT IS FILE STRUCTURED
Explanation: You used the BADBLOCKS command to try to create a
bad blocks list on a file-structured volume. The command did not
execute.
User Action: Make certain that you really want IOX
this device.

write

the

CONFIGURE

!OX -- UNIT ALREADY CONFIGURED
Explanation: You tried to configure a unit with
command that is already in the configuration.
User Action: Check the !OX device configuration.

E-44

THE RSX-llM I/O EXERCISER
!OX -- UNIT NOT CONFIGURED
Explanation: You tried to access a unit that is not
unit configuration.

the

IOX

User Action: Configure the unit using the CONFIGURE command •

!OX -- UNIT ALREADY SELECTED

Explanation: You tried to select a unit
selec:ted.

that

User Action: Check the printout to
previously selected.

which

find

has

already

units

you

been
have

!OX -- UNITS ARE SELECTED - COMMAND IGNORED
Explanation: The BUFFERSIZE command is valid only if no units are
selected by either the FILESll or SELECT command.
User Action: Deselect all selected units.

E.11.1

IOX Task Builder Command File

IOX is built with the defaults that it needs to perform its required
functionso
The Overlay Description Language
(ODL)
file for !OX
resides on UIC [l,20] on the system disk.
If you want to rebuild IOX
with different defaults,
you can create a Task Builder command file
like the one the system uses, which is shown below, and put it on UIC
[1,24]
for a mapped system or UIC (1.20] for an unmapped system.
These UICs are RSX-llM-PLUS/RSX-llM system conventions.
ThE~

system command file for building IOX puts the IOX task on system
UIC
[1,54]
for a mapped system;
the UIC for system tasks on an
unmapped system is [l,50]. The command file is shown as inline code
with commentary.
(The RSX-llM Task Builder and the
RSX-llM/M-PLUS Task Builder Manual.)

ODL

are

described

BUILD MAPPED I/O EXERCISER Vl4
;

•

[l,54]IOX/FU/CP/MM,[l,34]IOX/-SP/CR/MA/-SH=[l,20]IOXBLD/MP
STJ\CK=96
ASG=TI:l:2:4:5:6,SY0:3
PRJC=50
TASK= ••• IOX
PAH=GEN
;

; NOW DEFINE THE MAXIMUM AMOUNT OF UNITS YOU WILL EVER WANT TO
; TEST. THE MAXIMUM IS 250 AND THE DEFAULT IS 32.
;

UNITS=32
;

; JrnHIBIT USER OF UNUSED FCS READ/WRITE LONG CODE.
;

GBLDEF= •• RWLG:O

E-45

the

THE RSX-llM I/O EXERCISER
; THE DEFAULT TEMPORARY FILE STRUCTURED BLOCK SIZE IS
; DEFINED HERE. THE NORMAL DEFAULT IS 500 DECIMAL (764 OCTAL)
;

GBLDEF=FllSIZ:764
NOW WE WILL DEFINE THE DEFAULT 2-WORD PATTERN WHICH WILL BE
USED TO FILL THE WRITE BUFFER. THE VALUE MUST BE BETWEEN 1 AND 13.
THE VALUES CORRESPOND TO THE FOLLOWING PATTERNS:
1
000000,000000
2
177777,177777
3
125252,052525
4
165555.133333
5
163126,163126
6
055555,155555
7
022222,122222
10
111111,111111
11
007417,007417
12
021042,021042
13
104210~104210
;

GBLDEF=PATERN:4
NOW WE WILL DEFINE THE CHARACTERISTICS USED FOR MAGTAPE TESTING.
THE DEFAULT FOR TUlO IS CORE DUMP MODE; FOR ALL OTHERS IT IS
1600 BPI MODE. SEE THE I/O DRIVERS REFERENCE MANUAL FOR FURTHER
INFORMATION CONCERNING THIS VALUE.
;

GBLDEF=MAGSTC:004004
;

; NOW DEFINE THE DEFAULT TEST RUNTIME.
;

GBLDEF=RUNTIM:5
;

; NOW DEFINE THE DEFAULT INTERVAL BETWEEN SUMMARY REPORTS.
;

GBLDEF=SUMARY:l
;

; NOW DEFINE THE ERROR THRESHOLD. THIS IS THE NUMBER OF ERRORS
; PERMITTED BETWEEN SUMMARY REPORTS BEFORE THE UNIT WILL BE DE-SELECTED.
;

GBLDEF=ERRMAX:l2
;

; NOW DEFINE THE NUMBER OF ITERATIONS THAT WILL BE MADE IN THE
; BACKGROUND LOOP BEFORE A ITERATION IS COUNTED.
;

GBLDEF=ITRCNT:l2
;

; NOW DEFINE THE INTERLEAVE FACTOR THAT IS USED FOR SEQUENTIAL
; NON-FILE STRUCTURED DISK OPERATIONS.
;

GBLDEF= INTRLV: 4
;

; NOW DEFINE THE DEFAULT NAME FOR THE EXERCISER. THIS NAME IS IN
; RAD50 AND IS USUALLY "IOX".
;

GBLDEF=IOXNAM:035260
; NOW DEFINE THE DEFAULT NON-FILE STRUCTURED BYTE COUNT. THIS IS USED
; FOR ALL NON-FILE STRUCTURED DEVICES EXCEPT DECTAPE. THE USUAL VALUE
; IS 2 BLOCKS (2000(8} BYTES}.
;

GBLDEF=PABCNT:2000
;

; NOW WE WILL DEFINE THE UNSOLICITED AST CHARACTER. THIS IS THE

E-46

THE RSX-llM I/0 EXERCISER
; CHARACTER WHICH WILL INTERRUPT THE EXERCISER WHEN THE 'CONTROL C'
; FEATURE IS ENABLED. THE DEFAULT CHARACTER IS CONTROL/C.
;

GBLDEF=$CC:3
;

; NOW WE WILL DEFINE SOME DEFAULT YES/NO VALUES.
; A VALUE OF "O" SIGNIFIES "NO"; A VALUE OF "l" SIGNIFIES "YES".
;

GBLDEF=REPORT:l

;REPORT ERRORS TO CONSOLE

;

GBLJDEF=RANDOM:l

;USE RANDOM DISK SEEKS

;

GBLlDEF=CONTIN: 0

;DO NOT RUN CONTINUOUS

;

GBLlDEF=CTRLC:l

;USE UNSOLICITED AST'S

;

GBLlDEF=WAI TF: 1

;"WAIT" INSTRUCTION IN BACKGROUND LOOP

;

GBLDEF=VOLCHK:l

;FILE STRUCTURED VOLUME CHECKING

;

E-47

APPENDIX F
SYSTEM CONVENTIONS

F.l

RSX-llM UIC CONVENTIONS

The RSX-llM Release 3.2 distribution kits observe a set of UIC
conventions for files on disk. The purpose of these conventions is to
provide a uniform and consistent means of allocating,
locating, and
maintaining files on disk.
On a disk, there are many User File Directories (UFOs) in which files
are catalogued.
A particular UFO is referenced by specifying the
correct UIC (User Identification Code).
The UIC consists of two
numbers separated by a comma and enclosed in brackets (such as UIC
[11,20]). The first number (11) is the group number;
the second
number (20) is the member number, which indicates a specific directory
within a group of directories.
RSX-llM makes use of the UICs to keep
related files in specific directories.

F.1.1

Group Number

The group number is used to identify groups of directories.
By
convention,
group numbers of l through 10 are reserved for access by
the Executive. At present, only group number 1 is used.
It is used
to identify UFOs which contain files relevant to an RSX-llM system.
Group numbers 11-377(8) may be used for
user files.
Please note,
however,
that group numbers 11-27(8)
are reserved by DIGITAL for
storing files
relevant to the Executive and Ancillary
Control
Processors (ACP).
Group Number 11
12

is used for Executive files
is used for MCR files

In addition, group numbers 30-177(8)
are reserved for DEC-supplied
software tasks.
The distribution kit only uses group numbers 1, 11,
12, 13, 15, 45, and 200.
Group number
Group number
Group number

is used for privileged utility tasks
(PMD, RMDEMO, etc.)
45 is used for K-series files
200 is used for SYSGEN indirect command files

F-1

SYSTEM CONVENTIONS

Member Number

F.1.2

The second number (member number) is used to hold different file types
of the group.
For example, the UIC [11,10] contains source modules of
the Executive. Member numbers currently in use are:

•

Source modules.

Object modules, assembly and task build command
files, object module libraries, overlay descriptor
files for the
Executive
and
all
unmapped
privileged and nonprivileged tasks •

Same as 20 above, except that files are for mapped
privileged
and
nonprivileged tasks,
and the
Executive.

Listing and map files for all unmapped
and nonprivileged tasks.

privileged

Listing and map files for
and nonprivileged tasks.

privileged

SLP correction files
member number 10.

Tasks and Executive for RSX-llM unmapped system.

Tasks and Executive for RSX-llM mapped system.

Tasks and Executive for RSX-llS unmapped system.

Tasks and Executive for RSX-llS mapped system.

200

SYSGEN indirect command files.

for

all

mapped

files

located

under

Member numbers 50, 54, 60, and 64 exist only for group number 1.
Member numbers 10 and 40 exist only for group numbers above 10.
Member numbers 20, 24, 30, and 34 exist for all group numbers.
Member
number 200 is used exclusively with group number 200.
For example, for MCR:
[12,10]

Source files.

(12,20]

Unmapped object modules,
assembly
and library build command file.

(12,24]

Mapped object modules, assembly command files
library build command file.

(12,30]

Unmapped listing files.

[12,34]

Mapped listing files.

[12,40]

SLP correction files for files under [12,10].

F-2

command

files
and

SYSTEM CONVENTIONS
For the unmapped system:
[1,20]

Object module libraries, task build command files,
and Task Builder overlay description files for all
tasks.

[1,30]

Area for task maps.

[1,50]

RSX-llM Executive and system tasks.

•

For the mapped system:
[1,20]

Object module libraries, all task build overlay
descriptor files for all nonprivileged tasks.

[l,24]

Object module libraries, task build command files
for all mapped tasks,
and overlay description
files for all privileged tasks.

[l ,34]

Executive and task maps.

[l,54]

RSX-llM Executive and system tasks.

Other UICs:

F.2

[ 1'1]

System and macro object module libraries.

[ 1'2]

System message files.

[ 1'3]

Di rectory for lost files found by VFY.

[1,4)

Directory for Post-Mortem and Snapshot Dumps.

[1,6)

Directory for error log files.

[1,51)

Standalone DSC

NAMING CONVENTIONS

System file names have the following general format:
pppnnnsss.typ
where:
ppp

is an optional pref ix used to designate a spacial version or
characteristic of the named file.
The designation BIG, for
example, is sometimes used to designate a task, such as TKB, that
is built to operate in more than 8K of memory, e.g., BIGTKB.

nnn

is the system identification for the task. Table F-1 lists all
system tasks, together with the identification and group codes.

sss

is a suffix for noting the relationship of the file to the task
specified in the nnn identification.
For example, PIPBLD.CMD is
the command file for building PIP.
Suffixes:
ASM
BLD

Assembly command file
Task Builder command or overlay description file

F-3

SYSTEM CONVENTIONS
typ
'--''

,..

is the standard mnemonic for file type, such as MAP, CMD, etc.
Types:
CMD
DAT
LST
MAC
MAP
MLB
OBJ
ODL
OLB
PMD
SML
STB
TSK

Command File
Data files
MACR0-11 Listing File
MACR0-11 Source File
Task Map File
User Macro Library File
MACR0-11 Object Library File
Overlay Description File
Object Library File
Post-Mortem or Snapshot Dump File
System Macro Library File
Task Symbol Table File
Task/Driver Image File
Table F-1
System Identification Codes

System
ID

....

Group
Code

Description

RSX

RSX-llM/S Executive, drivers, and tables

MCR

Monitor Console Routines

FCP

Files-11 Ancillary Control Processor

RMD

RMDEMO

PMD

Post-Mortem and Snap-Dump Processor

BMR

Basic MCR (RSX-llS)

ERL

Error Logger

OTL

On-Line Task Loader

SIP

System Image Preservation Program (RSX-llS)

MTA

Magtape ACP

Queue Manager

MAC

MACR0-11 Assembler

'I'KB

Task Builder

PIP

Peripheral Interchange Program

F'LX

File Transfer Program

VFY

File Structure Verification Program

DMP

File Dump Utility

(ACP)

(RSX-llS)

(continued on next page)

F-4

SYSTEM CONVENTIONS
Table F-1 (Cont.)
System Identification Codes
System
ID

Group
Code

Description

DSC

Disk Save and Compress Utility (task version)

EDI

Line Text Editor

SLP

Source Language Input Program

PRES RV

Volume Preservation Program

LBR

Librarian

PRT

Serial De-spooler

ODT,TRACE 47

Online debugging tool, trace

FCS

File Control Services

PSE,SYE

Error log formatters

CML

Command Line Routing

ZAP

File Patch Utility Program

BAD

Bad Block Locator Program

DSCS8

Disk Save and Compress Utility (stand-alone
version)

CRF

Cross Reference Utility Program

VMR

Virtual MCR Program

BRU

Backup/Restore Utility

UMD

101

User Mode Diagnostics

FTB

106

Fast Task Builder

CMP

107

File Compare Utility

PAT

111

Obj~ct

FMT

112

Online Formatter

IOX

113

System I/O Exerciser

CDA

116

Crash Dump Analyzer

LPP

121

Queue Manager De-spooler

Module Patch Utility

F-5

APPENDIX G
BUILDING A 4K FCS RESIDENT LIBRARY

•
This Appendix documents the method to build a 4K FCS resident
(FCSRES).

'-'i

G-1

library

BUILDING A 4K FCS RESIDENT LIBRARY
.TITLE
.IDENT
COPYRIGHT

FCSRES • FCS RESIDENT LIBRARY

f ILE

117.0/

1q74,

DIGITAL

EQUIPMENT

CORP.,

MAYNARD,

MASS,

THIS SOFTWARE IS FURNISHED TO PURCHASER UNDE~ A LIC~NSE FOR USE
ON A SINGLE COMPUTER SYSTEM AND CAN BE COPIED (wITH INCLUSION
OF DEC'S COPYRIGHT
NOTICE) ONLY FOR USE IN SUCH SYSTEM, E~CEPT
AS MAY OTHERWISE BE PROVIDED IN WRITING BY otc.
THE I NF ORMA TI ON · IN TH IS DOCUMENT IS SUBJECT T0 CHANGE. lrol IT HOUT
NOTICE AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL
E~UlPMENT CORPORATION,
DtC ASSUMES NO RESPONSIBILITY FOR THE
OF ITS SOFTWARE ON EQUIPMENT WHICH IS

USE OR RELIABILITY
NOT SUPPLIED BY DEC,

MUOlFIED1

• COMMENT OUT ENTRY POINTS, TO RESTORE DEFAULT
FCSRES TO BELOW UK,
SR016 • INSERT CALLS OF ARITH ANO DARITH ROUTINES TO
CORRECT PSECT PROBLEM,
SR~17

THIS FILE DOCUMENTS HOW TO BUILD AN FCS RESIUENT LIBRARY,
ANO IT DEFINES ALL OF THE POSSIBLE MODULES THAT MIGHT GO INTO
SUCH A LIBRARY.
IT SHOULD BE UNDERSTOOD THAT PRECISELY HOW MUCH GOES INTO FCSRES
IS ACTUALLY DEPENDENT ON ~HICH PROGRAMS ARE ~OING TO USE IT ANO WHAT
THOSE PROGRAMS REQUIRE, THE IMPORTANT POINT TO BEAR IN MIND
IS THAT A PROGRAM LINKING TO FCSRES MAY NOT GET MISSING FCS MODULES
F~OM THE SYSLIB,OLB 08JECT LIBRARY FILE AS W~LL, A PROGRAM NEEDING
FCS MODULES wHICH WERE NOT PLACED IN FCSRES ~OULO HAVE NO CHOICE
BUT TO LIN~ WITHOUT FCSRES AND USE ALL THE MUOULES OUT OF SYSLIB,
FUR THE OBVIOUS REASONS OF SllE1 THE MINIMUM AMOUNT SHOULD SE PUT IN
FCSRES CONSfSTENT WITH THE NEEOS OF THE PROG~AMS USING IT,
T~OSE ENTRY POINTS THAT ARE INVOKED BY MACROS ARE DOCUMENTED BELOW
SU THAT IT IS POSSIBL~ TO PICK WHAT SHOULD GO INTO FCSRES,

IT IS INTENDED THAT THIS
MODULES FROM FCSRES,

FIL~

BE EDITED TO ELIMINATE UNDESIRED

THE ACTUAL BUILDING Of FCSRES INVOLVES THE FOLLOWINGS
t) ASSEMSLf THIS MODULE
MAC> FCSRES,FCSRES•FCSRES

,,
,
J
J
J
J

,
J
J
J
J

2) BUILD THE LIBRARY
SET /UIC•[t,tl
TO BUILD FCSR~S FOR A MAPPED SYSTEMS
TKB>[11l)FCSRES/•HO/MM/PI,LP1,sYlll11]FCSRES=L200,200JFCSRES
TKB>/
TKB>STACK:0
TKB>PAR:FCSRES10120000
TKB//

AN FCSRES ON AN UNMAPPED SYSTEMS
,, TO BUILDTKB>SYl[11llFCSRESl•HD/•MM/PI,LP1,sY1[1,1JFCSRES•l200,200JFCSRES
TKB>/

J
J
J
.J

TKB>STACK•0
TKB>PAR•FCSRES1140~00120000

TKB>//

G-2

~·

BUILDING A 4K FCS RESIDENT LIBRARY
.MCALL
.PSECT

'--"'

Of~ENING

CAL LR
SSRESL

FIL.ES

.GLOBL
,OPI• IDI 1CALl.R
.GL.08L.

.OPEN
.OPEN
.OPFNB

sOPEN$X, OPNSU, OPNT$X
JOFJD$X CAN us~ THE OPEN$X CODE
JOFNB$X • USED FOR FO~TAN RUN TIME

.CLOSE

JCLOSE$

.GET,.PUT
,PUT
.GET

JGETS, AND PUU, GE TS~, AND PUT$R
sPUUS CAt-.1 USE PUTS CODE.
,-GEUS CAN USE GE. TS CODE.

Cl.OSING F:lLES
• GLIJBL
Rl:.CORD 110
'!"

.GLOBL
,PUUQS ICALl.R
,GElSQs 1CALl.R

,'' AHlTH ANO DARlTH ROUTINES NECESSARY
.GLOBL $0IV,$0MUL $0DIV S

FOR

Gl:.T$ ANO PUTS

81.0CK 110

Dl~LE TE

FI I.ES
.GLOBL
.GLOBL

,DELET
,MRKDL

J DEi.EU
JUSED BY OPNT$Li

F:lLf. EXTENSION
.GLOBL.

,EXTND

DIRECTORY OPERATIONS
.GLOBL

,FINO,,ENTER,.REMOV

FILE POSITIONING

.GLOBL

,GTDlD,,GTDIR

RtAD AND WRITE FILE STORAGE REGION CELLS
.GLOBL

,RDFDR,.wDFDR,,RfOwN,,wFOwN,,RDFFP,,WDFFP

,•.•.......•..•..••......•..•...•..•.•......•...•...•••...•...•.....••.•
THE FOLLOWING MODUL.tS HAVE BEEN COMMENTED OUT TO REDUCE THE SIZE OF
THE DEFAULT FCSRES TO 8ELOW 4~q7, YOU MAY RtSTORE TH~M, BUT ONLY IF
YUU REMOVE OTHER ,GLOBL STATEMENTS,
THE FOLLOWING MODULE Is NORMALLY NOT USED, OtLET$ ls MUCH MORE COMMON
.GLOEIL

,DL.FNB

Rl!::.NAME. FILE
,GLOBL

,RENAM

ISSUE GENERAL QI/O AND SPECIAL MAGTAPE FUNCTION QI/OS

•~NI)

G-3

APPENDIX H

HELP TEXT FILES

•
Each distrib~tion kit includes a file
text source~ for the MCR Help command.

(HELP.ULB)

which

consists

For Big Disk kits, HELP.ULB can be found under the UFO [1,2].
For Dual RK05 kits, HELP.ULB is contained on the Executive source disk
(EXCSRC) under the UFO [1,2].
For RLOl kits, HELP.ULB is contained
(RLUTIL) under the UFO [1,2].

the

utility

source

disk

The following lists the steps to use the Help support from HELP.ULB:
l.

Log on privileged

Assign the default system device SY:
LB:.
For example:

'-"

the

pseudo

for

the

terminal.

device

>ASN LB:=SY:
3.

Establish [ 1, 2] as the default UIC
example:

For

>SET /UIC=[l,2]
4.

Mount the volume that contains HELP.ULB.

For example:

>MOU DKl:EXCSRC
5.

Copy HELP.ULB to the LB:
the DKl:
example):

device.

For

example

(continuing

>PIP /NV=DKl:HELP.ULB
6.

Extract the build module from
HELPBUILD.CMD. For example:

HELP .• ULB

and

name

the

file

>LBR HELPBUILD.CMD=HELP.ULB/EX:BUILD
7.

Initiate the Help build command file.

For example:

>@HELPBUILD
The Help build command file (HELPBUILD.CMD)
permits you to
build Help support for most of the MCR commands and several
of the RSX-llM utilities or you can build a skeletal Help
file.

H-1

HELP TEXT FILES
8.

When the task build completes, you can
HELPBUILD.CMD and HELP.ULB. For example:
>PIP HELPBUILD.CMD;*, HELP.ULB;*/DE

Then dismount the volume.

For example:

>OMO DKl:

H-2

delete

the

files

APPENDIX I

HARDWARE BOOTSTRAP PROCEDURES

I.l

HARDWARE BOOTSTRAP ROUTINES

This section describes the procedures for bootstrapping programs into
PDP-11 processor memory using the following PDP-11 bootstrap Read-Only
Memory pro9rams:

•

ThE~

BM792-YB Bootstrap ROM

• The MRll-DB Bootstrap ROM
• The BM873-YA Bootstrap ROM
• The BM873-YB Bootstrap ROM
• The M9301-YA and M9301-YB Bootstrap ROM'S
• The M9301-YC Bootstrap ROM (PDP-11/70 processors only)
• The M9301-YF Bootstrap ROM
RM792-YB Bootstrap ROM

I.1.1

Follow this procedure to start up the BM792-YB bootstrap ROM:
1.

Press HALT

Set the console switches to 173100.

Press LOAD ADDRESS.

Enter the address of the Load device in the console switches:
Device

Code

RKll
RFll
RPll
TCll

177406
177462
176716
177344

Disk
Disk
Disk
DECtape

Lift the HALT key.

Press START.

The system
sequence •

then

displays

the

......,,/
I-1

console

terminal

the

start-up

HARDWARE BOOTSTRAP PROCEDURES
I.1.2

MRll-DB Bootstrap ROM

Follow this procedure to start up the MRll-DB bootstrap ROM:
1.

Press HALT.

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

Code

RFll
RKll
TCll
TMll
RPll

173100
173110
173120
173136
173154

Disk
Disk
DECtape
Magtape
Disk

Press LOAD ADDRESS.

Lift the HALT key.

Press START.

The system
sequence.

I.1.3

then

displays

the

console

terminal

the

start-up

BM873-YA Bootstrap ROM

Follow this procedure to start up the BM873-YA bootstrap ROM:
1.

Press HALT.

Enter the address of the load device in the console switches:
Device
RFll DISK
RKll DISK
TCll DECTAPE
TMll MAGTAPE
RPll DISK
RCll DISK
KLll/ DLll
TAll CASSETTE
PCll PAPERTAPE

Press LOAD ADDRESS.

Lift the HALT key.

Press START.

The system
sequence.

then

displays

173000
173010
173030
173050
173100
173144
173210
173230
173312

the

I-2

console

·~.

terminal

the

start-up

HARDWARE BOOTSTRAP PROCEDURES
BM873-YB Bootstrap ROM

I.1.4

To start up the BM873-YB bootstrap ROM, follow this procedure:
1.

Press HALT.

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

Code

<RH11/RH70/RS03/RS04 Disk (unit 0)

173000

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

173002

RKll Disk (unit 0)

173030

RKll Disk (unit in switch register)

173032

TCll DECtape (unit 0)

173070

TMll Magtape (unit 0)

17 3110

RFll Disk

173136

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

173150

RH11/RH70 Device Combination (unit zero)

173230

RH11/RH70 Device Combination (unit in switch
register)

173232

RH11/RH70/RP04/RP05/RP06 Disk (unit 0)

173320

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

173322

RP11/RP02/RP03 Disk (unit 0)

173350

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

173352

KLll/DLll Console Terminal Reader

173510

TAll Cassette (unit zero)

173524

TAll Cassette (unit in switch register)

173526

PCll papertape reader

173620

Press LOAD ADDRESS. For units other than
number in switch register.

Lift the HALT key.

Press START.

The system
sequence.

then

displays

the

I-3

console

zero,

terminal

enter

the

unit

start-up

HARDWARE BOOTSTRAP PROCEDURES
M9301-YA or M9301-YB Bootstrap ROM

I.1.5

Follow this procedure to start up either the M9301-YA or the
bootstrap ROM:
1.

Press the BOOT switch.

In response to the $ prompt on the console
one of the following 2-letter codes:
Code

M9301-YB

terminal,

enter

Device

DB
DK
DP
DS
DT
DX
CT
MC
MM
MT
PR
TT

RP04 05/06 DISK M9301-YB ONLY
RKll DISK
RPll (RP02/03) DISK
RS03/04 DISK M9301-YB ONLY
TCll DECTAPE
RXll FLOPPY DISK
TAll CASSETTE TAPE
MIXED MASSBUS DEVICE M9301-YB ONLY
TM02/TU16/TU45 MAGTAPE M9301-YB ONLY
TMll/TMAll/TMBll/TUlO MAGTAPE
PCll/PRll PAPER TAPE READER
KLll/DLll CONSOLE TERMINAL READER

....

The two alphabetic characters may be followed by an optional
single octal digit for bootstrapping from units other than
zero, and terminated by a carriage return.
The system
sequence.

I.1.6

then

displays

the

console

terminal

the

start-up

M9301-YC Bootstrap (PDP-11/70 Only)

The M9301-YC bootstrap operates only on the
following steps to use this bootstrap.

PDP-11/70.

Perform

Press the HALT switch and set back to the enable position.

Set the START address of 17765000 in the console switches.

Press LOAD ADDRESS.

Set the device unit number in switches 0 through 2.

Set the device code in switches
codes are:

through

Code

Device

TM11/TU10/TS03 MAGNETIC TAPE
TC11/TU56 DECTAPE
RKll/RKOS DECPACK DISK CARTRIDGE
RP11/RP02/RP03 DISK PACK
RH70/TU16/TU45 MAGNETIC TAPE
RH70/RP04/RP05/RP06 DISK PACK
RH70/RS04/RS03 FIXED HEAD DISK

3
4
6
7

10
6.

Ensure that switches 7 through 21 are off (down).

Press START.

I-4

The

the

device

)

HARDWARE BOOTSTRAP PROCEDURES
The system
sequence.

then

displays

the

console

terminal

the

start-up

it performs
Before the M9301-YC bootstrap actually boots the system,
CPU tests,
instruction and addressing tests, and memory and cache
tests.
If a hardware failure is detected, and diagnostic program
halts.
The lights contain the ROM address of the HALT.
If this
occurs, call the Digital Field Service Engineer.
It may, however, be possible to continue with the bootstrap operation
if the lights contain the address 17773764, which indicates a cache
failure.
To continue in this case, press cont. This is the only case
in which it is possible to continue bootstrapping after the diagnostic
detects an error.

I.1.7

M9301-YF Bootstrap ROM

The following instructions bootstrap the system by means of the
M9301-YF console emulator.
Refer to the M9301 Bootstrap/Terminator
Maintenance Manual, for other ways to boot the system with the
M930l-YF.
Follow this procedure at the operator's terminal:
l.

Press the console BOOT switch.
If diagnostics are enabledl, the
CPU diagnostics.

M9301-YF

performs

primary

The terminal then displays the contents of RO, R4, SP, and
RS,
respectively;
the contents appear as four 16-bit octal
numbers. Note that pressing the boot switch at this time
causes PDP-11 systems without console registers to copy the
PC into RS before the power-up sequence begins.
The terminal then displays the prompt $ at the beginning of a
new line.
2.

In response to the prompt $, type the appropriate device code
at the terminal, followed by carriage return:
Code

Device

DBN
DKN
DMN
DSN
DTN
DXN
MMN
MTN
PR
TT

RP04, RPOS, RP06, DISK
RKOS DISK
RK06 DISK
RS03 OR RS04 DISK
TU56 DECTAPE
RXOl FLOPPY DISK
TU16 MAGNETIC TAPE
TUlO MAGNETIC TAPE
PCll PAPER TAPE READER
DLll CONSOLE TERMINAL READER

1 The M9301-YF micro switches must be set to
000 to perform
diagnostics when using the console emulator to boot the system.
If
the switches are set to 002, the M9301-YF console emulator boots the
system without performing diagnostics.
Consult a Digital Field
Service Engineer or see the M930l Bootstrap/Terminator Maintenance
Manual.

----

I-5

HARDWARE BOOTSTRAP PROCEDURES
In the list of codes above, n represents the device unit
number;
the only permissible values are O through 7. The
unit number can be omitted if it is O.
If diagnostics are enabled, the M9301-YF performs secondary
CPU and memory diagnostics before booting the system.
The system
sequence.

then

displays

the

console

terminal

the

start-up

I-6

RSX-llM
System Generation and
Management Guide
AA-H625A-TC

READER'S COMMENTS

NOTE:

This form is for document comments only. DIGITAL will
use comments submitted on this form at the company's
discretion.
If you require a written reply and are
eligible to receive one under Software Performance
Report (SPR) service, submit your comments on an SPR
form.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement •

Did you find errors in this manual?
pa1ge number.

If so, specify the error and the

Please indicate the type of reader that you most nearly represent.
[] Assembly language programmer
[] Higher-level language programmer
[] Occasional programmer (experienced)
[] User with little programming experience
[] Student programmer
[] Other (please specify)

Na.me
Organization~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Street~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

City.

~~~~·~~~~~~~State~~~~~~-Zip Code~~~~~~

or
Country

DoNotTear-FoldHereandTape -

~n~nomo

No Postage
Necessary
if Mailed in the
United States

111111

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

RT/C SOFTWARE PUBLICATIONS

TW/A14

DIGITAL EQUIPMENT CORPORATION
1925 ANDOVER STREET
TEWKSBURY, MASSACHUSETTS

-· -

Do Not Tear - Fold Here

01876

"'O
Q)

0
Q

l:)J)

=
0

-•

<
::s
u

I
I